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>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
11 <link>http://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
13 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
14 <description><p
>Three years ago, the first Norwegian Bokmål edition of
15 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
16 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
17 new and updated version based on Buster is getting ready. Work on the
18 updated Norwegian Bokmål edition has been going on for a few months
19 now, and yesterday, we reached the first mile stone, with
100% of the
20 texts being translated. A lot of proof reading remains, of course,
21 but a major step towards a new edition has been taken.
</p
>
23 <p
>The book is translated by volunteers, and we would love to get some
24 help with the proof reading. The translation uses
25 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
26 hosted Weblate service
</a
>, and we welcome everyone to have a look and
27 submit improvements and suggestions. There is also a proof readers
28 PDF available on request, get in touch if you want to help out that
31 <p
>As usual, if you use Bitcoin and want to show your support of my
32 activities, please send Bitcoin donations to my address
33 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
38 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
39 <link>http://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
40 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
41 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
42 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
43 User Group
</a
>, I have the pleasure of receiving the
44 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
45 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
46 several times a year. I rarely have time to read all the articles,
47 but try to at least skim through them all as there is a lot of nice
48 knowledge passed on there. I even carry the latest issue with me most
49 of the time to try to get through all the articles when I have a few
50 spare minutes.
</p
>
52 <p
>The other day I came across a nice article titled
53 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
54 Secure Socket API: TLS as an Operating System Service
</a
>" with a
55 marvellous idea I hope can make it all the way into the POSIX standard.
56 The idea is as simple as it is powerful. By introducing a new
57 socket() option IPPROTO_TLS to use TLS, and a system wide service to
58 handle setting up TLS connections, one both make it trivial to add TLS
59 support to any program currently using the POSIX socket API, and gain
60 system wide control over certificates, TLS versions and encryption
61 systems used. Instead of doing this:
</p
>
63 <p
><blockquote
><pre
>
64 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
65 </pre
></blockquote
></p
>
67 <p
>the program code would be doing this:
<p
>
69 <p
><blockquote
><pre
>
70 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
71 </pre
></blockquote
></p
>
73 <p
>According to the ;login: article, converting a C program to use TLS
74 would normally modify only
5-
10 lines in the code, which is amazing
75 when compared to using for example the OpenSSL API.
</p
>
77 <p
>The project has set up the
78 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
79 web site to spread the idea, and the code for a kernel module and the
80 associated system daemon is available from two github repositories:
81 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
82 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
83 Unfortunately there is no explicit license information with the code,
84 so its copyright status is unclear. A
85 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
86 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
88 <p
>I love the idea of extending socket() to gain TLS support, and
89 understand why it is an advantage to implement this as a kernel module
90 and system wide service daemon, but can not help to think that it
91 would be a lot easier to get projects to move to this way of setting
92 up TLS if it was done with a user space approach where programs
93 wanting to use this API approach could just link with a wrapper
96 <p
>I recommend you check out this simple and powerful approach to more
97 secure network connections. :)
</p
>
99 <p
>As usual, if you use Bitcoin and want to show your support of my
100 activities, please send Bitcoin donations to my address
101 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
106 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
107 <link>http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
108 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
109 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
110 <description><p
>Half a year ago,
111 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
112 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
113 client
</a
>, capable of peer-to-peer encrypted communication. It
114 handle both messages, audio and video. It uses distributed hash
115 tables instead of central infrastructure to connect its users to each
116 other, which in my book is a plus. I mentioned briefly that it could
117 also work as a SIP client, which came in handy when the higher
118 educational sector in Norway started to promote Zoom as its video
119 conferencing solution. I am reluctant to use the official Zoom client
120 software, due to their
<a href=
"https://zoom.us/terms
">copyright
121 license clauses
</a
> prohibiting users to reverse engineer (for example
122 to check the security) and benchmark it, and thus prefer to connect to
123 Zoom meetings with free software clients.
</p
>
125 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
126 password set on the room. The Jami daemon leak memory like crazy
127 (approximately
1 GiB a minute) when I am connected to the video
128 conference, so I had to restart the client every
7-
10 minutes, which
129 is not a great. I tried to get other SIP Linux clients to work
130 without success, so I decided I would have to live with this wart
131 until someone managed to fix the leak in the dring code base. But
132 another problem showed up once the rooms were password protected. I
133 could not get my dial tone signaling through from Jami to Zoom, and
134 dial tone signaling is used to enter the password when connecting to
135 Zoom. I tried a lot of different permutations with my Jami and
136 Asterisk setup to try to figure out why the signaling did not get
137 through, only to finally discover that the fundamental problem seem to
138 be that Zoom is simply not able to receive dial tone signaling when
139 connecting via SIP. There seem to be nothing wrong with the Jami and
140 Asterisk end, it is simply broken in the Zoom end. I got help from a
141 very skilled VoIP engineer figuring out this last part. And being a
142 very skilled engineer, he was also able to locate a solution for me.
143 Or to be exact, a workaround that solve my initial problem of
144 connecting to password protected Zoom rooms using Jami.
</p
>
146 <p
>So, how do you do this, I am sure you are wondering by now. The
148 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
149 from Zoom
</a
>, and it is to modify the SIP address to include the room
150 password. What is most surprising about this is that the
151 automatically generated email from Zoom with instructions on how to
152 connect via SIP do not mention this. The SIP address to use normally
153 consist of the room ID (a number), an @ character and the IP address
154 of the Zoom SIP gateway. But Zoom understand a lot more than just the
155 room ID in front of the at sign. The format is
"<tt
>[Meeting
156 ID].[Password].[Layout].[Host Key]
</tt
>", and you can hear see how you
157 can both enter password, control the layout (full screen, active
158 presence and gallery) and specify the host key to start the meeting.
159 The full SIP address entered into Jami to provide the password will
160 then look like this (all using made up numbers):
</p
>
162 <p
><blockquote
>
163 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
164 </blockquote
></p
>
166 <p
>Now if only jami would reduce its memory usage, I could even
167 recommend this setup to others. :)
</p
>
169 <p
>As usual, if you use Bitcoin and want to show your support of my
170 activities, please send Bitcoin donations to my address
171 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
176 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
177 <link>http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
179 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
180 <description><p
>The curiosity got the better of me when
181 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
182 reported
</a
> that New Jersey was desperately looking for
183 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
184 and a few days later it was reported that
185 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
186 tried to locate COBOL programmers
</a
>.
</p
>
188 <p
>I thus decided to have a look at free software alternatives to
189 learn COBOL, and had the pleasure to find
190 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
191 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
192 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
193 transforming COBOL code to C or C++ before giving it to GCC or Visual
194 Studio to build binaries.
</p
>
196 <p
>I managed to get in touch with upstream, and was impressed with the
197 quick response, and also was happy to see a new Debian maintainer
198 taking over when the original one recently asked to be replaced. A
199 new Debian upload was done as recently as yesterday.
</p
>
201 <p
>Using the Debian package, I was able to follow a simple COBOL
202 introduction and make and run simple COBOL programs. It was fun to
203 learn a new programming language. If you want to test for yourself,
204 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
205 page
</a
> have a few simple examples to get you startet.
</p
>
207 <p
>As I do not have much experience with COBOL, I do not know how
208 standard compliant it is, but it claim to pass most tests from COBOL
209 test suite, which sound good to me. It is nice to know it is possible
210 to learn COBOL using software without any usage restrictions, and I am
211 very happy such nice free software project as this is available. If
212 you as me is curious about COBOL, check it out.
</p
>
214 <p
>As usual, if you use Bitcoin and want to show your support of my
215 activities, please send Bitcoin donations to my address
216 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
221 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
222 <link>http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
224 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
225 <description><p
>Some years ago, in
2016, I
226 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
227 for the first time about
</a
> the Ring peer to peer messaging system.
228 It would provide messaging without any central server coordinating the
229 system and without requiring all users to register a phone number or
230 own a mobile phone. Back then, I could not get it to work, and put it
231 aside until it had seen more development. A few days ago I decided to
232 give it another try, and am happy to report that this time I am able
233 to not only send and receive messages, but also place audio and video
234 calls. But only if UDP is not blocked into your network.
</p
>
236 <p
>The Ring system changed name earlier this year to
237 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
238 tried doing web search for
'ring
' when I discovered it for the first
239 time, and can only applaud this change as it is impossible to find
240 something called Ring among the noise of other uses of that word. Now
241 you can search for
'jami
' and this client and
242 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
243 least on duckduckgo.
</p
>
245 <p
>Jami will by default encrypt messages as well as audio and video
246 calls, and try to send them directly between the communicating parties
247 if possible. If this proves impossible (for example if both ends are
248 behind NAT), it will use a central SIP TURN server maintained by the
249 Jami project. Jami can also be a normal SIP client. If the SIP
250 server is unencrypted, the audio and video calls will also be
251 unencrypted. This is as far as I know the only case where Jami will
252 do anything without encryption.
</p
>
254 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
255 Android, iOS, and Android TV. It is included in Debian already. Jami
256 also work for those using F-Droid without any Google connections,
258 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
259 protocol
</a
> is described in the Ring project wiki. The system uses a
260 distributed hash table (DHT) system (similar to BitTorrent) running
261 over UDP. On one of the networks I use, I discovered Jami failed to
262 work. I tracked this down to the fact that incoming UDP packages
263 going to ports
1-
49999 were blocked, and the DHT would pick a random
264 port and end up in the low range most of the time. After talking to
265 the developers, I solved this by enabling the dhtproxy in the
266 settings, thus using TCP to talk to a central DHT proxy instead of
268 peering directly with others. I
've been told the developers are
269 working on allowing DHT to use TCP to avoid this problem. I also ran
270 into a problem when trying to talk to the version of Ring included in
271 Debian Stable (Stretch). Apparently the protocol changed between
272 beta2 and the current version, making these clients incompatible.
273 Hopefully the protocol will not be made incompatible in the
276 <p
>It is worth noting that while looking at Jami and its features, I
277 came across another communication platform I have not tested yet. The
278 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
279 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
280 become the topic of a future blog post.
</p
>
282 <p
>As usual, if you use Bitcoin and want to show your support of my
283 activities, please send Bitcoin donations to my address
284 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
289 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
290 <link>http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
291 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
292 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
293 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
294 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
295 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
296 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
297 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
298 nye versjonen kom på nyåret, og ble
299 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
300 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
301 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
302 måtte justeres, men ikke noe alvorlig. Har oppdatert
303 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
304 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
306 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
307 å spille for oss som liker slikt. :)
</p
>
309 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
310 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
312 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
313 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
318 <title>Debian now got everything you need to program Micro:bit
</title>
319 <link>http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
320 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
321 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
322 <description><p
>I am amazed and very pleased to discover that since a few days ago,
323 everything you need to program the
<a href=
"https://microbit.org/
">BBC
324 micro:bit
</a
> is available from the Debian archive. All this is
325 thanks to the hard work of Nick Morrott and the Debian python
326 packaging team. The micro:bit project recommend the mu-editor to
327 program the microcomputer, as this editor will take care of all the
328 machinery required to injekt/flash micropython alongside the program
329 into the micro:bit, as long as the pieces are available.
</p
>
331 <p
>There are three main pieces involved. The first to enter Debian
333 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
334 which was accepted into the archive
2019-
01-
12. The next one was
335 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
336 showed up
2019-
01-
13. The final and hardest part to to into the
338 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
339 which needed to get its build system and dependencies into Debian
340 before it was accepted
2019-
01-
20. The last one is already in Debian
341 Unstable and should enter Debian Testing / Buster in three days. This
342 all allow any user of the micro:bit to get going by simply running
343 'apt install mu-editor
' when using Testing or Unstable, and once
344 Buster is released as stable, all the users of Debian stable will be
345 catered for.
</p
>
347 <p
>As a minor final touch, I added rules to
348 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
349 package
</a
> for recognizing micro:bit and recommend the mu-editor
350 package. This make sure any user of the isenkram desktop daemon will
351 get a popup suggesting to install mu-editor then the USB cable from
352 the micro:bit is inserted for the first time.
</p
>
354 <p
>This should make it easier to have fun.
</p
>
356 <p
>As usual, if you use Bitcoin and want to show your support of my
357 activities, please send Bitcoin donations to my address
358 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
363 <title>Learn to program with Minetest on Debian
</title>
364 <link>http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
365 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
366 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
367 <description><p
>A fun way to learn how to program
368 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
369 instructions in the book
370 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
371 with Minecraft
</a
>", which introduces programming in Python to people
372 who like to play with Minecraft. The book uses a Python library to
373 talk to a TCP/IP socket with an API accepting build instructions and
374 providing information about the current players in a Minecraft world.
375 The TCP/IP API was first created for the Minecraft implementation for
376 Raspberry Pi, and has since been ported to some server versions of
377 Minecraft. The book contain recipes for those using Windows, MacOSX
378 and Raspian. But a little known fact is that you can follow the same
379 recipes using the free software construction game
380 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
382 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
383 Minetest module implementing the same API
</a
>, making it possible to
384 use the Python programs coded to talk to Minecraft with Minetest too.
386 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
387 this module
</a
> to Debian two weeks ago, and as soon as it clears the
388 FTP masters NEW queue, learning to program Python with Minetest on
389 Debian will be a simple
'apt install
' away. The Debian package is
390 maintained as part of the Debian Games team, and
391 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
392 packaging rules
</a
> are currently located under
'unfinished
' on
395 <p
>You will most likely need to install several of the Minetest
396 modules in Debian for the examples included with the library to work
397 well, as there are several blocks used by the example scripts that are
398 provided via modules in Minetest. Without the required blocks, a
399 simple stone block is used instead. My initial testing with a analog
400 clock did not get gold arms as instructed in the python library, but
401 instead used stone arms.
</p
>
403 <p
>I tried to find a way to add the API to the desktop version of
404 Minecraft, but were unable to find any working recipes. The
405 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
406 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
407 working with a standalone Minecraft server setup. Are there any
408 options to use with the normal desktop version?
</p
>
410 <p
>As usual, if you use Bitcoin and want to show your support of my
411 activities, please send Bitcoin donations to my address
412 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
417 <title>Time for an official MIME type for patches?
</title>
418 <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
419 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
420 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
421 <description><p
>As part of my involvement in
422 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
423 archive API project
</a
>, I
've been importing a fairly large lump of
424 emails into a test instance of the archive to see how well this would
425 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
426 notmuch email database
</a
>, all public emails sent to me via
427 @lists.debian.org, giving me a set of around
216 000 emails to import.
428 In the process, I had a look at the various attachments included in
429 these emails, to figure out what to do with attachments, and noticed
430 that one of the most common attachment formats do not have
431 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
432 official MIME type
</a
> registered with IANA/IETF. The output from
433 diff, ie the input for patch, is on the top
10 list of formats
434 included in these emails. At the moment people seem to use either
435 text/x-patch or text/x-diff, but neither is officially registered. It
436 would be better if one official MIME type were registered and used
437 everywhere.
</p
>
439 <p
>To try to get one official MIME type for these files, I
've brought
441 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
442 media-types mailing list
</a
>. If you are interested in discussion
443 which MIME type to use as the official for patch files, or involved in
444 making software using a MIME type for patches, perhaps you would like
445 to join the discussion?
</p
>
447 <p
>As usual, if you use Bitcoin and want to show your support of my
448 activities, please send Bitcoin donations to my address
449 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
454 <title>Automatic Google Drive sync using grive in Debian
</title>
455 <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
457 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
458 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
459 rescue the remains, I helped set up automatic sync with Google Drive.
460 I did not find any sensible Debian package handling this
461 automatically, so I rebuild the grive2 source from
462 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
463 task and added a autostart desktop entry and a small shell script to
464 run in the background while the user is logged in to do the sync.
465 Here is a sketch of the setup for future reference.
</p
>
467 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
468 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
469 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
470 to start the sync when the user log in:
</p
>
472 <p
><blockquote
><pre
>
474 Name=Google drive autosync
476 Exec=/home/user/bin/grive-sync
477 </pre
></blockquote
></p
>
479 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
480 ~/googledrive/ with the files in Google Drive.
</p
>
482 <p
><blockquote
><pre
>
487 if [
"$syncpid
" ] ; then
491 trap cleanup EXIT INT QUIT
492 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
495 if ! xhost
>/dev/null
2>&1 ; then
496 echo
"no DISPLAY, exiting as the user probably logged out
"
499 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
500 /usr/lib/grive/grive-sync.sh sync googledrive
503 done
2>&1 | sed
"s%^%$
0:%
"
504 </pre
></blockquote
></p
>
506 <p
>Feel free to use the setup if you want. It can be assumed to be
507 GNU GPL v2 licensed (or any later version, at your leisure), but I
508 doubt this code is possible to claim copyright on.
</p
>
510 <p
>As usual, if you use Bitcoin and want to show your support of my
511 activities, please send Bitcoin donations to my address
512 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
517 <title>Using the Kodi API to play Youtube videos
</title>
518 <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
519 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
520 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
521 <description><p
>I continue to explore my Kodi installation, and today I wanted to
522 tell it to play a youtube URL I received in a chat, without having to
523 insert search terms using the on-screen keyboard. After searching the
524 web for API access to the Youtube plugin and testing a bit, I managed
525 to find a recipe that worked. If you got a kodi instance with its API
526 available from http://kodihost/jsonrpc, you can try the following to
527 have check out a nice cover band.
</p
>
529 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
530 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
531 "params
": {
"item
": {
"file
":
532 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
533 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
535 <p
>I
've extended kodi-stream program to take a video source as its
536 first argument. It can now handle direct video links, youtube links
537 and
'desktop
' to stream my desktop to Kodi. It is almost like a
538 Chromecast. :)
</p
>
540 <p
>As usual, if you use Bitcoin and want to show your support of my
541 activities, please send Bitcoin donations to my address
542 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
547 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
548 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
549 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
550 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
551 <description><p
>For a while now, I have looked for a sensible way to share images
552 with my family using a self hosted solution, as it is unacceptable to
553 place images from my personal life under the control of strangers
554 working for data hoarders like Google or Dropbox. The last few days I
555 have drafted an approach that might work out, and I would like to
556 share it with you. I would like to publish images on a server under
557 my control, and point some Internet connected display units using some
558 free and open standard to the images I published. As my primary
559 language is not limited to ASCII, I need to store metadata using
560 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
561 of reading a RSS feed with image references (aka using the
562 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
563 of such frames. In the end I gave up that approach.
</p
>
565 <p
>Some months ago, I discovered that
566 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
567 read images from a RSS feed, and used it to set up a screen saver on
568 my home info screen, showing images from the Daily images feed from
569 NASA. This proved to work well. More recently I discovered that
570 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
571 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
572 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
573 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
574 screen saver capable of reading a RSS feed with images and news. For
575 fun, I used it this summer to test Kodi on my parents TV by hooking up
576 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
577 screen saver showing selected pictures from my selection.
</p
>
579 <p
>Armed with motivation and a test photo frame, I set out to generate
580 a RSS feed for the Kodi instance. I adjusted my
<a
581 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
582 /var/www/html/privatepictures/, wrote a small Perl script to extract
583 title and description metadata from the photo files and generate the
584 RSS file. I ended up using Perl instead of python, as the
585 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
586 tags I ended up using, while python3-exif did not. The relevant EXIF
587 tags only support ASCII, so I had to find better alternatives. XMP
588 seem to have the support I need.
</p
>
590 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
591 use tags that can be easily added/updated using normal free software
592 photo managing software. I ended up using the tags set using this
593 exiftool command, as these tags can also be set using digiKam:
</p
>
595 <blockquote
><pre
>
596 exiftool -headline=
'The RSS image title
' \
597 -description=
'The RSS image description.
' \
598 -subject+=for-family photo.jpeg
599 </pre
></blockquote
>
601 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
602 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
603 use the keyword/subject
'for-family
' to flag that the photo should be
604 shared with my family. Images with this keyword set are located and
605 copied into my Freedombox for the RSS generating script to find.
</p
>
607 <p
>Are there better ways to do this? Get in touch if you have better
608 suggestions.
</p
>
610 <p
>As usual, if you use Bitcoin and want to show your support of my
611 activities, please send Bitcoin donations to my address
612 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
617 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
618 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
620 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
621 <description><p
>Last night, I wrote
622 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
623 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
624 During the day I received valuable feedback, and thanks to the
625 suggestions I have been able to rewrite the recipe into a much simpler
626 approach requiring no setup at all. It is a single script that take
627 care of it all.
</p
>
629 <p
>This new script uses GStreamer instead of VLC to capture the
630 desktop and stream it to Kodi. This fixed the video quality issue I
631 saw initially. It further removes the need to add a m3u file on the
632 Kodi machine, as it instead connects to
633 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
634 Kodi
</a
> and simply ask Kodi to play from the stream created using
635 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
636 the script below, run it with the DNS name or IP address of the kodi
637 server to stream to as the only argument, and watch your screen show
638 up on the Kodi screen. Note, it depend on multicast on the local
639 network, so if you need to stream outside the local network, the
640 script must be modified. Also note, I have no idea if audio work, as
641 I only care about the picture part.
</p
>
643 <blockquote
><pre
>
646 # Stream the Linux desktop view to Kodi. See
647 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
648 # for backgorund information.
650 # Make sure the stream is stopped in Kodi and the gstreamer process is
651 # killed if something go wrong (for example if curl is unable to find the
652 # kodi server). Do the same when interrupting this script.
656 params=
"$
3"
657 curl --silent --header
'Content-Type: application/json
' \
658 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
659 "http://$host/jsonrpc
"
662 if [ -n
"$kodihost
" ] ; then
663 # Stop the playing when we end
664 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
665 jq .result[].playerid)
666 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
668 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
669 kill
"$gstpid
"
672 trap cleanup EXIT INT
674 if [ -n
"$
1" ]; then
685 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
686 cut -d
" " -f2|head -
1)
687 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
688 videoconvert ! queue2 ! \
689 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
690 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
691 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
692 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
693 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
694 > /dev/null
2>&1 &
697 # Give stream a second to get going
700 # Ask kodi to start streaming using its JSON-RPC API
701 kodicmd
"$kodihost
" Player.Open \
702 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
704 # wait for gst to end
705 wait
"$gstpid
"
706 </pre
></blockquote
>
708 <p
>I hope you find the approach useful. I know I do.
</p
>
710 <p
>As usual, if you use Bitcoin and want to show your support of my
711 activities, please send Bitcoin donations to my address
712 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
717 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
718 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
719 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
720 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
721 <description><p
>PS: See
722 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
723 followup post
</a
> for a even better approach.
</p
>
725 <p
>A while back, I was asked by a friend how to stream the desktop to
726 my projector connected to Kodi. I sadly had to admit that I had no
727 idea, as it was a task I never had tried. Since then, I have been
728 looking for a way to do so, preferable without much extra software to
729 install on either side. Today I found a way that seem to kind of
730 work. Not great, but it is a start.
</p
>
732 <p
>I had a look at several approaches, for example
733 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
734 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
735 local storage enough to store the stream locally. This is not going
736 to work well for me, lacking enough free space, and it would
737 impossible for my friend to get working.
</p
>
739 <p
>Next, it occurred to me that perhaps I could use VLC to create a
740 video stream that Kodi could play. Preferably using
741 broadcast/multicast, to avoid having to change any setup on the Kodi
742 side when starting such stream. Unfortunately, the only recipe I
743 could find using multicast used the rtp protocol, and this protocol
744 seem to not be supported by Kodi.
</p
>
746 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
747 have to specify the IP address of the streaming machine in both the
748 sending command and the file on the Kodi server. But it is showing my
749 desktop, and thus allow us to have a shared look on the big screen at
750 the programs I work on.
</p
>
752 <p
>I did not spend much time investigating codeces. I combined the
753 rtp and rtsp recipes from
754 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
755 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
756 this working on the desktop/streaming end.
</p
>
758 <blockquote
><pre
>
759 vlc screen:// --sout \
760 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
761 </pre
></blockquote
>
763 <p
>I ssh-ed into my Kodi box and created a file like this with the
764 same IP address:
</p
>
766 <blockquote
><pre
>
767 echo rtsp://
192.168.11.4:
8080/test.sdp \
768 > /storage/videos/screenstream.m3u
769 </pre
></blockquote
>
771 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
772 as I can tell the IP must be hardcoded for this to work. In other
773 words, if someone elses machine is going to do the steaming, you have
774 to update screenstream.m3u on the Kodi machine and adjust the vlc
775 recipe. To get started, locate the file in Kodi and select the m3u
776 file while the VLC stream is running. The desktop then show up in my
777 big screen. :)
</p
>
779 <p
>When using the same technique to stream a video file with audio,
780 the audio quality is really bad. No idea if the problem is package
781 loss or bad parameters for the transcode. I do not know VLC nor Kodi
782 enough to tell.
</p
>
784 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
785 succestions and reminded me about an important step. The
"screen:
"
786 input source is only available once the vlc-plugin-access-extra
787 package is installed on Debian. Without it, you will see this error
788 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
789 for details.
" He further found that it is possible to drop some parts
790 of the VLC command line to reduce the amount of hardcoded information.
791 It is also useful to consider using cvlc to avoid having the VLC
792 window in the desktop view. In sum, this give us this command line on
795 <blockquote
><pre
>
796 cvlc screen:// --sout \
797 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
798 </pre
></blockquote
>
800 <p
>and this on the Kodi end
<p
>
802 <blockquote
><pre
>
803 echo rtsp://
192.168.11.4:
8080/ \
804 > /storage/videos/screenstream.m3u
805 </pre
></blockquote
>
807 <p
>Still bad image quality, though. But I did discover that streaming
808 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
809 audio quality, so I guess the issue is in the input or transcoding
810 parts, not the rtsp part. I
've tried to change the vb and ab
811 parameters to use more bandwidth, but it did not make a
812 difference.
</p
>
814 <p
>I further received a suggestion from Einar Haraldseid to try using
815 gstreamer instead of VLC, and this proved to work great! He also
816 provided me with the trick to get Kodi to use a multicast stream as
817 its source. By using this monstrous oneliner, I can stream my desktop
818 with good video quality in reasonable framerate to the
239.255.0.1
819 multicast address on port
1234:
821 <blockquote
><pre
>
822 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
823 videoconvert ! queue2 ! \
824 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
825 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
826 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
827 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
828 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
829 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
830 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
831 </pre
></blockquote
>
833 <p
>and this on the Kodi end
<p
>
835 <blockquote
><pre
>
836 echo udp://@
239.255.0.1:
1234 \
837 > /storage/videos/screenstream.m3u
838 </pre
></blockquote
>
840 <p
>Note the trick to pick a valid pulseaudio source. It might not
841 pick the one you need. This approach will of course lead to trouble
842 if more than one source uses the same multicast port and address.
843 Note the ttl-mc=
1 setting, which limit the multicast packages to the
844 local network. If the value is increased, your screen will be
845 broadcasted further, one network
"hop
" for each increase (read up on
846 multicast to learn more. :)!
</p
>
848 <p
>Having cracked how to get Kodi to receive multicast streams, I
849 could use this VLC command to stream to the same multicast address.
850 The image quality is way better than the rtsp approach, but gstreamer
851 seem to be doing a better job.
</p
>
853 <blockquote
><pre
>
854 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
855 </pre
></blockquote
>
857 <p
>As usual, if you use Bitcoin and want to show your support of my
858 activities, please send Bitcoin donations to my address
859 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
864 <title>What is the most supported MIME type in Debian in
2018?
</title>
865 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
866 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
867 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
868 <description><p
>Five years ago,
869 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
870 measured what the most supported MIME type in Debian was
</a
>, by
871 analysing the desktop files in all packages in the archive. Since
872 then, the DEP-
11 AppStream system has been put into production, making
873 the task a lot easier. This made me want to repeat the measurement,
874 to see how much things changed. Here are the new numbers, for
875 unstable only this time:
877 <p
><strong
>Debian Unstable:
</strong
></p
>
881 ----- -----------------------
893 30 audio/x-vorbis+ogg
894 29 image/x-portable-pixmap
896 27 image/x-portable-bitmap
904 <p
>The list was created like this using a sid chroot:
"cat
905 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
906 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
908 <p
>It is interesting to see how image formats have passed text/plain
909 as the most announced supported MIME type. These days, thanks to the
910 AppStream system, if you run into a file format you do not know, and
911 want to figure out which packages support the format, you can find the
912 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
913 look up all packages announcing support for this format in their
914 AppStream metadata (XML or .desktop file) using
"appstreamcli
915 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
916 me, want to know which packages support inode/directory, you can get a
917 list like this:
</p
>
919 <p
><blockquote
><pre
>
920 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
927 Package: doublecmd-common
929 Package: enlightenment
949 </pre
></blockquote
></p
>
951 <p
>Using the same method, I can quickly discover that the Sketchup file
952 format is not yet supported by any package in Debian:
</p
>
954 <p
><blockquote
><pre
>
955 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
956 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
958 </pre
></blockquote
></p
>
960 <p
>Yesterday I used it to figure out which packages support the STL
3D
963 <p
><blockquote
><pre
>
964 % appstreamcli what-provides mimetype application/sla|grep Package
969 </pre
></blockquote
></p
>
971 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
973 <p
>As usual, if you use Bitcoin and want to show your support of my
974 activities, please send Bitcoin donations to my address
975 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
980 <title>Debian APT upgrade without enough free space on the disk...
</title>
981 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
982 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
983 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
984 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
985 for a while, and when I need to update it there is not enough free
986 space on the disk for apt to do a normal
'apt upgrade
'. I normally
987 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
988 upgrade only some of the packages in one batch, until the amount of
989 packages to download fall below the amount of free space available.
990 Today, I had about
500 packages to upgrade, and after a while I got
991 tired of trying to install chunks of packages manually. I concluded
992 that I did not have the spare hours required to complete the task, and
993 decided to see if I could automate it. I came up with this small
994 script which I call
'apt-in-chunks
':
</p
>
996 <p
><blockquote
><pre
>
999 # Upgrade packages when the disk is too full to upgrade every
1000 # upgradable package in one lump. Fetching packages to upgrade using
1001 # apt, and then installing using dpkg, to avoid changing the package
1002 # flag for manual/automatic.
1007 if [
"$
1" ]; then
1008 grep -v
"$
1"
1014 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
1015 echo
"Upgrading $p
"
1017 apt install --download-only -y $p
1018 for f in /var/cache/apt/archives/*.deb; do
1019 if [ -e
"$f
" ]; then
1020 dpkg -i /var/cache/apt/archives/*.deb
1025 </pre
></blockquote
></p
>
1027 <p
>The script will extract the list of packages to upgrade, try to
1028 download the packages needed to upgrade one package, install the
1029 downloaded packages using dpkg. The idea is to upgrade packages
1030 without changing the APT mark for the package (ie the one recording of
1031 the package was manually requested or pulled in as a dependency). To
1032 use it, simply run it as root from the command line. If it fail, try
1033 'apt install -f
' to clean up the mess and run the script again. This
1034 might happen if the new packages conflict with one of the old
1035 packages. dpkg is unable to remove, while apt can do this.
</p
>
1037 <p
>It take one option, a package to ignore in the list of packages to
1038 upgrade. The option to ignore a package is there to be able to skip
1039 the packages that are simply too large to unpack. Today this was
1040 'ghc
', but I have run into other large packages causing similar
1041 problems earlier (like TeX).
</p
>
1043 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
1044 alternative ways to handle this. The
"unattended-upgrades
1045 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
1046 each package to upgrade, and then upgrade them in order, smallest set
1047 first. It might be a better option than my above mentioned script.
1048 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
1049 the need for using
"dpkg -i
" in the script above.
</p
>
1051 <p
>As usual, if you use Bitcoin and want to show your support of my
1052 activities, please send Bitcoin donations to my address
1053 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1058 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
1059 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
1060 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
1061 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
1062 <description><p
>A new version of the
1063 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
1064 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
1065 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
1066 useful. It was uploaded the last few days, and the last update will
1067 enter testing tomorrow. See the
1068 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
1069 notes
</a
> for the list of bug fixes and new features. Version
3.2
1070 was announced
6 days ago. We will try to get it into Debian as
1073 <p
>More information related to
3D printing is available on the
1074 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
1075 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
1076 in Debian.
</p
>
1078 <p
>As usual, if you use Bitcoin and want to show your support of my
1079 activities, please send Bitcoin donations to my address
1080 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1085 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
1086 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
1087 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
1088 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
1089 <description><p
>After several months of working and waiting, I am happy to report
1090 that the nice and user friendly
3D printer slicer software Cura just
1091 entered Debian Unstable. It consist of five packages,
1092 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
1093 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
1094 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
1095 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
1096 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
1097 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
1098 two, uranium and cura, entered Unstable yesterday. This should make
1099 it easier for Debian users to print on at least the Ultimaker class of
1100 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
1101 make life easier for at least me. :)
</p
>
1103 <p
>The work to make this happen was done by Gregor Riepl, and I was
1104 happy to assist him in sponsoring the packages. With the introduction
1105 of Cura, Debian is up to three
3D printer slicers at your service,
1106 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
1107 printer, give it a go. :)
</p
>
1109 <p
>The
3D printer software is maintained by the
3D printer Debian
1110 team, flocking together on the
1111 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
1112 mailing list and the
1113 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
1114 IRC channel.
</p
>
1116 <p
>The next step for Cura in Debian is to update the cura package to
1117 version
3.0.3 and then update the entire set of packages to version
1118 3.1.0 which showed up the last few days.
</p
>
1123 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
1124 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
1125 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
1126 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
1127 <description><p
>At my nearby maker space,
1128 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
1129 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
1130 on Windows and MacOS X than Linux, because the software involved had
1131 to be manually compiled and set up on Linux while premade packages
1132 worked out of the box on Windows and MacOS X. I found this annoying,
1133 as the software involved,
1134 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
1135 and should be trivial to get up and running on Linux if someone took
1136 the time to package it for the relevant distributions. I even found
1137 <a href=
"https://bugs.debian.org/
706656">a request for adding into
1138 Debian
</a
> from
2013, which had seem some activity over the years but
1139 never resulted in the software showing up in Debian. So a few days
1140 ago I offered my help to try to improve the situation.
</p
>
1142 <p
>Now I am very happy to see that all the packages required by a
1143 working Cura in Debian are uploaded into Debian and waiting in the NEW
1144 queue for the ftpmasters to have a look. You can track the progress
1146 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
1147 status page for the
3D printer team
</a
>.
</p
>
1149 <p
>The uploaded packages are a bit behind upstream, and was uploaded
1150 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
1151 queue
</a
> while we work up updating the packages to the latest
1152 upstream version.
</p
>
1154 <p
>On a related note, two competitors for Cura, which I found harder
1155 to use and was unable to configure correctly for Ultimaker
2+ in the
1156 short time I spent on it, are already in Debian. If you are looking
1157 for
3D printer
"slicers
" and want something already available in
1159 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
1160 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
1161 The latter is a fork of the former.
</p
>
1163 <p
>As usual, if you use Bitcoin and want to show your support of my
1164 activities, please send Bitcoin donations to my address
1165 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1170 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
1171 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
1172 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
1173 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
1174 <description><p
>Every mobile phone announce its existence over radio to the nearby
1175 mobile cell towers. And this radio chatter is available for anyone
1176 with a radio receiver capable of receiving them. Details about the
1177 mobile phones with very good accuracy is of course collected by the
1178 phone companies, but this is not the topic of this blog post. The
1179 mobile phone radio chatter make it possible to figure out when a cell
1180 phone is nearby, as it include the SIM card ID (IMSI). By paying
1181 attention over time, one can see when a phone arrive and when it leave
1182 an area. I believe it would be nice to make this information more
1183 available to the general public, to make more people aware of how
1184 their phones are announcing their whereabouts to anyone that care to
1187 <p
>I am very happy to report that we managed to get something
1188 visualizing this information up and running for
1189 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
1190 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
1191 library. The solution is based on the
1192 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
1193 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
1194 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
1195 Sone from the Computer Science department of the University of
1196 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
1197 IMSIs) as dots in a web browser graph, with lines to the dot
1198 representing mobile base station it is talking to. It was working in
1199 the lab yesterday, and was moved into place this morning.
</p
>
1201 <p
>We set up a fairly powerful desktop machine using Debian
1202 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
1203 connected and visualize the visible cell phone towers using an
1204 <a href=
"https://github.com/marlow925/hopglass
">English version of
1205 Hopglass
</a
>. A fairly powerfull machine is needed as the
1206 grgsm_livemon_headless processes from
1207 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
1208 the radio signal to data packages is quite CPU intensive.
</p
>
1210 <p
>The frequencies to listen to, are identified using a slightly
1211 patched scan-and-livemon (to set the --args values for each receiver),
1212 and the Hopglass data is generated using the
1213 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
1214 in my meshviewer-output branch
</a
>. For some reason we could not get
1215 more than four SDRs working. There is also a geographical map trying
1216 to show the location of the base stations, but I believe their
1217 coordinates are hardcoded to some random location in Germany, I
1218 believe. The code should be replaced with code to look up location in
1219 a text file, a sqlite database or one of the online databases
1221 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
1222 issue for the topic
</a
>.
1224 <p
>If this sound interesting, visit the stand at the festival!
</p
>
1229 <title>Easier recipe to observe the cell phones around you
</title>
1230 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
1231 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
1232 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
1233 <description><p
>A little more than a month ago I wrote
1234 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
1235 to observe the SIM card ID (aka IMSI number) of mobile phones talking
1236 to nearby mobile phone base stations using Debian GNU/Linux and a
1237 cheap USB software defined radio
</a
>, and thus being able to pinpoint
1238 the location of people and equipment (like cars and trains) with an
1239 accuracy of a few kilometer. Since then we have worked to make the
1240 procedure even simpler, and it is now possible to do this without any
1241 manual frequency tuning and without building your own packages.
</p
>
1243 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
1244 package is now included in Debian testing and unstable, and the
1245 IMSI-catcher code no longer require root access to fetch and decode
1246 the GSM data collected using gr-gsm.
</p
>
1248 <p
>Here is an updated recipe, using packages built by Debian and a git
1249 clone of two python scripts:
</p
>
1253 <li
>Start with a Debian machine running the Buster version (aka
1254 testing).
</li
>
1256 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
1257 python-scapy
</tt
>' as root to install required packages.
</li
>
1259 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
1260 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
1262 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
1264 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
1265 scan-and-livemon
</tt
>' to locate the frequency of nearby base
1266 stations and start listening for GSM packages on one of them.
</li
>
1268 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
1269 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
1273 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
1274 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
1275 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
1276 work with RTL
8232 and other similar USB radio receivers you can get
1278 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
1279 from ebay
</a
>), so for now the solution is to scan using the RTL radio
1280 and only use HackRF for fetching GSM data.
</p
>
1282 <p
>As far as I can tell, a cell phone only show up on one of the
1283 frequencies at the time, so if you are going to track and count every
1284 cell phone around you, you need to listen to all the frequencies used.
1285 To listen to several frequencies, use the --numrecv argument to
1286 scan-and-livemon to use several receivers. Further, I am not sure if
1287 phones using
3G or
4G will show as talking GSM to base stations, so
1288 this approach might not see all phones around you. I typically see
1289 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
1291 <p
>I
've tried to run the scanner on a
1292 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
1293 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
1294 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
1295 stdout, I am told there it is caused by a buffer overflow between the
1296 radio and GNU Radio, caused by the program being unable to read the
1297 GSM data fast enough. If you see a stream of
'O
's from the terminal
1298 where you started scan-and-livemon, you need a give the process more
1299 CPU power. Perhaps someone are able to optimize the code to a point
1300 where it become possible to set up RPi3 based GSM sniffers? I tried
1301 using Raspbian instead of Debian, but there seem to be something wrong
1302 with GNU Radio on raspbian, causing glibc to abort().
</p
>
1307 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
1308 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
1309 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
1310 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
1311 <description><p
>On friday, I came across an interesting article in the Norwegian
1312 web based ICT news magazine digi.no on
1313 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
1314 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
1315 DVB-T software defined radios. The article refered to instructions
1316 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
1317 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
1319 <p
>The instructions said to use Ubuntu, install pip using apt (to
1320 bypass apt), use pip to install pybombs (to bypass both apt and pip),
1321 and the ask pybombs to fetch and build everything you need from
1322 scratch. I wanted to see if I could do the same on the most recent
1323 Debian packages, but this did not work because pybombs tried to build
1324 stuff that no longer build with the most recent openssl library or
1325 some other version skew problem. While trying to get this recipe
1326 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
1327 and the only piece of software dependency missing in Debian was the
1328 gr-gsm package. I also found out that the lead upstream developer of
1329 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
1330 Debian packages provided in an Ubuntu PPA repository. All I needed to
1331 do was to dget the Debian source package and built it.
</p
>
1333 <p
>The IMSI collector is a python script listening for packages on the
1334 loopback network device and printing to the terminal some specific GSM
1335 packages with IMSI numbers in them. The code is fairly short and easy
1336 to understand. The reason this work is because gr-gsm include a tool
1337 to read GSM data from a software defined radio like a DVB-T USB stick
1338 and other software defined radios, decode them and inject them into a
1339 network device on your Linux machine (using the loopback device by
1340 default). This proved to work just fine, and I
've been testing the
1341 collector for a few days now.
</p
>
1343 <p
>The updated and simpler recipe is thus to
</p
>
1347 <li
>start with a Debian machine running Stretch or newer,
</li
>
1349 <li
>build and install the gr-gsm package available from
1350 <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
>
1352 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
1354 <li
>run grgsm_livemon and adjust the frequency until the terminal
1355 where it was started is filled with a stream of text (meaning you
1356 found a GSM station).
</li
>
1358 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
1362 <p
>To make it even easier in the future to get this sniffer up and
1363 running, I decided to package
1364 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
1365 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
1366 #
871055</a
>), and the package was uploaded into the NEW queue today.
1367 Luckily the gnuradio maintainer has promised to help me, as I do not
1368 know much about gnuradio stuff yet.
</p
>
1370 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
1371 commercial tools like
1372 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
1373 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
1374 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
1375 Stingray
</a
>, but I hope the existance of cheap alternatives can make
1376 more people realise how their whereabouts when carrying a cell phone
1377 is easily tracked. Seeing the data flow on the screen, realizing that
1378 I live close to a police station and knowing that the police is also
1379 wearing cell phones, I wonder how hard it would be for criminals to
1380 track the position of the police officers to discover when there are
1381 police near by, or for foreign military forces to track the location
1382 of the Norwegian military forces, or for anyone to track the location
1383 of government officials...
</p
>
1385 <p
>It is worth noting that the data reported by the IMSI-catcher
1386 script mentioned above is only a fraction of the data broadcasted on
1387 the GSM network. It will only collect one frequency at the time,
1388 while a typical phone will be using several frequencies, and not all
1389 phones will be using the frequencies tracked by the grgsm_livemod
1390 program. Also, there is a lot of radio chatter being ignored by the
1391 simple_IMSI-catcher script, which would be collected by extending the
1392 parser code. I wonder if gr-gsm can be set up to listen to more than
1393 one frequency?
</p
>
1398 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
1399 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
1400 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
1401 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
1402 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
1404 <p
>I finally received a copy of the Norwegian Bokmål edition of
1405 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1406 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
1407 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
1408 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
1409 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
1410 price. The book is also available for download in electronic form as
1411 PDF, EPUB and Mobipocket, as can be
1412 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
1413 as a web page
</a
>.
</p
>
1415 <p
>This is the second book I publish (the first was the book
1416 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
1418 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
1419 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
1421 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
1422 Bokmål
</a
>), and I am very excited to finally wrap up this
1424 "<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
1425 for Debian-administratoren
</a
>" will be well received.
</p
>
1430 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
1431 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
1432 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
1433 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
1434 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
1435 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
1436 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
1437 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
1438 på om den fri oversetterløsningen
1439 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
1440 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
1442 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
1445 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
1446 rolle og muligheter til å håndtere internasjonale utfordringer, som
1447 for eksempel flykningekrisen.
</p
>
1449 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
1450 på temaet:
</p
>
1452 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
1453 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
1458 <p
>Dette oversetter Apertium slik:
</p
>
1461 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
1462 andre aktørar og høve til å handtera internasjonale utfordringar, som
1463 til dømes *flykningekrisen.
</p
>
1465 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
1469 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
1470 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
1475 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
1476 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
1477 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
1478 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
1479 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
1480 det er kanskje flisespikking. Det understreker vel bare at det alltid
1481 trengs korrekturlesning etter automatisk oversettelse.
</p
>
1486 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
1487 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
1488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
1489 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
1490 <description><p
>Over the years, administrating thousand of NFS mounting linux
1491 computers at the time, I often needed a way to detect if the machine
1492 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
1493 file or directory affected by the hang, the process (and possibly the
1494 shell) will hang too. So you want to be able to detect this without
1495 risking the detection process getting stuck too. It has not been
1496 obvious how to do this. When the hang has lasted a while, it is
1497 possible to find messages like these in dmesg:
</p
>
1499 <p
><blockquote
>
1500 nfs: server nfsserver not responding, still trying
1501 <br
>nfs: server nfsserver OK
1502 </blockquote
></p
>
1504 <p
>It is hard to know if the hang is still going on, and it is hard to
1505 be sure looking in dmesg is going to work. If there are lots of other
1506 messages in dmesg the lines might have rotated out of site before they
1507 are noticed.
</p
>
1509 <p
>While reading through the nfs client implementation in linux kernel
1510 code, I came across some statistics that seem to give a way to detect
1511 it. The om_timeouts sunrpc value in the kernel will increase every
1512 time the above log entry is inserted into dmesg. And after digging a
1513 bit further, I discovered that this value show up in
1514 /proc/self/mountstats on Linux.
</p
>
1516 <p
>The mountstats content seem to be shared between files using the
1517 same file system context, so it is enough to check one of the
1518 mountstats files to get the state of the mount point for the machine.
1519 I assume this will not show lazy umounted NFS points, nor NFS mount
1520 points in a different process context (ie with a different filesystem
1521 view), but that does not worry me.
</p
>
1523 <p
>The content for a NFS mount point look similar to this:
</p
>
1525 <p
><blockquote
><pre
>
1527 device /dev/mapper/Debian-var mounted on /var with fstype ext3
1528 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
1529 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
1531 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
1532 sec: flavor=
1,pseudoflavor=
1
1533 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
1534 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
1535 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
1536 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1538 NULL:
0 0 0 0 0 0 0 0
1539 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1540 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
1541 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1542 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1543 READLINK:
125 125 0 20472 18620 0 1112 1118
1544 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1545 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1546 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
1547 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
1548 SYMLINK:
903 903 0 233428 245488 6 5865 5917
1549 MKNOD:
80 80 0 20148 21760 0 299 304
1550 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
1551 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
1552 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
1553 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
1554 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1555 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1556 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
1557 FSINFO:
2 2 0 232 328 0 1 1
1558 PATHCONF:
1 1 0 116 140 0 0 0
1559 COMMIT:
0 0 0 0 0 0 0 0
1561 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1563 </pre
></blockquote
></p
>
1565 <p
>The key number to look at is the third number in the per-op list.
1566 It is the number of NFS timeouts experiences per file system
1567 operation. Here
22 write timeouts and
5 access timeouts. If these
1568 numbers are increasing, I believe the machine is experiencing NFS
1569 hang. Unfortunately the timeout value do not start to increase right
1570 away. The NFS operations need to time out first, and this can take a
1571 while. The exact timeout value depend on the setup. For example the
1572 defaults for TCP and UDP mount points are quite different, and the
1573 timeout value is affected by the soft, hard, timeo and retrans NFS
1574 mount options.
</p
>
1576 <p
>The only way I have been able to get working on Debian and RedHat
1577 Enterprise Linux for getting the timeout count is to peek in /proc/.
1579 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
1580 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
1581 command can be used to get these timeout values. But this do not work
1582 on Linux, as far as I can tell. I
1583 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
1584 but have not seen any replies yet.
</p
>
1586 <p
>Is there a better way to figure out if a Linux NFS client is
1587 experiencing NFS hangs? Is there a way to detect which processes are
1588 affected? Is there a way to get the NFS mount going quickly once the
1589 network problem causing the NFS hang has been cleared? I would very
1590 much welcome some clues, as we regularly run into NFS hangs.
</p
>
1595 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
1596 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
1597 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</guid>
1598 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
1599 <description><p
>For almost a year now, we have been working on making a Norwegian
1600 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
1601 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
1602 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1603 we are working on the proof reading to ensure consistent language and
1604 use of correct computer science terms. The plan is to make the book
1605 available on paper, as well as in electronic form. For that to
1606 happen, the proof reading must be completed and all the figures need
1607 to be translated. If you want to help out, get in touch.
</p
>
1609 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
1611 fresh PDF edition
</a
> in A4 format (the final book will have smaller
1612 pages) of the book created every morning is available for
1613 proofreading. If you find any errors, please
1614 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
1615 Weblate and correct the error
</a
>. The
1616 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
1617 of the translation including figures
</a
> is a useful source for those
1618 provide Norwegian bokmål screen shots and figures.
</p
>
1623 <title>Unlimited randomness with the ChaosKey?
</title>
1624 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
1625 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
1626 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
1627 <description><p
>A few days ago I ordered a small batch of
1628 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
1629 USB dongle for generating entropy created by Bdale Garbee and Keith
1630 Packard. Yesterday it arrived, and I am very happy to report that it
1631 work great! According to its designers, to get it to work out of the
1632 box, you need the Linux kernel version
4.1 or later. I tested on a
1633 Debian Stretch machine (kernel version
4.9), and there it worked just
1634 fine, increasing the available entropy very quickly. I wrote a small
1635 test oneliner to test. It first print the current entropy level,
1636 drain /dev/random, and then print the entropy level for five seconds.
1637 Here is the situation without the ChaosKey inserted:
</p
>
1639 <blockquote
><pre
>
1640 % cat /proc/sys/kernel/random/entropy_avail; \
1641 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
1642 for n in $(seq
1 5); do \
1643 cat /proc/sys/kernel/random/entropy_avail; \
1649 28 byte kopiert,
0,
000264565 s,
106 kB/s
1656 </pre
></blockquote
>
1658 <p
>The entropy level increases by
3-
4 every second. In such case any
1659 application requiring random bits (like a HTTPS enabled web server)
1660 will halt and wait for more entrpy. And here is the situation with
1661 the ChaosKey inserted:
</p
>
1663 <blockquote
><pre
>
1664 % cat /proc/sys/kernel/random/entropy_avail; \
1665 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
1666 for n in $(seq
1 5); do \
1667 cat /proc/sys/kernel/random/entropy_avail; \
1673 104 byte kopiert,
0,
000487647 s,
213 kB/s
1680 </pre
></blockquote
>
1682 <p
>Quite the difference. :) I bought a few more than I need, in case
1683 someone want to buy one here in Norway. :)
</p
>
1685 <p
>Update: The dongle was presented at Debconf last year. You might
1686 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
1687 recording illuminating
</a
>. It explains exactly what the source of
1688 randomness is, if you are unable to spot it from the schema drawing
1689 available from the ChaosKey web site linked at the start of this blog
1695 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
1696 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
1697 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
1698 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
1699 <description><p
>Did you ever wonder where the web trafic really flow to reach the
1700 web servers, and who own the network equipment it is flowing through?
1701 It is possible to get a glimpse of this from using traceroute, but it
1702 is hard to find all the details. Many years ago, I wrote a system to
1703 map the Norwegian Internet (trying to figure out if our plans for a
1704 network game service would get low enough latency, and who we needed
1705 to talk to about setting up game servers close to the users. Back
1706 then I used traceroute output from many locations (I asked my friends
1707 to run a script and send me their traceroute output) to create the
1708 graph and the map. The output from traceroute typically look like
1711 <p
><pre
>
1712 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
1713 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
1714 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
1715 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
1716 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
1717 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
1718 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
1719 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
1723 </pre
></p
>
1725 <p
>This show the DNS names and IP addresses of (at least some of the)
1726 network equipment involved in getting the data traffic from me to the
1727 www.stortinget.no server, and how long it took in milliseconds for a
1728 package to reach the equipment and return to me. Three packages are
1729 sent, and some times the packages do not follow the same path. This
1730 is shown for hop
5, where three different IP addresses replied to the
1731 traceroute request.
</p
>
1733 <p
>There are many ways to measure trace routes. Other good traceroute
1734 implementations I use are traceroute (using ICMP packages) mtr (can do
1735 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1736 traceroute and a lot of other capabilities). All of them are easily
1737 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
1739 <p
>This time around, I wanted to know the geographic location of
1740 different route points, to visualize how visiting a web page spread
1741 information about the visit to a lot of servers around the globe. The
1742 background is that a web site today often will ask the browser to get
1743 from many servers the parts (for example HTML, JSON, fonts,
1744 JavaScript, CSS, video) required to display the content. This will
1745 leak information about the visit to those controlling these servers
1746 and anyone able to peek at the data traffic passing by (like your ISP,
1747 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
1749 <p
>Lets pick an example, the Norwegian parliament web site
1750 www.stortinget.no. It is read daily by all members of parliament and
1751 their staff, as well as political journalists, activits and many other
1752 citizens of Norway. A visit to the www.stortinget.no web site will
1753 ask your browser to contact
8 other servers: ajax.googleapis.com,
1754 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1755 stats.g.doubleclick.net, www.google-analytics.com,
1756 www.googletagmanager.com and www.netigate.se. I extracted this by
1757 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
1758 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1759 render the page (in HAR format using
1760 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
1761 netsniff example
</a
>. I am very grateful to Gorm for showing me how
1762 to do this). My goal is to visualize network traces to all IP
1763 addresses behind these DNS names, do show where visitors personal
1764 information is spread when visiting the page.
</p
>
1766 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
1767 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
>
1769 <p
>When I had a look around for options, I could not find any good
1770 free software tools to do this, and decided I needed my own traceroute
1771 wrapper outputting KML based on locations looked up using GeoIP. KML
1772 is easy to work with and easy to generate, and understood by several
1773 of the GIS tools I have available. I got good help from by NUUG
1774 colleague Anders Einar with this, and the result can be seen in
1775 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
1776 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
1777 free GeoIP databases I could find (and the for-pay databases my
1778 friends had access to) is not up to the task. The IP addresses of
1779 central Internet infrastructure would typically be placed near the
1780 controlling companies main office, and not where the router is really
1781 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
1782 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
1784 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
1785 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
>
1787 <p
>I also had a look at the visual traceroute graph created by
1788 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
1789 showing IP network ownership (aka AS owner) for the IP address in
1791 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
1792 graph display a lot of useful information about the traceroute in SVG
1793 format
</a
>, and give a good indication on who control the network
1794 equipment involved, but it do not include geolocation. This graph
1795 make it possible to see the information is made available at least for
1796 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1797 3 Communications and NetDNA.
</p
>
1799 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
1800 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
>
1802 <p
>In the process, I came across the
1803 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
1804 Salim Gasmi. Its methology of combining guesses based on DNS names,
1805 various location databases and finally use latecy times to rule out
1806 candidate locations seemed to do a very good job of guessing correct
1807 geolocation. But it could only do one trace at the time, did not have
1808 a sensor in Norway and did not make the geolocations easily available
1809 for postprocessing. So I contacted the developer and asked if he
1810 would be willing to share the code (he refused until he had time to
1811 clean it up), but he was interested in providing the geolocations in a
1812 machine readable format, and willing to set up a sensor in Norway. So
1813 since yesterday, it is possible to run traces from Norway in this
1814 service thanks to a sensor node set up by
1815 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
1816 trace in KML format for further processing.
</p
>
1818 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
1819 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
>
1821 <p
>Here we can see a lot of trafic passes Sweden on its way to
1822 Denmark, Germany, Holland and Ireland. Plenty of places where the
1823 Snowden confirmations verified the traffic is read by various actors
1824 without your best interest as their top priority.
</p
>
1826 <p
>Combining KML files is trivial using a text editor, so I could loop
1827 over all the hosts behind the urls imported by www.stortinget.no and
1828 ask for the KML file from GeoTraceroute, and create a combined KML
1829 file with all the traces (unfortunately only one of the IP addresses
1830 behind the DNS name is traced this time. To get them all, one would
1831 have to request traces using IP number instead of DNS names from
1832 GeoTraceroute). That might be the next step in this project.
</p
>
1834 <p
>Armed with these tools, I find it a lot easier to figure out where
1835 the IP traffic moves and who control the boxes involved in moving it.
1836 And every time the link crosses for example the Swedish border, we can
1837 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1838 Britain and NSA in USA and cables around the globe. (Hm, what should
1839 we tell them? :) Keep that in mind if you ever send anything
1840 unencrypted over the Internet.
</p
>
1842 <p
>PS: KML files are drawn using
1843 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
1844 Rublev
<a/
>, as it was less cluttered than the local Linux application
1845 Marble. There are heaps of other options too.
</p
>
1847 <p
>As usual, if you use Bitcoin and want to show your support of my
1848 activities, please send Bitcoin donations to my address
1849 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1854 <title>Appstream just learned how to map hardware to packages too!
</title>
1855 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
1856 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
1857 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
1858 <description><p
>I received a very nice Christmas present today. As my regular
1859 readers probably know, I have been working on the
1860 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
1861 system
</a
> for many years. The goal of the Isenkram system is to make
1862 it easier for users to figure out what to install to get a given piece
1863 of hardware to work in Debian, and a key part of this system is a way
1864 to map hardware to packages. Isenkram have its own mapping database,
1865 and also uses data provided by each package using the AppStream
1866 metadata format. And today,
1867 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
1868 Debian learned to look up hardware the same way Isenkram is doing it,
1869 ie using fnmatch():
</p
>
1871 <p
><pre
>
1872 % appstreamcli what-provides modalias \
1873 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1874 Identifier: pymissile [generic]
1876 Summary: Control original Striker USB Missile Launcher
1878 % appstreamcli what-provides modalias usb:v0694p0002d0000
1879 Identifier: libnxt [generic]
1881 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1884 Identifier: t2n [generic]
1886 Summary: Simple command-line tool for Lego NXT
1889 Identifier: python-nxt [generic]
1891 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1894 Identifier: nbc [generic]
1896 Summary: C compiler for LEGO Mindstorms NXT bricks
1899 </pre
></p
>
1901 <p
>A similar query can be done using the combined AppStream and
1902 Isenkram databases using the isenkram-lookup tool:
</p
>
1904 <p
><pre
>
1905 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1907 % isenkram-lookup usb:v0694p0002d0000
1913 </pre
></p
>
1915 <p
>You can find modalias values relevant for your machine using
1916 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
1918 <p
>If you want to make this system a success and help Debian users
1919 make the most of the hardware they have, please
1920 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
1921 AppStream metadata for your package following the guidelines
</a
>
1922 documented in the wiki. So far only
11 packages provide such
1923 information, among the several hundred hardware specific packages in
1924 Debian. The Isenkram database on the other hand contain
101 packages,
1925 mostly related to USB dongles. Most of the packages with hardware
1926 mapping in AppStream are LEGO Mindstorms related, because I have, as
1927 part of my involvement in
1928 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
1929 team
</a
> given priority to making sure LEGO users get proposed the
1930 complete set of packages in Debian for that particular hardware. The
1931 team also got a nice Christmas present today. The
1932 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
1933 package
</a
> made it into Debian. With this package in place, it is
1934 now possible to use the LEGO Mindstorms NXT unit with only free
1935 software, as the nxt-firmware package contain the source and firmware
1936 binaries for the NXT brick.
</p
>
1938 <p
>As usual, if you use Bitcoin and want to show your support of my
1939 activities, please send Bitcoin donations to my address
1940 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1945 <title>Isenkram updated with a lot more hardware-package mappings
</title>
1946 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
1947 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
1948 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
1949 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1950 system
</a
> I wrote two years ago to make it easier in Debian to find
1951 and install packages to get your hardware dongles to work, is still
1952 going strong. It is a system to look up the hardware present on or
1953 connected to the current system, and map the hardware to Debian
1954 packages. It can either be done using the tools in isenkram-cli or
1955 using the user space daemon in the isenkram package. The latter will
1956 notify you, when inserting new hardware, about what packages to
1957 install to get the dongle working. It will even provide a button to
1958 click on to ask packagekit to install the packages.
</p
>
1960 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
1962 <p
><pre
>
1979 </pre
></p
>
1981 <p
>It can also list the firware package providing firmware requested
1982 by the load kernel modules, which in my case is an empty list because
1983 I have all the firmware my machine need:
1985 <p
><pre
>
1986 % /usr/sbin/isenkram-autoinstall-firmware -l
1987 info: did not find any firmware files requested by loaded kernel modules. exiting
1989 </pre
></p
>
1991 <p
>The last few days I had a look at several of the around
250
1992 packages in Debian with udev rules. These seem like good candidates
1993 to install when a given hardware dongle is inserted, and I found
1994 several that should be proposed by isenkram. I have not had time to
1995 check all of them, but am happy to report that now there are
97
1996 packages packages mapped to hardware by Isenkram.
11 of these
1997 packages provide hardware mapping using AppStream, while the rest are
1998 listed in the modaliases file provided in isenkram.
</p
>
2000 <p
>These are the packages with hardware mappings at the moment. The
2001 <strong
>marked packages
</strong
> are also announcing their hardware
2002 support using AppStream, for everyone to use:
</p
>
2004 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
2005 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
2006 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
2007 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
2008 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
2009 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
2010 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
2011 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
2012 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
2013 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
2014 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
2015 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
2016 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
2017 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
2018 pcscd, pidgin-blinklight, printer-driver-splix,
2019 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
2020 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
2021 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
2022 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
2023 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
2024 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
2025 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
2026 xserver-xorg-video-vmware, yubikey-personalization and
2027 zd1211-firmware
</p
>
2029 <p
>If you know of other packages, please let me know with a wishlist
2030 bug report against the isenkram-cli package, and ask the package
2032 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
2033 metadata according to the guidelines
</a
> to provide the information
2034 for everyone. In time, I hope to get rid of the isenkram specific
2035 hardware mapping and depend exclusively on AppStream.
</p
>
2037 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
2038 much hardware, and suggest that the package with with any ethernet
2039 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
2040 the details. I hope the maintainer find time to address it soon. In
2041 the mean time I provide an override in isenkram.
</p
>
2046 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
2047 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
2048 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
2049 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
2050 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
2052 <p
>In my early years, I played
2053 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
2054 Elite
</a
> on my PC. I spent many months trading and fighting in
2055 space, and reached the
'elite
' fighting status before I moved on. The
2056 original Elite game was available on Commodore
64 and the IBM PC
2057 edition I played had a
64 KB executable. I am still impressed today
2058 that the authors managed to squeeze both a
3D engine and details about
2059 more than
2000 planet systems across
7 galaxies into a binary so
2062 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
2063 software game Oolite inspired by Elite
</a
> for a while, but did not
2064 really have time to test it properly until a few days ago. It was
2065 great to discover that my old knowledge about trading routes were
2066 still valid. But my fighting and flying abilities were gone, so I had
2067 to retrain to be able to dock on a space station. And I am still not
2068 able to make much resistance when I am attacked by pirates, so I
2069 bougth and mounted the most powerful laser in the rear to be able to
2070 put up at least some resistance while fleeing for my life. :)
</p
>
2072 <p
>When playing Elite in the late eighties, I had to discover
2073 everything on my own, and I had long lists of prices seen on different
2074 planets to be able to decide where to trade what. This time I had the
2076 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
2077 where information about each planet is easily available with common
2078 price ranges and suggested trading routes. This improved my ability
2079 to earn money and I have been able to earn enough to buy a lot of
2080 useful equipent in a few days. I believe I originally played for
2081 months before I could get a docking computer, while now I could get it
2082 after less then a week.
</p
>
2084 <p
>If you like science fiction and dreamed of a life as a vagabond in
2085 space, you should try out Oolite. It is available for Linux, MacOSX
2086 and Windows, and is included in Debian and derivatives since
2011.
</p
>
2088 <p
>As usual, if you use Bitcoin and want to show your support of my
2089 activities, please send Bitcoin donations to my address
2090 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2095 <title>Quicker Debian installations using eatmydata
</title>
2096 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
2097 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
2098 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
2099 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
2100 installation system, observing how using
2101 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
2102 could speed up the installation
</a
> quite a bit. My testing measured
2103 speedup around
20-
40 percent for Debian Edu, where we install around
2104 1000 packages from within the installer. The eatmydata package
2105 provide a way to disable/delay file system flushing. This is a bit
2106 risky in the general case, as files that should be stored on disk will
2107 stay only in memory a bit longer than expected, causing problems if a
2108 machine crashes at an inconvenient time. But for an installation, if
2109 the machine crashes during installation the process is normally
2110 restarted, and avoiding disk operations as much as possible to speed
2111 up the process make perfect sense.
2113 <p
>I added code in the Debian Edu specific installation code to enable
2114 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
2115 but did not have time to push it any further. But a few months ago I
2116 picked it up again and worked with the libeatmydata package maintainer
2117 Mattia Rizzolo to make it easier for everyone to get this installation
2118 speedup in Debian. Thanks to our cooperation There is now an
2119 eatmydata-udeb package in Debian testing and unstable, and simply
2120 enabling/installing it in debian-installer (d-i) is enough to get the
2121 quicker installations. It can be enabled using preseeding. The
2122 following untested kernel argument should do the trick:
</p
>
2124 <blockquote
><pre
>
2125 preseed/early_command=
"anna-install eatmydata-udeb
"
2126 </pre
></blockquote
>
2128 <p
>This should ask d-i to install the package inside the d-i
2129 environment early in the installation sequence. Having it installed
2130 in d-i in turn will make sure the relevant scripts are called just
2131 after debootstrap filled /target/ with the freshly installed Debian
2132 system to configure apt to run dpkg with eatmydata. This is enough to
2133 speed up the installation process. There is a proposal to
2134 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
2135 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
2136 tested its impact.
</p
>
2142 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
2143 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
2144 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
2145 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
2146 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
2147 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
2148 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
2149 elever over det ganske land skal levere inn hvert år. Det mange ikke
2150 vet er at selv om de kommersielle alternativene
2151 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
2152 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
2153 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
2154 utmerket fri programvarealternativ som kan. Oversetterverktøyet
2155 Apertium har støtte for en rekke språkkombinasjoner, og takket være
2156 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
2157 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
2158 nynorsk, og få den automatoversatt til det andre skriftspråket.
2159 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
2160 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
2161 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
2162 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
2163 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
2164 teksten din i webskjemaet der.
2166 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
2167 teknologien kan du enten installere pakken
2168 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
2169 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
2170 api.apertium.org. Se
2171 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
2172 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
2173 denne teksten som ble skrevet på bokmål over maskinoversatt til
2178 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
2179 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
2180 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
2181 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
2182 veit er at sjølv om dei kommersielle alternativa
2183 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
2184 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
2185 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
2186 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
2187 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
2188 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
2189 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
2190 nynorsk, og få den *automatoversatt til det andre skriftspråket.
2191 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
2192 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
2193 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
2194 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
2195 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
2196 teksta di i *webskjemaet der.
2198 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
2199 teknologien kan du anten installera pakken
2200 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
2201 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
2202 *api.*apertium.org. Sjå
2203 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
2204 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
2205 for denne teksta som vart skreva på bokmål over *maskinoversatt til
2211 <title>Coz profiler for multi-threaded software is now in Debian
</title>
2212 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
2213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
2214 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
2215 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
2216 profiler able to run benchmarking experiments on the instrumented
2217 multi-threaded program, finally
2218 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
2219 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
2221 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
2222 blogged about the coz tool
</a
> in August working with upstream to make
2223 it suitable for Debian. There are still issues with clang
2224 compatibility, inline assembly only working x86 and minimized
2225 JavaScript libraries.
</p
>
2227 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
2229 <p
><blockquote
>
2230 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
2231 </blockquote
></p
>
2233 <p
>This will produce a profile.coz file in the current working
2234 directory with the profiling information. This is then given to a
2235 JavaScript application provided in the package and available from
2236 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
2237 To start the local copy, invoke it in a browser like this:
</p
>
2239 <p
><blockquote
>
2240 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
2241 </blockquote
></p
>
2243 <p
>See the project home page and the
2244 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
2245 ;login: article on Coz
</a
> for more information on how it is
2251 <title>My own self balancing Lego Segway
</title>
2252 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
2253 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
2254 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
2255 <description><p
>A while back I received a Gyro sensor for the NXT
2256 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
2257 present. It had been on my wishlist for a while, because I wanted to
2258 build a Segway like balancing lego robot. I had already built
2259 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
2260 robot
</a
> with the kids, using the light/color sensor included in the
2261 NXT kit as the balance sensor, but it was not working very well. It
2262 could balance for a while, but was very sensitive to the light
2263 condition in the room and the reflective properties of the surface and
2264 would fall over after a short while. I wanted something more robust,
2266 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
2267 gyro sensor from HiTechnic
</a
> I believed would solve it on my
2268 wishlist for some years before it suddenly showed up as a gift from my
2269 loved ones. :)
</p
>
2271 <p
>Unfortunately I have not had time to sit down and play with it
2272 since then. But that changed some days ago, when I was searching for
2273 lego segway information and came across a recipe from HiTechnic for
2275 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
2276 HTWay
</a
>, a segway like balancing robot. Build instructions and
2277 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
2278 code
</a
> was included, so it was just a question of putting it all
2279 together. And thanks to the great work of many Debian developers, the
2280 compiler needed to build the source for the NXT is already included in
2281 Debian, so I was read to go in less than an hour. The resulting robot
2282 do not look very impressive in its simplicity:
</p
>
2284 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
2286 <p
>Because I lack the infrared sensor used to control the robot in the
2287 design from HiTechnic, I had to comment out the last task
2288 (taskControl). I simply placed /* and */ around it get the program
2289 working without that sensor present. Now it balances just fine until
2290 the battery status run low:
</p
>
2292 <p align=
"center
"><video width=
"70%
" controls=
"true
">
2293 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
2294 </video
></p
>
2296 <p
>Now we would like to teach it how to follow a line and take remote
2297 control instructions using the included Bluetooth receiver in the NXT.
</p
>
2299 <p
>If you, like me, love LEGO and want to make sure we find the tools
2300 they need to work with LEGO in Debian and all our derivative
2301 distributions like Ubuntu, check out
2302 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
2303 project page
</a
> and join the Debian LEGO team. Personally I own a
2304 RCX and NXT controller (no EV3), and would like to make sure the
2305 Debian tools needed to program the systems I own work as they
2311 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
2312 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
2313 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
2314 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
2315 <description><p
>In July
2316 <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
2317 wrote how to get the Signal Chrome/Chromium app working
</a
> without
2318 the ability to receive SMS messages (aka without a cell phone). It is
2319 time to share some experiences and provide an updated setup.
</p
>
2321 <p
>The Signal app have worked fine for several months now, and I use
2322 it regularly to chat with my loved ones. I had a major snag at the
2323 end of my summer vacation, when the the app completely forgot my
2324 setup, identity and keys. The reason behind this major mess was
2325 running out of disk space. To avoid that ever happening again I have
2326 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
2327 roll back to an earlier version if the files are wiped by mistake. I
2328 had to use it once after introducing the git backup. When rolling
2329 back to an earlier version, one need to use the
'reset session
' option
2330 in Signal to get going, and notify the people you talk with about the
2331 problem. I assume there is some sequence number tracking in the
2332 protocol to detect rollback attacks. The git repository is rather big
2333 (
674 MiB so far), but I have not tried to figure out if some of the
2334 content can be added to a .gitignore file due to lack of spare
2337 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
2338 make it impossible to send messages using Signal. I could still
2339 receive them, but had to patch the code with a new timestamp to send.
2340 I believe the timeout is added by the developers to force people to
2341 upgrade to the latest version of the app, even when there is no
2342 protocol changes, to reduce the version skew among the user base and
2343 thus try to keep the number of support requests down.
</p
>
2345 <p
>Since my original recipe, the Signal source code changed slightly,
2346 making the old patch fail to apply cleanly. Below is an updated
2347 patch, including the shell wrapper I use to start Signal. The
2348 original version required a new user to locate the JavaScript console
2349 and call a function from there. I got help from a friend with more
2350 JavaScript knowledge than me to modify the code to provide a GUI
2351 button instead. This mean that to get started you just need to run
2352 the wrapper and click the
'Register without mobile phone
' to get going
2353 now. I
've also modified the timeout code to always set it to
90 days
2354 in the future, to avoid having to patch the code regularly.
</p
>
2356 <p
>So, the updated recipe for Debian Jessie:
</p
>
2360 <li
>First, install required packages to get the source code and the
2361 browser you need. Signal only work with Chrome/Chromium, as far as I
2362 know, so you need to install it.
2365 apt install git tor chromium
2366 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2367 </pre
></li
>
2369 <li
>Modify the source code using command listed in the the patch
2370 block below.
</li
>
2372 <li
>Start Signal using the run-signal-app wrapper (for example using
2373 <tt
>`pwd`/run-signal-app
</tt
>).
2375 <li
>Click on the
'Register without mobile phone
', will in a phone
2376 number you can receive calls to the next minute, receive the
2377 verification code and enter it into the form field and press
2378 'Register
'. Note, the phone number you use will be user Signal
2379 username, ie the way others can find you on Signal.
</li
>
2381 <li
>You can now use Signal to contact others. Note, new contacts do
2382 not show up in the contact list until you restart Signal, and there is
2383 no way to assign names to Contacts. There is also no way to create or
2384 update chat groups. I suspect this is because the web app do not have
2385 a associated contact database.
</li
>
2389 <p
>I am still a bit uneasy about using Signal, because of the way its
2390 main author moxie0 reject federation and accept dependencies to major
2391 corporations like Google (part of the code is fetched from Google) and
2392 Amazon (the central coordination point is owned by Amazon). See for
2394 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
2395 LibreSignal issue tracker
</a
> for a thread documenting the authors
2396 view on these issues. But the network effect is strong in this case,
2397 and several of the people I want to communicate with already use
2398 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
2399 once it
<a href=
"https://bugs.debian.org/
830265">work on my
2400 laptop
</a
>? It already work on Windows and Android, and is included
2401 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
2402 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
2403 working on Debian Stable.
</p
>
2405 <p
>Anyway, this is the patch I apply to the Signal code to get it
2406 working. It switch to the production servers, disable to timeout,
2407 make registration easier and add the shell wrapper:
</p
>
2410 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
2411 diff --git a/js/background.js b/js/background.js
2412 index
24b4c1d.
.579345f
100644
2413 --- a/js/background.js
2414 +++ b/js/background.js
2419 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
2420 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
2421 var SERVER_PORTS = [
80,
4433,
8443];
2422 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
2423 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
2424 var messageReceiver;
2425 window.getSocketStatus = function() {
2426 if (messageReceiver) {
2427 diff --git a/js/expire.js b/js/expire.js
2428 index
639aeae..beb91c3
100644
2433 'use strict
';
2434 - var BUILD_EXPIRATION =
0;
2435 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
2437 window.extension = window.extension || {};
2439 diff --git a/js/views/install_view.js b/js/views/install_view.js
2440 index
7816f4f.
.1d6233b
100644
2441 --- a/js/views/install_view.js
2442 +++ b/js/views/install_view.js
2445 'click .step1
': this.selectStep.bind(this,
1),
2446 'click .step2
': this.selectStep.bind(this,
2),
2447 -
'click .step3
': this.selectStep.bind(this,
3)
2448 +
'click .step3
': this.selectStep.bind(this,
3),
2449 +
'click .callreg
': function() { extension.install(
'standalone
') },
2452 clearQR: function() {
2453 diff --git a/options.html b/options.html
2454 index dc0f28e.
.8d709f6
100644
2458 &lt;div class=
'nav
'>
2459 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
2460 &lt;p
>{{ installTagline }}
&lt;/p
>
2461 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
2462 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
2463 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
2466 &lt;span class=
'dot step1 selected
'>&lt;/span
>
2467 &lt;span class=
'dot step2
'>&lt;/span
>
2468 &lt;span class=
'dot step3
'>&lt;/span
>
2469 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
2470 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
2476 +userdata=
"`pwd`/userdata
"
2477 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
2478 + (cd $userdata
&& git init)
2480 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
2482 + --proxy-server=
"socks://localhost:
9050" \
2483 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
2485 chmod a+rx run-signal-app
2488 <p
>As usual, if you use Bitcoin and want to show your support of my
2489 activities, please send Bitcoin donations to my address
2490 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2495 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
2496 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
2497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
2498 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
2499 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
2500 system
</a
> provide a practical and easy way to figure out which
2501 packages support the hardware in a given machine. The command line
2502 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
2503 convenient way to list and install packages relevant for the current
2504 hardware during system installation, both user space packages and
2505 firmware packages. The GUI background daemon on the other hand provide
2506 a pop-up proposing to install packages when a new dongle is inserted
2507 while using the computer. For example, if you plug in a smart card
2508 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
2509 that package isn
't already installed, and if you plug in a USB video
2510 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
2511 cheese is currently missing. This already work just fine.
</p
>
2513 <p
>But Isenkram depend on a database mapping from hardware IDs to
2514 package names. When I started no such database existed in Debian, so
2515 I made my own data set and included it with the isenkram package and
2516 made isenkram fetch the latest version of this database from git using
2517 http. This way the isenkram users would get updated package proposals
2518 as soon as I learned more about hardware related packages.
</p
>
2520 <p
>The hardware is identified using modalias strings. The modalias
2521 design is from the Linux kernel where most hardware descriptors are
2522 made available as a strings that can be matched using filename style
2523 globbing. It handle USB, PCI, DMI and a lot of other hardware related
2524 identifiers.
</p
>
2526 <p
>The downside to the Isenkram specific database is that there is no
2527 information about relevant distribution / Debian version, making
2528 isenkram propose obsolete packages too. But along came AppStream, a
2529 cross distribution mechanism to store and collect metadata about
2530 software packages. When I heard about the proposal, I contacted the
2531 people involved and suggested to add a hardware matching rule using
2532 modalias strings in the specification, to be able to use AppStream for
2533 mapping hardware to packages. This idea was accepted and AppStream is
2534 now a great way for a package to announce the hardware it support in a
2535 distribution neutral way. I wrote
2536 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
2537 recipe on how to add such meta-information
</a
> in a blog post last
2538 December. If you have a hardware related package in Debian, please
2539 announce the relevant hardware IDs using AppStream.
</p
>
2541 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
2542 RCX or NXT unit, announce this support using AppStream. The effect is
2543 that when you insert such LEGO robot controller into your Debian
2544 machine, Isenkram will propose to install the packages needed to get
2545 it working. The intention is that this should allow the local user to
2546 start programming his robot controller right away without having to
2547 guess what packages to use or which permissions to fix.
</p
>
2549 <p
>But when I sat down with my son the other day to program our NXT
2550 unit using his Debian Stretch computer, I discovered something
2551 annoying. The local console user (ie my son) did not get access to
2552 the USB device for programming the unit. This used to work, but no
2553 longer in Jessie and Stretch. After some investigation and asking
2554 around on #debian-devel, I discovered that this was because udev had
2555 changed the mechanism used to grant access to local devices. The
2556 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
2557 no longer applied, because LDAP users no longer was added to the
2558 plugdev group during login. Michael Biebl told me that this method
2559 was obsolete and the new method used ACLs instead. This was good
2560 news, as the plugdev mechanism is a mess when using a remote user
2561 directory like LDAP. Using ACLs would make sure a user lost device
2562 access when she logged out, even if the user left behind a background
2563 process which would retain the plugdev membership with the ConsoleKit
2564 setup. Armed with this knowledge I moved on to fix the access problem
2565 for the LEGO Mindstorms related packages.
</p
>
2567 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
2568 applied directly for a device, or is applied in
2569 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
2570 LEGO Mindstorms udev rules did not have a class, I decided to add the
2571 tag directly in the udev rules files included in the packages. Here
2572 is one example. For the nqc C compiler for the RCX, the
2573 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
2575 <p
><pre
>
2576 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
2577 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
2578 </pre
></p
>
2580 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
2581 packages using plugdev in their /lib/udev/rules.d/ files should be
2582 changed to use this tag (either directly or indirectly via
2583 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
2584 to detect this?
</p
>
2586 <p
>I
've been unable to find good documentation on the uaccess feature.
2587 It is unclear to me if the uaccess tag is an internal implementation
2588 detail like the udev-acl tag used by
2589 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
2590 indirect method is the preferred way. Michael
2591 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
2592 documentation from the systemd project
</a
> and I hope it will make
2593 this clearer. For now I use the generic classes when they exist and
2594 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
2595 directly if no such class exist.
</p
>
2597 <p
>To learn more about the isenkram system, please check out
2598 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2599 blog posts tagged isenkram
</a
>.
</p
>
2601 <p
>To help out making life for LEGO constructors in Debian easier,
2602 please join us on our IRC channel
2603 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
2604 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
2605 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
2606 list is not yet created, but we are working on it. :)
</p
>
2608 <p
>As usual, if you use Bitcoin and want to show your support of my
2609 activities, please send Bitcoin donations to my address
2610 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2615 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
2616 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
2617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</guid>
2618 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
2619 <description><p
>In April we
2620 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
2621 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
2622 how to set up and administrate a Debian system. Today I am happy to
2623 report that the first draft is now publicly available. You can find
2624 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
2625 Administrator
's Handbook page
</a
> (under Other languages). The first
2626 eight chapters have a first draft translation, and we are working on
2627 proofreading the content. If you want to help out, please start
2629 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2630 hosted weblate project page
</a
>, and get in touch using
2631 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2632 translators mailing list
</a
>. Please also check out
2633 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2634 contributors
</a
>. A good way to contribute is to proofread the text
2635 and update weblate if you find errors.
</p
>
2637 <p
>Our goal is still to make the Norwegian book available on paper as well as
2638 electronic form.
</p
>
2643 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
2644 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
2645 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
2646 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
2647 <description><p
>This summer, I read a great article
2648 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
2649 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
2650 how to profile multi-threaded programs. It presented a system for
2651 profiling software by running experiences in the running program,
2652 testing how run time performance is affected by
"speeding up
" parts of
2653 the code to various degrees compared to a normal run. It does this by
2654 slowing down parallel threads while the
"faster up
" code is running
2655 and measure how this affect processing time. The processing time is
2656 measured using probes inserted into the code, either using progress
2657 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2658 can also measure unmodified code by measuring complete the program
2659 runtime and running the program several times instead.
</p
>
2661 <p
>The project and presentation was so inspiring that I would like to
2662 get the system into Debian. I
2663 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
2664 a WNPP request for it
</a
> and contacted upstream to try to make the
2665 system ready for Debian by sending patches. The build process need to
2666 be changed a bit to avoid running
'git clone
' to get dependencies, and
2667 to include the JavaScript web page used to visualize the collected
2668 profiling information included in the source package.
2669 But I expect that should work out fairly soon.
</p
>
2671 <p
>The way the system work is fairly simple. To run an coz experiment
2672 on a binary with debug symbols available, start the program like this:
2674 <p
><blockquote
><pre
>
2675 coz run --- program-to-run
2676 </pre
></blockquote
></p
>
2678 <p
>This will create a text file profile.coz with the instrumentation
2679 information. To show what part of the code affect the performance
2680 most, use a web browser and either point it to
2681 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
2682 or use the copy from git (in the gh-pages branch). Check out this web
2683 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
2684 profiling more useful you include
&lt;coz.h
&gt; and insert the
2685 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2686 code, rebuild and run the profiler. This allow coz to do more
2687 targeted experiments.
</p
>
2689 <p
>A video published by ACM
2690 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
2691 Coz profiler
</a
> is available from Youtube. There is also a paper
2692 from the
25th Symposium on Operating Systems Principles available
2694 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
2695 finding code that counts with causal profiling
</a
>.
</p
>
2697 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
2698 for Coz is available from github. It will only build with clang
2700 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
2701 feature missing in GCC
</a
>, but I
've submitted
2702 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
2703 it
</a
> and hope it will be included in the upstream source soon.
</p
>
2705 <p
>Please get in touch if you, like me, would like to see this piece
2706 of software in Debian. I would very much like some help with the
2707 packaging effort, as I lack the in depth knowledge on how to package
2708 C++ libraries.
</p
>
2713 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
2714 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
2715 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
2716 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
2717 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2718 to be a slight challenge. Here is the recipe if I ever need to do it
2719 again. It all started by me wanting to try the recipe to set up
2720 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
2721 hardened Android installation
</a
> from the Tor project blog on a
2722 device I had access to. It is a old mobile phone with a broken
2723 microphone The initial idea had been to just
2724 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
2725 CyanogenMod on it
</a
>, but did not quite find time to start on it
2726 until a few days ago.
</p
>
2728 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
2729 loader (press volume down and power at the same time), (
2) select
2730 'fastboot
' before (
3) connecting the device via USB to a Linux
2731 machine, (
4) request the device identifier token by running
'fastboot
2732 oem get_identifier_token
', (
5) request the device unlocking key using
2733 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
2734 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
2736 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
2737 or newer, and the device I was working on had
2.00.0027. This
2738 apparently can be easily fixed by downloading a Windows program and
2739 running it on your Windows machine, if you accept the terms Microsoft
2740 require you to accept to use Windows - which I do not. So I had to
2741 come up with a different approach. I got a lot of help from AndyCap
2742 on #nuug, and would not have been able to get this working without
2745 <p
>First I needed to extract the hboot firmware from
2746 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
2747 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
2748 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
2749 project named unruu
</a
> using libunshield. The unshield tool did not
2750 recognise the file format, but unruu worked and extracted rom.zip,
2751 containing the new hboot firmware and a text file describing which
2752 devices it would work for.
</p
>
2754 <p
>Next, I needed to get the new firmware into the device. For this I
2755 followed some instructions
2756 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
2757 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
2758 machine with Debian testing:
</p
>
2760 <p
><pre
>
2761 adb reboot-bootloader
2762 fastboot oem rebootRUU
2763 fastboot flash zip rom.zip
2764 fastboot flash zip rom.zip
2766 </pre
></p
>
2768 <p
>The flash command apparently need to be done twice to take effect,
2769 as the first is just preparations and the second one do the flashing.
2770 The adb command is just to get to the boot loader menu, so turning the
2771 device on while holding volume down and the power button should work
2774 <p
>With the new hboot version in place I could start following the
2775 instructions on the HTC developer web site. I got the device token
2776 like this:
</p
>
2778 <p
><pre
>
2779 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
2782 <p
>And once I got the unlock code via email, I could use it like
2785 <p
><pre
>
2786 fastboot flash unlocktoken Unlock_code.bin
2787 </pre
></p
>
2789 <p
>And with that final step in place, the phone was unlocked and I
2790 could start stuffing the software of my own choosing into the device.
2791 So far I only inserted a replacement recovery image to wipe the phone
2792 before I start. We will see what happen next. Perhaps I should
2793 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
2798 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
2799 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</link>
2800 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
</guid>
2801 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
2802 <description><p
>For a while now, I have wanted to test
2803 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
2804 said to provide end to end encrypted communication and several of my
2805 friends and family are already using it. As I by choice do not own a
2806 mobile phone, this proved to be harder than expected. And I wanted to
2807 have the source of the client and know that it was the code used on my
2808 machine. But yesterday I managed to get it working. I used the
2809 Github source, compared it to the source in
2810 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
2811 Signal Chrome app
</a
> available from the Chrome web store, applied
2812 patches to use the production Signal servers, started the app and
2813 asked for the hidden
"register without a smart phone
" form. Here is
2814 the recipe how I did it.
</p
>
2816 <p
>First, I fetched the Signal desktop source from Github, using
2819 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2822 <p
>Next, I patched the source to use the production servers, to be
2823 able to talk to other Signal users:
</p
>
2826 cat
&lt;
&lt;EOF | patch -p0
2827 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2828 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2829 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
2834 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
2835 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
2836 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
2837 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
2838 var messageReceiver;
2839 window.getSocketStatus = function() {
2840 if (messageReceiver) {
2841 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
2842 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2843 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
2846 'use strict
';
2847 - var BUILD_EXPIRATION =
0;
2848 + var BUILD_EXPIRATION =
1474492690000;
2850 window.extension = window.extension || {};
2855 <p
>The first part is changing the servers, and the second is updating
2856 an expiration timestamp. This timestamp need to be updated regularly.
2857 It is set
90 days in the future by the build process (Gruntfile.js).
2858 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
2860 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
2861 script to launch Signal in Chromium.
</p
>
2868 --proxy-server=
"socks://localhost:
9050" \
2869 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2872 <p
> The script start the app and configure Chromium to use the Tor
2873 SOCKS5 proxy to make sure those controlling the Signal servers (today
2874 Amazon and Whisper Systems) as well as those listening on the lines
2875 will have a harder time location my laptop based on the Signal
2876 connections if they use source IP address.
</p
>
2878 <p
>When the script starts, one need to follow the instructions under
2879 "Standalone Registration
" in the CONTRIBUTING.md file in the git
2880 repository. I right clicked on the Signal window to get up the
2881 Chromium debugging tool, visited the
'Console
' tab and wrote
2882 'extension.install(
"standalone
")
' on the console prompt to get the
2883 registration form. Then I entered by land line phone number and
2884 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
2885 repeated the verification code three times. After entering the number
2886 into the verification code field in the form, I could start using
2887 Signal from my laptop.
2889 <p
>As far as I can tell, The Signal app will leak who is talking to
2890 whom and thus who know who to those controlling the central server,
2891 but such leakage is hard to avoid with a centrally controlled server
2892 setup. It is something to keep in mind when using Signal - the
2893 content of your chats are harder to intercept, but the meta data
2894 exposing your contact network is available to people you do not know.
2895 So better than many options, but not great. And sadly the usage is
2896 connected to my land line, thus allowing those controlling the server
2897 to associate it to my home and person. I would prefer it if only
2898 those I knew could tell who I was on Signal. There are options
2899 avoiding such information leakage, but most of my friends are not
2900 using them, so I am stuck with Signal for now.
</p
>
2902 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
2904 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
2905 and updated recipe for using the Signal app without a mobile
2906 phone
</a
>.
</p
>
2911 <title>The new
"best
" multimedia player in Debian?
</title>
2912 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
2913 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
2914 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
2915 <description><p
>When I set out a few weeks ago to figure out
2916 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
2917 multimedia player in Debian claimed to support most file formats /
2918 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
2919 the various players claimed support for. The range was from
55 to
130
2920 MIME types. I suspect most media formats are supported by all
2921 players, but this is not really reflected in the MimeTypes values in
2922 their desktop files. There are probably also some bogus MIME types
2923 listed, but it is hard to identify which one this is.
</p
>
2925 <p
>Anyway, in the mean time I got in touch with upstream for some of
2926 the players suggesting to add more MIME types to their desktop files,
2927 and decided to spend some time myself improving the situation for my
2928 favorite media player VLC. The fixes for VLC entered Debian unstable
2929 yesterday. The complete list of MIME types can be seen on the
2930 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
2931 player MIME type support status
</a
> Debian wiki page.
</p
>
2933 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
2934 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2935 kmplayer. I am sure some of the other players desktop files support
2936 several of the formats currently listed as working only with vlc,
2937 toten and parole.
</p
>
2939 <p
>A sad observation is that only
14 MIME types are listed as
2940 supported by all the tested multimedia players in Debian in their
2941 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2942 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2943 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2944 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2945 it sad that video/ogg and video/webm is not supported by all the media
2946 players in Debian. As far as I can tell, all of them can handle both
2952 <title>A program should be able to open its own files on Linux
</title>
2953 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
2954 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
2955 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
2956 <description><p
>Many years ago, when koffice was fresh and with few users, I
2957 decided to test its presentation tool when making the slides for a
2958 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2959 wrote the first draft of the slides, saved the result and went to bed
2960 the day before I would give the talk. The next day I took a plane to
2961 the location where the meeting should take place, and on the plane I
2962 started up koffice again to polish the talk a bit, only to discover
2963 that kpresenter refused to load its own data file. I cursed a bit and
2964 started making the slides again from memory, to have something to
2965 present when I arrived. I tested that the saved files could be
2966 loaded, and the day seemed to be rescued. I continued to polish the
2967 slides until I suddenly discovered that the saved file could no longer
2968 be loaded into kpresenter. In the end I had to rewrite the slides
2969 three times, condensing the content until the talk became shorter and
2970 shorter. After the talk I was able to pinpoint the problem
&ndash;
2971 kpresenter wrote inline images in a way itself could not understand.
2972 Eventually that bug was fixed and kpresenter ended up being a great
2973 program to make slides. The point I
'm trying to make is that we
2974 expect a program to be able to load its own data files, and it is
2975 embarrassing to its developers if it can
't.
</p
>
2977 <p
>Did you ever experience a program failing to load its own data
2978 files from the desktop file browser? It is not a uncommon problem. A
2979 while back I discovered that the screencast recorder
2980 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2981 browser would refuse to open. No video player claimed to understand
2982 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
2983 returning the application/ogg MIME type, which no video player I had
2984 installed listed as a MIME type they would understand. I asked for
2985 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
2986 behavour
</a
> and use the MIME type video/ogg instead. I also asked
2987 several video players to add video/ogg to their desktop files, to give
2988 the file browser an idea what to do about Ogg Theora files. After a
2989 while, the desktop file browsers in Debian started to handle the
2990 output from gtk-recordmydesktop properly.
</p
>
2992 <p
>But history repeats itself. A few days ago I tested the music
2993 system Rosegarden again, and I discovered that the KDE and xfce file
2994 browsers did not know what to do with the Rosegarden project files
2995 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
2996 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
2997 included in the next upload. To increase the chance of me remembering
2998 how to fix the problem next time some program fail to load its files
2999 from the file browser, here are some notes on how to fix it.
</p
>
3001 <p
>The file browsers in Debian in general operates on MIME types.
3002 There are two sources for the MIME type of a given file. The output from
3003 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
3004 shared MIME type registry (under /usr/share/mime/). The file MIME
3005 type is mapped to programs supporting the MIME type, and this
3006 information is collected from
3007 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
3008 desktop files
</a
> available in /usr/share/applications/. If there is
3009 one desktop file claiming support for the MIME type of the file, it is
3010 activated when asking to open a given file. If there are more, one
3011 can normally select which one to use by right-clicking on the file and
3012 selecting the wanted one using
'Open with
' or similar. In general
3013 this work well. But it depend on each program picking a good MIME
3015 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
3016 MIME type registered with IANA
</a
>), file and/or the shared MIME
3017 registry recognizing the file and the desktop file to list the MIME
3018 type in its list of supported MIME types.
</p
>
3020 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
3021 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
3022 Shared MIME database
</a
> look like this:
</p
>
3024 <p
><blockquote
><pre
>
3025 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3026 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
3027 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
3028 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
3029 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
3030 &lt;glob pattern=
"*.rg
"/
&gt;
3031 &lt;/mime-type
&gt;
3032 &lt;/mime-info
&gt;
3033 </pre
></blockquote
></p
>
3035 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
3036 (it is a gzipped XML file). Note, it is much better to use an
3037 official MIME type registered with IANA than it is to make up ones own
3038 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
3040 <p
>The desktop file of the rosegarden program failed to list
3041 audio/x-rosegarden in its list of supported MIME types, causing the
3042 file browsers to have no idea what to do with *.rg files:
</p
>
3044 <p
><blockquote
><pre
>
3045 % grep Mime /usr/share/applications/rosegarden.desktop
3046 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
3047 X-KDE-NativeMimeType=audio/x-rosegarden-composition
3049 </pre
></blockquote
></p
>
3051 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
3052 MimeType= line.
</p
>
3054 <p
>If you run into a file which fail to open the correct program when
3055 selected from the file browser, please check out the output from
3056 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
3057 MIME type is registered somewhere under /usr/share/mime/ and check
3058 that some desktop file under /usr/share/applications/ is claiming
3059 support for this MIME type. If not, please report a bug to have it
3065 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
3066 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
3067 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
3068 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
3069 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
3070 system
</a
> is a user-focused solution in Debian for handling hardware
3071 related packages. The idea is to have a database of mappings between
3072 hardware and packages, and pop up a dialog suggesting for the user to
3073 install the packages to use a given hardware dongle. Some use cases
3074 are when you insert a Yubikey, it proposes to install the software
3075 needed to control it; when you insert a braille reader list it
3076 proposes to install the packages needed to send text to the reader;
3077 and when you insert a ColorHug screen calibrator it suggests to
3078 install the driver for it. The system work well, and even have a few
3079 command line tools to install firmware packages and packages for the
3080 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
3082 <p
>The system was initially written using aptdaemon, because I found
3083 good documentation and example code on how to use it. But aptdaemon
3084 is going away and is generally being replaced by
3085 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
3086 so Isenkram needed a rewrite. And today, thanks to the great patch
3087 from my college Sunil Mohan Adapa in the FreedomBox project, the
3088 rewrite finally took place. I
've just uploaded a new version of
3089 Isenkram into Debian Unstable with the patch included, and the default
3090 for the background daemon is now to use PackageKit. To check it out,
3091 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
3092 and see if it is recognised.
</p
>
3094 <p
>If you want to know what kind of packages isenkram would propose for
3095 the machine it is running on, you can check out the isenkram-lookup
3096 program. This is what it look like on a Thinkpad X230:
</p
>
3098 <p
><blockquote
><pre
>
3114 </pre
></blockquote
></p
>
3116 <p
>The hardware mappings come from several places. The preferred way
3117 is for packages to announce their hardware support using
3118 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
3119 cross distribution appstream system
</a
>.
3121 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
3122 blog posts about isenkram
</a
> to learn how to do that.
</p
>
3127 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
3128 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
3129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
3130 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
3131 <description><p
>Yesterday I updated the
3132 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
3133 package in Debian
</a
> with a few patches sent to me by skilled and
3134 enterprising users. There were some nice user and visible changes.
3135 First of all, both desktop menu entries now work. A design flaw in
3136 one of the script made the history graph fail to show up (its PNG was
3137 dumped in ~/.xsession-errors) if no controlling TTY was available.
3138 The script worked when called from the command line, but not when
3139 called from the desktop menu. I changed this to look for a DISPLAY
3140 variable or a TTY before deciding where to draw the graph, and now the
3141 graph window pop up as expected.
</p
>
3143 <p
>The next new feature is a discharge rate estimator in one of the
3144 graphs (the one showing the last few hours). New is also the user of
3145 colours showing charging in blue and discharge in red. The percentages
3146 of this graph is relative to last full charge, not battery design
3149 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
3151 <p
>The other graph show the entire history of the collected battery
3152 statistics, comparing it to the design capacity of the battery to
3153 visualise how the battery life time get shorter over time. The red
3154 line in this graph is what the previous graph considers
100 percent:
3156 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
3158 <p
>In this graph you can see that I only charge the battery to
80
3159 percent of last full capacity, and how the capacity of the battery is
3160 shrinking. :(
</p
>
3162 <p
>The last new feature is in the collector, which now will handle
3163 more hardware models. On some hardware, Linux power supply
3164 information is stored in /sys/class/power_supply/ACAD/, while the
3165 collector previously only looked in /sys/class/power_supply/AC/. Now
3166 both are checked to figure if there is power connected to the
3169 <p
>If you are interested in how your laptop battery is doing, please
3171 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
3172 in Debian unstable, or rebuild it on Jessie to get it working on
3173 Debian stable. :) The upstream source is available from
<a
3174 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
3175 Patches are very welcome.
</p
>
3177 <p
>As usual, if you use Bitcoin and want to show your support of my
3178 activities, please send Bitcoin donations to my address
3179 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3184 <title>Debian now with ZFS on Linux included
</title>
3185 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
3186 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
3187 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
3188 <description><p
>Today, after many years of hard work from many people,
3189 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
3190 Debian. The package status can be seen on
3191 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
3192 for zfs-linux
</a
>. and
3193 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
3194 team status page
</a
>. If you want to help out, please join us.
3195 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
3196 source code
</a
> is available via git on Alioth. It would also be
3197 great if you could help out with
3198 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
3199 it is an important piece of the puzzle to get ZFS working.
</p
>
3204 <title>What is the best multimedia player in Debian?
</title>
3205 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
3206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
3207 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
3208 <description><p
><strong
>Where I set out to figure out which multimedia player in
3209 Debian claim support for most file formats.
</strong
></p
>
3211 <p
>A few years ago, I had a look at the media support for Browser
3212 plugins in Debian, to get an idea which plugins to include in Debian
3213 Edu. I created a script to extract the set of supported MIME types
3214 for each plugin, and used this to find out which multimedia browser
3215 plugin supported most file formats / media types.
3216 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
3217 result
</a
> can still be seen on the Debian wiki, even though it have
3218 not been updated for a while. But browser plugins are less relevant
3219 these days, so I thought it was time to look at standalone
3222 <p
>A few days ago I was tired of VLC not being listed as a viable
3223 player when I wanted to play videos from the Norwegian National
3224 Broadcasting Company, and decided to investigate why. The cause is a
3225 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
3226 desktop file
</a
>. In the process I wrote a script to compare the set
3227 of MIME types announced in the desktop file and the browser plugin,
3228 only to discover that there is quite a large difference between the
3229 two for VLC. This discovery made me dig up the script I used to
3230 compare browser plugins, and adjust it to compare desktop files
3231 instead, to try to figure out which multimedia player in Debian
3232 support most file formats.
</p
>
3234 <p
>The result can be seen on the Debian Wiki, as
3235 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
3236 table listing all MIME types supported by one of the packages included
3237 in the table
</a
>, with the package supporting most MIME types being
3238 listed first in the table.
</p
>
3240 </p
>The best multimedia player in Debian? It is totem, followed by
3241 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
3242 kmplayer. Time for the other players to update their announced MIME
3248 <title>The Pyra - handheld computer with Debian preinstalled
</title>
3249 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
3250 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
3251 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
3252 <description>A friend of mine made me aware of
3253 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
3254 handheld computer which will be delivered with Debian preinstalled. I
3255 would love to get one of those for my birthday. :)
</p
>
3257 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
3258 plugs and many others connectors, and include a full keyboard and a
5"
3259 LCD touch screen. The
6000mAh battery is claimed to provide a whole
3260 day of battery life time, but I have not seen any independent tests
3261 confirming this. The vendor is still collecting preorders, and the
3262 last I heard last night was that
22 more orders were needed before
3263 production started.
</p
>
3265 <p
>As far as I know, this is the first handheld preinstalled with
3266 Debian. Please let me know if you know of any others. Is it the
3267 first computer being sold with Debian preinstalled?
</p
>
3272 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
3273 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
3274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
3275 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
3276 <description><p
>During this weekends
3277 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
3278 squashing party and developer gathering
</a
>, we decided to do our part
3279 to make sure there are good books about Debian available in Norwegian
3280 Bokmål, and got in touch with the people behind the
3281 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
3282 project
</a
> to get started. If you want to help out, please start
3284 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
3285 hosted weblate project page
</a
>, and get in touch using
3286 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
3287 translators mailing list
</a
>. Please also check out
3288 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
3289 contributors
</a
>.
</p
>
3291 <p
>The book is already available on paper in English, French and
3292 Japanese, and our goal is to get it available on paper in Norwegian
3293 Bokmål too. In addition to the paper edition, there are also EPUB and
3294 Mobi versions available. And there are incomplete translations
3295 available for many more languages.
</p
>
3300 <title>One in two hundred Debian users using ZFS on Linux?
</title>
3301 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
3302 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
3303 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
3304 <description><p
>Just for fun I had a look at the popcon number of ZFS related
3305 packages in Debian, and was quite surprised with what I found. I use
3306 ZFS myself at home, but did not really expect many others to do so.
3307 But I might be wrong.
</p
>
3309 <p
>According to
3310 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
3311 results for spl-linux
</a
>, there are
1019 Debian installations, or
3312 0.53% of the population, with the package installed. As far as I know
3313 the only use of the spl-linux package is as a support library for ZFS
3314 on Linux, so I use it here as proxy for measuring the number of ZFS
3315 installation on Linux in Debian. In the kFreeBSD variant of Debian
3316 the ZFS feature is already available, and there
3317 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
3318 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
3319 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
3321 <p
>But even though the Debian project leader Lucas Nussbaum
3322 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
3323 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
3324 cleared, the package is still not in Debian. The package is again in
3325 the NEW queue. Several uploads have been rejected so far because the
3326 debian/copyright file was incomplete or wrong, but there is no reason
3327 to give up. The current status can be seen on
3328 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
3329 team status page
</a
>, and
3330 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
3331 source code
</a
> is available on Alioth.
</p
>
3333 <p
>As I want ZFS to be included in next version of Debian to make sure
3334 my home server can function in the future using only official Debian
3335 packages, and the current blocker is to get the debian/copyright file
3336 accepted by the FTP masters in Debian, I decided a while back to try
3337 to help out the team. This was the background for my blog post about
3338 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
3339 updating and checking debian/copyright semi-automatically
</a
>, and I
3340 used the techniques I explored there to try to find any errors in the
3341 copyright file. It is not very easy to check every one of the around
3342 2000 files in the source package, but I hope we this time got it
3343 right. If you want to help out, check out the git source and try to
3344 find missing entries in the debian/copyright file.
</p
>
3349 <title>Full battery stats collector is now available in Debian
</title>
3350 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
3351 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
3352 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
3353 <description><p
>Since this morning, the battery-stats package in Debian include an
3354 extended collector that will collect the complete battery history for
3355 later processing and graphing. The original collector store the
3356 battery level as percentage of last full level, while the new
3357 collector also record battery vendor, model, serial number, design
3358 full level, last full level and current battery level. This make it
3359 possible to predict the lifetime of the battery as well as visualise
3360 the energy flow when the battery is charging or discharging.
</p
>
3362 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
3363 in the version
0.5.1 package in unstable. Get the new battery level graph
3364 and lifetime prediction by running:
3366 <p
><pre
>
3367 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
3368 </pre
></p
>
3370 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
3372 <p
>The flow in/out of the battery can be seen by running (no menu
3373 entry yet):
</p
>
3375 <p
><pre
>
3376 /usr/share/battery-stats/battery-stats-graph-flow
3377 </pre
></p
>
3379 <p
>I
'm not quite happy with the way the data is visualised, at least
3380 when there are few data points. The graphs look a bit better with a
3381 few years of data.
</p
>
3383 <p
>A while back one important feature I use in the battery stats
3384 collector broke in Debian. The scripts in
3385 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
3386 suspect it happened when Jessie started using systemd, but I do not
3387 know. The issue is reported as
3388 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
3389 pm-utils. I managed to work around it by adding an udev rule to call
3390 the collector script every time the power connector is connected and
3391 disconnected. With this fix in place it was finally time to make a
3392 new release of the package, and get it into Debian.
</p
>
3394 <p
>If you are interested in how your laptop battery is doing, please
3396 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
3397 in Debian unstable, or rebuild it on Jessie to get it working on
3398 Debian stable. :) The upstream source is available from
3399 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
3400 As always, patches are very welcome.
</p
>
3405 <title>Making battery measurements a little easier in Debian
</title>
3406 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
3407 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
3408 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
3409 <description><p
>Back in September, I blogged about
3410 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
3411 system I wrote to collect statistics about my laptop battery
</a
>, and
3412 how it showed the decay and death of this battery (now replaced). I
3413 created a simple deb package to handle the collection and graphing,
3414 but did not want to upload it to Debian as there were already
3415 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
3416 package in Debian
</a
> that should do the same thing, and I did not see
3417 a point of uploading a competing package when battery-stats could be
3418 fixed instead. I reported a few bugs about its non-function, and
3419 hoped someone would step in and fix it. But no-one did.
</p
>
3421 <p
>I got tired of waiting a few days ago, and took matters in my own
3422 hands. The end result is that I am now the new upstream developer of
3423 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
3424 battery-stats in Debian, and the package in Debian unstable is finally
3425 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
3426 information provided by the Linux kernel. If you install the
3427 battery-stats package from unstable now, you will be able to get a
3428 graph of the current battery fill level, to get some idea about the
3429 status of the battery. The source package build and work just fine in
3430 Debian testing and stable (and probably oldstable too, but I have not
3431 tested). The default graph you get for that system look like this:
</p
>
3433 <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
>
3435 <p
>My plans for the future is to merge my old scripts into the
3436 battery-stats package, as my old scripts collected a lot more details
3437 about the battery. The scripts are merged into the upstream
3438 battery-stats git repository already, but I am not convinced they work
3439 yet, as I changed a lot of paths along the way. Will have to test a
3440 bit more before I make a new release.
</p
>
3442 <p
>I will also consider changing the file format slightly, as I
3443 suspect the way I combine several values into one field might make it
3444 impossible to know the type of the value when using it for processing
3445 and graphing.
</p
>
3447 <p
>If you would like I would like to keep an close eye on your laptop
3448 battery, check out the battery-stats package in
3449 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
3451 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
3452 I would love some help to improve the system further.
</p
>
3457 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
3458 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
3459 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
3460 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
3461 <description><p
>Making packages for Debian requires quite a lot of attention to
3462 details. And one of the details is the content of the
3463 debian/copyright file, which should list all relevant licenses used by
3464 the code in the package in question, preferably in
3465 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
3466 readable DEP5 format
</a
>.
</p
>
3468 <p
>For large packages with lots of contributors it is hard to write
3469 and update this file manually, and if you get some detail wrong, the
3470 package is normally rejected by the ftpmasters. So getting it right
3471 the first time around get the package into Debian faster, and save
3472 both you and the ftpmasters some work.. Today, while trying to figure
3473 out what was wrong with
3474 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
3475 zfsonlinux copyright file
</a
>, I decided to spend some time on
3476 figuring out the options for doing this job automatically, or at least
3477 semi-automatically.
</p
>
3479 <p
>Lucikly, there are at least two tools available for generating the
3480 file based on the code in the source package,
3481 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
3482 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
3483 not sure which one of them came first, but both seem to be able to
3484 create a sensible draft file. As far as I can tell, none of them can
3485 be trusted to get the result just right, so the content need to be
3486 polished a bit before the file is OK to upload. I found the debmake
3488 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
3489 blog posts from
2014</a
>.
3491 <p
>To generate using debmake, use the -cc option:
3493 <p
><pre
>
3494 debmake -cc
> debian/copyright
3495 </pre
></p
>
3497 <p
>Note there are some problems with python and non-ASCII names, so
3498 this might not be the best option.
</p
>
3500 <p
>The cme option is based on a config parsing library, and I found
3502 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
3503 blog post from
2015</a
>. To generate using cme, use the
'update
3504 dpkg-copyright
' option:
3506 <p
><pre
>
3507 cme update dpkg-copyright
3508 </pre
></p
>
3510 <p
>This will create or update debian/copyright. The cme tool seem to
3511 handle UTF-
8 names better than debmake.
</p
>
3513 <p
>When the copyright file is created, I would also like some help to
3514 check if the file is correct. For this I found two good options,
3515 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
3516 to focus on license types and file matching, and is able to detect
3517 ineffective blocks in the copyright file. The latter reports missing
3518 copyright holders and years, but was confused by inconsistent license
3519 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
3520 fix all issues reported by them before uploading. But I do not know
3521 if the tools and the ftpmasters agree on what is important to fix in a
3522 copyright file, so the package might still be rejected.
</p
>
3524 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
3525 will read through the source and try to find all copyright statements.
3526 It is not comparing the result to the content of debian/copyright, but
3527 can be useful when verifying the content of the copyright file.
</p
>
3529 <p
>Are you aware of better tools in Debian to create and update
3530 debian/copyright file. Please let me know, or blog about it on
3531 planet.debian.org.
</p
>
3533 <p
>As usual, if you use Bitcoin and want to show your support of my
3534 activities, please send Bitcoin donations to my address
3535 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3537 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
3538 on how to use licensecheck and cdbs to create a draft copyright file
3540 <p
><pre
>
3541 licensecheck --copyright -r `find * -type f` | \
3542 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
3543 </pre
></p
>
3545 <p
>He mentioned that he normally check the generated file into the
3546 version control system to make it easier to discover license and
3547 copyright changes in the upstream source. I will try to do the same
3548 with my packages in the future.
</p
>
3550 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
3551 against using -quiet for new users, so I removed it from the proposed
3552 command line.
</p
>
3557 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
3558 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
3559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
3560 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
3561 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
3562 is taking shape in Debian, and one provided feature is a very
3563 convenient way to tell you which package to install to make a given
3564 firmware file available when the kernel is looking for it. This can
3565 be done using apt-file too, but that is for someone else to blog
3568 <p
>Here is a small recipe to find the package with a given firmware
3569 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
3570 picked from the set of firmware announced using appstream in Debian
3571 unstable. In general you would be looking for the firmware requested
3572 by the kernel during kernel module loading. To find the package
3573 providing the example file, do like this:
</p
>
3575 <blockquote
><pre
>
3576 % apt install appstream
3580 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
3581 awk
'/Package:/ {print $
2}
'
3584 </pre
></blockquote
>
3586 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
3587 appstream wiki
</a
> page to learn how to embed the package metadata in
3588 a way appstream can use.
</p
>
3590 <p
>This same approach can be used to find any package supporting a
3591 given MIME type. This is very useful when you get a file you do not
3592 know how to handle. First find the mime type using
<tt
>file
3593 --mime-type
</tt
>, and next look up the package providing support for
3594 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3595 and you can find all packages handling this type like this:
</p
>
3597 <blockquote
><pre
>
3598 % apt install appstream
3602 % appstreamcli what-provides mimetype image/svg+xml | \
3603 awk
'/Package:/ {print $
2}
'
3625 </pre
></blockquote
>
3627 <p
>I believe the MIME types are fetched from the desktop file for
3628 packages providing appstream metadata.
</p
>
3633 <title>Creepy, visualise geotagged social media information - nice free software
</title>
3634 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
3635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
3636 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
3637 <description><p
>Most people seem not to realise that every time they walk around
3638 with the computerised radio beacon known as a mobile phone their
3639 position is tracked by the phone company and often stored for a long
3640 time (like every time a SMS is received or sent). And if their
3641 computerised radio beacon is capable of running programs (often called
3642 mobile apps) downloaded from the Internet, these programs are often
3643 also capable of tracking their location (if the app requested access
3644 during installation). And when these programs send out information to
3645 central collection points, the location is often included, unless
3646 extra care is taken to not send the location. The provided
3647 information is used by several entities, for good and bad (what is
3648 good and bad, depend on your point of view). What is certain, is that
3649 the private sphere and the right to free movement is challenged and
3650 perhaps even eradicated for those announcing their location this way,
3651 when they share their whereabouts with private and public
3654 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
3656 <p
>The phone company logs provide a register of locations to check out
3657 when one want to figure out what the tracked person was doing. It is
3658 unavailable for most of us, but provided to selected government
3659 officials, company staff, those illegally buying information from
3660 unfaithful servants and crackers stealing the information. But the
3661 public information can be collected and analysed, and a free software
3662 tool to do so is called
3663 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
3664 discovered it when I read
3665 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
3666 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
3667 November
2014, and decided to check if it was available in Debian.
3668 The python program was in Debian, but
3669 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
3670 Debian
</a
> was completely broken and practically unmaintained. I
3671 uploaded a new version which did not work quite right, but did not
3672 have time to fix it then. This Christmas I decided to finally try to
3673 get Creepy operational in Debian. Now a fixed version is available in
3674 Debian unstable and testing, and almost all Debian specific patches
3676 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
3678 <p
>The Creepy program visualises geolocation information fetched from
3679 Twitter, Instagram, Flickr and Google+, and allow one to get a
3680 complete picture of every social media message posted recently in a
3681 given area, or track the movement of a given individual across all
3682 these services. Earlier it was possible to use the search API of at
3683 least some of these services without identifying oneself, but these
3684 days it is impossible. This mean that to use Creepy, you need to
3685 configure it to log in as yourself on these services, and provide
3686 information to them about your search interests. This should be taken
3687 into account when using Creepy, as it will also share information
3688 about yourself with the services.
</p
>
3690 <p
>The picture above show the twitter messages sent from (or at least
3691 geotagged with a position from) the city centre of Oslo, the capital
3692 of Norway. One useful way to use Creepy is to first look at
3693 information tagged with an area of interest, and next look at all the
3694 information provided by one or more individuals who was in the area.
3695 I tested it by checking out which celebrity provide their location in
3696 twitter messages by checkout out who sent twitter messages near a
3697 Norwegian TV station, and next could track their position over time,
3698 making it possible to locate their home and work place, among other
3699 things. A similar technique have been
3700 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
3701 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
3702 tool to discover lying governments, and a useful tool to help people
3703 understand the value of the private information they provide to the
3706 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
3707 it depend on several python modules currently missing in Jessie (at
3708 least python-instagram, python-flickrapi and
3709 python-requests-toolbelt).
</p
>
3711 <p
>(I have uploaded
3712 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
3713 screenshots.debian.net
</a
> and licensed it under the same terms as the
3714 Creepy program in Debian.)
</p
>
3719 <title>Always download Debian packages using Tor - the simple recipe
</title>
3720 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
3721 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
3722 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
3723 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
3724 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
3725 that those listening on the Internet lines would have good reason to
3726 believe a computer have a given security hole
</a
> if it download a
3727 security fix from a Debian mirror. This is a good reason to always
3728 use encrypted connections to the Debian mirror, to make sure those
3729 listening do not know which IP address to attack. In August, Richard
3730 Hartmann observed that encryption was not enough, when it was possible
3731 to interfere download size to security patches or the fact that
3732 download took place shortly after a security fix was released, and
3733 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
3734 to always use Tor to download packages from the Debian mirror
</a
>. He
3735 was not the first to propose this, as the
3736 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
3737 package by Tim Retout already existed to make it easy to convince apt
3738 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
3739 aware of that package when I read the blog post from Richard.
</p
>
3741 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
3742 sysadmins, and he set up a Tor hidden service on one of the central
3743 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3744 it possible to download packages directly between two tor nodes,
3745 making sure the network traffic always were encrypted.
</p
>
3747 <p
>Here is a short recipe for enabling this on your machine, by
3748 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
3749 urls with tor+http and tor+https, and using the hidden service instead
3750 of the official Debian mirror site. I recommend installing
3751 <tt
>etckeeper
</tt
> before you start to have a history of the changes
3752 done in /etc/.
</p
>
3754 <blockquote
><pre
>
3755 apt install apt-transport-tor
3756 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
3757 sed -i
's% http% tor+http%
' /etc/apt/sources.list
3758 </pre
></blockquote
>
3760 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
3761 the sed commands for these too. The sed command is assuming your are
3762 using the ftp.debian.org Debian mirror. Adjust the command (or just
3763 edit the file manually) to match your mirror.
</p
>
3765 <p
>This work in Debian Jessie and later. Note that tools like
3766 <tt
>apt-file
</tt
> only recently started using the apt transport
3767 system, and do not work with these tor+http URLs. For
3768 <tt
>apt-file
</tt
> you need the version currently in experimental,
3769 which need a recent apt version currently only in unstable. So if you
3770 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
3772 <p
>Another advantage from this change is that your machine will start
3773 using Tor regularly and at fairly random intervals (every time you
3774 update the package lists or upgrade or install a new package), thus
3775 masking other Tor traffic done from the same machine. Using Tor will
3776 become normal for the machine in question.
</p
>
3778 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
3779 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
3780 enabled. It would be great if it was the default on any Debian
3786 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
3787 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
3788 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
3789 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
3790 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
3791 call the car license plate numbers in those days. I would write the
3792 numbers down in my little book and compare notes with the other kids
3793 to see how many region codes we had seen and if we had seen some
3794 exotic or special region codes and numbers. It was a fun game to pass
3795 time, as we kids have plenty of it.
</p
>
3797 <p
>A few days I came across
3798 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
3799 project
</a
>, a free software project to automatically discover and
3800 report license plates in images and video streams, and provide the
3801 "car numbers
" in a machine readable format. I
've been looking for
3802 such system for a while now, because I believe it is a bad idea that the
3803 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
3804 number plate recognition
</a
> tool only is available in the hands of
3805 the powerful, and want it to be available also for the powerless to
3806 even the score when it comes to surveillance and sousveillance. I
3807 discovered the developer
3808 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
3809 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
3810 help him get it into shape to get the package uploaded into the Debian
3813 <p
>Today we finally managed to get the package into shape and uploaded
3814 it into Debian, where it currently
3815 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
3816 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
3818 <p
>I guess you are wondering why on earth such tool would be useful
3819 for the common folks, ie those not running a large government
3820 surveillance system? Well, I plan to put it in a computer on my bike
3821 and in my car, tracking the cars nearby and allowing me to be notified
3822 when number plates on my watch list are discovered. Another use case
3823 was suggested by a friend of mine, who wanted to set it up at his home
3824 to open the car port automatically when it discovered the plate on his
3825 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3826 capable of placing his license plate number of a piece of cardboard to
3827 open his car port, men replied that it was always unlocked anyway. I
3828 guess for such use case it make sense. I am sure there are other use
3829 cases too, for those with imagination and a vision.
</p
>
3831 <p
>If you want to build your own version of the Debian package, check
3832 out the upstream git source and symlink ./distros/debian to ./debian/
3833 before running
"debuild
" to build the source. Or wait a bit until the
3834 package show up in unstable.
</p
>
3839 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
3840 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
3841 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
3842 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
3843 <description><p
>Around three years ago, I created
3844 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
3845 system
</a
> to get a more practical solution in Debian for handing
3846 hardware related packages. A GUI system in the isenkram package will
3847 present a pop-up dialog when some hardware dongle supported by
3848 relevant packages in Debian is inserted into the machine. The same
3849 lookup mechanism to detect packages is available as command line
3850 tools in the isenkram-cli package. In addition to mapping hardware,
3851 it will also map kernel firmware files to packages and make it easy to
3852 install needed firmware packages automatically. The key for this
3853 system to work is a good way to map hardware to packages, in other
3854 words, allow packages to announce what hardware they will work
3857 <p
>I started by providing data files in the isenkram source, and
3858 adding code to download the latest version of these data files at run
3859 time, to ensure every user had the most up to date mapping available.
3860 I also added support for storing the mapping in the Packages file in
3861 the apt repositories, but did not push this approach because while I
3862 was trying to figure out how to best store hardware/package mappings,
3863 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
3864 appstream system
</a
> was announced. I got in touch and suggested to
3865 add the hardware mapping into that data set to be able to use
3866 appstream as a data source, and this was accepted at least for the
3867 Debian version of appstream.
</p
>
3869 <p
>A few days ago using appstream in Debian for this became possible,
3870 and today I uploaded a new version
0.20 of isenkram adding support for
3871 appstream as a data source for mapping hardware to packages. The only
3872 package so far using appstream to announce its hardware support is my
3873 pymissile package. I got help from Matthias Klumpp with figuring out
3874 how do add the required
3875 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
3876 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
3877 this content:
</p
>
3879 <blockquote
><pre
>
3880 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3881 &lt;component
&gt;
3882 &lt;id
&gt;pymissile
&lt;/id
&gt;
3883 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
3884 &lt;name
&gt;pymissile
&lt;/name
&gt;
3885 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
3886 &lt;description
&gt;
3888 Pymissile provides a curses interface to control an original
3889 Marks and Spencer / Striker USB Missile Launcher, as well as a
3890 motion control script to allow a webcamera to control the
3893 &lt;/description
&gt;
3894 &lt;provides
&gt;
3895 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
3896 &lt;/provides
&gt;
3897 &lt;/component
&gt;
3898 </pre
></blockquote
>
3900 <p
>The key for isenkram is the component/provides/modalias value,
3901 which is a glob style match rule for hardware specific strings
3902 (modalias strings) provided by the Linux kernel. In this case, it
3903 will map to all USB devices with vendor code
1130 and product code
3906 <p
>Note, it is important that the license of all the metadata files
3907 are compatible to have permissions to aggregate them into archive wide
3908 appstream files. Matthias suggested to use MIT or BSD licenses for
3909 these files. A challenge is figuring out a good id for the data, as
3910 it is supposed to be globally unique and shared across distributions
3911 (in other words, best to coordinate with upstream what to use). But
3912 it can be changed later or, so we went with the package name as
3913 upstream for this project is dormant.
</p
>
3915 <p
>To get the metadata file installed in the correct location for the
3916 mirror update scripts to pick it up and include its content the
3917 appstream data source, the file must be installed in the binary
3918 package under /usr/share/appdata/. I did this by adding the following
3919 line to debian/pymissile.install:
</p
>
3921 <blockquote
><pre
>
3922 debian/pymissile.metainfo.xml usr/share/appdata
3923 </pre
></blockquote
>
3925 <p
>With that in place, the command line tool isenkram-lookup will list
3926 all packages useful on the current computer automatically, and the GUI
3927 pop-up handler will propose to install the package not already
3928 installed if a hardware dongle is inserted into the machine in
3931 <p
>Details of the modalias field in appstream is available from the
3932 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
3934 <p
>To locate the modalias values of all hardware present in a machine,
3935 try running this command on the command line:
</p
>
3937 <blockquote
><pre
>
3938 cat $(find /sys/devices/|grep modalias)
3939 </pre
></blockquote
>
3941 <p
>To learn more about the isenkram system, please check out
3942 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3943 blog posts tagged isenkram
</a
>.
</p
>
3948 <title>The GNU General Public License is not magic pixie dust
</title>
3949 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
3950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
3951 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
3952 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
3953 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
3954 GPL is not magic pixie dust
</a
>" explain the importance of making sure
3955 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
3956 I quote the blog post from Paul in full here with his permission:
<p
>
3960 <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
>
3963 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
3965 The first step is to choose a
3966 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
3969 The next step is, when someone fails to follow that copyleft license,
3970 <b
>it must be enforced
</b
><br/
>
3972 and its a simple fact of our modern society that such type of
3975 is incredibly expensive to do and incredibly difficult to do.
3978 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
3979 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
3980 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
3981 0x57</a
></small
></p
>
3983 <p
>As the Debian Website
3984 <a href=
"https://bugs.debian.org/
794116">used
</a
>
3985 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
3986 imply, public domain and permissively licensed software can lead to
3987 the production of more proprietary software as people discover useful
3988 software, extend it and or incorporate it into their hardware or
3989 software products. Copyleft licenses such as the GNU GPL were created
3990 to close off this avenue to the production of proprietary software but
3991 such licenses are not enough. With the ongoing adoption of Free
3992 Software by individuals and groups, inevitably the community
's
3993 expectations of license compliance are violated, usually out of
3994 ignorance of the way Free Software works, but not always. As Karen
3995 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
3996 Freedom
">FaiF
</a
>
3997 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
3998 copyleft is nothing if no-one is willing and able to stand up in court
3999 to protect it. The reality of today
's world is that legal
4000 representation is expensive, difficult and time consuming. With
4001 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
4002 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
4003 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
4004 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
4005 of the Linux project, Debian and other groups against GPL violations.
4006 In March the SFC supported a
4007 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
4008 by Christoph Hellwig
</a
> against VMware for refusing to
4009 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
4010 with the GPL
</a
> in relation to their use of parts of the Linux
4011 kernel. Since then two of their sponsors pulled corporate funding and
4013 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
4014 or cancelled their talks
</a
>. As a result they have decided to rely
4015 less on corporate funding and more on the broad community of
4016 individuals who support Free Software and copyleft. So the SFC has
4017 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
4018 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
4019 a community of folks who stand up for copyleft and the GPL by
4020 supporting their work on promoting and supporting copyleft and Free
4023 <p
>If you support Free Software,
4024 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
4025 what the SFC do, agree with their
4026 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
4027 principles
</a
>, are happy about their
4028 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
4029 work on a project that is an SFC
4030 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
4031 just want to stand up for copyleft, please join
4032 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
4033 Allan Webber
</a
>,
4034 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
4036 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
4037 Bacon
</a
>, myself and
4038 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
4040 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
4041 next week your donation will be
4042 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
4043 by an anonymous donor. Please also consider asking your employer to
4044 match your donation or become a sponsor of SFC. Don
't forget to
4045 spread the word about your support for SFC via email, your blog and or
4046 social media accounts.
</p
>
4050 <p
>I agree with Paul on this topic and just signed up as a Supporter
4051 of Software Freedom Conservancy myself. Perhaps you should be a
4052 supporter too?
</p
>
4057 <title>PGP key transition statement for key EE4E02F9
</title>
4058 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
4059 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
4060 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
4061 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
4062 set it up properly. I wanted to generate it offline and have it
4063 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
4064 smart card
</a
> for daily use, and learning how to do it and finding
4065 time to sit down with an offline machine almost took forever. But
4066 finally I
've been able to complete the process, and have now moved
4067 from my old GPG key to a new GPG key. See
4068 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
4069 full transition statement, signed with both my old and new key
</a
> for
4070 the details. This is my new key:
</p
>
4073 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
4074 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
4075 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
4076 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
4077 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
4078 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
4079 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
4082 <p
>The key can be downloaded from the OpenPGP key servers, signed by
4083 my old key.
</p
>
4085 <p
>If you signed my old key
4086 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
4087 I
'd very much appreciate a signature on my new key, details and
4088 instructions in the transition statement. I m happy to reciprocate if
4089 you have a similarly signed transition statement to present.
</p
>
4094 <title>The life and death of a laptop battery
</title>
4095 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
4096 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
4097 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
4098 <description><p
>When I get a new laptop, the battery life time at the start is OK.
4099 But this do not last. The last few laptops gave me a feeling that
4100 within a year, the life time is just a fraction of what it used to be,
4101 and it slowly become painful to use the laptop without power connected
4102 all the time. Because of this, when I got a new Thinkpad X230 laptop
4103 about two years ago, I decided to monitor its battery state to have
4104 more hard facts when the battery started to fail.
</p
>
4106 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
4108 <p
>First I tried to find a sensible Debian package to record the
4109 battery status, assuming that this must be a problem already handled
4110 by someone else. I found
4111 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
4112 which collects statistics from the battery, but it was completely
4113 broken. I sent a few suggestions to the maintainer, but decided to
4114 write my own collector as a shell script while I waited for feedback
4116 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
4117 blog post about the battery development on a MacBook Air
</a
> I also
4119 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
4120 available in Debian.
</p
>
4122 <p
>I started my collector
2013-
07-
15, and it has been collecting
4123 battery stats ever since. Now my
4124 /var/log/hjemmenett-battery-status.log file contain around
115,
000
4125 measurements, from the time the battery was working great until now,
4126 when it is unable to charge above
7% of original capacity. My
4127 collector shell script is quite simple and look like this:
</p
>
4132 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
4134 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
4135 logfile=/var/log/hjemmenett-battery-status.log
4137 files=
"manufacturer model_name technology serial_number \
4138 energy_full energy_full_design energy_now cycle_count status
"
4140 if [ ! -e
"$logfile
" ] ; then
4142 printf
"timestamp,
"
4144 printf
"%s,
" $f
4147 )
> "$logfile
"
4151 # Print complete message in one echo call, to avoid race condition
4152 # when several log processes run in parallel.
4153 msg=$(printf
"%s,
" $(date +%s); \
4154 for f in $files; do \
4155 printf
"%s,
" $(cat $f); \
4157 echo
"$msg
"
4160 cd /sys/class/power_supply
4163 (cd $bat
&& log_battery
>> "$logfile
")
4167 <p
>The script is called when the power management system detect a
4168 change in the power status (power plug in or out), and when going into
4169 and out of hibernation and suspend. In addition, it collect a value
4170 every
10 minutes. This make it possible for me know when the battery
4171 is discharging, charging and how the maximum charge change over time.
4172 The code for the Debian package
4173 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
4174 available on github
</a
>.
</p
>
4176 <p
>The collected log file look like this:
</p
>
4179 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
4180 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
4182 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
4183 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
4186 <p
>I wrote a small script to create a graph of the charge development
4187 over time. This graph depicted above show the slow death of my laptop
4190 <p
>But why is this happening? Why are my laptop batteries always
4191 dying in a year or two, while the batteries of space probes and
4192 satellites keep working year after year. If we are to believe
4193 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
4194 University
</a
>, the cause is me charging the battery whenever I have a
4195 chance, and the fix is to not charge the Lithium-ion batteries to
100%
4196 all the time, but to stay below
90% of full charge most of the time.
4197 I
've been told that the Tesla electric cars
4198 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
4199 the charge of their batteries to
80%
</a
>, with the option to charge to
4200 100% when preparing for a longer trip (not that I would want a car
4201 like Tesla where rights to privacy is abandoned, but that is another
4202 story), which I guess is the option we should have for laptops on
4203 Linux too.
</p
>
4205 <p
>Is there a good and generic way with Linux to tell the battery to
4206 stop charging at
80%, unless requested to charge to
100% once in
4207 preparation for a longer trip? I found
4208 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
4209 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
4210 80%
</a
>, but could not get it to work (kernel module refused to
4213 <p
>I wonder why the battery capacity was reported to be more than
100%
4214 at the start. I also wonder why the
"full capacity
" increases some
4215 times, and if it is possible to repeat the process to get the battery
4216 back to design capacity. And I wonder if the discharge and charge
4217 speed change over time, or if this stay the same. I did not yet try
4218 to write a tool to calculate the derivative values of the battery
4219 level, but suspect some interesting insights might be learned from
4222 <p
>Update
2015-
09-
24: I got a tip to install the packages
4223 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
4224 packages instead of the tp-smapi-dkms package I had tried to use
4225 initially, and use
'tlp setcharge
40 80' to change when charging start
4226 and stop. I
've done so now, but expect my existing battery is toast
4227 and need to be replaced. The proposal is unfortunately Thinkpad
4233 <title>New laptop - some more clues and ideas based on feedback
</title>
4234 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
4235 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
4236 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
4237 <description><p
>Several people contacted me after my previous blog post about my
4238 need for a new laptop, and provided very useful feedback. I wish to
4239 thank every one of these. Several pointed me to the possibility of
4240 fixing my X230, and I am already in the process of getting Lenovo to
4241 do so thanks to the on site, next day support contract covering the
4242 machine. But the battery is almost useless (I expect to replace it
4243 with a non-official battery) and I do not expect the machine to live
4244 for many more years, so it is time to plan its replacement. If I did
4245 not have a support contract, it was suggested to find replacement parts
4246 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
4247 might present a language barrier as I do not understand French.
</p
>
4249 <p
>One tip I got was to use the
4250 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
4251 compare laptop models. It seem to have more models available than
4252 prisjakt.no. Another tip I got from someone I know have similar
4253 keyboard preferences was that the HP EliteBook
840 keyboard is not
4254 very good, and this matches my experience with earlier EliteBook
4255 keyboards I tested. Because of this, I will not consider it any further.
4257 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
4258 newest Thinkpad X model. The keyboard reintroduces mouse buttons
4259 (which is missing from the X240), and is working fairly well with
4260 Debian Sid/Unstable according to
4261 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
4262 got on the keyboard quality are not consistent. Some say the keyboard
4263 is good, others say it is ok, while others say it is not very good.
4264 Those with experience from X41 and and X60 agree that the X250
4265 keyboard is not as good as those trusty old laptops, and suggest I
4266 keep and fix my X230 instead of upgrading, or get a used X230 to
4267 replace it. I
'm also told that the X250 lack leds for caps lock, disk
4268 activity and battery status, which is very convenient on my X230. I
'm
4269 also told that the CPU fan is running very often, making it a bit
4270 noisy. In any case, the X250 do not work out of the box with Debian
4271 Stable/Jessie, one of my requirements.
</p
>
4273 <p
>I have also gotten a few vendor proposals, one was
4274 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
4275 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
4276 The latter look very attractive to me.
</p
>
4278 <p
>Again, thank you all for the very useful feedback. It help a lot
4279 as I keep looking for a replacement.
</p
>
4281 <p
>Update
2015-
07-
06: I was recommended to check out the
4282 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
4284 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
4285 thinkpad X models
</a
>, and provide one year warranty.
</p
>
4290 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
4291 <link>http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html
</link>
4292 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html
</guid>
4293 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
4294 <description><p
>My primary work horse laptop is failing, and will need a
4295 replacement soon. The left
5 cm of the screen on my Thinkpad X230
4296 started flickering yesterday, and I suspect the cause is a broken
4297 cable, as changing the angle of the screen some times get rid of the
4298 flickering.
</p
>
4300 <p
>My requirements have not really changed since I bought it, and is
4302 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
4303 described them in
2013</a
>. The last time I bought a laptop, I had
4305 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
4306 where I could select at least a few of the requirements (mouse pin,
4307 wifi, weight) and go through the rest manually. Three button mouse
4308 and a good keyboard is not available as an option, and all the three
4309 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
4310 G2) lack three mouse buttons). It is also unclear to me how good the
4311 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
4312 the keyboard, even if the quality and robustness in the X series have
4313 deteriorated since X41.
</p
>
4315 <p
>I wonder how I can find a sensible laptop when none of the options
4316 seem sensible to me? Are there better services around to search the
4317 set of available laptops for features? Please send me an email if you
4318 have suggestions.
</p
>
4320 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
4321 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
4322 of endorsed hardware
</a
>, which is useful background information.
</p
>
4327 <title>How to stay with sysvinit in Debian Jessie
</title>
4328 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
4329 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
4330 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
4331 <description><p
>By now, it is well known that Debian Jessie will not be using
4332 sysvinit as its boot system by default. But how can one keep using
4333 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
4335 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
4336 Schubert
</a
> and
4337 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
4340 <p
>If you already are using Wheezy and want to upgrade to Jessie and
4341 keep sysvinit as your boot system, create a file
4342 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
4343 you upgrade:
</p
>
4345 <p
><blockquote
><pre
>
4346 Package: systemd-sysv
4347 Pin: release o=Debian
4349 </pre
></blockquote
><p
>
4351 <p
>This file content will tell apt and aptitude to not consider
4352 installing systemd-sysv as part of any installation and upgrade
4353 solution when resolving dependencies, and thus tell it to avoid
4354 systemd as a default boot system. The end result should be that the
4355 upgraded system keep using sysvinit.
</p
>
4357 <p
>If you are installing Jessie for the first time, there is no way to
4358 get sysvinit installed by default (debootstrap used by
4359 debian-installer have no option for this), but one can tell the
4360 installer to switch to sysvinit before the first boot. Either by
4361 using a kernel argument to the installer, or by adding a line to the
4362 preseed file used. First, the kernel command line argument:
4364 <p
><blockquote
><pre
>
4365 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
4366 </pre
></blockquote
><p
>
4368 <p
>Next, the line to use in a preseed file:
</p
>
4370 <p
><blockquote
><pre
>
4371 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
4372 </pre
></blockquote
><p
>
4374 <p
>One can of course also do this after the first boot by installing
4375 the sysvinit-core package.
</p
>
4377 <p
>I recommend only using sysvinit if you really need it, as the
4378 sysvinit boot sequence in Debian have several hardware specific bugs
4379 on Linux caused by the fact that it is unpredictable when hardware
4380 devices show up during boot. But on the other hand, the new default
4381 boot system still have a few rough edges I hope will be fixed before
4382 Jessie is released.
</p
>
4384 <p
>Update
2014-
11-
26: Inspired by
4385 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
4386 blog post by Torsten Glaser
</a
>, added --purge to the preseed
4392 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
4393 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
4394 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
4395 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
4396 <description><p
>The right to communicate with your friends and family in private,
4397 without anyone snooping, is a right every citicen have in a liberal
4398 democracy. But this right is under serious attack these days.
</p
>
4400 <p
>A while back it occurred to me that one way to make the dragnet
4401 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
4402 the whisleblower Snowden) more expensive for Internet email,
4403 is to deliver all email using SMTP via Tor. Such SMTP option would be
4404 a nice addition to the FreedomBox project if we could send email
4405 between FreedomBox machines without leaking metadata about the emails
4406 to the people peeking on the wire. I
4407 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
4408 this on the FreedomBox project mailing list in October
</a
> and got a
4409 lot of useful feedback and suggestions. It also became obvious to me
4410 that this was not a novel idea, as the same idea was tested and
4411 documented by Johannes Berg as early as
2006, and both
4412 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
4413 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
4414 propose a similar method / protocol to pass emails between users.
</p
>
4416 <p
>To implement such system one need to set up a Tor hidden service
4417 providing the SMTP protocol on port
25, and use email addresses
4418 looking like username@hidden-service-name.onion. With such addresses
4419 the connections to port
25 on hidden-service-name.onion using Tor will
4420 go to the correct SMTP server. To do this, one need to configure the
4421 Tor daemon to provide the hidden service and the mail server to accept
4422 emails for this .onion domain. To learn more about Exim configuration
4423 in Debian and test the design provided by Johannes Berg in his FAQ, I
4424 set out yesterday to create a Debian package for making it trivial to
4425 set up such SMTP over Tor service based on Debian. Getting it to work
4426 were fairly easy, and
4427 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
4428 source code for the Debian package
</a
> is available from github. I
4429 plan to move it into Debian if further testing prove this to be a
4430 useful approach.
</p
>
4432 <p
>If you want to test this, set up a blank Debian machine without any
4433 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
4434 get rid of exim4). Install tor, clone the git repository mentioned
4435 above, build the deb and install it on the machine. Next, run
4436 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
4437 the instructions to get the service up and running. Restart tor and
4438 exim when it is done, and test mail delivery using swaks like
4441 <p
><blockquote
><pre
>
4442 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
4443 --to fbx@dutlqrrmjhtfa3vp.onion
4444 </pre
></blockquote
></p
>
4446 <p
>This will test the SMTP delivery using tor. Replace the email
4447 address with your own address to test your server. :)
</p
>
4449 <p
>The setup procedure is still to complex, and I hope it can be made
4450 easier and more automatic. Especially the tor setup need more work.
4451 Also, the package include a tor-smtp tool written in C, but its task
4452 should probably be rewritten in some script language to make the deb
4453 architecture independent. It would probably also make the code easier
4454 to review. The tor-smtp tool currently need to listen on a socket for
4455 exim to talk to it and is started using xinetd. It would be better if
4456 no daemon and no socket is needed. I suspect it is possible to get
4457 exim to run a command line tool for delivery instead of talking to a
4458 socket, and hope to figure out how in a future version of this
4461 <p
>Until I wipe my test machine, I can be reached using the
4462 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
4463 SMTorP. :)
</p
>
4468 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
4469 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
4470 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
4471 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
4472 <description><p
>If you ever had to moderate a mailman list, like the ones on
4473 alioth.debian.org, you know the web interface is fairly slow to
4474 operate. First you visit one web page, enter the moderation password
4475 and get a new page shown with a list of all the messages to moderate
4476 and various options for each email address. This take a while for
4477 every list you moderate, and you need to do it regularly to do a good
4478 job as a list moderator. But there is a quick alternative,
4479 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
4480 listadmin program
</a
>. It allow you to check lists for new messages
4481 to moderate in a fraction of a second. Here is a test run on two
4482 lists I recently took over:
</p
>
4484 <p
><blockquote
><pre
>
4485 % time listadmin xiph
4486 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
4487 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
4493 </pre
></blockquote
></p
>
4495 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
4496 there are no message in the moderation queue. Every morning I
4497 currently moderate
68 mailman lists, and it normally take around two
4498 minutes. When I took over the two pkg-xiph lists above a few days
4499 ago, there were
400 emails waiting in the moderator queue. It took me
4500 less than
15 minutes to process them all using the listadmin
4503 <p
>If you install
4504 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
4505 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
4506 with content like this, the moderation task is a breeze:
</p
>
4508 <p
><blockquote
><pre
>
4509 username username@example.org
4512 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
4515 adminurl https://{domain}/mailman/admindb/{list}
4516 mailman-list@lists.example.com
4519 other-list@otherserver.example.org
4520 </pre
></blockquote
></p
>
4522 <p
>There are other options to set as well. Check the manual page to
4523 learn the details.
</p
>
4525 <p
>If you are forced to moderate lists on a mailman installation where
4526 the SSL certificate is self signed or not properly signed by a
4527 generally accepted signing authority, you can set a environment
4528 variable when calling listadmin to disable SSL verification:
</p
>
4530 <p
><blockquote
><pre
>
4531 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
4532 </pre
></blockquote
></p
>
4534 <p
>If you want to moderate a subset of the lists you take care of, you
4535 can provide an argument to the listadmin script like I do in the
4536 initial screen dump (the xiph argument). Using an argument, only
4537 lists matching the argument string will be processed. This make it
4538 quick to accept messages if you notice the moderation request in your
4541 <p
>Without the listadmin program, I would never be the moderator of
68
4542 mailing lists, as I simply do not have time to spend on that if the
4543 process was any slower. The listadmin program have saved me hours of
4544 time I could spend elsewhere over the years. It truly is nice free
4547 <p
>As usual, if you use Bitcoin and want to show your support of my
4548 activities, please send Bitcoin donations to my address
4549 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4551 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
4552 configuration example. Also, I
've been told that the
4553 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
4559 <title>Debian Jessie, PXE and automatic firmware installation
</title>
4560 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
4561 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
4562 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
4563 <description><p
>When PXE installing laptops with Debian, I often run into the
4564 problem that the WiFi card require some firmware to work properly.
4565 And it has been a pain to fix this using preseeding in Debian.
4566 Normally something more is needed. But thanks to
4567 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
4568 package
</a
> and its recent tasksel extension, it has now become easy
4569 to do this using simple preseeding.
</p
>
4571 <p
>The isenkram-cli package provide tasksel tasks which will install
4572 firmware for the hardware found in the machine (actually, requested by
4573 the kernel modules for the hardware). (It can also install user space
4574 programs supporting the hardware detected, but that is not the focus
4575 of this story.)
</p
>
4577 <p
>To get this working in the default installation, two preeseding
4578 values are needed. First, the isenkram-cli package must be installed
4579 into the target chroot (aka the hard drive) before tasksel is executed
4580 in the pkgsel step of the debian-installer system. This is done by
4581 preseeding the base-installer/includes debconf value to include the
4582 isenkram-cli package. The package name is next passed to debootstrap
4583 for installation. With the isenkram-cli package in place, tasksel
4584 will automatically use the isenkram tasks to detect hardware specific
4585 packages for the machine being installed and install them, because
4586 isenkram-cli contain tasksel tasks.
</p
>
4588 <p
>Second, one need to enable the non-free APT repository, because
4589 most firmware unfortunately is non-free. This is done by preseeding
4590 the apt-mirror-setup step. This is unfortunate, but for a lot of
4591 hardware it is the only option in Debian.
</p
>
4593 <p
>The end result is two lines needed in your preseeding file to get
4594 firmware installed automatically by the installer:
</p
>
4596 <p
><blockquote
><pre
>
4597 base-installer base-installer/includes string isenkram-cli
4598 apt-mirror-setup apt-setup/non-free boolean true
4599 </pre
></blockquote
></p
>
4601 <p
>The current version of isenkram-cli in testing/jessie will install
4602 both firmware and user space packages when using this method. It also
4603 do not work well, so use version
0.15 or later. Installing both
4604 firmware and user space packages might give you a bit more than you
4605 want, so I decided to split the tasksel task in two, one for firmware
4606 and one for user space programs. The firmware task is enabled by
4607 default, while the one for user space programs is not. This split is
4608 implemented in the package currently in unstable.
</p
>
4610 <p
>If you decide to give this a go, please let me know (via email) how
4611 this recipe work for you. :)
</p
>
4613 <p
>So, I bet you are wondering, how can this work. First and
4614 foremost, it work because tasksel is modular, and driven by whatever
4615 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4616 isenkram-cli package place two files for tasksel to find. First there
4617 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
4619 <p
><blockquote
><pre
>
4620 Task: isenkram-packages
4622 Description: Hardware specific packages (autodetected by isenkram)
4623 Based on the detected hardware various hardware specific packages are
4625 Test-new-install: show show
4627 Packages: for-current-hardware
4629 Task: isenkram-firmware
4631 Description: Hardware specific firmware packages (autodetected by isenkram)
4632 Based on the detected hardware various hardware specific firmware
4633 packages are proposed.
4634 Test-new-install: mark show
4636 Packages: for-current-hardware-firmware
4637 </pre
></blockquote
></p
>
4639 <p
>The key parts are Test-new-install which indicate how the task
4640 should be handled and the Packages line referencing to a script in
4641 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4642 list of packages to install. The for-current-hardware-firmware script
4643 look like this to list relevant firmware for the machine:
4645 <p
><blockquote
><pre
>
4648 PATH=/usr/sbin:$PATH
4650 isenkram-autoinstall-firmware -l
4651 </pre
></blockquote
></p
>
4653 <p
>With those two pieces in place, the firmware is installed by
4654 tasksel during the normal d-i run. :)
</p
>
4656 <p
>If you want to test what tasksel will install when isenkram-cli is
4657 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
4658 --new-install
</tt
> to get the list of packages that tasksel would
4661 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
4662 pilots in testing this feature, as isenkram is used there now to
4663 install firmware, replacing the earlier scripts.
</p
>
4668 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
4669 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
4670 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
4671 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
4672 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
4673 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4674 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
4675 on a screen normally showing the bread types and prizes:
</p
>
4677 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
4679 <p
>If it had booted as it was supposed to, I would never had known
4680 about this hidden Linux installation. It is interesting what
4681 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
4686 <title>New lsdvd release version
0.17 is ready
</title>
4687 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
4688 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
4689 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
4690 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
4691 got a new set of developers a few weeks ago, after the original
4692 developer decided to step down and pass the project to fresh blood.
4693 This project is now maintained by Petter Reinholdtsen and Steve
4696 <p
>I just wrapped up
4697 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
4698 new lsdvd release
</a
>, available in git or from
4699 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
4700 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
4705 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
4706 <li
>Check for garbage in the program chains, which indicate that a track is
4707 non-existant, to work around additional copy protection
</li
>
4708 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
4709 <li
>Fix pallete display of first entry
</li
>
4710 <li
>Fix include orders
</li
>
4711 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
4712 <li
>Fix the chapter count
</li
>
4713 <li
>Make sure the array size and the array limit used when initialising
4714 the palette size is the same.
</li
>
4715 <li
>Fix array printing.
</li
>
4716 <li
>Correct subsecond calculations.
</li
>
4717 <li
>Add sector information to the output format.
</li
>
4718 <li
>Clean up code to be closer to ANSI C and compile without warnings
4719 with more GCC compiler warnings.
</li
>
4723 <p
>This change bring together patches for lsdvd in use in various
4724 Linux and Unix distributions, as well as patches submitted to the
4725 project the last nine years. Please check it out. :)
</p
>
4730 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
4731 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
4732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
4733 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
4734 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4735 project
</a
> provide a Linux solution for schools, including a
4736 powerful desktop with education software, a central server providing
4737 web pages, user database, user home directories, central login and PXE
4738 boot of both clients without disk and the installation to install Debian
4739 Edu on machines with disk (and a few other services perhaps to small
4740 to mention here). We in the Debian Edu team are currently working on
4741 the Jessie based version, trying to get everything in shape before the
4742 freeze, to avoid having to maintain our own package repository in the
4744 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
4745 status
</a
> can be seen on the Debian wiki, and there is still heaps of
4746 work left. Some fatal problems block testing, breaking the installer,
4747 but it is possible to work around these to get anyway. Here is a
4748 recipe on how to get the installation limping along.
</p
>
4750 <p
>First, download the test ISO via
4751 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
4752 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
4754 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
4755 The ISO build was broken on Tuesday, so we do not get a new ISO every
4756 12 hours or so, but thankfully the ISO we already got we are able to
4757 install with some tweaking.
</p
>
4759 <p
>When you get to the Debian Edu profile question, go to tty2
4760 (use Alt-Ctrl-F2), run
</p
>
4762 <p
><blockquote
><pre
>
4763 nano /usr/bin/edu-eatmydata-install
4764 </pre
></blockquote
></p
>
4766 <p
>and add
'exit
0' as the second line, disabling the eatmydata
4767 optimization. Return to the installation, select the profile you want
4768 and continue. Without this change, exim4-config will fail to install
4769 due to a known bug in eatmydata.
</p
>
4771 <p
>When you get the grub question at the end, answer /dev/sda (or if
4772 this do not work, figure out what your correct value would be. All my
4773 test machines need /dev/sda, so I have no advice if it do not fit
4774 your need.
</p
>
4776 <p
>If you installed a profile including a graphical desktop, log in as
4777 root after the initial boot from hard drive, and install the
4778 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4779 or mate. If you want several desktop options, install more than one
4780 metapackage. Once this is done, reboot and you should have a working
4781 graphical login screen. This workaround should no longer be needed
4782 once the education-tasks package version
1.801 enter testing in two
4785 <p
>I believe the ISO build will start working on two days when the new
4786 tasksel package enter testing and Steve McIntyre get a chance to
4787 update the debian-cd git repository. The eatmydata, grub and desktop
4788 issues are already fixed in unstable and testing, and should show up
4789 on the ISO as soon as the ISO build start working again. Well the
4790 eatmydata optimization is really just disabled. The proper fix
4791 require an upload by the eatmydata maintainer applying the patch
4792 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
4793 The rest have proper fixes in unstable.
</p
>
4795 <p
>I hope this get you going with the installation testing, as we are
4796 quickly running out of time trying to get our Jessie based
4797 installation ready before the distribution freeze in a month.
</p
>
4802 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
4803 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
4804 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
4805 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
4806 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
4807 to handle my fairly large DVD collection. It is a nice command line
4808 tool to get details about a DVD, like title, tracks, track length,
4809 etc, in XML, Perl or human readable format. But lsdvd have not seen
4810 any new development since
2006 and had a few irritating bugs affecting
4811 its use with some DVDs. Upstream seemed to be dead, and in January I
4812 sent a small probe asking for a version control repository for the
4813 project, without any reply. But I use it regularly and would like to
4814 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
4815 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
4816 the project admin, and after getting a reply from him explaining that
4817 he was no longer interested in the project, I asked if I could take
4818 over. And yesterday, I became project admin.
</p
>
4820 <p
>I
've been in touch with a Gentoo developer and the Debian
4821 maintainer interested in joining forces to maintain the upstream
4822 project, and I hope we can get a new release out fairly quickly,
4823 collecting the patches spread around on the internet into on place.
4824 I
've added the relevant Debian patches to the freshly created git
4825 repository, and expect the Gentoo patches to make it too. If you got
4826 a DVD collection and care about command line tools, check out
4827 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
4828 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
4829 list
</a
>. :)
</p
>
4834 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
4835 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
4836 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
4837 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
4838 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
4839 a lot quicker. When we install more than
2000 packages in
4840 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
4841 tasksel in the installer, unpacking the binary packages take forever.
4842 A part of the slow I/O issue was discussed in
4843 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
4844 much file system sync-ing done by dpkg, which is the package
4845 responsible for unpacking the binary packages. Other parts (like code
4846 executed by postinst scripts) might also sync to disk during
4847 installation. All this sync-ing to disk do not really make sense to
4848 me. If the machine crash half-way through, I start over, I do not try
4849 to salvage the half installed system. So the failure sync-ing is
4850 supposed to protect against, hardware or system crash, is not really
4851 relevant while the installer is running.
</p
>
4853 <p
>A few days ago, I thought of a way to get rid of all the file
4854 system sync()-ing in a fairly non-intrusive way, without the need to
4855 change the code in several packages. The idea is not new, but I have
4856 not heard anyone propose the approach using dpkg-divert before. It
4857 depend on the small and clever package
4858 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
4859 uses LD_PRELOAD to replace the system functions for syncing data to
4860 disk with functions doing nothing, thus allowing programs to live
4861 dangerous while speeding up disk I/O significantly. Instead of
4862 modifying the implementation of dpkg, apt and tasksel (which are the
4863 packages responsible for selecting, fetching and installing packages),
4864 it occurred to me that we could just divert the programs away, replace
4865 them with a simple shell wrapper calling
4866 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
4867 Two days ago I decided to test the idea, and wrapped up a simple
4868 implementation for the Debian Edu udeb.
</p
>
4870 <p
>The effect was stunning. In my first test it reduced the running
4871 time of the pkgsel step (installing tasks) from
64 to less than
44
4872 minutes (
20 minutes shaved off the installation) on an old Dell
4873 Latitude D505 machine. I am not quite sure what the optimised time
4874 would have been, as I messed up the testing a bit, causing the debconf
4875 priority to get low enough for two questions to pop up during
4876 installation. As soon as I saw the questions I moved the installation
4877 along, but do not know how long the question were holding up the
4878 installation. I did some more measurements using Debian Edu Jessie,
4879 and got these results. The time measured is the time stamp in
4880 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
4881 "pkgsel: finishing up
" lines, if you want to do the same measurement
4882 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4883 timing thus do not depend on how quickly the user handle the tasksel
4886 <p
><table
>
4889 <th
>Machine/setup
</th
>
4890 <th
>Original tasksel
</th
>
4891 <th
>Optimised tasksel
</th
>
4892 <th
>Reduction
</th
>
4896 <td
>Latitude D505 Main+LTSP LXDE
</td
>
4897 <td
>64 min (
07:
46-
08:
50)
</td
>
4898 <td
><44 min (
11:
27-
12:
11)
</td
>
4899 <td
>>20 min
18%
</td
>
4903 <td
>Latitude D505 Roaming LXDE
</td
>
4904 <td
>57 min (
08:
48-
09:
45)
</td
>
4905 <td
>34 min (
07:
43-
08:
17)
</td
>
4906 <td
>23 min
40%
</td
>
4910 <td
>Latitude D505 Minimal
</td
>
4911 <td
>22 min (
10:
37-
10:
59)
</td
>
4912 <td
>11 min (
11:
16-
11:
27)
</td
>
4913 <td
>11 min
50%
</td
>
4917 <td
>Thinkpad X200 Minimal
</td
>
4918 <td
>6 min (
08:
19-
08:
25)
</td
>
4919 <td
>4 min (
08:
04-
08:
08)
</td
>
4920 <td
>2 min
33%
</td
>
4924 <td
>Thinkpad X200 Roaming KDE
</td
>
4925 <td
>19 min (
09:
21-
09:
40)
</td
>
4926 <td
>15 min (
10:
25-
10:
40)
</td
>
4927 <td
>4 min
21%
</td
>
4930 </table
></p
>
4932 <p
>The test is done using a netinst ISO on a USB stick, so some of the
4933 time is spent downloading packages. The connection to the Internet
4934 was
100Mbit/s during testing, so downloading should not be a
4935 significant factor in the measurement. Download typically took a few
4936 seconds to a few minutes, depending on the amount of packages being
4937 installed.
</p
>
4939 <p
>The speedup is implemented by using two hooks in
4940 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
4941 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
4942 finish-install.d hook to remove the divert at the end of the
4943 installation. I picked the pre-pkgsel.d hook instead of the
4944 post-base-installer.d hook because I test using an ISO without the
4945 eatmydata package included, and the post-base-installer.d hook in
4946 Debian Edu can only operate on packages included in the ISO. The
4947 negative effect of this is that I am unable to activate this
4948 optimization for the kernel installation step in d-i. If the code is
4949 moved to the post-base-installer.d hook, the speedup would be larger
4950 for the entire installation.
</p
>
4952 <p
>I
've implemented this in the
4953 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
4954 git repository, and plan to provide the optimization as part of the
4955 Debian Edu installation. If you want to test this yourself, you can
4956 create two files in the installer (or in an udeb). One shell script
4957 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
4959 <p
><blockquote
><pre
>
4962 . /usr/share/debconf/confmodule
4964 logger -t my-pkgsel
"info: $*
"
4967 logger -t my-pkgsel
"error: $*
"
4969 override_install() {
4970 apt-install eatmydata || true
4971 if [ -x /target/usr/bin/eatmydata ] ; then
4972 for bin in dpkg apt-get aptitude tasksel ; do
4974 # Test that the file exist and have not been diverted already.
4975 if [ -f /target$file ] ; then
4976 info
"diverting $file using eatmydata
"
4977 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
4978 > /target$file.edu
4979 chmod
755 /target$file.edu
4980 in-target dpkg-divert --package debian-edu-config \
4981 --rename --quiet --add $file
4982 ln -sf ./$bin.edu /target$file
4984 error
"unable to divert $file, as it is missing.
"
4988 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
4993 </pre
></blockquote
></p
>
4995 <p
>To clean up, another shell script should go into
4996 /usr/lib/finish-install.d/ with code like this:
4998 <p
><blockquote
><pre
>
5000 . /usr/share/debconf/confmodule
5002 logger -t my-finish-install
"error: $@
"
5004 remove_install_override() {
5005 for bin in dpkg apt-get aptitude tasksel ; do
5007 if [ -x /target$file.edu ] ; then
5009 in-target dpkg-divert --package debian-edu-config \
5010 --rename --quiet --remove $file
5013 error
"Missing divert for $file.
"
5016 sync # Flush file buffers before continuing
5019 remove_install_override
5020 </pre
></blockquote
></p
>
5022 <p
>In Debian Edu, I placed both code fragments in a separate script
5023 edu-eatmydata-install and call it from the pre-pkgsel.d and
5024 finish-install.d scripts.
</p
>
5026 <p
>By now you might ask if this change should get into the normal
5027 Debian installer too? I suspect it should, but am not sure the
5028 current debian-installer coordinators find it useful enough. It also
5029 depend on the side effects of the change. I
'm not aware of any, but I
5030 guess we will see if the change is safe after some more testing.
5031 Perhaps there is some package in Debian depending on sync() and
5032 fsync() having effect? Perhaps it should go into its own udeb, to
5033 allow those of us wanting to enable it to do so without affecting
5036 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
5037 will break installation of all programs using gnutls because of
5038 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
5039 eatmydata package in Debian will solve it.
</p
>
5041 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
5042 the optimization work again. And I have discovered that the
5043 dpkg-divert trick is not really needed and implemented a slightly
5044 simpler approach as part of the debian-edu-install package. See
5045 tools/edu-eatmydata-install in the source package.
</p
>
5047 <p
>Update
2014-
11-
11: Unfortunately, a new
5048 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
5049 triggering on i386 made it into testing, and broke this installation
5050 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
5051 request
768893</a
> is accepted, it should be working again.
</p
>
5056 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
5057 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
5058 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
5059 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
5060 <description><p
>Yesterday, I had the pleasure of attending a talk with the
5061 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
5062 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
5063 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
5064 learn that there is a large set of publicly available key servers to
5065 use when looking for peoples public key. So far I have used
5066 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
5067 were misbehaving, but those days are ended. The servers I have used
5068 up until yesterday have been slow and some times unavailable. I hope
5069 those problems are gone now.
</p
>
5071 <p
>Behind the round robin DNS entry of the
5072 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
5073 there is a pool of more than
100 keyservers which are checked every
5074 day to ensure they are well connected and up to date. It must be
5075 better than what I have used so far. :)
</p
>
5077 <p
>Yesterdays speaker told me that the service is the default
5078 keyserver provided by the default configuration in GnuPG, but this do
5079 not seem to be used in Debian. Perhaps it should?
</p
>
5081 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
5084 <p
><blockquote
><pre
>
5085 keyserver pool.sks-keyservers.net
5086 </pre
></blockquote
></p
>
5088 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
5089 entries in DNS. Just for fun, I did just that at work, so now every
5090 user of GnuPG at the University of Oslo should find a OpenGPG
5091 keyserver automatically should their need it:
</p
>
5093 <p
><blockquote
><pre
>
5094 % host -t srv _pgpkey-http._tcp.uio.no
5095 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
5097 </pre
></blockquote
></p
>
5099 <p
>Now if only
5100 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
5101 HKP lookup protocol
</a
> supported finding signature paths, I would be
5102 very happy. It can look up a given key or search for a user ID, but I
5103 normally do not want that, but to find a trust path from my key to
5104 another key. Given a user ID or key ID, I would like to find (and
5105 download) the keys representing a signature path from my key to the
5106 key in question, to be able to get a trust path between the two keys.
5107 This is as far as I can tell not possible today. Perhaps something
5108 for a future version of the protocol?
</p
>
5113 <title>From English wiki to translated PDF and epub via Docbook
</title>
5114 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
5115 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
5116 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
5117 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
5118 project
</a
> provide an instruction manual for teachers, system
5119 administrators and other users that contain useful tips for setting up
5120 and maintaining a Debian Edu installation. This text is about how the
5121 text processing of this manual is handled in the project.
</p
>
5123 <p
>One goal of the project is to provide information in the native
5124 language of its users, and for this we need to handle translations.
5125 But we also want to make sure each language contain the same
5126 information, so for this we need a good way to keep the translations
5127 in sync. And we want it to be easy for our users to improve the
5128 documentation, avoiding the need to learn special formats or tools to
5129 contribute, and the obvious way to do this is to make it possible to
5130 edit the documentation using a web browser. We also want it to be
5131 easy for translators to keep the translation up to date, and give them
5132 help in figuring out what need to be translated. Here is the list of
5133 tools and the process we have found trying to reach all these
5136 <p
>We maintain the authoritative source of our manual in the
5137 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
5138 wiki
</a
>, as several wiki pages written in English. It consist of one
5139 front page with references to the different chapters, several pages
5140 for each chapter, and finally one
"collection page
" gluing all the
5141 chapters together into one large web page (aka
5142 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
5143 AllInOne page
</a
>). The AllInOne page is the one used for further
5144 processing and translations. Thanks to the fact that the
5145 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
5146 wiki.debian.org support exporting pages in
5147 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
5148 the list of pages to export using the raw version of the AllInOne
5149 page, loop over each of them to generate a Docbook XML version of the
5150 manual. This process also download images and transform image
5151 references to use the locally downloaded images. The generated
5152 Docbook XML files are slightly broken, so some post-processing is done
5153 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
5154 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
5155 a handfull of images. The XML file can now be used to generate PDF, HTML
5156 and epub versions of the English manual. This is the basic step of
5157 our process, making PDF (using dblatex), HTML (using xsltproc) and
5158 epub (using dbtoepub) version from Docbook XML, and the resulting files
5159 are placed in the debian-edu-doc-en binary package.
</p
>
5161 <p
>But English documentation is not enough for us. We want translated
5162 documentation too, and we want to make it easy for translators to
5163 track the English original. For this we use the
5164 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
5165 which allow us to transform the English Docbook XML file into a
5166 translation file (a .pot file), usable with the normal gettext based
5167 translation tools used by those translating free software. The pot
5168 file is used to create and maintain translation files (several .po
5169 files), which the translations update with the native language
5170 translations of all titles, paragraphs and blocks of text in the
5171 original. The next step is combining the original English Docbook XML
5172 and the translation file (say debian-edu-wheezy-manual.nb.po), to
5173 create a translated Docbook XML file (in this case
5174 debian-edu-wheezy-manual.nb.xml). This translated (or partly
5175 translated, if the translation is not complete) Docbook XML file can
5176 then be used like the original to create a PDF, HTML and epub version
5177 of the documentation.
</p
>
5179 <p
>The translators use different tools to edit the .po files. We
5181 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
5182 while some use emacs and vi, others can use web based editors like
5183 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
5184 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
5185 is where the .po file end up, in our git repository. Updated
5186 translations can either be committed directly to git, or submitted as
5187 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
5188 against the debian-edu-doc package
</a
>.
</p
>
5190 <p
>One challenge is images, which both might need to be translated (if
5191 they show translated user applications), and are needed in different
5192 formats when creating PDF and HTML versions (epub is a HTML version in
5193 this regard). For this we transform the original PNG images to the
5194 needed density and format during build, and have a way to provide
5195 translated images by storing translated versions in
5196 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
5197 package maintainers know more.
</p
>
5199 <p
>If you wonder what the result look like, we provide
5200 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
5201 of the documentation packages on the web
</a
>. See for example the
5202 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
5203 PDF version
</a
> or the
5204 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
5205 HTML version
</a
>. We do not yet build the epub version by default,
5206 but perhaps it will be done in the future.
</p
>
5208 <p
>To learn more, check out
5209 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
5210 debian-edu-doc package
</a
>,
5211 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
5212 manual on the wiki
</a
> and
5213 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
5214 translation instructions
</a
> in the manual.
</p
>
5219 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
5220 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
5221 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
5222 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
5223 <description><p
>It would be nice if it was easier in Debian to get all the hardware
5224 related packages relevant for the computer installed automatically.
5225 So I implemented one, using
5226 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
5227 package
</a
>. To use it, install the tasksel and isenkram packages and
5228 run tasksel as user root. You should be presented with a new option,
5229 "Hardware specific packages (autodetected by isenkram)
". When you
5230 select it, tasksel will install the packages isenkram claim is fit for
5231 the current hardware, hot pluggable or not.
<p
>
5233 <p
>The implementation is in two files, one is the tasksel menu entry
5234 description, and the other is the script used to extract the list of
5235 packages to install. The first part is in
5236 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
5239 <p
><blockquote
><pre
>
5242 Description: Hardware specific packages (autodetected by isenkram)
5243 Based on the detected hardware various hardware specific packages are
5245 Test-new-install: mark show
5247 Packages: for-current-hardware
5248 </pre
></blockquote
></p
>
5250 <p
>The second part is in
5251 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
5254 <p
><blockquote
><pre
>
5259 isenkram-autoinstall-firmware -l
5261 </pre
></blockquote
></p
>
5263 <p
>All in all, a very short and simple implementation making it
5264 trivial to install the hardware dependent package we all may want to
5265 have installed on our machines. I
've not been able to find a way to
5266 get tasksel to tell you exactly which packages it plan to install
5267 before doing the installation. So if you are curious or careful,
5268 check the output from the isenkram-* command line tools first.
</p
>
5270 <p
>The information about which packages are handling which hardware is
5271 fetched either from the isenkram package itself in
5272 /usr/share/isenkram/, from git.debian.org or from the APT package
5273 database (using the Modaliases header). The APT package database
5274 parsing have caused a nasty resource leak in the isenkram daemon (bugs
5275 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
5276 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
5277 the python-apt code (bug
5278 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
5279 workaround I was able to get rid of the file descriptor leak and
5280 reduce the memory leak from ~
30 MiB per hardware detection down to
5281 around
2 MiB per hardware detection. It should make the desktop
5282 daemon a lot more useful. The fix is in version
0.7 uploaded to
5283 unstable today.
</p
>
5285 <p
>I believe the current way of mapping hardware to packages in
5286 Isenkram is is a good draft, but in the future I expect isenkram to
5287 use the AppStream data source for this. A proposal for getting proper
5288 AppStream support into Debian is floating around as
5289 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
5290 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
5291 project
</a
> will take place this summer to improve the situation. I
5292 look forward to seeing the result, and welcome patches for isenkram to
5293 start using the information when it is ready.
</p
>
5295 <p
>If you want your package to map to some specific hardware, either
5296 add a
"Xb-Modaliases
" header to your control file like I did in
5297 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
5298 package
</a
> or submit a bug report with the details to the isenkram
5300 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
5301 blog posts tagged isenkram
</a
> for details on the notation. I expect
5302 the information will be migrated to AppStream eventually, but for the
5303 moment I got no better place to store it.
</p
>
5308 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
5309 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
5310 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
5311 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
5312 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
5313 project
</a
> is working on providing the software and hardware to make
5314 it easy for non-technical people to host their data and communication
5315 at home, and being able to communicate with their friends and family
5316 encrypted and away from prying eyes. It is still going strong, and
5317 today a major mile stone was reached.
</p
>
5319 <p
>Today, the last of the packages currently used by the project to
5320 created the system images were accepted into Debian Unstable. It was
5321 the freedombox-setup package, which is used to configure the images
5322 during build and on the first boot. Now all one need to get going is
5323 the build code from the freedom-maker git repository and packages from
5324 Debian. And once the freedombox-setup package enter testing, we can
5325 build everything directly from Debian. :)
</p
>
5327 <p
>Some key packages used by Freedombox are
5328 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
5329 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
5330 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
5331 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
5332 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
5333 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
5334 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
5335 are plans to integrate more packages into the setup. User
5336 documentation is maintained on the Debian wiki. Please
5337 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
5338 the manual
</a
> and help us improve it.
</p
>
5340 <p
>To test for yourself and create boot images with the FreedomBox
5341 setup, run this on a Debian machine using a user with sudo rights to
5342 become root:
</p
>
5344 <p
><pre
>
5345 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5346 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5348 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5350 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5351 </pre
></p
>
5353 <p
>Root access is needed to run debootstrap and mount loopback
5354 devices. See the README in the freedom-maker git repo for more
5355 details on the build. If you do not want all three images, trim the
5356 make line. Note that the virtualbox-image target is not really
5357 virtualbox specific. It create a x86 image usable in kvm, qemu,
5358 vmware and any other x86 virtual machine environment. You might need
5359 the version of vmdebootstrap in Jessie to get the build working, as it
5360 include fixes for a race condition with kpartx.
</p
>
5362 <p
>If you instead want to install using a Debian CD and the preseed
5363 method, boot a Debian Wheezy ISO and use this boot argument to load
5364 the preseed values:
</p
>
5366 <p
><pre
>
5367 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
5368 </pre
></p
>
5370 <p
>I have not tested it myself the last few weeks, so I do not know if
5371 it still work.
</p
>
5373 <p
>If you wonder how to help, one task you could look at is using
5374 systemd as the boot system. It will become the default for Linux in
5375 Jessie, so we need to make sure it is usable on the Freedombox. I did
5376 a simple test a few weeks ago, and noticed dnsmasq failed to start
5377 during boot when using systemd. I suspect there are other problems
5378 too. :) To detect problems, there is a test suite included, which can
5379 be run from the plinth web interface.
</p
>
5381 <p
>Give it a go and let us know how it goes on the mailing list, and help
5382 us get the new release published. :) Please join us on
5383 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
5384 irc.debian.org)
</a
> and
5385 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5386 mailing list
</a
> if you want to help make this vision come true.
</p
>
5391 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
5392 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
5393 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
5394 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
5395 <description><p
>For a while now, I have been looking for a sensible offsite backup
5396 solution for use at home. My requirements are simple, it must be
5397 cheap and locally encrypted (in other words, I keep the encryption
5398 keys, the storage provider do not have access to my private files).
5399 One idea me and my friends had many years ago, before the cloud
5400 storage providers showed up, was to use Google mail as storage,
5401 writing a Linux block device storing blocks as emails in the mail
5402 service provided by Google, and thus get heaps of free space. On top
5403 of this one can add encryption, RAID and volume management to have
5404 lots of (fairly slow, I admit that) cheap and encrypted storage. But
5405 I never found time to implement such system. But the last few weeks I
5406 have looked at a system called
5407 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
5408 mounted network backed file system with the features I need.
</p
>
5410 <p
>S3QL is a fuse file system with a local cache and cloud storage,
5411 handling several different storage providers, any with Amazon S3,
5412 Google Drive or OpenStack API. There are heaps of such storage
5413 providers. S3QL can also use a local directory as storage, which
5414 combined with sshfs allow for file storage on any ssh server. S3QL
5415 include support for encryption, compression, de-duplication, snapshots
5416 and immutable file systems, allowing me to mount the remote storage as
5417 a local mount point, look at and use the files as if they were local,
5418 while the content is stored in the cloud as well. This allow me to
5419 have a backup that should survive fire. The file system can not be
5420 shared between several machines at the same time, as only one can
5421 mount it at the time, but any machine with the encryption key and
5422 access to the storage service can mount it if it is unmounted.
</p
>
5424 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
5425 package is included already. So to get started, run
<tt
>apt-get
5426 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
5427 Greenqloud, after reading their nice recipe on
5428 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
5429 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
5430 in Iceland more than those in USA when it come to keeping my personal
5431 data safe and private, and thus would rather spend money on a company
5432 in Iceland. Another nice recipe is available from the article
5433 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
5434 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
5435 Admin magazine. When the provider is picked, figure out how to get
5436 the API key needed to connect to the storage API. With Greencloud,
5437 the key did not show up until I had added payment details to my
5440 <p
>Armed with the API access details, it is time to create the file
5441 system. First, create a new bucket in the cloud. This bucket is the
5442 file system storage area. I picked a bucket name reflecting the
5443 machine that was going to store data there, but any name will do.
5444 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
5445 the API login and password, and a locally created password. Store it
5446 all in ~root/.s3ql/authinfo2 like this:
5448 <p
><blockquote
><pre
>
5450 storage-url: s3c://s.greenqloud.com:
443/bucket-name
5451 backend-login: API-login
5452 backend-password: API-password
5453 fs-passphrase: local-password
5454 </pre
></blockquote
></p
>
5456 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
5457 but any sensible way to create a fairly random password should do it.
5458 Armed with these details, it is now time to run mkfs, entering the API
5459 details and password to create it:
</p
>
5461 <p
><blockquote
><pre
>
5462 # mkdir -m
700 /var/lib/s3ql-cache
5463 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5464 --ssl s3c://s.greenqloud.com:
443/bucket-name
5465 Enter backend login:
5466 Enter backend password:
5467 Before using S3QL, make sure to read the user
's guide, especially
5468 the
'Important Rules to Avoid Loosing Data
' section.
5469 Enter encryption password:
5470 Confirm encryption password:
5471 Generating random encryption key...
5472 Creating metadata tables...
5482 Compressing and uploading metadata...
5483 Wrote
0.00 MB of compressed metadata.
5484 #
</pre
></blockquote
></p
>
5486 <p
>The next step is mounting the file system to make the storage available.
5488 <p
><blockquote
><pre
>
5489 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5490 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
5491 Using
4 upload threads.
5492 Downloading and decompressing metadata...
5502 Mounting filesystem...
5504 Filesystem Size Used Avail Use% Mounted on
5505 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
5507 </pre
></blockquote
></p
>
5509 <p
>The file system is now ready for use. I use rsync to store my
5510 backups in it, and as the metadata used by rsync is downloaded at
5511 mount time, no network traffic (and storage cost) is triggered by
5512 running rsync. To unmount, one should not use the normal umount
5513 command, as this will not flush the cache to the cloud storage, but
5514 instead running the umount.s3ql command like this:
5516 <p
><blockquote
><pre
>
5519 </pre
></blockquote
></p
>
5521 <p
>There is a fsck command available to check the file system and
5522 correct any problems detected. This can be used if the local server
5523 crashes while the file system is mounted, to reset the
"already
5524 mounted
" flag. This is what it look like when processing a working
5525 file system:
</p
>
5527 <p
><blockquote
><pre
>
5528 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
5529 Using cached metadata.
5530 File system seems clean, checking anyway.
5531 Checking DB integrity...
5532 Creating temporary extra indices...
5533 Checking lost+found...
5534 Checking cached objects...
5535 Checking names (refcounts)...
5536 Checking contents (names)...
5537 Checking contents (inodes)...
5538 Checking contents (parent inodes)...
5539 Checking objects (reference counts)...
5540 Checking objects (backend)...
5541 ..processed
5000 objects so far..
5542 ..processed
10000 objects so far..
5543 ..processed
15000 objects so far..
5544 Checking objects (sizes)...
5545 Checking blocks (referenced objects)...
5546 Checking blocks (refcounts)...
5547 Checking inode-block mapping (blocks)...
5548 Checking inode-block mapping (inodes)...
5549 Checking inodes (refcounts)...
5550 Checking inodes (sizes)...
5551 Checking extended attributes (names)...
5552 Checking extended attributes (inodes)...
5553 Checking symlinks (inodes)...
5554 Checking directory reachability...
5555 Checking unix conventions...
5556 Checking referential integrity...
5557 Dropping temporary indices...
5558 Backing up old metadata...
5568 Compressing and uploading metadata...
5569 Wrote
0.89 MB of compressed metadata.
5571 </pre
></blockquote
></p
>
5573 <p
>Thanks to the cache, working on files that fit in the cache is very
5574 quick, about the same speed as local file access. Uploading large
5575 amount of data is to me limited by the bandwidth out of and into my
5576 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
5577 which is very close to my upload speed, and downloading the same
5578 Debian installation ISO gave me
610 kiB/s, close to my download speed.
5579 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
5580 network, not the file system code. I do not know what a good cache
5581 size would be, but suspect that the cache should e larger than your
5582 working set.
</p
>
5584 <p
>I mentioned that only one machine can mount the file system at the
5585 time. If another machine try, it is told that the file system is
5588 <p
><blockquote
><pre
>
5589 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5590 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
5591 Using
8 upload threads.
5592 Backend reports that fs is still mounted elsewhere, aborting.
5594 </pre
></blockquote
></p
>
5596 <p
>The file content is uploaded when the cache is full, while the
5597 metadata is uploaded once every
24 hour by default. To ensure the
5598 file system content is flushed to the cloud, one can either umount the
5599 file system, or ask S3QL to flush the cache and metadata using
5602 <p
><blockquote
><pre
>
5603 # s3qlctrl upload-meta /s3ql
5604 # s3qlctrl flushcache /s3ql
5606 </pre
></blockquote
></p
>
5608 <p
>If you are curious about how much space your data uses in the
5609 cloud, and how much compression and deduplication cut down on the
5610 storage usage, you can use s3qlstat on the mounted file system to get
5613 <p
><blockquote
><pre
>
5615 Directory entries:
9141
5618 Total data size:
22049.38 MB
5619 After de-duplication:
21955.46 MB (
99.57% of total)
5620 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
5621 Database size:
2.39 MB (uncompressed)
5622 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5624 </pre
></blockquote
></p
>
5626 <p
>I mentioned earlier that there are several possible suppliers of
5627 storage. I did not try to locate them all, but am aware of at least
5628 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
5629 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
5630 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
5631 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
5632 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
5633 accept payment in Bitcoin. Pick one that suit your need. Some of
5634 them provide several GiB of free storage, but the prize models are
5635 quite different and you will have to figure out what suits you
5638 <p
>While researching this blog post, I had a look at research papers
5639 and posters discussing the S3QL file system. There are several, which
5640 told me that the file system is getting a critical check by the
5641 science community and increased my confidence in using it. One nice
5643 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
5644 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5645 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
5646 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5647 and Pamela Smith. Please have a look.
</p
>
5649 <p
>Given my problems with different file systems earlier, I decided to
5650 check out the mounted S3QL file system to see if it would be usable as
5651 a home directory (in other word, that it provided POSIX semantics when
5652 it come to locking and umask handling etc). Running
5653 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
5654 test code to check file system semantics
</a
>, I was happy to discover that
5655 no error was found. So the file system can be used for home
5656 directories, if one chooses to do so.
</p
>
5658 <p
>If you do not want a locally file system, and want something that
5659 work without the Linux fuse file system, I would like to mention the
5660 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
5661 provide locally encrypted backup using a command line client. It have
5662 a nicer access control system, where one can split out read and write
5663 access, allowing some systems to write to the backup and others to
5664 only read from it.
</p
>
5666 <p
>As usual, if you use Bitcoin and want to show your support of my
5667 activities, please send Bitcoin donations to my address
5668 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5673 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
5674 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
5675 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
5676 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
5677 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
5678 project
</a
> is working on providing the software and hardware for
5679 making it easy for non-technical people to host their data and
5680 communication at home, and being able to communicate with their
5681 friends and family encrypted and away from prying eyes. It has been
5682 going on for a while, and is slowly progressing towards a new test
5683 release (
0.2).
</p
>
5685 <p
>And what day could be better than the Pi day to announce that the
5686 new version will provide
"hard drive
" / SD card / USB stick images for
5687 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5688 system), and can also be installed using a Debian installer preseed
5689 file. The Debian based Freedombox is now based on Debian Jessie,
5690 where most of the needed packages used are already present. Only one,
5691 the freedombox-setup package, is missing. To try to build your own
5692 boot image to test the current status, fetch the freedom-maker scripts
5694 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
5695 with a user with sudo access to become root:
5698 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5700 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5701 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5703 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5706 <p
>Root access is needed to run debootstrap and mount loopback
5707 devices. See the README for more details on the build. If you do not
5708 want all three images, trim the make line. But note that thanks to
<a
5709 href=
"https://bugs.debian.org/
741407">a race condition in
5710 vmdebootstrap
</a
>, the build might fail without the patch to the
5711 kpartx call.
</p
>
5713 <p
>If you instead want to install using a Debian CD and the preseed
5714 method, boot a Debian Wheezy ISO and use this boot argument to load
5715 the preseed values:
</p
>
5718 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
5721 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
5722 recently introduced bug in apt in Jessie
</a
>, the installer will
5723 currently hang while setting up APT sources. Killing the
5724 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
5725 installation will get the installation going. This affect all
5726 installations in Jessie, and I expect it will be fixed soon.
</p
>
5728 <p
>Give it a go and let us know how it goes on the mailing list, and help
5729 us get the new release published. :) Please join us on
5730 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
5731 irc.debian.org)
</a
> and
5732 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5733 mailing list
</a
> if you want to help make this vision come true.
</p
>
5738 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
5739 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
5740 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
5741 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
5742 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
5743 innetgr tools, because I needed them in
5744 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
5745 ng-utils, and it has served me well. I placed the project under the
5746 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
5747 repository. But many years ago, the CVS repository was dropped (lost,
5748 not migrated to new hardware, not sure), and the project have lacked a
5749 proper home since then.
</p
>
5751 <p
>Last summer, I had a look at the package and made a new release
5752 fixing a irritating crash bug, but was unable to store the changes in
5753 a proper source control system. I applied for a project on
5754 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
5755 to follow up on it. Until today. :)
</p
>
5757 <p
>After many hours of cleaning and migration, the ng-utils project
5758 now have a new home, and a git repository with the highlight of the
5759 history of the project. I published all release tarballs and imported
5760 them into the git repository. As the project is really stable and not
5761 expected to gain new features any time soon, I decided to make a new
5762 release and call it
1.0. Visit the new project home on
5763 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
5764 if you want to check it out. The new version is also uploaded into
5765 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
5770 <title>Testing sysvinit from experimental in Debian Hurd
</title>
5771 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
5772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
5773 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
5774 <description><p
>A few days ago I decided to try to help the Hurd people to get
5775 their changes into sysvinit, to allow them to use the normal sysvinit
5776 boot system instead of their old one. This follow up on the
5777 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
5778 Google Summer of Code work
</a
> done last summer by Justus Winter to
5779 get Debian on Hurd working more like Debian on Linux. To get started,
5780 I downloaded a prebuilt hard disk image from
5781 <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
>,
5782 and started it using virt-manager.
</p
>
5784 <p
>The first think I had to do after logging in (root without any
5785 password) was to get the network operational. I followed
5786 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
5787 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
5788 commands as root to get the machine to accept a IP address from the
5789 kvm internal DHCP server:
</p
>
5791 <p
><blockquote
><pre
>
5792 settrans -fgap /dev/netdde /hurd/netdde
5793 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
5794 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
5796 </pre
></blockquote
></p
>
5798 <p
>After this, the machine had internet connectivity, and I could
5799 upgrade it and install the sysvinit packages from experimental and
5800 enable it as the default boot system in Hurd.
</p
>
5802 <p
>But before I did that, I set a password on the root user, as ssh is
5803 running on the machine it for ssh login to work a password need to be
5804 set. Also, note that a bug somewhere in openssh on Hurd block
5805 compression from working. Remember to turn that off on the client
5808 <p
>Run these commands as root to upgrade and test the new sysvinit
5811 <p
><blockquote
><pre
>
5812 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
5813 deb http://http.debian.net/debian/ experimental main
5816 apt-get dist-upgrade
5817 apt-get install -t experimental initscripts sysv-rc sysvinit \
5818 sysvinit-core sysvinit-utils
5819 update-alternatives --config runsystem
5820 </pre
></blockquote
></p
>
5822 <p
>To reboot after switching boot system, you have to use
5823 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
5824 yet a sysvinit process able to receive the signals from the normal
5825 'reboot
' command. After switching to sysvinit as the boot system,
5826 upgrading every package and rebooting, the network come up with DHCP
5827 after boot as it should, and the settrans/pkill hack mentioned at the
5828 start is no longer needed. But for some strange reason, there are no
5829 longer any login prompt in the virtual console, so I logged in using
5832 <p
>Note that there are some race conditions in Hurd making the boot
5833 fail some times. No idea what the cause is, but hope the Hurd porters
5834 figure it out. At least Justus said on IRC (#debian-hurd on
5835 irc.debian.org) that they are aware of the problem. A way to reduce
5836 the impact is to upgrade to the Hurd packages built by Justus by
5837 adding this repository to the machine:
</p
>
5839 <p
><blockquote
><pre
>
5840 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
5841 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5843 </pre
></blockquote
></p
>
5845 <p
>At the moment the prebuilt virtual machine get some packages from
5846 http://ftp.debian-ports.org/debian, because some of the packages in
5847 unstable do not yet include the required patches that are lingering in
5848 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
5850 <p
><blockquote
><pre
>
5851 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
5852 i emacs - GNU Emacs editor (metapackage)
5853 i gdb - GNU Debugger
5854 i hurd-recommended - Miscellaneous translators
5855 i isc-dhcp-client - ISC DHCP client
5856 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5857 i libc-bin - Embedded GNU C Library: Binaries
5858 i libc-dev-bin - Embedded GNU C Library: Development binaries
5859 i libc0.3 - Embedded GNU C Library: Shared libraries
5860 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5861 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5862 i multiarch-support - Transitional package to ensure multiarch compatibilit
5863 i A x11-common - X Window System (X.Org) infrastructure
5864 i xorg - X.Org X Window System
5865 i A xserver-xorg - X.Org X server
5866 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5868 </pre
></blockquote
></p
>
5870 <p
>All in all, testing hurd has been an interesting experience. :)
5871 X.org did not work out of the box and I never took the time to follow
5872 the porters instructions to fix it. This time I was interested in the
5873 command line stuff.
<p
>
5878 <title>New chrpath release
0.16</title>
5879 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
5880 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
5881 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
5882 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
5883 find problems in C, C++ and Java code using static source code
5884 analysis. It can detect a lot of different problems, and is very
5885 useful to find memory and locking bugs in the error handling part of
5886 the source. The company behind it provide
5887 <a href=
"https://scan.coverity.com/
">check of free software projects as
5888 a community service
</a
>, and many hundred free software projects are
5889 already checked. A few days ago I decided to have a closer look at
5890 the Coverity system, and discovered that the
5891 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
5892 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
5893 projects I am involved with was already registered. But these are
5894 fairly big, and I would also like to have a small and easy project to
5895 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
5896 checking of the chrpath project
</a
>. It was
5897 added to the checker and discovered seven potential defects. Six of
5898 these were real, mostly resource
"leak
" when the program detected an
5899 error. Nothing serious, as the resources would be released a fraction
5900 of a second later when the program exited because of the error, but it
5901 is nice to do it right in case the source of the program some time in
5902 the future end up in a library. Having fixed all defects and added
5903 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
5904 mailing list for the chrpath developers
</a
>, I decided it was time to
5905 publish a new release. These are the release notes:
</p
>
5907 <p
>New in
0.16 released
2014-
01-
14:
</p
>
5911 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
5912 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
5913 <li
>Mention new project mailing list in the documentation.
</li
>
5918 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5919 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
5920 project if something is wrong with the new release. The test suite
5921 did not discover any old errors, so if you find a new one, please also
5922 include a test suite check.
</p
>
5927 <title>New chrpath release
0.15</title>
5928 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
5929 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
5930 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
5931 <description><p
>After many years break from the package and a vain hope that
5932 development would be continued by someone else, I finally pulled my
5933 acts together this morning and wrapped up a new release of chrpath,
5934 the command line tool to modify the rpath and runpath of already
5935 compiled ELF programs. The update was triggered by the persistence of
5936 Isha Vishnoi at IBM, which needed a new config.guess file to get
5937 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
5938 is working on. I checked the
5939 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
5940 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
5941 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
5942 packages for interesting patches (failed to find the source from
5943 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5944 These are the release notes:
</p
>
5946 <p
>New in
0.15 released
2013-
11-
24:
</p
>
5950 <li
>Updated config.sub and config.guess from the GNU project to work
5951 with newer architectures. Thanks to isha vishnoi for the heads
5954 <li
>Updated README with current URLs.
</li
>
5956 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5957 Matthias Klose.
</li
>
5959 <li
>Added missing help for -k|--keepgoing option, using patch by
5960 Petr Machata found in Fedora.
</li
>
5962 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
5963 .dynamic is a NULL terminated string. Based on patch found in
5964 Fedora credited Axel Thimm and Christian Krause.
</li
>
5969 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5970 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
5971 project if something is wrong with the new release. The test suite
5972 did not discover any old errors, so if you find a new one, please also
5973 include a testsuite check.
</p
>
5978 <title>Debian init.d boot script example for rsyslog
</title>
5979 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
5980 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
5981 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
5982 <description><p
>If one of the points of switching to a new init system in Debian is
5983 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
5984 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
5985 init.d scripts at all. Here is an example init.d script, ie a rewrite
5986 of /etc/init.d/rsyslog:
</p
>
5988 <p
><pre
>
5989 #!/lib/init/init-d-script
5992 # Required-Start: $remote_fs $time
5993 # Required-Stop: umountnfs $time
5994 # X-Stop-After: sendsigs
5995 # Default-Start:
2 3 4 5
5996 # Default-Stop:
0 1 6
5997 # Short-Description: enhanced syslogd
5998 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5999 # It is quite compatible to stock sysklogd and can be
6000 # used as a drop-in replacement.
6002 DESC=
"enhanced syslogd
"
6003 DAEMON=/usr/sbin/rsyslogd
6004 </pre
></p
>
6006 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
6007 script was
137 lines, and the above is just
15 lines, most of it meta
6008 info/comments.
</p
>
6010 <p
>How to do this, you ask? Well, one create a new script
6011 /lib/init/init-d-script looking something like this:
6013 <p
><pre
>
6016 # Define LSB log_* functions.
6017 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
6018 # and status_of_proc is working.
6019 . /lib/lsb/init-functions
6022 # Function that starts the daemon/service
6028 #
0 if daemon has been started
6029 #
1 if daemon was already running
6030 #
2 if daemon could not be started
6031 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
6033 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
6036 # Add code here, if necessary, that waits for the process to be ready
6037 # to handle requests from services started subsequently which depend
6038 # on this one. As a last resort, sleep for some time.
6042 # Function that stops the daemon/service
6047 #
0 if daemon has been stopped
6048 #
1 if daemon was already stopped
6049 #
2 if daemon could not be stopped
6050 # other if a failure occurred
6051 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
6052 RETVAL=
"$?
"
6053 [
"$RETVAL
" =
2 ]
&& return
2
6054 # Wait for children to finish too if this is a daemon that forks
6055 # and if the daemon is only ever run from this initscript.
6056 # If the above conditions are not satisfied then add some other code
6057 # that waits for the process to drop all resources that could be
6058 # needed by services started subsequently. A last resort is to
6059 # sleep for some time.
6060 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
6061 [
"$?
" =
2 ]
&& return
2
6062 # Many daemons don
't delete their pidfiles when they exit.
6064 return
"$RETVAL
"
6068 # Function that sends a SIGHUP to the daemon/service
6072 # If the daemon can reload its configuration without
6073 # restarting (for example, when it is sent a SIGHUP),
6074 # then implement that here.
6076 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
6081 scriptbasename=
"$(basename $
1)
"
6082 echo
"SN: $scriptbasename
"
6083 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
6084 script=
"$
1"
6091 NAME=$(basename $DAEMON)
6092 PIDFILE=/var/run/$NAME.pid
6094 # Exit if the package is not installed
6095 #[ -x
"$DAEMON
" ] || exit
0
6097 # Read configuration variable file if it is present
6098 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
6100 # Load the VERBOSE setting and other rcS variables
6103 case
"$
1" in
6105 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
6107 case
"$?
" in
6108 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
6109 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
6113 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
6115 case
"$?
" in
6116 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
6117 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
6121 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
6123 #reload|force-reload)
6125 # If do_reload() is not implemented then leave this commented out
6126 # and leave
'force-reload
' as an alias for
'restart
'.
6128 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
6132 restart|force-reload)
6134 # If the
"reload
" option is implemented then remove the
6135 #
'force-reload
' alias
6137 log_daemon_msg
"Restarting $DESC
" "$NAME
"
6139 case
"$?
" in
6142 case
"$?
" in
6144 1) log_end_msg
1 ;; # Old process is still running
6145 *) log_end_msg
1 ;; # Failed to start
6155 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
6161 </pre
></p
>
6163 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
6164 lot. I did not really polish the approach, so it might not always
6165 work out of the box, but you get the idea. I did not try very hard to
6166 optimize it nor make it more robust either.
</p
>
6168 <p
>A better argument for switching init system in Debian than reducing
6169 the size of init scripts (which is a good thing to do anyway), is to
6170 get boot system that is able to handle the kernel events sensibly and
6171 robustly, and do not depend on the boot to run sequentially. The boot
6172 and the kernel have not behaved sequentially in years.
</p
>
6177 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
6178 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
6179 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
6180 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
6181 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
6182 remote display access is the preferred solution with oVirt and RedHat
6183 Enterprise Virtualization, and I was sad to discover the other day
6184 that the browser plugin needed to use these systems seamlessly was
6185 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
6186 for a package
</a
> was from
2012-
04-
10 with no progress since
6187 2013-
04-
01, so I decided to wrap up a package based on the great work
6188 from Cajus Pollmeier and put it in a collab-maint maintained git
6189 repository to get a package I could use. I would very much like
6190 others to help me maintain the package (or just take over, I do not
6191 mind), but as no-one had volunteered so far, I just uploaded it to
6192 NEW. I hope it will be available in Debian in a few days.
</p
>
6194 <p
>The source is now available from
6195 <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
>
6200 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
6201 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
6202 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
6203 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
6204 <description><p
>The
6205 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
6206 program is a a very nice system to create virtual machine images. It
6207 create a image file, add a partition table, mount it and run
6208 debootstrap in the mounted directory to create a Debian system on a
6209 stick. Yesterday, I decided to try to teach it how to make images for
6210 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
6211 of a plan to simplify the build system for
6212 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
6213 project
</a
>. The FreedomBox project already uses vmdebootstrap for
6214 the virtualbox images, but its current build system made multistrap
6215 based system for Dreamplug images, and it is lacking support for
6216 Raspberry Pi.
</p
>
6218 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
6219 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
6220 code and adjusted it to be able to build armel images on my amd64
6221 Debian laptop. I ended up giving vmdebootstrap five new options,
6222 allowing me to replicate the image creation process I use to make
6223 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
6224 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
6225 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
6226 call debootstrap with --foreign and to copy the handler into the
6227 generated chroot before running the second stage. This allow
6228 vmdebootstrap to create armel images on an amd64 host. Next I added
6229 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
6230 fstype
</tt
> to teach it to create a separate /boot/ partition with the
6231 given file system type, allowing me to create an image with a vfat
6232 partition for the /boot/ stuff. I also added a
<tt
>--variant
6233 variant
</tt
> option to allow me to create smaller images without the
6234 Debian base system packages installed. Finally, I added an option
6235 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
6236 as a boot loader. It is not needed on the Raspberry Pi and probably
6237 most other non-x86 architectures. The changes were accepted by the
6238 upstream author of vmdebootstrap yesterday and today, and is now
6240 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
6241 upstream project page
</a
>.
</p
>
6243 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
6244 create a small script (the customize script) to add the non-free
6245 binary blob needed to boot the Raspberry Pi and the APT source
6248 <p
><pre
>
6250 set -e # Exit on first error
6251 rootdir=
"$
1"
6252 cd
"$rootdir
"
6253 cat
&lt;
&lt;EOF
> etc/apt/sources.list
6254 deb http://http.debian.net/debian/ jessie main contrib non-free
6256 # Install non-free binary blob needed to boot Raspberry Pi. This
6257 # install a kernel somewhere too.
6258 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
6259 -O $rootdir/usr/bin/rpi-update
6260 chmod a+x $rootdir/usr/bin/rpi-update
6261 mkdir -p $rootdir/lib/modules
6262 touch $rootdir/boot/start.elf
6263 chroot $rootdir rpi-update
6264 </pre
></p
>
6266 <p
>Next, fetch the latest vmdebootstrap script and call it like this
6267 to build the image:
</p
>
6270 sudo ./vmdebootstrap \
6273 --distribution jessie \
6274 --mirror http://http.debian.net/debian \
6283 --root-password raspberry \
6284 --hostname raspberrypi \
6285 --foreign /usr/bin/qemu-arm-static \
6286 --customize `pwd`/customize \
6288 --package git-core \
6289 --package binutils \
6290 --package ca-certificates \
6293 </pre
></p
>
6295 <p
>The list of packages being installed are the ones needed by
6296 rpi-update to make the image bootable on the Raspberry Pi, with the
6297 exception of netbase, which is needed by debootstrap to find
6298 /etc/hosts with the minbase variant. I really wish there was a way to
6299 set up an Raspberry Pi using only packages in the Debian archive, but
6300 that is not possible as far as I know, because it boots from the GPU
6301 using a non-free binary blob.
</p
>
6303 <p
>The build host need debootstrap, kpartx and qemu-user-static and
6304 probably a few others installed. I have not checked the complete
6305 build dependency list.
</p
>
6307 <p
>The resulting image will not use the hardware floating point unit
6308 on the Raspberry PI, because the armel architecture in Debian is not
6309 optimized for that use. So the images created will be a bit slower
6310 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
6315 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
6316 <link>http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</link>
6317 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</guid>
6318 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
6319 <description><p
>The last few days I came across a few good causes that should get
6320 wider attention. I recommend signing and donating to each one of
6323 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
6324 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
6325 Women program which is a Google Summer of Code like initiative to get
6326 more women involved in free software. One debian sponsor has offered
6327 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
6328 earmarked
</a
> for this initiative. I donated a few minutes ago, and
6329 hope you will to. :)
</p
>
6331 <p
>And the Electronic Frontier Foundation just announced plans to
6332 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
6333 documentaries about the excessive spying
</a
> on every Internet user that
6334 take place these days, and their need to fund the work. I
've already
6335 donated. Are you next?
</p
>
6337 <p
>For my Norwegian audience, the organisation Studentenes og
6338 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
6339 statement under the heading
6340 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
6341 Access
</a
> for those of us asking for more focus on open access in the
6342 Norwegian government. So far
499 signatures. I hope you will sign it
6348 <title>Videos about the Freedombox project - for inspiration and learning
</title>
6349 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
6350 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
6351 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
6352 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
6353 project
</a
> have been going on for a while, and have presented the
6354 vision, ideas and solution several places. Here is a little
6355 collection of videos of talks and presentation of the project.
</p
>
6359 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
6360 2,
5 minute marketing film
</a
> (Youtube)
</li
>
6362 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
6363 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
6365 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
6366 Freedom in the Cloud - Software Freedom, Privacy and and Security for
6367 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
6368 (Youtube)
</li
>
6370 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
6371 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
6373 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
6374 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
6376 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
6377 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
6378 York City in
2012</a
> (Youtube)
</li
>
6380 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
6381 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
6382 (Youtube)
</li
>
6384 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
6385 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
6387 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
6388 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
6390 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
6391 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
6392 2013</a
> (Youtube)
</li
>
6396 <p
>A larger list is available from
6397 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
6398 Freedombox Wiki
</a
>.
</p
>
6400 <p
>On other news, I am happy to report that Freedombox based on Debian
6401 Jessie is coming along quite well, and soon both Owncloud and using
6402 Tor should be available for testers of the Freedombox solution. :) In
6403 a few weeks I hope everything needed to test it is included in Debian.
6404 The withsqlite package is already in Debian, and the plinth package is
6405 pending in NEW. The third and vital part of that puzzle is the
6406 metapackage/setup framework, which is still pending an upload. Join
6407 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
6408 (#freedombox on irc.debian.org)
</a
> and
6409 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6410 mailing list
</a
> if you want to help make this vision come true.
</p
>
6415 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
6416 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
6417 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
6418 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
6419 <description><p
>I was introduced to the
6420 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
6421 in
2010, when Eben Moglen presented his vision about serving the need
6422 of non-technical people to keep their personal information private and
6423 within the legal protection of their own homes. The idea is to give
6424 people back the power over their network and machines, and return
6425 Internet back to its intended peer-to-peer architecture. Instead of
6426 depending on a central service, the Freedombox will give everyone
6427 control over their own basic infrastructure.
</p
>
6429 <p
>I
've intended to join the effort since then, but other tasks have
6430 taken priority. But this summers nasty news about the misuse of trust
6431 and privilege exercised by the
"western
" intelligence gathering
6432 communities increased my eagerness to contribute to a point where I
6433 actually started working on the project a while back.
</p
>
6435 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
6436 Debian initiative
</a
> based on the vision from Eben Moglen, is to
6437 create a simple and cheap Debian based appliance that anyone can hook
6438 up in their home and get access to secure and private services and
6439 communication. The initial deployment platform have been the
6440 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
6441 which is a piece of hardware I do not own. So to be able to test what
6442 the current Freedombox setup look like, I had to come up with a way to install
6443 it on some hardware I do have access to. I have rewritten the
6444 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
6445 image build framework to use .deb packages instead of only copying
6446 setup into the boot images, and thanks to this rewrite I am able to
6447 set up any machine supported by Debian Wheezy as a Freedombox, using
6448 the previously mentioned deb (and a few support debs for packages
6449 missing in Debian).
</p
>
6451 <p
>The current Freedombox setup consist of a set of bootstrapping
6453 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
6454 and a administrative web interface
6455 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
6456 withsqlite), as well as a privacy enhancing proxy based on
6457 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
6458 (freedombox-privoxy). There is also a web/javascript based XMPP
6459 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
6460 trying (unsuccessfully so far) to talk to the XMPP server
6461 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
6462 web interface is pluggable, and the goal is to use it to enable OpenID
6463 services, mesh network connectivity, use of TOR, etc, etc. Not much of
6464 this is really working yet, see
6465 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
6466 project TODO
</a
> for links to GIT repositories. Most of the code is
6467 on github at the moment. The HTTP proxy is operational out of the
6468 box, and the admin web interface can be used to add/remove plinth
6469 users. I
've not been able to do anything else with it so far, but
6470 know there are several branches spread around github and other places
6471 with lots of half baked features.
</p
>
6473 <p
>Anyway, if you want to have a look at the current state, the
6474 following recipes should work to give you a test machine to poke
6477 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
6481 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
6482 <li
>Boot from it, either as CD or USB stick.
</li
>
6483 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
6484 to the Debian installer:
<p
>
6485 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
6487 <li
>Answer the few language/region/password questions and pick disk to
6488 install on.
</li
>
6490 <li
>When the installation is finished and the machine have rebooted a
6491 few times, your Freedombox is ready for testing.
</li
>
6495 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
6499 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
6500 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
6501 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
6503 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
6504 </pre
></li
>
6505 <li
><p
>Run this as root:
</p
>
6507 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
6510 apt-get install freedombox-setup
6511 /usr/lib/freedombox/setup
6512 </pre
></li
>
6513 <li
>Reboot into your freshly created Freedombox.
</li
>
6517 <p
>You can test it on other architectures too, but because the
6518 freedombox-privoxy package is binary, it will only work as intended on
6519 the architectures where I have had time to build the binary and put it
6520 in my APT repository. But do not let this stop you. It is only a
6521 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
6523 <p
>Note that by default Freedombox is a DHCP server on the
6524 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
6525 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
6526 disable
</tt
>" as root.
</p
>
6528 <p
>Please let me know if this works for you, or if you have any
6529 problems. We gather on the IRC channel
6530 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
6531 irc.debian.org and the
6532 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
6533 mailing list
</a
>.
</p
>
6535 <p
>Once you get your freedombox operational, you can visit
6536 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
6537 welcome screen (dead end - do not be surprised if you are unable to
6538 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
6539 to look at the rest of plinth. The default user is
'admin
' and the
6540 default password is
'secret
'.
</p
>
6545 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
6546 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
6547 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
6548 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
6549 <description><p
>Earlier, I reported about
6550 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
6551 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
6552 told by IBM that the original disk should be thrown away. And as
6553 there no longer was a problem if I bricked the firmware, I decided
6554 today to try to install Intel firmware to replace the Lenovo firmware
6555 currently on the disk.
</p
>
6557 <p
>I searched the Intel site for firmware, and found
6558 <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
>
6559 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6560 according to the site should contain the latest firmware for SSD
6561 disks. I inserted the broken disk in one of my spare laptops and
6562 booted the ISO from a USB stick. The disk was recognized, but the
6563 program claimed the newest firmware already were installed and refused
6564 to insert any Intel firmware. So no change, and the disk is still
6565 unable to handle write load. :( I guess the only way to get them
6566 working would be if Lenovo releases new firmware. No idea how likely
6567 that is. Anyway, just blogging about this test for completeness. I
6568 got a working Samsung disk, and see no point in spending more time on
6569 the broken disks.
</p
>
6574 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
6575 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
6576 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
6577 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
6578 <description><p
>Today I switched to
6579 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
6580 new laptop
</a
>. I
've previously written about the problems I had with
6581 my new Thinkpad X230, which was delivered with an
6582 <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
6583 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
6584 sustained writes. My hardware supplier have been very forthcoming in
6585 trying to find a solution, and after first trying with another
6586 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
6587 disk instead to fix it once and for all. The Samsung disk survived
6588 the installation of Debian with encrypted disks (filling the disk with
6589 random data during installation killed the first two), and I thus
6590 decided to trust it with my data. I have installed it as a Debian Edu
6591 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6592 server at home using Kerberos and LDAP, and will use it as my work
6593 station from now on.
</p
>
6595 <p
>As this is a solid state disk with no moving parts, I believe the
6596 Debian Wheezy default installation need to be tuned a bit to increase
6597 performance and increase life time of the disk. The Linux kernel and
6598 user space applications do not yet adjust automatically to such
6599 environment. To make it easier for my self, I created a draft Debian
6600 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
6601 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
6602 for the ssd-setup package
</a
> is available from collab-maint, and it
6603 is set up to adjust the setup of the machine by just installing the
6604 package. If there is any non-SSD disk in the machine, the package
6605 will refuse to install, as I did not try to write any logic to sort
6606 file systems in SSD and non-SSD file systems.
</p
>
6608 <p
>I consider the package a draft, as I am a bit unsure how to best
6609 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6610 where I set up the machine with one large encrypted partition (in
6611 addition to /boot), put LVM on top of this and set up partitions on
6612 top of this again. See the README file in the package source for the
6613 references I used to pick the settings. At the moment these
6614 parameters are tuned:
</p
>
6618 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
6619 (adding discard to /etc/crypttab)
</li
>
6621 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
6622 this case a cryptsetup partition) by changing issue_discards from
6623 0 to
1 in /etc/lvm/lvm.conf.
</li
>
6625 <li
>Set relatime as a file system option for ext3 and ext4 file
6628 <li
>Tell swap to use TRIM commands by adding
'discard
' to
6629 /etc/fstab.
</li
>
6631 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
6633 <li
>Run fstrim on every ext3 and ext4 file system every night (from
6634 cron.daily).
</li
>
6636 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
6637 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
6641 <p
>During installation, I cancelled the part where the installer fill
6642 the disk with random data, as this would kill the SSD performance for
6643 little gain. My goal with the encrypted file system is to ensure
6644 those stealing my laptop end up with a brick and not a working
6645 computer. I have no hope in keeping the really resourceful people
6646 from getting the data on the disk (see
6647 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
6648 Thus I concluded that adding the discard option to crypttab is the
6649 right thing to do.
</p
>
6651 <p
>I considered using the noop I/O scheduler, as several recommended
6652 it for SSD, but others recommended deadline and a benchmark I found
6653 indicated that deadline might be better for interactive use.
</p
>
6655 <p
>I also considered using the
'discard
' file system option for ext3
6656 and ext4, but read that it would give a performance hit ever time a
6657 file is removed, and thought it best to that that slowdown once a day
6658 instead of during my work.
</p
>
6660 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6661 this is already done by Debian Edu.
</p
>
6663 <p
>I have not yet started on the user space tuning. I expect
6664 iceweasel need some tuning, and perhaps other applications too, but
6665 have not yet had time to investigate those parts.
</p
>
6667 <p
>The package should work on Ubuntu too, but I have not yet tested it
6670 <p
>As for the answer to the question in the title of this blog post,
6671 as far as I know, the only solution I know about is to replace the
6672 disk. It might be possible to flash it with Intel firmware instead of
6673 the Lenovo firmware. But I have not tried and did not want to do so
6674 without approval from Lenovo as I wanted to keep the warranty on the
6675 disk until a solution was found and they wanted the broken disks
6681 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
6682 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
6683 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</guid>
6684 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
6685 <description><p
>A few days ago, I wrote about
6686 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
6687 problems I experienced with my new X230 and its SSD disk
</a
>, which
6688 was dying during installation because it is unable to cope with
6689 sustained write. My supplier is in contact with
6690 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
6691 replacement disk to try to fix the problem. They decided to send an
6692 identical model, so my hopes for a permanent fix was slim.
</p
>
6694 <p
>Anyway, today I got the replacement disk and tried to install
6695 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6696 same firmware version as the original. This time my hope raised
6697 slightly as the installation progressed, as the original disk used to
6698 die after
4-
7% of the disk was written to, while this time it kept
6699 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
6700 died again and I was back on square one. I still do not have a new
6701 laptop with a disk I can trust. I can not live with a disk that might
6702 lock up when I download a new
6703 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
6704 other large files. I look forward to hearing from my supplier with
6705 the next proposal from Lenovo.
</p
>
6707 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
6708 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6709 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
6710 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
6711 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6712 P/N
45N8295, P0C38732.
</p
>
6714 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
6715 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
6716 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
6717 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
6718 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6719 P/N
45N8295, P0C38732.
</p
>
6721 <p
>The only difference is in the first number (serial number?), ISN,
6722 SA, date and WNPP values. Mentioning all the details here in case
6723 someone is able to use the information to find a way to identify the
6724 failing disk among working ones (if any such working disk actually
6730 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
6731 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
6732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
6733 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
6734 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
6735 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6736 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
6737 member assosiation NUUG
</a
> and
6738 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
6739 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
6740 Bitraf
</a
>.
</p
>
6742 <p
>It starts
10:
00 and continue until late evening. Everyone is
6743 welcome, and there is no fee to participate. There is on the other
6744 hand limited space, and only room for
30 people. Please put your name
6745 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
6746 wiki page
</a
> if you plan to join us.
</p
>
6751 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
6752 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
6753 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
6754 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
6755 <description><p
>Half a year ago, I reported that I had to find a
6756 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
6757 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
6758 time to spend on it, and it took a while to find a model I believe
6759 will do the job, but two days ago the replacement finally arrived. I
6761 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
6762 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6763 a roaming workstation, and it seemed to work flawlessly. But my
6764 second installation with encrypted disk was not as successful. More
6765 on that below.
</p
>
6767 <p
>I had a hard time trying to track down a good laptop, as my most
6768 important requirements (robust and with a good keyboard) are never
6769 listed in the feature list. But I did get good help from the search
6770 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6771 allowed me to limit the list of interesting laptops based on my other
6772 requirements. A bit surprising that SSD disk are not disks according
6773 to that search interface, so I had to drop specifying the number of
6774 disks from my search parameters. I also asked around among friends to
6775 get their impression on keyboards and robustness.
</p
>
6777 <p
>So the new laptop arrived, and it is quite a lot wider than the
6778 X41. I am not quite convinced about the keyboard, as it is
6779 significantly wider than my old keyboard, and I have to stretch my
6780 hand a lot more to reach the edges. But the key response is fairly
6781 good and the individual key shape is fairly easy to handle, so I hope
6782 I will get used to it. My old X40 was starting to fail, and I really
6783 needed a new laptop now. :)
</p
>
6785 <p
>Turning off the touch pad was simple. All it took was a quick
6786 visit to the BIOS during boot it disable it.
</p
>
6788 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
6789 lock up during load. And this happen when installing Debian Wheezy
6790 with encrypted disk, while the disk is being filled with random data.
6791 I also tested to install Ubuntu Raring, and it happen there too if I
6792 reenable the code to fill the disk with random data (it is disabled by
6793 default in Ubuntu). And the bug with is already known. It was
6794 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
6795 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
6796 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6797 kernel developers as
6798 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
6799 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
6800 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6801 Lenovo forums, both for
6802 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
6803 2012-
11-
10</a
> and for
6804 <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
6805 03-
20-
2013</a
>. The problem do not only affect installation. The
6806 reports state that the disk lock up during use if many writes are done
6807 on the disk, so it is much no use to work around the installation
6808 problem and end up with a computer that can lock up at any moment.
6810 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
6811 available
</a
> that will lock up the hard drive after running a few
6812 minutes by writing to a file.
</p
>
6814 <p
>I
've contacted my supplier and asked how to handle this, and after
6815 contacting PCHELP Norway (request
01D1FDP) which handle support
6816 requests for Lenovo, his first suggestion was to upgrade the disk
6817 firmware. Unfortunately there is no newer firmware available from
6818 Lenovo, as my disk already have the most recent one (version LF1i). I
6819 hope to hear more from him today and hope the problem can be
6825 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
6826 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
6827 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
6828 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
6829 <description><p
>Half a year ago, I reported that I had to find a replacement for my
6830 trusty old Thinkpad X41. Unfortunately I did not have much time to
6831 spend on it, but today the replacement finally arrived. I ended up
6832 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
6833 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
6834 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6835 this, it is installing what I hope will be a more final installation,
6836 with a encrypted hard drive to ensure any dope head stealing it end up
6837 with an expencive door stop.
</p
>
6839 <p
>I had a hard time trying to track down a good laptop, as my most
6840 important requirements (robust and with a good keyboard) are never
6841 listed in the feature list. But I did get good help from the search
6842 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6843 allowed me to limit the list of interesting laptops based on my other
6844 requirements. A bit surprising that SSD disk are not disks, so I had
6845 to drop number of disks from my search parameters.
</p
>
6847 <p
>I am not quite convinced about the keyboard, as it is significantly
6848 wider than my old keyboard, and I have to stretch my hand a lot more
6849 to reach the edges. But the key response is fairly good and the
6850 individual key shape is fairly easy to handle, so I hope I will get
6851 used to it. My old X40 was starting to fail, and I really needed a
6852 new laptop now. :)
</p
>
6854 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
6859 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
6860 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
6861 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
6862 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
6863 <description><p
>It annoys me when the computer fail to do automatically what it is
6864 perfectly capable of, and I have to do it manually to get things
6865 working. One such task is to find out what firmware packages are
6866 needed to get the hardware on my computer working. Most often this
6867 affect the wifi card, but some times it even affect the RAID
6868 controller or the ethernet card. Today I pushed version
0.4 of the
6869 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
6870 including a new script isenkram-autoinstall-firmware handling the
6871 process of asking all the loaded kernel modules what firmware files
6872 they want, find debian packages providing these files and install the
6873 debian packages. Here is a test run on my laptop:
</p
>
6875 <p
><pre
>
6876 # isenkram-autoinstall-firmware
6877 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6878 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6879 info: locating packages with the requested firmware files
6880 info: Updating APT sources after adding non-free APT source
6881 info: trying to install firmware-ipw2x00
6884 Preconfiguring packages ...
6885 Selecting previously deselected package firmware-ipw2x00.
6886 (Reading database ...
259727 files and directories currently installed.)
6887 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6888 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
6890 </pre
></p
>
6892 <p
>When all the requested firmware is present, a simple message is
6893 printed instead:
</p
>
6895 <p
><pre
>
6896 # isenkram-autoinstall-firmware
6897 info: did not find any firmware files requested by loaded kernel modules. exiting
6899 </pre
></p
>
6901 <p
>It could use some polish, but it is already working well and saving
6902 me some time when setting up new machines. :)
</p
>
6904 <p
>So, how does it work? It look at the set of currently loaded
6905 kernel modules, and look up each one of them using modinfo, to find
6906 the firmware files listed in the module meta-information. Next, it
6907 download the Contents file from a nearby APT mirror, and search for
6908 the firmware files in this file to locate the package with the
6909 requested firmware file. If the package is in the non-free section, a
6910 non-free APT source is added and the package is installed using
6911 <tt
>apt-get install
</tt
>. The end result is a slightly better working
6914 <p
>I hope someone find time to implement a more polished version of
6915 this script as part of the hw-detect debian-installer module, to
6916 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
6917 #
655507</a
>. There really is no need to insert USB sticks with
6918 firmware during a PXE install when the packages already are available
6919 from the nearby Debian mirror.
</p
>
6924 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
6925 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
6926 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
6927 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
6928 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6929 the screen just turn black when Linux boot, either during installation
6930 or on first boot from the hard disk. I
've seen it once in a while the
6931 last few years, but only recently understood the cause. I
've seen it
6932 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6933 The reason seem to be in the wiring of some laptops. The system to
6934 control the screen background light is inverted, so when Linux try to
6935 turn the brightness fully on, it end up turning it off instead. I do
6936 not know which Linux drivers are affected, but this post is about the
6937 i915 driver used by the
6938 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6939 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
6941 <p
>The problem can be worked around two ways. Either by adding
6942 i915.invert_brightness=
1 as a kernel option, or by adding a file in
6943 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
6944 option when it load the i915 kernel module. On Debian and Ubuntu, it
6945 can be done by running these commands as root:
</p
>
6948 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
6949 update-initramfs -u -k all
6952 <p
>Since March
2012 there is
6953 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
6954 mechanism in the Linux kernel
</a
> to tell the i915 driver which
6955 hardware have this problem, and get the driver to invert the
6956 brightness setting automatically. To use it, one need to add a row in
6957 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
6958 intel_quirks array
</a
> in the driver source
6959 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
6960 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
6961 number (vendor number
8086 is assumed) and subdevice vendor and device
6964 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
6965 -vvnn
</tt
> for the video card in question:
</p
>
6967 <p
><pre
>
6968 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
6969 3rd Gen Core processor Graphics Controller [
8086:
0156] \
6970 (rev
09) (prog-if
00 [VGA controller])
6971 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
6972 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6973 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6974 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
6975 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
6977 Interrupt: pin A routed to IRQ
42
6978 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
6979 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
6980 Region
4: I/O ports at
4000 [size=
64]
6981 Expansion ROM at
<unassigned
> [disabled]
6982 Capabilities:
<access denied
>
6983 Kernel driver in use: i915
6984 </pre
></p
>
6986 <p
>The resulting intel_quirks entry would then look like this:
</p
>
6988 <p
><pre
>
6989 struct intel_quirk intel_quirks[] = {
6991 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6992 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
6995 </pre
></p
>
6997 <p
>According to the kernel module instructions (as seen using
6998 <tt
>modinfo i915
</tt
>), information about hardware needing the
6999 invert_brightness flag should be sent to the
7000 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
7001 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
7002 developers. But my email about the laptop sent
2013-
06-
03 have not
7004 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
7005 web archive for the mailing list
</a
>, so I suspect they do not accept
7006 emails from non-subscribers. Because of this, I sent my patch also to
7007 the Debian bug tracking system instead as
7008 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
7009 sure the patch is not lost.
</p
>
7011 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
7012 with this problem working properly with Linux. If you use Gnome, your
7013 worries should be over at this point. But if you use KDE, there is
7014 something in KDE ignoring the invert_brightness setting and turning on
7015 the screen during login. I
've reported it to Debian as
7016 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
7017 have no idea yet how to figure out exactly what subsystem is doing
7018 this. Perhaps you can help? Perhaps you know what the Gnome
7019 developers did to handle this, and this can give a clue to the KDE
7020 developers? Or you know where in KDE the screen brightness is changed
7021 during login? If so, please update the BTS report (or get in touch if
7022 you do not know how to update BTS).
</p
>
7024 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
7025 acpi_backlight=vendor, to disable ACPI backlight support completely,
7026 as the ACPI information on the machine is trash and it is better to
7027 leave it to the intel video driver to control the screen
7028 backlight.
</p
>
7033 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
7034 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
7035 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</guid>
7036 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
7037 <description><p
>Two days ago, I asked
7038 <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
7039 I could install Linux on a Packard Bell EasyNote LV computer
7040 preinstalled with Windows
8</a
>. I found a solution, but am horrified
7041 with the obstacles put in the way of Linux users on a laptop with UEFI
7042 and Windows
8.
</p
>
7044 <p
>I never found out if the cause of my problems were the use of UEFI
7045 secure booting or fast boot. I suspect fast boot was the problem,
7046 causing the firmware to boot directly from HD without considering any
7047 key presses and alternative devices, but do not know UEFI settings
7048 enough to tell.
</p
>
7050 <p
>There is no way to install Linux on the machine in question without
7051 opening the box and disconnecting the hard drive! This is as far as I
7052 can tell, the only way to get access to the firmware setup menu
7053 without accepting the Windows
8 license agreement. I am told (and
7054 found description on how to) that it is possible to configure the
7055 firmware setup once booted into Windows
8. But as I believe the terms
7056 of that agreement are completely unacceptable, accepting the license
7057 was never an alternative. I do not enter agreements I do not intend
7058 to follow.
</p
>
7060 <p
>I feared I had to return the laptops and ask for a refund, and
7061 waste many hours on this, but luckily there was a way to get it to
7062 work. But I would not recommend it to anyone planning to run Linux on
7063 it, and I have become sceptical to Windows
8 certified laptops. Is
7064 this the way Linux will be forced out of the market place, by making
7065 it close to impossible for
"normal
" users to install Linux without
7066 accepting the Microsoft Windows license terms? Or at least not
7067 without risking to loose the warranty?
</p
>
7069 <p
>I
've updated the
7070 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
7071 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
7072 do not have to struggle as much as I did to get Linux into the
7075 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
7076 Michael Tokarev and others for feedback and ideas.
</p
>
7081 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
7082 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
7083 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</guid>
7084 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
7085 <description><p
>I
've run into quite a problem the last few days. I bought three
7086 new laptops for my parents and a few others. I bought Packard Bell
7087 Easynote LV to run Kubuntu on and use as their home computer. But I
7088 am completely unable to figure out how to install Linux on it. The
7089 computer is preinstalled with Windows
8, and I suspect it uses UEFI
7090 instead of a BIOS to boot.
</p
>
7092 <p
>The problem is that I am unable to get it to PXE boot, and unable
7093 to get it to boot the Linux installer from my USB stick. I have yet
7094 to try the DVD install, and still hope it will work. when I turn on
7095 the computer, there is no information on what buttons to press to get
7096 the normal boot menu. I expect to get some boot menu to select PXE or
7097 USB stick booting. When booting, it first ask for the language to
7098 use, then for some regional settings, and finally if I will accept the
7099 Windows
8 terms of use. As these terms are completely unacceptable to
7100 me, I have no other choice but to turn off the computer and try again
7101 to get it to boot the Linux installer.
</p
>
7103 <p
>I have gathered my findings so far on a Linlap page about the
7104 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
7105 EasyNote LV
</a
> model. If you have any idea how to get Linux
7106 installed on this machine, please get in touch or update that wiki
7107 page. If I can
't find a way to install Linux, I will have to return
7108 the laptop to the seller and find another machine for my parents.
</p
>
7110 <p
>I wonder, is this the way Linux will be forced out of the market
7111 using UEFI and
"secure boot
" by making it impossible to install Linux
7112 on new Laptops?
</p
>
7117 <title>How to transform a Debian based system to a Debian Edu installation
</title>
7118 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
7119 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
7120 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
7121 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
7122 an operating system based on Debian intended for use in schools. It
7123 contain a turn-key solution for the computer network provided to
7124 pupils in the primary schools. It provide both the central server,
7125 network boot servers and desktop environments with heaps of
7126 educational software. The project was founded almost
12 years ago,
7127 2001-
07-
02. If you want to support the project, which is in need for
7128 cash to fund developer gatherings and other project related activity,
7129 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
7130 donate some money
</a
>.
7132 <p
>A topic that come up again and again on the Debian Edu mailing
7133 lists and elsewhere, is the question on how to transform a Debian or
7134 Ubuntu installation into a Debian Edu installation. It isn
't very
7135 hard, and last week I wrote a script to replicate the steps done by
7136 the Debian Edu installer.
</p
>
7138 <p
>The script,
7139 <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/
>
7140 in the debian-edu-config package, will go through these six steps and
7141 transform an existing Debian Wheezy or Ubuntu (untested) installation
7142 into a Debian Edu Workstation:
</p
>
7146 <li
>Add skolelinux related APT sources.
</li
>
7147 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
7148 <li
>Install debian-edu-install to load preseeding values and pull in
7149 our configuration.
</li
>
7150 <li
>Preseed debconf database with profile setup in
7151 /etc/debian-edu/config, and run tasksel to install packages
7152 according to the profile specified in the config above,
7153 overriding some of the Debian automation machinery.
</li
>
7154 <li
>Run debian-edu-cfengine-D installation to configure everything
7155 that could not be done using preseeding.
</li
>
7156 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
7160 <p
>There are some steps in the Debian Edu installation that can not be
7161 replicated like this. Disk partitioning and LVM setup, for example.
7162 So this script just assume there is enough disk space to install all
7163 the needed packages.
</p
>
7165 <p
>The script was created to help a Debian Edu student working on
7166 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
7167 Debian Edu client, and using it he can take the existing
7168 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
7169 transform it into a fully functioning Debian Edu Workstation (or
7170 Roaming Workstation, or whatever :).
</p
>
7172 <p
>The default setting in the script is to create a KDE Workstation.
7173 If a LXDE based Roaming workstation is wanted instead, modify the
7174 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
7176 <p
><pre
>
7177 PROFILE=
"Roaming-Workstation
"
7178 DESKTOP=
"lxde
"
7179 </pre
></p
>
7181 <p
>The script could even become useful to set up Debian Edu servers in
7182 the cloud, by starting with a virtual Debian installation at some
7183 virtual hosting service and setting up all the services on first
7189 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
7190 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
7191 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
7192 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
7193 <description><P
>In January,
7194 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
7195 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
7196 channel #debian-lego
</a
>, for those of us in the Debian and Linux
7197 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
7198 marvellous construction system from Denmark. We also created
7199 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
7200 a place to take notes and write down our plans and hopes. And several
7201 people showed up to help. I was very happy to see the effect of my
7202 call. Since the small start, we have a debtags tag
7203 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
7204 tag for LEGO related packages, and now count
10 packages related to
7205 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
7207 <p
><table
>
7208 <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
>
7209 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
7210 <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
>
7211 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
7212 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
7213 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
7214 <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
>
7215 <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
>
7216 <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
>
7217 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
7218 </table
></p
>
7220 <p
>Some of these are available in Wheezy, and all but one are
7221 currently available in Jessie/testing. leocad is so far only
7222 available in experimental.
</p
>
7224 <p
>If you care about LEGO in Debian, please join us on IRC and help
7225 adding the rest of the great free software tools available on Linux
7226 for LEGO designers.
</p
>
7231 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
7232 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
7233 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
7234 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
7235 <description><p
>When I woke up this morning, I was very happy to see that the
7236 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
7237 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
7238 Debian release, and I expect to move my machines at home over to it fairly
7241 <p
>The new debian release contain heaps of new stuff, and one program
7242 in particular make me very happy to see included. The
7243 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
7244 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
7245 included for the first time. Alongside similar programs like
7246 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
7247 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
7248 it allow for visual programming where syntax errors can not happen,
7249 and a friendly programming environment for learning to control the
7250 computer. Scratch will also be included in the next release of Debian
7253 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
7254 Edu/Skolelinux release too. The
7255 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
7256 alpha release
</a
> went out last week, and the next should soon
7262 <title>Isenkram
0.2 finally in the Debian archive
</title>
7263 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
7264 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
7265 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
7266 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
7267 package
</a
> finally made it into the archive, after lingering in NEW
7268 for many months. I uploaded it to the Debian experimental suite
7269 2013-
01-
27, and today it was accepted into the archive.
</p
>
7271 <p
>Isenkram is a system for suggesting to users what packages to
7272 install to work with a pluggable hardware device. The suggestion pop
7273 up when the device is plugged in. For example if a Lego Mindstorm NXT
7274 is inserted, it will suggest to install the program needed to program
7275 the NXT controller. Give it a go, and report bugs and suggestions to
7281 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
7282 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
7283 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
7284 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
7285 <description><p
>My
7286 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
7287 bitcoin related blog post
</a
> mentioned that the new
7288 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
7289 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
7290 2013-
01-
19, and have been available in unstable since then. It was
7291 automatically copied to Ubuntu, and is available in their Raring
7292 version too.
</p
>
7294 <p
>But there is a strange problem with the build that block this new
7295 version from being available on the i386 and kfreebsd-i386
7296 architectures. For some strange reason, the autobuilders in Debian
7297 for these architectures fail to run the test suite on these
7298 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
7299 We are so far unable to reproduce it when building it manually, and
7300 no-one have been able to propose a fix. If you got an idea what is
7301 failing, please let us know via the BTS.
</p
>
7303 <p
>One feature that is annoying me with of the bitcoin client, because
7304 I often run low on disk space, is the fact that the client will exit
7305 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
7306 #
696715</a
>). So make sure you have enough disk space when you run
7309 <p
>As usual, if you use bitcoin and want to show your support of my
7310 activities, please send Bitcoin donations to my address
7311 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7316 <title>Welcome to the world, Isenkram!
</title>
7317 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
7318 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
7319 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
7320 <description><p
>Yesterday, I
7321 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
7322 for testers
</a
> for my prototype for making Debian better at handling
7323 pluggable hardware devices, which I
7324 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
7325 out to create
</a
> earlier this month. Several valuable testers showed
7326 up, and caused me to really want to to open up the development to more
7327 people. But before I did this, I want to come up with a sensible name
7328 for this project. Today I finally decided on a new name, and I have
7329 renamed the project from hw-support-handler to this new name. In the
7330 process, I moved the source to git and made it available as a
7331 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
7332 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
7333 To fetch and build the latest version of the source, use
</p
>
7336 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
7337 cd isenkram
&& git-buildpackage -us -uc
7340 <p
>I have not yet adjusted all files to use the new name yet. If you
7341 want to hack on the source or improve the package, please go ahead.
7342 But please talk to me first on IRC or via email before you do major
7343 changes, to make sure we do not step on each others toes. :)
</p
>
7345 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
7346 stuff, typically meaning tools, nails, screws, etc. Typical hardware
7347 stuff, in other words. I
've been told it is the Norwegian variant of
7348 the German word eisenkram, for those that are familiar with that
7351 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
7352 instructions, to avoid confusing people with an error from the signing
7355 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
7356 clone argument to avoid the need for authentication.
</p
>
7361 <title>First prototype ready making hardware easier to use in Debian
</title>
7362 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
7363 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
7364 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
7365 <description><p
>Early this month I set out to try to
7366 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
7367 the Debian support for pluggable hardware devices
</a
>. Now my
7368 prototype is working, and it is ready for a larger audience. To test
7370 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
7371 from the Debian Edu subversion repository
</a
>, build and install the
7372 package. You might have to log out and in again activate the
7373 autostart script.
</p
>
7375 <p
>The design is simple:
</p
>
7379 <li
>Add desktop entry in /usr/share/autostart/ causing a program
7380 hw-support-handlerd to start when the user log in.
</li
>
7382 <li
>This program listen for kernel events about new hardware (directly
7383 from the kernel like udev does), not using HAL dbus events as I
7384 initially did.
</li
>
7386 <li
>When new hardware is inserted, look up the hardware modalias in
7387 the APT database, a database
7388 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
7389 via HTTP
</a
> and a database available as part of the package.
</li
>
7391 <li
>If a package is mapped to the hardware in question, the package
7392 isn
't installed yet and this is the first time the hardware was
7393 plugged in, show a desktop notification suggesting to install the
7394 package or packages.
</li
>
7396 <li
>If the user click on the
'install package now
' button, ask
7397 aptdaemon via the PackageKit API to install the requrired package.
</li
>
7399 <li
>aptdaemon ask for root password or sudo password, and install the
7400 package while showing progress information in a window.
</li
>
7404 <p
>I still need to come up with a better name for the system. Here
7405 are some screen shots showing the prototype in action. First the
7406 notification, then the password request, and finally the request to
7407 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
7409 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
7410 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
7411 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
7412 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
7413 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
7415 <p
>The prototype still need to be improved with longer timeouts, but
7416 is already useful. The database of hardware to package mappings also
7417 need more work. It is currently compatible with the Ubuntu way of
7418 storing such information in the package control file, but could be
7419 changed to use other formats instead or in addition to the current
7420 method. I
've dropped the use of discover for this mapping, as the
7421 modalias approach is more flexible and easier to use on Linux as long
7422 as the Linux kernel expose its modalias strings directly.
</p
>
7424 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
7425 here is the command required to check out and build the source: Use
7426 '<tt
>svn checkout
7427 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
7428 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
7429 devscripts package.
</p
>
7431 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
7432 renamed to Isenkram and the source moved from the Debian Edu
7433 subversion repository to a Debian collab-maint git repository. See
7434 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
7435 instructions
</a
> for details.
</p
>
7440 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
7441 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
7442 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
7443 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
7444 <description><p
>This Christmas my trusty old laptop died. It died quietly and
7445 suddenly in bed. With a quiet whimper, it went completely quiet and
7446 black. The power button was no longer able to turn it on. It was a
7447 IBM Thinkpad X41, and the best laptop I ever had. Better than both
7448 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
7449 Compaq I had before that. Now I need to find a replacement. To keep
7450 going during Christmas, I moved the one year old SSD disk to my old
7451 X40 where it fitted (only one I had left that could use it), but it is
7452 not a durable solution.
7454 <p
>My laptop needs are fairly modest. This is my wishlist from when I
7455 got a new one more than
10 years ago. It still holds true.:)
</p
>
7459 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
7460 than A4).
</li
>
7461 <li
>Robust, it will be in my backpack every day.
</li
>
7462 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
7463 <li
>Long battery life time. Preferable a week.
</li
>
7464 <li
>Internal WIFI network card.
</li
>
7465 <li
>Internal Twisted Pair network card.
</li
>
7466 <li
>Some USB slots (
2-
3 is plenty)
</li
>
7467 <li
>Good keyboard - similar to the Thinkpad.
</li
>
7468 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
7470 <li
>Hardware supported by Debian Stable, ie the default kernel and
7471 X.org packages.
</li
>
7472 <li
>Quiet, preferably fan free (or at least not using the fan most of
7477 <p
>You will notice that there are no RAM and CPU requirements in the
7478 list. The reason is simply that the specifications on laptops the
7479 last
10-
15 years have been sufficient for my needs, and I have to look
7480 at other features to choose my laptop. But are there still made as
7481 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
7482 robust, and Thinkpads seem to be heading in the wrong direction since
7483 Lenovo took over. But I
've been told that X220 and X1 Carbon might
7484 still be useful.
</p
>
7486 <p
>Perhaps I should rethink my needs, and look for a pad with an
7487 external keyboard? I
'll have to check the
7488 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
7489 well-supported laptops, or perhaps just buy one preinstalled from one
7490 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
7491 Pre-loaded site
</a
>.
</p
>
7496 <title>How to find a browser plugin supporting a given MIME type
</title>
7497 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
7498 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
7499 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
7500 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
7501 install to get support for a given MIME type. Thanks to
7502 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
7503 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
7504 Unfortunately, not very many packages provide the needed meta
7505 information, Anyway, here is a small script to look up all browser
7506 plugin packages announcing ther MIME support using this specification:
</p
>
7512 def pkgs_handling_mimetype(mimetype):
7517 version = pkg.candidate
7519 version = pkg.installed
7522 record = version.record
7523 if not record.has_key(
'Npp-MimeType
'):
7525 mime_types = record[
'Npp-MimeType
'].split(
',
')
7526 for t in mime_types:
7527 t = t.rstrip().strip()
7529 thepkgs.append(pkg.name)
7531 mimetype =
"audio/ogg
"
7532 if
1 < len(sys.argv):
7533 mimetype = sys.argv[
1]
7534 print
"Browser plugin packages supporting %s:
" % mimetype
7535 for pkg in pkgs_handling_mimetype(mimetype):
7536 print
" %s
" %pkg
7539 <p
>It can be used like this to look up a given MIME type:
</p
>
7542 % ./apt-find-browserplug-for-mimetype
7543 Browser plugin packages supporting audio/ogg:
7545 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7546 Browser plugin packages supporting application/x-shockwave-flash:
7547 browser-plugin-gnash
7551 <p
>In Ubuntu this mechanism is combined with support in the browser
7552 itself to query for plugins and propose to install the needed
7553 packages. It would be great if Debian supported such feature too. Is
7554 anyone working on adding it?
</p
>
7556 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
7557 request for icweasel support for this feature is
7558 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
7559 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
7560 of manpower and wish for a different design is the reason thus feature
7561 is not yet in iceweasel from Debian.
</p
>
7566 <title>What is the most supported MIME type in Debian?
</title>
7567 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
7568 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
7569 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
7570 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
7571 proposal to add AppStream information to the Debian archive
</a
>, is a
7572 proposal to make it possible for a Desktop application to propose to
7573 the user some package to install to gain support for a given MIME
7574 type, font, library etc. that is currently missing. With such
7575 mechanism in place, it would be possible for the desktop to
7576 automatically propose and install leocad if some LDraw file is
7577 downloaded by the browser.
</p
>
7579 <p
>To get some idea about the current content of the archive, I decided
7580 to write a simple program to extract all .desktop files from the
7581 Debian archive and look up the claimed MIME support there. The result
7583 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
7584 site
</a
>. Using the collected information, it become possible to
7585 answer the question in the title. Here are the
20 most supported MIME
7586 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7587 The complete list is available from the link above.
</p
>
7589 <p
><strong
>Debian Stable:
</strong
></p
>
7593 ----- -----------------------
7609 18 application/x-ogg
7616 <p
><strong
>Debian Testing:
</strong
></p
>
7620 ----- -----------------------
7636 18 application/x-ogg
7643 <p
><strong
>Debian Unstable:
</strong
></p
>
7647 ----- -----------------------
7664 18 application/x-ogg
7670 <p
>I am told that PackageKit can provide an API to access the kind of
7671 information mentioned in DEP-
11. I have not yet had time to look at
7672 it, but hope the PackageKit people in Debian are on top of these
7675 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
7676 discovering a typo in my script.
</p
>
7681 <title>Using modalias info to find packages handling my hardware
</title>
7682 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
7683 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
7684 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
7685 <description><p
>Yesterday, I wrote about the
7686 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
7687 values provided by the Linux kernel
</a
> following my hope for
7688 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
7689 dongle support in Debian
</a
>. Using this knowledge, I have tested how
7690 modalias values attached to package names can be used to map packages
7691 to hardware. This allow the system to look up and suggest relevant
7692 packages when I plug in some new hardware into my machine, and replace
7693 discover and discover-data as the database used to map hardware to
7696 <p
>I create a modaliases file with entries like the following,
7697 containing package name, kernel module name (if relevant, otherwise
7698 the package name) and globs matching the relevant hardware
7701 <p
><blockquote
>
7702 Package: package-name
7703 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
7704 </blockquote
></p
>
7706 <p
>It is fairly trivial to write code to find the relevant packages
7707 for a given modalias value using this file.
</p
>
7709 <p
>An entry like this would suggest the video and picture application
7710 cheese for many USB web cameras (interface bus class
0E01):
</p
>
7712 <p
><blockquote
>
7714 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
7715 </blockquote
></p
>
7717 <p
>An entry like this would suggest the pcmciautils package when a
7718 CardBus bridge (bus class
0607) PCI device is present:
</p
>
7720 <p
><blockquote
>
7721 Package: pcmciautils
7722 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7723 </blockquote
></p
>
7725 <p
>An entry like this would suggest the package colorhug-client when
7726 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
7728 <p
><blockquote
>
7729 Package: colorhug-client
7730 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
7731 </blockquote
></p
>
7733 <p
>I believe the format is compatible with the format of the Packages
7734 file in the Debian archive. Ubuntu already uses their Packages file
7735 to store their mappings from packages to hardware.
</p
>
7737 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
7738 announce the hardware it support in a way my prototype understand.
7739 This allow those publishing packages in an APT source outside the
7740 Debian archive as well as those backporting packages to make sure the
7741 hardware mapping are included in the package meta information. I
've
7742 tested such header in the pymissile package, and its modalias mapping
7743 is working as it should with my prototype. It even made it to Ubuntu
7746 <p
>To test if it was possible to look up supported hardware using only
7747 the shell tools available in the Debian installer, I wrote a shell
7748 implementation of the lookup code. The idea is to create files for
7749 each modalias and let the shell do the matching. Please check out and
7751 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
7752 shell script. It run without any extra dependencies and fetch the
7753 hardware mappings from the Debian archive and the subversion
7754 repository where I currently work on my prototype.
</p
>
7756 <p
>When I use it on a machine with a yubikey inserted, it suggest to
7757 install yubikey-personalization:
</p
>
7759 <p
><blockquote
>
7760 % ./hw-support-lookup
7761 <br
>yubikey-personalization
7763 </blockquote
></p
>
7765 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7766 propose to install the pcmciautils package:
</p
>
7768 <p
><blockquote
>
7769 % ./hw-support-lookup
7770 <br
>pcmciautils
7772 </blockquote
></p
>
7774 <p
>If you know of any hardware-package mapping that should be added to
7775 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
7776 database
</a
>, please tell me about it.
</p
>
7778 <p
>It could be possible to generate several of the mappings between
7779 packages and hardware. One source would be to look at packages with
7780 kernel modules, ie packages with *.ko files in /lib/modules/, and
7781 extract their modalias information. Another would be to look at
7782 packages with udev rules, ie packages with files in
7783 /lib/udev/rules.d/, and extract their vendor/model information to
7784 generate a modalias matching rule. I have not tested any of these to
7785 see if it work.
</p
>
7787 <p
>If you want to help implementing a system to let us propose what
7788 packages to install when new hardware is plugged into a Debian
7789 machine, please send me an email or talk to me on
7790 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7795 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
7796 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
7797 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
7798 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
7799 <description><p
>While looking into how to look up Debian packages based on hardware
7800 information, to find the packages that support a given piece of
7801 hardware, I refreshed my memory regarding modalias values, and decided
7802 to document the details. Here are my findings so far, also available
7804 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7805 Debian Edu subversion repository
</a
>:
7807 <p
><strong
>Modalias decoded
</strong
></p
>
7809 <p
>This document try to explain what the different types of modalias
7810 values stands for. It is in part based on information from
7811 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
7812 &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;,
7813 &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
7814 &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;.
7816 <p
>The modalias entries for a given Linux machine can be found using
7817 this shell script:
</p
>
7820 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
7823 <p
>The supported modalias globs for a given kernel module can be found
7824 using modinfo:
</p
>
7827 % /sbin/modinfo psmouse | grep alias:
7828 alias: serio:ty05pr*id*ex*
7829 alias: serio:ty01pr*id*ex*
7833 <p
><strong
>PCI subtype
</strong
></p
>
7835 <p
>A typical PCI entry can look like this. This is an Intel Host
7836 Bridge memory controller:
</p
>
7838 <p
><blockquote
>
7839 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7840 </blockquote
></p
>
7842 <p
>This represent these values:
</p
>
7847 sv
00001028 (subvendor)
7848 sd
000001AD (subdevice)
7850 sc
00 (bus subclass)
7854 <p
>The vendor/device values are the same values outputted from
'lspci
7855 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
7856 0600. The
0600 class is a host bridge. Other useful bus values are
7857 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
7859 <p
>Not sure how to figure out the interface value, nor what it
7862 <p
><strong
>USB subtype
</strong
></p
>
7864 <p
>Some typical USB entries can look like this. This is an internal
7865 USB hub in a laptop:
</p
>
7867 <p
><blockquote
>
7868 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7869 </blockquote
></p
>
7871 <p
>Here is the values included in this alias:
</p
>
7874 v
1D6B (device vendor)
7875 p
0001 (device product)
7877 dc
09 (device class)
7878 dsc
00 (device subclass)
7879 dp
00 (device protocol)
7880 ic
09 (interface class)
7881 isc
00 (interface subclass)
7882 ip
00 (interface protocol)
7885 <p
>The
0900 device class/subclass means hub. Some times the relevant
7886 class is in the interface class section. For a simple USB web camera,
7887 these alias entries show up:
</p
>
7889 <p
><blockquote
>
7890 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7891 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7892 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7893 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7894 </blockquote
></p
>
7896 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
7897 camera),
0101 is audio control device and
0102 is audio streaming (aka
7898 microphone). Thus this is a camera with microphone included.
</p
>
7900 <p
><strong
>ACPI subtype
</strong
></p
>
7902 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
7903 receiver in a Thinkpad X40:
</p
>
7905 <p
><blockquote
>
7906 acpi:IBM0071:PNP0511:
7907 </blockquote
></p
>
7909 <p
>The values between the colons are IDs.
</p
>
7911 <p
><strong
>DMI subtype
</strong
></p
>
7913 <p
>The DMI table contain lots of information about the computer case
7914 and model. This is an entry for a IBM Thinkpad X40, fetched from
7915 /sys/devices/virtual/dmi/id/modalias:
</p
>
7917 <p
><blockquote
>
7918 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7919 </blockquote
></p
>
7921 <p
>The values present are
</p
>
7924 bvn IBM (BIOS vendor)
7925 bvr
1UETB
6WW(
1.66) (BIOS version)
7926 bd
06/
15/
2005 (BIOS date)
7927 svn IBM (system vendor)
7928 pn
2371H4G (product name)
7929 pvr ThinkPadX40 (product version)
7930 rvn IBM (board vendor)
7931 rn
2371H4G (board name)
7932 rvr NotAvailable (board version)
7933 cvn IBM (chassis vendor)
7934 ct
10 (chassis type)
7935 cvr NotAvailable (chassis version)
7938 <p
>The chassis type
10 is Notebook. Other interesting values can be
7939 found in the dmidecode source:
</p
>
7943 4 Low Profile Desktop
7956 17 Main Server Chassis
7957 18 Expansion Chassis
7959 20 Bus Expansion Chassis
7960 21 Peripheral Chassis
7962 23 Rack Mount Chassis
7971 <p
>The chassis type values are not always accurately set in the DMI
7972 table. For example my home server is a tower, but the DMI modalias
7973 claim it is a desktop.
</p
>
7975 <p
><strong
>SerIO subtype
</strong
></p
>
7977 <p
>This type is used for PS/
2 mouse plugs. One example is from my
7978 test machine:
</p
>
7980 <p
><blockquote
>
7981 serio:ty01pr00id00ex00
7982 </blockquote
></p
>
7984 <p
>The values present are
</p
>
7993 <p
>This type is supported by the psmouse driver. I am not sure what
7994 the valid values are.
</p
>
7996 <p
><strong
>Other subtypes
</strong
></p
>
7998 <p
>There are heaps of other modalias subtypes according to
7999 file2alias.c. There is the rest of the list from that source: amba,
8000 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
8001 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
8002 vmbus, x86cpu and zorro. I did not spend time documenting all of
8003 these, as they do not seem relevant for my intended use with mapping
8004 hardware to packages when new stuff is inserted during run time.
</p
>
8006 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
8008 <p
>To check which kernel modules provide support for a given modalias,
8009 one can use the following shell script:
</p
>
8012 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
8013 echo
"$id
" ; \
8014 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
8018 <p
>The output can look like this (only the first few entries as the
8019 list is very long on my test machine):
</p
>
8023 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
8025 FATAL: Module acpi:device: not found.
8027 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
8028 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
8029 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
8030 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
8031 acpi:IBM0071:PNP0511:
8032 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
8033 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
8034 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
8038 <p
>If you want to help implementing a system to let us propose what
8039 packages to install when new hardware is plugged into a Debian
8040 machine, please send me an email or talk to me on
8041 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
8043 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
8044 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
8045 in /sys/ with space in them.
</p
>
8050 <title>Moved the pymissile Debian packaging to collab-maint
</title>
8051 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
8052 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
8053 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
8054 <description><p
>As part of my investigation on how to improve the support in Debian
8055 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
8056 Launcher and updated the Debian package
8057 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
8058 sure udev will fix the device permissions when it is plugged in. I
8059 also added a
"Modaliases
" header to test it in the Debian archive and
8060 hopefully make the package be proposed by jockey in Ubuntu when a user
8061 plug in his rocket launcher. In the process I moved the source to a
8062 git repository under collab-maint, to make it easier for any DD to
8063 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
8064 is not very active, but the software still work for me even after five
8065 years of relative silence. The new git repository is not listed in
8066 the uploaded package yet, because I want to test the other changes a
8067 bit more before I upload the new version. If you want to check out
8068 the new version with a .desktop file included, visit the
8069 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
8070 view
</a
> or use
"<tt
>git clone
8071 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
8076 <title>Lets make hardware dongles easier to use in Debian
</title>
8077 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
8078 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
8079 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
8080 <description><p
>One thing that annoys me with Debian and Linux distributions in
8081 general, is that there is a great package management system with the
8082 ability to automatically install software packages by downloading them
8083 from the distribution mirrors, but no way to get it to automatically
8084 install the packages I need to use the hardware I plug into my
8085 machine. Even if the package to use it is easily available from the
8086 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
8087 suggest to automatically install the python-nxt, nbc and t2n packages
8088 I need to talk to it. When I plug in a Yubikey, it could propose the
8089 yubikey-personalization package. The information required to do this
8090 is available, but no-one have pulled all the pieces together.
</p
>
8092 <p
>Some years ago, I proposed to
8093 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
8094 the discover subsystem to implement this
</a
>. The idea is fairly
8099 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
8100 starting when a user log in.
</li
>
8102 <li
>Set this program up to listen for kernel events emitted when new
8103 hardware is inserted into the computer.
</li
>
8105 <li
>When new hardware is inserted, look up the hardware ID in a
8106 database mapping to packages, and take note of any non-installed
8107 packages.
</li
>
8109 <li
>Show a message to the user proposing to install the discovered
8110 package, and make it easy to install it.
</li
>
8114 <p
>I am not sure what the best way to implement this is, but my
8115 initial idea was to use dbus events to discover new hardware, the
8116 discover database to find packages and
8117 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
8120 <p
>Yesterday, I found time to try to implement this idea, and the
8121 draft package is now checked into
8122 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
8123 Debian Edu subversion repository
</a
>. In the process, I updated the
8124 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
8125 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
8126 the relevant packages in Debian, and uploaded a new version
8127 2.2013.01.09 to unstable. I also discovered that the current
8128 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
8129 package in Debian no longer discovered any USB devices, because
8130 /proc/bus/usb/devices is no longer present. I ported it to use
8131 libusb as a fall back option to get it working. The fixed package
8132 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
8133 because of the freeze).
</p
>
8135 <p
>With this prototype in place, I can insert my Yubikey, and get this
8136 desktop notification to show up (only once, the first time it is
8137 inserted):
</p
>
8139 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
8141 <p
>For this prototype to be really useful, some way to automatically
8142 install the proposed packages by pressing the
"Please install
8143 program(s)
" button should to be implemented.
</p
>
8145 <p
>If this idea seem useful to you, and you want to help make it
8146 happen, please help me update the discover-data database with mappings
8147 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
8148 list the package you would like to have installed when a given
8149 hardware device is inserted into your computer, and report bugs using
8150 reportbug if it isn
't. Or, if you know of a better way to provide
8151 such mapping, please let me know.
</p
>
8153 <p
>This prototype need more work, and there are several questions that
8154 should be considered before it is ready for production use. Is dbus
8155 the correct way to detect new hardware? At the moment I look for HAL
8156 dbus events on the system bus, because that is the events I could see
8157 on my Debian Squeeze KDE desktop. Are there better events to use?
8158 How should the user be notified? Is the desktop notification
8159 mechanism the best option, or should the background daemon raise a
8160 popup instead? How should packages be installed? When should they
8161 not be installed?
</p
>
8163 <p
>If you want to help getting such feature implemented in Debian,
8164 please send me an email. :)
</p
>
8169 <title>New IRC channel for LEGO designers using Debian
</title>
8170 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
8171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
8172 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
8173 <description><p
>During Christmas, I have worked a bit on the Debian support for
8174 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
8175 NXT
</a
>. My son and I have played a bit with my NXT set, and I
8176 discovered I had to build all the tools myself because none were
8177 already in Debian Squeeze. If Debian support for LEGO is something
8178 you care about, please join me on the IRC channel
8179 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
8180 irc.debian.org). There is a lot that could be done to improve the
8181 Debian support for LEGO designers. For example both CAD software
8182 and Mindstorm compilers are missing. :)
</p
>
8184 <p
>Update
2012-
01-
03: A
8185 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
8186 including links to Lego related packages is now available.
</p
>
8191 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
8192 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
8193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
8194 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
8195 <description><p
>Let me start by wishing you all marry Christmas and a happy new
8196 year! I hope next year will prove to be a good year.
</p
>
8198 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
8199 decentralised
"currency
" that allow people to transfer bitcoins
8200 between each other with minimal overhead, is a very interesting
8201 experiment. And as I wrote a few days ago, the bitcoin situation in
8202 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
8203 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
8204 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
8205 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
8206 for one of the ftpmasters to approve the new bitcoin-qt package
8209 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
8210 team in Debian, you can easily test the package in Debian Squeeze
8211 using the following steps to get a set of working packages:
</p
>
8213 <blockquote
><pre
>
8214 git clone git://git.debian.org/git/collab-maint/bitcoin
8216 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
8217 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
8218 </pre
></blockquote
>
8220 <p
>You might have to install some build dependencies as well. The
8221 list of commands should give you two packages, bitcoind and
8222 bitcoin-qt, ready for use in a Squeeze environment. Note that the
8223 client will download the complete set of bitcoin
"blocks
", which need
8224 around
5.6 GiB of data on my machine at the moment. Make sure your
8225 ~/.bitcoin/ directory have lots of spare room if you want to download
8226 all the blocks. The client will warn if the disk is getting full, so
8227 there is not really a problem if you got too little room, but you will
8228 not be able to get all the features out of the client.
</p
>
8230 <p
>As usual, if you use bitcoin and want to show your support of my
8231 activities, please send Bitcoin donations to my address
8232 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8237 <title>A word on bitcoin support in Debian
</title>
8238 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
8239 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
8240 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
8241 <description><p
>It has been a while since I wrote about
8242 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
8243 peer-to-peer based crypto-currency, and the reason is simply that I
8244 have been busy elsewhere. But two days ago, I started looking at the
8245 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
8246 Debian
</a
> again to try to recover my old bitcoin wallet. The package
8247 is now maintained by a
8248 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
8249 people
</a
>, and the grunt work had already been done by this team. We
8250 owe a huge thank you to all these team members. :)
8251 But I was sad to discover that the bitcoin client is missing in
8252 Wheezy. It is only available in Sid (and an outdated client from
8253 backports). The client had several RC bugs registered in BTS blocking
8254 it from entering testing. To try to help the team and improve the
8255 situation, I spent some time providing patches and triaging the bug
8256 reports. I also had a look at the bitcoin package available from Matt
8258 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
8259 Ubuntu
</a
>, and moved the useful pieces from that version into the
8260 Debian package.
</p
>
8262 <p
>After checking with the main package maintainer Jonas Smedegaard on
8263 IRC, I pushed several patches into the collab-maint git repository to
8264 improve the package. It now contains fixes for the RC issues (not from
8265 me, but fixed by Scott Howard), build rules for a Qt GUI client
8266 package, konqueror support for the bitcoin: URI and bash completion
8267 setup. As I work on Debian Squeeze, I also created
8268 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
8269 patch to backport
</a
> the latest version. Jonas is going to look at
8270 it and try to integrate it into the git repository before uploading a
8271 new version to unstable.
8273 <p
>I would very much like bitcoin to succeed, to get rid of the
8274 centralized control currently exercised in the monetary system. I
8275 find it completely unacceptable that the USA government is collecting
8276 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
8277 that the major credit card companies can block legal money
8278 transactions to Wikileaks. But for bitcoin to succeed, more people
8279 need to use bitcoins, and more people need to accept bitcoins when
8280 they sell products and services. Improving the bitcoin support in
8281 Debian is a small step in the right direction, but not enough.
8282 Unfortunately the user experience when browsing the web and wanting to
8283 pay with bitcoin is still not very good. The bitcoin: URI is a step
8284 in the right direction, but need to work in most or every browser in
8285 use. Also the bitcoin-qt client is too heavy to fire up to do a
8286 quick transaction. I believe there are other clients available, but
8287 have not tested them.
</p
>
8290 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
8291 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
8292 I received
20.15 BTC so far on the address I provided in my blog two
8293 years ago, as can be
8294 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
8295 on the blockexplorer service
</a
>. Thank you everyone for your
8296 donation. The blockexplorer service demonstrates quite well that
8297 bitcoin is not quite anonymous and untracked. :) I wonder if the
8298 number of users have gone up since then. If you use bitcoin and want
8299 to show your support of my activity, please send Bitcoin donations to
8300 the same address as last time,
8301 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8306 <title>Git repository for song book for Computer Scientists
</title>
8307 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
8308 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
8309 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
8310 <description><p
>As I
8311 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
8312 this summer
</a
>, I have created a Computer Science song book a few
8313 years ago, and today I finally found time to create a public
8314 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
8315 repository for the project
</a
>.
</p
>
8317 <p
>If you want to help out, please clone the source and submit patches
8318 to the HTML version. To generate the PDF and PostScript version,
8319 please use prince XML, or let me know about a useful free software
8320 processor capable of creating a good looking PDF from the HTML.
</p
>
8322 <p
>Want to sing? You can still find the song book in HTML, PDF and
8323 PostScript formats at
8324 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
8325 Science Songbook
</a
>.
</p
>
8330 <title>Gratulerer med
19-årsdagen, Debian!
</title>
8331 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
8332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
8333 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
8334 <description><p
>I dag fyller
8335 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
8336 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
8337 si gratulerer med dagen, Debian!
</p
>
8342 <title>Song book for Computer Scientists
</title>
8343 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
8344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
8345 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
8346 <description><p
>Many years ago, while studying Computer Science at the
8347 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
8348 collecting computer related songs for use at parties. The original
8349 version was written in LaTeX, but a few years ago I got help from
8350 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
8351 while keeping the ability to create a nice book in PDF format. I have
8352 not had time to maintain the book for a while now, and guess I should
8353 put it up on some public version control repository where others can
8354 help me extend and update the book. If anyone is volunteering to help
8355 me with this, send me an email. Also let me know if there are songs
8356 missing in my book.
</p
>
8358 <p
>I have not mentioned the book on my blog so far, and it occured to
8359 me today that I really should let all my readers share the joys of
8360 singing out load about programming, computers and computer networks.
8361 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
8362 12</a
> is about to start (and I am not going). Want to sing? Check
8363 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
8364 Computer Science Songbook
</a
>.
8369 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
8370 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
8371 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
8372 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
8373 <description><p
>At work we have heaps of servers. I believe the total count is
8374 around
1000 at the moment. To be able to get help from the vendors
8375 when something go wrong, we want to keep the firmware on the servers
8376 up to date. If the firmware isn
't the latest and greatest, the
8377 vendors typically refuse to start debugging any problems until the
8378 firmware is upgraded. So before every reboot, we want to upgrade the
8379 firmware, and we would really like everyone handling servers at the
8380 university to do this themselves when they plan to reboot a machine.
8381 For that to happen we at the unix server admin group need to provide
8382 the tools to do so.
</p
>
8384 <p
>To make firmware upgrading easier, I am working on a script to
8385 fetch and install the latest firmware for the servers we got. Most of
8386 our hardware are from Dell and HP, so I have focused on these servers
8387 so far. This blog post is about the Dell part.
</P
>
8389 <p
>On the Dell FTP site I was lucky enough to find
8390 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
8391 with firmware information for all
11th generation servers, listing
8392 which firmware should be used on a given model and where on the FTP
8393 site I can find it. Using a simple perl XML parser I can then
8394 download the shell scripts Dell provides to do firmware upgrades from
8395 within Linux and reboot when all the firmware is primed and ready to
8396 be activated on the first reboot.
</p
>
8398 <p
>This is the Dell related fragment of the perl code I am working on.
8399 Are there anyone working on similar tools for firmware upgrading all
8400 servers at a site? Please get in touch and lets share resources.
</p
>
8402 <p
><pre
>
8406 use File::Temp qw(tempdir);
8408 # Install needed RHEL packages if missing
8410 'XML::Simple
' =
> 'perl-XML-Simple
',
8412 for my $module (keys %rhelmodules) {
8413 eval
"use $module;
";
8415 my $pkg = $rhelmodules{$module};
8416 system(
"yum install -y $pkg
");
8417 eval
"use $module;
";
8421 my $errorsto =
'pere@hungry.com
';
8427 sub run_firmware_script {
8428 my ($opts, $script) = @_;
8430 print STDERR
"fail: missing script name\n
";
8433 print STDERR
"Running $script\n\n
";
8435 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
8436 print STDERR
"success: firmware script ran succcessfully\n
";
8438 print STDERR
"fail: firmware script returned error\n
";
8442 sub run_firmware_scripts {
8443 my ($opts, @dirs) = @_;
8444 # Run firmware packages
8445 for my $dir (@dirs) {
8446 print STDERR
"info: Running scripts in $dir\n
";
8447 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
8448 while (my $s = readdir $dh) {
8449 next if $s =~ m/^\.\.?/;
8450 run_firmware_script($opts,
"$dir/$s
");
8458 print STDERR
"info: Downloading $url\n
";
8459 system(
"wget --quiet \
"$url\
"");
8464 my $product = `dmidecode -s system-product-name`;
8467 if ($product =~ m/PowerEdge/) {
8469 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
8470 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
8472 my $tmpdir = tempdir(
8476 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
8477 system(
'gunzip Catalog.xml.gz
');
8478 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
8479 # -q is quiet, disabling interactivity and reducing console output
8480 my $fwopts =
"-q
";
8482 for my $url (@paths) {
8483 fetch_dell_fw($url);
8485 run_firmware_scripts($fwopts, $tmpdir);
8487 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
8488 print STDERR
"error: Please report to $errorsto.\n
";
8492 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
8493 print STDERR
"error: Please report to $errorsto.\n
";
8499 my $url =
"ftp://ftp.us.dell.com/$path
";
8503 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
8504 # firmware packages to download from Dell. Only work for Linux
8505 # machines and
11th generation Dell servers.
8506 sub fetch_dell_fw_list {
8507 my $filename = shift;
8509 my $product = `dmidecode -s system-product-name`;
8511 my ($mybrand, $mymodel) = split(/\s+/, $product);
8513 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
8515 my $xml = XMLin($filename);
8517 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
8518 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
8519 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
8521 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
8522 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
8524 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
8526 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
8528 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
8531 for my $component (@{$xml-
>{SoftwareComponent}}) {
8532 my $componenttype = $component-
>{ComponentType}-
>{value};
8534 # Drop application packages, only firmware and BIOS
8535 next if
'APAC
' eq $componenttype;
8537 my $cpath = $component-
>{path};
8538 for my $path (@paths) {
8539 if ($cpath =~ m%/$path$%) {
8540 push(@paths, $cpath);
8548 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
8549 it could work on other platforms with some tweaking. Anyone know a
8550 index like Catalog.xml is available from HP for HP servers? At the
8551 moment I maintain a similar list manually and it is quickly getting
8557 <title>How is booting into runlevel
1 different from single user boots?
</title>
8558 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
8559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
8560 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
8561 <description><p
>Wouter Verhelst have some
8562 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
8563 comments and opinions
</a
> on my blog post on
8564 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
8565 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
8566 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
8567 default KDE desktop in Debian
</a
>. I only have time to address one
8568 small piece of his comment now, and though it best to address the
8569 misunderstanding he bring forward:
</p
>
8571 <p
><blockquote
>
8572 Currently, a system admin has four options: [...] boot to a
8573 single-user system (by adding
'single
' to the kernel command line;
8574 this runs rcS and rc1 scripts)
8575 </blockquote
></p
>
8577 <p
>This make me believe Wouter believe booting into single user mode
8578 and booting into runlevel
1 is the same. I am not surprised he
8579 believe this, because it would make sense and is a quite sensible
8580 thing to believe. But because the boot in Debian is slightly broken,
8581 runlevel
1 do not work properly and it isn
't the same as single user
8582 mode. I
'll try to explain what is actually happing, but it is a bit
8583 hard to explain.
</p
>
8585 <p
>Single user mode is defined like this in /etc/inittab:
8586 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
8587 executed in single user mode is sulogin. Single user mode is a boot
8588 state
"between
" the runlevels, and when booting into single user mode,
8589 only the scripts in /etc/rcS.d/ are executed before the init process
8590 enters the single user state. When switching to runlevel
1, the state
8591 is in fact not ending in runlevel
1, but it passes through runlevel
1
8592 and end up in the single user mode (see /etc/rc1.d/S03single, which
8593 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
8594 1. It is confusing that the
'S
' (single user) init mode is not the
8595 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8598 <p
>This summary might make it clearer. When booting for the first
8599 time into single user mode, the following commands are executed:
8600 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
8601 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
8602 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
8603 trying to continue after visiting single user mode. Not all services
8604 are started again as they should, causing the machine to end up in an
8605 unpredicatble state. This is why Debian admins recommend rebooting
8606 after visiting single user mode.
</p
>
8608 <p
>A similar problem with runlevel
1 is caused by the amount of
8609 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
8610 to runlevel
1, the services started from /etc/rcS.d/ are not properly
8611 stopped when passing through the scripts in /etc/rc1.d/, and not
8612 started again when switching away from runlevel
1 to the runlevels
8613 2-
5. I believe the problem is best fixed by moving all the scripts
8614 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
8615 functioning single user mode during boot.
</p
>
8617 <p
>I have spent several years investigating the Debian boot system,
8618 and discovered this problem a few years ago. I suspect it originates
8619 from when sysvinit was introduced into Debian, a long time ago.
</p
>
8624 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
8625 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
8626 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
8627 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
8628 <description><p
>In the Debian boot system, several packages include scripts that
8629 are started from /etc/rcS.d/. In fact, there is a bite more of them
8630 than make sense, and this causes a few problems. What kind of
8631 problems, you might ask. There are at least two problems. The first
8632 is that it is not possible to recover a machine after switching to
8633 runlevel
1. One need to actually reboot to get the machine back to
8634 the expected state. The other is that single user boot will sometimes
8635 run into problems because some of the subsystems are activated before
8636 the root login is presented, causing problems when trying to recover a
8637 machine from a problem in that subsystem. A minor additional point is
8638 that moving more scripts out of rcS.d/ and into the other rc#.d/
8639 directories will increase the amount of scripts that can run in
8640 parallel during boot, and thus decrease the boot time.
</p
>
8642 <p
>So, which scripts should start from rcS.d/. In short, only the
8643 scripts that _have_ to execute before the root login prompt is
8644 presented during a single user boot should go there. Everything else
8645 should go into the numeric runlevels. This means things like
8646 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8647 the numeric runlevels. Today in Debian, there are around
115 init.d
8648 scripts that are started from rcS.d/, and most of them should be moved
8649 out. Do your package have one of them? Please help us make single
8650 user and runlevel
1 better by moving it.
</p
>
8652 <p
>Scripts setting up the screen, keyboard, system partitions
8653 etc. should still be started from rcS.d/, but there is for example no
8654 need to have the network enabled before the single user login prompt
8655 is presented.
</p
>
8657 <p
>As always, things are not so easy to fix as they sound. To keep
8658 Debian systems working while scripts migrate and during upgrades, the
8659 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8660 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8661 and the next ones can only be moved when their dependencies have been
8662 moved first. This migration must be done sequentially while we ensure
8663 that the package system upgrade packages in the right order to keep
8664 the system state correct. This will require some coordination when it
8665 comes to network related packages, but most of the packages with
8666 scripts that should migrate do not have anything in rcS.d/ depending
8667 on them. Some packages have already been updated, like the sudo
8668 package, while others are still left to do. I wish I had time to work
8669 on this myself, but real live constrains make it unlikely that I will
8670 find time to push this forward.
</p
>
8675 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
8676 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
8677 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
8678 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
8679 <description><p
>While at Debconf11, I have several times during discussions
8680 mentioned the issues I believe should be improved in Debian for its
8681 desktop to be useful for more people. The use case for this is my
8682 parents, which are currently running Kubuntu which solve the
8685 <p
>I suspect these four missing features are not very hard to
8686 implement. After all, they are present in Ubuntu, so if we wanted to
8687 do this in Debian we would have a source.
</p
>
8691 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
8692 are new packages available for upgrades, a icon in the KDE status bar
8693 indicate this, and clicking on it will activate the simple upgrade
8694 tool to handle it. I have no problem guiding both of my parents
8695 through the process over the phone. If a kernel reboot is required,
8696 this too is indicated by the status bars and the upgrade tool. Last
8697 time I checked, nothing with the same features was working in KDE in
8700 <li
><strong
>Simple handling of missing Firefox browser
8701 plugins.
</strong
> When the browser encounter a MIME type it do not
8702 currently have a handler for, it will ask the user if the system
8703 should search for a package that would add support for this MIME type,
8704 and if the user say yes, the APT sources will be searched for packages
8705 advertising the MIME type in their control file (visible in the
8706 Packages file in the APT archive). If one or more packages are found,
8707 it is a simple click of the mouse to add support for the missing mime
8708 type. If the package require the user to accept some non-free
8709 license, this is explained to the user. The entire process make it
8710 more clear to the user why something do not work in the browser, and
8711 make the chances higher for the user to blame the web page authors and
8712 not the browser for any missing features.
</li
>
8714 <li
><strong
>Simple handling of missing multimedia codec/format
8715 handlers.
</strong
> When the media players encounter a format or codec
8716 it is not supporting, a dialog pop up asking the user if the system
8717 should search for a package that would add support for it. This
8718 happen with things like MP3, Windows Media or H
.264. The selection
8719 and installation procedure is very similar to the Firefox browser
8720 plugin handling. This is as far as I know implemented using a
8721 gstreamer hook. The end result is that the user easily get access to
8722 the codecs that are present from the APT archives available, while
8723 explaining more on why a given format is unsupported by Ubuntu.
</li
>
8725 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
8726 displaying a text/plain file in my Debian browser, it will propose to
8727 start emacs to show it. If I remember correctly, when doing the same
8728 in Kunbutu it show the file as a text file in the browser. At least I
8729 know Opera will show text files within the browser. I much prefer the
8730 latter behaviour.
</li
>
8734 <p
>There are other nice features as well, like the simplified suite
8735 upgrader, but given that I am the one mostly doing the dist-upgrade,
8736 it do not matter much.
</p
>
8738 <p
>I really hope we could get these features in place for the next
8739 Debian release. It would require the coordinated effort of several
8740 maintainers, but would make the end user experience a lot better.
</p
>
8745 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
8746 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
8747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
8748 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
8749 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
8750 site is build on Debian/Squeeze, and this platform was chosen because
8751 I am most familiar with Debian (being a Debian Developer for around
10
8752 years) because it is the latest stable Debian release which should get
8753 security support for a few years.
</p
>
8755 <p
>The web service is written in Perl, and depend on some perl modules
8756 that are missing in Debian at the moment. It would be great if these
8757 modules were added to the Debian archive, allowing anyone to set up
8758 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
8759 in their own country using only Debian packages. The list of modules
8760 missing in Debian/Squeeze isn
't very long, and I hope the perl group
8761 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
8762 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8763 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8764 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8765 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8766 easier in the future.
</p
>
8768 <p
>Thanks to the great tools in Debian, getting the missing modules
8769 installed on my server was a simple call to
'cpan2deb Module::Name
'
8770 and
'dpkg -i
' to install the resulting package. But this leave me
8771 with the responsibility of tracking security problems, which I really
8772 do not have time for.
</p
>
8777 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
8778 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
8779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
8780 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
8781 <description><p
>Here is a small update for my English readers. Most of my blog
8782 posts have been in Norwegian the last few weeks, so here is a short
8783 update in English.
</p
>
8785 <p
>The kids still keep me too busy to get much free software work
8786 done, but I did manage to organise a project to get a Norwegian port
8787 of the British service
8788 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
8789 and it has been running for a month now. The entire project has been
8790 organised by me and two others. Around Christmas we gathered sponsors
8791 to fund the development work. In January I drafted a contract with
8792 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
8793 and in February the development took place. Most of it involved
8794 converting the source to use GPS coordinates instead of British
8795 easting/northing, and the resulting code should be a lot easier to get
8796 running in any country by now. The Norwegian
8797 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
8798 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
8799 source and the source for administrative borders in Norway, and
8800 support for this had to be added/fixed.
</p
>
8802 <p
>The Norwegian version went live March
3th, and we spent the weekend
8803 polishing the system before we announced it March
7th. The system is
8804 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
8805 problem reports in a few weeks. Soon we hope to announce the Android
8806 and iPhone versions making it even easier to report problems with the
8807 public infrastructure.
</p
>
8809 <p
>Perhaps something to consider for those of you in countries without
8810 such service?
</p
>
8815 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
8816 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
8817 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
8818 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
8819 <description><p
>The last few days I have looked at ways to track open security
8820 issues here at my work with the University of Oslo. My idea is that
8821 it should be possible to use the information about security issues
8822 available on the Internet, and check our locally
8823 maintained/distributed software against this information. It should
8824 allow us to verify that no known security issues are forgotten. The
8825 CVE database listing vulnerabilities seem like a great central point,
8826 and by using the package lists from Debian mapped to CVEs provided by
8827 the testing security team, I believed it should be possible to figure
8828 out which security holes were present in our free software
8829 collection.
</p
>
8831 <p
>After reading up on the topic, it became obvious that the first
8832 building block is to be able to name software packages in a unique and
8833 consistent way across data sources. I considered several ways to do
8834 this, for example coming up with my own naming scheme like using URLs
8835 to project home pages or URLs to the Freshmeat entries, or using some
8836 existing naming scheme. And it seem like I am not the first one to
8837 come across this problem, as MITRE already proposed and implemented a
8838 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
8839 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
8840 software, hardware and other platform components. The CPE ids are
8841 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
8842 Vulnerability Database
</a
>, allowing me to look up know security
8843 issues for any CPE name. With this in place, all I need to do is to
8844 locate the CPE id for the software packages we use at the university.
8845 This is fairly trivial (I google for
'cve cpe $package
' and check the
8846 NVD entry if a CVE for the package exist).
</p
>
8848 <p
>To give you an example. The GNU gzip source package have the CPE
8849 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
8850 check out, one could look up
8851 <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
8852 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
8853 The most recent one is
8854 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
8855 and at the bottom of the NVD page for this vulnerability the complete
8856 list of affected versions is provided.
</p
>
8858 <p
>The NVD database of CVEs is also available as a XML dump, allowing
8859 for offline processing of issues. Using this dump, I
've written a
8860 small script taking a list of CPEs as input and list all CVEs
8861 affecting the packages represented by these CPEs. One give it CPEs
8862 with version numbers as specified above and get a list of open
8863 security issues out.
</p
>
8865 <p
>Of course for this approach to be useful, the quality of the NVD
8866 information need to be high. For that to happen, I believe as many as
8867 possible need to use and contribute to the NVD database. I notice
8869 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
8870 map from CVE to CPE
</a
>, indicating that they are using the CPE
8871 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
8873 <p
>To get an idea about the quality for free software, I spent some
8874 time making it possible to compare the CVE database from Debian with
8875 the CVE database in NVD. The result look fairly good, but there are
8876 some inconsistencies in NVD (same software package having several
8877 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8878 Debian believe are affected by a CVE). Hope to find time to improve
8879 the quality of NVD, but that require being able to get in touch with
8880 someone maintaining it. So far my three emails with questions and
8881 corrections have not seen any reply, but I hope contact can be
8882 established soon.
</p
>
8884 <p
>An interesting application for CPEs is cross platform package
8885 mapping. It would be useful to know which packages in for example
8886 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8887 this would be trivial if all linux distributions provided CPE entries
8888 for their packages.
</p
>
8893 <title>Which module is loaded for a given PCI and USB device?
</title>
8894 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
8895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
8896 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
8897 <description><p
>In the
8898 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
8899 package in Debian, there is a script to report useful information
8900 about the running hardware for use when people report missing
8901 information. One part of this script that I find very useful when
8902 debugging hardware problems, is the part mapping loaded kernel module
8903 to the PCI device it claims. It allow me to quickly see if the kernel
8904 module I expect is driving the hardware I am struggling with. To see
8905 the output, make sure discover-data is installed and run
8906 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
8907 one of my machines like this:
</p
>
8911 10de:
03eb i2c_nforce2
8914 10de:
03f0 snd_hda_intel
8923 <p
>The code in question look like this, slightly modified for
8924 readability and to drop the output to file descriptor
3:
</p
>
8927 if [ -d /sys/bus/pci/devices/ ] ; then
8928 echo loaded pci modules:
8930 cd /sys/bus/pci/devices/
8931 for address in * ; do
8932 if [ -d
"$address/driver/module
" ] ; then
8933 module=`cd $address/driver/module ; pwd -P | xargs basename`
8934 if grep -q
"^$module
" /proc/modules ; then
8935 address=$(echo $address |sed s/
0000://)
8936 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
8937 echo
"$id $module
"
8946 <p
>Similar code could be used to extract USB device module
8950 if [ -d /sys/bus/usb/devices/ ] ; then
8951 echo loaded usb modules:
8953 cd /sys/bus/usb/devices/
8954 for address in * ; do
8955 if [ -d
"$address/driver/module
" ] ; then
8956 module=`cd $address/driver/module ; pwd -P | xargs basename`
8957 if grep -q
"^$module
" /proc/modules ; then
8958 address=$(echo $address |sed s/
0000://)
8959 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
8960 if [
"$id
" ] ; then
8961 echo
"$id $module
"
8971 <p
>This might perhaps be something to include in other tools as
8977 <title>How to test if a laptop is working with Linux
</title>
8978 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
8979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
8980 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
8981 <description><p
>The last few days I have spent at work here at the
<a
8982 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
8983 batch of computers will work with Linux. Every year for the last few
8984 years the university have organised shared bid of a few thousand
8985 computers, and this year HP won the bid. Two different desktops and
8986 five different laptops are on the list this year. We in the UNIX
8987 group want to know which one of these computers work well with RHEL
8988 and Ubuntu, the two Linux distributions we currently handle at the
8989 university.
</p
>
8991 <p
>My test method is simple, and I share it here to get feedback and
8992 perhaps inspire others to test hardware as well. To test, I PXE
8993 install the OS version of choice, and log in as my normal user and run
8994 a few applications and plug in selected pieces of hardware. When
8995 something fail, I make a note about this in the test matrix and move
8996 on. If I have some spare time I try to report the bug to the OS
8997 vendor, but as I only have the machines for a short time, I rarely
8998 have the time to do this for all the problems I find.
</p
>
9000 <p
>Anyway, to get to the point of this post. Here is the simple tests
9001 I perform on a new model.
</p
>
9005 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
9006 and Ubuntu Maverik at the moment. If I feel like it, I also test with
9007 RHEL5 and Debian Edu/Squeeze.
</li
>
9009 <li
>Is X.org working? If the graphical login screen show up after
9010 installation, X.org is working.
</li
>
9012 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
9013 package mesa-utils on Ubuntu) and writing down the frames per second
9014 reported by the program.
</li
>
9016 <li
>Is sound working? With Gnome and KDE, a sound is played when
9017 logging in, and if I can hear this the test is successful. If there
9018 are several audio exits on the machine, I try them all and check if
9019 the Gnome/KDE audio mixer can control where to send the sound. I
9020 normally test this by playing
9021 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
9022 video
</a
> in Firefox/Iceweasel.
</li
>
9024 <li
>Is the USB subsystem working? I test this by plugging in a USB
9025 memory stick and see if Gnome/KDE notices this.
</li
>
9027 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
9028 I have lying around, and see if Gnome/KDE notices this.
</li
>
9030 <li
>Is any built in camera working? Test using cheese, and see if a
9031 picture from the v4l device show up.
</li
>
9033 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
9034 any bluetooth devices are discovered. In my office, I normally see a
9037 <li
>For laptops, is the SD or Compaq Flash reader working. I have
9038 memory modules lying around, and stick them in and see if Gnome/KDE
9039 notice this.
</li
>
9041 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
9042 special button work, and if the laptop continue to work after
9045 <li
>For laptops, is the extra buttons working, like audio level,
9046 adjusting background light, switching on/off external video output,
9047 switching on/off wifi, bluetooth, etc? The set of buttons differ from
9048 laptop to laptop, so I just write down which are working and which are
9051 <li
>Some laptops have smart card readers, finger print readers,
9052 acceleration sensors etc. I rarely test these, as I do not know how
9053 to quickly test if they are working or not, so I only document their
9054 existence.
</li
>
9058 <p
>By now I suspect you are really curious what the test results are
9059 for the HP machines I am testing. I
'm not done yet, so I will report
9060 the test results later. For now I can report that HP
8100 Elite work
9061 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
9062 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
9063 can see, I have most machines left to test. One interesting
9064 observation is that Ubuntu Lucid has almost twice the frame rate than
9065 RHEL6 with glxgears. No idea why.
</p
>
9070 <title>Some thoughts on BitCoins
</title>
9071 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
9072 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
9073 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
9074 <description><p
>As I continue to explore
9075 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
9076 what properties the system have, and how it will be affected by laws
9077 and regulations here in Norway. Here are some random notes.
</p
>
9079 <p
>One interesting thing to note is that since the transactions are
9080 verified using a peer to peer network, all details about a transaction
9081 is known to everyone. This means that if a BitCoin address has been
9082 published like I did with mine in my initial post about BitCoin, it is
9083 possible for everyone to see how many BitCoins have been transfered to
9084 that address. There is even a web service to look at the details for
9085 all transactions. There I can see that my address
9086 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
9087 have received
16.06 Bitcoin, the
9088 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
9089 address of Simon Phipps have received
181.97 BitCoin and the address
9090 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
9091 of EFF have received
2447.38 BitCoins so far. Thank you to each and
9092 every one of you that donated bitcoins to support my activity. The
9093 fact that anyone can see how much money was transfered to a given
9094 address make it more obvious why the BitCoin community recommend to
9095 generate and hand out a new address for each transaction. I
'm told
9096 there is no way to track which addresses belong to a given person or
9097 organisation without the person or organisation revealing it
9098 themselves, as Simon, EFF and I have done.
</p
>
9100 <p
>In Norway, and in most other countries, there are laws and
9101 regulations limiting how much money one can transfer across the border
9102 without declaring it. There are money laundering, tax and accounting
9103 laws and regulations I would expect to apply to the use of BitCoin.
9104 If the Skolelinux foundation
9105 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
9106 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
9107 normal bank transfers like EFF is doing, how should this be accounted?
9108 Given that it is impossible to know if money can cross the border or
9109 not, should everything or nothing be declared? What exchange rate
9110 should be used when calculating taxes? Would receivers have to pay
9111 income tax if the foundation were to pay Skolelinux contributors in
9112 BitCoin? I have no idea, but it would be interesting to know.
</p
>
9114 <p
>For a currency to be useful and successful, it must be trusted and
9115 accepted by a lot of users. It must be possible to get easy access to
9116 the currency (as a wage or using currency exchanges), and it must be
9117 easy to spend it. At the moment BitCoin seem fairly easy to get
9118 access to, but there are very few places to spend it. I am not really
9119 a regular user of any of the vendor types currently accepting BitCoin,
9120 so I wonder when my kind of shop would start accepting BitCoins. I
9121 would like to buy electronics, travels and subway tickets, not herbs
9122 and books. :) The currency is young, and this will improve over time
9123 if it become popular, but I suspect regular banks will start to lobby
9124 to get BitCoin declared illegal if it become popular. I
'm sure they
9125 will claim it is helping fund terrorism and money laundering (which
9126 probably would be true, as is any currency in existence), but I
9127 believe the problems should be solved elsewhere and not by blaming
9128 currencies.
</p
>
9130 <p
>The process of creating new BitCoins is called mining, and it is
9131 CPU intensive process that depend on a bit of luck as well (as one is
9132 competing against all the other miners currently spending CPU cycles
9133 to see which one get the next lump of cash). The
"winner
" get
50
9134 BitCoin when this happen. Yesterday I came across the obvious way to
9135 join forces to increase ones changes of getting at least some coins,
9136 by coordinating the work on mining BitCoins across several machines
9137 and people, and sharing the result if one is lucky and get the
50
9139 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
9140 if this sounds interesting. I have not had time to try to set up a
9141 machine to participate there yet, but have seen that running on ones
9142 own for a few days have not yield any BitCoins througth mining
9145 <p
>Update
2010-
12-
15: Found an
<a
9146 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
9147 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
9148 it was interesting to read. The arguments presented seem to be
9149 equally valid for gold, which was used as a currency for many years.
</p
>
9154 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
9155 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
9156 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
9157 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
9158 <description><p
>With this weeks lawless
9159 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
9160 attacks
</a
> on Wikileak and
9161 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
9162 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
9163 not be trusted to handle money transactions.
9165 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
9166 Phipps on bitcoin
</a
> reminded me about a project that a friend of
9167 mine mentioned earlier. I decided to follow Simon
's example, and get
9168 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
9169 some help from my friend to get it all running, and he even handed me
9170 some bitcoins to get started. I even donated a few bitcoins to Simon
9171 for helping me remember BitCoin.
</p
>
9173 <p
>So, what is bitcoins, you probably wonder? It is a digital
9174 crypto-currency, decentralised and handled using peer-to-peer
9175 networks. It allows anonymous transactions and prohibits central
9176 control over the transactions, making it impossible for governments
9177 and companies alike to block donations and other transactions. The
9178 source is free software, and while the key dependency wxWidgets
2.9
9179 for the graphical user interface is missing in Debian, the command
9180 line client builds just fine. Hopefully Jonas
9181 <a href=
"http://bugs.debian.org/
578157">will get the package into
9182 Debian
</a
> soon.
</p
>
9184 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
9185 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
9186 bitcoins
</a
> when selling services and goods, and there are even
9187 currency
"stock
" markets where the exchange rate is decided. There
9188 are not many users so far, but the concept seems promising. If you
9189 want to get started and lack a friend with any bitcoins to spare,
9191 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
9192 bitcoin at the time of writing). Use
9193 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
9194 on the current exchange rates.
</p
>
9196 <p
>As an experiment, I have decided to set up bitcoind on one of my
9197 machines. If you want to support my activity, please send Bitcoin
9198 donations to the address
9199 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
9204 <title>Why isn
't Debian Edu using VLC?
</title>
9205 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
9206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
9207 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
9208 <description><p
>In the latest issue of Linux Journal, the readers choices were
9209 presented, and the winner among the multimedia player were VLC.
9210 Personally, I like VLC, and it is my player of choice when I first try
9211 to play a video file or stream. Only if VLC fail will I drag out
9212 gmplayer to see if it can do better. The reason is mostly the failure
9213 model and trust. When VLC fail, it normally pop up a error message
9214 reporting the problem. When mplayer fail, it normally segfault or
9215 just hangs. The latter failure mode drain my trust in the program.
<p
>
9217 <p
>But even if VLC is my player of choice, we have choosen to use
9218 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
9219 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
9220 plugin to play web videos seamlessly, and the VLC browser plugin is
9221 not very good. For example, it lack in-line control buttons, so there
9222 is no way for the user to pause the video. Also, when I
9223 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
9224 tested the browser plugins
</a
> available in Debian, the VLC plugin
9225 failed on several video pages where mplayer based plugins worked. If
9226 the browser plugin for VLC was as good as the gecko-mediaplayer
9227 package (which uses mplayer), we would switch.
</P
>
9229 <p
>While VLC is a good player, its user interface is slightly
9230 annoying. The most annoying feature is its inconsistent use of
9231 keyboard shortcuts. When the player is in full screen mode, its
9232 shortcuts are different from when it is playing the video in a window.
9233 For example, space only work as pause when in full screen mode. I
9234 wish it had consisten shortcuts and that space also would work when in
9235 window mode. Another nice shortcut in gmplayer is [enter] to restart
9236 the current video. It is very nice when playing short videos from the
9237 web and want to restart it when new people arrive to have a look at
9238 what is going on.
</p
>
9243 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
9244 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
9245 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</guid>
9246 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
9247 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
9248 upgrade testing of the
9249 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
9250 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
9251 This seem like a very good idea, so I adjusted by test scripts and
9252 can now present the updated result from today:
</p
>
9254 <p
>This is for Gnome:
</p
>
9256 <p
>Installed using apt-get, missing with aptitude
</p
>
9258 <blockquote
><p
>
9263 browser-plugin-gnash
9270 freedesktop-sound-theme
9272 gconf-defaults-service
9287 gnome-desktop-environment
9291 gnome-session-canberra
9296 gstreamer0.10-fluendo-mp3
9302 libapache2-mod-dnssd
9305 libaprutil1-dbd-sqlite3
9308 libboost-date-time1.42
.0
9309 libboost-python1.42
.0
9310 libboost-thread1.42
.0
9312 libchamplain-gtk-
0.4-
0
9314 libclutter-gtk-
0.10-
0
9321 libfreerdp-plugins-standard
9336 libgnomepanel2.24-cil
9341 libgtksourceview2.0-common
9342 libmono-addins-gui0.2-cil
9343 libmono-addins0.2-cil
9344 libmono-cairo2.0-cil
9345 libmono-corlib2.0-cil
9346 libmono-i18n-west2.0-cil
9347 libmono-posix2.0-cil
9348 libmono-security2.0-cil
9349 libmono-sharpzip2.84-cil
9350 libmono-system2.0-cil
9353 libndesk-dbus-glib1.0-cil
9354 libndesk-dbus1.0-cil
9364 libtelepathy-farsight0
9373 nautilus-sendto-empathy
9377 python-aptdaemon-gtk
9379 python-beautifulsoup
9394 python-gtksourceview2
9405 python-pkg-resources
9412 python-twisted-conch
9418 python-zope.interface
9423 rhythmbox-plugin-cdrecorder
9430 system-config-printer-udev
9432 telepathy-mission-control-
5
9443 </p
></blockquote
>
9445 <p
>Installed using apt-get, removed with aptitude
</p
>
9447 <blockquote
><p
>
9453 fast-user-switch-applet
9472 libgtksourceview2.0-
0
9474 libsdl1.2debian-alsa
9480 system-config-printer
9485 </p
></blockquote
>
9487 <p
>Installed using aptitude, missing with apt-get
</p
>
9489 <blockquote
><p
>
9490 gstreamer0.10-gnomevfs
9491 </p
></blockquote
>
9493 <p
>Installed using aptitude, removed with apt-get
</p
>
9495 <blockquote
><p
>
9497 </p
></blockquote
>
9499 <p
>This is for KDE:
</p
>
9501 <p
>Installed using apt-get, missing with aptitude
</p
>
9503 <blockquote
><p
>
9505 </p
></blockquote
>
9507 <p
>Installed using apt-get, removed with aptitude
</p
>
9509 <blockquote
><p
>
9512 </p
></blockquote
>
9514 <p
>Installed using aptitude, missing with apt-get
</p
>
9516 <blockquote
><p
>
9530 kdeartwork-emoticons
9532 kdeartwork-theme-icon
9536 kdebase-workspace-bin
9537 kdebase-workspace-data
9551 kscreensaver-xsavers
9566 plasma-dataengines-workspace
9568 plasma-desktopthemes-artwork
9569 plasma-runners-addons
9570 plasma-scriptengine-googlegadgets
9571 plasma-scriptengine-python
9572 plasma-scriptengine-qedje
9573 plasma-scriptengine-ruby
9574 plasma-scriptengine-webkit
9575 plasma-scriptengines
9576 plasma-wallpapers-addons
9577 plasma-widget-folderview
9578 plasma-widget-networkmanagement
9582 xscreensaver-data-extra
9584 xscreensaver-gl-extra
9585 xscreensaver-screensaver-bsod
9586 </p
></blockquote
>
9588 <p
>Installed using aptitude, removed with apt-get
</p
>
9590 <blockquote
><p
>
9592 google-gadgets-common
9610 libggadget-qt-
1.0-
0b
9615 libkonqsidebarplugin4a
9624 libplasma-geolocation-interface4
9626 libplasmagenericshell4
9640 libsmokeknewstuff2-
3
9641 libsmokeknewstuff3-
3
9643 libsmokektexteditor3
9651 libsmokeqtnetwork4-
3
9657 libsmokeqtuitools4-
3
9669 plasma-dataengines-addons
9670 plasma-scriptengine-superkaramba
9671 plasma-widget-lancelot
9672 plasma-widgets-addons
9673 plasma-widgets-workspace
9677 update-notifier-common
9678 </p
></blockquote
>
9680 <p
>Running apt-get autoremove made the results using apt-get and
9681 aptitude a bit more similar, but there are still quite a lott of
9682 differences. I have no idea what packages should be installed after
9683 the upgrade, but hope those that do can have a look.
</p
>
9688 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
9689 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
9690 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
9691 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
9692 <description><p
>Most of the computers in use by the
9693 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
9694 are virtual machines. And they have been Xen machines running on a
9695 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
9696 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
9697 bit harder that it could have been, because we set up the Xen virtual
9698 machines to get the virtual partitions from LVM, which as far as I
9699 know is not supported by KVM. So to migrate, we had to convert
9700 several LVM logical volumes to partitions on a virtual disk file.
</p
>
9703 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
9704 nice recipe
</a
> to do this, and wrote the following script to do the
9705 migration. It uses qemu-img from the qemu package to make the disk
9706 image, parted to partition it, losetup and kpartx to present the disk
9707 image partions as devices, and dd to copy the data. I NFS mounted the
9708 new servers storage area on the old server to do the migration.
</p
>
9714 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9719 if [ -z
"$
1" ] ; then
9720 echo
"Usage: $
0 &lt;hostname
&gt;
"
9726 if [ ! -e /dev/vg_data/$host-disk ] ; then
9727 echo
"error: unable to find LVM volume for $host
"
9731 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9732 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9733 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9734 totalsize=$(( ( $disksize + $swapsize ) ))
9737 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
9738 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9740 parted $img mklabel msdos
9741 parted $img mkpart primary linux-swap
0 $disksize
9742 parted $img mkpart primary ext2 $disksize $totalsize
9743 parted $img set
1 boot on
9746 losetup /dev/loop0 $img
9747 kpartx -a /dev/loop0
9749 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
9750 fsck.ext3 -f /dev/mapper/loop0p1 || true
9751 mkswap /dev/mapper/loop0p2
9753 kpartx -d /dev/loop0
9754 losetup -d /dev/loop0
9757 <p
>The script is perhaps so simple that it is not copyrightable, but
9758 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
9760 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
9761 the new disk image attached, installed grub-pc and linux-image-
686 and
9762 set up grub to boot from the disk image. After this, the KVM machines
9763 seem to work just fine.
</p
>
9768 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
9769 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
9770 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
9771 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
9772 <description><p
>I
'm still running upgrade testing of the
9773 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
9774 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
9775 status. Here is a short update based on a test I ran
20101118.
</p
>
9777 <p
>I still do not know what a correct migration should look like, so I
9778 report any differences between apt and aptitude and hope someone else
9779 can see if anything should be changed.
</p
>
9781 <p
>This is for Gnome:
</p
>
9783 <p
>Installed using apt-get, missing with aptitude
</p
>
9785 <blockquote
><p
>
9786 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9787 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
9788 dmz-cursor-theme empathy empathy-common finger
9789 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9790 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9791 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9792 gnome-cards-data gnome-codec-install gnome-core
9793 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9794 gnome-search-tool gnome-session-canberra gnome-spell
9795 gnome-system-log gnome-themes-extras gnome-themes-more
9796 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9797 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9798 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9799 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9800 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
9801 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
9802 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
9803 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
9804 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
9805 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9806 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
9807 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9808 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9809 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9810 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9811 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9812 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9813 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9814 libmono-security2.0-cil libmono-sharpzip2.84-cil
9815 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
9816 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
9817 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
9818 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
9819 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
9820 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
9821 libxalan2-java libxerces2-java media-player-info mesa-utils
9822 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
9823 nautilus-sendto-empathy openoffice.org-writer2latex
9824 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
9825 python-aptdaemon python-aptdaemon-gtk python-axiom
9826 python-beautifulsoup python-bugbuddy python-clientform
9827 python-coherence python-configobj python-crypto python-cupshelpers
9828 python-cupsutils python-eggtrayicon python-elementtree
9829 python-epsilon python-evolution python-feedparser python-gdata
9830 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9831 python-gtksourceview2 python-httplib2 python-louie python-mako
9832 python-markupsafe python-mechanize python-nevow python-notify
9833 python-opengl python-openssl python-pam python-pkg-resources
9834 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9835 python-tagpy python-twisted-bin python-twisted-conch
9836 python-twisted-core python-twisted-web python-utidylib python-webkit
9837 python-xdg python-zope.interface remmina remmina-plugin-data
9838 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9839 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9840 software-center svgalibg1 system-config-printer-udev
9841 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
9842 totem totem-coherence totem-mozilla totem-plugins
9843 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9845 </p
></blockquote
>
9847 Installed using apt-get, removed with aptitude
9849 <blockquote
><p
>
9850 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9851 epiphany-extensions epiphany-gecko evolution-exchange
9852 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9853 gedit-common gnome-app-install gnome-games gnome-games-data
9854 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9855 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9856 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9857 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
9858 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
9859 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
9860 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
9861 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9862 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9863 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9864 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
9865 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
9866 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9867 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9868 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9869 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9870 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
9871 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
9872 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
9873 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
9874 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
9875 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9876 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9877 sound-juicer swfdec-gnome system-config-printer totem-common
9878 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9879 </p
></blockquote
>
9881 <p
>Installed using aptitude, missing with apt-get
</p
>
9883 <blockquote
><p
>
9884 gstreamer0.10-gnomevfs
9885 </p
></blockquote
>
9887 <p
>Installed using aptitude, removed with apt-get
</p
>
9889 <blockquote
><p
>
9891 </p
></blockquote
>
9893 <p
>This is for KDE:
</p
>
9895 <p
>Installed using apt-get, missing with aptitude
</p
>
9897 <blockquote
><p
>
9898 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
9899 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9900 ghostscript-x git gnome-audio gnugo granatier gs-common
9901 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9902 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9903 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9904 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9905 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9906 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9907 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9908 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9909 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9910 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9911 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9912 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
9913 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9914 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9915 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9916 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9917 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9918 libkrossui4 libmailtools-perl libmime-tools-perl
9919 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9920 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9921 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9922 lirc luatex marble networkstatus noatun-plugins
9923 openoffice.org-writer2latex palapeli palapeli-data parley
9924 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9925 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9926 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9928 </p
></blockquote
>
9930 <p
>Installed using apt-get, removed with aptitude
</p
>
9932 <blockquote
><p
>
9933 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9934 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9935 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9936 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9937 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9938 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9939 kitchensync kiten kjumpingcube klatin klettres klickety klines
9940 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9941 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9942 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9943 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9944 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9945 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9946 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9947 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9948 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9949 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
9950 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
9951 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9952 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
9953 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
9954 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9955 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9956 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9957 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9958 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9959 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9960 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
9961 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
9962 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9963 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9964 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9965 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9966 </p
></blockquote
>
9968 <p
>Installed using aptitude, missing with apt-get
</p
>
9970 <blockquote
><p
>
9971 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9972 kdeartwork kdebase kdebase-apps kdebase-workspace
9973 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9974 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9975 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9976 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9977 xscreensaver-screensaver-bsod
9978 </p
></blockquote
>
9980 <p
>Installed using aptitude, removed with apt-get
</p
>
9982 <blockquote
><p
>
9983 kdebase-bin konq-plugins konqueror
9984 </p
></blockquote
>
9989 <title>Gnash buildbot slave and Debian kfreebsd
</title>
9990 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
9991 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
9992 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
9993 <description><p
>Answering
9994 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
9995 call from the Gnash project
</a
> for
9996 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
9997 current source, I have set up a virtual KVM machine on the Debian
9998 Edu/Skolelinux virtualization host to test the git source on
9999 Debian/Squeeze. I hope this can help the developers in getting new
10000 releases out more often.
</p
>
10002 <p
>As the developers want less main-stream build platforms tested to,
10003 I have considered setting up a
<a
10004 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
10005 machine as well. I have also considered using the kfreebsd
10006 architecture in Debian as a file server in NUUG to get access to the
5
10007 TB zfs volume we currently use to store DV video. Because of this, I
10008 finally got around to do a test installation of Debian/Squeeze with
10009 kfreebsd. Installation went fairly smooth, thought I noticed some
10010 visual glitches in the cdebconf dialogs (black cursor left on the
10011 screen at random locations). Have not gotten very far with the
10012 testing. Noticed cfdisk did not work, but fdisk did so it was not a
10013 fatal problem. Have to spend some more time on it to see if it is
10014 useful as a file server for NUUG. Will try to find time to set up a
10015 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
10020 <title>Debian in
3D
</title>
10021 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
10022 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
10023 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
10024 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
10026 <p
>3D printing is just great. I just came across this Debian logo in
10028 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
10029 thingiverse blog
</a
>.
</p
>
10034 <title>Software updates
2010-
10-
24</title>
10035 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
10036 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
10037 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
10038 <description><p
>Some updates.
</p
>
10040 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
10041 raise money for the project is going well. The lower limit of
10
10042 signers was reached in
24 hours, and so far
13 people have signed it.
10043 More signers and more funding is most welcome, and I am really curious
10044 how far we can get before the time limit of December
24 is reached.
10047 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
10048 about what appear to be a great code coverage tool capable of
10049 generating code coverage stats without any changes to the source code.
10051 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
10052 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
10053 It is missing in Debian, but the git source built just fine in Squeeze
10054 after I installed libelf-dev, libdwarf-dev, pkg-config and
10055 libglib2.0-dev. Failed to build in Lenny, but suspect that is
10056 solvable. I hope kcov make it into Debian soon.
</p
>
10058 <p
>Finally found time to wrap up the release notes for
<a
10059 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
10060 new alpha release of Debian Edu
</a
>, and just published the second
10061 alpha test release of the Squeeze based Debian Edu /
10062 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
10063 release. Give it a try if you need a complete linux solution for your
10064 school, including central infrastructure server, workstations, thin
10065 client servers and diskless workstations. A nice touch added
10066 yesterday is RDP support on the thin client servers, for windows
10067 clients to get a Linux desktop on request.
</p
>
10072 <title>Some notes on Flash in Debian and Debian Edu
</title>
10073 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
10074 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
10075 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
10076 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
10077 popularity-contest numbers
</a
>, the adobe-flashplugin package the
10078 second most popular used package that is missing in Debian. The sixth
10079 most popular is flashplayer-mozilla. This is a clear indication that
10080 working flash is important for Debian users. Around
10 percent of the
10081 users submitting data to popcon.debian.org have this package
10082 installed.
</p
>
10084 <p
>In the report written by Lars Risan in August
2008
10085 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
10086 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
10087 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
10088 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
10089 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
10090 web sites require Flash to work, and lacking working Flash support in
10091 the web browser and the problems with installing it was perceived as a
10092 good reason to stay with Windows.
</p
>
10094 <p
>I once saw a funny and sad comment in a web forum, where Linux was
10095 said to be the retarded cousin that did not really understand
10096 everything you told him but could work fairly well. This was a
10097 comment regarding the problems Linux have with proprietary formats and
10098 non-standard web pages, and is sad because it exposes a fairly common
10099 understanding of whose fault it is if web pages that only work in for
10100 example Internet Explorer
6 fail to work on Firefox, and funny because
10101 it explain very well how annoying it is for users when Linux
10102 distributions do not work with the documents they receive or the web
10103 pages they want to visit.
</p
>
10105 <p
>This is part of the reason why I believe it is important for Debian
10106 and Debian Edu to have a well working Flash implementation in the
10107 distribution, to get at least popular sites as Youtube and Google
10108 Video to working out of the box. For Squeeze, Debian have the chance
10109 to include the latest version of Gnash that will make this happen, as
10110 the new release
0.8.8 was published a few weeks ago and is resting in
10111 unstable. The new version work with more sites that version
0.8.7.
10112 The Gnash maintainers have asked for a freeze exception, but the
10113 release team have not had time to reply to it yet. I hope they agree
10114 with me that Flash is important for the Debian desktop users, and thus
10115 accept the new package into Squeeze.
</p
>
10120 <title>Circular package dependencies harms apt recovery
</title>
10121 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
10122 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
10123 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
10124 <description><p
>I discovered this while doing
10125 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
10126 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
10127 in Debian still got circular dependencies, and it is often claimed
10128 that apt and aptitude should be able to handle this just fine, but
10129 some times these dependency loops causes apt to fail.
</p
>
10131 <p
>An example is from todays
10132 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
10133 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
10134 causes perl-modules to fail to upgrade. The cause is simple. If a
10135 package fail to unpack, then only part of packages with the circular
10136 dependency might end up being unpacked when unpacking aborts, and the
10137 ones already unpacked will fail to configure in the recovery phase
10138 because its dependencies are unavailable.
</p
>
10140 <p
>In this log, the problem manifest itself with this error:
</p
>
10142 <blockquote
><pre
>
10143 dpkg: dependency problems prevent configuration of perl-modules:
10144 perl-modules depends on perl (
>=
5.10.1-
1); however:
10145 Version of perl on system is
5.10.0-
19lenny
2.
10146 dpkg: error processing perl-modules (--configure):
10147 dependency problems - leaving unconfigured
10148 </pre
></blockquote
>
10150 <p
>The perl/perl-modules circular dependency is already
10151 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
10152 hopefully be solved as soon as possible, but it is not the only one,
10153 and each one of these loops in the dependency tree can cause similar
10154 failures. Of course, they only occur when there are bugs in other
10155 packages causing the unpacking to fail, but it is rather nasty when
10156 the failure of one package causes the problem to become worse because
10157 of dependency loops.
</p
>
10160 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
10161 tireless effort by Bill Allombert
</a
>, the number of circular
10163 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
10164 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
10166 <p
>Todays testing also exposed a bug in
10167 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
10168 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
10169 apt-get and aptitude, the latter possibly caused by some circular
10170 dependency. Reported both to BTS to try to get someone to look at
10176 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
10177 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
10178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
10179 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
10180 <description><p
>This is a
10181 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
10183 <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
10185 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
10186 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
10188 <p
>As a step to try to see if it possible to merge the DNS and DHCP
10189 LDAP objects, I have had a look at how the packages pdns-backend-ldap
10190 and dhcp3-server-ldap in Debian use the LDAP server. The two
10191 implementations are quite different in how they use LDAP.
</p
>
10193 To get this information, I started slapd with debugging enabled and
10194 dumped the debug output to a file to get the LDAP searches performed
10195 on a Debian Edu main-server. Here is a summary.
10197 <p
><strong
>powerdns
</strong
></p
>
10199 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
10200 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
10203 <p
>PowerDNS have two modes of operation using LDAP as its backend.
10204 One
"strict
" mode where the forward and reverse DNS lookups are done
10205 using the same LDAP objects, and a
"tree
" mode where the forward and
10206 reverse entries are in two different subtrees in LDAP with a structure
10207 based on the DNS names, as in tjener.intern and
10208 2.2.0.10.in-addr.arpa.
</p
>
10210 <p
>In tree mode, the server is set up to use a LDAP subtree as its
10211 base, and uses a
"base
" scoped search for the DNS name by adding
10212 "dc=tjener,dc=intern,
" to the base with a filter for
10213 "(associateddomain=tjener.intern)
" for the forward entry and
10214 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
10215 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
10216 forward entries, it is looking for attributes named dnsttl, arecord,
10217 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
10218 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
10219 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
10220 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
10221 spfrecord and modifytimestamp. For reverse entries it is looking for
10222 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
10223 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
10224 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
10225 ldapsearch commands could look like this:
</p
>
10227 <blockquote
><pre
>
10228 ldapsearch -h ldap \
10229 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10230 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
10231 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10232 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10233 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10234 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10236 ldapsearch -h ldap \
10237 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10238 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
10239 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
10240 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
10241 srvrecord naptrrecord modifytimestamp
10242 </pre
></blockquote
>
10244 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
10245 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
10246 example LDAP objects used there. In addition to these objects, the
10247 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
10248 also exist.
</p
>
10250 <blockquote
><pre
>
10251 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
10253 objectclass: dnsdomain
10254 objectclass: domainrelatedobject
10257 associateddomain: tjener.intern
10259 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
10261 objectclass: dnsdomain2
10262 objectclass: domainrelatedobject
10264 ptrrecord: tjener.intern
10265 associateddomain:
2.2.0.10.in-addr.arpa
10266 </pre
></blockquote
>
10268 <p
>In strict mode, the server behaves differently. When looking for
10269 forward DNS entries, it is doing a
"subtree
" scoped search with the
10270 same base as in the tree mode for a object with filter
10271 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
10272 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
10273 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
10274 naptrrecord and modifytimestamp. For reverse entires it also do a
10275 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
10276 and the requested attributes are associateddomain, dnsttl and
10277 modifytimestamp. In short, in strict mode the objects with ptrrecord
10278 go away, and the arecord attribute in the forward object is used
10281 <p
>The forward and reverse searches can be simulated using ldapsearch
10282 like this:
</p
>
10284 <blockquote
><pre
>
10285 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10286 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
10287 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10288 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10289 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10290 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10292 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10293 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
10294 </pre
></blockquote
>
10296 <p
>In addition to the forward and reverse searches , there is also a
10297 search for SOA records, which behave similar to the forward and
10298 reverse lookups.
</p
>
10300 <p
>A thing to note with the PowerDNS behaviour is that it do not
10301 specify any objectclass names, and instead look for the attributes it
10302 need to generate a DNS reply. This make it able to work with any
10303 objectclass that provide the needed attributes.
</p
>
10305 <p
>The attributes are normally provided in the cosine (RFC
1274) and
10306 dnsdomain2 schemas. The latter is used for reverse entries like
10307 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
10309 <p
>In Debian Edu, we have created DNS objects using the object classes
10310 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
10311 attributes) and domainrelatedobject (for associatedDomain). The use
10312 of structural object classes make it impossible to combine these
10313 classes with the object classes used by DHCP.
</p
>
10315 <p
>There are other schemas that could be used too, for example the
10316 dnszone structural object class used by Gosa and bind-sdb for the DNS
10317 attributes combined with the domainrelatedobject object class, but in
10318 this case some unused attributes would have to be included as well
10319 (zonename and relativedomainname).
</p
>
10321 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
10322 mode and not use any of the existing objectclasses (dnsdomain,
10323 dnsdomain2 and dnszone) when one want to combine the DNS information
10324 with DHCP information, and instead create a auxiliary object class
10325 defined something like this (using the attributes defined for
10326 dnsdomain and dnsdomain2 or dnszone):
</p
>
10328 <blockquote
><pre
>
10329 objectclass ( some-oid NAME
'dnsDomainAux
'
10332 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
10333 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
10334 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
10335 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
10336 A6Record $ DNAMERecord
10338 </pre
></blockquote
>
10340 <p
>This will allow any object to become a DNS entry when combined with
10341 the domainrelatedobject object class, and allow any entity to include
10342 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
10343 developers asking for their view on this schema and if they are
10344 interested in providing such schema with PowerDNS, and I hope my
10345 message will be accepted into their mailing list soon.
</p
>
10347 <p
><strong
>ISC dhcp
</strong
></p
>
10349 <p
>The DHCP server searches for specific objectclass and requests all
10350 the object attributes, and then uses the attributes it want. This
10351 make it harder to figure out exactly what attributes are used, but
10352 thanks to the working example in Debian Edu I can at least get an idea
10353 what is needed without having to read the source code.
</p
>
10355 <p
>In the DHCP server configuration, the LDAP base to use and the
10356 search filter to use to locate the correct dhcpServer entity is
10357 stored. These are the relevant entries from
10358 /etc/dhcp3/dhcpd.conf:
</p
>
10360 <blockquote
><pre
>
10361 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
10362 ldap-dhcp-server-cn
"dhcp
";
10363 </pre
></blockquote
>
10365 <p
>The DHCP server uses this information to nest all the DHCP
10366 configuration it need. The cn
"dhcp
" is located using the given LDAP
10367 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
10368 search result is this entry:
</p
>
10370 <blockquote
><pre
>
10371 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
10374 objectClass: dhcpServer
10375 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10376 </pre
></blockquote
>
10378 <p
>The content of the dhcpServiceDN attribute is next used to locate the
10379 subtree with DHCP configuration. The DHCP configuration subtree base
10380 is located using a base scope search with base
"cn=DHCP
10381 Config,dc=skole,dc=skolelinux,dc=no
" and filter
10382 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
10383 The search result is this entry:
</p
>
10385 <blockquote
><pre
>
10386 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10389 objectClass: dhcpService
10390 objectClass: dhcpOptions
10391 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
10392 dhcpStatements: ddns-update-style none
10393 dhcpStatements: authoritative
10394 dhcpOption: smtp-server code
69 = array of ip-address
10395 dhcpOption: www-server code
72 = array of ip-address
10396 dhcpOption: wpad-url code
252 = text
10397 </pre
></blockquote
>
10399 <p
>Next, the entire subtree is processed, one level at the time. When
10400 all the DHCP configuration is loaded, it is ready to receive requests.
10401 The subtree in Debian Edu contain objects with object classes
10402 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
10403 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
10404 and information about netmasks, dynamic range etc. Leaving out the
10405 details here because it is not relevant for the focus of my
10406 investigation, which is to see if it is possible to merge dns and dhcp
10407 related computer objects.
</p
>
10409 <p
>When a DHCP request come in, LDAP is searched for the MAC address
10410 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
10411 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
10412 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
10413 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
10416 <blockquote
><pre
>
10417 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10420 objectClass: dhcpHost
10421 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
10422 dhcpStatements: fixed-address hostname
10423 </pre
></blockquote
>
10425 <p
>There is less flexiblity in the way LDAP searches are done here.
10426 The object classes need to have fixed names, and the configuration
10427 need to be stored in a fairly specific LDAP structure. On the
10428 positive side, the invidiual dhcpHost entires can be anywhere without
10429 the DN pointed to by the dhcpServer entries. The latter should make
10430 it possible to group all host entries in a subtree next to the
10431 configuration entries, and this subtree can also be shared with the
10432 DNS server if the schema proposed above is combined with the dhcpHost
10433 structural object class.
10435 <p
><strong
>Conclusion
</strong
></p
>
10437 <p
>The PowerDNS implementation seem to be very flexible when it come
10438 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
10439 come to the the LDAP structure, the
"strict
" mode is very flexible,
10440 allowing DNS objects to be stored anywhere under the base cn specified
10441 in the configuration.
</p
>
10443 <p
>The DHCP implementation on the other hand is very inflexible, both
10444 regarding which LDAP schemas to use and which LDAP structure to use.
10445 I guess one could implement ones own schema, as long as the
10446 objectclasses and attributes have the names used, but this do not
10447 really help when the DHCP subtree need to have a fairly fixed
10448 structure.
</p
>
10450 <p
>Based on the observed behaviour, I suspect a LDAP structure like
10451 this might work for Debian Edu:
</p
>
10453 <blockquote
><pre
>
10455 cn=machine-info (dhcpService) - dhcpServiceDN points here
10456 cn=dhcp (dhcpServer)
10457 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
10458 cn=
10.0.2.0 (dhcpSubnet)
10459 cn=group1 (dhcpGroup/dhcpOptions)
10460 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
10461 cn=
192.168.0.0 (dhcpSubnet)
10462 cn=group1 (dhcpGroup/dhcpOptions)
10463 ou=machines - PowerDNS base points here
10464 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
10465 </pre
></blockquote
>
10467 <P
>This is not tested yet. If the DHCP server require the dhcpHost
10468 entries to be in the dhcpGroup subtrees, the entries can be stored
10469 there instead of a common machines subtree, and the PowerDNS base
10470 would have to be moved one level up to the machine-info subtree.
</p
>
10472 <p
>The combined object under the machines subtree would look something
10473 like this:
</p
>
10475 <blockquote
><pre
>
10476 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
10479 objectClass: dhcpHost
10480 objectclass: domainrelatedobject
10481 objectclass: dnsDomainAux
10482 associateddomain: hostname.intern
10483 arecord:
10.11.12.13
10484 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
10485 dhcpStatements: fixed-address hostname.intern
10486 </pre
></blockquote
>
10488 </p
>One could even add the LTSP configuration associated with a given
10489 machine, as long as the required attributes are available in a
10490 auxiliary object class.
</p
>
10495 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
10496 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
10497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
10498 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
10499 <description><p
>For a while now, I have wanted to find a way to change the DNS and
10500 DHCP services in Debian Edu to use the same LDAP objects for a given
10501 computer, to avoid the possibility of having a inconsistent state for
10502 a computer in LDAP (as in DHCP but no DNS entry or the other way
10503 around) and make it easier to add computers to LDAP.
</p
>
10505 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
10506 information finally found a solution that seem to work.
</p
>
10508 <p
>The old setup required three LDAP objects for a given computer.
10509 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
10510 we switch powerdns to use its strict LDAP method (ldap-method=strict
10511 in pdns-debian-edu.conf), the forward and reverse DNS entries are
10512 merged into one while making it impossible to transfer the reverse map
10513 to a slave DNS server.
</p
>
10515 <p
>If we also replace the object class used to get the DNS related
10516 attributes to one allowing these attributes to be combined with the
10517 dhcphost object class, we can merge the DNS and DHCP entries into one.
10518 I
've written such object class in the dnsdomainaux.schema file (need
10519 proper OIDs, but that is a minor issue), and tested the setup. It
10520 seem to work.
</p
>
10522 <p
>With this test setup in place, we can get away with one LDAP object
10523 for both DNS and DHCP, and even the LTSP configuration I suggested in
10524 an earlier email. The combined LDAP object will look something like
10527 <blockquote
><pre
>
10528 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10530 objectClass: dhcphost
10531 objectclass: domainrelatedobject
10532 objectclass: dnsdomainaux
10533 associateddomain: hostname.intern
10534 arecord:
10.11.12.13
10535 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
10536 dhcpstatements: fixed-address hostname
10538 </pre
></blockquote
>
10540 <p
>The DNS server uses the associateddomain and arecord entries, while
10541 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10542 before asking DNS to resolve the fixed-adddress. LTSP will use
10543 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
10545 <p
>I am not yet sure if I can get the DHCP server to look for its
10546 dhcphost in a different location, to allow us to put the objects
10547 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
10548 that. If I can
't figure out a way to do that, we can still get rid of
10549 the hosts subtree and move all its content into the DHCP Config tree
10550 (which probably should be renamed to be more related to the new
10551 content. I suspect cn=dnsdhcp,ou=services or something like that
10552 might be a good place to put it.
</p
>
10554 <p
>If you want to help out with implementing this for Debian Edu,
10555 please contact us on debian-edu@lists.debian.org.
</p
>
10560 <title>Idea for storing LTSP configuration in LDAP
</title>
10561 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
10562 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
10563 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
10564 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
10565 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10566 clients, and that this can be used to fetch configuration from LDAP if
10567 Debian Edu choose to store configuration there.
</p
>
10569 <p
>Armed with this information, I got inspired and wrote a test module
10570 to get configuration from LDAP. The idea is to look up the MAC
10571 address of the client in LDAP, and look for attributes on the form
10572 ltspconfigsetting=value, and use this to export SETTING=value to the
10573 LTSP clients.
</p
>
10575 <p
>The goal is to be able to store the LTSP configuration attributes
10576 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
10577 allowing us to store all information about a computer in one place.
</p
>
10579 <p
>This is a untested draft implementation, and I welcome feedback on
10580 this approach. A real LDAP schema for the ltspClientAux objectclass
10581 need to be written. Comments, suggestions, etc?
</p
>
10583 <blockquote
><pre
>
10584 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10586 # Fetch LTSP client settings from LDAP based on MAC address
10588 # Uses ethernet address as stored in the dhcpHost objectclass using
10589 # the dhcpHWAddress attribute or ethernet address stored in the
10590 # ieee802Device objectclass with the macAddress attribute.
10592 # This module is written to be schema agnostic, and only depend on the
10593 # existence of attribute names.
10595 # The LTSP configuration variables are saved directly using a
10596 # ltspConfig prefix and uppercasing the rest of the attribute name.
10597 # To set the SERVER variable, set the ltspConfigServer attribute.
10599 # Some LDAP schema should be created with all the relevant
10600 # configuration settings. Something like this should work:
10602 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
10605 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10607 LDAPSERVER=$(debian-edu-ldapserver)
10608 if [
"$LDAPSERVER
" ] ; then
10609 LDAPBASE=$(debian-edu-ldapserver -b)
10610 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
10611 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
10612 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
10613 grep
'^ltspConfig
' | while read attr value ; do
10614 # Remove prefix and convert to upper case
10615 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
10616 # bass value on to clients
10617 eval
"$attr=$value; export $attr
"
10621 </pre
></blockquote
>
10623 <p
>I
'm not sure this shell construction will work, because I suspect
10624 the while block might end up in a subshell causing the variables set
10625 there to not show up in ltsp-config, but if that is the case I am sure
10626 the code can be restructured to make sure the variables are passed on.
10627 I expect that can be solved with some testing. :)
</p
>
10629 <p
>If you want to help out with implementing this for Debian Edu,
10630 please contact us on debian-edu@lists.debian.org.
</p
>
10632 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
10633 configuration in LDAP that was created around year
2000 by
10634 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
10635 Xperience, Inc.,
2000</a
>. I found its
10636 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
10637 personal home page over at redhat.com.
</p
>
10642 <title>jXplorer, a very nice LDAP GUI
</title>
10643 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
10644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
10645 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
10646 <description><p
>Since
10647 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
10648 last post
</a
> about available LDAP tools in Debian, I was told about a
10649 LDAP GUI that is even better than luma. The java application
10650 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
10651 moving LDAP objects and subtrees using drag-and-drop, and can
10652 authenticate using Kerberos. I have only tested the Kerberos
10653 authentication, but do not have a LDAP setup allowing me to rewrite
10654 LDAP with my test user yet. It is
10655 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
10656 Debian
</a
> testing and unstable at the moment. The only problem I
10657 have with it is how it handle errors. If something go wrong, its
10658 non-intuitive behaviour require me to go through some query work list
10659 and remove the failing query. Nothing big, but very annoying.
</p
>
10664 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
10665 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
10666 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
10667 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
10668 <description><p
>Here is a short update on my
<a
10669 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
10670 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
10671 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
10672 not reporting the status for KDE, because the upgrade crashes when
10673 aptitude try because of missing conflicts
10674 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
10675 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
10677 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
10678 complete list of the installed packages. Based on this I see these
10679 differences when I did a test run today. As usual, I do not really
10680 know what the correct set of packages would be, but thought it best to
10681 publish the difference.
</p
>
10683 <p
>Installed using apt-get, missing with aptitude
</p
>
10685 <blockquote
><p
>
10686 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
10687 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
10688 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10689 libgtksourceview-common libpt-
1.10.10-plugins-alsa
10690 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10691 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10692 python-
4suite-xml python-eggtrayicon python-gtkhtml2
10693 python-gtkmozembed svgalibg1 xserver-xephyr zip
10694 </p
></blockquote
>
10696 <p
>Installed using apt-get, removed with aptitude
</p
>
10698 <blockquote
><p
>
10699 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10700 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10701 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
10702 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
10703 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
10704 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
10705 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
10706 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
10707 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
10708 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
10709 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
10710 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
10711 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10712 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
10713 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10714 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
10715 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
10716 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10717 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10718 mysql-common swfdec-gnome totem-gstreamer wodim
10719 </p
></blockquote
>
10721 <p
>Installed using aptitude, missing with apt-get
</p
>
10723 <blockquote
><p
>
10724 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10725 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10726 xserver-xorg-input-all xserver-xorg-input-evdev
10727 xserver-xorg-input-kbd xserver-xorg-input-mouse
10728 xserver-xorg-input-synaptics xserver-xorg-video-all
10729 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10730 xserver-xorg-video-chips xserver-xorg-video-cirrus
10731 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10732 xserver-xorg-video-glint xserver-xorg-video-i128
10733 xserver-xorg-video-i740 xserver-xorg-video-mach64
10734 xserver-xorg-video-mga xserver-xorg-video-neomagic
10735 xserver-xorg-video-nouveau xserver-xorg-video-nv
10736 xserver-xorg-video-r128 xserver-xorg-video-radeon
10737 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10738 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10739 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10740 xserver-xorg-video-sis xserver-xorg-video-sisusb
10741 xserver-xorg-video-tdfx xserver-xorg-video-tga
10742 xserver-xorg-video-trident xserver-xorg-video-tseng
10743 xserver-xorg-video-vesa xserver-xorg-video-vmware
10744 xserver-xorg-video-voodoo
10745 </p
></blockquote
>
10747 <p
>Installed using aptitude, removed with apt-get
</p
>
10749 <blockquote
><p
>
10750 deskbar-applet xserver-xorg xserver-xorg-core
10751 xserver-xorg-input-wacom xserver-xorg-video-intel
10752 xserver-xorg-video-openchrome
10753 </p
></blockquote
>
10755 <p
>I was told on IRC that the xorg-xserver package was
10756 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
10757 in git
</a
> today to try to get apt-get to not remove xorg completely.
10758 No idea when it hits Squeeze, but when it does I hope it will reduce
10759 the difference somewhat.
10764 <title>LUMA, a very nice LDAP GUI
</title>
10765 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
10766 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
10767 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
10768 <description><p
>The last few days I have been looking into the status of the LDAP
10769 directory in Debian Edu, and in the process I started to miss a GUI
10770 tool to browse the LDAP tree. The only one I was able to find in
10771 Debian/Squeeze and Lenny is
10772 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
10773 be a great tool to get a overview of the current LDAP directory
10774 populated by default in Skolelinux. Thanks to it, I have been able to
10775 find empty and obsolete subtrees, misplaced objects and duplicate
10776 objects. It will be installed by default in Debian/Squeeze. If you
10777 are working with LDAP, give it a go. :)
</p
>
10779 <p
>I did notice one problem with it I have not had time to report to
10780 the BTS yet. There is no .desktop file in the package, so the tool do
10781 not show up in the Gnome and KDE menus, but only deep down in in the
10782 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10783 released.
</p
>
10785 <p
>I have not yet been able to get it to modify the tree yet. I would
10786 like to move objects and remove subtrees directly in the GUI, but have
10787 not found a way to do that with LUMA yet. So in the mean time, I use
10788 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
10790 <p
>If you have tips on other GUI tools for LDAP that might be useful
10791 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
10793 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
10794 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
10795 useful GUI alternative. It seem like a good tool, but is unmaintained
10796 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10797 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
10802 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
10803 <link>http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html
</link>
10804 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html
</guid>
10805 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
10806 <description><p
>A while back, I
10807 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
10808 about the fact
</a
> that it is not possible with the provided schemas
10809 for storing DNS and DHCP information in LDAP to combine the two sets
10810 of information into one LDAP object representing a computer.
</p
>
10812 <p
>In the mean time, I discovered that a simple fix would be to make
10813 the dhcpHost object class auxiliary, to allow it to be combined with
10814 the dNSDomain object class, and thus forming one object for one
10815 computer when storing both DHCP and DNS information in LDAP.
</p
>
10817 <p
>If I understand this correctly, it is not safe to do this change
10818 without also changing the assigned number for the object class, and I
10819 do not know enough about LDAP schema design to do that properly for
10820 Debian Edu.
</p
>
10822 <p
>Anyway, for future reference, this is how I believe we could change
10824 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
10825 schema
</a
> to solve at least part of the problem with the LDAP schemas
10826 available today from IETF.
</p
>
10829 --- dhcp.schema (revision
65192)
10830 +++ dhcp.schema (working copy)
10831 @@ -
376,
7 +
376,
7 @@
10832 objectclass (
2.16.840.1.113719.1.203.6.6
10833 NAME
'dhcpHost
'
10834 DESC
'This represents information about a particular client
'
10836 + SUP top AUXILIARY
10838 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10839 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
10842 <p
>I very much welcome clues on how to do this properly for Debian
10843 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10844 package, and should thus be free to rewrite it as we see fit.
</p
>
10846 <p
>If you want to help out with implementing this for Debian Edu,
10847 please contact us on debian-edu@lists.debian.org.
</p
>
10852 <title>Calling tasksel like the installer, while still getting useful output
</title>
10853 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
10854 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
10855 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
10856 <description><p
>A few times I have had the need to simulate the way tasksel
10857 installs packages during the normal debian-installer run. Until now,
10858 I have ended up letting tasksel do the work, with the annoying problem
10859 of not getting any feedback at all when something fails (like a
10860 conffile question from dpkg or a download that fails), using code like
10863 <blockquote
><pre
>
10864 export DEBIAN_FRONTEND=noninteractive
10865 tasksel --new-install
10866 </pre
></blockquote
>
10868 This would invoke tasksel, let its automatic task selection pick the
10869 tasks to install, and continue to install the requested tasks without
10870 any output what so ever.
10872 Recently I revisited this problem while working on the automatic
10873 package upgrade testing, because tasksel would some times hang without
10874 any useful feedback, and I want to see what is going on when it
10875 happen. Then it occured to me, I can parse the output from tasksel
10876 when asked to run in test mode, and use that aptitude command line
10877 printed by tasksel then to simulate the tasksel run. I ended up using
10880 <blockquote
><pre
>
10881 export DEBIAN_FRONTEND=noninteractive
10882 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
10884 </pre
></blockquote
>
10886 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
10887 --without-recommends -o APT::Install-Recommends=no -y install
10888 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10889 ~pimportant
</tt
>", which will install the gnome desktop task, the
10890 laptop task and all packages with priority standard , required and
10891 important, just like tasksel would have done it during
10892 installation.
</p
>
10894 <p
>A better approach is probably to extend tasksel to be able to
10895 install packages without using debconf-apt-progress, for use cases
10896 like this.
</p
>
10901 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
10902 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
10903 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
10904 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
10905 <description><p
>My
10906 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
10907 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
10908 finally made the upgrade logs available from
10909 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
10910 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10911 apt and aptitude, and found their differences interesting. This time
10912 I will only focus on their removal plans.
</p
>
10914 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
10915 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
10916 surprising part is that it want to remove xorg and all
10917 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10918 sure why. When asking aptitude to do the same, it want to remove
129
10919 packages, but most of them are library packages I suspect are no
10920 longer needed. Both of them want to remove bluetooth packages, which
10921 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
10923 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
10924 which seem like a bad idea and xorg the same way as with Gnome. Asking
10925 aptitude for the same, it wants to remove
192 packages, none which are
10926 too surprising.
</p
>
10928 <p
>I guess the removal of xorg during upgrades should be investigated
10929 and avoided, and perhaps others as well. Here are the complete list
10930 of planned removals. The complete logs is available from the URL
10931 above. Note if you want to repeat these tests, that the upgrade test
10932 for kde+apt-get hung in the tasksel setup because of dpkg asking
10933 conffile questions. No idea why. I worked around it by using
10934 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
10935 continue.
</p
>
10937 <p
><b
>apt-get gnome
72</b
>
10938 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
10939 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10940 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
10941 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10942 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10943 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10944 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10945 xserver-xorg-input-kbd xserver-xorg-input-mouse
10946 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10947 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10948 xserver-xorg-video-ati xserver-xorg-video-chips
10949 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10950 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10951 xserver-xorg-video-glint xserver-xorg-video-i128
10952 xserver-xorg-video-i740 xserver-xorg-video-imstt
10953 xserver-xorg-video-intel xserver-xorg-video-mach64
10954 xserver-xorg-video-mga xserver-xorg-video-neomagic
10955 xserver-xorg-video-nsc xserver-xorg-video-nv
10956 xserver-xorg-video-openchrome xserver-xorg-video-r128
10957 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10958 xserver-xorg-video-rendition xserver-xorg-video-s3
10959 xserver-xorg-video-s3virge xserver-xorg-video-savage
10960 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10961 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10962 xserver-xorg-video-tga xserver-xorg-video-trident
10963 xserver-xorg-video-tseng xserver-xorg-video-v4l
10964 xserver-xorg-video-vesa xserver-xorg-video-vga
10965 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
10966 xulrunner-
1.9-gnome-support
</p
>
10968 <p
><b
>aptitude gnome
129</b
>
10970 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
10971 djvulibre-desktop finger gnome-app-install gnome-mount
10972 gnome-network-admin gnome-spell gnome-vfs-obexftp
10973 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10974 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10975 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10976 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
10977 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
10978 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
10979 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
10980 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
10981 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
10982 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
10983 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
10984 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
10985 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10986 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
10987 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
10988 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
10989 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
10990 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
10991 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10992 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10993 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10994 openoffice.org-writer2latex openssl-blacklist p7zip
10995 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
10996 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10997 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10998 swfdec-mozilla totem-gstreamer update-manager wodim
10999 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11000 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11003 <p
><b
>apt-get kde
82</b
>
11005 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
11006 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
11007 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
11008 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
11009 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
11010 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
11011 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11012 xserver-xorg-input-kbd xserver-xorg-input-mouse
11013 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11014 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11015 xserver-xorg-video-ati xserver-xorg-video-chips
11016 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11017 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11018 xserver-xorg-video-glint xserver-xorg-video-i128
11019 xserver-xorg-video-i740 xserver-xorg-video-imstt
11020 xserver-xorg-video-intel xserver-xorg-video-mach64
11021 xserver-xorg-video-mga xserver-xorg-video-neomagic
11022 xserver-xorg-video-nsc xserver-xorg-video-nv
11023 xserver-xorg-video-openchrome xserver-xorg-video-r128
11024 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11025 xserver-xorg-video-rendition xserver-xorg-video-s3
11026 xserver-xorg-video-s3virge xserver-xorg-video-savage
11027 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11028 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11029 xserver-xorg-video-tga xserver-xorg-video-trident
11030 xserver-xorg-video-tseng xserver-xorg-video-v4l
11031 xserver-xorg-video-vesa xserver-xorg-video-vga
11032 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
11034 <p
><b
>aptitude kde
192</b
>
11035 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
11036 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
11037 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
11038 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
11039 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11040 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
11041 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
11042 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11043 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
11044 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
11045 kghostview khelpcenter khexedit kiconedit kitchensync klatin
11046 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
11047 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
11048 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
11049 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
11050 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
11051 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
11052 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11053 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
11054 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
11055 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11056 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
11057 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
11058 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
11059 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11060 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
11061 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
11062 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
11063 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
11064 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
11065 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
11066 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
11067 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
11068 texlive-common texlive-doc-base texlive-fonts-recommended
11069 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11070 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11071 xulrunner-
1.9</p
>
11077 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
11078 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
11079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
11080 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
11081 <description><p
>The last few days I have done some upgrade testing in Debian, to
11082 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
11083 have been discovered and reported in the process
11084 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
11085 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
11086 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
11087 kdebase-workspace-data), and to get a more regular testing going on, I
11088 am working on a script to automate the test.
</p
>
11090 <p
>The idea is to create a Lenny chroot and use tasksel to install a
11091 Gnome or KDE desktop installation inside the chroot before upgrading
11092 it. To ensure no services are started in the chroot, a policy-rc.d
11093 script is inserted. To make sure tasksel believe it is to install a
11094 desktop on a laptop, the tasksel tests are replaced in the chroot
11095 (only acceptable because this is a throw-away chroot).
</p
>
11097 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
11098 currently always fail because udev refuses to upgrade with the kernel
11099 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
11100 is created. The bug report
11101 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
11102 this problem do not trigger in a chroot, but I touch the file anyway
11103 to make sure the upgrade go well. Testing on virtual and real
11104 hardware have failed me because of udev so far, and creating this file
11105 do the trick in such settings anyway. This is a
11106 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
11107 issue
</a
> and the current udev behaviour is intended by the udev
11108 maintainer because he lack the resources to rewrite udev to keep
11109 working with old kernels or something like that. I really wish the
11110 udev upstream would keep udev backwards compatible, to avoid such
11111 upgrade problem, but given that they fail to do so, I guess
11112 documenting the way out of this mess is the best option we got for
11113 Debian Squeeze.
</p
>
11115 <p
>Anyway, back to the task at hand, testing upgrades. This test
11116 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
11119 <blockquote
><pre
>
11123 if [
"$
1" ] ; then
11132 exec
&lt; /dev/null
11134 mirror=http://ftp.skolelinux.org/debian
11135 tmpdir=chroot-$from-upgrade-$to-$desktop
11137 debootstrap $from $tmpdir $mirror
11138 chroot $tmpdir aptitude update
11139 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
11143 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
11145 umount $tmpdir/proc
11147 mount -t proc proc $tmpdir/proc
11148 # Make sure proc is unmounted also on failure
11149 trap exit_cleanup EXIT INT
11151 chroot $tmpdir aptitude -y install debconf-utils
11153 # Make sure tasksel autoselection trigger. It need the test scripts
11154 # to return the correct answers.
11155 echo tasksel tasksel/desktop multiselect $desktop | \
11156 chroot $tmpdir debconf-set-selections
11158 # Include the desktop and laptop task
11159 for test in desktop laptop ; do
11160 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
11164 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
11167 DEBIAN_FRONTEND=noninteractive
11168 DEBIAN_PRIORITY=critical
11169 export DEBIAN_FRONTEND DEBIAN_PRIORITY
11170 chroot $tmpdir tasksel --new-install
11172 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
11173 chroot $tmpdir aptitude update
11174 touch $tmpdir/etc/udev/kernel-upgrade
11175 chroot $tmpdir aptitude -y dist-upgrade
11177 </pre
></blockquote
>
11179 <p
>I suspect it would be useful to test upgrades with both apt-get and
11180 with aptitude, but I have not had time to look at how they behave
11181 differently so far. I hope to get a cron job running to do the test
11182 regularly and post the result on the web. The Gnome upgrade currently
11183 work, while the KDE upgrade fail because of the bug in
11184 kdebase-workspace-data
</p
>
11186 <p
>I am not quite sure what kind of extract from the huge upgrade logs
11187 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
11188 post, so I will refrain from trying. I can report that for Gnome,
11189 aptitude report
760 packages upgraded,
448 newly installed,
129 to
11190 remove and
1 not upgraded and
1024MB need to be downloaded while for
11191 KDE the same numbers are
702 packages upgraded,
507 newly installed,
11192 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
11194 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
11195 is able to migrate to dependency based boot sequencing and parallel
11196 booting without a hitch. Was unsure if there were still bugs with
11197 packages failing to clean up their obsolete init.d script during
11198 upgrades, and no such problem seem to affect the Gnome desktop+laptop
11199 packages.
</p
>
11204 <title>Upstart or sysvinit - as init.d scripts see it
</title>
11205 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
11206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
11207 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
11208 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
11209 scripts to migrate (some of) their operations to upstart job while
11210 keeping the init.d for hurd and kfreebsd. The packages with such
11211 needs will need a way to get their init.d scripts to behave
11212 differently when used with sysvinit and with upstart. Because of
11213 this, I had a look at the environment variables set when a init.d
11214 script is running under upstart, and when it is not.
</p
>
11216 <p
>With upstart, I notice these environment variables are set when a
11217 script is started from rcS.d/ (ignoring some irrelevant ones like
11218 COLUMNS):
</p
>
11220 <blockquote
><pre
>
11226 UPSTART_EVENTS=startup
11228 UPSTART_JOB=rc-sysinit
11229 </pre
></blockquote
>
11231 <p
>With sysvinit, these environment variables are set for the same
11234 <blockquote
><pre
>
11235 INIT_VERSION=sysvinit-
2.88
11240 </pre
></blockquote
>
11242 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
11243 sysvinit are not set by upstart. Not sure if it is intentional or not
11244 to not be compatible with sysvinit in this regard.
</p
>
11246 <p
>For scripts needing to behave differently when upstart is used,
11247 looking for the UPSTART_JOB environment variable seem to be a good
11253 <title>A manual for standards wars...
</title>
11254 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
11255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
11256 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
11257 <description><p
>Via the
11258 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
11259 of Rob Weir
</a
> I came across the very interesting essay named
11260 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
11261 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
11262 following the standards wars of today.
</p
>
11267 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
11268 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
11269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
11270 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
11271 <description><p
>When using sitesummary at a site to track machines, it is possible
11272 to get a list of the machine types in use thanks to the DMI
11273 information extracted from each machine. The script to do so is
11274 included in the sitesummary package, and here is example output from
11275 the Skolelinux build servers:
</p
>
11277 <blockquote
><pre
>
11278 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
11280 Dell Computer Corporation
1
11283 eserver xSeries
345 -[
8670M1X]-
1
11287 </pre
></blockquote
>
11289 <p
>The quality of the report depend on the quality of the DMI tables
11290 provided in each machine. Here there are Intel machines without model
11291 information listed with Intel as vendor and no model, and virtual Xen
11292 machines listed as [no-dmi-info]. One can add -l as a command line
11293 option to list the individual machines.
</p
>
11295 <p
>A larger list is
11296 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
11297 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
11298 provide the basic sitesummary report publicly. In their report there
11299 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
11300 their machines, and as sitesummary is available in both distributions,
11301 it is trivial to get all of them to report to the same central
11302 collector.
</p
>
11307 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
11308 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
11309 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</guid>
11310 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
11311 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
11312 start at boot when an NVidia video card is used is handled. The
11313 problem seem to be that the nvidia X.org driver uses a long time to
11314 initialize, and this duration is longer than kdm is configured to
11317 <p
>I came across two bugs related to this issue,
11318 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
11319 against initscripts and passed on to nvidia-glx when it became obvious
11320 that the nvidia drivers were involved, and
11321 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
11322 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
11324 <p
>To me, it seem that no-one is interested in actually solving the
11325 problem nvidia video card owners experience and make sure the Debian
11326 distribution work out of the box for these users. The nvidia driver
11327 maintainers expect kdm to be set up to wait longer, while kdm expect
11328 the nvidia driver maintainers to fix the driver to start faster, and
11329 while they wait for each other I guess the users end up switching to a
11330 distribution that work for them. I have no idea what the solution is,
11331 but I am pretty sure that waiting for each other is not it.
</p
>
11333 <p
>I wonder why we end up handling bugs this way.
</p
>
11338 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
11339 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
11340 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
11341 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
11342 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
11343 The feature seem to hold up pretty well, but three fairly serious
11344 issues are known and should be solved:
11346 <p
><ul
>
11348 <li
>The wicd package seen to
11349 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
11350 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
11351 parallel booting is enabled. No idea why, but the wicd maintainer
11352 seem to be on the case.
</li
>
11354 <li
>The nvidia X driver seem to
11355 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
11356 triggered more easily when parallel booting is in effect. The
11357 maintainer is on the case.
</li
>
11359 <li
>The sysv-rc package fail to properly enable dependency based boot
11360 sequencing (the shutdown is broken) when old file-rc users
11361 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
11362 sysv-rc. One way to solve it would be for file-rc to create
11363 /etc/init.d/.legacy-bootordering, and another is to try to make
11364 sysv-rc more robust. Will investigate some more and probably upload a
11365 workaround in sysv-rc to help those trying to move from file-rc to
11366 sysv-rc get a working shutdown.
</li
>
11368 </ul
></p
>
11370 <p
>All in all not many surprising issues, and all of them seem
11371 solvable before Squeeze is released. In addition to these there are
11372 some packages with bugs in their dependencies and run level settings,
11373 which I expect will be fixed in a reasonable time span.
</p
>
11375 <p
>If you report any problems with dependencies in init.d scripts to
11376 the BTS, please usertag the report to get it to show up at
11377 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
11378 list of usertagged bugs related to this
</a
>.
</p
>
11380 <p
>Update: Correct bug number to file-rc issue.
</p
>
11385 <title>More flexible firmware handling in debian-installer
</title>
11386 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
11387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
11388 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
11389 <description><p
>After a long break from debian-installer development, I finally
11390 found time today to return to the project. Having to spend less time
11391 working dependency based boot in debian, as it is almost complete now,
11392 definitely helped freeing some time.
</p
>
11394 <p
>A while back, I ran into a problem while working on Debian Edu. We
11395 include some firmware packages on the Debian Edu CDs, those needed to
11396 get disk and network controllers working. Without having these
11397 firmware packages available during installation, it is impossible to
11398 install Debian Edu on the given machine, and because our target group
11399 are non-technical people, asking them to provide firmware packages on
11400 an external medium is a support pain. Initially, I expected it to be
11401 enough to include the firmware packages on the CD to get
11402 debian-installer to find and use them. This proved to be wrong.
11403 Next, I hoped it was enough to symlink the relevant firmware packages
11404 to some useful location on the CD (tried /cdrom/ and
11405 /cdrom/firmware/). This also proved to not work, and at this point I
11406 found time to look at the debian-installer code to figure out what was
11407 going to work.
</p
>
11409 <p
>The firmware loading code is in the hw-detect package, and a closer
11410 look revealed that it would only look for firmware packages outside
11411 the installation media, so the CD was never checked for firmware
11412 packages. It would only check USB sticks, floppies and other
11413 "external
" media devices. Today I changed it to also look in the
11414 /cdrom/firmware/ directory on the mounted CD or DVD, which should
11415 solve the problem I ran into with Debian edu. I also changed it to
11416 look in /firmware/, to make sure the installer also find firmware
11417 provided in the initrd when booting the installer via PXE, to allow us
11418 to provide the same feature in the PXE setup included in Debian
11421 <p
>To make sure firmware deb packages with a license questions are not
11422 activated without asking if the license is accepted, I extended
11423 hw-detect to look for preinst scripts in the firmware packages, and
11424 run these before activating the firmware during installation. The
11425 license question is asked using debconf in the preinst, so this should
11426 solve the issue for the firmware packages I have looked at so far.
</p
>
11428 <p
>If you want to discuss the details of these features, please
11429 contact us on debian-boot@lists.debian.org.
</p
>
11434 <title>Parallellized boot is now the default in Debian/unstable
</title>
11435 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
11436 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
11437 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
11438 <description><p
>Since this evening, parallel booting is the default in
11439 Debian/unstable for machines using dependency based boot sequencing.
11440 Apparently the testing of concurrent booting has been wider than
11441 expected, if I am to believe the
11442 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
11443 on debian-devel@
</a
>, and I concluded a few days ago to move forward
11444 with the feature this weekend, to give us some time to detect any
11445 remaining problems before Squeeze is frozen. If serious problems are
11446 detected, it is simple to change the default back to sequential boot.
11447 The upload of the new sysvinit package also activate a new upstream
11450 More information about
11451 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11452 based boot sequencing
</a
> is available from the Debian wiki. It is
11453 currently possible to disable parallel booting when one run into
11454 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
11456 <blockquote
><pre
>
11458 </pre
></blockquote
>
11460 <p
>If you report any problems with dependencies in init.d scripts to
11461 the BTS, please usertag the report to get it to show up at
11462 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
11463 list of usertagged bugs related to this
</a
>.
</p
>
11468 <title>Sitesummary tip: Listing MAC address of all clients
</title>
11469 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
11470 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
11471 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
11472 <description><p
>In the recent Debian Edu versions, the
11473 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
11474 system
</a
> is used to keep track of the machines in the school
11475 network. Each machine will automatically report its status to the
11476 central server after boot and once per night. The network setup is
11477 also reported, and using this information it is possible to get the
11478 MAC address of all network interfaces in the machines. This is useful
11479 to update the DHCP configuration.
</p
>
11481 <p
>To give some idea how to use sitesummary, here is a one-liner to
11482 ist all MAC addresses of all machines reporting to sitesummary. Run
11483 this on the collector host:
</p
>
11485 <blockquote
><pre
>
11486 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
11487 </pre
></blockquote
>
11489 <p
>This will list all MAC addresses assosiated with all machine, one
11490 line per machine and with space between the MAC addresses.
</p
>
11492 <p
>To allow system administrators easier job at adding static DHCP
11493 addresses for hosts, it would be possible to extend this to fetch
11494 machine information from sitesummary and update the DHCP and DNS
11495 tables in LDAP using this information. Such tool is unfortunately not
11496 written yet.
</p
>
11501 <title>systemd, an interesting alternative to upstart
</title>
11502 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
11503 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
11504 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
11505 <description><p
>The last few days a new boot system called
11506 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
11508 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
11510 to the free software world. I have not yet had time to play around
11511 with it, but it seem to be a very interesting alternative to
11512 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
11513 a good alternative for Debian when we are able to switch to an event
11514 based boot system. Tollef is
11515 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
11516 systemd into Debian, and I look forward to seeing how well it work. I
11517 like the fact that systemd handles init.d scripts with dependency
11518 information natively, allowing them to run in parallel where upstart
11519 at the moment do not.
</p
>
11521 <p
>Unfortunately do systemd have the same problem as upstart regarding
11522 platform support. It only work on recent Linux kernels, and also need
11523 some new kernel features enabled to function properly. This means
11524 kFreeBSD and Hurd ports of Debian will need a port or a different boot
11525 system. Not sure how that will be handled if systemd proves to be the
11526 way forward.
</p
>
11528 <p
>In the mean time, based on the
11529 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
11530 on debian-devel@
</a
> regarding parallel booting in Debian, I have
11531 decided to enable full parallel booting as the default in Debian as
11532 soon as possible (probably this weekend or early next week), to see if
11533 there are any remaining serious bugs in the init.d dependencies. A
11534 new version of the sysvinit package implementing this change is
11535 already in experimental. If all go well, Squeeze will be released
11536 with parallel booting enabled by default.
</p
>
11541 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
11542 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
11543 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
11544 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
11545 <description><p
>These days, the init.d script dependencies in Squeeze are quite
11546 complete, so complete that it is actually possible to run all the
11547 init.d scripts in parallell based on these dependencies. If you want
11548 to test your Squeeze system, make sure
11549 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11550 based boot sequencing
</a
> is enabled, and add this line to
11551 /etc/default/rcS:
</p
>
11553 <blockquote
><pre
>
11554 CONCURRENCY=makefile
11555 </pre
></blockquote
>
11557 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
11558 scripts in parallel using the dependency information stored in
11559 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11560 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11561 to try to start the kdm and gdm scripts as early as possible, and will
11562 start the facilities required by kdm or gdm as early as possible to
11563 make this happen.
</p
>
11565 <p
>Give it a try, and see if you like the result. If some services
11566 fail to start properly, it is most likely because they have incomplete
11567 init.d script dependencies in their startup script (or some of their
11568 dependent scripts have incomplete dependencies). Report bugs and get
11569 the package maintainers to fix it. :)
</p
>
11571 <p
>Running scripts in parallel could be the default in Debian when we
11572 manage to get the init.d script dependencies complete and correct. I
11573 expect we will get there in Squeeze+
1, if we get manage to test and
11574 fix the remaining issues.
</p
>
11576 <p
>If you report any problems with dependencies in init.d scripts to
11577 the BTS, please usertag the report to get it to show up at
11578 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
11579 list of usertagged bugs related to this
</a
>.
</p
>
11584 <title>Debian has switched to dependency based boot sequencing
</title>
11585 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
11586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
11587 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
11588 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
11589 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
11590 have been migrated to using dependency based boot sequencing. This
11591 conclude work me and others have been doing for the last three days.
11592 It feels great to see this finally part of the default Debian
11593 installation. Now we just need to weed out the last few problems that
11594 are bound to show up, to get everything ready for Squeeze.
</p
>
11596 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
11597 fixing the more fundamental problem of handing the event based
11598 non-predictable kernel in the early boot.
</p
>
11603 <title>Taking over sysvinit development
</title>
11604 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
11605 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
11606 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
11607 <description><p
>After several years of frustration with the lack of activity from
11608 the existing sysvinit upstream developer, I decided a few weeks ago to
11609 take over the package and become the new upstream. The number of
11610 patches to track for the Debian package was becoming a burden, and the
11611 lack of synchronization between the distribution made it hard to keep
11612 the package up to date.
</p
>
11614 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11615 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
11616 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
11617 and Fedora), based on the patches currently in use in these
11618 distributions. We Debian maintainers plan to move to this tarball as
11619 the new upstream as soon as we find time to do the merge. Since the
11620 new tarball was created, we agreed with Werner at SuSe to make a new
11621 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
11622 development there. The project is registered and currently waiting
11623 for approval by the Savannah administrators, and as soon as it is
11624 approved, we will import the old versions from svn and continue
11625 working on the future release.
</p
>
11627 <p
>It is a bit ironic that this is done now, when some of the involved
11628 distributions are moving to upstart as a syvinit replacement.
</p
>
11633 <title>Debian boots quicker and quicker
</title>
11634 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
11635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
11636 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
11637 <description><p
>I spent Monday and tuesday this week in London with a lot of the
11638 people involved in the boot system on Debian and Ubuntu, to see if we
11639 could find more ways to speed up the boot system. This was an Ubuntu
11641 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
11642 gathering
</a
>. It was quite productive. We also discussed the future
11643 of boot systems, and ways to handle the increasing number of boot
11644 issues introduced by the Linux kernel becoming more and more
11645 asynchronous and event base. The Ubuntu approach using udev and
11646 upstart might be a good way forward. Time will show.
</p
>
11648 <p
>Anyway, there are a few ways at the moment to speed up the boot
11649 process in Debian. All of these should be applied to get a quick
11654 <li
>Use dash as /bin/sh.
</li
>
11656 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
11657 clock is in UTC.
</li
>
11659 <li
>Install and activate the insserv package to enable
11660 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11661 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
11665 These points are based on the Google summer of code work done by
11666 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
11667 Villegas
</a
>.
11669 <p
>Support for makefile-style concurrency during boot was uploaded to
11670 unstable yesterday. When we tested it, we were able to cut
6 seconds
11671 from the boot sequence. It depend on very correct dependency
11672 declaration in all init.d scripts, so I expect us to find edge cases
11673 where the dependences in some scripts are slightly wrong when we start
11674 using this.
</p
>
11676 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11677 introduced by Raphael Geissert today, one that could affect the
11678 startup speed as well. Instead of starting some scripts concurrently
11679 from rcS.d/ and another set of scripts from rc2.d/, it would be
11680 possible to run a of them in the same process. A quick way to test
11681 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
11682 insserv
'. Will need to test if that work. :)
</p
>
11687 <title>BSAs påstander om piratkopiering møter motstand
</title>
11688 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
11689 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
11690 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
11691 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
11692 programvareselskapene som Microsoft og Apple, publisert en rapport der
11693 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11694 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11696 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
11697 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
11698 dagene. Et spesielt interessant kommentar fra Sverige,
11699 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
11700 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
11703 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
11704 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11705 företag.
"Man bör nog kanske inte se de här siffrorna som helt
11706 exakta
", säger BSAs Sverigechef John Hugosson.
11707 </blockquote
>
11709 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
11710 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
11711 piracy figures need a shot of reality
</a
> og
<a
11712 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
11713 Copyright Treaty Work?
</a
></p
>
11715 <p
>Fant lenkene via
<a
11716 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
11717 på Slashdot
</a
>.
</p
>
11722 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
11723 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
11724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
11725 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
11726 <description><p
>Kom over
11727 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
11728 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11729 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11730 jobber til daglig. En rask opptelling forteller meg at vi har
490
11731 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
11732 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
11733 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
11738 <title>Kryptert harddisk - naturligvis
</title>
11739 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
11740 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
11741 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
11742 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
11743 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
11744 når en tar tap av arbeidstid, fortrolige dokumenter,
11745 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11746 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11747 til at jeg har kryptert harddisken på både kontormaskinen og min
11748 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11749 komme på avveie, den første informasjon relatert til jobben min ved
11750 Universitetet i Oslo, og den andre relatert til blant annet
11751 foreningsarbeide. Kryptering av diskene gjør at det er lite
11752 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11753 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11754 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11755 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11756 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11757 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11758 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11759 det er gjort slik jeg gjør det er minimale, og gevinstene er
11760 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11761 maskinen reinstalleres og alt er tapt.
</p
>
11763 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11764 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11765 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11766 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11767 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11768 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11769 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11770 betydelige.
</p
>
11775 <title>Two projects that have improved the quality of free software a lot
</title>
11776 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
11777 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
11778 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
11779 <description><p
>There are two software projects that have had huge influence on the
11780 quality of free software, and I wanted to mention both in case someone
11781 do not yet know them.
</p
>
11783 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
11784 tool to detect and expose errors in the memory handling of programs.
11785 It is easy to use, all one need to do is to run
'valgrind program
',
11786 and it will report any problems on stdout. It is even better if the
11787 program include debug information. With debug information, it is able
11788 to report the source file name and line number where the problem
11789 occurs. It can report things like
'reading past memory block in file
11790 X line N, the memory block was allocated in file Y, line M
', and
11791 'using uninitialised value in control logic
'. This tool has made it
11792 trivial to investigate reproducible crash bugs in programs, and have
11793 reduced the number of this kind of bugs in free software a lot.
11795 <p
>The second one is
11796 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
11797 a source code checker. It is able to process the source of a program
11798 and find problems in the logic without running the program. It
11799 started out as the Stanford Checker and became well known when it was
11800 used to find bugs in the Linux kernel. It is now a commercial tool
11801 and the company behind it is running
11802 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
11803 free software community, where a lot of free software projects get
11804 their source checked for free. Several thousand defects have been
11805 found and fixed so far. It can find errors like
'lock L taken in file
11806 X line N is never released if exiting in line M
', or
'the code in file
11807 Y lines O to P can never be executed
'. The projects included in the
11808 community service project have managed to get rid of a lot of
11809 reliability problems thanks to Coverity.
</p
>
11811 <p
>I believe tools like this, that are able to automatically find
11812 errors in the source, are vital to improve the quality of software and
11813 make sure we can get rid of the crashing and failing software we are
11814 surrounded by today.
</p
>
11819 <title>No patch is not better than a useless patch
</title>
11820 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
11821 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
11822 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
11823 <description><p
>Julien Blache
11824 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
11825 patch is better than a useless patch
</a
>. I completely disagree, as a
11826 patch allow one to discuss a concrete and proposed solution, and also
11827 prove that the issue at hand is important enough for someone to spent
11828 time on fixing it. No patch do not provide any of these positive
11829 properties.
</p
>
11834 <title>Standardize on protocols and formats, not vendors and applications
</title>
11835 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
11836 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
11837 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
11838 <description><p
>Where I work at the University of Oslo, one decision stand out as a
11839 very good one to form a long lived computer infrastructure. It is the
11840 simple one, lost by many in todays computer industry: Standardize on
11841 open network protocols and open exchange/storage formats, not applications.
11842 Applications come and go, while protocols and files tend to stay, and
11843 thus one want to make it easy to change application and vendor, while
11844 avoiding conversion costs and locking users to a specific platform or
11845 application.
</p
>
11847 <p
>This approach make it possible to replace the client applications
11848 independently of the server applications. One can even allow users to
11849 use several different applications as long as they handle the selected
11850 protocol and format. In the normal case, only one client application
11851 is recommended and users only get help if they choose to use this
11852 application, but those that want to deviate from the easy path are not
11853 blocked from doing so.
</p
>
11855 <p
>It also allow us to replace the server side without forcing the
11856 users to replace their applications, and thus allow us to select the
11857 best server implementation at any moment, when scale and resouce
11858 requirements change.
</p
>
11860 <p
>I strongly recommend standardizing - on open network protocols and
11861 open formats, but I would never recommend standardizing on a single
11862 application that do not use open network protocol or open formats.
</p
>
11867 <title>Returning from Skolelinux developer gathering
</title>
11868 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
11869 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
11870 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
11871 <description><p
>I
'm sitting on the train going home from this weekends Debian
11872 Edu/Skolelinux development gathering. I got a bit done tuning the
11873 desktop, and looked into the dynamic service location protocol
11874 implementation avahi. It look like it could be useful for us. Almost
11875 30 people participated, and I believe it was a great environment to
11876 get to know the Skolelinux system. Walter Bender, involved in the
11877 development of the Sugar educational platform, presented his stuff and
11878 also helped me improve my OLPC installation. He also showed me that
11879 his Turtle Art application can be used in standalone mode, and we
11880 agreed that I would help getting it packaged for Debian. As a
11881 standalone application it would be great for Debian Edu. We also
11882 tried to get the video conferencing working with two OLPCs, but that
11883 proved to be too hard for us. The application seem to need more work
11884 before it is ready for me. I look forward to getting home and relax
11890 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
11891 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
11892 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
11893 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
11894 <description><p
>The state of standardized LDAP schemas on Linux is far from
11895 optimal. There is RFC
2307 documenting one way to store NIS maps in
11896 LDAP, and a modified version of this normally called RFC
2307bis, with
11897 some modifications to be compatible with Active Directory. The RFC
11898 specification handle the content of a lot of system databases, but do
11899 not handle DNS zones and DHCP configuration.
</p
>
11901 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
11902 we would like to store information about users, SMB clients/hosts,
11903 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11904 and LTSP configuration in LDAP. These objects have a lot in common,
11905 but with the current LDAP schemas it is not possible to have one
11906 object per entity. For example, one need to have at least three LDAP
11907 objects for a given computer, one with the SMB related stuff, one with
11908 DNS information and another with DHCP information. The schemas
11909 provided for DNS and DHCP are impossible to combine into one LDAP
11910 object. In addition, it is impossible to implement quick queries for
11911 netgroup membership, because of the way NIS triples are implemented.
11912 It just do not scale. I believe it is time for a few RFC
11913 specifications to cleam up this mess.
</p
>
11915 <p
>I would like to have one LDAP object representing each computer in
11916 the network, and this object can then keep the SMB (ie host key), DHCP
11917 (mac address/name) and DNS (name/IP address) settings in one place.
11918 It need to be efficently stored to make sure it scale well.
</p
>
11920 <p
>I would also like to have a quick way to map from a user or
11921 computer and to the net group this user or computer is a member.
</p
>
11923 <p
>Active Directory have done a better job than unix heads like myself
11924 in this regard, and the unix side need to catch up. Time to start a
11925 new IETF work group?
</p
>
11930 <title>Endelig er Debian Lenny gitt ut
</title>
11931 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
11932 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
11933 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
11934 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
11935 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
11936 Et langt steg videre for Debian-prosjektet, og en rekke nye
11937 programpakker blir nå tilgjengelig for de av oss som bruker den
11938 stabile utgaven av Debian. Neste steg er nå å få
11939 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
11940 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
11941 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11942 slippes løs på skolene. Takk til alle debian-utviklerne som har
11943 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11944 bootsekvens tilgjengelig i stabil utgave, vha pakken
11945 <tt
>insserv
</tt
>.
</p
>
11950 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
11951 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
11952 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
11953 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
11954 <description><p
>This weekend we had a small developer gathering for Debian Edu in
11955 Oslo. Most of Saturday was used for the general assemly for the
11956 member organization, but the rest of the weekend I used to tune the
11957 LTSP installation. LTSP now work out of the box on the
10-network.
11958 Acer Aspire One proved to be a very nice thin client, with both
11959 screen, mouse and keybard in a small box. Was working on getting the
11960 diskless workstation setup configured out of the box, but did not
11961 finish it before the weekend was up.
</p
>
11963 <p
>Did not find time to look at the
4 VGA cards in one box we got from
11964 the Brazilian group, so that will have to wait for the next
11965 development gathering. Would love to have the Debian Edu installer
11966 automatically detect and configure a multiseat setup when it find one
11967 of these cards.
</p
>
11972 <title>The sorry state of multimedia browser plugins in Debian
</title>
11973 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
11974 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
11975 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
11976 <description><p
>Recently I have spent some time evaluating the multimedia browser
11977 plugins available in Debian Lenny, to see which one we should use by
11978 default in Debian Edu. We need an embedded video playing plugin with
11979 control buttons to pause or stop the video, and capable of streaming
11980 all the multimedia content available on the web. The test results and
11981 notes are available on
11982 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
11983 Debian wiki
</a
>. I was surprised how few of the plugins are able to
11984 fill this need. My personal video player favorite, VLC, has a really
11985 bad plugin which fail on a lot of the test pages. A lot of the MIME
11986 types I would expect to work with any free software player (like
11987 video/ogg), just do not work. And simple formats like the
11988 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
11989 totem and vlc plugins. I hope the situation will improve soon. No
11990 wonder sites use the proprietary Adobe flash to play video.
</p
>
11992 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
11993 be the only one fitting our needs. :/
</p
>