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>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
11 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
13 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
14 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
16 <p
>I finally received a copy of the Norwegian Bokmål edition of
17 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
18 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
19 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
20 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
21 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
22 price. The book is also available for download in electronic form as
23 PDF, EPUB and Mobipocket, as can be
24 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
25 as a web page
</a
>.
</p
>
27 <p
>This is the second book I publish (the first was the book
28 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
30 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
31 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
33 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
34 Bokmål
</a
>), and I am very excited to finally wrap up this
36 "<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
37 for Debian-administratoren
</a
>" will be well received.
</p
>
42 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
43 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
44 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
45 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
46 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
47 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
48 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
49 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
50 på om den fri oversetterløsningen
51 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
52 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
54 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
57 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
58 rolle og muligheter til å håndtere internasjonale utfordringer, som
59 for eksempel flykningekrisen.
</p
>
61 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
64 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
65 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
70 <p
>Dette oversetter Apertium slik:
</p
>
73 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
74 andre aktørar og høve til å handtera internasjonale utfordringar, som
75 til dømes *flykningekrisen.
</p
>
77 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
81 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
82 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
87 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
88 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
89 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
90 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
91 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
92 det er kanskje flisespikking. Det understreker vel bare at det alltid
93 trengs korrekturlesning etter automatisk oversettelse.
</p
>
98 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
99 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
101 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
102 <description><p
>Over the years, administrating thousand of NFS mounting linux
103 computers at the time, I often needed a way to detect if the machine
104 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
105 file or directory affected by the hang, the process (and possibly the
106 shell) will hang too. So you want to be able to detect this without
107 risking the detection process getting stuck too. It has not been
108 obvious how to do this. When the hang has lasted a while, it is
109 possible to find messages like these in dmesg:
</p
>
111 <p
><blockquote
>
112 nfs: server nfsserver not responding, still trying
113 <br
>nfs: server nfsserver OK
114 </blockquote
></p
>
116 <p
>It is hard to know if the hang is still going on, and it is hard to
117 be sure looking in dmesg is going to work. If there are lots of other
118 messages in dmesg the lines might have rotated out of site before they
119 are noticed.
</p
>
121 <p
>While reading through the nfs client implementation in linux kernel
122 code, I came across some statistics that seem to give a way to detect
123 it. The om_timeouts sunrpc value in the kernel will increase every
124 time the above log entry is inserted into dmesg. And after digging a
125 bit further, I discovered that this value show up in
126 /proc/self/mountstats on Linux.
</p
>
128 <p
>The mountstats content seem to be shared between files using the
129 same file system context, so it is enough to check one of the
130 mountstats files to get the state of the mount point for the machine.
131 I assume this will not show lazy umounted NFS points, nor NFS mount
132 points in a different process context (ie with a different filesystem
133 view), but that does not worry me.
</p
>
135 <p
>The content for a NFS mount point look similar to this:
</p
>
137 <p
><blockquote
><pre
>
139 device /dev/mapper/Debian-var mounted on /var with fstype ext3
140 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
141 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
143 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
144 sec: flavor=
1,pseudoflavor=
1
145 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
146 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
147 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
148 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
150 NULL:
0 0 0 0 0 0 0 0
151 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
152 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
153 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
154 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
155 READLINK:
125 125 0 20472 18620 0 1112 1118
156 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
157 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
158 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
159 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
160 SYMLINK:
903 903 0 233428 245488 6 5865 5917
161 MKNOD:
80 80 0 20148 21760 0 299 304
162 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
163 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
164 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
165 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
166 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
167 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
168 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
169 FSINFO:
2 2 0 232 328 0 1 1
170 PATHCONF:
1 1 0 116 140 0 0 0
171 COMMIT:
0 0 0 0 0 0 0 0
173 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
175 </pre
></blockquote
></p
>
177 <p
>The key number to look at is the third number in the per-op list.
178 It is the number of NFS timeouts experiences per file system
179 operation. Here
22 write timeouts and
5 access timeouts. If these
180 numbers are increasing, I believe the machine is experiencing NFS
181 hang. Unfortunately the timeout value do not start to increase right
182 away. The NFS operations need to time out first, and this can take a
183 while. The exact timeout value depend on the setup. For example the
184 defaults for TCP and UDP mount points are quite different, and the
185 timeout value is affected by the soft, hard, timeo and retrans NFS
186 mount options.
</p
>
188 <p
>The only way I have been able to get working on Debian and RedHat
189 Enterprise Linux for getting the timeout count is to peek in /proc/.
191 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
192 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
193 command can be used to get these timeout values. But this do not work
194 on Linux, as far as I can tell. I
195 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
196 but have not seen any replies yet.
</p
>
198 <p
>Is there a better way to figure out if a Linux NFS client is
199 experiencing NFS hangs? Is there a way to detect which processes are
200 affected? Is there a way to get the NFS mount going quickly once the
201 network problem causing the NFS hang has been cleared? I would very
202 much welcome some clues, as we regularly run into NFS hangs.
</p
>
207 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
208 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
209 <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>
210 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
211 <description><p
>For almost a year now, we have been working on making a Norwegian
212 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
213 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
214 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
215 we are working on the proof reading to ensure consistent language and
216 use of correct computer science terms. The plan is to make the book
217 available on paper, as well as in electronic form. For that to
218 happen, the proof reading must be completed and all the figures need
219 to be translated. If you want to help out, get in touch.
</p
>
221 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
223 fresh PDF edition
</a
> in A4 format (the final book will have smaller
224 pages) of the book created every morning is available for
225 proofreading. If you find any errors, please
226 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
227 Weblate and correct the error
</a
>. The
228 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
229 of the translation including figures
</a
> is a useful source for those
230 provide Norwegian bokmål screen shots and figures.
</p
>
235 <title>Unlimited randomness with the ChaosKey?
</title>
236 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
237 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
238 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
239 <description><p
>A few days ago I ordered a small batch of
240 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
241 USB dongle for generating entropy created by Bdale Garbee and Keith
242 Packard. Yesterday it arrived, and I am very happy to report that it
243 work great! According to its designers, to get it to work out of the
244 box, you need the Linux kernel version
4.1 or later. I tested on a
245 Debian Stretch machine (kernel version
4.9), and there it worked just
246 fine, increasing the available entropy very quickly. I wrote a small
247 test oneliner to test. It first print the current entropy level,
248 drain /dev/random, and then print the entropy level for five seconds.
249 Here is the situation without the ChaosKey inserted:
</p
>
251 <blockquote
><pre
>
252 % cat /proc/sys/kernel/random/entropy_avail; \
253 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
254 for n in $(seq
1 5); do \
255 cat /proc/sys/kernel/random/entropy_avail; \
261 28 byte kopiert,
0,
000264565 s,
106 kB/s
268 </pre
></blockquote
>
270 <p
>The entropy level increases by
3-
4 every second. In such case any
271 application requiring random bits (like a HTTPS enabled web server)
272 will halt and wait for more entrpy. And here is the situation with
273 the ChaosKey inserted:
</p
>
275 <blockquote
><pre
>
276 % cat /proc/sys/kernel/random/entropy_avail; \
277 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
278 for n in $(seq
1 5); do \
279 cat /proc/sys/kernel/random/entropy_avail; \
285 104 byte kopiert,
0,
000487647 s,
213 kB/s
292 </pre
></blockquote
>
294 <p
>Quite the difference. :) I bought a few more than I need, in case
295 someone want to buy one here in Norway. :)
</p
>
297 <p
>Update: The dongle was presented at Debconf last year. You might
298 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
299 recording illuminating
</a
>. It explains exactly what the source of
300 randomness is, if you are unable to spot it from the schema drawing
301 available from the ChaosKey web site linked at the start of this blog
307 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
308 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
309 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
310 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
311 <description><p
>Did you ever wonder where the web trafic really flow to reach the
312 web servers, and who own the network equipment it is flowing through?
313 It is possible to get a glimpse of this from using traceroute, but it
314 is hard to find all the details. Many years ago, I wrote a system to
315 map the Norwegian Internet (trying to figure out if our plans for a
316 network game service would get low enough latency, and who we needed
317 to talk to about setting up game servers close to the users. Back
318 then I used traceroute output from many locations (I asked my friends
319 to run a script and send me their traceroute output) to create the
320 graph and the map. The output from traceroute typically look like
324 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
325 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
326 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
327 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
328 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
329 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
330 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
331 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
335 </pre
></p
>
337 <p
>This show the DNS names and IP addresses of (at least some of the)
338 network equipment involved in getting the data traffic from me to the
339 www.stortinget.no server, and how long it took in milliseconds for a
340 package to reach the equipment and return to me. Three packages are
341 sent, and some times the packages do not follow the same path. This
342 is shown for hop
5, where three different IP addresses replied to the
343 traceroute request.
</p
>
345 <p
>There are many ways to measure trace routes. Other good traceroute
346 implementations I use are traceroute (using ICMP packages) mtr (can do
347 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
348 traceroute and a lot of other capabilities). All of them are easily
349 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
351 <p
>This time around, I wanted to know the geographic location of
352 different route points, to visualize how visiting a web page spread
353 information about the visit to a lot of servers around the globe. The
354 background is that a web site today often will ask the browser to get
355 from many servers the parts (for example HTML, JSON, fonts,
356 JavaScript, CSS, video) required to display the content. This will
357 leak information about the visit to those controlling these servers
358 and anyone able to peek at the data traffic passing by (like your ISP,
359 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
361 <p
>Lets pick an example, the Norwegian parliament web site
362 www.stortinget.no. It is read daily by all members of parliament and
363 their staff, as well as political journalists, activits and many other
364 citizens of Norway. A visit to the www.stortinget.no web site will
365 ask your browser to contact
8 other servers: ajax.googleapis.com,
366 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
367 stats.g.doubleclick.net, www.google-analytics.com,
368 www.googletagmanager.com and www.netigate.se. I extracted this by
369 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
370 Stortinget web page and tell me all the URLs PhantomJS downloaded to
371 render the page (in HAR format using
372 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
373 netsniff example
</a
>. I am very grateful to Gorm for showing me how
374 to do this). My goal is to visualize network traces to all IP
375 addresses behind these DNS names, do show where visitors personal
376 information is spread when visiting the page.
</p
>
378 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
379 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
>
381 <p
>When I had a look around for options, I could not find any good
382 free software tools to do this, and decided I needed my own traceroute
383 wrapper outputting KML based on locations looked up using GeoIP. KML
384 is easy to work with and easy to generate, and understood by several
385 of the GIS tools I have available. I got good help from by NUUG
386 colleague Anders Einar with this, and the result can be seen in
387 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
388 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
389 free GeoIP databases I could find (and the for-pay databases my
390 friends had access to) is not up to the task. The IP addresses of
391 central Internet infrastructure would typically be placed near the
392 controlling companies main office, and not where the router is really
393 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
394 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
396 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
397 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
>
399 <p
>I also had a look at the visual traceroute graph created by
400 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
401 showing IP network ownership (aka AS owner) for the IP address in
403 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
404 graph display a lot of useful information about the traceroute in SVG
405 format
</a
>, and give a good indication on who control the network
406 equipment involved, but it do not include geolocation. This graph
407 make it possible to see the information is made available at least for
408 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
409 3 Communications and NetDNA.
</p
>
411 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
412 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
>
414 <p
>In the process, I came across the
415 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
416 Salim Gasmi. Its methology of combining guesses based on DNS names,
417 various location databases and finally use latecy times to rule out
418 candidate locations seemed to do a very good job of guessing correct
419 geolocation. But it could only do one trace at the time, did not have
420 a sensor in Norway and did not make the geolocations easily available
421 for postprocessing. So I contacted the developer and asked if he
422 would be willing to share the code (he refused until he had time to
423 clean it up), but he was interested in providing the geolocations in a
424 machine readable format, and willing to set up a sensor in Norway. So
425 since yesterday, it is possible to run traces from Norway in this
426 service thanks to a sensor node set up by
427 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
428 trace in KML format for further processing.
</p
>
430 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
431 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
>
433 <p
>Here we can see a lot of trafic passes Sweden on its way to
434 Denmark, Germany, Holland and Ireland. Plenty of places where the
435 Snowden confirmations verified the traffic is read by various actors
436 without your best interest as their top priority.
</p
>
438 <p
>Combining KML files is trivial using a text editor, so I could loop
439 over all the hosts behind the urls imported by www.stortinget.no and
440 ask for the KML file from GeoTraceroute, and create a combined KML
441 file with all the traces (unfortunately only one of the IP addresses
442 behind the DNS name is traced this time. To get them all, one would
443 have to request traces using IP number instead of DNS names from
444 GeoTraceroute). That might be the next step in this project.
</p
>
446 <p
>Armed with these tools, I find it a lot easier to figure out where
447 the IP traffic moves and who control the boxes involved in moving it.
448 And every time the link crosses for example the Swedish border, we can
449 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
450 Britain and NSA in USA and cables around the globe. (Hm, what should
451 we tell them? :) Keep that in mind if you ever send anything
452 unencrypted over the Internet.
</p
>
454 <p
>PS: KML files are drawn using
455 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
456 Rublev
<a/
>, as it was less cluttered than the local Linux application
457 Marble. There are heaps of other options too.
</p
>
459 <p
>As usual, if you use Bitcoin and want to show your support of my
460 activities, please send Bitcoin donations to my address
461 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
466 <title>Appstream just learned how to map hardware to packages too!
</title>
467 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
468 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
469 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
470 <description><p
>I received a very nice Christmas present today. As my regular
471 readers probably know, I have been working on the
472 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
473 system
</a
> for many years. The goal of the Isenkram system is to make
474 it easier for users to figure out what to install to get a given piece
475 of hardware to work in Debian, and a key part of this system is a way
476 to map hardware to packages. Isenkram have its own mapping database,
477 and also uses data provided by each package using the AppStream
478 metadata format. And today,
479 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
480 Debian learned to look up hardware the same way Isenkram is doing it,
481 ie using fnmatch():
</p
>
484 % appstreamcli what-provides modalias \
485 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
486 Identifier: pymissile [generic]
488 Summary: Control original Striker USB Missile Launcher
490 % appstreamcli what-provides modalias usb:v0694p0002d0000
491 Identifier: libnxt [generic]
493 Summary: utility library for talking to the LEGO Mindstorms NXT brick
496 Identifier: t2n [generic]
498 Summary: Simple command-line tool for Lego NXT
501 Identifier: python-nxt [generic]
503 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
506 Identifier: nbc [generic]
508 Summary: C compiler for LEGO Mindstorms NXT bricks
511 </pre
></p
>
513 <p
>A similar query can be done using the combined AppStream and
514 Isenkram databases using the isenkram-lookup tool:
</p
>
517 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
519 % isenkram-lookup usb:v0694p0002d0000
525 </pre
></p
>
527 <p
>You can find modalias values relevant for your machine using
528 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
530 <p
>If you want to make this system a success and help Debian users
531 make the most of the hardware they have, please
532 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
533 AppStream metadata for your package following the guidelines
</a
>
534 documented in the wiki. So far only
11 packages provide such
535 information, among the several hundred hardware specific packages in
536 Debian. The Isenkram database on the other hand contain
101 packages,
537 mostly related to USB dongles. Most of the packages with hardware
538 mapping in AppStream are LEGO Mindstorms related, because I have, as
539 part of my involvement in
540 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
541 team
</a
> given priority to making sure LEGO users get proposed the
542 complete set of packages in Debian for that particular hardware. The
543 team also got a nice Christmas present today. The
544 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
545 package
</a
> made it into Debian. With this package in place, it is
546 now possible to use the LEGO Mindstorms NXT unit with only free
547 software, as the nxt-firmware package contain the source and firmware
548 binaries for the NXT brick.
</p
>
550 <p
>As usual, if you use Bitcoin and want to show your support of my
551 activities, please send Bitcoin donations to my address
552 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
557 <title>Isenkram updated with a lot more hardware-package mappings
</title>
558 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
560 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
561 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
562 system
</a
> I wrote two years ago to make it easier in Debian to find
563 and install packages to get your hardware dongles to work, is still
564 going strong. It is a system to look up the hardware present on or
565 connected to the current system, and map the hardware to Debian
566 packages. It can either be done using the tools in isenkram-cli or
567 using the user space daemon in the isenkram package. The latter will
568 notify you, when inserting new hardware, about what packages to
569 install to get the dongle working. It will even provide a button to
570 click on to ask packagekit to install the packages.
</p
>
572 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
591 </pre
></p
>
593 <p
>It can also list the firware package providing firmware requested
594 by the load kernel modules, which in my case is an empty list because
595 I have all the firmware my machine need:
598 % /usr/sbin/isenkram-autoinstall-firmware -l
599 info: did not find any firmware files requested by loaded kernel modules. exiting
601 </pre
></p
>
603 <p
>The last few days I had a look at several of the around
250
604 packages in Debian with udev rules. These seem like good candidates
605 to install when a given hardware dongle is inserted, and I found
606 several that should be proposed by isenkram. I have not had time to
607 check all of them, but am happy to report that now there are
97
608 packages packages mapped to hardware by Isenkram.
11 of these
609 packages provide hardware mapping using AppStream, while the rest are
610 listed in the modaliases file provided in isenkram.
</p
>
612 <p
>These are the packages with hardware mappings at the moment. The
613 <strong
>marked packages
</strong
> are also announcing their hardware
614 support using AppStream, for everyone to use:
</p
>
616 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
617 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
618 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
619 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
620 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
621 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
622 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
623 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
624 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
625 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
626 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
627 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
628 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
629 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
630 pcscd, pidgin-blinklight, printer-driver-splix,
631 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
632 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
633 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
634 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
635 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
636 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
637 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
638 xserver-xorg-video-vmware, yubikey-personalization and
639 zd1211-firmware
</p
>
641 <p
>If you know of other packages, please let me know with a wishlist
642 bug report against the isenkram-cli package, and ask the package
644 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
645 metadata according to the guidelines
</a
> to provide the information
646 for everyone. In time, I hope to get rid of the isenkram specific
647 hardware mapping and depend exclusively on AppStream.
</p
>
649 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
650 much hardware, and suggest that the package with with any ethernet
651 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
652 the details. I hope the maintainer find time to address it soon. In
653 the mean time I provide an override in isenkram.
</p
>
658 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
659 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
660 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
661 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
662 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
664 <p
>In my early years, I played
665 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
666 Elite
</a
> on my PC. I spent many months trading and fighting in
667 space, and reached the
'elite
' fighting status before I moved on. The
668 original Elite game was available on Commodore
64 and the IBM PC
669 edition I played had a
64 KB executable. I am still impressed today
670 that the authors managed to squeeze both a
3D engine and details about
671 more than
2000 planet systems across
7 galaxies into a binary so
674 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
675 software game Oolite inspired by Elite
</a
> for a while, but did not
676 really have time to test it properly until a few days ago. It was
677 great to discover that my old knowledge about trading routes were
678 still valid. But my fighting and flying abilities were gone, so I had
679 to retrain to be able to dock on a space station. And I am still not
680 able to make much resistance when I am attacked by pirates, so I
681 bougth and mounted the most powerful laser in the rear to be able to
682 put up at least some resistance while fleeing for my life. :)
</p
>
684 <p
>When playing Elite in the late eighties, I had to discover
685 everything on my own, and I had long lists of prices seen on different
686 planets to be able to decide where to trade what. This time I had the
688 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
689 where information about each planet is easily available with common
690 price ranges and suggested trading routes. This improved my ability
691 to earn money and I have been able to earn enough to buy a lot of
692 useful equipent in a few days. I believe I originally played for
693 months before I could get a docking computer, while now I could get it
694 after less then a week.
</p
>
696 <p
>If you like science fiction and dreamed of a life as a vagabond in
697 space, you should try out Oolite. It is available for Linux, MacOSX
698 and Windows, and is included in Debian and derivatives since
2011.
</p
>
700 <p
>As usual, if you use Bitcoin and want to show your support of my
701 activities, please send Bitcoin donations to my address
702 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
707 <title>Quicker Debian installations using eatmydata
</title>
708 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
710 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
711 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
712 installation system, observing how using
713 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
714 could speed up the installation
</a
> quite a bit. My testing measured
715 speedup around
20-
40 percent for Debian Edu, where we install around
716 1000 packages from within the installer. The eatmydata package
717 provide a way to disable/delay file system flushing. This is a bit
718 risky in the general case, as files that should be stored on disk will
719 stay only in memory a bit longer than expected, causing problems if a
720 machine crashes at an inconvenient time. But for an installation, if
721 the machine crashes during installation the process is normally
722 restarted, and avoiding disk operations as much as possible to speed
723 up the process make perfect sense.
725 <p
>I added code in the Debian Edu specific installation code to enable
726 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
727 but did not have time to push it any further. But a few months ago I
728 picked it up again and worked with the libeatmydata package maintainer
729 Mattia Rizzolo to make it easier for everyone to get this installation
730 speedup in Debian. Thanks to our cooperation There is now an
731 eatmydata-udeb package in Debian testing and unstable, and simply
732 enabling/installing it in debian-installer (d-i) is enough to get the
733 quicker installations. It can be enabled using preseeding. The
734 following untested kernel argument should do the trick:
</p
>
736 <blockquote
><pre
>
737 preseed/early_command=
"anna-install eatmydata-udeb
"
738 </pre
></blockquote
>
740 <p
>This should ask d-i to install the package inside the d-i
741 environment early in the installation sequence. Having it installed
742 in d-i in turn will make sure the relevant scripts are called just
743 after debootstrap filled /target/ with the freshly installed Debian
744 system to configure apt to run dpkg with eatmydata. This is enough to
745 speed up the installation process. There is a proposal to
746 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
747 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
748 tested its impact.
</p
>
754 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
755 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
756 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
757 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
758 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
759 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
760 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
761 elever over det ganske land skal levere inn hvert år. Det mange ikke
762 vet er at selv om de kommersielle alternativene
763 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
764 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
765 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
766 utmerket fri programvarealternativ som kan. Oversetterverktøyet
767 Apertium har støtte for en rekke språkkombinasjoner, og takket være
768 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
769 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
770 nynorsk, og få den automatoversatt til det andre skriftspråket.
771 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
772 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
773 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
774 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
775 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
776 teksten din i webskjemaet der.
778 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
779 teknologien kan du enten installere pakken
780 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
781 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
783 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
784 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
785 denne teksten som ble skrevet på bokmål over maskinoversatt til
790 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
791 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
792 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
793 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
794 veit er at sjølv om dei kommersielle alternativa
795 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
796 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
797 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
798 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
799 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
800 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
801 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
802 nynorsk, og få den *automatoversatt til det andre skriftspråket.
803 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
804 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
805 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
806 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
807 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
808 teksta di i *webskjemaet der.
810 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
811 teknologien kan du anten installera pakken
812 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
813 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
814 *api.*apertium.org. Sjå
815 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
816 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
817 for denne teksta som vart skreva på bokmål over *maskinoversatt til
823 <title>Coz profiler for multi-threaded software is now in Debian
</title>
824 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
825 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
826 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
827 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
828 profiler able to run benchmarking experiments on the instrumented
829 multi-threaded program, finally
830 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
831 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
833 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
834 blogged about the coz tool
</a
> in August working with upstream to make
835 it suitable for Debian. There are still issues with clang
836 compatibility, inline assembly only working x86 and minimized
837 JavaScript libraries.
</p
>
839 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
841 <p
><blockquote
>
842 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
843 </blockquote
></p
>
845 <p
>This will produce a profile.coz file in the current working
846 directory with the profiling information. This is then given to a
847 JavaScript application provided in the package and available from
848 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
849 To start the local copy, invoke it in a browser like this:
</p
>
851 <p
><blockquote
>
852 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
853 </blockquote
></p
>
855 <p
>See the project home page and the
856 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
857 ;login: article on Coz
</a
> for more information on how it is
863 <title>My own self balancing Lego Segway
</title>
864 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
865 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
866 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
867 <description><p
>A while back I received a Gyro sensor for the NXT
868 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
869 present. It had been on my wishlist for a while, because I wanted to
870 build a Segway like balancing lego robot. I had already built
871 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
872 robot
</a
> with the kids, using the light/color sensor included in the
873 NXT kit as the balance sensor, but it was not working very well. It
874 could balance for a while, but was very sensitive to the light
875 condition in the room and the reflective properties of the surface and
876 would fall over after a short while. I wanted something more robust,
878 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
879 gyro sensor from HiTechnic
</a
> I believed would solve it on my
880 wishlist for some years before it suddenly showed up as a gift from my
881 loved ones. :)
</p
>
883 <p
>Unfortunately I have not had time to sit down and play with it
884 since then. But that changed some days ago, when I was searching for
885 lego segway information and came across a recipe from HiTechnic for
887 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
888 HTWay
</a
>, a segway like balancing robot. Build instructions and
889 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
890 code
</a
> was included, so it was just a question of putting it all
891 together. And thanks to the great work of many Debian developers, the
892 compiler needed to build the source for the NXT is already included in
893 Debian, so I was read to go in less than an hour. The resulting robot
894 do not look very impressive in its simplicity:
</p
>
896 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
898 <p
>Because I lack the infrared sensor used to control the robot in the
899 design from HiTechnic, I had to comment out the last task
900 (taskControl). I simply placed /* and */ around it get the program
901 working without that sensor present. Now it balances just fine until
902 the battery status run low:
</p
>
904 <p align=
"center
"><video width=
"70%
" controls=
"true
">
905 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
906 </video
></p
>
908 <p
>Now we would like to teach it how to follow a line and take remote
909 control instructions using the included Bluetooth receiver in the NXT.
</p
>
911 <p
>If you, like me, love LEGO and want to make sure we find the tools
912 they need to work with LEGO in Debian and all our derivative
913 distributions like Ubuntu, check out
914 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
915 project page
</a
> and join the Debian LEGO team. Personally I own a
916 RCX and NXT controller (no EV3), and would like to make sure the
917 Debian tools needed to program the systems I own work as they
923 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
924 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
925 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
926 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
927 <description><p
>In July
928 <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
929 wrote how to get the Signal Chrome/Chromium app working
</a
> without
930 the ability to receive SMS messages (aka without a cell phone). It is
931 time to share some experiences and provide an updated setup.
</p
>
933 <p
>The Signal app have worked fine for several months now, and I use
934 it regularly to chat with my loved ones. I had a major snag at the
935 end of my summer vacation, when the the app completely forgot my
936 setup, identity and keys. The reason behind this major mess was
937 running out of disk space. To avoid that ever happening again I have
938 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
939 roll back to an earlier version if the files are wiped by mistake. I
940 had to use it once after introducing the git backup. When rolling
941 back to an earlier version, one need to use the
'reset session
' option
942 in Signal to get going, and notify the people you talk with about the
943 problem. I assume there is some sequence number tracking in the
944 protocol to detect rollback attacks. The git repository is rather big
945 (
674 MiB so far), but I have not tried to figure out if some of the
946 content can be added to a .gitignore file due to lack of spare
949 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
950 make it impossible to send messages using Signal. I could still
951 receive them, but had to patch the code with a new timestamp to send.
952 I believe the timeout is added by the developers to force people to
953 upgrade to the latest version of the app, even when there is no
954 protocol changes, to reduce the version skew among the user base and
955 thus try to keep the number of support requests down.
</p
>
957 <p
>Since my original recipe, the Signal source code changed slightly,
958 making the old patch fail to apply cleanly. Below is an updated
959 patch, including the shell wrapper I use to start Signal. The
960 original version required a new user to locate the JavaScript console
961 and call a function from there. I got help from a friend with more
962 JavaScript knowledge than me to modify the code to provide a GUI
963 button instead. This mean that to get started you just need to run
964 the wrapper and click the
'Register without mobile phone
' to get going
965 now. I
've also modified the timeout code to always set it to
90 days
966 in the future, to avoid having to patch the code regularly.
</p
>
968 <p
>So, the updated recipe for Debian Jessie:
</p
>
972 <li
>First, install required packages to get the source code and the
973 browser you need. Signal only work with Chrome/Chromium, as far as I
974 know, so you need to install it.
977 apt install git tor chromium
978 git clone https://github.com/WhisperSystems/Signal-Desktop.git
979 </pre
></li
>
981 <li
>Modify the source code using command listed in the the patch
982 block below.
</li
>
984 <li
>Start Signal using the run-signal-app wrapper (for example using
985 <tt
>`pwd`/run-signal-app
</tt
>).
987 <li
>Click on the
'Register without mobile phone
', will in a phone
988 number you can receive calls to the next minute, receive the
989 verification code and enter it into the form field and press
990 'Register
'. Note, the phone number you use will be user Signal
991 username, ie the way others can find you on Signal.
</li
>
993 <li
>You can now use Signal to contact others. Note, new contacts do
994 not show up in the contact list until you restart Signal, and there is
995 no way to assign names to Contacts. There is also no way to create or
996 update chat groups. I suspect this is because the web app do not have
997 a associated contact database.
</li
>
1001 <p
>I am still a bit uneasy about using Signal, because of the way its
1002 main author moxie0 reject federation and accept dependencies to major
1003 corporations like Google (part of the code is fetched from Google) and
1004 Amazon (the central coordination point is owned by Amazon). See for
1006 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1007 LibreSignal issue tracker
</a
> for a thread documenting the authors
1008 view on these issues. But the network effect is strong in this case,
1009 and several of the people I want to communicate with already use
1010 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1011 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1012 laptop
</a
>? It already work on Windows and Android, and is included
1013 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1014 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1015 working on Debian Stable.
</p
>
1017 <p
>Anyway, this is the patch I apply to the Signal code to get it
1018 working. It switch to the production servers, disable to timeout,
1019 make registration easier and add the shell wrapper:
</p
>
1022 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1023 diff --git a/js/background.js b/js/background.js
1024 index
24b4c1d.
.579345f
100644
1025 --- a/js/background.js
1026 +++ b/js/background.js
1031 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1032 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1033 var SERVER_PORTS = [
80,
4433,
8443];
1034 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1035 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1036 var messageReceiver;
1037 window.getSocketStatus = function() {
1038 if (messageReceiver) {
1039 diff --git a/js/expire.js b/js/expire.js
1040 index
639aeae..beb91c3
100644
1045 'use strict
';
1046 - var BUILD_EXPIRATION =
0;
1047 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1049 window.extension = window.extension || {};
1051 diff --git a/js/views/install_view.js b/js/views/install_view.js
1052 index
7816f4f.
.1d6233b
100644
1053 --- a/js/views/install_view.js
1054 +++ b/js/views/install_view.js
1057 'click .step1
': this.selectStep.bind(this,
1),
1058 'click .step2
': this.selectStep.bind(this,
2),
1059 -
'click .step3
': this.selectStep.bind(this,
3)
1060 +
'click .step3
': this.selectStep.bind(this,
3),
1061 +
'click .callreg
': function() { extension.install(
'standalone
') },
1064 clearQR: function() {
1065 diff --git a/options.html b/options.html
1066 index dc0f28e.
.8d709f6
100644
1070 &lt;div class=
'nav
'>
1071 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1072 &lt;p
>{{ installTagline }}
&lt;/p
>
1073 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1074 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1075 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1078 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1079 &lt;span class=
'dot step2
'>&lt;/span
>
1080 &lt;span class=
'dot step3
'>&lt;/span
>
1081 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1082 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1088 +userdata=
"`pwd`/userdata
"
1089 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1090 + (cd $userdata
&& git init)
1092 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1094 + --proxy-server=
"socks://localhost:
9050" \
1095 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1097 chmod a+rx run-signal-app
1100 <p
>As usual, if you use Bitcoin and want to show your support of my
1101 activities, please send Bitcoin donations to my address
1102 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1107 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1108 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1109 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1110 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1111 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1112 system
</a
> provide a practical and easy way to figure out which
1113 packages support the hardware in a given machine. The command line
1114 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1115 convenient way to list and install packages relevant for the current
1116 hardware during system installation, both user space packages and
1117 firmware packages. The GUI background daemon on the other hand provide
1118 a pop-up proposing to install packages when a new dongle is inserted
1119 while using the computer. For example, if you plug in a smart card
1120 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1121 that package isn
't already installed, and if you plug in a USB video
1122 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1123 cheese is currently missing. This already work just fine.
</p
>
1125 <p
>But Isenkram depend on a database mapping from hardware IDs to
1126 package names. When I started no such database existed in Debian, so
1127 I made my own data set and included it with the isenkram package and
1128 made isenkram fetch the latest version of this database from git using
1129 http. This way the isenkram users would get updated package proposals
1130 as soon as I learned more about hardware related packages.
</p
>
1132 <p
>The hardware is identified using modalias strings. The modalias
1133 design is from the Linux kernel where most hardware descriptors are
1134 made available as a strings that can be matched using filename style
1135 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1136 identifiers.
</p
>
1138 <p
>The downside to the Isenkram specific database is that there is no
1139 information about relevant distribution / Debian version, making
1140 isenkram propose obsolete packages too. But along came AppStream, a
1141 cross distribution mechanism to store and collect metadata about
1142 software packages. When I heard about the proposal, I contacted the
1143 people involved and suggested to add a hardware matching rule using
1144 modalias strings in the specification, to be able to use AppStream for
1145 mapping hardware to packages. This idea was accepted and AppStream is
1146 now a great way for a package to announce the hardware it support in a
1147 distribution neutral way. I wrote
1148 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1149 recipe on how to add such meta-information
</a
> in a blog post last
1150 December. If you have a hardware related package in Debian, please
1151 announce the relevant hardware IDs using AppStream.
</p
>
1153 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1154 RCX or NXT unit, announce this support using AppStream. The effect is
1155 that when you insert such LEGO robot controller into your Debian
1156 machine, Isenkram will propose to install the packages needed to get
1157 it working. The intention is that this should allow the local user to
1158 start programming his robot controller right away without having to
1159 guess what packages to use or which permissions to fix.
</p
>
1161 <p
>But when I sat down with my son the other day to program our NXT
1162 unit using his Debian Stretch computer, I discovered something
1163 annoying. The local console user (ie my son) did not get access to
1164 the USB device for programming the unit. This used to work, but no
1165 longer in Jessie and Stretch. After some investigation and asking
1166 around on #debian-devel, I discovered that this was because udev had
1167 changed the mechanism used to grant access to local devices. The
1168 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1169 no longer applied, because LDAP users no longer was added to the
1170 plugdev group during login. Michael Biebl told me that this method
1171 was obsolete and the new method used ACLs instead. This was good
1172 news, as the plugdev mechanism is a mess when using a remote user
1173 directory like LDAP. Using ACLs would make sure a user lost device
1174 access when she logged out, even if the user left behind a background
1175 process which would retain the plugdev membership with the ConsoleKit
1176 setup. Armed with this knowledge I moved on to fix the access problem
1177 for the LEGO Mindstorms related packages.
</p
>
1179 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1180 applied directly for a device, or is applied in
1181 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1182 LEGO Mindstorms udev rules did not have a class, I decided to add the
1183 tag directly in the udev rules files included in the packages. Here
1184 is one example. For the nqc C compiler for the RCX, the
1185 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1187 <p
><pre
>
1188 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1189 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1190 </pre
></p
>
1192 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1193 packages using plugdev in their /lib/udev/rules.d/ files should be
1194 changed to use this tag (either directly or indirectly via
1195 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1196 to detect this?
</p
>
1198 <p
>I
've been unable to find good documentation on the uaccess feature.
1199 It is unclear to me if the uaccess tag is an internal implementation
1200 detail like the udev-acl tag used by
1201 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1202 indirect method is the preferred way. Michael
1203 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1204 documentation from the systemd project
</a
> and I hope it will make
1205 this clearer. For now I use the generic classes when they exist and
1206 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1207 directly if no such class exist.
</p
>
1209 <p
>To learn more about the isenkram system, please check out
1210 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1211 blog posts tagged isenkram
</a
>.
</p
>
1213 <p
>To help out making life for LEGO constructors in Debian easier,
1214 please join us on our IRC channel
1215 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1216 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1217 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1218 list is not yet created, but we are working on it. :)
</p
>
1220 <p
>As usual, if you use Bitcoin and want to show your support of my
1221 activities, please send Bitcoin donations to my address
1222 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1227 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1228 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1229 <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>
1230 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1231 <description><p
>In April we
1232 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1233 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1234 how to set up and administrate a Debian system. Today I am happy to
1235 report that the first draft is now publicly available. You can find
1236 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1237 Administrator
's Handbook page
</a
> (under Other languages). The first
1238 eight chapters have a first draft translation, and we are working on
1239 proofreading the content. If you want to help out, please start
1241 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1242 hosted weblate project page
</a
>, and get in touch using
1243 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1244 translators mailing list
</a
>. Please also check out
1245 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1246 contributors
</a
>. A good way to contribute is to proofread the text
1247 and update weblate if you find errors.
</p
>
1249 <p
>Our goal is still to make the Norwegian book available on paper as well as
1250 electronic form.
</p
>
1255 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1256 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1257 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1258 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1259 <description><p
>This summer, I read a great article
1260 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1261 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1262 how to profile multi-threaded programs. It presented a system for
1263 profiling software by running experiences in the running program,
1264 testing how run time performance is affected by
"speeding up
" parts of
1265 the code to various degrees compared to a normal run. It does this by
1266 slowing down parallel threads while the
"faster up
" code is running
1267 and measure how this affect processing time. The processing time is
1268 measured using probes inserted into the code, either using progress
1269 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1270 can also measure unmodified code by measuring complete the program
1271 runtime and running the program several times instead.
</p
>
1273 <p
>The project and presentation was so inspiring that I would like to
1274 get the system into Debian. I
1275 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1276 a WNPP request for it
</a
> and contacted upstream to try to make the
1277 system ready for Debian by sending patches. The build process need to
1278 be changed a bit to avoid running
'git clone
' to get dependencies, and
1279 to include the JavaScript web page used to visualize the collected
1280 profiling information included in the source package.
1281 But I expect that should work out fairly soon.
</p
>
1283 <p
>The way the system work is fairly simple. To run an coz experiment
1284 on a binary with debug symbols available, start the program like this:
1286 <p
><blockquote
><pre
>
1287 coz run --- program-to-run
1288 </pre
></blockquote
></p
>
1290 <p
>This will create a text file profile.coz with the instrumentation
1291 information. To show what part of the code affect the performance
1292 most, use a web browser and either point it to
1293 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1294 or use the copy from git (in the gh-pages branch). Check out this web
1295 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
1296 profiling more useful you include
&lt;coz.h
&gt; and insert the
1297 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1298 code, rebuild and run the profiler. This allow coz to do more
1299 targeted experiments.
</p
>
1301 <p
>A video published by ACM
1302 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1303 Coz profiler
</a
> is available from Youtube. There is also a paper
1304 from the
25th Symposium on Operating Systems Principles available
1306 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1307 finding code that counts with causal profiling
</a
>.
</p
>
1309 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1310 for Coz is available from github. It will only build with clang
1312 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1313 feature missing in GCC
</a
>, but I
've submitted
1314 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1315 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1317 <p
>Please get in touch if you, like me, would like to see this piece
1318 of software in Debian. I would very much like some help with the
1319 packaging effort, as I lack the in depth knowledge on how to package
1320 C++ libraries.
</p
>
1325 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1326 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1327 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1328 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1329 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1330 to be a slight challenge. Here is the recipe if I ever need to do it
1331 again. It all started by me wanting to try the recipe to set up
1332 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1333 hardened Android installation
</a
> from the Tor project blog on a
1334 device I had access to. It is a old mobile phone with a broken
1335 microphone The initial idea had been to just
1336 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1337 CyanogenMod on it
</a
>, but did not quite find time to start on it
1338 until a few days ago.
</p
>
1340 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1341 loader (press volume down and power at the same time), (
2) select
1342 'fastboot
' before (
3) connecting the device via USB to a Linux
1343 machine, (
4) request the device identifier token by running
'fastboot
1344 oem get_identifier_token
', (
5) request the device unlocking key using
1345 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1346 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1348 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1349 or newer, and the device I was working on had
2.00.0027. This
1350 apparently can be easily fixed by downloading a Windows program and
1351 running it on your Windows machine, if you accept the terms Microsoft
1352 require you to accept to use Windows - which I do not. So I had to
1353 come up with a different approach. I got a lot of help from AndyCap
1354 on #nuug, and would not have been able to get this working without
1357 <p
>First I needed to extract the hboot firmware from
1358 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1359 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1360 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1361 project named unruu
</a
> using libunshield. The unshield tool did not
1362 recognise the file format, but unruu worked and extracted rom.zip,
1363 containing the new hboot firmware and a text file describing which
1364 devices it would work for.
</p
>
1366 <p
>Next, I needed to get the new firmware into the device. For this I
1367 followed some instructions
1368 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1369 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1370 machine with Debian testing:
</p
>
1372 <p
><pre
>
1373 adb reboot-bootloader
1374 fastboot oem rebootRUU
1375 fastboot flash zip rom.zip
1376 fastboot flash zip rom.zip
1378 </pre
></p
>
1380 <p
>The flash command apparently need to be done twice to take effect,
1381 as the first is just preparations and the second one do the flashing.
1382 The adb command is just to get to the boot loader menu, so turning the
1383 device on while holding volume down and the power button should work
1386 <p
>With the new hboot version in place I could start following the
1387 instructions on the HTC developer web site. I got the device token
1388 like this:
</p
>
1390 <p
><pre
>
1391 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1394 <p
>And once I got the unlock code via email, I could use it like
1397 <p
><pre
>
1398 fastboot flash unlocktoken Unlock_code.bin
1399 </pre
></p
>
1401 <p
>And with that final step in place, the phone was unlocked and I
1402 could start stuffing the software of my own choosing into the device.
1403 So far I only inserted a replacement recovery image to wipe the phone
1404 before I start. We will see what happen next. Perhaps I should
1405 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1410 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1411 <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>
1412 <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>
1413 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1414 <description><p
>For a while now, I have wanted to test
1415 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1416 said to provide end to end encrypted communication and several of my
1417 friends and family are already using it. As I by choice do not own a
1418 mobile phone, this proved to be harder than expected. And I wanted to
1419 have the source of the client and know that it was the code used on my
1420 machine. But yesterday I managed to get it working. I used the
1421 Github source, compared it to the source in
1422 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1423 Signal Chrome app
</a
> available from the Chrome web store, applied
1424 patches to use the production Signal servers, started the app and
1425 asked for the hidden
"register without a smart phone
" form. Here is
1426 the recipe how I did it.
</p
>
1428 <p
>First, I fetched the Signal desktop source from Github, using
1431 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1434 <p
>Next, I patched the source to use the production servers, to be
1435 able to talk to other Signal users:
</p
>
1438 cat
&lt;
&lt;EOF | patch -p0
1439 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1440 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1441 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1446 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1447 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1448 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1449 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1450 var messageReceiver;
1451 window.getSocketStatus = function() {
1452 if (messageReceiver) {
1453 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1454 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1455 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1458 'use strict
';
1459 - var BUILD_EXPIRATION =
0;
1460 + var BUILD_EXPIRATION =
1474492690000;
1462 window.extension = window.extension || {};
1467 <p
>The first part is changing the servers, and the second is updating
1468 an expiration timestamp. This timestamp need to be updated regularly.
1469 It is set
90 days in the future by the build process (Gruntfile.js).
1470 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1472 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1473 script to launch Signal in Chromium.
</p
>
1480 --proxy-server=
"socks://localhost:
9050" \
1481 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1484 <p
> The script start the app and configure Chromium to use the Tor
1485 SOCKS5 proxy to make sure those controlling the Signal servers (today
1486 Amazon and Whisper Systems) as well as those listening on the lines
1487 will have a harder time location my laptop based on the Signal
1488 connections if they use source IP address.
</p
>
1490 <p
>When the script starts, one need to follow the instructions under
1491 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1492 repository. I right clicked on the Signal window to get up the
1493 Chromium debugging tool, visited the
'Console
' tab and wrote
1494 'extension.install(
"standalone
")
' on the console prompt to get the
1495 registration form. Then I entered by land line phone number and
1496 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1497 repeated the verification code three times. After entering the number
1498 into the verification code field in the form, I could start using
1499 Signal from my laptop.
1501 <p
>As far as I can tell, The Signal app will leak who is talking to
1502 whom and thus who know who to those controlling the central server,
1503 but such leakage is hard to avoid with a centrally controlled server
1504 setup. It is something to keep in mind when using Signal - the
1505 content of your chats are harder to intercept, but the meta data
1506 exposing your contact network is available to people you do not know.
1507 So better than many options, but not great. And sadly the usage is
1508 connected to my land line, thus allowing those controlling the server
1509 to associate it to my home and person. I would prefer it if only
1510 those I knew could tell who I was on Signal. There are options
1511 avoiding such information leakage, but most of my friends are not
1512 using them, so I am stuck with Signal for now.
</p
>
1514 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1516 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1517 and updated recipe for using the Signal app without a mobile
1518 phone
</a
>.
</p
>
1523 <title>The new
"best
" multimedia player in Debian?
</title>
1524 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1525 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1526 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1527 <description><p
>When I set out a few weeks ago to figure out
1528 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1529 multimedia player in Debian claimed to support most file formats /
1530 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1531 the various players claimed support for. The range was from
55 to
130
1532 MIME types. I suspect most media formats are supported by all
1533 players, but this is not really reflected in the MimeTypes values in
1534 their desktop files. There are probably also some bogus MIME types
1535 listed, but it is hard to identify which one this is.
</p
>
1537 <p
>Anyway, in the mean time I got in touch with upstream for some of
1538 the players suggesting to add more MIME types to their desktop files,
1539 and decided to spend some time myself improving the situation for my
1540 favorite media player VLC. The fixes for VLC entered Debian unstable
1541 yesterday. The complete list of MIME types can be seen on the
1542 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1543 player MIME type support status
</a
> Debian wiki page.
</p
>
1545 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1546 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1547 kmplayer. I am sure some of the other players desktop files support
1548 several of the formats currently listed as working only with vlc,
1549 toten and parole.
</p
>
1551 <p
>A sad observation is that only
14 MIME types are listed as
1552 supported by all the tested multimedia players in Debian in their
1553 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1554 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1555 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1556 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1557 it sad that video/ogg and video/webm is not supported by all the media
1558 players in Debian. As far as I can tell, all of them can handle both
1564 <title>A program should be able to open its own files on Linux
</title>
1565 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1566 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1567 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1568 <description><p
>Many years ago, when koffice was fresh and with few users, I
1569 decided to test its presentation tool when making the slides for a
1570 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1571 wrote the first draft of the slides, saved the result and went to bed
1572 the day before I would give the talk. The next day I took a plane to
1573 the location where the meeting should take place, and on the plane I
1574 started up koffice again to polish the talk a bit, only to discover
1575 that kpresenter refused to load its own data file. I cursed a bit and
1576 started making the slides again from memory, to have something to
1577 present when I arrived. I tested that the saved files could be
1578 loaded, and the day seemed to be rescued. I continued to polish the
1579 slides until I suddenly discovered that the saved file could no longer
1580 be loaded into kpresenter. In the end I had to rewrite the slides
1581 three times, condensing the content until the talk became shorter and
1582 shorter. After the talk I was able to pinpoint the problem
&ndash;
1583 kpresenter wrote inline images in a way itself could not understand.
1584 Eventually that bug was fixed and kpresenter ended up being a great
1585 program to make slides. The point I
'm trying to make is that we
1586 expect a program to be able to load its own data files, and it is
1587 embarrassing to its developers if it can
't.
</p
>
1589 <p
>Did you ever experience a program failing to load its own data
1590 files from the desktop file browser? It is not a uncommon problem. A
1591 while back I discovered that the screencast recorder
1592 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1593 browser would refuse to open. No video player claimed to understand
1594 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1595 returning the application/ogg MIME type, which no video player I had
1596 installed listed as a MIME type they would understand. I asked for
1597 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1598 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1599 several video players to add video/ogg to their desktop files, to give
1600 the file browser an idea what to do about Ogg Theora files. After a
1601 while, the desktop file browsers in Debian started to handle the
1602 output from gtk-recordmydesktop properly.
</p
>
1604 <p
>But history repeats itself. A few days ago I tested the music
1605 system Rosegarden again, and I discovered that the KDE and xfce file
1606 browsers did not know what to do with the Rosegarden project files
1607 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1608 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1609 included in the next upload. To increase the chance of me remembering
1610 how to fix the problem next time some program fail to load its files
1611 from the file browser, here are some notes on how to fix it.
</p
>
1613 <p
>The file browsers in Debian in general operates on MIME types.
1614 There are two sources for the MIME type of a given file. The output from
1615 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1616 shared MIME type registry (under /usr/share/mime/). The file MIME
1617 type is mapped to programs supporting the MIME type, and this
1618 information is collected from
1619 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1620 desktop files
</a
> available in /usr/share/applications/. If there is
1621 one desktop file claiming support for the MIME type of the file, it is
1622 activated when asking to open a given file. If there are more, one
1623 can normally select which one to use by right-clicking on the file and
1624 selecting the wanted one using
'Open with
' or similar. In general
1625 this work well. But it depend on each program picking a good MIME
1627 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1628 MIME type registered with IANA
</a
>), file and/or the shared MIME
1629 registry recognizing the file and the desktop file to list the MIME
1630 type in its list of supported MIME types.
</p
>
1632 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1633 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1634 Shared MIME database
</a
> look like this:
</p
>
1636 <p
><blockquote
><pre
>
1637 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1638 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1639 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1640 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1641 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1642 &lt;glob pattern=
"*.rg
"/
&gt;
1643 &lt;/mime-type
&gt;
1644 &lt;/mime-info
&gt;
1645 </pre
></blockquote
></p
>
1647 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1648 (it is a gzipped XML file). Note, it is much better to use an
1649 official MIME type registered with IANA than it is to make up ones own
1650 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1652 <p
>The desktop file of the rosegarden program failed to list
1653 audio/x-rosegarden in its list of supported MIME types, causing the
1654 file browsers to have no idea what to do with *.rg files:
</p
>
1656 <p
><blockquote
><pre
>
1657 % grep Mime /usr/share/applications/rosegarden.desktop
1658 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1659 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1661 </pre
></blockquote
></p
>
1663 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1664 MimeType= line.
</p
>
1666 <p
>If you run into a file which fail to open the correct program when
1667 selected from the file browser, please check out the output from
1668 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1669 MIME type is registered somewhere under /usr/share/mime/ and check
1670 that some desktop file under /usr/share/applications/ is claiming
1671 support for this MIME type. If not, please report a bug to have it
1677 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1678 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1679 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1680 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1681 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1682 system
</a
> is a user-focused solution in Debian for handling hardware
1683 related packages. The idea is to have a database of mappings between
1684 hardware and packages, and pop up a dialog suggesting for the user to
1685 install the packages to use a given hardware dongle. Some use cases
1686 are when you insert a Yubikey, it proposes to install the software
1687 needed to control it; when you insert a braille reader list it
1688 proposes to install the packages needed to send text to the reader;
1689 and when you insert a ColorHug screen calibrator it suggests to
1690 install the driver for it. The system work well, and even have a few
1691 command line tools to install firmware packages and packages for the
1692 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1694 <p
>The system was initially written using aptdaemon, because I found
1695 good documentation and example code on how to use it. But aptdaemon
1696 is going away and is generally being replaced by
1697 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1698 so Isenkram needed a rewrite. And today, thanks to the great patch
1699 from my college Sunil Mohan Adapa in the FreedomBox project, the
1700 rewrite finally took place. I
've just uploaded a new version of
1701 Isenkram into Debian Unstable with the patch included, and the default
1702 for the background daemon is now to use PackageKit. To check it out,
1703 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1704 and see if it is recognised.
</p
>
1706 <p
>If you want to know what kind of packages isenkram would propose for
1707 the machine it is running on, you can check out the isenkram-lookup
1708 program. This is what it look like on a Thinkpad X230:
</p
>
1710 <p
><blockquote
><pre
>
1726 </pre
></blockquote
></p
>
1728 <p
>The hardware mappings come from several places. The preferred way
1729 is for packages to announce their hardware support using
1730 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1731 cross distribution appstream system
</a
>.
1733 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1734 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1739 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1740 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1741 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1742 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1743 <description><p
>Yesterday I updated the
1744 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1745 package in Debian
</a
> with a few patches sent to me by skilled and
1746 enterprising users. There were some nice user and visible changes.
1747 First of all, both desktop menu entries now work. A design flaw in
1748 one of the script made the history graph fail to show up (its PNG was
1749 dumped in ~/.xsession-errors) if no controlling TTY was available.
1750 The script worked when called from the command line, but not when
1751 called from the desktop menu. I changed this to look for a DISPLAY
1752 variable or a TTY before deciding where to draw the graph, and now the
1753 graph window pop up as expected.
</p
>
1755 <p
>The next new feature is a discharge rate estimator in one of the
1756 graphs (the one showing the last few hours). New is also the user of
1757 colours showing charging in blue and discharge in red. The percentages
1758 of this graph is relative to last full charge, not battery design
1761 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1763 <p
>The other graph show the entire history of the collected battery
1764 statistics, comparing it to the design capacity of the battery to
1765 visualise how the battery life time get shorter over time. The red
1766 line in this graph is what the previous graph considers
100 percent:
1768 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1770 <p
>In this graph you can see that I only charge the battery to
80
1771 percent of last full capacity, and how the capacity of the battery is
1772 shrinking. :(
</p
>
1774 <p
>The last new feature is in the collector, which now will handle
1775 more hardware models. On some hardware, Linux power supply
1776 information is stored in /sys/class/power_supply/ACAD/, while the
1777 collector previously only looked in /sys/class/power_supply/AC/. Now
1778 both are checked to figure if there is power connected to the
1781 <p
>If you are interested in how your laptop battery is doing, please
1783 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1784 in Debian unstable, or rebuild it on Jessie to get it working on
1785 Debian stable. :) The upstream source is available from
<a
1786 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1787 Patches are very welcome.
</p
>
1789 <p
>As usual, if you use Bitcoin and want to show your support of my
1790 activities, please send Bitcoin donations to my address
1791 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1796 <title>Debian now with ZFS on Linux included
</title>
1797 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1798 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1799 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1800 <description><p
>Today, after many years of hard work from many people,
1801 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1802 Debian. The package status can be seen on
1803 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1804 for zfs-linux
</a
>. and
1805 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1806 team status page
</a
>. If you want to help out, please join us.
1807 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1808 source code
</a
> is available via git on Alioth. It would also be
1809 great if you could help out with
1810 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1811 it is an important piece of the puzzle to get ZFS working.
</p
>
1816 <title>What is the best multimedia player in Debian?
</title>
1817 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1818 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1819 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1820 <description><p
><strong
>Where I set out to figure out which multimedia player in
1821 Debian claim support for most file formats.
</strong
></p
>
1823 <p
>A few years ago, I had a look at the media support for Browser
1824 plugins in Debian, to get an idea which plugins to include in Debian
1825 Edu. I created a script to extract the set of supported MIME types
1826 for each plugin, and used this to find out which multimedia browser
1827 plugin supported most file formats / media types.
1828 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1829 result
</a
> can still be seen on the Debian wiki, even though it have
1830 not been updated for a while. But browser plugins are less relevant
1831 these days, so I thought it was time to look at standalone
1834 <p
>A few days ago I was tired of VLC not being listed as a viable
1835 player when I wanted to play videos from the Norwegian National
1836 Broadcasting Company, and decided to investigate why. The cause is a
1837 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1838 desktop file
</a
>. In the process I wrote a script to compare the set
1839 of MIME types announced in the desktop file and the browser plugin,
1840 only to discover that there is quite a large difference between the
1841 two for VLC. This discovery made me dig up the script I used to
1842 compare browser plugins, and adjust it to compare desktop files
1843 instead, to try to figure out which multimedia player in Debian
1844 support most file formats.
</p
>
1846 <p
>The result can be seen on the Debian Wiki, as
1847 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1848 table listing all MIME types supported by one of the packages included
1849 in the table
</a
>, with the package supporting most MIME types being
1850 listed first in the table.
</p
>
1852 </p
>The best multimedia player in Debian? It is totem, followed by
1853 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1854 kmplayer. Time for the other players to update their announced MIME
1860 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1861 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1862 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1863 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1864 <description>A friend of mine made me aware of
1865 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1866 handheld computer which will be delivered with Debian preinstalled. I
1867 would love to get one of those for my birthday. :)
</p
>
1869 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1870 plugs and many others connectors, and include a full keyboard and a
5"
1871 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1872 day of battery life time, but I have not seen any independent tests
1873 confirming this. The vendor is still collecting preorders, and the
1874 last I heard last night was that
22 more orders were needed before
1875 production started.
</p
>
1877 <p
>As far as I know, this is the first handheld preinstalled with
1878 Debian. Please let me know if you know of any others. Is it the
1879 first computer being sold with Debian preinstalled?
</p
>
1884 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1885 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1886 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1887 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1888 <description><p
>During this weekends
1889 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1890 squashing party and developer gathering
</a
>, we decided to do our part
1891 to make sure there are good books about Debian available in Norwegian
1892 Bokmål, and got in touch with the people behind the
1893 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1894 project
</a
> to get started. If you want to help out, please start
1896 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1897 hosted weblate project page
</a
>, and get in touch using
1898 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1899 translators mailing list
</a
>. Please also check out
1900 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1901 contributors
</a
>.
</p
>
1903 <p
>The book is already available on paper in English, French and
1904 Japanese, and our goal is to get it available on paper in Norwegian
1905 Bokmål too. In addition to the paper edition, there are also EPUB and
1906 Mobi versions available. And there are incomplete translations
1907 available for many more languages.
</p
>
1912 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1913 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1914 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1915 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1916 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1917 packages in Debian, and was quite surprised with what I found. I use
1918 ZFS myself at home, but did not really expect many others to do so.
1919 But I might be wrong.
</p
>
1921 <p
>According to
1922 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1923 results for spl-linux
</a
>, there are
1019 Debian installations, or
1924 0.53% of the population, with the package installed. As far as I know
1925 the only use of the spl-linux package is as a support library for ZFS
1926 on Linux, so I use it here as proxy for measuring the number of ZFS
1927 installation on Linux in Debian. In the kFreeBSD variant of Debian
1928 the ZFS feature is already available, and there
1929 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1930 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1931 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1933 <p
>But even though the Debian project leader Lucas Nussbaum
1934 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1935 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1936 cleared, the package is still not in Debian. The package is again in
1937 the NEW queue. Several uploads have been rejected so far because the
1938 debian/copyright file was incomplete or wrong, but there is no reason
1939 to give up. The current status can be seen on
1940 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1941 team status page
</a
>, and
1942 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1943 source code
</a
> is available on Alioth.
</p
>
1945 <p
>As I want ZFS to be included in next version of Debian to make sure
1946 my home server can function in the future using only official Debian
1947 packages, and the current blocker is to get the debian/copyright file
1948 accepted by the FTP masters in Debian, I decided a while back to try
1949 to help out the team. This was the background for my blog post about
1950 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1951 updating and checking debian/copyright semi-automatically
</a
>, and I
1952 used the techniques I explored there to try to find any errors in the
1953 copyright file. It is not very easy to check every one of the around
1954 2000 files in the source package, but I hope we this time got it
1955 right. If you want to help out, check out the git source and try to
1956 find missing entries in the debian/copyright file.
</p
>
1961 <title>Full battery stats collector is now available in Debian
</title>
1962 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1963 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1964 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1965 <description><p
>Since this morning, the battery-stats package in Debian include an
1966 extended collector that will collect the complete battery history for
1967 later processing and graphing. The original collector store the
1968 battery level as percentage of last full level, while the new
1969 collector also record battery vendor, model, serial number, design
1970 full level, last full level and current battery level. This make it
1971 possible to predict the lifetime of the battery as well as visualise
1972 the energy flow when the battery is charging or discharging.
</p
>
1974 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1975 in the version
0.5.1 package in unstable. Get the new battery level graph
1976 and lifetime prediction by running:
1978 <p
><pre
>
1979 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1980 </pre
></p
>
1982 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1984 <p
>The flow in/out of the battery can be seen by running (no menu
1985 entry yet):
</p
>
1987 <p
><pre
>
1988 /usr/share/battery-stats/battery-stats-graph-flow
1989 </pre
></p
>
1991 <p
>I
'm not quite happy with the way the data is visualised, at least
1992 when there are few data points. The graphs look a bit better with a
1993 few years of data.
</p
>
1995 <p
>A while back one important feature I use in the battery stats
1996 collector broke in Debian. The scripts in
1997 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1998 suspect it happened when Jessie started using systemd, but I do not
1999 know. The issue is reported as
2000 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2001 pm-utils. I managed to work around it by adding an udev rule to call
2002 the collector script every time the power connector is connected and
2003 disconnected. With this fix in place it was finally time to make a
2004 new release of the package, and get it into Debian.
</p
>
2006 <p
>If you are interested in how your laptop battery is doing, please
2008 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2009 in Debian unstable, or rebuild it on Jessie to get it working on
2010 Debian stable. :) The upstream source is available from
2011 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2012 As always, patches are very welcome.
</p
>
2017 <title>Making battery measurements a little easier in Debian
</title>
2018 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2019 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2020 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2021 <description><p
>Back in September, I blogged about
2022 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2023 system I wrote to collect statistics about my laptop battery
</a
>, and
2024 how it showed the decay and death of this battery (now replaced). I
2025 created a simple deb package to handle the collection and graphing,
2026 but did not want to upload it to Debian as there were already
2027 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2028 package in Debian
</a
> that should do the same thing, and I did not see
2029 a point of uploading a competing package when battery-stats could be
2030 fixed instead. I reported a few bugs about its non-function, and
2031 hoped someone would step in and fix it. But no-one did.
</p
>
2033 <p
>I got tired of waiting a few days ago, and took matters in my own
2034 hands. The end result is that I am now the new upstream developer of
2035 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2036 battery-stats in Debian, and the package in Debian unstable is finally
2037 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2038 information provided by the Linux kernel. If you install the
2039 battery-stats package from unstable now, you will be able to get a
2040 graph of the current battery fill level, to get some idea about the
2041 status of the battery. The source package build and work just fine in
2042 Debian testing and stable (and probably oldstable too, but I have not
2043 tested). The default graph you get for that system look like this:
</p
>
2045 <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
>
2047 <p
>My plans for the future is to merge my old scripts into the
2048 battery-stats package, as my old scripts collected a lot more details
2049 about the battery. The scripts are merged into the upstream
2050 battery-stats git repository already, but I am not convinced they work
2051 yet, as I changed a lot of paths along the way. Will have to test a
2052 bit more before I make a new release.
</p
>
2054 <p
>I will also consider changing the file format slightly, as I
2055 suspect the way I combine several values into one field might make it
2056 impossible to know the type of the value when using it for processing
2057 and graphing.
</p
>
2059 <p
>If you would like I would like to keep an close eye on your laptop
2060 battery, check out the battery-stats package in
2061 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2063 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2064 I would love some help to improve the system further.
</p
>
2069 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2070 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2071 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2072 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2073 <description><p
>Making packages for Debian requires quite a lot of attention to
2074 details. And one of the details is the content of the
2075 debian/copyright file, which should list all relevant licenses used by
2076 the code in the package in question, preferably in
2077 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2078 readable DEP5 format
</a
>.
</p
>
2080 <p
>For large packages with lots of contributors it is hard to write
2081 and update this file manually, and if you get some detail wrong, the
2082 package is normally rejected by the ftpmasters. So getting it right
2083 the first time around get the package into Debian faster, and save
2084 both you and the ftpmasters some work.. Today, while trying to figure
2085 out what was wrong with
2086 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2087 zfsonlinux copyright file
</a
>, I decided to spend some time on
2088 figuring out the options for doing this job automatically, or at least
2089 semi-automatically.
</p
>
2091 <p
>Lucikly, there are at least two tools available for generating the
2092 file based on the code in the source package,
2093 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2094 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2095 not sure which one of them came first, but both seem to be able to
2096 create a sensible draft file. As far as I can tell, none of them can
2097 be trusted to get the result just right, so the content need to be
2098 polished a bit before the file is OK to upload. I found the debmake
2100 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2101 blog posts from
2014</a
>.
2103 <p
>To generate using debmake, use the -cc option:
2105 <p
><pre
>
2106 debmake -cc
> debian/copyright
2107 </pre
></p
>
2109 <p
>Note there are some problems with python and non-ASCII names, so
2110 this might not be the best option.
</p
>
2112 <p
>The cme option is based on a config parsing library, and I found
2114 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2115 blog post from
2015</a
>. To generate using cme, use the
'update
2116 dpkg-copyright
' option:
2118 <p
><pre
>
2119 cme update dpkg-copyright
2120 </pre
></p
>
2122 <p
>This will create or update debian/copyright. The cme tool seem to
2123 handle UTF-
8 names better than debmake.
</p
>
2125 <p
>When the copyright file is created, I would also like some help to
2126 check if the file is correct. For this I found two good options,
2127 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2128 to focus on license types and file matching, and is able to detect
2129 ineffective blocks in the copyright file. The latter reports missing
2130 copyright holders and years, but was confused by inconsistent license
2131 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2132 fix all issues reported by them before uploading. But I do not know
2133 if the tools and the ftpmasters agree on what is important to fix in a
2134 copyright file, so the package might still be rejected.
</p
>
2136 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2137 will read through the source and try to find all copyright statements.
2138 It is not comparing the result to the content of debian/copyright, but
2139 can be useful when verifying the content of the copyright file.
</p
>
2141 <p
>Are you aware of better tools in Debian to create and update
2142 debian/copyright file. Please let me know, or blog about it on
2143 planet.debian.org.
</p
>
2145 <p
>As usual, if you use Bitcoin and want to show your support of my
2146 activities, please send Bitcoin donations to my address
2147 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2149 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2150 on how to use licensecheck and cdbs to create a draft copyright file
2152 <p
><pre
>
2153 licensecheck --copyright -r `find * -type f` | \
2154 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2155 </pre
></p
>
2157 <p
>He mentioned that he normally check the generated file into the
2158 version control system to make it easier to discover license and
2159 copyright changes in the upstream source. I will try to do the same
2160 with my packages in the future.
</p
>
2162 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2163 against using -quiet for new users, so I removed it from the proposed
2164 command line.
</p
>
2169 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2170 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2172 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2173 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2174 is taking shape in Debian, and one provided feature is a very
2175 convenient way to tell you which package to install to make a given
2176 firmware file available when the kernel is looking for it. This can
2177 be done using apt-file too, but that is for someone else to blog
2180 <p
>Here is a small recipe to find the package with a given firmware
2181 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2182 picked from the set of firmware announced using appstream in Debian
2183 unstable. In general you would be looking for the firmware requested
2184 by the kernel during kernel module loading. To find the package
2185 providing the example file, do like this:
</p
>
2187 <blockquote
><pre
>
2188 % apt install appstream
2192 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2193 awk
'/Package:/ {print $
2}
'
2196 </pre
></blockquote
>
2198 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2199 appstream wiki
</a
> page to learn how to embed the package metadata in
2200 a way appstream can use.
</p
>
2202 <p
>This same approach can be used to find any package supporting a
2203 given MIME type. This is very useful when you get a file you do not
2204 know how to handle. First find the mime type using
<tt
>file
2205 --mime-type
</tt
>, and next look up the package providing support for
2206 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2207 and you can find all packages handling this type like this:
</p
>
2209 <blockquote
><pre
>
2210 % apt install appstream
2214 % appstreamcli what-provides mimetype image/svg+xml | \
2215 awk
'/Package:/ {print $
2}
'
2237 </pre
></blockquote
>
2239 <p
>I believe the MIME types are fetched from the desktop file for
2240 packages providing appstream metadata.
</p
>
2245 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2246 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2247 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2248 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2249 <description><p
>Most people seem not to realise that every time they walk around
2250 with the computerised radio beacon known as a mobile phone their
2251 position is tracked by the phone company and often stored for a long
2252 time (like every time a SMS is received or sent). And if their
2253 computerised radio beacon is capable of running programs (often called
2254 mobile apps) downloaded from the Internet, these programs are often
2255 also capable of tracking their location (if the app requested access
2256 during installation). And when these programs send out information to
2257 central collection points, the location is often included, unless
2258 extra care is taken to not send the location. The provided
2259 information is used by several entities, for good and bad (what is
2260 good and bad, depend on your point of view). What is certain, is that
2261 the private sphere and the right to free movement is challenged and
2262 perhaps even eradicated for those announcing their location this way,
2263 when they share their whereabouts with private and public
2266 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2268 <p
>The phone company logs provide a register of locations to check out
2269 when one want to figure out what the tracked person was doing. It is
2270 unavailable for most of us, but provided to selected government
2271 officials, company staff, those illegally buying information from
2272 unfaithful servants and crackers stealing the information. But the
2273 public information can be collected and analysed, and a free software
2274 tool to do so is called
2275 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2276 discovered it when I read
2277 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2278 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2279 November
2014, and decided to check if it was available in Debian.
2280 The python program was in Debian, but
2281 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2282 Debian
</a
> was completely broken and practically unmaintained. I
2283 uploaded a new version which did not work quite right, but did not
2284 have time to fix it then. This Christmas I decided to finally try to
2285 get Creepy operational in Debian. Now a fixed version is available in
2286 Debian unstable and testing, and almost all Debian specific patches
2288 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2290 <p
>The Creepy program visualises geolocation information fetched from
2291 Twitter, Instagram, Flickr and Google+, and allow one to get a
2292 complete picture of every social media message posted recently in a
2293 given area, or track the movement of a given individual across all
2294 these services. Earlier it was possible to use the search API of at
2295 least some of these services without identifying oneself, but these
2296 days it is impossible. This mean that to use Creepy, you need to
2297 configure it to log in as yourself on these services, and provide
2298 information to them about your search interests. This should be taken
2299 into account when using Creepy, as it will also share information
2300 about yourself with the services.
</p
>
2302 <p
>The picture above show the twitter messages sent from (or at least
2303 geotagged with a position from) the city centre of Oslo, the capital
2304 of Norway. One useful way to use Creepy is to first look at
2305 information tagged with an area of interest, and next look at all the
2306 information provided by one or more individuals who was in the area.
2307 I tested it by checking out which celebrity provide their location in
2308 twitter messages by checkout out who sent twitter messages near a
2309 Norwegian TV station, and next could track their position over time,
2310 making it possible to locate their home and work place, among other
2311 things. A similar technique have been
2312 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2313 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2314 tool to discover lying governments, and a useful tool to help people
2315 understand the value of the private information they provide to the
2318 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2319 it depend on several python modules currently missing in Jessie (at
2320 least python-instagram, python-flickrapi and
2321 python-requests-toolbelt).
</p
>
2323 <p
>(I have uploaded
2324 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2325 screenshots.debian.net
</a
> and licensed it under the same terms as the
2326 Creepy program in Debian.)
</p
>
2331 <title>Always download Debian packages using Tor - the simple recipe
</title>
2332 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2333 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2334 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2335 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2336 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2337 that those listening on the Internet lines would have good reason to
2338 believe a computer have a given security hole
</a
> if it download a
2339 security fix from a Debian mirror. This is a good reason to always
2340 use encrypted connections to the Debian mirror, to make sure those
2341 listening do not know which IP address to attack. In August, Richard
2342 Hartmann observed that encryption was not enough, when it was possible
2343 to interfere download size to security patches or the fact that
2344 download took place shortly after a security fix was released, and
2345 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2346 to always use Tor to download packages from the Debian mirror
</a
>. He
2347 was not the first to propose this, as the
2348 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2349 package by Tim Retout already existed to make it easy to convince apt
2350 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2351 aware of that package when I read the blog post from Richard.
</p
>
2353 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2354 sysadmins, and he set up a Tor hidden service on one of the central
2355 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2356 it possible to download packages directly between two tor nodes,
2357 making sure the network traffic always were encrypted.
</p
>
2359 <p
>Here is a short recipe for enabling this on your machine, by
2360 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2361 urls with tor+http and tor+https, and using the hidden service instead
2362 of the official Debian mirror site. I recommend installing
2363 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2364 done in /etc/.
</p
>
2366 <blockquote
><pre
>
2367 apt install apt-transport-tor
2368 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2369 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2370 </pre
></blockquote
>
2372 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2373 the sed commands for these too. The sed command is assuming your are
2374 using the ftp.debian.org Debian mirror. Adjust the command (or just
2375 edit the file manually) to match your mirror.
</p
>
2377 <p
>This work in Debian Jessie and later. Note that tools like
2378 <tt
>apt-file
</tt
> only recently started using the apt transport
2379 system, and do not work with these tor+http URLs. For
2380 <tt
>apt-file
</tt
> you need the version currently in experimental,
2381 which need a recent apt version currently only in unstable. So if you
2382 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2384 <p
>Another advantage from this change is that your machine will start
2385 using Tor regularly and at fairly random intervals (every time you
2386 update the package lists or upgrade or install a new package), thus
2387 masking other Tor traffic done from the same machine. Using Tor will
2388 become normal for the machine in question.
</p
>
2390 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2391 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2392 enabled. It would be great if it was the default on any Debian
2398 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2399 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2400 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2401 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2402 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2403 call the car license plate numbers in those days. I would write the
2404 numbers down in my little book and compare notes with the other kids
2405 to see how many region codes we had seen and if we had seen some
2406 exotic or special region codes and numbers. It was a fun game to pass
2407 time, as we kids have plenty of it.
</p
>
2409 <p
>A few days I came across
2410 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2411 project
</a
>, a free software project to automatically discover and
2412 report license plates in images and video streams, and provide the
2413 "car numbers
" in a machine readable format. I
've been looking for
2414 such system for a while now, because I believe it is a bad idea that the
2415 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2416 number plate recognition
</a
> tool only is available in the hands of
2417 the powerful, and want it to be available also for the powerless to
2418 even the score when it comes to surveillance and sousveillance. I
2419 discovered the developer
2420 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2421 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2422 help him get it into shape to get the package uploaded into the Debian
2425 <p
>Today we finally managed to get the package into shape and uploaded
2426 it into Debian, where it currently
2427 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2428 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2430 <p
>I guess you are wondering why on earth such tool would be useful
2431 for the common folks, ie those not running a large government
2432 surveillance system? Well, I plan to put it in a computer on my bike
2433 and in my car, tracking the cars nearby and allowing me to be notified
2434 when number plates on my watch list are discovered. Another use case
2435 was suggested by a friend of mine, who wanted to set it up at his home
2436 to open the car port automatically when it discovered the plate on his
2437 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2438 capable of placing his license plate number of a piece of cardboard to
2439 open his car port, men replied that it was always unlocked anyway. I
2440 guess for such use case it make sense. I am sure there are other use
2441 cases too, for those with imagination and a vision.
</p
>
2443 <p
>If you want to build your own version of the Debian package, check
2444 out the upstream git source and symlink ./distros/debian to ./debian/
2445 before running
"debuild
" to build the source. Or wait a bit until the
2446 package show up in unstable.
</p
>
2451 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2452 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2453 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2454 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2455 <description><p
>Around three years ago, I created
2456 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2457 system
</a
> to get a more practical solution in Debian for handing
2458 hardware related packages. A GUI system in the isenkram package will
2459 present a pop-up dialog when some hardware dongle supported by
2460 relevant packages in Debian is inserted into the machine. The same
2461 lookup mechanism to detect packages is available as command line
2462 tools in the isenkram-cli package. In addition to mapping hardware,
2463 it will also map kernel firmware files to packages and make it easy to
2464 install needed firmware packages automatically. The key for this
2465 system to work is a good way to map hardware to packages, in other
2466 words, allow packages to announce what hardware they will work
2469 <p
>I started by providing data files in the isenkram source, and
2470 adding code to download the latest version of these data files at run
2471 time, to ensure every user had the most up to date mapping available.
2472 I also added support for storing the mapping in the Packages file in
2473 the apt repositories, but did not push this approach because while I
2474 was trying to figure out how to best store hardware/package mappings,
2475 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2476 appstream system
</a
> was announced. I got in touch and suggested to
2477 add the hardware mapping into that data set to be able to use
2478 appstream as a data source, and this was accepted at least for the
2479 Debian version of appstream.
</p
>
2481 <p
>A few days ago using appstream in Debian for this became possible,
2482 and today I uploaded a new version
0.20 of isenkram adding support for
2483 appstream as a data source for mapping hardware to packages. The only
2484 package so far using appstream to announce its hardware support is my
2485 pymissile package. I got help from Matthias Klumpp with figuring out
2486 how do add the required
2487 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2488 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2489 this content:
</p
>
2491 <blockquote
><pre
>
2492 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2493 &lt;component
&gt;
2494 &lt;id
&gt;pymissile
&lt;/id
&gt;
2495 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2496 &lt;name
&gt;pymissile
&lt;/name
&gt;
2497 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2498 &lt;description
&gt;
2500 Pymissile provides a curses interface to control an original
2501 Marks and Spencer / Striker USB Missile Launcher, as well as a
2502 motion control script to allow a webcamera to control the
2505 &lt;/description
&gt;
2506 &lt;provides
&gt;
2507 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2508 &lt;/provides
&gt;
2509 &lt;/component
&gt;
2510 </pre
></blockquote
>
2512 <p
>The key for isenkram is the component/provides/modalias value,
2513 which is a glob style match rule for hardware specific strings
2514 (modalias strings) provided by the Linux kernel. In this case, it
2515 will map to all USB devices with vendor code
1130 and product code
2518 <p
>Note, it is important that the license of all the metadata files
2519 are compatible to have permissions to aggregate them into archive wide
2520 appstream files. Matthias suggested to use MIT or BSD licenses for
2521 these files. A challenge is figuring out a good id for the data, as
2522 it is supposed to be globally unique and shared across distributions
2523 (in other words, best to coordinate with upstream what to use). But
2524 it can be changed later or, so we went with the package name as
2525 upstream for this project is dormant.
</p
>
2527 <p
>To get the metadata file installed in the correct location for the
2528 mirror update scripts to pick it up and include its content the
2529 appstream data source, the file must be installed in the binary
2530 package under /usr/share/appdata/. I did this by adding the following
2531 line to debian/pymissile.install:
</p
>
2533 <blockquote
><pre
>
2534 debian/pymissile.metainfo.xml usr/share/appdata
2535 </pre
></blockquote
>
2537 <p
>With that in place, the command line tool isenkram-lookup will list
2538 all packages useful on the current computer automatically, and the GUI
2539 pop-up handler will propose to install the package not already
2540 installed if a hardware dongle is inserted into the machine in
2543 <p
>Details of the modalias field in appstream is available from the
2544 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2546 <p
>To locate the modalias values of all hardware present in a machine,
2547 try running this command on the command line:
</p
>
2549 <blockquote
><pre
>
2550 cat $(find /sys/devices/|grep modalias)
2551 </pre
></blockquote
>
2553 <p
>To learn more about the isenkram system, please check out
2554 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2555 blog posts tagged isenkram
</a
>.
</p
>
2560 <title>The GNU General Public License is not magic pixie dust
</title>
2561 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2562 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2563 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2564 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2565 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2566 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2567 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2568 I quote the blog post from Paul in full here with his permission:
<p
>
2572 <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
>
2575 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2577 The first step is to choose a
2578 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2581 The next step is, when someone fails to follow that copyleft license,
2582 <b
>it must be enforced
</b
><br/
>
2584 and its a simple fact of our modern society that such type of
2587 is incredibly expensive to do and incredibly difficult to do.
2590 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2591 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2592 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2593 0x57</a
></small
></p
>
2595 <p
>As the Debian Website
2596 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2597 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2598 imply, public domain and permissively licensed software can lead to
2599 the production of more proprietary software as people discover useful
2600 software, extend it and or incorporate it into their hardware or
2601 software products. Copyleft licenses such as the GNU GPL were created
2602 to close off this avenue to the production of proprietary software but
2603 such licenses are not enough. With the ongoing adoption of Free
2604 Software by individuals and groups, inevitably the community
's
2605 expectations of license compliance are violated, usually out of
2606 ignorance of the way Free Software works, but not always. As Karen
2607 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2608 Freedom
">FaiF
</a
>
2609 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2610 copyleft is nothing if no-one is willing and able to stand up in court
2611 to protect it. The reality of today
's world is that legal
2612 representation is expensive, difficult and time consuming. With
2613 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2614 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2615 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2616 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2617 of the Linux project, Debian and other groups against GPL violations.
2618 In March the SFC supported a
2619 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2620 by Christoph Hellwig
</a
> against VMware for refusing to
2621 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2622 with the GPL
</a
> in relation to their use of parts of the Linux
2623 kernel. Since then two of their sponsors pulled corporate funding and
2625 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2626 or cancelled their talks
</a
>. As a result they have decided to rely
2627 less on corporate funding and more on the broad community of
2628 individuals who support Free Software and copyleft. So the SFC has
2629 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2630 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2631 a community of folks who stand up for copyleft and the GPL by
2632 supporting their work on promoting and supporting copyleft and Free
2635 <p
>If you support Free Software,
2636 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2637 what the SFC do, agree with their
2638 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2639 principles
</a
>, are happy about their
2640 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2641 work on a project that is an SFC
2642 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2643 just want to stand up for copyleft, please join
2644 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2645 Allan Webber
</a
>,
2646 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2648 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2649 Bacon
</a
>, myself and
2650 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2652 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2653 next week your donation will be
2654 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2655 by an anonymous donor. Please also consider asking your employer to
2656 match your donation or become a sponsor of SFC. Don
't forget to
2657 spread the word about your support for SFC via email, your blog and or
2658 social media accounts.
</p
>
2662 <p
>I agree with Paul on this topic and just signed up as a Supporter
2663 of Software Freedom Conservancy myself. Perhaps you should be a
2664 supporter too?
</p
>
2669 <title>PGP key transition statement for key EE4E02F9
</title>
2670 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2671 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2672 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2673 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2674 set it up properly. I wanted to generate it offline and have it
2675 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2676 smart card
</a
> for daily use, and learning how to do it and finding
2677 time to sit down with an offline machine almost took forever. But
2678 finally I
've been able to complete the process, and have now moved
2679 from my old GPG key to a new GPG key. See
2680 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2681 full transition statement, signed with both my old and new key
</a
> for
2682 the details. This is my new key:
</p
>
2685 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2686 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2687 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2688 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2689 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2690 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2691 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2694 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2695 my old key.
</p
>
2697 <p
>If you signed my old key
2698 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2699 I
'd very much appreciate a signature on my new key, details and
2700 instructions in the transition statement. I m happy to reciprocate if
2701 you have a similarly signed transition statement to present.
</p
>
2706 <title>The life and death of a laptop battery
</title>
2707 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2708 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2709 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2710 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2711 But this do not last. The last few laptops gave me a feeling that
2712 within a year, the life time is just a fraction of what it used to be,
2713 and it slowly become painful to use the laptop without power connected
2714 all the time. Because of this, when I got a new Thinkpad X230 laptop
2715 about two years ago, I decided to monitor its battery state to have
2716 more hard facts when the battery started to fail.
</p
>
2718 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2720 <p
>First I tried to find a sensible Debian package to record the
2721 battery status, assuming that this must be a problem already handled
2722 by someone else. I found
2723 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2724 which collects statistics from the battery, but it was completely
2725 broken. I sent a few suggestions to the maintainer, but decided to
2726 write my own collector as a shell script while I waited for feedback
2728 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2729 blog post about the battery development on a MacBook Air
</a
> I also
2731 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2732 available in Debian.
</p
>
2734 <p
>I started my collector
2013-
07-
15, and it has been collecting
2735 battery stats ever since. Now my
2736 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2737 measurements, from the time the battery was working great until now,
2738 when it is unable to charge above
7% of original capacity. My
2739 collector shell script is quite simple and look like this:
</p
>
2744 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2746 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2747 logfile=/var/log/hjemmenett-battery-status.log
2749 files=
"manufacturer model_name technology serial_number \
2750 energy_full energy_full_design energy_now cycle_count status
"
2752 if [ ! -e
"$logfile
" ] ; then
2754 printf
"timestamp,
"
2756 printf
"%s,
" $f
2759 )
> "$logfile
"
2763 # Print complete message in one echo call, to avoid race condition
2764 # when several log processes run in parallel.
2765 msg=$(printf
"%s,
" $(date +%s); \
2766 for f in $files; do \
2767 printf
"%s,
" $(cat $f); \
2769 echo
"$msg
"
2772 cd /sys/class/power_supply
2775 (cd $bat
&& log_battery
>> "$logfile
")
2779 <p
>The script is called when the power management system detect a
2780 change in the power status (power plug in or out), and when going into
2781 and out of hibernation and suspend. In addition, it collect a value
2782 every
10 minutes. This make it possible for me know when the battery
2783 is discharging, charging and how the maximum charge change over time.
2784 The code for the Debian package
2785 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2786 available on github
</a
>.
</p
>
2788 <p
>The collected log file look like this:
</p
>
2791 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2792 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2794 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2795 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2798 <p
>I wrote a small script to create a graph of the charge development
2799 over time. This graph depicted above show the slow death of my laptop
2802 <p
>But why is this happening? Why are my laptop batteries always
2803 dying in a year or two, while the batteries of space probes and
2804 satellites keep working year after year. If we are to believe
2805 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2806 University
</a
>, the cause is me charging the battery whenever I have a
2807 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2808 all the time, but to stay below
90% of full charge most of the time.
2809 I
've been told that the Tesla electric cars
2810 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2811 the charge of their batteries to
80%
</a
>, with the option to charge to
2812 100% when preparing for a longer trip (not that I would want a car
2813 like Tesla where rights to privacy is abandoned, but that is another
2814 story), which I guess is the option we should have for laptops on
2815 Linux too.
</p
>
2817 <p
>Is there a good and generic way with Linux to tell the battery to
2818 stop charging at
80%, unless requested to charge to
100% once in
2819 preparation for a longer trip? I found
2820 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2821 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2822 80%
</a
>, but could not get it to work (kernel module refused to
2825 <p
>I wonder why the battery capacity was reported to be more than
100%
2826 at the start. I also wonder why the
"full capacity
" increases some
2827 times, and if it is possible to repeat the process to get the battery
2828 back to design capacity. And I wonder if the discharge and charge
2829 speed change over time, or if this stay the same. I did not yet try
2830 to write a tool to calculate the derivative values of the battery
2831 level, but suspect some interesting insights might be learned from
2834 <p
>Update
2015-
09-
24: I got a tip to install the packages
2835 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2836 packages instead of the tp-smapi-dkms package I had tried to use
2837 initially, and use
'tlp setcharge
40 80' to change when charging start
2838 and stop. I
've done so now, but expect my existing battery is toast
2839 and need to be replaced. The proposal is unfortunately Thinkpad
2845 <title>New laptop - some more clues and ideas based on feedback
</title>
2846 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2848 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2849 <description><p
>Several people contacted me after my previous blog post about my
2850 need for a new laptop, and provided very useful feedback. I wish to
2851 thank every one of these. Several pointed me to the possibility of
2852 fixing my X230, and I am already in the process of getting Lenovo to
2853 do so thanks to the on site, next day support contract covering the
2854 machine. But the battery is almost useless (I expect to replace it
2855 with a non-official battery) and I do not expect the machine to live
2856 for many more years, so it is time to plan its replacement. If I did
2857 not have a support contract, it was suggested to find replacement parts
2858 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2859 might present a language barrier as I do not understand French.
</p
>
2861 <p
>One tip I got was to use the
2862 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2863 compare laptop models. It seem to have more models available than
2864 prisjakt.no. Another tip I got from someone I know have similar
2865 keyboard preferences was that the HP EliteBook
840 keyboard is not
2866 very good, and this matches my experience with earlier EliteBook
2867 keyboards I tested. Because of this, I will not consider it any further.
2869 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2870 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2871 (which is missing from the X240), and is working fairly well with
2872 Debian Sid/Unstable according to
2873 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2874 got on the keyboard quality are not consistent. Some say the keyboard
2875 is good, others say it is ok, while others say it is not very good.
2876 Those with experience from X41 and and X60 agree that the X250
2877 keyboard is not as good as those trusty old laptops, and suggest I
2878 keep and fix my X230 instead of upgrading, or get a used X230 to
2879 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2880 activity and battery status, which is very convenient on my X230. I
'm
2881 also told that the CPU fan is running very often, making it a bit
2882 noisy. In any case, the X250 do not work out of the box with Debian
2883 Stable/Jessie, one of my requirements.
</p
>
2885 <p
>I have also gotten a few vendor proposals, one was
2886 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2887 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2888 The latter look very attractive to me.
</p
>
2890 <p
>Again, thank you all for the very useful feedback. It help a lot
2891 as I keep looking for a replacement.
</p
>
2893 <p
>Update
2015-
07-
06: I was recommended to check out the
2894 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2896 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2897 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2902 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2903 <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>
2904 <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>
2905 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2906 <description><p
>My primary work horse laptop is failing, and will need a
2907 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2908 started flickering yesterday, and I suspect the cause is a broken
2909 cable, as changing the angle of the screen some times get rid of the
2910 flickering.
</p
>
2912 <p
>My requirements have not really changed since I bought it, and is
2914 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2915 described them in
2013</a
>. The last time I bought a laptop, I had
2917 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2918 where I could select at least a few of the requirements (mouse pin,
2919 wifi, weight) and go through the rest manually. Three button mouse
2920 and a good keyboard is not available as an option, and all the three
2921 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2922 G2) lack three mouse buttons). It is also unclear to me how good the
2923 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2924 the keyboard, even if the quality and robustness in the X series have
2925 deteriorated since X41.
</p
>
2927 <p
>I wonder how I can find a sensible laptop when none of the options
2928 seem sensible to me? Are there better services around to search the
2929 set of available laptops for features? Please send me an email if you
2930 have suggestions.
</p
>
2932 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2933 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2934 of endorsed hardware
</a
>, which is useful background information.
</p
>
2939 <title>How to stay with sysvinit in Debian Jessie
</title>
2940 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2941 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2942 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2943 <description><p
>By now, it is well known that Debian Jessie will not be using
2944 sysvinit as its boot system by default. But how can one keep using
2945 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2947 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2948 Schubert
</a
> and
2949 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2952 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2953 keep sysvinit as your boot system, create a file
2954 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2955 you upgrade:
</p
>
2957 <p
><blockquote
><pre
>
2958 Package: systemd-sysv
2959 Pin: release o=Debian
2961 </pre
></blockquote
><p
>
2963 <p
>This file content will tell apt and aptitude to not consider
2964 installing systemd-sysv as part of any installation and upgrade
2965 solution when resolving dependencies, and thus tell it to avoid
2966 systemd as a default boot system. The end result should be that the
2967 upgraded system keep using sysvinit.
</p
>
2969 <p
>If you are installing Jessie for the first time, there is no way to
2970 get sysvinit installed by default (debootstrap used by
2971 debian-installer have no option for this), but one can tell the
2972 installer to switch to sysvinit before the first boot. Either by
2973 using a kernel argument to the installer, or by adding a line to the
2974 preseed file used. First, the kernel command line argument:
2976 <p
><blockquote
><pre
>
2977 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2978 </pre
></blockquote
><p
>
2980 <p
>Next, the line to use in a preseed file:
</p
>
2982 <p
><blockquote
><pre
>
2983 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2984 </pre
></blockquote
><p
>
2986 <p
>One can of course also do this after the first boot by installing
2987 the sysvinit-core package.
</p
>
2989 <p
>I recommend only using sysvinit if you really need it, as the
2990 sysvinit boot sequence in Debian have several hardware specific bugs
2991 on Linux caused by the fact that it is unpredictable when hardware
2992 devices show up during boot. But on the other hand, the new default
2993 boot system still have a few rough edges I hope will be fixed before
2994 Jessie is released.
</p
>
2996 <p
>Update
2014-
11-
26: Inspired by
2997 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2998 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3004 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3005 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3006 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3007 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3008 <description><p
>The right to communicate with your friends and family in private,
3009 without anyone snooping, is a right every citicen have in a liberal
3010 democracy. But this right is under serious attack these days.
</p
>
3012 <p
>A while back it occurred to me that one way to make the dragnet
3013 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3014 the whisleblower Snowden) more expensive for Internet email,
3015 is to deliver all email using SMTP via Tor. Such SMTP option would be
3016 a nice addition to the FreedomBox project if we could send email
3017 between FreedomBox machines without leaking metadata about the emails
3018 to the people peeking on the wire. I
3019 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3020 this on the FreedomBox project mailing list in October
</a
> and got a
3021 lot of useful feedback and suggestions. It also became obvious to me
3022 that this was not a novel idea, as the same idea was tested and
3023 documented by Johannes Berg as early as
2006, and both
3024 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3025 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3026 propose a similar method / protocol to pass emails between users.
</p
>
3028 <p
>To implement such system one need to set up a Tor hidden service
3029 providing the SMTP protocol on port
25, and use email addresses
3030 looking like username@hidden-service-name.onion. With such addresses
3031 the connections to port
25 on hidden-service-name.onion using Tor will
3032 go to the correct SMTP server. To do this, one need to configure the
3033 Tor daemon to provide the hidden service and the mail server to accept
3034 emails for this .onion domain. To learn more about Exim configuration
3035 in Debian and test the design provided by Johannes Berg in his FAQ, I
3036 set out yesterday to create a Debian package for making it trivial to
3037 set up such SMTP over Tor service based on Debian. Getting it to work
3038 were fairly easy, and
3039 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3040 source code for the Debian package
</a
> is available from github. I
3041 plan to move it into Debian if further testing prove this to be a
3042 useful approach.
</p
>
3044 <p
>If you want to test this, set up a blank Debian machine without any
3045 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3046 get rid of exim4). Install tor, clone the git repository mentioned
3047 above, build the deb and install it on the machine. Next, run
3048 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3049 the instructions to get the service up and running. Restart tor and
3050 exim when it is done, and test mail delivery using swaks like
3053 <p
><blockquote
><pre
>
3054 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3055 --to fbx@dutlqrrmjhtfa3vp.onion
3056 </pre
></blockquote
></p
>
3058 <p
>This will test the SMTP delivery using tor. Replace the email
3059 address with your own address to test your server. :)
</p
>
3061 <p
>The setup procedure is still to complex, and I hope it can be made
3062 easier and more automatic. Especially the tor setup need more work.
3063 Also, the package include a tor-smtp tool written in C, but its task
3064 should probably be rewritten in some script language to make the deb
3065 architecture independent. It would probably also make the code easier
3066 to review. The tor-smtp tool currently need to listen on a socket for
3067 exim to talk to it and is started using xinetd. It would be better if
3068 no daemon and no socket is needed. I suspect it is possible to get
3069 exim to run a command line tool for delivery instead of talking to a
3070 socket, and hope to figure out how in a future version of this
3073 <p
>Until I wipe my test machine, I can be reached using the
3074 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3075 SMTorP. :)
</p
>
3080 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3081 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3082 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3083 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3084 <description><p
>If you ever had to moderate a mailman list, like the ones on
3085 alioth.debian.org, you know the web interface is fairly slow to
3086 operate. First you visit one web page, enter the moderation password
3087 and get a new page shown with a list of all the messages to moderate
3088 and various options for each email address. This take a while for
3089 every list you moderate, and you need to do it regularly to do a good
3090 job as a list moderator. But there is a quick alternative,
3091 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3092 listadmin program
</a
>. It allow you to check lists for new messages
3093 to moderate in a fraction of a second. Here is a test run on two
3094 lists I recently took over:
</p
>
3096 <p
><blockquote
><pre
>
3097 % time listadmin xiph
3098 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3099 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3105 </pre
></blockquote
></p
>
3107 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3108 there are no message in the moderation queue. Every morning I
3109 currently moderate
68 mailman lists, and it normally take around two
3110 minutes. When I took over the two pkg-xiph lists above a few days
3111 ago, there were
400 emails waiting in the moderator queue. It took me
3112 less than
15 minutes to process them all using the listadmin
3115 <p
>If you install
3116 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3117 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3118 with content like this, the moderation task is a breeze:
</p
>
3120 <p
><blockquote
><pre
>
3121 username username@example.org
3124 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3127 adminurl https://{domain}/mailman/admindb/{list}
3128 mailman-list@lists.example.com
3131 other-list@otherserver.example.org
3132 </pre
></blockquote
></p
>
3134 <p
>There are other options to set as well. Check the manual page to
3135 learn the details.
</p
>
3137 <p
>If you are forced to moderate lists on a mailman installation where
3138 the SSL certificate is self signed or not properly signed by a
3139 generally accepted signing authority, you can set a environment
3140 variable when calling listadmin to disable SSL verification:
</p
>
3142 <p
><blockquote
><pre
>
3143 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3144 </pre
></blockquote
></p
>
3146 <p
>If you want to moderate a subset of the lists you take care of, you
3147 can provide an argument to the listadmin script like I do in the
3148 initial screen dump (the xiph argument). Using an argument, only
3149 lists matching the argument string will be processed. This make it
3150 quick to accept messages if you notice the moderation request in your
3153 <p
>Without the listadmin program, I would never be the moderator of
68
3154 mailing lists, as I simply do not have time to spend on that if the
3155 process was any slower. The listadmin program have saved me hours of
3156 time I could spend elsewhere over the years. It truly is nice free
3159 <p
>As usual, if you use Bitcoin and want to show your support of my
3160 activities, please send Bitcoin donations to my address
3161 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3163 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3164 configuration example. Also, I
've been told that the
3165 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3171 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3172 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3173 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3174 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3175 <description><p
>When PXE installing laptops with Debian, I often run into the
3176 problem that the WiFi card require some firmware to work properly.
3177 And it has been a pain to fix this using preseeding in Debian.
3178 Normally something more is needed. But thanks to
3179 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3180 package
</a
> and its recent tasksel extension, it has now become easy
3181 to do this using simple preseeding.
</p
>
3183 <p
>The isenkram-cli package provide tasksel tasks which will install
3184 firmware for the hardware found in the machine (actually, requested by
3185 the kernel modules for the hardware). (It can also install user space
3186 programs supporting the hardware detected, but that is not the focus
3187 of this story.)
</p
>
3189 <p
>To get this working in the default installation, two preeseding
3190 values are needed. First, the isenkram-cli package must be installed
3191 into the target chroot (aka the hard drive) before tasksel is executed
3192 in the pkgsel step of the debian-installer system. This is done by
3193 preseeding the base-installer/includes debconf value to include the
3194 isenkram-cli package. The package name is next passed to debootstrap
3195 for installation. With the isenkram-cli package in place, tasksel
3196 will automatically use the isenkram tasks to detect hardware specific
3197 packages for the machine being installed and install them, because
3198 isenkram-cli contain tasksel tasks.
</p
>
3200 <p
>Second, one need to enable the non-free APT repository, because
3201 most firmware unfortunately is non-free. This is done by preseeding
3202 the apt-mirror-setup step. This is unfortunate, but for a lot of
3203 hardware it is the only option in Debian.
</p
>
3205 <p
>The end result is two lines needed in your preseeding file to get
3206 firmware installed automatically by the installer:
</p
>
3208 <p
><blockquote
><pre
>
3209 base-installer base-installer/includes string isenkram-cli
3210 apt-mirror-setup apt-setup/non-free boolean true
3211 </pre
></blockquote
></p
>
3213 <p
>The current version of isenkram-cli in testing/jessie will install
3214 both firmware and user space packages when using this method. It also
3215 do not work well, so use version
0.15 or later. Installing both
3216 firmware and user space packages might give you a bit more than you
3217 want, so I decided to split the tasksel task in two, one for firmware
3218 and one for user space programs. The firmware task is enabled by
3219 default, while the one for user space programs is not. This split is
3220 implemented in the package currently in unstable.
</p
>
3222 <p
>If you decide to give this a go, please let me know (via email) how
3223 this recipe work for you. :)
</p
>
3225 <p
>So, I bet you are wondering, how can this work. First and
3226 foremost, it work because tasksel is modular, and driven by whatever
3227 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3228 isenkram-cli package place two files for tasksel to find. First there
3229 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3231 <p
><blockquote
><pre
>
3232 Task: isenkram-packages
3234 Description: Hardware specific packages (autodetected by isenkram)
3235 Based on the detected hardware various hardware specific packages are
3237 Test-new-install: show show
3239 Packages: for-current-hardware
3241 Task: isenkram-firmware
3243 Description: Hardware specific firmware packages (autodetected by isenkram)
3244 Based on the detected hardware various hardware specific firmware
3245 packages are proposed.
3246 Test-new-install: mark show
3248 Packages: for-current-hardware-firmware
3249 </pre
></blockquote
></p
>
3251 <p
>The key parts are Test-new-install which indicate how the task
3252 should be handled and the Packages line referencing to a script in
3253 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3254 list of packages to install. The for-current-hardware-firmware script
3255 look like this to list relevant firmware for the machine:
3257 <p
><blockquote
><pre
>
3260 PATH=/usr/sbin:$PATH
3262 isenkram-autoinstall-firmware -l
3263 </pre
></blockquote
></p
>
3265 <p
>With those two pieces in place, the firmware is installed by
3266 tasksel during the normal d-i run. :)
</p
>
3268 <p
>If you want to test what tasksel will install when isenkram-cli is
3269 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3270 --new-install
</tt
> to get the list of packages that tasksel would
3273 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3274 pilots in testing this feature, as isenkram is used there now to
3275 install firmware, replacing the earlier scripts.
</p
>
3280 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3281 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3282 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3283 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3284 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3285 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3286 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3287 on a screen normally showing the bread types and prizes:
</p
>
3289 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3291 <p
>If it had booted as it was supposed to, I would never had known
3292 about this hidden Linux installation. It is interesting what
3293 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3298 <title>New lsdvd release version
0.17 is ready
</title>
3299 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3300 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3301 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3302 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3303 got a new set of developers a few weeks ago, after the original
3304 developer decided to step down and pass the project to fresh blood.
3305 This project is now maintained by Petter Reinholdtsen and Steve
3308 <p
>I just wrapped up
3309 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3310 new lsdvd release
</a
>, available in git or from
3311 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3312 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3317 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3318 <li
>Check for garbage in the program chains, which indicate that a track is
3319 non-existant, to work around additional copy protection
</li
>
3320 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3321 <li
>Fix pallete display of first entry
</li
>
3322 <li
>Fix include orders
</li
>
3323 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3324 <li
>Fix the chapter count
</li
>
3325 <li
>Make sure the array size and the array limit used when initialising
3326 the palette size is the same.
</li
>
3327 <li
>Fix array printing.
</li
>
3328 <li
>Correct subsecond calculations.
</li
>
3329 <li
>Add sector information to the output format.
</li
>
3330 <li
>Clean up code to be closer to ANSI C and compile without warnings
3331 with more GCC compiler warnings.
</li
>
3335 <p
>This change bring together patches for lsdvd in use in various
3336 Linux and Unix distributions, as well as patches submitted to the
3337 project the last nine years. Please check it out. :)
</p
>
3342 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3343 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3345 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3346 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3347 project
</a
> provide a Linux solution for schools, including a
3348 powerful desktop with education software, a central server providing
3349 web pages, user database, user home directories, central login and PXE
3350 boot of both clients without disk and the installation to install Debian
3351 Edu on machines with disk (and a few other services perhaps to small
3352 to mention here). We in the Debian Edu team are currently working on
3353 the Jessie based version, trying to get everything in shape before the
3354 freeze, to avoid having to maintain our own package repository in the
3356 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3357 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3358 work left. Some fatal problems block testing, breaking the installer,
3359 but it is possible to work around these to get anyway. Here is a
3360 recipe on how to get the installation limping along.
</p
>
3362 <p
>First, download the test ISO via
3363 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3364 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3366 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3367 The ISO build was broken on Tuesday, so we do not get a new ISO every
3368 12 hours or so, but thankfully the ISO we already got we are able to
3369 install with some tweaking.
</p
>
3371 <p
>When you get to the Debian Edu profile question, go to tty2
3372 (use Alt-Ctrl-F2), run
</p
>
3374 <p
><blockquote
><pre
>
3375 nano /usr/bin/edu-eatmydata-install
3376 </pre
></blockquote
></p
>
3378 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3379 optimization. Return to the installation, select the profile you want
3380 and continue. Without this change, exim4-config will fail to install
3381 due to a known bug in eatmydata.
</p
>
3383 <p
>When you get the grub question at the end, answer /dev/sda (or if
3384 this do not work, figure out what your correct value would be. All my
3385 test machines need /dev/sda, so I have no advice if it do not fit
3386 your need.
</p
>
3388 <p
>If you installed a profile including a graphical desktop, log in as
3389 root after the initial boot from hard drive, and install the
3390 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3391 or mate. If you want several desktop options, install more than one
3392 metapackage. Once this is done, reboot and you should have a working
3393 graphical login screen. This workaround should no longer be needed
3394 once the education-tasks package version
1.801 enter testing in two
3397 <p
>I believe the ISO build will start working on two days when the new
3398 tasksel package enter testing and Steve McIntyre get a chance to
3399 update the debian-cd git repository. The eatmydata, grub and desktop
3400 issues are already fixed in unstable and testing, and should show up
3401 on the ISO as soon as the ISO build start working again. Well the
3402 eatmydata optimization is really just disabled. The proper fix
3403 require an upload by the eatmydata maintainer applying the patch
3404 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3405 The rest have proper fixes in unstable.
</p
>
3407 <p
>I hope this get you going with the installation testing, as we are
3408 quickly running out of time trying to get our Jessie based
3409 installation ready before the distribution freeze in a month.
</p
>
3414 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3415 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3416 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3417 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3418 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3419 to handle my fairly large DVD collection. It is a nice command line
3420 tool to get details about a DVD, like title, tracks, track length,
3421 etc, in XML, Perl or human readable format. But lsdvd have not seen
3422 any new development since
2006 and had a few irritating bugs affecting
3423 its use with some DVDs. Upstream seemed to be dead, and in January I
3424 sent a small probe asking for a version control repository for the
3425 project, without any reply. But I use it regularly and would like to
3426 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3427 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3428 the project admin, and after getting a reply from him explaining that
3429 he was no longer interested in the project, I asked if I could take
3430 over. And yesterday, I became project admin.
</p
>
3432 <p
>I
've been in touch with a Gentoo developer and the Debian
3433 maintainer interested in joining forces to maintain the upstream
3434 project, and I hope we can get a new release out fairly quickly,
3435 collecting the patches spread around on the internet into on place.
3436 I
've added the relevant Debian patches to the freshly created git
3437 repository, and expect the Gentoo patches to make it too. If you got
3438 a DVD collection and care about command line tools, check out
3439 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3440 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3441 list
</a
>. :)
</p
>
3446 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3447 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3449 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3450 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3451 a lot quicker. When we install more than
2000 packages in
3452 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3453 tasksel in the installer, unpacking the binary packages take forever.
3454 A part of the slow I/O issue was discussed in
3455 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3456 much file system sync-ing done by dpkg, which is the package
3457 responsible for unpacking the binary packages. Other parts (like code
3458 executed by postinst scripts) might also sync to disk during
3459 installation. All this sync-ing to disk do not really make sense to
3460 me. If the machine crash half-way through, I start over, I do not try
3461 to salvage the half installed system. So the failure sync-ing is
3462 supposed to protect against, hardware or system crash, is not really
3463 relevant while the installer is running.
</p
>
3465 <p
>A few days ago, I thought of a way to get rid of all the file
3466 system sync()-ing in a fairly non-intrusive way, without the need to
3467 change the code in several packages. The idea is not new, but I have
3468 not heard anyone propose the approach using dpkg-divert before. It
3469 depend on the small and clever package
3470 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3471 uses LD_PRELOAD to replace the system functions for syncing data to
3472 disk with functions doing nothing, thus allowing programs to live
3473 dangerous while speeding up disk I/O significantly. Instead of
3474 modifying the implementation of dpkg, apt and tasksel (which are the
3475 packages responsible for selecting, fetching and installing packages),
3476 it occurred to me that we could just divert the programs away, replace
3477 them with a simple shell wrapper calling
3478 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3479 Two days ago I decided to test the idea, and wrapped up a simple
3480 implementation for the Debian Edu udeb.
</p
>
3482 <p
>The effect was stunning. In my first test it reduced the running
3483 time of the pkgsel step (installing tasks) from
64 to less than
44
3484 minutes (
20 minutes shaved off the installation) on an old Dell
3485 Latitude D505 machine. I am not quite sure what the optimised time
3486 would have been, as I messed up the testing a bit, causing the debconf
3487 priority to get low enough for two questions to pop up during
3488 installation. As soon as I saw the questions I moved the installation
3489 along, but do not know how long the question were holding up the
3490 installation. I did some more measurements using Debian Edu Jessie,
3491 and got these results. The time measured is the time stamp in
3492 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3493 "pkgsel: finishing up
" lines, if you want to do the same measurement
3494 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3495 timing thus do not depend on how quickly the user handle the tasksel
3498 <p
><table
>
3501 <th
>Machine/setup
</th
>
3502 <th
>Original tasksel
</th
>
3503 <th
>Optimised tasksel
</th
>
3504 <th
>Reduction
</th
>
3508 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3509 <td
>64 min (
07:
46-
08:
50)
</td
>
3510 <td
><44 min (
11:
27-
12:
11)
</td
>
3511 <td
>>20 min
18%
</td
>
3515 <td
>Latitude D505 Roaming LXDE
</td
>
3516 <td
>57 min (
08:
48-
09:
45)
</td
>
3517 <td
>34 min (
07:
43-
08:
17)
</td
>
3518 <td
>23 min
40%
</td
>
3522 <td
>Latitude D505 Minimal
</td
>
3523 <td
>22 min (
10:
37-
10:
59)
</td
>
3524 <td
>11 min (
11:
16-
11:
27)
</td
>
3525 <td
>11 min
50%
</td
>
3529 <td
>Thinkpad X200 Minimal
</td
>
3530 <td
>6 min (
08:
19-
08:
25)
</td
>
3531 <td
>4 min (
08:
04-
08:
08)
</td
>
3532 <td
>2 min
33%
</td
>
3536 <td
>Thinkpad X200 Roaming KDE
</td
>
3537 <td
>19 min (
09:
21-
09:
40)
</td
>
3538 <td
>15 min (
10:
25-
10:
40)
</td
>
3539 <td
>4 min
21%
</td
>
3542 </table
></p
>
3544 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3545 time is spent downloading packages. The connection to the Internet
3546 was
100Mbit/s during testing, so downloading should not be a
3547 significant factor in the measurement. Download typically took a few
3548 seconds to a few minutes, depending on the amount of packages being
3549 installed.
</p
>
3551 <p
>The speedup is implemented by using two hooks in
3552 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3553 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3554 finish-install.d hook to remove the divert at the end of the
3555 installation. I picked the pre-pkgsel.d hook instead of the
3556 post-base-installer.d hook because I test using an ISO without the
3557 eatmydata package included, and the post-base-installer.d hook in
3558 Debian Edu can only operate on packages included in the ISO. The
3559 negative effect of this is that I am unable to activate this
3560 optimization for the kernel installation step in d-i. If the code is
3561 moved to the post-base-installer.d hook, the speedup would be larger
3562 for the entire installation.
</p
>
3564 <p
>I
've implemented this in the
3565 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3566 git repository, and plan to provide the optimization as part of the
3567 Debian Edu installation. If you want to test this yourself, you can
3568 create two files in the installer (or in an udeb). One shell script
3569 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3571 <p
><blockquote
><pre
>
3574 . /usr/share/debconf/confmodule
3576 logger -t my-pkgsel
"info: $*
"
3579 logger -t my-pkgsel
"error: $*
"
3581 override_install() {
3582 apt-install eatmydata || true
3583 if [ -x /target/usr/bin/eatmydata ] ; then
3584 for bin in dpkg apt-get aptitude tasksel ; do
3586 # Test that the file exist and have not been diverted already.
3587 if [ -f /target$file ] ; then
3588 info
"diverting $file using eatmydata
"
3589 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3590 > /target$file.edu
3591 chmod
755 /target$file.edu
3592 in-target dpkg-divert --package debian-edu-config \
3593 --rename --quiet --add $file
3594 ln -sf ./$bin.edu /target$file
3596 error
"unable to divert $file, as it is missing.
"
3600 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3605 </pre
></blockquote
></p
>
3607 <p
>To clean up, another shell script should go into
3608 /usr/lib/finish-install.d/ with code like this:
3610 <p
><blockquote
><pre
>
3612 . /usr/share/debconf/confmodule
3614 logger -t my-finish-install
"error: $@
"
3616 remove_install_override() {
3617 for bin in dpkg apt-get aptitude tasksel ; do
3619 if [ -x /target$file.edu ] ; then
3621 in-target dpkg-divert --package debian-edu-config \
3622 --rename --quiet --remove $file
3625 error
"Missing divert for $file.
"
3628 sync # Flush file buffers before continuing
3631 remove_install_override
3632 </pre
></blockquote
></p
>
3634 <p
>In Debian Edu, I placed both code fragments in a separate script
3635 edu-eatmydata-install and call it from the pre-pkgsel.d and
3636 finish-install.d scripts.
</p
>
3638 <p
>By now you might ask if this change should get into the normal
3639 Debian installer too? I suspect it should, but am not sure the
3640 current debian-installer coordinators find it useful enough. It also
3641 depend on the side effects of the change. I
'm not aware of any, but I
3642 guess we will see if the change is safe after some more testing.
3643 Perhaps there is some package in Debian depending on sync() and
3644 fsync() having effect? Perhaps it should go into its own udeb, to
3645 allow those of us wanting to enable it to do so without affecting
3648 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3649 will break installation of all programs using gnutls because of
3650 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3651 eatmydata package in Debian will solve it.
</p
>
3653 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3654 the optimization work again. And I have discovered that the
3655 dpkg-divert trick is not really needed and implemented a slightly
3656 simpler approach as part of the debian-edu-install package. See
3657 tools/edu-eatmydata-install in the source package.
</p
>
3659 <p
>Update
2014-
11-
11: Unfortunately, a new
3660 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3661 triggering on i386 made it into testing, and broke this installation
3662 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3663 request
768893</a
> is accepted, it should be working again.
</p
>
3668 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3669 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3670 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3671 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3672 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3673 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3674 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3675 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3676 learn that there is a large set of publicly available key servers to
3677 use when looking for peoples public key. So far I have used
3678 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3679 were misbehaving, but those days are ended. The servers I have used
3680 up until yesterday have been slow and some times unavailable. I hope
3681 those problems are gone now.
</p
>
3683 <p
>Behind the round robin DNS entry of the
3684 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3685 there is a pool of more than
100 keyservers which are checked every
3686 day to ensure they are well connected and up to date. It must be
3687 better than what I have used so far. :)
</p
>
3689 <p
>Yesterdays speaker told me that the service is the default
3690 keyserver provided by the default configuration in GnuPG, but this do
3691 not seem to be used in Debian. Perhaps it should?
</p
>
3693 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3696 <p
><blockquote
><pre
>
3697 keyserver pool.sks-keyservers.net
3698 </pre
></blockquote
></p
>
3700 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3701 entries in DNS. Just for fun, I did just that at work, so now every
3702 user of GnuPG at the University of Oslo should find a OpenGPG
3703 keyserver automatically should their need it:
</p
>
3705 <p
><blockquote
><pre
>
3706 % host -t srv _pgpkey-http._tcp.uio.no
3707 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3709 </pre
></blockquote
></p
>
3711 <p
>Now if only
3712 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3713 HKP lookup protocol
</a
> supported finding signature paths, I would be
3714 very happy. It can look up a given key or search for a user ID, but I
3715 normally do not want that, but to find a trust path from my key to
3716 another key. Given a user ID or key ID, I would like to find (and
3717 download) the keys representing a signature path from my key to the
3718 key in question, to be able to get a trust path between the two keys.
3719 This is as far as I can tell not possible today. Perhaps something
3720 for a future version of the protocol?
</p
>
3725 <title>From English wiki to translated PDF and epub via Docbook
</title>
3726 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3727 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3728 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3729 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3730 project
</a
> provide an instruction manual for teachers, system
3731 administrators and other users that contain useful tips for setting up
3732 and maintaining a Debian Edu installation. This text is about how the
3733 text processing of this manual is handled in the project.
</p
>
3735 <p
>One goal of the project is to provide information in the native
3736 language of its users, and for this we need to handle translations.
3737 But we also want to make sure each language contain the same
3738 information, so for this we need a good way to keep the translations
3739 in sync. And we want it to be easy for our users to improve the
3740 documentation, avoiding the need to learn special formats or tools to
3741 contribute, and the obvious way to do this is to make it possible to
3742 edit the documentation using a web browser. We also want it to be
3743 easy for translators to keep the translation up to date, and give them
3744 help in figuring out what need to be translated. Here is the list of
3745 tools and the process we have found trying to reach all these
3748 <p
>We maintain the authoritative source of our manual in the
3749 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3750 wiki
</a
>, as several wiki pages written in English. It consist of one
3751 front page with references to the different chapters, several pages
3752 for each chapter, and finally one
"collection page
" gluing all the
3753 chapters together into one large web page (aka
3754 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3755 AllInOne page
</a
>). The AllInOne page is the one used for further
3756 processing and translations. Thanks to the fact that the
3757 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3758 wiki.debian.org support exporting pages in
3759 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3760 the list of pages to export using the raw version of the AllInOne
3761 page, loop over each of them to generate a Docbook XML version of the
3762 manual. This process also download images and transform image
3763 references to use the locally downloaded images. The generated
3764 Docbook XML files are slightly broken, so some post-processing is done
3765 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3766 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3767 a handfull of images. The XML file can now be used to generate PDF, HTML
3768 and epub versions of the English manual. This is the basic step of
3769 our process, making PDF (using dblatex), HTML (using xsltproc) and
3770 epub (using dbtoepub) version from Docbook XML, and the resulting files
3771 are placed in the debian-edu-doc-en binary package.
</p
>
3773 <p
>But English documentation is not enough for us. We want translated
3774 documentation too, and we want to make it easy for translators to
3775 track the English original. For this we use the
3776 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3777 which allow us to transform the English Docbook XML file into a
3778 translation file (a .pot file), usable with the normal gettext based
3779 translation tools used by those translating free software. The pot
3780 file is used to create and maintain translation files (several .po
3781 files), which the translations update with the native language
3782 translations of all titles, paragraphs and blocks of text in the
3783 original. The next step is combining the original English Docbook XML
3784 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3785 create a translated Docbook XML file (in this case
3786 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3787 translated, if the translation is not complete) Docbook XML file can
3788 then be used like the original to create a PDF, HTML and epub version
3789 of the documentation.
</p
>
3791 <p
>The translators use different tools to edit the .po files. We
3793 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3794 while some use emacs and vi, others can use web based editors like
3795 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3796 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3797 is where the .po file end up, in our git repository. Updated
3798 translations can either be committed directly to git, or submitted as
3799 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3800 against the debian-edu-doc package
</a
>.
</p
>
3802 <p
>One challenge is images, which both might need to be translated (if
3803 they show translated user applications), and are needed in different
3804 formats when creating PDF and HTML versions (epub is a HTML version in
3805 this regard). For this we transform the original PNG images to the
3806 needed density and format during build, and have a way to provide
3807 translated images by storing translated versions in
3808 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3809 package maintainers know more.
</p
>
3811 <p
>If you wonder what the result look like, we provide
3812 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3813 of the documentation packages on the web
</a
>. See for example the
3814 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3815 PDF version
</a
> or the
3816 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3817 HTML version
</a
>. We do not yet build the epub version by default,
3818 but perhaps it will be done in the future.
</p
>
3820 <p
>To learn more, check out
3821 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3822 debian-edu-doc package
</a
>,
3823 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3824 manual on the wiki
</a
> and
3825 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3826 translation instructions
</a
> in the manual.
</p
>
3831 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3832 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3833 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3834 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3835 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3836 related packages relevant for the computer installed automatically.
3837 So I implemented one, using
3838 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3839 package
</a
>. To use it, install the tasksel and isenkram packages and
3840 run tasksel as user root. You should be presented with a new option,
3841 "Hardware specific packages (autodetected by isenkram)
". When you
3842 select it, tasksel will install the packages isenkram claim is fit for
3843 the current hardware, hot pluggable or not.
<p
>
3845 <p
>The implementation is in two files, one is the tasksel menu entry
3846 description, and the other is the script used to extract the list of
3847 packages to install. The first part is in
3848 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3851 <p
><blockquote
><pre
>
3854 Description: Hardware specific packages (autodetected by isenkram)
3855 Based on the detected hardware various hardware specific packages are
3857 Test-new-install: mark show
3859 Packages: for-current-hardware
3860 </pre
></blockquote
></p
>
3862 <p
>The second part is in
3863 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3866 <p
><blockquote
><pre
>
3871 isenkram-autoinstall-firmware -l
3873 </pre
></blockquote
></p
>
3875 <p
>All in all, a very short and simple implementation making it
3876 trivial to install the hardware dependent package we all may want to
3877 have installed on our machines. I
've not been able to find a way to
3878 get tasksel to tell you exactly which packages it plan to install
3879 before doing the installation. So if you are curious or careful,
3880 check the output from the isenkram-* command line tools first.
</p
>
3882 <p
>The information about which packages are handling which hardware is
3883 fetched either from the isenkram package itself in
3884 /usr/share/isenkram/, from git.debian.org or from the APT package
3885 database (using the Modaliases header). The APT package database
3886 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3887 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3888 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3889 the python-apt code (bug
3890 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3891 workaround I was able to get rid of the file descriptor leak and
3892 reduce the memory leak from ~
30 MiB per hardware detection down to
3893 around
2 MiB per hardware detection. It should make the desktop
3894 daemon a lot more useful. The fix is in version
0.7 uploaded to
3895 unstable today.
</p
>
3897 <p
>I believe the current way of mapping hardware to packages in
3898 Isenkram is is a good draft, but in the future I expect isenkram to
3899 use the AppStream data source for this. A proposal for getting proper
3900 AppStream support into Debian is floating around as
3901 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3902 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3903 project
</a
> will take place this summer to improve the situation. I
3904 look forward to seeing the result, and welcome patches for isenkram to
3905 start using the information when it is ready.
</p
>
3907 <p
>If you want your package to map to some specific hardware, either
3908 add a
"Xb-Modaliases
" header to your control file like I did in
3909 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3910 package
</a
> or submit a bug report with the details to the isenkram
3912 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3913 blog posts tagged isenkram
</a
> for details on the notation. I expect
3914 the information will be migrated to AppStream eventually, but for the
3915 moment I got no better place to store it.
</p
>
3920 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3921 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3922 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3923 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3924 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3925 project
</a
> is working on providing the software and hardware to make
3926 it easy for non-technical people to host their data and communication
3927 at home, and being able to communicate with their friends and family
3928 encrypted and away from prying eyes. It is still going strong, and
3929 today a major mile stone was reached.
</p
>
3931 <p
>Today, the last of the packages currently used by the project to
3932 created the system images were accepted into Debian Unstable. It was
3933 the freedombox-setup package, which is used to configure the images
3934 during build and on the first boot. Now all one need to get going is
3935 the build code from the freedom-maker git repository and packages from
3936 Debian. And once the freedombox-setup package enter testing, we can
3937 build everything directly from Debian. :)
</p
>
3939 <p
>Some key packages used by Freedombox are
3940 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3941 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3942 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3943 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3944 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3945 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3946 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3947 are plans to integrate more packages into the setup. User
3948 documentation is maintained on the Debian wiki. Please
3949 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3950 the manual
</a
> and help us improve it.
</p
>
3952 <p
>To test for yourself and create boot images with the FreedomBox
3953 setup, run this on a Debian machine using a user with sudo rights to
3954 become root:
</p
>
3956 <p
><pre
>
3957 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3958 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3960 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3962 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3963 </pre
></p
>
3965 <p
>Root access is needed to run debootstrap and mount loopback
3966 devices. See the README in the freedom-maker git repo for more
3967 details on the build. If you do not want all three images, trim the
3968 make line. Note that the virtualbox-image target is not really
3969 virtualbox specific. It create a x86 image usable in kvm, qemu,
3970 vmware and any other x86 virtual machine environment. You might need
3971 the version of vmdebootstrap in Jessie to get the build working, as it
3972 include fixes for a race condition with kpartx.
</p
>
3974 <p
>If you instead want to install using a Debian CD and the preseed
3975 method, boot a Debian Wheezy ISO and use this boot argument to load
3976 the preseed values:
</p
>
3978 <p
><pre
>
3979 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3980 </pre
></p
>
3982 <p
>I have not tested it myself the last few weeks, so I do not know if
3983 it still work.
</p
>
3985 <p
>If you wonder how to help, one task you could look at is using
3986 systemd as the boot system. It will become the default for Linux in
3987 Jessie, so we need to make sure it is usable on the Freedombox. I did
3988 a simple test a few weeks ago, and noticed dnsmasq failed to start
3989 during boot when using systemd. I suspect there are other problems
3990 too. :) To detect problems, there is a test suite included, which can
3991 be run from the plinth web interface.
</p
>
3993 <p
>Give it a go and let us know how it goes on the mailing list, and help
3994 us get the new release published. :) Please join us on
3995 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3996 irc.debian.org)
</a
> and
3997 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3998 mailing list
</a
> if you want to help make this vision come true.
</p
>
4003 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4004 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4005 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4006 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4007 <description><p
>For a while now, I have been looking for a sensible offsite backup
4008 solution for use at home. My requirements are simple, it must be
4009 cheap and locally encrypted (in other words, I keep the encryption
4010 keys, the storage provider do not have access to my private files).
4011 One idea me and my friends had many years ago, before the cloud
4012 storage providers showed up, was to use Google mail as storage,
4013 writing a Linux block device storing blocks as emails in the mail
4014 service provided by Google, and thus get heaps of free space. On top
4015 of this one can add encryption, RAID and volume management to have
4016 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4017 I never found time to implement such system. But the last few weeks I
4018 have looked at a system called
4019 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4020 mounted network backed file system with the features I need.
</p
>
4022 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4023 handling several different storage providers, any with Amazon S3,
4024 Google Drive or OpenStack API. There are heaps of such storage
4025 providers. S3QL can also use a local directory as storage, which
4026 combined with sshfs allow for file storage on any ssh server. S3QL
4027 include support for encryption, compression, de-duplication, snapshots
4028 and immutable file systems, allowing me to mount the remote storage as
4029 a local mount point, look at and use the files as if they were local,
4030 while the content is stored in the cloud as well. This allow me to
4031 have a backup that should survive fire. The file system can not be
4032 shared between several machines at the same time, as only one can
4033 mount it at the time, but any machine with the encryption key and
4034 access to the storage service can mount it if it is unmounted.
</p
>
4036 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4037 package is included already. So to get started, run
<tt
>apt-get
4038 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4039 Greenqloud, after reading their nice recipe on
4040 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4041 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4042 in Iceland more than those in USA when it come to keeping my personal
4043 data safe and private, and thus would rather spend money on a company
4044 in Iceland. Another nice recipe is available from the article
4045 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4046 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4047 Admin magazine. When the provider is picked, figure out how to get
4048 the API key needed to connect to the storage API. With Greencloud,
4049 the key did not show up until I had added payment details to my
4052 <p
>Armed with the API access details, it is time to create the file
4053 system. First, create a new bucket in the cloud. This bucket is the
4054 file system storage area. I picked a bucket name reflecting the
4055 machine that was going to store data there, but any name will do.
4056 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4057 the API login and password, and a locally created password. Store it
4058 all in ~root/.s3ql/authinfo2 like this:
4060 <p
><blockquote
><pre
>
4062 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4063 backend-login: API-login
4064 backend-password: API-password
4065 fs-passphrase: local-password
4066 </pre
></blockquote
></p
>
4068 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4069 but any sensible way to create a fairly random password should do it.
4070 Armed with these details, it is now time to run mkfs, entering the API
4071 details and password to create it:
</p
>
4073 <p
><blockquote
><pre
>
4074 # mkdir -m
700 /var/lib/s3ql-cache
4075 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4076 --ssl s3c://s.greenqloud.com:
443/bucket-name
4077 Enter backend login:
4078 Enter backend password:
4079 Before using S3QL, make sure to read the user
's guide, especially
4080 the
'Important Rules to Avoid Loosing Data
' section.
4081 Enter encryption password:
4082 Confirm encryption password:
4083 Generating random encryption key...
4084 Creating metadata tables...
4094 Compressing and uploading metadata...
4095 Wrote
0.00 MB of compressed metadata.
4096 #
</pre
></blockquote
></p
>
4098 <p
>The next step is mounting the file system to make the storage available.
4100 <p
><blockquote
><pre
>
4101 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4102 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4103 Using
4 upload threads.
4104 Downloading and decompressing metadata...
4114 Mounting filesystem...
4116 Filesystem Size Used Avail Use% Mounted on
4117 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4119 </pre
></blockquote
></p
>
4121 <p
>The file system is now ready for use. I use rsync to store my
4122 backups in it, and as the metadata used by rsync is downloaded at
4123 mount time, no network traffic (and storage cost) is triggered by
4124 running rsync. To unmount, one should not use the normal umount
4125 command, as this will not flush the cache to the cloud storage, but
4126 instead running the umount.s3ql command like this:
4128 <p
><blockquote
><pre
>
4131 </pre
></blockquote
></p
>
4133 <p
>There is a fsck command available to check the file system and
4134 correct any problems detected. This can be used if the local server
4135 crashes while the file system is mounted, to reset the
"already
4136 mounted
" flag. This is what it look like when processing a working
4137 file system:
</p
>
4139 <p
><blockquote
><pre
>
4140 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4141 Using cached metadata.
4142 File system seems clean, checking anyway.
4143 Checking DB integrity...
4144 Creating temporary extra indices...
4145 Checking lost+found...
4146 Checking cached objects...
4147 Checking names (refcounts)...
4148 Checking contents (names)...
4149 Checking contents (inodes)...
4150 Checking contents (parent inodes)...
4151 Checking objects (reference counts)...
4152 Checking objects (backend)...
4153 ..processed
5000 objects so far..
4154 ..processed
10000 objects so far..
4155 ..processed
15000 objects so far..
4156 Checking objects (sizes)...
4157 Checking blocks (referenced objects)...
4158 Checking blocks (refcounts)...
4159 Checking inode-block mapping (blocks)...
4160 Checking inode-block mapping (inodes)...
4161 Checking inodes (refcounts)...
4162 Checking inodes (sizes)...
4163 Checking extended attributes (names)...
4164 Checking extended attributes (inodes)...
4165 Checking symlinks (inodes)...
4166 Checking directory reachability...
4167 Checking unix conventions...
4168 Checking referential integrity...
4169 Dropping temporary indices...
4170 Backing up old metadata...
4180 Compressing and uploading metadata...
4181 Wrote
0.89 MB of compressed metadata.
4183 </pre
></blockquote
></p
>
4185 <p
>Thanks to the cache, working on files that fit in the cache is very
4186 quick, about the same speed as local file access. Uploading large
4187 amount of data is to me limited by the bandwidth out of and into my
4188 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4189 which is very close to my upload speed, and downloading the same
4190 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4191 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4192 network, not the file system code. I do not know what a good cache
4193 size would be, but suspect that the cache should e larger than your
4194 working set.
</p
>
4196 <p
>I mentioned that only one machine can mount the file system at the
4197 time. If another machine try, it is told that the file system is
4200 <p
><blockquote
><pre
>
4201 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4202 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4203 Using
8 upload threads.
4204 Backend reports that fs is still mounted elsewhere, aborting.
4206 </pre
></blockquote
></p
>
4208 <p
>The file content is uploaded when the cache is full, while the
4209 metadata is uploaded once every
24 hour by default. To ensure the
4210 file system content is flushed to the cloud, one can either umount the
4211 file system, or ask S3QL to flush the cache and metadata using
4214 <p
><blockquote
><pre
>
4215 # s3qlctrl upload-meta /s3ql
4216 # s3qlctrl flushcache /s3ql
4218 </pre
></blockquote
></p
>
4220 <p
>If you are curious about how much space your data uses in the
4221 cloud, and how much compression and deduplication cut down on the
4222 storage usage, you can use s3qlstat on the mounted file system to get
4225 <p
><blockquote
><pre
>
4227 Directory entries:
9141
4230 Total data size:
22049.38 MB
4231 After de-duplication:
21955.46 MB (
99.57% of total)
4232 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4233 Database size:
2.39 MB (uncompressed)
4234 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4236 </pre
></blockquote
></p
>
4238 <p
>I mentioned earlier that there are several possible suppliers of
4239 storage. I did not try to locate them all, but am aware of at least
4240 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4241 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4242 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4243 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4244 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4245 accept payment in Bitcoin. Pick one that suit your need. Some of
4246 them provide several GiB of free storage, but the prize models are
4247 quite different and you will have to figure out what suits you
4250 <p
>While researching this blog post, I had a look at research papers
4251 and posters discussing the S3QL file system. There are several, which
4252 told me that the file system is getting a critical check by the
4253 science community and increased my confidence in using it. One nice
4255 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4256 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4257 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4258 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4259 and Pamela Smith. Please have a look.
</p
>
4261 <p
>Given my problems with different file systems earlier, I decided to
4262 check out the mounted S3QL file system to see if it would be usable as
4263 a home directory (in other word, that it provided POSIX semantics when
4264 it come to locking and umask handling etc). Running
4265 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4266 test code to check file system semantics
</a
>, I was happy to discover that
4267 no error was found. So the file system can be used for home
4268 directories, if one chooses to do so.
</p
>
4270 <p
>If you do not want a locally file system, and want something that
4271 work without the Linux fuse file system, I would like to mention the
4272 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4273 provide locally encrypted backup using a command line client. It have
4274 a nicer access control system, where one can split out read and write
4275 access, allowing some systems to write to the backup and others to
4276 only read from it.
</p
>
4278 <p
>As usual, if you use Bitcoin and want to show your support of my
4279 activities, please send Bitcoin donations to my address
4280 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4285 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4286 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4287 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4288 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4289 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4290 project
</a
> is working on providing the software and hardware for
4291 making it easy for non-technical people to host their data and
4292 communication at home, and being able to communicate with their
4293 friends and family encrypted and away from prying eyes. It has been
4294 going on for a while, and is slowly progressing towards a new test
4295 release (
0.2).
</p
>
4297 <p
>And what day could be better than the Pi day to announce that the
4298 new version will provide
"hard drive
" / SD card / USB stick images for
4299 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4300 system), and can also be installed using a Debian installer preseed
4301 file. The Debian based Freedombox is now based on Debian Jessie,
4302 where most of the needed packages used are already present. Only one,
4303 the freedombox-setup package, is missing. To try to build your own
4304 boot image to test the current status, fetch the freedom-maker scripts
4306 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4307 with a user with sudo access to become root:
4310 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4312 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4313 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4315 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4318 <p
>Root access is needed to run debootstrap and mount loopback
4319 devices. See the README for more details on the build. If you do not
4320 want all three images, trim the make line. But note that thanks to
<a
4321 href=
"https://bugs.debian.org/
741407">a race condition in
4322 vmdebootstrap
</a
>, the build might fail without the patch to the
4323 kpartx call.
</p
>
4325 <p
>If you instead want to install using a Debian CD and the preseed
4326 method, boot a Debian Wheezy ISO and use this boot argument to load
4327 the preseed values:
</p
>
4330 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4333 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4334 recently introduced bug in apt in Jessie
</a
>, the installer will
4335 currently hang while setting up APT sources. Killing the
4336 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4337 installation will get the installation going. This affect all
4338 installations in Jessie, and I expect it will be fixed soon.
</p
>
4340 <p
>Give it a go and let us know how it goes on the mailing list, and help
4341 us get the new release published. :) Please join us on
4342 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4343 irc.debian.org)
</a
> and
4344 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4345 mailing list
</a
> if you want to help make this vision come true.
</p
>
4350 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4351 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4353 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4354 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4355 innetgr tools, because I needed them in
4356 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4357 ng-utils, and it has served me well. I placed the project under the
4358 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4359 repository. But many years ago, the CVS repository was dropped (lost,
4360 not migrated to new hardware, not sure), and the project have lacked a
4361 proper home since then.
</p
>
4363 <p
>Last summer, I had a look at the package and made a new release
4364 fixing a irritating crash bug, but was unable to store the changes in
4365 a proper source control system. I applied for a project on
4366 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4367 to follow up on it. Until today. :)
</p
>
4369 <p
>After many hours of cleaning and migration, the ng-utils project
4370 now have a new home, and a git repository with the highlight of the
4371 history of the project. I published all release tarballs and imported
4372 them into the git repository. As the project is really stable and not
4373 expected to gain new features any time soon, I decided to make a new
4374 release and call it
1.0. Visit the new project home on
4375 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4376 if you want to check it out. The new version is also uploaded into
4377 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4382 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4383 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4384 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4385 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4386 <description><p
>A few days ago I decided to try to help the Hurd people to get
4387 their changes into sysvinit, to allow them to use the normal sysvinit
4388 boot system instead of their old one. This follow up on the
4389 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4390 Google Summer of Code work
</a
> done last summer by Justus Winter to
4391 get Debian on Hurd working more like Debian on Linux. To get started,
4392 I downloaded a prebuilt hard disk image from
4393 <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
>,
4394 and started it using virt-manager.
</p
>
4396 <p
>The first think I had to do after logging in (root without any
4397 password) was to get the network operational. I followed
4398 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4399 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4400 commands as root to get the machine to accept a IP address from the
4401 kvm internal DHCP server:
</p
>
4403 <p
><blockquote
><pre
>
4404 settrans -fgap /dev/netdde /hurd/netdde
4405 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4406 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4408 </pre
></blockquote
></p
>
4410 <p
>After this, the machine had internet connectivity, and I could
4411 upgrade it and install the sysvinit packages from experimental and
4412 enable it as the default boot system in Hurd.
</p
>
4414 <p
>But before I did that, I set a password on the root user, as ssh is
4415 running on the machine it for ssh login to work a password need to be
4416 set. Also, note that a bug somewhere in openssh on Hurd block
4417 compression from working. Remember to turn that off on the client
4420 <p
>Run these commands as root to upgrade and test the new sysvinit
4423 <p
><blockquote
><pre
>
4424 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4425 deb http://http.debian.net/debian/ experimental main
4428 apt-get dist-upgrade
4429 apt-get install -t experimental initscripts sysv-rc sysvinit \
4430 sysvinit-core sysvinit-utils
4431 update-alternatives --config runsystem
4432 </pre
></blockquote
></p
>
4434 <p
>To reboot after switching boot system, you have to use
4435 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4436 yet a sysvinit process able to receive the signals from the normal
4437 'reboot
' command. After switching to sysvinit as the boot system,
4438 upgrading every package and rebooting, the network come up with DHCP
4439 after boot as it should, and the settrans/pkill hack mentioned at the
4440 start is no longer needed. But for some strange reason, there are no
4441 longer any login prompt in the virtual console, so I logged in using
4444 <p
>Note that there are some race conditions in Hurd making the boot
4445 fail some times. No idea what the cause is, but hope the Hurd porters
4446 figure it out. At least Justus said on IRC (#debian-hurd on
4447 irc.debian.org) that they are aware of the problem. A way to reduce
4448 the impact is to upgrade to the Hurd packages built by Justus by
4449 adding this repository to the machine:
</p
>
4451 <p
><blockquote
><pre
>
4452 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4453 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4455 </pre
></blockquote
></p
>
4457 <p
>At the moment the prebuilt virtual machine get some packages from
4458 http://ftp.debian-ports.org/debian, because some of the packages in
4459 unstable do not yet include the required patches that are lingering in
4460 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4462 <p
><blockquote
><pre
>
4463 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4464 i emacs - GNU Emacs editor (metapackage)
4465 i gdb - GNU Debugger
4466 i hurd-recommended - Miscellaneous translators
4467 i isc-dhcp-client - ISC DHCP client
4468 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4469 i libc-bin - Embedded GNU C Library: Binaries
4470 i libc-dev-bin - Embedded GNU C Library: Development binaries
4471 i libc0.3 - Embedded GNU C Library: Shared libraries
4472 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4473 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4474 i multiarch-support - Transitional package to ensure multiarch compatibilit
4475 i A x11-common - X Window System (X.Org) infrastructure
4476 i xorg - X.Org X Window System
4477 i A xserver-xorg - X.Org X server
4478 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4480 </pre
></blockquote
></p
>
4482 <p
>All in all, testing hurd has been an interesting experience. :)
4483 X.org did not work out of the box and I never took the time to follow
4484 the porters instructions to fix it. This time I was interested in the
4485 command line stuff.
<p
>
4490 <title>New chrpath release
0.16</title>
4491 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4493 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4494 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4495 find problems in C, C++ and Java code using static source code
4496 analysis. It can detect a lot of different problems, and is very
4497 useful to find memory and locking bugs in the error handling part of
4498 the source. The company behind it provide
4499 <a href=
"https://scan.coverity.com/
">check of free software projects as
4500 a community service
</a
>, and many hundred free software projects are
4501 already checked. A few days ago I decided to have a closer look at
4502 the Coverity system, and discovered that the
4503 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4504 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4505 projects I am involved with was already registered. But these are
4506 fairly big, and I would also like to have a small and easy project to
4507 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4508 checking of the chrpath project
</a
>. It was
4509 added to the checker and discovered seven potential defects. Six of
4510 these were real, mostly resource
"leak
" when the program detected an
4511 error. Nothing serious, as the resources would be released a fraction
4512 of a second later when the program exited because of the error, but it
4513 is nice to do it right in case the source of the program some time in
4514 the future end up in a library. Having fixed all defects and added
4515 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4516 mailing list for the chrpath developers
</a
>, I decided it was time to
4517 publish a new release. These are the release notes:
</p
>
4519 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4523 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4524 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4525 <li
>Mention new project mailing list in the documentation.
</li
>
4530 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4531 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4532 project if something is wrong with the new release. The test suite
4533 did not discover any old errors, so if you find a new one, please also
4534 include a test suite check.
</p
>
4539 <title>New chrpath release
0.15</title>
4540 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4541 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4542 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4543 <description><p
>After many years break from the package and a vain hope that
4544 development would be continued by someone else, I finally pulled my
4545 acts together this morning and wrapped up a new release of chrpath,
4546 the command line tool to modify the rpath and runpath of already
4547 compiled ELF programs. The update was triggered by the persistence of
4548 Isha Vishnoi at IBM, which needed a new config.guess file to get
4549 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4550 is working on. I checked the
4551 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4552 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4553 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4554 packages for interesting patches (failed to find the source from
4555 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4556 These are the release notes:
</p
>
4558 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4562 <li
>Updated config.sub and config.guess from the GNU project to work
4563 with newer architectures. Thanks to isha vishnoi for the heads
4566 <li
>Updated README with current URLs.
</li
>
4568 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4569 Matthias Klose.
</li
>
4571 <li
>Added missing help for -k|--keepgoing option, using patch by
4572 Petr Machata found in Fedora.
</li
>
4574 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4575 .dynamic is a NULL terminated string. Based on patch found in
4576 Fedora credited Axel Thimm and Christian Krause.
</li
>
4581 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4582 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4583 project if something is wrong with the new release. The test suite
4584 did not discover any old errors, so if you find a new one, please also
4585 include a testsuite check.
</p
>
4590 <title>Debian init.d boot script example for rsyslog
</title>
4591 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4592 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4593 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4594 <description><p
>If one of the points of switching to a new init system in Debian is
4595 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4596 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4597 init.d scripts at all. Here is an example init.d script, ie a rewrite
4598 of /etc/init.d/rsyslog:
</p
>
4600 <p
><pre
>
4601 #!/lib/init/init-d-script
4604 # Required-Start: $remote_fs $time
4605 # Required-Stop: umountnfs $time
4606 # X-Stop-After: sendsigs
4607 # Default-Start:
2 3 4 5
4608 # Default-Stop:
0 1 6
4609 # Short-Description: enhanced syslogd
4610 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4611 # It is quite compatible to stock sysklogd and can be
4612 # used as a drop-in replacement.
4614 DESC=
"enhanced syslogd
"
4615 DAEMON=/usr/sbin/rsyslogd
4616 </pre
></p
>
4618 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4619 script was
137 lines, and the above is just
15 lines, most of it meta
4620 info/comments.
</p
>
4622 <p
>How to do this, you ask? Well, one create a new script
4623 /lib/init/init-d-script looking something like this:
4625 <p
><pre
>
4628 # Define LSB log_* functions.
4629 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4630 # and status_of_proc is working.
4631 . /lib/lsb/init-functions
4634 # Function that starts the daemon/service
4640 #
0 if daemon has been started
4641 #
1 if daemon was already running
4642 #
2 if daemon could not be started
4643 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4645 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4648 # Add code here, if necessary, that waits for the process to be ready
4649 # to handle requests from services started subsequently which depend
4650 # on this one. As a last resort, sleep for some time.
4654 # Function that stops the daemon/service
4659 #
0 if daemon has been stopped
4660 #
1 if daemon was already stopped
4661 #
2 if daemon could not be stopped
4662 # other if a failure occurred
4663 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4664 RETVAL=
"$?
"
4665 [
"$RETVAL
" =
2 ]
&& return
2
4666 # Wait for children to finish too if this is a daemon that forks
4667 # and if the daemon is only ever run from this initscript.
4668 # If the above conditions are not satisfied then add some other code
4669 # that waits for the process to drop all resources that could be
4670 # needed by services started subsequently. A last resort is to
4671 # sleep for some time.
4672 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4673 [
"$?
" =
2 ]
&& return
2
4674 # Many daemons don
't delete their pidfiles when they exit.
4676 return
"$RETVAL
"
4680 # Function that sends a SIGHUP to the daemon/service
4684 # If the daemon can reload its configuration without
4685 # restarting (for example, when it is sent a SIGHUP),
4686 # then implement that here.
4688 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4693 scriptbasename=
"$(basename $
1)
"
4694 echo
"SN: $scriptbasename
"
4695 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4696 script=
"$
1"
4703 NAME=$(basename $DAEMON)
4704 PIDFILE=/var/run/$NAME.pid
4706 # Exit if the package is not installed
4707 #[ -x
"$DAEMON
" ] || exit
0
4709 # Read configuration variable file if it is present
4710 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4712 # Load the VERBOSE setting and other rcS variables
4715 case
"$
1" in
4717 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4719 case
"$?
" in
4720 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4721 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4725 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4727 case
"$?
" in
4728 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4729 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4733 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4735 #reload|force-reload)
4737 # If do_reload() is not implemented then leave this commented out
4738 # and leave
'force-reload
' as an alias for
'restart
'.
4740 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4744 restart|force-reload)
4746 # If the
"reload
" option is implemented then remove the
4747 #
'force-reload
' alias
4749 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4751 case
"$?
" in
4754 case
"$?
" in
4756 1) log_end_msg
1 ;; # Old process is still running
4757 *) log_end_msg
1 ;; # Failed to start
4767 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4773 </pre
></p
>
4775 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4776 lot. I did not really polish the approach, so it might not always
4777 work out of the box, but you get the idea. I did not try very hard to
4778 optimize it nor make it more robust either.
</p
>
4780 <p
>A better argument for switching init system in Debian than reducing
4781 the size of init scripts (which is a good thing to do anyway), is to
4782 get boot system that is able to handle the kernel events sensibly and
4783 robustly, and do not depend on the boot to run sequentially. The boot
4784 and the kernel have not behaved sequentially in years.
</p
>
4789 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4790 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4791 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4792 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4793 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4794 remote display access is the preferred solution with oVirt and RedHat
4795 Enterprise Virtualization, and I was sad to discover the other day
4796 that the browser plugin needed to use these systems seamlessly was
4797 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4798 for a package
</a
> was from
2012-
04-
10 with no progress since
4799 2013-
04-
01, so I decided to wrap up a package based on the great work
4800 from Cajus Pollmeier and put it in a collab-maint maintained git
4801 repository to get a package I could use. I would very much like
4802 others to help me maintain the package (or just take over, I do not
4803 mind), but as no-one had volunteered so far, I just uploaded it to
4804 NEW. I hope it will be available in Debian in a few days.
</p
>
4806 <p
>The source is now available from
4807 <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
>
4812 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4813 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4814 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4815 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4816 <description><p
>The
4817 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4818 program is a a very nice system to create virtual machine images. It
4819 create a image file, add a partition table, mount it and run
4820 debootstrap in the mounted directory to create a Debian system on a
4821 stick. Yesterday, I decided to try to teach it how to make images for
4822 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4823 of a plan to simplify the build system for
4824 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4825 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4826 the virtualbox images, but its current build system made multistrap
4827 based system for Dreamplug images, and it is lacking support for
4828 Raspberry Pi.
</p
>
4830 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4831 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4832 code and adjusted it to be able to build armel images on my amd64
4833 Debian laptop. I ended up giving vmdebootstrap five new options,
4834 allowing me to replicate the image creation process I use to make
4835 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4836 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4837 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4838 call debootstrap with --foreign and to copy the handler into the
4839 generated chroot before running the second stage. This allow
4840 vmdebootstrap to create armel images on an amd64 host. Next I added
4841 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4842 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4843 given file system type, allowing me to create an image with a vfat
4844 partition for the /boot/ stuff. I also added a
<tt
>--variant
4845 variant
</tt
> option to allow me to create smaller images without the
4846 Debian base system packages installed. Finally, I added an option
4847 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4848 as a boot loader. It is not needed on the Raspberry Pi and probably
4849 most other non-x86 architectures. The changes were accepted by the
4850 upstream author of vmdebootstrap yesterday and today, and is now
4852 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4853 upstream project page
</a
>.
</p
>
4855 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4856 create a small script (the customize script) to add the non-free
4857 binary blob needed to boot the Raspberry Pi and the APT source
4860 <p
><pre
>
4862 set -e # Exit on first error
4863 rootdir=
"$
1"
4864 cd
"$rootdir
"
4865 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4866 deb http://http.debian.net/debian/ jessie main contrib non-free
4868 # Install non-free binary blob needed to boot Raspberry Pi. This
4869 # install a kernel somewhere too.
4870 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4871 -O $rootdir/usr/bin/rpi-update
4872 chmod a+x $rootdir/usr/bin/rpi-update
4873 mkdir -p $rootdir/lib/modules
4874 touch $rootdir/boot/start.elf
4875 chroot $rootdir rpi-update
4876 </pre
></p
>
4878 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4879 to build the image:
</p
>
4882 sudo ./vmdebootstrap \
4885 --distribution jessie \
4886 --mirror http://http.debian.net/debian \
4895 --root-password raspberry \
4896 --hostname raspberrypi \
4897 --foreign /usr/bin/qemu-arm-static \
4898 --customize `pwd`/customize \
4900 --package git-core \
4901 --package binutils \
4902 --package ca-certificates \
4905 </pre
></p
>
4907 <p
>The list of packages being installed are the ones needed by
4908 rpi-update to make the image bootable on the Raspberry Pi, with the
4909 exception of netbase, which is needed by debootstrap to find
4910 /etc/hosts with the minbase variant. I really wish there was a way to
4911 set up an Raspberry Pi using only packages in the Debian archive, but
4912 that is not possible as far as I know, because it boots from the GPU
4913 using a non-free binary blob.
</p
>
4915 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4916 probably a few others installed. I have not checked the complete
4917 build dependency list.
</p
>
4919 <p
>The resulting image will not use the hardware floating point unit
4920 on the Raspberry PI, because the armel architecture in Debian is not
4921 optimized for that use. So the images created will be a bit slower
4922 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4927 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4928 <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>
4929 <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>
4930 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4931 <description><p
>The last few days I came across a few good causes that should get
4932 wider attention. I recommend signing and donating to each one of
4935 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4936 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4937 Women program which is a Google Summer of Code like initiative to get
4938 more women involved in free software. One debian sponsor has offered
4939 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4940 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4941 hope you will to. :)
</p
>
4943 <p
>And the Electronic Frontier Foundation just announced plans to
4944 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4945 documentaries about the excessive spying
</a
> on every Internet user that
4946 take place these days, and their need to fund the work. I
've already
4947 donated. Are you next?
</p
>
4949 <p
>For my Norwegian audience, the organisation Studentenes og
4950 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4951 statement under the heading
4952 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4953 Access
</a
> for those of us asking for more focus on open access in the
4954 Norwegian government. So far
499 signatures. I hope you will sign it
4960 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4961 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4962 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4963 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4964 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4965 project
</a
> have been going on for a while, and have presented the
4966 vision, ideas and solution several places. Here is a little
4967 collection of videos of talks and presentation of the project.
</p
>
4971 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4972 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4974 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4975 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4977 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4978 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4979 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4980 (Youtube)
</li
>
4982 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4983 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4985 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4986 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4988 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4989 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4990 York City in
2012</a
> (Youtube)
</li
>
4992 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4993 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4994 (Youtube)
</li
>
4996 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4997 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4999 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5000 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5002 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5003 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5004 2013</a
> (Youtube)
</li
>
5008 <p
>A larger list is available from
5009 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5010 Freedombox Wiki
</a
>.
</p
>
5012 <p
>On other news, I am happy to report that Freedombox based on Debian
5013 Jessie is coming along quite well, and soon both Owncloud and using
5014 Tor should be available for testers of the Freedombox solution. :) In
5015 a few weeks I hope everything needed to test it is included in Debian.
5016 The withsqlite package is already in Debian, and the plinth package is
5017 pending in NEW. The third and vital part of that puzzle is the
5018 metapackage/setup framework, which is still pending an upload. Join
5019 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5020 (#freedombox on irc.debian.org)
</a
> and
5021 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5022 mailing list
</a
> if you want to help make this vision come true.
</p
>
5027 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5028 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5029 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5030 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5031 <description><p
>I was introduced to the
5032 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5033 in
2010, when Eben Moglen presented his vision about serving the need
5034 of non-technical people to keep their personal information private and
5035 within the legal protection of their own homes. The idea is to give
5036 people back the power over their network and machines, and return
5037 Internet back to its intended peer-to-peer architecture. Instead of
5038 depending on a central service, the Freedombox will give everyone
5039 control over their own basic infrastructure.
</p
>
5041 <p
>I
've intended to join the effort since then, but other tasks have
5042 taken priority. But this summers nasty news about the misuse of trust
5043 and privilege exercised by the
"western
" intelligence gathering
5044 communities increased my eagerness to contribute to a point where I
5045 actually started working on the project a while back.
</p
>
5047 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5048 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5049 create a simple and cheap Debian based appliance that anyone can hook
5050 up in their home and get access to secure and private services and
5051 communication. The initial deployment platform have been the
5052 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5053 which is a piece of hardware I do not own. So to be able to test what
5054 the current Freedombox setup look like, I had to come up with a way to install
5055 it on some hardware I do have access to. I have rewritten the
5056 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5057 image build framework to use .deb packages instead of only copying
5058 setup into the boot images, and thanks to this rewrite I am able to
5059 set up any machine supported by Debian Wheezy as a Freedombox, using
5060 the previously mentioned deb (and a few support debs for packages
5061 missing in Debian).
</p
>
5063 <p
>The current Freedombox setup consist of a set of bootstrapping
5065 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5066 and a administrative web interface
5067 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5068 withsqlite), as well as a privacy enhancing proxy based on
5069 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5070 (freedombox-privoxy). There is also a web/javascript based XMPP
5071 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5072 trying (unsuccessfully so far) to talk to the XMPP server
5073 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5074 web interface is pluggable, and the goal is to use it to enable OpenID
5075 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5076 this is really working yet, see
5077 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5078 project TODO
</a
> for links to GIT repositories. Most of the code is
5079 on github at the moment. The HTTP proxy is operational out of the
5080 box, and the admin web interface can be used to add/remove plinth
5081 users. I
've not been able to do anything else with it so far, but
5082 know there are several branches spread around github and other places
5083 with lots of half baked features.
</p
>
5085 <p
>Anyway, if you want to have a look at the current state, the
5086 following recipes should work to give you a test machine to poke
5089 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5093 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5094 <li
>Boot from it, either as CD or USB stick.
</li
>
5095 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5096 to the Debian installer:
<p
>
5097 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5099 <li
>Answer the few language/region/password questions and pick disk to
5100 install on.
</li
>
5102 <li
>When the installation is finished and the machine have rebooted a
5103 few times, your Freedombox is ready for testing.
</li
>
5107 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5111 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5112 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5113 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5115 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5116 </pre
></li
>
5117 <li
><p
>Run this as root:
</p
>
5119 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5122 apt-get install freedombox-setup
5123 /usr/lib/freedombox/setup
5124 </pre
></li
>
5125 <li
>Reboot into your freshly created Freedombox.
</li
>
5129 <p
>You can test it on other architectures too, but because the
5130 freedombox-privoxy package is binary, it will only work as intended on
5131 the architectures where I have had time to build the binary and put it
5132 in my APT repository. But do not let this stop you. It is only a
5133 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5135 <p
>Note that by default Freedombox is a DHCP server on the
5136 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5137 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5138 disable
</tt
>" as root.
</p
>
5140 <p
>Please let me know if this works for you, or if you have any
5141 problems. We gather on the IRC channel
5142 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5143 irc.debian.org and the
5144 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5145 mailing list
</a
>.
</p
>
5147 <p
>Once you get your freedombox operational, you can visit
5148 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5149 welcome screen (dead end - do not be surprised if you are unable to
5150 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5151 to look at the rest of plinth. The default user is
'admin
' and the
5152 default password is
'secret
'.
</p
>
5157 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5158 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5159 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5160 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5161 <description><p
>Earlier, I reported about
5162 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5163 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5164 told by IBM that the original disk should be thrown away. And as
5165 there no longer was a problem if I bricked the firmware, I decided
5166 today to try to install Intel firmware to replace the Lenovo firmware
5167 currently on the disk.
</p
>
5169 <p
>I searched the Intel site for firmware, and found
5170 <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
>
5171 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5172 according to the site should contain the latest firmware for SSD
5173 disks. I inserted the broken disk in one of my spare laptops and
5174 booted the ISO from a USB stick. The disk was recognized, but the
5175 program claimed the newest firmware already were installed and refused
5176 to insert any Intel firmware. So no change, and the disk is still
5177 unable to handle write load. :( I guess the only way to get them
5178 working would be if Lenovo releases new firmware. No idea how likely
5179 that is. Anyway, just blogging about this test for completeness. I
5180 got a working Samsung disk, and see no point in spending more time on
5181 the broken disks.
</p
>
5186 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5187 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5188 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5189 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5190 <description><p
>Today I switched to
5191 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5192 new laptop
</a
>. I
've previously written about the problems I had with
5193 my new Thinkpad X230, which was delivered with an
5194 <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
5195 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5196 sustained writes. My hardware supplier have been very forthcoming in
5197 trying to find a solution, and after first trying with another
5198 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5199 disk instead to fix it once and for all. The Samsung disk survived
5200 the installation of Debian with encrypted disks (filling the disk with
5201 random data during installation killed the first two), and I thus
5202 decided to trust it with my data. I have installed it as a Debian Edu
5203 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5204 server at home using Kerberos and LDAP, and will use it as my work
5205 station from now on.
</p
>
5207 <p
>As this is a solid state disk with no moving parts, I believe the
5208 Debian Wheezy default installation need to be tuned a bit to increase
5209 performance and increase life time of the disk. The Linux kernel and
5210 user space applications do not yet adjust automatically to such
5211 environment. To make it easier for my self, I created a draft Debian
5212 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5213 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5214 for the ssd-setup package
</a
> is available from collab-maint, and it
5215 is set up to adjust the setup of the machine by just installing the
5216 package. If there is any non-SSD disk in the machine, the package
5217 will refuse to install, as I did not try to write any logic to sort
5218 file systems in SSD and non-SSD file systems.
</p
>
5220 <p
>I consider the package a draft, as I am a bit unsure how to best
5221 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5222 where I set up the machine with one large encrypted partition (in
5223 addition to /boot), put LVM on top of this and set up partitions on
5224 top of this again. See the README file in the package source for the
5225 references I used to pick the settings. At the moment these
5226 parameters are tuned:
</p
>
5230 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5231 (adding discard to /etc/crypttab)
</li
>
5233 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5234 this case a cryptsetup partition) by changing issue_discards from
5235 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5237 <li
>Set relatime as a file system option for ext3 and ext4 file
5240 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5241 /etc/fstab.
</li
>
5243 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5245 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5246 cron.daily).
</li
>
5248 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5249 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5253 <p
>During installation, I cancelled the part where the installer fill
5254 the disk with random data, as this would kill the SSD performance for
5255 little gain. My goal with the encrypted file system is to ensure
5256 those stealing my laptop end up with a brick and not a working
5257 computer. I have no hope in keeping the really resourceful people
5258 from getting the data on the disk (see
5259 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5260 Thus I concluded that adding the discard option to crypttab is the
5261 right thing to do.
</p
>
5263 <p
>I considered using the noop I/O scheduler, as several recommended
5264 it for SSD, but others recommended deadline and a benchmark I found
5265 indicated that deadline might be better for interactive use.
</p
>
5267 <p
>I also considered using the
'discard
' file system option for ext3
5268 and ext4, but read that it would give a performance hit ever time a
5269 file is removed, and thought it best to that that slowdown once a day
5270 instead of during my work.
</p
>
5272 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5273 this is already done by Debian Edu.
</p
>
5275 <p
>I have not yet started on the user space tuning. I expect
5276 iceweasel need some tuning, and perhaps other applications too, but
5277 have not yet had time to investigate those parts.
</p
>
5279 <p
>The package should work on Ubuntu too, but I have not yet tested it
5282 <p
>As for the answer to the question in the title of this blog post,
5283 as far as I know, the only solution I know about is to replace the
5284 disk. It might be possible to flash it with Intel firmware instead of
5285 the Lenovo firmware. But I have not tried and did not want to do so
5286 without approval from Lenovo as I wanted to keep the warranty on the
5287 disk until a solution was found and they wanted the broken disks
5293 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5294 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5295 <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>
5296 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5297 <description><p
>A few days ago, I wrote about
5298 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5299 problems I experienced with my new X230 and its SSD disk
</a
>, which
5300 was dying during installation because it is unable to cope with
5301 sustained write. My supplier is in contact with
5302 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5303 replacement disk to try to fix the problem. They decided to send an
5304 identical model, so my hopes for a permanent fix was slim.
</p
>
5306 <p
>Anyway, today I got the replacement disk and tried to install
5307 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5308 same firmware version as the original. This time my hope raised
5309 slightly as the installation progressed, as the original disk used to
5310 die after
4-
7% of the disk was written to, while this time it kept
5311 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5312 died again and I was back on square one. I still do not have a new
5313 laptop with a disk I can trust. I can not live with a disk that might
5314 lock up when I download a new
5315 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5316 other large files. I look forward to hearing from my supplier with
5317 the next proposal from Lenovo.
</p
>
5319 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5320 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5321 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5322 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5323 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5324 P/N
45N8295, P0C38732.
</p
>
5326 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5327 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5328 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5329 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5330 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5331 P/N
45N8295, P0C38732.
</p
>
5333 <p
>The only difference is in the first number (serial number?), ISN,
5334 SA, date and WNPP values. Mentioning all the details here in case
5335 someone is able to use the information to find a way to identify the
5336 failing disk among working ones (if any such working disk actually
5342 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5343 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5345 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5346 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5347 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5348 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5349 member assosiation NUUG
</a
> and
5350 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5351 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5352 Bitraf
</a
>.
</p
>
5354 <p
>It starts
10:
00 and continue until late evening. Everyone is
5355 welcome, and there is no fee to participate. There is on the other
5356 hand limited space, and only room for
30 people. Please put your name
5357 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5358 wiki page
</a
> if you plan to join us.
</p
>
5363 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5364 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5365 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5366 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5367 <description><p
>Half a year ago, I reported that I had to find a
5368 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5369 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5370 time to spend on it, and it took a while to find a model I believe
5371 will do the job, but two days ago the replacement finally arrived. I
5373 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5374 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5375 a roaming workstation, and it seemed to work flawlessly. But my
5376 second installation with encrypted disk was not as successful. More
5377 on that below.
</p
>
5379 <p
>I had a hard time trying to track down a good laptop, as my most
5380 important requirements (robust and with a good keyboard) are never
5381 listed in the feature list. But I did get good help from the search
5382 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5383 allowed me to limit the list of interesting laptops based on my other
5384 requirements. A bit surprising that SSD disk are not disks according
5385 to that search interface, so I had to drop specifying the number of
5386 disks from my search parameters. I also asked around among friends to
5387 get their impression on keyboards and robustness.
</p
>
5389 <p
>So the new laptop arrived, and it is quite a lot wider than the
5390 X41. I am not quite convinced about the keyboard, as it is
5391 significantly wider than my old keyboard, and I have to stretch my
5392 hand a lot more to reach the edges. But the key response is fairly
5393 good and the individual key shape is fairly easy to handle, so I hope
5394 I will get used to it. My old X40 was starting to fail, and I really
5395 needed a new laptop now. :)
</p
>
5397 <p
>Turning off the touch pad was simple. All it took was a quick
5398 visit to the BIOS during boot it disable it.
</p
>
5400 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5401 lock up during load. And this happen when installing Debian Wheezy
5402 with encrypted disk, while the disk is being filled with random data.
5403 I also tested to install Ubuntu Raring, and it happen there too if I
5404 reenable the code to fill the disk with random data (it is disabled by
5405 default in Ubuntu). And the bug with is already known. It was
5406 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5407 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5408 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5409 kernel developers as
5410 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5411 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5412 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5413 Lenovo forums, both for
5414 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5415 2012-
11-
10</a
> and for
5416 <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
5417 03-
20-
2013</a
>. The problem do not only affect installation. The
5418 reports state that the disk lock up during use if many writes are done
5419 on the disk, so it is much no use to work around the installation
5420 problem and end up with a computer that can lock up at any moment.
5422 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5423 available
</a
> that will lock up the hard drive after running a few
5424 minutes by writing to a file.
</p
>
5426 <p
>I
've contacted my supplier and asked how to handle this, and after
5427 contacting PCHELP Norway (request
01D1FDP) which handle support
5428 requests for Lenovo, his first suggestion was to upgrade the disk
5429 firmware. Unfortunately there is no newer firmware available from
5430 Lenovo, as my disk already have the most recent one (version LF1i). I
5431 hope to hear more from him today and hope the problem can be
5437 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5438 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5439 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5440 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5441 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5442 trusty old Thinkpad X41. Unfortunately I did not have much time to
5443 spend on it, but today the replacement finally arrived. I ended up
5444 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5445 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5446 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5447 this, it is installing what I hope will be a more final installation,
5448 with a encrypted hard drive to ensure any dope head stealing it end up
5449 with an expencive door stop.
</p
>
5451 <p
>I had a hard time trying to track down a good laptop, as my most
5452 important requirements (robust and with a good keyboard) are never
5453 listed in the feature list. But I did get good help from the search
5454 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5455 allowed me to limit the list of interesting laptops based on my other
5456 requirements. A bit surprising that SSD disk are not disks, so I had
5457 to drop number of disks from my search parameters.
</p
>
5459 <p
>I am not quite convinced about the keyboard, as it is significantly
5460 wider than my old keyboard, and I have to stretch my hand a lot more
5461 to reach the edges. But the key response is fairly good and the
5462 individual key shape is fairly easy to handle, so I hope I will get
5463 used to it. My old X40 was starting to fail, and I really needed a
5464 new laptop now. :)
</p
>
5466 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5471 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5472 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5473 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5474 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5475 <description><p
>It annoys me when the computer fail to do automatically what it is
5476 perfectly capable of, and I have to do it manually to get things
5477 working. One such task is to find out what firmware packages are
5478 needed to get the hardware on my computer working. Most often this
5479 affect the wifi card, but some times it even affect the RAID
5480 controller or the ethernet card. Today I pushed version
0.4 of the
5481 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5482 including a new script isenkram-autoinstall-firmware handling the
5483 process of asking all the loaded kernel modules what firmware files
5484 they want, find debian packages providing these files and install the
5485 debian packages. Here is a test run on my laptop:
</p
>
5487 <p
><pre
>
5488 # isenkram-autoinstall-firmware
5489 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5490 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5491 info: locating packages with the requested firmware files
5492 info: Updating APT sources after adding non-free APT source
5493 info: trying to install firmware-ipw2x00
5496 Preconfiguring packages ...
5497 Selecting previously deselected package firmware-ipw2x00.
5498 (Reading database ...
259727 files and directories currently installed.)
5499 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5500 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5502 </pre
></p
>
5504 <p
>When all the requested firmware is present, a simple message is
5505 printed instead:
</p
>
5507 <p
><pre
>
5508 # isenkram-autoinstall-firmware
5509 info: did not find any firmware files requested by loaded kernel modules. exiting
5511 </pre
></p
>
5513 <p
>It could use some polish, but it is already working well and saving
5514 me some time when setting up new machines. :)
</p
>
5516 <p
>So, how does it work? It look at the set of currently loaded
5517 kernel modules, and look up each one of them using modinfo, to find
5518 the firmware files listed in the module meta-information. Next, it
5519 download the Contents file from a nearby APT mirror, and search for
5520 the firmware files in this file to locate the package with the
5521 requested firmware file. If the package is in the non-free section, a
5522 non-free APT source is added and the package is installed using
5523 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5526 <p
>I hope someone find time to implement a more polished version of
5527 this script as part of the hw-detect debian-installer module, to
5528 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5529 #
655507</a
>. There really is no need to insert USB sticks with
5530 firmware during a PXE install when the packages already are available
5531 from the nearby Debian mirror.
</p
>
5536 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5537 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5538 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5539 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5540 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5541 the screen just turn black when Linux boot, either during installation
5542 or on first boot from the hard disk. I
've seen it once in a while the
5543 last few years, but only recently understood the cause. I
've seen it
5544 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5545 The reason seem to be in the wiring of some laptops. The system to
5546 control the screen background light is inverted, so when Linux try to
5547 turn the brightness fully on, it end up turning it off instead. I do
5548 not know which Linux drivers are affected, but this post is about the
5549 i915 driver used by the
5550 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5551 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5553 <p
>The problem can be worked around two ways. Either by adding
5554 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5555 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5556 option when it load the i915 kernel module. On Debian and Ubuntu, it
5557 can be done by running these commands as root:
</p
>
5560 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5561 update-initramfs -u -k all
5564 <p
>Since March
2012 there is
5565 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5566 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5567 hardware have this problem, and get the driver to invert the
5568 brightness setting automatically. To use it, one need to add a row in
5569 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5570 intel_quirks array
</a
> in the driver source
5571 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5572 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5573 number (vendor number
8086 is assumed) and subdevice vendor and device
5576 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5577 -vvnn
</tt
> for the video card in question:
</p
>
5579 <p
><pre
>
5580 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5581 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5582 (rev
09) (prog-if
00 [VGA controller])
5583 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5584 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5585 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5586 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5587 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5589 Interrupt: pin A routed to IRQ
42
5590 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5591 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5592 Region
4: I/O ports at
4000 [size=
64]
5593 Expansion ROM at
<unassigned
> [disabled]
5594 Capabilities:
<access denied
>
5595 Kernel driver in use: i915
5596 </pre
></p
>
5598 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5600 <p
><pre
>
5601 struct intel_quirk intel_quirks[] = {
5603 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5604 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5607 </pre
></p
>
5609 <p
>According to the kernel module instructions (as seen using
5610 <tt
>modinfo i915
</tt
>), information about hardware needing the
5611 invert_brightness flag should be sent to the
5612 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5613 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5614 developers. But my email about the laptop sent
2013-
06-
03 have not
5616 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5617 web archive for the mailing list
</a
>, so I suspect they do not accept
5618 emails from non-subscribers. Because of this, I sent my patch also to
5619 the Debian bug tracking system instead as
5620 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5621 sure the patch is not lost.
</p
>
5623 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5624 with this problem working properly with Linux. If you use Gnome, your
5625 worries should be over at this point. But if you use KDE, there is
5626 something in KDE ignoring the invert_brightness setting and turning on
5627 the screen during login. I
've reported it to Debian as
5628 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5629 have no idea yet how to figure out exactly what subsystem is doing
5630 this. Perhaps you can help? Perhaps you know what the Gnome
5631 developers did to handle this, and this can give a clue to the KDE
5632 developers? Or you know where in KDE the screen brightness is changed
5633 during login? If so, please update the BTS report (or get in touch if
5634 you do not know how to update BTS).
</p
>
5636 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5637 acpi_backlight=vendor, to disable ACPI backlight support completely,
5638 as the ACPI information on the machine is trash and it is better to
5639 leave it to the intel video driver to control the screen
5640 backlight.
</p
>
5645 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5646 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5647 <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>
5648 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5649 <description><p
>Two days ago, I asked
5650 <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
5651 I could install Linux on a Packard Bell EasyNote LV computer
5652 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5653 with the obstacles put in the way of Linux users on a laptop with UEFI
5654 and Windows
8.
</p
>
5656 <p
>I never found out if the cause of my problems were the use of UEFI
5657 secure booting or fast boot. I suspect fast boot was the problem,
5658 causing the firmware to boot directly from HD without considering any
5659 key presses and alternative devices, but do not know UEFI settings
5660 enough to tell.
</p
>
5662 <p
>There is no way to install Linux on the machine in question without
5663 opening the box and disconnecting the hard drive! This is as far as I
5664 can tell, the only way to get access to the firmware setup menu
5665 without accepting the Windows
8 license agreement. I am told (and
5666 found description on how to) that it is possible to configure the
5667 firmware setup once booted into Windows
8. But as I believe the terms
5668 of that agreement are completely unacceptable, accepting the license
5669 was never an alternative. I do not enter agreements I do not intend
5670 to follow.
</p
>
5672 <p
>I feared I had to return the laptops and ask for a refund, and
5673 waste many hours on this, but luckily there was a way to get it to
5674 work. But I would not recommend it to anyone planning to run Linux on
5675 it, and I have become sceptical to Windows
8 certified laptops. Is
5676 this the way Linux will be forced out of the market place, by making
5677 it close to impossible for
"normal
" users to install Linux without
5678 accepting the Microsoft Windows license terms? Or at least not
5679 without risking to loose the warranty?
</p
>
5681 <p
>I
've updated the
5682 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5683 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5684 do not have to struggle as much as I did to get Linux into the
5687 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5688 Michael Tokarev and others for feedback and ideas.
</p
>
5693 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5694 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5695 <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>
5696 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5697 <description><p
>I
've run into quite a problem the last few days. I bought three
5698 new laptops for my parents and a few others. I bought Packard Bell
5699 Easynote LV to run Kubuntu on and use as their home computer. But I
5700 am completely unable to figure out how to install Linux on it. The
5701 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5702 instead of a BIOS to boot.
</p
>
5704 <p
>The problem is that I am unable to get it to PXE boot, and unable
5705 to get it to boot the Linux installer from my USB stick. I have yet
5706 to try the DVD install, and still hope it will work. when I turn on
5707 the computer, there is no information on what buttons to press to get
5708 the normal boot menu. I expect to get some boot menu to select PXE or
5709 USB stick booting. When booting, it first ask for the language to
5710 use, then for some regional settings, and finally if I will accept the
5711 Windows
8 terms of use. As these terms are completely unacceptable to
5712 me, I have no other choice but to turn off the computer and try again
5713 to get it to boot the Linux installer.
</p
>
5715 <p
>I have gathered my findings so far on a Linlap page about the
5716 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5717 EasyNote LV
</a
> model. If you have any idea how to get Linux
5718 installed on this machine, please get in touch or update that wiki
5719 page. If I can
't find a way to install Linux, I will have to return
5720 the laptop to the seller and find another machine for my parents.
</p
>
5722 <p
>I wonder, is this the way Linux will be forced out of the market
5723 using UEFI and
"secure boot
" by making it impossible to install Linux
5724 on new Laptops?
</p
>
5729 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5730 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5731 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5732 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5733 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5734 an operating system based on Debian intended for use in schools. It
5735 contain a turn-key solution for the computer network provided to
5736 pupils in the primary schools. It provide both the central server,
5737 network boot servers and desktop environments with heaps of
5738 educational software. The project was founded almost
12 years ago,
5739 2001-
07-
02. If you want to support the project, which is in need for
5740 cash to fund developer gatherings and other project related activity,
5741 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5742 donate some money
</a
>.
5744 <p
>A topic that come up again and again on the Debian Edu mailing
5745 lists and elsewhere, is the question on how to transform a Debian or
5746 Ubuntu installation into a Debian Edu installation. It isn
't very
5747 hard, and last week I wrote a script to replicate the steps done by
5748 the Debian Edu installer.
</p
>
5750 <p
>The script,
5751 <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/
>
5752 in the debian-edu-config package, will go through these six steps and
5753 transform an existing Debian Wheezy or Ubuntu (untested) installation
5754 into a Debian Edu Workstation:
</p
>
5758 <li
>Add skolelinux related APT sources.
</li
>
5759 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5760 <li
>Install debian-edu-install to load preseeding values and pull in
5761 our configuration.
</li
>
5762 <li
>Preseed debconf database with profile setup in
5763 /etc/debian-edu/config, and run tasksel to install packages
5764 according to the profile specified in the config above,
5765 overriding some of the Debian automation machinery.
</li
>
5766 <li
>Run debian-edu-cfengine-D installation to configure everything
5767 that could not be done using preseeding.
</li
>
5768 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5772 <p
>There are some steps in the Debian Edu installation that can not be
5773 replicated like this. Disk partitioning and LVM setup, for example.
5774 So this script just assume there is enough disk space to install all
5775 the needed packages.
</p
>
5777 <p
>The script was created to help a Debian Edu student working on
5778 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5779 Debian Edu client, and using it he can take the existing
5780 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5781 transform it into a fully functioning Debian Edu Workstation (or
5782 Roaming Workstation, or whatever :).
</p
>
5784 <p
>The default setting in the script is to create a KDE Workstation.
5785 If a LXDE based Roaming workstation is wanted instead, modify the
5786 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5788 <p
><pre
>
5789 PROFILE=
"Roaming-Workstation
"
5790 DESKTOP=
"lxde
"
5791 </pre
></p
>
5793 <p
>The script could even become useful to set up Debian Edu servers in
5794 the cloud, by starting with a virtual Debian installation at some
5795 virtual hosting service and setting up all the services on first
5801 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5802 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5803 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5804 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5805 <description><P
>In January,
5806 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5807 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5808 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5809 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5810 marvellous construction system from Denmark. We also created
5811 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5812 a place to take notes and write down our plans and hopes. And several
5813 people showed up to help. I was very happy to see the effect of my
5814 call. Since the small start, we have a debtags tag
5815 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5816 tag for LEGO related packages, and now count
10 packages related to
5817 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5819 <p
><table
>
5820 <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
>
5821 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5822 <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
>
5823 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5824 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5825 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5826 <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
>
5827 <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
>
5828 <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
>
5829 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5830 </table
></p
>
5832 <p
>Some of these are available in Wheezy, and all but one are
5833 currently available in Jessie/testing. leocad is so far only
5834 available in experimental.
</p
>
5836 <p
>If you care about LEGO in Debian, please join us on IRC and help
5837 adding the rest of the great free software tools available on Linux
5838 for LEGO designers.
</p
>
5843 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5844 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5845 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5846 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5847 <description><p
>When I woke up this morning, I was very happy to see that the
5848 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5849 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5850 Debian release, and I expect to move my machines at home over to it fairly
5853 <p
>The new debian release contain heaps of new stuff, and one program
5854 in particular make me very happy to see included. The
5855 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5856 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5857 included for the first time. Alongside similar programs like
5858 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5859 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5860 it allow for visual programming where syntax errors can not happen,
5861 and a friendly programming environment for learning to control the
5862 computer. Scratch will also be included in the next release of Debian
5865 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5866 Edu/Skolelinux release too. The
5867 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5868 alpha release
</a
> went out last week, and the next should soon
5874 <title>Isenkram
0.2 finally in the Debian archive
</title>
5875 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5876 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5877 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5878 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5879 package
</a
> finally made it into the archive, after lingering in NEW
5880 for many months. I uploaded it to the Debian experimental suite
5881 2013-
01-
27, and today it was accepted into the archive.
</p
>
5883 <p
>Isenkram is a system for suggesting to users what packages to
5884 install to work with a pluggable hardware device. The suggestion pop
5885 up when the device is plugged in. For example if a Lego Mindstorm NXT
5886 is inserted, it will suggest to install the program needed to program
5887 the NXT controller. Give it a go, and report bugs and suggestions to
5893 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5894 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5896 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5897 <description><p
>My
5898 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5899 bitcoin related blog post
</a
> mentioned that the new
5900 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5901 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5902 2013-
01-
19, and have been available in unstable since then. It was
5903 automatically copied to Ubuntu, and is available in their Raring
5904 version too.
</p
>
5906 <p
>But there is a strange problem with the build that block this new
5907 version from being available on the i386 and kfreebsd-i386
5908 architectures. For some strange reason, the autobuilders in Debian
5909 for these architectures fail to run the test suite on these
5910 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5911 We are so far unable to reproduce it when building it manually, and
5912 no-one have been able to propose a fix. If you got an idea what is
5913 failing, please let us know via the BTS.
</p
>
5915 <p
>One feature that is annoying me with of the bitcoin client, because
5916 I often run low on disk space, is the fact that the client will exit
5917 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5918 #
696715</a
>). So make sure you have enough disk space when you run
5921 <p
>As usual, if you use bitcoin and want to show your support of my
5922 activities, please send Bitcoin donations to my address
5923 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5928 <title>Welcome to the world, Isenkram!
</title>
5929 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5930 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5931 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5932 <description><p
>Yesterday, I
5933 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5934 for testers
</a
> for my prototype for making Debian better at handling
5935 pluggable hardware devices, which I
5936 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5937 out to create
</a
> earlier this month. Several valuable testers showed
5938 up, and caused me to really want to to open up the development to more
5939 people. But before I did this, I want to come up with a sensible name
5940 for this project. Today I finally decided on a new name, and I have
5941 renamed the project from hw-support-handler to this new name. In the
5942 process, I moved the source to git and made it available as a
5943 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5944 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5945 To fetch and build the latest version of the source, use
</p
>
5948 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5949 cd isenkram
&& git-buildpackage -us -uc
5952 <p
>I have not yet adjusted all files to use the new name yet. If you
5953 want to hack on the source or improve the package, please go ahead.
5954 But please talk to me first on IRC or via email before you do major
5955 changes, to make sure we do not step on each others toes. :)
</p
>
5957 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5958 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5959 stuff, in other words. I
've been told it is the Norwegian variant of
5960 the German word eisenkram, for those that are familiar with that
5963 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5964 instructions, to avoid confusing people with an error from the signing
5967 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5968 clone argument to avoid the need for authentication.
</p
>
5973 <title>First prototype ready making hardware easier to use in Debian
</title>
5974 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5975 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5976 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5977 <description><p
>Early this month I set out to try to
5978 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5979 the Debian support for pluggable hardware devices
</a
>. Now my
5980 prototype is working, and it is ready for a larger audience. To test
5982 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5983 from the Debian Edu subversion repository
</a
>, build and install the
5984 package. You might have to log out and in again activate the
5985 autostart script.
</p
>
5987 <p
>The design is simple:
</p
>
5991 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5992 hw-support-handlerd to start when the user log in.
</li
>
5994 <li
>This program listen for kernel events about new hardware (directly
5995 from the kernel like udev does), not using HAL dbus events as I
5996 initially did.
</li
>
5998 <li
>When new hardware is inserted, look up the hardware modalias in
5999 the APT database, a database
6000 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6001 via HTTP
</a
> and a database available as part of the package.
</li
>
6003 <li
>If a package is mapped to the hardware in question, the package
6004 isn
't installed yet and this is the first time the hardware was
6005 plugged in, show a desktop notification suggesting to install the
6006 package or packages.
</li
>
6008 <li
>If the user click on the
'install package now
' button, ask
6009 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6011 <li
>aptdaemon ask for root password or sudo password, and install the
6012 package while showing progress information in a window.
</li
>
6016 <p
>I still need to come up with a better name for the system. Here
6017 are some screen shots showing the prototype in action. First the
6018 notification, then the password request, and finally the request to
6019 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6021 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6022 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6023 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6024 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6025 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6027 <p
>The prototype still need to be improved with longer timeouts, but
6028 is already useful. The database of hardware to package mappings also
6029 need more work. It is currently compatible with the Ubuntu way of
6030 storing such information in the package control file, but could be
6031 changed to use other formats instead or in addition to the current
6032 method. I
've dropped the use of discover for this mapping, as the
6033 modalias approach is more flexible and easier to use on Linux as long
6034 as the Linux kernel expose its modalias strings directly.
</p
>
6036 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6037 here is the command required to check out and build the source: Use
6038 '<tt
>svn checkout
6039 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6040 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6041 devscripts package.
</p
>
6043 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6044 renamed to Isenkram and the source moved from the Debian Edu
6045 subversion repository to a Debian collab-maint git repository. See
6046 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6047 instructions
</a
> for details.
</p
>
6052 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6053 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6055 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6056 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6057 suddenly in bed. With a quiet whimper, it went completely quiet and
6058 black. The power button was no longer able to turn it on. It was a
6059 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6060 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6061 Compaq I had before that. Now I need to find a replacement. To keep
6062 going during Christmas, I moved the one year old SSD disk to my old
6063 X40 where it fitted (only one I had left that could use it), but it is
6064 not a durable solution.
6066 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6067 got a new one more than
10 years ago. It still holds true.:)
</p
>
6071 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6072 than A4).
</li
>
6073 <li
>Robust, it will be in my backpack every day.
</li
>
6074 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6075 <li
>Long battery life time. Preferable a week.
</li
>
6076 <li
>Internal WIFI network card.
</li
>
6077 <li
>Internal Twisted Pair network card.
</li
>
6078 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6079 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6080 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6082 <li
>Hardware supported by Debian Stable, ie the default kernel and
6083 X.org packages.
</li
>
6084 <li
>Quiet, preferably fan free (or at least not using the fan most of
6089 <p
>You will notice that there are no RAM and CPU requirements in the
6090 list. The reason is simply that the specifications on laptops the
6091 last
10-
15 years have been sufficient for my needs, and I have to look
6092 at other features to choose my laptop. But are there still made as
6093 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6094 robust, and Thinkpads seem to be heading in the wrong direction since
6095 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6096 still be useful.
</p
>
6098 <p
>Perhaps I should rethink my needs, and look for a pad with an
6099 external keyboard? I
'll have to check the
6100 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6101 well-supported laptops, or perhaps just buy one preinstalled from one
6102 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6103 Pre-loaded site
</a
>.
</p
>
6108 <title>How to find a browser plugin supporting a given MIME type
</title>
6109 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6110 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6111 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6112 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6113 install to get support for a given MIME type. Thanks to
6114 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6115 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6116 Unfortunately, not very many packages provide the needed meta
6117 information, Anyway, here is a small script to look up all browser
6118 plugin packages announcing ther MIME support using this specification:
</p
>
6124 def pkgs_handling_mimetype(mimetype):
6129 version = pkg.candidate
6131 version = pkg.installed
6134 record = version.record
6135 if not record.has_key(
'Npp-MimeType
'):
6137 mime_types = record[
'Npp-MimeType
'].split(
',
')
6138 for t in mime_types:
6139 t = t.rstrip().strip()
6141 thepkgs.append(pkg.name)
6143 mimetype =
"audio/ogg
"
6144 if
1 < len(sys.argv):
6145 mimetype = sys.argv[
1]
6146 print
"Browser plugin packages supporting %s:
" % mimetype
6147 for pkg in pkgs_handling_mimetype(mimetype):
6148 print
" %s
" %pkg
6151 <p
>It can be used like this to look up a given MIME type:
</p
>
6154 % ./apt-find-browserplug-for-mimetype
6155 Browser plugin packages supporting audio/ogg:
6157 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6158 Browser plugin packages supporting application/x-shockwave-flash:
6159 browser-plugin-gnash
6163 <p
>In Ubuntu this mechanism is combined with support in the browser
6164 itself to query for plugins and propose to install the needed
6165 packages. It would be great if Debian supported such feature too. Is
6166 anyone working on adding it?
</p
>
6168 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6169 request for icweasel support for this feature is
6170 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6171 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6172 of manpower and wish for a different design is the reason thus feature
6173 is not yet in iceweasel from Debian.
</p
>
6178 <title>What is the most supported MIME type in Debian?
</title>
6179 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6180 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6181 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6182 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6183 proposal to add AppStream information to the Debian archive
</a
>, is a
6184 proposal to make it possible for a Desktop application to propose to
6185 the user some package to install to gain support for a given MIME
6186 type, font, library etc. that is currently missing. With such
6187 mechanism in place, it would be possible for the desktop to
6188 automatically propose and install leocad if some LDraw file is
6189 downloaded by the browser.
</p
>
6191 <p
>To get some idea about the current content of the archive, I decided
6192 to write a simple program to extract all .desktop files from the
6193 Debian archive and look up the claimed MIME support there. The result
6195 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6196 site
</a
>. Using the collected information, it become possible to
6197 answer the question in the title. Here are the
20 most supported MIME
6198 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6199 The complete list is available from the link above.
</p
>
6201 <p
><strong
>Debian Stable:
</strong
></p
>
6205 ----- -----------------------
6221 18 application/x-ogg
6228 <p
><strong
>Debian Testing:
</strong
></p
>
6232 ----- -----------------------
6248 18 application/x-ogg
6255 <p
><strong
>Debian Unstable:
</strong
></p
>
6259 ----- -----------------------
6276 18 application/x-ogg
6282 <p
>I am told that PackageKit can provide an API to access the kind of
6283 information mentioned in DEP-
11. I have not yet had time to look at
6284 it, but hope the PackageKit people in Debian are on top of these
6287 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6288 discovering a typo in my script.
</p
>
6293 <title>Using modalias info to find packages handling my hardware
</title>
6294 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6295 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6296 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6297 <description><p
>Yesterday, I wrote about the
6298 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6299 values provided by the Linux kernel
</a
> following my hope for
6300 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6301 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6302 modalias values attached to package names can be used to map packages
6303 to hardware. This allow the system to look up and suggest relevant
6304 packages when I plug in some new hardware into my machine, and replace
6305 discover and discover-data as the database used to map hardware to
6308 <p
>I create a modaliases file with entries like the following,
6309 containing package name, kernel module name (if relevant, otherwise
6310 the package name) and globs matching the relevant hardware
6313 <p
><blockquote
>
6314 Package: package-name
6315 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6316 </blockquote
></p
>
6318 <p
>It is fairly trivial to write code to find the relevant packages
6319 for a given modalias value using this file.
</p
>
6321 <p
>An entry like this would suggest the video and picture application
6322 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6324 <p
><blockquote
>
6326 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6327 </blockquote
></p
>
6329 <p
>An entry like this would suggest the pcmciautils package when a
6330 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6332 <p
><blockquote
>
6333 Package: pcmciautils
6334 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6335 </blockquote
></p
>
6337 <p
>An entry like this would suggest the package colorhug-client when
6338 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6340 <p
><blockquote
>
6341 Package: colorhug-client
6342 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6343 </blockquote
></p
>
6345 <p
>I believe the format is compatible with the format of the Packages
6346 file in the Debian archive. Ubuntu already uses their Packages file
6347 to store their mappings from packages to hardware.
</p
>
6349 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6350 announce the hardware it support in a way my prototype understand.
6351 This allow those publishing packages in an APT source outside the
6352 Debian archive as well as those backporting packages to make sure the
6353 hardware mapping are included in the package meta information. I
've
6354 tested such header in the pymissile package, and its modalias mapping
6355 is working as it should with my prototype. It even made it to Ubuntu
6358 <p
>To test if it was possible to look up supported hardware using only
6359 the shell tools available in the Debian installer, I wrote a shell
6360 implementation of the lookup code. The idea is to create files for
6361 each modalias and let the shell do the matching. Please check out and
6363 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6364 shell script. It run without any extra dependencies and fetch the
6365 hardware mappings from the Debian archive and the subversion
6366 repository where I currently work on my prototype.
</p
>
6368 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6369 install yubikey-personalization:
</p
>
6371 <p
><blockquote
>
6372 % ./hw-support-lookup
6373 <br
>yubikey-personalization
6375 </blockquote
></p
>
6377 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6378 propose to install the pcmciautils package:
</p
>
6380 <p
><blockquote
>
6381 % ./hw-support-lookup
6382 <br
>pcmciautils
6384 </blockquote
></p
>
6386 <p
>If you know of any hardware-package mapping that should be added to
6387 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6388 database
</a
>, please tell me about it.
</p
>
6390 <p
>It could be possible to generate several of the mappings between
6391 packages and hardware. One source would be to look at packages with
6392 kernel modules, ie packages with *.ko files in /lib/modules/, and
6393 extract their modalias information. Another would be to look at
6394 packages with udev rules, ie packages with files in
6395 /lib/udev/rules.d/, and extract their vendor/model information to
6396 generate a modalias matching rule. I have not tested any of these to
6397 see if it work.
</p
>
6399 <p
>If you want to help implementing a system to let us propose what
6400 packages to install when new hardware is plugged into a Debian
6401 machine, please send me an email or talk to me on
6402 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6407 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6408 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6409 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6410 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6411 <description><p
>While looking into how to look up Debian packages based on hardware
6412 information, to find the packages that support a given piece of
6413 hardware, I refreshed my memory regarding modalias values, and decided
6414 to document the details. Here are my findings so far, also available
6416 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6417 Debian Edu subversion repository
</a
>:
6419 <p
><strong
>Modalias decoded
</strong
></p
>
6421 <p
>This document try to explain what the different types of modalias
6422 values stands for. It is in part based on information from
6423 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6424 &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;,
6425 &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
6426 &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;.
6428 <p
>The modalias entries for a given Linux machine can be found using
6429 this shell script:
</p
>
6432 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6435 <p
>The supported modalias globs for a given kernel module can be found
6436 using modinfo:
</p
>
6439 % /sbin/modinfo psmouse | grep alias:
6440 alias: serio:ty05pr*id*ex*
6441 alias: serio:ty01pr*id*ex*
6445 <p
><strong
>PCI subtype
</strong
></p
>
6447 <p
>A typical PCI entry can look like this. This is an Intel Host
6448 Bridge memory controller:
</p
>
6450 <p
><blockquote
>
6451 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6452 </blockquote
></p
>
6454 <p
>This represent these values:
</p
>
6459 sv
00001028 (subvendor)
6460 sd
000001AD (subdevice)
6462 sc
00 (bus subclass)
6466 <p
>The vendor/device values are the same values outputted from
'lspci
6467 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6468 0600. The
0600 class is a host bridge. Other useful bus values are
6469 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6471 <p
>Not sure how to figure out the interface value, nor what it
6474 <p
><strong
>USB subtype
</strong
></p
>
6476 <p
>Some typical USB entries can look like this. This is an internal
6477 USB hub in a laptop:
</p
>
6479 <p
><blockquote
>
6480 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6481 </blockquote
></p
>
6483 <p
>Here is the values included in this alias:
</p
>
6486 v
1D6B (device vendor)
6487 p
0001 (device product)
6489 dc
09 (device class)
6490 dsc
00 (device subclass)
6491 dp
00 (device protocol)
6492 ic
09 (interface class)
6493 isc
00 (interface subclass)
6494 ip
00 (interface protocol)
6497 <p
>The
0900 device class/subclass means hub. Some times the relevant
6498 class is in the interface class section. For a simple USB web camera,
6499 these alias entries show up:
</p
>
6501 <p
><blockquote
>
6502 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6503 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6504 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6505 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6506 </blockquote
></p
>
6508 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6509 camera),
0101 is audio control device and
0102 is audio streaming (aka
6510 microphone). Thus this is a camera with microphone included.
</p
>
6512 <p
><strong
>ACPI subtype
</strong
></p
>
6514 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6515 receiver in a Thinkpad X40:
</p
>
6517 <p
><blockquote
>
6518 acpi:IBM0071:PNP0511:
6519 </blockquote
></p
>
6521 <p
>The values between the colons are IDs.
</p
>
6523 <p
><strong
>DMI subtype
</strong
></p
>
6525 <p
>The DMI table contain lots of information about the computer case
6526 and model. This is an entry for a IBM Thinkpad X40, fetched from
6527 /sys/devices/virtual/dmi/id/modalias:
</p
>
6529 <p
><blockquote
>
6530 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6531 </blockquote
></p
>
6533 <p
>The values present are
</p
>
6536 bvn IBM (BIOS vendor)
6537 bvr
1UETB
6WW(
1.66) (BIOS version)
6538 bd
06/
15/
2005 (BIOS date)
6539 svn IBM (system vendor)
6540 pn
2371H4G (product name)
6541 pvr ThinkPadX40 (product version)
6542 rvn IBM (board vendor)
6543 rn
2371H4G (board name)
6544 rvr NotAvailable (board version)
6545 cvn IBM (chassis vendor)
6546 ct
10 (chassis type)
6547 cvr NotAvailable (chassis version)
6550 <p
>The chassis type
10 is Notebook. Other interesting values can be
6551 found in the dmidecode source:
</p
>
6555 4 Low Profile Desktop
6568 17 Main Server Chassis
6569 18 Expansion Chassis
6571 20 Bus Expansion Chassis
6572 21 Peripheral Chassis
6574 23 Rack Mount Chassis
6583 <p
>The chassis type values are not always accurately set in the DMI
6584 table. For example my home server is a tower, but the DMI modalias
6585 claim it is a desktop.
</p
>
6587 <p
><strong
>SerIO subtype
</strong
></p
>
6589 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6590 test machine:
</p
>
6592 <p
><blockquote
>
6593 serio:ty01pr00id00ex00
6594 </blockquote
></p
>
6596 <p
>The values present are
</p
>
6605 <p
>This type is supported by the psmouse driver. I am not sure what
6606 the valid values are.
</p
>
6608 <p
><strong
>Other subtypes
</strong
></p
>
6610 <p
>There are heaps of other modalias subtypes according to
6611 file2alias.c. There is the rest of the list from that source: amba,
6612 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6613 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6614 vmbus, x86cpu and zorro. I did not spend time documenting all of
6615 these, as they do not seem relevant for my intended use with mapping
6616 hardware to packages when new stuff is inserted during run time.
</p
>
6618 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6620 <p
>To check which kernel modules provide support for a given modalias,
6621 one can use the following shell script:
</p
>
6624 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6625 echo
"$id
" ; \
6626 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6630 <p
>The output can look like this (only the first few entries as the
6631 list is very long on my test machine):
</p
>
6635 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6637 FATAL: Module acpi:device: not found.
6639 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6640 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6641 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6642 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6643 acpi:IBM0071:PNP0511:
6644 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6645 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6646 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6650 <p
>If you want to help implementing a system to let us propose what
6651 packages to install when new hardware is plugged into a Debian
6652 machine, please send me an email or talk to me on
6653 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6655 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6656 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6657 in /sys/ with space in them.
</p
>
6662 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6663 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6664 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6665 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6666 <description><p
>As part of my investigation on how to improve the support in Debian
6667 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6668 Launcher and updated the Debian package
6669 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6670 sure udev will fix the device permissions when it is plugged in. I
6671 also added a
"Modaliases
" header to test it in the Debian archive and
6672 hopefully make the package be proposed by jockey in Ubuntu when a user
6673 plug in his rocket launcher. In the process I moved the source to a
6674 git repository under collab-maint, to make it easier for any DD to
6675 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6676 is not very active, but the software still work for me even after five
6677 years of relative silence. The new git repository is not listed in
6678 the uploaded package yet, because I want to test the other changes a
6679 bit more before I upload the new version. If you want to check out
6680 the new version with a .desktop file included, visit the
6681 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6682 view
</a
> or use
"<tt
>git clone
6683 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6688 <title>Lets make hardware dongles easier to use in Debian
</title>
6689 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6690 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6691 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6692 <description><p
>One thing that annoys me with Debian and Linux distributions in
6693 general, is that there is a great package management system with the
6694 ability to automatically install software packages by downloading them
6695 from the distribution mirrors, but no way to get it to automatically
6696 install the packages I need to use the hardware I plug into my
6697 machine. Even if the package to use it is easily available from the
6698 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6699 suggest to automatically install the python-nxt, nbc and t2n packages
6700 I need to talk to it. When I plug in a Yubikey, it could propose the
6701 yubikey-personalization package. The information required to do this
6702 is available, but no-one have pulled all the pieces together.
</p
>
6704 <p
>Some years ago, I proposed to
6705 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6706 the discover subsystem to implement this
</a
>. The idea is fairly
6711 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6712 starting when a user log in.
</li
>
6714 <li
>Set this program up to listen for kernel events emitted when new
6715 hardware is inserted into the computer.
</li
>
6717 <li
>When new hardware is inserted, look up the hardware ID in a
6718 database mapping to packages, and take note of any non-installed
6719 packages.
</li
>
6721 <li
>Show a message to the user proposing to install the discovered
6722 package, and make it easy to install it.
</li
>
6726 <p
>I am not sure what the best way to implement this is, but my
6727 initial idea was to use dbus events to discover new hardware, the
6728 discover database to find packages and
6729 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6732 <p
>Yesterday, I found time to try to implement this idea, and the
6733 draft package is now checked into
6734 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6735 Debian Edu subversion repository
</a
>. In the process, I updated the
6736 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6737 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6738 the relevant packages in Debian, and uploaded a new version
6739 2.2013.01.09 to unstable. I also discovered that the current
6740 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6741 package in Debian no longer discovered any USB devices, because
6742 /proc/bus/usb/devices is no longer present. I ported it to use
6743 libusb as a fall back option to get it working. The fixed package
6744 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6745 because of the freeze).
</p
>
6747 <p
>With this prototype in place, I can insert my Yubikey, and get this
6748 desktop notification to show up (only once, the first time it is
6749 inserted):
</p
>
6751 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6753 <p
>For this prototype to be really useful, some way to automatically
6754 install the proposed packages by pressing the
"Please install
6755 program(s)
" button should to be implemented.
</p
>
6757 <p
>If this idea seem useful to you, and you want to help make it
6758 happen, please help me update the discover-data database with mappings
6759 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6760 list the package you would like to have installed when a given
6761 hardware device is inserted into your computer, and report bugs using
6762 reportbug if it isn
't. Or, if you know of a better way to provide
6763 such mapping, please let me know.
</p
>
6765 <p
>This prototype need more work, and there are several questions that
6766 should be considered before it is ready for production use. Is dbus
6767 the correct way to detect new hardware? At the moment I look for HAL
6768 dbus events on the system bus, because that is the events I could see
6769 on my Debian Squeeze KDE desktop. Are there better events to use?
6770 How should the user be notified? Is the desktop notification
6771 mechanism the best option, or should the background daemon raise a
6772 popup instead? How should packages be installed? When should they
6773 not be installed?
</p
>
6775 <p
>If you want to help getting such feature implemented in Debian,
6776 please send me an email. :)
</p
>
6781 <title>New IRC channel for LEGO designers using Debian
</title>
6782 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6783 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6784 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6785 <description><p
>During Christmas, I have worked a bit on the Debian support for
6786 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6787 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6788 discovered I had to build all the tools myself because none were
6789 already in Debian Squeeze. If Debian support for LEGO is something
6790 you care about, please join me on the IRC channel
6791 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6792 irc.debian.org). There is a lot that could be done to improve the
6793 Debian support for LEGO designers. For example both CAD software
6794 and Mindstorm compilers are missing. :)
</p
>
6796 <p
>Update
2012-
01-
03: A
6797 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6798 including links to Lego related packages is now available.
</p
>
6803 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6804 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6805 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6806 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6807 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6808 year! I hope next year will prove to be a good year.
</p
>
6810 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6811 decentralised
"currency
" that allow people to transfer bitcoins
6812 between each other with minimal overhead, is a very interesting
6813 experiment. And as I wrote a few days ago, the bitcoin situation in
6814 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6815 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6816 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6817 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6818 for one of the ftpmasters to approve the new bitcoin-qt package
6821 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6822 team in Debian, you can easily test the package in Debian Squeeze
6823 using the following steps to get a set of working packages:
</p
>
6825 <blockquote
><pre
>
6826 git clone git://git.debian.org/git/collab-maint/bitcoin
6828 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6829 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6830 </pre
></blockquote
>
6832 <p
>You might have to install some build dependencies as well. The
6833 list of commands should give you two packages, bitcoind and
6834 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6835 client will download the complete set of bitcoin
"blocks
", which need
6836 around
5.6 GiB of data on my machine at the moment. Make sure your
6837 ~/.bitcoin/ directory have lots of spare room if you want to download
6838 all the blocks. The client will warn if the disk is getting full, so
6839 there is not really a problem if you got too little room, but you will
6840 not be able to get all the features out of the client.
</p
>
6842 <p
>As usual, if you use bitcoin and want to show your support of my
6843 activities, please send Bitcoin donations to my address
6844 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6849 <title>A word on bitcoin support in Debian
</title>
6850 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6851 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6852 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6853 <description><p
>It has been a while since I wrote about
6854 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6855 peer-to-peer based crypto-currency, and the reason is simply that I
6856 have been busy elsewhere. But two days ago, I started looking at the
6857 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6858 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6859 is now maintained by a
6860 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6861 people
</a
>, and the grunt work had already been done by this team. We
6862 owe a huge thank you to all these team members. :)
6863 But I was sad to discover that the bitcoin client is missing in
6864 Wheezy. It is only available in Sid (and an outdated client from
6865 backports). The client had several RC bugs registered in BTS blocking
6866 it from entering testing. To try to help the team and improve the
6867 situation, I spent some time providing patches and triaging the bug
6868 reports. I also had a look at the bitcoin package available from Matt
6870 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6871 Ubuntu
</a
>, and moved the useful pieces from that version into the
6872 Debian package.
</p
>
6874 <p
>After checking with the main package maintainer Jonas Smedegaard on
6875 IRC, I pushed several patches into the collab-maint git repository to
6876 improve the package. It now contains fixes for the RC issues (not from
6877 me, but fixed by Scott Howard), build rules for a Qt GUI client
6878 package, konqueror support for the bitcoin: URI and bash completion
6879 setup. As I work on Debian Squeeze, I also created
6880 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6881 patch to backport
</a
> the latest version. Jonas is going to look at
6882 it and try to integrate it into the git repository before uploading a
6883 new version to unstable.
6885 <p
>I would very much like bitcoin to succeed, to get rid of the
6886 centralized control currently exercised in the monetary system. I
6887 find it completely unacceptable that the USA government is collecting
6888 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6889 that the major credit card companies can block legal money
6890 transactions to Wikileaks. But for bitcoin to succeed, more people
6891 need to use bitcoins, and more people need to accept bitcoins when
6892 they sell products and services. Improving the bitcoin support in
6893 Debian is a small step in the right direction, but not enough.
6894 Unfortunately the user experience when browsing the web and wanting to
6895 pay with bitcoin is still not very good. The bitcoin: URI is a step
6896 in the right direction, but need to work in most or every browser in
6897 use. Also the bitcoin-qt client is too heavy to fire up to do a
6898 quick transaction. I believe there are other clients available, but
6899 have not tested them.
</p
>
6902 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6903 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6904 I received
20.15 BTC so far on the address I provided in my blog two
6905 years ago, as can be
6906 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6907 on the blockexplorer service
</a
>. Thank you everyone for your
6908 donation. The blockexplorer service demonstrates quite well that
6909 bitcoin is not quite anonymous and untracked. :) I wonder if the
6910 number of users have gone up since then. If you use bitcoin and want
6911 to show your support of my activity, please send Bitcoin donations to
6912 the same address as last time,
6913 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6918 <title>Git repository for song book for Computer Scientists
</title>
6919 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6921 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6922 <description><p
>As I
6923 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6924 this summer
</a
>, I have created a Computer Science song book a few
6925 years ago, and today I finally found time to create a public
6926 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6927 repository for the project
</a
>.
</p
>
6929 <p
>If you want to help out, please clone the source and submit patches
6930 to the HTML version. To generate the PDF and PostScript version,
6931 please use prince XML, or let me know about a useful free software
6932 processor capable of creating a good looking PDF from the HTML.
</p
>
6934 <p
>Want to sing? You can still find the song book in HTML, PDF and
6935 PostScript formats at
6936 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6937 Science Songbook
</a
>.
</p
>
6942 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6943 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6944 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6945 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6946 <description><p
>I dag fyller
6947 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6948 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6949 si gratulerer med dagen, Debian!
</p
>
6954 <title>Song book for Computer Scientists
</title>
6955 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6957 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6958 <description><p
>Many years ago, while studying Computer Science at the
6959 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6960 collecting computer related songs for use at parties. The original
6961 version was written in LaTeX, but a few years ago I got help from
6962 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6963 while keeping the ability to create a nice book in PDF format. I have
6964 not had time to maintain the book for a while now, and guess I should
6965 put it up on some public version control repository where others can
6966 help me extend and update the book. If anyone is volunteering to help
6967 me with this, send me an email. Also let me know if there are songs
6968 missing in my book.
</p
>
6970 <p
>I have not mentioned the book on my blog so far, and it occured to
6971 me today that I really should let all my readers share the joys of
6972 singing out load about programming, computers and computer networks.
6973 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6974 12</a
> is about to start (and I am not going). Want to sing? Check
6975 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6976 Computer Science Songbook
</a
>.
6981 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6982 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6983 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6984 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6985 <description><p
>At work we have heaps of servers. I believe the total count is
6986 around
1000 at the moment. To be able to get help from the vendors
6987 when something go wrong, we want to keep the firmware on the servers
6988 up to date. If the firmware isn
't the latest and greatest, the
6989 vendors typically refuse to start debugging any problems until the
6990 firmware is upgraded. So before every reboot, we want to upgrade the
6991 firmware, and we would really like everyone handling servers at the
6992 university to do this themselves when they plan to reboot a machine.
6993 For that to happen we at the unix server admin group need to provide
6994 the tools to do so.
</p
>
6996 <p
>To make firmware upgrading easier, I am working on a script to
6997 fetch and install the latest firmware for the servers we got. Most of
6998 our hardware are from Dell and HP, so I have focused on these servers
6999 so far. This blog post is about the Dell part.
</P
>
7001 <p
>On the Dell FTP site I was lucky enough to find
7002 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7003 with firmware information for all
11th generation servers, listing
7004 which firmware should be used on a given model and where on the FTP
7005 site I can find it. Using a simple perl XML parser I can then
7006 download the shell scripts Dell provides to do firmware upgrades from
7007 within Linux and reboot when all the firmware is primed and ready to
7008 be activated on the first reboot.
</p
>
7010 <p
>This is the Dell related fragment of the perl code I am working on.
7011 Are there anyone working on similar tools for firmware upgrading all
7012 servers at a site? Please get in touch and lets share resources.
</p
>
7014 <p
><pre
>
7018 use File::Temp qw(tempdir);
7020 # Install needed RHEL packages if missing
7022 'XML::Simple
' =
> 'perl-XML-Simple
',
7024 for my $module (keys %rhelmodules) {
7025 eval
"use $module;
";
7027 my $pkg = $rhelmodules{$module};
7028 system(
"yum install -y $pkg
");
7029 eval
"use $module;
";
7033 my $errorsto =
'pere@hungry.com
';
7039 sub run_firmware_script {
7040 my ($opts, $script) = @_;
7042 print STDERR
"fail: missing script name\n
";
7045 print STDERR
"Running $script\n\n
";
7047 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7048 print STDERR
"success: firmware script ran succcessfully\n
";
7050 print STDERR
"fail: firmware script returned error\n
";
7054 sub run_firmware_scripts {
7055 my ($opts, @dirs) = @_;
7056 # Run firmware packages
7057 for my $dir (@dirs) {
7058 print STDERR
"info: Running scripts in $dir\n
";
7059 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7060 while (my $s = readdir $dh) {
7061 next if $s =~ m/^\.\.?/;
7062 run_firmware_script($opts,
"$dir/$s
");
7070 print STDERR
"info: Downloading $url\n
";
7071 system(
"wget --quiet \
"$url\
"");
7076 my $product = `dmidecode -s system-product-name`;
7079 if ($product =~ m/PowerEdge/) {
7081 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7082 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7084 my $tmpdir = tempdir(
7088 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7089 system(
'gunzip Catalog.xml.gz
');
7090 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7091 # -q is quiet, disabling interactivity and reducing console output
7092 my $fwopts =
"-q
";
7094 for my $url (@paths) {
7095 fetch_dell_fw($url);
7097 run_firmware_scripts($fwopts, $tmpdir);
7099 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7100 print STDERR
"error: Please report to $errorsto.\n
";
7104 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7105 print STDERR
"error: Please report to $errorsto.\n
";
7111 my $url =
"ftp://ftp.us.dell.com/$path
";
7115 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7116 # firmware packages to download from Dell. Only work for Linux
7117 # machines and
11th generation Dell servers.
7118 sub fetch_dell_fw_list {
7119 my $filename = shift;
7121 my $product = `dmidecode -s system-product-name`;
7123 my ($mybrand, $mymodel) = split(/\s+/, $product);
7125 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7127 my $xml = XMLin($filename);
7129 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7130 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7131 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7133 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7134 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7136 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7138 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7140 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7143 for my $component (@{$xml-
>{SoftwareComponent}}) {
7144 my $componenttype = $component-
>{ComponentType}-
>{value};
7146 # Drop application packages, only firmware and BIOS
7147 next if
'APAC
' eq $componenttype;
7149 my $cpath = $component-
>{path};
7150 for my $path (@paths) {
7151 if ($cpath =~ m%/$path$%) {
7152 push(@paths, $cpath);
7160 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7161 it could work on other platforms with some tweaking. Anyone know a
7162 index like Catalog.xml is available from HP for HP servers? At the
7163 moment I maintain a similar list manually and it is quickly getting
7169 <title>How is booting into runlevel
1 different from single user boots?
</title>
7170 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7172 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7173 <description><p
>Wouter Verhelst have some
7174 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7175 comments and opinions
</a
> on my blog post on
7176 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7177 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7178 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7179 default KDE desktop in Debian
</a
>. I only have time to address one
7180 small piece of his comment now, and though it best to address the
7181 misunderstanding he bring forward:
</p
>
7183 <p
><blockquote
>
7184 Currently, a system admin has four options: [...] boot to a
7185 single-user system (by adding
'single
' to the kernel command line;
7186 this runs rcS and rc1 scripts)
7187 </blockquote
></p
>
7189 <p
>This make me believe Wouter believe booting into single user mode
7190 and booting into runlevel
1 is the same. I am not surprised he
7191 believe this, because it would make sense and is a quite sensible
7192 thing to believe. But because the boot in Debian is slightly broken,
7193 runlevel
1 do not work properly and it isn
't the same as single user
7194 mode. I
'll try to explain what is actually happing, but it is a bit
7195 hard to explain.
</p
>
7197 <p
>Single user mode is defined like this in /etc/inittab:
7198 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7199 executed in single user mode is sulogin. Single user mode is a boot
7200 state
"between
" the runlevels, and when booting into single user mode,
7201 only the scripts in /etc/rcS.d/ are executed before the init process
7202 enters the single user state. When switching to runlevel
1, the state
7203 is in fact not ending in runlevel
1, but it passes through runlevel
1
7204 and end up in the single user mode (see /etc/rc1.d/S03single, which
7205 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7206 1. It is confusing that the
'S
' (single user) init mode is not the
7207 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7210 <p
>This summary might make it clearer. When booting for the first
7211 time into single user mode, the following commands are executed:
7212 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7213 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7214 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7215 trying to continue after visiting single user mode. Not all services
7216 are started again as they should, causing the machine to end up in an
7217 unpredicatble state. This is why Debian admins recommend rebooting
7218 after visiting single user mode.
</p
>
7220 <p
>A similar problem with runlevel
1 is caused by the amount of
7221 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7222 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7223 stopped when passing through the scripts in /etc/rc1.d/, and not
7224 started again when switching away from runlevel
1 to the runlevels
7225 2-
5. I believe the problem is best fixed by moving all the scripts
7226 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7227 functioning single user mode during boot.
</p
>
7229 <p
>I have spent several years investigating the Debian boot system,
7230 and discovered this problem a few years ago. I suspect it originates
7231 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7236 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7237 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7238 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7239 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7240 <description><p
>In the Debian boot system, several packages include scripts that
7241 are started from /etc/rcS.d/. In fact, there is a bite more of them
7242 than make sense, and this causes a few problems. What kind of
7243 problems, you might ask. There are at least two problems. The first
7244 is that it is not possible to recover a machine after switching to
7245 runlevel
1. One need to actually reboot to get the machine back to
7246 the expected state. The other is that single user boot will sometimes
7247 run into problems because some of the subsystems are activated before
7248 the root login is presented, causing problems when trying to recover a
7249 machine from a problem in that subsystem. A minor additional point is
7250 that moving more scripts out of rcS.d/ and into the other rc#.d/
7251 directories will increase the amount of scripts that can run in
7252 parallel during boot, and thus decrease the boot time.
</p
>
7254 <p
>So, which scripts should start from rcS.d/. In short, only the
7255 scripts that _have_ to execute before the root login prompt is
7256 presented during a single user boot should go there. Everything else
7257 should go into the numeric runlevels. This means things like
7258 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7259 the numeric runlevels. Today in Debian, there are around
115 init.d
7260 scripts that are started from rcS.d/, and most of them should be moved
7261 out. Do your package have one of them? Please help us make single
7262 user and runlevel
1 better by moving it.
</p
>
7264 <p
>Scripts setting up the screen, keyboard, system partitions
7265 etc. should still be started from rcS.d/, but there is for example no
7266 need to have the network enabled before the single user login prompt
7267 is presented.
</p
>
7269 <p
>As always, things are not so easy to fix as they sound. To keep
7270 Debian systems working while scripts migrate and during upgrades, the
7271 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7272 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7273 and the next ones can only be moved when their dependencies have been
7274 moved first. This migration must be done sequentially while we ensure
7275 that the package system upgrade packages in the right order to keep
7276 the system state correct. This will require some coordination when it
7277 comes to network related packages, but most of the packages with
7278 scripts that should migrate do not have anything in rcS.d/ depending
7279 on them. Some packages have already been updated, like the sudo
7280 package, while others are still left to do. I wish I had time to work
7281 on this myself, but real live constrains make it unlikely that I will
7282 find time to push this forward.
</p
>
7287 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7288 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7290 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7291 <description><p
>While at Debconf11, I have several times during discussions
7292 mentioned the issues I believe should be improved in Debian for its
7293 desktop to be useful for more people. The use case for this is my
7294 parents, which are currently running Kubuntu which solve the
7297 <p
>I suspect these four missing features are not very hard to
7298 implement. After all, they are present in Ubuntu, so if we wanted to
7299 do this in Debian we would have a source.
</p
>
7303 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7304 are new packages available for upgrades, a icon in the KDE status bar
7305 indicate this, and clicking on it will activate the simple upgrade
7306 tool to handle it. I have no problem guiding both of my parents
7307 through the process over the phone. If a kernel reboot is required,
7308 this too is indicated by the status bars and the upgrade tool. Last
7309 time I checked, nothing with the same features was working in KDE in
7312 <li
><strong
>Simple handling of missing Firefox browser
7313 plugins.
</strong
> When the browser encounter a MIME type it do not
7314 currently have a handler for, it will ask the user if the system
7315 should search for a package that would add support for this MIME type,
7316 and if the user say yes, the APT sources will be searched for packages
7317 advertising the MIME type in their control file (visible in the
7318 Packages file in the APT archive). If one or more packages are found,
7319 it is a simple click of the mouse to add support for the missing mime
7320 type. If the package require the user to accept some non-free
7321 license, this is explained to the user. The entire process make it
7322 more clear to the user why something do not work in the browser, and
7323 make the chances higher for the user to blame the web page authors and
7324 not the browser for any missing features.
</li
>
7326 <li
><strong
>Simple handling of missing multimedia codec/format
7327 handlers.
</strong
> When the media players encounter a format or codec
7328 it is not supporting, a dialog pop up asking the user if the system
7329 should search for a package that would add support for it. This
7330 happen with things like MP3, Windows Media or H
.264. The selection
7331 and installation procedure is very similar to the Firefox browser
7332 plugin handling. This is as far as I know implemented using a
7333 gstreamer hook. The end result is that the user easily get access to
7334 the codecs that are present from the APT archives available, while
7335 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7337 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7338 displaying a text/plain file in my Debian browser, it will propose to
7339 start emacs to show it. If I remember correctly, when doing the same
7340 in Kunbutu it show the file as a text file in the browser. At least I
7341 know Opera will show text files within the browser. I much prefer the
7342 latter behaviour.
</li
>
7346 <p
>There are other nice features as well, like the simplified suite
7347 upgrader, but given that I am the one mostly doing the dist-upgrade,
7348 it do not matter much.
</p
>
7350 <p
>I really hope we could get these features in place for the next
7351 Debian release. It would require the coordinated effort of several
7352 maintainers, but would make the end user experience a lot better.
</p
>
7357 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7358 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7360 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7361 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7362 site is build on Debian/Squeeze, and this platform was chosen because
7363 I am most familiar with Debian (being a Debian Developer for around
10
7364 years) because it is the latest stable Debian release which should get
7365 security support for a few years.
</p
>
7367 <p
>The web service is written in Perl, and depend on some perl modules
7368 that are missing in Debian at the moment. It would be great if these
7369 modules were added to the Debian archive, allowing anyone to set up
7370 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7371 in their own country using only Debian packages. The list of modules
7372 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7373 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7374 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7375 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7376 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7377 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7378 easier in the future.
</p
>
7380 <p
>Thanks to the great tools in Debian, getting the missing modules
7381 installed on my server was a simple call to
'cpan2deb Module::Name
'
7382 and
'dpkg -i
' to install the resulting package. But this leave me
7383 with the responsibility of tracking security problems, which I really
7384 do not have time for.
</p
>
7389 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7390 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7391 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7392 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7393 <description><p
>Here is a small update for my English readers. Most of my blog
7394 posts have been in Norwegian the last few weeks, so here is a short
7395 update in English.
</p
>
7397 <p
>The kids still keep me too busy to get much free software work
7398 done, but I did manage to organise a project to get a Norwegian port
7399 of the British service
7400 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7401 and it has been running for a month now. The entire project has been
7402 organised by me and two others. Around Christmas we gathered sponsors
7403 to fund the development work. In January I drafted a contract with
7404 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7405 and in February the development took place. Most of it involved
7406 converting the source to use GPS coordinates instead of British
7407 easting/northing, and the resulting code should be a lot easier to get
7408 running in any country by now. The Norwegian
7409 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7410 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7411 source and the source for administrative borders in Norway, and
7412 support for this had to be added/fixed.
</p
>
7414 <p
>The Norwegian version went live March
3th, and we spent the weekend
7415 polishing the system before we announced it March
7th. The system is
7416 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7417 problem reports in a few weeks. Soon we hope to announce the Android
7418 and iPhone versions making it even easier to report problems with the
7419 public infrastructure.
</p
>
7421 <p
>Perhaps something to consider for those of you in countries without
7422 such service?
</p
>
7427 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7428 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7429 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7430 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7431 <description><p
>The last few days I have looked at ways to track open security
7432 issues here at my work with the University of Oslo. My idea is that
7433 it should be possible to use the information about security issues
7434 available on the Internet, and check our locally
7435 maintained/distributed software against this information. It should
7436 allow us to verify that no known security issues are forgotten. The
7437 CVE database listing vulnerabilities seem like a great central point,
7438 and by using the package lists from Debian mapped to CVEs provided by
7439 the testing security team, I believed it should be possible to figure
7440 out which security holes were present in our free software
7441 collection.
</p
>
7443 <p
>After reading up on the topic, it became obvious that the first
7444 building block is to be able to name software packages in a unique and
7445 consistent way across data sources. I considered several ways to do
7446 this, for example coming up with my own naming scheme like using URLs
7447 to project home pages or URLs to the Freshmeat entries, or using some
7448 existing naming scheme. And it seem like I am not the first one to
7449 come across this problem, as MITRE already proposed and implemented a
7450 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7451 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7452 software, hardware and other platform components. The CPE ids are
7453 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7454 Vulnerability Database
</a
>, allowing me to look up know security
7455 issues for any CPE name. With this in place, all I need to do is to
7456 locate the CPE id for the software packages we use at the university.
7457 This is fairly trivial (I google for
'cve cpe $package
' and check the
7458 NVD entry if a CVE for the package exist).
</p
>
7460 <p
>To give you an example. The GNU gzip source package have the CPE
7461 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7462 check out, one could look up
7463 <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
7464 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7465 The most recent one is
7466 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7467 and at the bottom of the NVD page for this vulnerability the complete
7468 list of affected versions is provided.
</p
>
7470 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7471 for offline processing of issues. Using this dump, I
've written a
7472 small script taking a list of CPEs as input and list all CVEs
7473 affecting the packages represented by these CPEs. One give it CPEs
7474 with version numbers as specified above and get a list of open
7475 security issues out.
</p
>
7477 <p
>Of course for this approach to be useful, the quality of the NVD
7478 information need to be high. For that to happen, I believe as many as
7479 possible need to use and contribute to the NVD database. I notice
7481 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7482 map from CVE to CPE
</a
>, indicating that they are using the CPE
7483 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7485 <p
>To get an idea about the quality for free software, I spent some
7486 time making it possible to compare the CVE database from Debian with
7487 the CVE database in NVD. The result look fairly good, but there are
7488 some inconsistencies in NVD (same software package having several
7489 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7490 Debian believe are affected by a CVE). Hope to find time to improve
7491 the quality of NVD, but that require being able to get in touch with
7492 someone maintaining it. So far my three emails with questions and
7493 corrections have not seen any reply, but I hope contact can be
7494 established soon.
</p
>
7496 <p
>An interesting application for CPEs is cross platform package
7497 mapping. It would be useful to know which packages in for example
7498 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7499 this would be trivial if all linux distributions provided CPE entries
7500 for their packages.
</p
>
7505 <title>Which module is loaded for a given PCI and USB device?
</title>
7506 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7507 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7508 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7509 <description><p
>In the
7510 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7511 package in Debian, there is a script to report useful information
7512 about the running hardware for use when people report missing
7513 information. One part of this script that I find very useful when
7514 debugging hardware problems, is the part mapping loaded kernel module
7515 to the PCI device it claims. It allow me to quickly see if the kernel
7516 module I expect is driving the hardware I am struggling with. To see
7517 the output, make sure discover-data is installed and run
7518 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7519 one of my machines like this:
</p
>
7523 10de:
03eb i2c_nforce2
7526 10de:
03f0 snd_hda_intel
7535 <p
>The code in question look like this, slightly modified for
7536 readability and to drop the output to file descriptor
3:
</p
>
7539 if [ -d /sys/bus/pci/devices/ ] ; then
7540 echo loaded pci modules:
7542 cd /sys/bus/pci/devices/
7543 for address in * ; do
7544 if [ -d
"$address/driver/module
" ] ; then
7545 module=`cd $address/driver/module ; pwd -P | xargs basename`
7546 if grep -q
"^$module
" /proc/modules ; then
7547 address=$(echo $address |sed s/
0000://)
7548 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7549 echo
"$id $module
"
7558 <p
>Similar code could be used to extract USB device module
7562 if [ -d /sys/bus/usb/devices/ ] ; then
7563 echo loaded usb modules:
7565 cd /sys/bus/usb/devices/
7566 for address in * ; do
7567 if [ -d
"$address/driver/module
" ] ; then
7568 module=`cd $address/driver/module ; pwd -P | xargs basename`
7569 if grep -q
"^$module
" /proc/modules ; then
7570 address=$(echo $address |sed s/
0000://)
7571 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7572 if [
"$id
" ] ; then
7573 echo
"$id $module
"
7583 <p
>This might perhaps be something to include in other tools as
7589 <title>How to test if a laptop is working with Linux
</title>
7590 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7591 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7592 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7593 <description><p
>The last few days I have spent at work here at the
<a
7594 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7595 batch of computers will work with Linux. Every year for the last few
7596 years the university have organised shared bid of a few thousand
7597 computers, and this year HP won the bid. Two different desktops and
7598 five different laptops are on the list this year. We in the UNIX
7599 group want to know which one of these computers work well with RHEL
7600 and Ubuntu, the two Linux distributions we currently handle at the
7601 university.
</p
>
7603 <p
>My test method is simple, and I share it here to get feedback and
7604 perhaps inspire others to test hardware as well. To test, I PXE
7605 install the OS version of choice, and log in as my normal user and run
7606 a few applications and plug in selected pieces of hardware. When
7607 something fail, I make a note about this in the test matrix and move
7608 on. If I have some spare time I try to report the bug to the OS
7609 vendor, but as I only have the machines for a short time, I rarely
7610 have the time to do this for all the problems I find.
</p
>
7612 <p
>Anyway, to get to the point of this post. Here is the simple tests
7613 I perform on a new model.
</p
>
7617 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7618 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7619 RHEL5 and Debian Edu/Squeeze.
</li
>
7621 <li
>Is X.org working? If the graphical login screen show up after
7622 installation, X.org is working.
</li
>
7624 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7625 package mesa-utils on Ubuntu) and writing down the frames per second
7626 reported by the program.
</li
>
7628 <li
>Is sound working? With Gnome and KDE, a sound is played when
7629 logging in, and if I can hear this the test is successful. If there
7630 are several audio exits on the machine, I try them all and check if
7631 the Gnome/KDE audio mixer can control where to send the sound. I
7632 normally test this by playing
7633 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7634 video
</a
> in Firefox/Iceweasel.
</li
>
7636 <li
>Is the USB subsystem working? I test this by plugging in a USB
7637 memory stick and see if Gnome/KDE notices this.
</li
>
7639 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7640 I have lying around, and see if Gnome/KDE notices this.
</li
>
7642 <li
>Is any built in camera working? Test using cheese, and see if a
7643 picture from the v4l device show up.
</li
>
7645 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7646 any bluetooth devices are discovered. In my office, I normally see a
7649 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7650 memory modules lying around, and stick them in and see if Gnome/KDE
7651 notice this.
</li
>
7653 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7654 special button work, and if the laptop continue to work after
7657 <li
>For laptops, is the extra buttons working, like audio level,
7658 adjusting background light, switching on/off external video output,
7659 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7660 laptop to laptop, so I just write down which are working and which are
7663 <li
>Some laptops have smart card readers, finger print readers,
7664 acceleration sensors etc. I rarely test these, as I do not know how
7665 to quickly test if they are working or not, so I only document their
7666 existence.
</li
>
7670 <p
>By now I suspect you are really curious what the test results are
7671 for the HP machines I am testing. I
'm not done yet, so I will report
7672 the test results later. For now I can report that HP
8100 Elite work
7673 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7674 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7675 can see, I have most machines left to test. One interesting
7676 observation is that Ubuntu Lucid has almost twice the frame rate than
7677 RHEL6 with glxgears. No idea why.
</p
>
7682 <title>Some thoughts on BitCoins
</title>
7683 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7685 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7686 <description><p
>As I continue to explore
7687 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7688 what properties the system have, and how it will be affected by laws
7689 and regulations here in Norway. Here are some random notes.
</p
>
7691 <p
>One interesting thing to note is that since the transactions are
7692 verified using a peer to peer network, all details about a transaction
7693 is known to everyone. This means that if a BitCoin address has been
7694 published like I did with mine in my initial post about BitCoin, it is
7695 possible for everyone to see how many BitCoins have been transfered to
7696 that address. There is even a web service to look at the details for
7697 all transactions. There I can see that my address
7698 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7699 have received
16.06 Bitcoin, the
7700 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7701 address of Simon Phipps have received
181.97 BitCoin and the address
7702 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7703 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7704 every one of you that donated bitcoins to support my activity. The
7705 fact that anyone can see how much money was transfered to a given
7706 address make it more obvious why the BitCoin community recommend to
7707 generate and hand out a new address for each transaction. I
'm told
7708 there is no way to track which addresses belong to a given person or
7709 organisation without the person or organisation revealing it
7710 themselves, as Simon, EFF and I have done.
</p
>
7712 <p
>In Norway, and in most other countries, there are laws and
7713 regulations limiting how much money one can transfer across the border
7714 without declaring it. There are money laundering, tax and accounting
7715 laws and regulations I would expect to apply to the use of BitCoin.
7716 If the Skolelinux foundation
7717 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7718 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7719 normal bank transfers like EFF is doing, how should this be accounted?
7720 Given that it is impossible to know if money can cross the border or
7721 not, should everything or nothing be declared? What exchange rate
7722 should be used when calculating taxes? Would receivers have to pay
7723 income tax if the foundation were to pay Skolelinux contributors in
7724 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7726 <p
>For a currency to be useful and successful, it must be trusted and
7727 accepted by a lot of users. It must be possible to get easy access to
7728 the currency (as a wage or using currency exchanges), and it must be
7729 easy to spend it. At the moment BitCoin seem fairly easy to get
7730 access to, but there are very few places to spend it. I am not really
7731 a regular user of any of the vendor types currently accepting BitCoin,
7732 so I wonder when my kind of shop would start accepting BitCoins. I
7733 would like to buy electronics, travels and subway tickets, not herbs
7734 and books. :) The currency is young, and this will improve over time
7735 if it become popular, but I suspect regular banks will start to lobby
7736 to get BitCoin declared illegal if it become popular. I
'm sure they
7737 will claim it is helping fund terrorism and money laundering (which
7738 probably would be true, as is any currency in existence), but I
7739 believe the problems should be solved elsewhere and not by blaming
7740 currencies.
</p
>
7742 <p
>The process of creating new BitCoins is called mining, and it is
7743 CPU intensive process that depend on a bit of luck as well (as one is
7744 competing against all the other miners currently spending CPU cycles
7745 to see which one get the next lump of cash). The
"winner
" get
50
7746 BitCoin when this happen. Yesterday I came across the obvious way to
7747 join forces to increase ones changes of getting at least some coins,
7748 by coordinating the work on mining BitCoins across several machines
7749 and people, and sharing the result if one is lucky and get the
50
7751 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7752 if this sounds interesting. I have not had time to try to set up a
7753 machine to participate there yet, but have seen that running on ones
7754 own for a few days have not yield any BitCoins througth mining
7757 <p
>Update
2010-
12-
15: Found an
<a
7758 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7759 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7760 it was interesting to read. The arguments presented seem to be
7761 equally valid for gold, which was used as a currency for many years.
</p
>
7766 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7767 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7768 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7769 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7770 <description><p
>With this weeks lawless
7771 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7772 attacks
</a
> on Wikileak and
7773 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7774 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7775 not be trusted to handle money transactions.
7777 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7778 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7779 mine mentioned earlier. I decided to follow Simon
's example, and get
7780 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7781 some help from my friend to get it all running, and he even handed me
7782 some bitcoins to get started. I even donated a few bitcoins to Simon
7783 for helping me remember BitCoin.
</p
>
7785 <p
>So, what is bitcoins, you probably wonder? It is a digital
7786 crypto-currency, decentralised and handled using peer-to-peer
7787 networks. It allows anonymous transactions and prohibits central
7788 control over the transactions, making it impossible for governments
7789 and companies alike to block donations and other transactions. The
7790 source is free software, and while the key dependency wxWidgets
2.9
7791 for the graphical user interface is missing in Debian, the command
7792 line client builds just fine. Hopefully Jonas
7793 <a href=
"http://bugs.debian.org/
578157">will get the package into
7794 Debian
</a
> soon.
</p
>
7796 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7797 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7798 bitcoins
</a
> when selling services and goods, and there are even
7799 currency
"stock
" markets where the exchange rate is decided. There
7800 are not many users so far, but the concept seems promising. If you
7801 want to get started and lack a friend with any bitcoins to spare,
7803 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7804 bitcoin at the time of writing). Use
7805 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7806 on the current exchange rates.
</p
>
7808 <p
>As an experiment, I have decided to set up bitcoind on one of my
7809 machines. If you want to support my activity, please send Bitcoin
7810 donations to the address
7811 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7816 <title>Why isn
't Debian Edu using VLC?
</title>
7817 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7818 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7819 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7820 <description><p
>In the latest issue of Linux Journal, the readers choices were
7821 presented, and the winner among the multimedia player were VLC.
7822 Personally, I like VLC, and it is my player of choice when I first try
7823 to play a video file or stream. Only if VLC fail will I drag out
7824 gmplayer to see if it can do better. The reason is mostly the failure
7825 model and trust. When VLC fail, it normally pop up a error message
7826 reporting the problem. When mplayer fail, it normally segfault or
7827 just hangs. The latter failure mode drain my trust in the program.
<p
>
7829 <p
>But even if VLC is my player of choice, we have choosen to use
7830 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7831 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7832 plugin to play web videos seamlessly, and the VLC browser plugin is
7833 not very good. For example, it lack in-line control buttons, so there
7834 is no way for the user to pause the video. Also, when I
7835 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7836 tested the browser plugins
</a
> available in Debian, the VLC plugin
7837 failed on several video pages where mplayer based plugins worked. If
7838 the browser plugin for VLC was as good as the gecko-mediaplayer
7839 package (which uses mplayer), we would switch.
</P
>
7841 <p
>While VLC is a good player, its user interface is slightly
7842 annoying. The most annoying feature is its inconsistent use of
7843 keyboard shortcuts. When the player is in full screen mode, its
7844 shortcuts are different from when it is playing the video in a window.
7845 For example, space only work as pause when in full screen mode. I
7846 wish it had consisten shortcuts and that space also would work when in
7847 window mode. Another nice shortcut in gmplayer is [enter] to restart
7848 the current video. It is very nice when playing short videos from the
7849 web and want to restart it when new people arrive to have a look at
7850 what is going on.
</p
>
7855 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7856 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7857 <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>
7858 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7859 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7860 upgrade testing of the
7861 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7862 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7863 This seem like a very good idea, so I adjusted by test scripts and
7864 can now present the updated result from today:
</p
>
7866 <p
>This is for Gnome:
</p
>
7868 <p
>Installed using apt-get, missing with aptitude
</p
>
7870 <blockquote
><p
>
7875 browser-plugin-gnash
7882 freedesktop-sound-theme
7884 gconf-defaults-service
7899 gnome-desktop-environment
7903 gnome-session-canberra
7908 gstreamer0.10-fluendo-mp3
7914 libapache2-mod-dnssd
7917 libaprutil1-dbd-sqlite3
7920 libboost-date-time1.42
.0
7921 libboost-python1.42
.0
7922 libboost-thread1.42
.0
7924 libchamplain-gtk-
0.4-
0
7926 libclutter-gtk-
0.10-
0
7933 libfreerdp-plugins-standard
7948 libgnomepanel2.24-cil
7953 libgtksourceview2.0-common
7954 libmono-addins-gui0.2-cil
7955 libmono-addins0.2-cil
7956 libmono-cairo2.0-cil
7957 libmono-corlib2.0-cil
7958 libmono-i18n-west2.0-cil
7959 libmono-posix2.0-cil
7960 libmono-security2.0-cil
7961 libmono-sharpzip2.84-cil
7962 libmono-system2.0-cil
7965 libndesk-dbus-glib1.0-cil
7966 libndesk-dbus1.0-cil
7976 libtelepathy-farsight0
7985 nautilus-sendto-empathy
7989 python-aptdaemon-gtk
7991 python-beautifulsoup
8006 python-gtksourceview2
8017 python-pkg-resources
8024 python-twisted-conch
8030 python-zope.interface
8035 rhythmbox-plugin-cdrecorder
8042 system-config-printer-udev
8044 telepathy-mission-control-
5
8055 </p
></blockquote
>
8057 <p
>Installed using apt-get, removed with aptitude
</p
>
8059 <blockquote
><p
>
8065 fast-user-switch-applet
8084 libgtksourceview2.0-
0
8086 libsdl1.2debian-alsa
8092 system-config-printer
8097 </p
></blockquote
>
8099 <p
>Installed using aptitude, missing with apt-get
</p
>
8101 <blockquote
><p
>
8102 gstreamer0.10-gnomevfs
8103 </p
></blockquote
>
8105 <p
>Installed using aptitude, removed with apt-get
</p
>
8107 <blockquote
><p
>
8109 </p
></blockquote
>
8111 <p
>This is for KDE:
</p
>
8113 <p
>Installed using apt-get, missing with aptitude
</p
>
8115 <blockquote
><p
>
8117 </p
></blockquote
>
8119 <p
>Installed using apt-get, removed with aptitude
</p
>
8121 <blockquote
><p
>
8124 </p
></blockquote
>
8126 <p
>Installed using aptitude, missing with apt-get
</p
>
8128 <blockquote
><p
>
8142 kdeartwork-emoticons
8144 kdeartwork-theme-icon
8148 kdebase-workspace-bin
8149 kdebase-workspace-data
8163 kscreensaver-xsavers
8178 plasma-dataengines-workspace
8180 plasma-desktopthemes-artwork
8181 plasma-runners-addons
8182 plasma-scriptengine-googlegadgets
8183 plasma-scriptengine-python
8184 plasma-scriptengine-qedje
8185 plasma-scriptengine-ruby
8186 plasma-scriptengine-webkit
8187 plasma-scriptengines
8188 plasma-wallpapers-addons
8189 plasma-widget-folderview
8190 plasma-widget-networkmanagement
8194 xscreensaver-data-extra
8196 xscreensaver-gl-extra
8197 xscreensaver-screensaver-bsod
8198 </p
></blockquote
>
8200 <p
>Installed using aptitude, removed with apt-get
</p
>
8202 <blockquote
><p
>
8204 google-gadgets-common
8222 libggadget-qt-
1.0-
0b
8227 libkonqsidebarplugin4a
8236 libplasma-geolocation-interface4
8238 libplasmagenericshell4
8252 libsmokeknewstuff2-
3
8253 libsmokeknewstuff3-
3
8255 libsmokektexteditor3
8263 libsmokeqtnetwork4-
3
8269 libsmokeqtuitools4-
3
8281 plasma-dataengines-addons
8282 plasma-scriptengine-superkaramba
8283 plasma-widget-lancelot
8284 plasma-widgets-addons
8285 plasma-widgets-workspace
8289 update-notifier-common
8290 </p
></blockquote
>
8292 <p
>Running apt-get autoremove made the results using apt-get and
8293 aptitude a bit more similar, but there are still quite a lott of
8294 differences. I have no idea what packages should be installed after
8295 the upgrade, but hope those that do can have a look.
</p
>
8300 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8301 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8302 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8303 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8304 <description><p
>Most of the computers in use by the
8305 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8306 are virtual machines. And they have been Xen machines running on a
8307 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8308 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8309 bit harder that it could have been, because we set up the Xen virtual
8310 machines to get the virtual partitions from LVM, which as far as I
8311 know is not supported by KVM. So to migrate, we had to convert
8312 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8315 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8316 nice recipe
</a
> to do this, and wrote the following script to do the
8317 migration. It uses qemu-img from the qemu package to make the disk
8318 image, parted to partition it, losetup and kpartx to present the disk
8319 image partions as devices, and dd to copy the data. I NFS mounted the
8320 new servers storage area on the old server to do the migration.
</p
>
8326 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8331 if [ -z
"$
1" ] ; then
8332 echo
"Usage: $
0 &lt;hostname
&gt;
"
8338 if [ ! -e /dev/vg_data/$host-disk ] ; then
8339 echo
"error: unable to find LVM volume for $host
"
8343 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8344 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8345 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8346 totalsize=$(( ( $disksize + $swapsize ) ))
8349 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8350 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8352 parted $img mklabel msdos
8353 parted $img mkpart primary linux-swap
0 $disksize
8354 parted $img mkpart primary ext2 $disksize $totalsize
8355 parted $img set
1 boot on
8358 losetup /dev/loop0 $img
8359 kpartx -a /dev/loop0
8361 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8362 fsck.ext3 -f /dev/mapper/loop0p1 || true
8363 mkswap /dev/mapper/loop0p2
8365 kpartx -d /dev/loop0
8366 losetup -d /dev/loop0
8369 <p
>The script is perhaps so simple that it is not copyrightable, but
8370 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8372 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8373 the new disk image attached, installed grub-pc and linux-image-
686 and
8374 set up grub to boot from the disk image. After this, the KVM machines
8375 seem to work just fine.
</p
>
8380 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8381 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8382 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8383 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8384 <description><p
>I
'm still running upgrade testing of the
8385 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8386 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8387 status. Here is a short update based on a test I ran
20101118.
</p
>
8389 <p
>I still do not know what a correct migration should look like, so I
8390 report any differences between apt and aptitude and hope someone else
8391 can see if anything should be changed.
</p
>
8393 <p
>This is for Gnome:
</p
>
8395 <p
>Installed using apt-get, missing with aptitude
</p
>
8397 <blockquote
><p
>
8398 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8399 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8400 dmz-cursor-theme empathy empathy-common finger
8401 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8402 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8403 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8404 gnome-cards-data gnome-codec-install gnome-core
8405 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8406 gnome-search-tool gnome-session-canberra gnome-spell
8407 gnome-system-log gnome-themes-extras gnome-themes-more
8408 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8409 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8410 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8411 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8412 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8413 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8414 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8415 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8416 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8417 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8418 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8419 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8420 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8421 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8422 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8423 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8424 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8425 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8426 libmono-security2.0-cil libmono-sharpzip2.84-cil
8427 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8428 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8429 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8430 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8431 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8432 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8433 libxalan2-java libxerces2-java media-player-info mesa-utils
8434 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8435 nautilus-sendto-empathy openoffice.org-writer2latex
8436 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8437 python-aptdaemon python-aptdaemon-gtk python-axiom
8438 python-beautifulsoup python-bugbuddy python-clientform
8439 python-coherence python-configobj python-crypto python-cupshelpers
8440 python-cupsutils python-eggtrayicon python-elementtree
8441 python-epsilon python-evolution python-feedparser python-gdata
8442 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8443 python-gtksourceview2 python-httplib2 python-louie python-mako
8444 python-markupsafe python-mechanize python-nevow python-notify
8445 python-opengl python-openssl python-pam python-pkg-resources
8446 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8447 python-tagpy python-twisted-bin python-twisted-conch
8448 python-twisted-core python-twisted-web python-utidylib python-webkit
8449 python-xdg python-zope.interface remmina remmina-plugin-data
8450 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8451 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8452 software-center svgalibg1 system-config-printer-udev
8453 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8454 totem totem-coherence totem-mozilla totem-plugins
8455 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8457 </p
></blockquote
>
8459 Installed using apt-get, removed with aptitude
8461 <blockquote
><p
>
8462 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8463 epiphany-extensions epiphany-gecko evolution-exchange
8464 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8465 gedit-common gnome-app-install gnome-games gnome-games-data
8466 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8467 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8468 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8469 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8470 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8471 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8472 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8473 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8474 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8475 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8476 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8477 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8478 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8479 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8480 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8481 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8482 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8483 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8484 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8485 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8486 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8487 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8488 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8489 sound-juicer swfdec-gnome system-config-printer totem-common
8490 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8491 </p
></blockquote
>
8493 <p
>Installed using aptitude, missing with apt-get
</p
>
8495 <blockquote
><p
>
8496 gstreamer0.10-gnomevfs
8497 </p
></blockquote
>
8499 <p
>Installed using aptitude, removed with apt-get
</p
>
8501 <blockquote
><p
>
8503 </p
></blockquote
>
8505 <p
>This is for KDE:
</p
>
8507 <p
>Installed using apt-get, missing with aptitude
</p
>
8509 <blockquote
><p
>
8510 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8511 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8512 ghostscript-x git gnome-audio gnugo granatier gs-common
8513 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8514 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8515 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8516 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8517 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8518 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8519 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8520 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8521 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8522 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8523 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8524 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8525 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8526 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8527 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8528 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8529 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8530 libkrossui4 libmailtools-perl libmime-tools-perl
8531 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8532 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8533 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8534 lirc luatex marble networkstatus noatun-plugins
8535 openoffice.org-writer2latex palapeli palapeli-data parley
8536 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8537 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8538 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8540 </p
></blockquote
>
8542 <p
>Installed using apt-get, removed with aptitude
</p
>
8544 <blockquote
><p
>
8545 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8546 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8547 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8548 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8549 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8550 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8551 kitchensync kiten kjumpingcube klatin klettres klickety klines
8552 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8553 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8554 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8555 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8556 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8557 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8558 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8559 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8560 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8561 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8562 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8563 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8564 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8565 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8566 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8567 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8568 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8569 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8570 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8571 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8572 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8573 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8574 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8575 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8576 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8577 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8578 </p
></blockquote
>
8580 <p
>Installed using aptitude, missing with apt-get
</p
>
8582 <blockquote
><p
>
8583 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8584 kdeartwork kdebase kdebase-apps kdebase-workspace
8585 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8586 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8587 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8588 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8589 xscreensaver-screensaver-bsod
8590 </p
></blockquote
>
8592 <p
>Installed using aptitude, removed with apt-get
</p
>
8594 <blockquote
><p
>
8595 kdebase-bin konq-plugins konqueror
8596 </p
></blockquote
>
8601 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8602 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8603 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8604 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8605 <description><p
>Answering
8606 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8607 call from the Gnash project
</a
> for
8608 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8609 current source, I have set up a virtual KVM machine on the Debian
8610 Edu/Skolelinux virtualization host to test the git source on
8611 Debian/Squeeze. I hope this can help the developers in getting new
8612 releases out more often.
</p
>
8614 <p
>As the developers want less main-stream build platforms tested to,
8615 I have considered setting up a
<a
8616 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8617 machine as well. I have also considered using the kfreebsd
8618 architecture in Debian as a file server in NUUG to get access to the
5
8619 TB zfs volume we currently use to store DV video. Because of this, I
8620 finally got around to do a test installation of Debian/Squeeze with
8621 kfreebsd. Installation went fairly smooth, thought I noticed some
8622 visual glitches in the cdebconf dialogs (black cursor left on the
8623 screen at random locations). Have not gotten very far with the
8624 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8625 fatal problem. Have to spend some more time on it to see if it is
8626 useful as a file server for NUUG. Will try to find time to set up a
8627 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8632 <title>Debian in
3D
</title>
8633 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8635 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8636 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8638 <p
>3D printing is just great. I just came across this Debian logo in
8640 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8641 thingiverse blog
</a
>.
</p
>
8646 <title>Software updates
2010-
10-
24</title>
8647 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8648 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8649 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8650 <description><p
>Some updates.
</p
>
8652 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8653 raise money for the project is going well. The lower limit of
10
8654 signers was reached in
24 hours, and so far
13 people have signed it.
8655 More signers and more funding is most welcome, and I am really curious
8656 how far we can get before the time limit of December
24 is reached.
8659 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8660 about what appear to be a great code coverage tool capable of
8661 generating code coverage stats without any changes to the source code.
8663 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8664 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8665 It is missing in Debian, but the git source built just fine in Squeeze
8666 after I installed libelf-dev, libdwarf-dev, pkg-config and
8667 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8668 solvable. I hope kcov make it into Debian soon.
</p
>
8670 <p
>Finally found time to wrap up the release notes for
<a
8671 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8672 new alpha release of Debian Edu
</a
>, and just published the second
8673 alpha test release of the Squeeze based Debian Edu /
8674 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8675 release. Give it a try if you need a complete linux solution for your
8676 school, including central infrastructure server, workstations, thin
8677 client servers and diskless workstations. A nice touch added
8678 yesterday is RDP support on the thin client servers, for windows
8679 clients to get a Linux desktop on request.
</p
>
8684 <title>Some notes on Flash in Debian and Debian Edu
</title>
8685 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8686 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8687 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8688 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8689 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8690 second most popular used package that is missing in Debian. The sixth
8691 most popular is flashplayer-mozilla. This is a clear indication that
8692 working flash is important for Debian users. Around
10 percent of the
8693 users submitting data to popcon.debian.org have this package
8694 installed.
</p
>
8696 <p
>In the report written by Lars Risan in August
2008
8697 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8698 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8699 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8700 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8701 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8702 web sites require Flash to work, and lacking working Flash support in
8703 the web browser and the problems with installing it was perceived as a
8704 good reason to stay with Windows.
</p
>
8706 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8707 said to be the retarded cousin that did not really understand
8708 everything you told him but could work fairly well. This was a
8709 comment regarding the problems Linux have with proprietary formats and
8710 non-standard web pages, and is sad because it exposes a fairly common
8711 understanding of whose fault it is if web pages that only work in for
8712 example Internet Explorer
6 fail to work on Firefox, and funny because
8713 it explain very well how annoying it is for users when Linux
8714 distributions do not work with the documents they receive or the web
8715 pages they want to visit.
</p
>
8717 <p
>This is part of the reason why I believe it is important for Debian
8718 and Debian Edu to have a well working Flash implementation in the
8719 distribution, to get at least popular sites as Youtube and Google
8720 Video to working out of the box. For Squeeze, Debian have the chance
8721 to include the latest version of Gnash that will make this happen, as
8722 the new release
0.8.8 was published a few weeks ago and is resting in
8723 unstable. The new version work with more sites that version
0.8.7.
8724 The Gnash maintainers have asked for a freeze exception, but the
8725 release team have not had time to reply to it yet. I hope they agree
8726 with me that Flash is important for the Debian desktop users, and thus
8727 accept the new package into Squeeze.
</p
>
8732 <title>Circular package dependencies harms apt recovery
</title>
8733 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8734 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8735 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8736 <description><p
>I discovered this while doing
8737 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8738 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8739 in Debian still got circular dependencies, and it is often claimed
8740 that apt and aptitude should be able to handle this just fine, but
8741 some times these dependency loops causes apt to fail.
</p
>
8743 <p
>An example is from todays
8744 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8745 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8746 causes perl-modules to fail to upgrade. The cause is simple. If a
8747 package fail to unpack, then only part of packages with the circular
8748 dependency might end up being unpacked when unpacking aborts, and the
8749 ones already unpacked will fail to configure in the recovery phase
8750 because its dependencies are unavailable.
</p
>
8752 <p
>In this log, the problem manifest itself with this error:
</p
>
8754 <blockquote
><pre
>
8755 dpkg: dependency problems prevent configuration of perl-modules:
8756 perl-modules depends on perl (
>=
5.10.1-
1); however:
8757 Version of perl on system is
5.10.0-
19lenny
2.
8758 dpkg: error processing perl-modules (--configure):
8759 dependency problems - leaving unconfigured
8760 </pre
></blockquote
>
8762 <p
>The perl/perl-modules circular dependency is already
8763 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8764 hopefully be solved as soon as possible, but it is not the only one,
8765 and each one of these loops in the dependency tree can cause similar
8766 failures. Of course, they only occur when there are bugs in other
8767 packages causing the unpacking to fail, but it is rather nasty when
8768 the failure of one package causes the problem to become worse because
8769 of dependency loops.
</p
>
8772 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8773 tireless effort by Bill Allombert
</a
>, the number of circular
8775 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8776 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8778 <p
>Todays testing also exposed a bug in
8779 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8780 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8781 apt-get and aptitude, the latter possibly caused by some circular
8782 dependency. Reported both to BTS to try to get someone to look at
8788 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8789 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8790 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8791 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8792 <description><p
>This is a
8793 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8795 <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
8797 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8798 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8800 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8801 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8802 and dhcp3-server-ldap in Debian use the LDAP server. The two
8803 implementations are quite different in how they use LDAP.
</p
>
8805 To get this information, I started slapd with debugging enabled and
8806 dumped the debug output to a file to get the LDAP searches performed
8807 on a Debian Edu main-server. Here is a summary.
8809 <p
><strong
>powerdns
</strong
></p
>
8811 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8812 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8815 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8816 One
"strict
" mode where the forward and reverse DNS lookups are done
8817 using the same LDAP objects, and a
"tree
" mode where the forward and
8818 reverse entries are in two different subtrees in LDAP with a structure
8819 based on the DNS names, as in tjener.intern and
8820 2.2.0.10.in-addr.arpa.
</p
>
8822 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8823 base, and uses a
"base
" scoped search for the DNS name by adding
8824 "dc=tjener,dc=intern,
" to the base with a filter for
8825 "(associateddomain=tjener.intern)
" for the forward entry and
8826 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8827 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8828 forward entries, it is looking for attributes named dnsttl, arecord,
8829 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8830 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8831 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8832 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8833 spfrecord and modifytimestamp. For reverse entries it is looking for
8834 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8835 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8836 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8837 ldapsearch commands could look like this:
</p
>
8839 <blockquote
><pre
>
8840 ldapsearch -h ldap \
8841 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8842 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8843 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8844 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8845 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8846 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8848 ldapsearch -h ldap \
8849 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8850 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8851 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8852 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8853 srvrecord naptrrecord modifytimestamp
8854 </pre
></blockquote
>
8856 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8857 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8858 example LDAP objects used there. In addition to these objects, the
8859 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8860 also exist.
</p
>
8862 <blockquote
><pre
>
8863 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8865 objectclass: dnsdomain
8866 objectclass: domainrelatedobject
8869 associateddomain: tjener.intern
8871 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8873 objectclass: dnsdomain2
8874 objectclass: domainrelatedobject
8876 ptrrecord: tjener.intern
8877 associateddomain:
2.2.0.10.in-addr.arpa
8878 </pre
></blockquote
>
8880 <p
>In strict mode, the server behaves differently. When looking for
8881 forward DNS entries, it is doing a
"subtree
" scoped search with the
8882 same base as in the tree mode for a object with filter
8883 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8884 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8885 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8886 naptrrecord and modifytimestamp. For reverse entires it also do a
8887 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8888 and the requested attributes are associateddomain, dnsttl and
8889 modifytimestamp. In short, in strict mode the objects with ptrrecord
8890 go away, and the arecord attribute in the forward object is used
8893 <p
>The forward and reverse searches can be simulated using ldapsearch
8894 like this:
</p
>
8896 <blockquote
><pre
>
8897 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8898 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8899 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8900 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8901 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8902 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8904 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8905 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8906 </pre
></blockquote
>
8908 <p
>In addition to the forward and reverse searches , there is also a
8909 search for SOA records, which behave similar to the forward and
8910 reverse lookups.
</p
>
8912 <p
>A thing to note with the PowerDNS behaviour is that it do not
8913 specify any objectclass names, and instead look for the attributes it
8914 need to generate a DNS reply. This make it able to work with any
8915 objectclass that provide the needed attributes.
</p
>
8917 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8918 dnsdomain2 schemas. The latter is used for reverse entries like
8919 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8921 <p
>In Debian Edu, we have created DNS objects using the object classes
8922 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8923 attributes) and domainrelatedobject (for associatedDomain). The use
8924 of structural object classes make it impossible to combine these
8925 classes with the object classes used by DHCP.
</p
>
8927 <p
>There are other schemas that could be used too, for example the
8928 dnszone structural object class used by Gosa and bind-sdb for the DNS
8929 attributes combined with the domainrelatedobject object class, but in
8930 this case some unused attributes would have to be included as well
8931 (zonename and relativedomainname).
</p
>
8933 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8934 mode and not use any of the existing objectclasses (dnsdomain,
8935 dnsdomain2 and dnszone) when one want to combine the DNS information
8936 with DHCP information, and instead create a auxiliary object class
8937 defined something like this (using the attributes defined for
8938 dnsdomain and dnsdomain2 or dnszone):
</p
>
8940 <blockquote
><pre
>
8941 objectclass ( some-oid NAME
'dnsDomainAux
'
8944 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8945 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8946 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8947 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8948 A6Record $ DNAMERecord
8950 </pre
></blockquote
>
8952 <p
>This will allow any object to become a DNS entry when combined with
8953 the domainrelatedobject object class, and allow any entity to include
8954 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8955 developers asking for their view on this schema and if they are
8956 interested in providing such schema with PowerDNS, and I hope my
8957 message will be accepted into their mailing list soon.
</p
>
8959 <p
><strong
>ISC dhcp
</strong
></p
>
8961 <p
>The DHCP server searches for specific objectclass and requests all
8962 the object attributes, and then uses the attributes it want. This
8963 make it harder to figure out exactly what attributes are used, but
8964 thanks to the working example in Debian Edu I can at least get an idea
8965 what is needed without having to read the source code.
</p
>
8967 <p
>In the DHCP server configuration, the LDAP base to use and the
8968 search filter to use to locate the correct dhcpServer entity is
8969 stored. These are the relevant entries from
8970 /etc/dhcp3/dhcpd.conf:
</p
>
8972 <blockquote
><pre
>
8973 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8974 ldap-dhcp-server-cn
"dhcp
";
8975 </pre
></blockquote
>
8977 <p
>The DHCP server uses this information to nest all the DHCP
8978 configuration it need. The cn
"dhcp
" is located using the given LDAP
8979 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8980 search result is this entry:
</p
>
8982 <blockquote
><pre
>
8983 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8986 objectClass: dhcpServer
8987 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8988 </pre
></blockquote
>
8990 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8991 subtree with DHCP configuration. The DHCP configuration subtree base
8992 is located using a base scope search with base
"cn=DHCP
8993 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8994 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8995 The search result is this entry:
</p
>
8997 <blockquote
><pre
>
8998 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9001 objectClass: dhcpService
9002 objectClass: dhcpOptions
9003 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9004 dhcpStatements: ddns-update-style none
9005 dhcpStatements: authoritative
9006 dhcpOption: smtp-server code
69 = array of ip-address
9007 dhcpOption: www-server code
72 = array of ip-address
9008 dhcpOption: wpad-url code
252 = text
9009 </pre
></blockquote
>
9011 <p
>Next, the entire subtree is processed, one level at the time. When
9012 all the DHCP configuration is loaded, it is ready to receive requests.
9013 The subtree in Debian Edu contain objects with object classes
9014 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9015 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9016 and information about netmasks, dynamic range etc. Leaving out the
9017 details here because it is not relevant for the focus of my
9018 investigation, which is to see if it is possible to merge dns and dhcp
9019 related computer objects.
</p
>
9021 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9022 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9023 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9024 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9025 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9028 <blockquote
><pre
>
9029 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9032 objectClass: dhcpHost
9033 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9034 dhcpStatements: fixed-address hostname
9035 </pre
></blockquote
>
9037 <p
>There is less flexiblity in the way LDAP searches are done here.
9038 The object classes need to have fixed names, and the configuration
9039 need to be stored in a fairly specific LDAP structure. On the
9040 positive side, the invidiual dhcpHost entires can be anywhere without
9041 the DN pointed to by the dhcpServer entries. The latter should make
9042 it possible to group all host entries in a subtree next to the
9043 configuration entries, and this subtree can also be shared with the
9044 DNS server if the schema proposed above is combined with the dhcpHost
9045 structural object class.
9047 <p
><strong
>Conclusion
</strong
></p
>
9049 <p
>The PowerDNS implementation seem to be very flexible when it come
9050 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9051 come to the the LDAP structure, the
"strict
" mode is very flexible,
9052 allowing DNS objects to be stored anywhere under the base cn specified
9053 in the configuration.
</p
>
9055 <p
>The DHCP implementation on the other hand is very inflexible, both
9056 regarding which LDAP schemas to use and which LDAP structure to use.
9057 I guess one could implement ones own schema, as long as the
9058 objectclasses and attributes have the names used, but this do not
9059 really help when the DHCP subtree need to have a fairly fixed
9060 structure.
</p
>
9062 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9063 this might work for Debian Edu:
</p
>
9065 <blockquote
><pre
>
9067 cn=machine-info (dhcpService) - dhcpServiceDN points here
9068 cn=dhcp (dhcpServer)
9069 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9070 cn=
10.0.2.0 (dhcpSubnet)
9071 cn=group1 (dhcpGroup/dhcpOptions)
9072 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9073 cn=
192.168.0.0 (dhcpSubnet)
9074 cn=group1 (dhcpGroup/dhcpOptions)
9075 ou=machines - PowerDNS base points here
9076 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9077 </pre
></blockquote
>
9079 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9080 entries to be in the dhcpGroup subtrees, the entries can be stored
9081 there instead of a common machines subtree, and the PowerDNS base
9082 would have to be moved one level up to the machine-info subtree.
</p
>
9084 <p
>The combined object under the machines subtree would look something
9085 like this:
</p
>
9087 <blockquote
><pre
>
9088 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9091 objectClass: dhcpHost
9092 objectclass: domainrelatedobject
9093 objectclass: dnsDomainAux
9094 associateddomain: hostname.intern
9095 arecord:
10.11.12.13
9096 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9097 dhcpStatements: fixed-address hostname.intern
9098 </pre
></blockquote
>
9100 </p
>One could even add the LTSP configuration associated with a given
9101 machine, as long as the required attributes are available in a
9102 auxiliary object class.
</p
>
9107 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9108 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9109 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9110 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9111 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9112 DHCP services in Debian Edu to use the same LDAP objects for a given
9113 computer, to avoid the possibility of having a inconsistent state for
9114 a computer in LDAP (as in DHCP but no DNS entry or the other way
9115 around) and make it easier to add computers to LDAP.
</p
>
9117 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9118 information finally found a solution that seem to work.
</p
>
9120 <p
>The old setup required three LDAP objects for a given computer.
9121 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9122 we switch powerdns to use its strict LDAP method (ldap-method=strict
9123 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9124 merged into one while making it impossible to transfer the reverse map
9125 to a slave DNS server.
</p
>
9127 <p
>If we also replace the object class used to get the DNS related
9128 attributes to one allowing these attributes to be combined with the
9129 dhcphost object class, we can merge the DNS and DHCP entries into one.
9130 I
've written such object class in the dnsdomainaux.schema file (need
9131 proper OIDs, but that is a minor issue), and tested the setup. It
9132 seem to work.
</p
>
9134 <p
>With this test setup in place, we can get away with one LDAP object
9135 for both DNS and DHCP, and even the LTSP configuration I suggested in
9136 an earlier email. The combined LDAP object will look something like
9139 <blockquote
><pre
>
9140 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9142 objectClass: dhcphost
9143 objectclass: domainrelatedobject
9144 objectclass: dnsdomainaux
9145 associateddomain: hostname.intern
9146 arecord:
10.11.12.13
9147 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9148 dhcpstatements: fixed-address hostname
9150 </pre
></blockquote
>
9152 <p
>The DNS server uses the associateddomain and arecord entries, while
9153 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9154 before asking DNS to resolve the fixed-adddress. LTSP will use
9155 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9157 <p
>I am not yet sure if I can get the DHCP server to look for its
9158 dhcphost in a different location, to allow us to put the objects
9159 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9160 that. If I can
't figure out a way to do that, we can still get rid of
9161 the hosts subtree and move all its content into the DHCP Config tree
9162 (which probably should be renamed to be more related to the new
9163 content. I suspect cn=dnsdhcp,ou=services or something like that
9164 might be a good place to put it.
</p
>
9166 <p
>If you want to help out with implementing this for Debian Edu,
9167 please contact us on debian-edu@lists.debian.org.
</p
>
9172 <title>Idea for storing LTSP configuration in LDAP
</title>
9173 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9174 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9175 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9176 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9177 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9178 clients, and that this can be used to fetch configuration from LDAP if
9179 Debian Edu choose to store configuration there.
</p
>
9181 <p
>Armed with this information, I got inspired and wrote a test module
9182 to get configuration from LDAP. The idea is to look up the MAC
9183 address of the client in LDAP, and look for attributes on the form
9184 ltspconfigsetting=value, and use this to export SETTING=value to the
9185 LTSP clients.
</p
>
9187 <p
>The goal is to be able to store the LTSP configuration attributes
9188 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9189 allowing us to store all information about a computer in one place.
</p
>
9191 <p
>This is a untested draft implementation, and I welcome feedback on
9192 this approach. A real LDAP schema for the ltspClientAux objectclass
9193 need to be written. Comments, suggestions, etc?
</p
>
9195 <blockquote
><pre
>
9196 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9198 # Fetch LTSP client settings from LDAP based on MAC address
9200 # Uses ethernet address as stored in the dhcpHost objectclass using
9201 # the dhcpHWAddress attribute or ethernet address stored in the
9202 # ieee802Device objectclass with the macAddress attribute.
9204 # This module is written to be schema agnostic, and only depend on the
9205 # existence of attribute names.
9207 # The LTSP configuration variables are saved directly using a
9208 # ltspConfig prefix and uppercasing the rest of the attribute name.
9209 # To set the SERVER variable, set the ltspConfigServer attribute.
9211 # Some LDAP schema should be created with all the relevant
9212 # configuration settings. Something like this should work:
9214 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9217 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9219 LDAPSERVER=$(debian-edu-ldapserver)
9220 if [
"$LDAPSERVER
" ] ; then
9221 LDAPBASE=$(debian-edu-ldapserver -b)
9222 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9223 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9224 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9225 grep
'^ltspConfig
' | while read attr value ; do
9226 # Remove prefix and convert to upper case
9227 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9228 # bass value on to clients
9229 eval
"$attr=$value; export $attr
"
9233 </pre
></blockquote
>
9235 <p
>I
'm not sure this shell construction will work, because I suspect
9236 the while block might end up in a subshell causing the variables set
9237 there to not show up in ltsp-config, but if that is the case I am sure
9238 the code can be restructured to make sure the variables are passed on.
9239 I expect that can be solved with some testing. :)
</p
>
9241 <p
>If you want to help out with implementing this for Debian Edu,
9242 please contact us on debian-edu@lists.debian.org.
</p
>
9244 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9245 configuration in LDAP that was created around year
2000 by
9246 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9247 Xperience, Inc.,
2000</a
>. I found its
9248 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9249 personal home page over at redhat.com.
</p
>
9254 <title>jXplorer, a very nice LDAP GUI
</title>
9255 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9256 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9257 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9258 <description><p
>Since
9259 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9260 last post
</a
> about available LDAP tools in Debian, I was told about a
9261 LDAP GUI that is even better than luma. The java application
9262 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9263 moving LDAP objects and subtrees using drag-and-drop, and can
9264 authenticate using Kerberos. I have only tested the Kerberos
9265 authentication, but do not have a LDAP setup allowing me to rewrite
9266 LDAP with my test user yet. It is
9267 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9268 Debian
</a
> testing and unstable at the moment. The only problem I
9269 have with it is how it handle errors. If something go wrong, its
9270 non-intuitive behaviour require me to go through some query work list
9271 and remove the failing query. Nothing big, but very annoying.
</p
>
9276 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9277 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9278 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9279 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9280 <description><p
>Here is a short update on my
<a
9281 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9282 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9283 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9284 not reporting the status for KDE, because the upgrade crashes when
9285 aptitude try because of missing conflicts
9286 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9287 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9289 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9290 complete list of the installed packages. Based on this I see these
9291 differences when I did a test run today. As usual, I do not really
9292 know what the correct set of packages would be, but thought it best to
9293 publish the difference.
</p
>
9295 <p
>Installed using apt-get, missing with aptitude
</p
>
9297 <blockquote
><p
>
9298 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9299 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9300 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9301 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9302 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9303 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9304 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9305 python-gtkmozembed svgalibg1 xserver-xephyr zip
9306 </p
></blockquote
>
9308 <p
>Installed using apt-get, removed with aptitude
</p
>
9310 <blockquote
><p
>
9311 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9312 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9313 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9314 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9315 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9316 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9317 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9318 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9319 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9320 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9321 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9322 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9323 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9324 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9325 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9326 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9327 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9328 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9329 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9330 mysql-common swfdec-gnome totem-gstreamer wodim
9331 </p
></blockquote
>
9333 <p
>Installed using aptitude, missing with apt-get
</p
>
9335 <blockquote
><p
>
9336 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9337 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9338 xserver-xorg-input-all xserver-xorg-input-evdev
9339 xserver-xorg-input-kbd xserver-xorg-input-mouse
9340 xserver-xorg-input-synaptics xserver-xorg-video-all
9341 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9342 xserver-xorg-video-chips xserver-xorg-video-cirrus
9343 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9344 xserver-xorg-video-glint xserver-xorg-video-i128
9345 xserver-xorg-video-i740 xserver-xorg-video-mach64
9346 xserver-xorg-video-mga xserver-xorg-video-neomagic
9347 xserver-xorg-video-nouveau xserver-xorg-video-nv
9348 xserver-xorg-video-r128 xserver-xorg-video-radeon
9349 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9350 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9351 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9352 xserver-xorg-video-sis xserver-xorg-video-sisusb
9353 xserver-xorg-video-tdfx xserver-xorg-video-tga
9354 xserver-xorg-video-trident xserver-xorg-video-tseng
9355 xserver-xorg-video-vesa xserver-xorg-video-vmware
9356 xserver-xorg-video-voodoo
9357 </p
></blockquote
>
9359 <p
>Installed using aptitude, removed with apt-get
</p
>
9361 <blockquote
><p
>
9362 deskbar-applet xserver-xorg xserver-xorg-core
9363 xserver-xorg-input-wacom xserver-xorg-video-intel
9364 xserver-xorg-video-openchrome
9365 </p
></blockquote
>
9367 <p
>I was told on IRC that the xorg-xserver package was
9368 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9369 in git
</a
> today to try to get apt-get to not remove xorg completely.
9370 No idea when it hits Squeeze, but when it does I hope it will reduce
9371 the difference somewhat.
9376 <title>LUMA, a very nice LDAP GUI
</title>
9377 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9378 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9379 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9380 <description><p
>The last few days I have been looking into the status of the LDAP
9381 directory in Debian Edu, and in the process I started to miss a GUI
9382 tool to browse the LDAP tree. The only one I was able to find in
9383 Debian/Squeeze and Lenny is
9384 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9385 be a great tool to get a overview of the current LDAP directory
9386 populated by default in Skolelinux. Thanks to it, I have been able to
9387 find empty and obsolete subtrees, misplaced objects and duplicate
9388 objects. It will be installed by default in Debian/Squeeze. If you
9389 are working with LDAP, give it a go. :)
</p
>
9391 <p
>I did notice one problem with it I have not had time to report to
9392 the BTS yet. There is no .desktop file in the package, so the tool do
9393 not show up in the Gnome and KDE menus, but only deep down in in the
9394 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9397 <p
>I have not yet been able to get it to modify the tree yet. I would
9398 like to move objects and remove subtrees directly in the GUI, but have
9399 not found a way to do that with LUMA yet. So in the mean time, I use
9400 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9402 <p
>If you have tips on other GUI tools for LDAP that might be useful
9403 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9405 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9406 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9407 useful GUI alternative. It seem like a good tool, but is unmaintained
9408 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9409 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9414 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9415 <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>
9416 <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>
9417 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9418 <description><p
>A while back, I
9419 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9420 about the fact
</a
> that it is not possible with the provided schemas
9421 for storing DNS and DHCP information in LDAP to combine the two sets
9422 of information into one LDAP object representing a computer.
</p
>
9424 <p
>In the mean time, I discovered that a simple fix would be to make
9425 the dhcpHost object class auxiliary, to allow it to be combined with
9426 the dNSDomain object class, and thus forming one object for one
9427 computer when storing both DHCP and DNS information in LDAP.
</p
>
9429 <p
>If I understand this correctly, it is not safe to do this change
9430 without also changing the assigned number for the object class, and I
9431 do not know enough about LDAP schema design to do that properly for
9432 Debian Edu.
</p
>
9434 <p
>Anyway, for future reference, this is how I believe we could change
9436 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9437 schema
</a
> to solve at least part of the problem with the LDAP schemas
9438 available today from IETF.
</p
>
9441 --- dhcp.schema (revision
65192)
9442 +++ dhcp.schema (working copy)
9444 objectclass (
2.16.840.1.113719.1.203.6.6
9445 NAME
'dhcpHost
'
9446 DESC
'This represents information about a particular client
'
9450 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9451 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9454 <p
>I very much welcome clues on how to do this properly for Debian
9455 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9456 package, and should thus be free to rewrite it as we see fit.
</p
>
9458 <p
>If you want to help out with implementing this for Debian Edu,
9459 please contact us on debian-edu@lists.debian.org.
</p
>
9464 <title>Calling tasksel like the installer, while still getting useful output
</title>
9465 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9466 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9467 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9468 <description><p
>A few times I have had the need to simulate the way tasksel
9469 installs packages during the normal debian-installer run. Until now,
9470 I have ended up letting tasksel do the work, with the annoying problem
9471 of not getting any feedback at all when something fails (like a
9472 conffile question from dpkg or a download that fails), using code like
9475 <blockquote
><pre
>
9476 export DEBIAN_FRONTEND=noninteractive
9477 tasksel --new-install
9478 </pre
></blockquote
>
9480 This would invoke tasksel, let its automatic task selection pick the
9481 tasks to install, and continue to install the requested tasks without
9482 any output what so ever.
9484 Recently I revisited this problem while working on the automatic
9485 package upgrade testing, because tasksel would some times hang without
9486 any useful feedback, and I want to see what is going on when it
9487 happen. Then it occured to me, I can parse the output from tasksel
9488 when asked to run in test mode, and use that aptitude command line
9489 printed by tasksel then to simulate the tasksel run. I ended up using
9492 <blockquote
><pre
>
9493 export DEBIAN_FRONTEND=noninteractive
9494 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9496 </pre
></blockquote
>
9498 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9499 --without-recommends -o APT::Install-Recommends=no -y install
9500 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9501 ~pimportant
</tt
>", which will install the gnome desktop task, the
9502 laptop task and all packages with priority standard , required and
9503 important, just like tasksel would have done it during
9504 installation.
</p
>
9506 <p
>A better approach is probably to extend tasksel to be able to
9507 install packages without using debconf-apt-progress, for use cases
9508 like this.
</p
>
9513 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9514 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9515 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9516 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9517 <description><p
>My
9518 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9519 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9520 finally made the upgrade logs available from
9521 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9522 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9523 apt and aptitude, and found their differences interesting. This time
9524 I will only focus on their removal plans.
</p
>
9526 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9527 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9528 surprising part is that it want to remove xorg and all
9529 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9530 sure why. When asking aptitude to do the same, it want to remove
129
9531 packages, but most of them are library packages I suspect are no
9532 longer needed. Both of them want to remove bluetooth packages, which
9533 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9535 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9536 which seem like a bad idea and xorg the same way as with Gnome. Asking
9537 aptitude for the same, it wants to remove
192 packages, none which are
9538 too surprising.
</p
>
9540 <p
>I guess the removal of xorg during upgrades should be investigated
9541 and avoided, and perhaps others as well. Here are the complete list
9542 of planned removals. The complete logs is available from the URL
9543 above. Note if you want to repeat these tests, that the upgrade test
9544 for kde+apt-get hung in the tasksel setup because of dpkg asking
9545 conffile questions. No idea why. I worked around it by using
9546 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9549 <p
><b
>apt-get gnome
72</b
>
9550 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9551 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9552 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9553 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9554 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9555 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9556 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9557 xserver-xorg-input-kbd xserver-xorg-input-mouse
9558 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9559 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9560 xserver-xorg-video-ati xserver-xorg-video-chips
9561 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9562 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9563 xserver-xorg-video-glint xserver-xorg-video-i128
9564 xserver-xorg-video-i740 xserver-xorg-video-imstt
9565 xserver-xorg-video-intel xserver-xorg-video-mach64
9566 xserver-xorg-video-mga xserver-xorg-video-neomagic
9567 xserver-xorg-video-nsc xserver-xorg-video-nv
9568 xserver-xorg-video-openchrome xserver-xorg-video-r128
9569 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9570 xserver-xorg-video-rendition xserver-xorg-video-s3
9571 xserver-xorg-video-s3virge xserver-xorg-video-savage
9572 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9573 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9574 xserver-xorg-video-tga xserver-xorg-video-trident
9575 xserver-xorg-video-tseng xserver-xorg-video-v4l
9576 xserver-xorg-video-vesa xserver-xorg-video-vga
9577 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9578 xulrunner-
1.9-gnome-support
</p
>
9580 <p
><b
>aptitude gnome
129</b
>
9582 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9583 djvulibre-desktop finger gnome-app-install gnome-mount
9584 gnome-network-admin gnome-spell gnome-vfs-obexftp
9585 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9586 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9587 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9588 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9589 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9590 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9591 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9592 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9593 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9594 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9595 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9596 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9597 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9598 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9599 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9600 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9601 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9602 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9603 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9604 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9605 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9606 openoffice.org-writer2latex openssl-blacklist p7zip
9607 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9608 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9609 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9610 swfdec-mozilla totem-gstreamer update-manager wodim
9611 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9612 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9615 <p
><b
>apt-get kde
82</b
>
9617 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9618 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9619 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9620 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9621 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9622 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9623 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9624 xserver-xorg-input-kbd xserver-xorg-input-mouse
9625 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9626 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9627 xserver-xorg-video-ati xserver-xorg-video-chips
9628 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9629 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9630 xserver-xorg-video-glint xserver-xorg-video-i128
9631 xserver-xorg-video-i740 xserver-xorg-video-imstt
9632 xserver-xorg-video-intel xserver-xorg-video-mach64
9633 xserver-xorg-video-mga xserver-xorg-video-neomagic
9634 xserver-xorg-video-nsc xserver-xorg-video-nv
9635 xserver-xorg-video-openchrome xserver-xorg-video-r128
9636 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9637 xserver-xorg-video-rendition xserver-xorg-video-s3
9638 xserver-xorg-video-s3virge xserver-xorg-video-savage
9639 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9640 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9641 xserver-xorg-video-tga xserver-xorg-video-trident
9642 xserver-xorg-video-tseng xserver-xorg-video-v4l
9643 xserver-xorg-video-vesa xserver-xorg-video-vga
9644 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9646 <p
><b
>aptitude kde
192</b
>
9647 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9648 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9649 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9650 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9651 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9652 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9653 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9654 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9655 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9656 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9657 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9658 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9659 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9660 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9661 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9662 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9663 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9664 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9665 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9666 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9667 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9668 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9669 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9670 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9671 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9672 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9673 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9674 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9675 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9676 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9677 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9678 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9679 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9680 texlive-common texlive-doc-base texlive-fonts-recommended
9681 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9682 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9683 xulrunner-
1.9</p
>
9689 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9690 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9691 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9692 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9693 <description><p
>The last few days I have done some upgrade testing in Debian, to
9694 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9695 have been discovered and reported in the process
9696 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9697 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9698 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9699 kdebase-workspace-data), and to get a more regular testing going on, I
9700 am working on a script to automate the test.
</p
>
9702 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9703 Gnome or KDE desktop installation inside the chroot before upgrading
9704 it. To ensure no services are started in the chroot, a policy-rc.d
9705 script is inserted. To make sure tasksel believe it is to install a
9706 desktop on a laptop, the tasksel tests are replaced in the chroot
9707 (only acceptable because this is a throw-away chroot).
</p
>
9709 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9710 currently always fail because udev refuses to upgrade with the kernel
9711 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9712 is created. The bug report
9713 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9714 this problem do not trigger in a chroot, but I touch the file anyway
9715 to make sure the upgrade go well. Testing on virtual and real
9716 hardware have failed me because of udev so far, and creating this file
9717 do the trick in such settings anyway. This is a
9718 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9719 issue
</a
> and the current udev behaviour is intended by the udev
9720 maintainer because he lack the resources to rewrite udev to keep
9721 working with old kernels or something like that. I really wish the
9722 udev upstream would keep udev backwards compatible, to avoid such
9723 upgrade problem, but given that they fail to do so, I guess
9724 documenting the way out of this mess is the best option we got for
9725 Debian Squeeze.
</p
>
9727 <p
>Anyway, back to the task at hand, testing upgrades. This test
9728 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9731 <blockquote
><pre
>
9735 if [
"$
1" ] ; then
9744 exec
&lt; /dev/null
9746 mirror=http://ftp.skolelinux.org/debian
9747 tmpdir=chroot-$from-upgrade-$to-$desktop
9749 debootstrap $from $tmpdir $mirror
9750 chroot $tmpdir aptitude update
9751 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9755 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9759 mount -t proc proc $tmpdir/proc
9760 # Make sure proc is unmounted also on failure
9761 trap exit_cleanup EXIT INT
9763 chroot $tmpdir aptitude -y install debconf-utils
9765 # Make sure tasksel autoselection trigger. It need the test scripts
9766 # to return the correct answers.
9767 echo tasksel tasksel/desktop multiselect $desktop | \
9768 chroot $tmpdir debconf-set-selections
9770 # Include the desktop and laptop task
9771 for test in desktop laptop ; do
9772 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9776 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9779 DEBIAN_FRONTEND=noninteractive
9780 DEBIAN_PRIORITY=critical
9781 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9782 chroot $tmpdir tasksel --new-install
9784 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9785 chroot $tmpdir aptitude update
9786 touch $tmpdir/etc/udev/kernel-upgrade
9787 chroot $tmpdir aptitude -y dist-upgrade
9789 </pre
></blockquote
>
9791 <p
>I suspect it would be useful to test upgrades with both apt-get and
9792 with aptitude, but I have not had time to look at how they behave
9793 differently so far. I hope to get a cron job running to do the test
9794 regularly and post the result on the web. The Gnome upgrade currently
9795 work, while the KDE upgrade fail because of the bug in
9796 kdebase-workspace-data
</p
>
9798 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9799 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9800 post, so I will refrain from trying. I can report that for Gnome,
9801 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9802 remove and
1 not upgraded and
1024MB need to be downloaded while for
9803 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9804 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9806 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9807 is able to migrate to dependency based boot sequencing and parallel
9808 booting without a hitch. Was unsure if there were still bugs with
9809 packages failing to clean up their obsolete init.d script during
9810 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9816 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9817 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9818 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9819 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9820 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9821 scripts to migrate (some of) their operations to upstart job while
9822 keeping the init.d for hurd and kfreebsd. The packages with such
9823 needs will need a way to get their init.d scripts to behave
9824 differently when used with sysvinit and with upstart. Because of
9825 this, I had a look at the environment variables set when a init.d
9826 script is running under upstart, and when it is not.
</p
>
9828 <p
>With upstart, I notice these environment variables are set when a
9829 script is started from rcS.d/ (ignoring some irrelevant ones like
9832 <blockquote
><pre
>
9838 UPSTART_EVENTS=startup
9840 UPSTART_JOB=rc-sysinit
9841 </pre
></blockquote
>
9843 <p
>With sysvinit, these environment variables are set for the same
9846 <blockquote
><pre
>
9847 INIT_VERSION=sysvinit-
2.88
9852 </pre
></blockquote
>
9854 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9855 sysvinit are not set by upstart. Not sure if it is intentional or not
9856 to not be compatible with sysvinit in this regard.
</p
>
9858 <p
>For scripts needing to behave differently when upstart is used,
9859 looking for the UPSTART_JOB environment variable seem to be a good
9865 <title>A manual for standards wars...
</title>
9866 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9867 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9868 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9869 <description><p
>Via the
9870 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9871 of Rob Weir
</a
> I came across the very interesting essay named
9872 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9873 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9874 following the standards wars of today.
</p
>
9879 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9880 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9881 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9882 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9883 <description><p
>When using sitesummary at a site to track machines, it is possible
9884 to get a list of the machine types in use thanks to the DMI
9885 information extracted from each machine. The script to do so is
9886 included in the sitesummary package, and here is example output from
9887 the Skolelinux build servers:
</p
>
9889 <blockquote
><pre
>
9890 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9892 Dell Computer Corporation
1
9895 eserver xSeries
345 -[
8670M1X]-
1
9899 </pre
></blockquote
>
9901 <p
>The quality of the report depend on the quality of the DMI tables
9902 provided in each machine. Here there are Intel machines without model
9903 information listed with Intel as vendor and no model, and virtual Xen
9904 machines listed as [no-dmi-info]. One can add -l as a command line
9905 option to list the individual machines.
</p
>
9907 <p
>A larger list is
9908 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9909 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9910 provide the basic sitesummary report publicly. In their report there
9911 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9912 their machines, and as sitesummary is available in both distributions,
9913 it is trivial to get all of them to report to the same central
9914 collector.
</p
>
9919 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9920 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9921 <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>
9922 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9923 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9924 start at boot when an NVidia video card is used is handled. The
9925 problem seem to be that the nvidia X.org driver uses a long time to
9926 initialize, and this duration is longer than kdm is configured to
9929 <p
>I came across two bugs related to this issue,
9930 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9931 against initscripts and passed on to nvidia-glx when it became obvious
9932 that the nvidia drivers were involved, and
9933 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9934 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9936 <p
>To me, it seem that no-one is interested in actually solving the
9937 problem nvidia video card owners experience and make sure the Debian
9938 distribution work out of the box for these users. The nvidia driver
9939 maintainers expect kdm to be set up to wait longer, while kdm expect
9940 the nvidia driver maintainers to fix the driver to start faster, and
9941 while they wait for each other I guess the users end up switching to a
9942 distribution that work for them. I have no idea what the solution is,
9943 but I am pretty sure that waiting for each other is not it.
</p
>
9945 <p
>I wonder why we end up handling bugs this way.
</p
>
9950 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9951 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9952 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9953 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9954 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9955 The feature seem to hold up pretty well, but three fairly serious
9956 issues are known and should be solved:
9960 <li
>The wicd package seen to
9961 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9962 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9963 parallel booting is enabled. No idea why, but the wicd maintainer
9964 seem to be on the case.
</li
>
9966 <li
>The nvidia X driver seem to
9967 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9968 triggered more easily when parallel booting is in effect. The
9969 maintainer is on the case.
</li
>
9971 <li
>The sysv-rc package fail to properly enable dependency based boot
9972 sequencing (the shutdown is broken) when old file-rc users
9973 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9974 sysv-rc. One way to solve it would be for file-rc to create
9975 /etc/init.d/.legacy-bootordering, and another is to try to make
9976 sysv-rc more robust. Will investigate some more and probably upload a
9977 workaround in sysv-rc to help those trying to move from file-rc to
9978 sysv-rc get a working shutdown.
</li
>
9980 </ul
></p
>
9982 <p
>All in all not many surprising issues, and all of them seem
9983 solvable before Squeeze is released. In addition to these there are
9984 some packages with bugs in their dependencies and run level settings,
9985 which I expect will be fixed in a reasonable time span.
</p
>
9987 <p
>If you report any problems with dependencies in init.d scripts to
9988 the BTS, please usertag the report to get it to show up at
9989 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9990 list of usertagged bugs related to this
</a
>.
</p
>
9992 <p
>Update: Correct bug number to file-rc issue.
</p
>
9997 <title>More flexible firmware handling in debian-installer
</title>
9998 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9999 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10000 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10001 <description><p
>After a long break from debian-installer development, I finally
10002 found time today to return to the project. Having to spend less time
10003 working dependency based boot in debian, as it is almost complete now,
10004 definitely helped freeing some time.
</p
>
10006 <p
>A while back, I ran into a problem while working on Debian Edu. We
10007 include some firmware packages on the Debian Edu CDs, those needed to
10008 get disk and network controllers working. Without having these
10009 firmware packages available during installation, it is impossible to
10010 install Debian Edu on the given machine, and because our target group
10011 are non-technical people, asking them to provide firmware packages on
10012 an external medium is a support pain. Initially, I expected it to be
10013 enough to include the firmware packages on the CD to get
10014 debian-installer to find and use them. This proved to be wrong.
10015 Next, I hoped it was enough to symlink the relevant firmware packages
10016 to some useful location on the CD (tried /cdrom/ and
10017 /cdrom/firmware/). This also proved to not work, and at this point I
10018 found time to look at the debian-installer code to figure out what was
10019 going to work.
</p
>
10021 <p
>The firmware loading code is in the hw-detect package, and a closer
10022 look revealed that it would only look for firmware packages outside
10023 the installation media, so the CD was never checked for firmware
10024 packages. It would only check USB sticks, floppies and other
10025 "external
" media devices. Today I changed it to also look in the
10026 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10027 solve the problem I ran into with Debian edu. I also changed it to
10028 look in /firmware/, to make sure the installer also find firmware
10029 provided in the initrd when booting the installer via PXE, to allow us
10030 to provide the same feature in the PXE setup included in Debian
10033 <p
>To make sure firmware deb packages with a license questions are not
10034 activated without asking if the license is accepted, I extended
10035 hw-detect to look for preinst scripts in the firmware packages, and
10036 run these before activating the firmware during installation. The
10037 license question is asked using debconf in the preinst, so this should
10038 solve the issue for the firmware packages I have looked at so far.
</p
>
10040 <p
>If you want to discuss the details of these features, please
10041 contact us on debian-boot@lists.debian.org.
</p
>
10046 <title>Parallellized boot is now the default in Debian/unstable
</title>
10047 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10048 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10049 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10050 <description><p
>Since this evening, parallel booting is the default in
10051 Debian/unstable for machines using dependency based boot sequencing.
10052 Apparently the testing of concurrent booting has been wider than
10053 expected, if I am to believe the
10054 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10055 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10056 with the feature this weekend, to give us some time to detect any
10057 remaining problems before Squeeze is frozen. If serious problems are
10058 detected, it is simple to change the default back to sequential boot.
10059 The upload of the new sysvinit package also activate a new upstream
10062 More information about
10063 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10064 based boot sequencing
</a
> is available from the Debian wiki. It is
10065 currently possible to disable parallel booting when one run into
10066 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10068 <blockquote
><pre
>
10070 </pre
></blockquote
>
10072 <p
>If you report any problems with dependencies in init.d scripts to
10073 the BTS, please usertag the report to get it to show up at
10074 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10075 list of usertagged bugs related to this
</a
>.
</p
>
10080 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10081 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10082 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10083 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10084 <description><p
>In the recent Debian Edu versions, the
10085 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10086 system
</a
> is used to keep track of the machines in the school
10087 network. Each machine will automatically report its status to the
10088 central server after boot and once per night. The network setup is
10089 also reported, and using this information it is possible to get the
10090 MAC address of all network interfaces in the machines. This is useful
10091 to update the DHCP configuration.
</p
>
10093 <p
>To give some idea how to use sitesummary, here is a one-liner to
10094 ist all MAC addresses of all machines reporting to sitesummary. Run
10095 this on the collector host:
</p
>
10097 <blockquote
><pre
>
10098 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10099 </pre
></blockquote
>
10101 <p
>This will list all MAC addresses assosiated with all machine, one
10102 line per machine and with space between the MAC addresses.
</p
>
10104 <p
>To allow system administrators easier job at adding static DHCP
10105 addresses for hosts, it would be possible to extend this to fetch
10106 machine information from sitesummary and update the DHCP and DNS
10107 tables in LDAP using this information. Such tool is unfortunately not
10108 written yet.
</p
>
10113 <title>systemd, an interesting alternative to upstart
</title>
10114 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10115 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10116 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10117 <description><p
>The last few days a new boot system called
10118 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10120 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10122 to the free software world. I have not yet had time to play around
10123 with it, but it seem to be a very interesting alternative to
10124 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10125 a good alternative for Debian when we are able to switch to an event
10126 based boot system. Tollef is
10127 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10128 systemd into Debian, and I look forward to seeing how well it work. I
10129 like the fact that systemd handles init.d scripts with dependency
10130 information natively, allowing them to run in parallel where upstart
10131 at the moment do not.
</p
>
10133 <p
>Unfortunately do systemd have the same problem as upstart regarding
10134 platform support. It only work on recent Linux kernels, and also need
10135 some new kernel features enabled to function properly. This means
10136 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10137 system. Not sure how that will be handled if systemd proves to be the
10138 way forward.
</p
>
10140 <p
>In the mean time, based on the
10141 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10142 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10143 decided to enable full parallel booting as the default in Debian as
10144 soon as possible (probably this weekend or early next week), to see if
10145 there are any remaining serious bugs in the init.d dependencies. A
10146 new version of the sysvinit package implementing this change is
10147 already in experimental. If all go well, Squeeze will be released
10148 with parallel booting enabled by default.
</p
>
10153 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10154 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10155 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10156 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10157 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10158 complete, so complete that it is actually possible to run all the
10159 init.d scripts in parallell based on these dependencies. If you want
10160 to test your Squeeze system, make sure
10161 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10162 based boot sequencing
</a
> is enabled, and add this line to
10163 /etc/default/rcS:
</p
>
10165 <blockquote
><pre
>
10166 CONCURRENCY=makefile
10167 </pre
></blockquote
>
10169 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10170 scripts in parallel using the dependency information stored in
10171 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10172 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10173 to try to start the kdm and gdm scripts as early as possible, and will
10174 start the facilities required by kdm or gdm as early as possible to
10175 make this happen.
</p
>
10177 <p
>Give it a try, and see if you like the result. If some services
10178 fail to start properly, it is most likely because they have incomplete
10179 init.d script dependencies in their startup script (or some of their
10180 dependent scripts have incomplete dependencies). Report bugs and get
10181 the package maintainers to fix it. :)
</p
>
10183 <p
>Running scripts in parallel could be the default in Debian when we
10184 manage to get the init.d script dependencies complete and correct. I
10185 expect we will get there in Squeeze+
1, if we get manage to test and
10186 fix the remaining issues.
</p
>
10188 <p
>If you report any problems with dependencies in init.d scripts to
10189 the BTS, please usertag the report to get it to show up at
10190 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10191 list of usertagged bugs related to this
</a
>.
</p
>
10196 <title>Debian has switched to dependency based boot sequencing
</title>
10197 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10199 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10200 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10201 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10202 have been migrated to using dependency based boot sequencing. This
10203 conclude work me and others have been doing for the last three days.
10204 It feels great to see this finally part of the default Debian
10205 installation. Now we just need to weed out the last few problems that
10206 are bound to show up, to get everything ready for Squeeze.
</p
>
10208 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10209 fixing the more fundamental problem of handing the event based
10210 non-predictable kernel in the early boot.
</p
>
10215 <title>Taking over sysvinit development
</title>
10216 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10217 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10218 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10219 <description><p
>After several years of frustration with the lack of activity from
10220 the existing sysvinit upstream developer, I decided a few weeks ago to
10221 take over the package and become the new upstream. The number of
10222 patches to track for the Debian package was becoming a burden, and the
10223 lack of synchronization between the distribution made it hard to keep
10224 the package up to date.
</p
>
10226 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10227 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10228 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10229 and Fedora), based on the patches currently in use in these
10230 distributions. We Debian maintainers plan to move to this tarball as
10231 the new upstream as soon as we find time to do the merge. Since the
10232 new tarball was created, we agreed with Werner at SuSe to make a new
10233 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10234 development there. The project is registered and currently waiting
10235 for approval by the Savannah administrators, and as soon as it is
10236 approved, we will import the old versions from svn and continue
10237 working on the future release.
</p
>
10239 <p
>It is a bit ironic that this is done now, when some of the involved
10240 distributions are moving to upstart as a syvinit replacement.
</p
>
10245 <title>Debian boots quicker and quicker
</title>
10246 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10247 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10248 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10249 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10250 people involved in the boot system on Debian and Ubuntu, to see if we
10251 could find more ways to speed up the boot system. This was an Ubuntu
10253 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10254 gathering
</a
>. It was quite productive. We also discussed the future
10255 of boot systems, and ways to handle the increasing number of boot
10256 issues introduced by the Linux kernel becoming more and more
10257 asynchronous and event base. The Ubuntu approach using udev and
10258 upstart might be a good way forward. Time will show.
</p
>
10260 <p
>Anyway, there are a few ways at the moment to speed up the boot
10261 process in Debian. All of these should be applied to get a quick
10266 <li
>Use dash as /bin/sh.
</li
>
10268 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10269 clock is in UTC.
</li
>
10271 <li
>Install and activate the insserv package to enable
10272 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10273 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10277 These points are based on the Google summer of code work done by
10278 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10279 Villegas
</a
>.
10281 <p
>Support for makefile-style concurrency during boot was uploaded to
10282 unstable yesterday. When we tested it, we were able to cut
6 seconds
10283 from the boot sequence. It depend on very correct dependency
10284 declaration in all init.d scripts, so I expect us to find edge cases
10285 where the dependences in some scripts are slightly wrong when we start
10286 using this.
</p
>
10288 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10289 introduced by Raphael Geissert today, one that could affect the
10290 startup speed as well. Instead of starting some scripts concurrently
10291 from rcS.d/ and another set of scripts from rc2.d/, it would be
10292 possible to run a of them in the same process. A quick way to test
10293 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10294 insserv
'. Will need to test if that work. :)
</p
>
10299 <title>BSAs påstander om piratkopiering møter motstand
</title>
10300 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10301 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10302 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10303 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10304 programvareselskapene som Microsoft og Apple, publisert en rapport der
10305 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10306 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10308 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10309 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10310 dagene. Et spesielt interessant kommentar fra Sverige,
10311 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10312 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10315 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10316 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10317 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10318 exakta
", säger BSAs Sverigechef John Hugosson.
10319 </blockquote
>
10321 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10322 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10323 piracy figures need a shot of reality
</a
> og
<a
10324 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10325 Copyright Treaty Work?
</a
></p
>
10327 <p
>Fant lenkene via
<a
10328 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10329 på Slashdot
</a
>.
</p
>
10334 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10335 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10336 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10337 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10338 <description><p
>Kom over
10339 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10340 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10341 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10342 jobber til daglig. En rask opptelling forteller meg at vi har
490
10343 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10344 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10345 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10350 <title>Kryptert harddisk - naturligvis
</title>
10351 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10353 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10354 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10355 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10356 når en tar tap av arbeidstid, fortrolige dokumenter,
10357 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10358 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10359 til at jeg har kryptert harddisken på både kontormaskinen og min
10360 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10361 komme på avveie, den første informasjon relatert til jobben min ved
10362 Universitetet i Oslo, og den andre relatert til blant annet
10363 foreningsarbeide. Kryptering av diskene gjør at det er lite
10364 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10365 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10366 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10367 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10368 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10369 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10370 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10371 det er gjort slik jeg gjør det er minimale, og gevinstene er
10372 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10373 maskinen reinstalleres og alt er tapt.
</p
>
10375 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10376 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10377 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10378 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10379 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10380 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10381 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10382 betydelige.
</p
>
10387 <title>Two projects that have improved the quality of free software a lot
</title>
10388 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10390 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10391 <description><p
>There are two software projects that have had huge influence on the
10392 quality of free software, and I wanted to mention both in case someone
10393 do not yet know them.
</p
>
10395 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10396 tool to detect and expose errors in the memory handling of programs.
10397 It is easy to use, all one need to do is to run
'valgrind program
',
10398 and it will report any problems on stdout. It is even better if the
10399 program include debug information. With debug information, it is able
10400 to report the source file name and line number where the problem
10401 occurs. It can report things like
'reading past memory block in file
10402 X line N, the memory block was allocated in file Y, line M
', and
10403 'using uninitialised value in control logic
'. This tool has made it
10404 trivial to investigate reproducible crash bugs in programs, and have
10405 reduced the number of this kind of bugs in free software a lot.
10407 <p
>The second one is
10408 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10409 a source code checker. It is able to process the source of a program
10410 and find problems in the logic without running the program. It
10411 started out as the Stanford Checker and became well known when it was
10412 used to find bugs in the Linux kernel. It is now a commercial tool
10413 and the company behind it is running
10414 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10415 free software community, where a lot of free software projects get
10416 their source checked for free. Several thousand defects have been
10417 found and fixed so far. It can find errors like
'lock L taken in file
10418 X line N is never released if exiting in line M
', or
'the code in file
10419 Y lines O to P can never be executed
'. The projects included in the
10420 community service project have managed to get rid of a lot of
10421 reliability problems thanks to Coverity.
</p
>
10423 <p
>I believe tools like this, that are able to automatically find
10424 errors in the source, are vital to improve the quality of software and
10425 make sure we can get rid of the crashing and failing software we are
10426 surrounded by today.
</p
>
10431 <title>No patch is not better than a useless patch
</title>
10432 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10433 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10434 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10435 <description><p
>Julien Blache
10436 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10437 patch is better than a useless patch
</a
>. I completely disagree, as a
10438 patch allow one to discuss a concrete and proposed solution, and also
10439 prove that the issue at hand is important enough for someone to spent
10440 time on fixing it. No patch do not provide any of these positive
10441 properties.
</p
>
10446 <title>Standardize on protocols and formats, not vendors and applications
</title>
10447 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10449 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10450 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10451 very good one to form a long lived computer infrastructure. It is the
10452 simple one, lost by many in todays computer industry: Standardize on
10453 open network protocols and open exchange/storage formats, not applications.
10454 Applications come and go, while protocols and files tend to stay, and
10455 thus one want to make it easy to change application and vendor, while
10456 avoiding conversion costs and locking users to a specific platform or
10457 application.
</p
>
10459 <p
>This approach make it possible to replace the client applications
10460 independently of the server applications. One can even allow users to
10461 use several different applications as long as they handle the selected
10462 protocol and format. In the normal case, only one client application
10463 is recommended and users only get help if they choose to use this
10464 application, but those that want to deviate from the easy path are not
10465 blocked from doing so.
</p
>
10467 <p
>It also allow us to replace the server side without forcing the
10468 users to replace their applications, and thus allow us to select the
10469 best server implementation at any moment, when scale and resouce
10470 requirements change.
</p
>
10472 <p
>I strongly recommend standardizing - on open network protocols and
10473 open formats, but I would never recommend standardizing on a single
10474 application that do not use open network protocol or open formats.
</p
>
10479 <title>Returning from Skolelinux developer gathering
</title>
10480 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10481 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10482 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10483 <description><p
>I
'm sitting on the train going home from this weekends Debian
10484 Edu/Skolelinux development gathering. I got a bit done tuning the
10485 desktop, and looked into the dynamic service location protocol
10486 implementation avahi. It look like it could be useful for us. Almost
10487 30 people participated, and I believe it was a great environment to
10488 get to know the Skolelinux system. Walter Bender, involved in the
10489 development of the Sugar educational platform, presented his stuff and
10490 also helped me improve my OLPC installation. He also showed me that
10491 his Turtle Art application can be used in standalone mode, and we
10492 agreed that I would help getting it packaged for Debian. As a
10493 standalone application it would be great for Debian Edu. We also
10494 tried to get the video conferencing working with two OLPCs, but that
10495 proved to be too hard for us. The application seem to need more work
10496 before it is ready for me. I look forward to getting home and relax
10502 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10503 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10504 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10505 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10506 <description><p
>The state of standardized LDAP schemas on Linux is far from
10507 optimal. There is RFC
2307 documenting one way to store NIS maps in
10508 LDAP, and a modified version of this normally called RFC
2307bis, with
10509 some modifications to be compatible with Active Directory. The RFC
10510 specification handle the content of a lot of system databases, but do
10511 not handle DNS zones and DHCP configuration.
</p
>
10513 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10514 we would like to store information about users, SMB clients/hosts,
10515 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10516 and LTSP configuration in LDAP. These objects have a lot in common,
10517 but with the current LDAP schemas it is not possible to have one
10518 object per entity. For example, one need to have at least three LDAP
10519 objects for a given computer, one with the SMB related stuff, one with
10520 DNS information and another with DHCP information. The schemas
10521 provided for DNS and DHCP are impossible to combine into one LDAP
10522 object. In addition, it is impossible to implement quick queries for
10523 netgroup membership, because of the way NIS triples are implemented.
10524 It just do not scale. I believe it is time for a few RFC
10525 specifications to cleam up this mess.
</p
>
10527 <p
>I would like to have one LDAP object representing each computer in
10528 the network, and this object can then keep the SMB (ie host key), DHCP
10529 (mac address/name) and DNS (name/IP address) settings in one place.
10530 It need to be efficently stored to make sure it scale well.
</p
>
10532 <p
>I would also like to have a quick way to map from a user or
10533 computer and to the net group this user or computer is a member.
</p
>
10535 <p
>Active Directory have done a better job than unix heads like myself
10536 in this regard, and the unix side need to catch up. Time to start a
10537 new IETF work group?
</p
>
10542 <title>Endelig er Debian Lenny gitt ut
</title>
10543 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10545 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10546 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10547 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10548 Et langt steg videre for Debian-prosjektet, og en rekke nye
10549 programpakker blir nå tilgjengelig for de av oss som bruker den
10550 stabile utgaven av Debian. Neste steg er nå å få
10551 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10552 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10553 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10554 slippes løs på skolene. Takk til alle debian-utviklerne som har
10555 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10556 bootsekvens tilgjengelig i stabil utgave, vha pakken
10557 <tt
>insserv
</tt
>.
</p
>
10562 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10563 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10564 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10565 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10566 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10567 Oslo. Most of Saturday was used for the general assemly for the
10568 member organization, but the rest of the weekend I used to tune the
10569 LTSP installation. LTSP now work out of the box on the
10-network.
10570 Acer Aspire One proved to be a very nice thin client, with both
10571 screen, mouse and keybard in a small box. Was working on getting the
10572 diskless workstation setup configured out of the box, but did not
10573 finish it before the weekend was up.
</p
>
10575 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10576 the Brazilian group, so that will have to wait for the next
10577 development gathering. Would love to have the Debian Edu installer
10578 automatically detect and configure a multiseat setup when it find one
10579 of these cards.
</p
>
10584 <title>The sorry state of multimedia browser plugins in Debian
</title>
10585 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10587 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10588 <description><p
>Recently I have spent some time evaluating the multimedia browser
10589 plugins available in Debian Lenny, to see which one we should use by
10590 default in Debian Edu. We need an embedded video playing plugin with
10591 control buttons to pause or stop the video, and capable of streaming
10592 all the multimedia content available on the web. The test results and
10593 notes are available on
10594 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10595 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10596 fill this need. My personal video player favorite, VLC, has a really
10597 bad plugin which fail on a lot of the test pages. A lot of the MIME
10598 types I would expect to work with any free software player (like
10599 video/ogg), just do not work. And simple formats like the
10600 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10601 totem and vlc plugins. I hope the situation will improve soon. No
10602 wonder sites use the proprietary Adobe flash to play video.
</p
>
10604 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10605 be the only one fitting our needs. :/
</p
>