1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged debian
</title>
5 <description>Entries tagged debian
</description>
6 <link>https://people.skolelinux.org/pere/blog/
</link>
10 <title>Test framework for DocBook processors / formatters
</title>
11 <link>https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html
</link>
12 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html
</guid>
13 <pubDate>Sun,
5 Nov
2023 13:
00:
00 +
0100</pubDate>
14 <description><p
>All the books I have published so far has been using
15 <a href=
"https://docbook.org/
">DocBook
</a
> somewhere in the process.
16 For the first book, the source format was DocBook, while for every
17 later book it was an intermediate format used as the stepping stone to
18 be able to present the same manuscript in several formats, on paper,
19 as ebook in ePub format, as a HTML page and as a PDF file either for
20 paper production or for Internet consumption. This is made possible
21 with a wide variety of free software tools with DocBook support in
22 Debian. The source format of later books have been docx via rst,
23 Markdown, Filemaker and Asciidoc, and for all of these I was able to
24 generate a suitable DocBook file for further processing using
25 <a href=
"https://tracker.debian.org/pkg/pandoc
">pandoc
</a
>,
26 <a href=
"https://tracker.debian.org/pkg/asciidoc
">a2x
</a
> and
27 <a href=
"https://tracker.debian.org/pkg/asciidoctor
">asciidoctor
</a
>,
28 as well as rendering using
29 <a href=
"https://tracker.debian.org/pkg/xmlto
">xmlto
</a
>,
30 <a href=
"https://tracker.debian.org/pkg/dbtoepub
">dbtoepub
</a
>,
31 <a href=
"https://tracker.debian.org/pkg/dblatex
">dblatex
</a
>,
32 <a href=
"https://tracker.debian.org/pkg/dblatex
">docbook-xsl
</a
> and
33 <a href=
"https://tracker.debian.org/pkg/fop
">fop
</a
>.
</p
>
35 <p
>Most of the
<a href=
"http://www.hungry.com/~pere/publisher/
">books I
36 have published
</a
> are translated books, with English as the source
38 <a href=
"https://tracker.debian.org/pkg/po4a
">po4a
</a
> to
39 handle translations using the gettext PO format has been a blessing,
40 but publishing translated books had triggered the need to ensure the
41 DocBook tools handle relevant languages correctly. For every new
42 language I have published, I had to submit patches dblatex, dbtoepub
43 and docbook-xsl fixing incorrect language and country specific issues
44 in the framework themselves. Typically this has been missing keywords
45 like
'figure
' or sort ordering of index entries. After a while it
46 became tiresome to only discover issues like this by accident, and I
47 decided to write a DocBook
"test framework
" exercising various
48 features of DocBook and allowing me to see all features exercised for
49 a given language. It consist of a set of DocBook files, a version
4
50 book, a version
5 book, a v4 book set, a v4 selection of problematic
51 tables, one v4 testing sidefloat and finally one v4 testing a book of
52 articles. The DocBook files are accompanied with a set of build rules
53 for building PDF using dblatex and docbook-xsl/fop, HTML using xmlto
54 or docbook-xsl and epub using dbtoepub. The result is a set of files
55 visualizing footnotes, indexes, table of content list, figures,
56 formulas and other DocBook features, allowing for a quick review on
57 the completeness of the given locale settings. To build with a
58 different language setting, all one need to do is edit the lang= value
59 in the .xml file to pick a different ISO
639 code value and run
60 'make
'.
</p
>
62 <p
>The
<a href=
"https://codeberg.org/pere/docbook-example/
">test framework
63 source code
</a
> is available from Codeberg, and a generated set of
64 presentations of the various examples is available as Codeberg static
66 <a href=
"https://pere.codeberg.page/docbook-example/
">https://pere.codeberg.page/docbook-example/
</a
>.
67 Using this test framework I have been able to discover and report
68 several bugs and missing features in various tools, and got a lot of
69 them fixed. For example I got Northern Sami keywords added to both
70 docbook-xsl and dblatex, fixed several typos in Norwegian bokmål and
71 Norwegian Nynorsk, support for non-ascii title IDs added to pandoc,
72 Norwegian index sorting support fixed in xindy and initial Norwegian
73 Bokmål support added to dblatex. Some issues still remains, though.
74 Default index sorting rules are still broken in several tools, so the
75 Norwegian letters æ, ø and å are more often than not sorted properly
76 in the book index.
</p
>
78 <p
>The test framework recently received some more polish, as part of
79 publishing my latest book. This book contained a lot of fairly
80 complex tables, which exposed bugs in some of the tools. This made me
81 add a new test file with various tables, as well as spend some time to
82 brush up the build rules. My goal is for the test framework to
83 exercise all DocBook features to make it easier to see which features
84 work with different processors, and hopefully get them all to support
85 the full set of DocBook features. Feel free to send patches to extend
86 the test set, and test it with your favorite DocBook processor.
87 Please visit these two URLs to learn more:
</p
>
90 <li
><a href=
"https://codeberg.org/pere/docbook-example/
">https://codeberg.org/pere/docbook-example/
</a
></li
>
91 <li
><a href=
"https://pere.codeberg.page/docbook-example/
">https://pere.codeberg.page/docbook-example/
</a
></li
>
94 <p
>If you want to learn more on Docbook and translations, I recommend
95 having a look at the
<a href=
"https://docbook.org/
">the DocBook
97 <a href=
"https://doccookbook.sourceforge.net/html/en/
">the DoCookBook
98 site
<a/
> and my earlier blog post on
99 <a href=
"https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
">how
100 the Skolelinux project process and translate documentation
</a
>, a talk I gave earlier this year on
101 <a href=
"https://www.nuug.no/aktiviteter/
20230314-oversetting-og-publisering-av-b%c3%b8ker-med-fri-programvare/
">how
102 to translate and publish books using free software
</a
> (Norwegian
107 https://github.com/docbook/xslt10-stylesheets/issues/
205 (docbook-xsl: sme support)
108 https://bugs.debian.org/
968437 (xindy: index sorting rules for nb/nn)
109 https://bugs.debian.org/
856123 (pandoc: markdown to docbook with non-english titles)
110 https://bugs.debian.org/
864813 (dblatex: missing nb words)
111 https://bugs.debian.org/
756386 (dblatex: index sorting rules for nb/nn)
112 https://bugs.debian.org/
796871 (dbtoepub: index sorting rules for nb/nn)
113 https://bugs.debian.org/
792616 (dblatex: PDF metadata)
114 https://bugs.debian.org/
686908 (docbook-xsl: index sorting rules for nb/nn)
115 https://sourceforge.net/tracker/?func=detail
&atid=
373747&aid=
3556630&group_id=
21935 (docbook-xsl: nb/nn support)
116 https://bugs.debian.org/
684391 (dblatex: initial nb support)
120 <p
>As usual, if you use Bitcoin and want to show your support of my
121 activities, please send Bitcoin donations to my address
122 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
127 <title>What did I learn from OpenSnitch this summer?
</title>
128 <link>https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html
</link>
129 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_did_I_learn_from_OpenSnitch_this_summer_.html
</guid>
130 <pubDate>Sun,
11 Jun
2023 08:
30:
00 +
0200</pubDate>
131 <description><p
>With yesterdays
132 <a href=
"https://www.debian.org/News/
2023/
20230610">release of Debian
133 12 Bookworm
</a
>, I am happy to know the
134 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
135 application firewall OpenSnitch
</a
> is available for a wider audience.
136 I have been running it for a few weeks now, and have been surprised
137 about some of the programs connecting to the Internet. Some programs
138 are obviously calling out from my machine, like the NTP network based
139 clock adjusting system and Tor to reach other Tor clients, but others
140 were more dubious. For example, the KDE Window manager try to look up
141 the host name in DNS, for no apparent reason, but if this lookup is
142 blocked the KDE desktop get periodically stuck when I use it. Another
143 surprise was how much Firefox call home directly to mozilla.com,
144 mozilla.net and googleapis.com, to mention a few, when I visit other
145 web pages. This direct connection happen even if I told Firefox to
146 always use a proxy, and the proxy setting is ignored for this traffic.
147 Other surprising connections come from audacity and dirmngr (I do not
148 use Gnome). It took some trial and error to get a good default set of
149 permissions. Without it, I would get popups asking for permissions at
150 any time, also the most inconvenient ones where I am in the middle of
151 a time sensitive gaming session.
</p
>
153 <p
>I suspect some application developers should rethink when then need
154 to use network connections or DNS lookups, and recommend testing
155 OpenSnitch (only
<tt
>apt install opensnitch
</tt
> away in Debian
156 Bookworm) to locate and report any surprising Internet connections on
157 your desktop machine.
</p
>
159 <p
>At the moment the upstream developer and Debian package maintainer
160 is working on making the system more reliable in Debian, by enabling
161 the eBPF kernel module to track processes and connections instead of
162 depending in content in /proc/. This should enter unstable fairly
165 <p
>As usual, if you use Bitcoin and want to show your support of my
166 activities, please send Bitcoin donations to my address
167 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
169 <p
><strong
>Update
2023-
06-
12</strong
>: I got a tip about
170 <a href=
"https://wiki.debian.org/PrivacyIssues
">a list of privacy
171 issues in Free Software
</a
> and the
172 <a href=
"irc://irc.debian.org/%
23debian-privacy
">#debian-privacy IRC
173 channel
</a
> discussing these topics.
</p
>
179 <title>wmbusmeters, parse data from your utility meter - nice free software
</title>
180 <link>https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html
</link>
181 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/wmbusmeters__parse_data_from_your_utility_meter___nice_free_software.html
</guid>
182 <pubDate>Fri,
19 May
2023 21:
50:
00 +
0200</pubDate>
183 <description><p
>There is a European standard for reading utility meters like water,
184 gas, electricity or heat distribution meters. The
185 <a href=
"https://en.wikipedia.org/wiki/Meter-Bus
">Meter-Bus standard
186 (EN
13757-
2, EN
13757-
3 and EN
13757–
4)
</a
> provide a cross vendor way
187 to talk to and collect meter data. I ran into this standard when I
188 wanted to monitor some heat distribution meters, and managed to find
189 free software that could do the job. The meters in question broadcast
190 encrypted messages with meter information via radio, and the hardest
191 part was to track down the encryption keys from the vendor. With this
192 in place I could set up a MQTT gateway to submit the meter data for
195 <p
>The free software systems in question,
196 <a href=
"https://tracker.debian.org/pkg/rtl-wmbus
">rtl-wmbus
</a
> to
197 read the messages from a software defined radio, and
198 <a href=
"https://tracker.debian.org/pkg/wmbusmeters
">wmbusmeters
</a
> to
199 decrypt and decode the content of the messages, is working very well
200 and allowe me to get frequent updates from my meters. I got in touch
201 with upstream last year to see if there was any interest in publishing
202 the packages via Debian. I was very happy to learn that Fredrik
203 Öhrström volunteered to maintain the packages, and I have since
204 assisted him in getting Debian package build rules in place as well as
205 sponsoring the packages into the Debian archive. Sadly we completed
206 it too late for them to become part of the next stable Debian release
207 (Bookworm). The wmbusmeters package just cleared the NEW queue. It
208 will need some work to fix a built problem, but I expect Fredrik will
209 find a solution soon.
</p
>
211 <p
>If you got a infrastructure meter supporting the Meter Bus
212 standard, I strongly recommend having a look at these nice
215 <p
>As usual, if you use Bitcoin and want to show your support of my
216 activities, please send Bitcoin donations to my address
217 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
222 <title>The
2023 LinuxCNC Norwegian developer gathering
</title>
223 <link>https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html
</link>
224 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_2023_LinuxCNC_Norwegian_developer_gathering.html
</guid>
225 <pubDate>Sun,
14 May
2023 20:
30:
00 +
0200</pubDate>
226 <description><p
>The LinuxCNC project is making headway these days. A lot of
227 patches and issues have seen activity on
228 <a href=
"https://github.com/LinuxCNC/linuxcnc/
">the project github
229 pages
</a
> recently. A few weeks ago there was a developer gathering
230 over at the
<a href=
"https://tormach.com/
">Tormach
</a
> headquarter in
231 Wisconsin, and now we are planning a new gathering in Norway. If you
232 wonder what LinuxCNC is, lets quote Wikipedia:
</p
>
235 "LinuxCNC is a software system for numerical control of
236 machines such as milling machines, lathes, plasma cutters, routers,
237 cutting machines, robots and hexapods. It can control up to
9 axes or
238 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
239 several GUIs suited to specific kinds of usage (touch screen,
240 interactive development).
"
243 <p
>The Norwegian developer gathering take place the weekend June
16th
244 to
18th this year, and is open for everyone interested in contributing
245 to LinuxCNC. Up to date information about the gathering can be found
247 <a href=
"https://sourceforge.net/p/emc/mailman/emc-developers/thread/sa64jp06nob.fsf%
40hjemme.reinholdtsen.name/#msg37837251
">the
248 developer mailing list thread
</a
> where the gathering was announced.
249 Thanks to the good people at
250 <a href=
"https://www.debian.org/
">Debian
</a
>,
251 <a href=
"https://www.redpill-linpro.com/
">Redpill-Linpro
</a
> and
252 <a href=
"https://www.nuugfoundation.no/no/
">NUUG Foundation
</a
>, we
253 have enough sponsor funds to pay for food, and shelter for the people
254 traveling from afar to join us. If you would like to join the
255 gathering, get in touch.
</p
>
257 <p
>As usual, if you use Bitcoin and want to show your support of my
258 activities, please send Bitcoin donations to my address
259 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
264 <title>OpenSnitch in Debian ready for prime time
</title>
265 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html
</link>
266 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_in_Debian_ready_for_prime_time.html
</guid>
267 <pubDate>Sat,
13 May
2023 12:
10:
00 +
0200</pubDate>
268 <description><p
>A bit delayed,
269 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
270 application firewall OpenSnitch
</a
> package in Debian now got the
271 latest fixes ready for Debian Bookworm. Because it depend on a
272 package missing on some architectures, the autopkgtest check of the
273 testing migration script did not understand that the tests were
274 actually working, so the migration was delayed. A bug in the package
275 dependencies is also fixed, so those installing the firewall package
276 (opensnitch) now also get the GUI admin tool (python3-opensnitch-ui)
277 installed by default. I am very grateful to Gustavo Iñiguez Goya for
278 his work on getting the package ready for Debian Bookworm.
</p
>
280 <p
>Armed with this package I have discovered some surprising
281 connections from programs I believed were able to work completly
282 offline, and it has already proven its worth, at least to me. If you
283 too want to get more familiar with the kind of programs using
284 Internett connections on your machine, I recommend testing
<tt
>apt
285 install opensnitch
</tt
> in Bookworm and see what you think.
</p
>
287 <p
>The package is still not able to build its eBPF module within
288 Debian. Not sure how much work it would be to get it working, but
289 suspect some kernel related packages need to be extended with more
290 header files to get it working.
</p
>
292 <p
>As usual, if you use Bitcoin and want to show your support of my
293 activities, please send Bitcoin donations to my address
294 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
299 <title>Speech to text, she APTly whispered, how hard can it be?
</title>
300 <link>https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</link>
301 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speech_to_text__she_APTly_whispered__how_hard_can_it_be_.html
</guid>
302 <pubDate>Sun,
23 Apr
2023 09:
40:
00 +
0200</pubDate>
303 <description><p
>While visiting a convention during Easter, it occurred to me that
304 it would be great if I could have a digital Dictaphone with
305 transcribing capabilities, providing me with texts to cut-n-paste into
306 stuff I need to write. The background is that long drives often bring
307 up the urge to write on texts I am working on, which of course is out
308 of the question while driving. With the release of
309 <a href=
"https://github.com/openai/whisper/
">OpenAI Whisper
</a
>, this
310 seem to be within reach with Free Software, so I decided to give it a
311 go. OpenAI Whisper is a Linux based neural network system to read in
312 audio files and provide text representation of the speech in that
313 audio recording. It handle multiple languages and according to its
314 creators even can translate into a different language than the spoken
315 one. I have not tested the latter feature. It can either use the CPU
316 or a GPU with CUDA support. As far as I can tell, CUDA in practice
317 limit that feature to NVidia graphics cards. I have few of those, as
318 they do not work great with free software drivers, and have not tested
319 the GPU option. While looking into the matter, I did discover some
320 work to provide CUDA support on non-NVidia GPUs, and some work with
321 the library used by Whisper to port it to other GPUs, but have not
322 spent much time looking into GPU support yet. I
've so far used an old
323 X220 laptop as my test machine, and only transcribed using its
326 <p
>As it from a privacy standpoint is unthinkable to use computers
327 under control of someone else (aka a
"cloud
" service) to transcribe
328 ones thoughts and personal notes, I want to run the transcribing
329 system locally on my own computers. The only sensible approach to me
330 is to make the effort I put into this available for any Linux user and
331 to upload the needed packages into Debian. Looking at Debian Bookworm, I
332 discovered that only three packages were missing,
333 <a href=
"https://bugs.debian.org/
1034307">tiktoken
</a
>,
334 <a href=
"https://bugs.debian.org/
1034144">triton
</a
>, and
335 <a href=
"https://bugs.debian.org/
1034091">openai-whisper
</a
>. For a while
337 <a href=
"https://bugs.debian.org/
1034286">ffmpeg-python
</a
> was
339 <a href=
"https://github.com/kkroening/ffmpeg-python/issues/
760">upstream
340 seem to have vanished
</a
> I found it safer
341 <a href=
"https://github.com/openai/whisper/pull/
1242">to rewrite
342 whisper
</a
> to stop depending on in than to introduce ffmpeg-python
343 into Debian. I decided to place these packages under the umbrella of
344 <a href=
"https://salsa.debian.org/deeplearning-team
">the Debian Deep
345 Learning Team
</a
>, which seem like the best team to look after such
346 packages. Discussing the topic within the group also made me aware
347 that the triton package was already a future dependency of newer
348 versions of the torch package being planned, and would be needed after
349 Bookworm is released.
</p
>
351 <p
>All required code packages have been now waiting in
352 <a href=
"https://ftp-master.debian.org/new.html
">the Debian NEW
353 queue
</a
> since Wednesday, heading for Debian Experimental until
354 Bookworm is released. An unsolved issue is how to handle the neural
355 network models used by Whisper. The default behaviour of Whisper is
356 to require Internet connectivity and download the model requested to
357 <tt
>~/.cache/whisper/
</tt
> on first invocation. This obviously would
358 fail
<a href=
"https://people.debian.org/~bap/dfsg-faq.html
">the
359 deserted island test of free software
</a
> as the Debian packages would
360 be unusable for someone stranded with only the Debian archive and solar
361 powered computer on a deserted island.
</p
>
363 <p
>Because of this, I would love to include the models in the Debian
364 mirror system. This is problematic, as the models are very large
365 files, which would put a heavy strain on the Debian mirror
366 infrastructure around the globe. The strain would be even higher if
367 the models change often, which luckily as far as I can tell they do
368 not. The small model, which according to its creator is most useful
369 for English and in my experience is not doing a great job there
370 either, is
462 MiB (deb is
414 MiB). The medium model, which to me
371 seem to handle English speech fairly well is
1.5 GiB (deb is
1.3 GiB)
372 and the large model is
2.9 GiB (deb is
2.6 GiB). I would assume
373 everyone with enough resources would prefer to use the large model for
374 highest quality. I believe the models themselves would have to go
375 into the non-free part of the Debian archive, as they are not really
376 including any useful source code for updating the models. The
377 "source
", aka the model training set, according to the creators
378 consist of
"680,
000 hours of multilingual and multitask supervised
379 data collected from the web
", which to me reads material with both
380 unknown copyright terms, unavailable to the general public. In other
381 words, the source is not available according to the Debian Free
382 Software Guidelines and the model should be considered non-free.
</p
>
384 <p
>I asked the Debian FTP masters for advice regarding uploading a
385 model package on their IRC channel, and based on the feedback there it
386 is still unclear to me if such package would be accepted into the
387 archive. In any case I wrote build rules for a
388 <a href=
"https://salsa.debian.org/deeplearning-team/openai-whisper-model
">OpenAI
389 Whisper model package
</a
> and
390 <a href=
"https://github.com/openai/whisper/pull/
1257">modified the
391 Whisper code base
</a
> to prefer shared files under
<tt
>/usr/
</tt
> and
392 <tt
>/var/
</tt
> over user specific files in
<tt
>~/.cache/whisper/
</tt
>
393 to be able to use these model packages, to prepare for such
394 possibility. One solution might be to include only one of the models
395 (small or medium, I guess) in the Debian archive, and ask people to
396 download the others from the Internet. Not quite sure what to do
397 here, and advice is most welcome (use the debian-ai mailing list).
</p
>
399 <p
>To make it easier to test the new packages while I wait for them to
400 clear the NEW queue, I created an APT source targeting bookworm. I
401 selected Bookworm instead of Bullseye, even though I know the latter
402 would reach more users, is that some of the required dependencies are
403 missing from Bullseye and I during this phase of testing did not want
404 to backport a lot of packages just to get up and running.
</p
>
406 <p
>Here is a recipe to run as user root if you want to test OpenAI
407 Whisper using Debian packages on your Debian Bookworm installation,
408 first adding the APT repository GPG key to the list of trusted keys,
409 then setting up the APT repository and finally installing the packages
410 and one of the models:
</p
>
413 curl https://geekbay.nuug.no/~pere/openai-whisper/D78F5C4796F353D211B119E28200D9B589641240.asc \
414 -o /etc/apt/trusted.gpg.d/pere-whisper.asc
415 mkdir -p /etc/apt/sources.list.d
416 cat
> /etc/apt/sources.list.d/pere-whisper.list
&lt;
&lt;EOF
417 deb https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
418 deb-src https://geekbay.nuug.no/~pere/openai-whisper/ bookworm main
421 apt install openai-whisper
422 </pre
></p
>
424 <p
>The package work for me, but have not yet been tested on any other
425 computer than my own. With it, I have been able to (badly) transcribe
426 a
2 minute
40 second Norwegian audio clip to test using the small
427 model. This took
11 minutes and around
2.2 GiB of RAM. Transcribing
428 the same file with the medium model gave a accurate text in
77 minutes
429 using around
5.2 GiB of RAM. My test machine had too little memory to
430 test the large model, which I believe require
11 GiB of RAM. In
431 short, this now work for me using Debian packages, and I hope it will
432 for you and everyone else once the packages enter Debian.
</p
>
434 <p
>Now I can start on the audio recording part of this project.
</p
>
436 <p
>As usual, if you use Bitcoin and want to show your support of my
437 activities, please send Bitcoin donations to my address
438 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
443 <title>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software
</title>
444 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</link>
445 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</guid>
446 <pubDate>Fri,
7 Apr
2023 23:
10:
00 +
0200</pubDate>
447 <description><p
>Today I finally found time to track down a useful radio frequency
448 scanner for my software defined radio. Just for fun I tried to locate
449 the radios used in the areas, and a good start would be to scan all
450 the frequencies to see what is in use. I
've tried to find a useful
451 program earlier, but ran out of time before I managed to find a useful
452 tool. This time I was more successful, and after a few false leads I
453 found a description of
454 <a href=
"https://www.kali.org/tools/rtlsdr-scanner/
">rtlsdr-scanner
455 over at the Kali site
</a
>, and was able to track down
456 <a href=
"https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git
">the
457 Kali package git repository
</a
> to build a deb package for the
458 scanner. Sadly the package is missing from the Debian project itself,
459 at least in Debian Bullseye. Two runtime dependencies,
460 <a href=
"https://gitlab.com/kalilinux/packages/python-visvis.git
">python-visvis
</a
>
462 <a href=
"https://gitlab.com/kalilinux/packages/python-rtlsdr.git
">python-rtlsdr
</a
>
463 had to be built and installed separately. Luckily
'<tt
>gbp
464 buildpackage
</tt
>' handled them just fine and no further packages had
465 to be manually built. The end result worked out of the box after
466 installation.
</p
>
468 <p
>My initial scans for FM channels worked just fine, so I knew the
469 scanner was functioning. But when I tried to scan every frequency
470 from
100 to
1000 MHz, the program stopped unexpectedly near the
471 completion. After some debugging I discovered USB software radio I
472 used rejected frequencies above
948 MHz, triggering a unreported
473 exception breaking the scan. Changing the scan to end at
957 worked
474 better. I similarly found the lower limit to be around
15, and ended
475 up with the following full scan:
</p
>
477 <p
><a href=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
" width=
"100%
"></a
></p
>
479 <p
>Saving the scan did not work, but exporting it as a CSV file worked
480 just fine. I ended up with around
477k CVS lines with dB level for
481 the given frequency.
</p
>
483 <p
>The save failure seem to be a missing UTF-
8 encoding issue in the
484 python code. Will see if I can find time to send a patch
485 <a href=
"https://github.com/CdeMills/RTLSDR-Scanner/
">upstream
</a
>
486 later to fix this exception:
</p
>
489 Traceback (most recent call last):
490 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
491 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
492 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
493 handle.write(json.dumps(data, indent=
4))
494 TypeError: a bytes-like object is required, not
'str
'
495 Traceback (most recent call last):
496 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
497 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
498 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
499 handle.write(json.dumps(data, indent=
4))
500 TypeError: a bytes-like object is required, not
'str
'
503 <p
>As usual, if you use Bitcoin and want to show your support of my
504 activities, please send Bitcoin donations to my address
505 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
510 <title>OpenSnitch available in Debian Sid and Bookworm
</title>
511 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</link>
512 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</guid>
513 <pubDate>Sat,
25 Feb
2023 20:
30:
00 +
0100</pubDate>
514 <description><p
>Thanks to the efforts of the OpenSnitch lead developer Gustavo
515 Iñiguez Goya allowing me to sponsor the upload,
516 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
517 application firewall OpenSnitch
</a
> is now available in Debian
518 Testing, soon to become the next stable release of Debian.
</p
>
520 <p
>This is a package which set up a network firewall on one or more
521 machines, which is controlled by a graphical user interface that will
522 ask the user if a program should be allowed to connect to the local
523 network or the Internet. If some background daemon is trying to dial
524 home, it can be blocked from doing so with a simple mouse click, or by
525 default simply by not doing anything when the GUI question dialog pop
526 up. A list of all programs discovered using the network is provided
527 in the GUI, giving the user an overview of how the machine(s) programs
528 use the network.
</p
>
530 <p
>OpenSnitch was uploaded for NEW processing about a month ago, and I
531 had little hope of it getting accepted and shaping up in time for the
532 package freeze, but the Debian ftpmasters proved to be amazingly quick
533 at checking out the package and it was accepted into the archive about
534 week after the first upload. It is now team maintained under the Go
535 language team umbrella. A few fixes to the default setup is only in
536 Sid, and should migrate to Testing/Bookworm in a week.
</p
>
538 <p
>During testing I ran into an
539 <a href=
"https://github.com/evilsocket/opensnitch/issues/
813">issue
540 with Minecraft server broadcasts disappearing
</a
>, which was quickly
541 resolved by the developer with a patch and a proposed configuration
542 change. I
've been told this was caused by the Debian packages default
543 use if /proc/ information to track down kernel status, instead of the
544 newer eBPF module that can be used. The reason is simply that
545 upstream and I have failed to find a way to build the eBPF modules for
546 OpenSnitch without a complete configured Linux kernel source tree,
547 which as far as we can tell is unavailable as a build dependency in
548 Debian. We tried unsuccessfully so far to use the kernel-headers
549 package. It would be great if someone could provide some clues how to
550 build eBPF modules on build daemons in Debian, possibly without the full
551 kernel source.
</p
>
553 <p
>As usual, if you use Bitcoin and want to show your support of my
554 activities, please send Bitcoin donations to my address
555 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
560 <title>Is the desktop recommending your program for opening its files?
</title>
561 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</link>
562 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</guid>
563 <pubDate>Sun,
29 Jan
2023 11:
00:
00 +
0100</pubDate>
564 <description><p
>Linux desktop systems
565 <a href=
"https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
">have
566 standardized
</a
> how programs present themselves to the desktop
567 system. If a package include a .desktop file in
568 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
569 environments will pick up the file and use its content to generate the
570 menu of available programs in the system. A lesser known fact is that
571 a package can also explain to the desktop system how to recognize the
572 files created by the program in question, and use it to open these
573 files on request, for example via a GUI file browser.
</p
>
575 <p
>A while back I ran into a package that did not tell the desktop
576 system how to recognize its files and was not used to open its files
577 in the file browser and fixed it. In the process I wrote a simple
578 debian/tests/ script to ensure the setup keep working. It might be
579 useful for other packages too, to ensure any future version of the
580 package keep handling its own files.
</p
>
582 <p
>For this to work the file format need a useful MIME type that can
583 be used to identify the format. If the file format do not yet have a
584 MIME type, it should define one and preferably also
585 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">register
586 it with IANA
</a
> to ensure the MIME type string is reserved.
</p
>
588 <p
>The script uses the
<tt
>xdg-mime
</tt
> program from xdg-utils to
589 query the database of standardized package information and ensure it
590 return sensible values. It also need the location of an example file
591 for xdg-mime to guess the format of.
</p
>
596 # Author: Petter Reinholdtsen
597 # License: GPL v2 or later at your choice.
599 # Validate the MIME setup, making sure motor types have
600 # application/vnd.openmotor+yaml associated with them and is connected
601 # to the openmotor desktop file.
605 mimetype=
"application/vnd.openmotor+yaml
"
606 testfile=
"test/data/real/o3100/motor.ric
"
607 mydesktopfile=
"openmotor.desktop
"
609 filemime=
"$(xdg-mime query filetype
"$testfile
")
"
611 if [
"$mimetype
" !=
"$filemime
" ] ; then
613 echo
"error: xdg-mime claim motor file MIME type is $filemine, not $mimetype
"
615 echo
"success: xdg-mime report correct mime type $mimetype for motor file
"
618 desktop=$(xdg-mime query default
"$mimetype
")
620 if [
"$mydesktopfile
" !=
"$desktop
" ]; then
622 echo
"error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile
"
624 echo
"success: xdg-mime agree motor file should be handled by $mydesktopfile
"
630 <p
>It is a simple way to ensure your users are not very surprised when
631 they try to open one of your file formats in their file browser.
</p
>
633 <p
>As usual, if you use Bitcoin and want to show your support of my
634 activities, please send Bitcoin donations to my address
635 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
640 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive
</title>
641 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</link>
642 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</guid>
643 <pubDate>Sun,
22 Jan
2023 23:
55:
00 +
0100</pubDate>
644 <description><p
>While reading a
645 <a href=
"https://sneak.berlin/
20230115/macos-scans-your-local-files-now/
">blog
646 post claiming MacOS X recently started scanning local files and
647 reporting information about them to Apple
</a
>, even on a machine where
648 all such callback features had been disabled, I came across a
649 description of the Little Snitch application for MacOS X. It seemed
650 like a very nice tool to have in the tool box, and I decided to see if
651 something similar was available for Linux.
</p
>
653 <p
>It did not take long to find
654 <a href=
"https://github.com/evilsocket/opensnitch
">the OpenSnitch
655 package
</a
>, which has been in development since
2017, and now is in
656 version
1.5.0. It has had a
657 <a href=
"https://bugs.debian.org/
909567">request for Debian
658 packaging
</a
> since
2018, but no-one completed the job so far. Just
659 for fun, I decided to see if I could help, and I was very happy to
661 <a href=
"https://github.com/evilsocket/opensnitch/issues/
304">upstream
662 want a Debian package too
</a
>.
</p
>
664 <p
>After struggling a bit with getting the program to run, figuring
665 out building Go programs (and a little failed detour to look at eBPF
666 builds too - help needed), I am very happy to report that I am
667 sponsoring upstream to maintain the package in Debian, and it has
668 since this morning been waiting in NEW for the ftpmasters to have a
669 look. Perhaps it can get into the archive in time for the Bookworm
672 <p
>As usual, if you use Bitcoin and want to show your support of my
673 activities, please send Bitcoin donations to my address
674 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
679 <title>LinuxCNC MQTT publisher component
</title>
680 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</link>
681 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</guid>
682 <pubDate>Sun,
8 Jan
2023 19:
30:
00 +
0100</pubDate>
683 <description><p
>I watched
<a href=
"https://yewtu.be/watch?v=jmKUV3aNLjk
">a
2015
684 video from Andreas Schiffler
</a
> the other day, where he set up
685 <a href=
"https://linuxcnc.org/
">LinuxCNC
</a
> to send status
686 information to the MQTT broker IBM Bluemix. As I also use MQTT for
687 graphing, it occured to me that a generic MQTT LinuxCNC component
688 would be useful and I set out to implement it. Today I got the first
689 draft limping along and submitted as
690 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
2253">a patch to the
691 LinuxCNC project
</a
>.
</p
>
693 <p
>The simple part was setting up the MQTT publishing code in Python.
694 I already have set up other parts submitting data to my Mosquito MQTT
695 broker, so I could reuse that code. Writing a LinuxCNC component in
696 Python as new to me, but using existing examples in the code
697 repository and the extensive documentation, this was fairly straight
698 forward. The hardest part was creating a automated test for the
699 component to ensure it was working. Testing it in a simulated
700 LinuxCNC machine proved very useful, as I discovered features I needed
701 that I had not thought of yet, and adjusted the code quite a bit to
702 make it easier to test without a operational MQTT broker
705 <p
>The draft is ready and working, but I am unsure which LinuxCNC HAL
706 pins I should collect and publish by default (in other words, the
707 default set of information pieces published), and how to get the
708 machine name from the LinuxCNC INI file. The latter is a minor
709 detail, but I expect it would be useful in a setup with several
710 machines available. I am hoping for feedback from the experienced
711 LinuxCNC developers and users, to make the component even better
712 before it can go into the mainland LinuxCNC code base.
</p
>
714 <p
>Since I started on the MQTT component, I came across
715 <a href=
"https://yewtu.be/watch?v=Bqa2grG0XtA
">another video from Kent
716 VanderVelden
</a
> where he combine LinuxCNC with a set of screen glasses
717 controlled by a Raspberry Pi, and it occured to me that it would
718 be useful for such use cases if LinuxCNC also provided a REST API for
719 querying its status. I hope to start on such component once the MQTT
720 component is working well.
</p
>
722 <p
>As usual, if you use Bitcoin and want to show your support of my
723 activities, please send Bitcoin donations to my address
724 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
729 <title>ONVIF IP camera management tool finally in Debian
</title>
730 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</link>
731 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</guid>
732 <pubDate>Sat,
24 Dec
2022 08:
00:
00 +
0100</pubDate>
733 <description><p
>Merry Christmas to you all. Here is a small gift to all those with
734 IP cameras following the
<a href=
"https://www.onvif.org/
">ONVIF
735 specification
</a
>. There is finally a nice command line and GUI tool
736 in Debian to manage ONVIF IP cameras. After working with upstream for
737 a few months and sponsoring the upload, I am very happy to report that
738 the
<a href=
"https://tracker.debian.org/libonvif
">libonvif package
</a
>
739 entered Debian Sid last night.
</p
>
741 <p
>The package provide a C library to communicate with such cameras, a
742 command line tool to locate and update settings of (like password) the
743 cameras and a GUI tool to configure and control the units as well as
744 preview the video from the camera. Libonvif is available on Both
745 Linux and Windows and the GUI tool uses the Qt library. The main
746 competitors are non-free software, while libonvif is GNU GPL licensed.
747 I am very glad Debian users in the future can control their cameras
748 using a free software system provided by Debian. But the ONVIF world
749 is full of slightly broken firmware, where the cameras pretend to
750 follow the ONVIF specification but fail to set some configuration
751 values or refuse to provide video to more than one recipient at the
752 time, and the onvif project is quite young and might take a while
753 before it completely work with your camera. Upstream seem eager to
754 improve the library, so handling any broken camera might be just
<a
755 href=
"https://github.com/sr99622/libonvif/
">a bug report away
</a
>.
</p
>
757 <p
>The package just cleared NEW, and need a new source only upload
758 before it can enter testing. This will happen in the next few
761 <p
>As usual, if you use Bitcoin and want to show your support of my
762 activities, please send Bitcoin donations to my address
763 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
768 <title>Managing and using ONVIF IP cameras with Linux
</title>
769 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</link>
770 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</guid>
771 <pubDate>Wed,
19 Oct
2022 12:
30:
00 +
0200</pubDate>
772 <description><p
>Recently I have been looking at how to control and collect data
773 from a handful IP cameras using Linux. I both wanted to change their
774 settings and to make their imagery available via a free software
775 service under my control. Here is a summary of the tools I found.
</p
>
777 <p
>First I had to identify the cameras and their protocols. As far as
778 I could tell, they were using some SOAP looking protocol and their
779 internal web server seem to only work with Microsoft Internet Explorer
780 with some proprietary binary plugin, which in these days of course is
781 a security disaster and also made it impossible for me to use the
782 camera web interface. Luckily I discovered that the SOAP looking
783 protocol is actually following
<a href=
"https://www.onvif.org/
">the
784 ONVIF specification
</a
>, which seem to be supported by a lot of IP
785 cameras these days.
</p
>
787 <p
>Once the protocol was identified, I was able to find what appear to
788 be the most popular way to configure ONVIF cameras, the free software
790 <a href=
"https://sourceforge.net/projects/onvifdm/
">ONVIF Device
791 Manager
</a
>. Lacking any other options at the time, I tried
792 unsuccessfully to get it running using Wine, but was missing a dotnet
793 40 library and I found no way around it to run it on Linux.
</p
>
795 <p
>The next tool I found to configure the cameras were a non-free Linux Qt
796 client
<a href=
"https://www.lingodigit.com/onvif_nvcdemo.html
">ONVIF
797 Device Tool
</a
>. I did not like its terms of use, so did not spend
798 much time on it.
</p
>
800 <p
>To collect the video and make it available in a web interface, I
801 found the Zoneminder tool in Debian. A recent version was able to
802 automatically detect and configure ONVIF devices, so I could use it to
803 set up motion detection in and collection of the camera output. I had
804 initial problems getting the ONVIF autodetection to work, as both
805 Firefox and Chromium
<a href=
"https://bugs.debian.org/
1001188">refused
806 the inter-tab communication
</a
> being used by the Zoneminder web
807 pages, but managed to get konqueror to work. Apparently the
"Enhanced
808 Tracking Protection
" in Firefox cause the problem. I ended up
809 upgrading to the Bookworm edition of Zoneminder in the process to try
810 to fix the issue, and believe the problem might be solved now.
</p
>
812 <p
>In the process I came across the nice Linux GUI tool
813 <a href=
"https://gitlab.com/caspermeijn/onvifviewer/
">ONVIF Viewer
</a
>
814 allowing me to preview the camera output and validate the login
815 passwords required. Sadly its author has grown tired of maintaining
816 the software, so it might not see any future updates. Which is sad,
817 as the viewer is sightly unstable and the picture tend to lock up.
818 Note, this lockup might be due to limitations in the cameras and not
819 the viewer implementation. I suspect the camera is only able to
820 provide pictures to one client at the time, and the Zoneminder feed
821 might interfere with the GUI viewer. I have
822 <a href=
"https://bugs.debian.org/
1000820">asked for the tool to be
823 included in Debian
</a
>.
</p
>
825 <p
>Finally, I found what appear to be very nice Linux free software
826 replacement for the Windows tool, named
827 <a href=
"https://github.com/sr99622/libonvif/
">libonvif
</a
>. It
828 provide a C library to talk to ONVIF devices as well as a command line
829 and GUI tool using the library. Using the GUI tool I was able to change
830 the admin passwords and update other settings of the cameras. I have
831 <a href=
"https://bugs.debian.org/
1021980">asked for the package to be
832 included in Debian
</a
>.
</p
>
834 <p
>As usual, if you use Bitcoin and want to show your support of my
835 activities, please send Bitcoin donations to my address
836 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
838 <p
><strong
>Update
2022-
10-
20</strong
>: Since my initial publication of
839 this text, I got several suggestions for more free software Linux
840 tools. There is
<a href=
"https://github.com/quatanium/python-onvif
">a
841 ONVIF python library
</a
> (already
842 <a href=
"https://bugs.debian.org/
824240">requested into Debian
</a
>) and
843 <a href=
"https://github.com/FalkTannhaeuser/python-onvif-zeep
">a python
3
844 fork
</a
> using a different SOAP dependency. There is also
845 <a href=
"https://www.home-assistant.io/integrations/onvif/
">support for
846 ONVIF in Home Assistant
</a
>, and there is an alternative to Zoneminder
847 called
<a href=
"https://www.shinobi.video/
">Shinobi
</a
>. The latter
848 two are not included in Debian either. I have not tested any of these
854 <title>Time to translate the Bullseye edition of the Debian Administrator
's Handbook
</title>
855 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</link>
856 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</guid>
857 <pubDate>Mon,
12 Sep
2022 15:
45:
00 +
0200</pubDate>
858 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
860 <p
>(The picture is of the previous edition.)
</p
>
862 <p
>Almost two years after the previous Norwegian Bokmål translation of
863 the
"<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
864 Handbook
</a
>" was published, a new edition is finally being prepared. The
865 english text is updated, and it is time to start working on the
866 translations. Around
37 percent of the strings have been updated, one
867 way or another, and the translations starting from a complete Debian Buster
868 edition now need to bring their translation up from
63% to
100%. The
869 complete book is licensed using a Creative Commons license, and has
870 been published in several languages over the years. The translations
871 are done by volunteers to bring Linux in their native tongue. The
872 last time I checked, it complete text was available in English,
873 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
874 In addition, work has been started for Arabic (Morocco), Catalan,
875 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
876 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
877 Romanian, Russian, Swedish, Turkish and Vietnamese.
</p
>
879 <p
>The translation is conducted on
880 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
881 hosted weblate project page
</a
>. Prospective translators are
882 recommeded to subscribe to
883 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
884 translators mailing list
</a
> and should also check out
885 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
886 contributors
</a
>.
</p
>
888 <p
>I am one of the Norwegian Bokmål translators of this book, and we
889 have just started. Your contribution is most welcome.
</p
>
891 <p
>As usual, if you use Bitcoin and want to show your support of my
892 activities, please send Bitcoin donations to my address
893 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
898 <title>Automatic LinuxCNC servo PID tuning?
</title>
899 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</link>
900 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</guid>
901 <pubDate>Sat,
16 Jul
2022 22:
30:
00 +
0200</pubDate>
902 <description><p
>While working on a CNC with servo motors controlled by the
903 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>
904 <a href=
"https://en.wikipedia.org/wiki/PID_controller
">PID
905 controller
</a
>, I recently had to learn how to tune the collection of values
906 that control such mathematical machinery that a PID controller is. It
907 proved to be a lot harder than I hoped, and I still have not succeeded
908 in getting the Z PID controller to successfully defy gravity, nor X
909 and Y to move accurately and reliably. But while climbing up this
910 rather steep learning curve, I discovered that some motor control
911 systems are able to tune their PID controllers. I got the impression
912 from the documentation that LinuxCNC were not. This proved to be not
915 <p
>The LinuxCNC
916 <a href=
"http://linuxcnc.org/docs/html/man/man9/pid
.9.html
">pid
917 component
</a
> is the recommended PID controller to use. It uses eight
918 constants
<tt
>Pgain
</tt
>,
<tt
>Igain
</tt
>,
<tt
>Dgain
</tt
>,
919 <tt
>bias
</tt
>,
<tt
>FF0
</tt
>,
<tt
>FF1
</tt
>,
<tt
>FF2
</tt
> and
920 <tt
>FF3
</tt
> to calculate the output value based on current and wanted
921 state, and all of these need to have a sensible value for the
922 controller to behave properly. Note, there are even more values
923 involved, theser are just the most important ones. In my case I need
924 the X, Y and Z axes to follow the requested path with little error.
925 This has proved quite a challenge for someone who have never tuned a
926 PID controller before, but there is at least some help to be found.
928 <p
>I discovered that included in LinuxCNC was this old PID component
929 at_pid claiming to have auto tuning capabilities. Sadly it had been
930 neglected since
2011, and could not be used as a plug in replacement
931 for the default pid component. One would have to rewriting the
932 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
933 to quickly test auto tuning to see if it did a better job than me at
934 figuring out good P, I and D values to use.
</p
>
936 <p
>I decided to have a look if the situation could be improved. This
937 involved trying to understand the code and history of the pid and
938 at_pid components. Apparently they had a common ancestor, as code
939 structure, comments and variable names were quite close to each other.
940 Sadly this was not reflected in the git history, making it hard to
941 figure out what really happened. My guess is that the author of
942 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c
">at_pid.c
</a
>
944 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c
">pid.c
</a
>,
945 rewrote it to follow the structure he wished pid.c to have, then added
946 support for auto tuning and finally got it included into the LinuxCNC
947 repository. The restructuring and lack of early history made it
948 harder to figure out which part of the code were relevant to the auto
949 tuning, and which part of the code needed to be updated to work the
950 same way as the current pid.c implementation. I started by trying to
951 isolate relevant changes in pid.c, and applying them to at_pid.c. My
952 aim was to make sure the at_pid component could replace the pid
953 component with a simple change in the HAL setup loadrt line, without
954 having to
"rewire
" the rest of the HAL configuration. After a few
955 hours following this approach, I had learned quite a lot about the
956 code structure of both components, while concluding I was heading down
957 the wrong rabbit hole, and should get back to the surface and find a
958 different path.
</p
>
960 <p
>For the second attempt, I decided to throw away all the PID control
961 related part of the original at_pid.c, and instead isolate and lift
962 the auto tuning part of the code and inject it into a copy of pid.c.
963 This ensured compatibility with the current pid component, while
964 adding auto tuning as a run time option. To make it easier to identify
965 the relevant parts in the future, I wrapped all the auto tuning code
966 with
'#ifdef AUTO_TUNER
'. The end result behave just like the current
967 pid component by default, as that part of the code is identical. The
968 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
1820">end result
969 entered the LinuxCNC master branch
</a
> a few days ago.
</p
>
971 <p
>To enable auto tuning, one need to set a few HAL pins in the PID
972 component. The most important ones are
<tt
>tune-effort
</tt
>,
973 <tt
>tune-mode
</tt
> and
<tt
>tune-start
</tt
>. But lets take a step
974 back, and see what the auto tuning code will do. I do not know the
975 mathematical foundation of the at_pid algorithm, but from observation
976 I can tell that the algorithm will, when enabled, produce a square
977 wave pattern centered around the
<tt
>bias
</tt
> value on the output pin
978 of the PID controller. This can be seen using the HAL Scope provided
979 by LinuxCNC. In my case, this is translated into voltage (+-
10V) sent
980 to the motor controller, which in turn is translated into motor speed.
981 So at_pid will ask the motor to move the axis back and forth. The
982 number of cycles in the pattern is controlled by the
983 <tt
>tune-cycles
</tt
> pin, and the extremes of the wave pattern is
984 controlled by the
<tt
>tune-effort
</tt
> pin. Of course, trying to
985 change the direction of a physical object instantly (as in going
986 directly from a positive voltage to the equivalent negative voltage)
987 do not change velocity instantly, and it take some time for the object
988 to slow down and move in the opposite direction. This result in a
989 more smooth movement wave form, as the axis in question were vibrating
990 back and forth. When the axis reached the target speed in the
991 opposing direction, the auto tuner change direction again. After
992 several of these changes, the average time delay between the
'peaks
'
993 and
'valleys
' of this movement graph is then used to calculate
994 proposed values for Pgain, Igain and Dgain, and insert them into the
995 HAL model to use by the pid controller. The auto tuned settings are
996 not great, but htye work a lot better than the values I had been able
997 to cook up on my own, at least for the horizontal X and Y axis. But I
998 had to use very small
<tt
>tune-effort
<tt
> values, as my motor
999 controllers error out if the voltage change too quickly. I
've been
1000 less lucky with the Z axis, which is moving a heavy object up and
1001 down, and seem to confuse the algorithm. The Z axis movement became a
1002 lot better when I introduced a
<tt
>bias
</tt
> value to counter the
1003 gravitational drag, but I will have to work a lot more on the Z axis
1004 PID values.
</p
>
1006 <p
>Armed with this knowledge, it is time to look at how to do the
1007 tuning. Lets say the HAL configuration in question load the PID
1008 component for X, Y and Z like this:
</p
>
1010 <blockquote
><pre
>
1011 loadrt pid names=pid.x,pid.y,pid.z
1012 </pre
></blockquote
>
1014 <p
>Armed with the new and improved at_pid component, the new line will
1015 look like this:
</p
>
1017 <blockquote
><pre
>
1018 loadrt at_pid names=pid.x,pid.y,pid.z
1019 </pre
></blockquote
>
1021 <p
>The rest of the HAL setup can stay the same. This work because the
1022 components are referenced by name. If the component had used count=
3
1023 instead, all use of pid.# had to be changed to at_pid.#.
</p
>
1025 <p
>To start tuning the X axis, move the axis to the middle of its
1026 range, to make sure it do not hit anything when it start moving back
1027 and forth. Next, set the
<tt
>tune-effort
</tt
> to a low number in the
1028 output range. I used
0.1 as my initial value. Next, assign
1 to the
1029 <tt
>tune-mode
</tt
> value. Note, this will disable the pid controlling
1030 part and feed
0 to the output pin, which in my case initially caused a
1031 lot of drift. In my case it proved to be a good idea with X and Y to
1032 tune the motor driver to make sure
0 voltage stopped the motor
1033 rotation. On the other hand, for the Z axis this proved to be a bad
1034 idea, so it will depend on your setup. It might help to set the
1035 <tt
>bias
</tt
> value to a output value that reduce or eliminate the
1036 axis drift. Finally, after setting
<tt
>tune-mode
</tt
>, set
1037 <tt
>tune-start
</tt
> to
1 to activate the auto tuning. If all go well,
1038 your axis will vibrate for a few seconds and when it is done, new
1039 values for Pgain, Igain and Dgain will be active. To test them,
1040 change
<tt
>tune-mode
</tt
> back to
0. Note that this might cause the
1041 machine to suddenly jerk as it bring the axis back to its commanded
1042 position, which it might have drifted away from during tuning. To
1043 summarize with some halcmd lines:
</p
>
1045 <blockquote
><pre
>
1046 setp pid.x.tune-effort
0.1
1047 setp pid.x.tune-mode
1
1048 setp pid.x.tune-start
1
1049 # wait for the tuning to complete
1050 setp pid.x.tune-mode
0
1051 </pre
></blockquote
>
1053 <p
>After doing this task quite a few times while trying to figure out
1054 how to properly tune the PID controllers on the machine in, I decided
1055 to figure out if this process could be automated, and wrote a script
1056 to do the entire tuning process from power on. The end result will
1057 ensure the machine is powered on and ready to run, home all axis if it
1058 is not already done, check that the extra tuning pins are available,
1059 move the axis to its mid point, run the auto tuning and re-enable the
1060 pid controller when it is done. It can be run several times. Check
1062 <a href=
"https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner
">run-auto-pid-tuner
</a
>
1063 script on github if you want to learn how it is done.
</p
>
1065 <p
>My hope is that this little adventure can inspire someone who know
1066 more about motor PID controller tuning can implement even better
1067 algorithms for automatic PID tuning in LinuxCNC, making life easier
1068 for both me and all the others that want to use LinuxCNC but lack the
1069 in depth knowledge needed to tune PID controllers well.
</p
>
1071 <p
>As usual, if you use Bitcoin and want to show your support of my
1072 activities, please send Bitcoin donations to my address
1073 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1078 <title>LinuxCNC translators life just got a bit easier
</title>
1079 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</link>
1080 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</guid>
1081 <pubDate>Fri,
3 Jun
2022 21:
10:
00 +
0200</pubDate>
1082 <description><p
>Back in oktober last year, when I started looking at the
1083 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
> system, I
1084 proposed to change the documentation build system make life easier for
1085 translators. The original system consisted of independently written
1086 documentation files for each language, with no automated way to track
1087 changes done in other translations and no help for the translators to
1088 know how much was left to translated. By using
1089 <a href=
"https://po4a.org/
">the po4a system
</a
> to generate POT and PO
1090 files from the English documentation, this can be improved. A small
1091 team of LinuxCNC contributors got together and today our labour
1092 finally payed off. Since a few hours ago, it is now possible to
1093 translate
<a href=
"https://hosted.weblate.org/projects/linuxcnc/
">the
1094 LinuxCNC documentation on Weblate
</a
>, alongside the program itself.
</p
>
1096 <p
>The effort to migrate the documentation to use po4a has been both
1097 slow and frustrating. I am very happy we finally made it.
</p
>
1099 <p
>As usual, if you use Bitcoin and want to show your support of my
1100 activities, please send Bitcoin donations to my address
1101 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1106 <title>geteltorito make CD firmware upgrades a breeze
</title>
1107 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</link>
1108 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</guid>
1109 <pubDate>Wed,
20 Apr
2022 11:
50:
00 +
0200</pubDate>
1110 <description><p
>Recently I wanted to upgrade the firmware of my thinkpad, and
1111 located the firmware download page from Lenovo (which annoyingly do
1112 not allow access via Tor, forcing me to hand them more personal
1113 information that I would like). The
1114 <a href=
"https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso
&SearchType=Customer search
&searchLocation=Masthead
">download
1115 from Lenovo
</a
> is a bootable ISO image, which is a bit of a problem
1116 when all I got available is a USB memory stick. I tried booting the
1117 ISO as a USB stick, but this did not work. But genisoimage came to
1118 the rescue.
</p
>
1120 <P
>The geteltorito program in
1121 <a href=
"http://tracker.debian.org/cdrkit
">the genisoimage binary
1122 package
</a
> is able to convert the bootable ISO image to a bootable
1123 USB stick using a simple command line recipe, which I then can write
1124 to the most recently inserted USB stick:
</p
>
1126 <blockquote
><pre
>
1127 geteltorito -o usbstick.img lenovo-firmware.iso
1128 sudo dd bs=
10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -
1)
1129 </pre
></blockquote
>
1131 <p
>This USB stick booted the firmware upgrader just fine, and in a few
1132 minutes my machine had the latest and greatest BIOS firmware in place.
</p
>
1137 <title>Run your industrial metal working machine using Debian?
</title>
1138 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</link>
1139 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</guid>
1140 <pubDate>Wed,
2 Mar
2022 18:
40:
00 +
0100</pubDate>
1141 <description><p
>After many months of hard work by the good people involved in
1142 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>, the
1143 system was accepted Sunday
1144 <a href=
"https://tracker.debian.org/pkg/linuxcnc
">into Debian
</a
>.
1145 Once it was available from Debian, I was surprised to discover from
1146 <a href=
"https://qa.debian.org/popcon.php?package=linuxcnc
">its
1147 popularity-contest numbers
</a
> that people have been reporting its use
1148 since
2012.
<a href=
"http://linuxcnc.org/
">Its project site
</a
> might
1149 be a good place to check out, but sadly is not working when visiting
1152 <p
>But what is LinuxCNC, you are probably wondering? Perhaps a
1153 Wikipedia quote is in place?
</p
>
1156 "LinuxCNC is a software system for numerical control of
1157 machines such as milling machines, lathes, plasma cutters, routers,
1158 cutting machines, robots and hexapods. It can control up to
9 axes or
1159 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
1160 several GUIs suited to specific kinds of usage (touch screen,
1161 interactive development).
"
1164 <p
>It can even control
3D printers. And even though the Wikipedia
1165 page indicate that it can only work with hard real time kernel
1166 features, it can also work with the user space soft real time features
1167 provided by the Debian kernel.
1168 <a href=
"https://github.com/linuxcnc/linuxcnc
">The source code
</a
> is
1169 available from Github. The last few months I
've been involved in the
1170 translation setup for the program and documentation. Translators are
1172 <a href=
"https://hosted.weblate.org/engage/linuxcnc/
">join the
1173 effort
</a
> using Weblate.
</p
>
1175 <p
>As usual, if you use Bitcoin and want to show your support of my
1176 activities, please send Bitcoin donations to my address
1177 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1182 <title>Debian still an excellent choice for Lego builders
</title>
1183 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</link>
1184 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</guid>
1185 <pubDate>Sun,
24 Oct
2021 07:
10:
00 +
0200</pubDate>
1186 <description><p
>The Debian Lego team saw a lot of activity the last few weeks. All
1187 the packages under the team umbrella has been updated to fix
1188 packaging, lintian issues and BTS reports. In addition, a new and
1189 inspiring team member appeared on both the
1190 <a href=
"https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team
">debian-lego-team
1191 Team mailing list
</a
> and
1192 <a href=
"irc://irc.debian.org/%
23debian-lego
">IRC channel
1193 #debian-lego
</a
>. If you are interested in Lego CAD design and LEGO
1194 Mindstorms programming, check out the
1195 <a href=
"http://wiki.debian.org/LegoDesigners
">team wiki page
</a
> to
1196 see what Debian can offer the Lego enthusiast.
</p
>
1198 <p
>Patches has been sent upstream, causing new upstream releases, one
1199 even the first one in more than ten years, and old upstreams was
1200 released with new ones. There are still a lot of work left, and the
1201 team welcome more members to help us make sure Debian is the Linux
1202 distribution of choice for Lego builders. If you want to contribute,
1203 join us in the IRC channel and become part of
1204 <a href=
"https://salsa.debian.org/debian-lego-team/
">the team on
1205 Salsa
</a
>.
</p
>
1207 <p
>As usual, if you use Bitcoin and want to show your support of my
1208 activities, please send Bitcoin donations to my address
1209 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1214 <title>Six complete translations of The Debian Administrator
's Handbook for Buster
</title>
1215 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</link>
1216 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</guid>
1217 <pubDate>Mon,
5 Jul
2021 19:
20:
00 +
0200</pubDate>
1218 <description><p
>I am happy observe that the
<a href=
"https://debian-handbook.info/
">The
1219 Debian Administrator
's Handbook
</a
> is available in six languages now.
1220 I am not sure which one of these are completely proof read, but the
1221 complete book is available in these languages:
1225 <li
>English
</li
>
1226 <li
>Norwegian Bokmål
</li
>
1227 <li
>German
</li
>
1228 <li
>Indonesian
</li
>
1229 <li
>Brazil Portuguese
</li
>
1230 <li
>Spanish
</li
>
1234 <p
>This is the list of languages more than
70% complete, in other
1235 words with not too much left to do:
</p
>
1239 <li
>Chinese (Simplified) -
90%
</li
>
1240 <li
>French -
79%
</li
>
1241 <li
>Italian -
79%
</li
>
1242 <li
>Japanese -
77%
</li
>
1243 <li
>Arabic (Morocco) -
75%
</li
>
1244 <li
>Persian -
71%
</li
>
1248 <p
>I wonder how long it will take to bring these to
100%.
</p
>
1250 <p
>Then there is the list of languages about halfway done:
</p
>
1254 <li
>Russian -
63%
</li
>
1255 <li
>Swedish -
53%
</li
>
1256 <li
>Chinese (Traditional) -
46%
</li
>
1257 <li
>Catalan -
45%
</li
>
1261 <p
>Several are on to a good start:
</p
>
1265 <li
>Dutch -
26%
</li
>
1266 <li
>Vietnamese -
25%
</li
>
1267 <li
>Polish -
23%
</li
>
1268 <li
>Czech -
22%
</li
>
1269 <li
>Turkish -
18%
</li
>
1273 <p
>Finally, there are the ones just getting started:
</p
>
1277 <li
>Korean -
4%
</li
>
1278 <li
>Croatian -
2%
</li
>
1279 <li
>Greek -
2%
</li
>
1280 <li
>Danish -
1%
</li
>
1281 <li
>Romanian -
1%
</li
>
1285 <p
>If you want to help provide a Debian instruction book in your own
1287 <a href=
"https://hosted.weblate.org/projects/debian-handbook/#languages
">Weblate
</a
>
1288 to contribute to the translations.
</p
>
1290 <p
>As usual, if you use Bitcoin and want to show your support of my
1291 activities, please send Bitcoin donations to my address
1292 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1297 <title>Latest Jami back in Debian Testing, and scriptable using dbus
</title>
1298 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</link>
1299 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</guid>
1300 <pubDate>Tue,
12 Jan
2021 17:
00:
00 +
0100</pubDate>
1301 <description><p
>After a lot of hard work by its maintainer Alexandre Viau and
1302 others, the decentralized communication platform
1303 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>
1304 (earlier known as Ring), managed to get
1305 <a href=
"https://tracker.debian.org/pkg/ring
">its latest version
</a
>
1306 into Debian Testing. Several of its dependencies has caused build and
1307 propagation problems, which all seem to be solved now.
</p
>
1309 <p
>In addition to the fact that Jami is decentralized, similar to how
1310 bittorrent is decentralized, I first of all like how it is not
1311 connected to external IDs like phone numbers. This allow me to set up
1312 computers to send me notifications using Jami without having to find
1313 get a phone number for each computer. Automatic notification via Jami
1314 is also made trivial thanks to the provided client side API (as a DBus
1315 service). Here is my bourne shell script demonstrating how to let any
1316 system send a message to any Jami address. It will create a new
1317 identity before sending the message, if no Jami identity exist
1320 <p
><pre
>
1323 # Usage: $
0 <jami-address
> <message
>
1325 # Send
<message
> to
<jami-address
>, create local jami account if
1328 # License: GPL v2 or later at your choice
1329 # Author: Petter Reinholdtsen
1332 if [ -z
"$HOME
" ] ; then
1333 echo
"error: missing \$HOME, required for dbus to work
"
1337 # First, get dbus running if not already running
1338 DBUSLAUNCH=/usr/bin/dbus-launch
1339 PIDFILE=/run/asterisk/dbus-session.pid
1340 if [ -e $PIDFILE ] ; then
1342 if ! kill -
0 $DBUS_SESSION_BUS_PID
2>/dev/null ; then
1343 unset DBUS_SESSION_BUS_ADDRESS
1346 if [ -z
"$DBUS_SESSION_BUS_ADDRESS
" ]
&& [ -x
"$DBUSLAUNCH
" ]; then
1347 DBUS_SESSION_BUS_ADDRESS=
"unix:path=$HOME/.dbus
"
1348 dbus-daemon --session --address=
"$DBUS_SESSION_BUS_ADDRESS
" --nofork --nopidfile --syslog-only
< /dev/null
> /dev/null
2>&1 3>&1 &
1349 DBUS_SESSION_BUS_PID=$!
1351 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
1352 echo DBUS_SESSION_BUS_ADDRESS=\
""$DBUS_SESSION_BUS_ADDRESS
"\
"
1353 echo export DBUS_SESSION_BUS_ADDRESS
1359 part=
"$
1"; shift
1360 op=
"$
1"; shift
1361 dbus-send --session \
1362 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1366 part=
"$
1"; shift
1367 op=
"$
1"; shift
1368 dbus-send --session --print-reply \
1369 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
1373 dringopreply ConfigurationManager getAccountList | \
1374 grep string | awk -F
'"' '{print $
2}
' | head -n
1
1377 account=$(firstaccount)
1379 if [ -z
"$account
" ] ; then
1380 echo
"Missing local account, trying to create it
"
1381 dringop ConfigurationManager addAccount \
1382 dict:string:string:
"Account.type
",
"RING
",
"Account.videoEnabled
",
"false
"
1383 account=$(firstaccount)
1384 if [ -z
"$account
" ] ; then
1385 echo
"unable to create local account
"
1390 # Not using dringopreply to ensure $
2 can contain spaces
1391 dbus-send --print-reply --session \
1392 --dest=cx.ring.Ring \
1393 /cx/ring/Ring/ConfigurationManager \
1394 cx.ring.Ring.ConfigurationManager.sendTextMessage \
1395 string:
"$account
" string:
"$
1" \
1396 dict:string:string:
"text/plain
",
"$
2"
1397 </pre
></p
>
1399 <p
>If you want to check it out yourself, visit the
1400 <a href=
"https://jami.net/
">the Jami system project page
</a
> to learn
1401 more, and install the latest Jami client from Debian Unstable or
1404 <p
>As usual, if you use Bitcoin and want to show your support of my
1405 activities, please send Bitcoin donations to my address
1406 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1411 <title>Buster based Bokmål edition of Debian Administrator
's Handbook
</title>
1412 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
1413 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
1414 <pubDate>Tue,
20 Oct
2020 18:
35:
00 +
0200</pubDate>
1415 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
1417 <p
>I am happy to report that we finally made it! Norwegian Bokmål
1418 became the first translation published on paper of the new Buster
1419 based edition of
"<a href=
"https://debian-handbook.info/
">The Debian
1420 Administrator
's Handbook
</a
>". The print proof reading copy arrived
1421 some days ago, and it looked good, so now the book is approved for
1422 general distribution. This updated paperback edition
<a
1423 href=
"https://debian-handbook.info/get/#norwegian
">is available from
1424 lulu.com
</a
>. The book is also available for download in electronic
1425 form as PDF, EPUB and Mobipocket, and can also be
1426 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
</a
>.
</p
>
1428 <p
>I am very happy to wrap up this Creative Common licensed project,
1429 which concludes several months of work by several volunteers. The
1430 number of Linux related books published in Norwegian are few, and I
1431 really hope this one will gain many readers, as it is packed with deep
1432 knowledge on Linux and the Debian ecosystem. The book will be
1433 available for various Internet book stores like Amazon and Barnes
&
1434 Noble soon, but I recommend buying
1435 "<a href=
"https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
9j7qwq.html
">Håndbok
1436 for Debian-administratoren
</a
>" directly from the source at Lulu.
1438 <p
>As usual, if you use Bitcoin and want to show your support of my
1439 activities, please send Bitcoin donations to my address
1440 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1445 <title>Buster update of Norwegian Bokmål edition of Debian Administrator
's Handbook almost done
</title>
1446 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</link>
1447 <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>
1448 <pubDate>Fri,
11 Sep
2020 09:
45:
00 +
0200</pubDate>
1449 <description><p
>Thanks to the good work of several volunteers, the updated edition
1450 of the Norwegian translation for
1451 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1452 Handbook
</a
>" is now almost completed. After many months of proof
1453 reading, I consider the proof reading complete enough for us to move
1454 to the next step, and have asked for the print version to be prepared
1455 and sent of to the print on demand service lulu.com. While it is
1456 still not to late if you find any incorrect translations on
1457 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
1458 hosted Weblate service
</a
>, but it will be soon. :) You can check out
1459 <a href=
" https://debian-handbook.info/browse/nb-NO/stable/
">the Buster
1460 edition on the web
</a
> until the print edition is ready.
</p
>
1462 <p
>The book will be for sale on lulu.com and various web book stores,
1463 with links available from the web site for the book linked to above.
1464 I hope a lot of readers find it useful.
</p
>
1466 <p
>As usual, if you use Bitcoin and want to show your support of my
1467 activities, please send Bitcoin donations to my address
1468 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1473 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
1474 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
1475 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
1476 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
1477 <description><p
>Three years ago, the first Norwegian Bokmål edition of
1478 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1479 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
1480 new and updated version based on Buster is getting ready. Work on the
1481 updated Norwegian Bokmål edition has been going on for a few months
1482 now, and yesterday, we reached the first mile stone, with
100% of the
1483 texts being translated. A lot of proof reading remains, of course,
1484 but a major step towards a new edition has been taken.
</p
>
1486 <p
>The book is translated by volunteers, and we would love to get some
1487 help with the proof reading. The translation uses
1488 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
1489 hosted Weblate service
</a
>, and we welcome everyone to have a look and
1490 submit improvements and suggestions. There is also a proof readers
1491 PDF available on request, get in touch if you want to help out that
1494 <p
>As usual, if you use Bitcoin and want to show your support of my
1495 activities, please send Bitcoin donations to my address
1496 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1501 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
1502 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
1503 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
1504 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
1505 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
1506 User Group
</a
>, I have the pleasure of receiving the
1507 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
1508 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
1509 several times a year. I rarely have time to read all the articles,
1510 but try to at least skim through them all as there is a lot of nice
1511 knowledge passed on there. I even carry the latest issue with me most
1512 of the time to try to get through all the articles when I have a few
1513 spare minutes.
</p
>
1515 <p
>The other day I came across a nice article titled
1516 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
1517 Secure Socket API: TLS as an Operating System Service
</a
>" with a
1518 marvellous idea I hope can make it all the way into the POSIX standard.
1519 The idea is as simple as it is powerful. By introducing a new
1520 socket() option IPPROTO_TLS to use TLS, and a system wide service to
1521 handle setting up TLS connections, one both make it trivial to add TLS
1522 support to any program currently using the POSIX socket API, and gain
1523 system wide control over certificates, TLS versions and encryption
1524 systems used. Instead of doing this:
</p
>
1526 <p
><blockquote
><pre
>
1527 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
1528 </pre
></blockquote
></p
>
1530 <p
>the program code would be doing this:
<p
>
1532 <p
><blockquote
><pre
>
1533 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
1534 </pre
></blockquote
></p
>
1536 <p
>According to the ;login: article, converting a C program to use TLS
1537 would normally modify only
5-
10 lines in the code, which is amazing
1538 when compared to using for example the OpenSSL API.
</p
>
1540 <p
>The project has set up the
1541 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
1542 web site to spread the idea, and the code for a kernel module and the
1543 associated system daemon is available from two github repositories:
1544 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
1545 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
1546 Unfortunately there is no explicit license information with the code,
1547 so its copyright status is unclear. A
1548 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
1549 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
1551 <p
>I love the idea of extending socket() to gain TLS support, and
1552 understand why it is an advantage to implement this as a kernel module
1553 and system wide service daemon, but can not help to think that it
1554 would be a lot easier to get projects to move to this way of setting
1555 up TLS if it was done with a user space approach where programs
1556 wanting to use this API approach could just link with a wrapper
1559 <p
>I recommend you check out this simple and powerful approach to more
1560 secure network connections. :)
</p
>
1562 <p
>As usual, if you use Bitcoin and want to show your support of my
1563 activities, please send Bitcoin donations to my address
1564 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1569 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
1570 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
1571 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
1572 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
1573 <description><p
>Half a year ago,
1574 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
1575 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
1576 client
</a
>, capable of peer-to-peer encrypted communication. It
1577 handle both messages, audio and video. It uses distributed hash
1578 tables instead of central infrastructure to connect its users to each
1579 other, which in my book is a plus. I mentioned briefly that it could
1580 also work as a SIP client, which came in handy when the higher
1581 educational sector in Norway started to promote Zoom as its video
1582 conferencing solution. I am reluctant to use the official Zoom client
1583 software, due to their
<a href=
"https://zoom.us/terms
">copyright
1584 license clauses
</a
> prohibiting users to reverse engineer (for example
1585 to check the security) and benchmark it, and thus prefer to connect to
1586 Zoom meetings with free software clients.
</p
>
1588 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
1589 password set on the room. The Jami daemon leak memory like crazy
1590 (approximately
1 GiB a minute) when I am connected to the video
1591 conference, so I had to restart the client every
7-
10 minutes, which
1592 is not great. I tried to get other SIP Linux clients to work
1593 without success, so I decided I would have to live with this wart
1594 until someone managed to fix the leak in the dring code base. But
1595 another problem showed up once the rooms were password protected. I
1596 could not get my dial tone signaling through from Jami to Zoom, and
1597 dial tone signaling is used to enter the password when connecting to
1598 Zoom. I tried a lot of different permutations with my Jami and
1599 Asterisk setup to try to figure out why the signaling did not get
1600 through, only to finally discover that the fundamental problem seem to
1601 be that Zoom is simply not able to receive dial tone signaling when
1602 connecting via SIP. There seem to be nothing wrong with the Jami and
1603 Asterisk end, it is simply broken in the Zoom end. I got help from a
1604 very skilled VoIP engineer figuring out this last part. And being a
1605 very skilled engineer, he was also able to locate a solution for me.
1606 Or to be exact, a workaround that solve my initial problem of
1607 connecting to password protected Zoom rooms using Jami.
</p
>
1609 <p
>So, how do you do this, I am sure you are wondering by now. The
1611 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
1612 from Zoom
</a
>, and it is to modify the SIP address to include the room
1613 password. What is most surprising about this is that the
1614 automatically generated email from Zoom with instructions on how to
1615 connect via SIP do not mention this. The SIP address to use normally
1616 consist of the room ID (a number), an @ character and the IP address
1617 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1618 room ID in front of the at sign. The format is
"<tt
>[Meeting
1619 ID].[Password].[Layout].[Host Key]
</tt
>", and you can here see how you
1620 can both enter password, control the layout (full screen, active
1621 presence and gallery) and specify the host key to start the meeting.
1622 The full SIP address entered into Jami to provide the password will
1623 then look like this (all using made up numbers):
</p
>
1625 <p
><blockquote
>
1626 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
1627 </blockquote
></p
>
1629 <p
>Now if only jami would reduce its memory usage, I could even
1630 recommend this setup to others. :)
</p
>
1632 <p
>As usual, if you use Bitcoin and want to show your support of my
1633 activities, please send Bitcoin donations to my address
1634 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1639 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
1640 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
1641 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
1642 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
1643 <description><p
>The curiosity got the better of me when
1644 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
1645 reported
</a
> that New Jersey was desperately looking for
1646 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
1647 and a few days later it was reported that
1648 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
1649 tried to locate COBOL programmers
</a
>.
</p
>
1651 <p
>I thus decided to have a look at free software alternatives to
1652 learn COBOL, and had the pleasure to find
1653 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
1654 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
1655 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
1656 transforming COBOL code to C or C++ before giving it to GCC or Visual
1657 Studio to build binaries.
</p
>
1659 <p
>I managed to get in touch with upstream, and was impressed with the
1660 quick response, and also was happy to see a new Debian maintainer
1661 taking over when the original one recently asked to be replaced. A
1662 new Debian upload was done as recently as yesterday.
</p
>
1664 <p
>Using the Debian package, I was able to follow a simple COBOL
1665 introduction and make and run simple COBOL programs. It was fun to
1666 learn a new programming language. If you want to test for yourself,
1667 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
1668 page
</a
> have a few simple examples to get you startet.
</p
>
1670 <p
>As I do not have much experience with COBOL, I do not know how
1671 standard compliant it is, but it claim to pass most tests from COBOL
1672 test suite, which sound good to me. It is nice to know it is possible
1673 to learn COBOL using software without any usage restrictions, and I am
1674 very happy such nice free software project as this is available. If
1675 you as me is curious about COBOL, check it out.
</p
>
1677 <p
>As usual, if you use Bitcoin and want to show your support of my
1678 activities, please send Bitcoin donations to my address
1679 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1684 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
1685 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
1686 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
1687 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
1688 <description><p
>Some years ago, in
2016, I
1689 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
1690 for the first time about
</a
> the Ring peer to peer messaging system.
1691 It would provide messaging without any central server coordinating the
1692 system and without requiring all users to register a phone number or
1693 own a mobile phone. Back then, I could not get it to work, and put it
1694 aside until it had seen more development. A few days ago I decided to
1695 give it another try, and am happy to report that this time I am able
1696 to not only send and receive messages, but also place audio and video
1697 calls. But only if UDP is not blocked into your network.
</p
>
1699 <p
>The Ring system changed name earlier this year to
1700 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
1701 tried doing web search for
'ring
' when I discovered it for the first
1702 time, and can only applaud this change as it is impossible to find
1703 something called Ring among the noise of other uses of that word. Now
1704 you can search for
'jami
' and this client and
1705 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
1706 least on duckduckgo.
</p
>
1708 <p
>Jami will by default encrypt messages as well as audio and video
1709 calls, and try to send them directly between the communicating parties
1710 if possible. If this proves impossible (for example if both ends are
1711 behind NAT), it will use a central SIP TURN server maintained by the
1712 Jami project. Jami can also be a normal SIP client. If the SIP
1713 server is unencrypted, the audio and video calls will also be
1714 unencrypted. This is as far as I know the only case where Jami will
1715 do anything without encryption.
</p
>
1717 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
1718 Android, iOS, and Android TV. It is included in Debian already. Jami
1719 also work for those using F-Droid without any Google connections,
1720 while Signal do not.
1721 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
1722 protocol
</a
> is described in the Ring project wiki. The system uses a
1723 distributed hash table (DHT) system (similar to BitTorrent) running
1724 over UDP. On one of the networks I use, I discovered Jami failed to
1725 work. I tracked this down to the fact that incoming UDP packages
1726 going to ports
1-
49999 were blocked, and the DHT would pick a random
1727 port and end up in the low range most of the time. After talking to
1728 the developers, I solved this by enabling the dhtproxy in the
1729 settings, thus using TCP to talk to a central DHT proxy instead of
1731 peering directly with others. I
've been told the developers are
1732 working on allowing DHT to use TCP to avoid this problem. I also ran
1733 into a problem when trying to talk to the version of Ring included in
1734 Debian Stable (Stretch). Apparently the protocol changed between
1735 beta2 and the current version, making these clients incompatible.
1736 Hopefully the protocol will not be made incompatible in the
1739 <p
>It is worth noting that while looking at Jami and its features, I
1740 came across another communication platform I have not tested yet. The
1741 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
1742 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
1743 become the topic of a future blog post.
</p
>
1745 <p
>As usual, if you use Bitcoin and want to show your support of my
1746 activities, please send Bitcoin donations to my address
1747 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1752 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
1753 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
1754 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
1755 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
1756 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
1757 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
1758 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
1759 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1760 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1761 nye versjonen kom på nyåret, og ble
1762 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
1763 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
1764 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1765 måtte justeres, men ikke noe alvorlig. Har oppdatert
1766 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
1767 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
1769 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1770 å spille for oss som liker slikt. :)
</p
>
1772 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1773 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1775 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
1776 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
1781 <title>Debian now got everything you need to program Micro:bit
</title>
1782 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
1783 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
1784 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
1785 <description><p
>I am amazed and very pleased to discover that since a few days ago,
1786 everything you need to program the
<a href=
"https://microbit.org/
">BBC
1787 micro:bit
</a
> is available from the Debian archive. All this is
1788 thanks to the hard work of Nick Morrott and the Debian python
1789 packaging team. The micro:bit project recommend the mu-editor to
1790 program the microcomputer, as this editor will take care of all the
1791 machinery required to injekt/flash micropython alongside the program
1792 into the micro:bit, as long as the pieces are available.
</p
>
1794 <p
>There are three main pieces involved. The first to enter Debian
1796 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
1797 which was accepted into the archive
2019-
01-
12. The next one was
1798 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
1799 showed up
2019-
01-
13. The final and hardest part to to into the
1801 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
1802 which needed to get its build system and dependencies into Debian
1803 before it was accepted
2019-
01-
20. The last one is already in Debian
1804 Unstable and should enter Debian Testing / Buster in three days. This
1805 all allow any user of the micro:bit to get going by simply running
1806 'apt install mu-editor
' when using Testing or Unstable, and once
1807 Buster is released as stable, all the users of Debian stable will be
1808 catered for.
</p
>
1810 <p
>As a minor final touch, I added rules to
1811 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
1812 package
</a
> for recognizing micro:bit and recommend the mu-editor
1813 package. This make sure any user of the isenkram desktop daemon will
1814 get a popup suggesting to install mu-editor then the USB cable from
1815 the micro:bit is inserted for the first time.
</p
>
1817 <p
>This should make it easier to have fun.
</p
>
1819 <p
>As usual, if you use Bitcoin and want to show your support of my
1820 activities, please send Bitcoin donations to my address
1821 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1826 <title>Learn to program with Minetest on Debian
</title>
1827 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
1828 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
1829 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
1830 <description><p
>A fun way to learn how to program
1831 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
1832 instructions in the book
1833 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
1834 with Minecraft
</a
>", which introduces programming in Python to people
1835 who like to play with Minecraft. The book uses a Python library to
1836 talk to a TCP/IP socket with an API accepting build instructions and
1837 providing information about the current players in a Minecraft world.
1838 The TCP/IP API was first created for the Minecraft implementation for
1839 Raspberry Pi, and has since been ported to some server versions of
1840 Minecraft. The book contain recipes for those using Windows, MacOSX
1841 and Raspian. But a little known fact is that you can follow the same
1842 recipes using the free software construction game
1843 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
1845 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
1846 Minetest module implementing the same API
</a
>, making it possible to
1847 use the Python programs coded to talk to Minecraft with Minetest too.
1849 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
1850 this module
</a
> to Debian two weeks ago, and as soon as it clears the
1851 FTP masters NEW queue, learning to program Python with Minetest on
1852 Debian will be a simple
'apt install
' away. The Debian package is
1853 maintained as part of the Debian Games team, and
1854 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
1855 packaging rules
</a
> are currently located under
'unfinished
' on
1858 <p
>You will most likely need to install several of the Minetest
1859 modules in Debian for the examples included with the library to work
1860 well, as there are several blocks used by the example scripts that are
1861 provided via modules in Minetest. Without the required blocks, a
1862 simple stone block is used instead. My initial testing with a analog
1863 clock did not get gold arms as instructed in the python library, but
1864 instead used stone arms.
</p
>
1866 <p
>I tried to find a way to add the API to the desktop version of
1867 Minecraft, but were unable to find any working recipes. The
1868 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
1869 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
1870 working with a standalone Minecraft server setup. Are there any
1871 options to use with the normal desktop version?
</p
>
1873 <p
>As usual, if you use Bitcoin and want to show your support of my
1874 activities, please send Bitcoin donations to my address
1875 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1880 <title>Time for an official MIME type for patches?
</title>
1881 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
1882 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
1883 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
1884 <description><p
>As part of my involvement in
1885 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
1886 archive API project
</a
>, I
've been importing a fairly large lump of
1887 emails into a test instance of the archive to see how well this would
1888 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
1889 notmuch email database
</a
>, all public emails sent to me via
1890 @lists.debian.org, giving me a set of around
216 000 emails to import.
1891 In the process, I had a look at the various attachments included in
1892 these emails, to figure out what to do with attachments, and noticed
1893 that one of the most common attachment formats do not have
1894 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
1895 official MIME type
</a
> registered with IANA/IETF. The output from
1896 diff, ie the input for patch, is on the top
10 list of formats
1897 included in these emails. At the moment people seem to use either
1898 text/x-patch or text/x-diff, but neither is officially registered. It
1899 would be better if one official MIME type were registered and used
1900 everywhere.
</p
>
1902 <p
>To try to get one official MIME type for these files, I
've brought
1904 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
1905 media-types mailing list
</a
>. If you are interested in discussion
1906 which MIME type to use as the official for patch files, or involved in
1907 making software using a MIME type for patches, perhaps you would like
1908 to join the discussion?
</p
>
1910 <p
>As usual, if you use Bitcoin and want to show your support of my
1911 activities, please send Bitcoin donations to my address
1912 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1917 <title>Automatic Google Drive sync using grive in Debian
</title>
1918 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
1919 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
1920 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
1921 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
1922 rescue the remains, I helped set up automatic sync with Google Drive.
1923 I did not find any sensible Debian package handling this
1924 automatically, so I rebuild the grive2 source from
1925 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
1926 task and added a autostart desktop entry and a small shell script to
1927 run in the background while the user is logged in to do the sync.
1928 Here is a sketch of the setup for future reference.
</p
>
1930 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
1931 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
1932 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
1933 to start the sync when the user log in:
</p
>
1935 <p
><blockquote
><pre
>
1937 Name=Google drive autosync
1939 Exec=/home/user/bin/grive-sync
1940 </pre
></blockquote
></p
>
1942 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
1943 ~/googledrive/ with the files in Google Drive.
</p
>
1945 <p
><blockquote
><pre
>
1950 if [
"$syncpid
" ] ; then
1954 trap cleanup EXIT INT QUIT
1955 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
1958 if ! xhost
>/dev/null
2>&1 ; then
1959 echo
"no DISPLAY, exiting as the user probably logged out
"
1962 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
1963 /usr/lib/grive/grive-sync.sh sync googledrive
1966 done
2>&1 | sed
"s%^%$
0:%
"
1967 </pre
></blockquote
></p
>
1969 <p
>Feel free to use the setup if you want. It can be assumed to be
1970 GNU GPL v2 licensed (or any later version, at your leisure), but I
1971 doubt this code is possible to claim copyright on.
</p
>
1973 <p
>As usual, if you use Bitcoin and want to show your support of my
1974 activities, please send Bitcoin donations to my address
1975 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1980 <title>Using the Kodi API to play Youtube videos
</title>
1981 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
1982 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
1983 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
1984 <description><p
>I continue to explore my Kodi installation, and today I wanted to
1985 tell it to play a youtube URL I received in a chat, without having to
1986 insert search terms using the on-screen keyboard. After searching the
1987 web for API access to the Youtube plugin and testing a bit, I managed
1988 to find a recipe that worked. If you got a kodi instance with its API
1989 available from http://kodihost/jsonrpc, you can try the following to
1990 have check out a nice cover band.
</p
>
1992 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
1993 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
1994 "params
": {
"item
": {
"file
":
1995 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
1996 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
1998 <p
>I
've extended kodi-stream program to take a video source as its
1999 first argument. It can now handle direct video links, youtube links
2000 and
'desktop
' to stream my desktop to Kodi. It is almost like a
2001 Chromecast. :)
</p
>
2003 <p
>As usual, if you use Bitcoin and want to show your support of my
2004 activities, please send Bitcoin donations to my address
2005 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2010 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
2011 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
2012 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
2013 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
2014 <description><p
>For a while now, I have looked for a sensible way to share images
2015 with my family using a self hosted solution, as it is unacceptable to
2016 place images from my personal life under the control of strangers
2017 working for data hoarders like Google or Dropbox. The last few days I
2018 have drafted an approach that might work out, and I would like to
2019 share it with you. I would like to publish images on a server under
2020 my control, and point some Internet connected display units using some
2021 free and open standard to the images I published. As my primary
2022 language is not limited to ASCII, I need to store metadata using
2023 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
2024 of reading a RSS feed with image references (aka using the
2025 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
2026 of such frames. In the end I gave up that approach.
</p
>
2028 <p
>Some months ago, I discovered that
2029 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
2030 read images from a RSS feed, and used it to set up a screen saver on
2031 my home info screen, showing images from the Daily images feed from
2032 NASA. This proved to work well. More recently I discovered that
2033 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
2034 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
2035 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
2036 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
2037 screen saver capable of reading a RSS feed with images and news. For
2038 fun, I used it this summer to test Kodi on my parents TV by hooking up
2039 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
2040 screen saver showing selected pictures from my selection.
</p
>
2042 <p
>Armed with motivation and a test photo frame, I set out to generate
2043 a RSS feed for the Kodi instance. I adjusted my
<a
2044 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
2045 /var/www/html/privatepictures/, wrote a small Perl script to extract
2046 title and description metadata from the photo files and generate the
2047 RSS file. I ended up using Perl instead of python, as the
2048 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
2049 tags I ended up using, while python3-exif did not. The relevant EXIF
2050 tags only support ASCII, so I had to find better alternatives. XMP
2051 seem to have the support I need.
</p
>
2053 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
2054 use tags that can be easily added/updated using normal free software
2055 photo managing software. I ended up using the tags set using this
2056 exiftool command, as these tags can also be set using digiKam:
</p
>
2058 <blockquote
><pre
>
2059 exiftool -headline=
'The RSS image title
' \
2060 -description=
'The RSS image description.
' \
2061 -subject+=for-family photo.jpeg
2062 </pre
></blockquote
>
2064 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
2065 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
2066 use the keyword/subject
'for-family
' to flag that the photo should be
2067 shared with my family. Images with this keyword set are located and
2068 copied into my Freedombox for the RSS generating script to find.
</p
>
2070 <p
>Are there better ways to do this? Get in touch if you have better
2071 suggestions.
</p
>
2073 <p
>As usual, if you use Bitcoin and want to show your support of my
2074 activities, please send Bitcoin donations to my address
2075 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2080 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
2081 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
2082 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
2083 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
2084 <description><p
>Last night, I wrote
2085 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
2086 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
2087 During the day I received valuable feedback, and thanks to the
2088 suggestions I have been able to rewrite the recipe into a much simpler
2089 approach requiring no setup at all. It is a single script that take
2090 care of it all.
</p
>
2092 <p
>This new script uses GStreamer instead of VLC to capture the
2093 desktop and stream it to Kodi. This fixed the video quality issue I
2094 saw initially. It further removes the need to add a m3u file on the
2095 Kodi machine, as it instead connects to
2096 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
2097 Kodi
</a
> and simply ask Kodi to play from the stream created using
2098 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
2099 the script below, run it with the DNS name or IP address of the kodi
2100 server to stream to as the only argument, and watch your screen show
2101 up on the Kodi screen. Note, it depend on multicast on the local
2102 network, so if you need to stream outside the local network, the
2103 script must be modified. Also note, I have no idea if audio work, as
2104 I only care about the picture part.
</p
>
2106 <blockquote
><pre
>
2109 # Stream the Linux desktop view to Kodi. See
2110 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
2111 # for backgorund information.
2113 # Make sure the stream is stopped in Kodi and the gstreamer process is
2114 # killed if something go wrong (for example if curl is unable to find the
2115 # kodi server). Do the same when interrupting this script.
2119 params=
"$
3"
2120 curl --silent --header
'Content-Type: application/json
' \
2121 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
2122 "http://$host/jsonrpc
"
2125 if [ -n
"$kodihost
" ] ; then
2126 # Stop the playing when we end
2127 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
2128 jq .result[].playerid)
2129 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
2131 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
2132 kill
"$gstpid
"
2135 trap cleanup EXIT INT
2137 if [ -n
"$
1" ]; then
2148 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
2149 cut -d
" " -f2|head -
1)
2150 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
2151 videoconvert ! queue2 ! \
2152 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
2153 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
2154 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
2155 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
2156 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
2157 > /dev/null
2>&1 &
2160 # Give stream a second to get going
2163 # Ask kodi to start streaming using its JSON-RPC API
2164 kodicmd
"$kodihost
" Player.Open \
2165 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
2167 # wait for gst to end
2168 wait
"$gstpid
"
2169 </pre
></blockquote
>
2171 <p
>I hope you find the approach useful. I know I do.
</p
>
2173 <p
>As usual, if you use Bitcoin and want to show your support of my
2174 activities, please send Bitcoin donations to my address
2175 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2180 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
2181 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
2182 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
2183 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
2184 <description><p
>PS: See
2185 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
2186 followup post
</a
> for a even better approach.
</p
>
2188 <p
>A while back, I was asked by a friend how to stream the desktop to
2189 my projector connected to Kodi. I sadly had to admit that I had no
2190 idea, as it was a task I never had tried. Since then, I have been
2191 looking for a way to do so, preferable without much extra software to
2192 install on either side. Today I found a way that seem to kind of
2193 work. Not great, but it is a start.
</p
>
2195 <p
>I had a look at several approaches, for example
2196 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
2197 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
2198 local storage enough to store the stream locally. This is not going
2199 to work well for me, lacking enough free space, and it would
2200 impossible for my friend to get working.
</p
>
2202 <p
>Next, it occurred to me that perhaps I could use VLC to create a
2203 video stream that Kodi could play. Preferably using
2204 broadcast/multicast, to avoid having to change any setup on the Kodi
2205 side when starting such stream. Unfortunately, the only recipe I
2206 could find using multicast used the rtp protocol, and this protocol
2207 seem to not be supported by Kodi.
</p
>
2209 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
2210 have to specify the IP address of the streaming machine in both the
2211 sending command and the file on the Kodi server. But it is showing my
2212 desktop, and thus allow us to have a shared look on the big screen at
2213 the programs I work on.
</p
>
2215 <p
>I did not spend much time investigating codeces. I combined the
2216 rtp and rtsp recipes from
2217 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
2218 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
2219 this working on the desktop/streaming end.
</p
>
2221 <blockquote
><pre
>
2222 vlc screen:// --sout \
2223 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
2224 </pre
></blockquote
>
2226 <p
>I ssh-ed into my Kodi box and created a file like this with the
2227 same IP address:
</p
>
2229 <blockquote
><pre
>
2230 echo rtsp://
192.168.11.4:
8080/test.sdp \
2231 > /storage/videos/screenstream.m3u
2232 </pre
></blockquote
>
2234 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
2235 as I can tell the IP must be hardcoded for this to work. In other
2236 words, if someone elses machine is going to do the steaming, you have
2237 to update screenstream.m3u on the Kodi machine and adjust the vlc
2238 recipe. To get started, locate the file in Kodi and select the m3u
2239 file while the VLC stream is running. The desktop then show up in my
2240 big screen. :)
</p
>
2242 <p
>When using the same technique to stream a video file with audio,
2243 the audio quality is really bad. No idea if the problem is package
2244 loss or bad parameters for the transcode. I do not know VLC nor Kodi
2245 enough to tell.
</p
>
2247 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
2248 succestions and reminded me about an important step. The
"screen:
"
2249 input source is only available once the vlc-plugin-access-extra
2250 package is installed on Debian. Without it, you will see this error
2251 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
2252 for details.
" He further found that it is possible to drop some parts
2253 of the VLC command line to reduce the amount of hardcoded information.
2254 It is also useful to consider using cvlc to avoid having the VLC
2255 window in the desktop view. In sum, this give us this command line on
2258 <blockquote
><pre
>
2259 cvlc screen:// --sout \
2260 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
2261 </pre
></blockquote
>
2263 <p
>and this on the Kodi end
<p
>
2265 <blockquote
><pre
>
2266 echo rtsp://
192.168.11.4:
8080/ \
2267 > /storage/videos/screenstream.m3u
2268 </pre
></blockquote
>
2270 <p
>Still bad image quality, though. But I did discover that streaming
2271 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
2272 audio quality, so I guess the issue is in the input or transcoding
2273 parts, not the rtsp part. I
've tried to change the vb and ab
2274 parameters to use more bandwidth, but it did not make a
2275 difference.
</p
>
2277 <p
>I further received a suggestion from Einar Haraldseid to try using
2278 gstreamer instead of VLC, and this proved to work great! He also
2279 provided me with the trick to get Kodi to use a multicast stream as
2280 its source. By using this monstrous oneliner, I can stream my desktop
2281 with good video quality in reasonable framerate to the
239.255.0.1
2282 multicast address on port
1234:
2284 <blockquote
><pre
>
2285 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
2286 videoconvert ! queue2 ! \
2287 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
2288 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
2289 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
2290 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
2291 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
2292 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
2293 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
2294 </pre
></blockquote
>
2296 <p
>and this on the Kodi end
<p
>
2298 <blockquote
><pre
>
2299 echo udp://@
239.255.0.1:
1234 \
2300 > /storage/videos/screenstream.m3u
2301 </pre
></blockquote
>
2303 <p
>Note the trick to pick a valid pulseaudio source. It might not
2304 pick the one you need. This approach will of course lead to trouble
2305 if more than one source uses the same multicast port and address.
2306 Note the ttl-mc=
1 setting, which limit the multicast packages to the
2307 local network. If the value is increased, your screen will be
2308 broadcasted further, one network
"hop
" for each increase (read up on
2309 multicast to learn more. :)!
</p
>
2311 <p
>Having cracked how to get Kodi to receive multicast streams, I
2312 could use this VLC command to stream to the same multicast address.
2313 The image quality is way better than the rtsp approach, but gstreamer
2314 seem to be doing a better job.
</p
>
2316 <blockquote
><pre
>
2317 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
2318 </pre
></blockquote
>
2320 <p
>As usual, if you use Bitcoin and want to show your support of my
2321 activities, please send Bitcoin donations to my address
2322 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2327 <title>What is the most supported MIME type in Debian in
2018?
</title>
2328 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
2329 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
2330 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
2331 <description><p
>Five years ago,
2332 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
2333 measured what the most supported MIME type in Debian was
</a
>, by
2334 analysing the desktop files in all packages in the archive. Since
2335 then, the DEP-
11 AppStream system has been put into production, making
2336 the task a lot easier. This made me want to repeat the measurement,
2337 to see how much things changed. Here are the new numbers, for
2338 unstable only this time:
2340 <p
><strong
>Debian Unstable:
</strong
></p
>
2344 ----- -----------------------
2356 30 audio/x-vorbis+ogg
2357 29 image/x-portable-pixmap
2359 27 image/x-portable-bitmap
2361 26 application/x-ogg
2367 <p
>The list was created like this using a sid chroot:
"cat
2368 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
2369 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
2371 <p
>It is interesting to see how image formats have passed text/plain
2372 as the most announced supported MIME type. These days, thanks to the
2373 AppStream system, if you run into a file format you do not know, and
2374 want to figure out which packages support the format, you can find the
2375 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
2376 look up all packages announcing support for this format in their
2377 AppStream metadata (XML or .desktop file) using
"appstreamcli
2378 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
2379 me, want to know which packages support inode/directory, you can get a
2380 list like this:
</p
>
2382 <p
><blockquote
><pre
>
2383 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
2390 Package: doublecmd-common
2392 Package: enlightenment
2412 </pre
></blockquote
></p
>
2414 <p
>Using the same method, I can quickly discover that the Sketchup file
2415 format is not yet supported by any package in Debian:
</p
>
2417 <p
><blockquote
><pre
>
2418 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
2419 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
2421 </pre
></blockquote
></p
>
2423 <p
>Yesterday I used it to figure out which packages support the STL
3D
2426 <p
><blockquote
><pre
>
2427 % appstreamcli what-provides mimetype application/sla|grep Package
2432 </pre
></blockquote
></p
>
2434 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
2436 <p
>As usual, if you use Bitcoin and want to show your support of my
2437 activities, please send Bitcoin donations to my address
2438 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2443 <title>Debian APT upgrade without enough free space on the disk...
</title>
2444 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
2445 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
2446 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
2447 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
2448 for a while, and when I need to update it there is not enough free
2449 space on the disk for apt to do a normal
'apt upgrade
'. I normally
2450 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
2451 upgrade only some of the packages in one batch, until the amount of
2452 packages to download fall below the amount of free space available.
2453 Today, I had about
500 packages to upgrade, and after a while I got
2454 tired of trying to install chunks of packages manually. I concluded
2455 that I did not have the spare hours required to complete the task, and
2456 decided to see if I could automate it. I came up with this small
2457 script which I call
'apt-in-chunks
':
</p
>
2459 <p
><blockquote
><pre
>
2462 # Upgrade packages when the disk is too full to upgrade every
2463 # upgradable package in one lump. Fetching packages to upgrade using
2464 # apt, and then installing using dpkg, to avoid changing the package
2465 # flag for manual/automatic.
2470 if [
"$
1" ]; then
2471 grep -v
"$
1"
2477 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
2478 echo
"Upgrading $p
"
2480 apt install --download-only -y $p
2481 for f in /var/cache/apt/archives/*.deb; do
2482 if [ -e
"$f
" ]; then
2483 dpkg -i /var/cache/apt/archives/*.deb
2488 </pre
></blockquote
></p
>
2490 <p
>The script will extract the list of packages to upgrade, try to
2491 download the packages needed to upgrade one package, install the
2492 downloaded packages using dpkg. The idea is to upgrade packages
2493 without changing the APT mark for the package (ie the one recording of
2494 the package was manually requested or pulled in as a dependency). To
2495 use it, simply run it as root from the command line. If it fail, try
2496 'apt install -f
' to clean up the mess and run the script again. This
2497 might happen if the new packages conflict with one of the old
2498 packages. dpkg is unable to remove, while apt can do this.
</p
>
2500 <p
>It take one option, a package to ignore in the list of packages to
2501 upgrade. The option to ignore a package is there to be able to skip
2502 the packages that are simply too large to unpack. Today this was
2503 'ghc
', but I have run into other large packages causing similar
2504 problems earlier (like TeX).
</p
>
2506 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
2507 alternative ways to handle this. The
"unattended-upgrades
2508 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
2509 each package to upgrade, and then upgrade them in order, smallest set
2510 first. It might be a better option than my above mentioned script.
2511 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
2512 the need for using
"dpkg -i
" in the script above.
</p
>
2514 <p
>As usual, if you use Bitcoin and want to show your support of my
2515 activities, please send Bitcoin donations to my address
2516 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2521 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
2522 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
2523 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
2524 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
2525 <description><p
>A new version of the
2526 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
2527 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
2528 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
2529 useful. It was uploaded the last few days, and the last update will
2530 enter testing tomorrow. See the
2531 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
2532 notes
</a
> for the list of bug fixes and new features. Version
3.2
2533 was announced
6 days ago. We will try to get it into Debian as
2536 <p
>More information related to
3D printing is available on the
2537 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
2538 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
2539 in Debian.
</p
>
2541 <p
>As usual, if you use Bitcoin and want to show your support of my
2542 activities, please send Bitcoin donations to my address
2543 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2548 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
2549 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
2550 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
2551 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
2552 <description><p
>After several months of working and waiting, I am happy to report
2553 that the nice and user friendly
3D printer slicer software Cura just
2554 entered Debian Unstable. It consist of five packages,
2555 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
2556 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
2557 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
2558 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
2559 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
2560 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
2561 two, uranium and cura, entered Unstable yesterday. This should make
2562 it easier for Debian users to print on at least the Ultimaker class of
2563 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
2564 make life easier for at least me. :)
</p
>
2566 <p
>The work to make this happen was done by Gregor Riepl, and I was
2567 happy to assist him in sponsoring the packages. With the introduction
2568 of Cura, Debian is up to three
3D printer slicers at your service,
2569 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
2570 printer, give it a go. :)
</p
>
2572 <p
>The
3D printer software is maintained by the
3D printer Debian
2573 team, flocking together on the
2574 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
2575 mailing list and the
2576 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
2577 IRC channel.
</p
>
2579 <p
>The next step for Cura in Debian is to update the cura package to
2580 version
3.0.3 and then update the entire set of packages to version
2581 3.1.0 which showed up the last few days.
</p
>
2586 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
2587 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
2588 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
2589 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
2590 <description><p
>At my nearby maker space,
2591 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
2592 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
2593 on Windows and MacOS X than Linux, because the software involved had
2594 to be manually compiled and set up on Linux while premade packages
2595 worked out of the box on Windows and MacOS X. I found this annoying,
2596 as the software involved,
2597 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
2598 and should be trivial to get up and running on Linux if someone took
2599 the time to package it for the relevant distributions. I even found
2600 <a href=
"https://bugs.debian.org/
706656">a request for adding into
2601 Debian
</a
> from
2013, which had seem some activity over the years but
2602 never resulted in the software showing up in Debian. So a few days
2603 ago I offered my help to try to improve the situation.
</p
>
2605 <p
>Now I am very happy to see that all the packages required by a
2606 working Cura in Debian are uploaded into Debian and waiting in the NEW
2607 queue for the ftpmasters to have a look. You can track the progress
2609 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
2610 status page for the
3D printer team
</a
>.
</p
>
2612 <p
>The uploaded packages are a bit behind upstream, and was uploaded
2613 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
2614 queue
</a
> while we work up updating the packages to the latest
2615 upstream version.
</p
>
2617 <p
>On a related note, two competitors for Cura, which I found harder
2618 to use and was unable to configure correctly for Ultimaker
2+ in the
2619 short time I spent on it, are already in Debian. If you are looking
2620 for
3D printer
"slicers
" and want something already available in
2622 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
2623 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
2624 The latter is a fork of the former.
</p
>
2626 <p
>As usual, if you use Bitcoin and want to show your support of my
2627 activities, please send Bitcoin donations to my address
2628 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2633 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
2634 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
2635 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
2636 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
2637 <description><p
>Every mobile phone announce its existence over radio to the nearby
2638 mobile cell towers. And this radio chatter is available for anyone
2639 with a radio receiver capable of receiving them. Details about the
2640 mobile phones with very good accuracy is of course collected by the
2641 phone companies, but this is not the topic of this blog post. The
2642 mobile phone radio chatter make it possible to figure out when a cell
2643 phone is nearby, as it include the SIM card ID (IMSI). By paying
2644 attention over time, one can see when a phone arrive and when it leave
2645 an area. I believe it would be nice to make this information more
2646 available to the general public, to make more people aware of how
2647 their phones are announcing their whereabouts to anyone that care to
2650 <p
>I am very happy to report that we managed to get something
2651 visualizing this information up and running for
2652 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
2653 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2654 library. The solution is based on the
2655 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
2656 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
2657 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
2658 Sone from the Computer Science department of the University of
2659 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
2660 IMSIs) as dots in a web browser graph, with lines to the dot
2661 representing mobile base station it is talking to. It was working in
2662 the lab yesterday, and was moved into place this morning.
</p
>
2664 <p
>We set up a fairly powerful desktop machine using Debian
2665 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2666 connected and visualize the visible cell phone towers using an
2667 <a href=
"https://github.com/marlow925/hopglass
">English version of
2668 Hopglass
</a
>. A fairly powerfull machine is needed as the
2669 grgsm_livemon_headless processes from
2670 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
2671 the radio signal to data packages is quite CPU intensive.
</p
>
2673 <p
>The frequencies to listen to, are identified using a slightly
2674 patched scan-and-livemon (to set the --args values for each receiver),
2675 and the Hopglass data is generated using the
2676 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
2677 in my meshviewer-output branch
</a
>. For some reason we could not get
2678 more than four SDRs working. There is also a geographical map trying
2679 to show the location of the base stations, but I believe their
2680 coordinates are hardcoded to some random location in Germany, I
2681 believe. The code should be replaced with code to look up location in
2682 a text file, a sqlite database or one of the online databases
2684 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
2685 issue for the topic
</a
>.
2687 <p
>If this sound interesting, visit the stand at the festival!
</p
>
2692 <title>Easier recipe to observe the cell phones around you
</title>
2693 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
2694 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
2695 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
2696 <description><p
>A little more than a month ago I wrote
2697 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
2698 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2699 to nearby mobile phone base stations using Debian GNU/Linux and a
2700 cheap USB software defined radio
</a
>, and thus being able to pinpoint
2701 the location of people and equipment (like cars and trains) with an
2702 accuracy of a few kilometer. Since then we have worked to make the
2703 procedure even simpler, and it is now possible to do this without any
2704 manual frequency tuning and without building your own packages.
</p
>
2706 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
2707 package is now included in Debian testing and unstable, and the
2708 IMSI-catcher code no longer require root access to fetch and decode
2709 the GSM data collected using gr-gsm.
</p
>
2711 <p
>Here is an updated recipe, using packages built by Debian and a git
2712 clone of two python scripts:
</p
>
2716 <li
>Start with a Debian machine running the Buster version (aka
2717 testing).
</li
>
2719 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
2720 python-scapy
</tt
>' as root to install required packages.
</li
>
2722 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
2723 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
2725 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
2727 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2728 scan-and-livemon
</tt
>' to locate the frequency of nearby base
2729 stations and start listening for GSM packages on one of them.
</li
>
2731 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2732 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
2736 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
2737 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
2738 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
2739 work with RTL
8232 and other similar USB radio receivers you can get
2741 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
2742 from ebay
</a
>), so for now the solution is to scan using the RTL radio
2743 and only use HackRF for fetching GSM data.
</p
>
2745 <p
>As far as I can tell, a cell phone only show up on one of the
2746 frequencies at the time, so if you are going to track and count every
2747 cell phone around you, you need to listen to all the frequencies used.
2748 To listen to several frequencies, use the --numrecv argument to
2749 scan-and-livemon to use several receivers. Further, I am not sure if
2750 phones using
3G or
4G will show as talking GSM to base stations, so
2751 this approach might not see all phones around you. I typically see
2752 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
2754 <p
>I
've tried to run the scanner on a
2755 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
2756 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
2757 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
2758 stdout, I am told there it is caused by a buffer overflow between the
2759 radio and GNU Radio, caused by the program being unable to read the
2760 GSM data fast enough. If you see a stream of
'O
's from the terminal
2761 where you started scan-and-livemon, you need a give the process more
2762 CPU power. Perhaps someone are able to optimize the code to a point
2763 where it become possible to set up RPi3 based GSM sniffers? I tried
2764 using Raspbian instead of Debian, but there seem to be something wrong
2765 with GNU Radio on raspbian, causing glibc to abort().
</p
>
2770 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
2771 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
2772 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
2773 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
2774 <description><p
>On friday, I came across an interesting article in the Norwegian
2775 web based ICT news magazine digi.no on
2776 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
2777 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
2778 DVB-T software defined radios. The article refered to instructions
2779 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
2780 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
2782 <p
>The instructions said to use Ubuntu, install pip using apt (to
2783 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2784 and the ask pybombs to fetch and build everything you need from
2785 scratch. I wanted to see if I could do the same on the most recent
2786 Debian packages, but this did not work because pybombs tried to build
2787 stuff that no longer build with the most recent openssl library or
2788 some other version skew problem. While trying to get this recipe
2789 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
2790 and the only piece of software dependency missing in Debian was the
2791 gr-gsm package. I also found out that the lead upstream developer of
2792 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2793 Debian packages provided in an Ubuntu PPA repository. All I needed to
2794 do was to dget the Debian source package and built it.
</p
>
2796 <p
>The IMSI collector is a python script listening for packages on the
2797 loopback network device and printing to the terminal some specific GSM
2798 packages with IMSI numbers in them. The code is fairly short and easy
2799 to understand. The reason this work is because gr-gsm include a tool
2800 to read GSM data from a software defined radio like a DVB-T USB stick
2801 and other software defined radios, decode them and inject them into a
2802 network device on your Linux machine (using the loopback device by
2803 default). This proved to work just fine, and I
've been testing the
2804 collector for a few days now.
</p
>
2806 <p
>The updated and simpler recipe is thus to
</p
>
2810 <li
>start with a Debian machine running Stretch or newer,
</li
>
2812 <li
>build and install the gr-gsm package available from
2813 <a href=
"http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
</a
>,
</li
>
2815 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
2817 <li
>run grgsm_livemon and adjust the frequency until the terminal
2818 where it was started is filled with a stream of text (meaning you
2819 found a GSM station).
</li
>
2821 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
2825 <p
>To make it even easier in the future to get this sniffer up and
2826 running, I decided to package
2827 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
2828 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
2829 #
871055</a
>), and the package was uploaded into the NEW queue today.
2830 Luckily the gnuradio maintainer has promised to help me, as I do not
2831 know much about gnuradio stuff yet.
</p
>
2833 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
2834 commercial tools like
2835 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
2836 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
2837 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
2838 Stingray
</a
>, but I hope the existance of cheap alternatives can make
2839 more people realise how their whereabouts when carrying a cell phone
2840 is easily tracked. Seeing the data flow on the screen, realizing that
2841 I live close to a police station and knowing that the police is also
2842 wearing cell phones, I wonder how hard it would be for criminals to
2843 track the position of the police officers to discover when there are
2844 police near by, or for foreign military forces to track the location
2845 of the Norwegian military forces, or for anyone to track the location
2846 of government officials...
</p
>
2848 <p
>It is worth noting that the data reported by the IMSI-catcher
2849 script mentioned above is only a fraction of the data broadcasted on
2850 the GSM network. It will only collect one frequency at the time,
2851 while a typical phone will be using several frequencies, and not all
2852 phones will be using the frequencies tracked by the grgsm_livemod
2853 program. Also, there is a lot of radio chatter being ignored by the
2854 simple_IMSI-catcher script, which would be collected by extending the
2855 parser code. I wonder if gr-gsm can be set up to listen to more than
2856 one frequency?
</p
>
2861 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
2862 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
2863 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
2864 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
2865 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
2867 <p
>I finally received a copy of the Norwegian Bokmål edition of
2868 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2869 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
2870 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2871 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
2872 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
2873 price. The book is also available for download in electronic form as
2874 PDF, EPUB and Mobipocket, as can be
2875 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
2876 as a web page
</a
>.
</p
>
2878 <p
>This is the second book I publish (the first was the book
2879 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
2881 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
2882 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
2884 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
2885 Bokmål
</a
>), and I am very excited to finally wrap up this
2887 "<a href=
"http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
23262290.html
">Håndbok
2888 for Debian-administratoren
</a
>" will be well received.
</p
>
2893 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
2894 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
2895 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
2896 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
2897 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
2898 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
2899 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2900 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2901 på om den fri oversetterløsningen
2902 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
2903 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
2905 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
2908 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2909 rolle og muligheter til å håndtere internasjonale utfordringer, som
2910 for eksempel flykningekrisen.
</p
>
2912 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2913 på temaet:
</p
>
2915 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
2916 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
2921 <p
>Dette oversetter Apertium slik:
</p
>
2924 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2925 andre aktørar og høve til å handtera internasjonale utfordringar, som
2926 til dømes *flykningekrisen.
</p
>
2928 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
2932 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
2933 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
2938 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
2939 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2940 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2941 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
2942 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
2943 det er kanskje flisespikking. Det understreker vel bare at det alltid
2944 trengs korrekturlesning etter automatisk oversettelse.
</p
>
2949 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
2950 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
2951 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
2952 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
2953 <description><p
>Over the years, administrating thousand of NFS mounting linux
2954 computers at the time, I often needed a way to detect if the machine
2955 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
2956 file or directory affected by the hang, the process (and possibly the
2957 shell) will hang too. So you want to be able to detect this without
2958 risking the detection process getting stuck too. It has not been
2959 obvious how to do this. When the hang has lasted a while, it is
2960 possible to find messages like these in dmesg:
</p
>
2962 <p
><blockquote
>
2963 nfs: server nfsserver not responding, still trying
2964 <br
>nfs: server nfsserver OK
2965 </blockquote
></p
>
2967 <p
>It is hard to know if the hang is still going on, and it is hard to
2968 be sure looking in dmesg is going to work. If there are lots of other
2969 messages in dmesg the lines might have rotated out of site before they
2970 are noticed.
</p
>
2972 <p
>While reading through the nfs client implementation in linux kernel
2973 code, I came across some statistics that seem to give a way to detect
2974 it. The om_timeouts sunrpc value in the kernel will increase every
2975 time the above log entry is inserted into dmesg. And after digging a
2976 bit further, I discovered that this value show up in
2977 /proc/self/mountstats on Linux.
</p
>
2979 <p
>The mountstats content seem to be shared between files using the
2980 same file system context, so it is enough to check one of the
2981 mountstats files to get the state of the mount point for the machine.
2982 I assume this will not show lazy umounted NFS points, nor NFS mount
2983 points in a different process context (ie with a different filesystem
2984 view), but that does not worry me.
</p
>
2986 <p
>The content for a NFS mount point look similar to this:
</p
>
2988 <p
><blockquote
><pre
>
2990 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2991 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
2992 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
2994 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
2995 sec: flavor=
1,pseudoflavor=
1
2996 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
2997 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2998 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
2999 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
3001 NULL:
0 0 0 0 0 0 0 0
3002 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
3003 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
3004 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
3005 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
3006 READLINK:
125 125 0 20472 18620 0 1112 1118
3007 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
3008 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
3009 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
3010 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
3011 SYMLINK:
903 903 0 233428 245488 6 5865 5917
3012 MKNOD:
80 80 0 20148 21760 0 299 304
3013 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
3014 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
3015 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
3016 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
3017 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
3018 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
3019 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
3020 FSINFO:
2 2 0 232 328 0 1 1
3021 PATHCONF:
1 1 0 116 140 0 0 0
3022 COMMIT:
0 0 0 0 0 0 0 0
3024 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
3026 </pre
></blockquote
></p
>
3028 <p
>The key number to look at is the third number in the per-op list.
3029 It is the number of NFS timeouts experiences per file system
3030 operation. Here
22 write timeouts and
5 access timeouts. If these
3031 numbers are increasing, I believe the machine is experiencing NFS
3032 hang. Unfortunately the timeout value do not start to increase right
3033 away. The NFS operations need to time out first, and this can take a
3034 while. The exact timeout value depend on the setup. For example the
3035 defaults for TCP and UDP mount points are quite different, and the
3036 timeout value is affected by the soft, hard, timeo and retrans NFS
3037 mount options.
</p
>
3039 <p
>The only way I have been able to get working on Debian and RedHat
3040 Enterprise Linux for getting the timeout count is to peek in /proc/.
3042 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
3043 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
3044 command can be used to get these timeout values. But this do not work
3045 on Linux, as far as I can tell. I
3046 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
3047 but have not seen any replies yet.
</p
>
3049 <p
>Is there a better way to figure out if a Linux NFS client is
3050 experiencing NFS hangs? Is there a way to detect which processes are
3051 affected? Is there a way to get the NFS mount going quickly once the
3052 network problem causing the NFS hang has been cleared? I would very
3053 much welcome some clues, as we regularly run into NFS hangs.
</p
>
3058 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
3059 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
3060 <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>
3061 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
3062 <description><p
>For almost a year now, we have been working on making a Norwegian
3063 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
3064 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
3065 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
3066 we are working on the proof reading to ensure consistent language and
3067 use of correct computer science terms. The plan is to make the book
3068 available on paper, as well as in electronic form. For that to
3069 happen, the proof reading must be completed and all the figures need
3070 to be translated. If you want to help out, get in touch.
</p
>
3072 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
3074 fresh PDF edition
</a
> in A4 format (the final book will have smaller
3075 pages) of the book created every morning is available for
3076 proofreading. If you find any errors, please
3077 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
3078 Weblate and correct the error
</a
>. The
3079 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
3080 of the translation including figures
</a
> is a useful source for those
3081 provide Norwegian bokmål screen shots and figures.
</p
>
3086 <title>Unlimited randomness with the ChaosKey?
</title>
3087 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
3088 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
3089 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
3090 <description><p
>A few days ago I ordered a small batch of
3091 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
3092 USB dongle for generating entropy created by Bdale Garbee and Keith
3093 Packard. Yesterday it arrived, and I am very happy to report that it
3094 work great! According to its designers, to get it to work out of the
3095 box, you need the Linux kernel version
4.1 or later. I tested on a
3096 Debian Stretch machine (kernel version
4.9), and there it worked just
3097 fine, increasing the available entropy very quickly. I wrote a small
3098 test oneliner to test. It first print the current entropy level,
3099 drain /dev/random, and then print the entropy level for five seconds.
3100 Here is the situation without the ChaosKey inserted:
</p
>
3102 <blockquote
><pre
>
3103 % cat /proc/sys/kernel/random/entropy_avail; \
3104 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
3105 for n in $(seq
1 5); do \
3106 cat /proc/sys/kernel/random/entropy_avail; \
3112 28 byte kopiert,
0,
000264565 s,
106 kB/s
3119 </pre
></blockquote
>
3121 <p
>The entropy level increases by
3-
4 every second. In such case any
3122 application requiring random bits (like a HTTPS enabled web server)
3123 will halt and wait for more entrpy. And here is the situation with
3124 the ChaosKey inserted:
</p
>
3126 <blockquote
><pre
>
3127 % cat /proc/sys/kernel/random/entropy_avail; \
3128 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
3129 for n in $(seq
1 5); do \
3130 cat /proc/sys/kernel/random/entropy_avail; \
3136 104 byte kopiert,
0,
000487647 s,
213 kB/s
3143 </pre
></blockquote
>
3145 <p
>Quite the difference. :) I bought a few more than I need, in case
3146 someone want to buy one here in Norway. :)
</p
>
3148 <p
>Update: The dongle was presented at Debconf last year. You might
3149 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
3150 recording illuminating
</a
>. It explains exactly what the source of
3151 randomness is, if you are unable to spot it from the schema drawing
3152 available from the ChaosKey web site linked at the start of this blog
3158 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
3159 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
3160 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
3161 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
3162 <description><p
>Did you ever wonder where the web trafic really flow to reach the
3163 web servers, and who own the network equipment it is flowing through?
3164 It is possible to get a glimpse of this from using traceroute, but it
3165 is hard to find all the details. Many years ago, I wrote a system to
3166 map the Norwegian Internet (trying to figure out if our plans for a
3167 network game service would get low enough latency, and who we needed
3168 to talk to about setting up game servers close to the users. Back
3169 then I used traceroute output from many locations (I asked my friends
3170 to run a script and send me their traceroute output) to create the
3171 graph and the map. The output from traceroute typically look like
3174 <p
><pre
>
3175 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
3176 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
3177 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
3178 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
3179 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
3180 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
3181 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
3182 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
3186 </pre
></p
>
3188 <p
>This show the DNS names and IP addresses of (at least some of the)
3189 network equipment involved in getting the data traffic from me to the
3190 www.stortinget.no server, and how long it took in milliseconds for a
3191 package to reach the equipment and return to me. Three packages are
3192 sent, and some times the packages do not follow the same path. This
3193 is shown for hop
5, where three different IP addresses replied to the
3194 traceroute request.
</p
>
3196 <p
>There are many ways to measure trace routes. Other good traceroute
3197 implementations I use are traceroute (using ICMP packages) mtr (can do
3198 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
3199 traceroute and a lot of other capabilities). All of them are easily
3200 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
3202 <p
>This time around, I wanted to know the geographic location of
3203 different route points, to visualize how visiting a web page spread
3204 information about the visit to a lot of servers around the globe. The
3205 background is that a web site today often will ask the browser to get
3206 from many servers the parts (for example HTML, JSON, fonts,
3207 JavaScript, CSS, video) required to display the content. This will
3208 leak information about the visit to those controlling these servers
3209 and anyone able to peek at the data traffic passing by (like your ISP,
3210 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
3212 <p
>Lets pick an example, the Norwegian parliament web site
3213 www.stortinget.no. It is read daily by all members of parliament and
3214 their staff, as well as political journalists, activits and many other
3215 citizens of Norway. A visit to the www.stortinget.no web site will
3216 ask your browser to contact
8 other servers: ajax.googleapis.com,
3217 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
3218 stats.g.doubleclick.net, www.google-analytics.com,
3219 www.googletagmanager.com and www.netigate.se. I extracted this by
3220 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
3221 Stortinget web page and tell me all the URLs PhantomJS downloaded to
3222 render the page (in HAR format using
3223 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
3224 netsniff example
</a
>. I am very grateful to Gorm for showing me how
3225 to do this). My goal is to visualize network traces to all IP
3226 addresses behind these DNS names, do show where visitors personal
3227 information is spread when visiting the page.
</p
>
3229 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
3230 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geoip-small.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using GeoIP
"/
></a
></p
>
3232 <p
>When I had a look around for options, I could not find any good
3233 free software tools to do this, and decided I needed my own traceroute
3234 wrapper outputting KML based on locations looked up using GeoIP. KML
3235 is easy to work with and easy to generate, and understood by several
3236 of the GIS tools I have available. I got good help from by NUUG
3237 colleague Anders Einar with this, and the result can be seen in
3238 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
3239 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
3240 free GeoIP databases I could find (and the for-pay databases my
3241 friends had access to) is not up to the task. The IP addresses of
3242 central Internet infrastructure would typically be placed near the
3243 controlling companies main office, and not where the router is really
3244 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
3245 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
3247 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
3248 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy-small.png
" alt=
"scapy traceroute graph for URLs used by www.stortinget.no
"/
></a
></p
>
3250 <p
>I also had a look at the visual traceroute graph created by
3251 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
3252 showing IP network ownership (aka AS owner) for the IP address in
3254 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
3255 graph display a lot of useful information about the traceroute in SVG
3256 format
</a
>, and give a good indication on who control the network
3257 equipment involved, but it do not include geolocation. This graph
3258 make it possible to see the information is made available at least for
3259 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
3260 3 Communications and NetDNA.
</p
>
3262 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
3263 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-small.png
" alt=
"example geotraceroute view for www.stortinget.no
"/
></a
></p
>
3265 <p
>In the process, I came across the
3266 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
3267 Salim Gasmi. Its methology of combining guesses based on DNS names,
3268 various location databases and finally use latecy times to rule out
3269 candidate locations seemed to do a very good job of guessing correct
3270 geolocation. But it could only do one trace at the time, did not have
3271 a sensor in Norway and did not make the geolocations easily available
3272 for postprocessing. So I contacted the developer and asked if he
3273 would be willing to share the code (he refused until he had time to
3274 clean it up), but he was interested in providing the geolocations in a
3275 machine readable format, and willing to set up a sensor in Norway. So
3276 since yesterday, it is possible to run traces from Norway in this
3277 service thanks to a sensor node set up by
3278 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
3279 trace in KML format for further processing.
</p
>
3281 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
3282 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using geotraceroute
"/
></a
></p
>
3284 <p
>Here we can see a lot of trafic passes Sweden on its way to
3285 Denmark, Germany, Holland and Ireland. Plenty of places where the
3286 Snowden confirmations verified the traffic is read by various actors
3287 without your best interest as their top priority.
</p
>
3289 <p
>Combining KML files is trivial using a text editor, so I could loop
3290 over all the hosts behind the urls imported by www.stortinget.no and
3291 ask for the KML file from GeoTraceroute, and create a combined KML
3292 file with all the traces (unfortunately only one of the IP addresses
3293 behind the DNS name is traced this time. To get them all, one would
3294 have to request traces using IP number instead of DNS names from
3295 GeoTraceroute). That might be the next step in this project.
</p
>
3297 <p
>Armed with these tools, I find it a lot easier to figure out where
3298 the IP traffic moves and who control the boxes involved in moving it.
3299 And every time the link crosses for example the Swedish border, we can
3300 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
3301 Britain and NSA in USA and cables around the globe. (Hm, what should
3302 we tell them? :) Keep that in mind if you ever send anything
3303 unencrypted over the Internet.
</p
>
3305 <p
>PS: KML files are drawn using
3306 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
3307 Rublev
<a/
>, as it was less cluttered than the local Linux application
3308 Marble. There are heaps of other options too.
</p
>
3310 <p
>As usual, if you use Bitcoin and want to show your support of my
3311 activities, please send Bitcoin donations to my address
3312 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3317 <title>Appstream just learned how to map hardware to packages too!
</title>
3318 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
3319 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
3320 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
3321 <description><p
>I received a very nice Christmas present today. As my regular
3322 readers probably know, I have been working on the
3323 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
3324 system
</a
> for many years. The goal of the Isenkram system is to make
3325 it easier for users to figure out what to install to get a given piece
3326 of hardware to work in Debian, and a key part of this system is a way
3327 to map hardware to packages. Isenkram have its own mapping database,
3328 and also uses data provided by each package using the AppStream
3329 metadata format. And today,
3330 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
3331 Debian learned to look up hardware the same way Isenkram is doing it,
3332 ie using fnmatch():
</p
>
3334 <p
><pre
>
3335 % appstreamcli what-provides modalias \
3336 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3337 Identifier: pymissile [generic]
3339 Summary: Control original Striker USB Missile Launcher
3341 % appstreamcli what-provides modalias usb:v0694p0002d0000
3342 Identifier: libnxt [generic]
3344 Summary: utility library for talking to the LEGO Mindstorms NXT brick
3347 Identifier: t2n [generic]
3349 Summary: Simple command-line tool for Lego NXT
3352 Identifier: python-nxt [generic]
3354 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
3357 Identifier: nbc [generic]
3359 Summary: C compiler for LEGO Mindstorms NXT bricks
3362 </pre
></p
>
3364 <p
>A similar query can be done using the combined AppStream and
3365 Isenkram databases using the isenkram-lookup tool:
</p
>
3367 <p
><pre
>
3368 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
3370 % isenkram-lookup usb:v0694p0002d0000
3376 </pre
></p
>
3378 <p
>You can find modalias values relevant for your machine using
3379 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
3381 <p
>If you want to make this system a success and help Debian users
3382 make the most of the hardware they have, please
3383 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
3384 AppStream metadata for your package following the guidelines
</a
>
3385 documented in the wiki. So far only
11 packages provide such
3386 information, among the several hundred hardware specific packages in
3387 Debian. The Isenkram database on the other hand contain
101 packages,
3388 mostly related to USB dongles. Most of the packages with hardware
3389 mapping in AppStream are LEGO Mindstorms related, because I have, as
3390 part of my involvement in
3391 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
3392 team
</a
> given priority to making sure LEGO users get proposed the
3393 complete set of packages in Debian for that particular hardware. The
3394 team also got a nice Christmas present today. The
3395 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
3396 package
</a
> made it into Debian. With this package in place, it is
3397 now possible to use the LEGO Mindstorms NXT unit with only free
3398 software, as the nxt-firmware package contain the source and firmware
3399 binaries for the NXT brick.
</p
>
3401 <p
>As usual, if you use Bitcoin and want to show your support of my
3402 activities, please send Bitcoin donations to my address
3403 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3408 <title>Isenkram updated with a lot more hardware-package mappings
</title>
3409 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
3410 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
3411 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
3412 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
3413 system
</a
> I wrote two years ago to make it easier in Debian to find
3414 and install packages to get your hardware dongles to work, is still
3415 going strong. It is a system to look up the hardware present on or
3416 connected to the current system, and map the hardware to Debian
3417 packages. It can either be done using the tools in isenkram-cli or
3418 using the user space daemon in the isenkram package. The latter will
3419 notify you, when inserting new hardware, about what packages to
3420 install to get the dongle working. It will even provide a button to
3421 click on to ask packagekit to install the packages.
</p
>
3423 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
3425 <p
><pre
>
3442 </pre
></p
>
3444 <p
>It can also list the firware package providing firmware requested
3445 by the load kernel modules, which in my case is an empty list because
3446 I have all the firmware my machine need:
3448 <p
><pre
>
3449 % /usr/sbin/isenkram-autoinstall-firmware -l
3450 info: did not find any firmware files requested by loaded kernel modules. exiting
3452 </pre
></p
>
3454 <p
>The last few days I had a look at several of the around
250
3455 packages in Debian with udev rules. These seem like good candidates
3456 to install when a given hardware dongle is inserted, and I found
3457 several that should be proposed by isenkram. I have not had time to
3458 check all of them, but am happy to report that now there are
97
3459 packages packages mapped to hardware by Isenkram.
11 of these
3460 packages provide hardware mapping using AppStream, while the rest are
3461 listed in the modaliases file provided in isenkram.
</p
>
3463 <p
>These are the packages with hardware mappings at the moment. The
3464 <strong
>marked packages
</strong
> are also announcing their hardware
3465 support using AppStream, for everyone to use:
</p
>
3467 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
3468 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
3469 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
3470 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
3471 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
3472 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
3473 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
3474 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
3475 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
3476 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
3477 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
3478 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
3479 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
3480 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
3481 pcscd, pidgin-blinklight, printer-driver-splix,
3482 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
3483 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
3484 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
3485 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
3486 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
3487 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
3488 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
3489 xserver-xorg-video-vmware, yubikey-personalization and
3490 zd1211-firmware
</p
>
3492 <p
>If you know of other packages, please let me know with a wishlist
3493 bug report against the isenkram-cli package, and ask the package
3495 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
3496 metadata according to the guidelines
</a
> to provide the information
3497 for everyone. In time, I hope to get rid of the isenkram specific
3498 hardware mapping and depend exclusively on AppStream.
</p
>
3500 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
3501 much hardware, and suggest that the package with with any ethernet
3502 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
3503 the details. I hope the maintainer find time to address it soon. In
3504 the mean time I provide an override in isenkram.
</p
>
3509 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
3510 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
3511 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
3512 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
3513 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
3515 <p
>In my early years, I played
3516 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
3517 Elite
</a
> on my PC. I spent many months trading and fighting in
3518 space, and reached the
'elite
' fighting status before I moved on. The
3519 original Elite game was available on Commodore
64 and the IBM PC
3520 edition I played had a
64 KB executable. I am still impressed today
3521 that the authors managed to squeeze both a
3D engine and details about
3522 more than
2000 planet systems across
7 galaxies into a binary so
3525 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
3526 software game Oolite inspired by Elite
</a
> for a while, but did not
3527 really have time to test it properly until a few days ago. It was
3528 great to discover that my old knowledge about trading routes were
3529 still valid. But my fighting and flying abilities were gone, so I had
3530 to retrain to be able to dock on a space station. And I am still not
3531 able to make much resistance when I am attacked by pirates, so I
3532 bougth and mounted the most powerful laser in the rear to be able to
3533 put up at least some resistance while fleeing for my life. :)
</p
>
3535 <p
>When playing Elite in the late eighties, I had to discover
3536 everything on my own, and I had long lists of prices seen on different
3537 planets to be able to decide where to trade what. This time I had the
3539 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
3540 where information about each planet is easily available with common
3541 price ranges and suggested trading routes. This improved my ability
3542 to earn money and I have been able to earn enough to buy a lot of
3543 useful equipent in a few days. I believe I originally played for
3544 months before I could get a docking computer, while now I could get it
3545 after less then a week.
</p
>
3547 <p
>If you like science fiction and dreamed of a life as a vagabond in
3548 space, you should try out Oolite. It is available for Linux, MacOSX
3549 and Windows, and is included in Debian and derivatives since
2011.
</p
>
3551 <p
>As usual, if you use Bitcoin and want to show your support of my
3552 activities, please send Bitcoin donations to my address
3553 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3558 <title>Quicker Debian installations using eatmydata
</title>
3559 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
3560 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
3561 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
3562 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
3563 installation system, observing how using
3564 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
3565 could speed up the installation
</a
> quite a bit. My testing measured
3566 speedup around
20-
40 percent for Debian Edu, where we install around
3567 1000 packages from within the installer. The eatmydata package
3568 provide a way to disable/delay file system flushing. This is a bit
3569 risky in the general case, as files that should be stored on disk will
3570 stay only in memory a bit longer than expected, causing problems if a
3571 machine crashes at an inconvenient time. But for an installation, if
3572 the machine crashes during installation the process is normally
3573 restarted, and avoiding disk operations as much as possible to speed
3574 up the process make perfect sense.
3576 <p
>I added code in the Debian Edu specific installation code to enable
3577 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
3578 but did not have time to push it any further. But a few months ago I
3579 picked it up again and worked with the libeatmydata package maintainer
3580 Mattia Rizzolo to make it easier for everyone to get this installation
3581 speedup in Debian. Thanks to our cooperation There is now an
3582 eatmydata-udeb package in Debian testing and unstable, and simply
3583 enabling/installing it in debian-installer (d-i) is enough to get the
3584 quicker installations. It can be enabled using preseeding. The
3585 following untested kernel argument should do the trick:
</p
>
3587 <blockquote
><pre
>
3588 preseed/early_command=
"anna-install eatmydata-udeb
"
3589 </pre
></blockquote
>
3591 <p
>This should ask d-i to install the package inside the d-i
3592 environment early in the installation sequence. Having it installed
3593 in d-i in turn will make sure the relevant scripts are called just
3594 after debootstrap filled /target/ with the freshly installed Debian
3595 system to configure apt to run dpkg with eatmydata. This is enough to
3596 speed up the installation process. There is a proposal to
3597 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
3598 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
3599 tested its impact.
</p
>
3605 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
3606 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
3607 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
3608 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
3609 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3610 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3611 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3612 elever over det ganske land skal levere inn hvert år. Det mange ikke
3613 vet er at selv om de kommersielle alternativene
3614 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
3615 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
3616 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3617 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3618 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3619 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3620 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3621 nynorsk, og få den automatoversatt til det andre skriftspråket.
3622 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3623 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3624 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3625 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3626 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
3627 teksten din i webskjemaet der.
3629 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
3630 teknologien kan du enten installere pakken
3631 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
3632 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3633 api.apertium.org. Se
3634 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
3635 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3636 denne teksten som ble skrevet på bokmål over maskinoversatt til
3641 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3642 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3643 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3644 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3645 veit er at sjølv om dei kommersielle alternativa
3646 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
3647 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
3648 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3649 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3650 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3651 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3652 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3653 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3654 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3655 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3656 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3657 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3658 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
3659 teksta di i *webskjemaet der.
3661 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
3662 teknologien kan du anten installera pakken
3663 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
3664 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3665 *api.*apertium.org. Sjå
3666 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
3667 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3668 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3674 <title>Coz profiler for multi-threaded software is now in Debian
</title>
3675 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
3676 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
3677 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
3678 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
3679 profiler able to run benchmarking experiments on the instrumented
3680 multi-threaded program, finally
3681 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
3682 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
3684 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
3685 blogged about the coz tool
</a
> in August working with upstream to make
3686 it suitable for Debian. There are still issues with clang
3687 compatibility, inline assembly only working x86 and minimized
3688 JavaScript libraries.
</p
>
3690 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
3692 <p
><blockquote
>
3693 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
3694 </blockquote
></p
>
3696 <p
>This will produce a profile.coz file in the current working
3697 directory with the profiling information. This is then given to a
3698 JavaScript application provided in the package and available from
3699 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
3700 To start the local copy, invoke it in a browser like this:
</p
>
3702 <p
><blockquote
>
3703 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
3704 </blockquote
></p
>
3706 <p
>See the project home page and the
3707 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
3708 ;login: article on Coz
</a
> for more information on how it is
3714 <title>My own self balancing Lego Segway
</title>
3715 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
3716 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
3717 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
3718 <description><p
>A while back I received a Gyro sensor for the NXT
3719 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
3720 present. It had been on my wishlist for a while, because I wanted to
3721 build a Segway like balancing lego robot. I had already built
3722 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
3723 robot
</a
> with the kids, using the light/color sensor included in the
3724 NXT kit as the balance sensor, but it was not working very well. It
3725 could balance for a while, but was very sensitive to the light
3726 condition in the room and the reflective properties of the surface and
3727 would fall over after a short while. I wanted something more robust,
3729 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
3730 gyro sensor from HiTechnic
</a
> I believed would solve it on my
3731 wishlist for some years before it suddenly showed up as a gift from my
3732 loved ones. :)
</p
>
3734 <p
>Unfortunately I have not had time to sit down and play with it
3735 since then. But that changed some days ago, when I was searching for
3736 lego segway information and came across a recipe from HiTechnic for
3738 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
3739 HTWay
</a
>, a segway like balancing robot. Build instructions and
3740 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
3741 code
</a
> was included, so it was just a question of putting it all
3742 together. And thanks to the great work of many Debian developers, the
3743 compiler needed to build the source for the NXT is already included in
3744 Debian, so I was read to go in less than an hour. The resulting robot
3745 do not look very impressive in its simplicity:
</p
>
3747 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
3749 <p
>Because I lack the infrared sensor used to control the robot in the
3750 design from HiTechnic, I had to comment out the last task
3751 (taskControl). I simply placed /* and */ around it get the program
3752 working without that sensor present. Now it balances just fine until
3753 the battery status run low:
</p
>
3755 <p align=
"center
"><video width=
"70%
" controls=
"true
">
3756 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
3757 </video
></p
>
3759 <p
>Now we would like to teach it how to follow a line and take remote
3760 control instructions using the included Bluetooth receiver in the NXT.
</p
>
3762 <p
>If you, like me, love LEGO and want to make sure we find the tools
3763 they need to work with LEGO in Debian and all our derivative
3764 distributions like Ubuntu, check out
3765 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
3766 project page
</a
> and join the Debian LEGO team. Personally I own a
3767 RCX and NXT controller (no EV3), and would like to make sure the
3768 Debian tools needed to program the systems I own work as they
3774 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
3775 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
3776 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
3777 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
3778 <description><p
>In July
3779 <a href=
"http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
">I
3780 wrote how to get the Signal Chrome/Chromium app working
</a
> without
3781 the ability to receive SMS messages (aka without a cell phone). It is
3782 time to share some experiences and provide an updated setup.
</p
>
3784 <p
>The Signal app have worked fine for several months now, and I use
3785 it regularly to chat with my loved ones. I had a major snag at the
3786 end of my summer vacation, when the the app completely forgot my
3787 setup, identity and keys. The reason behind this major mess was
3788 running out of disk space. To avoid that ever happening again I have
3789 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
3790 roll back to an earlier version if the files are wiped by mistake. I
3791 had to use it once after introducing the git backup. When rolling
3792 back to an earlier version, one need to use the
'reset session
' option
3793 in Signal to get going, and notify the people you talk with about the
3794 problem. I assume there is some sequence number tracking in the
3795 protocol to detect rollback attacks. The git repository is rather big
3796 (
674 MiB so far), but I have not tried to figure out if some of the
3797 content can be added to a .gitignore file due to lack of spare
3800 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
3801 make it impossible to send messages using Signal. I could still
3802 receive them, but had to patch the code with a new timestamp to send.
3803 I believe the timeout is added by the developers to force people to
3804 upgrade to the latest version of the app, even when there is no
3805 protocol changes, to reduce the version skew among the user base and
3806 thus try to keep the number of support requests down.
</p
>
3808 <p
>Since my original recipe, the Signal source code changed slightly,
3809 making the old patch fail to apply cleanly. Below is an updated
3810 patch, including the shell wrapper I use to start Signal. The
3811 original version required a new user to locate the JavaScript console
3812 and call a function from there. I got help from a friend with more
3813 JavaScript knowledge than me to modify the code to provide a GUI
3814 button instead. This mean that to get started you just need to run
3815 the wrapper and click the
'Register without mobile phone
' to get going
3816 now. I
've also modified the timeout code to always set it to
90 days
3817 in the future, to avoid having to patch the code regularly.
</p
>
3819 <p
>So, the updated recipe for Debian Jessie:
</p
>
3823 <li
>First, install required packages to get the source code and the
3824 browser you need. Signal only work with Chrome/Chromium, as far as I
3825 know, so you need to install it.
3828 apt install git tor chromium
3829 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3830 </pre
></li
>
3832 <li
>Modify the source code using command listed in the the patch
3833 block below.
</li
>
3835 <li
>Start Signal using the run-signal-app wrapper (for example using
3836 <tt
>`pwd`/run-signal-app
</tt
>).
3838 <li
>Click on the
'Register without mobile phone
', will in a phone
3839 number you can receive calls to the next minute, receive the
3840 verification code and enter it into the form field and press
3841 'Register
'. Note, the phone number you use will be user Signal
3842 username, ie the way others can find you on Signal.
</li
>
3844 <li
>You can now use Signal to contact others. Note, new contacts do
3845 not show up in the contact list until you restart Signal, and there is
3846 no way to assign names to Contacts. There is also no way to create or
3847 update chat groups. I suspect this is because the web app do not have
3848 a associated contact database.
</li
>
3852 <p
>I am still a bit uneasy about using Signal, because of the way its
3853 main author moxie0 reject federation and accept dependencies to major
3854 corporations like Google (part of the code is fetched from Google) and
3855 Amazon (the central coordination point is owned by Amazon). See for
3857 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
3858 LibreSignal issue tracker
</a
> for a thread documenting the authors
3859 view on these issues. But the network effect is strong in this case,
3860 and several of the people I want to communicate with already use
3861 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
3862 once it
<a href=
"https://bugs.debian.org/
830265">work on my
3863 laptop
</a
>? It already work on Windows and Android, and is included
3864 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
3865 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
3866 working on Debian Stable.
</p
>
3868 <p
>Anyway, this is the patch I apply to the Signal code to get it
3869 working. It switch to the production servers, disable to timeout,
3870 make registration easier and add the shell wrapper:
</p
>
3873 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
3874 diff --git a/js/background.js b/js/background.js
3875 index
24b4c1d.
.579345f
100644
3876 --- a/js/background.js
3877 +++ b/js/background.js
3882 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3883 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
3884 var SERVER_PORTS = [
80,
4433,
8443];
3885 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3886 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3887 var messageReceiver;
3888 window.getSocketStatus = function() {
3889 if (messageReceiver) {
3890 diff --git a/js/expire.js b/js/expire.js
3891 index
639aeae..beb91c3
100644
3896 'use strict
';
3897 - var BUILD_EXPIRATION =
0;
3898 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
3900 window.extension = window.extension || {};
3902 diff --git a/js/views/install_view.js b/js/views/install_view.js
3903 index
7816f4f.
.1d6233b
100644
3904 --- a/js/views/install_view.js
3905 +++ b/js/views/install_view.js
3908 'click .step1
': this.selectStep.bind(this,
1),
3909 'click .step2
': this.selectStep.bind(this,
2),
3910 -
'click .step3
': this.selectStep.bind(this,
3)
3911 +
'click .step3
': this.selectStep.bind(this,
3),
3912 +
'click .callreg
': function() { extension.install(
'standalone
') },
3915 clearQR: function() {
3916 diff --git a/options.html b/options.html
3917 index dc0f28e.
.8d709f6
100644
3921 &lt;div class=
'nav
'>
3922 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
3923 &lt;p
>{{ installTagline }}
&lt;/p
>
3924 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
3925 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
3926 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
3929 &lt;span class=
'dot step1 selected
'>&lt;/span
>
3930 &lt;span class=
'dot step2
'>&lt;/span
>
3931 &lt;span class=
'dot step3
'>&lt;/span
>
3932 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
3933 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
3939 +userdata=
"`pwd`/userdata
"
3940 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
3941 + (cd $userdata
&& git init)
3943 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
3945 + --proxy-server=
"socks://localhost:
9050" \
3946 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3948 chmod a+rx run-signal-app
3951 <p
>As usual, if you use Bitcoin and want to show your support of my
3952 activities, please send Bitcoin donations to my address
3953 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3958 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
3959 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
3960 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
3961 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
3962 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
3963 system
</a
> provide a practical and easy way to figure out which
3964 packages support the hardware in a given machine. The command line
3965 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
3966 convenient way to list and install packages relevant for the current
3967 hardware during system installation, both user space packages and
3968 firmware packages. The GUI background daemon on the other hand provide
3969 a pop-up proposing to install packages when a new dongle is inserted
3970 while using the computer. For example, if you plug in a smart card
3971 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
3972 that package isn
't already installed, and if you plug in a USB video
3973 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
3974 cheese is currently missing. This already work just fine.
</p
>
3976 <p
>But Isenkram depend on a database mapping from hardware IDs to
3977 package names. When I started no such database existed in Debian, so
3978 I made my own data set and included it with the isenkram package and
3979 made isenkram fetch the latest version of this database from git using
3980 http. This way the isenkram users would get updated package proposals
3981 as soon as I learned more about hardware related packages.
</p
>
3983 <p
>The hardware is identified using modalias strings. The modalias
3984 design is from the Linux kernel where most hardware descriptors are
3985 made available as a strings that can be matched using filename style
3986 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3987 identifiers.
</p
>
3989 <p
>The downside to the Isenkram specific database is that there is no
3990 information about relevant distribution / Debian version, making
3991 isenkram propose obsolete packages too. But along came AppStream, a
3992 cross distribution mechanism to store and collect metadata about
3993 software packages. When I heard about the proposal, I contacted the
3994 people involved and suggested to add a hardware matching rule using
3995 modalias strings in the specification, to be able to use AppStream for
3996 mapping hardware to packages. This idea was accepted and AppStream is
3997 now a great way for a package to announce the hardware it support in a
3998 distribution neutral way. I wrote
3999 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
4000 recipe on how to add such meta-information
</a
> in a blog post last
4001 December. If you have a hardware related package in Debian, please
4002 announce the relevant hardware IDs using AppStream.
</p
>
4004 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
4005 RCX or NXT unit, announce this support using AppStream. The effect is
4006 that when you insert such LEGO robot controller into your Debian
4007 machine, Isenkram will propose to install the packages needed to get
4008 it working. The intention is that this should allow the local user to
4009 start programming his robot controller right away without having to
4010 guess what packages to use or which permissions to fix.
</p
>
4012 <p
>But when I sat down with my son the other day to program our NXT
4013 unit using his Debian Stretch computer, I discovered something
4014 annoying. The local console user (ie my son) did not get access to
4015 the USB device for programming the unit. This used to work, but no
4016 longer in Jessie and Stretch. After some investigation and asking
4017 around on #debian-devel, I discovered that this was because udev had
4018 changed the mechanism used to grant access to local devices. The
4019 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
4020 no longer applied, because LDAP users no longer was added to the
4021 plugdev group during login. Michael Biebl told me that this method
4022 was obsolete and the new method used ACLs instead. This was good
4023 news, as the plugdev mechanism is a mess when using a remote user
4024 directory like LDAP. Using ACLs would make sure a user lost device
4025 access when she logged out, even if the user left behind a background
4026 process which would retain the plugdev membership with the ConsoleKit
4027 setup. Armed with this knowledge I moved on to fix the access problem
4028 for the LEGO Mindstorms related packages.
</p
>
4030 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
4031 applied directly for a device, or is applied in
4032 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
4033 LEGO Mindstorms udev rules did not have a class, I decided to add the
4034 tag directly in the udev rules files included in the packages. Here
4035 is one example. For the nqc C compiler for the RCX, the
4036 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
4038 <p
><pre
>
4039 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
4040 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
4041 </pre
></p
>
4043 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
4044 packages using plugdev in their /lib/udev/rules.d/ files should be
4045 changed to use this tag (either directly or indirectly via
4046 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
4047 to detect this?
</p
>
4049 <p
>I
've been unable to find good documentation on the uaccess feature.
4050 It is unclear to me if the uaccess tag is an internal implementation
4051 detail like the udev-acl tag used by
4052 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
4053 indirect method is the preferred way. Michael
4054 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
4055 documentation from the systemd project
</a
> and I hope it will make
4056 this clearer. For now I use the generic classes when they exist and
4057 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
4058 directly if no such class exist.
</p
>
4060 <p
>To learn more about the isenkram system, please check out
4061 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
4062 blog posts tagged isenkram
</a
>.
</p
>
4064 <p
>To help out making life for LEGO constructors in Debian easier,
4065 please join us on our IRC channel
4066 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
4067 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
4068 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
4069 list is not yet created, but we are working on it. :)
</p
>
4071 <p
>As usual, if you use Bitcoin and want to show your support of my
4072 activities, please send Bitcoin donations to my address
4073 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4078 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
4079 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
4080 <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>
4081 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
4082 <description><p
>In April we
4083 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
4084 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
4085 how to set up and administrate a Debian system. Today I am happy to
4086 report that the first draft is now publicly available. You can find
4087 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
4088 Administrator
's Handbook page
</a
> (under Other languages). The first
4089 eight chapters have a first draft translation, and we are working on
4090 proofreading the content. If you want to help out, please start
4092 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
4093 hosted weblate project page
</a
>, and get in touch using
4094 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
4095 translators mailing list
</a
>. Please also check out
4096 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
4097 contributors
</a
>. A good way to contribute is to proofread the text
4098 and update weblate if you find errors.
</p
>
4100 <p
>Our goal is still to make the Norwegian book available on paper as well as
4101 electronic form.
</p
>
4106 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
4107 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
4108 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
4109 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
4110 <description><p
>This summer, I read a great article
4111 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
4112 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
4113 how to profile multi-threaded programs. It presented a system for
4114 profiling software by running experiences in the running program,
4115 testing how run time performance is affected by
"speeding up
" parts of
4116 the code to various degrees compared to a normal run. It does this by
4117 slowing down parallel threads while the
"faster up
" code is running
4118 and measure how this affect processing time. The processing time is
4119 measured using probes inserted into the code, either using progress
4120 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
4121 can also measure unmodified code by measuring complete the program
4122 runtime and running the program several times instead.
</p
>
4124 <p
>The project and presentation was so inspiring that I would like to
4125 get the system into Debian. I
4126 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
4127 a WNPP request for it
</a
> and contacted upstream to try to make the
4128 system ready for Debian by sending patches. The build process need to
4129 be changed a bit to avoid running
'git clone
' to get dependencies, and
4130 to include the JavaScript web page used to visualize the collected
4131 profiling information included in the source package.
4132 But I expect that should work out fairly soon.
</p
>
4134 <p
>The way the system work is fairly simple. To run an coz experiment
4135 on a binary with debug symbols available, start the program like this:
4137 <p
><blockquote
><pre
>
4138 coz run --- program-to-run
4139 </pre
></blockquote
></p
>
4141 <p
>This will create a text file profile.coz with the instrumentation
4142 information. To show what part of the code affect the performance
4143 most, use a web browser and either point it to
4144 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
4145 or use the copy from git (in the gh-pages branch). Check out this web
4146 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
4147 profiling more useful you include
&lt;coz.h
&gt; and insert the
4148 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
4149 code, rebuild and run the profiler. This allow coz to do more
4150 targeted experiments.
</p
>
4152 <p
>A video published by ACM
4153 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
4154 Coz profiler
</a
> is available from Youtube. There is also a paper
4155 from the
25th Symposium on Operating Systems Principles available
4157 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
4158 finding code that counts with causal profiling
</a
>.
</p
>
4160 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
4161 for Coz is available from github. It will only build with clang
4163 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
4164 feature missing in GCC
</a
>, but I
've submitted
4165 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
4166 it
</a
> and hope it will be included in the upstream source soon.
</p
>
4168 <p
>Please get in touch if you, like me, would like to see this piece
4169 of software in Debian. I would very much like some help with the
4170 packaging effort, as I lack the in depth knowledge on how to package
4171 C++ libraries.
</p
>
4176 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
4177 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
4178 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
4179 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
4180 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
4181 to be a slight challenge. Here is the recipe if I ever need to do it
4182 again. It all started by me wanting to try the recipe to set up
4183 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
4184 hardened Android installation
</a
> from the Tor project blog on a
4185 device I had access to. It is a old mobile phone with a broken
4186 microphone The initial idea had been to just
4187 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
4188 CyanogenMod on it
</a
>, but did not quite find time to start on it
4189 until a few days ago.
</p
>
4191 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
4192 loader (press volume down and power at the same time), (
2) select
4193 'fastboot
' before (
3) connecting the device via USB to a Linux
4194 machine, (
4) request the device identifier token by running
'fastboot
4195 oem get_identifier_token
', (
5) request the device unlocking key using
4196 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
4197 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
4199 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
4200 or newer, and the device I was working on had
2.00.0027. This
4201 apparently can be easily fixed by downloading a Windows program and
4202 running it on your Windows machine, if you accept the terms Microsoft
4203 require you to accept to use Windows - which I do not. So I had to
4204 come up with a different approach. I got a lot of help from AndyCap
4205 on #nuug, and would not have been able to get this working without
4208 <p
>First I needed to extract the hboot firmware from
4209 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
4210 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
4211 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
4212 project named unruu
</a
> using libunshield. The unshield tool did not
4213 recognise the file format, but unruu worked and extracted rom.zip,
4214 containing the new hboot firmware and a text file describing which
4215 devices it would work for.
</p
>
4217 <p
>Next, I needed to get the new firmware into the device. For this I
4218 followed some instructions
4219 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
4220 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
4221 machine with Debian testing:
</p
>
4223 <p
><pre
>
4224 adb reboot-bootloader
4225 fastboot oem rebootRUU
4226 fastboot flash zip rom.zip
4227 fastboot flash zip rom.zip
4229 </pre
></p
>
4231 <p
>The flash command apparently need to be done twice to take effect,
4232 as the first is just preparations and the second one do the flashing.
4233 The adb command is just to get to the boot loader menu, so turning the
4234 device on while holding volume down and the power button should work
4237 <p
>With the new hboot version in place I could start following the
4238 instructions on the HTC developer web site. I got the device token
4239 like this:
</p
>
4241 <p
><pre
>
4242 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
4245 <p
>And once I got the unlock code via email, I could use it like
4248 <p
><pre
>
4249 fastboot flash unlocktoken Unlock_code.bin
4250 </pre
></p
>
4252 <p
>And with that final step in place, the phone was unlocked and I
4253 could start stuffing the software of my own choosing into the device.
4254 So far I only inserted a replacement recovery image to wipe the phone
4255 before I start. We will see what happen next. Perhaps I should
4256 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
4261 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
4262 <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>
4263 <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>
4264 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
4265 <description><p
>For a while now, I have wanted to test
4266 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
4267 said to provide end to end encrypted communication and several of my
4268 friends and family are already using it. As I by choice do not own a
4269 mobile phone, this proved to be harder than expected. And I wanted to
4270 have the source of the client and know that it was the code used on my
4271 machine. But yesterday I managed to get it working. I used the
4272 Github source, compared it to the source in
4273 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
4274 Signal Chrome app
</a
> available from the Chrome web store, applied
4275 patches to use the production Signal servers, started the app and
4276 asked for the hidden
"register without a smart phone
" form. Here is
4277 the recipe how I did it.
</p
>
4279 <p
>First, I fetched the Signal desktop source from Github, using
4282 git clone https://github.com/WhisperSystems/Signal-Desktop.git
4285 <p
>Next, I patched the source to use the production servers, to be
4286 able to talk to other Signal users:
</p
>
4289 cat
&lt;
&lt;EOF | patch -p0
4290 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
4291 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
4292 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
4297 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
4298 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
4299 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
4300 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
4301 var messageReceiver;
4302 window.getSocketStatus = function() {
4303 if (messageReceiver) {
4304 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
4305 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
4306 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
4309 'use strict
';
4310 - var BUILD_EXPIRATION =
0;
4311 + var BUILD_EXPIRATION =
1474492690000;
4313 window.extension = window.extension || {};
4318 <p
>The first part is changing the servers, and the second is updating
4319 an expiration timestamp. This timestamp need to be updated regularly.
4320 It is set
90 days in the future by the build process (Gruntfile.js).
4321 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
4323 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
4324 script to launch Signal in Chromium.
</p
>
4331 --proxy-server=
"socks://localhost:
9050" \
4332 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
4335 <p
> The script start the app and configure Chromium to use the Tor
4336 SOCKS5 proxy to make sure those controlling the Signal servers (today
4337 Amazon and Whisper Systems) as well as those listening on the lines
4338 will have a harder time location my laptop based on the Signal
4339 connections if they use source IP address.
</p
>
4341 <p
>When the script starts, one need to follow the instructions under
4342 "Standalone Registration
" in the CONTRIBUTING.md file in the git
4343 repository. I right clicked on the Signal window to get up the
4344 Chromium debugging tool, visited the
'Console
' tab and wrote
4345 'extension.install(
"standalone
")
' on the console prompt to get the
4346 registration form. Then I entered by land line phone number and
4347 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
4348 repeated the verification code three times. After entering the number
4349 into the verification code field in the form, I could start using
4350 Signal from my laptop.
4352 <p
>As far as I can tell, The Signal app will leak who is talking to
4353 whom and thus who know who to those controlling the central server,
4354 but such leakage is hard to avoid with a centrally controlled server
4355 setup. It is something to keep in mind when using Signal - the
4356 content of your chats are harder to intercept, but the meta data
4357 exposing your contact network is available to people you do not know.
4358 So better than many options, but not great. And sadly the usage is
4359 connected to my land line, thus allowing those controlling the server
4360 to associate it to my home and person. I would prefer it if only
4361 those I knew could tell who I was on Signal. There are options
4362 avoiding such information leakage, but most of my friends are not
4363 using them, so I am stuck with Signal for now.
</p
>
4365 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
4367 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
4368 and updated recipe for using the Signal app without a mobile
4369 phone
</a
>.
</p
>
4374 <title>The new
"best
" multimedia player in Debian?
</title>
4375 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
4376 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
4377 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
4378 <description><p
>When I set out a few weeks ago to figure out
4379 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
4380 multimedia player in Debian claimed to support most file formats /
4381 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
4382 the various players claimed support for. The range was from
55 to
130
4383 MIME types. I suspect most media formats are supported by all
4384 players, but this is not really reflected in the MimeTypes values in
4385 their desktop files. There are probably also some bogus MIME types
4386 listed, but it is hard to identify which one this is.
</p
>
4388 <p
>Anyway, in the mean time I got in touch with upstream for some of
4389 the players suggesting to add more MIME types to their desktop files,
4390 and decided to spend some time myself improving the situation for my
4391 favorite media player VLC. The fixes for VLC entered Debian unstable
4392 yesterday. The complete list of MIME types can be seen on the
4393 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
4394 player MIME type support status
</a
> Debian wiki page.
</p
>
4396 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
4397 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
4398 kmplayer. I am sure some of the other players desktop files support
4399 several of the formats currently listed as working only with vlc,
4400 toten and parole.
</p
>
4402 <p
>A sad observation is that only
14 MIME types are listed as
4403 supported by all the tested multimedia players in Debian in their
4404 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
4405 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
4406 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
4407 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
4408 it sad that video/ogg and video/webm is not supported by all the media
4409 players in Debian. As far as I can tell, all of them can handle both
4415 <title>A program should be able to open its own files on Linux
</title>
4416 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
4417 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
4418 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
4419 <description><p
>Many years ago, when koffice was fresh and with few users, I
4420 decided to test its presentation tool when making the slides for a
4421 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
4422 wrote the first draft of the slides, saved the result and went to bed
4423 the day before I would give the talk. The next day I took a plane to
4424 the location where the meeting should take place, and on the plane I
4425 started up koffice again to polish the talk a bit, only to discover
4426 that kpresenter refused to load its own data file. I cursed a bit and
4427 started making the slides again from memory, to have something to
4428 present when I arrived. I tested that the saved files could be
4429 loaded, and the day seemed to be rescued. I continued to polish the
4430 slides until I suddenly discovered that the saved file could no longer
4431 be loaded into kpresenter. In the end I had to rewrite the slides
4432 three times, condensing the content until the talk became shorter and
4433 shorter. After the talk I was able to pinpoint the problem
&ndash;
4434 kpresenter wrote inline images in a way itself could not understand.
4435 Eventually that bug was fixed and kpresenter ended up being a great
4436 program to make slides. The point I
'm trying to make is that we
4437 expect a program to be able to load its own data files, and it is
4438 embarrassing to its developers if it can
't.
</p
>
4440 <p
>Did you ever experience a program failing to load its own data
4441 files from the desktop file browser? It is not a uncommon problem. A
4442 while back I discovered that the screencast recorder
4443 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
4444 browser would refuse to open. No video player claimed to understand
4445 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
4446 returning the application/ogg MIME type, which no video player I had
4447 installed listed as a MIME type they would understand. I asked for
4448 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
4449 behavour
</a
> and use the MIME type video/ogg instead. I also asked
4450 several video players to add video/ogg to their desktop files, to give
4451 the file browser an idea what to do about Ogg Theora files. After a
4452 while, the desktop file browsers in Debian started to handle the
4453 output from gtk-recordmydesktop properly.
</p
>
4455 <p
>But history repeats itself. A few days ago I tested the music
4456 system Rosegarden again, and I discovered that the KDE and xfce file
4457 browsers did not know what to do with the Rosegarden project files
4458 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
4459 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
4460 included in the next upload. To increase the chance of me remembering
4461 how to fix the problem next time some program fail to load its files
4462 from the file browser, here are some notes on how to fix it.
</p
>
4464 <p
>The file browsers in Debian in general operates on MIME types.
4465 There are two sources for the MIME type of a given file. The output from
4466 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
4467 shared MIME type registry (under /usr/share/mime/). The file MIME
4468 type is mapped to programs supporting the MIME type, and this
4469 information is collected from
4470 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
4471 desktop files
</a
> available in /usr/share/applications/. If there is
4472 one desktop file claiming support for the MIME type of the file, it is
4473 activated when asking to open a given file. If there are more, one
4474 can normally select which one to use by right-clicking on the file and
4475 selecting the wanted one using
'Open with
' or similar. In general
4476 this work well. But it depend on each program picking a good MIME
4478 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
4479 MIME type registered with IANA
</a
>), file and/or the shared MIME
4480 registry recognizing the file and the desktop file to list the MIME
4481 type in its list of supported MIME types.
</p
>
4483 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
4484 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
4485 Shared MIME database
</a
> look like this:
</p
>
4487 <p
><blockquote
><pre
>
4488 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
4489 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
4490 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
4491 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
4492 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
4493 &lt;glob pattern=
"*.rg
"/
&gt;
4494 &lt;/mime-type
&gt;
4495 &lt;/mime-info
&gt;
4496 </pre
></blockquote
></p
>
4498 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
4499 (it is a gzipped XML file). Note, it is much better to use an
4500 official MIME type registered with IANA than it is to make up ones own
4501 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
4503 <p
>The desktop file of the rosegarden program failed to list
4504 audio/x-rosegarden in its list of supported MIME types, causing the
4505 file browsers to have no idea what to do with *.rg files:
</p
>
4507 <p
><blockquote
><pre
>
4508 % grep Mime /usr/share/applications/rosegarden.desktop
4509 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
4510 X-KDE-NativeMimeType=audio/x-rosegarden-composition
4512 </pre
></blockquote
></p
>
4514 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
4515 MimeType= line.
</p
>
4517 <p
>If you run into a file which fail to open the correct program when
4518 selected from the file browser, please check out the output from
4519 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
4520 MIME type is registered somewhere under /usr/share/mime/ and check
4521 that some desktop file under /usr/share/applications/ is claiming
4522 support for this MIME type. If not, please report a bug to have it
4528 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
4529 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
4530 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
4531 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
4532 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
4533 system
</a
> is a user-focused solution in Debian for handling hardware
4534 related packages. The idea is to have a database of mappings between
4535 hardware and packages, and pop up a dialog suggesting for the user to
4536 install the packages to use a given hardware dongle. Some use cases
4537 are when you insert a Yubikey, it proposes to install the software
4538 needed to control it; when you insert a braille reader list it
4539 proposes to install the packages needed to send text to the reader;
4540 and when you insert a ColorHug screen calibrator it suggests to
4541 install the driver for it. The system work well, and even have a few
4542 command line tools to install firmware packages and packages for the
4543 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
4545 <p
>The system was initially written using aptdaemon, because I found
4546 good documentation and example code on how to use it. But aptdaemon
4547 is going away and is generally being replaced by
4548 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
4549 so Isenkram needed a rewrite. And today, thanks to the great patch
4550 from my college Sunil Mohan Adapa in the FreedomBox project, the
4551 rewrite finally took place. I
've just uploaded a new version of
4552 Isenkram into Debian Unstable with the patch included, and the default
4553 for the background daemon is now to use PackageKit. To check it out,
4554 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
4555 and see if it is recognised.
</p
>
4557 <p
>If you want to know what kind of packages isenkram would propose for
4558 the machine it is running on, you can check out the isenkram-lookup
4559 program. This is what it look like on a Thinkpad X230:
</p
>
4561 <p
><blockquote
><pre
>
4577 </pre
></blockquote
></p
>
4579 <p
>The hardware mappings come from several places. The preferred way
4580 is for packages to announce their hardware support using
4581 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
4582 cross distribution appstream system
</a
>.
4584 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
4585 blog posts about isenkram
</a
> to learn how to do that.
</p
>
4590 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
4591 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
4592 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
4593 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
4594 <description><p
>Yesterday I updated the
4595 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
4596 package in Debian
</a
> with a few patches sent to me by skilled and
4597 enterprising users. There were some nice user and visible changes.
4598 First of all, both desktop menu entries now work. A design flaw in
4599 one of the script made the history graph fail to show up (its PNG was
4600 dumped in ~/.xsession-errors) if no controlling TTY was available.
4601 The script worked when called from the command line, but not when
4602 called from the desktop menu. I changed this to look for a DISPLAY
4603 variable or a TTY before deciding where to draw the graph, and now the
4604 graph window pop up as expected.
</p
>
4606 <p
>The next new feature is a discharge rate estimator in one of the
4607 graphs (the one showing the last few hours). New is also the user of
4608 colours showing charging in blue and discharge in red. The percentages
4609 of this graph is relative to last full charge, not battery design
4612 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
4614 <p
>The other graph show the entire history of the collected battery
4615 statistics, comparing it to the design capacity of the battery to
4616 visualise how the battery life time get shorter over time. The red
4617 line in this graph is what the previous graph considers
100 percent:
4619 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
4621 <p
>In this graph you can see that I only charge the battery to
80
4622 percent of last full capacity, and how the capacity of the battery is
4623 shrinking. :(
</p
>
4625 <p
>The last new feature is in the collector, which now will handle
4626 more hardware models. On some hardware, Linux power supply
4627 information is stored in /sys/class/power_supply/ACAD/, while the
4628 collector previously only looked in /sys/class/power_supply/AC/. Now
4629 both are checked to figure if there is power connected to the
4632 <p
>If you are interested in how your laptop battery is doing, please
4634 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4635 in Debian unstable, or rebuild it on Jessie to get it working on
4636 Debian stable. :) The upstream source is available from
<a
4637 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4638 Patches are very welcome.
</p
>
4640 <p
>As usual, if you use Bitcoin and want to show your support of my
4641 activities, please send Bitcoin donations to my address
4642 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4647 <title>Debian now with ZFS on Linux included
</title>
4648 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
4649 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
4650 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
4651 <description><p
>Today, after many years of hard work from many people,
4652 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
4653 Debian. The package status can be seen on
4654 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
4655 for zfs-linux
</a
>. and
4656 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4657 team status page
</a
>. If you want to help out, please join us.
4658 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
4659 source code
</a
> is available via git on Alioth. It would also be
4660 great if you could help out with
4661 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
4662 it is an important piece of the puzzle to get ZFS working.
</p
>
4667 <title>What is the best multimedia player in Debian?
</title>
4668 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
4669 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
4670 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
4671 <description><p
><strong
>Where I set out to figure out which multimedia player in
4672 Debian claim support for most file formats.
</strong
></p
>
4674 <p
>A few years ago, I had a look at the media support for Browser
4675 plugins in Debian, to get an idea which plugins to include in Debian
4676 Edu. I created a script to extract the set of supported MIME types
4677 for each plugin, and used this to find out which multimedia browser
4678 plugin supported most file formats / media types.
4679 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
4680 result
</a
> can still be seen on the Debian wiki, even though it have
4681 not been updated for a while. But browser plugins are less relevant
4682 these days, so I thought it was time to look at standalone
4685 <p
>A few days ago I was tired of VLC not being listed as a viable
4686 player when I wanted to play videos from the Norwegian National
4687 Broadcasting Company, and decided to investigate why. The cause is a
4688 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
4689 desktop file
</a
>. In the process I wrote a script to compare the set
4690 of MIME types announced in the desktop file and the browser plugin,
4691 only to discover that there is quite a large difference between the
4692 two for VLC. This discovery made me dig up the script I used to
4693 compare browser plugins, and adjust it to compare desktop files
4694 instead, to try to figure out which multimedia player in Debian
4695 support most file formats.
</p
>
4697 <p
>The result can be seen on the Debian Wiki, as
4698 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
4699 table listing all MIME types supported by one of the packages included
4700 in the table
</a
>, with the package supporting most MIME types being
4701 listed first in the table.
</p
>
4703 </p
>The best multimedia player in Debian? It is totem, followed by
4704 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4705 kmplayer. Time for the other players to update their announced MIME
4711 <title>The Pyra - handheld computer with Debian preinstalled
</title>
4712 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
4713 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
4714 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
4715 <description>A friend of mine made me aware of
4716 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
4717 handheld computer which will be delivered with Debian preinstalled. I
4718 would love to get one of those for my birthday. :)
</p
>
4720 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4721 plugs and many others connectors, and include a full keyboard and a
5"
4722 LCD touch screen. The
6000mAh battery is claimed to provide a whole
4723 day of battery life time, but I have not seen any independent tests
4724 confirming this. The vendor is still collecting preorders, and the
4725 last I heard last night was that
22 more orders were needed before
4726 production started.
</p
>
4728 <p
>As far as I know, this is the first handheld preinstalled with
4729 Debian. Please let me know if you know of any others. Is it the
4730 first computer being sold with Debian preinstalled?
</p
>
4735 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
4736 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
4737 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
4738 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
4739 <description><p
>During this weekends
4740 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
4741 squashing party and developer gathering
</a
>, we decided to do our part
4742 to make sure there are good books about Debian available in Norwegian
4743 Bokmål, and got in touch with the people behind the
4744 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
4745 project
</a
> to get started. If you want to help out, please start
4747 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
4748 hosted weblate project page
</a
>, and get in touch using
4749 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
4750 translators mailing list
</a
>. Please also check out
4751 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
4752 contributors
</a
>.
</p
>
4754 <p
>The book is already available on paper in English, French and
4755 Japanese, and our goal is to get it available on paper in Norwegian
4756 Bokmål too. In addition to the paper edition, there are also EPUB and
4757 Mobi versions available. And there are incomplete translations
4758 available for many more languages.
</p
>
4763 <title>One in two hundred Debian users using ZFS on Linux?
</title>
4764 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
4765 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
4766 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
4767 <description><p
>Just for fun I had a look at the popcon number of ZFS related
4768 packages in Debian, and was quite surprised with what I found. I use
4769 ZFS myself at home, but did not really expect many others to do so.
4770 But I might be wrong.
</p
>
4772 <p
>According to
4773 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
4774 results for spl-linux
</a
>, there are
1019 Debian installations, or
4775 0.53% of the population, with the package installed. As far as I know
4776 the only use of the spl-linux package is as a support library for ZFS
4777 on Linux, so I use it here as proxy for measuring the number of ZFS
4778 installation on Linux in Debian. In the kFreeBSD variant of Debian
4779 the ZFS feature is already available, and there
4780 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
4781 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
4782 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
4784 <p
>But even though the Debian project leader Lucas Nussbaum
4785 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
4786 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
4787 cleared, the package is still not in Debian. The package is again in
4788 the NEW queue. Several uploads have been rejected so far because the
4789 debian/copyright file was incomplete or wrong, but there is no reason
4790 to give up. The current status can be seen on
4791 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4792 team status page
</a
>, and
4793 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
4794 source code
</a
> is available on Alioth.
</p
>
4796 <p
>As I want ZFS to be included in next version of Debian to make sure
4797 my home server can function in the future using only official Debian
4798 packages, and the current blocker is to get the debian/copyright file
4799 accepted by the FTP masters in Debian, I decided a while back to try
4800 to help out the team. This was the background for my blog post about
4801 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
4802 updating and checking debian/copyright semi-automatically
</a
>, and I
4803 used the techniques I explored there to try to find any errors in the
4804 copyright file. It is not very easy to check every one of the around
4805 2000 files in the source package, but I hope we this time got it
4806 right. If you want to help out, check out the git source and try to
4807 find missing entries in the debian/copyright file.
</p
>
4812 <title>Full battery stats collector is now available in Debian
</title>
4813 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
4814 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
4815 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
4816 <description><p
>Since this morning, the battery-stats package in Debian include an
4817 extended collector that will collect the complete battery history for
4818 later processing and graphing. The original collector store the
4819 battery level as percentage of last full level, while the new
4820 collector also record battery vendor, model, serial number, design
4821 full level, last full level and current battery level. This make it
4822 possible to predict the lifetime of the battery as well as visualise
4823 the energy flow when the battery is charging or discharging.
</p
>
4825 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
4826 in the version
0.5.1 package in unstable. Get the new battery level graph
4827 and lifetime prediction by running:
4829 <p
><pre
>
4830 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4831 </pre
></p
>
4833 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
4835 <p
>The flow in/out of the battery can be seen by running (no menu
4836 entry yet):
</p
>
4838 <p
><pre
>
4839 /usr/share/battery-stats/battery-stats-graph-flow
4840 </pre
></p
>
4842 <p
>I
'm not quite happy with the way the data is visualised, at least
4843 when there are few data points. The graphs look a bit better with a
4844 few years of data.
</p
>
4846 <p
>A while back one important feature I use in the battery stats
4847 collector broke in Debian. The scripts in
4848 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
4849 suspect it happened when Jessie started using systemd, but I do not
4850 know. The issue is reported as
4851 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
4852 pm-utils. I managed to work around it by adding an udev rule to call
4853 the collector script every time the power connector is connected and
4854 disconnected. With this fix in place it was finally time to make a
4855 new release of the package, and get it into Debian.
</p
>
4857 <p
>If you are interested in how your laptop battery is doing, please
4859 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4860 in Debian unstable, or rebuild it on Jessie to get it working on
4861 Debian stable. :) The upstream source is available from
4862 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4863 As always, patches are very welcome.
</p
>
4868 <title>Making battery measurements a little easier in Debian
</title>
4869 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
4870 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
4871 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
4872 <description><p
>Back in September, I blogged about
4873 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
4874 system I wrote to collect statistics about my laptop battery
</a
>, and
4875 how it showed the decay and death of this battery (now replaced). I
4876 created a simple deb package to handle the collection and graphing,
4877 but did not want to upload it to Debian as there were already
4878 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
4879 package in Debian
</a
> that should do the same thing, and I did not see
4880 a point of uploading a competing package when battery-stats could be
4881 fixed instead. I reported a few bugs about its non-function, and
4882 hoped someone would step in and fix it. But no-one did.
</p
>
4884 <p
>I got tired of waiting a few days ago, and took matters in my own
4885 hands. The end result is that I am now the new upstream developer of
4886 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
4887 battery-stats in Debian, and the package in Debian unstable is finally
4888 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
4889 information provided by the Linux kernel. If you install the
4890 battery-stats package from unstable now, you will be able to get a
4891 graph of the current battery fill level, to get some idea about the
4892 status of the battery. The source package build and work just fine in
4893 Debian testing and stable (and probably oldstable too, but I have not
4894 tested). The default graph you get for that system look like this:
</p
>
4896 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
03-
15-battery-stats-graph-example.png
" width=
"70%
" align=
"center
"></p
>
4898 <p
>My plans for the future is to merge my old scripts into the
4899 battery-stats package, as my old scripts collected a lot more details
4900 about the battery. The scripts are merged into the upstream
4901 battery-stats git repository already, but I am not convinced they work
4902 yet, as I changed a lot of paths along the way. Will have to test a
4903 bit more before I make a new release.
</p
>
4905 <p
>I will also consider changing the file format slightly, as I
4906 suspect the way I combine several values into one field might make it
4907 impossible to know the type of the value when using it for processing
4908 and graphing.
</p
>
4910 <p
>If you would like I would like to keep an close eye on your laptop
4911 battery, check out the battery-stats package in
4912 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
4914 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4915 I would love some help to improve the system further.
</p
>
4920 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
4921 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
4922 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
4923 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
4924 <description><p
>Making packages for Debian requires quite a lot of attention to
4925 details. And one of the details is the content of the
4926 debian/copyright file, which should list all relevant licenses used by
4927 the code in the package in question, preferably in
4928 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
4929 readable DEP5 format
</a
>.
</p
>
4931 <p
>For large packages with lots of contributors it is hard to write
4932 and update this file manually, and if you get some detail wrong, the
4933 package is normally rejected by the ftpmasters. So getting it right
4934 the first time around get the package into Debian faster, and save
4935 both you and the ftpmasters some work.. Today, while trying to figure
4936 out what was wrong with
4937 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
4938 zfsonlinux copyright file
</a
>, I decided to spend some time on
4939 figuring out the options for doing this job automatically, or at least
4940 semi-automatically.
</p
>
4942 <p
>Lucikly, there are at least two tools available for generating the
4943 file based on the code in the source package,
4944 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
4945 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
4946 not sure which one of them came first, but both seem to be able to
4947 create a sensible draft file. As far as I can tell, none of them can
4948 be trusted to get the result just right, so the content need to be
4949 polished a bit before the file is OK to upload. I found the debmake
4951 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
4952 blog posts from
2014</a
>.
4954 <p
>To generate using debmake, use the -cc option:
4956 <p
><pre
>
4957 debmake -cc
> debian/copyright
4958 </pre
></p
>
4960 <p
>Note there are some problems with python and non-ASCII names, so
4961 this might not be the best option.
</p
>
4963 <p
>The cme option is based on a config parsing library, and I found
4965 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
4966 blog post from
2015</a
>. To generate using cme, use the
'update
4967 dpkg-copyright
' option:
4969 <p
><pre
>
4970 cme update dpkg-copyright
4971 </pre
></p
>
4973 <p
>This will create or update debian/copyright. The cme tool seem to
4974 handle UTF-
8 names better than debmake.
</p
>
4976 <p
>When the copyright file is created, I would also like some help to
4977 check if the file is correct. For this I found two good options,
4978 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
4979 to focus on license types and file matching, and is able to detect
4980 ineffective blocks in the copyright file. The latter reports missing
4981 copyright holders and years, but was confused by inconsistent license
4982 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
4983 fix all issues reported by them before uploading. But I do not know
4984 if the tools and the ftpmasters agree on what is important to fix in a
4985 copyright file, so the package might still be rejected.
</p
>
4987 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
4988 will read through the source and try to find all copyright statements.
4989 It is not comparing the result to the content of debian/copyright, but
4990 can be useful when verifying the content of the copyright file.
</p
>
4992 <p
>Are you aware of better tools in Debian to create and update
4993 debian/copyright file. Please let me know, or blog about it on
4994 planet.debian.org.
</p
>
4996 <p
>As usual, if you use Bitcoin and want to show your support of my
4997 activities, please send Bitcoin donations to my address
4998 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5000 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
5001 on how to use licensecheck and cdbs to create a draft copyright file
5003 <p
><pre
>
5004 licensecheck --copyright -r `find * -type f` | \
5005 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
5006 </pre
></p
>
5008 <p
>He mentioned that he normally check the generated file into the
5009 version control system to make it easier to discover license and
5010 copyright changes in the upstream source. I will try to do the same
5011 with my packages in the future.
</p
>
5013 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
5014 against using -quiet for new users, so I removed it from the proposed
5015 command line.
</p
>
5020 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
5021 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
5022 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
5023 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
5024 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
5025 is taking shape in Debian, and one provided feature is a very
5026 convenient way to tell you which package to install to make a given
5027 firmware file available when the kernel is looking for it. This can
5028 be done using apt-file too, but that is for someone else to blog
5031 <p
>Here is a small recipe to find the package with a given firmware
5032 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
5033 picked from the set of firmware announced using appstream in Debian
5034 unstable. In general you would be looking for the firmware requested
5035 by the kernel during kernel module loading. To find the package
5036 providing the example file, do like this:
</p
>
5038 <blockquote
><pre
>
5039 % apt install appstream
5043 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
5044 awk
'/Package:/ {print $
2}
'
5047 </pre
></blockquote
>
5049 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
5050 appstream wiki
</a
> page to learn how to embed the package metadata in
5051 a way appstream can use.
</p
>
5053 <p
>This same approach can be used to find any package supporting a
5054 given MIME type. This is very useful when you get a file you do not
5055 know how to handle. First find the mime type using
<tt
>file
5056 --mime-type
</tt
>, and next look up the package providing support for
5057 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
5058 and you can find all packages handling this type like this:
</p
>
5060 <blockquote
><pre
>
5061 % apt install appstream
5065 % appstreamcli what-provides mimetype image/svg+xml | \
5066 awk
'/Package:/ {print $
2}
'
5088 </pre
></blockquote
>
5090 <p
>I believe the MIME types are fetched from the desktop file for
5091 packages providing appstream metadata.
</p
>
5096 <title>Creepy, visualise geotagged social media information - nice free software
</title>
5097 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
5098 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
5099 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
5100 <description><p
>Most people seem not to realise that every time they walk around
5101 with the computerised radio beacon known as a mobile phone their
5102 position is tracked by the phone company and often stored for a long
5103 time (like every time a SMS is received or sent). And if their
5104 computerised radio beacon is capable of running programs (often called
5105 mobile apps) downloaded from the Internet, these programs are often
5106 also capable of tracking their location (if the app requested access
5107 during installation). And when these programs send out information to
5108 central collection points, the location is often included, unless
5109 extra care is taken to not send the location. The provided
5110 information is used by several entities, for good and bad (what is
5111 good and bad, depend on your point of view). What is certain, is that
5112 the private sphere and the right to free movement is challenged and
5113 perhaps even eradicated for those announcing their location this way,
5114 when they share their whereabouts with private and public
5117 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
5119 <p
>The phone company logs provide a register of locations to check out
5120 when one want to figure out what the tracked person was doing. It is
5121 unavailable for most of us, but provided to selected government
5122 officials, company staff, those illegally buying information from
5123 unfaithful servants and crackers stealing the information. But the
5124 public information can be collected and analysed, and a free software
5125 tool to do so is called
5126 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
5127 discovered it when I read
5128 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
5129 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
5130 November
2014, and decided to check if it was available in Debian.
5131 The python program was in Debian, but
5132 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
5133 Debian
</a
> was completely broken and practically unmaintained. I
5134 uploaded a new version which did not work quite right, but did not
5135 have time to fix it then. This Christmas I decided to finally try to
5136 get Creepy operational in Debian. Now a fixed version is available in
5137 Debian unstable and testing, and almost all Debian specific patches
5139 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
5141 <p
>The Creepy program visualises geolocation information fetched from
5142 Twitter, Instagram, Flickr and Google+, and allow one to get a
5143 complete picture of every social media message posted recently in a
5144 given area, or track the movement of a given individual across all
5145 these services. Earlier it was possible to use the search API of at
5146 least some of these services without identifying oneself, but these
5147 days it is impossible. This mean that to use Creepy, you need to
5148 configure it to log in as yourself on these services, and provide
5149 information to them about your search interests. This should be taken
5150 into account when using Creepy, as it will also share information
5151 about yourself with the services.
</p
>
5153 <p
>The picture above show the twitter messages sent from (or at least
5154 geotagged with a position from) the city centre of Oslo, the capital
5155 of Norway. One useful way to use Creepy is to first look at
5156 information tagged with an area of interest, and next look at all the
5157 information provided by one or more individuals who was in the area.
5158 I tested it by checking out which celebrity provide their location in
5159 twitter messages by checkout out who sent twitter messages near a
5160 Norwegian TV station, and next could track their position over time,
5161 making it possible to locate their home and work place, among other
5162 things. A similar technique have been
5163 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
5164 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
5165 tool to discover lying governments, and a useful tool to help people
5166 understand the value of the private information they provide to the
5169 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
5170 it depend on several python modules currently missing in Jessie (at
5171 least python-instagram, python-flickrapi and
5172 python-requests-toolbelt).
</p
>
5174 <p
>(I have uploaded
5175 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
5176 screenshots.debian.net
</a
> and licensed it under the same terms as the
5177 Creepy program in Debian.)
</p
>
5182 <title>Always download Debian packages using Tor - the simple recipe
</title>
5183 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
5184 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
5185 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
5186 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
5187 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
5188 that those listening on the Internet lines would have good reason to
5189 believe a computer have a given security hole
</a
> if it download a
5190 security fix from a Debian mirror. This is a good reason to always
5191 use encrypted connections to the Debian mirror, to make sure those
5192 listening do not know which IP address to attack. In August, Richard
5193 Hartmann observed that encryption was not enough, when it was possible
5194 to interfere download size to security patches or the fact that
5195 download took place shortly after a security fix was released, and
5196 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
5197 to always use Tor to download packages from the Debian mirror
</a
>. He
5198 was not the first to propose this, as the
5199 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
5200 package by Tim Retout already existed to make it easy to convince apt
5201 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
5202 aware of that package when I read the blog post from Richard.
</p
>
5204 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
5205 sysadmins, and he set up a Tor hidden service on one of the central
5206 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
5207 it possible to download packages directly between two tor nodes,
5208 making sure the network traffic always were encrypted.
</p
>
5210 <p
>Here is a short recipe for enabling this on your machine, by
5211 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
5212 urls with tor+http and tor+https, and using the hidden service instead
5213 of the official Debian mirror site. I recommend installing
5214 <tt
>etckeeper
</tt
> before you start to have a history of the changes
5215 done in /etc/.
</p
>
5217 <blockquote
><pre
>
5218 apt install apt-transport-tor
5219 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
5220 sed -i
's% http% tor+http%
' /etc/apt/sources.list
5221 </pre
></blockquote
>
5223 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
5224 the sed commands for these too. The sed command is assuming your are
5225 using the ftp.debian.org Debian mirror. Adjust the command (or just
5226 edit the file manually) to match your mirror.
</p
>
5228 <p
>This work in Debian Jessie and later. Note that tools like
5229 <tt
>apt-file
</tt
> only recently started using the apt transport
5230 system, and do not work with these tor+http URLs. For
5231 <tt
>apt-file
</tt
> you need the version currently in experimental,
5232 which need a recent apt version currently only in unstable. So if you
5233 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
5235 <p
>Another advantage from this change is that your machine will start
5236 using Tor regularly and at fairly random intervals (every time you
5237 update the package lists or upgrade or install a new package), thus
5238 masking other Tor traffic done from the same machine. Using Tor will
5239 become normal for the machine in question.
</p
>
5241 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
5242 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
5243 enabled. It would be great if it was the default on any Debian
5249 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
5250 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
5251 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
5252 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
5253 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
5254 call the car license plate numbers in those days. I would write the
5255 numbers down in my little book and compare notes with the other kids
5256 to see how many region codes we had seen and if we had seen some
5257 exotic or special region codes and numbers. It was a fun game to pass
5258 time, as we kids have plenty of it.
</p
>
5260 <p
>A few days I came across
5261 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
5262 project
</a
>, a free software project to automatically discover and
5263 report license plates in images and video streams, and provide the
5264 "car numbers
" in a machine readable format. I
've been looking for
5265 such system for a while now, because I believe it is a bad idea that the
5266 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
5267 number plate recognition
</a
> tool only is available in the hands of
5268 the powerful, and want it to be available also for the powerless to
5269 even the score when it comes to surveillance and sousveillance. I
5270 discovered the developer
5271 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
5272 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
5273 help him get it into shape to get the package uploaded into the Debian
5276 <p
>Today we finally managed to get the package into shape and uploaded
5277 it into Debian, where it currently
5278 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
5279 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
5281 <p
>I guess you are wondering why on earth such tool would be useful
5282 for the common folks, ie those not running a large government
5283 surveillance system? Well, I plan to put it in a computer on my bike
5284 and in my car, tracking the cars nearby and allowing me to be notified
5285 when number plates on my watch list are discovered. Another use case
5286 was suggested by a friend of mine, who wanted to set it up at his home
5287 to open the car port automatically when it discovered the plate on his
5288 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
5289 capable of placing his license plate number of a piece of cardboard to
5290 open his car port, men replied that it was always unlocked anyway. I
5291 guess for such use case it make sense. I am sure there are other use
5292 cases too, for those with imagination and a vision.
</p
>
5294 <p
>If you want to build your own version of the Debian package, check
5295 out the upstream git source and symlink ./distros/debian to ./debian/
5296 before running
"debuild
" to build the source. Or wait a bit until the
5297 package show up in unstable.
</p
>
5302 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
5303 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
5304 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
5305 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
5306 <description><p
>Around three years ago, I created
5307 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
5308 system
</a
> to get a more practical solution in Debian for handing
5309 hardware related packages. A GUI system in the isenkram package will
5310 present a pop-up dialog when some hardware dongle supported by
5311 relevant packages in Debian is inserted into the machine. The same
5312 lookup mechanism to detect packages is available as command line
5313 tools in the isenkram-cli package. In addition to mapping hardware,
5314 it will also map kernel firmware files to packages and make it easy to
5315 install needed firmware packages automatically. The key for this
5316 system to work is a good way to map hardware to packages, in other
5317 words, allow packages to announce what hardware they will work
5320 <p
>I started by providing data files in the isenkram source, and
5321 adding code to download the latest version of these data files at run
5322 time, to ensure every user had the most up to date mapping available.
5323 I also added support for storing the mapping in the Packages file in
5324 the apt repositories, but did not push this approach because while I
5325 was trying to figure out how to best store hardware/package mappings,
5326 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
5327 appstream system
</a
> was announced. I got in touch and suggested to
5328 add the hardware mapping into that data set to be able to use
5329 appstream as a data source, and this was accepted at least for the
5330 Debian version of appstream.
</p
>
5332 <p
>A few days ago using appstream in Debian for this became possible,
5333 and today I uploaded a new version
0.20 of isenkram adding support for
5334 appstream as a data source for mapping hardware to packages. The only
5335 package so far using appstream to announce its hardware support is my
5336 pymissile package. I got help from Matthias Klumpp with figuring out
5337 how do add the required
5338 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
5339 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
5340 this content:
</p
>
5342 <blockquote
><pre
>
5343 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
5344 &lt;component
&gt;
5345 &lt;id
&gt;pymissile
&lt;/id
&gt;
5346 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
5347 &lt;name
&gt;pymissile
&lt;/name
&gt;
5348 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
5349 &lt;description
&gt;
5351 Pymissile provides a curses interface to control an original
5352 Marks and Spencer / Striker USB Missile Launcher, as well as a
5353 motion control script to allow a webcamera to control the
5356 &lt;/description
&gt;
5357 &lt;provides
&gt;
5358 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
5359 &lt;/provides
&gt;
5360 &lt;/component
&gt;
5361 </pre
></blockquote
>
5363 <p
>The key for isenkram is the component/provides/modalias value,
5364 which is a glob style match rule for hardware specific strings
5365 (modalias strings) provided by the Linux kernel. In this case, it
5366 will map to all USB devices with vendor code
1130 and product code
5369 <p
>Note, it is important that the license of all the metadata files
5370 are compatible to have permissions to aggregate them into archive wide
5371 appstream files. Matthias suggested to use MIT or BSD licenses for
5372 these files. A challenge is figuring out a good id for the data, as
5373 it is supposed to be globally unique and shared across distributions
5374 (in other words, best to coordinate with upstream what to use). But
5375 it can be changed later or, so we went with the package name as
5376 upstream for this project is dormant.
</p
>
5378 <p
>To get the metadata file installed in the correct location for the
5379 mirror update scripts to pick it up and include its content the
5380 appstream data source, the file must be installed in the binary
5381 package under /usr/share/appdata/. I did this by adding the following
5382 line to debian/pymissile.install:
</p
>
5384 <blockquote
><pre
>
5385 debian/pymissile.metainfo.xml usr/share/appdata
5386 </pre
></blockquote
>
5388 <p
>With that in place, the command line tool isenkram-lookup will list
5389 all packages useful on the current computer automatically, and the GUI
5390 pop-up handler will propose to install the package not already
5391 installed if a hardware dongle is inserted into the machine in
5394 <p
>Details of the modalias field in appstream is available from the
5395 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
5397 <p
>To locate the modalias values of all hardware present in a machine,
5398 try running this command on the command line:
</p
>
5400 <blockquote
><pre
>
5401 cat $(find /sys/devices/|grep modalias)
5402 </pre
></blockquote
>
5404 <p
>To learn more about the isenkram system, please check out
5405 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
5406 blog posts tagged isenkram
</a
>.
</p
>
5411 <title>The GNU General Public License is not magic pixie dust
</title>
5412 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
5413 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
5414 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
5415 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
5416 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
5417 GPL is not magic pixie dust
</a
>" explain the importance of making sure
5418 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
5419 I quote the blog post from Paul in full here with his permission:
<p
>
5423 <p
><a href=
"https://sfconservancy.org/supporter/
"><img src=
"https://sfconservancy.org/img/supporter-badge.png
" width=
"194" height=
"90" alt=
"Become a Software Freedom Conservancy Supporter!
" align=
"right
" border=
"0" /
></a
></p
>
5426 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
5428 The first step is to choose a
5429 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
5432 The next step is, when someone fails to follow that copyleft license,
5433 <b
>it must be enforced
</b
><br/
>
5435 and its a simple fact of our modern society that such type of
5438 is incredibly expensive to do and incredibly difficult to do.
5441 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
5442 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
5443 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
5444 0x57</a
></small
></p
>
5446 <p
>As the Debian Website
5447 <a href=
"https://bugs.debian.org/
794116">used
</a
>
5448 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
5449 imply, public domain and permissively licensed software can lead to
5450 the production of more proprietary software as people discover useful
5451 software, extend it and or incorporate it into their hardware or
5452 software products. Copyleft licenses such as the GNU GPL were created
5453 to close off this avenue to the production of proprietary software but
5454 such licenses are not enough. With the ongoing adoption of Free
5455 Software by individuals and groups, inevitably the community
's
5456 expectations of license compliance are violated, usually out of
5457 ignorance of the way Free Software works, but not always. As Karen
5458 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
5459 Freedom
">FaiF
</a
>
5460 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
5461 copyleft is nothing if no-one is willing and able to stand up in court
5462 to protect it. The reality of today
's world is that legal
5463 representation is expensive, difficult and time consuming. With
5464 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
5465 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
5466 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
5467 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
5468 of the Linux project, Debian and other groups against GPL violations.
5469 In March the SFC supported a
5470 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
5471 by Christoph Hellwig
</a
> against VMware for refusing to
5472 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
5473 with the GPL
</a
> in relation to their use of parts of the Linux
5474 kernel. Since then two of their sponsors pulled corporate funding and
5476 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
5477 or cancelled their talks
</a
>. As a result they have decided to rely
5478 less on corporate funding and more on the broad community of
5479 individuals who support Free Software and copyleft. So the SFC has
5480 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
5481 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
5482 a community of folks who stand up for copyleft and the GPL by
5483 supporting their work on promoting and supporting copyleft and Free
5486 <p
>If you support Free Software,
5487 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
5488 what the SFC do, agree with their
5489 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
5490 principles
</a
>, are happy about their
5491 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
5492 work on a project that is an SFC
5493 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
5494 just want to stand up for copyleft, please join
5495 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
5496 Allan Webber
</a
>,
5497 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
5499 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
5500 Bacon
</a
>, myself and
5501 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
5503 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
5504 next week your donation will be
5505 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
5506 by an anonymous donor. Please also consider asking your employer to
5507 match your donation or become a sponsor of SFC. Don
't forget to
5508 spread the word about your support for SFC via email, your blog and or
5509 social media accounts.
</p
>
5513 <p
>I agree with Paul on this topic and just signed up as a Supporter
5514 of Software Freedom Conservancy myself. Perhaps you should be a
5515 supporter too?
</p
>
5520 <title>PGP key transition statement for key EE4E02F9
</title>
5521 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
5522 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
5523 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
5524 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
5525 set it up properly. I wanted to generate it offline and have it
5526 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
5527 smart card
</a
> for daily use, and learning how to do it and finding
5528 time to sit down with an offline machine almost took forever. But
5529 finally I
've been able to complete the process, and have now moved
5530 from my old GPG key to a new GPG key. See
5531 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
5532 full transition statement, signed with both my old and new key
</a
> for
5533 the details. This is my new key:
</p
>
5536 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
5537 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
5538 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
5539 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
5540 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
5541 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
5542 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
5545 <p
>The key can be downloaded from the OpenPGP key servers, signed by
5546 my old key.
</p
>
5548 <p
>If you signed my old key
5549 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
5550 I
'd very much appreciate a signature on my new key, details and
5551 instructions in the transition statement. I m happy to reciprocate if
5552 you have a similarly signed transition statement to present.
</p
>
5557 <title>The life and death of a laptop battery
</title>
5558 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
5559 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
5560 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
5561 <description><p
>When I get a new laptop, the battery life time at the start is OK.
5562 But this do not last. The last few laptops gave me a feeling that
5563 within a year, the life time is just a fraction of what it used to be,
5564 and it slowly become painful to use the laptop without power connected
5565 all the time. Because of this, when I got a new Thinkpad X230 laptop
5566 about two years ago, I decided to monitor its battery state to have
5567 more hard facts when the battery started to fail.
</p
>
5569 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
5571 <p
>First I tried to find a sensible Debian package to record the
5572 battery status, assuming that this must be a problem already handled
5573 by someone else. I found
5574 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
5575 which collects statistics from the battery, but it was completely
5576 broken. I sent a few suggestions to the maintainer, but decided to
5577 write my own collector as a shell script while I waited for feedback
5579 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
5580 blog post about the battery development on a MacBook Air
</a
> I also
5582 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
5583 available in Debian.
</p
>
5585 <p
>I started my collector
2013-
07-
15, and it has been collecting
5586 battery stats ever since. Now my
5587 /var/log/hjemmenett-battery-status.log file contain around
115,
000
5588 measurements, from the time the battery was working great until now,
5589 when it is unable to charge above
7% of original capacity. My
5590 collector shell script is quite simple and look like this:
</p
>
5595 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
5597 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
5598 logfile=/var/log/hjemmenett-battery-status.log
5600 files=
"manufacturer model_name technology serial_number \
5601 energy_full energy_full_design energy_now cycle_count status
"
5603 if [ ! -e
"$logfile
" ] ; then
5605 printf
"timestamp,
"
5607 printf
"%s,
" $f
5610 )
> "$logfile
"
5614 # Print complete message in one echo call, to avoid race condition
5615 # when several log processes run in parallel.
5616 msg=$(printf
"%s,
" $(date +%s); \
5617 for f in $files; do \
5618 printf
"%s,
" $(cat $f); \
5620 echo
"$msg
"
5623 cd /sys/class/power_supply
5626 (cd $bat
&& log_battery
>> "$logfile
")
5630 <p
>The script is called when the power management system detect a
5631 change in the power status (power plug in or out), and when going into
5632 and out of hibernation and suspend. In addition, it collect a value
5633 every
10 minutes. This make it possible for me know when the battery
5634 is discharging, charging and how the maximum charge change over time.
5635 The code for the Debian package
5636 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
5637 available on github
</a
>.
</p
>
5639 <p
>The collected log file look like this:
</p
>
5642 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5643 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
5645 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5646 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5649 <p
>I wrote a small script to create a graph of the charge development
5650 over time. This graph depicted above show the slow death of my laptop
5653 <p
>But why is this happening? Why are my laptop batteries always
5654 dying in a year or two, while the batteries of space probes and
5655 satellites keep working year after year. If we are to believe
5656 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
5657 University
</a
>, the cause is me charging the battery whenever I have a
5658 chance, and the fix is to not charge the Lithium-ion batteries to
100%
5659 all the time, but to stay below
90% of full charge most of the time.
5660 I
've been told that the Tesla electric cars
5661 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
5662 the charge of their batteries to
80%
</a
>, with the option to charge to
5663 100% when preparing for a longer trip (not that I would want a car
5664 like Tesla where rights to privacy is abandoned, but that is another
5665 story), which I guess is the option we should have for laptops on
5666 Linux too.
</p
>
5668 <p
>Is there a good and generic way with Linux to tell the battery to
5669 stop charging at
80%, unless requested to charge to
100% once in
5670 preparation for a longer trip? I found
5671 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
5672 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5673 80%
</a
>, but could not get it to work (kernel module refused to
5676 <p
>I wonder why the battery capacity was reported to be more than
100%
5677 at the start. I also wonder why the
"full capacity
" increases some
5678 times, and if it is possible to repeat the process to get the battery
5679 back to design capacity. And I wonder if the discharge and charge
5680 speed change over time, or if this stay the same. I did not yet try
5681 to write a tool to calculate the derivative values of the battery
5682 level, but suspect some interesting insights might be learned from
5685 <p
>Update
2015-
09-
24: I got a tip to install the packages
5686 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5687 packages instead of the tp-smapi-dkms package I had tried to use
5688 initially, and use
'tlp setcharge
40 80' to change when charging start
5689 and stop. I
've done so now, but expect my existing battery is toast
5690 and need to be replaced. The proposal is unfortunately Thinkpad
5696 <title>New laptop - some more clues and ideas based on feedback
</title>
5697 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
5698 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
5699 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
5700 <description><p
>Several people contacted me after my previous blog post about my
5701 need for a new laptop, and provided very useful feedback. I wish to
5702 thank every one of these. Several pointed me to the possibility of
5703 fixing my X230, and I am already in the process of getting Lenovo to
5704 do so thanks to the on site, next day support contract covering the
5705 machine. But the battery is almost useless (I expect to replace it
5706 with a non-official battery) and I do not expect the machine to live
5707 for many more years, so it is time to plan its replacement. If I did
5708 not have a support contract, it was suggested to find replacement parts
5709 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
5710 might present a language barrier as I do not understand French.
</p
>
5712 <p
>One tip I got was to use the
5713 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
5714 compare laptop models. It seem to have more models available than
5715 prisjakt.no. Another tip I got from someone I know have similar
5716 keyboard preferences was that the HP EliteBook
840 keyboard is not
5717 very good, and this matches my experience with earlier EliteBook
5718 keyboards I tested. Because of this, I will not consider it any further.
5720 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
5721 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5722 (which is missing from the X240), and is working fairly well with
5723 Debian Sid/Unstable according to
5724 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
5725 got on the keyboard quality are not consistent. Some say the keyboard
5726 is good, others say it is ok, while others say it is not very good.
5727 Those with experience from X41 and and X60 agree that the X250
5728 keyboard is not as good as those trusty old laptops, and suggest I
5729 keep and fix my X230 instead of upgrading, or get a used X230 to
5730 replace it. I
'm also told that the X250 lack leds for caps lock, disk
5731 activity and battery status, which is very convenient on my X230. I
'm
5732 also told that the CPU fan is running very often, making it a bit
5733 noisy. In any case, the X250 do not work out of the box with Debian
5734 Stable/Jessie, one of my requirements.
</p
>
5736 <p
>I have also gotten a few vendor proposals, one was
5737 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
5738 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
5739 The latter look very attractive to me.
</p
>
5741 <p
>Again, thank you all for the very useful feedback. It help a lot
5742 as I keep looking for a replacement.
</p
>
5744 <p
>Update
2015-
07-
06: I was recommended to check out the
5745 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
5747 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
5748 thinkpad X models
</a
>, and provide one year warranty.
</p
>
5753 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
5754 <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>
5755 <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>
5756 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
5757 <description><p
>My primary work horse laptop is failing, and will need a
5758 replacement soon. The left
5 cm of the screen on my Thinkpad X230
5759 started flickering yesterday, and I suspect the cause is a broken
5760 cable, as changing the angle of the screen some times get rid of the
5761 flickering.
</p
>
5763 <p
>My requirements have not really changed since I bought it, and is
5765 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
5766 described them in
2013</a
>. The last time I bought a laptop, I had
5768 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
5769 where I could select at least a few of the requirements (mouse pin,
5770 wifi, weight) and go through the rest manually. Three button mouse
5771 and a good keyboard is not available as an option, and all the three
5772 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
5773 G2) lack three mouse buttons). It is also unclear to me how good the
5774 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5775 the keyboard, even if the quality and robustness in the X series have
5776 deteriorated since X41.
</p
>
5778 <p
>I wonder how I can find a sensible laptop when none of the options
5779 seem sensible to me? Are there better services around to search the
5780 set of available laptops for features? Please send me an email if you
5781 have suggestions.
</p
>
5783 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
5784 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
5785 of endorsed hardware
</a
>, which is useful background information.
</p
>
5790 <title>How to stay with sysvinit in Debian Jessie
</title>
5791 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
5792 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
5793 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
5794 <description><p
>By now, it is well known that Debian Jessie will not be using
5795 sysvinit as its boot system by default. But how can one keep using
5796 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5798 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
5799 Schubert
</a
> and
5800 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
5803 <p
>If you already are using Wheezy and want to upgrade to Jessie and
5804 keep sysvinit as your boot system, create a file
5805 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
5806 you upgrade:
</p
>
5808 <p
><blockquote
><pre
>
5809 Package: systemd-sysv
5810 Pin: release o=Debian
5812 </pre
></blockquote
><p
>
5814 <p
>This file content will tell apt and aptitude to not consider
5815 installing systemd-sysv as part of any installation and upgrade
5816 solution when resolving dependencies, and thus tell it to avoid
5817 systemd as a default boot system. The end result should be that the
5818 upgraded system keep using sysvinit.
</p
>
5820 <p
>If you are installing Jessie for the first time, there is no way to
5821 get sysvinit installed by default (debootstrap used by
5822 debian-installer have no option for this), but one can tell the
5823 installer to switch to sysvinit before the first boot. Either by
5824 using a kernel argument to the installer, or by adding a line to the
5825 preseed file used. First, the kernel command line argument:
5827 <p
><blockquote
><pre
>
5828 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
5829 </pre
></blockquote
><p
>
5831 <p
>Next, the line to use in a preseed file:
</p
>
5833 <p
><blockquote
><pre
>
5834 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5835 </pre
></blockquote
><p
>
5837 <p
>One can of course also do this after the first boot by installing
5838 the sysvinit-core package.
</p
>
5840 <p
>I recommend only using sysvinit if you really need it, as the
5841 sysvinit boot sequence in Debian have several hardware specific bugs
5842 on Linux caused by the fact that it is unpredictable when hardware
5843 devices show up during boot. But on the other hand, the new default
5844 boot system still have a few rough edges I hope will be fixed before
5845 Jessie is released.
</p
>
5847 <p
>Update
2014-
11-
26: Inspired by
5848 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
5849 blog post by Torsten Glaser
</a
>, added --purge to the preseed
5855 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
5856 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
5857 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
5858 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
5859 <description><p
>The right to communicate with your friends and family in private,
5860 without anyone snooping, is a right every citicen have in a liberal
5861 democracy. But this right is under serious attack these days.
</p
>
5863 <p
>A while back it occurred to me that one way to make the dragnet
5864 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5865 the whisleblower Snowden) more expensive for Internet email,
5866 is to deliver all email using SMTP via Tor. Such SMTP option would be
5867 a nice addition to the FreedomBox project if we could send email
5868 between FreedomBox machines without leaking metadata about the emails
5869 to the people peeking on the wire. I
5870 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
5871 this on the FreedomBox project mailing list in October
</a
> and got a
5872 lot of useful feedback and suggestions. It also became obvious to me
5873 that this was not a novel idea, as the same idea was tested and
5874 documented by Johannes Berg as early as
2006, and both
5875 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
5876 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
5877 propose a similar method / protocol to pass emails between users.
</p
>
5879 <p
>To implement such system one need to set up a Tor hidden service
5880 providing the SMTP protocol on port
25, and use email addresses
5881 looking like username@hidden-service-name.onion. With such addresses
5882 the connections to port
25 on hidden-service-name.onion using Tor will
5883 go to the correct SMTP server. To do this, one need to configure the
5884 Tor daemon to provide the hidden service and the mail server to accept
5885 emails for this .onion domain. To learn more about Exim configuration
5886 in Debian and test the design provided by Johannes Berg in his FAQ, I
5887 set out yesterday to create a Debian package for making it trivial to
5888 set up such SMTP over Tor service based on Debian. Getting it to work
5889 were fairly easy, and
5890 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
5891 source code for the Debian package
</a
> is available from github. I
5892 plan to move it into Debian if further testing prove this to be a
5893 useful approach.
</p
>
5895 <p
>If you want to test this, set up a blank Debian machine without any
5896 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
5897 get rid of exim4). Install tor, clone the git repository mentioned
5898 above, build the deb and install it on the machine. Next, run
5899 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
5900 the instructions to get the service up and running. Restart tor and
5901 exim when it is done, and test mail delivery using swaks like
5904 <p
><blockquote
><pre
>
5905 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5906 --to fbx@dutlqrrmjhtfa3vp.onion
5907 </pre
></blockquote
></p
>
5909 <p
>This will test the SMTP delivery using tor. Replace the email
5910 address with your own address to test your server. :)
</p
>
5912 <p
>The setup procedure is still to complex, and I hope it can be made
5913 easier and more automatic. Especially the tor setup need more work.
5914 Also, the package include a tor-smtp tool written in C, but its task
5915 should probably be rewritten in some script language to make the deb
5916 architecture independent. It would probably also make the code easier
5917 to review. The tor-smtp tool currently need to listen on a socket for
5918 exim to talk to it and is started using xinetd. It would be better if
5919 no daemon and no socket is needed. I suspect it is possible to get
5920 exim to run a command line tool for delivery instead of talking to a
5921 socket, and hope to figure out how in a future version of this
5924 <p
>Until I wipe my test machine, I can be reached using the
5925 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
5926 SMTorP. :)
</p
>
5931 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
5932 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
5933 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
5934 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
5935 <description><p
>If you ever had to moderate a mailman list, like the ones on
5936 alioth.debian.org, you know the web interface is fairly slow to
5937 operate. First you visit one web page, enter the moderation password
5938 and get a new page shown with a list of all the messages to moderate
5939 and various options for each email address. This take a while for
5940 every list you moderate, and you need to do it regularly to do a good
5941 job as a list moderator. But there is a quick alternative,
5942 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
5943 listadmin program
</a
>. It allow you to check lists for new messages
5944 to moderate in a fraction of a second. Here is a test run on two
5945 lists I recently took over:
</p
>
5947 <p
><blockquote
><pre
>
5948 % time listadmin xiph
5949 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5950 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5956 </pre
></blockquote
></p
>
5958 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
5959 there are no message in the moderation queue. Every morning I
5960 currently moderate
68 mailman lists, and it normally take around two
5961 minutes. When I took over the two pkg-xiph lists above a few days
5962 ago, there were
400 emails waiting in the moderator queue. It took me
5963 less than
15 minutes to process them all using the listadmin
5966 <p
>If you install
5967 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
5968 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
5969 with content like this, the moderation task is a breeze:
</p
>
5971 <p
><blockquote
><pre
>
5972 username username@example.org
5975 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
5978 adminurl https://{domain}/mailman/admindb/{list}
5979 mailman-list@lists.example.com
5982 other-list@otherserver.example.org
5983 </pre
></blockquote
></p
>
5985 <p
>There are other options to set as well. Check the manual page to
5986 learn the details.
</p
>
5988 <p
>If you are forced to moderate lists on a mailman installation where
5989 the SSL certificate is self signed or not properly signed by a
5990 generally accepted signing authority, you can set a environment
5991 variable when calling listadmin to disable SSL verification:
</p
>
5993 <p
><blockquote
><pre
>
5994 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
5995 </pre
></blockquote
></p
>
5997 <p
>If you want to moderate a subset of the lists you take care of, you
5998 can provide an argument to the listadmin script like I do in the
5999 initial screen dump (the xiph argument). Using an argument, only
6000 lists matching the argument string will be processed. This make it
6001 quick to accept messages if you notice the moderation request in your
6004 <p
>Without the listadmin program, I would never be the moderator of
68
6005 mailing lists, as I simply do not have time to spend on that if the
6006 process was any slower. The listadmin program have saved me hours of
6007 time I could spend elsewhere over the years. It truly is nice free
6010 <p
>As usual, if you use Bitcoin and want to show your support of my
6011 activities, please send Bitcoin donations to my address
6012 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6014 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
6015 configuration example. Also, I
've been told that the
6016 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
6022 <title>Debian Jessie, PXE and automatic firmware installation
</title>
6023 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
6024 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
6025 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
6026 <description><p
>When PXE installing laptops with Debian, I often run into the
6027 problem that the WiFi card require some firmware to work properly.
6028 And it has been a pain to fix this using preseeding in Debian.
6029 Normally something more is needed. But thanks to
6030 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
6031 package
</a
> and its recent tasksel extension, it has now become easy
6032 to do this using simple preseeding.
</p
>
6034 <p
>The isenkram-cli package provide tasksel tasks which will install
6035 firmware for the hardware found in the machine (actually, requested by
6036 the kernel modules for the hardware). (It can also install user space
6037 programs supporting the hardware detected, but that is not the focus
6038 of this story.)
</p
>
6040 <p
>To get this working in the default installation, two preeseding
6041 values are needed. First, the isenkram-cli package must be installed
6042 into the target chroot (aka the hard drive) before tasksel is executed
6043 in the pkgsel step of the debian-installer system. This is done by
6044 preseeding the base-installer/includes debconf value to include the
6045 isenkram-cli package. The package name is next passed to debootstrap
6046 for installation. With the isenkram-cli package in place, tasksel
6047 will automatically use the isenkram tasks to detect hardware specific
6048 packages for the machine being installed and install them, because
6049 isenkram-cli contain tasksel tasks.
</p
>
6051 <p
>Second, one need to enable the non-free APT repository, because
6052 most firmware unfortunately is non-free. This is done by preseeding
6053 the apt-mirror-setup step. This is unfortunate, but for a lot of
6054 hardware it is the only option in Debian.
</p
>
6056 <p
>The end result is two lines needed in your preseeding file to get
6057 firmware installed automatically by the installer:
</p
>
6059 <p
><blockquote
><pre
>
6060 base-installer base-installer/includes string isenkram-cli
6061 apt-mirror-setup apt-setup/non-free boolean true
6062 </pre
></blockquote
></p
>
6064 <p
>The current version of isenkram-cli in testing/jessie will install
6065 both firmware and user space packages when using this method. It also
6066 do not work well, so use version
0.15 or later. Installing both
6067 firmware and user space packages might give you a bit more than you
6068 want, so I decided to split the tasksel task in two, one for firmware
6069 and one for user space programs. The firmware task is enabled by
6070 default, while the one for user space programs is not. This split is
6071 implemented in the package currently in unstable.
</p
>
6073 <p
>If you decide to give this a go, please let me know (via email) how
6074 this recipe work for you. :)
</p
>
6076 <p
>So, I bet you are wondering, how can this work. First and
6077 foremost, it work because tasksel is modular, and driven by whatever
6078 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
6079 isenkram-cli package place two files for tasksel to find. First there
6080 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
6082 <p
><blockquote
><pre
>
6083 Task: isenkram-packages
6085 Description: Hardware specific packages (autodetected by isenkram)
6086 Based on the detected hardware various hardware specific packages are
6088 Test-new-install: show show
6090 Packages: for-current-hardware
6092 Task: isenkram-firmware
6094 Description: Hardware specific firmware packages (autodetected by isenkram)
6095 Based on the detected hardware various hardware specific firmware
6096 packages are proposed.
6097 Test-new-install: mark show
6099 Packages: for-current-hardware-firmware
6100 </pre
></blockquote
></p
>
6102 <p
>The key parts are Test-new-install which indicate how the task
6103 should be handled and the Packages line referencing to a script in
6104 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
6105 list of packages to install. The for-current-hardware-firmware script
6106 look like this to list relevant firmware for the machine:
6108 <p
><blockquote
><pre
>
6111 PATH=/usr/sbin:$PATH
6113 isenkram-autoinstall-firmware -l
6114 </pre
></blockquote
></p
>
6116 <p
>With those two pieces in place, the firmware is installed by
6117 tasksel during the normal d-i run. :)
</p
>
6119 <p
>If you want to test what tasksel will install when isenkram-cli is
6120 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
6121 --new-install
</tt
> to get the list of packages that tasksel would
6124 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
6125 pilots in testing this feature, as isenkram is used there now to
6126 install firmware, replacing the earlier scripts.
</p
>
6131 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
6132 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
6133 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
6134 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
6135 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
6136 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
6137 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
6138 on a screen normally showing the bread types and prizes:
</p
>
6140 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
6142 <p
>If it had booted as it was supposed to, I would never had known
6143 about this hidden Linux installation. It is interesting what
6144 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
6149 <title>New lsdvd release version
0.17 is ready
</title>
6150 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
6151 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
6152 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
6153 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
6154 got a new set of developers a few weeks ago, after the original
6155 developer decided to step down and pass the project to fresh blood.
6156 This project is now maintained by Petter Reinholdtsen and Steve
6159 <p
>I just wrapped up
6160 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
6161 new lsdvd release
</a
>, available in git or from
6162 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
6163 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
6168 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
6169 <li
>Check for garbage in the program chains, which indicate that a track is
6170 non-existant, to work around additional copy protection
</li
>
6171 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
6172 <li
>Fix pallete display of first entry
</li
>
6173 <li
>Fix include orders
</li
>
6174 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
6175 <li
>Fix the chapter count
</li
>
6176 <li
>Make sure the array size and the array limit used when initialising
6177 the palette size is the same.
</li
>
6178 <li
>Fix array printing.
</li
>
6179 <li
>Correct subsecond calculations.
</li
>
6180 <li
>Add sector information to the output format.
</li
>
6181 <li
>Clean up code to be closer to ANSI C and compile without warnings
6182 with more GCC compiler warnings.
</li
>
6186 <p
>This change bring together patches for lsdvd in use in various
6187 Linux and Unix distributions, as well as patches submitted to the
6188 project the last nine years. Please check it out. :)
</p
>
6193 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
6194 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
6195 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
6196 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
6197 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
6198 project
</a
> provide a Linux solution for schools, including a
6199 powerful desktop with education software, a central server providing
6200 web pages, user database, user home directories, central login and PXE
6201 boot of both clients without disk and the installation to install Debian
6202 Edu on machines with disk (and a few other services perhaps to small
6203 to mention here). We in the Debian Edu team are currently working on
6204 the Jessie based version, trying to get everything in shape before the
6205 freeze, to avoid having to maintain our own package repository in the
6207 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
6208 status
</a
> can be seen on the Debian wiki, and there is still heaps of
6209 work left. Some fatal problems block testing, breaking the installer,
6210 but it is possible to work around these to get anyway. Here is a
6211 recipe on how to get the installation limping along.
</p
>
6213 <p
>First, download the test ISO via
6214 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
6215 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
6217 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
6218 The ISO build was broken on Tuesday, so we do not get a new ISO every
6219 12 hours or so, but thankfully the ISO we already got we are able to
6220 install with some tweaking.
</p
>
6222 <p
>When you get to the Debian Edu profile question, go to tty2
6223 (use Alt-Ctrl-F2), run
</p
>
6225 <p
><blockquote
><pre
>
6226 nano /usr/bin/edu-eatmydata-install
6227 </pre
></blockquote
></p
>
6229 <p
>and add
'exit
0' as the second line, disabling the eatmydata
6230 optimization. Return to the installation, select the profile you want
6231 and continue. Without this change, exim4-config will fail to install
6232 due to a known bug in eatmydata.
</p
>
6234 <p
>When you get the grub question at the end, answer /dev/sda (or if
6235 this do not work, figure out what your correct value would be. All my
6236 test machines need /dev/sda, so I have no advice if it do not fit
6237 your need.
</p
>
6239 <p
>If you installed a profile including a graphical desktop, log in as
6240 root after the initial boot from hard drive, and install the
6241 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
6242 or mate. If you want several desktop options, install more than one
6243 metapackage. Once this is done, reboot and you should have a working
6244 graphical login screen. This workaround should no longer be needed
6245 once the education-tasks package version
1.801 enter testing in two
6248 <p
>I believe the ISO build will start working on two days when the new
6249 tasksel package enter testing and Steve McIntyre get a chance to
6250 update the debian-cd git repository. The eatmydata, grub and desktop
6251 issues are already fixed in unstable and testing, and should show up
6252 on the ISO as soon as the ISO build start working again. Well the
6253 eatmydata optimization is really just disabled. The proper fix
6254 require an upload by the eatmydata maintainer applying the patch
6255 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
6256 The rest have proper fixes in unstable.
</p
>
6258 <p
>I hope this get you going with the installation testing, as we are
6259 quickly running out of time trying to get our Jessie based
6260 installation ready before the distribution freeze in a month.
</p
>
6265 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
6266 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
6267 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
6268 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
6269 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
6270 to handle my fairly large DVD collection. It is a nice command line
6271 tool to get details about a DVD, like title, tracks, track length,
6272 etc, in XML, Perl or human readable format. But lsdvd have not seen
6273 any new development since
2006 and had a few irritating bugs affecting
6274 its use with some DVDs. Upstream seemed to be dead, and in January I
6275 sent a small probe asking for a version control repository for the
6276 project, without any reply. But I use it regularly and would like to
6277 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
6278 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
6279 the project admin, and after getting a reply from him explaining that
6280 he was no longer interested in the project, I asked if I could take
6281 over. And yesterday, I became project admin.
</p
>
6283 <p
>I
've been in touch with a Gentoo developer and the Debian
6284 maintainer interested in joining forces to maintain the upstream
6285 project, and I hope we can get a new release out fairly quickly,
6286 collecting the patches spread around on the internet into on place.
6287 I
've added the relevant Debian patches to the freshly created git
6288 repository, and expect the Gentoo patches to make it too. If you got
6289 a DVD collection and care about command line tools, check out
6290 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
6291 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
6292 list
</a
>. :)
</p
>
6297 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
6298 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
6299 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
6300 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
6301 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
6302 a lot quicker. When we install more than
2000 packages in
6303 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
6304 tasksel in the installer, unpacking the binary packages take forever.
6305 A part of the slow I/O issue was discussed in
6306 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
6307 much file system sync-ing done by dpkg, which is the package
6308 responsible for unpacking the binary packages. Other parts (like code
6309 executed by postinst scripts) might also sync to disk during
6310 installation. All this sync-ing to disk do not really make sense to
6311 me. If the machine crash half-way through, I start over, I do not try
6312 to salvage the half installed system. So the failure sync-ing is
6313 supposed to protect against, hardware or system crash, is not really
6314 relevant while the installer is running.
</p
>
6316 <p
>A few days ago, I thought of a way to get rid of all the file
6317 system sync()-ing in a fairly non-intrusive way, without the need to
6318 change the code in several packages. The idea is not new, but I have
6319 not heard anyone propose the approach using dpkg-divert before. It
6320 depend on the small and clever package
6321 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
6322 uses LD_PRELOAD to replace the system functions for syncing data to
6323 disk with functions doing nothing, thus allowing programs to live
6324 dangerous while speeding up disk I/O significantly. Instead of
6325 modifying the implementation of dpkg, apt and tasksel (which are the
6326 packages responsible for selecting, fetching and installing packages),
6327 it occurred to me that we could just divert the programs away, replace
6328 them with a simple shell wrapper calling
6329 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
6330 Two days ago I decided to test the idea, and wrapped up a simple
6331 implementation for the Debian Edu udeb.
</p
>
6333 <p
>The effect was stunning. In my first test it reduced the running
6334 time of the pkgsel step (installing tasks) from
64 to less than
44
6335 minutes (
20 minutes shaved off the installation) on an old Dell
6336 Latitude D505 machine. I am not quite sure what the optimised time
6337 would have been, as I messed up the testing a bit, causing the debconf
6338 priority to get low enough for two questions to pop up during
6339 installation. As soon as I saw the questions I moved the installation
6340 along, but do not know how long the question were holding up the
6341 installation. I did some more measurements using Debian Edu Jessie,
6342 and got these results. The time measured is the time stamp in
6343 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
6344 "pkgsel: finishing up
" lines, if you want to do the same measurement
6345 yourself. In Debian Edu, the tasksel dialog do not show up, and the
6346 timing thus do not depend on how quickly the user handle the tasksel
6349 <p
><table
>
6352 <th
>Machine/setup
</th
>
6353 <th
>Original tasksel
</th
>
6354 <th
>Optimised tasksel
</th
>
6355 <th
>Reduction
</th
>
6359 <td
>Latitude D505 Main+LTSP LXDE
</td
>
6360 <td
>64 min (
07:
46-
08:
50)
</td
>
6361 <td
><44 min (
11:
27-
12:
11)
</td
>
6362 <td
>>20 min
18%
</td
>
6366 <td
>Latitude D505 Roaming LXDE
</td
>
6367 <td
>57 min (
08:
48-
09:
45)
</td
>
6368 <td
>34 min (
07:
43-
08:
17)
</td
>
6369 <td
>23 min
40%
</td
>
6373 <td
>Latitude D505 Minimal
</td
>
6374 <td
>22 min (
10:
37-
10:
59)
</td
>
6375 <td
>11 min (
11:
16-
11:
27)
</td
>
6376 <td
>11 min
50%
</td
>
6380 <td
>Thinkpad X200 Minimal
</td
>
6381 <td
>6 min (
08:
19-
08:
25)
</td
>
6382 <td
>4 min (
08:
04-
08:
08)
</td
>
6383 <td
>2 min
33%
</td
>
6387 <td
>Thinkpad X200 Roaming KDE
</td
>
6388 <td
>19 min (
09:
21-
09:
40)
</td
>
6389 <td
>15 min (
10:
25-
10:
40)
</td
>
6390 <td
>4 min
21%
</td
>
6393 </table
></p
>
6395 <p
>The test is done using a netinst ISO on a USB stick, so some of the
6396 time is spent downloading packages. The connection to the Internet
6397 was
100Mbit/s during testing, so downloading should not be a
6398 significant factor in the measurement. Download typically took a few
6399 seconds to a few minutes, depending on the amount of packages being
6400 installed.
</p
>
6402 <p
>The speedup is implemented by using two hooks in
6403 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
6404 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
6405 finish-install.d hook to remove the divert at the end of the
6406 installation. I picked the pre-pkgsel.d hook instead of the
6407 post-base-installer.d hook because I test using an ISO without the
6408 eatmydata package included, and the post-base-installer.d hook in
6409 Debian Edu can only operate on packages included in the ISO. The
6410 negative effect of this is that I am unable to activate this
6411 optimization for the kernel installation step in d-i. If the code is
6412 moved to the post-base-installer.d hook, the speedup would be larger
6413 for the entire installation.
</p
>
6415 <p
>I
've implemented this in the
6416 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
6417 git repository, and plan to provide the optimization as part of the
6418 Debian Edu installation. If you want to test this yourself, you can
6419 create two files in the installer (or in an udeb). One shell script
6420 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
6422 <p
><blockquote
><pre
>
6425 . /usr/share/debconf/confmodule
6427 logger -t my-pkgsel
"info: $*
"
6430 logger -t my-pkgsel
"error: $*
"
6432 override_install() {
6433 apt-install eatmydata || true
6434 if [ -x /target/usr/bin/eatmydata ] ; then
6435 for bin in dpkg apt-get aptitude tasksel ; do
6437 # Test that the file exist and have not been diverted already.
6438 if [ -f /target$file ] ; then
6439 info
"diverting $file using eatmydata
"
6440 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
6441 > /target$file.edu
6442 chmod
755 /target$file.edu
6443 in-target dpkg-divert --package debian-edu-config \
6444 --rename --quiet --add $file
6445 ln -sf ./$bin.edu /target$file
6447 error
"unable to divert $file, as it is missing.
"
6451 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
6456 </pre
></blockquote
></p
>
6458 <p
>To clean up, another shell script should go into
6459 /usr/lib/finish-install.d/ with code like this:
6461 <p
><blockquote
><pre
>
6463 . /usr/share/debconf/confmodule
6465 logger -t my-finish-install
"error: $@
"
6467 remove_install_override() {
6468 for bin in dpkg apt-get aptitude tasksel ; do
6470 if [ -x /target$file.edu ] ; then
6472 in-target dpkg-divert --package debian-edu-config \
6473 --rename --quiet --remove $file
6476 error
"Missing divert for $file.
"
6479 sync # Flush file buffers before continuing
6482 remove_install_override
6483 </pre
></blockquote
></p
>
6485 <p
>In Debian Edu, I placed both code fragments in a separate script
6486 edu-eatmydata-install and call it from the pre-pkgsel.d and
6487 finish-install.d scripts.
</p
>
6489 <p
>By now you might ask if this change should get into the normal
6490 Debian installer too? I suspect it should, but am not sure the
6491 current debian-installer coordinators find it useful enough. It also
6492 depend on the side effects of the change. I
'm not aware of any, but I
6493 guess we will see if the change is safe after some more testing.
6494 Perhaps there is some package in Debian depending on sync() and
6495 fsync() having effect? Perhaps it should go into its own udeb, to
6496 allow those of us wanting to enable it to do so without affecting
6499 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
6500 will break installation of all programs using gnutls because of
6501 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
6502 eatmydata package in Debian will solve it.
</p
>
6504 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
6505 the optimization work again. And I have discovered that the
6506 dpkg-divert trick is not really needed and implemented a slightly
6507 simpler approach as part of the debian-edu-install package. See
6508 tools/edu-eatmydata-install in the source package.
</p
>
6510 <p
>Update
2014-
11-
11: Unfortunately, a new
6511 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
6512 triggering on i386 made it into testing, and broke this installation
6513 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
6514 request
768893</a
> is accepted, it should be working again.
</p
>
6519 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
6520 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
6521 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
6522 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
6523 <description><p
>Yesterday, I had the pleasure of attending a talk with the
6524 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
6525 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
6526 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
6527 learn that there is a large set of publicly available key servers to
6528 use when looking for peoples public key. So far I have used
6529 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
6530 were misbehaving, but those days are ended. The servers I have used
6531 up until yesterday have been slow and some times unavailable. I hope
6532 those problems are gone now.
</p
>
6534 <p
>Behind the round robin DNS entry of the
6535 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
6536 there is a pool of more than
100 keyservers which are checked every
6537 day to ensure they are well connected and up to date. It must be
6538 better than what I have used so far. :)
</p
>
6540 <p
>Yesterdays speaker told me that the service is the default
6541 keyserver provided by the default configuration in GnuPG, but this do
6542 not seem to be used in Debian. Perhaps it should?
</p
>
6544 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
6547 <p
><blockquote
><pre
>
6548 keyserver pool.sks-keyservers.net
6549 </pre
></blockquote
></p
>
6551 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
6552 entries in DNS. Just for fun, I did just that at work, so now every
6553 user of GnuPG at the University of Oslo should find a OpenGPG
6554 keyserver automatically should their need it:
</p
>
6556 <p
><blockquote
><pre
>
6557 % host -t srv _pgpkey-http._tcp.uio.no
6558 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
6560 </pre
></blockquote
></p
>
6562 <p
>Now if only
6563 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
6564 HKP lookup protocol
</a
> supported finding signature paths, I would be
6565 very happy. It can look up a given key or search for a user ID, but I
6566 normally do not want that, but to find a trust path from my key to
6567 another key. Given a user ID or key ID, I would like to find (and
6568 download) the keys representing a signature path from my key to the
6569 key in question, to be able to get a trust path between the two keys.
6570 This is as far as I can tell not possible today. Perhaps something
6571 for a future version of the protocol?
</p
>
6576 <title>From English wiki to translated PDF and epub via Docbook
</title>
6577 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
6578 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
6579 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
6580 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
6581 project
</a
> provide an instruction manual for teachers, system
6582 administrators and other users that contain useful tips for setting up
6583 and maintaining a Debian Edu installation. This text is about how the
6584 text processing of this manual is handled in the project.
</p
>
6586 <p
>One goal of the project is to provide information in the native
6587 language of its users, and for this we need to handle translations.
6588 But we also want to make sure each language contain the same
6589 information, so for this we need a good way to keep the translations
6590 in sync. And we want it to be easy for our users to improve the
6591 documentation, avoiding the need to learn special formats or tools to
6592 contribute, and the obvious way to do this is to make it possible to
6593 edit the documentation using a web browser. We also want it to be
6594 easy for translators to keep the translation up to date, and give them
6595 help in figuring out what need to be translated. Here is the list of
6596 tools and the process we have found trying to reach all these
6599 <p
>We maintain the authoritative source of our manual in the
6600 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
6601 wiki
</a
>, as several wiki pages written in English. It consist of one
6602 front page with references to the different chapters, several pages
6603 for each chapter, and finally one
"collection page
" gluing all the
6604 chapters together into one large web page (aka
6605 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
6606 AllInOne page
</a
>). The AllInOne page is the one used for further
6607 processing and translations. Thanks to the fact that the
6608 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
6609 wiki.debian.org support exporting pages in
6610 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
6611 the list of pages to export using the raw version of the AllInOne
6612 page, loop over each of them to generate a Docbook XML version of the
6613 manual. This process also download images and transform image
6614 references to use the locally downloaded images. The generated
6615 Docbook XML files are slightly broken, so some post-processing is done
6616 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
6617 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6618 a handfull of images. The XML file can now be used to generate PDF, HTML
6619 and epub versions of the English manual. This is the basic step of
6620 our process, making PDF (using dblatex), HTML (using xsltproc) and
6621 epub (using dbtoepub) version from Docbook XML, and the resulting files
6622 are placed in the debian-edu-doc-en binary package.
</p
>
6624 <p
>But English documentation is not enough for us. We want translated
6625 documentation too, and we want to make it easy for translators to
6626 track the English original. For this we use the
6627 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
6628 which allow us to transform the English Docbook XML file into a
6629 translation file (a .pot file), usable with the normal gettext based
6630 translation tools used by those translating free software. The pot
6631 file is used to create and maintain translation files (several .po
6632 files), which the translations update with the native language
6633 translations of all titles, paragraphs and blocks of text in the
6634 original. The next step is combining the original English Docbook XML
6635 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6636 create a translated Docbook XML file (in this case
6637 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6638 translated, if the translation is not complete) Docbook XML file can
6639 then be used like the original to create a PDF, HTML and epub version
6640 of the documentation.
</p
>
6642 <p
>The translators use different tools to edit the .po files. We
6644 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
6645 while some use emacs and vi, others can use web based editors like
6646 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
6647 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
6648 is where the .po file end up, in our git repository. Updated
6649 translations can either be committed directly to git, or submitted as
6650 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
6651 against the debian-edu-doc package
</a
>.
</p
>
6653 <p
>One challenge is images, which both might need to be translated (if
6654 they show translated user applications), and are needed in different
6655 formats when creating PDF and HTML versions (epub is a HTML version in
6656 this regard). For this we transform the original PNG images to the
6657 needed density and format during build, and have a way to provide
6658 translated images by storing translated versions in
6659 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6660 package maintainers know more.
</p
>
6662 <p
>If you wonder what the result look like, we provide
6663 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
6664 of the documentation packages on the web
</a
>. See for example the
6665 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
6666 PDF version
</a
> or the
6667 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
6668 HTML version
</a
>. We do not yet build the epub version by default,
6669 but perhaps it will be done in the future.
</p
>
6671 <p
>To learn more, check out
6672 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
6673 debian-edu-doc package
</a
>,
6674 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
6675 manual on the wiki
</a
> and
6676 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
6677 translation instructions
</a
> in the manual.
</p
>
6682 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
6683 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
6684 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
6685 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
6686 <description><p
>It would be nice if it was easier in Debian to get all the hardware
6687 related packages relevant for the computer installed automatically.
6688 So I implemented one, using
6689 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
6690 package
</a
>. To use it, install the tasksel and isenkram packages and
6691 run tasksel as user root. You should be presented with a new option,
6692 "Hardware specific packages (autodetected by isenkram)
". When you
6693 select it, tasksel will install the packages isenkram claim is fit for
6694 the current hardware, hot pluggable or not.
<p
>
6696 <p
>The implementation is in two files, one is the tasksel menu entry
6697 description, and the other is the script used to extract the list of
6698 packages to install. The first part is in
6699 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
6702 <p
><blockquote
><pre
>
6705 Description: Hardware specific packages (autodetected by isenkram)
6706 Based on the detected hardware various hardware specific packages are
6708 Test-new-install: mark show
6710 Packages: for-current-hardware
6711 </pre
></blockquote
></p
>
6713 <p
>The second part is in
6714 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
6717 <p
><blockquote
><pre
>
6722 isenkram-autoinstall-firmware -l
6724 </pre
></blockquote
></p
>
6726 <p
>All in all, a very short and simple implementation making it
6727 trivial to install the hardware dependent package we all may want to
6728 have installed on our machines. I
've not been able to find a way to
6729 get tasksel to tell you exactly which packages it plan to install
6730 before doing the installation. So if you are curious or careful,
6731 check the output from the isenkram-* command line tools first.
</p
>
6733 <p
>The information about which packages are handling which hardware is
6734 fetched either from the isenkram package itself in
6735 /usr/share/isenkram/, from git.debian.org or from the APT package
6736 database (using the Modaliases header). The APT package database
6737 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6738 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
6739 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
6740 the python-apt code (bug
6741 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
6742 workaround I was able to get rid of the file descriptor leak and
6743 reduce the memory leak from ~
30 MiB per hardware detection down to
6744 around
2 MiB per hardware detection. It should make the desktop
6745 daemon a lot more useful. The fix is in version
0.7 uploaded to
6746 unstable today.
</p
>
6748 <p
>I believe the current way of mapping hardware to packages in
6749 Isenkram is is a good draft, but in the future I expect isenkram to
6750 use the AppStream data source for this. A proposal for getting proper
6751 AppStream support into Debian is floating around as
6752 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
6753 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
6754 project
</a
> will take place this summer to improve the situation. I
6755 look forward to seeing the result, and welcome patches for isenkram to
6756 start using the information when it is ready.
</p
>
6758 <p
>If you want your package to map to some specific hardware, either
6759 add a
"Xb-Modaliases
" header to your control file like I did in
6760 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
6761 package
</a
> or submit a bug report with the details to the isenkram
6763 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
6764 blog posts tagged isenkram
</a
> for details on the notation. I expect
6765 the information will be migrated to AppStream eventually, but for the
6766 moment I got no better place to store it.
</p
>
6771 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
6772 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
6773 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
6774 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
6775 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6776 project
</a
> is working on providing the software and hardware to make
6777 it easy for non-technical people to host their data and communication
6778 at home, and being able to communicate with their friends and family
6779 encrypted and away from prying eyes. It is still going strong, and
6780 today a major mile stone was reached.
</p
>
6782 <p
>Today, the last of the packages currently used by the project to
6783 created the system images were accepted into Debian Unstable. It was
6784 the freedombox-setup package, which is used to configure the images
6785 during build and on the first boot. Now all one need to get going is
6786 the build code from the freedom-maker git repository and packages from
6787 Debian. And once the freedombox-setup package enter testing, we can
6788 build everything directly from Debian. :)
</p
>
6790 <p
>Some key packages used by Freedombox are
6791 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
6792 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
6793 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
6794 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
6795 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
6796 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
6797 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
6798 are plans to integrate more packages into the setup. User
6799 documentation is maintained on the Debian wiki. Please
6800 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
6801 the manual
</a
> and help us improve it.
</p
>
6803 <p
>To test for yourself and create boot images with the FreedomBox
6804 setup, run this on a Debian machine using a user with sudo rights to
6805 become root:
</p
>
6807 <p
><pre
>
6808 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6809 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6811 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6813 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6814 </pre
></p
>
6816 <p
>Root access is needed to run debootstrap and mount loopback
6817 devices. See the README in the freedom-maker git repo for more
6818 details on the build. If you do not want all three images, trim the
6819 make line. Note that the virtualbox-image target is not really
6820 virtualbox specific. It create a x86 image usable in kvm, qemu,
6821 vmware and any other x86 virtual machine environment. You might need
6822 the version of vmdebootstrap in Jessie to get the build working, as it
6823 include fixes for a race condition with kpartx.
</p
>
6825 <p
>If you instead want to install using a Debian CD and the preseed
6826 method, boot a Debian Wheezy ISO and use this boot argument to load
6827 the preseed values:
</p
>
6829 <p
><pre
>
6830 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6831 </pre
></p
>
6833 <p
>I have not tested it myself the last few weeks, so I do not know if
6834 it still work.
</p
>
6836 <p
>If you wonder how to help, one task you could look at is using
6837 systemd as the boot system. It will become the default for Linux in
6838 Jessie, so we need to make sure it is usable on the Freedombox. I did
6839 a simple test a few weeks ago, and noticed dnsmasq failed to start
6840 during boot when using systemd. I suspect there are other problems
6841 too. :) To detect problems, there is a test suite included, which can
6842 be run from the plinth web interface.
</p
>
6844 <p
>Give it a go and let us know how it goes on the mailing list, and help
6845 us get the new release published. :) Please join us on
6846 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6847 irc.debian.org)
</a
> and
6848 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6849 mailing list
</a
> if you want to help make this vision come true.
</p
>
6854 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
6855 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
6856 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
6857 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
6858 <description><p
>For a while now, I have been looking for a sensible offsite backup
6859 solution for use at home. My requirements are simple, it must be
6860 cheap and locally encrypted (in other words, I keep the encryption
6861 keys, the storage provider do not have access to my private files).
6862 One idea me and my friends had many years ago, before the cloud
6863 storage providers showed up, was to use Google mail as storage,
6864 writing a Linux block device storing blocks as emails in the mail
6865 service provided by Google, and thus get heaps of free space. On top
6866 of this one can add encryption, RAID and volume management to have
6867 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6868 I never found time to implement such system. But the last few weeks I
6869 have looked at a system called
6870 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
6871 mounted network backed file system with the features I need.
</p
>
6873 <p
>S3QL is a fuse file system with a local cache and cloud storage,
6874 handling several different storage providers, any with Amazon S3,
6875 Google Drive or OpenStack API. There are heaps of such storage
6876 providers. S3QL can also use a local directory as storage, which
6877 combined with sshfs allow for file storage on any ssh server. S3QL
6878 include support for encryption, compression, de-duplication, snapshots
6879 and immutable file systems, allowing me to mount the remote storage as
6880 a local mount point, look at and use the files as if they were local,
6881 while the content is stored in the cloud as well. This allow me to
6882 have a backup that should survive fire. The file system can not be
6883 shared between several machines at the same time, as only one can
6884 mount it at the time, but any machine with the encryption key and
6885 access to the storage service can mount it if it is unmounted.
</p
>
6887 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
6888 package is included already. So to get started, run
<tt
>apt-get
6889 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
6890 Greenqloud, after reading their nice recipe on
6891 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
6892 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
6893 in Iceland more than those in USA when it come to keeping my personal
6894 data safe and private, and thus would rather spend money on a company
6895 in Iceland. Another nice recipe is available from the article
6896 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
6897 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
6898 Admin magazine. When the provider is picked, figure out how to get
6899 the API key needed to connect to the storage API. With Greencloud,
6900 the key did not show up until I had added payment details to my
6903 <p
>Armed with the API access details, it is time to create the file
6904 system. First, create a new bucket in the cloud. This bucket is the
6905 file system storage area. I picked a bucket name reflecting the
6906 machine that was going to store data there, but any name will do.
6907 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
6908 the API login and password, and a locally created password. Store it
6909 all in ~root/.s3ql/authinfo2 like this:
6911 <p
><blockquote
><pre
>
6913 storage-url: s3c://s.greenqloud.com:
443/bucket-name
6914 backend-login: API-login
6915 backend-password: API-password
6916 fs-passphrase: local-password
6917 </pre
></blockquote
></p
>
6919 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
6920 but any sensible way to create a fairly random password should do it.
6921 Armed with these details, it is now time to run mkfs, entering the API
6922 details and password to create it:
</p
>
6924 <p
><blockquote
><pre
>
6925 # mkdir -m
700 /var/lib/s3ql-cache
6926 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6927 --ssl s3c://s.greenqloud.com:
443/bucket-name
6928 Enter backend login:
6929 Enter backend password:
6930 Before using S3QL, make sure to read the user
's guide, especially
6931 the
'Important Rules to Avoid Loosing Data
' section.
6932 Enter encryption password:
6933 Confirm encryption password:
6934 Generating random encryption key...
6935 Creating metadata tables...
6945 Compressing and uploading metadata...
6946 Wrote
0.00 MB of compressed metadata.
6947 #
</pre
></blockquote
></p
>
6949 <p
>The next step is mounting the file system to make the storage available.
6951 <p
><blockquote
><pre
>
6952 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6953 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6954 Using
4 upload threads.
6955 Downloading and decompressing metadata...
6965 Mounting filesystem...
6967 Filesystem Size Used Avail Use% Mounted on
6968 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
6970 </pre
></blockquote
></p
>
6972 <p
>The file system is now ready for use. I use rsync to store my
6973 backups in it, and as the metadata used by rsync is downloaded at
6974 mount time, no network traffic (and storage cost) is triggered by
6975 running rsync. To unmount, one should not use the normal umount
6976 command, as this will not flush the cache to the cloud storage, but
6977 instead running the umount.s3ql command like this:
6979 <p
><blockquote
><pre
>
6982 </pre
></blockquote
></p
>
6984 <p
>There is a fsck command available to check the file system and
6985 correct any problems detected. This can be used if the local server
6986 crashes while the file system is mounted, to reset the
"already
6987 mounted
" flag. This is what it look like when processing a working
6988 file system:
</p
>
6990 <p
><blockquote
><pre
>
6991 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
6992 Using cached metadata.
6993 File system seems clean, checking anyway.
6994 Checking DB integrity...
6995 Creating temporary extra indices...
6996 Checking lost+found...
6997 Checking cached objects...
6998 Checking names (refcounts)...
6999 Checking contents (names)...
7000 Checking contents (inodes)...
7001 Checking contents (parent inodes)...
7002 Checking objects (reference counts)...
7003 Checking objects (backend)...
7004 ..processed
5000 objects so far..
7005 ..processed
10000 objects so far..
7006 ..processed
15000 objects so far..
7007 Checking objects (sizes)...
7008 Checking blocks (referenced objects)...
7009 Checking blocks (refcounts)...
7010 Checking inode-block mapping (blocks)...
7011 Checking inode-block mapping (inodes)...
7012 Checking inodes (refcounts)...
7013 Checking inodes (sizes)...
7014 Checking extended attributes (names)...
7015 Checking extended attributes (inodes)...
7016 Checking symlinks (inodes)...
7017 Checking directory reachability...
7018 Checking unix conventions...
7019 Checking referential integrity...
7020 Dropping temporary indices...
7021 Backing up old metadata...
7031 Compressing and uploading metadata...
7032 Wrote
0.89 MB of compressed metadata.
7034 </pre
></blockquote
></p
>
7036 <p
>Thanks to the cache, working on files that fit in the cache is very
7037 quick, about the same speed as local file access. Uploading large
7038 amount of data is to me limited by the bandwidth out of and into my
7039 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
7040 which is very close to my upload speed, and downloading the same
7041 Debian installation ISO gave me
610 kiB/s, close to my download speed.
7042 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
7043 network, not the file system code. I do not know what a good cache
7044 size would be, but suspect that the cache should e larger than your
7045 working set.
</p
>
7047 <p
>I mentioned that only one machine can mount the file system at the
7048 time. If another machine try, it is told that the file system is
7051 <p
><blockquote
><pre
>
7052 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
7053 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
7054 Using
8 upload threads.
7055 Backend reports that fs is still mounted elsewhere, aborting.
7057 </pre
></blockquote
></p
>
7059 <p
>The file content is uploaded when the cache is full, while the
7060 metadata is uploaded once every
24 hour by default. To ensure the
7061 file system content is flushed to the cloud, one can either umount the
7062 file system, or ask S3QL to flush the cache and metadata using
7065 <p
><blockquote
><pre
>
7066 # s3qlctrl upload-meta /s3ql
7067 # s3qlctrl flushcache /s3ql
7069 </pre
></blockquote
></p
>
7071 <p
>If you are curious about how much space your data uses in the
7072 cloud, and how much compression and deduplication cut down on the
7073 storage usage, you can use s3qlstat on the mounted file system to get
7076 <p
><blockquote
><pre
>
7078 Directory entries:
9141
7081 Total data size:
22049.38 MB
7082 After de-duplication:
21955.46 MB (
99.57% of total)
7083 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
7084 Database size:
2.39 MB (uncompressed)
7085 (some values do not take into account not-yet-uploaded dirty blocks in cache)
7087 </pre
></blockquote
></p
>
7089 <p
>I mentioned earlier that there are several possible suppliers of
7090 storage. I did not try to locate them all, but am aware of at least
7091 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
7092 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
7093 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
7094 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
7095 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
7096 accept payment in Bitcoin. Pick one that suit your need. Some of
7097 them provide several GiB of free storage, but the prize models are
7098 quite different and you will have to figure out what suits you
7101 <p
>While researching this blog post, I had a look at research papers
7102 and posters discussing the S3QL file system. There are several, which
7103 told me that the file system is getting a critical check by the
7104 science community and increased my confidence in using it. One nice
7106 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
7107 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
7108 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
7109 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
7110 and Pamela Smith. Please have a look.
</p
>
7112 <p
>Given my problems with different file systems earlier, I decided to
7113 check out the mounted S3QL file system to see if it would be usable as
7114 a home directory (in other word, that it provided POSIX semantics when
7115 it come to locking and umask handling etc). Running
7116 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
7117 test code to check file system semantics
</a
>, I was happy to discover that
7118 no error was found. So the file system can be used for home
7119 directories, if one chooses to do so.
</p
>
7121 <p
>If you do not want a locally file system, and want something that
7122 work without the Linux fuse file system, I would like to mention the
7123 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
7124 provide locally encrypted backup using a command line client. It have
7125 a nicer access control system, where one can split out read and write
7126 access, allowing some systems to write to the backup and others to
7127 only read from it.
</p
>
7129 <p
>As usual, if you use Bitcoin and want to show your support of my
7130 activities, please send Bitcoin donations to my address
7131 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7136 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
7137 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
7138 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
7139 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
7140 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
7141 project
</a
> is working on providing the software and hardware for
7142 making it easy for non-technical people to host their data and
7143 communication at home, and being able to communicate with their
7144 friends and family encrypted and away from prying eyes. It has been
7145 going on for a while, and is slowly progressing towards a new test
7146 release (
0.2).
</p
>
7148 <p
>And what day could be better than the Pi day to announce that the
7149 new version will provide
"hard drive
" / SD card / USB stick images for
7150 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
7151 system), and can also be installed using a Debian installer preseed
7152 file. The Debian based Freedombox is now based on Debian Jessie,
7153 where most of the needed packages used are already present. Only one,
7154 the freedombox-setup package, is missing. To try to build your own
7155 boot image to test the current status, fetch the freedom-maker scripts
7157 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
7158 with a user with sudo access to become root:
7161 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
7163 sudo apt-get install git vmdebootstrap mercurial python-docutils \
7164 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
7166 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
7169 <p
>Root access is needed to run debootstrap and mount loopback
7170 devices. See the README for more details on the build. If you do not
7171 want all three images, trim the make line. But note that thanks to
<a
7172 href=
"https://bugs.debian.org/
741407">a race condition in
7173 vmdebootstrap
</a
>, the build might fail without the patch to the
7174 kpartx call.
</p
>
7176 <p
>If you instead want to install using a Debian CD and the preseed
7177 method, boot a Debian Wheezy ISO and use this boot argument to load
7178 the preseed values:
</p
>
7181 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
7184 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
7185 recently introduced bug in apt in Jessie
</a
>, the installer will
7186 currently hang while setting up APT sources. Killing the
7187 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
7188 installation will get the installation going. This affect all
7189 installations in Jessie, and I expect it will be fixed soon.
</p
>
7191 <p
>Give it a go and let us know how it goes on the mailing list, and help
7192 us get the new release published. :) Please join us on
7193 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
7194 irc.debian.org)
</a
> and
7195 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7196 mailing list
</a
> if you want to help make this vision come true.
</p
>
7201 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
7202 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
7203 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
7204 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
7205 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
7206 innetgr tools, because I needed them in
7207 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
7208 ng-utils, and it has served me well. I placed the project under the
7209 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
7210 repository. But many years ago, the CVS repository was dropped (lost,
7211 not migrated to new hardware, not sure), and the project have lacked a
7212 proper home since then.
</p
>
7214 <p
>Last summer, I had a look at the package and made a new release
7215 fixing a irritating crash bug, but was unable to store the changes in
7216 a proper source control system. I applied for a project on
7217 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
7218 to follow up on it. Until today. :)
</p
>
7220 <p
>After many hours of cleaning and migration, the ng-utils project
7221 now have a new home, and a git repository with the highlight of the
7222 history of the project. I published all release tarballs and imported
7223 them into the git repository. As the project is really stable and not
7224 expected to gain new features any time soon, I decided to make a new
7225 release and call it
1.0. Visit the new project home on
7226 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
7227 if you want to check it out. The new version is also uploaded into
7228 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
7233 <title>Testing sysvinit from experimental in Debian Hurd
</title>
7234 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
7235 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
7236 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
7237 <description><p
>A few days ago I decided to try to help the Hurd people to get
7238 their changes into sysvinit, to allow them to use the normal sysvinit
7239 boot system instead of their old one. This follow up on the
7240 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
7241 Google Summer of Code work
</a
> done last summer by Justus Winter to
7242 get Debian on Hurd working more like Debian on Linux. To get started,
7243 I downloaded a prebuilt hard disk image from
7244 <a href=
"http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
">http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
</a
>,
7245 and started it using virt-manager.
</p
>
7247 <p
>The first think I had to do after logging in (root without any
7248 password) was to get the network operational. I followed
7249 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
7250 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
7251 commands as root to get the machine to accept a IP address from the
7252 kvm internal DHCP server:
</p
>
7254 <p
><blockquote
><pre
>
7255 settrans -fgap /dev/netdde /hurd/netdde
7256 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
7257 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
7259 </pre
></blockquote
></p
>
7261 <p
>After this, the machine had internet connectivity, and I could
7262 upgrade it and install the sysvinit packages from experimental and
7263 enable it as the default boot system in Hurd.
</p
>
7265 <p
>But before I did that, I set a password on the root user, as ssh is
7266 running on the machine it for ssh login to work a password need to be
7267 set. Also, note that a bug somewhere in openssh on Hurd block
7268 compression from working. Remember to turn that off on the client
7271 <p
>Run these commands as root to upgrade and test the new sysvinit
7274 <p
><blockquote
><pre
>
7275 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
7276 deb http://http.debian.net/debian/ experimental main
7279 apt-get dist-upgrade
7280 apt-get install -t experimental initscripts sysv-rc sysvinit \
7281 sysvinit-core sysvinit-utils
7282 update-alternatives --config runsystem
7283 </pre
></blockquote
></p
>
7285 <p
>To reboot after switching boot system, you have to use
7286 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
7287 yet a sysvinit process able to receive the signals from the normal
7288 'reboot
' command. After switching to sysvinit as the boot system,
7289 upgrading every package and rebooting, the network come up with DHCP
7290 after boot as it should, and the settrans/pkill hack mentioned at the
7291 start is no longer needed. But for some strange reason, there are no
7292 longer any login prompt in the virtual console, so I logged in using
7295 <p
>Note that there are some race conditions in Hurd making the boot
7296 fail some times. No idea what the cause is, but hope the Hurd porters
7297 figure it out. At least Justus said on IRC (#debian-hurd on
7298 irc.debian.org) that they are aware of the problem. A way to reduce
7299 the impact is to upgrade to the Hurd packages built by Justus by
7300 adding this repository to the machine:
</p
>
7302 <p
><blockquote
><pre
>
7303 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
7304 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
7306 </pre
></blockquote
></p
>
7308 <p
>At the moment the prebuilt virtual machine get some packages from
7309 http://ftp.debian-ports.org/debian, because some of the packages in
7310 unstable do not yet include the required patches that are lingering in
7311 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
7313 <p
><blockquote
><pre
>
7314 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
7315 i emacs - GNU Emacs editor (metapackage)
7316 i gdb - GNU Debugger
7317 i hurd-recommended - Miscellaneous translators
7318 i isc-dhcp-client - ISC DHCP client
7319 i isc-dhcp-common - common files used by all the isc-dhcp* packages
7320 i libc-bin - Embedded GNU C Library: Binaries
7321 i libc-dev-bin - Embedded GNU C Library: Development binaries
7322 i libc0.3 - Embedded GNU C Library: Shared libraries
7323 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
7324 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
7325 i multiarch-support - Transitional package to ensure multiarch compatibilit
7326 i A x11-common - X Window System (X.Org) infrastructure
7327 i xorg - X.Org X Window System
7328 i A xserver-xorg - X.Org X server
7329 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
7331 </pre
></blockquote
></p
>
7333 <p
>All in all, testing hurd has been an interesting experience. :)
7334 X.org did not work out of the box and I never took the time to follow
7335 the porters instructions to fix it. This time I was interested in the
7336 command line stuff.
<p
>
7341 <title>New chrpath release
0.16</title>
7342 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
7343 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
7344 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
7345 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
7346 find problems in C, C++ and Java code using static source code
7347 analysis. It can detect a lot of different problems, and is very
7348 useful to find memory and locking bugs in the error handling part of
7349 the source. The company behind it provide
7350 <a href=
"https://scan.coverity.com/
">check of free software projects as
7351 a community service
</a
>, and many hundred free software projects are
7352 already checked. A few days ago I decided to have a closer look at
7353 the Coverity system, and discovered that the
7354 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
7355 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
7356 projects I am involved with was already registered. But these are
7357 fairly big, and I would also like to have a small and easy project to
7358 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
7359 checking of the chrpath project
</a
>. It was
7360 added to the checker and discovered seven potential defects. Six of
7361 these were real, mostly resource
"leak
" when the program detected an
7362 error. Nothing serious, as the resources would be released a fraction
7363 of a second later when the program exited because of the error, but it
7364 is nice to do it right in case the source of the program some time in
7365 the future end up in a library. Having fixed all defects and added
7366 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
7367 mailing list for the chrpath developers
</a
>, I decided it was time to
7368 publish a new release. These are the release notes:
</p
>
7370 <p
>New in
0.16 released
2014-
01-
14:
</p
>
7374 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
7375 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
7376 <li
>Mention new project mailing list in the documentation.
</li
>
7381 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
7382 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
7383 project if something is wrong with the new release. The test suite
7384 did not discover any old errors, so if you find a new one, please also
7385 include a test suite check.
</p
>
7390 <title>New chrpath release
0.15</title>
7391 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
7392 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
7393 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
7394 <description><p
>After many years break from the package and a vain hope that
7395 development would be continued by someone else, I finally pulled my
7396 acts together this morning and wrapped up a new release of chrpath,
7397 the command line tool to modify the rpath and runpath of already
7398 compiled ELF programs. The update was triggered by the persistence of
7399 Isha Vishnoi at IBM, which needed a new config.guess file to get
7400 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
7401 is working on. I checked the
7402 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
7403 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
7404 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
7405 packages for interesting patches (failed to find the source from
7406 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
7407 These are the release notes:
</p
>
7409 <p
>New in
0.15 released
2013-
11-
24:
</p
>
7413 <li
>Updated config.sub and config.guess from the GNU project to work
7414 with newer architectures. Thanks to isha vishnoi for the heads
7417 <li
>Updated README with current URLs.
</li
>
7419 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
7420 Matthias Klose.
</li
>
7422 <li
>Added missing help for -k|--keepgoing option, using patch by
7423 Petr Machata found in Fedora.
</li
>
7425 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
7426 .dynamic is a NULL terminated string. Based on patch found in
7427 Fedora credited Axel Thimm and Christian Krause.
</li
>
7432 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
7433 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
7434 project if something is wrong with the new release. The test suite
7435 did not discover any old errors, so if you find a new one, please also
7436 include a testsuite check.
</p
>
7441 <title>Debian init.d boot script example for rsyslog
</title>
7442 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
7443 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
7444 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
7445 <description><p
>If one of the points of switching to a new init system in Debian is
7446 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
7447 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
7448 init.d scripts at all. Here is an example init.d script, ie a rewrite
7449 of /etc/init.d/rsyslog:
</p
>
7451 <p
><pre
>
7452 #!/lib/init/init-d-script
7455 # Required-Start: $remote_fs $time
7456 # Required-Stop: umountnfs $time
7457 # X-Stop-After: sendsigs
7458 # Default-Start:
2 3 4 5
7459 # Default-Stop:
0 1 6
7460 # Short-Description: enhanced syslogd
7461 # Description: Rsyslog is an enhanced multi-threaded syslogd.
7462 # It is quite compatible to stock sysklogd and can be
7463 # used as a drop-in replacement.
7465 DESC=
"enhanced syslogd
"
7466 DAEMON=/usr/sbin/rsyslogd
7467 </pre
></p
>
7469 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
7470 script was
137 lines, and the above is just
15 lines, most of it meta
7471 info/comments.
</p
>
7473 <p
>How to do this, you ask? Well, one create a new script
7474 /lib/init/init-d-script looking something like this:
7476 <p
><pre
>
7479 # Define LSB log_* functions.
7480 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
7481 # and status_of_proc is working.
7482 . /lib/lsb/init-functions
7485 # Function that starts the daemon/service
7491 #
0 if daemon has been started
7492 #
1 if daemon was already running
7493 #
2 if daemon could not be started
7494 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
7496 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
7499 # Add code here, if necessary, that waits for the process to be ready
7500 # to handle requests from services started subsequently which depend
7501 # on this one. As a last resort, sleep for some time.
7505 # Function that stops the daemon/service
7510 #
0 if daemon has been stopped
7511 #
1 if daemon was already stopped
7512 #
2 if daemon could not be stopped
7513 # other if a failure occurred
7514 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
7515 RETVAL=
"$?
"
7516 [
"$RETVAL
" =
2 ]
&& return
2
7517 # Wait for children to finish too if this is a daemon that forks
7518 # and if the daemon is only ever run from this initscript.
7519 # If the above conditions are not satisfied then add some other code
7520 # that waits for the process to drop all resources that could be
7521 # needed by services started subsequently. A last resort is to
7522 # sleep for some time.
7523 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
7524 [
"$?
" =
2 ]
&& return
2
7525 # Many daemons don
't delete their pidfiles when they exit.
7527 return
"$RETVAL
"
7531 # Function that sends a SIGHUP to the daemon/service
7535 # If the daemon can reload its configuration without
7536 # restarting (for example, when it is sent a SIGHUP),
7537 # then implement that here.
7539 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
7544 scriptbasename=
"$(basename $
1)
"
7545 echo
"SN: $scriptbasename
"
7546 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
7547 script=
"$
1"
7554 NAME=$(basename $DAEMON)
7555 PIDFILE=/var/run/$NAME.pid
7557 # Exit if the package is not installed
7558 #[ -x
"$DAEMON
" ] || exit
0
7560 # Read configuration variable file if it is present
7561 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
7563 # Load the VERBOSE setting and other rcS variables
7566 case
"$
1" in
7568 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
7570 case
"$?
" in
7571 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7572 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7576 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
7578 case
"$?
" in
7579 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7580 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7584 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
7586 #reload|force-reload)
7588 # If do_reload() is not implemented then leave this commented out
7589 # and leave
'force-reload
' as an alias for
'restart
'.
7591 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
7595 restart|force-reload)
7597 # If the
"reload
" option is implemented then remove the
7598 #
'force-reload
' alias
7600 log_daemon_msg
"Restarting $DESC
" "$NAME
"
7602 case
"$?
" in
7605 case
"$?
" in
7607 1) log_end_msg
1 ;; # Old process is still running
7608 *) log_end_msg
1 ;; # Failed to start
7618 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
7624 </pre
></p
>
7626 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
7627 lot. I did not really polish the approach, so it might not always
7628 work out of the box, but you get the idea. I did not try very hard to
7629 optimize it nor make it more robust either.
</p
>
7631 <p
>A better argument for switching init system in Debian than reducing
7632 the size of init scripts (which is a good thing to do anyway), is to
7633 get boot system that is able to handle the kernel events sensibly and
7634 robustly, and do not depend on the boot to run sequentially. The boot
7635 and the kernel have not behaved sequentially in years.
</p
>
7640 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
7641 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
7642 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
7643 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
7644 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
7645 remote display access is the preferred solution with oVirt and RedHat
7646 Enterprise Virtualization, and I was sad to discover the other day
7647 that the browser plugin needed to use these systems seamlessly was
7648 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
7649 for a package
</a
> was from
2012-
04-
10 with no progress since
7650 2013-
04-
01, so I decided to wrap up a package based on the great work
7651 from Cajus Pollmeier and put it in a collab-maint maintained git
7652 repository to get a package I could use. I would very much like
7653 others to help me maintain the package (or just take over, I do not
7654 mind), but as no-one had volunteered so far, I just uploaded it to
7655 NEW. I hope it will be available in Debian in a few days.
</p
>
7657 <p
>The source is now available from
7658 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
</a
>.
</p
>
7663 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
7664 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
7665 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
7666 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
7667 <description><p
>The
7668 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
7669 program is a a very nice system to create virtual machine images. It
7670 create a image file, add a partition table, mount it and run
7671 debootstrap in the mounted directory to create a Debian system on a
7672 stick. Yesterday, I decided to try to teach it how to make images for
7673 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
7674 of a plan to simplify the build system for
7675 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
7676 project
</a
>. The FreedomBox project already uses vmdebootstrap for
7677 the virtualbox images, but its current build system made multistrap
7678 based system for Dreamplug images, and it is lacking support for
7679 Raspberry Pi.
</p
>
7681 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
7682 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7683 code and adjusted it to be able to build armel images on my amd64
7684 Debian laptop. I ended up giving vmdebootstrap five new options,
7685 allowing me to replicate the image creation process I use to make
7686 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
7687 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
7688 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
7689 call debootstrap with --foreign and to copy the handler into the
7690 generated chroot before running the second stage. This allow
7691 vmdebootstrap to create armel images on an amd64 host. Next I added
7692 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
7693 fstype
</tt
> to teach it to create a separate /boot/ partition with the
7694 given file system type, allowing me to create an image with a vfat
7695 partition for the /boot/ stuff. I also added a
<tt
>--variant
7696 variant
</tt
> option to allow me to create smaller images without the
7697 Debian base system packages installed. Finally, I added an option
7698 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
7699 as a boot loader. It is not needed on the Raspberry Pi and probably
7700 most other non-x86 architectures. The changes were accepted by the
7701 upstream author of vmdebootstrap yesterday and today, and is now
7703 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
7704 upstream project page
</a
>.
</p
>
7706 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
7707 create a small script (the customize script) to add the non-free
7708 binary blob needed to boot the Raspberry Pi and the APT source
7711 <p
><pre
>
7713 set -e # Exit on first error
7714 rootdir=
"$
1"
7715 cd
"$rootdir
"
7716 cat
&lt;
&lt;EOF
> etc/apt/sources.list
7717 deb http://http.debian.net/debian/ jessie main contrib non-free
7719 # Install non-free binary blob needed to boot Raspberry Pi. This
7720 # install a kernel somewhere too.
7721 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7722 -O $rootdir/usr/bin/rpi-update
7723 chmod a+x $rootdir/usr/bin/rpi-update
7724 mkdir -p $rootdir/lib/modules
7725 touch $rootdir/boot/start.elf
7726 chroot $rootdir rpi-update
7727 </pre
></p
>
7729 <p
>Next, fetch the latest vmdebootstrap script and call it like this
7730 to build the image:
</p
>
7733 sudo ./vmdebootstrap \
7736 --distribution jessie \
7737 --mirror http://http.debian.net/debian \
7746 --root-password raspberry \
7747 --hostname raspberrypi \
7748 --foreign /usr/bin/qemu-arm-static \
7749 --customize `pwd`/customize \
7751 --package git-core \
7752 --package binutils \
7753 --package ca-certificates \
7756 </pre
></p
>
7758 <p
>The list of packages being installed are the ones needed by
7759 rpi-update to make the image bootable on the Raspberry Pi, with the
7760 exception of netbase, which is needed by debootstrap to find
7761 /etc/hosts with the minbase variant. I really wish there was a way to
7762 set up an Raspberry Pi using only packages in the Debian archive, but
7763 that is not possible as far as I know, because it boots from the GPU
7764 using a non-free binary blob.
</p
>
7766 <p
>The build host need debootstrap, kpartx and qemu-user-static and
7767 probably a few others installed. I have not checked the complete
7768 build dependency list.
</p
>
7770 <p
>The resulting image will not use the hardware floating point unit
7771 on the Raspberry PI, because the armel architecture in Debian is not
7772 optimized for that use. So the images created will be a bit slower
7773 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
7778 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
7779 <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>
7780 <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>
7781 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
7782 <description><p
>The last few days I came across a few good causes that should get
7783 wider attention. I recommend signing and donating to each one of
7786 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
7787 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
7788 Women program which is a Google Summer of Code like initiative to get
7789 more women involved in free software. One debian sponsor has offered
7790 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
7791 earmarked
</a
> for this initiative. I donated a few minutes ago, and
7792 hope you will to. :)
</p
>
7794 <p
>And the Electronic Frontier Foundation just announced plans to
7795 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
7796 documentaries about the excessive spying
</a
> on every Internet user that
7797 take place these days, and their need to fund the work. I
've already
7798 donated. Are you next?
</p
>
7800 <p
>For my Norwegian audience, the organisation Studentenes og
7801 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7802 statement under the heading
7803 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
7804 Access
</a
> for those of us asking for more focus on open access in the
7805 Norwegian government. So far
499 signatures. I hope you will sign it
7811 <title>Videos about the Freedombox project - for inspiration and learning
</title>
7812 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
7813 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
7814 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
7815 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
7816 project
</a
> have been going on for a while, and have presented the
7817 vision, ideas and solution several places. Here is a little
7818 collection of videos of talks and presentation of the project.
</p
>
7822 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
7823 2,
5 minute marketing film
</a
> (Youtube)
</li
>
7825 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
7826 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
7828 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
7829 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7830 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
7831 (Youtube)
</li
>
7833 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
7834 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
7836 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
7837 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
7839 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
7840 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7841 York City in
2012</a
> (Youtube)
</li
>
7843 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
7844 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
7845 (Youtube)
</li
>
7847 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
7848 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
7850 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
7851 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
7853 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
7854 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7855 2013</a
> (Youtube)
</li
>
7859 <p
>A larger list is available from
7860 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
7861 Freedombox Wiki
</a
>.
</p
>
7863 <p
>On other news, I am happy to report that Freedombox based on Debian
7864 Jessie is coming along quite well, and soon both Owncloud and using
7865 Tor should be available for testers of the Freedombox solution. :) In
7866 a few weeks I hope everything needed to test it is included in Debian.
7867 The withsqlite package is already in Debian, and the plinth package is
7868 pending in NEW. The third and vital part of that puzzle is the
7869 metapackage/setup framework, which is still pending an upload. Join
7870 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
7871 (#freedombox on irc.debian.org)
</a
> and
7872 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7873 mailing list
</a
> if you want to help make this vision come true.
</p
>
7878 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
7879 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
7880 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
7881 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
7882 <description><p
>I was introduced to the
7883 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
7884 in
2010, when Eben Moglen presented his vision about serving the need
7885 of non-technical people to keep their personal information private and
7886 within the legal protection of their own homes. The idea is to give
7887 people back the power over their network and machines, and return
7888 Internet back to its intended peer-to-peer architecture. Instead of
7889 depending on a central service, the Freedombox will give everyone
7890 control over their own basic infrastructure.
</p
>
7892 <p
>I
've intended to join the effort since then, but other tasks have
7893 taken priority. But this summers nasty news about the misuse of trust
7894 and privilege exercised by the
"western
" intelligence gathering
7895 communities increased my eagerness to contribute to a point where I
7896 actually started working on the project a while back.
</p
>
7898 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
7899 Debian initiative
</a
> based on the vision from Eben Moglen, is to
7900 create a simple and cheap Debian based appliance that anyone can hook
7901 up in their home and get access to secure and private services and
7902 communication. The initial deployment platform have been the
7903 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
7904 which is a piece of hardware I do not own. So to be able to test what
7905 the current Freedombox setup look like, I had to come up with a way to install
7906 it on some hardware I do have access to. I have rewritten the
7907 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
7908 image build framework to use .deb packages instead of only copying
7909 setup into the boot images, and thanks to this rewrite I am able to
7910 set up any machine supported by Debian Wheezy as a Freedombox, using
7911 the previously mentioned deb (and a few support debs for packages
7912 missing in Debian).
</p
>
7914 <p
>The current Freedombox setup consist of a set of bootstrapping
7916 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
7917 and a administrative web interface
7918 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
7919 withsqlite), as well as a privacy enhancing proxy based on
7920 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
7921 (freedombox-privoxy). There is also a web/javascript based XMPP
7922 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
7923 trying (unsuccessfully so far) to talk to the XMPP server
7924 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
7925 web interface is pluggable, and the goal is to use it to enable OpenID
7926 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7927 this is really working yet, see
7928 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
7929 project TODO
</a
> for links to GIT repositories. Most of the code is
7930 on github at the moment. The HTTP proxy is operational out of the
7931 box, and the admin web interface can be used to add/remove plinth
7932 users. I
've not been able to do anything else with it so far, but
7933 know there are several branches spread around github and other places
7934 with lots of half baked features.
</p
>
7936 <p
>Anyway, if you want to have a look at the current state, the
7937 following recipes should work to give you a test machine to poke
7940 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
7944 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
7945 <li
>Boot from it, either as CD or USB stick.
</li
>
7946 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
7947 to the Debian installer:
<p
>
7948 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
7950 <li
>Answer the few language/region/password questions and pick disk to
7951 install on.
</li
>
7953 <li
>When the installation is finished and the machine have rebooted a
7954 few times, your Freedombox is ready for testing.
</li
>
7958 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
7962 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
7963 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
7964 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
7966 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
7967 </pre
></li
>
7968 <li
><p
>Run this as root:
</p
>
7970 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7973 apt-get install freedombox-setup
7974 /usr/lib/freedombox/setup
7975 </pre
></li
>
7976 <li
>Reboot into your freshly created Freedombox.
</li
>
7980 <p
>You can test it on other architectures too, but because the
7981 freedombox-privoxy package is binary, it will only work as intended on
7982 the architectures where I have had time to build the binary and put it
7983 in my APT repository. But do not let this stop you. It is only a
7984 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
7986 <p
>Note that by default Freedombox is a DHCP server on the
7987 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
7988 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
7989 disable
</tt
>" as root.
</p
>
7991 <p
>Please let me know if this works for you, or if you have any
7992 problems. We gather on the IRC channel
7993 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
7994 irc.debian.org and the
7995 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
7996 mailing list
</a
>.
</p
>
7998 <p
>Once you get your freedombox operational, you can visit
7999 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
8000 welcome screen (dead end - do not be surprised if you are unable to
8001 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
8002 to look at the rest of plinth. The default user is
'admin
' and the
8003 default password is
'secret
'.
</p
>
8008 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
8009 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
8010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
8011 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
8012 <description><p
>Earlier, I reported about
8013 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
8014 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
8015 told by IBM that the original disk should be thrown away. And as
8016 there no longer was a problem if I bricked the firmware, I decided
8017 today to try to install Intel firmware to replace the Lenovo firmware
8018 currently on the disk.
</p
>
8020 <p
>I searched the Intel site for firmware, and found
8021 <a href=
"https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y
&ProdId=
3472&DwnldID=
18363&ProductFamily=Solid-State+Drives+and+Caching
&ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive
&ProductProduct=Intel%c2%ae+SSD+
520+Series+(
180GB%
2c+
2.5in+SATA+
6Gb%
2fs%
2c+
25nm%
2c+MLC)
&lang=eng
">issdfut_2.0
.4.iso
</a
>
8022 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
8023 according to the site should contain the latest firmware for SSD
8024 disks. I inserted the broken disk in one of my spare laptops and
8025 booted the ISO from a USB stick. The disk was recognized, but the
8026 program claimed the newest firmware already were installed and refused
8027 to insert any Intel firmware. So no change, and the disk is still
8028 unable to handle write load. :( I guess the only way to get them
8029 working would be if Lenovo releases new firmware. No idea how likely
8030 that is. Anyway, just blogging about this test for completeness. I
8031 got a working Samsung disk, and see no point in spending more time on
8032 the broken disks.
</p
>
8037 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
8038 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
8039 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
8040 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
8041 <description><p
>Today I switched to
8042 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
8043 new laptop
</a
>. I
've previously written about the problems I had with
8044 my new Thinkpad X230, which was delivered with an
8045 <a href=
"http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
">180
8046 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
8047 sustained writes. My hardware supplier have been very forthcoming in
8048 trying to find a solution, and after first trying with another
8049 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
8050 disk instead to fix it once and for all. The Samsung disk survived
8051 the installation of Debian with encrypted disks (filling the disk with
8052 random data during installation killed the first two), and I thus
8053 decided to trust it with my data. I have installed it as a Debian Edu
8054 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
8055 server at home using Kerberos and LDAP, and will use it as my work
8056 station from now on.
</p
>
8058 <p
>As this is a solid state disk with no moving parts, I believe the
8059 Debian Wheezy default installation need to be tuned a bit to increase
8060 performance and increase life time of the disk. The Linux kernel and
8061 user space applications do not yet adjust automatically to such
8062 environment. To make it easier for my self, I created a draft Debian
8063 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
8064 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
8065 for the ssd-setup package
</a
> is available from collab-maint, and it
8066 is set up to adjust the setup of the machine by just installing the
8067 package. If there is any non-SSD disk in the machine, the package
8068 will refuse to install, as I did not try to write any logic to sort
8069 file systems in SSD and non-SSD file systems.
</p
>
8071 <p
>I consider the package a draft, as I am a bit unsure how to best
8072 set up Debian Wheezy with an SSD. It is adjusted to my use case,
8073 where I set up the machine with one large encrypted partition (in
8074 addition to /boot), put LVM on top of this and set up partitions on
8075 top of this again. See the README file in the package source for the
8076 references I used to pick the settings. At the moment these
8077 parameters are tuned:
</p
>
8081 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
8082 (adding discard to /etc/crypttab)
</li
>
8084 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
8085 this case a cryptsetup partition) by changing issue_discards from
8086 0 to
1 in /etc/lvm/lvm.conf.
</li
>
8088 <li
>Set relatime as a file system option for ext3 and ext4 file
8091 <li
>Tell swap to use TRIM commands by adding
'discard
' to
8092 /etc/fstab.
</li
>
8094 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
8096 <li
>Run fstrim on every ext3 and ext4 file system every night (from
8097 cron.daily).
</li
>
8099 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
8100 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
8104 <p
>During installation, I cancelled the part where the installer fill
8105 the disk with random data, as this would kill the SSD performance for
8106 little gain. My goal with the encrypted file system is to ensure
8107 those stealing my laptop end up with a brick and not a working
8108 computer. I have no hope in keeping the really resourceful people
8109 from getting the data on the disk (see
8110 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
8111 Thus I concluded that adding the discard option to crypttab is the
8112 right thing to do.
</p
>
8114 <p
>I considered using the noop I/O scheduler, as several recommended
8115 it for SSD, but others recommended deadline and a benchmark I found
8116 indicated that deadline might be better for interactive use.
</p
>
8118 <p
>I also considered using the
'discard
' file system option for ext3
8119 and ext4, but read that it would give a performance hit ever time a
8120 file is removed, and thought it best to that that slowdown once a day
8121 instead of during my work.
</p
>
8123 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
8124 this is already done by Debian Edu.
</p
>
8126 <p
>I have not yet started on the user space tuning. I expect
8127 iceweasel need some tuning, and perhaps other applications too, but
8128 have not yet had time to investigate those parts.
</p
>
8130 <p
>The package should work on Ubuntu too, but I have not yet tested it
8133 <p
>As for the answer to the question in the title of this blog post,
8134 as far as I know, the only solution I know about is to replace the
8135 disk. It might be possible to flash it with Intel firmware instead of
8136 the Lenovo firmware. But I have not tried and did not want to do so
8137 without approval from Lenovo as I wanted to keep the warranty on the
8138 disk until a solution was found and they wanted the broken disks
8144 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
8145 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
8146 <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>
8147 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
8148 <description><p
>A few days ago, I wrote about
8149 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
8150 problems I experienced with my new X230 and its SSD disk
</a
>, which
8151 was dying during installation because it is unable to cope with
8152 sustained write. My supplier is in contact with
8153 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
8154 replacement disk to try to fix the problem. They decided to send an
8155 identical model, so my hopes for a permanent fix was slim.
</p
>
8157 <p
>Anyway, today I got the replacement disk and tried to install
8158 Debian Edu Wheezy with encrypted disk on it. The new disk have the
8159 same firmware version as the original. This time my hope raised
8160 slightly as the installation progressed, as the original disk used to
8161 die after
4-
7% of the disk was written to, while this time it kept
8162 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
8163 died again and I was back on square one. I still do not have a new
8164 laptop with a disk I can trust. I can not live with a disk that might
8165 lock up when I download a new
8166 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
8167 other large files. I look forward to hearing from my supplier with
8168 the next proposal from Lenovo.
</p
>
8170 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
8171 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
8172 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
8173 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
8174 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
8175 P/N
45N8295, P0C38732.
</p
>
8177 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
8178 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
8179 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
8180 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
8181 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
8182 P/N
45N8295, P0C38732.
</p
>
8184 <p
>The only difference is in the first number (serial number?), ISN,
8185 SA, date and WNPP values. Mentioning all the details here in case
8186 someone is able to use the information to find a way to identify the
8187 failing disk among working ones (if any such working disk actually
8193 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
8194 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
8195 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
8196 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
8197 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
8198 Debian Edu developer gathering and Debian and Ubuntu bug squashing
8199 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
8200 member assosiation NUUG
</a
> and
8201 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
8202 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
8203 Bitraf
</a
>.
</p
>
8205 <p
>It starts
10:
00 and continue until late evening. Everyone is
8206 welcome, and there is no fee to participate. There is on the other
8207 hand limited space, and only room for
30 people. Please put your name
8208 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
8209 wiki page
</a
> if you plan to join us.
</p
>
8214 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
8215 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
8216 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
8217 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
8218 <description><p
>Half a year ago, I reported that I had to find a
8219 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
8220 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
8221 time to spend on it, and it took a while to find a model I believe
8222 will do the job, but two days ago the replacement finally arrived. I
8224 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
8225 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
8226 a roaming workstation, and it seemed to work flawlessly. But my
8227 second installation with encrypted disk was not as successful. More
8228 on that below.
</p
>
8230 <p
>I had a hard time trying to track down a good laptop, as my most
8231 important requirements (robust and with a good keyboard) are never
8232 listed in the feature list. But I did get good help from the search
8233 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
8234 allowed me to limit the list of interesting laptops based on my other
8235 requirements. A bit surprising that SSD disk are not disks according
8236 to that search interface, so I had to drop specifying the number of
8237 disks from my search parameters. I also asked around among friends to
8238 get their impression on keyboards and robustness.
</p
>
8240 <p
>So the new laptop arrived, and it is quite a lot wider than the
8241 X41. I am not quite convinced about the keyboard, as it is
8242 significantly wider than my old keyboard, and I have to stretch my
8243 hand a lot more to reach the edges. But the key response is fairly
8244 good and the individual key shape is fairly easy to handle, so I hope
8245 I will get used to it. My old X40 was starting to fail, and I really
8246 needed a new laptop now. :)
</p
>
8248 <p
>Turning off the touch pad was simple. All it took was a quick
8249 visit to the BIOS during boot it disable it.
</p
>
8251 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
8252 lock up during load. And this happen when installing Debian Wheezy
8253 with encrypted disk, while the disk is being filled with random data.
8254 I also tested to install Ubuntu Raring, and it happen there too if I
8255 reenable the code to fill the disk with random data (it is disabled by
8256 default in Ubuntu). And the bug with is already known. It was
8257 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
8258 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
8259 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
8260 kernel developers as
8261 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
8262 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
8263 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
8264 Lenovo forums, both for
8265 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
8266 2012-
11-
10</a
> and for
8267 <a href=
"http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-
180GB-Intel-
520-SSD-under-heavy-write-load/m-p/
1068147">X230
8268 03-
20-
2013</a
>. The problem do not only affect installation. The
8269 reports state that the disk lock up during use if many writes are done
8270 on the disk, so it is much no use to work around the installation
8271 problem and end up with a computer that can lock up at any moment.
8273 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
8274 available
</a
> that will lock up the hard drive after running a few
8275 minutes by writing to a file.
</p
>
8277 <p
>I
've contacted my supplier and asked how to handle this, and after
8278 contacting PCHELP Norway (request
01D1FDP) which handle support
8279 requests for Lenovo, his first suggestion was to upgrade the disk
8280 firmware. Unfortunately there is no newer firmware available from
8281 Lenovo, as my disk already have the most recent one (version LF1i). I
8282 hope to hear more from him today and hope the problem can be
8288 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
8289 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
8290 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
8291 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
8292 <description><p
>Half a year ago, I reported that I had to find a replacement for my
8293 trusty old Thinkpad X41. Unfortunately I did not have much time to
8294 spend on it, but today the replacement finally arrived. I ended up
8295 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
8296 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
8297 Wheezy as a roaming workstation, and it worked flawlessly. As I write
8298 this, it is installing what I hope will be a more final installation,
8299 with a encrypted hard drive to ensure any dope head stealing it end up
8300 with an expencive door stop.
</p
>
8302 <p
>I had a hard time trying to track down a good laptop, as my most
8303 important requirements (robust and with a good keyboard) are never
8304 listed in the feature list. But I did get good help from the search
8305 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
8306 allowed me to limit the list of interesting laptops based on my other
8307 requirements. A bit surprising that SSD disk are not disks, so I had
8308 to drop number of disks from my search parameters.
</p
>
8310 <p
>I am not quite convinced about the keyboard, as it is significantly
8311 wider than my old keyboard, and I have to stretch my hand a lot more
8312 to reach the edges. But the key response is fairly good and the
8313 individual key shape is fairly easy to handle, so I hope I will get
8314 used to it. My old X40 was starting to fail, and I really needed a
8315 new laptop now. :)
</p
>
8317 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
8322 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
8323 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
8324 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
8325 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
8326 <description><p
>It annoys me when the computer fail to do automatically what it is
8327 perfectly capable of, and I have to do it manually to get things
8328 working. One such task is to find out what firmware packages are
8329 needed to get the hardware on my computer working. Most often this
8330 affect the wifi card, but some times it even affect the RAID
8331 controller or the ethernet card. Today I pushed version
0.4 of the
8332 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
8333 including a new script isenkram-autoinstall-firmware handling the
8334 process of asking all the loaded kernel modules what firmware files
8335 they want, find debian packages providing these files and install the
8336 debian packages. Here is a test run on my laptop:
</p
>
8338 <p
><pre
>
8339 # isenkram-autoinstall-firmware
8340 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
8341 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
8342 info: locating packages with the requested firmware files
8343 info: Updating APT sources after adding non-free APT source
8344 info: trying to install firmware-ipw2x00
8347 Preconfiguring packages ...
8348 Selecting previously deselected package firmware-ipw2x00.
8349 (Reading database ...
259727 files and directories currently installed.)
8350 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
8351 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
8353 </pre
></p
>
8355 <p
>When all the requested firmware is present, a simple message is
8356 printed instead:
</p
>
8358 <p
><pre
>
8359 # isenkram-autoinstall-firmware
8360 info: did not find any firmware files requested by loaded kernel modules. exiting
8362 </pre
></p
>
8364 <p
>It could use some polish, but it is already working well and saving
8365 me some time when setting up new machines. :)
</p
>
8367 <p
>So, how does it work? It look at the set of currently loaded
8368 kernel modules, and look up each one of them using modinfo, to find
8369 the firmware files listed in the module meta-information. Next, it
8370 download the Contents file from a nearby APT mirror, and search for
8371 the firmware files in this file to locate the package with the
8372 requested firmware file. If the package is in the non-free section, a
8373 non-free APT source is added and the package is installed using
8374 <tt
>apt-get install
</tt
>. The end result is a slightly better working
8377 <p
>I hope someone find time to implement a more polished version of
8378 this script as part of the hw-detect debian-installer module, to
8379 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
8380 #
655507</a
>. There really is no need to insert USB sticks with
8381 firmware during a PXE install when the packages already are available
8382 from the nearby Debian mirror.
</p
>
8387 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
8388 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
8389 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
8390 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
8391 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
8392 the screen just turn black when Linux boot, either during installation
8393 or on first boot from the hard disk. I
've seen it once in a while the
8394 last few years, but only recently understood the cause. I
've seen it
8395 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
8396 The reason seem to be in the wiring of some laptops. The system to
8397 control the screen background light is inverted, so when Linux try to
8398 turn the brightness fully on, it end up turning it off instead. I do
8399 not know which Linux drivers are affected, but this post is about the
8400 i915 driver used by the
8401 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
8402 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
8404 <p
>The problem can be worked around two ways. Either by adding
8405 i915.invert_brightness=
1 as a kernel option, or by adding a file in
8406 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
8407 option when it load the i915 kernel module. On Debian and Ubuntu, it
8408 can be done by running these commands as root:
</p
>
8411 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
8412 update-initramfs -u -k all
8415 <p
>Since March
2012 there is
8416 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
8417 mechanism in the Linux kernel
</a
> to tell the i915 driver which
8418 hardware have this problem, and get the driver to invert the
8419 brightness setting automatically. To use it, one need to add a row in
8420 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
8421 intel_quirks array
</a
> in the driver source
8422 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
8423 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
8424 number (vendor number
8086 is assumed) and subdevice vendor and device
8427 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
8428 -vvnn
</tt
> for the video card in question:
</p
>
8430 <p
><pre
>
8431 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
8432 3rd Gen Core processor Graphics Controller [
8086:
0156] \
8433 (rev
09) (prog-if
00 [VGA controller])
8434 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
8435 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
8436 ParErr- Stepping- SE RR- FastB2B- DisINTx+
8437 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
8438 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
8440 Interrupt: pin A routed to IRQ
42
8441 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
8442 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
8443 Region
4: I/O ports at
4000 [size=
64]
8444 Expansion ROM at
<unassigned
> [disabled]
8445 Capabilities:
<access denied
>
8446 Kernel driver in use: i915
8447 </pre
></p
>
8449 <p
>The resulting intel_quirks entry would then look like this:
</p
>
8451 <p
><pre
>
8452 struct intel_quirk intel_quirks[] = {
8454 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
8455 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
8458 </pre
></p
>
8460 <p
>According to the kernel module instructions (as seen using
8461 <tt
>modinfo i915
</tt
>), information about hardware needing the
8462 invert_brightness flag should be sent to the
8463 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
8464 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
8465 developers. But my email about the laptop sent
2013-
06-
03 have not
8467 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
8468 web archive for the mailing list
</a
>, so I suspect they do not accept
8469 emails from non-subscribers. Because of this, I sent my patch also to
8470 the Debian bug tracking system instead as
8471 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
8472 sure the patch is not lost.
</p
>
8474 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
8475 with this problem working properly with Linux. If you use Gnome, your
8476 worries should be over at this point. But if you use KDE, there is
8477 something in KDE ignoring the invert_brightness setting and turning on
8478 the screen during login. I
've reported it to Debian as
8479 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
8480 have no idea yet how to figure out exactly what subsystem is doing
8481 this. Perhaps you can help? Perhaps you know what the Gnome
8482 developers did to handle this, and this can give a clue to the KDE
8483 developers? Or you know where in KDE the screen brightness is changed
8484 during login? If so, please update the BTS report (or get in touch if
8485 you do not know how to update BTS).
</p
>
8487 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
8488 acpi_backlight=vendor, to disable ACPI backlight support completely,
8489 as the ACPI information on the machine is trash and it is better to
8490 leave it to the intel video driver to control the screen
8491 backlight.
</p
>
8496 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
8497 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
8498 <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>
8499 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
8500 <description><p
>Two days ago, I asked
8501 <a href=
"http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
">how
8502 I could install Linux on a Packard Bell EasyNote LV computer
8503 preinstalled with Windows
8</a
>. I found a solution, but am horrified
8504 with the obstacles put in the way of Linux users on a laptop with UEFI
8505 and Windows
8.
</p
>
8507 <p
>I never found out if the cause of my problems were the use of UEFI
8508 secure booting or fast boot. I suspect fast boot was the problem,
8509 causing the firmware to boot directly from HD without considering any
8510 key presses and alternative devices, but do not know UEFI settings
8511 enough to tell.
</p
>
8513 <p
>There is no way to install Linux on the machine in question without
8514 opening the box and disconnecting the hard drive! This is as far as I
8515 can tell, the only way to get access to the firmware setup menu
8516 without accepting the Windows
8 license agreement. I am told (and
8517 found description on how to) that it is possible to configure the
8518 firmware setup once booted into Windows
8. But as I believe the terms
8519 of that agreement are completely unacceptable, accepting the license
8520 was never an alternative. I do not enter agreements I do not intend
8521 to follow.
</p
>
8523 <p
>I feared I had to return the laptops and ask for a refund, and
8524 waste many hours on this, but luckily there was a way to get it to
8525 work. But I would not recommend it to anyone planning to run Linux on
8526 it, and I have become sceptical to Windows
8 certified laptops. Is
8527 this the way Linux will be forced out of the market place, by making
8528 it close to impossible for
"normal
" users to install Linux without
8529 accepting the Microsoft Windows license terms? Or at least not
8530 without risking to loose the warranty?
</p
>
8532 <p
>I
've updated the
8533 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
8534 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
8535 do not have to struggle as much as I did to get Linux into the
8538 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
8539 Michael Tokarev and others for feedback and ideas.
</p
>
8544 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
8545 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
8546 <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>
8547 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
8548 <description><p
>I
've run into quite a problem the last few days. I bought three
8549 new laptops for my parents and a few others. I bought Packard Bell
8550 Easynote LV to run Kubuntu on and use as their home computer. But I
8551 am completely unable to figure out how to install Linux on it. The
8552 computer is preinstalled with Windows
8, and I suspect it uses UEFI
8553 instead of a BIOS to boot.
</p
>
8555 <p
>The problem is that I am unable to get it to PXE boot, and unable
8556 to get it to boot the Linux installer from my USB stick. I have yet
8557 to try the DVD install, and still hope it will work. when I turn on
8558 the computer, there is no information on what buttons to press to get
8559 the normal boot menu. I expect to get some boot menu to select PXE or
8560 USB stick booting. When booting, it first ask for the language to
8561 use, then for some regional settings, and finally if I will accept the
8562 Windows
8 terms of use. As these terms are completely unacceptable to
8563 me, I have no other choice but to turn off the computer and try again
8564 to get it to boot the Linux installer.
</p
>
8566 <p
>I have gathered my findings so far on a Linlap page about the
8567 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
8568 EasyNote LV
</a
> model. If you have any idea how to get Linux
8569 installed on this machine, please get in touch or update that wiki
8570 page. If I can
't find a way to install Linux, I will have to return
8571 the laptop to the seller and find another machine for my parents.
</p
>
8573 <p
>I wonder, is this the way Linux will be forced out of the market
8574 using UEFI and
"secure boot
" by making it impossible to install Linux
8575 on new Laptops?
</p
>
8580 <title>How to transform a Debian based system to a Debian Edu installation
</title>
8581 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
8582 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
8583 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
8584 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
8585 an operating system based on Debian intended for use in schools. It
8586 contain a turn-key solution for the computer network provided to
8587 pupils in the primary schools. It provide both the central server,
8588 network boot servers and desktop environments with heaps of
8589 educational software. The project was founded almost
12 years ago,
8590 2001-
07-
02. If you want to support the project, which is in need for
8591 cash to fund developer gatherings and other project related activity,
8592 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
8593 donate some money
</a
>.
8595 <p
>A topic that come up again and again on the Debian Edu mailing
8596 lists and elsewhere, is the question on how to transform a Debian or
8597 Ubuntu installation into a Debian Edu installation. It isn
't very
8598 hard, and last week I wrote a script to replicate the steps done by
8599 the Debian Edu installer.
</p
>
8601 <p
>The script,
8602 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup
">debian-edu-bless
<a/
>
8603 in the debian-edu-config package, will go through these six steps and
8604 transform an existing Debian Wheezy or Ubuntu (untested) installation
8605 into a Debian Edu Workstation:
</p
>
8609 <li
>Add skolelinux related APT sources.
</li
>
8610 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
8611 <li
>Install debian-edu-install to load preseeding values and pull in
8612 our configuration.
</li
>
8613 <li
>Preseed debconf database with profile setup in
8614 /etc/debian-edu/config, and run tasksel to install packages
8615 according to the profile specified in the config above,
8616 overriding some of the Debian automation machinery.
</li
>
8617 <li
>Run debian-edu-cfengine-D installation to configure everything
8618 that could not be done using preseeding.
</li
>
8619 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
8623 <p
>There are some steps in the Debian Edu installation that can not be
8624 replicated like this. Disk partitioning and LVM setup, for example.
8625 So this script just assume there is enough disk space to install all
8626 the needed packages.
</p
>
8628 <p
>The script was created to help a Debian Edu student working on
8629 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
8630 Debian Edu client, and using it he can take the existing
8631 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
8632 transform it into a fully functioning Debian Edu Workstation (or
8633 Roaming Workstation, or whatever :).
</p
>
8635 <p
>The default setting in the script is to create a KDE Workstation.
8636 If a LXDE based Roaming workstation is wanted instead, modify the
8637 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
8639 <p
><pre
>
8640 PROFILE=
"Roaming-Workstation
"
8641 DESKTOP=
"lxde
"
8642 </pre
></p
>
8644 <p
>The script could even become useful to set up Debian Edu servers in
8645 the cloud, by starting with a virtual Debian installation at some
8646 virtual hosting service and setting up all the services on first
8652 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
8653 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
8654 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
8655 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
8656 <description><P
>In January,
8657 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
8658 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
8659 channel #debian-lego
</a
>, for those of us in the Debian and Linux
8660 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
8661 marvellous construction system from Denmark. We also created
8662 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
8663 a place to take notes and write down our plans and hopes. And several
8664 people showed up to help. I was very happy to see the effect of my
8665 call. Since the small start, we have a debtags tag
8666 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
8667 tag for LEGO related packages, and now count
10 packages related to
8668 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
8670 <p
><table
>
8671 <tr
><td
><a href=
"http://packages.qa.debian.org/brickos
">brickos
</a
></td
><td
>alternative OS for LEGO Mindstorms RCX. Supports development in C/C++
</td
></tr
>
8672 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
8673 <tr
><td
><a href=
"http://packages.qa.debian.org/libnxt
">libnxt
</a
></td
><td
>utility library for talking to the LEGO Mindstorms NX
</td
></tr
>
8674 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
8675 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
8676 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
8677 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt
">python-nxt
</a
></td
><td
>python driver/interface/wrapper for the Lego Mindstorms NXT robot
</td
></tr
>
8678 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt-filer
">python-nxt-filer
</a
></td
><td
>simple GUI to manage files on a LEGO Mindstorms NXT
</td
></tr
>
8679 <tr
><td
><a href=
"http://packages.qa.debian.org/scratch
">scratch
</a
></td
><td
>easy to use programming environment for ages
8 and up
</td
></tr
>
8680 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
8681 </table
></p
>
8683 <p
>Some of these are available in Wheezy, and all but one are
8684 currently available in Jessie/testing. leocad is so far only
8685 available in experimental.
</p
>
8687 <p
>If you care about LEGO in Debian, please join us on IRC and help
8688 adding the rest of the great free software tools available on Linux
8689 for LEGO designers.
</p
>
8694 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
8695 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
8696 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
8697 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
8698 <description><p
>When I woke up this morning, I was very happy to see that the
8699 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
8700 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
8701 Debian release, and I expect to move my machines at home over to it fairly
8704 <p
>The new debian release contain heaps of new stuff, and one program
8705 in particular make me very happy to see included. The
8706 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
8707 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
8708 included for the first time. Alongside similar programs like
8709 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
8710 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
8711 it allow for visual programming where syntax errors can not happen,
8712 and a friendly programming environment for learning to control the
8713 computer. Scratch will also be included in the next release of Debian
8716 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
8717 Edu/Skolelinux release too. The
8718 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
8719 alpha release
</a
> went out last week, and the next should soon
8725 <title>Isenkram
0.2 finally in the Debian archive
</title>
8726 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
8727 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
8728 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
8729 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
8730 package
</a
> finally made it into the archive, after lingering in NEW
8731 for many months. I uploaded it to the Debian experimental suite
8732 2013-
01-
27, and today it was accepted into the archive.
</p
>
8734 <p
>Isenkram is a system for suggesting to users what packages to
8735 install to work with a pluggable hardware device. The suggestion pop
8736 up when the device is plugged in. For example if a Lego Mindstorm NXT
8737 is inserted, it will suggest to install the program needed to program
8738 the NXT controller. Give it a go, and report bugs and suggestions to
8744 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
8745 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
8746 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
8747 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
8748 <description><p
>My
8749 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
8750 bitcoin related blog post
</a
> mentioned that the new
8751 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
8752 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8753 2013-
01-
19, and have been available in unstable since then. It was
8754 automatically copied to Ubuntu, and is available in their Raring
8755 version too.
</p
>
8757 <p
>But there is a strange problem with the build that block this new
8758 version from being available on the i386 and kfreebsd-i386
8759 architectures. For some strange reason, the autobuilders in Debian
8760 for these architectures fail to run the test suite on these
8761 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
8762 We are so far unable to reproduce it when building it manually, and
8763 no-one have been able to propose a fix. If you got an idea what is
8764 failing, please let us know via the BTS.
</p
>
8766 <p
>One feature that is annoying me with of the bitcoin client, because
8767 I often run low on disk space, is the fact that the client will exit
8768 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
8769 #
696715</a
>). So make sure you have enough disk space when you run
8772 <p
>As usual, if you use bitcoin and want to show your support of my
8773 activities, please send Bitcoin donations to my address
8774 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8779 <title>Welcome to the world, Isenkram!
</title>
8780 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
8781 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
8782 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
8783 <description><p
>Yesterday, I
8784 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
8785 for testers
</a
> for my prototype for making Debian better at handling
8786 pluggable hardware devices, which I
8787 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
8788 out to create
</a
> earlier this month. Several valuable testers showed
8789 up, and caused me to really want to to open up the development to more
8790 people. But before I did this, I want to come up with a sensible name
8791 for this project. Today I finally decided on a new name, and I have
8792 renamed the project from hw-support-handler to this new name. In the
8793 process, I moved the source to git and made it available as a
8794 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
8795 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
8796 To fetch and build the latest version of the source, use
</p
>
8799 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8800 cd isenkram
&& git-buildpackage -us -uc
8803 <p
>I have not yet adjusted all files to use the new name yet. If you
8804 want to hack on the source or improve the package, please go ahead.
8805 But please talk to me first on IRC or via email before you do major
8806 changes, to make sure we do not step on each others toes. :)
</p
>
8808 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
8809 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8810 stuff, in other words. I
've been told it is the Norwegian variant of
8811 the German word eisenkram, for those that are familiar with that
8814 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
8815 instructions, to avoid confusing people with an error from the signing
8818 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
8819 clone argument to avoid the need for authentication.
</p
>
8824 <title>First prototype ready making hardware easier to use in Debian
</title>
8825 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
8826 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
8827 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
8828 <description><p
>Early this month I set out to try to
8829 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
8830 the Debian support for pluggable hardware devices
</a
>. Now my
8831 prototype is working, and it is ready for a larger audience. To test
8833 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
8834 from the Debian Edu subversion repository
</a
>, build and install the
8835 package. You might have to log out and in again activate the
8836 autostart script.
</p
>
8838 <p
>The design is simple:
</p
>
8842 <li
>Add desktop entry in /usr/share/autostart/ causing a program
8843 hw-support-handlerd to start when the user log in.
</li
>
8845 <li
>This program listen for kernel events about new hardware (directly
8846 from the kernel like udev does), not using HAL dbus events as I
8847 initially did.
</li
>
8849 <li
>When new hardware is inserted, look up the hardware modalias in
8850 the APT database, a database
8851 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
8852 via HTTP
</a
> and a database available as part of the package.
</li
>
8854 <li
>If a package is mapped to the hardware in question, the package
8855 isn
't installed yet and this is the first time the hardware was
8856 plugged in, show a desktop notification suggesting to install the
8857 package or packages.
</li
>
8859 <li
>If the user click on the
'install package now
' button, ask
8860 aptdaemon via the PackageKit API to install the requrired package.
</li
>
8862 <li
>aptdaemon ask for root password or sudo password, and install the
8863 package while showing progress information in a window.
</li
>
8867 <p
>I still need to come up with a better name for the system. Here
8868 are some screen shots showing the prototype in action. First the
8869 notification, then the password request, and finally the request to
8870 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
8872 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
8873 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
8874 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
8875 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
8876 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
8878 <p
>The prototype still need to be improved with longer timeouts, but
8879 is already useful. The database of hardware to package mappings also
8880 need more work. It is currently compatible with the Ubuntu way of
8881 storing such information in the package control file, but could be
8882 changed to use other formats instead or in addition to the current
8883 method. I
've dropped the use of discover for this mapping, as the
8884 modalias approach is more flexible and easier to use on Linux as long
8885 as the Linux kernel expose its modalias strings directly.
</p
>
8887 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
8888 here is the command required to check out and build the source: Use
8889 '<tt
>svn checkout
8890 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8891 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
8892 devscripts package.
</p
>
8894 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
8895 renamed to Isenkram and the source moved from the Debian Edu
8896 subversion repository to a Debian collab-maint git repository. See
8897 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
8898 instructions
</a
> for details.
</p
>
8903 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
8904 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
8905 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
8906 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
8907 <description><p
>This Christmas my trusty old laptop died. It died quietly and
8908 suddenly in bed. With a quiet whimper, it went completely quiet and
8909 black. The power button was no longer able to turn it on. It was a
8910 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8911 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8912 Compaq I had before that. Now I need to find a replacement. To keep
8913 going during Christmas, I moved the one year old SSD disk to my old
8914 X40 where it fitted (only one I had left that could use it), but it is
8915 not a durable solution.
8917 <p
>My laptop needs are fairly modest. This is my wishlist from when I
8918 got a new one more than
10 years ago. It still holds true.:)
</p
>
8922 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
8923 than A4).
</li
>
8924 <li
>Robust, it will be in my backpack every day.
</li
>
8925 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
8926 <li
>Long battery life time. Preferable a week.
</li
>
8927 <li
>Internal WIFI network card.
</li
>
8928 <li
>Internal Twisted Pair network card.
</li
>
8929 <li
>Some USB slots (
2-
3 is plenty)
</li
>
8930 <li
>Good keyboard - similar to the Thinkpad.
</li
>
8931 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
8933 <li
>Hardware supported by Debian Stable, ie the default kernel and
8934 X.org packages.
</li
>
8935 <li
>Quiet, preferably fan free (or at least not using the fan most of
8940 <p
>You will notice that there are no RAM and CPU requirements in the
8941 list. The reason is simply that the specifications on laptops the
8942 last
10-
15 years have been sufficient for my needs, and I have to look
8943 at other features to choose my laptop. But are there still made as
8944 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8945 robust, and Thinkpads seem to be heading in the wrong direction since
8946 Lenovo took over. But I
've been told that X220 and X1 Carbon might
8947 still be useful.
</p
>
8949 <p
>Perhaps I should rethink my needs, and look for a pad with an
8950 external keyboard? I
'll have to check the
8951 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
8952 well-supported laptops, or perhaps just buy one preinstalled from one
8953 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
8954 Pre-loaded site
</a
>.
</p
>
8959 <title>How to find a browser plugin supporting a given MIME type
</title>
8960 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
8961 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
8962 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
8963 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
8964 install to get support for a given MIME type. Thanks to
8965 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
8966 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
8967 Unfortunately, not very many packages provide the needed meta
8968 information, Anyway, here is a small script to look up all browser
8969 plugin packages announcing ther MIME support using this specification:
</p
>
8975 def pkgs_handling_mimetype(mimetype):
8980 version = pkg.candidate
8982 version = pkg.installed
8985 record = version.record
8986 if not record.has_key(
'Npp-MimeType
'):
8988 mime_types = record[
'Npp-MimeType
'].split(
',
')
8989 for t in mime_types:
8990 t = t.rstrip().strip()
8992 thepkgs.append(pkg.name)
8994 mimetype =
"audio/ogg
"
8995 if
1 < len(sys.argv):
8996 mimetype = sys.argv[
1]
8997 print
"Browser plugin packages supporting %s:
" % mimetype
8998 for pkg in pkgs_handling_mimetype(mimetype):
8999 print
" %s
" %pkg
9002 <p
>It can be used like this to look up a given MIME type:
</p
>
9005 % ./apt-find-browserplug-for-mimetype
9006 Browser plugin packages supporting audio/ogg:
9008 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
9009 Browser plugin packages supporting application/x-shockwave-flash:
9010 browser-plugin-gnash
9014 <p
>In Ubuntu this mechanism is combined with support in the browser
9015 itself to query for plugins and propose to install the needed
9016 packages. It would be great if Debian supported such feature too. Is
9017 anyone working on adding it?
</p
>
9019 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
9020 request for icweasel support for this feature is
9021 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
9022 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
9023 of manpower and wish for a different design is the reason thus feature
9024 is not yet in iceweasel from Debian.
</p
>
9029 <title>What is the most supported MIME type in Debian?
</title>
9030 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
9031 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
9032 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
9033 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
9034 proposal to add AppStream information to the Debian archive
</a
>, is a
9035 proposal to make it possible for a Desktop application to propose to
9036 the user some package to install to gain support for a given MIME
9037 type, font, library etc. that is currently missing. With such
9038 mechanism in place, it would be possible for the desktop to
9039 automatically propose and install leocad if some LDraw file is
9040 downloaded by the browser.
</p
>
9042 <p
>To get some idea about the current content of the archive, I decided
9043 to write a simple program to extract all .desktop files from the
9044 Debian archive and look up the claimed MIME support there. The result
9046 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
9047 site
</a
>. Using the collected information, it become possible to
9048 answer the question in the title. Here are the
20 most supported MIME
9049 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
9050 The complete list is available from the link above.
</p
>
9052 <p
><strong
>Debian Stable:
</strong
></p
>
9056 ----- -----------------------
9072 18 application/x-ogg
9079 <p
><strong
>Debian Testing:
</strong
></p
>
9083 ----- -----------------------
9099 18 application/x-ogg
9106 <p
><strong
>Debian Unstable:
</strong
></p
>
9110 ----- -----------------------
9127 18 application/x-ogg
9133 <p
>I am told that PackageKit can provide an API to access the kind of
9134 information mentioned in DEP-
11. I have not yet had time to look at
9135 it, but hope the PackageKit people in Debian are on top of these
9138 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
9139 discovering a typo in my script.
</p
>
9144 <title>Using modalias info to find packages handling my hardware
</title>
9145 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
9146 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
9147 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
9148 <description><p
>Yesterday, I wrote about the
9149 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
9150 values provided by the Linux kernel
</a
> following my hope for
9151 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
9152 dongle support in Debian
</a
>. Using this knowledge, I have tested how
9153 modalias values attached to package names can be used to map packages
9154 to hardware. This allow the system to look up and suggest relevant
9155 packages when I plug in some new hardware into my machine, and replace
9156 discover and discover-data as the database used to map hardware to
9159 <p
>I create a modaliases file with entries like the following,
9160 containing package name, kernel module name (if relevant, otherwise
9161 the package name) and globs matching the relevant hardware
9164 <p
><blockquote
>
9165 Package: package-name
9166 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
9167 </blockquote
></p
>
9169 <p
>It is fairly trivial to write code to find the relevant packages
9170 for a given modalias value using this file.
</p
>
9172 <p
>An entry like this would suggest the video and picture application
9173 cheese for many USB web cameras (interface bus class
0E01):
</p
>
9175 <p
><blockquote
>
9177 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
9178 </blockquote
></p
>
9180 <p
>An entry like this would suggest the pcmciautils package when a
9181 CardBus bridge (bus class
0607) PCI device is present:
</p
>
9183 <p
><blockquote
>
9184 Package: pcmciautils
9185 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
9186 </blockquote
></p
>
9188 <p
>An entry like this would suggest the package colorhug-client when
9189 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
9191 <p
><blockquote
>
9192 Package: colorhug-client
9193 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
9194 </blockquote
></p
>
9196 <p
>I believe the format is compatible with the format of the Packages
9197 file in the Debian archive. Ubuntu already uses their Packages file
9198 to store their mappings from packages to hardware.
</p
>
9200 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
9201 announce the hardware it support in a way my prototype understand.
9202 This allow those publishing packages in an APT source outside the
9203 Debian archive as well as those backporting packages to make sure the
9204 hardware mapping are included in the package meta information. I
've
9205 tested such header in the pymissile package, and its modalias mapping
9206 is working as it should with my prototype. It even made it to Ubuntu
9209 <p
>To test if it was possible to look up supported hardware using only
9210 the shell tools available in the Debian installer, I wrote a shell
9211 implementation of the lookup code. The idea is to create files for
9212 each modalias and let the shell do the matching. Please check out and
9214 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
9215 shell script. It run without any extra dependencies and fetch the
9216 hardware mappings from the Debian archive and the subversion
9217 repository where I currently work on my prototype.
</p
>
9219 <p
>When I use it on a machine with a yubikey inserted, it suggest to
9220 install yubikey-personalization:
</p
>
9222 <p
><blockquote
>
9223 % ./hw-support-lookup
9224 <br
>yubikey-personalization
9226 </blockquote
></p
>
9228 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
9229 propose to install the pcmciautils package:
</p
>
9231 <p
><blockquote
>
9232 % ./hw-support-lookup
9233 <br
>pcmciautils
9235 </blockquote
></p
>
9237 <p
>If you know of any hardware-package mapping that should be added to
9238 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
9239 database
</a
>, please tell me about it.
</p
>
9241 <p
>It could be possible to generate several of the mappings between
9242 packages and hardware. One source would be to look at packages with
9243 kernel modules, ie packages with *.ko files in /lib/modules/, and
9244 extract their modalias information. Another would be to look at
9245 packages with udev rules, ie packages with files in
9246 /lib/udev/rules.d/, and extract their vendor/model information to
9247 generate a modalias matching rule. I have not tested any of these to
9248 see if it work.
</p
>
9250 <p
>If you want to help implementing a system to let us propose what
9251 packages to install when new hardware is plugged into a Debian
9252 machine, please send me an email or talk to me on
9253 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
9258 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
9259 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
9260 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
9261 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
9262 <description><p
>While looking into how to look up Debian packages based on hardware
9263 information, to find the packages that support a given piece of
9264 hardware, I refreshed my memory regarding modalias values, and decided
9265 to document the details. Here are my findings so far, also available
9267 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
9268 Debian Edu subversion repository
</a
>:
9270 <p
><strong
>Modalias decoded
</strong
></p
>
9272 <p
>This document try to explain what the different types of modalias
9273 values stands for. It is in part based on information from
9274 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
9275 &lt;URL:
<a href=
"http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
">http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
</a
> &gt;,
9276 &lt;URL:
<a href=
"http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
</a
> &gt; and
9277 &lt;URL:
<a href=
"http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
</a
> &gt;.
9279 <p
>The modalias entries for a given Linux machine can be found using
9280 this shell script:
</p
>
9283 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
9286 <p
>The supported modalias globs for a given kernel module can be found
9287 using modinfo:
</p
>
9290 % /sbin/modinfo psmouse | grep alias:
9291 alias: serio:ty05pr*id*ex*
9292 alias: serio:ty01pr*id*ex*
9296 <p
><strong
>PCI subtype
</strong
></p
>
9298 <p
>A typical PCI entry can look like this. This is an Intel Host
9299 Bridge memory controller:
</p
>
9301 <p
><blockquote
>
9302 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
9303 </blockquote
></p
>
9305 <p
>This represent these values:
</p
>
9310 sv
00001028 (subvendor)
9311 sd
000001AD (subdevice)
9313 sc
00 (bus subclass)
9317 <p
>The vendor/device values are the same values outputted from
'lspci
9318 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
9319 0600. The
0600 class is a host bridge. Other useful bus values are
9320 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
9322 <p
>Not sure how to figure out the interface value, nor what it
9325 <p
><strong
>USB subtype
</strong
></p
>
9327 <p
>Some typical USB entries can look like this. This is an internal
9328 USB hub in a laptop:
</p
>
9330 <p
><blockquote
>
9331 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
9332 </blockquote
></p
>
9334 <p
>Here is the values included in this alias:
</p
>
9337 v
1D6B (device vendor)
9338 p
0001 (device product)
9340 dc
09 (device class)
9341 dsc
00 (device subclass)
9342 dp
00 (device protocol)
9343 ic
09 (interface class)
9344 isc
00 (interface subclass)
9345 ip
00 (interface protocol)
9348 <p
>The
0900 device class/subclass means hub. Some times the relevant
9349 class is in the interface class section. For a simple USB web camera,
9350 these alias entries show up:
</p
>
9352 <p
><blockquote
>
9353 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
9354 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
9355 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
9356 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
9357 </blockquote
></p
>
9359 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
9360 camera),
0101 is audio control device and
0102 is audio streaming (aka
9361 microphone). Thus this is a camera with microphone included.
</p
>
9363 <p
><strong
>ACPI subtype
</strong
></p
>
9365 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
9366 receiver in a Thinkpad X40:
</p
>
9368 <p
><blockquote
>
9369 acpi:IBM0071:PNP0511:
9370 </blockquote
></p
>
9372 <p
>The values between the colons are IDs.
</p
>
9374 <p
><strong
>DMI subtype
</strong
></p
>
9376 <p
>The DMI table contain lots of information about the computer case
9377 and model. This is an entry for a IBM Thinkpad X40, fetched from
9378 /sys/devices/virtual/dmi/id/modalias:
</p
>
9380 <p
><blockquote
>
9381 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
9382 </blockquote
></p
>
9384 <p
>The values present are
</p
>
9387 bvn IBM (BIOS vendor)
9388 bvr
1UETB
6WW(
1.66) (BIOS version)
9389 bd
06/
15/
2005 (BIOS date)
9390 svn IBM (system vendor)
9391 pn
2371H4G (product name)
9392 pvr ThinkPadX40 (product version)
9393 rvn IBM (board vendor)
9394 rn
2371H4G (board name)
9395 rvr NotAvailable (board version)
9396 cvn IBM (chassis vendor)
9397 ct
10 (chassis type)
9398 cvr NotAvailable (chassis version)
9401 <p
>The chassis type
10 is Notebook. Other interesting values can be
9402 found in the dmidecode source:
</p
>
9406 4 Low Profile Desktop
9419 17 Main Server Chassis
9420 18 Expansion Chassis
9422 20 Bus Expansion Chassis
9423 21 Peripheral Chassis
9425 23 Rack Mount Chassis
9434 <p
>The chassis type values are not always accurately set in the DMI
9435 table. For example my home server is a tower, but the DMI modalias
9436 claim it is a desktop.
</p
>
9438 <p
><strong
>SerIO subtype
</strong
></p
>
9440 <p
>This type is used for PS/
2 mouse plugs. One example is from my
9441 test machine:
</p
>
9443 <p
><blockquote
>
9444 serio:ty01pr00id00ex00
9445 </blockquote
></p
>
9447 <p
>The values present are
</p
>
9456 <p
>This type is supported by the psmouse driver. I am not sure what
9457 the valid values are.
</p
>
9459 <p
><strong
>Other subtypes
</strong
></p
>
9461 <p
>There are heaps of other modalias subtypes according to
9462 file2alias.c. There is the rest of the list from that source: amba,
9463 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
9464 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
9465 vmbus, x86cpu and zorro. I did not spend time documenting all of
9466 these, as they do not seem relevant for my intended use with mapping
9467 hardware to packages when new stuff is inserted during run time.
</p
>
9469 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
9471 <p
>To check which kernel modules provide support for a given modalias,
9472 one can use the following shell script:
</p
>
9475 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
9476 echo
"$id
" ; \
9477 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
9481 <p
>The output can look like this (only the first few entries as the
9482 list is very long on my test machine):
</p
>
9486 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
9488 FATAL: Module acpi:device: not found.
9490 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
9491 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
9492 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
9493 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
9494 acpi:IBM0071:PNP0511:
9495 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
9496 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
9497 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
9501 <p
>If you want to help implementing a system to let us propose what
9502 packages to install when new hardware is plugged into a Debian
9503 machine, please send me an email or talk to me on
9504 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
9506 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
9507 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
9508 in /sys/ with space in them.
</p
>
9513 <title>Moved the pymissile Debian packaging to collab-maint
</title>
9514 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
9515 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
9516 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
9517 <description><p
>As part of my investigation on how to improve the support in Debian
9518 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
9519 Launcher and updated the Debian package
9520 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
9521 sure udev will fix the device permissions when it is plugged in. I
9522 also added a
"Modaliases
" header to test it in the Debian archive and
9523 hopefully make the package be proposed by jockey in Ubuntu when a user
9524 plug in his rocket launcher. In the process I moved the source to a
9525 git repository under collab-maint, to make it easier for any DD to
9526 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
9527 is not very active, but the software still work for me even after five
9528 years of relative silence. The new git repository is not listed in
9529 the uploaded package yet, because I want to test the other changes a
9530 bit more before I upload the new version. If you want to check out
9531 the new version with a .desktop file included, visit the
9532 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
9533 view
</a
> or use
"<tt
>git clone
9534 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
9539 <title>Lets make hardware dongles easier to use in Debian
</title>
9540 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
9541 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
9542 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
9543 <description><p
>One thing that annoys me with Debian and Linux distributions in
9544 general, is that there is a great package management system with the
9545 ability to automatically install software packages by downloading them
9546 from the distribution mirrors, but no way to get it to automatically
9547 install the packages I need to use the hardware I plug into my
9548 machine. Even if the package to use it is easily available from the
9549 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9550 suggest to automatically install the python-nxt, nbc and t2n packages
9551 I need to talk to it. When I plug in a Yubikey, it could propose the
9552 yubikey-personalization package. The information required to do this
9553 is available, but no-one have pulled all the pieces together.
</p
>
9555 <p
>Some years ago, I proposed to
9556 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
9557 the discover subsystem to implement this
</a
>. The idea is fairly
9562 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
9563 starting when a user log in.
</li
>
9565 <li
>Set this program up to listen for kernel events emitted when new
9566 hardware is inserted into the computer.
</li
>
9568 <li
>When new hardware is inserted, look up the hardware ID in a
9569 database mapping to packages, and take note of any non-installed
9570 packages.
</li
>
9572 <li
>Show a message to the user proposing to install the discovered
9573 package, and make it easy to install it.
</li
>
9577 <p
>I am not sure what the best way to implement this is, but my
9578 initial idea was to use dbus events to discover new hardware, the
9579 discover database to find packages and
9580 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
9583 <p
>Yesterday, I found time to try to implement this idea, and the
9584 draft package is now checked into
9585 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
9586 Debian Edu subversion repository
</a
>. In the process, I updated the
9587 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
9588 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9589 the relevant packages in Debian, and uploaded a new version
9590 2.2013.01.09 to unstable. I also discovered that the current
9591 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
9592 package in Debian no longer discovered any USB devices, because
9593 /proc/bus/usb/devices is no longer present. I ported it to use
9594 libusb as a fall back option to get it working. The fixed package
9595 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
9596 because of the freeze).
</p
>
9598 <p
>With this prototype in place, I can insert my Yubikey, and get this
9599 desktop notification to show up (only once, the first time it is
9600 inserted):
</p
>
9602 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
9604 <p
>For this prototype to be really useful, some way to automatically
9605 install the proposed packages by pressing the
"Please install
9606 program(s)
" button should to be implemented.
</p
>
9608 <p
>If this idea seem useful to you, and you want to help make it
9609 happen, please help me update the discover-data database with mappings
9610 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
9611 list the package you would like to have installed when a given
9612 hardware device is inserted into your computer, and report bugs using
9613 reportbug if it isn
't. Or, if you know of a better way to provide
9614 such mapping, please let me know.
</p
>
9616 <p
>This prototype need more work, and there are several questions that
9617 should be considered before it is ready for production use. Is dbus
9618 the correct way to detect new hardware? At the moment I look for HAL
9619 dbus events on the system bus, because that is the events I could see
9620 on my Debian Squeeze KDE desktop. Are there better events to use?
9621 How should the user be notified? Is the desktop notification
9622 mechanism the best option, or should the background daemon raise a
9623 popup instead? How should packages be installed? When should they
9624 not be installed?
</p
>
9626 <p
>If you want to help getting such feature implemented in Debian,
9627 please send me an email. :)
</p
>
9632 <title>New IRC channel for LEGO designers using Debian
</title>
9633 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
9634 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
9635 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
9636 <description><p
>During Christmas, I have worked a bit on the Debian support for
9637 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
9638 NXT
</a
>. My son and I have played a bit with my NXT set, and I
9639 discovered I had to build all the tools myself because none were
9640 already in Debian Squeeze. If Debian support for LEGO is something
9641 you care about, please join me on the IRC channel
9642 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
9643 irc.debian.org). There is a lot that could be done to improve the
9644 Debian support for LEGO designers. For example both CAD software
9645 and Mindstorm compilers are missing. :)
</p
>
9647 <p
>Update
2012-
01-
03: A
9648 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
9649 including links to Lego related packages is now available.
</p
>
9654 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
9655 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
9656 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
9657 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
9658 <description><p
>Let me start by wishing you all marry Christmas and a happy new
9659 year! I hope next year will prove to be a good year.
</p
>
9661 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
9662 decentralised
"currency
" that allow people to transfer bitcoins
9663 between each other with minimal overhead, is a very interesting
9664 experiment. And as I wrote a few days ago, the bitcoin situation in
9665 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
9666 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
9667 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
9668 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
9669 for one of the ftpmasters to approve the new bitcoin-qt package
9672 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
9673 team in Debian, you can easily test the package in Debian Squeeze
9674 using the following steps to get a set of working packages:
</p
>
9676 <blockquote
><pre
>
9677 git clone git://git.debian.org/git/collab-maint/bitcoin
9679 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9680 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9681 </pre
></blockquote
>
9683 <p
>You might have to install some build dependencies as well. The
9684 list of commands should give you two packages, bitcoind and
9685 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9686 client will download the complete set of bitcoin
"blocks
", which need
9687 around
5.6 GiB of data on my machine at the moment. Make sure your
9688 ~/.bitcoin/ directory have lots of spare room if you want to download
9689 all the blocks. The client will warn if the disk is getting full, so
9690 there is not really a problem if you got too little room, but you will
9691 not be able to get all the features out of the client.
</p
>
9693 <p
>As usual, if you use bitcoin and want to show your support of my
9694 activities, please send Bitcoin donations to my address
9695 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9700 <title>A word on bitcoin support in Debian
</title>
9701 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
9702 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
9703 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
9704 <description><p
>It has been a while since I wrote about
9705 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
9706 peer-to-peer based crypto-currency, and the reason is simply that I
9707 have been busy elsewhere. But two days ago, I started looking at the
9708 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
9709 Debian
</a
> again to try to recover my old bitcoin wallet. The package
9710 is now maintained by a
9711 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
9712 people
</a
>, and the grunt work had already been done by this team. We
9713 owe a huge thank you to all these team members. :)
9714 But I was sad to discover that the bitcoin client is missing in
9715 Wheezy. It is only available in Sid (and an outdated client from
9716 backports). The client had several RC bugs registered in BTS blocking
9717 it from entering testing. To try to help the team and improve the
9718 situation, I spent some time providing patches and triaging the bug
9719 reports. I also had a look at the bitcoin package available from Matt
9721 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
9722 Ubuntu
</a
>, and moved the useful pieces from that version into the
9723 Debian package.
</p
>
9725 <p
>After checking with the main package maintainer Jonas Smedegaard on
9726 IRC, I pushed several patches into the collab-maint git repository to
9727 improve the package. It now contains fixes for the RC issues (not from
9728 me, but fixed by Scott Howard), build rules for a Qt GUI client
9729 package, konqueror support for the bitcoin: URI and bash completion
9730 setup. As I work on Debian Squeeze, I also created
9731 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
9732 patch to backport
</a
> the latest version. Jonas is going to look at
9733 it and try to integrate it into the git repository before uploading a
9734 new version to unstable.
9736 <p
>I would very much like bitcoin to succeed, to get rid of the
9737 centralized control currently exercised in the monetary system. I
9738 find it completely unacceptable that the USA government is collecting
9739 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9740 that the major credit card companies can block legal money
9741 transactions to Wikileaks. But for bitcoin to succeed, more people
9742 need to use bitcoins, and more people need to accept bitcoins when
9743 they sell products and services. Improving the bitcoin support in
9744 Debian is a small step in the right direction, but not enough.
9745 Unfortunately the user experience when browsing the web and wanting to
9746 pay with bitcoin is still not very good. The bitcoin: URI is a step
9747 in the right direction, but need to work in most or every browser in
9748 use. Also the bitcoin-qt client is too heavy to fire up to do a
9749 quick transaction. I believe there are other clients available, but
9750 have not tested them.
</p
>
9753 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
9754 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
9755 I received
20.15 BTC so far on the address I provided in my blog two
9756 years ago, as can be
9757 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
9758 on the blockexplorer service
</a
>. Thank you everyone for your
9759 donation. The blockexplorer service demonstrates quite well that
9760 bitcoin is not quite anonymous and untracked. :) I wonder if the
9761 number of users have gone up since then. If you use bitcoin and want
9762 to show your support of my activity, please send Bitcoin donations to
9763 the same address as last time,
9764 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9769 <title>Git repository for song book for Computer Scientists
</title>
9770 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
9771 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
9772 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
9773 <description><p
>As I
9774 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
9775 this summer
</a
>, I have created a Computer Science song book a few
9776 years ago, and today I finally found time to create a public
9777 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
9778 repository for the project
</a
>.
</p
>
9780 <p
>If you want to help out, please clone the source and submit patches
9781 to the HTML version. To generate the PDF and PostScript version,
9782 please use prince XML, or let me know about a useful free software
9783 processor capable of creating a good looking PDF from the HTML.
</p
>
9785 <p
>Want to sing? You can still find the song book in HTML, PDF and
9786 PostScript formats at
9787 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
9788 Science Songbook
</a
>.
</p
>
9793 <title>Gratulerer med
19-årsdagen, Debian!
</title>
9794 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
9795 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
9796 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
9797 <description><p
>I dag fyller
9798 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
9799 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
9800 si gratulerer med dagen, Debian!
</p
>
9805 <title>Song book for Computer Scientists
</title>
9806 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
9807 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
9808 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
9809 <description><p
>Many years ago, while studying Computer Science at the
9810 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
9811 collecting computer related songs for use at parties. The original
9812 version was written in LaTeX, but a few years ago I got help from
9813 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9814 while keeping the ability to create a nice book in PDF format. I have
9815 not had time to maintain the book for a while now, and guess I should
9816 put it up on some public version control repository where others can
9817 help me extend and update the book. If anyone is volunteering to help
9818 me with this, send me an email. Also let me know if there are songs
9819 missing in my book.
</p
>
9821 <p
>I have not mentioned the book on my blog so far, and it occured to
9822 me today that I really should let all my readers share the joys of
9823 singing out load about programming, computers and computer networks.
9824 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
9825 12</a
> is about to start (and I am not going). Want to sing? Check
9826 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
9827 Computer Science Songbook
</a
>.
9832 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
9833 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
9834 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
9835 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
9836 <description><p
>At work we have heaps of servers. I believe the total count is
9837 around
1000 at the moment. To be able to get help from the vendors
9838 when something go wrong, we want to keep the firmware on the servers
9839 up to date. If the firmware isn
't the latest and greatest, the
9840 vendors typically refuse to start debugging any problems until the
9841 firmware is upgraded. So before every reboot, we want to upgrade the
9842 firmware, and we would really like everyone handling servers at the
9843 university to do this themselves when they plan to reboot a machine.
9844 For that to happen we at the unix server admin group need to provide
9845 the tools to do so.
</p
>
9847 <p
>To make firmware upgrading easier, I am working on a script to
9848 fetch and install the latest firmware for the servers we got. Most of
9849 our hardware are from Dell and HP, so I have focused on these servers
9850 so far. This blog post is about the Dell part.
</P
>
9852 <p
>On the Dell FTP site I was lucky enough to find
9853 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
9854 with firmware information for all
11th generation servers, listing
9855 which firmware should be used on a given model and where on the FTP
9856 site I can find it. Using a simple perl XML parser I can then
9857 download the shell scripts Dell provides to do firmware upgrades from
9858 within Linux and reboot when all the firmware is primed and ready to
9859 be activated on the first reboot.
</p
>
9861 <p
>This is the Dell related fragment of the perl code I am working on.
9862 Are there anyone working on similar tools for firmware upgrading all
9863 servers at a site? Please get in touch and lets share resources.
</p
>
9865 <p
><pre
>
9869 use File::Temp qw(tempdir);
9871 # Install needed RHEL packages if missing
9873 'XML::Simple
' =
> 'perl-XML-Simple
',
9875 for my $module (keys %rhelmodules) {
9876 eval
"use $module;
";
9878 my $pkg = $rhelmodules{$module};
9879 system(
"yum install -y $pkg
");
9880 eval
"use $module;
";
9884 my $errorsto =
'pere@hungry.com
';
9890 sub run_firmware_script {
9891 my ($opts, $script) = @_;
9893 print STDERR
"fail: missing script name\n
";
9896 print STDERR
"Running $script\n\n
";
9898 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
9899 print STDERR
"success: firmware script ran succcessfully\n
";
9901 print STDERR
"fail: firmware script returned error\n
";
9905 sub run_firmware_scripts {
9906 my ($opts, @dirs) = @_;
9907 # Run firmware packages
9908 for my $dir (@dirs) {
9909 print STDERR
"info: Running scripts in $dir\n
";
9910 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
9911 while (my $s = readdir $dh) {
9912 next if $s =~ m/^\.\.?/;
9913 run_firmware_script($opts,
"$dir/$s
");
9921 print STDERR
"info: Downloading $url\n
";
9922 system(
"wget --quiet \
"$url\
"");
9927 my $product = `dmidecode -s system-product-name`;
9930 if ($product =~ m/PowerEdge/) {
9932 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9933 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
9935 my $tmpdir = tempdir(
9939 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
9940 system(
'gunzip Catalog.xml.gz
');
9941 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
9942 # -q is quiet, disabling interactivity and reducing console output
9943 my $fwopts =
"-q
";
9945 for my $url (@paths) {
9946 fetch_dell_fw($url);
9948 run_firmware_scripts($fwopts, $tmpdir);
9950 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9951 print STDERR
"error: Please report to $errorsto.\n
";
9955 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9956 print STDERR
"error: Please report to $errorsto.\n
";
9962 my $url =
"ftp://ftp.us.dell.com/$path
";
9966 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9967 # firmware packages to download from Dell. Only work for Linux
9968 # machines and
11th generation Dell servers.
9969 sub fetch_dell_fw_list {
9970 my $filename = shift;
9972 my $product = `dmidecode -s system-product-name`;
9974 my ($mybrand, $mymodel) = split(/\s+/, $product);
9976 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
9978 my $xml = XMLin($filename);
9980 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
9981 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
9982 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
9984 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
9985 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
9987 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
9989 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
9991 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
9994 for my $component (@{$xml-
>{SoftwareComponent}}) {
9995 my $componenttype = $component-
>{ComponentType}-
>{value};
9997 # Drop application packages, only firmware and BIOS
9998 next if
'APAC
' eq $componenttype;
10000 my $cpath = $component-
>{path};
10001 for my $path (@paths) {
10002 if ($cpath =~ m%/$path$%) {
10003 push(@paths, $cpath);
10011 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
10012 it could work on other platforms with some tweaking. Anyone know a
10013 index like Catalog.xml is available from HP for HP servers? At the
10014 moment I maintain a similar list manually and it is quickly getting
10015 outdated.
</p
>
10020 <title>How is booting into runlevel
1 different from single user boots?
</title>
10021 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
10022 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
10023 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
10024 <description><p
>Wouter Verhelst have some
10025 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
10026 comments and opinions
</a
> on my blog post on
10027 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
10028 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
10029 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
10030 default KDE desktop in Debian
</a
>. I only have time to address one
10031 small piece of his comment now, and though it best to address the
10032 misunderstanding he bring forward:
</p
>
10034 <p
><blockquote
>
10035 Currently, a system admin has four options: [...] boot to a
10036 single-user system (by adding
'single
' to the kernel command line;
10037 this runs rcS and rc1 scripts)
10038 </blockquote
></p
>
10040 <p
>This make me believe Wouter believe booting into single user mode
10041 and booting into runlevel
1 is the same. I am not surprised he
10042 believe this, because it would make sense and is a quite sensible
10043 thing to believe. But because the boot in Debian is slightly broken,
10044 runlevel
1 do not work properly and it isn
't the same as single user
10045 mode. I
'll try to explain what is actually happing, but it is a bit
10046 hard to explain.
</p
>
10048 <p
>Single user mode is defined like this in /etc/inittab:
10049 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
10050 executed in single user mode is sulogin. Single user mode is a boot
10051 state
"between
" the runlevels, and when booting into single user mode,
10052 only the scripts in /etc/rcS.d/ are executed before the init process
10053 enters the single user state. When switching to runlevel
1, the state
10054 is in fact not ending in runlevel
1, but it passes through runlevel
1
10055 and end up in the single user mode (see /etc/rc1.d/S03single, which
10056 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
10057 1. It is confusing that the
'S
' (single user) init mode is not the
10058 mode enabled by /etc/rcS.d/ (which is more like the initial boot
10061 <p
>This summary might make it clearer. When booting for the first
10062 time into single user mode, the following commands are executed:
10063 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
10064 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
10065 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
10066 trying to continue after visiting single user mode. Not all services
10067 are started again as they should, causing the machine to end up in an
10068 unpredicatble state. This is why Debian admins recommend rebooting
10069 after visiting single user mode.
</p
>
10071 <p
>A similar problem with runlevel
1 is caused by the amount of
10072 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
10073 to runlevel
1, the services started from /etc/rcS.d/ are not properly
10074 stopped when passing through the scripts in /etc/rc1.d/, and not
10075 started again when switching away from runlevel
1 to the runlevels
10076 2-
5. I believe the problem is best fixed by moving all the scripts
10077 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
10078 functioning single user mode during boot.
</p
>
10080 <p
>I have spent several years investigating the Debian boot system,
10081 and discovered this problem a few years ago. I suspect it originates
10082 from when sysvinit was introduced into Debian, a long time ago.
</p
>
10087 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
10088 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
10089 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
10090 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
10091 <description><p
>In the Debian boot system, several packages include scripts that
10092 are started from /etc/rcS.d/. In fact, there is a bite more of them
10093 than make sense, and this causes a few problems. What kind of
10094 problems, you might ask. There are at least two problems. The first
10095 is that it is not possible to recover a machine after switching to
10096 runlevel
1. One need to actually reboot to get the machine back to
10097 the expected state. The other is that single user boot will sometimes
10098 run into problems because some of the subsystems are activated before
10099 the root login is presented, causing problems when trying to recover a
10100 machine from a problem in that subsystem. A minor additional point is
10101 that moving more scripts out of rcS.d/ and into the other rc#.d/
10102 directories will increase the amount of scripts that can run in
10103 parallel during boot, and thus decrease the boot time.
</p
>
10105 <p
>So, which scripts should start from rcS.d/. In short, only the
10106 scripts that _have_ to execute before the root login prompt is
10107 presented during a single user boot should go there. Everything else
10108 should go into the numeric runlevels. This means things like
10109 lm-sensors, fuse and x11-common should not run from rcS.d, but from
10110 the numeric runlevels. Today in Debian, there are around
115 init.d
10111 scripts that are started from rcS.d/, and most of them should be moved
10112 out. Do your package have one of them? Please help us make single
10113 user and runlevel
1 better by moving it.
</p
>
10115 <p
>Scripts setting up the screen, keyboard, system partitions
10116 etc. should still be started from rcS.d/, but there is for example no
10117 need to have the network enabled before the single user login prompt
10118 is presented.
</p
>
10120 <p
>As always, things are not so easy to fix as they sound. To keep
10121 Debian systems working while scripts migrate and during upgrades, the
10122 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
10123 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
10124 and the next ones can only be moved when their dependencies have been
10125 moved first. This migration must be done sequentially while we ensure
10126 that the package system upgrade packages in the right order to keep
10127 the system state correct. This will require some coordination when it
10128 comes to network related packages, but most of the packages with
10129 scripts that should migrate do not have anything in rcS.d/ depending
10130 on them. Some packages have already been updated, like the sudo
10131 package, while others are still left to do. I wish I had time to work
10132 on this myself, but real live constrains make it unlikely that I will
10133 find time to push this forward.
</p
>
10138 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
10139 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
10140 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
10141 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
10142 <description><p
>While at Debconf11, I have several times during discussions
10143 mentioned the issues I believe should be improved in Debian for its
10144 desktop to be useful for more people. The use case for this is my
10145 parents, which are currently running Kubuntu which solve the
10148 <p
>I suspect these four missing features are not very hard to
10149 implement. After all, they are present in Ubuntu, so if we wanted to
10150 do this in Debian we would have a source.
</p
>
10154 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
10155 are new packages available for upgrades, a icon in the KDE status bar
10156 indicate this, and clicking on it will activate the simple upgrade
10157 tool to handle it. I have no problem guiding both of my parents
10158 through the process over the phone. If a kernel reboot is required,
10159 this too is indicated by the status bars and the upgrade tool. Last
10160 time I checked, nothing with the same features was working in KDE in
10163 <li
><strong
>Simple handling of missing Firefox browser
10164 plugins.
</strong
> When the browser encounter a MIME type it do not
10165 currently have a handler for, it will ask the user if the system
10166 should search for a package that would add support for this MIME type,
10167 and if the user say yes, the APT sources will be searched for packages
10168 advertising the MIME type in their control file (visible in the
10169 Packages file in the APT archive). If one or more packages are found,
10170 it is a simple click of the mouse to add support for the missing mime
10171 type. If the package require the user to accept some non-free
10172 license, this is explained to the user. The entire process make it
10173 more clear to the user why something do not work in the browser, and
10174 make the chances higher for the user to blame the web page authors and
10175 not the browser for any missing features.
</li
>
10177 <li
><strong
>Simple handling of missing multimedia codec/format
10178 handlers.
</strong
> When the media players encounter a format or codec
10179 it is not supporting, a dialog pop up asking the user if the system
10180 should search for a package that would add support for it. This
10181 happen with things like MP3, Windows Media or H
.264. The selection
10182 and installation procedure is very similar to the Firefox browser
10183 plugin handling. This is as far as I know implemented using a
10184 gstreamer hook. The end result is that the user easily get access to
10185 the codecs that are present from the APT archives available, while
10186 explaining more on why a given format is unsupported by Ubuntu.
</li
>
10188 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
10189 displaying a text/plain file in my Debian browser, it will propose to
10190 start emacs to show it. If I remember correctly, when doing the same
10191 in Kunbutu it show the file as a text file in the browser. At least I
10192 know Opera will show text files within the browser. I much prefer the
10193 latter behaviour.
</li
>
10197 <p
>There are other nice features as well, like the simplified suite
10198 upgrader, but given that I am the one mostly doing the dist-upgrade,
10199 it do not matter much.
</p
>
10201 <p
>I really hope we could get these features in place for the next
10202 Debian release. It would require the coordinated effort of several
10203 maintainers, but would make the end user experience a lot better.
</p
>
10208 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
10209 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
10210 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
10211 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
10212 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
10213 site is build on Debian/Squeeze, and this platform was chosen because
10214 I am most familiar with Debian (being a Debian Developer for around
10
10215 years) because it is the latest stable Debian release which should get
10216 security support for a few years.
</p
>
10218 <p
>The web service is written in Perl, and depend on some perl modules
10219 that are missing in Debian at the moment. It would be great if these
10220 modules were added to the Debian archive, allowing anyone to set up
10221 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
10222 in their own country using only Debian packages. The list of modules
10223 missing in Debian/Squeeze isn
't very long, and I hope the perl group
10224 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
10225 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
10226 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
10227 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
10228 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
10229 easier in the future.
</p
>
10231 <p
>Thanks to the great tools in Debian, getting the missing modules
10232 installed on my server was a simple call to
'cpan2deb Module::Name
'
10233 and
'dpkg -i
' to install the resulting package. But this leave me
10234 with the responsibility of tracking security problems, which I really
10235 do not have time for.
</p
>
10240 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
10241 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
10242 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
10243 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
10244 <description><p
>Here is a small update for my English readers. Most of my blog
10245 posts have been in Norwegian the last few weeks, so here is a short
10246 update in English.
</p
>
10248 <p
>The kids still keep me too busy to get much free software work
10249 done, but I did manage to organise a project to get a Norwegian port
10250 of the British service
10251 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
10252 and it has been running for a month now. The entire project has been
10253 organised by me and two others. Around Christmas we gathered sponsors
10254 to fund the development work. In January I drafted a contract with
10255 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
10256 and in February the development took place. Most of it involved
10257 converting the source to use GPS coordinates instead of British
10258 easting/northing, and the resulting code should be a lot easier to get
10259 running in any country by now. The Norwegian
10260 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
10261 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
10262 source and the source for administrative borders in Norway, and
10263 support for this had to be added/fixed.
</p
>
10265 <p
>The Norwegian version went live March
3th, and we spent the weekend
10266 polishing the system before we announced it March
7th. The system is
10267 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
10268 problem reports in a few weeks. Soon we hope to announce the Android
10269 and iPhone versions making it even easier to report problems with the
10270 public infrastructure.
</p
>
10272 <p
>Perhaps something to consider for those of you in countries without
10273 such service?
</p
>
10278 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
10279 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
10280 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
10281 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
10282 <description><p
>The last few days I have looked at ways to track open security
10283 issues here at my work with the University of Oslo. My idea is that
10284 it should be possible to use the information about security issues
10285 available on the Internet, and check our locally
10286 maintained/distributed software against this information. It should
10287 allow us to verify that no known security issues are forgotten. The
10288 CVE database listing vulnerabilities seem like a great central point,
10289 and by using the package lists from Debian mapped to CVEs provided by
10290 the testing security team, I believed it should be possible to figure
10291 out which security holes were present in our free software
10292 collection.
</p
>
10294 <p
>After reading up on the topic, it became obvious that the first
10295 building block is to be able to name software packages in a unique and
10296 consistent way across data sources. I considered several ways to do
10297 this, for example coming up with my own naming scheme like using URLs
10298 to project home pages or URLs to the Freshmeat entries, or using some
10299 existing naming scheme. And it seem like I am not the first one to
10300 come across this problem, as MITRE already proposed and implemented a
10301 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
10302 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
10303 software, hardware and other platform components. The CPE ids are
10304 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
10305 Vulnerability Database
</a
>, allowing me to look up know security
10306 issues for any CPE name. With this in place, all I need to do is to
10307 locate the CPE id for the software packages we use at the university.
10308 This is fairly trivial (I google for
'cve cpe $package
' and check the
10309 NVD entry if a CVE for the package exist).
</p
>
10311 <p
>To give you an example. The GNU gzip source package have the CPE
10312 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
10313 check out, one could look up
10314 <a href=
"http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%
3A%
2Fa%
3Agnu%
3Agzip:
1.3.3">cpe:/a:gnu:gzip:
1.3.3
10315 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
10316 The most recent one is
10317 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
10318 and at the bottom of the NVD page for this vulnerability the complete
10319 list of affected versions is provided.
</p
>
10321 <p
>The NVD database of CVEs is also available as a XML dump, allowing
10322 for offline processing of issues. Using this dump, I
've written a
10323 small script taking a list of CPEs as input and list all CVEs
10324 affecting the packages represented by these CPEs. One give it CPEs
10325 with version numbers as specified above and get a list of open
10326 security issues out.
</p
>
10328 <p
>Of course for this approach to be useful, the quality of the NVD
10329 information need to be high. For that to happen, I believe as many as
10330 possible need to use and contribute to the NVD database. I notice
10332 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
10333 map from CVE to CPE
</a
>, indicating that they are using the CPE
10334 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
10336 <p
>To get an idea about the quality for free software, I spent some
10337 time making it possible to compare the CVE database from Debian with
10338 the CVE database in NVD. The result look fairly good, but there are
10339 some inconsistencies in NVD (same software package having several
10340 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
10341 Debian believe are affected by a CVE). Hope to find time to improve
10342 the quality of NVD, but that require being able to get in touch with
10343 someone maintaining it. So far my three emails with questions and
10344 corrections have not seen any reply, but I hope contact can be
10345 established soon.
</p
>
10347 <p
>An interesting application for CPEs is cross platform package
10348 mapping. It would be useful to know which packages in for example
10349 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
10350 this would be trivial if all linux distributions provided CPE entries
10351 for their packages.
</p
>
10356 <title>Which module is loaded for a given PCI and USB device?
</title>
10357 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
10358 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
10359 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
10360 <description><p
>In the
10361 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
10362 package in Debian, there is a script to report useful information
10363 about the running hardware for use when people report missing
10364 information. One part of this script that I find very useful when
10365 debugging hardware problems, is the part mapping loaded kernel module
10366 to the PCI device it claims. It allow me to quickly see if the kernel
10367 module I expect is driving the hardware I am struggling with. To see
10368 the output, make sure discover-data is installed and run
10369 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
10370 one of my machines like this:
</p
>
10374 10de:
03eb i2c_nforce2
10377 10de:
03f0 snd_hda_intel
10382 109e:
0878 snd_bt87x
10386 <p
>The code in question look like this, slightly modified for
10387 readability and to drop the output to file descriptor
3:
</p
>
10390 if [ -d /sys/bus/pci/devices/ ] ; then
10391 echo loaded pci modules:
10393 cd /sys/bus/pci/devices/
10394 for address in * ; do
10395 if [ -d
"$address/driver/module
" ] ; then
10396 module=`cd $address/driver/module ; pwd -P | xargs basename`
10397 if grep -q
"^$module
" /proc/modules ; then
10398 address=$(echo $address |sed s/
0000://)
10399 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
10400 echo
"$id $module
"
10409 <p
>Similar code could be used to extract USB device module
10410 mappings:
</p
>
10413 if [ -d /sys/bus/usb/devices/ ] ; then
10414 echo loaded usb modules:
10416 cd /sys/bus/usb/devices/
10417 for address in * ; do
10418 if [ -d
"$address/driver/module
" ] ; then
10419 module=`cd $address/driver/module ; pwd -P | xargs basename`
10420 if grep -q
"^$module
" /proc/modules ; then
10421 address=$(echo $address |sed s/
0000://)
10422 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
10423 if [
"$id
" ] ; then
10424 echo
"$id $module
"
10434 <p
>This might perhaps be something to include in other tools as
10440 <title>How to test if a laptop is working with Linux
</title>
10441 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
10442 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
10443 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
10444 <description><p
>The last few days I have spent at work here at the
<a
10445 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
10446 batch of computers will work with Linux. Every year for the last few
10447 years the university have organised shared bid of a few thousand
10448 computers, and this year HP won the bid. Two different desktops and
10449 five different laptops are on the list this year. We in the UNIX
10450 group want to know which one of these computers work well with RHEL
10451 and Ubuntu, the two Linux distributions we currently handle at the
10452 university.
</p
>
10454 <p
>My test method is simple, and I share it here to get feedback and
10455 perhaps inspire others to test hardware as well. To test, I PXE
10456 install the OS version of choice, and log in as my normal user and run
10457 a few applications and plug in selected pieces of hardware. When
10458 something fail, I make a note about this in the test matrix and move
10459 on. If I have some spare time I try to report the bug to the OS
10460 vendor, but as I only have the machines for a short time, I rarely
10461 have the time to do this for all the problems I find.
</p
>
10463 <p
>Anyway, to get to the point of this post. Here is the simple tests
10464 I perform on a new model.
</p
>
10468 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
10469 and Ubuntu Maverik at the moment. If I feel like it, I also test with
10470 RHEL5 and Debian Edu/Squeeze.
</li
>
10472 <li
>Is X.org working? If the graphical login screen show up after
10473 installation, X.org is working.
</li
>
10475 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
10476 package mesa-utils on Ubuntu) and writing down the frames per second
10477 reported by the program.
</li
>
10479 <li
>Is sound working? With Gnome and KDE, a sound is played when
10480 logging in, and if I can hear this the test is successful. If there
10481 are several audio exits on the machine, I try them all and check if
10482 the Gnome/KDE audio mixer can control where to send the sound. I
10483 normally test this by playing
10484 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
10485 video
</a
> in Firefox/Iceweasel.
</li
>
10487 <li
>Is the USB subsystem working? I test this by plugging in a USB
10488 memory stick and see if Gnome/KDE notices this.
</li
>
10490 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
10491 I have lying around, and see if Gnome/KDE notices this.
</li
>
10493 <li
>Is any built in camera working? Test using cheese, and see if a
10494 picture from the v4l device show up.
</li
>
10496 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
10497 any bluetooth devices are discovered. In my office, I normally see a
10500 <li
>For laptops, is the SD or Compaq Flash reader working. I have
10501 memory modules lying around, and stick them in and see if Gnome/KDE
10502 notice this.
</li
>
10504 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
10505 special button work, and if the laptop continue to work after
10508 <li
>For laptops, is the extra buttons working, like audio level,
10509 adjusting background light, switching on/off external video output,
10510 switching on/off wifi, bluetooth, etc? The set of buttons differ from
10511 laptop to laptop, so I just write down which are working and which are
10514 <li
>Some laptops have smart card readers, finger print readers,
10515 acceleration sensors etc. I rarely test these, as I do not know how
10516 to quickly test if they are working or not, so I only document their
10517 existence.
</li
>
10521 <p
>By now I suspect you are really curious what the test results are
10522 for the HP machines I am testing. I
'm not done yet, so I will report
10523 the test results later. For now I can report that HP
8100 Elite work
10524 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
10525 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
10526 can see, I have most machines left to test. One interesting
10527 observation is that Ubuntu Lucid has almost twice the frame rate than
10528 RHEL6 with glxgears. No idea why.
</p
>
10533 <title>Some thoughts on BitCoins
</title>
10534 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
10535 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
10536 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
10537 <description><p
>As I continue to explore
10538 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
10539 what properties the system have, and how it will be affected by laws
10540 and regulations here in Norway. Here are some random notes.
</p
>
10542 <p
>One interesting thing to note is that since the transactions are
10543 verified using a peer to peer network, all details about a transaction
10544 is known to everyone. This means that if a BitCoin address has been
10545 published like I did with mine in my initial post about BitCoin, it is
10546 possible for everyone to see how many BitCoins have been transfered to
10547 that address. There is even a web service to look at the details for
10548 all transactions. There I can see that my address
10549 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
10550 have received
16.06 Bitcoin, the
10551 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
10552 address of Simon Phipps have received
181.97 BitCoin and the address
10553 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
10554 of EFF have received
2447.38 BitCoins so far. Thank you to each and
10555 every one of you that donated bitcoins to support my activity. The
10556 fact that anyone can see how much money was transfered to a given
10557 address make it more obvious why the BitCoin community recommend to
10558 generate and hand out a new address for each transaction. I
'm told
10559 there is no way to track which addresses belong to a given person or
10560 organisation without the person or organisation revealing it
10561 themselves, as Simon, EFF and I have done.
</p
>
10563 <p
>In Norway, and in most other countries, there are laws and
10564 regulations limiting how much money one can transfer across the border
10565 without declaring it. There are money laundering, tax and accounting
10566 laws and regulations I would expect to apply to the use of BitCoin.
10567 If the Skolelinux foundation
10568 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
10569 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
10570 normal bank transfers like EFF is doing, how should this be accounted?
10571 Given that it is impossible to know if money can cross the border or
10572 not, should everything or nothing be declared? What exchange rate
10573 should be used when calculating taxes? Would receivers have to pay
10574 income tax if the foundation were to pay Skolelinux contributors in
10575 BitCoin? I have no idea, but it would be interesting to know.
</p
>
10577 <p
>For a currency to be useful and successful, it must be trusted and
10578 accepted by a lot of users. It must be possible to get easy access to
10579 the currency (as a wage or using currency exchanges), and it must be
10580 easy to spend it. At the moment BitCoin seem fairly easy to get
10581 access to, but there are very few places to spend it. I am not really
10582 a regular user of any of the vendor types currently accepting BitCoin,
10583 so I wonder when my kind of shop would start accepting BitCoins. I
10584 would like to buy electronics, travels and subway tickets, not herbs
10585 and books. :) The currency is young, and this will improve over time
10586 if it become popular, but I suspect regular banks will start to lobby
10587 to get BitCoin declared illegal if it become popular. I
'm sure they
10588 will claim it is helping fund terrorism and money laundering (which
10589 probably would be true, as is any currency in existence), but I
10590 believe the problems should be solved elsewhere and not by blaming
10591 currencies.
</p
>
10593 <p
>The process of creating new BitCoins is called mining, and it is
10594 CPU intensive process that depend on a bit of luck as well (as one is
10595 competing against all the other miners currently spending CPU cycles
10596 to see which one get the next lump of cash). The
"winner
" get
50
10597 BitCoin when this happen. Yesterday I came across the obvious way to
10598 join forces to increase ones changes of getting at least some coins,
10599 by coordinating the work on mining BitCoins across several machines
10600 and people, and sharing the result if one is lucky and get the
50
10601 BitCoins. Check out
10602 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
10603 if this sounds interesting. I have not had time to try to set up a
10604 machine to participate there yet, but have seen that running on ones
10605 own for a few days have not yield any BitCoins througth mining
10608 <p
>Update
2010-
12-
15: Found an
<a
10609 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
10610 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
10611 it was interesting to read. The arguments presented seem to be
10612 equally valid for gold, which was used as a currency for many years.
</p
>
10617 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
10618 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
10619 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
10620 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
10621 <description><p
>With this weeks lawless
10622 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
10623 attacks
</a
> on Wikileak and
10624 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
10625 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
10626 not be trusted to handle money transactions.
10628 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
10629 Phipps on bitcoin
</a
> reminded me about a project that a friend of
10630 mine mentioned earlier. I decided to follow Simon
's example, and get
10631 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
10632 some help from my friend to get it all running, and he even handed me
10633 some bitcoins to get started. I even donated a few bitcoins to Simon
10634 for helping me remember BitCoin.
</p
>
10636 <p
>So, what is bitcoins, you probably wonder? It is a digital
10637 crypto-currency, decentralised and handled using peer-to-peer
10638 networks. It allows anonymous transactions and prohibits central
10639 control over the transactions, making it impossible for governments
10640 and companies alike to block donations and other transactions. The
10641 source is free software, and while the key dependency wxWidgets
2.9
10642 for the graphical user interface is missing in Debian, the command
10643 line client builds just fine. Hopefully Jonas
10644 <a href=
"http://bugs.debian.org/
578157">will get the package into
10645 Debian
</a
> soon.
</p
>
10647 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
10648 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
10649 bitcoins
</a
> when selling services and goods, and there are even
10650 currency
"stock
" markets where the exchange rate is decided. There
10651 are not many users so far, but the concept seems promising. If you
10652 want to get started and lack a friend with any bitcoins to spare,
10654 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
10655 bitcoin at the time of writing). Use
10656 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
10657 on the current exchange rates.
</p
>
10659 <p
>As an experiment, I have decided to set up bitcoind on one of my
10660 machines. If you want to support my activity, please send Bitcoin
10661 donations to the address
10662 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
10667 <title>Why isn
't Debian Edu using VLC?
</title>
10668 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
10669 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
10670 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
10671 <description><p
>In the latest issue of Linux Journal, the readers choices were
10672 presented, and the winner among the multimedia player were VLC.
10673 Personally, I like VLC, and it is my player of choice when I first try
10674 to play a video file or stream. Only if VLC fail will I drag out
10675 gmplayer to see if it can do better. The reason is mostly the failure
10676 model and trust. When VLC fail, it normally pop up a error message
10677 reporting the problem. When mplayer fail, it normally segfault or
10678 just hangs. The latter failure mode drain my trust in the program.
<p
>
10680 <p
>But even if VLC is my player of choice, we have choosen to use
10681 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
10682 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
10683 plugin to play web videos seamlessly, and the VLC browser plugin is
10684 not very good. For example, it lack in-line control buttons, so there
10685 is no way for the user to pause the video. Also, when I
10686 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
10687 tested the browser plugins
</a
> available in Debian, the VLC plugin
10688 failed on several video pages where mplayer based plugins worked. If
10689 the browser plugin for VLC was as good as the gecko-mediaplayer
10690 package (which uses mplayer), we would switch.
</P
>
10692 <p
>While VLC is a good player, its user interface is slightly
10693 annoying. The most annoying feature is its inconsistent use of
10694 keyboard shortcuts. When the player is in full screen mode, its
10695 shortcuts are different from when it is playing the video in a window.
10696 For example, space only work as pause when in full screen mode. I
10697 wish it had consisten shortcuts and that space also would work when in
10698 window mode. Another nice shortcut in gmplayer is [enter] to restart
10699 the current video. It is very nice when playing short videos from the
10700 web and want to restart it when new people arrive to have a look at
10701 what is going on.
</p
>
10706 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
10707 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
10708 <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>
10709 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
10710 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
10711 upgrade testing of the
10712 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10713 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
10714 This seem like a very good idea, so I adjusted by test scripts and
10715 can now present the updated result from today:
</p
>
10717 <p
>This is for Gnome:
</p
>
10719 <p
>Installed using apt-get, missing with aptitude
</p
>
10721 <blockquote
><p
>
10726 browser-plugin-gnash
10733 freedesktop-sound-theme
10735 gconf-defaults-service
10748 gnome-codec-install
10750 gnome-desktop-environment
10754 gnome-session-canberra
10756 gnome-themes-extras
10759 gstreamer0.10-fluendo-mp3
10760 gstreamer0.10-tools
10762 gtk2-engines-pixbuf
10763 gtk2-engines-smooth
10765 libapache2-mod-dnssd
10768 libaprutil1-dbd-sqlite3
10771 libboost-date-time1.42
.0
10772 libboost-python1.42
.0
10773 libboost-thread1.42
.0
10775 libchamplain-gtk-
0.4-
0
10777 libclutter-gtk-
0.10-
0
10784 libfreerdp-plugins-standard
10797 libgnome-vfs2.0-cil
10799 libgnomepanel2.24-cil
10804 libgtksourceview2.0-common
10805 libmono-addins-gui0.2-cil
10806 libmono-addins0.2-cil
10807 libmono-cairo2.0-cil
10808 libmono-corlib2.0-cil
10809 libmono-i18n-west2.0-cil
10810 libmono-posix2.0-cil
10811 libmono-security2.0-cil
10812 libmono-sharpzip2.84-cil
10813 libmono-system2.0-cil
10816 libndesk-dbus-glib1.0-cil
10817 libndesk-dbus1.0-cil
10827 libtelepathy-farsight0
10836 nautilus-sendto-empathy
10840 python-aptdaemon-gtk
10842 python-beautifulsoup
10857 python-gtksourceview2
10868 python-pkg-resources
10875 python-twisted-conch
10876 python-twisted-core
10881 python-zope.interface
10883 remmina-plugin-data
10886 rhythmbox-plugin-cdrecorder
10893 system-config-printer-udev
10895 telepathy-mission-control-
5
10902 transmission-common
10906 </p
></blockquote
>
10908 <p
>Installed using apt-get, removed with aptitude
</p
>
10910 <blockquote
><p
>
10914 epiphany-extensions
10916 fast-user-switch-applet
10935 libgtksourceview2.0-
0
10937 libsdl1.2debian-alsa
10943 system-config-printer
10948 </p
></blockquote
>
10950 <p
>Installed using aptitude, missing with apt-get
</p
>
10952 <blockquote
><p
>
10953 gstreamer0.10-gnomevfs
10954 </p
></blockquote
>
10956 <p
>Installed using aptitude, removed with apt-get
</p
>
10958 <blockquote
><p
>
10960 </p
></blockquote
>
10962 <p
>This is for KDE:
</p
>
10964 <p
>Installed using apt-get, missing with aptitude
</p
>
10966 <blockquote
><p
>
10968 </p
></blockquote
>
10970 <p
>Installed using apt-get, removed with aptitude
</p
>
10972 <blockquote
><p
>
10974 network-manager-kde
10975 </p
></blockquote
>
10977 <p
>Installed using aptitude, missing with apt-get
</p
>
10979 <blockquote
><p
>
10993 kdeartwork-emoticons
10995 kdeartwork-theme-icon
10999 kdebase-workspace-bin
11000 kdebase-workspace-data
11012 konqueror-nsplugins
11014 kscreensaver-xsavers
11029 plasma-dataengines-workspace
11031 plasma-desktopthemes-artwork
11032 plasma-runners-addons
11033 plasma-scriptengine-googlegadgets
11034 plasma-scriptengine-python
11035 plasma-scriptengine-qedje
11036 plasma-scriptengine-ruby
11037 plasma-scriptengine-webkit
11038 plasma-scriptengines
11039 plasma-wallpapers-addons
11040 plasma-widget-folderview
11041 plasma-widget-networkmanagement
11044 update-notifier-kde
11045 xscreensaver-data-extra
11047 xscreensaver-gl-extra
11048 xscreensaver-screensaver-bsod
11049 </p
></blockquote
>
11051 <p
>Installed using aptitude, removed with apt-get
</p
>
11053 <blockquote
><p
>
11055 google-gadgets-common
11073 libggadget-qt-
1.0-
0b
11078 libkonqsidebarplugin4a
11082 libkunitconversion4
11087 libplasma-geolocation-interface4
11089 libplasmagenericshell4
11103 libsmokeknewstuff2-
3
11104 libsmokeknewstuff3-
3
11106 libsmokektexteditor3
11114 libsmokeqtnetwork4-
3
11115 libsmokeqtopengl4-
3
11116 libsmokeqtscript4-
3
11120 libsmokeqtuitools4-
3
11121 libsmokeqtwebkit4-
3
11132 plasma-dataengines-addons
11133 plasma-scriptengine-superkaramba
11134 plasma-widget-lancelot
11135 plasma-widgets-addons
11136 plasma-widgets-workspace
11140 update-notifier-common
11141 </p
></blockquote
>
11143 <p
>Running apt-get autoremove made the results using apt-get and
11144 aptitude a bit more similar, but there are still quite a lott of
11145 differences. I have no idea what packages should be installed after
11146 the upgrade, but hope those that do can have a look.
</p
>
11151 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
11152 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
11153 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
11154 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
11155 <description><p
>Most of the computers in use by the
11156 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
11157 are virtual machines. And they have been Xen machines running on a
11158 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
11159 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
11160 bit harder that it could have been, because we set up the Xen virtual
11161 machines to get the virtual partitions from LVM, which as far as I
11162 know is not supported by KVM. So to migrate, we had to convert
11163 several LVM logical volumes to partitions on a virtual disk file.
</p
>
11166 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
11167 nice recipe
</a
> to do this, and wrote the following script to do the
11168 migration. It uses qemu-img from the qemu package to make the disk
11169 image, parted to partition it, losetup and kpartx to present the disk
11170 image partions as devices, and dd to copy the data. I NFS mounted the
11171 new servers storage area on the old server to do the migration.
</p
>
11177 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
11182 if [ -z
"$
1" ] ; then
11183 echo
"Usage: $
0 &lt;hostname
&gt;
"
11186 host=
"$
1"
11189 if [ ! -e /dev/vg_data/$host-disk ] ; then
11190 echo
"error: unable to find LVM volume for $host
"
11194 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
11195 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
11196 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
11197 totalsize=$(( ( $disksize + $swapsize ) ))
11200 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
11201 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
11203 parted $img mklabel msdos
11204 parted $img mkpart primary linux-swap
0 $disksize
11205 parted $img mkpart primary ext2 $disksize $totalsize
11206 parted $img set
1 boot on
11209 losetup /dev/loop0 $img
11210 kpartx -a /dev/loop0
11212 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
11213 fsck.ext3 -f /dev/mapper/loop0p1 || true
11214 mkswap /dev/mapper/loop0p2
11216 kpartx -d /dev/loop0
11217 losetup -d /dev/loop0
11220 <p
>The script is perhaps so simple that it is not copyrightable, but
11221 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
11223 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
11224 the new disk image attached, installed grub-pc and linux-image-
686 and
11225 set up grub to boot from the disk image. After this, the KVM machines
11226 seem to work just fine.
</p
>
11231 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
11232 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
11233 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
11234 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
11235 <description><p
>I
'm still running upgrade testing of the
11236 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
11237 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
11238 status. Here is a short update based on a test I ran
20101118.
</p
>
11240 <p
>I still do not know what a correct migration should look like, so I
11241 report any differences between apt and aptitude and hope someone else
11242 can see if anything should be changed.
</p
>
11244 <p
>This is for Gnome:
</p
>
11246 <p
>Installed using apt-get, missing with aptitude
</p
>
11248 <blockquote
><p
>
11249 apache2.2-bin aptdaemon at-spi baobab binfmt-support
11250 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
11251 dmz-cursor-theme empathy empathy-common finger
11252 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
11253 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
11254 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
11255 gnome-cards-data gnome-codec-install gnome-core
11256 gnome-desktop-environment gnome-disk-utility gnome-screenshot
11257 gnome-search-tool gnome-session-canberra gnome-spell
11258 gnome-system-log gnome-themes-extras gnome-themes-more
11259 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
11260 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
11261 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
11262 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
11263 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
11264 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
11265 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
11266 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
11267 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
11268 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
11269 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
11270 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
11271 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
11272 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
11273 libgtk2.0-cil libgtkglext1 libgtksourceview-common
11274 libgtksourceview2.0-common libmono-addins-gui0.2-cil
11275 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
11276 libmono-i18n-west2.0-cil libmono-posix2.0-cil
11277 libmono-security2.0-cil libmono-sharpzip2.84-cil
11278 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
11279 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
11280 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
11281 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
11282 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
11283 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
11284 libxalan2-java libxerces2-java media-player-info mesa-utils
11285 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
11286 nautilus-sendto-empathy openoffice.org-writer2latex
11287 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
11288 python-aptdaemon python-aptdaemon-gtk python-axiom
11289 python-beautifulsoup python-bugbuddy python-clientform
11290 python-coherence python-configobj python-crypto python-cupshelpers
11291 python-cupsutils python-eggtrayicon python-elementtree
11292 python-epsilon python-evolution python-feedparser python-gdata
11293 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
11294 python-gtksourceview2 python-httplib2 python-louie python-mako
11295 python-markupsafe python-mechanize python-nevow python-notify
11296 python-opengl python-openssl python-pam python-pkg-resources
11297 python-pyasn1 python-pysqlite2 python-rdflib python-serial
11298 python-tagpy python-twisted-bin python-twisted-conch
11299 python-twisted-core python-twisted-web python-utidylib python-webkit
11300 python-xdg python-zope.interface remmina remmina-plugin-data
11301 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
11302 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
11303 software-center svgalibg1 system-config-printer-udev
11304 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
11305 totem totem-coherence totem-mozilla totem-plugins
11306 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
11308 </p
></blockquote
>
11310 Installed using apt-get, removed with aptitude
11312 <blockquote
><p
>
11313 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
11314 epiphany-extensions epiphany-gecko evolution-exchange
11315 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
11316 gedit-common gnome-app-install gnome-games gnome-games-data
11317 gnome-nettool gnome-system-tools gnome-themes gnome-utils
11318 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
11319 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
11320 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
11321 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
11322 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
11323 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
11324 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
11325 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
11326 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
11327 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
11328 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
11329 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
11330 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
11331 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
11332 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
11333 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
11334 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
11335 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
11336 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
11337 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
11338 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
11339 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
11340 sound-juicer swfdec-gnome system-config-printer totem-common
11341 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
11342 </p
></blockquote
>
11344 <p
>Installed using aptitude, missing with apt-get
</p
>
11346 <blockquote
><p
>
11347 gstreamer0.10-gnomevfs
11348 </p
></blockquote
>
11350 <p
>Installed using aptitude, removed with apt-get
</p
>
11352 <blockquote
><p
>
11354 </p
></blockquote
>
11356 <p
>This is for KDE:
</p
>
11358 <p
>Installed using apt-get, missing with aptitude
</p
>
11360 <blockquote
><p
>
11361 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
11362 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
11363 ghostscript-x git gnome-audio gnugo granatier gs-common
11364 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
11365 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
11366 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
11367 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11368 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
11369 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
11370 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11371 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
11372 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
11373 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
11374 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
11375 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
11376 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
11377 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
11378 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
11379 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
11380 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
11381 libkrossui4 libmailtools-perl libmime-tools-perl
11382 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
11383 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
11384 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
11385 lirc luatex marble networkstatus noatun-plugins
11386 openoffice.org-writer2latex palapeli palapeli-data parley
11387 parley-data poster psutils pulseaudio pulseaudio-esound-compat
11388 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
11389 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
11390 ttf-sazanami-gothic
11391 </p
></blockquote
>
11393 <p
>Installed using apt-get, removed with aptitude
</p
>
11395 <blockquote
><p
>
11396 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
11397 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
11398 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
11399 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
11400 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
11401 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
11402 kitchensync kiten kjumpingcube klatin klettres klickety klines
11403 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
11404 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
11405 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
11406 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
11407 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
11408 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
11409 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
11410 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
11411 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11412 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
11413 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
11414 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11415 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
11416 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
11417 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
11418 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
11419 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11420 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
11421 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
11422 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
11423 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
11424 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
11425 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
11426 mpeglib network-manager-kde noatun pmount tex-common texlive-base
11427 texlive-common texlive-doc-base texlive-fonts-recommended tidy
11428 ttf-dustin ttf-kochi-gothic ttf-sjfonts
11429 </p
></blockquote
>
11431 <p
>Installed using aptitude, missing with apt-get
</p
>
11433 <blockquote
><p
>
11434 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
11435 kdeartwork kdebase kdebase-apps kdebase-workspace
11436 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
11437 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
11438 netpbm plasma-widget-folderview plasma-widget-networkmanagement
11439 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
11440 xscreensaver-screensaver-bsod
11441 </p
></blockquote
>
11443 <p
>Installed using aptitude, removed with apt-get
</p
>
11445 <blockquote
><p
>
11446 kdebase-bin konq-plugins konqueror
11447 </p
></blockquote
>
11452 <title>Gnash buildbot slave and Debian kfreebsd
</title>
11453 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
11454 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
11455 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
11456 <description><p
>Answering
11457 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
11458 call from the Gnash project
</a
> for
11459 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
11460 current source, I have set up a virtual KVM machine on the Debian
11461 Edu/Skolelinux virtualization host to test the git source on
11462 Debian/Squeeze. I hope this can help the developers in getting new
11463 releases out more often.
</p
>
11465 <p
>As the developers want less main-stream build platforms tested to,
11466 I have considered setting up a
<a
11467 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
11468 machine as well. I have also considered using the kfreebsd
11469 architecture in Debian as a file server in NUUG to get access to the
5
11470 TB zfs volume we currently use to store DV video. Because of this, I
11471 finally got around to do a test installation of Debian/Squeeze with
11472 kfreebsd. Installation went fairly smooth, thought I noticed some
11473 visual glitches in the cdebconf dialogs (black cursor left on the
11474 screen at random locations). Have not gotten very far with the
11475 testing. Noticed cfdisk did not work, but fdisk did so it was not a
11476 fatal problem. Have to spend some more time on it to see if it is
11477 useful as a file server for NUUG. Will try to find time to set up a
11478 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
11483 <title>Debian in
3D
</title>
11484 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
11485 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
11486 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
11487 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
11489 <p
>3D printing is just great. I just came across this Debian logo in
11491 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
11492 thingiverse blog
</a
>.
</p
>
11497 <title>Software updates
2010-
10-
24</title>
11498 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
11499 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
11500 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
11501 <description><p
>Some updates.
</p
>
11503 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
11504 raise money for the project is going well. The lower limit of
10
11505 signers was reached in
24 hours, and so far
13 people have signed it.
11506 More signers and more funding is most welcome, and I am really curious
11507 how far we can get before the time limit of December
24 is reached.
11510 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
11511 about what appear to be a great code coverage tool capable of
11512 generating code coverage stats without any changes to the source code.
11514 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
11515 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
11516 It is missing in Debian, but the git source built just fine in Squeeze
11517 after I installed libelf-dev, libdwarf-dev, pkg-config and
11518 libglib2.0-dev. Failed to build in Lenny, but suspect that is
11519 solvable. I hope kcov make it into Debian soon.
</p
>
11521 <p
>Finally found time to wrap up the release notes for
<a
11522 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
11523 new alpha release of Debian Edu
</a
>, and just published the second
11524 alpha test release of the Squeeze based Debian Edu /
11525 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
11526 release. Give it a try if you need a complete linux solution for your
11527 school, including central infrastructure server, workstations, thin
11528 client servers and diskless workstations. A nice touch added
11529 yesterday is RDP support on the thin client servers, for windows
11530 clients to get a Linux desktop on request.
</p
>
11535 <title>Some notes on Flash in Debian and Debian Edu
</title>
11536 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
11537 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
11538 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
11539 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
11540 popularity-contest numbers
</a
>, the adobe-flashplugin package the
11541 second most popular used package that is missing in Debian. The sixth
11542 most popular is flashplayer-mozilla. This is a clear indication that
11543 working flash is important for Debian users. Around
10 percent of the
11544 users submitting data to popcon.debian.org have this package
11545 installed.
</p
>
11547 <p
>In the report written by Lars Risan in August
2008
11548 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
11549 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11550 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
11551 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
11552 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
11553 web sites require Flash to work, and lacking working Flash support in
11554 the web browser and the problems with installing it was perceived as a
11555 good reason to stay with Windows.
</p
>
11557 <p
>I once saw a funny and sad comment in a web forum, where Linux was
11558 said to be the retarded cousin that did not really understand
11559 everything you told him but could work fairly well. This was a
11560 comment regarding the problems Linux have with proprietary formats and
11561 non-standard web pages, and is sad because it exposes a fairly common
11562 understanding of whose fault it is if web pages that only work in for
11563 example Internet Explorer
6 fail to work on Firefox, and funny because
11564 it explain very well how annoying it is for users when Linux
11565 distributions do not work with the documents they receive or the web
11566 pages they want to visit.
</p
>
11568 <p
>This is part of the reason why I believe it is important for Debian
11569 and Debian Edu to have a well working Flash implementation in the
11570 distribution, to get at least popular sites as Youtube and Google
11571 Video to working out of the box. For Squeeze, Debian have the chance
11572 to include the latest version of Gnash that will make this happen, as
11573 the new release
0.8.8 was published a few weeks ago and is resting in
11574 unstable. The new version work with more sites that version
0.8.7.
11575 The Gnash maintainers have asked for a freeze exception, but the
11576 release team have not had time to reply to it yet. I hope they agree
11577 with me that Flash is important for the Debian desktop users, and thus
11578 accept the new package into Squeeze.
</p
>
11583 <title>Circular package dependencies harms apt recovery
</title>
11584 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
11585 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
11586 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
11587 <description><p
>I discovered this while doing
11588 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
11589 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
11590 in Debian still got circular dependencies, and it is often claimed
11591 that apt and aptitude should be able to handle this just fine, but
11592 some times these dependency loops causes apt to fail.
</p
>
11594 <p
>An example is from todays
11595 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
11596 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
11597 causes perl-modules to fail to upgrade. The cause is simple. If a
11598 package fail to unpack, then only part of packages with the circular
11599 dependency might end up being unpacked when unpacking aborts, and the
11600 ones already unpacked will fail to configure in the recovery phase
11601 because its dependencies are unavailable.
</p
>
11603 <p
>In this log, the problem manifest itself with this error:
</p
>
11605 <blockquote
><pre
>
11606 dpkg: dependency problems prevent configuration of perl-modules:
11607 perl-modules depends on perl (
>=
5.10.1-
1); however:
11608 Version of perl on system is
5.10.0-
19lenny
2.
11609 dpkg: error processing perl-modules (--configure):
11610 dependency problems - leaving unconfigured
11611 </pre
></blockquote
>
11613 <p
>The perl/perl-modules circular dependency is already
11614 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
11615 hopefully be solved as soon as possible, but it is not the only one,
11616 and each one of these loops in the dependency tree can cause similar
11617 failures. Of course, they only occur when there are bugs in other
11618 packages causing the unpacking to fail, but it is rather nasty when
11619 the failure of one package causes the problem to become worse because
11620 of dependency loops.
</p
>
11623 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
11624 tireless effort by Bill Allombert
</a
>, the number of circular
11626 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
11627 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
11629 <p
>Todays testing also exposed a bug in
11630 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
11631 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
11632 apt-get and aptitude, the latter possibly caused by some circular
11633 dependency. Reported both to BTS to try to get someone to look at
11639 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
11640 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
11641 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
11642 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
11643 <description><p
>This is a
11644 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
11646 <a href=
"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
">previous
11648 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
11649 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
11651 <p
>As a step to try to see if it possible to merge the DNS and DHCP
11652 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11653 and dhcp3-server-ldap in Debian use the LDAP server. The two
11654 implementations are quite different in how they use LDAP.
</p
>
11656 To get this information, I started slapd with debugging enabled and
11657 dumped the debug output to a file to get the LDAP searches performed
11658 on a Debian Edu main-server. Here is a summary.
11660 <p
><strong
>powerdns
</strong
></p
>
11662 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
11663 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
11666 <p
>PowerDNS have two modes of operation using LDAP as its backend.
11667 One
"strict
" mode where the forward and reverse DNS lookups are done
11668 using the same LDAP objects, and a
"tree
" mode where the forward and
11669 reverse entries are in two different subtrees in LDAP with a structure
11670 based on the DNS names, as in tjener.intern and
11671 2.2.0.10.in-addr.arpa.
</p
>
11673 <p
>In tree mode, the server is set up to use a LDAP subtree as its
11674 base, and uses a
"base
" scoped search for the DNS name by adding
11675 "dc=tjener,dc=intern,
" to the base with a filter for
11676 "(associateddomain=tjener.intern)
" for the forward entry and
11677 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
11678 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
11679 forward entries, it is looking for attributes named dnsttl, arecord,
11680 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11681 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11682 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11683 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11684 spfrecord and modifytimestamp. For reverse entries it is looking for
11685 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11686 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11687 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11688 ldapsearch commands could look like this:
</p
>
11690 <blockquote
><pre
>
11691 ldapsearch -h ldap \
11692 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11693 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11694 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11695 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11696 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11697 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11699 ldapsearch -h ldap \
11700 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11701 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
11702 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11703 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11704 srvrecord naptrrecord modifytimestamp
11705 </pre
></blockquote
>
11707 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
11708 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11709 example LDAP objects used there. In addition to these objects, the
11710 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11711 also exist.
</p
>
11713 <blockquote
><pre
>
11714 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11716 objectclass: dnsdomain
11717 objectclass: domainrelatedobject
11720 associateddomain: tjener.intern
11722 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11724 objectclass: dnsdomain2
11725 objectclass: domainrelatedobject
11727 ptrrecord: tjener.intern
11728 associateddomain:
2.2.0.10.in-addr.arpa
11729 </pre
></blockquote
>
11731 <p
>In strict mode, the server behaves differently. When looking for
11732 forward DNS entries, it is doing a
"subtree
" scoped search with the
11733 same base as in the tree mode for a object with filter
11734 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
11735 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11736 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11737 naptrrecord and modifytimestamp. For reverse entires it also do a
11738 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
11739 and the requested attributes are associateddomain, dnsttl and
11740 modifytimestamp. In short, in strict mode the objects with ptrrecord
11741 go away, and the arecord attribute in the forward object is used
11744 <p
>The forward and reverse searches can be simulated using ldapsearch
11745 like this:
</p
>
11747 <blockquote
><pre
>
11748 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11749 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11750 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11751 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11752 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11753 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11755 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11756 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
11757 </pre
></blockquote
>
11759 <p
>In addition to the forward and reverse searches , there is also a
11760 search for SOA records, which behave similar to the forward and
11761 reverse lookups.
</p
>
11763 <p
>A thing to note with the PowerDNS behaviour is that it do not
11764 specify any objectclass names, and instead look for the attributes it
11765 need to generate a DNS reply. This make it able to work with any
11766 objectclass that provide the needed attributes.
</p
>
11768 <p
>The attributes are normally provided in the cosine (RFC
1274) and
11769 dnsdomain2 schemas. The latter is used for reverse entries like
11770 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
11772 <p
>In Debian Edu, we have created DNS objects using the object classes
11773 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11774 attributes) and domainrelatedobject (for associatedDomain). The use
11775 of structural object classes make it impossible to combine these
11776 classes with the object classes used by DHCP.
</p
>
11778 <p
>There are other schemas that could be used too, for example the
11779 dnszone structural object class used by Gosa and bind-sdb for the DNS
11780 attributes combined with the domainrelatedobject object class, but in
11781 this case some unused attributes would have to be included as well
11782 (zonename and relativedomainname).
</p
>
11784 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
11785 mode and not use any of the existing objectclasses (dnsdomain,
11786 dnsdomain2 and dnszone) when one want to combine the DNS information
11787 with DHCP information, and instead create a auxiliary object class
11788 defined something like this (using the attributes defined for
11789 dnsdomain and dnsdomain2 or dnszone):
</p
>
11791 <blockquote
><pre
>
11792 objectclass ( some-oid NAME
'dnsDomainAux
'
11795 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11796 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11797 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11798 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11799 A6Record $ DNAMERecord
11801 </pre
></blockquote
>
11803 <p
>This will allow any object to become a DNS entry when combined with
11804 the domainrelatedobject object class, and allow any entity to include
11805 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
11806 developers asking for their view on this schema and if they are
11807 interested in providing such schema with PowerDNS, and I hope my
11808 message will be accepted into their mailing list soon.
</p
>
11810 <p
><strong
>ISC dhcp
</strong
></p
>
11812 <p
>The DHCP server searches for specific objectclass and requests all
11813 the object attributes, and then uses the attributes it want. This
11814 make it harder to figure out exactly what attributes are used, but
11815 thanks to the working example in Debian Edu I can at least get an idea
11816 what is needed without having to read the source code.
</p
>
11818 <p
>In the DHCP server configuration, the LDAP base to use and the
11819 search filter to use to locate the correct dhcpServer entity is
11820 stored. These are the relevant entries from
11821 /etc/dhcp3/dhcpd.conf:
</p
>
11823 <blockquote
><pre
>
11824 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
11825 ldap-dhcp-server-cn
"dhcp
";
11826 </pre
></blockquote
>
11828 <p
>The DHCP server uses this information to nest all the DHCP
11829 configuration it need. The cn
"dhcp
" is located using the given LDAP
11830 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
11831 search result is this entry:
</p
>
11833 <blockquote
><pre
>
11834 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11837 objectClass: dhcpServer
11838 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11839 </pre
></blockquote
>
11841 <p
>The content of the dhcpServiceDN attribute is next used to locate the
11842 subtree with DHCP configuration. The DHCP configuration subtree base
11843 is located using a base scope search with base
"cn=DHCP
11844 Config,dc=skole,dc=skolelinux,dc=no
" and filter
11845 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
11846 The search result is this entry:
</p
>
11848 <blockquote
><pre
>
11849 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11852 objectClass: dhcpService
11853 objectClass: dhcpOptions
11854 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11855 dhcpStatements: ddns-update-style none
11856 dhcpStatements: authoritative
11857 dhcpOption: smtp-server code
69 = array of ip-address
11858 dhcpOption: www-server code
72 = array of ip-address
11859 dhcpOption: wpad-url code
252 = text
11860 </pre
></blockquote
>
11862 <p
>Next, the entire subtree is processed, one level at the time. When
11863 all the DHCP configuration is loaded, it is ready to receive requests.
11864 The subtree in Debian Edu contain objects with object classes
11865 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11866 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11867 and information about netmasks, dynamic range etc. Leaving out the
11868 details here because it is not relevant for the focus of my
11869 investigation, which is to see if it is possible to merge dns and dhcp
11870 related computer objects.
</p
>
11872 <p
>When a DHCP request come in, LDAP is searched for the MAC address
11873 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
11874 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
11875 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11876 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
11879 <blockquote
><pre
>
11880 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11883 objectClass: dhcpHost
11884 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11885 dhcpStatements: fixed-address hostname
11886 </pre
></blockquote
>
11888 <p
>There is less flexiblity in the way LDAP searches are done here.
11889 The object classes need to have fixed names, and the configuration
11890 need to be stored in a fairly specific LDAP structure. On the
11891 positive side, the invidiual dhcpHost entires can be anywhere without
11892 the DN pointed to by the dhcpServer entries. The latter should make
11893 it possible to group all host entries in a subtree next to the
11894 configuration entries, and this subtree can also be shared with the
11895 DNS server if the schema proposed above is combined with the dhcpHost
11896 structural object class.
11898 <p
><strong
>Conclusion
</strong
></p
>
11900 <p
>The PowerDNS implementation seem to be very flexible when it come
11901 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
11902 come to the the LDAP structure, the
"strict
" mode is very flexible,
11903 allowing DNS objects to be stored anywhere under the base cn specified
11904 in the configuration.
</p
>
11906 <p
>The DHCP implementation on the other hand is very inflexible, both
11907 regarding which LDAP schemas to use and which LDAP structure to use.
11908 I guess one could implement ones own schema, as long as the
11909 objectclasses and attributes have the names used, but this do not
11910 really help when the DHCP subtree need to have a fairly fixed
11911 structure.
</p
>
11913 <p
>Based on the observed behaviour, I suspect a LDAP structure like
11914 this might work for Debian Edu:
</p
>
11916 <blockquote
><pre
>
11918 cn=machine-info (dhcpService) - dhcpServiceDN points here
11919 cn=dhcp (dhcpServer)
11920 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11921 cn=
10.0.2.0 (dhcpSubnet)
11922 cn=group1 (dhcpGroup/dhcpOptions)
11923 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11924 cn=
192.168.0.0 (dhcpSubnet)
11925 cn=group1 (dhcpGroup/dhcpOptions)
11926 ou=machines - PowerDNS base points here
11927 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11928 </pre
></blockquote
>
11930 <P
>This is not tested yet. If the DHCP server require the dhcpHost
11931 entries to be in the dhcpGroup subtrees, the entries can be stored
11932 there instead of a common machines subtree, and the PowerDNS base
11933 would have to be moved one level up to the machine-info subtree.
</p
>
11935 <p
>The combined object under the machines subtree would look something
11936 like this:
</p
>
11938 <blockquote
><pre
>
11939 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11942 objectClass: dhcpHost
11943 objectclass: domainrelatedobject
11944 objectclass: dnsDomainAux
11945 associateddomain: hostname.intern
11946 arecord:
10.11.12.13
11947 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11948 dhcpStatements: fixed-address hostname.intern
11949 </pre
></blockquote
>
11951 </p
>One could even add the LTSP configuration associated with a given
11952 machine, as long as the required attributes are available in a
11953 auxiliary object class.
</p
>
11958 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
11959 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
11960 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
11961 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
11962 <description><p
>For a while now, I have wanted to find a way to change the DNS and
11963 DHCP services in Debian Edu to use the same LDAP objects for a given
11964 computer, to avoid the possibility of having a inconsistent state for
11965 a computer in LDAP (as in DHCP but no DNS entry or the other way
11966 around) and make it easier to add computers to LDAP.
</p
>
11968 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
11969 information finally found a solution that seem to work.
</p
>
11971 <p
>The old setup required three LDAP objects for a given computer.
11972 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11973 we switch powerdns to use its strict LDAP method (ldap-method=strict
11974 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11975 merged into one while making it impossible to transfer the reverse map
11976 to a slave DNS server.
</p
>
11978 <p
>If we also replace the object class used to get the DNS related
11979 attributes to one allowing these attributes to be combined with the
11980 dhcphost object class, we can merge the DNS and DHCP entries into one.
11981 I
've written such object class in the dnsdomainaux.schema file (need
11982 proper OIDs, but that is a minor issue), and tested the setup. It
11983 seem to work.
</p
>
11985 <p
>With this test setup in place, we can get away with one LDAP object
11986 for both DNS and DHCP, and even the LTSP configuration I suggested in
11987 an earlier email. The combined LDAP object will look something like
11990 <blockquote
><pre
>
11991 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11993 objectClass: dhcphost
11994 objectclass: domainrelatedobject
11995 objectclass: dnsdomainaux
11996 associateddomain: hostname.intern
11997 arecord:
10.11.12.13
11998 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
11999 dhcpstatements: fixed-address hostname
12001 </pre
></blockquote
>
12003 <p
>The DNS server uses the associateddomain and arecord entries, while
12004 the DHCP server uses the dhcphwaddress and dhcpstatements entries
12005 before asking DNS to resolve the fixed-adddress. LTSP will use
12006 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
12008 <p
>I am not yet sure if I can get the DHCP server to look for its
12009 dhcphost in a different location, to allow us to put the objects
12010 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
12011 that. If I can
't figure out a way to do that, we can still get rid of
12012 the hosts subtree and move all its content into the DHCP Config tree
12013 (which probably should be renamed to be more related to the new
12014 content. I suspect cn=dnsdhcp,ou=services or something like that
12015 might be a good place to put it.
</p
>
12017 <p
>If you want to help out with implementing this for Debian Edu,
12018 please contact us on debian-edu@lists.debian.org.
</p
>
12023 <title>Idea for storing LTSP configuration in LDAP
</title>
12024 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
12025 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
12026 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
12027 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
12028 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
12029 clients, and that this can be used to fetch configuration from LDAP if
12030 Debian Edu choose to store configuration there.
</p
>
12032 <p
>Armed with this information, I got inspired and wrote a test module
12033 to get configuration from LDAP. The idea is to look up the MAC
12034 address of the client in LDAP, and look for attributes on the form
12035 ltspconfigsetting=value, and use this to export SETTING=value to the
12036 LTSP clients.
</p
>
12038 <p
>The goal is to be able to store the LTSP configuration attributes
12039 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
12040 allowing us to store all information about a computer in one place.
</p
>
12042 <p
>This is a untested draft implementation, and I welcome feedback on
12043 this approach. A real LDAP schema for the ltspClientAux objectclass
12044 need to be written. Comments, suggestions, etc?
</p
>
12046 <blockquote
><pre
>
12047 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
12049 # Fetch LTSP client settings from LDAP based on MAC address
12051 # Uses ethernet address as stored in the dhcpHost objectclass using
12052 # the dhcpHWAddress attribute or ethernet address stored in the
12053 # ieee802Device objectclass with the macAddress attribute.
12055 # This module is written to be schema agnostic, and only depend on the
12056 # existence of attribute names.
12058 # The LTSP configuration variables are saved directly using a
12059 # ltspConfig prefix and uppercasing the rest of the attribute name.
12060 # To set the SERVER variable, set the ltspConfigServer attribute.
12062 # Some LDAP schema should be created with all the relevant
12063 # configuration settings. Something like this should work:
12065 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
12068 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
12070 LDAPSERVER=$(debian-edu-ldapserver)
12071 if [
"$LDAPSERVER
" ] ; then
12072 LDAPBASE=$(debian-edu-ldapserver -b)
12073 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
12074 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
12075 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
12076 grep
'^ltspConfig
' | while read attr value ; do
12077 # Remove prefix and convert to upper case
12078 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
12079 # bass value on to clients
12080 eval
"$attr=$value; export $attr
"
12084 </pre
></blockquote
>
12086 <p
>I
'm not sure this shell construction will work, because I suspect
12087 the while block might end up in a subshell causing the variables set
12088 there to not show up in ltsp-config, but if that is the case I am sure
12089 the code can be restructured to make sure the variables are passed on.
12090 I expect that can be solved with some testing. :)
</p
>
12092 <p
>If you want to help out with implementing this for Debian Edu,
12093 please contact us on debian-edu@lists.debian.org.
</p
>
12095 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
12096 configuration in LDAP that was created around year
2000 by
12097 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
12098 Xperience, Inc.,
2000</a
>. I found its
12099 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
12100 personal home page over at redhat.com.
</p
>
12105 <title>jXplorer, a very nice LDAP GUI
</title>
12106 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
12107 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
12108 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
12109 <description><p
>Since
12110 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
12111 last post
</a
> about available LDAP tools in Debian, I was told about a
12112 LDAP GUI that is even better than luma. The java application
12113 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
12114 moving LDAP objects and subtrees using drag-and-drop, and can
12115 authenticate using Kerberos. I have only tested the Kerberos
12116 authentication, but do not have a LDAP setup allowing me to rewrite
12117 LDAP with my test user yet. It is
12118 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
12119 Debian
</a
> testing and unstable at the moment. The only problem I
12120 have with it is how it handle errors. If something go wrong, its
12121 non-intuitive behaviour require me to go through some query work list
12122 and remove the failing query. Nothing big, but very annoying.
</p
>
12127 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
12128 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
12129 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
12130 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
12131 <description><p
>Here is a short update on my
<a
12132 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
12133 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
12134 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
12135 not reporting the status for KDE, because the upgrade crashes when
12136 aptitude try because of missing conflicts
12137 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
12138 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
12140 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
12141 complete list of the installed packages. Based on this I see these
12142 differences when I did a test run today. As usual, I do not really
12143 know what the correct set of packages would be, but thought it best to
12144 publish the difference.
</p
>
12146 <p
>Installed using apt-get, missing with aptitude
</p
>
12148 <blockquote
><p
>
12149 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
12150 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
12151 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
12152 libgtksourceview-common libpt-
1.10.10-plugins-alsa
12153 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
12154 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
12155 python-
4suite-xml python-eggtrayicon python-gtkhtml2
12156 python-gtkmozembed svgalibg1 xserver-xephyr zip
12157 </p
></blockquote
>
12159 <p
>Installed using apt-get, removed with aptitude
</p
>
12161 <blockquote
><p
>
12162 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
12163 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
12164 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
12165 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
12166 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
12167 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
12168 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
12169 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
12170 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
12171 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
12172 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
12173 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
12174 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
12175 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
12176 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
12177 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
12178 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
12179 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
12180 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
12181 mysql-common swfdec-gnome totem-gstreamer wodim
12182 </p
></blockquote
>
12184 <p
>Installed using aptitude, missing with apt-get
</p
>
12186 <blockquote
><p
>
12187 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
12188 python-gnomekeyring python-wnck rhythmbox-plugins xorg
12189 xserver-xorg-input-all xserver-xorg-input-evdev
12190 xserver-xorg-input-kbd xserver-xorg-input-mouse
12191 xserver-xorg-input-synaptics xserver-xorg-video-all
12192 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
12193 xserver-xorg-video-chips xserver-xorg-video-cirrus
12194 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12195 xserver-xorg-video-glint xserver-xorg-video-i128
12196 xserver-xorg-video-i740 xserver-xorg-video-mach64
12197 xserver-xorg-video-mga xserver-xorg-video-neomagic
12198 xserver-xorg-video-nouveau xserver-xorg-video-nv
12199 xserver-xorg-video-r128 xserver-xorg-video-radeon
12200 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
12201 xserver-xorg-video-s3 xserver-xorg-video-s3virge
12202 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
12203 xserver-xorg-video-sis xserver-xorg-video-sisusb
12204 xserver-xorg-video-tdfx xserver-xorg-video-tga
12205 xserver-xorg-video-trident xserver-xorg-video-tseng
12206 xserver-xorg-video-vesa xserver-xorg-video-vmware
12207 xserver-xorg-video-voodoo
12208 </p
></blockquote
>
12210 <p
>Installed using aptitude, removed with apt-get
</p
>
12212 <blockquote
><p
>
12213 deskbar-applet xserver-xorg xserver-xorg-core
12214 xserver-xorg-input-wacom xserver-xorg-video-intel
12215 xserver-xorg-video-openchrome
12216 </p
></blockquote
>
12218 <p
>I was told on IRC that the xorg-xserver package was
12219 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
12220 in git
</a
> today to try to get apt-get to not remove xorg completely.
12221 No idea when it hits Squeeze, but when it does I hope it will reduce
12222 the difference somewhat.
12227 <title>LUMA, a very nice LDAP GUI
</title>
12228 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
12229 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
12230 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
12231 <description><p
>The last few days I have been looking into the status of the LDAP
12232 directory in Debian Edu, and in the process I started to miss a GUI
12233 tool to browse the LDAP tree. The only one I was able to find in
12234 Debian/Squeeze and Lenny is
12235 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
12236 be a great tool to get a overview of the current LDAP directory
12237 populated by default in Skolelinux. Thanks to it, I have been able to
12238 find empty and obsolete subtrees, misplaced objects and duplicate
12239 objects. It will be installed by default in Debian/Squeeze. If you
12240 are working with LDAP, give it a go. :)
</p
>
12242 <p
>I did notice one problem with it I have not had time to report to
12243 the BTS yet. There is no .desktop file in the package, so the tool do
12244 not show up in the Gnome and KDE menus, but only deep down in in the
12245 Debian submenu in KDE. I hope that can be fixed before Squeeze is
12246 released.
</p
>
12248 <p
>I have not yet been able to get it to modify the tree yet. I would
12249 like to move objects and remove subtrees directly in the GUI, but have
12250 not found a way to do that with LUMA yet. So in the mean time, I use
12251 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
12253 <p
>If you have tips on other GUI tools for LDAP that might be useful
12254 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
12256 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
12257 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
12258 useful GUI alternative. It seem like a good tool, but is unmaintained
12259 in Debian and got a RC bug keeping it out of Squeeze. Unless that
12260 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
12265 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
12266 <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>
12267 <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>
12268 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
12269 <description><p
>A while back, I
12270 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
12271 about the fact
</a
> that it is not possible with the provided schemas
12272 for storing DNS and DHCP information in LDAP to combine the two sets
12273 of information into one LDAP object representing a computer.
</p
>
12275 <p
>In the mean time, I discovered that a simple fix would be to make
12276 the dhcpHost object class auxiliary, to allow it to be combined with
12277 the dNSDomain object class, and thus forming one object for one
12278 computer when storing both DHCP and DNS information in LDAP.
</p
>
12280 <p
>If I understand this correctly, it is not safe to do this change
12281 without also changing the assigned number for the object class, and I
12282 do not know enough about LDAP schema design to do that properly for
12283 Debian Edu.
</p
>
12285 <p
>Anyway, for future reference, this is how I believe we could change
12287 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
12288 schema
</a
> to solve at least part of the problem with the LDAP schemas
12289 available today from IETF.
</p
>
12292 --- dhcp.schema (revision
65192)
12293 +++ dhcp.schema (working copy)
12294 @@ -
376,
7 +
376,
7 @@
12295 objectclass (
2.16.840.1.113719.1.203.6.6
12296 NAME
'dhcpHost
'
12297 DESC
'This represents information about a particular client
'
12299 + SUP top AUXILIARY
12301 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
12302 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
12305 <p
>I very much welcome clues on how to do this properly for Debian
12306 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
12307 package, and should thus be free to rewrite it as we see fit.
</p
>
12309 <p
>If you want to help out with implementing this for Debian Edu,
12310 please contact us on debian-edu@lists.debian.org.
</p
>
12315 <title>Calling tasksel like the installer, while still getting useful output
</title>
12316 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
12317 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
12318 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
12319 <description><p
>A few times I have had the need to simulate the way tasksel
12320 installs packages during the normal debian-installer run. Until now,
12321 I have ended up letting tasksel do the work, with the annoying problem
12322 of not getting any feedback at all when something fails (like a
12323 conffile question from dpkg or a download that fails), using code like
12326 <blockquote
><pre
>
12327 export DEBIAN_FRONTEND=noninteractive
12328 tasksel --new-install
12329 </pre
></blockquote
>
12331 This would invoke tasksel, let its automatic task selection pick the
12332 tasks to install, and continue to install the requested tasks without
12333 any output what so ever.
12335 Recently I revisited this problem while working on the automatic
12336 package upgrade testing, because tasksel would some times hang without
12337 any useful feedback, and I want to see what is going on when it
12338 happen. Then it occured to me, I can parse the output from tasksel
12339 when asked to run in test mode, and use that aptitude command line
12340 printed by tasksel then to simulate the tasksel run. I ended up using
12343 <blockquote
><pre
>
12344 export DEBIAN_FRONTEND=noninteractive
12345 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
12347 </pre
></blockquote
>
12349 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
12350 --without-recommends -o APT::Install-Recommends=no -y install
12351 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
12352 ~pimportant
</tt
>", which will install the gnome desktop task, the
12353 laptop task and all packages with priority standard , required and
12354 important, just like tasksel would have done it during
12355 installation.
</p
>
12357 <p
>A better approach is probably to extend tasksel to be able to
12358 install packages without using debconf-apt-progress, for use cases
12359 like this.
</p
>
12364 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
12365 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
12366 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
12367 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
12368 <description><p
>My
12369 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
12370 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
12371 finally made the upgrade logs available from
12372 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
12373 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
12374 apt and aptitude, and found their differences interesting. This time
12375 I will only focus on their removal plans.
</p
>
12377 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
12378 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
12379 surprising part is that it want to remove xorg and all
12380 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
12381 sure why. When asking aptitude to do the same, it want to remove
129
12382 packages, but most of them are library packages I suspect are no
12383 longer needed. Both of them want to remove bluetooth packages, which
12384 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
12386 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
12387 which seem like a bad idea and xorg the same way as with Gnome. Asking
12388 aptitude for the same, it wants to remove
192 packages, none which are
12389 too surprising.
</p
>
12391 <p
>I guess the removal of xorg during upgrades should be investigated
12392 and avoided, and perhaps others as well. Here are the complete list
12393 of planned removals. The complete logs is available from the URL
12394 above. Note if you want to repeat these tests, that the upgrade test
12395 for kde+apt-get hung in the tasksel setup because of dpkg asking
12396 conffile questions. No idea why. I worked around it by using
12397 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
12398 continue.
</p
>
12400 <p
><b
>apt-get gnome
72</b
>
12401 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
12402 gnome-desktop-environment gnome-network-admin gtkhtml3.14
12403 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
12404 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
12405 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
12406 serpentine swfdec-mozilla update-manager xorg xserver-xorg
12407 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12408 xserver-xorg-input-kbd xserver-xorg-input-mouse
12409 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12410 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12411 xserver-xorg-video-ati xserver-xorg-video-chips
12412 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12413 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12414 xserver-xorg-video-glint xserver-xorg-video-i128
12415 xserver-xorg-video-i740 xserver-xorg-video-imstt
12416 xserver-xorg-video-intel xserver-xorg-video-mach64
12417 xserver-xorg-video-mga xserver-xorg-video-neomagic
12418 xserver-xorg-video-nsc xserver-xorg-video-nv
12419 xserver-xorg-video-openchrome xserver-xorg-video-r128
12420 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12421 xserver-xorg-video-rendition xserver-xorg-video-s3
12422 xserver-xorg-video-s3virge xserver-xorg-video-savage
12423 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12424 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12425 xserver-xorg-video-tga xserver-xorg-video-trident
12426 xserver-xorg-video-tseng xserver-xorg-video-v4l
12427 xserver-xorg-video-vesa xserver-xorg-video-vga
12428 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
12429 xulrunner-
1.9-gnome-support
</p
>
12431 <p
><b
>aptitude gnome
129</b
>
12433 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
12434 djvulibre-desktop finger gnome-app-install gnome-mount
12435 gnome-network-admin gnome-spell gnome-vfs-obexftp
12436 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
12437 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
12438 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
12439 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
12440 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
12441 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
12442 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
12443 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
12444 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
12445 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
12446 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
12447 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
12448 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
12449 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
12450 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
12451 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
12452 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
12453 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
12454 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
12455 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
12456 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
12457 openoffice.org-writer2latex openssl-blacklist p7zip
12458 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
12459 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
12460 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
12461 swfdec-mozilla totem-gstreamer update-manager wodim
12462 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12463 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12466 <p
><b
>apt-get kde
82</b
>
12468 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
12469 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
12470 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
12471 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
12472 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
12473 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
12474 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12475 xserver-xorg-input-kbd xserver-xorg-input-mouse
12476 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12477 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12478 xserver-xorg-video-ati xserver-xorg-video-chips
12479 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12480 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12481 xserver-xorg-video-glint xserver-xorg-video-i128
12482 xserver-xorg-video-i740 xserver-xorg-video-imstt
12483 xserver-xorg-video-intel xserver-xorg-video-mach64
12484 xserver-xorg-video-mga xserver-xorg-video-neomagic
12485 xserver-xorg-video-nsc xserver-xorg-video-nv
12486 xserver-xorg-video-openchrome xserver-xorg-video-r128
12487 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12488 xserver-xorg-video-rendition xserver-xorg-video-s3
12489 xserver-xorg-video-s3virge xserver-xorg-video-savage
12490 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12491 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12492 xserver-xorg-video-tga xserver-xorg-video-trident
12493 xserver-xorg-video-tseng xserver-xorg-video-v4l
12494 xserver-xorg-video-vesa xserver-xorg-video-vga
12495 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
12497 <p
><b
>aptitude kde
192</b
>
12498 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
12499 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
12500 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
12501 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
12502 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12503 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
12504 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
12505 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12506 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
12507 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
12508 kghostview khelpcenter khexedit kiconedit kitchensync klatin
12509 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
12510 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
12511 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
12512 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
12513 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
12514 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
12515 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12516 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
12517 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
12518 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12519 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
12520 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
12521 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
12522 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12523 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
12524 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
12525 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
12526 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
12527 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
12528 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
12529 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
12530 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
12531 texlive-common texlive-doc-base texlive-fonts-recommended
12532 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12533 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12534 xulrunner-
1.9</p
>
12540 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
12541 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
12542 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
12543 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
12544 <description><p
>The last few days I have done some upgrade testing in Debian, to
12545 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
12546 have been discovered and reported in the process
12547 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
12548 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
12549 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
12550 kdebase-workspace-data), and to get a more regular testing going on, I
12551 am working on a script to automate the test.
</p
>
12553 <p
>The idea is to create a Lenny chroot and use tasksel to install a
12554 Gnome or KDE desktop installation inside the chroot before upgrading
12555 it. To ensure no services are started in the chroot, a policy-rc.d
12556 script is inserted. To make sure tasksel believe it is to install a
12557 desktop on a laptop, the tasksel tests are replaced in the chroot
12558 (only acceptable because this is a throw-away chroot).
</p
>
12560 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12561 currently always fail because udev refuses to upgrade with the kernel
12562 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12563 is created. The bug report
12564 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
12565 this problem do not trigger in a chroot, but I touch the file anyway
12566 to make sure the upgrade go well. Testing on virtual and real
12567 hardware have failed me because of udev so far, and creating this file
12568 do the trick in such settings anyway. This is a
12569 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
12570 issue
</a
> and the current udev behaviour is intended by the udev
12571 maintainer because he lack the resources to rewrite udev to keep
12572 working with old kernels or something like that. I really wish the
12573 udev upstream would keep udev backwards compatible, to avoid such
12574 upgrade problem, but given that they fail to do so, I guess
12575 documenting the way out of this mess is the best option we got for
12576 Debian Squeeze.
</p
>
12578 <p
>Anyway, back to the task at hand, testing upgrades. This test
12579 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
12582 <blockquote
><pre
>
12586 if [
"$
1" ] ; then
12595 exec
&lt; /dev/null
12597 mirror=http://ftp.skolelinux.org/debian
12598 tmpdir=chroot-$from-upgrade-$to-$desktop
12600 debootstrap $from $tmpdir $mirror
12601 chroot $tmpdir aptitude update
12602 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
12606 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12608 umount $tmpdir/proc
12610 mount -t proc proc $tmpdir/proc
12611 # Make sure proc is unmounted also on failure
12612 trap exit_cleanup EXIT INT
12614 chroot $tmpdir aptitude -y install debconf-utils
12616 # Make sure tasksel autoselection trigger. It need the test scripts
12617 # to return the correct answers.
12618 echo tasksel tasksel/desktop multiselect $desktop | \
12619 chroot $tmpdir debconf-set-selections
12621 # Include the desktop and laptop task
12622 for test in desktop laptop ; do
12623 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
12627 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12630 DEBIAN_FRONTEND=noninteractive
12631 DEBIAN_PRIORITY=critical
12632 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12633 chroot $tmpdir tasksel --new-install
12635 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
12636 chroot $tmpdir aptitude update
12637 touch $tmpdir/etc/udev/kernel-upgrade
12638 chroot $tmpdir aptitude -y dist-upgrade
12640 </pre
></blockquote
>
12642 <p
>I suspect it would be useful to test upgrades with both apt-get and
12643 with aptitude, but I have not had time to look at how they behave
12644 differently so far. I hope to get a cron job running to do the test
12645 regularly and post the result on the web. The Gnome upgrade currently
12646 work, while the KDE upgrade fail because of the bug in
12647 kdebase-workspace-data
</p
>
12649 <p
>I am not quite sure what kind of extract from the huge upgrade logs
12650 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
12651 post, so I will refrain from trying. I can report that for Gnome,
12652 aptitude report
760 packages upgraded,
448 newly installed,
129 to
12653 remove and
1 not upgraded and
1024MB need to be downloaded while for
12654 KDE the same numbers are
702 packages upgraded,
507 newly installed,
12655 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
12657 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
12658 is able to migrate to dependency based boot sequencing and parallel
12659 booting without a hitch. Was unsure if there were still bugs with
12660 packages failing to clean up their obsolete init.d script during
12661 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12662 packages.
</p
>
12667 <title>Upstart or sysvinit - as init.d scripts see it
</title>
12668 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
12669 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
12670 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
12671 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
12672 scripts to migrate (some of) their operations to upstart job while
12673 keeping the init.d for hurd and kfreebsd. The packages with such
12674 needs will need a way to get their init.d scripts to behave
12675 differently when used with sysvinit and with upstart. Because of
12676 this, I had a look at the environment variables set when a init.d
12677 script is running under upstart, and when it is not.
</p
>
12679 <p
>With upstart, I notice these environment variables are set when a
12680 script is started from rcS.d/ (ignoring some irrelevant ones like
12681 COLUMNS):
</p
>
12683 <blockquote
><pre
>
12689 UPSTART_EVENTS=startup
12691 UPSTART_JOB=rc-sysinit
12692 </pre
></blockquote
>
12694 <p
>With sysvinit, these environment variables are set for the same
12697 <blockquote
><pre
>
12698 INIT_VERSION=sysvinit-
2.88
12703 </pre
></blockquote
>
12705 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
12706 sysvinit are not set by upstart. Not sure if it is intentional or not
12707 to not be compatible with sysvinit in this regard.
</p
>
12709 <p
>For scripts needing to behave differently when upstart is used,
12710 looking for the UPSTART_JOB environment variable seem to be a good
12716 <title>A manual for standards wars...
</title>
12717 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
12718 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
12719 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
12720 <description><p
>Via the
12721 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
12722 of Rob Weir
</a
> I came across the very interesting essay named
12723 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
12724 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
12725 following the standards wars of today.
</p
>
12730 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
12731 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
12732 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
12733 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
12734 <description><p
>When using sitesummary at a site to track machines, it is possible
12735 to get a list of the machine types in use thanks to the DMI
12736 information extracted from each machine. The script to do so is
12737 included in the sitesummary package, and here is example output from
12738 the Skolelinux build servers:
</p
>
12740 <blockquote
><pre
>
12741 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12743 Dell Computer Corporation
1
12746 eserver xSeries
345 -[
8670M1X]-
1
12750 </pre
></blockquote
>
12752 <p
>The quality of the report depend on the quality of the DMI tables
12753 provided in each machine. Here there are Intel machines without model
12754 information listed with Intel as vendor and no model, and virtual Xen
12755 machines listed as [no-dmi-info]. One can add -l as a command line
12756 option to list the individual machines.
</p
>
12758 <p
>A larger list is
12759 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
12760 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
12761 provide the basic sitesummary report publicly. In their report there
12762 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
12763 their machines, and as sitesummary is available in both distributions,
12764 it is trivial to get all of them to report to the same central
12765 collector.
</p
>
12770 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
12771 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
12772 <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>
12773 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
12774 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
12775 start at boot when an NVidia video card is used is handled. The
12776 problem seem to be that the nvidia X.org driver uses a long time to
12777 initialize, and this duration is longer than kdm is configured to
12780 <p
>I came across two bugs related to this issue,
12781 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
12782 against initscripts and passed on to nvidia-glx when it became obvious
12783 that the nvidia drivers were involved, and
12784 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
12785 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
12787 <p
>To me, it seem that no-one is interested in actually solving the
12788 problem nvidia video card owners experience and make sure the Debian
12789 distribution work out of the box for these users. The nvidia driver
12790 maintainers expect kdm to be set up to wait longer, while kdm expect
12791 the nvidia driver maintainers to fix the driver to start faster, and
12792 while they wait for each other I guess the users end up switching to a
12793 distribution that work for them. I have no idea what the solution is,
12794 but I am pretty sure that waiting for each other is not it.
</p
>
12796 <p
>I wonder why we end up handling bugs this way.
</p
>
12801 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
12802 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
12803 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
12804 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
12805 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
12806 The feature seem to hold up pretty well, but three fairly serious
12807 issues are known and should be solved:
12809 <p
><ul
>
12811 <li
>The wicd package seen to
12812 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
12813 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
12814 parallel booting is enabled. No idea why, but the wicd maintainer
12815 seem to be on the case.
</li
>
12817 <li
>The nvidia X driver seem to
12818 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
12819 triggered more easily when parallel booting is in effect. The
12820 maintainer is on the case.
</li
>
12822 <li
>The sysv-rc package fail to properly enable dependency based boot
12823 sequencing (the shutdown is broken) when old file-rc users
12824 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
12825 sysv-rc. One way to solve it would be for file-rc to create
12826 /etc/init.d/.legacy-bootordering, and another is to try to make
12827 sysv-rc more robust. Will investigate some more and probably upload a
12828 workaround in sysv-rc to help those trying to move from file-rc to
12829 sysv-rc get a working shutdown.
</li
>
12831 </ul
></p
>
12833 <p
>All in all not many surprising issues, and all of them seem
12834 solvable before Squeeze is released. In addition to these there are
12835 some packages with bugs in their dependencies and run level settings,
12836 which I expect will be fixed in a reasonable time span.
</p
>
12838 <p
>If you report any problems with dependencies in init.d scripts to
12839 the BTS, please usertag the report to get it to show up at
12840 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12841 list of usertagged bugs related to this
</a
>.
</p
>
12843 <p
>Update: Correct bug number to file-rc issue.
</p
>
12848 <title>More flexible firmware handling in debian-installer
</title>
12849 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
12850 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
12851 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
12852 <description><p
>After a long break from debian-installer development, I finally
12853 found time today to return to the project. Having to spend less time
12854 working dependency based boot in debian, as it is almost complete now,
12855 definitely helped freeing some time.
</p
>
12857 <p
>A while back, I ran into a problem while working on Debian Edu. We
12858 include some firmware packages on the Debian Edu CDs, those needed to
12859 get disk and network controllers working. Without having these
12860 firmware packages available during installation, it is impossible to
12861 install Debian Edu on the given machine, and because our target group
12862 are non-technical people, asking them to provide firmware packages on
12863 an external medium is a support pain. Initially, I expected it to be
12864 enough to include the firmware packages on the CD to get
12865 debian-installer to find and use them. This proved to be wrong.
12866 Next, I hoped it was enough to symlink the relevant firmware packages
12867 to some useful location on the CD (tried /cdrom/ and
12868 /cdrom/firmware/). This also proved to not work, and at this point I
12869 found time to look at the debian-installer code to figure out what was
12870 going to work.
</p
>
12872 <p
>The firmware loading code is in the hw-detect package, and a closer
12873 look revealed that it would only look for firmware packages outside
12874 the installation media, so the CD was never checked for firmware
12875 packages. It would only check USB sticks, floppies and other
12876 "external
" media devices. Today I changed it to also look in the
12877 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12878 solve the problem I ran into with Debian edu. I also changed it to
12879 look in /firmware/, to make sure the installer also find firmware
12880 provided in the initrd when booting the installer via PXE, to allow us
12881 to provide the same feature in the PXE setup included in Debian
12884 <p
>To make sure firmware deb packages with a license questions are not
12885 activated without asking if the license is accepted, I extended
12886 hw-detect to look for preinst scripts in the firmware packages, and
12887 run these before activating the firmware during installation. The
12888 license question is asked using debconf in the preinst, so this should
12889 solve the issue for the firmware packages I have looked at so far.
</p
>
12891 <p
>If you want to discuss the details of these features, please
12892 contact us on debian-boot@lists.debian.org.
</p
>
12897 <title>Parallellized boot is now the default in Debian/unstable
</title>
12898 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
12899 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
12900 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
12901 <description><p
>Since this evening, parallel booting is the default in
12902 Debian/unstable for machines using dependency based boot sequencing.
12903 Apparently the testing of concurrent booting has been wider than
12904 expected, if I am to believe the
12905 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12906 on debian-devel@
</a
>, and I concluded a few days ago to move forward
12907 with the feature this weekend, to give us some time to detect any
12908 remaining problems before Squeeze is frozen. If serious problems are
12909 detected, it is simple to change the default back to sequential boot.
12910 The upload of the new sysvinit package also activate a new upstream
12913 More information about
12914 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12915 based boot sequencing
</a
> is available from the Debian wiki. It is
12916 currently possible to disable parallel booting when one run into
12917 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
12919 <blockquote
><pre
>
12921 </pre
></blockquote
>
12923 <p
>If you report any problems with dependencies in init.d scripts to
12924 the BTS, please usertag the report to get it to show up at
12925 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12926 list of usertagged bugs related to this
</a
>.
</p
>
12931 <title>Sitesummary tip: Listing MAC address of all clients
</title>
12932 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
12933 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
12934 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
12935 <description><p
>In the recent Debian Edu versions, the
12936 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
12937 system
</a
> is used to keep track of the machines in the school
12938 network. Each machine will automatically report its status to the
12939 central server after boot and once per night. The network setup is
12940 also reported, and using this information it is possible to get the
12941 MAC address of all network interfaces in the machines. This is useful
12942 to update the DHCP configuration.
</p
>
12944 <p
>To give some idea how to use sitesummary, here is a one-liner to
12945 ist all MAC addresses of all machines reporting to sitesummary. Run
12946 this on the collector host:
</p
>
12948 <blockquote
><pre
>
12949 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
12950 </pre
></blockquote
>
12952 <p
>This will list all MAC addresses assosiated with all machine, one
12953 line per machine and with space between the MAC addresses.
</p
>
12955 <p
>To allow system administrators easier job at adding static DHCP
12956 addresses for hosts, it would be possible to extend this to fetch
12957 machine information from sitesummary and update the DHCP and DNS
12958 tables in LDAP using this information. Such tool is unfortunately not
12959 written yet.
</p
>
12964 <title>systemd, an interesting alternative to upstart
</title>
12965 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
12966 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
12967 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
12968 <description><p
>The last few days a new boot system called
12969 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
12971 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
12973 to the free software world. I have not yet had time to play around
12974 with it, but it seem to be a very interesting alternative to
12975 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
12976 a good alternative for Debian when we are able to switch to an event
12977 based boot system. Tollef is
12978 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
12979 systemd into Debian, and I look forward to seeing how well it work. I
12980 like the fact that systemd handles init.d scripts with dependency
12981 information natively, allowing them to run in parallel where upstart
12982 at the moment do not.
</p
>
12984 <p
>Unfortunately do systemd have the same problem as upstart regarding
12985 platform support. It only work on recent Linux kernels, and also need
12986 some new kernel features enabled to function properly. This means
12987 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12988 system. Not sure how that will be handled if systemd proves to be the
12989 way forward.
</p
>
12991 <p
>In the mean time, based on the
12992 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12993 on debian-devel@
</a
> regarding parallel booting in Debian, I have
12994 decided to enable full parallel booting as the default in Debian as
12995 soon as possible (probably this weekend or early next week), to see if
12996 there are any remaining serious bugs in the init.d dependencies. A
12997 new version of the sysvinit package implementing this change is
12998 already in experimental. If all go well, Squeeze will be released
12999 with parallel booting enabled by default.
</p
>
13004 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
13005 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
13006 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
13007 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
13008 <description><p
>These days, the init.d script dependencies in Squeeze are quite
13009 complete, so complete that it is actually possible to run all the
13010 init.d scripts in parallell based on these dependencies. If you want
13011 to test your Squeeze system, make sure
13012 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13013 based boot sequencing
</a
> is enabled, and add this line to
13014 /etc/default/rcS:
</p
>
13016 <blockquote
><pre
>
13017 CONCURRENCY=makefile
13018 </pre
></blockquote
>
13020 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
13021 scripts in parallel using the dependency information stored in
13022 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
13023 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
13024 to try to start the kdm and gdm scripts as early as possible, and will
13025 start the facilities required by kdm or gdm as early as possible to
13026 make this happen.
</p
>
13028 <p
>Give it a try, and see if you like the result. If some services
13029 fail to start properly, it is most likely because they have incomplete
13030 init.d script dependencies in their startup script (or some of their
13031 dependent scripts have incomplete dependencies). Report bugs and get
13032 the package maintainers to fix it. :)
</p
>
13034 <p
>Running scripts in parallel could be the default in Debian when we
13035 manage to get the init.d script dependencies complete and correct. I
13036 expect we will get there in Squeeze+
1, if we get manage to test and
13037 fix the remaining issues.
</p
>
13039 <p
>If you report any problems with dependencies in init.d scripts to
13040 the BTS, please usertag the report to get it to show up at
13041 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
13042 list of usertagged bugs related to this
</a
>.
</p
>
13047 <title>Debian has switched to dependency based boot sequencing
</title>
13048 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
13049 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
13050 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
13051 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
13052 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
13053 have been migrated to using dependency based boot sequencing. This
13054 conclude work me and others have been doing for the last three days.
13055 It feels great to see this finally part of the default Debian
13056 installation. Now we just need to weed out the last few problems that
13057 are bound to show up, to get everything ready for Squeeze.
</p
>
13059 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
13060 fixing the more fundamental problem of handing the event based
13061 non-predictable kernel in the early boot.
</p
>
13066 <title>Taking over sysvinit development
</title>
13067 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
13068 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
13069 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
13070 <description><p
>After several years of frustration with the lack of activity from
13071 the existing sysvinit upstream developer, I decided a few weeks ago to
13072 take over the package and become the new upstream. The number of
13073 patches to track for the Debian package was becoming a burden, and the
13074 lack of synchronization between the distribution made it hard to keep
13075 the package up to date.
</p
>
13077 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
13078 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
13079 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
13080 and Fedora), based on the patches currently in use in these
13081 distributions. We Debian maintainers plan to move to this tarball as
13082 the new upstream as soon as we find time to do the merge. Since the
13083 new tarball was created, we agreed with Werner at SuSe to make a new
13084 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
13085 development there. The project is registered and currently waiting
13086 for approval by the Savannah administrators, and as soon as it is
13087 approved, we will import the old versions from svn and continue
13088 working on the future release.
</p
>
13090 <p
>It is a bit ironic that this is done now, when some of the involved
13091 distributions are moving to upstart as a syvinit replacement.
</p
>
13096 <title>Debian boots quicker and quicker
</title>
13097 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
13098 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
13099 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
13100 <description><p
>I spent Monday and tuesday this week in London with a lot of the
13101 people involved in the boot system on Debian and Ubuntu, to see if we
13102 could find more ways to speed up the boot system. This was an Ubuntu
13104 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
13105 gathering
</a
>. It was quite productive. We also discussed the future
13106 of boot systems, and ways to handle the increasing number of boot
13107 issues introduced by the Linux kernel becoming more and more
13108 asynchronous and event base. The Ubuntu approach using udev and
13109 upstart might be a good way forward. Time will show.
</p
>
13111 <p
>Anyway, there are a few ways at the moment to speed up the boot
13112 process in Debian. All of these should be applied to get a quick
13117 <li
>Use dash as /bin/sh.
</li
>
13119 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
13120 clock is in UTC.
</li
>
13122 <li
>Install and activate the insserv package to enable
13123 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
13124 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
13128 These points are based on the Google summer of code work done by
13129 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
13130 Villegas
</a
>.
13132 <p
>Support for makefile-style concurrency during boot was uploaded to
13133 unstable yesterday. When we tested it, we were able to cut
6 seconds
13134 from the boot sequence. It depend on very correct dependency
13135 declaration in all init.d scripts, so I expect us to find edge cases
13136 where the dependences in some scripts are slightly wrong when we start
13137 using this.
</p
>
13139 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
13140 introduced by Raphael Geissert today, one that could affect the
13141 startup speed as well. Instead of starting some scripts concurrently
13142 from rcS.d/ and another set of scripts from rc2.d/, it would be
13143 possible to run a of them in the same process. A quick way to test
13144 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
13145 insserv
'. Will need to test if that work. :)
</p
>
13150 <title>BSAs påstander om piratkopiering møter motstand
</title>
13151 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
13152 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
13153 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
13154 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
13155 programvareselskapene som Microsoft og Apple, publisert en rapport der
13156 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
13157 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
13159 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
13160 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
13161 dagene. Et spesielt interessant kommentar fra Sverige,
13162 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
13163 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
13166 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
13167 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
13168 företag.
"Man bör nog kanske inte se de här siffrorna som helt
13169 exakta
", säger BSAs Sverigechef John Hugosson.
13170 </blockquote
>
13172 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
13173 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
13174 piracy figures need a shot of reality
</a
> og
<a
13175 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
13176 Copyright Treaty Work?
</a
></p
>
13178 <p
>Fant lenkene via
<a
13179 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
13180 på Slashdot
</a
>.
</p
>
13185 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
13186 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
13187 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
13188 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
13189 <description><p
>Kom over
13190 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
13191 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
13192 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
13193 jobber til daglig. En rask opptelling forteller meg at vi har
490
13194 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
13195 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
13196 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
13201 <title>Kryptert harddisk - naturligvis
</title>
13202 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
13203 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
13204 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
13205 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
13206 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
13207 når en tar tap av arbeidstid, fortrolige dokumenter,
13208 personopplysninger og alt annet det innebærer. Det er ingen tvil om
13209 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
13210 til at jeg har kryptert harddisken på både kontormaskinen og min
13211 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
13212 komme på avveie, den første informasjon relatert til jobben min ved
13213 Universitetet i Oslo, og den andre relatert til blant annet
13214 foreningsarbeide. Kryptering av diskene gjør at det er lite
13215 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
13216 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
13217 og en reboot vil gjøre at de ber om passord før de vil starte opp.
13218 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
13219 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
13220 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
13221 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
13222 det er gjort slik jeg gjør det er minimale, og gevinstene er
13223 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
13224 maskinen reinstalleres og alt er tapt.
</p
>
13226 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
13227 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
13228 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
13229 er for min del høyere enn gevinsten. Jeg tror oddsene for at
13230 f.eks. etteretningsorganisasjoner har glede av å titte på mine
13231 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
13232 gjøre det vanskeligere for angripere med kompetanse og ressurser er
13233 betydelige.
</p
>
13238 <title>Two projects that have improved the quality of free software a lot
</title>
13239 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
13240 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
13241 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
13242 <description><p
>There are two software projects that have had huge influence on the
13243 quality of free software, and I wanted to mention both in case someone
13244 do not yet know them.
</p
>
13246 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
13247 tool to detect and expose errors in the memory handling of programs.
13248 It is easy to use, all one need to do is to run
'valgrind program
',
13249 and it will report any problems on stdout. It is even better if the
13250 program include debug information. With debug information, it is able
13251 to report the source file name and line number where the problem
13252 occurs. It can report things like
'reading past memory block in file
13253 X line N, the memory block was allocated in file Y, line M
', and
13254 'using uninitialised value in control logic
'. This tool has made it
13255 trivial to investigate reproducible crash bugs in programs, and have
13256 reduced the number of this kind of bugs in free software a lot.
13258 <p
>The second one is
13259 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
13260 a source code checker. It is able to process the source of a program
13261 and find problems in the logic without running the program. It
13262 started out as the Stanford Checker and became well known when it was
13263 used to find bugs in the Linux kernel. It is now a commercial tool
13264 and the company behind it is running
13265 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
13266 free software community, where a lot of free software projects get
13267 their source checked for free. Several thousand defects have been
13268 found and fixed so far. It can find errors like
'lock L taken in file
13269 X line N is never released if exiting in line M
', or
'the code in file
13270 Y lines O to P can never be executed
'. The projects included in the
13271 community service project have managed to get rid of a lot of
13272 reliability problems thanks to Coverity.
</p
>
13274 <p
>I believe tools like this, that are able to automatically find
13275 errors in the source, are vital to improve the quality of software and
13276 make sure we can get rid of the crashing and failing software we are
13277 surrounded by today.
</p
>
13282 <title>No patch is not better than a useless patch
</title>
13283 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
13284 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
13285 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
13286 <description><p
>Julien Blache
13287 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
13288 patch is better than a useless patch
</a
>. I completely disagree, as a
13289 patch allow one to discuss a concrete and proposed solution, and also
13290 prove that the issue at hand is important enough for someone to spent
13291 time on fixing it. No patch do not provide any of these positive
13292 properties.
</p
>
13297 <title>Standardize on protocols and formats, not vendors and applications
</title>
13298 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
13299 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
13300 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
13301 <description><p
>Where I work at the University of Oslo, one decision stand out as a
13302 very good one to form a long lived computer infrastructure. It is the
13303 simple one, lost by many in todays computer industry: Standardize on
13304 open network protocols and open exchange/storage formats, not applications.
13305 Applications come and go, while protocols and files tend to stay, and
13306 thus one want to make it easy to change application and vendor, while
13307 avoiding conversion costs and locking users to a specific platform or
13308 application.
</p
>
13310 <p
>This approach make it possible to replace the client applications
13311 independently of the server applications. One can even allow users to
13312 use several different applications as long as they handle the selected
13313 protocol and format. In the normal case, only one client application
13314 is recommended and users only get help if they choose to use this
13315 application, but those that want to deviate from the easy path are not
13316 blocked from doing so.
</p
>
13318 <p
>It also allow us to replace the server side without forcing the
13319 users to replace their applications, and thus allow us to select the
13320 best server implementation at any moment, when scale and resouce
13321 requirements change.
</p
>
13323 <p
>I strongly recommend standardizing - on open network protocols and
13324 open formats, but I would never recommend standardizing on a single
13325 application that do not use open network protocol or open formats.
</p
>
13330 <title>Returning from Skolelinux developer gathering
</title>
13331 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
13332 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
13333 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
13334 <description><p
>I
'm sitting on the train going home from this weekends Debian
13335 Edu/Skolelinux development gathering. I got a bit done tuning the
13336 desktop, and looked into the dynamic service location protocol
13337 implementation avahi. It look like it could be useful for us. Almost
13338 30 people participated, and I believe it was a great environment to
13339 get to know the Skolelinux system. Walter Bender, involved in the
13340 development of the Sugar educational platform, presented his stuff and
13341 also helped me improve my OLPC installation. He also showed me that
13342 his Turtle Art application can be used in standalone mode, and we
13343 agreed that I would help getting it packaged for Debian. As a
13344 standalone application it would be great for Debian Edu. We also
13345 tried to get the video conferencing working with two OLPCs, but that
13346 proved to be too hard for us. The application seem to need more work
13347 before it is ready for me. I look forward to getting home and relax
13353 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
13354 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
13355 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
13356 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
13357 <description><p
>The state of standardized LDAP schemas on Linux is far from
13358 optimal. There is RFC
2307 documenting one way to store NIS maps in
13359 LDAP, and a modified version of this normally called RFC
2307bis, with
13360 some modifications to be compatible with Active Directory. The RFC
13361 specification handle the content of a lot of system databases, but do
13362 not handle DNS zones and DHCP configuration.
</p
>
13364 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
13365 we would like to store information about users, SMB clients/hosts,
13366 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
13367 and LTSP configuration in LDAP. These objects have a lot in common,
13368 but with the current LDAP schemas it is not possible to have one
13369 object per entity. For example, one need to have at least three LDAP
13370 objects for a given computer, one with the SMB related stuff, one with
13371 DNS information and another with DHCP information. The schemas
13372 provided for DNS and DHCP are impossible to combine into one LDAP
13373 object. In addition, it is impossible to implement quick queries for
13374 netgroup membership, because of the way NIS triples are implemented.
13375 It just do not scale. I believe it is time for a few RFC
13376 specifications to cleam up this mess.
</p
>
13378 <p
>I would like to have one LDAP object representing each computer in
13379 the network, and this object can then keep the SMB (ie host key), DHCP
13380 (mac address/name) and DNS (name/IP address) settings in one place.
13381 It need to be efficently stored to make sure it scale well.
</p
>
13383 <p
>I would also like to have a quick way to map from a user or
13384 computer and to the net group this user or computer is a member.
</p
>
13386 <p
>Active Directory have done a better job than unix heads like myself
13387 in this regard, and the unix side need to catch up. Time to start a
13388 new IETF work group?
</p
>
13393 <title>Endelig er Debian Lenny gitt ut
</title>
13394 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
13395 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
13396 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
13397 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
13398 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
13399 Et langt steg videre for Debian-prosjektet, og en rekke nye
13400 programpakker blir nå tilgjengelig for de av oss som bruker den
13401 stabile utgaven av Debian. Neste steg er nå å få
13402 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
13403 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
13404 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
13405 slippes løs på skolene. Takk til alle debian-utviklerne som har
13406 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
13407 bootsekvens tilgjengelig i stabil utgave, vha pakken
13408 <tt
>insserv
</tt
>.
</p
>
13413 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
13414 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
13415 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
13416 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
13417 <description><p
>This weekend we had a small developer gathering for Debian Edu in
13418 Oslo. Most of Saturday was used for the general assemly for the
13419 member organization, but the rest of the weekend I used to tune the
13420 LTSP installation. LTSP now work out of the box on the
10-network.
13421 Acer Aspire One proved to be a very nice thin client, with both
13422 screen, mouse and keybard in a small box. Was working on getting the
13423 diskless workstation setup configured out of the box, but did not
13424 finish it before the weekend was up.
</p
>
13426 <p
>Did not find time to look at the
4 VGA cards in one box we got from
13427 the Brazilian group, so that will have to wait for the next
13428 development gathering. Would love to have the Debian Edu installer
13429 automatically detect and configure a multiseat setup when it find one
13430 of these cards.
</p
>
13435 <title>The sorry state of multimedia browser plugins in Debian
</title>
13436 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
13437 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
13438 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
13439 <description><p
>Recently I have spent some time evaluating the multimedia browser
13440 plugins available in Debian Lenny, to see which one we should use by
13441 default in Debian Edu. We need an embedded video playing plugin with
13442 control buttons to pause or stop the video, and capable of streaming
13443 all the multimedia content available on the web. The test results and
13444 notes are available on
13445 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
13446 Debian wiki
</a
>. I was surprised how few of the plugins are able to
13447 fill this need. My personal video player favorite, VLC, has a really
13448 bad plugin which fail on a lot of the test pages. A lot of the MIME
13449 types I would expect to work with any free software player (like
13450 video/ogg), just do not work. And simple formats like the
13451 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
13452 totem and vlc plugins. I hope the situation will improve soon. No
13453 wonder sites use the proprietary Adobe flash to play video.
</p
>
13455 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
13456 be the only one fitting our needs. :/
</p
>