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>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
11 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
13 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
14 <description><p
>On friday, I came across an interesting article in the Norwegian
15 web based ICT news magazine digi.no on
16 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
17 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
18 DVB-T software defined radios. The article refered to instructions
19 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
20 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
22 <p
>The instructions said to use Ubuntu, install pip using apt (to
23 bypass apt), use pip to install pybombs (to bypass both apt and pip),
24 and the ask pybombs to fetch and build everything you need from
25 scratch. I wanted to see if I could do the same on the most recent
26 Debian packages, but this did not work because pybombs tried to build
27 stuff that no longer build with the most recent openssl library or
28 some other version skew problem. While trying to get this recipe
29 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
30 and the only piece of software dependency missing in Debian was the
31 gr-gsm package. I also found out that the lead upstream developer of
32 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
33 Debian packages provided in an Ubuntu PPA repository. All I needed to
34 do was to dget the Debian source package and built it.
</p
>
36 <p
>The IMSI collector is a python script listening for packages on the
37 loopback network device and printing to the terminal some specific GSM
38 packages with IMSI numbers in them. The code is fairly short and easy
39 to understand. The reason this work is because gr-gsm include a tool
40 to read GSM data from a software defined radio like a DVB-T USB stick
41 and other software defined radios, decode them and inject them into a
42 network device on your Linux machine (using the loopback device by
43 default). This proved to work just fine, and I
've been testing the
44 collector for a few days now.
</p
>
46 <p
>The updated and simpler recipe is thus to
</p
>
50 <li
>start with a Debian machine running Stretch or newer,
</li
>
52 <li
>build and install the gr-gsm package available from
53 <a href=
"http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
</a
>,
</li
>
55 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
57 <li
>run grgsm_livemon and adjust the frequency until the terminal
58 where it was started is filled with a stream of text (meaning you
59 found a GSM station).
</li
>
61 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
65 <p
>To make it even easier in the future to get this sniffer up and
66 running, I decided to package
67 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
68 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
69 #
871055</a
>), and the package was uploaded into the NEW queue today.
70 Luckily the gnuradio maintainer has promised to help me, as I do not
71 know much about gnuradio stuff yet.
</p
>
73 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
75 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
76 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
77 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
78 Stingray
</a
>, but I hope the existance of cheap alternatives can make
79 more people realise how their whereabouts when carrying a cell phone
80 is easily tracked. Seeing the data flow on the screen, realizing that
81 I live close to a police station and knowing that the police is also
82 wearing cell phones, I wonder how hard it would be for criminals to
83 track the position of the police officers to discover when there are
84 police near by, or for foreign military forces to track the location
85 of the Norwegian military forces, or for anyone to track the location
86 of government officials...
</p
>
88 <p
>It is worth noting that the data reported by the IMSI-catcher
89 script mentioned above is only a fraction of the data broadcasted on
90 the GSM network. It will only collect one frequency at the time,
91 while a typical phone will be using several frequencies, and not all
92 phones will be using the frequencies tracked by the grgsm_livemod
93 program. Also, there is a lot of radio chatter being ignored by the
94 simple_IMSI-catcher script, which would be collected by extending the
95 parser code. I wonder if gr-gsm can be set up to listen to more than
96 one frequency?
</p
>
101 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
102 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
104 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
105 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
107 <p
>I finally received a copy of the Norwegian Bokmål edition of
108 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
109 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
110 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
111 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
112 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
113 price. The book is also available for download in electronic form as
114 PDF, EPUB and Mobipocket, as can be
115 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
116 as a web page
</a
>.
</p
>
118 <p
>This is the second book I publish (the first was the book
119 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
121 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
122 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
124 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
125 Bokmål
</a
>), and I am very excited to finally wrap up this
127 "<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
128 for Debian-administratoren
</a
>" will be well received.
</p
>
133 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
134 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
135 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
136 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
137 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
138 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
139 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
140 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
141 på om den fri oversetterløsningen
142 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
143 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
145 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
148 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
149 rolle og muligheter til å håndtere internasjonale utfordringer, som
150 for eksempel flykningekrisen.
</p
>
152 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
155 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
156 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
161 <p
>Dette oversetter Apertium slik:
</p
>
164 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
165 andre aktørar og høve til å handtera internasjonale utfordringar, som
166 til dømes *flykningekrisen.
</p
>
168 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
172 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
173 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
178 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
179 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
180 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
181 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
182 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
183 det er kanskje flisespikking. Det understreker vel bare at det alltid
184 trengs korrekturlesning etter automatisk oversettelse.
</p
>
189 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
190 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
191 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
192 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
193 <description><p
>Over the years, administrating thousand of NFS mounting linux
194 computers at the time, I often needed a way to detect if the machine
195 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
196 file or directory affected by the hang, the process (and possibly the
197 shell) will hang too. So you want to be able to detect this without
198 risking the detection process getting stuck too. It has not been
199 obvious how to do this. When the hang has lasted a while, it is
200 possible to find messages like these in dmesg:
</p
>
202 <p
><blockquote
>
203 nfs: server nfsserver not responding, still trying
204 <br
>nfs: server nfsserver OK
205 </blockquote
></p
>
207 <p
>It is hard to know if the hang is still going on, and it is hard to
208 be sure looking in dmesg is going to work. If there are lots of other
209 messages in dmesg the lines might have rotated out of site before they
210 are noticed.
</p
>
212 <p
>While reading through the nfs client implementation in linux kernel
213 code, I came across some statistics that seem to give a way to detect
214 it. The om_timeouts sunrpc value in the kernel will increase every
215 time the above log entry is inserted into dmesg. And after digging a
216 bit further, I discovered that this value show up in
217 /proc/self/mountstats on Linux.
</p
>
219 <p
>The mountstats content seem to be shared between files using the
220 same file system context, so it is enough to check one of the
221 mountstats files to get the state of the mount point for the machine.
222 I assume this will not show lazy umounted NFS points, nor NFS mount
223 points in a different process context (ie with a different filesystem
224 view), but that does not worry me.
</p
>
226 <p
>The content for a NFS mount point look similar to this:
</p
>
228 <p
><blockquote
><pre
>
230 device /dev/mapper/Debian-var mounted on /var with fstype ext3
231 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
232 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
234 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
235 sec: flavor=
1,pseudoflavor=
1
236 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
237 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
238 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
239 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
241 NULL:
0 0 0 0 0 0 0 0
242 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
243 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
244 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
245 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
246 READLINK:
125 125 0 20472 18620 0 1112 1118
247 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
248 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
249 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
250 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
251 SYMLINK:
903 903 0 233428 245488 6 5865 5917
252 MKNOD:
80 80 0 20148 21760 0 299 304
253 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
254 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
255 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
256 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
257 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
258 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
259 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
260 FSINFO:
2 2 0 232 328 0 1 1
261 PATHCONF:
1 1 0 116 140 0 0 0
262 COMMIT:
0 0 0 0 0 0 0 0
264 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
266 </pre
></blockquote
></p
>
268 <p
>The key number to look at is the third number in the per-op list.
269 It is the number of NFS timeouts experiences per file system
270 operation. Here
22 write timeouts and
5 access timeouts. If these
271 numbers are increasing, I believe the machine is experiencing NFS
272 hang. Unfortunately the timeout value do not start to increase right
273 away. The NFS operations need to time out first, and this can take a
274 while. The exact timeout value depend on the setup. For example the
275 defaults for TCP and UDP mount points are quite different, and the
276 timeout value is affected by the soft, hard, timeo and retrans NFS
277 mount options.
</p
>
279 <p
>The only way I have been able to get working on Debian and RedHat
280 Enterprise Linux for getting the timeout count is to peek in /proc/.
282 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
283 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
284 command can be used to get these timeout values. But this do not work
285 on Linux, as far as I can tell. I
286 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
287 but have not seen any replies yet.
</p
>
289 <p
>Is there a better way to figure out if a Linux NFS client is
290 experiencing NFS hangs? Is there a way to detect which processes are
291 affected? Is there a way to get the NFS mount going quickly once the
292 network problem causing the NFS hang has been cleared? I would very
293 much welcome some clues, as we regularly run into NFS hangs.
</p
>
298 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
299 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
300 <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>
301 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
302 <description><p
>For almost a year now, we have been working on making a Norwegian
303 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
304 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
305 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
306 we are working on the proof reading to ensure consistent language and
307 use of correct computer science terms. The plan is to make the book
308 available on paper, as well as in electronic form. For that to
309 happen, the proof reading must be completed and all the figures need
310 to be translated. If you want to help out, get in touch.
</p
>
312 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
314 fresh PDF edition
</a
> in A4 format (the final book will have smaller
315 pages) of the book created every morning is available for
316 proofreading. If you find any errors, please
317 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
318 Weblate and correct the error
</a
>. The
319 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
320 of the translation including figures
</a
> is a useful source for those
321 provide Norwegian bokmål screen shots and figures.
</p
>
326 <title>Unlimited randomness with the ChaosKey?
</title>
327 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
329 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
330 <description><p
>A few days ago I ordered a small batch of
331 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
332 USB dongle for generating entropy created by Bdale Garbee and Keith
333 Packard. Yesterday it arrived, and I am very happy to report that it
334 work great! According to its designers, to get it to work out of the
335 box, you need the Linux kernel version
4.1 or later. I tested on a
336 Debian Stretch machine (kernel version
4.9), and there it worked just
337 fine, increasing the available entropy very quickly. I wrote a small
338 test oneliner to test. It first print the current entropy level,
339 drain /dev/random, and then print the entropy level for five seconds.
340 Here is the situation without the ChaosKey inserted:
</p
>
342 <blockquote
><pre
>
343 % cat /proc/sys/kernel/random/entropy_avail; \
344 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
345 for n in $(seq
1 5); do \
346 cat /proc/sys/kernel/random/entropy_avail; \
352 28 byte kopiert,
0,
000264565 s,
106 kB/s
359 </pre
></blockquote
>
361 <p
>The entropy level increases by
3-
4 every second. In such case any
362 application requiring random bits (like a HTTPS enabled web server)
363 will halt and wait for more entrpy. And here is the situation with
364 the ChaosKey inserted:
</p
>
366 <blockquote
><pre
>
367 % cat /proc/sys/kernel/random/entropy_avail; \
368 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
369 for n in $(seq
1 5); do \
370 cat /proc/sys/kernel/random/entropy_avail; \
376 104 byte kopiert,
0,
000487647 s,
213 kB/s
383 </pre
></blockquote
>
385 <p
>Quite the difference. :) I bought a few more than I need, in case
386 someone want to buy one here in Norway. :)
</p
>
388 <p
>Update: The dongle was presented at Debconf last year. You might
389 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
390 recording illuminating
</a
>. It explains exactly what the source of
391 randomness is, if you are unable to spot it from the schema drawing
392 available from the ChaosKey web site linked at the start of this blog
398 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
399 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
400 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
401 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
402 <description><p
>Did you ever wonder where the web trafic really flow to reach the
403 web servers, and who own the network equipment it is flowing through?
404 It is possible to get a glimpse of this from using traceroute, but it
405 is hard to find all the details. Many years ago, I wrote a system to
406 map the Norwegian Internet (trying to figure out if our plans for a
407 network game service would get low enough latency, and who we needed
408 to talk to about setting up game servers close to the users. Back
409 then I used traceroute output from many locations (I asked my friends
410 to run a script and send me their traceroute output) to create the
411 graph and the map. The output from traceroute typically look like
415 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
416 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
417 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
418 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
419 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
420 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
421 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
422 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
426 </pre
></p
>
428 <p
>This show the DNS names and IP addresses of (at least some of the)
429 network equipment involved in getting the data traffic from me to the
430 www.stortinget.no server, and how long it took in milliseconds for a
431 package to reach the equipment and return to me. Three packages are
432 sent, and some times the packages do not follow the same path. This
433 is shown for hop
5, where three different IP addresses replied to the
434 traceroute request.
</p
>
436 <p
>There are many ways to measure trace routes. Other good traceroute
437 implementations I use are traceroute (using ICMP packages) mtr (can do
438 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
439 traceroute and a lot of other capabilities). All of them are easily
440 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
442 <p
>This time around, I wanted to know the geographic location of
443 different route points, to visualize how visiting a web page spread
444 information about the visit to a lot of servers around the globe. The
445 background is that a web site today often will ask the browser to get
446 from many servers the parts (for example HTML, JSON, fonts,
447 JavaScript, CSS, video) required to display the content. This will
448 leak information about the visit to those controlling these servers
449 and anyone able to peek at the data traffic passing by (like your ISP,
450 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
452 <p
>Lets pick an example, the Norwegian parliament web site
453 www.stortinget.no. It is read daily by all members of parliament and
454 their staff, as well as political journalists, activits and many other
455 citizens of Norway. A visit to the www.stortinget.no web site will
456 ask your browser to contact
8 other servers: ajax.googleapis.com,
457 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
458 stats.g.doubleclick.net, www.google-analytics.com,
459 www.googletagmanager.com and www.netigate.se. I extracted this by
460 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
461 Stortinget web page and tell me all the URLs PhantomJS downloaded to
462 render the page (in HAR format using
463 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
464 netsniff example
</a
>. I am very grateful to Gorm for showing me how
465 to do this). My goal is to visualize network traces to all IP
466 addresses behind these DNS names, do show where visitors personal
467 information is spread when visiting the page.
</p
>
469 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
470 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
>
472 <p
>When I had a look around for options, I could not find any good
473 free software tools to do this, and decided I needed my own traceroute
474 wrapper outputting KML based on locations looked up using GeoIP. KML
475 is easy to work with and easy to generate, and understood by several
476 of the GIS tools I have available. I got good help from by NUUG
477 colleague Anders Einar with this, and the result can be seen in
478 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
479 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
480 free GeoIP databases I could find (and the for-pay databases my
481 friends had access to) is not up to the task. The IP addresses of
482 central Internet infrastructure would typically be placed near the
483 controlling companies main office, and not where the router is really
484 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
485 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
487 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
488 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
>
490 <p
>I also had a look at the visual traceroute graph created by
491 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
492 showing IP network ownership (aka AS owner) for the IP address in
494 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
495 graph display a lot of useful information about the traceroute in SVG
496 format
</a
>, and give a good indication on who control the network
497 equipment involved, but it do not include geolocation. This graph
498 make it possible to see the information is made available at least for
499 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
500 3 Communications and NetDNA.
</p
>
502 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
503 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
>
505 <p
>In the process, I came across the
506 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
507 Salim Gasmi. Its methology of combining guesses based on DNS names,
508 various location databases and finally use latecy times to rule out
509 candidate locations seemed to do a very good job of guessing correct
510 geolocation. But it could only do one trace at the time, did not have
511 a sensor in Norway and did not make the geolocations easily available
512 for postprocessing. So I contacted the developer and asked if he
513 would be willing to share the code (he refused until he had time to
514 clean it up), but he was interested in providing the geolocations in a
515 machine readable format, and willing to set up a sensor in Norway. So
516 since yesterday, it is possible to run traces from Norway in this
517 service thanks to a sensor node set up by
518 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
519 trace in KML format for further processing.
</p
>
521 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
522 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
>
524 <p
>Here we can see a lot of trafic passes Sweden on its way to
525 Denmark, Germany, Holland and Ireland. Plenty of places where the
526 Snowden confirmations verified the traffic is read by various actors
527 without your best interest as their top priority.
</p
>
529 <p
>Combining KML files is trivial using a text editor, so I could loop
530 over all the hosts behind the urls imported by www.stortinget.no and
531 ask for the KML file from GeoTraceroute, and create a combined KML
532 file with all the traces (unfortunately only one of the IP addresses
533 behind the DNS name is traced this time. To get them all, one would
534 have to request traces using IP number instead of DNS names from
535 GeoTraceroute). That might be the next step in this project.
</p
>
537 <p
>Armed with these tools, I find it a lot easier to figure out where
538 the IP traffic moves and who control the boxes involved in moving it.
539 And every time the link crosses for example the Swedish border, we can
540 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
541 Britain and NSA in USA and cables around the globe. (Hm, what should
542 we tell them? :) Keep that in mind if you ever send anything
543 unencrypted over the Internet.
</p
>
545 <p
>PS: KML files are drawn using
546 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
547 Rublev
<a/
>, as it was less cluttered than the local Linux application
548 Marble. There are heaps of other options too.
</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>Appstream just learned how to map hardware to packages too!
</title>
558 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
560 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
561 <description><p
>I received a very nice Christmas present today. As my regular
562 readers probably know, I have been working on the
563 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
564 system
</a
> for many years. The goal of the Isenkram system is to make
565 it easier for users to figure out what to install to get a given piece
566 of hardware to work in Debian, and a key part of this system is a way
567 to map hardware to packages. Isenkram have its own mapping database,
568 and also uses data provided by each package using the AppStream
569 metadata format. And today,
570 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
571 Debian learned to look up hardware the same way Isenkram is doing it,
572 ie using fnmatch():
</p
>
575 % appstreamcli what-provides modalias \
576 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
577 Identifier: pymissile [generic]
579 Summary: Control original Striker USB Missile Launcher
581 % appstreamcli what-provides modalias usb:v0694p0002d0000
582 Identifier: libnxt [generic]
584 Summary: utility library for talking to the LEGO Mindstorms NXT brick
587 Identifier: t2n [generic]
589 Summary: Simple command-line tool for Lego NXT
592 Identifier: python-nxt [generic]
594 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
597 Identifier: nbc [generic]
599 Summary: C compiler for LEGO Mindstorms NXT bricks
602 </pre
></p
>
604 <p
>A similar query can be done using the combined AppStream and
605 Isenkram databases using the isenkram-lookup tool:
</p
>
608 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
610 % isenkram-lookup usb:v0694p0002d0000
616 </pre
></p
>
618 <p
>You can find modalias values relevant for your machine using
619 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
621 <p
>If you want to make this system a success and help Debian users
622 make the most of the hardware they have, please
623 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
624 AppStream metadata for your package following the guidelines
</a
>
625 documented in the wiki. So far only
11 packages provide such
626 information, among the several hundred hardware specific packages in
627 Debian. The Isenkram database on the other hand contain
101 packages,
628 mostly related to USB dongles. Most of the packages with hardware
629 mapping in AppStream are LEGO Mindstorms related, because I have, as
630 part of my involvement in
631 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
632 team
</a
> given priority to making sure LEGO users get proposed the
633 complete set of packages in Debian for that particular hardware. The
634 team also got a nice Christmas present today. The
635 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
636 package
</a
> made it into Debian. With this package in place, it is
637 now possible to use the LEGO Mindstorms NXT unit with only free
638 software, as the nxt-firmware package contain the source and firmware
639 binaries for the NXT brick.
</p
>
641 <p
>As usual, if you use Bitcoin and want to show your support of my
642 activities, please send Bitcoin donations to my address
643 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
648 <title>Isenkram updated with a lot more hardware-package mappings
</title>
649 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
650 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
651 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
652 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
653 system
</a
> I wrote two years ago to make it easier in Debian to find
654 and install packages to get your hardware dongles to work, is still
655 going strong. It is a system to look up the hardware present on or
656 connected to the current system, and map the hardware to Debian
657 packages. It can either be done using the tools in isenkram-cli or
658 using the user space daemon in the isenkram package. The latter will
659 notify you, when inserting new hardware, about what packages to
660 install to get the dongle working. It will even provide a button to
661 click on to ask packagekit to install the packages.
</p
>
663 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
682 </pre
></p
>
684 <p
>It can also list the firware package providing firmware requested
685 by the load kernel modules, which in my case is an empty list because
686 I have all the firmware my machine need:
689 % /usr/sbin/isenkram-autoinstall-firmware -l
690 info: did not find any firmware files requested by loaded kernel modules. exiting
692 </pre
></p
>
694 <p
>The last few days I had a look at several of the around
250
695 packages in Debian with udev rules. These seem like good candidates
696 to install when a given hardware dongle is inserted, and I found
697 several that should be proposed by isenkram. I have not had time to
698 check all of them, but am happy to report that now there are
97
699 packages packages mapped to hardware by Isenkram.
11 of these
700 packages provide hardware mapping using AppStream, while the rest are
701 listed in the modaliases file provided in isenkram.
</p
>
703 <p
>These are the packages with hardware mappings at the moment. The
704 <strong
>marked packages
</strong
> are also announcing their hardware
705 support using AppStream, for everyone to use:
</p
>
707 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
708 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
709 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
710 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
711 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
712 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
713 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
714 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
715 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
716 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
717 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
718 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
719 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
720 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
721 pcscd, pidgin-blinklight, printer-driver-splix,
722 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
723 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
724 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
725 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
726 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
727 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
728 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
729 xserver-xorg-video-vmware, yubikey-personalization and
730 zd1211-firmware
</p
>
732 <p
>If you know of other packages, please let me know with a wishlist
733 bug report against the isenkram-cli package, and ask the package
735 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
736 metadata according to the guidelines
</a
> to provide the information
737 for everyone. In time, I hope to get rid of the isenkram specific
738 hardware mapping and depend exclusively on AppStream.
</p
>
740 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
741 much hardware, and suggest that the package with with any ethernet
742 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
743 the details. I hope the maintainer find time to address it soon. In
744 the mean time I provide an override in isenkram.
</p
>
749 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
750 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
751 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
752 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
753 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
755 <p
>In my early years, I played
756 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
757 Elite
</a
> on my PC. I spent many months trading and fighting in
758 space, and reached the
'elite
' fighting status before I moved on. The
759 original Elite game was available on Commodore
64 and the IBM PC
760 edition I played had a
64 KB executable. I am still impressed today
761 that the authors managed to squeeze both a
3D engine and details about
762 more than
2000 planet systems across
7 galaxies into a binary so
765 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
766 software game Oolite inspired by Elite
</a
> for a while, but did not
767 really have time to test it properly until a few days ago. It was
768 great to discover that my old knowledge about trading routes were
769 still valid. But my fighting and flying abilities were gone, so I had
770 to retrain to be able to dock on a space station. And I am still not
771 able to make much resistance when I am attacked by pirates, so I
772 bougth and mounted the most powerful laser in the rear to be able to
773 put up at least some resistance while fleeing for my life. :)
</p
>
775 <p
>When playing Elite in the late eighties, I had to discover
776 everything on my own, and I had long lists of prices seen on different
777 planets to be able to decide where to trade what. This time I had the
779 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
780 where information about each planet is easily available with common
781 price ranges and suggested trading routes. This improved my ability
782 to earn money and I have been able to earn enough to buy a lot of
783 useful equipent in a few days. I believe I originally played for
784 months before I could get a docking computer, while now I could get it
785 after less then a week.
</p
>
787 <p
>If you like science fiction and dreamed of a life as a vagabond in
788 space, you should try out Oolite. It is available for Linux, MacOSX
789 and Windows, and is included in Debian and derivatives since
2011.
</p
>
791 <p
>As usual, if you use Bitcoin and want to show your support of my
792 activities, please send Bitcoin donations to my address
793 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
798 <title>Quicker Debian installations using eatmydata
</title>
799 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
800 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
801 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
802 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
803 installation system, observing how using
804 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
805 could speed up the installation
</a
> quite a bit. My testing measured
806 speedup around
20-
40 percent for Debian Edu, where we install around
807 1000 packages from within the installer. The eatmydata package
808 provide a way to disable/delay file system flushing. This is a bit
809 risky in the general case, as files that should be stored on disk will
810 stay only in memory a bit longer than expected, causing problems if a
811 machine crashes at an inconvenient time. But for an installation, if
812 the machine crashes during installation the process is normally
813 restarted, and avoiding disk operations as much as possible to speed
814 up the process make perfect sense.
816 <p
>I added code in the Debian Edu specific installation code to enable
817 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
818 but did not have time to push it any further. But a few months ago I
819 picked it up again and worked with the libeatmydata package maintainer
820 Mattia Rizzolo to make it easier for everyone to get this installation
821 speedup in Debian. Thanks to our cooperation There is now an
822 eatmydata-udeb package in Debian testing and unstable, and simply
823 enabling/installing it in debian-installer (d-i) is enough to get the
824 quicker installations. It can be enabled using preseeding. The
825 following untested kernel argument should do the trick:
</p
>
827 <blockquote
><pre
>
828 preseed/early_command=
"anna-install eatmydata-udeb
"
829 </pre
></blockquote
>
831 <p
>This should ask d-i to install the package inside the d-i
832 environment early in the installation sequence. Having it installed
833 in d-i in turn will make sure the relevant scripts are called just
834 after debootstrap filled /target/ with the freshly installed Debian
835 system to configure apt to run dpkg with eatmydata. This is enough to
836 speed up the installation process. There is a proposal to
837 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
838 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
839 tested its impact.
</p
>
845 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
846 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
848 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
849 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
850 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
851 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
852 elever over det ganske land skal levere inn hvert år. Det mange ikke
853 vet er at selv om de kommersielle alternativene
854 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
855 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
856 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
857 utmerket fri programvarealternativ som kan. Oversetterverktøyet
858 Apertium har støtte for en rekke språkkombinasjoner, og takket være
859 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
860 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
861 nynorsk, og få den automatoversatt til det andre skriftspråket.
862 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
863 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
864 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
865 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
866 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
867 teksten din i webskjemaet der.
869 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
870 teknologien kan du enten installere pakken
871 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
872 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
874 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
875 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
876 denne teksten som ble skrevet på bokmål over maskinoversatt til
881 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
882 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
883 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
884 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
885 veit er at sjølv om dei kommersielle alternativa
886 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
887 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
888 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
889 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
890 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
891 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
892 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
893 nynorsk, og få den *automatoversatt til det andre skriftspråket.
894 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
895 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
896 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
897 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
898 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
899 teksta di i *webskjemaet der.
901 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
902 teknologien kan du anten installera pakken
903 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
904 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
905 *api.*apertium.org. Sjå
906 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
907 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
908 for denne teksta som vart skreva på bokmål over *maskinoversatt til
914 <title>Coz profiler for multi-threaded software is now in Debian
</title>
915 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
916 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
917 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
918 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
919 profiler able to run benchmarking experiments on the instrumented
920 multi-threaded program, finally
921 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
922 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
924 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
925 blogged about the coz tool
</a
> in August working with upstream to make
926 it suitable for Debian. There are still issues with clang
927 compatibility, inline assembly only working x86 and minimized
928 JavaScript libraries.
</p
>
930 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
932 <p
><blockquote
>
933 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
934 </blockquote
></p
>
936 <p
>This will produce a profile.coz file in the current working
937 directory with the profiling information. This is then given to a
938 JavaScript application provided in the package and available from
939 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
940 To start the local copy, invoke it in a browser like this:
</p
>
942 <p
><blockquote
>
943 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
944 </blockquote
></p
>
946 <p
>See the project home page and the
947 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
948 ;login: article on Coz
</a
> for more information on how it is
954 <title>My own self balancing Lego Segway
</title>
955 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
957 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
958 <description><p
>A while back I received a Gyro sensor for the NXT
959 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
960 present. It had been on my wishlist for a while, because I wanted to
961 build a Segway like balancing lego robot. I had already built
962 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
963 robot
</a
> with the kids, using the light/color sensor included in the
964 NXT kit as the balance sensor, but it was not working very well. It
965 could balance for a while, but was very sensitive to the light
966 condition in the room and the reflective properties of the surface and
967 would fall over after a short while. I wanted something more robust,
969 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
970 gyro sensor from HiTechnic
</a
> I believed would solve it on my
971 wishlist for some years before it suddenly showed up as a gift from my
972 loved ones. :)
</p
>
974 <p
>Unfortunately I have not had time to sit down and play with it
975 since then. But that changed some days ago, when I was searching for
976 lego segway information and came across a recipe from HiTechnic for
978 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
979 HTWay
</a
>, a segway like balancing robot. Build instructions and
980 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
981 code
</a
> was included, so it was just a question of putting it all
982 together. And thanks to the great work of many Debian developers, the
983 compiler needed to build the source for the NXT is already included in
984 Debian, so I was read to go in less than an hour. The resulting robot
985 do not look very impressive in its simplicity:
</p
>
987 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
989 <p
>Because I lack the infrared sensor used to control the robot in the
990 design from HiTechnic, I had to comment out the last task
991 (taskControl). I simply placed /* and */ around it get the program
992 working without that sensor present. Now it balances just fine until
993 the battery status run low:
</p
>
995 <p align=
"center
"><video width=
"70%
" controls=
"true
">
996 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
997 </video
></p
>
999 <p
>Now we would like to teach it how to follow a line and take remote
1000 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1002 <p
>If you, like me, love LEGO and want to make sure we find the tools
1003 they need to work with LEGO in Debian and all our derivative
1004 distributions like Ubuntu, check out
1005 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1006 project page
</a
> and join the Debian LEGO team. Personally I own a
1007 RCX and NXT controller (no EV3), and would like to make sure the
1008 Debian tools needed to program the systems I own work as they
1014 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1015 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1016 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1017 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1018 <description><p
>In July
1019 <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
1020 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1021 the ability to receive SMS messages (aka without a cell phone). It is
1022 time to share some experiences and provide an updated setup.
</p
>
1024 <p
>The Signal app have worked fine for several months now, and I use
1025 it regularly to chat with my loved ones. I had a major snag at the
1026 end of my summer vacation, when the the app completely forgot my
1027 setup, identity and keys. The reason behind this major mess was
1028 running out of disk space. To avoid that ever happening again I have
1029 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1030 roll back to an earlier version if the files are wiped by mistake. I
1031 had to use it once after introducing the git backup. When rolling
1032 back to an earlier version, one need to use the
'reset session
' option
1033 in Signal to get going, and notify the people you talk with about the
1034 problem. I assume there is some sequence number tracking in the
1035 protocol to detect rollback attacks. The git repository is rather big
1036 (
674 MiB so far), but I have not tried to figure out if some of the
1037 content can be added to a .gitignore file due to lack of spare
1040 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1041 make it impossible to send messages using Signal. I could still
1042 receive them, but had to patch the code with a new timestamp to send.
1043 I believe the timeout is added by the developers to force people to
1044 upgrade to the latest version of the app, even when there is no
1045 protocol changes, to reduce the version skew among the user base and
1046 thus try to keep the number of support requests down.
</p
>
1048 <p
>Since my original recipe, the Signal source code changed slightly,
1049 making the old patch fail to apply cleanly. Below is an updated
1050 patch, including the shell wrapper I use to start Signal. The
1051 original version required a new user to locate the JavaScript console
1052 and call a function from there. I got help from a friend with more
1053 JavaScript knowledge than me to modify the code to provide a GUI
1054 button instead. This mean that to get started you just need to run
1055 the wrapper and click the
'Register without mobile phone
' to get going
1056 now. I
've also modified the timeout code to always set it to
90 days
1057 in the future, to avoid having to patch the code regularly.
</p
>
1059 <p
>So, the updated recipe for Debian Jessie:
</p
>
1063 <li
>First, install required packages to get the source code and the
1064 browser you need. Signal only work with Chrome/Chromium, as far as I
1065 know, so you need to install it.
1068 apt install git tor chromium
1069 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1070 </pre
></li
>
1072 <li
>Modify the source code using command listed in the the patch
1073 block below.
</li
>
1075 <li
>Start Signal using the run-signal-app wrapper (for example using
1076 <tt
>`pwd`/run-signal-app
</tt
>).
1078 <li
>Click on the
'Register without mobile phone
', will in a phone
1079 number you can receive calls to the next minute, receive the
1080 verification code and enter it into the form field and press
1081 'Register
'. Note, the phone number you use will be user Signal
1082 username, ie the way others can find you on Signal.
</li
>
1084 <li
>You can now use Signal to contact others. Note, new contacts do
1085 not show up in the contact list until you restart Signal, and there is
1086 no way to assign names to Contacts. There is also no way to create or
1087 update chat groups. I suspect this is because the web app do not have
1088 a associated contact database.
</li
>
1092 <p
>I am still a bit uneasy about using Signal, because of the way its
1093 main author moxie0 reject federation and accept dependencies to major
1094 corporations like Google (part of the code is fetched from Google) and
1095 Amazon (the central coordination point is owned by Amazon). See for
1097 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1098 LibreSignal issue tracker
</a
> for a thread documenting the authors
1099 view on these issues. But the network effect is strong in this case,
1100 and several of the people I want to communicate with already use
1101 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1102 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1103 laptop
</a
>? It already work on Windows and Android, and is included
1104 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1105 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1106 working on Debian Stable.
</p
>
1108 <p
>Anyway, this is the patch I apply to the Signal code to get it
1109 working. It switch to the production servers, disable to timeout,
1110 make registration easier and add the shell wrapper:
</p
>
1113 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1114 diff --git a/js/background.js b/js/background.js
1115 index
24b4c1d.
.579345f
100644
1116 --- a/js/background.js
1117 +++ b/js/background.js
1122 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1123 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1124 var SERVER_PORTS = [
80,
4433,
8443];
1125 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1126 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1127 var messageReceiver;
1128 window.getSocketStatus = function() {
1129 if (messageReceiver) {
1130 diff --git a/js/expire.js b/js/expire.js
1131 index
639aeae..beb91c3
100644
1136 'use strict
';
1137 - var BUILD_EXPIRATION =
0;
1138 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1140 window.extension = window.extension || {};
1142 diff --git a/js/views/install_view.js b/js/views/install_view.js
1143 index
7816f4f.
.1d6233b
100644
1144 --- a/js/views/install_view.js
1145 +++ b/js/views/install_view.js
1148 'click .step1
': this.selectStep.bind(this,
1),
1149 'click .step2
': this.selectStep.bind(this,
2),
1150 -
'click .step3
': this.selectStep.bind(this,
3)
1151 +
'click .step3
': this.selectStep.bind(this,
3),
1152 +
'click .callreg
': function() { extension.install(
'standalone
') },
1155 clearQR: function() {
1156 diff --git a/options.html b/options.html
1157 index dc0f28e.
.8d709f6
100644
1161 &lt;div class=
'nav
'>
1162 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1163 &lt;p
>{{ installTagline }}
&lt;/p
>
1164 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1165 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1166 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1169 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1170 &lt;span class=
'dot step2
'>&lt;/span
>
1171 &lt;span class=
'dot step3
'>&lt;/span
>
1172 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1173 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1179 +userdata=
"`pwd`/userdata
"
1180 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1181 + (cd $userdata
&& git init)
1183 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1185 + --proxy-server=
"socks://localhost:
9050" \
1186 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1188 chmod a+rx run-signal-app
1191 <p
>As usual, if you use Bitcoin and want to show your support of my
1192 activities, please send Bitcoin donations to my address
1193 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1198 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1199 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1200 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1201 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1202 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1203 system
</a
> provide a practical and easy way to figure out which
1204 packages support the hardware in a given machine. The command line
1205 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1206 convenient way to list and install packages relevant for the current
1207 hardware during system installation, both user space packages and
1208 firmware packages. The GUI background daemon on the other hand provide
1209 a pop-up proposing to install packages when a new dongle is inserted
1210 while using the computer. For example, if you plug in a smart card
1211 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1212 that package isn
't already installed, and if you plug in a USB video
1213 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1214 cheese is currently missing. This already work just fine.
</p
>
1216 <p
>But Isenkram depend on a database mapping from hardware IDs to
1217 package names. When I started no such database existed in Debian, so
1218 I made my own data set and included it with the isenkram package and
1219 made isenkram fetch the latest version of this database from git using
1220 http. This way the isenkram users would get updated package proposals
1221 as soon as I learned more about hardware related packages.
</p
>
1223 <p
>The hardware is identified using modalias strings. The modalias
1224 design is from the Linux kernel where most hardware descriptors are
1225 made available as a strings that can be matched using filename style
1226 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1227 identifiers.
</p
>
1229 <p
>The downside to the Isenkram specific database is that there is no
1230 information about relevant distribution / Debian version, making
1231 isenkram propose obsolete packages too. But along came AppStream, a
1232 cross distribution mechanism to store and collect metadata about
1233 software packages. When I heard about the proposal, I contacted the
1234 people involved and suggested to add a hardware matching rule using
1235 modalias strings in the specification, to be able to use AppStream for
1236 mapping hardware to packages. This idea was accepted and AppStream is
1237 now a great way for a package to announce the hardware it support in a
1238 distribution neutral way. I wrote
1239 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1240 recipe on how to add such meta-information
</a
> in a blog post last
1241 December. If you have a hardware related package in Debian, please
1242 announce the relevant hardware IDs using AppStream.
</p
>
1244 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1245 RCX or NXT unit, announce this support using AppStream. The effect is
1246 that when you insert such LEGO robot controller into your Debian
1247 machine, Isenkram will propose to install the packages needed to get
1248 it working. The intention is that this should allow the local user to
1249 start programming his robot controller right away without having to
1250 guess what packages to use or which permissions to fix.
</p
>
1252 <p
>But when I sat down with my son the other day to program our NXT
1253 unit using his Debian Stretch computer, I discovered something
1254 annoying. The local console user (ie my son) did not get access to
1255 the USB device for programming the unit. This used to work, but no
1256 longer in Jessie and Stretch. After some investigation and asking
1257 around on #debian-devel, I discovered that this was because udev had
1258 changed the mechanism used to grant access to local devices. The
1259 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1260 no longer applied, because LDAP users no longer was added to the
1261 plugdev group during login. Michael Biebl told me that this method
1262 was obsolete and the new method used ACLs instead. This was good
1263 news, as the plugdev mechanism is a mess when using a remote user
1264 directory like LDAP. Using ACLs would make sure a user lost device
1265 access when she logged out, even if the user left behind a background
1266 process which would retain the plugdev membership with the ConsoleKit
1267 setup. Armed with this knowledge I moved on to fix the access problem
1268 for the LEGO Mindstorms related packages.
</p
>
1270 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1271 applied directly for a device, or is applied in
1272 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1273 LEGO Mindstorms udev rules did not have a class, I decided to add the
1274 tag directly in the udev rules files included in the packages. Here
1275 is one example. For the nqc C compiler for the RCX, the
1276 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1278 <p
><pre
>
1279 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1280 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1281 </pre
></p
>
1283 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1284 packages using plugdev in their /lib/udev/rules.d/ files should be
1285 changed to use this tag (either directly or indirectly via
1286 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1287 to detect this?
</p
>
1289 <p
>I
've been unable to find good documentation on the uaccess feature.
1290 It is unclear to me if the uaccess tag is an internal implementation
1291 detail like the udev-acl tag used by
1292 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1293 indirect method is the preferred way. Michael
1294 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1295 documentation from the systemd project
</a
> and I hope it will make
1296 this clearer. For now I use the generic classes when they exist and
1297 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1298 directly if no such class exist.
</p
>
1300 <p
>To learn more about the isenkram system, please check out
1301 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1302 blog posts tagged isenkram
</a
>.
</p
>
1304 <p
>To help out making life for LEGO constructors in Debian easier,
1305 please join us on our IRC channel
1306 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1307 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1308 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1309 list is not yet created, but we are working on it. :)
</p
>
1311 <p
>As usual, if you use Bitcoin and want to show your support of my
1312 activities, please send Bitcoin donations to my address
1313 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1318 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1319 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1320 <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>
1321 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1322 <description><p
>In April we
1323 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1324 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1325 how to set up and administrate a Debian system. Today I am happy to
1326 report that the first draft is now publicly available. You can find
1327 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1328 Administrator
's Handbook page
</a
> (under Other languages). The first
1329 eight chapters have a first draft translation, and we are working on
1330 proofreading the content. If you want to help out, please start
1332 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1333 hosted weblate project page
</a
>, and get in touch using
1334 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1335 translators mailing list
</a
>. Please also check out
1336 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1337 contributors
</a
>. A good way to contribute is to proofread the text
1338 and update weblate if you find errors.
</p
>
1340 <p
>Our goal is still to make the Norwegian book available on paper as well as
1341 electronic form.
</p
>
1346 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1347 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1348 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1349 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1350 <description><p
>This summer, I read a great article
1351 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1352 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1353 how to profile multi-threaded programs. It presented a system for
1354 profiling software by running experiences in the running program,
1355 testing how run time performance is affected by
"speeding up
" parts of
1356 the code to various degrees compared to a normal run. It does this by
1357 slowing down parallel threads while the
"faster up
" code is running
1358 and measure how this affect processing time. The processing time is
1359 measured using probes inserted into the code, either using progress
1360 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1361 can also measure unmodified code by measuring complete the program
1362 runtime and running the program several times instead.
</p
>
1364 <p
>The project and presentation was so inspiring that I would like to
1365 get the system into Debian. I
1366 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1367 a WNPP request for it
</a
> and contacted upstream to try to make the
1368 system ready for Debian by sending patches. The build process need to
1369 be changed a bit to avoid running
'git clone
' to get dependencies, and
1370 to include the JavaScript web page used to visualize the collected
1371 profiling information included in the source package.
1372 But I expect that should work out fairly soon.
</p
>
1374 <p
>The way the system work is fairly simple. To run an coz experiment
1375 on a binary with debug symbols available, start the program like this:
1377 <p
><blockquote
><pre
>
1378 coz run --- program-to-run
1379 </pre
></blockquote
></p
>
1381 <p
>This will create a text file profile.coz with the instrumentation
1382 information. To show what part of the code affect the performance
1383 most, use a web browser and either point it to
1384 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1385 or use the copy from git (in the gh-pages branch). Check out this web
1386 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
1387 profiling more useful you include
&lt;coz.h
&gt; and insert the
1388 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1389 code, rebuild and run the profiler. This allow coz to do more
1390 targeted experiments.
</p
>
1392 <p
>A video published by ACM
1393 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1394 Coz profiler
</a
> is available from Youtube. There is also a paper
1395 from the
25th Symposium on Operating Systems Principles available
1397 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1398 finding code that counts with causal profiling
</a
>.
</p
>
1400 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1401 for Coz is available from github. It will only build with clang
1403 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1404 feature missing in GCC
</a
>, but I
've submitted
1405 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1406 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1408 <p
>Please get in touch if you, like me, would like to see this piece
1409 of software in Debian. I would very much like some help with the
1410 packaging effort, as I lack the in depth knowledge on how to package
1411 C++ libraries.
</p
>
1416 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1417 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1418 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1419 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1420 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1421 to be a slight challenge. Here is the recipe if I ever need to do it
1422 again. It all started by me wanting to try the recipe to set up
1423 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1424 hardened Android installation
</a
> from the Tor project blog on a
1425 device I had access to. It is a old mobile phone with a broken
1426 microphone The initial idea had been to just
1427 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1428 CyanogenMod on it
</a
>, but did not quite find time to start on it
1429 until a few days ago.
</p
>
1431 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1432 loader (press volume down and power at the same time), (
2) select
1433 'fastboot
' before (
3) connecting the device via USB to a Linux
1434 machine, (
4) request the device identifier token by running
'fastboot
1435 oem get_identifier_token
', (
5) request the device unlocking key using
1436 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1437 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1439 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1440 or newer, and the device I was working on had
2.00.0027. This
1441 apparently can be easily fixed by downloading a Windows program and
1442 running it on your Windows machine, if you accept the terms Microsoft
1443 require you to accept to use Windows - which I do not. So I had to
1444 come up with a different approach. I got a lot of help from AndyCap
1445 on #nuug, and would not have been able to get this working without
1448 <p
>First I needed to extract the hboot firmware from
1449 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1450 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1451 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1452 project named unruu
</a
> using libunshield. The unshield tool did not
1453 recognise the file format, but unruu worked and extracted rom.zip,
1454 containing the new hboot firmware and a text file describing which
1455 devices it would work for.
</p
>
1457 <p
>Next, I needed to get the new firmware into the device. For this I
1458 followed some instructions
1459 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1460 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1461 machine with Debian testing:
</p
>
1463 <p
><pre
>
1464 adb reboot-bootloader
1465 fastboot oem rebootRUU
1466 fastboot flash zip rom.zip
1467 fastboot flash zip rom.zip
1469 </pre
></p
>
1471 <p
>The flash command apparently need to be done twice to take effect,
1472 as the first is just preparations and the second one do the flashing.
1473 The adb command is just to get to the boot loader menu, so turning the
1474 device on while holding volume down and the power button should work
1477 <p
>With the new hboot version in place I could start following the
1478 instructions on the HTC developer web site. I got the device token
1479 like this:
</p
>
1481 <p
><pre
>
1482 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1485 <p
>And once I got the unlock code via email, I could use it like
1488 <p
><pre
>
1489 fastboot flash unlocktoken Unlock_code.bin
1490 </pre
></p
>
1492 <p
>And with that final step in place, the phone was unlocked and I
1493 could start stuffing the software of my own choosing into the device.
1494 So far I only inserted a replacement recovery image to wipe the phone
1495 before I start. We will see what happen next. Perhaps I should
1496 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1501 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1502 <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>
1503 <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>
1504 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1505 <description><p
>For a while now, I have wanted to test
1506 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1507 said to provide end to end encrypted communication and several of my
1508 friends and family are already using it. As I by choice do not own a
1509 mobile phone, this proved to be harder than expected. And I wanted to
1510 have the source of the client and know that it was the code used on my
1511 machine. But yesterday I managed to get it working. I used the
1512 Github source, compared it to the source in
1513 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1514 Signal Chrome app
</a
> available from the Chrome web store, applied
1515 patches to use the production Signal servers, started the app and
1516 asked for the hidden
"register without a smart phone
" form. Here is
1517 the recipe how I did it.
</p
>
1519 <p
>First, I fetched the Signal desktop source from Github, using
1522 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1525 <p
>Next, I patched the source to use the production servers, to be
1526 able to talk to other Signal users:
</p
>
1529 cat
&lt;
&lt;EOF | patch -p0
1530 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1531 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1532 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1537 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1538 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1539 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1540 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1541 var messageReceiver;
1542 window.getSocketStatus = function() {
1543 if (messageReceiver) {
1544 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1545 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1546 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1549 'use strict
';
1550 - var BUILD_EXPIRATION =
0;
1551 + var BUILD_EXPIRATION =
1474492690000;
1553 window.extension = window.extension || {};
1558 <p
>The first part is changing the servers, and the second is updating
1559 an expiration timestamp. This timestamp need to be updated regularly.
1560 It is set
90 days in the future by the build process (Gruntfile.js).
1561 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1563 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1564 script to launch Signal in Chromium.
</p
>
1571 --proxy-server=
"socks://localhost:
9050" \
1572 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1575 <p
> The script start the app and configure Chromium to use the Tor
1576 SOCKS5 proxy to make sure those controlling the Signal servers (today
1577 Amazon and Whisper Systems) as well as those listening on the lines
1578 will have a harder time location my laptop based on the Signal
1579 connections if they use source IP address.
</p
>
1581 <p
>When the script starts, one need to follow the instructions under
1582 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1583 repository. I right clicked on the Signal window to get up the
1584 Chromium debugging tool, visited the
'Console
' tab and wrote
1585 'extension.install(
"standalone
")
' on the console prompt to get the
1586 registration form. Then I entered by land line phone number and
1587 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1588 repeated the verification code three times. After entering the number
1589 into the verification code field in the form, I could start using
1590 Signal from my laptop.
1592 <p
>As far as I can tell, The Signal app will leak who is talking to
1593 whom and thus who know who to those controlling the central server,
1594 but such leakage is hard to avoid with a centrally controlled server
1595 setup. It is something to keep in mind when using Signal - the
1596 content of your chats are harder to intercept, but the meta data
1597 exposing your contact network is available to people you do not know.
1598 So better than many options, but not great. And sadly the usage is
1599 connected to my land line, thus allowing those controlling the server
1600 to associate it to my home and person. I would prefer it if only
1601 those I knew could tell who I was on Signal. There are options
1602 avoiding such information leakage, but most of my friends are not
1603 using them, so I am stuck with Signal for now.
</p
>
1605 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1607 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1608 and updated recipe for using the Signal app without a mobile
1609 phone
</a
>.
</p
>
1614 <title>The new
"best
" multimedia player in Debian?
</title>
1615 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1616 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1617 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1618 <description><p
>When I set out a few weeks ago to figure out
1619 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1620 multimedia player in Debian claimed to support most file formats /
1621 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1622 the various players claimed support for. The range was from
55 to
130
1623 MIME types. I suspect most media formats are supported by all
1624 players, but this is not really reflected in the MimeTypes values in
1625 their desktop files. There are probably also some bogus MIME types
1626 listed, but it is hard to identify which one this is.
</p
>
1628 <p
>Anyway, in the mean time I got in touch with upstream for some of
1629 the players suggesting to add more MIME types to their desktop files,
1630 and decided to spend some time myself improving the situation for my
1631 favorite media player VLC. The fixes for VLC entered Debian unstable
1632 yesterday. The complete list of MIME types can be seen on the
1633 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1634 player MIME type support status
</a
> Debian wiki page.
</p
>
1636 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1637 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1638 kmplayer. I am sure some of the other players desktop files support
1639 several of the formats currently listed as working only with vlc,
1640 toten and parole.
</p
>
1642 <p
>A sad observation is that only
14 MIME types are listed as
1643 supported by all the tested multimedia players in Debian in their
1644 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1645 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1646 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1647 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1648 it sad that video/ogg and video/webm is not supported by all the media
1649 players in Debian. As far as I can tell, all of them can handle both
1655 <title>A program should be able to open its own files on Linux
</title>
1656 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1657 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1658 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1659 <description><p
>Many years ago, when koffice was fresh and with few users, I
1660 decided to test its presentation tool when making the slides for a
1661 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1662 wrote the first draft of the slides, saved the result and went to bed
1663 the day before I would give the talk. The next day I took a plane to
1664 the location where the meeting should take place, and on the plane I
1665 started up koffice again to polish the talk a bit, only to discover
1666 that kpresenter refused to load its own data file. I cursed a bit and
1667 started making the slides again from memory, to have something to
1668 present when I arrived. I tested that the saved files could be
1669 loaded, and the day seemed to be rescued. I continued to polish the
1670 slides until I suddenly discovered that the saved file could no longer
1671 be loaded into kpresenter. In the end I had to rewrite the slides
1672 three times, condensing the content until the talk became shorter and
1673 shorter. After the talk I was able to pinpoint the problem
&ndash;
1674 kpresenter wrote inline images in a way itself could not understand.
1675 Eventually that bug was fixed and kpresenter ended up being a great
1676 program to make slides. The point I
'm trying to make is that we
1677 expect a program to be able to load its own data files, and it is
1678 embarrassing to its developers if it can
't.
</p
>
1680 <p
>Did you ever experience a program failing to load its own data
1681 files from the desktop file browser? It is not a uncommon problem. A
1682 while back I discovered that the screencast recorder
1683 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1684 browser would refuse to open. No video player claimed to understand
1685 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1686 returning the application/ogg MIME type, which no video player I had
1687 installed listed as a MIME type they would understand. I asked for
1688 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1689 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1690 several video players to add video/ogg to their desktop files, to give
1691 the file browser an idea what to do about Ogg Theora files. After a
1692 while, the desktop file browsers in Debian started to handle the
1693 output from gtk-recordmydesktop properly.
</p
>
1695 <p
>But history repeats itself. A few days ago I tested the music
1696 system Rosegarden again, and I discovered that the KDE and xfce file
1697 browsers did not know what to do with the Rosegarden project files
1698 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1699 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1700 included in the next upload. To increase the chance of me remembering
1701 how to fix the problem next time some program fail to load its files
1702 from the file browser, here are some notes on how to fix it.
</p
>
1704 <p
>The file browsers in Debian in general operates on MIME types.
1705 There are two sources for the MIME type of a given file. The output from
1706 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1707 shared MIME type registry (under /usr/share/mime/). The file MIME
1708 type is mapped to programs supporting the MIME type, and this
1709 information is collected from
1710 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1711 desktop files
</a
> available in /usr/share/applications/. If there is
1712 one desktop file claiming support for the MIME type of the file, it is
1713 activated when asking to open a given file. If there are more, one
1714 can normally select which one to use by right-clicking on the file and
1715 selecting the wanted one using
'Open with
' or similar. In general
1716 this work well. But it depend on each program picking a good MIME
1718 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1719 MIME type registered with IANA
</a
>), file and/or the shared MIME
1720 registry recognizing the file and the desktop file to list the MIME
1721 type in its list of supported MIME types.
</p
>
1723 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1724 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1725 Shared MIME database
</a
> look like this:
</p
>
1727 <p
><blockquote
><pre
>
1728 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1729 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1730 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1731 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1732 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1733 &lt;glob pattern=
"*.rg
"/
&gt;
1734 &lt;/mime-type
&gt;
1735 &lt;/mime-info
&gt;
1736 </pre
></blockquote
></p
>
1738 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1739 (it is a gzipped XML file). Note, it is much better to use an
1740 official MIME type registered with IANA than it is to make up ones own
1741 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1743 <p
>The desktop file of the rosegarden program failed to list
1744 audio/x-rosegarden in its list of supported MIME types, causing the
1745 file browsers to have no idea what to do with *.rg files:
</p
>
1747 <p
><blockquote
><pre
>
1748 % grep Mime /usr/share/applications/rosegarden.desktop
1749 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1750 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1752 </pre
></blockquote
></p
>
1754 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1755 MimeType= line.
</p
>
1757 <p
>If you run into a file which fail to open the correct program when
1758 selected from the file browser, please check out the output from
1759 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1760 MIME type is registered somewhere under /usr/share/mime/ and check
1761 that some desktop file under /usr/share/applications/ is claiming
1762 support for this MIME type. If not, please report a bug to have it
1768 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1769 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1770 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1771 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1772 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1773 system
</a
> is a user-focused solution in Debian for handling hardware
1774 related packages. The idea is to have a database of mappings between
1775 hardware and packages, and pop up a dialog suggesting for the user to
1776 install the packages to use a given hardware dongle. Some use cases
1777 are when you insert a Yubikey, it proposes to install the software
1778 needed to control it; when you insert a braille reader list it
1779 proposes to install the packages needed to send text to the reader;
1780 and when you insert a ColorHug screen calibrator it suggests to
1781 install the driver for it. The system work well, and even have a few
1782 command line tools to install firmware packages and packages for the
1783 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1785 <p
>The system was initially written using aptdaemon, because I found
1786 good documentation and example code on how to use it. But aptdaemon
1787 is going away and is generally being replaced by
1788 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1789 so Isenkram needed a rewrite. And today, thanks to the great patch
1790 from my college Sunil Mohan Adapa in the FreedomBox project, the
1791 rewrite finally took place. I
've just uploaded a new version of
1792 Isenkram into Debian Unstable with the patch included, and the default
1793 for the background daemon is now to use PackageKit. To check it out,
1794 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1795 and see if it is recognised.
</p
>
1797 <p
>If you want to know what kind of packages isenkram would propose for
1798 the machine it is running on, you can check out the isenkram-lookup
1799 program. This is what it look like on a Thinkpad X230:
</p
>
1801 <p
><blockquote
><pre
>
1817 </pre
></blockquote
></p
>
1819 <p
>The hardware mappings come from several places. The preferred way
1820 is for packages to announce their hardware support using
1821 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1822 cross distribution appstream system
</a
>.
1824 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1825 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1830 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1831 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1832 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1833 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1834 <description><p
>Yesterday I updated the
1835 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1836 package in Debian
</a
> with a few patches sent to me by skilled and
1837 enterprising users. There were some nice user and visible changes.
1838 First of all, both desktop menu entries now work. A design flaw in
1839 one of the script made the history graph fail to show up (its PNG was
1840 dumped in ~/.xsession-errors) if no controlling TTY was available.
1841 The script worked when called from the command line, but not when
1842 called from the desktop menu. I changed this to look for a DISPLAY
1843 variable or a TTY before deciding where to draw the graph, and now the
1844 graph window pop up as expected.
</p
>
1846 <p
>The next new feature is a discharge rate estimator in one of the
1847 graphs (the one showing the last few hours). New is also the user of
1848 colours showing charging in blue and discharge in red. The percentages
1849 of this graph is relative to last full charge, not battery design
1852 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1854 <p
>The other graph show the entire history of the collected battery
1855 statistics, comparing it to the design capacity of the battery to
1856 visualise how the battery life time get shorter over time. The red
1857 line in this graph is what the previous graph considers
100 percent:
1859 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1861 <p
>In this graph you can see that I only charge the battery to
80
1862 percent of last full capacity, and how the capacity of the battery is
1863 shrinking. :(
</p
>
1865 <p
>The last new feature is in the collector, which now will handle
1866 more hardware models. On some hardware, Linux power supply
1867 information is stored in /sys/class/power_supply/ACAD/, while the
1868 collector previously only looked in /sys/class/power_supply/AC/. Now
1869 both are checked to figure if there is power connected to the
1872 <p
>If you are interested in how your laptop battery is doing, please
1874 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1875 in Debian unstable, or rebuild it on Jessie to get it working on
1876 Debian stable. :) The upstream source is available from
<a
1877 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1878 Patches are very welcome.
</p
>
1880 <p
>As usual, if you use Bitcoin and want to show your support of my
1881 activities, please send Bitcoin donations to my address
1882 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1887 <title>Debian now with ZFS on Linux included
</title>
1888 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1889 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1890 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1891 <description><p
>Today, after many years of hard work from many people,
1892 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1893 Debian. The package status can be seen on
1894 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1895 for zfs-linux
</a
>. and
1896 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1897 team status page
</a
>. If you want to help out, please join us.
1898 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1899 source code
</a
> is available via git on Alioth. It would also be
1900 great if you could help out with
1901 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1902 it is an important piece of the puzzle to get ZFS working.
</p
>
1907 <title>What is the best multimedia player in Debian?
</title>
1908 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1909 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1910 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1911 <description><p
><strong
>Where I set out to figure out which multimedia player in
1912 Debian claim support for most file formats.
</strong
></p
>
1914 <p
>A few years ago, I had a look at the media support for Browser
1915 plugins in Debian, to get an idea which plugins to include in Debian
1916 Edu. I created a script to extract the set of supported MIME types
1917 for each plugin, and used this to find out which multimedia browser
1918 plugin supported most file formats / media types.
1919 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1920 result
</a
> can still be seen on the Debian wiki, even though it have
1921 not been updated for a while. But browser plugins are less relevant
1922 these days, so I thought it was time to look at standalone
1925 <p
>A few days ago I was tired of VLC not being listed as a viable
1926 player when I wanted to play videos from the Norwegian National
1927 Broadcasting Company, and decided to investigate why. The cause is a
1928 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1929 desktop file
</a
>. In the process I wrote a script to compare the set
1930 of MIME types announced in the desktop file and the browser plugin,
1931 only to discover that there is quite a large difference between the
1932 two for VLC. This discovery made me dig up the script I used to
1933 compare browser plugins, and adjust it to compare desktop files
1934 instead, to try to figure out which multimedia player in Debian
1935 support most file formats.
</p
>
1937 <p
>The result can be seen on the Debian Wiki, as
1938 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1939 table listing all MIME types supported by one of the packages included
1940 in the table
</a
>, with the package supporting most MIME types being
1941 listed first in the table.
</p
>
1943 </p
>The best multimedia player in Debian? It is totem, followed by
1944 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1945 kmplayer. Time for the other players to update their announced MIME
1951 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1952 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1953 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1954 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1955 <description>A friend of mine made me aware of
1956 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1957 handheld computer which will be delivered with Debian preinstalled. I
1958 would love to get one of those for my birthday. :)
</p
>
1960 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1961 plugs and many others connectors, and include a full keyboard and a
5"
1962 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1963 day of battery life time, but I have not seen any independent tests
1964 confirming this. The vendor is still collecting preorders, and the
1965 last I heard last night was that
22 more orders were needed before
1966 production started.
</p
>
1968 <p
>As far as I know, this is the first handheld preinstalled with
1969 Debian. Please let me know if you know of any others. Is it the
1970 first computer being sold with Debian preinstalled?
</p
>
1975 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1976 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1977 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1978 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1979 <description><p
>During this weekends
1980 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1981 squashing party and developer gathering
</a
>, we decided to do our part
1982 to make sure there are good books about Debian available in Norwegian
1983 Bokmål, and got in touch with the people behind the
1984 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1985 project
</a
> to get started. If you want to help out, please start
1987 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1988 hosted weblate project page
</a
>, and get in touch using
1989 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1990 translators mailing list
</a
>. Please also check out
1991 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1992 contributors
</a
>.
</p
>
1994 <p
>The book is already available on paper in English, French and
1995 Japanese, and our goal is to get it available on paper in Norwegian
1996 Bokmål too. In addition to the paper edition, there are also EPUB and
1997 Mobi versions available. And there are incomplete translations
1998 available for many more languages.
</p
>
2003 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2004 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2005 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2006 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2007 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2008 packages in Debian, and was quite surprised with what I found. I use
2009 ZFS myself at home, but did not really expect many others to do so.
2010 But I might be wrong.
</p
>
2012 <p
>According to
2013 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2014 results for spl-linux
</a
>, there are
1019 Debian installations, or
2015 0.53% of the population, with the package installed. As far as I know
2016 the only use of the spl-linux package is as a support library for ZFS
2017 on Linux, so I use it here as proxy for measuring the number of ZFS
2018 installation on Linux in Debian. In the kFreeBSD variant of Debian
2019 the ZFS feature is already available, and there
2020 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2021 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2022 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2024 <p
>But even though the Debian project leader Lucas Nussbaum
2025 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2026 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2027 cleared, the package is still not in Debian. The package is again in
2028 the NEW queue. Several uploads have been rejected so far because the
2029 debian/copyright file was incomplete or wrong, but there is no reason
2030 to give up. The current status can be seen on
2031 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2032 team status page
</a
>, and
2033 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2034 source code
</a
> is available on Alioth.
</p
>
2036 <p
>As I want ZFS to be included in next version of Debian to make sure
2037 my home server can function in the future using only official Debian
2038 packages, and the current blocker is to get the debian/copyright file
2039 accepted by the FTP masters in Debian, I decided a while back to try
2040 to help out the team. This was the background for my blog post about
2041 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2042 updating and checking debian/copyright semi-automatically
</a
>, and I
2043 used the techniques I explored there to try to find any errors in the
2044 copyright file. It is not very easy to check every one of the around
2045 2000 files in the source package, but I hope we this time got it
2046 right. If you want to help out, check out the git source and try to
2047 find missing entries in the debian/copyright file.
</p
>
2052 <title>Full battery stats collector is now available in Debian
</title>
2053 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2055 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2056 <description><p
>Since this morning, the battery-stats package in Debian include an
2057 extended collector that will collect the complete battery history for
2058 later processing and graphing. The original collector store the
2059 battery level as percentage of last full level, while the new
2060 collector also record battery vendor, model, serial number, design
2061 full level, last full level and current battery level. This make it
2062 possible to predict the lifetime of the battery as well as visualise
2063 the energy flow when the battery is charging or discharging.
</p
>
2065 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2066 in the version
0.5.1 package in unstable. Get the new battery level graph
2067 and lifetime prediction by running:
2069 <p
><pre
>
2070 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2071 </pre
></p
>
2073 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2075 <p
>The flow in/out of the battery can be seen by running (no menu
2076 entry yet):
</p
>
2078 <p
><pre
>
2079 /usr/share/battery-stats/battery-stats-graph-flow
2080 </pre
></p
>
2082 <p
>I
'm not quite happy with the way the data is visualised, at least
2083 when there are few data points. The graphs look a bit better with a
2084 few years of data.
</p
>
2086 <p
>A while back one important feature I use in the battery stats
2087 collector broke in Debian. The scripts in
2088 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2089 suspect it happened when Jessie started using systemd, but I do not
2090 know. The issue is reported as
2091 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2092 pm-utils. I managed to work around it by adding an udev rule to call
2093 the collector script every time the power connector is connected and
2094 disconnected. With this fix in place it was finally time to make a
2095 new release of the package, and get it into Debian.
</p
>
2097 <p
>If you are interested in how your laptop battery is doing, please
2099 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2100 in Debian unstable, or rebuild it on Jessie to get it working on
2101 Debian stable. :) The upstream source is available from
2102 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2103 As always, patches are very welcome.
</p
>
2108 <title>Making battery measurements a little easier in Debian
</title>
2109 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2110 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2111 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2112 <description><p
>Back in September, I blogged about
2113 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2114 system I wrote to collect statistics about my laptop battery
</a
>, and
2115 how it showed the decay and death of this battery (now replaced). I
2116 created a simple deb package to handle the collection and graphing,
2117 but did not want to upload it to Debian as there were already
2118 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2119 package in Debian
</a
> that should do the same thing, and I did not see
2120 a point of uploading a competing package when battery-stats could be
2121 fixed instead. I reported a few bugs about its non-function, and
2122 hoped someone would step in and fix it. But no-one did.
</p
>
2124 <p
>I got tired of waiting a few days ago, and took matters in my own
2125 hands. The end result is that I am now the new upstream developer of
2126 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2127 battery-stats in Debian, and the package in Debian unstable is finally
2128 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2129 information provided by the Linux kernel. If you install the
2130 battery-stats package from unstable now, you will be able to get a
2131 graph of the current battery fill level, to get some idea about the
2132 status of the battery. The source package build and work just fine in
2133 Debian testing and stable (and probably oldstable too, but I have not
2134 tested). The default graph you get for that system look like this:
</p
>
2136 <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
>
2138 <p
>My plans for the future is to merge my old scripts into the
2139 battery-stats package, as my old scripts collected a lot more details
2140 about the battery. The scripts are merged into the upstream
2141 battery-stats git repository already, but I am not convinced they work
2142 yet, as I changed a lot of paths along the way. Will have to test a
2143 bit more before I make a new release.
</p
>
2145 <p
>I will also consider changing the file format slightly, as I
2146 suspect the way I combine several values into one field might make it
2147 impossible to know the type of the value when using it for processing
2148 and graphing.
</p
>
2150 <p
>If you would like I would like to keep an close eye on your laptop
2151 battery, check out the battery-stats package in
2152 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2154 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2155 I would love some help to improve the system further.
</p
>
2160 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2161 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2162 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2163 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2164 <description><p
>Making packages for Debian requires quite a lot of attention to
2165 details. And one of the details is the content of the
2166 debian/copyright file, which should list all relevant licenses used by
2167 the code in the package in question, preferably in
2168 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2169 readable DEP5 format
</a
>.
</p
>
2171 <p
>For large packages with lots of contributors it is hard to write
2172 and update this file manually, and if you get some detail wrong, the
2173 package is normally rejected by the ftpmasters. So getting it right
2174 the first time around get the package into Debian faster, and save
2175 both you and the ftpmasters some work.. Today, while trying to figure
2176 out what was wrong with
2177 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2178 zfsonlinux copyright file
</a
>, I decided to spend some time on
2179 figuring out the options for doing this job automatically, or at least
2180 semi-automatically.
</p
>
2182 <p
>Lucikly, there are at least two tools available for generating the
2183 file based on the code in the source package,
2184 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2185 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2186 not sure which one of them came first, but both seem to be able to
2187 create a sensible draft file. As far as I can tell, none of them can
2188 be trusted to get the result just right, so the content need to be
2189 polished a bit before the file is OK to upload. I found the debmake
2191 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2192 blog posts from
2014</a
>.
2194 <p
>To generate using debmake, use the -cc option:
2196 <p
><pre
>
2197 debmake -cc
> debian/copyright
2198 </pre
></p
>
2200 <p
>Note there are some problems with python and non-ASCII names, so
2201 this might not be the best option.
</p
>
2203 <p
>The cme option is based on a config parsing library, and I found
2205 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2206 blog post from
2015</a
>. To generate using cme, use the
'update
2207 dpkg-copyright
' option:
2209 <p
><pre
>
2210 cme update dpkg-copyright
2211 </pre
></p
>
2213 <p
>This will create or update debian/copyright. The cme tool seem to
2214 handle UTF-
8 names better than debmake.
</p
>
2216 <p
>When the copyright file is created, I would also like some help to
2217 check if the file is correct. For this I found two good options,
2218 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2219 to focus on license types and file matching, and is able to detect
2220 ineffective blocks in the copyright file. The latter reports missing
2221 copyright holders and years, but was confused by inconsistent license
2222 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2223 fix all issues reported by them before uploading. But I do not know
2224 if the tools and the ftpmasters agree on what is important to fix in a
2225 copyright file, so the package might still be rejected.
</p
>
2227 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2228 will read through the source and try to find all copyright statements.
2229 It is not comparing the result to the content of debian/copyright, but
2230 can be useful when verifying the content of the copyright file.
</p
>
2232 <p
>Are you aware of better tools in Debian to create and update
2233 debian/copyright file. Please let me know, or blog about it on
2234 planet.debian.org.
</p
>
2236 <p
>As usual, if you use Bitcoin and want to show your support of my
2237 activities, please send Bitcoin donations to my address
2238 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2240 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2241 on how to use licensecheck and cdbs to create a draft copyright file
2243 <p
><pre
>
2244 licensecheck --copyright -r `find * -type f` | \
2245 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2246 </pre
></p
>
2248 <p
>He mentioned that he normally check the generated file into the
2249 version control system to make it easier to discover license and
2250 copyright changes in the upstream source. I will try to do the same
2251 with my packages in the future.
</p
>
2253 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2254 against using -quiet for new users, so I removed it from the proposed
2255 command line.
</p
>
2260 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2261 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2262 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2263 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2264 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2265 is taking shape in Debian, and one provided feature is a very
2266 convenient way to tell you which package to install to make a given
2267 firmware file available when the kernel is looking for it. This can
2268 be done using apt-file too, but that is for someone else to blog
2271 <p
>Here is a small recipe to find the package with a given firmware
2272 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2273 picked from the set of firmware announced using appstream in Debian
2274 unstable. In general you would be looking for the firmware requested
2275 by the kernel during kernel module loading. To find the package
2276 providing the example file, do like this:
</p
>
2278 <blockquote
><pre
>
2279 % apt install appstream
2283 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2284 awk
'/Package:/ {print $
2}
'
2287 </pre
></blockquote
>
2289 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2290 appstream wiki
</a
> page to learn how to embed the package metadata in
2291 a way appstream can use.
</p
>
2293 <p
>This same approach can be used to find any package supporting a
2294 given MIME type. This is very useful when you get a file you do not
2295 know how to handle. First find the mime type using
<tt
>file
2296 --mime-type
</tt
>, and next look up the package providing support for
2297 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2298 and you can find all packages handling this type like this:
</p
>
2300 <blockquote
><pre
>
2301 % apt install appstream
2305 % appstreamcli what-provides mimetype image/svg+xml | \
2306 awk
'/Package:/ {print $
2}
'
2328 </pre
></blockquote
>
2330 <p
>I believe the MIME types are fetched from the desktop file for
2331 packages providing appstream metadata.
</p
>
2336 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2337 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2338 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2339 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2340 <description><p
>Most people seem not to realise that every time they walk around
2341 with the computerised radio beacon known as a mobile phone their
2342 position is tracked by the phone company and often stored for a long
2343 time (like every time a SMS is received or sent). And if their
2344 computerised radio beacon is capable of running programs (often called
2345 mobile apps) downloaded from the Internet, these programs are often
2346 also capable of tracking their location (if the app requested access
2347 during installation). And when these programs send out information to
2348 central collection points, the location is often included, unless
2349 extra care is taken to not send the location. The provided
2350 information is used by several entities, for good and bad (what is
2351 good and bad, depend on your point of view). What is certain, is that
2352 the private sphere and the right to free movement is challenged and
2353 perhaps even eradicated for those announcing their location this way,
2354 when they share their whereabouts with private and public
2357 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2359 <p
>The phone company logs provide a register of locations to check out
2360 when one want to figure out what the tracked person was doing. It is
2361 unavailable for most of us, but provided to selected government
2362 officials, company staff, those illegally buying information from
2363 unfaithful servants and crackers stealing the information. But the
2364 public information can be collected and analysed, and a free software
2365 tool to do so is called
2366 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2367 discovered it when I read
2368 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2369 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2370 November
2014, and decided to check if it was available in Debian.
2371 The python program was in Debian, but
2372 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2373 Debian
</a
> was completely broken and practically unmaintained. I
2374 uploaded a new version which did not work quite right, but did not
2375 have time to fix it then. This Christmas I decided to finally try to
2376 get Creepy operational in Debian. Now a fixed version is available in
2377 Debian unstable and testing, and almost all Debian specific patches
2379 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2381 <p
>The Creepy program visualises geolocation information fetched from
2382 Twitter, Instagram, Flickr and Google+, and allow one to get a
2383 complete picture of every social media message posted recently in a
2384 given area, or track the movement of a given individual across all
2385 these services. Earlier it was possible to use the search API of at
2386 least some of these services without identifying oneself, but these
2387 days it is impossible. This mean that to use Creepy, you need to
2388 configure it to log in as yourself on these services, and provide
2389 information to them about your search interests. This should be taken
2390 into account when using Creepy, as it will also share information
2391 about yourself with the services.
</p
>
2393 <p
>The picture above show the twitter messages sent from (or at least
2394 geotagged with a position from) the city centre of Oslo, the capital
2395 of Norway. One useful way to use Creepy is to first look at
2396 information tagged with an area of interest, and next look at all the
2397 information provided by one or more individuals who was in the area.
2398 I tested it by checking out which celebrity provide their location in
2399 twitter messages by checkout out who sent twitter messages near a
2400 Norwegian TV station, and next could track their position over time,
2401 making it possible to locate their home and work place, among other
2402 things. A similar technique have been
2403 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2404 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2405 tool to discover lying governments, and a useful tool to help people
2406 understand the value of the private information they provide to the
2409 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2410 it depend on several python modules currently missing in Jessie (at
2411 least python-instagram, python-flickrapi and
2412 python-requests-toolbelt).
</p
>
2414 <p
>(I have uploaded
2415 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2416 screenshots.debian.net
</a
> and licensed it under the same terms as the
2417 Creepy program in Debian.)
</p
>
2422 <title>Always download Debian packages using Tor - the simple recipe
</title>
2423 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2424 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2425 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2426 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2427 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2428 that those listening on the Internet lines would have good reason to
2429 believe a computer have a given security hole
</a
> if it download a
2430 security fix from a Debian mirror. This is a good reason to always
2431 use encrypted connections to the Debian mirror, to make sure those
2432 listening do not know which IP address to attack. In August, Richard
2433 Hartmann observed that encryption was not enough, when it was possible
2434 to interfere download size to security patches or the fact that
2435 download took place shortly after a security fix was released, and
2436 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2437 to always use Tor to download packages from the Debian mirror
</a
>. He
2438 was not the first to propose this, as the
2439 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2440 package by Tim Retout already existed to make it easy to convince apt
2441 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2442 aware of that package when I read the blog post from Richard.
</p
>
2444 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2445 sysadmins, and he set up a Tor hidden service on one of the central
2446 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2447 it possible to download packages directly between two tor nodes,
2448 making sure the network traffic always were encrypted.
</p
>
2450 <p
>Here is a short recipe for enabling this on your machine, by
2451 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2452 urls with tor+http and tor+https, and using the hidden service instead
2453 of the official Debian mirror site. I recommend installing
2454 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2455 done in /etc/.
</p
>
2457 <blockquote
><pre
>
2458 apt install apt-transport-tor
2459 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2460 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2461 </pre
></blockquote
>
2463 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2464 the sed commands for these too. The sed command is assuming your are
2465 using the ftp.debian.org Debian mirror. Adjust the command (or just
2466 edit the file manually) to match your mirror.
</p
>
2468 <p
>This work in Debian Jessie and later. Note that tools like
2469 <tt
>apt-file
</tt
> only recently started using the apt transport
2470 system, and do not work with these tor+http URLs. For
2471 <tt
>apt-file
</tt
> you need the version currently in experimental,
2472 which need a recent apt version currently only in unstable. So if you
2473 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2475 <p
>Another advantage from this change is that your machine will start
2476 using Tor regularly and at fairly random intervals (every time you
2477 update the package lists or upgrade or install a new package), thus
2478 masking other Tor traffic done from the same machine. Using Tor will
2479 become normal for the machine in question.
</p
>
2481 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2482 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2483 enabled. It would be great if it was the default on any Debian
2489 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2490 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2491 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2492 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2493 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2494 call the car license plate numbers in those days. I would write the
2495 numbers down in my little book and compare notes with the other kids
2496 to see how many region codes we had seen and if we had seen some
2497 exotic or special region codes and numbers. It was a fun game to pass
2498 time, as we kids have plenty of it.
</p
>
2500 <p
>A few days I came across
2501 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2502 project
</a
>, a free software project to automatically discover and
2503 report license plates in images and video streams, and provide the
2504 "car numbers
" in a machine readable format. I
've been looking for
2505 such system for a while now, because I believe it is a bad idea that the
2506 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2507 number plate recognition
</a
> tool only is available in the hands of
2508 the powerful, and want it to be available also for the powerless to
2509 even the score when it comes to surveillance and sousveillance. I
2510 discovered the developer
2511 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2512 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2513 help him get it into shape to get the package uploaded into the Debian
2516 <p
>Today we finally managed to get the package into shape and uploaded
2517 it into Debian, where it currently
2518 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2519 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2521 <p
>I guess you are wondering why on earth such tool would be useful
2522 for the common folks, ie those not running a large government
2523 surveillance system? Well, I plan to put it in a computer on my bike
2524 and in my car, tracking the cars nearby and allowing me to be notified
2525 when number plates on my watch list are discovered. Another use case
2526 was suggested by a friend of mine, who wanted to set it up at his home
2527 to open the car port automatically when it discovered the plate on his
2528 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2529 capable of placing his license plate number of a piece of cardboard to
2530 open his car port, men replied that it was always unlocked anyway. I
2531 guess for such use case it make sense. I am sure there are other use
2532 cases too, for those with imagination and a vision.
</p
>
2534 <p
>If you want to build your own version of the Debian package, check
2535 out the upstream git source and symlink ./distros/debian to ./debian/
2536 before running
"debuild
" to build the source. Or wait a bit until the
2537 package show up in unstable.
</p
>
2542 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2543 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2545 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2546 <description><p
>Around three years ago, I created
2547 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2548 system
</a
> to get a more practical solution in Debian for handing
2549 hardware related packages. A GUI system in the isenkram package will
2550 present a pop-up dialog when some hardware dongle supported by
2551 relevant packages in Debian is inserted into the machine. The same
2552 lookup mechanism to detect packages is available as command line
2553 tools in the isenkram-cli package. In addition to mapping hardware,
2554 it will also map kernel firmware files to packages and make it easy to
2555 install needed firmware packages automatically. The key for this
2556 system to work is a good way to map hardware to packages, in other
2557 words, allow packages to announce what hardware they will work
2560 <p
>I started by providing data files in the isenkram source, and
2561 adding code to download the latest version of these data files at run
2562 time, to ensure every user had the most up to date mapping available.
2563 I also added support for storing the mapping in the Packages file in
2564 the apt repositories, but did not push this approach because while I
2565 was trying to figure out how to best store hardware/package mappings,
2566 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2567 appstream system
</a
> was announced. I got in touch and suggested to
2568 add the hardware mapping into that data set to be able to use
2569 appstream as a data source, and this was accepted at least for the
2570 Debian version of appstream.
</p
>
2572 <p
>A few days ago using appstream in Debian for this became possible,
2573 and today I uploaded a new version
0.20 of isenkram adding support for
2574 appstream as a data source for mapping hardware to packages. The only
2575 package so far using appstream to announce its hardware support is my
2576 pymissile package. I got help from Matthias Klumpp with figuring out
2577 how do add the required
2578 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2579 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2580 this content:
</p
>
2582 <blockquote
><pre
>
2583 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2584 &lt;component
&gt;
2585 &lt;id
&gt;pymissile
&lt;/id
&gt;
2586 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2587 &lt;name
&gt;pymissile
&lt;/name
&gt;
2588 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2589 &lt;description
&gt;
2591 Pymissile provides a curses interface to control an original
2592 Marks and Spencer / Striker USB Missile Launcher, as well as a
2593 motion control script to allow a webcamera to control the
2596 &lt;/description
&gt;
2597 &lt;provides
&gt;
2598 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2599 &lt;/provides
&gt;
2600 &lt;/component
&gt;
2601 </pre
></blockquote
>
2603 <p
>The key for isenkram is the component/provides/modalias value,
2604 which is a glob style match rule for hardware specific strings
2605 (modalias strings) provided by the Linux kernel. In this case, it
2606 will map to all USB devices with vendor code
1130 and product code
2609 <p
>Note, it is important that the license of all the metadata files
2610 are compatible to have permissions to aggregate them into archive wide
2611 appstream files. Matthias suggested to use MIT or BSD licenses for
2612 these files. A challenge is figuring out a good id for the data, as
2613 it is supposed to be globally unique and shared across distributions
2614 (in other words, best to coordinate with upstream what to use). But
2615 it can be changed later or, so we went with the package name as
2616 upstream for this project is dormant.
</p
>
2618 <p
>To get the metadata file installed in the correct location for the
2619 mirror update scripts to pick it up and include its content the
2620 appstream data source, the file must be installed in the binary
2621 package under /usr/share/appdata/. I did this by adding the following
2622 line to debian/pymissile.install:
</p
>
2624 <blockquote
><pre
>
2625 debian/pymissile.metainfo.xml usr/share/appdata
2626 </pre
></blockquote
>
2628 <p
>With that in place, the command line tool isenkram-lookup will list
2629 all packages useful on the current computer automatically, and the GUI
2630 pop-up handler will propose to install the package not already
2631 installed if a hardware dongle is inserted into the machine in
2634 <p
>Details of the modalias field in appstream is available from the
2635 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2637 <p
>To locate the modalias values of all hardware present in a machine,
2638 try running this command on the command line:
</p
>
2640 <blockquote
><pre
>
2641 cat $(find /sys/devices/|grep modalias)
2642 </pre
></blockquote
>
2644 <p
>To learn more about the isenkram system, please check out
2645 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2646 blog posts tagged isenkram
</a
>.
</p
>
2651 <title>The GNU General Public License is not magic pixie dust
</title>
2652 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2654 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2655 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2656 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2657 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2658 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2659 I quote the blog post from Paul in full here with his permission:
<p
>
2663 <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
>
2666 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2668 The first step is to choose a
2669 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2672 The next step is, when someone fails to follow that copyleft license,
2673 <b
>it must be enforced
</b
><br/
>
2675 and its a simple fact of our modern society that such type of
2678 is incredibly expensive to do and incredibly difficult to do.
2681 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2682 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2683 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2684 0x57</a
></small
></p
>
2686 <p
>As the Debian Website
2687 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2688 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2689 imply, public domain and permissively licensed software can lead to
2690 the production of more proprietary software as people discover useful
2691 software, extend it and or incorporate it into their hardware or
2692 software products. Copyleft licenses such as the GNU GPL were created
2693 to close off this avenue to the production of proprietary software but
2694 such licenses are not enough. With the ongoing adoption of Free
2695 Software by individuals and groups, inevitably the community
's
2696 expectations of license compliance are violated, usually out of
2697 ignorance of the way Free Software works, but not always. As Karen
2698 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2699 Freedom
">FaiF
</a
>
2700 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2701 copyleft is nothing if no-one is willing and able to stand up in court
2702 to protect it. The reality of today
's world is that legal
2703 representation is expensive, difficult and time consuming. With
2704 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2705 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2706 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2707 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2708 of the Linux project, Debian and other groups against GPL violations.
2709 In March the SFC supported a
2710 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2711 by Christoph Hellwig
</a
> against VMware for refusing to
2712 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2713 with the GPL
</a
> in relation to their use of parts of the Linux
2714 kernel. Since then two of their sponsors pulled corporate funding and
2716 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2717 or cancelled their talks
</a
>. As a result they have decided to rely
2718 less on corporate funding and more on the broad community of
2719 individuals who support Free Software and copyleft. So the SFC has
2720 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2721 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2722 a community of folks who stand up for copyleft and the GPL by
2723 supporting their work on promoting and supporting copyleft and Free
2726 <p
>If you support Free Software,
2727 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2728 what the SFC do, agree with their
2729 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2730 principles
</a
>, are happy about their
2731 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2732 work on a project that is an SFC
2733 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2734 just want to stand up for copyleft, please join
2735 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2736 Allan Webber
</a
>,
2737 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2739 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2740 Bacon
</a
>, myself and
2741 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2743 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2744 next week your donation will be
2745 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2746 by an anonymous donor. Please also consider asking your employer to
2747 match your donation or become a sponsor of SFC. Don
't forget to
2748 spread the word about your support for SFC via email, your blog and or
2749 social media accounts.
</p
>
2753 <p
>I agree with Paul on this topic and just signed up as a Supporter
2754 of Software Freedom Conservancy myself. Perhaps you should be a
2755 supporter too?
</p
>
2760 <title>PGP key transition statement for key EE4E02F9
</title>
2761 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2762 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2763 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2764 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2765 set it up properly. I wanted to generate it offline and have it
2766 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2767 smart card
</a
> for daily use, and learning how to do it and finding
2768 time to sit down with an offline machine almost took forever. But
2769 finally I
've been able to complete the process, and have now moved
2770 from my old GPG key to a new GPG key. See
2771 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2772 full transition statement, signed with both my old and new key
</a
> for
2773 the details. This is my new key:
</p
>
2776 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2777 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2778 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2779 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2780 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2781 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2782 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2785 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2786 my old key.
</p
>
2788 <p
>If you signed my old key
2789 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2790 I
'd very much appreciate a signature on my new key, details and
2791 instructions in the transition statement. I m happy to reciprocate if
2792 you have a similarly signed transition statement to present.
</p
>
2797 <title>The life and death of a laptop battery
</title>
2798 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2799 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2800 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2801 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2802 But this do not last. The last few laptops gave me a feeling that
2803 within a year, the life time is just a fraction of what it used to be,
2804 and it slowly become painful to use the laptop without power connected
2805 all the time. Because of this, when I got a new Thinkpad X230 laptop
2806 about two years ago, I decided to monitor its battery state to have
2807 more hard facts when the battery started to fail.
</p
>
2809 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2811 <p
>First I tried to find a sensible Debian package to record the
2812 battery status, assuming that this must be a problem already handled
2813 by someone else. I found
2814 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2815 which collects statistics from the battery, but it was completely
2816 broken. I sent a few suggestions to the maintainer, but decided to
2817 write my own collector as a shell script while I waited for feedback
2819 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2820 blog post about the battery development on a MacBook Air
</a
> I also
2822 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2823 available in Debian.
</p
>
2825 <p
>I started my collector
2013-
07-
15, and it has been collecting
2826 battery stats ever since. Now my
2827 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2828 measurements, from the time the battery was working great until now,
2829 when it is unable to charge above
7% of original capacity. My
2830 collector shell script is quite simple and look like this:
</p
>
2835 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2837 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2838 logfile=/var/log/hjemmenett-battery-status.log
2840 files=
"manufacturer model_name technology serial_number \
2841 energy_full energy_full_design energy_now cycle_count status
"
2843 if [ ! -e
"$logfile
" ] ; then
2845 printf
"timestamp,
"
2847 printf
"%s,
" $f
2850 )
> "$logfile
"
2854 # Print complete message in one echo call, to avoid race condition
2855 # when several log processes run in parallel.
2856 msg=$(printf
"%s,
" $(date +%s); \
2857 for f in $files; do \
2858 printf
"%s,
" $(cat $f); \
2860 echo
"$msg
"
2863 cd /sys/class/power_supply
2866 (cd $bat
&& log_battery
>> "$logfile
")
2870 <p
>The script is called when the power management system detect a
2871 change in the power status (power plug in or out), and when going into
2872 and out of hibernation and suspend. In addition, it collect a value
2873 every
10 minutes. This make it possible for me know when the battery
2874 is discharging, charging and how the maximum charge change over time.
2875 The code for the Debian package
2876 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2877 available on github
</a
>.
</p
>
2879 <p
>The collected log file look like this:
</p
>
2882 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2883 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2885 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2886 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2889 <p
>I wrote a small script to create a graph of the charge development
2890 over time. This graph depicted above show the slow death of my laptop
2893 <p
>But why is this happening? Why are my laptop batteries always
2894 dying in a year or two, while the batteries of space probes and
2895 satellites keep working year after year. If we are to believe
2896 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2897 University
</a
>, the cause is me charging the battery whenever I have a
2898 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2899 all the time, but to stay below
90% of full charge most of the time.
2900 I
've been told that the Tesla electric cars
2901 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2902 the charge of their batteries to
80%
</a
>, with the option to charge to
2903 100% when preparing for a longer trip (not that I would want a car
2904 like Tesla where rights to privacy is abandoned, but that is another
2905 story), which I guess is the option we should have for laptops on
2906 Linux too.
</p
>
2908 <p
>Is there a good and generic way with Linux to tell the battery to
2909 stop charging at
80%, unless requested to charge to
100% once in
2910 preparation for a longer trip? I found
2911 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2912 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2913 80%
</a
>, but could not get it to work (kernel module refused to
2916 <p
>I wonder why the battery capacity was reported to be more than
100%
2917 at the start. I also wonder why the
"full capacity
" increases some
2918 times, and if it is possible to repeat the process to get the battery
2919 back to design capacity. And I wonder if the discharge and charge
2920 speed change over time, or if this stay the same. I did not yet try
2921 to write a tool to calculate the derivative values of the battery
2922 level, but suspect some interesting insights might be learned from
2925 <p
>Update
2015-
09-
24: I got a tip to install the packages
2926 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2927 packages instead of the tp-smapi-dkms package I had tried to use
2928 initially, and use
'tlp setcharge
40 80' to change when charging start
2929 and stop. I
've done so now, but expect my existing battery is toast
2930 and need to be replaced. The proposal is unfortunately Thinkpad
2936 <title>New laptop - some more clues and ideas based on feedback
</title>
2937 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2938 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2939 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2940 <description><p
>Several people contacted me after my previous blog post about my
2941 need for a new laptop, and provided very useful feedback. I wish to
2942 thank every one of these. Several pointed me to the possibility of
2943 fixing my X230, and I am already in the process of getting Lenovo to
2944 do so thanks to the on site, next day support contract covering the
2945 machine. But the battery is almost useless (I expect to replace it
2946 with a non-official battery) and I do not expect the machine to live
2947 for many more years, so it is time to plan its replacement. If I did
2948 not have a support contract, it was suggested to find replacement parts
2949 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2950 might present a language barrier as I do not understand French.
</p
>
2952 <p
>One tip I got was to use the
2953 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2954 compare laptop models. It seem to have more models available than
2955 prisjakt.no. Another tip I got from someone I know have similar
2956 keyboard preferences was that the HP EliteBook
840 keyboard is not
2957 very good, and this matches my experience with earlier EliteBook
2958 keyboards I tested. Because of this, I will not consider it any further.
2960 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2961 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2962 (which is missing from the X240), and is working fairly well with
2963 Debian Sid/Unstable according to
2964 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2965 got on the keyboard quality are not consistent. Some say the keyboard
2966 is good, others say it is ok, while others say it is not very good.
2967 Those with experience from X41 and and X60 agree that the X250
2968 keyboard is not as good as those trusty old laptops, and suggest I
2969 keep and fix my X230 instead of upgrading, or get a used X230 to
2970 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2971 activity and battery status, which is very convenient on my X230. I
'm
2972 also told that the CPU fan is running very often, making it a bit
2973 noisy. In any case, the X250 do not work out of the box with Debian
2974 Stable/Jessie, one of my requirements.
</p
>
2976 <p
>I have also gotten a few vendor proposals, one was
2977 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2978 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2979 The latter look very attractive to me.
</p
>
2981 <p
>Again, thank you all for the very useful feedback. It help a lot
2982 as I keep looking for a replacement.
</p
>
2984 <p
>Update
2015-
07-
06: I was recommended to check out the
2985 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2987 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2988 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2993 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2994 <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>
2995 <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>
2996 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2997 <description><p
>My primary work horse laptop is failing, and will need a
2998 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2999 started flickering yesterday, and I suspect the cause is a broken
3000 cable, as changing the angle of the screen some times get rid of the
3001 flickering.
</p
>
3003 <p
>My requirements have not really changed since I bought it, and is
3005 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3006 described them in
2013</a
>. The last time I bought a laptop, I had
3008 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3009 where I could select at least a few of the requirements (mouse pin,
3010 wifi, weight) and go through the rest manually. Three button mouse
3011 and a good keyboard is not available as an option, and all the three
3012 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3013 G2) lack three mouse buttons). It is also unclear to me how good the
3014 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3015 the keyboard, even if the quality and robustness in the X series have
3016 deteriorated since X41.
</p
>
3018 <p
>I wonder how I can find a sensible laptop when none of the options
3019 seem sensible to me? Are there better services around to search the
3020 set of available laptops for features? Please send me an email if you
3021 have suggestions.
</p
>
3023 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3024 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3025 of endorsed hardware
</a
>, which is useful background information.
</p
>
3030 <title>How to stay with sysvinit in Debian Jessie
</title>
3031 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3032 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3033 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3034 <description><p
>By now, it is well known that Debian Jessie will not be using
3035 sysvinit as its boot system by default. But how can one keep using
3036 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3038 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3039 Schubert
</a
> and
3040 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3043 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3044 keep sysvinit as your boot system, create a file
3045 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3046 you upgrade:
</p
>
3048 <p
><blockquote
><pre
>
3049 Package: systemd-sysv
3050 Pin: release o=Debian
3052 </pre
></blockquote
><p
>
3054 <p
>This file content will tell apt and aptitude to not consider
3055 installing systemd-sysv as part of any installation and upgrade
3056 solution when resolving dependencies, and thus tell it to avoid
3057 systemd as a default boot system. The end result should be that the
3058 upgraded system keep using sysvinit.
</p
>
3060 <p
>If you are installing Jessie for the first time, there is no way to
3061 get sysvinit installed by default (debootstrap used by
3062 debian-installer have no option for this), but one can tell the
3063 installer to switch to sysvinit before the first boot. Either by
3064 using a kernel argument to the installer, or by adding a line to the
3065 preseed file used. First, the kernel command line argument:
3067 <p
><blockquote
><pre
>
3068 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3069 </pre
></blockquote
><p
>
3071 <p
>Next, the line to use in a preseed file:
</p
>
3073 <p
><blockquote
><pre
>
3074 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3075 </pre
></blockquote
><p
>
3077 <p
>One can of course also do this after the first boot by installing
3078 the sysvinit-core package.
</p
>
3080 <p
>I recommend only using sysvinit if you really need it, as the
3081 sysvinit boot sequence in Debian have several hardware specific bugs
3082 on Linux caused by the fact that it is unpredictable when hardware
3083 devices show up during boot. But on the other hand, the new default
3084 boot system still have a few rough edges I hope will be fixed before
3085 Jessie is released.
</p
>
3087 <p
>Update
2014-
11-
26: Inspired by
3088 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3089 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3095 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3096 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3097 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3098 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3099 <description><p
>The right to communicate with your friends and family in private,
3100 without anyone snooping, is a right every citicen have in a liberal
3101 democracy. But this right is under serious attack these days.
</p
>
3103 <p
>A while back it occurred to me that one way to make the dragnet
3104 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3105 the whisleblower Snowden) more expensive for Internet email,
3106 is to deliver all email using SMTP via Tor. Such SMTP option would be
3107 a nice addition to the FreedomBox project if we could send email
3108 between FreedomBox machines without leaking metadata about the emails
3109 to the people peeking on the wire. I
3110 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3111 this on the FreedomBox project mailing list in October
</a
> and got a
3112 lot of useful feedback and suggestions. It also became obvious to me
3113 that this was not a novel idea, as the same idea was tested and
3114 documented by Johannes Berg as early as
2006, and both
3115 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3116 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3117 propose a similar method / protocol to pass emails between users.
</p
>
3119 <p
>To implement such system one need to set up a Tor hidden service
3120 providing the SMTP protocol on port
25, and use email addresses
3121 looking like username@hidden-service-name.onion. With such addresses
3122 the connections to port
25 on hidden-service-name.onion using Tor will
3123 go to the correct SMTP server. To do this, one need to configure the
3124 Tor daemon to provide the hidden service and the mail server to accept
3125 emails for this .onion domain. To learn more about Exim configuration
3126 in Debian and test the design provided by Johannes Berg in his FAQ, I
3127 set out yesterday to create a Debian package for making it trivial to
3128 set up such SMTP over Tor service based on Debian. Getting it to work
3129 were fairly easy, and
3130 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3131 source code for the Debian package
</a
> is available from github. I
3132 plan to move it into Debian if further testing prove this to be a
3133 useful approach.
</p
>
3135 <p
>If you want to test this, set up a blank Debian machine without any
3136 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3137 get rid of exim4). Install tor, clone the git repository mentioned
3138 above, build the deb and install it on the machine. Next, run
3139 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3140 the instructions to get the service up and running. Restart tor and
3141 exim when it is done, and test mail delivery using swaks like
3144 <p
><blockquote
><pre
>
3145 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3146 --to fbx@dutlqrrmjhtfa3vp.onion
3147 </pre
></blockquote
></p
>
3149 <p
>This will test the SMTP delivery using tor. Replace the email
3150 address with your own address to test your server. :)
</p
>
3152 <p
>The setup procedure is still to complex, and I hope it can be made
3153 easier and more automatic. Especially the tor setup need more work.
3154 Also, the package include a tor-smtp tool written in C, but its task
3155 should probably be rewritten in some script language to make the deb
3156 architecture independent. It would probably also make the code easier
3157 to review. The tor-smtp tool currently need to listen on a socket for
3158 exim to talk to it and is started using xinetd. It would be better if
3159 no daemon and no socket is needed. I suspect it is possible to get
3160 exim to run a command line tool for delivery instead of talking to a
3161 socket, and hope to figure out how in a future version of this
3164 <p
>Until I wipe my test machine, I can be reached using the
3165 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3166 SMTorP. :)
</p
>
3171 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3172 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3173 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3174 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3175 <description><p
>If you ever had to moderate a mailman list, like the ones on
3176 alioth.debian.org, you know the web interface is fairly slow to
3177 operate. First you visit one web page, enter the moderation password
3178 and get a new page shown with a list of all the messages to moderate
3179 and various options for each email address. This take a while for
3180 every list you moderate, and you need to do it regularly to do a good
3181 job as a list moderator. But there is a quick alternative,
3182 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3183 listadmin program
</a
>. It allow you to check lists for new messages
3184 to moderate in a fraction of a second. Here is a test run on two
3185 lists I recently took over:
</p
>
3187 <p
><blockquote
><pre
>
3188 % time listadmin xiph
3189 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3190 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3196 </pre
></blockquote
></p
>
3198 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3199 there are no message in the moderation queue. Every morning I
3200 currently moderate
68 mailman lists, and it normally take around two
3201 minutes. When I took over the two pkg-xiph lists above a few days
3202 ago, there were
400 emails waiting in the moderator queue. It took me
3203 less than
15 minutes to process them all using the listadmin
3206 <p
>If you install
3207 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3208 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3209 with content like this, the moderation task is a breeze:
</p
>
3211 <p
><blockquote
><pre
>
3212 username username@example.org
3215 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3218 adminurl https://{domain}/mailman/admindb/{list}
3219 mailman-list@lists.example.com
3222 other-list@otherserver.example.org
3223 </pre
></blockquote
></p
>
3225 <p
>There are other options to set as well. Check the manual page to
3226 learn the details.
</p
>
3228 <p
>If you are forced to moderate lists on a mailman installation where
3229 the SSL certificate is self signed or not properly signed by a
3230 generally accepted signing authority, you can set a environment
3231 variable when calling listadmin to disable SSL verification:
</p
>
3233 <p
><blockquote
><pre
>
3234 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3235 </pre
></blockquote
></p
>
3237 <p
>If you want to moderate a subset of the lists you take care of, you
3238 can provide an argument to the listadmin script like I do in the
3239 initial screen dump (the xiph argument). Using an argument, only
3240 lists matching the argument string will be processed. This make it
3241 quick to accept messages if you notice the moderation request in your
3244 <p
>Without the listadmin program, I would never be the moderator of
68
3245 mailing lists, as I simply do not have time to spend on that if the
3246 process was any slower. The listadmin program have saved me hours of
3247 time I could spend elsewhere over the years. It truly is nice free
3250 <p
>As usual, if you use Bitcoin and want to show your support of my
3251 activities, please send Bitcoin donations to my address
3252 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3254 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3255 configuration example. Also, I
've been told that the
3256 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3262 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3263 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3264 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3265 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3266 <description><p
>When PXE installing laptops with Debian, I often run into the
3267 problem that the WiFi card require some firmware to work properly.
3268 And it has been a pain to fix this using preseeding in Debian.
3269 Normally something more is needed. But thanks to
3270 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3271 package
</a
> and its recent tasksel extension, it has now become easy
3272 to do this using simple preseeding.
</p
>
3274 <p
>The isenkram-cli package provide tasksel tasks which will install
3275 firmware for the hardware found in the machine (actually, requested by
3276 the kernel modules for the hardware). (It can also install user space
3277 programs supporting the hardware detected, but that is not the focus
3278 of this story.)
</p
>
3280 <p
>To get this working in the default installation, two preeseding
3281 values are needed. First, the isenkram-cli package must be installed
3282 into the target chroot (aka the hard drive) before tasksel is executed
3283 in the pkgsel step of the debian-installer system. This is done by
3284 preseeding the base-installer/includes debconf value to include the
3285 isenkram-cli package. The package name is next passed to debootstrap
3286 for installation. With the isenkram-cli package in place, tasksel
3287 will automatically use the isenkram tasks to detect hardware specific
3288 packages for the machine being installed and install them, because
3289 isenkram-cli contain tasksel tasks.
</p
>
3291 <p
>Second, one need to enable the non-free APT repository, because
3292 most firmware unfortunately is non-free. This is done by preseeding
3293 the apt-mirror-setup step. This is unfortunate, but for a lot of
3294 hardware it is the only option in Debian.
</p
>
3296 <p
>The end result is two lines needed in your preseeding file to get
3297 firmware installed automatically by the installer:
</p
>
3299 <p
><blockquote
><pre
>
3300 base-installer base-installer/includes string isenkram-cli
3301 apt-mirror-setup apt-setup/non-free boolean true
3302 </pre
></blockquote
></p
>
3304 <p
>The current version of isenkram-cli in testing/jessie will install
3305 both firmware and user space packages when using this method. It also
3306 do not work well, so use version
0.15 or later. Installing both
3307 firmware and user space packages might give you a bit more than you
3308 want, so I decided to split the tasksel task in two, one for firmware
3309 and one for user space programs. The firmware task is enabled by
3310 default, while the one for user space programs is not. This split is
3311 implemented in the package currently in unstable.
</p
>
3313 <p
>If you decide to give this a go, please let me know (via email) how
3314 this recipe work for you. :)
</p
>
3316 <p
>So, I bet you are wondering, how can this work. First and
3317 foremost, it work because tasksel is modular, and driven by whatever
3318 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3319 isenkram-cli package place two files for tasksel to find. First there
3320 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3322 <p
><blockquote
><pre
>
3323 Task: isenkram-packages
3325 Description: Hardware specific packages (autodetected by isenkram)
3326 Based on the detected hardware various hardware specific packages are
3328 Test-new-install: show show
3330 Packages: for-current-hardware
3332 Task: isenkram-firmware
3334 Description: Hardware specific firmware packages (autodetected by isenkram)
3335 Based on the detected hardware various hardware specific firmware
3336 packages are proposed.
3337 Test-new-install: mark show
3339 Packages: for-current-hardware-firmware
3340 </pre
></blockquote
></p
>
3342 <p
>The key parts are Test-new-install which indicate how the task
3343 should be handled and the Packages line referencing to a script in
3344 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3345 list of packages to install. The for-current-hardware-firmware script
3346 look like this to list relevant firmware for the machine:
3348 <p
><blockquote
><pre
>
3351 PATH=/usr/sbin:$PATH
3353 isenkram-autoinstall-firmware -l
3354 </pre
></blockquote
></p
>
3356 <p
>With those two pieces in place, the firmware is installed by
3357 tasksel during the normal d-i run. :)
</p
>
3359 <p
>If you want to test what tasksel will install when isenkram-cli is
3360 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3361 --new-install
</tt
> to get the list of packages that tasksel would
3364 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3365 pilots in testing this feature, as isenkram is used there now to
3366 install firmware, replacing the earlier scripts.
</p
>
3371 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3372 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3373 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3374 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3375 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3376 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3377 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3378 on a screen normally showing the bread types and prizes:
</p
>
3380 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3382 <p
>If it had booted as it was supposed to, I would never had known
3383 about this hidden Linux installation. It is interesting what
3384 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3389 <title>New lsdvd release version
0.17 is ready
</title>
3390 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3391 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3392 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3393 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3394 got a new set of developers a few weeks ago, after the original
3395 developer decided to step down and pass the project to fresh blood.
3396 This project is now maintained by Petter Reinholdtsen and Steve
3399 <p
>I just wrapped up
3400 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3401 new lsdvd release
</a
>, available in git or from
3402 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3403 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3408 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3409 <li
>Check for garbage in the program chains, which indicate that a track is
3410 non-existant, to work around additional copy protection
</li
>
3411 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3412 <li
>Fix pallete display of first entry
</li
>
3413 <li
>Fix include orders
</li
>
3414 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3415 <li
>Fix the chapter count
</li
>
3416 <li
>Make sure the array size and the array limit used when initialising
3417 the palette size is the same.
</li
>
3418 <li
>Fix array printing.
</li
>
3419 <li
>Correct subsecond calculations.
</li
>
3420 <li
>Add sector information to the output format.
</li
>
3421 <li
>Clean up code to be closer to ANSI C and compile without warnings
3422 with more GCC compiler warnings.
</li
>
3426 <p
>This change bring together patches for lsdvd in use in various
3427 Linux and Unix distributions, as well as patches submitted to the
3428 project the last nine years. Please check it out. :)
</p
>
3433 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3434 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3435 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3436 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3437 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3438 project
</a
> provide a Linux solution for schools, including a
3439 powerful desktop with education software, a central server providing
3440 web pages, user database, user home directories, central login and PXE
3441 boot of both clients without disk and the installation to install Debian
3442 Edu on machines with disk (and a few other services perhaps to small
3443 to mention here). We in the Debian Edu team are currently working on
3444 the Jessie based version, trying to get everything in shape before the
3445 freeze, to avoid having to maintain our own package repository in the
3447 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3448 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3449 work left. Some fatal problems block testing, breaking the installer,
3450 but it is possible to work around these to get anyway. Here is a
3451 recipe on how to get the installation limping along.
</p
>
3453 <p
>First, download the test ISO via
3454 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3455 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3457 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3458 The ISO build was broken on Tuesday, so we do not get a new ISO every
3459 12 hours or so, but thankfully the ISO we already got we are able to
3460 install with some tweaking.
</p
>
3462 <p
>When you get to the Debian Edu profile question, go to tty2
3463 (use Alt-Ctrl-F2), run
</p
>
3465 <p
><blockquote
><pre
>
3466 nano /usr/bin/edu-eatmydata-install
3467 </pre
></blockquote
></p
>
3469 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3470 optimization. Return to the installation, select the profile you want
3471 and continue. Without this change, exim4-config will fail to install
3472 due to a known bug in eatmydata.
</p
>
3474 <p
>When you get the grub question at the end, answer /dev/sda (or if
3475 this do not work, figure out what your correct value would be. All my
3476 test machines need /dev/sda, so I have no advice if it do not fit
3477 your need.
</p
>
3479 <p
>If you installed a profile including a graphical desktop, log in as
3480 root after the initial boot from hard drive, and install the
3481 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3482 or mate. If you want several desktop options, install more than one
3483 metapackage. Once this is done, reboot and you should have a working
3484 graphical login screen. This workaround should no longer be needed
3485 once the education-tasks package version
1.801 enter testing in two
3488 <p
>I believe the ISO build will start working on two days when the new
3489 tasksel package enter testing and Steve McIntyre get a chance to
3490 update the debian-cd git repository. The eatmydata, grub and desktop
3491 issues are already fixed in unstable and testing, and should show up
3492 on the ISO as soon as the ISO build start working again. Well the
3493 eatmydata optimization is really just disabled. The proper fix
3494 require an upload by the eatmydata maintainer applying the patch
3495 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3496 The rest have proper fixes in unstable.
</p
>
3498 <p
>I hope this get you going with the installation testing, as we are
3499 quickly running out of time trying to get our Jessie based
3500 installation ready before the distribution freeze in a month.
</p
>
3505 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3506 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3507 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3508 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3509 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3510 to handle my fairly large DVD collection. It is a nice command line
3511 tool to get details about a DVD, like title, tracks, track length,
3512 etc, in XML, Perl or human readable format. But lsdvd have not seen
3513 any new development since
2006 and had a few irritating bugs affecting
3514 its use with some DVDs. Upstream seemed to be dead, and in January I
3515 sent a small probe asking for a version control repository for the
3516 project, without any reply. But I use it regularly and would like to
3517 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3518 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3519 the project admin, and after getting a reply from him explaining that
3520 he was no longer interested in the project, I asked if I could take
3521 over. And yesterday, I became project admin.
</p
>
3523 <p
>I
've been in touch with a Gentoo developer and the Debian
3524 maintainer interested in joining forces to maintain the upstream
3525 project, and I hope we can get a new release out fairly quickly,
3526 collecting the patches spread around on the internet into on place.
3527 I
've added the relevant Debian patches to the freshly created git
3528 repository, and expect the Gentoo patches to make it too. If you got
3529 a DVD collection and care about command line tools, check out
3530 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3531 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3532 list
</a
>. :)
</p
>
3537 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3538 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3539 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3540 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3541 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3542 a lot quicker. When we install more than
2000 packages in
3543 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3544 tasksel in the installer, unpacking the binary packages take forever.
3545 A part of the slow I/O issue was discussed in
3546 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3547 much file system sync-ing done by dpkg, which is the package
3548 responsible for unpacking the binary packages. Other parts (like code
3549 executed by postinst scripts) might also sync to disk during
3550 installation. All this sync-ing to disk do not really make sense to
3551 me. If the machine crash half-way through, I start over, I do not try
3552 to salvage the half installed system. So the failure sync-ing is
3553 supposed to protect against, hardware or system crash, is not really
3554 relevant while the installer is running.
</p
>
3556 <p
>A few days ago, I thought of a way to get rid of all the file
3557 system sync()-ing in a fairly non-intrusive way, without the need to
3558 change the code in several packages. The idea is not new, but I have
3559 not heard anyone propose the approach using dpkg-divert before. It
3560 depend on the small and clever package
3561 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3562 uses LD_PRELOAD to replace the system functions for syncing data to
3563 disk with functions doing nothing, thus allowing programs to live
3564 dangerous while speeding up disk I/O significantly. Instead of
3565 modifying the implementation of dpkg, apt and tasksel (which are the
3566 packages responsible for selecting, fetching and installing packages),
3567 it occurred to me that we could just divert the programs away, replace
3568 them with a simple shell wrapper calling
3569 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3570 Two days ago I decided to test the idea, and wrapped up a simple
3571 implementation for the Debian Edu udeb.
</p
>
3573 <p
>The effect was stunning. In my first test it reduced the running
3574 time of the pkgsel step (installing tasks) from
64 to less than
44
3575 minutes (
20 minutes shaved off the installation) on an old Dell
3576 Latitude D505 machine. I am not quite sure what the optimised time
3577 would have been, as I messed up the testing a bit, causing the debconf
3578 priority to get low enough for two questions to pop up during
3579 installation. As soon as I saw the questions I moved the installation
3580 along, but do not know how long the question were holding up the
3581 installation. I did some more measurements using Debian Edu Jessie,
3582 and got these results. The time measured is the time stamp in
3583 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3584 "pkgsel: finishing up
" lines, if you want to do the same measurement
3585 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3586 timing thus do not depend on how quickly the user handle the tasksel
3589 <p
><table
>
3592 <th
>Machine/setup
</th
>
3593 <th
>Original tasksel
</th
>
3594 <th
>Optimised tasksel
</th
>
3595 <th
>Reduction
</th
>
3599 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3600 <td
>64 min (
07:
46-
08:
50)
</td
>
3601 <td
><44 min (
11:
27-
12:
11)
</td
>
3602 <td
>>20 min
18%
</td
>
3606 <td
>Latitude D505 Roaming LXDE
</td
>
3607 <td
>57 min (
08:
48-
09:
45)
</td
>
3608 <td
>34 min (
07:
43-
08:
17)
</td
>
3609 <td
>23 min
40%
</td
>
3613 <td
>Latitude D505 Minimal
</td
>
3614 <td
>22 min (
10:
37-
10:
59)
</td
>
3615 <td
>11 min (
11:
16-
11:
27)
</td
>
3616 <td
>11 min
50%
</td
>
3620 <td
>Thinkpad X200 Minimal
</td
>
3621 <td
>6 min (
08:
19-
08:
25)
</td
>
3622 <td
>4 min (
08:
04-
08:
08)
</td
>
3623 <td
>2 min
33%
</td
>
3627 <td
>Thinkpad X200 Roaming KDE
</td
>
3628 <td
>19 min (
09:
21-
09:
40)
</td
>
3629 <td
>15 min (
10:
25-
10:
40)
</td
>
3630 <td
>4 min
21%
</td
>
3633 </table
></p
>
3635 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3636 time is spent downloading packages. The connection to the Internet
3637 was
100Mbit/s during testing, so downloading should not be a
3638 significant factor in the measurement. Download typically took a few
3639 seconds to a few minutes, depending on the amount of packages being
3640 installed.
</p
>
3642 <p
>The speedup is implemented by using two hooks in
3643 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3644 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3645 finish-install.d hook to remove the divert at the end of the
3646 installation. I picked the pre-pkgsel.d hook instead of the
3647 post-base-installer.d hook because I test using an ISO without the
3648 eatmydata package included, and the post-base-installer.d hook in
3649 Debian Edu can only operate on packages included in the ISO. The
3650 negative effect of this is that I am unable to activate this
3651 optimization for the kernel installation step in d-i. If the code is
3652 moved to the post-base-installer.d hook, the speedup would be larger
3653 for the entire installation.
</p
>
3655 <p
>I
've implemented this in the
3656 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3657 git repository, and plan to provide the optimization as part of the
3658 Debian Edu installation. If you want to test this yourself, you can
3659 create two files in the installer (or in an udeb). One shell script
3660 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3662 <p
><blockquote
><pre
>
3665 . /usr/share/debconf/confmodule
3667 logger -t my-pkgsel
"info: $*
"
3670 logger -t my-pkgsel
"error: $*
"
3672 override_install() {
3673 apt-install eatmydata || true
3674 if [ -x /target/usr/bin/eatmydata ] ; then
3675 for bin in dpkg apt-get aptitude tasksel ; do
3677 # Test that the file exist and have not been diverted already.
3678 if [ -f /target$file ] ; then
3679 info
"diverting $file using eatmydata
"
3680 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3681 > /target$file.edu
3682 chmod
755 /target$file.edu
3683 in-target dpkg-divert --package debian-edu-config \
3684 --rename --quiet --add $file
3685 ln -sf ./$bin.edu /target$file
3687 error
"unable to divert $file, as it is missing.
"
3691 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3696 </pre
></blockquote
></p
>
3698 <p
>To clean up, another shell script should go into
3699 /usr/lib/finish-install.d/ with code like this:
3701 <p
><blockquote
><pre
>
3703 . /usr/share/debconf/confmodule
3705 logger -t my-finish-install
"error: $@
"
3707 remove_install_override() {
3708 for bin in dpkg apt-get aptitude tasksel ; do
3710 if [ -x /target$file.edu ] ; then
3712 in-target dpkg-divert --package debian-edu-config \
3713 --rename --quiet --remove $file
3716 error
"Missing divert for $file.
"
3719 sync # Flush file buffers before continuing
3722 remove_install_override
3723 </pre
></blockquote
></p
>
3725 <p
>In Debian Edu, I placed both code fragments in a separate script
3726 edu-eatmydata-install and call it from the pre-pkgsel.d and
3727 finish-install.d scripts.
</p
>
3729 <p
>By now you might ask if this change should get into the normal
3730 Debian installer too? I suspect it should, but am not sure the
3731 current debian-installer coordinators find it useful enough. It also
3732 depend on the side effects of the change. I
'm not aware of any, but I
3733 guess we will see if the change is safe after some more testing.
3734 Perhaps there is some package in Debian depending on sync() and
3735 fsync() having effect? Perhaps it should go into its own udeb, to
3736 allow those of us wanting to enable it to do so without affecting
3739 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3740 will break installation of all programs using gnutls because of
3741 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3742 eatmydata package in Debian will solve it.
</p
>
3744 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3745 the optimization work again. And I have discovered that the
3746 dpkg-divert trick is not really needed and implemented a slightly
3747 simpler approach as part of the debian-edu-install package. See
3748 tools/edu-eatmydata-install in the source package.
</p
>
3750 <p
>Update
2014-
11-
11: Unfortunately, a new
3751 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3752 triggering on i386 made it into testing, and broke this installation
3753 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3754 request
768893</a
> is accepted, it should be working again.
</p
>
3759 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3760 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3762 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3763 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3764 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3765 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3766 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3767 learn that there is a large set of publicly available key servers to
3768 use when looking for peoples public key. So far I have used
3769 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3770 were misbehaving, but those days are ended. The servers I have used
3771 up until yesterday have been slow and some times unavailable. I hope
3772 those problems are gone now.
</p
>
3774 <p
>Behind the round robin DNS entry of the
3775 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3776 there is a pool of more than
100 keyservers which are checked every
3777 day to ensure they are well connected and up to date. It must be
3778 better than what I have used so far. :)
</p
>
3780 <p
>Yesterdays speaker told me that the service is the default
3781 keyserver provided by the default configuration in GnuPG, but this do
3782 not seem to be used in Debian. Perhaps it should?
</p
>
3784 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3787 <p
><blockquote
><pre
>
3788 keyserver pool.sks-keyservers.net
3789 </pre
></blockquote
></p
>
3791 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3792 entries in DNS. Just for fun, I did just that at work, so now every
3793 user of GnuPG at the University of Oslo should find a OpenGPG
3794 keyserver automatically should their need it:
</p
>
3796 <p
><blockquote
><pre
>
3797 % host -t srv _pgpkey-http._tcp.uio.no
3798 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3800 </pre
></blockquote
></p
>
3802 <p
>Now if only
3803 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3804 HKP lookup protocol
</a
> supported finding signature paths, I would be
3805 very happy. It can look up a given key or search for a user ID, but I
3806 normally do not want that, but to find a trust path from my key to
3807 another key. Given a user ID or key ID, I would like to find (and
3808 download) the keys representing a signature path from my key to the
3809 key in question, to be able to get a trust path between the two keys.
3810 This is as far as I can tell not possible today. Perhaps something
3811 for a future version of the protocol?
</p
>
3816 <title>From English wiki to translated PDF and epub via Docbook
</title>
3817 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3818 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3819 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3820 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3821 project
</a
> provide an instruction manual for teachers, system
3822 administrators and other users that contain useful tips for setting up
3823 and maintaining a Debian Edu installation. This text is about how the
3824 text processing of this manual is handled in the project.
</p
>
3826 <p
>One goal of the project is to provide information in the native
3827 language of its users, and for this we need to handle translations.
3828 But we also want to make sure each language contain the same
3829 information, so for this we need a good way to keep the translations
3830 in sync. And we want it to be easy for our users to improve the
3831 documentation, avoiding the need to learn special formats or tools to
3832 contribute, and the obvious way to do this is to make it possible to
3833 edit the documentation using a web browser. We also want it to be
3834 easy for translators to keep the translation up to date, and give them
3835 help in figuring out what need to be translated. Here is the list of
3836 tools and the process we have found trying to reach all these
3839 <p
>We maintain the authoritative source of our manual in the
3840 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3841 wiki
</a
>, as several wiki pages written in English. It consist of one
3842 front page with references to the different chapters, several pages
3843 for each chapter, and finally one
"collection page
" gluing all the
3844 chapters together into one large web page (aka
3845 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3846 AllInOne page
</a
>). The AllInOne page is the one used for further
3847 processing and translations. Thanks to the fact that the
3848 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3849 wiki.debian.org support exporting pages in
3850 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3851 the list of pages to export using the raw version of the AllInOne
3852 page, loop over each of them to generate a Docbook XML version of the
3853 manual. This process also download images and transform image
3854 references to use the locally downloaded images. The generated
3855 Docbook XML files are slightly broken, so some post-processing is done
3856 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3857 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3858 a handfull of images. The XML file can now be used to generate PDF, HTML
3859 and epub versions of the English manual. This is the basic step of
3860 our process, making PDF (using dblatex), HTML (using xsltproc) and
3861 epub (using dbtoepub) version from Docbook XML, and the resulting files
3862 are placed in the debian-edu-doc-en binary package.
</p
>
3864 <p
>But English documentation is not enough for us. We want translated
3865 documentation too, and we want to make it easy for translators to
3866 track the English original. For this we use the
3867 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3868 which allow us to transform the English Docbook XML file into a
3869 translation file (a .pot file), usable with the normal gettext based
3870 translation tools used by those translating free software. The pot
3871 file is used to create and maintain translation files (several .po
3872 files), which the translations update with the native language
3873 translations of all titles, paragraphs and blocks of text in the
3874 original. The next step is combining the original English Docbook XML
3875 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3876 create a translated Docbook XML file (in this case
3877 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3878 translated, if the translation is not complete) Docbook XML file can
3879 then be used like the original to create a PDF, HTML and epub version
3880 of the documentation.
</p
>
3882 <p
>The translators use different tools to edit the .po files. We
3884 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3885 while some use emacs and vi, others can use web based editors like
3886 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3887 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3888 is where the .po file end up, in our git repository. Updated
3889 translations can either be committed directly to git, or submitted as
3890 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3891 against the debian-edu-doc package
</a
>.
</p
>
3893 <p
>One challenge is images, which both might need to be translated (if
3894 they show translated user applications), and are needed in different
3895 formats when creating PDF and HTML versions (epub is a HTML version in
3896 this regard). For this we transform the original PNG images to the
3897 needed density and format during build, and have a way to provide
3898 translated images by storing translated versions in
3899 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3900 package maintainers know more.
</p
>
3902 <p
>If you wonder what the result look like, we provide
3903 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3904 of the documentation packages on the web
</a
>. See for example the
3905 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3906 PDF version
</a
> or the
3907 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3908 HTML version
</a
>. We do not yet build the epub version by default,
3909 but perhaps it will be done in the future.
</p
>
3911 <p
>To learn more, check out
3912 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3913 debian-edu-doc package
</a
>,
3914 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3915 manual on the wiki
</a
> and
3916 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3917 translation instructions
</a
> in the manual.
</p
>
3922 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3923 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3924 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3925 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3926 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3927 related packages relevant for the computer installed automatically.
3928 So I implemented one, using
3929 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3930 package
</a
>. To use it, install the tasksel and isenkram packages and
3931 run tasksel as user root. You should be presented with a new option,
3932 "Hardware specific packages (autodetected by isenkram)
". When you
3933 select it, tasksel will install the packages isenkram claim is fit for
3934 the current hardware, hot pluggable or not.
<p
>
3936 <p
>The implementation is in two files, one is the tasksel menu entry
3937 description, and the other is the script used to extract the list of
3938 packages to install. The first part is in
3939 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3942 <p
><blockquote
><pre
>
3945 Description: Hardware specific packages (autodetected by isenkram)
3946 Based on the detected hardware various hardware specific packages are
3948 Test-new-install: mark show
3950 Packages: for-current-hardware
3951 </pre
></blockquote
></p
>
3953 <p
>The second part is in
3954 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3957 <p
><blockquote
><pre
>
3962 isenkram-autoinstall-firmware -l
3964 </pre
></blockquote
></p
>
3966 <p
>All in all, a very short and simple implementation making it
3967 trivial to install the hardware dependent package we all may want to
3968 have installed on our machines. I
've not been able to find a way to
3969 get tasksel to tell you exactly which packages it plan to install
3970 before doing the installation. So if you are curious or careful,
3971 check the output from the isenkram-* command line tools first.
</p
>
3973 <p
>The information about which packages are handling which hardware is
3974 fetched either from the isenkram package itself in
3975 /usr/share/isenkram/, from git.debian.org or from the APT package
3976 database (using the Modaliases header). The APT package database
3977 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3978 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3979 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3980 the python-apt code (bug
3981 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3982 workaround I was able to get rid of the file descriptor leak and
3983 reduce the memory leak from ~
30 MiB per hardware detection down to
3984 around
2 MiB per hardware detection. It should make the desktop
3985 daemon a lot more useful. The fix is in version
0.7 uploaded to
3986 unstable today.
</p
>
3988 <p
>I believe the current way of mapping hardware to packages in
3989 Isenkram is is a good draft, but in the future I expect isenkram to
3990 use the AppStream data source for this. A proposal for getting proper
3991 AppStream support into Debian is floating around as
3992 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3993 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3994 project
</a
> will take place this summer to improve the situation. I
3995 look forward to seeing the result, and welcome patches for isenkram to
3996 start using the information when it is ready.
</p
>
3998 <p
>If you want your package to map to some specific hardware, either
3999 add a
"Xb-Modaliases
" header to your control file like I did in
4000 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4001 package
</a
> or submit a bug report with the details to the isenkram
4003 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4004 blog posts tagged isenkram
</a
> for details on the notation. I expect
4005 the information will be migrated to AppStream eventually, but for the
4006 moment I got no better place to store it.
</p
>
4011 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4012 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4013 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4014 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4015 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4016 project
</a
> is working on providing the software and hardware to make
4017 it easy for non-technical people to host their data and communication
4018 at home, and being able to communicate with their friends and family
4019 encrypted and away from prying eyes. It is still going strong, and
4020 today a major mile stone was reached.
</p
>
4022 <p
>Today, the last of the packages currently used by the project to
4023 created the system images were accepted into Debian Unstable. It was
4024 the freedombox-setup package, which is used to configure the images
4025 during build and on the first boot. Now all one need to get going is
4026 the build code from the freedom-maker git repository and packages from
4027 Debian. And once the freedombox-setup package enter testing, we can
4028 build everything directly from Debian. :)
</p
>
4030 <p
>Some key packages used by Freedombox are
4031 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4032 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4033 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4034 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4035 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4036 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4037 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4038 are plans to integrate more packages into the setup. User
4039 documentation is maintained on the Debian wiki. Please
4040 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4041 the manual
</a
> and help us improve it.
</p
>
4043 <p
>To test for yourself and create boot images with the FreedomBox
4044 setup, run this on a Debian machine using a user with sudo rights to
4045 become root:
</p
>
4047 <p
><pre
>
4048 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4049 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4051 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4053 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4054 </pre
></p
>
4056 <p
>Root access is needed to run debootstrap and mount loopback
4057 devices. See the README in the freedom-maker git repo for more
4058 details on the build. If you do not want all three images, trim the
4059 make line. Note that the virtualbox-image target is not really
4060 virtualbox specific. It create a x86 image usable in kvm, qemu,
4061 vmware and any other x86 virtual machine environment. You might need
4062 the version of vmdebootstrap in Jessie to get the build working, as it
4063 include fixes for a race condition with kpartx.
</p
>
4065 <p
>If you instead want to install using a Debian CD and the preseed
4066 method, boot a Debian Wheezy ISO and use this boot argument to load
4067 the preseed values:
</p
>
4069 <p
><pre
>
4070 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4071 </pre
></p
>
4073 <p
>I have not tested it myself the last few weeks, so I do not know if
4074 it still work.
</p
>
4076 <p
>If you wonder how to help, one task you could look at is using
4077 systemd as the boot system. It will become the default for Linux in
4078 Jessie, so we need to make sure it is usable on the Freedombox. I did
4079 a simple test a few weeks ago, and noticed dnsmasq failed to start
4080 during boot when using systemd. I suspect there are other problems
4081 too. :) To detect problems, there is a test suite included, which can
4082 be run from the plinth web interface.
</p
>
4084 <p
>Give it a go and let us know how it goes on the mailing list, and help
4085 us get the new release published. :) Please join us on
4086 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4087 irc.debian.org)
</a
> and
4088 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4089 mailing list
</a
> if you want to help make this vision come true.
</p
>
4094 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4095 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4096 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4097 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4098 <description><p
>For a while now, I have been looking for a sensible offsite backup
4099 solution for use at home. My requirements are simple, it must be
4100 cheap and locally encrypted (in other words, I keep the encryption
4101 keys, the storage provider do not have access to my private files).
4102 One idea me and my friends had many years ago, before the cloud
4103 storage providers showed up, was to use Google mail as storage,
4104 writing a Linux block device storing blocks as emails in the mail
4105 service provided by Google, and thus get heaps of free space. On top
4106 of this one can add encryption, RAID and volume management to have
4107 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4108 I never found time to implement such system. But the last few weeks I
4109 have looked at a system called
4110 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4111 mounted network backed file system with the features I need.
</p
>
4113 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4114 handling several different storage providers, any with Amazon S3,
4115 Google Drive or OpenStack API. There are heaps of such storage
4116 providers. S3QL can also use a local directory as storage, which
4117 combined with sshfs allow for file storage on any ssh server. S3QL
4118 include support for encryption, compression, de-duplication, snapshots
4119 and immutable file systems, allowing me to mount the remote storage as
4120 a local mount point, look at and use the files as if they were local,
4121 while the content is stored in the cloud as well. This allow me to
4122 have a backup that should survive fire. The file system can not be
4123 shared between several machines at the same time, as only one can
4124 mount it at the time, but any machine with the encryption key and
4125 access to the storage service can mount it if it is unmounted.
</p
>
4127 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4128 package is included already. So to get started, run
<tt
>apt-get
4129 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4130 Greenqloud, after reading their nice recipe on
4131 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4132 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4133 in Iceland more than those in USA when it come to keeping my personal
4134 data safe and private, and thus would rather spend money on a company
4135 in Iceland. Another nice recipe is available from the article
4136 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4137 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4138 Admin magazine. When the provider is picked, figure out how to get
4139 the API key needed to connect to the storage API. With Greencloud,
4140 the key did not show up until I had added payment details to my
4143 <p
>Armed with the API access details, it is time to create the file
4144 system. First, create a new bucket in the cloud. This bucket is the
4145 file system storage area. I picked a bucket name reflecting the
4146 machine that was going to store data there, but any name will do.
4147 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4148 the API login and password, and a locally created password. Store it
4149 all in ~root/.s3ql/authinfo2 like this:
4151 <p
><blockquote
><pre
>
4153 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4154 backend-login: API-login
4155 backend-password: API-password
4156 fs-passphrase: local-password
4157 </pre
></blockquote
></p
>
4159 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4160 but any sensible way to create a fairly random password should do it.
4161 Armed with these details, it is now time to run mkfs, entering the API
4162 details and password to create it:
</p
>
4164 <p
><blockquote
><pre
>
4165 # mkdir -m
700 /var/lib/s3ql-cache
4166 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4167 --ssl s3c://s.greenqloud.com:
443/bucket-name
4168 Enter backend login:
4169 Enter backend password:
4170 Before using S3QL, make sure to read the user
's guide, especially
4171 the
'Important Rules to Avoid Loosing Data
' section.
4172 Enter encryption password:
4173 Confirm encryption password:
4174 Generating random encryption key...
4175 Creating metadata tables...
4185 Compressing and uploading metadata...
4186 Wrote
0.00 MB of compressed metadata.
4187 #
</pre
></blockquote
></p
>
4189 <p
>The next step is mounting the file system to make the storage available.
4191 <p
><blockquote
><pre
>
4192 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4193 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4194 Using
4 upload threads.
4195 Downloading and decompressing metadata...
4205 Mounting filesystem...
4207 Filesystem Size Used Avail Use% Mounted on
4208 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4210 </pre
></blockquote
></p
>
4212 <p
>The file system is now ready for use. I use rsync to store my
4213 backups in it, and as the metadata used by rsync is downloaded at
4214 mount time, no network traffic (and storage cost) is triggered by
4215 running rsync. To unmount, one should not use the normal umount
4216 command, as this will not flush the cache to the cloud storage, but
4217 instead running the umount.s3ql command like this:
4219 <p
><blockquote
><pre
>
4222 </pre
></blockquote
></p
>
4224 <p
>There is a fsck command available to check the file system and
4225 correct any problems detected. This can be used if the local server
4226 crashes while the file system is mounted, to reset the
"already
4227 mounted
" flag. This is what it look like when processing a working
4228 file system:
</p
>
4230 <p
><blockquote
><pre
>
4231 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4232 Using cached metadata.
4233 File system seems clean, checking anyway.
4234 Checking DB integrity...
4235 Creating temporary extra indices...
4236 Checking lost+found...
4237 Checking cached objects...
4238 Checking names (refcounts)...
4239 Checking contents (names)...
4240 Checking contents (inodes)...
4241 Checking contents (parent inodes)...
4242 Checking objects (reference counts)...
4243 Checking objects (backend)...
4244 ..processed
5000 objects so far..
4245 ..processed
10000 objects so far..
4246 ..processed
15000 objects so far..
4247 Checking objects (sizes)...
4248 Checking blocks (referenced objects)...
4249 Checking blocks (refcounts)...
4250 Checking inode-block mapping (blocks)...
4251 Checking inode-block mapping (inodes)...
4252 Checking inodes (refcounts)...
4253 Checking inodes (sizes)...
4254 Checking extended attributes (names)...
4255 Checking extended attributes (inodes)...
4256 Checking symlinks (inodes)...
4257 Checking directory reachability...
4258 Checking unix conventions...
4259 Checking referential integrity...
4260 Dropping temporary indices...
4261 Backing up old metadata...
4271 Compressing and uploading metadata...
4272 Wrote
0.89 MB of compressed metadata.
4274 </pre
></blockquote
></p
>
4276 <p
>Thanks to the cache, working on files that fit in the cache is very
4277 quick, about the same speed as local file access. Uploading large
4278 amount of data is to me limited by the bandwidth out of and into my
4279 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4280 which is very close to my upload speed, and downloading the same
4281 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4282 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4283 network, not the file system code. I do not know what a good cache
4284 size would be, but suspect that the cache should e larger than your
4285 working set.
</p
>
4287 <p
>I mentioned that only one machine can mount the file system at the
4288 time. If another machine try, it is told that the file system is
4291 <p
><blockquote
><pre
>
4292 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4293 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4294 Using
8 upload threads.
4295 Backend reports that fs is still mounted elsewhere, aborting.
4297 </pre
></blockquote
></p
>
4299 <p
>The file content is uploaded when the cache is full, while the
4300 metadata is uploaded once every
24 hour by default. To ensure the
4301 file system content is flushed to the cloud, one can either umount the
4302 file system, or ask S3QL to flush the cache and metadata using
4305 <p
><blockquote
><pre
>
4306 # s3qlctrl upload-meta /s3ql
4307 # s3qlctrl flushcache /s3ql
4309 </pre
></blockquote
></p
>
4311 <p
>If you are curious about how much space your data uses in the
4312 cloud, and how much compression and deduplication cut down on the
4313 storage usage, you can use s3qlstat on the mounted file system to get
4316 <p
><blockquote
><pre
>
4318 Directory entries:
9141
4321 Total data size:
22049.38 MB
4322 After de-duplication:
21955.46 MB (
99.57% of total)
4323 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4324 Database size:
2.39 MB (uncompressed)
4325 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4327 </pre
></blockquote
></p
>
4329 <p
>I mentioned earlier that there are several possible suppliers of
4330 storage. I did not try to locate them all, but am aware of at least
4331 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4332 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4333 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4334 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4335 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4336 accept payment in Bitcoin. Pick one that suit your need. Some of
4337 them provide several GiB of free storage, but the prize models are
4338 quite different and you will have to figure out what suits you
4341 <p
>While researching this blog post, I had a look at research papers
4342 and posters discussing the S3QL file system. There are several, which
4343 told me that the file system is getting a critical check by the
4344 science community and increased my confidence in using it. One nice
4346 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4347 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4348 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4349 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4350 and Pamela Smith. Please have a look.
</p
>
4352 <p
>Given my problems with different file systems earlier, I decided to
4353 check out the mounted S3QL file system to see if it would be usable as
4354 a home directory (in other word, that it provided POSIX semantics when
4355 it come to locking and umask handling etc). Running
4356 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4357 test code to check file system semantics
</a
>, I was happy to discover that
4358 no error was found. So the file system can be used for home
4359 directories, if one chooses to do so.
</p
>
4361 <p
>If you do not want a locally file system, and want something that
4362 work without the Linux fuse file system, I would like to mention the
4363 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4364 provide locally encrypted backup using a command line client. It have
4365 a nicer access control system, where one can split out read and write
4366 access, allowing some systems to write to the backup and others to
4367 only read from it.
</p
>
4369 <p
>As usual, if you use Bitcoin and want to show your support of my
4370 activities, please send Bitcoin donations to my address
4371 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4376 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4377 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4378 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4379 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4380 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4381 project
</a
> is working on providing the software and hardware for
4382 making it easy for non-technical people to host their data and
4383 communication at home, and being able to communicate with their
4384 friends and family encrypted and away from prying eyes. It has been
4385 going on for a while, and is slowly progressing towards a new test
4386 release (
0.2).
</p
>
4388 <p
>And what day could be better than the Pi day to announce that the
4389 new version will provide
"hard drive
" / SD card / USB stick images for
4390 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4391 system), and can also be installed using a Debian installer preseed
4392 file. The Debian based Freedombox is now based on Debian Jessie,
4393 where most of the needed packages used are already present. Only one,
4394 the freedombox-setup package, is missing. To try to build your own
4395 boot image to test the current status, fetch the freedom-maker scripts
4397 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4398 with a user with sudo access to become root:
4401 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4403 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4404 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4406 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4409 <p
>Root access is needed to run debootstrap and mount loopback
4410 devices. See the README for more details on the build. If you do not
4411 want all three images, trim the make line. But note that thanks to
<a
4412 href=
"https://bugs.debian.org/
741407">a race condition in
4413 vmdebootstrap
</a
>, the build might fail without the patch to the
4414 kpartx call.
</p
>
4416 <p
>If you instead want to install using a Debian CD and the preseed
4417 method, boot a Debian Wheezy ISO and use this boot argument to load
4418 the preseed values:
</p
>
4421 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4424 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4425 recently introduced bug in apt in Jessie
</a
>, the installer will
4426 currently hang while setting up APT sources. Killing the
4427 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4428 installation will get the installation going. This affect all
4429 installations in Jessie, and I expect it will be fixed soon.
</p
>
4431 <p
>Give it a go and let us know how it goes on the mailing list, and help
4432 us get the new release published. :) Please join us on
4433 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4434 irc.debian.org)
</a
> and
4435 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4436 mailing list
</a
> if you want to help make this vision come true.
</p
>
4441 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4442 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4443 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4444 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4445 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4446 innetgr tools, because I needed them in
4447 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4448 ng-utils, and it has served me well. I placed the project under the
4449 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4450 repository. But many years ago, the CVS repository was dropped (lost,
4451 not migrated to new hardware, not sure), and the project have lacked a
4452 proper home since then.
</p
>
4454 <p
>Last summer, I had a look at the package and made a new release
4455 fixing a irritating crash bug, but was unable to store the changes in
4456 a proper source control system. I applied for a project on
4457 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4458 to follow up on it. Until today. :)
</p
>
4460 <p
>After many hours of cleaning and migration, the ng-utils project
4461 now have a new home, and a git repository with the highlight of the
4462 history of the project. I published all release tarballs and imported
4463 them into the git repository. As the project is really stable and not
4464 expected to gain new features any time soon, I decided to make a new
4465 release and call it
1.0. Visit the new project home on
4466 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4467 if you want to check it out. The new version is also uploaded into
4468 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4473 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4474 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4475 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4476 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4477 <description><p
>A few days ago I decided to try to help the Hurd people to get
4478 their changes into sysvinit, to allow them to use the normal sysvinit
4479 boot system instead of their old one. This follow up on the
4480 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4481 Google Summer of Code work
</a
> done last summer by Justus Winter to
4482 get Debian on Hurd working more like Debian on Linux. To get started,
4483 I downloaded a prebuilt hard disk image from
4484 <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
>,
4485 and started it using virt-manager.
</p
>
4487 <p
>The first think I had to do after logging in (root without any
4488 password) was to get the network operational. I followed
4489 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4490 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4491 commands as root to get the machine to accept a IP address from the
4492 kvm internal DHCP server:
</p
>
4494 <p
><blockquote
><pre
>
4495 settrans -fgap /dev/netdde /hurd/netdde
4496 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4497 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4499 </pre
></blockquote
></p
>
4501 <p
>After this, the machine had internet connectivity, and I could
4502 upgrade it and install the sysvinit packages from experimental and
4503 enable it as the default boot system in Hurd.
</p
>
4505 <p
>But before I did that, I set a password on the root user, as ssh is
4506 running on the machine it for ssh login to work a password need to be
4507 set. Also, note that a bug somewhere in openssh on Hurd block
4508 compression from working. Remember to turn that off on the client
4511 <p
>Run these commands as root to upgrade and test the new sysvinit
4514 <p
><blockquote
><pre
>
4515 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4516 deb http://http.debian.net/debian/ experimental main
4519 apt-get dist-upgrade
4520 apt-get install -t experimental initscripts sysv-rc sysvinit \
4521 sysvinit-core sysvinit-utils
4522 update-alternatives --config runsystem
4523 </pre
></blockquote
></p
>
4525 <p
>To reboot after switching boot system, you have to use
4526 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4527 yet a sysvinit process able to receive the signals from the normal
4528 'reboot
' command. After switching to sysvinit as the boot system,
4529 upgrading every package and rebooting, the network come up with DHCP
4530 after boot as it should, and the settrans/pkill hack mentioned at the
4531 start is no longer needed. But for some strange reason, there are no
4532 longer any login prompt in the virtual console, so I logged in using
4535 <p
>Note that there are some race conditions in Hurd making the boot
4536 fail some times. No idea what the cause is, but hope the Hurd porters
4537 figure it out. At least Justus said on IRC (#debian-hurd on
4538 irc.debian.org) that they are aware of the problem. A way to reduce
4539 the impact is to upgrade to the Hurd packages built by Justus by
4540 adding this repository to the machine:
</p
>
4542 <p
><blockquote
><pre
>
4543 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4544 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4546 </pre
></blockquote
></p
>
4548 <p
>At the moment the prebuilt virtual machine get some packages from
4549 http://ftp.debian-ports.org/debian, because some of the packages in
4550 unstable do not yet include the required patches that are lingering in
4551 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4553 <p
><blockquote
><pre
>
4554 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4555 i emacs - GNU Emacs editor (metapackage)
4556 i gdb - GNU Debugger
4557 i hurd-recommended - Miscellaneous translators
4558 i isc-dhcp-client - ISC DHCP client
4559 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4560 i libc-bin - Embedded GNU C Library: Binaries
4561 i libc-dev-bin - Embedded GNU C Library: Development binaries
4562 i libc0.3 - Embedded GNU C Library: Shared libraries
4563 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4564 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4565 i multiarch-support - Transitional package to ensure multiarch compatibilit
4566 i A x11-common - X Window System (X.Org) infrastructure
4567 i xorg - X.Org X Window System
4568 i A xserver-xorg - X.Org X server
4569 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4571 </pre
></blockquote
></p
>
4573 <p
>All in all, testing hurd has been an interesting experience. :)
4574 X.org did not work out of the box and I never took the time to follow
4575 the porters instructions to fix it. This time I was interested in the
4576 command line stuff.
<p
>
4581 <title>New chrpath release
0.16</title>
4582 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4583 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4584 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4585 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4586 find problems in C, C++ and Java code using static source code
4587 analysis. It can detect a lot of different problems, and is very
4588 useful to find memory and locking bugs in the error handling part of
4589 the source. The company behind it provide
4590 <a href=
"https://scan.coverity.com/
">check of free software projects as
4591 a community service
</a
>, and many hundred free software projects are
4592 already checked. A few days ago I decided to have a closer look at
4593 the Coverity system, and discovered that the
4594 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4595 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4596 projects I am involved with was already registered. But these are
4597 fairly big, and I would also like to have a small and easy project to
4598 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4599 checking of the chrpath project
</a
>. It was
4600 added to the checker and discovered seven potential defects. Six of
4601 these were real, mostly resource
"leak
" when the program detected an
4602 error. Nothing serious, as the resources would be released a fraction
4603 of a second later when the program exited because of the error, but it
4604 is nice to do it right in case the source of the program some time in
4605 the future end up in a library. Having fixed all defects and added
4606 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4607 mailing list for the chrpath developers
</a
>, I decided it was time to
4608 publish a new release. These are the release notes:
</p
>
4610 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4614 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4615 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4616 <li
>Mention new project mailing list in the documentation.
</li
>
4621 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4622 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4623 project if something is wrong with the new release. The test suite
4624 did not discover any old errors, so if you find a new one, please also
4625 include a test suite check.
</p
>
4630 <title>New chrpath release
0.15</title>
4631 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4633 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4634 <description><p
>After many years break from the package and a vain hope that
4635 development would be continued by someone else, I finally pulled my
4636 acts together this morning and wrapped up a new release of chrpath,
4637 the command line tool to modify the rpath and runpath of already
4638 compiled ELF programs. The update was triggered by the persistence of
4639 Isha Vishnoi at IBM, which needed a new config.guess file to get
4640 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4641 is working on. I checked the
4642 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4643 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4644 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4645 packages for interesting patches (failed to find the source from
4646 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4647 These are the release notes:
</p
>
4649 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4653 <li
>Updated config.sub and config.guess from the GNU project to work
4654 with newer architectures. Thanks to isha vishnoi for the heads
4657 <li
>Updated README with current URLs.
</li
>
4659 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4660 Matthias Klose.
</li
>
4662 <li
>Added missing help for -k|--keepgoing option, using patch by
4663 Petr Machata found in Fedora.
</li
>
4665 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4666 .dynamic is a NULL terminated string. Based on patch found in
4667 Fedora credited Axel Thimm and Christian Krause.
</li
>
4672 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4673 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4674 project if something is wrong with the new release. The test suite
4675 did not discover any old errors, so if you find a new one, please also
4676 include a testsuite check.
</p
>
4681 <title>Debian init.d boot script example for rsyslog
</title>
4682 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4683 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4684 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4685 <description><p
>If one of the points of switching to a new init system in Debian is
4686 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4687 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4688 init.d scripts at all. Here is an example init.d script, ie a rewrite
4689 of /etc/init.d/rsyslog:
</p
>
4691 <p
><pre
>
4692 #!/lib/init/init-d-script
4695 # Required-Start: $remote_fs $time
4696 # Required-Stop: umountnfs $time
4697 # X-Stop-After: sendsigs
4698 # Default-Start:
2 3 4 5
4699 # Default-Stop:
0 1 6
4700 # Short-Description: enhanced syslogd
4701 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4702 # It is quite compatible to stock sysklogd and can be
4703 # used as a drop-in replacement.
4705 DESC=
"enhanced syslogd
"
4706 DAEMON=/usr/sbin/rsyslogd
4707 </pre
></p
>
4709 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4710 script was
137 lines, and the above is just
15 lines, most of it meta
4711 info/comments.
</p
>
4713 <p
>How to do this, you ask? Well, one create a new script
4714 /lib/init/init-d-script looking something like this:
4716 <p
><pre
>
4719 # Define LSB log_* functions.
4720 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4721 # and status_of_proc is working.
4722 . /lib/lsb/init-functions
4725 # Function that starts the daemon/service
4731 #
0 if daemon has been started
4732 #
1 if daemon was already running
4733 #
2 if daemon could not be started
4734 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4736 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4739 # Add code here, if necessary, that waits for the process to be ready
4740 # to handle requests from services started subsequently which depend
4741 # on this one. As a last resort, sleep for some time.
4745 # Function that stops the daemon/service
4750 #
0 if daemon has been stopped
4751 #
1 if daemon was already stopped
4752 #
2 if daemon could not be stopped
4753 # other if a failure occurred
4754 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4755 RETVAL=
"$?
"
4756 [
"$RETVAL
" =
2 ]
&& return
2
4757 # Wait for children to finish too if this is a daemon that forks
4758 # and if the daemon is only ever run from this initscript.
4759 # If the above conditions are not satisfied then add some other code
4760 # that waits for the process to drop all resources that could be
4761 # needed by services started subsequently. A last resort is to
4762 # sleep for some time.
4763 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4764 [
"$?
" =
2 ]
&& return
2
4765 # Many daemons don
't delete their pidfiles when they exit.
4767 return
"$RETVAL
"
4771 # Function that sends a SIGHUP to the daemon/service
4775 # If the daemon can reload its configuration without
4776 # restarting (for example, when it is sent a SIGHUP),
4777 # then implement that here.
4779 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4784 scriptbasename=
"$(basename $
1)
"
4785 echo
"SN: $scriptbasename
"
4786 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4787 script=
"$
1"
4794 NAME=$(basename $DAEMON)
4795 PIDFILE=/var/run/$NAME.pid
4797 # Exit if the package is not installed
4798 #[ -x
"$DAEMON
" ] || exit
0
4800 # Read configuration variable file if it is present
4801 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4803 # Load the VERBOSE setting and other rcS variables
4806 case
"$
1" in
4808 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4810 case
"$?
" in
4811 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4812 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4816 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4818 case
"$?
" in
4819 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4820 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4824 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4826 #reload|force-reload)
4828 # If do_reload() is not implemented then leave this commented out
4829 # and leave
'force-reload
' as an alias for
'restart
'.
4831 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4835 restart|force-reload)
4837 # If the
"reload
" option is implemented then remove the
4838 #
'force-reload
' alias
4840 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4842 case
"$?
" in
4845 case
"$?
" in
4847 1) log_end_msg
1 ;; # Old process is still running
4848 *) log_end_msg
1 ;; # Failed to start
4858 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4864 </pre
></p
>
4866 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4867 lot. I did not really polish the approach, so it might not always
4868 work out of the box, but you get the idea. I did not try very hard to
4869 optimize it nor make it more robust either.
</p
>
4871 <p
>A better argument for switching init system in Debian than reducing
4872 the size of init scripts (which is a good thing to do anyway), is to
4873 get boot system that is able to handle the kernel events sensibly and
4874 robustly, and do not depend on the boot to run sequentially. The boot
4875 and the kernel have not behaved sequentially in years.
</p
>
4880 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4881 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4882 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4883 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4884 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4885 remote display access is the preferred solution with oVirt and RedHat
4886 Enterprise Virtualization, and I was sad to discover the other day
4887 that the browser plugin needed to use these systems seamlessly was
4888 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4889 for a package
</a
> was from
2012-
04-
10 with no progress since
4890 2013-
04-
01, so I decided to wrap up a package based on the great work
4891 from Cajus Pollmeier and put it in a collab-maint maintained git
4892 repository to get a package I could use. I would very much like
4893 others to help me maintain the package (or just take over, I do not
4894 mind), but as no-one had volunteered so far, I just uploaded it to
4895 NEW. I hope it will be available in Debian in a few days.
</p
>
4897 <p
>The source is now available from
4898 <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
>
4903 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4904 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4905 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4906 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4907 <description><p
>The
4908 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4909 program is a a very nice system to create virtual machine images. It
4910 create a image file, add a partition table, mount it and run
4911 debootstrap in the mounted directory to create a Debian system on a
4912 stick. Yesterday, I decided to try to teach it how to make images for
4913 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4914 of a plan to simplify the build system for
4915 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4916 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4917 the virtualbox images, but its current build system made multistrap
4918 based system for Dreamplug images, and it is lacking support for
4919 Raspberry Pi.
</p
>
4921 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4922 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4923 code and adjusted it to be able to build armel images on my amd64
4924 Debian laptop. I ended up giving vmdebootstrap five new options,
4925 allowing me to replicate the image creation process I use to make
4926 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4927 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4928 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4929 call debootstrap with --foreign and to copy the handler into the
4930 generated chroot before running the second stage. This allow
4931 vmdebootstrap to create armel images on an amd64 host. Next I added
4932 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4933 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4934 given file system type, allowing me to create an image with a vfat
4935 partition for the /boot/ stuff. I also added a
<tt
>--variant
4936 variant
</tt
> option to allow me to create smaller images without the
4937 Debian base system packages installed. Finally, I added an option
4938 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4939 as a boot loader. It is not needed on the Raspberry Pi and probably
4940 most other non-x86 architectures. The changes were accepted by the
4941 upstream author of vmdebootstrap yesterday and today, and is now
4943 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4944 upstream project page
</a
>.
</p
>
4946 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4947 create a small script (the customize script) to add the non-free
4948 binary blob needed to boot the Raspberry Pi and the APT source
4951 <p
><pre
>
4953 set -e # Exit on first error
4954 rootdir=
"$
1"
4955 cd
"$rootdir
"
4956 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4957 deb http://http.debian.net/debian/ jessie main contrib non-free
4959 # Install non-free binary blob needed to boot Raspberry Pi. This
4960 # install a kernel somewhere too.
4961 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4962 -O $rootdir/usr/bin/rpi-update
4963 chmod a+x $rootdir/usr/bin/rpi-update
4964 mkdir -p $rootdir/lib/modules
4965 touch $rootdir/boot/start.elf
4966 chroot $rootdir rpi-update
4967 </pre
></p
>
4969 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4970 to build the image:
</p
>
4973 sudo ./vmdebootstrap \
4976 --distribution jessie \
4977 --mirror http://http.debian.net/debian \
4986 --root-password raspberry \
4987 --hostname raspberrypi \
4988 --foreign /usr/bin/qemu-arm-static \
4989 --customize `pwd`/customize \
4991 --package git-core \
4992 --package binutils \
4993 --package ca-certificates \
4996 </pre
></p
>
4998 <p
>The list of packages being installed are the ones needed by
4999 rpi-update to make the image bootable on the Raspberry Pi, with the
5000 exception of netbase, which is needed by debootstrap to find
5001 /etc/hosts with the minbase variant. I really wish there was a way to
5002 set up an Raspberry Pi using only packages in the Debian archive, but
5003 that is not possible as far as I know, because it boots from the GPU
5004 using a non-free binary blob.
</p
>
5006 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5007 probably a few others installed. I have not checked the complete
5008 build dependency list.
</p
>
5010 <p
>The resulting image will not use the hardware floating point unit
5011 on the Raspberry PI, because the armel architecture in Debian is not
5012 optimized for that use. So the images created will be a bit slower
5013 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5018 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5019 <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>
5020 <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>
5021 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5022 <description><p
>The last few days I came across a few good causes that should get
5023 wider attention. I recommend signing and donating to each one of
5026 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5027 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5028 Women program which is a Google Summer of Code like initiative to get
5029 more women involved in free software. One debian sponsor has offered
5030 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5031 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5032 hope you will to. :)
</p
>
5034 <p
>And the Electronic Frontier Foundation just announced plans to
5035 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5036 documentaries about the excessive spying
</a
> on every Internet user that
5037 take place these days, and their need to fund the work. I
've already
5038 donated. Are you next?
</p
>
5040 <p
>For my Norwegian audience, the organisation Studentenes og
5041 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5042 statement under the heading
5043 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5044 Access
</a
> for those of us asking for more focus on open access in the
5045 Norwegian government. So far
499 signatures. I hope you will sign it
5051 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5052 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5053 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5054 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5055 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5056 project
</a
> have been going on for a while, and have presented the
5057 vision, ideas and solution several places. Here is a little
5058 collection of videos of talks and presentation of the project.
</p
>
5062 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5063 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5065 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5066 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5068 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5069 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5070 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5071 (Youtube)
</li
>
5073 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5074 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5076 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5077 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5079 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5080 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5081 York City in
2012</a
> (Youtube)
</li
>
5083 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5084 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5085 (Youtube)
</li
>
5087 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5088 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5090 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5091 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5093 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5094 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5095 2013</a
> (Youtube)
</li
>
5099 <p
>A larger list is available from
5100 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5101 Freedombox Wiki
</a
>.
</p
>
5103 <p
>On other news, I am happy to report that Freedombox based on Debian
5104 Jessie is coming along quite well, and soon both Owncloud and using
5105 Tor should be available for testers of the Freedombox solution. :) In
5106 a few weeks I hope everything needed to test it is included in Debian.
5107 The withsqlite package is already in Debian, and the plinth package is
5108 pending in NEW. The third and vital part of that puzzle is the
5109 metapackage/setup framework, which is still pending an upload. Join
5110 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5111 (#freedombox on irc.debian.org)
</a
> and
5112 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5113 mailing list
</a
> if you want to help make this vision come true.
</p
>
5118 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5119 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5120 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5121 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5122 <description><p
>I was introduced to the
5123 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5124 in
2010, when Eben Moglen presented his vision about serving the need
5125 of non-technical people to keep their personal information private and
5126 within the legal protection of their own homes. The idea is to give
5127 people back the power over their network and machines, and return
5128 Internet back to its intended peer-to-peer architecture. Instead of
5129 depending on a central service, the Freedombox will give everyone
5130 control over their own basic infrastructure.
</p
>
5132 <p
>I
've intended to join the effort since then, but other tasks have
5133 taken priority. But this summers nasty news about the misuse of trust
5134 and privilege exercised by the
"western
" intelligence gathering
5135 communities increased my eagerness to contribute to a point where I
5136 actually started working on the project a while back.
</p
>
5138 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5139 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5140 create a simple and cheap Debian based appliance that anyone can hook
5141 up in their home and get access to secure and private services and
5142 communication. The initial deployment platform have been the
5143 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5144 which is a piece of hardware I do not own. So to be able to test what
5145 the current Freedombox setup look like, I had to come up with a way to install
5146 it on some hardware I do have access to. I have rewritten the
5147 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5148 image build framework to use .deb packages instead of only copying
5149 setup into the boot images, and thanks to this rewrite I am able to
5150 set up any machine supported by Debian Wheezy as a Freedombox, using
5151 the previously mentioned deb (and a few support debs for packages
5152 missing in Debian).
</p
>
5154 <p
>The current Freedombox setup consist of a set of bootstrapping
5156 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5157 and a administrative web interface
5158 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5159 withsqlite), as well as a privacy enhancing proxy based on
5160 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5161 (freedombox-privoxy). There is also a web/javascript based XMPP
5162 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5163 trying (unsuccessfully so far) to talk to the XMPP server
5164 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5165 web interface is pluggable, and the goal is to use it to enable OpenID
5166 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5167 this is really working yet, see
5168 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5169 project TODO
</a
> for links to GIT repositories. Most of the code is
5170 on github at the moment. The HTTP proxy is operational out of the
5171 box, and the admin web interface can be used to add/remove plinth
5172 users. I
've not been able to do anything else with it so far, but
5173 know there are several branches spread around github and other places
5174 with lots of half baked features.
</p
>
5176 <p
>Anyway, if you want to have a look at the current state, the
5177 following recipes should work to give you a test machine to poke
5180 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5184 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5185 <li
>Boot from it, either as CD or USB stick.
</li
>
5186 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5187 to the Debian installer:
<p
>
5188 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5190 <li
>Answer the few language/region/password questions and pick disk to
5191 install on.
</li
>
5193 <li
>When the installation is finished and the machine have rebooted a
5194 few times, your Freedombox is ready for testing.
</li
>
5198 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5202 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5203 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5204 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5206 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5207 </pre
></li
>
5208 <li
><p
>Run this as root:
</p
>
5210 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5213 apt-get install freedombox-setup
5214 /usr/lib/freedombox/setup
5215 </pre
></li
>
5216 <li
>Reboot into your freshly created Freedombox.
</li
>
5220 <p
>You can test it on other architectures too, but because the
5221 freedombox-privoxy package is binary, it will only work as intended on
5222 the architectures where I have had time to build the binary and put it
5223 in my APT repository. But do not let this stop you. It is only a
5224 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5226 <p
>Note that by default Freedombox is a DHCP server on the
5227 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5228 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5229 disable
</tt
>" as root.
</p
>
5231 <p
>Please let me know if this works for you, or if you have any
5232 problems. We gather on the IRC channel
5233 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5234 irc.debian.org and the
5235 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5236 mailing list
</a
>.
</p
>
5238 <p
>Once you get your freedombox operational, you can visit
5239 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5240 welcome screen (dead end - do not be surprised if you are unable to
5241 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5242 to look at the rest of plinth. The default user is
'admin
' and the
5243 default password is
'secret
'.
</p
>
5248 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5249 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5250 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5251 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5252 <description><p
>Earlier, I reported about
5253 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5254 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5255 told by IBM that the original disk should be thrown away. And as
5256 there no longer was a problem if I bricked the firmware, I decided
5257 today to try to install Intel firmware to replace the Lenovo firmware
5258 currently on the disk.
</p
>
5260 <p
>I searched the Intel site for firmware, and found
5261 <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
>
5262 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5263 according to the site should contain the latest firmware for SSD
5264 disks. I inserted the broken disk in one of my spare laptops and
5265 booted the ISO from a USB stick. The disk was recognized, but the
5266 program claimed the newest firmware already were installed and refused
5267 to insert any Intel firmware. So no change, and the disk is still
5268 unable to handle write load. :( I guess the only way to get them
5269 working would be if Lenovo releases new firmware. No idea how likely
5270 that is. Anyway, just blogging about this test for completeness. I
5271 got a working Samsung disk, and see no point in spending more time on
5272 the broken disks.
</p
>
5277 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5278 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5279 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5280 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5281 <description><p
>Today I switched to
5282 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5283 new laptop
</a
>. I
've previously written about the problems I had with
5284 my new Thinkpad X230, which was delivered with an
5285 <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
5286 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5287 sustained writes. My hardware supplier have been very forthcoming in
5288 trying to find a solution, and after first trying with another
5289 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5290 disk instead to fix it once and for all. The Samsung disk survived
5291 the installation of Debian with encrypted disks (filling the disk with
5292 random data during installation killed the first two), and I thus
5293 decided to trust it with my data. I have installed it as a Debian Edu
5294 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5295 server at home using Kerberos and LDAP, and will use it as my work
5296 station from now on.
</p
>
5298 <p
>As this is a solid state disk with no moving parts, I believe the
5299 Debian Wheezy default installation need to be tuned a bit to increase
5300 performance and increase life time of the disk. The Linux kernel and
5301 user space applications do not yet adjust automatically to such
5302 environment. To make it easier for my self, I created a draft Debian
5303 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5304 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5305 for the ssd-setup package
</a
> is available from collab-maint, and it
5306 is set up to adjust the setup of the machine by just installing the
5307 package. If there is any non-SSD disk in the machine, the package
5308 will refuse to install, as I did not try to write any logic to sort
5309 file systems in SSD and non-SSD file systems.
</p
>
5311 <p
>I consider the package a draft, as I am a bit unsure how to best
5312 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5313 where I set up the machine with one large encrypted partition (in
5314 addition to /boot), put LVM on top of this and set up partitions on
5315 top of this again. See the README file in the package source for the
5316 references I used to pick the settings. At the moment these
5317 parameters are tuned:
</p
>
5321 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5322 (adding discard to /etc/crypttab)
</li
>
5324 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5325 this case a cryptsetup partition) by changing issue_discards from
5326 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5328 <li
>Set relatime as a file system option for ext3 and ext4 file
5331 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5332 /etc/fstab.
</li
>
5334 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5336 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5337 cron.daily).
</li
>
5339 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5340 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5344 <p
>During installation, I cancelled the part where the installer fill
5345 the disk with random data, as this would kill the SSD performance for
5346 little gain. My goal with the encrypted file system is to ensure
5347 those stealing my laptop end up with a brick and not a working
5348 computer. I have no hope in keeping the really resourceful people
5349 from getting the data on the disk (see
5350 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5351 Thus I concluded that adding the discard option to crypttab is the
5352 right thing to do.
</p
>
5354 <p
>I considered using the noop I/O scheduler, as several recommended
5355 it for SSD, but others recommended deadline and a benchmark I found
5356 indicated that deadline might be better for interactive use.
</p
>
5358 <p
>I also considered using the
'discard
' file system option for ext3
5359 and ext4, but read that it would give a performance hit ever time a
5360 file is removed, and thought it best to that that slowdown once a day
5361 instead of during my work.
</p
>
5363 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5364 this is already done by Debian Edu.
</p
>
5366 <p
>I have not yet started on the user space tuning. I expect
5367 iceweasel need some tuning, and perhaps other applications too, but
5368 have not yet had time to investigate those parts.
</p
>
5370 <p
>The package should work on Ubuntu too, but I have not yet tested it
5373 <p
>As for the answer to the question in the title of this blog post,
5374 as far as I know, the only solution I know about is to replace the
5375 disk. It might be possible to flash it with Intel firmware instead of
5376 the Lenovo firmware. But I have not tried and did not want to do so
5377 without approval from Lenovo as I wanted to keep the warranty on the
5378 disk until a solution was found and they wanted the broken disks
5384 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5385 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5386 <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>
5387 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5388 <description><p
>A few days ago, I wrote about
5389 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5390 problems I experienced with my new X230 and its SSD disk
</a
>, which
5391 was dying during installation because it is unable to cope with
5392 sustained write. My supplier is in contact with
5393 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5394 replacement disk to try to fix the problem. They decided to send an
5395 identical model, so my hopes for a permanent fix was slim.
</p
>
5397 <p
>Anyway, today I got the replacement disk and tried to install
5398 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5399 same firmware version as the original. This time my hope raised
5400 slightly as the installation progressed, as the original disk used to
5401 die after
4-
7% of the disk was written to, while this time it kept
5402 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5403 died again and I was back on square one. I still do not have a new
5404 laptop with a disk I can trust. I can not live with a disk that might
5405 lock up when I download a new
5406 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5407 other large files. I look forward to hearing from my supplier with
5408 the next proposal from Lenovo.
</p
>
5410 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5411 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5412 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5413 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5414 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5415 P/N
45N8295, P0C38732.
</p
>
5417 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5418 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5419 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5420 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5421 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5422 P/N
45N8295, P0C38732.
</p
>
5424 <p
>The only difference is in the first number (serial number?), ISN,
5425 SA, date and WNPP values. Mentioning all the details here in case
5426 someone is able to use the information to find a way to identify the
5427 failing disk among working ones (if any such working disk actually
5433 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5434 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5435 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5436 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5437 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5438 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5439 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5440 member assosiation NUUG
</a
> and
5441 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5442 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5443 Bitraf
</a
>.
</p
>
5445 <p
>It starts
10:
00 and continue until late evening. Everyone is
5446 welcome, and there is no fee to participate. There is on the other
5447 hand limited space, and only room for
30 people. Please put your name
5448 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5449 wiki page
</a
> if you plan to join us.
</p
>
5454 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5455 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5457 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5458 <description><p
>Half a year ago, I reported that I had to find a
5459 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5460 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5461 time to spend on it, and it took a while to find a model I believe
5462 will do the job, but two days ago the replacement finally arrived. I
5464 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5465 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5466 a roaming workstation, and it seemed to work flawlessly. But my
5467 second installation with encrypted disk was not as successful. More
5468 on that below.
</p
>
5470 <p
>I had a hard time trying to track down a good laptop, as my most
5471 important requirements (robust and with a good keyboard) are never
5472 listed in the feature list. But I did get good help from the search
5473 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5474 allowed me to limit the list of interesting laptops based on my other
5475 requirements. A bit surprising that SSD disk are not disks according
5476 to that search interface, so I had to drop specifying the number of
5477 disks from my search parameters. I also asked around among friends to
5478 get their impression on keyboards and robustness.
</p
>
5480 <p
>So the new laptop arrived, and it is quite a lot wider than the
5481 X41. I am not quite convinced about the keyboard, as it is
5482 significantly wider than my old keyboard, and I have to stretch my
5483 hand a lot more to reach the edges. But the key response is fairly
5484 good and the individual key shape is fairly easy to handle, so I hope
5485 I will get used to it. My old X40 was starting to fail, and I really
5486 needed a new laptop now. :)
</p
>
5488 <p
>Turning off the touch pad was simple. All it took was a quick
5489 visit to the BIOS during boot it disable it.
</p
>
5491 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5492 lock up during load. And this happen when installing Debian Wheezy
5493 with encrypted disk, while the disk is being filled with random data.
5494 I also tested to install Ubuntu Raring, and it happen there too if I
5495 reenable the code to fill the disk with random data (it is disabled by
5496 default in Ubuntu). And the bug with is already known. It was
5497 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5498 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5499 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5500 kernel developers as
5501 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5502 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5503 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5504 Lenovo forums, both for
5505 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5506 2012-
11-
10</a
> and for
5507 <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
5508 03-
20-
2013</a
>. The problem do not only affect installation. The
5509 reports state that the disk lock up during use if many writes are done
5510 on the disk, so it is much no use to work around the installation
5511 problem and end up with a computer that can lock up at any moment.
5513 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5514 available
</a
> that will lock up the hard drive after running a few
5515 minutes by writing to a file.
</p
>
5517 <p
>I
've contacted my supplier and asked how to handle this, and after
5518 contacting PCHELP Norway (request
01D1FDP) which handle support
5519 requests for Lenovo, his first suggestion was to upgrade the disk
5520 firmware. Unfortunately there is no newer firmware available from
5521 Lenovo, as my disk already have the most recent one (version LF1i). I
5522 hope to hear more from him today and hope the problem can be
5528 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5529 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5530 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5531 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5532 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5533 trusty old Thinkpad X41. Unfortunately I did not have much time to
5534 spend on it, but today the replacement finally arrived. I ended up
5535 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5536 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5537 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5538 this, it is installing what I hope will be a more final installation,
5539 with a encrypted hard drive to ensure any dope head stealing it end up
5540 with an expencive door stop.
</p
>
5542 <p
>I had a hard time trying to track down a good laptop, as my most
5543 important requirements (robust and with a good keyboard) are never
5544 listed in the feature list. But I did get good help from the search
5545 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5546 allowed me to limit the list of interesting laptops based on my other
5547 requirements. A bit surprising that SSD disk are not disks, so I had
5548 to drop number of disks from my search parameters.
</p
>
5550 <p
>I am not quite convinced about the keyboard, as it is significantly
5551 wider than my old keyboard, and I have to stretch my hand a lot more
5552 to reach the edges. But the key response is fairly good and the
5553 individual key shape is fairly easy to handle, so I hope I will get
5554 used to it. My old X40 was starting to fail, and I really needed a
5555 new laptop now. :)
</p
>
5557 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5562 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5563 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5564 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5565 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5566 <description><p
>It annoys me when the computer fail to do automatically what it is
5567 perfectly capable of, and I have to do it manually to get things
5568 working. One such task is to find out what firmware packages are
5569 needed to get the hardware on my computer working. Most often this
5570 affect the wifi card, but some times it even affect the RAID
5571 controller or the ethernet card. Today I pushed version
0.4 of the
5572 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5573 including a new script isenkram-autoinstall-firmware handling the
5574 process of asking all the loaded kernel modules what firmware files
5575 they want, find debian packages providing these files and install the
5576 debian packages. Here is a test run on my laptop:
</p
>
5578 <p
><pre
>
5579 # isenkram-autoinstall-firmware
5580 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5581 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5582 info: locating packages with the requested firmware files
5583 info: Updating APT sources after adding non-free APT source
5584 info: trying to install firmware-ipw2x00
5587 Preconfiguring packages ...
5588 Selecting previously deselected package firmware-ipw2x00.
5589 (Reading database ...
259727 files and directories currently installed.)
5590 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5591 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5593 </pre
></p
>
5595 <p
>When all the requested firmware is present, a simple message is
5596 printed instead:
</p
>
5598 <p
><pre
>
5599 # isenkram-autoinstall-firmware
5600 info: did not find any firmware files requested by loaded kernel modules. exiting
5602 </pre
></p
>
5604 <p
>It could use some polish, but it is already working well and saving
5605 me some time when setting up new machines. :)
</p
>
5607 <p
>So, how does it work? It look at the set of currently loaded
5608 kernel modules, and look up each one of them using modinfo, to find
5609 the firmware files listed in the module meta-information. Next, it
5610 download the Contents file from a nearby APT mirror, and search for
5611 the firmware files in this file to locate the package with the
5612 requested firmware file. If the package is in the non-free section, a
5613 non-free APT source is added and the package is installed using
5614 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5617 <p
>I hope someone find time to implement a more polished version of
5618 this script as part of the hw-detect debian-installer module, to
5619 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5620 #
655507</a
>. There really is no need to insert USB sticks with
5621 firmware during a PXE install when the packages already are available
5622 from the nearby Debian mirror.
</p
>
5627 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5628 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5629 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5630 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5631 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5632 the screen just turn black when Linux boot, either during installation
5633 or on first boot from the hard disk. I
've seen it once in a while the
5634 last few years, but only recently understood the cause. I
've seen it
5635 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5636 The reason seem to be in the wiring of some laptops. The system to
5637 control the screen background light is inverted, so when Linux try to
5638 turn the brightness fully on, it end up turning it off instead. I do
5639 not know which Linux drivers are affected, but this post is about the
5640 i915 driver used by the
5641 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5642 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5644 <p
>The problem can be worked around two ways. Either by adding
5645 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5646 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5647 option when it load the i915 kernel module. On Debian and Ubuntu, it
5648 can be done by running these commands as root:
</p
>
5651 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5652 update-initramfs -u -k all
5655 <p
>Since March
2012 there is
5656 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5657 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5658 hardware have this problem, and get the driver to invert the
5659 brightness setting automatically. To use it, one need to add a row in
5660 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5661 intel_quirks array
</a
> in the driver source
5662 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5663 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5664 number (vendor number
8086 is assumed) and subdevice vendor and device
5667 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5668 -vvnn
</tt
> for the video card in question:
</p
>
5670 <p
><pre
>
5671 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5672 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5673 (rev
09) (prog-if
00 [VGA controller])
5674 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5675 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5676 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5677 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5678 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5680 Interrupt: pin A routed to IRQ
42
5681 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5682 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5683 Region
4: I/O ports at
4000 [size=
64]
5684 Expansion ROM at
<unassigned
> [disabled]
5685 Capabilities:
<access denied
>
5686 Kernel driver in use: i915
5687 </pre
></p
>
5689 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5691 <p
><pre
>
5692 struct intel_quirk intel_quirks[] = {
5694 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5695 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5698 </pre
></p
>
5700 <p
>According to the kernel module instructions (as seen using
5701 <tt
>modinfo i915
</tt
>), information about hardware needing the
5702 invert_brightness flag should be sent to the
5703 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5704 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5705 developers. But my email about the laptop sent
2013-
06-
03 have not
5707 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5708 web archive for the mailing list
</a
>, so I suspect they do not accept
5709 emails from non-subscribers. Because of this, I sent my patch also to
5710 the Debian bug tracking system instead as
5711 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5712 sure the patch is not lost.
</p
>
5714 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5715 with this problem working properly with Linux. If you use Gnome, your
5716 worries should be over at this point. But if you use KDE, there is
5717 something in KDE ignoring the invert_brightness setting and turning on
5718 the screen during login. I
've reported it to Debian as
5719 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5720 have no idea yet how to figure out exactly what subsystem is doing
5721 this. Perhaps you can help? Perhaps you know what the Gnome
5722 developers did to handle this, and this can give a clue to the KDE
5723 developers? Or you know where in KDE the screen brightness is changed
5724 during login? If so, please update the BTS report (or get in touch if
5725 you do not know how to update BTS).
</p
>
5727 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5728 acpi_backlight=vendor, to disable ACPI backlight support completely,
5729 as the ACPI information on the machine is trash and it is better to
5730 leave it to the intel video driver to control the screen
5731 backlight.
</p
>
5736 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5737 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5738 <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>
5739 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5740 <description><p
>Two days ago, I asked
5741 <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
5742 I could install Linux on a Packard Bell EasyNote LV computer
5743 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5744 with the obstacles put in the way of Linux users on a laptop with UEFI
5745 and Windows
8.
</p
>
5747 <p
>I never found out if the cause of my problems were the use of UEFI
5748 secure booting or fast boot. I suspect fast boot was the problem,
5749 causing the firmware to boot directly from HD without considering any
5750 key presses and alternative devices, but do not know UEFI settings
5751 enough to tell.
</p
>
5753 <p
>There is no way to install Linux on the machine in question without
5754 opening the box and disconnecting the hard drive! This is as far as I
5755 can tell, the only way to get access to the firmware setup menu
5756 without accepting the Windows
8 license agreement. I am told (and
5757 found description on how to) that it is possible to configure the
5758 firmware setup once booted into Windows
8. But as I believe the terms
5759 of that agreement are completely unacceptable, accepting the license
5760 was never an alternative. I do not enter agreements I do not intend
5761 to follow.
</p
>
5763 <p
>I feared I had to return the laptops and ask for a refund, and
5764 waste many hours on this, but luckily there was a way to get it to
5765 work. But I would not recommend it to anyone planning to run Linux on
5766 it, and I have become sceptical to Windows
8 certified laptops. Is
5767 this the way Linux will be forced out of the market place, by making
5768 it close to impossible for
"normal
" users to install Linux without
5769 accepting the Microsoft Windows license terms? Or at least not
5770 without risking to loose the warranty?
</p
>
5772 <p
>I
've updated the
5773 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5774 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5775 do not have to struggle as much as I did to get Linux into the
5778 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5779 Michael Tokarev and others for feedback and ideas.
</p
>
5784 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5785 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5786 <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>
5787 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5788 <description><p
>I
've run into quite a problem the last few days. I bought three
5789 new laptops for my parents and a few others. I bought Packard Bell
5790 Easynote LV to run Kubuntu on and use as their home computer. But I
5791 am completely unable to figure out how to install Linux on it. The
5792 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5793 instead of a BIOS to boot.
</p
>
5795 <p
>The problem is that I am unable to get it to PXE boot, and unable
5796 to get it to boot the Linux installer from my USB stick. I have yet
5797 to try the DVD install, and still hope it will work. when I turn on
5798 the computer, there is no information on what buttons to press to get
5799 the normal boot menu. I expect to get some boot menu to select PXE or
5800 USB stick booting. When booting, it first ask for the language to
5801 use, then for some regional settings, and finally if I will accept the
5802 Windows
8 terms of use. As these terms are completely unacceptable to
5803 me, I have no other choice but to turn off the computer and try again
5804 to get it to boot the Linux installer.
</p
>
5806 <p
>I have gathered my findings so far on a Linlap page about the
5807 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5808 EasyNote LV
</a
> model. If you have any idea how to get Linux
5809 installed on this machine, please get in touch or update that wiki
5810 page. If I can
't find a way to install Linux, I will have to return
5811 the laptop to the seller and find another machine for my parents.
</p
>
5813 <p
>I wonder, is this the way Linux will be forced out of the market
5814 using UEFI and
"secure boot
" by making it impossible to install Linux
5815 on new Laptops?
</p
>
5820 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5821 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5822 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5823 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5824 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5825 an operating system based on Debian intended for use in schools. It
5826 contain a turn-key solution for the computer network provided to
5827 pupils in the primary schools. It provide both the central server,
5828 network boot servers and desktop environments with heaps of
5829 educational software. The project was founded almost
12 years ago,
5830 2001-
07-
02. If you want to support the project, which is in need for
5831 cash to fund developer gatherings and other project related activity,
5832 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5833 donate some money
</a
>.
5835 <p
>A topic that come up again and again on the Debian Edu mailing
5836 lists and elsewhere, is the question on how to transform a Debian or
5837 Ubuntu installation into a Debian Edu installation. It isn
't very
5838 hard, and last week I wrote a script to replicate the steps done by
5839 the Debian Edu installer.
</p
>
5841 <p
>The script,
5842 <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/
>
5843 in the debian-edu-config package, will go through these six steps and
5844 transform an existing Debian Wheezy or Ubuntu (untested) installation
5845 into a Debian Edu Workstation:
</p
>
5849 <li
>Add skolelinux related APT sources.
</li
>
5850 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5851 <li
>Install debian-edu-install to load preseeding values and pull in
5852 our configuration.
</li
>
5853 <li
>Preseed debconf database with profile setup in
5854 /etc/debian-edu/config, and run tasksel to install packages
5855 according to the profile specified in the config above,
5856 overriding some of the Debian automation machinery.
</li
>
5857 <li
>Run debian-edu-cfengine-D installation to configure everything
5858 that could not be done using preseeding.
</li
>
5859 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5863 <p
>There are some steps in the Debian Edu installation that can not be
5864 replicated like this. Disk partitioning and LVM setup, for example.
5865 So this script just assume there is enough disk space to install all
5866 the needed packages.
</p
>
5868 <p
>The script was created to help a Debian Edu student working on
5869 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5870 Debian Edu client, and using it he can take the existing
5871 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5872 transform it into a fully functioning Debian Edu Workstation (or
5873 Roaming Workstation, or whatever :).
</p
>
5875 <p
>The default setting in the script is to create a KDE Workstation.
5876 If a LXDE based Roaming workstation is wanted instead, modify the
5877 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5879 <p
><pre
>
5880 PROFILE=
"Roaming-Workstation
"
5881 DESKTOP=
"lxde
"
5882 </pre
></p
>
5884 <p
>The script could even become useful to set up Debian Edu servers in
5885 the cloud, by starting with a virtual Debian installation at some
5886 virtual hosting service and setting up all the services on first
5892 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5893 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5894 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5895 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5896 <description><P
>In January,
5897 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5898 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5899 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5900 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5901 marvellous construction system from Denmark. We also created
5902 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5903 a place to take notes and write down our plans and hopes. And several
5904 people showed up to help. I was very happy to see the effect of my
5905 call. Since the small start, we have a debtags tag
5906 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5907 tag for LEGO related packages, and now count
10 packages related to
5908 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5910 <p
><table
>
5911 <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
>
5912 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5913 <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
>
5914 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5915 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5916 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5917 <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
>
5918 <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
>
5919 <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
>
5920 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5921 </table
></p
>
5923 <p
>Some of these are available in Wheezy, and all but one are
5924 currently available in Jessie/testing. leocad is so far only
5925 available in experimental.
</p
>
5927 <p
>If you care about LEGO in Debian, please join us on IRC and help
5928 adding the rest of the great free software tools available on Linux
5929 for LEGO designers.
</p
>
5934 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5935 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5936 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5937 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5938 <description><p
>When I woke up this morning, I was very happy to see that the
5939 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5940 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5941 Debian release, and I expect to move my machines at home over to it fairly
5944 <p
>The new debian release contain heaps of new stuff, and one program
5945 in particular make me very happy to see included. The
5946 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5947 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5948 included for the first time. Alongside similar programs like
5949 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5950 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5951 it allow for visual programming where syntax errors can not happen,
5952 and a friendly programming environment for learning to control the
5953 computer. Scratch will also be included in the next release of Debian
5956 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5957 Edu/Skolelinux release too. The
5958 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5959 alpha release
</a
> went out last week, and the next should soon
5965 <title>Isenkram
0.2 finally in the Debian archive
</title>
5966 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5967 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5968 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5969 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5970 package
</a
> finally made it into the archive, after lingering in NEW
5971 for many months. I uploaded it to the Debian experimental suite
5972 2013-
01-
27, and today it was accepted into the archive.
</p
>
5974 <p
>Isenkram is a system for suggesting to users what packages to
5975 install to work with a pluggable hardware device. The suggestion pop
5976 up when the device is plugged in. For example if a Lego Mindstorm NXT
5977 is inserted, it will suggest to install the program needed to program
5978 the NXT controller. Give it a go, and report bugs and suggestions to
5984 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5985 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5986 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5987 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5988 <description><p
>My
5989 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5990 bitcoin related blog post
</a
> mentioned that the new
5991 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5992 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5993 2013-
01-
19, and have been available in unstable since then. It was
5994 automatically copied to Ubuntu, and is available in their Raring
5995 version too.
</p
>
5997 <p
>But there is a strange problem with the build that block this new
5998 version from being available on the i386 and kfreebsd-i386
5999 architectures. For some strange reason, the autobuilders in Debian
6000 for these architectures fail to run the test suite on these
6001 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6002 We are so far unable to reproduce it when building it manually, and
6003 no-one have been able to propose a fix. If you got an idea what is
6004 failing, please let us know via the BTS.
</p
>
6006 <p
>One feature that is annoying me with of the bitcoin client, because
6007 I often run low on disk space, is the fact that the client will exit
6008 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6009 #
696715</a
>). So make sure you have enough disk space when you run
6012 <p
>As usual, if you use bitcoin and want to show your support of my
6013 activities, please send Bitcoin donations to my address
6014 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6019 <title>Welcome to the world, Isenkram!
</title>
6020 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6021 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6022 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6023 <description><p
>Yesterday, I
6024 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6025 for testers
</a
> for my prototype for making Debian better at handling
6026 pluggable hardware devices, which I
6027 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6028 out to create
</a
> earlier this month. Several valuable testers showed
6029 up, and caused me to really want to to open up the development to more
6030 people. But before I did this, I want to come up with a sensible name
6031 for this project. Today I finally decided on a new name, and I have
6032 renamed the project from hw-support-handler to this new name. In the
6033 process, I moved the source to git and made it available as a
6034 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6035 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6036 To fetch and build the latest version of the source, use
</p
>
6039 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6040 cd isenkram
&& git-buildpackage -us -uc
6043 <p
>I have not yet adjusted all files to use the new name yet. If you
6044 want to hack on the source or improve the package, please go ahead.
6045 But please talk to me first on IRC or via email before you do major
6046 changes, to make sure we do not step on each others toes. :)
</p
>
6048 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6049 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6050 stuff, in other words. I
've been told it is the Norwegian variant of
6051 the German word eisenkram, for those that are familiar with that
6054 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6055 instructions, to avoid confusing people with an error from the signing
6058 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6059 clone argument to avoid the need for authentication.
</p
>
6064 <title>First prototype ready making hardware easier to use in Debian
</title>
6065 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6066 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6067 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6068 <description><p
>Early this month I set out to try to
6069 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6070 the Debian support for pluggable hardware devices
</a
>. Now my
6071 prototype is working, and it is ready for a larger audience. To test
6073 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6074 from the Debian Edu subversion repository
</a
>, build and install the
6075 package. You might have to log out and in again activate the
6076 autostart script.
</p
>
6078 <p
>The design is simple:
</p
>
6082 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6083 hw-support-handlerd to start when the user log in.
</li
>
6085 <li
>This program listen for kernel events about new hardware (directly
6086 from the kernel like udev does), not using HAL dbus events as I
6087 initially did.
</li
>
6089 <li
>When new hardware is inserted, look up the hardware modalias in
6090 the APT database, a database
6091 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6092 via HTTP
</a
> and a database available as part of the package.
</li
>
6094 <li
>If a package is mapped to the hardware in question, the package
6095 isn
't installed yet and this is the first time the hardware was
6096 plugged in, show a desktop notification suggesting to install the
6097 package or packages.
</li
>
6099 <li
>If the user click on the
'install package now
' button, ask
6100 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6102 <li
>aptdaemon ask for root password or sudo password, and install the
6103 package while showing progress information in a window.
</li
>
6107 <p
>I still need to come up with a better name for the system. Here
6108 are some screen shots showing the prototype in action. First the
6109 notification, then the password request, and finally the request to
6110 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6112 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6113 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6114 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6115 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6116 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6118 <p
>The prototype still need to be improved with longer timeouts, but
6119 is already useful. The database of hardware to package mappings also
6120 need more work. It is currently compatible with the Ubuntu way of
6121 storing such information in the package control file, but could be
6122 changed to use other formats instead or in addition to the current
6123 method. I
've dropped the use of discover for this mapping, as the
6124 modalias approach is more flexible and easier to use on Linux as long
6125 as the Linux kernel expose its modalias strings directly.
</p
>
6127 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6128 here is the command required to check out and build the source: Use
6129 '<tt
>svn checkout
6130 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6131 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6132 devscripts package.
</p
>
6134 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6135 renamed to Isenkram and the source moved from the Debian Edu
6136 subversion repository to a Debian collab-maint git repository. See
6137 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6138 instructions
</a
> for details.
</p
>
6143 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6144 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6145 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6146 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6147 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6148 suddenly in bed. With a quiet whimper, it went completely quiet and
6149 black. The power button was no longer able to turn it on. It was a
6150 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6151 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6152 Compaq I had before that. Now I need to find a replacement. To keep
6153 going during Christmas, I moved the one year old SSD disk to my old
6154 X40 where it fitted (only one I had left that could use it), but it is
6155 not a durable solution.
6157 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6158 got a new one more than
10 years ago. It still holds true.:)
</p
>
6162 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6163 than A4).
</li
>
6164 <li
>Robust, it will be in my backpack every day.
</li
>
6165 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6166 <li
>Long battery life time. Preferable a week.
</li
>
6167 <li
>Internal WIFI network card.
</li
>
6168 <li
>Internal Twisted Pair network card.
</li
>
6169 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6170 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6171 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6173 <li
>Hardware supported by Debian Stable, ie the default kernel and
6174 X.org packages.
</li
>
6175 <li
>Quiet, preferably fan free (or at least not using the fan most of
6180 <p
>You will notice that there are no RAM and CPU requirements in the
6181 list. The reason is simply that the specifications on laptops the
6182 last
10-
15 years have been sufficient for my needs, and I have to look
6183 at other features to choose my laptop. But are there still made as
6184 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6185 robust, and Thinkpads seem to be heading in the wrong direction since
6186 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6187 still be useful.
</p
>
6189 <p
>Perhaps I should rethink my needs, and look for a pad with an
6190 external keyboard? I
'll have to check the
6191 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6192 well-supported laptops, or perhaps just buy one preinstalled from one
6193 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6194 Pre-loaded site
</a
>.
</p
>
6199 <title>How to find a browser plugin supporting a given MIME type
</title>
6200 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6201 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6202 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6203 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6204 install to get support for a given MIME type. Thanks to
6205 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6206 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6207 Unfortunately, not very many packages provide the needed meta
6208 information, Anyway, here is a small script to look up all browser
6209 plugin packages announcing ther MIME support using this specification:
</p
>
6215 def pkgs_handling_mimetype(mimetype):
6220 version = pkg.candidate
6222 version = pkg.installed
6225 record = version.record
6226 if not record.has_key(
'Npp-MimeType
'):
6228 mime_types = record[
'Npp-MimeType
'].split(
',
')
6229 for t in mime_types:
6230 t = t.rstrip().strip()
6232 thepkgs.append(pkg.name)
6234 mimetype =
"audio/ogg
"
6235 if
1 < len(sys.argv):
6236 mimetype = sys.argv[
1]
6237 print
"Browser plugin packages supporting %s:
" % mimetype
6238 for pkg in pkgs_handling_mimetype(mimetype):
6239 print
" %s
" %pkg
6242 <p
>It can be used like this to look up a given MIME type:
</p
>
6245 % ./apt-find-browserplug-for-mimetype
6246 Browser plugin packages supporting audio/ogg:
6248 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6249 Browser plugin packages supporting application/x-shockwave-flash:
6250 browser-plugin-gnash
6254 <p
>In Ubuntu this mechanism is combined with support in the browser
6255 itself to query for plugins and propose to install the needed
6256 packages. It would be great if Debian supported such feature too. Is
6257 anyone working on adding it?
</p
>
6259 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6260 request for icweasel support for this feature is
6261 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6262 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6263 of manpower and wish for a different design is the reason thus feature
6264 is not yet in iceweasel from Debian.
</p
>
6269 <title>What is the most supported MIME type in Debian?
</title>
6270 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6271 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6272 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6273 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6274 proposal to add AppStream information to the Debian archive
</a
>, is a
6275 proposal to make it possible for a Desktop application to propose to
6276 the user some package to install to gain support for a given MIME
6277 type, font, library etc. that is currently missing. With such
6278 mechanism in place, it would be possible for the desktop to
6279 automatically propose and install leocad if some LDraw file is
6280 downloaded by the browser.
</p
>
6282 <p
>To get some idea about the current content of the archive, I decided
6283 to write a simple program to extract all .desktop files from the
6284 Debian archive and look up the claimed MIME support there. The result
6286 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6287 site
</a
>. Using the collected information, it become possible to
6288 answer the question in the title. Here are the
20 most supported MIME
6289 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6290 The complete list is available from the link above.
</p
>
6292 <p
><strong
>Debian Stable:
</strong
></p
>
6296 ----- -----------------------
6312 18 application/x-ogg
6319 <p
><strong
>Debian Testing:
</strong
></p
>
6323 ----- -----------------------
6339 18 application/x-ogg
6346 <p
><strong
>Debian Unstable:
</strong
></p
>
6350 ----- -----------------------
6367 18 application/x-ogg
6373 <p
>I am told that PackageKit can provide an API to access the kind of
6374 information mentioned in DEP-
11. I have not yet had time to look at
6375 it, but hope the PackageKit people in Debian are on top of these
6378 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6379 discovering a typo in my script.
</p
>
6384 <title>Using modalias info to find packages handling my hardware
</title>
6385 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6386 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6387 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6388 <description><p
>Yesterday, I wrote about the
6389 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6390 values provided by the Linux kernel
</a
> following my hope for
6391 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6392 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6393 modalias values attached to package names can be used to map packages
6394 to hardware. This allow the system to look up and suggest relevant
6395 packages when I plug in some new hardware into my machine, and replace
6396 discover and discover-data as the database used to map hardware to
6399 <p
>I create a modaliases file with entries like the following,
6400 containing package name, kernel module name (if relevant, otherwise
6401 the package name) and globs matching the relevant hardware
6404 <p
><blockquote
>
6405 Package: package-name
6406 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6407 </blockquote
></p
>
6409 <p
>It is fairly trivial to write code to find the relevant packages
6410 for a given modalias value using this file.
</p
>
6412 <p
>An entry like this would suggest the video and picture application
6413 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6415 <p
><blockquote
>
6417 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6418 </blockquote
></p
>
6420 <p
>An entry like this would suggest the pcmciautils package when a
6421 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6423 <p
><blockquote
>
6424 Package: pcmciautils
6425 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6426 </blockquote
></p
>
6428 <p
>An entry like this would suggest the package colorhug-client when
6429 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6431 <p
><blockquote
>
6432 Package: colorhug-client
6433 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6434 </blockquote
></p
>
6436 <p
>I believe the format is compatible with the format of the Packages
6437 file in the Debian archive. Ubuntu already uses their Packages file
6438 to store their mappings from packages to hardware.
</p
>
6440 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6441 announce the hardware it support in a way my prototype understand.
6442 This allow those publishing packages in an APT source outside the
6443 Debian archive as well as those backporting packages to make sure the
6444 hardware mapping are included in the package meta information. I
've
6445 tested such header in the pymissile package, and its modalias mapping
6446 is working as it should with my prototype. It even made it to Ubuntu
6449 <p
>To test if it was possible to look up supported hardware using only
6450 the shell tools available in the Debian installer, I wrote a shell
6451 implementation of the lookup code. The idea is to create files for
6452 each modalias and let the shell do the matching. Please check out and
6454 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6455 shell script. It run without any extra dependencies and fetch the
6456 hardware mappings from the Debian archive and the subversion
6457 repository where I currently work on my prototype.
</p
>
6459 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6460 install yubikey-personalization:
</p
>
6462 <p
><blockquote
>
6463 % ./hw-support-lookup
6464 <br
>yubikey-personalization
6466 </blockquote
></p
>
6468 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6469 propose to install the pcmciautils package:
</p
>
6471 <p
><blockquote
>
6472 % ./hw-support-lookup
6473 <br
>pcmciautils
6475 </blockquote
></p
>
6477 <p
>If you know of any hardware-package mapping that should be added to
6478 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6479 database
</a
>, please tell me about it.
</p
>
6481 <p
>It could be possible to generate several of the mappings between
6482 packages and hardware. One source would be to look at packages with
6483 kernel modules, ie packages with *.ko files in /lib/modules/, and
6484 extract their modalias information. Another would be to look at
6485 packages with udev rules, ie packages with files in
6486 /lib/udev/rules.d/, and extract their vendor/model information to
6487 generate a modalias matching rule. I have not tested any of these to
6488 see if it work.
</p
>
6490 <p
>If you want to help implementing a system to let us propose what
6491 packages to install when new hardware is plugged into a Debian
6492 machine, please send me an email or talk to me on
6493 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6498 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6499 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6500 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6501 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6502 <description><p
>While looking into how to look up Debian packages based on hardware
6503 information, to find the packages that support a given piece of
6504 hardware, I refreshed my memory regarding modalias values, and decided
6505 to document the details. Here are my findings so far, also available
6507 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6508 Debian Edu subversion repository
</a
>:
6510 <p
><strong
>Modalias decoded
</strong
></p
>
6512 <p
>This document try to explain what the different types of modalias
6513 values stands for. It is in part based on information from
6514 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6515 &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;,
6516 &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
6517 &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;.
6519 <p
>The modalias entries for a given Linux machine can be found using
6520 this shell script:
</p
>
6523 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6526 <p
>The supported modalias globs for a given kernel module can be found
6527 using modinfo:
</p
>
6530 % /sbin/modinfo psmouse | grep alias:
6531 alias: serio:ty05pr*id*ex*
6532 alias: serio:ty01pr*id*ex*
6536 <p
><strong
>PCI subtype
</strong
></p
>
6538 <p
>A typical PCI entry can look like this. This is an Intel Host
6539 Bridge memory controller:
</p
>
6541 <p
><blockquote
>
6542 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6543 </blockquote
></p
>
6545 <p
>This represent these values:
</p
>
6550 sv
00001028 (subvendor)
6551 sd
000001AD (subdevice)
6553 sc
00 (bus subclass)
6557 <p
>The vendor/device values are the same values outputted from
'lspci
6558 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6559 0600. The
0600 class is a host bridge. Other useful bus values are
6560 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6562 <p
>Not sure how to figure out the interface value, nor what it
6565 <p
><strong
>USB subtype
</strong
></p
>
6567 <p
>Some typical USB entries can look like this. This is an internal
6568 USB hub in a laptop:
</p
>
6570 <p
><blockquote
>
6571 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6572 </blockquote
></p
>
6574 <p
>Here is the values included in this alias:
</p
>
6577 v
1D6B (device vendor)
6578 p
0001 (device product)
6580 dc
09 (device class)
6581 dsc
00 (device subclass)
6582 dp
00 (device protocol)
6583 ic
09 (interface class)
6584 isc
00 (interface subclass)
6585 ip
00 (interface protocol)
6588 <p
>The
0900 device class/subclass means hub. Some times the relevant
6589 class is in the interface class section. For a simple USB web camera,
6590 these alias entries show up:
</p
>
6592 <p
><blockquote
>
6593 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6594 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6595 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6596 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6597 </blockquote
></p
>
6599 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6600 camera),
0101 is audio control device and
0102 is audio streaming (aka
6601 microphone). Thus this is a camera with microphone included.
</p
>
6603 <p
><strong
>ACPI subtype
</strong
></p
>
6605 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6606 receiver in a Thinkpad X40:
</p
>
6608 <p
><blockquote
>
6609 acpi:IBM0071:PNP0511:
6610 </blockquote
></p
>
6612 <p
>The values between the colons are IDs.
</p
>
6614 <p
><strong
>DMI subtype
</strong
></p
>
6616 <p
>The DMI table contain lots of information about the computer case
6617 and model. This is an entry for a IBM Thinkpad X40, fetched from
6618 /sys/devices/virtual/dmi/id/modalias:
</p
>
6620 <p
><blockquote
>
6621 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6622 </blockquote
></p
>
6624 <p
>The values present are
</p
>
6627 bvn IBM (BIOS vendor)
6628 bvr
1UETB
6WW(
1.66) (BIOS version)
6629 bd
06/
15/
2005 (BIOS date)
6630 svn IBM (system vendor)
6631 pn
2371H4G (product name)
6632 pvr ThinkPadX40 (product version)
6633 rvn IBM (board vendor)
6634 rn
2371H4G (board name)
6635 rvr NotAvailable (board version)
6636 cvn IBM (chassis vendor)
6637 ct
10 (chassis type)
6638 cvr NotAvailable (chassis version)
6641 <p
>The chassis type
10 is Notebook. Other interesting values can be
6642 found in the dmidecode source:
</p
>
6646 4 Low Profile Desktop
6659 17 Main Server Chassis
6660 18 Expansion Chassis
6662 20 Bus Expansion Chassis
6663 21 Peripheral Chassis
6665 23 Rack Mount Chassis
6674 <p
>The chassis type values are not always accurately set in the DMI
6675 table. For example my home server is a tower, but the DMI modalias
6676 claim it is a desktop.
</p
>
6678 <p
><strong
>SerIO subtype
</strong
></p
>
6680 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6681 test machine:
</p
>
6683 <p
><blockquote
>
6684 serio:ty01pr00id00ex00
6685 </blockquote
></p
>
6687 <p
>The values present are
</p
>
6696 <p
>This type is supported by the psmouse driver. I am not sure what
6697 the valid values are.
</p
>
6699 <p
><strong
>Other subtypes
</strong
></p
>
6701 <p
>There are heaps of other modalias subtypes according to
6702 file2alias.c. There is the rest of the list from that source: amba,
6703 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6704 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6705 vmbus, x86cpu and zorro. I did not spend time documenting all of
6706 these, as they do not seem relevant for my intended use with mapping
6707 hardware to packages when new stuff is inserted during run time.
</p
>
6709 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6711 <p
>To check which kernel modules provide support for a given modalias,
6712 one can use the following shell script:
</p
>
6715 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6716 echo
"$id
" ; \
6717 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6721 <p
>The output can look like this (only the first few entries as the
6722 list is very long on my test machine):
</p
>
6726 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6728 FATAL: Module acpi:device: not found.
6730 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6731 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6732 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6733 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6734 acpi:IBM0071:PNP0511:
6735 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6736 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6737 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6741 <p
>If you want to help implementing a system to let us propose what
6742 packages to install when new hardware is plugged into a Debian
6743 machine, please send me an email or talk to me on
6744 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6746 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6747 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6748 in /sys/ with space in them.
</p
>
6753 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6754 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6755 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6756 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6757 <description><p
>As part of my investigation on how to improve the support in Debian
6758 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6759 Launcher and updated the Debian package
6760 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6761 sure udev will fix the device permissions when it is plugged in. I
6762 also added a
"Modaliases
" header to test it in the Debian archive and
6763 hopefully make the package be proposed by jockey in Ubuntu when a user
6764 plug in his rocket launcher. In the process I moved the source to a
6765 git repository under collab-maint, to make it easier for any DD to
6766 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6767 is not very active, but the software still work for me even after five
6768 years of relative silence. The new git repository is not listed in
6769 the uploaded package yet, because I want to test the other changes a
6770 bit more before I upload the new version. If you want to check out
6771 the new version with a .desktop file included, visit the
6772 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6773 view
</a
> or use
"<tt
>git clone
6774 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6779 <title>Lets make hardware dongles easier to use in Debian
</title>
6780 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6781 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6782 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6783 <description><p
>One thing that annoys me with Debian and Linux distributions in
6784 general, is that there is a great package management system with the
6785 ability to automatically install software packages by downloading them
6786 from the distribution mirrors, but no way to get it to automatically
6787 install the packages I need to use the hardware I plug into my
6788 machine. Even if the package to use it is easily available from the
6789 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6790 suggest to automatically install the python-nxt, nbc and t2n packages
6791 I need to talk to it. When I plug in a Yubikey, it could propose the
6792 yubikey-personalization package. The information required to do this
6793 is available, but no-one have pulled all the pieces together.
</p
>
6795 <p
>Some years ago, I proposed to
6796 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6797 the discover subsystem to implement this
</a
>. The idea is fairly
6802 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6803 starting when a user log in.
</li
>
6805 <li
>Set this program up to listen for kernel events emitted when new
6806 hardware is inserted into the computer.
</li
>
6808 <li
>When new hardware is inserted, look up the hardware ID in a
6809 database mapping to packages, and take note of any non-installed
6810 packages.
</li
>
6812 <li
>Show a message to the user proposing to install the discovered
6813 package, and make it easy to install it.
</li
>
6817 <p
>I am not sure what the best way to implement this is, but my
6818 initial idea was to use dbus events to discover new hardware, the
6819 discover database to find packages and
6820 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6823 <p
>Yesterday, I found time to try to implement this idea, and the
6824 draft package is now checked into
6825 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6826 Debian Edu subversion repository
</a
>. In the process, I updated the
6827 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6828 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6829 the relevant packages in Debian, and uploaded a new version
6830 2.2013.01.09 to unstable. I also discovered that the current
6831 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6832 package in Debian no longer discovered any USB devices, because
6833 /proc/bus/usb/devices is no longer present. I ported it to use
6834 libusb as a fall back option to get it working. The fixed package
6835 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6836 because of the freeze).
</p
>
6838 <p
>With this prototype in place, I can insert my Yubikey, and get this
6839 desktop notification to show up (only once, the first time it is
6840 inserted):
</p
>
6842 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6844 <p
>For this prototype to be really useful, some way to automatically
6845 install the proposed packages by pressing the
"Please install
6846 program(s)
" button should to be implemented.
</p
>
6848 <p
>If this idea seem useful to you, and you want to help make it
6849 happen, please help me update the discover-data database with mappings
6850 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6851 list the package you would like to have installed when a given
6852 hardware device is inserted into your computer, and report bugs using
6853 reportbug if it isn
't. Or, if you know of a better way to provide
6854 such mapping, please let me know.
</p
>
6856 <p
>This prototype need more work, and there are several questions that
6857 should be considered before it is ready for production use. Is dbus
6858 the correct way to detect new hardware? At the moment I look for HAL
6859 dbus events on the system bus, because that is the events I could see
6860 on my Debian Squeeze KDE desktop. Are there better events to use?
6861 How should the user be notified? Is the desktop notification
6862 mechanism the best option, or should the background daemon raise a
6863 popup instead? How should packages be installed? When should they
6864 not be installed?
</p
>
6866 <p
>If you want to help getting such feature implemented in Debian,
6867 please send me an email. :)
</p
>
6872 <title>New IRC channel for LEGO designers using Debian
</title>
6873 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6875 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6876 <description><p
>During Christmas, I have worked a bit on the Debian support for
6877 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6878 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6879 discovered I had to build all the tools myself because none were
6880 already in Debian Squeeze. If Debian support for LEGO is something
6881 you care about, please join me on the IRC channel
6882 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6883 irc.debian.org). There is a lot that could be done to improve the
6884 Debian support for LEGO designers. For example both CAD software
6885 and Mindstorm compilers are missing. :)
</p
>
6887 <p
>Update
2012-
01-
03: A
6888 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6889 including links to Lego related packages is now available.
</p
>
6894 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6895 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6896 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6897 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6898 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6899 year! I hope next year will prove to be a good year.
</p
>
6901 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6902 decentralised
"currency
" that allow people to transfer bitcoins
6903 between each other with minimal overhead, is a very interesting
6904 experiment. And as I wrote a few days ago, the bitcoin situation in
6905 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6906 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6907 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6908 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6909 for one of the ftpmasters to approve the new bitcoin-qt package
6912 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6913 team in Debian, you can easily test the package in Debian Squeeze
6914 using the following steps to get a set of working packages:
</p
>
6916 <blockquote
><pre
>
6917 git clone git://git.debian.org/git/collab-maint/bitcoin
6919 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6920 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6921 </pre
></blockquote
>
6923 <p
>You might have to install some build dependencies as well. The
6924 list of commands should give you two packages, bitcoind and
6925 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6926 client will download the complete set of bitcoin
"blocks
", which need
6927 around
5.6 GiB of data on my machine at the moment. Make sure your
6928 ~/.bitcoin/ directory have lots of spare room if you want to download
6929 all the blocks. The client will warn if the disk is getting full, so
6930 there is not really a problem if you got too little room, but you will
6931 not be able to get all the features out of the client.
</p
>
6933 <p
>As usual, if you use bitcoin and want to show your support of my
6934 activities, please send Bitcoin donations to my address
6935 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6940 <title>A word on bitcoin support in Debian
</title>
6941 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6942 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6943 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6944 <description><p
>It has been a while since I wrote about
6945 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6946 peer-to-peer based crypto-currency, and the reason is simply that I
6947 have been busy elsewhere. But two days ago, I started looking at the
6948 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6949 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6950 is now maintained by a
6951 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6952 people
</a
>, and the grunt work had already been done by this team. We
6953 owe a huge thank you to all these team members. :)
6954 But I was sad to discover that the bitcoin client is missing in
6955 Wheezy. It is only available in Sid (and an outdated client from
6956 backports). The client had several RC bugs registered in BTS blocking
6957 it from entering testing. To try to help the team and improve the
6958 situation, I spent some time providing patches and triaging the bug
6959 reports. I also had a look at the bitcoin package available from Matt
6961 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6962 Ubuntu
</a
>, and moved the useful pieces from that version into the
6963 Debian package.
</p
>
6965 <p
>After checking with the main package maintainer Jonas Smedegaard on
6966 IRC, I pushed several patches into the collab-maint git repository to
6967 improve the package. It now contains fixes for the RC issues (not from
6968 me, but fixed by Scott Howard), build rules for a Qt GUI client
6969 package, konqueror support for the bitcoin: URI and bash completion
6970 setup. As I work on Debian Squeeze, I also created
6971 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6972 patch to backport
</a
> the latest version. Jonas is going to look at
6973 it and try to integrate it into the git repository before uploading a
6974 new version to unstable.
6976 <p
>I would very much like bitcoin to succeed, to get rid of the
6977 centralized control currently exercised in the monetary system. I
6978 find it completely unacceptable that the USA government is collecting
6979 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6980 that the major credit card companies can block legal money
6981 transactions to Wikileaks. But for bitcoin to succeed, more people
6982 need to use bitcoins, and more people need to accept bitcoins when
6983 they sell products and services. Improving the bitcoin support in
6984 Debian is a small step in the right direction, but not enough.
6985 Unfortunately the user experience when browsing the web and wanting to
6986 pay with bitcoin is still not very good. The bitcoin: URI is a step
6987 in the right direction, but need to work in most or every browser in
6988 use. Also the bitcoin-qt client is too heavy to fire up to do a
6989 quick transaction. I believe there are other clients available, but
6990 have not tested them.
</p
>
6993 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6994 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6995 I received
20.15 BTC so far on the address I provided in my blog two
6996 years ago, as can be
6997 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6998 on the blockexplorer service
</a
>. Thank you everyone for your
6999 donation. The blockexplorer service demonstrates quite well that
7000 bitcoin is not quite anonymous and untracked. :) I wonder if the
7001 number of users have gone up since then. If you use bitcoin and want
7002 to show your support of my activity, please send Bitcoin donations to
7003 the same address as last time,
7004 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7009 <title>Git repository for song book for Computer Scientists
</title>
7010 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7011 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7012 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7013 <description><p
>As I
7014 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7015 this summer
</a
>, I have created a Computer Science song book a few
7016 years ago, and today I finally found time to create a public
7017 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7018 repository for the project
</a
>.
</p
>
7020 <p
>If you want to help out, please clone the source and submit patches
7021 to the HTML version. To generate the PDF and PostScript version,
7022 please use prince XML, or let me know about a useful free software
7023 processor capable of creating a good looking PDF from the HTML.
</p
>
7025 <p
>Want to sing? You can still find the song book in HTML, PDF and
7026 PostScript formats at
7027 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7028 Science Songbook
</a
>.
</p
>
7033 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7034 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7035 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7036 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7037 <description><p
>I dag fyller
7038 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7039 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7040 si gratulerer med dagen, Debian!
</p
>
7045 <title>Song book for Computer Scientists
</title>
7046 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7047 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7048 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7049 <description><p
>Many years ago, while studying Computer Science at the
7050 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7051 collecting computer related songs for use at parties. The original
7052 version was written in LaTeX, but a few years ago I got help from
7053 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7054 while keeping the ability to create a nice book in PDF format. I have
7055 not had time to maintain the book for a while now, and guess I should
7056 put it up on some public version control repository where others can
7057 help me extend and update the book. If anyone is volunteering to help
7058 me with this, send me an email. Also let me know if there are songs
7059 missing in my book.
</p
>
7061 <p
>I have not mentioned the book on my blog so far, and it occured to
7062 me today that I really should let all my readers share the joys of
7063 singing out load about programming, computers and computer networks.
7064 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7065 12</a
> is about to start (and I am not going). Want to sing? Check
7066 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7067 Computer Science Songbook
</a
>.
7072 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7073 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7074 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7075 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7076 <description><p
>At work we have heaps of servers. I believe the total count is
7077 around
1000 at the moment. To be able to get help from the vendors
7078 when something go wrong, we want to keep the firmware on the servers
7079 up to date. If the firmware isn
't the latest and greatest, the
7080 vendors typically refuse to start debugging any problems until the
7081 firmware is upgraded. So before every reboot, we want to upgrade the
7082 firmware, and we would really like everyone handling servers at the
7083 university to do this themselves when they plan to reboot a machine.
7084 For that to happen we at the unix server admin group need to provide
7085 the tools to do so.
</p
>
7087 <p
>To make firmware upgrading easier, I am working on a script to
7088 fetch and install the latest firmware for the servers we got. Most of
7089 our hardware are from Dell and HP, so I have focused on these servers
7090 so far. This blog post is about the Dell part.
</P
>
7092 <p
>On the Dell FTP site I was lucky enough to find
7093 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7094 with firmware information for all
11th generation servers, listing
7095 which firmware should be used on a given model and where on the FTP
7096 site I can find it. Using a simple perl XML parser I can then
7097 download the shell scripts Dell provides to do firmware upgrades from
7098 within Linux and reboot when all the firmware is primed and ready to
7099 be activated on the first reboot.
</p
>
7101 <p
>This is the Dell related fragment of the perl code I am working on.
7102 Are there anyone working on similar tools for firmware upgrading all
7103 servers at a site? Please get in touch and lets share resources.
</p
>
7105 <p
><pre
>
7109 use File::Temp qw(tempdir);
7111 # Install needed RHEL packages if missing
7113 'XML::Simple
' =
> 'perl-XML-Simple
',
7115 for my $module (keys %rhelmodules) {
7116 eval
"use $module;
";
7118 my $pkg = $rhelmodules{$module};
7119 system(
"yum install -y $pkg
");
7120 eval
"use $module;
";
7124 my $errorsto =
'pere@hungry.com
';
7130 sub run_firmware_script {
7131 my ($opts, $script) = @_;
7133 print STDERR
"fail: missing script name\n
";
7136 print STDERR
"Running $script\n\n
";
7138 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7139 print STDERR
"success: firmware script ran succcessfully\n
";
7141 print STDERR
"fail: firmware script returned error\n
";
7145 sub run_firmware_scripts {
7146 my ($opts, @dirs) = @_;
7147 # Run firmware packages
7148 for my $dir (@dirs) {
7149 print STDERR
"info: Running scripts in $dir\n
";
7150 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7151 while (my $s = readdir $dh) {
7152 next if $s =~ m/^\.\.?/;
7153 run_firmware_script($opts,
"$dir/$s
");
7161 print STDERR
"info: Downloading $url\n
";
7162 system(
"wget --quiet \
"$url\
"");
7167 my $product = `dmidecode -s system-product-name`;
7170 if ($product =~ m/PowerEdge/) {
7172 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7173 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7175 my $tmpdir = tempdir(
7179 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7180 system(
'gunzip Catalog.xml.gz
');
7181 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7182 # -q is quiet, disabling interactivity and reducing console output
7183 my $fwopts =
"-q
";
7185 for my $url (@paths) {
7186 fetch_dell_fw($url);
7188 run_firmware_scripts($fwopts, $tmpdir);
7190 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7191 print STDERR
"error: Please report to $errorsto.\n
";
7195 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7196 print STDERR
"error: Please report to $errorsto.\n
";
7202 my $url =
"ftp://ftp.us.dell.com/$path
";
7206 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7207 # firmware packages to download from Dell. Only work for Linux
7208 # machines and
11th generation Dell servers.
7209 sub fetch_dell_fw_list {
7210 my $filename = shift;
7212 my $product = `dmidecode -s system-product-name`;
7214 my ($mybrand, $mymodel) = split(/\s+/, $product);
7216 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7218 my $xml = XMLin($filename);
7220 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7221 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7222 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7224 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7225 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7227 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7229 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7231 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7234 for my $component (@{$xml-
>{SoftwareComponent}}) {
7235 my $componenttype = $component-
>{ComponentType}-
>{value};
7237 # Drop application packages, only firmware and BIOS
7238 next if
'APAC
' eq $componenttype;
7240 my $cpath = $component-
>{path};
7241 for my $path (@paths) {
7242 if ($cpath =~ m%/$path$%) {
7243 push(@paths, $cpath);
7251 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7252 it could work on other platforms with some tweaking. Anyone know a
7253 index like Catalog.xml is available from HP for HP servers? At the
7254 moment I maintain a similar list manually and it is quickly getting
7260 <title>How is booting into runlevel
1 different from single user boots?
</title>
7261 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7262 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7263 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7264 <description><p
>Wouter Verhelst have some
7265 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7266 comments and opinions
</a
> on my blog post on
7267 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7268 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7269 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7270 default KDE desktop in Debian
</a
>. I only have time to address one
7271 small piece of his comment now, and though it best to address the
7272 misunderstanding he bring forward:
</p
>
7274 <p
><blockquote
>
7275 Currently, a system admin has four options: [...] boot to a
7276 single-user system (by adding
'single
' to the kernel command line;
7277 this runs rcS and rc1 scripts)
7278 </blockquote
></p
>
7280 <p
>This make me believe Wouter believe booting into single user mode
7281 and booting into runlevel
1 is the same. I am not surprised he
7282 believe this, because it would make sense and is a quite sensible
7283 thing to believe. But because the boot in Debian is slightly broken,
7284 runlevel
1 do not work properly and it isn
't the same as single user
7285 mode. I
'll try to explain what is actually happing, but it is a bit
7286 hard to explain.
</p
>
7288 <p
>Single user mode is defined like this in /etc/inittab:
7289 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7290 executed in single user mode is sulogin. Single user mode is a boot
7291 state
"between
" the runlevels, and when booting into single user mode,
7292 only the scripts in /etc/rcS.d/ are executed before the init process
7293 enters the single user state. When switching to runlevel
1, the state
7294 is in fact not ending in runlevel
1, but it passes through runlevel
1
7295 and end up in the single user mode (see /etc/rc1.d/S03single, which
7296 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7297 1. It is confusing that the
'S
' (single user) init mode is not the
7298 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7301 <p
>This summary might make it clearer. When booting for the first
7302 time into single user mode, the following commands are executed:
7303 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7304 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7305 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7306 trying to continue after visiting single user mode. Not all services
7307 are started again as they should, causing the machine to end up in an
7308 unpredicatble state. This is why Debian admins recommend rebooting
7309 after visiting single user mode.
</p
>
7311 <p
>A similar problem with runlevel
1 is caused by the amount of
7312 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7313 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7314 stopped when passing through the scripts in /etc/rc1.d/, and not
7315 started again when switching away from runlevel
1 to the runlevels
7316 2-
5. I believe the problem is best fixed by moving all the scripts
7317 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7318 functioning single user mode during boot.
</p
>
7320 <p
>I have spent several years investigating the Debian boot system,
7321 and discovered this problem a few years ago. I suspect it originates
7322 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7327 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7328 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7329 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7330 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7331 <description><p
>In the Debian boot system, several packages include scripts that
7332 are started from /etc/rcS.d/. In fact, there is a bite more of them
7333 than make sense, and this causes a few problems. What kind of
7334 problems, you might ask. There are at least two problems. The first
7335 is that it is not possible to recover a machine after switching to
7336 runlevel
1. One need to actually reboot to get the machine back to
7337 the expected state. The other is that single user boot will sometimes
7338 run into problems because some of the subsystems are activated before
7339 the root login is presented, causing problems when trying to recover a
7340 machine from a problem in that subsystem. A minor additional point is
7341 that moving more scripts out of rcS.d/ and into the other rc#.d/
7342 directories will increase the amount of scripts that can run in
7343 parallel during boot, and thus decrease the boot time.
</p
>
7345 <p
>So, which scripts should start from rcS.d/. In short, only the
7346 scripts that _have_ to execute before the root login prompt is
7347 presented during a single user boot should go there. Everything else
7348 should go into the numeric runlevels. This means things like
7349 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7350 the numeric runlevels. Today in Debian, there are around
115 init.d
7351 scripts that are started from rcS.d/, and most of them should be moved
7352 out. Do your package have one of them? Please help us make single
7353 user and runlevel
1 better by moving it.
</p
>
7355 <p
>Scripts setting up the screen, keyboard, system partitions
7356 etc. should still be started from rcS.d/, but there is for example no
7357 need to have the network enabled before the single user login prompt
7358 is presented.
</p
>
7360 <p
>As always, things are not so easy to fix as they sound. To keep
7361 Debian systems working while scripts migrate and during upgrades, the
7362 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7363 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7364 and the next ones can only be moved when their dependencies have been
7365 moved first. This migration must be done sequentially while we ensure
7366 that the package system upgrade packages in the right order to keep
7367 the system state correct. This will require some coordination when it
7368 comes to network related packages, but most of the packages with
7369 scripts that should migrate do not have anything in rcS.d/ depending
7370 on them. Some packages have already been updated, like the sudo
7371 package, while others are still left to do. I wish I had time to work
7372 on this myself, but real live constrains make it unlikely that I will
7373 find time to push this forward.
</p
>
7378 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7379 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7380 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7381 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7382 <description><p
>While at Debconf11, I have several times during discussions
7383 mentioned the issues I believe should be improved in Debian for its
7384 desktop to be useful for more people. The use case for this is my
7385 parents, which are currently running Kubuntu which solve the
7388 <p
>I suspect these four missing features are not very hard to
7389 implement. After all, they are present in Ubuntu, so if we wanted to
7390 do this in Debian we would have a source.
</p
>
7394 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7395 are new packages available for upgrades, a icon in the KDE status bar
7396 indicate this, and clicking on it will activate the simple upgrade
7397 tool to handle it. I have no problem guiding both of my parents
7398 through the process over the phone. If a kernel reboot is required,
7399 this too is indicated by the status bars and the upgrade tool. Last
7400 time I checked, nothing with the same features was working in KDE in
7403 <li
><strong
>Simple handling of missing Firefox browser
7404 plugins.
</strong
> When the browser encounter a MIME type it do not
7405 currently have a handler for, it will ask the user if the system
7406 should search for a package that would add support for this MIME type,
7407 and if the user say yes, the APT sources will be searched for packages
7408 advertising the MIME type in their control file (visible in the
7409 Packages file in the APT archive). If one or more packages are found,
7410 it is a simple click of the mouse to add support for the missing mime
7411 type. If the package require the user to accept some non-free
7412 license, this is explained to the user. The entire process make it
7413 more clear to the user why something do not work in the browser, and
7414 make the chances higher for the user to blame the web page authors and
7415 not the browser for any missing features.
</li
>
7417 <li
><strong
>Simple handling of missing multimedia codec/format
7418 handlers.
</strong
> When the media players encounter a format or codec
7419 it is not supporting, a dialog pop up asking the user if the system
7420 should search for a package that would add support for it. This
7421 happen with things like MP3, Windows Media or H
.264. The selection
7422 and installation procedure is very similar to the Firefox browser
7423 plugin handling. This is as far as I know implemented using a
7424 gstreamer hook. The end result is that the user easily get access to
7425 the codecs that are present from the APT archives available, while
7426 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7428 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7429 displaying a text/plain file in my Debian browser, it will propose to
7430 start emacs to show it. If I remember correctly, when doing the same
7431 in Kunbutu it show the file as a text file in the browser. At least I
7432 know Opera will show text files within the browser. I much prefer the
7433 latter behaviour.
</li
>
7437 <p
>There are other nice features as well, like the simplified suite
7438 upgrader, but given that I am the one mostly doing the dist-upgrade,
7439 it do not matter much.
</p
>
7441 <p
>I really hope we could get these features in place for the next
7442 Debian release. It would require the coordinated effort of several
7443 maintainers, but would make the end user experience a lot better.
</p
>
7448 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7449 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7450 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7451 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7452 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7453 site is build on Debian/Squeeze, and this platform was chosen because
7454 I am most familiar with Debian (being a Debian Developer for around
10
7455 years) because it is the latest stable Debian release which should get
7456 security support for a few years.
</p
>
7458 <p
>The web service is written in Perl, and depend on some perl modules
7459 that are missing in Debian at the moment. It would be great if these
7460 modules were added to the Debian archive, allowing anyone to set up
7461 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7462 in their own country using only Debian packages. The list of modules
7463 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7464 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7465 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7466 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7467 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7468 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7469 easier in the future.
</p
>
7471 <p
>Thanks to the great tools in Debian, getting the missing modules
7472 installed on my server was a simple call to
'cpan2deb Module::Name
'
7473 and
'dpkg -i
' to install the resulting package. But this leave me
7474 with the responsibility of tracking security problems, which I really
7475 do not have time for.
</p
>
7480 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7481 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7482 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7483 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7484 <description><p
>Here is a small update for my English readers. Most of my blog
7485 posts have been in Norwegian the last few weeks, so here is a short
7486 update in English.
</p
>
7488 <p
>The kids still keep me too busy to get much free software work
7489 done, but I did manage to organise a project to get a Norwegian port
7490 of the British service
7491 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7492 and it has been running for a month now. The entire project has been
7493 organised by me and two others. Around Christmas we gathered sponsors
7494 to fund the development work. In January I drafted a contract with
7495 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7496 and in February the development took place. Most of it involved
7497 converting the source to use GPS coordinates instead of British
7498 easting/northing, and the resulting code should be a lot easier to get
7499 running in any country by now. The Norwegian
7500 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7501 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7502 source and the source for administrative borders in Norway, and
7503 support for this had to be added/fixed.
</p
>
7505 <p
>The Norwegian version went live March
3th, and we spent the weekend
7506 polishing the system before we announced it March
7th. The system is
7507 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7508 problem reports in a few weeks. Soon we hope to announce the Android
7509 and iPhone versions making it even easier to report problems with the
7510 public infrastructure.
</p
>
7512 <p
>Perhaps something to consider for those of you in countries without
7513 such service?
</p
>
7518 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7519 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7520 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7521 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7522 <description><p
>The last few days I have looked at ways to track open security
7523 issues here at my work with the University of Oslo. My idea is that
7524 it should be possible to use the information about security issues
7525 available on the Internet, and check our locally
7526 maintained/distributed software against this information. It should
7527 allow us to verify that no known security issues are forgotten. The
7528 CVE database listing vulnerabilities seem like a great central point,
7529 and by using the package lists from Debian mapped to CVEs provided by
7530 the testing security team, I believed it should be possible to figure
7531 out which security holes were present in our free software
7532 collection.
</p
>
7534 <p
>After reading up on the topic, it became obvious that the first
7535 building block is to be able to name software packages in a unique and
7536 consistent way across data sources. I considered several ways to do
7537 this, for example coming up with my own naming scheme like using URLs
7538 to project home pages or URLs to the Freshmeat entries, or using some
7539 existing naming scheme. And it seem like I am not the first one to
7540 come across this problem, as MITRE already proposed and implemented a
7541 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7542 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7543 software, hardware and other platform components. The CPE ids are
7544 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7545 Vulnerability Database
</a
>, allowing me to look up know security
7546 issues for any CPE name. With this in place, all I need to do is to
7547 locate the CPE id for the software packages we use at the university.
7548 This is fairly trivial (I google for
'cve cpe $package
' and check the
7549 NVD entry if a CVE for the package exist).
</p
>
7551 <p
>To give you an example. The GNU gzip source package have the CPE
7552 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7553 check out, one could look up
7554 <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
7555 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7556 The most recent one is
7557 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7558 and at the bottom of the NVD page for this vulnerability the complete
7559 list of affected versions is provided.
</p
>
7561 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7562 for offline processing of issues. Using this dump, I
've written a
7563 small script taking a list of CPEs as input and list all CVEs
7564 affecting the packages represented by these CPEs. One give it CPEs
7565 with version numbers as specified above and get a list of open
7566 security issues out.
</p
>
7568 <p
>Of course for this approach to be useful, the quality of the NVD
7569 information need to be high. For that to happen, I believe as many as
7570 possible need to use and contribute to the NVD database. I notice
7572 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7573 map from CVE to CPE
</a
>, indicating that they are using the CPE
7574 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7576 <p
>To get an idea about the quality for free software, I spent some
7577 time making it possible to compare the CVE database from Debian with
7578 the CVE database in NVD. The result look fairly good, but there are
7579 some inconsistencies in NVD (same software package having several
7580 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7581 Debian believe are affected by a CVE). Hope to find time to improve
7582 the quality of NVD, but that require being able to get in touch with
7583 someone maintaining it. So far my three emails with questions and
7584 corrections have not seen any reply, but I hope contact can be
7585 established soon.
</p
>
7587 <p
>An interesting application for CPEs is cross platform package
7588 mapping. It would be useful to know which packages in for example
7589 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7590 this would be trivial if all linux distributions provided CPE entries
7591 for their packages.
</p
>
7596 <title>Which module is loaded for a given PCI and USB device?
</title>
7597 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7599 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7600 <description><p
>In the
7601 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7602 package in Debian, there is a script to report useful information
7603 about the running hardware for use when people report missing
7604 information. One part of this script that I find very useful when
7605 debugging hardware problems, is the part mapping loaded kernel module
7606 to the PCI device it claims. It allow me to quickly see if the kernel
7607 module I expect is driving the hardware I am struggling with. To see
7608 the output, make sure discover-data is installed and run
7609 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7610 one of my machines like this:
</p
>
7614 10de:
03eb i2c_nforce2
7617 10de:
03f0 snd_hda_intel
7626 <p
>The code in question look like this, slightly modified for
7627 readability and to drop the output to file descriptor
3:
</p
>
7630 if [ -d /sys/bus/pci/devices/ ] ; then
7631 echo loaded pci modules:
7633 cd /sys/bus/pci/devices/
7634 for address in * ; do
7635 if [ -d
"$address/driver/module
" ] ; then
7636 module=`cd $address/driver/module ; pwd -P | xargs basename`
7637 if grep -q
"^$module
" /proc/modules ; then
7638 address=$(echo $address |sed s/
0000://)
7639 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7640 echo
"$id $module
"
7649 <p
>Similar code could be used to extract USB device module
7653 if [ -d /sys/bus/usb/devices/ ] ; then
7654 echo loaded usb modules:
7656 cd /sys/bus/usb/devices/
7657 for address in * ; do
7658 if [ -d
"$address/driver/module
" ] ; then
7659 module=`cd $address/driver/module ; pwd -P | xargs basename`
7660 if grep -q
"^$module
" /proc/modules ; then
7661 address=$(echo $address |sed s/
0000://)
7662 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7663 if [
"$id
" ] ; then
7664 echo
"$id $module
"
7674 <p
>This might perhaps be something to include in other tools as
7680 <title>How to test if a laptop is working with Linux
</title>
7681 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7682 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7683 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7684 <description><p
>The last few days I have spent at work here at the
<a
7685 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7686 batch of computers will work with Linux. Every year for the last few
7687 years the university have organised shared bid of a few thousand
7688 computers, and this year HP won the bid. Two different desktops and
7689 five different laptops are on the list this year. We in the UNIX
7690 group want to know which one of these computers work well with RHEL
7691 and Ubuntu, the two Linux distributions we currently handle at the
7692 university.
</p
>
7694 <p
>My test method is simple, and I share it here to get feedback and
7695 perhaps inspire others to test hardware as well. To test, I PXE
7696 install the OS version of choice, and log in as my normal user and run
7697 a few applications and plug in selected pieces of hardware. When
7698 something fail, I make a note about this in the test matrix and move
7699 on. If I have some spare time I try to report the bug to the OS
7700 vendor, but as I only have the machines for a short time, I rarely
7701 have the time to do this for all the problems I find.
</p
>
7703 <p
>Anyway, to get to the point of this post. Here is the simple tests
7704 I perform on a new model.
</p
>
7708 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7709 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7710 RHEL5 and Debian Edu/Squeeze.
</li
>
7712 <li
>Is X.org working? If the graphical login screen show up after
7713 installation, X.org is working.
</li
>
7715 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7716 package mesa-utils on Ubuntu) and writing down the frames per second
7717 reported by the program.
</li
>
7719 <li
>Is sound working? With Gnome and KDE, a sound is played when
7720 logging in, and if I can hear this the test is successful. If there
7721 are several audio exits on the machine, I try them all and check if
7722 the Gnome/KDE audio mixer can control where to send the sound. I
7723 normally test this by playing
7724 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7725 video
</a
> in Firefox/Iceweasel.
</li
>
7727 <li
>Is the USB subsystem working? I test this by plugging in a USB
7728 memory stick and see if Gnome/KDE notices this.
</li
>
7730 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7731 I have lying around, and see if Gnome/KDE notices this.
</li
>
7733 <li
>Is any built in camera working? Test using cheese, and see if a
7734 picture from the v4l device show up.
</li
>
7736 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7737 any bluetooth devices are discovered. In my office, I normally see a
7740 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7741 memory modules lying around, and stick them in and see if Gnome/KDE
7742 notice this.
</li
>
7744 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7745 special button work, and if the laptop continue to work after
7748 <li
>For laptops, is the extra buttons working, like audio level,
7749 adjusting background light, switching on/off external video output,
7750 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7751 laptop to laptop, so I just write down which are working and which are
7754 <li
>Some laptops have smart card readers, finger print readers,
7755 acceleration sensors etc. I rarely test these, as I do not know how
7756 to quickly test if they are working or not, so I only document their
7757 existence.
</li
>
7761 <p
>By now I suspect you are really curious what the test results are
7762 for the HP machines I am testing. I
'm not done yet, so I will report
7763 the test results later. For now I can report that HP
8100 Elite work
7764 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7765 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7766 can see, I have most machines left to test. One interesting
7767 observation is that Ubuntu Lucid has almost twice the frame rate than
7768 RHEL6 with glxgears. No idea why.
</p
>
7773 <title>Some thoughts on BitCoins
</title>
7774 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7775 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7776 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7777 <description><p
>As I continue to explore
7778 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7779 what properties the system have, and how it will be affected by laws
7780 and regulations here in Norway. Here are some random notes.
</p
>
7782 <p
>One interesting thing to note is that since the transactions are
7783 verified using a peer to peer network, all details about a transaction
7784 is known to everyone. This means that if a BitCoin address has been
7785 published like I did with mine in my initial post about BitCoin, it is
7786 possible for everyone to see how many BitCoins have been transfered to
7787 that address. There is even a web service to look at the details for
7788 all transactions. There I can see that my address
7789 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7790 have received
16.06 Bitcoin, the
7791 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7792 address of Simon Phipps have received
181.97 BitCoin and the address
7793 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7794 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7795 every one of you that donated bitcoins to support my activity. The
7796 fact that anyone can see how much money was transfered to a given
7797 address make it more obvious why the BitCoin community recommend to
7798 generate and hand out a new address for each transaction. I
'm told
7799 there is no way to track which addresses belong to a given person or
7800 organisation without the person or organisation revealing it
7801 themselves, as Simon, EFF and I have done.
</p
>
7803 <p
>In Norway, and in most other countries, there are laws and
7804 regulations limiting how much money one can transfer across the border
7805 without declaring it. There are money laundering, tax and accounting
7806 laws and regulations I would expect to apply to the use of BitCoin.
7807 If the Skolelinux foundation
7808 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7809 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7810 normal bank transfers like EFF is doing, how should this be accounted?
7811 Given that it is impossible to know if money can cross the border or
7812 not, should everything or nothing be declared? What exchange rate
7813 should be used when calculating taxes? Would receivers have to pay
7814 income tax if the foundation were to pay Skolelinux contributors in
7815 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7817 <p
>For a currency to be useful and successful, it must be trusted and
7818 accepted by a lot of users. It must be possible to get easy access to
7819 the currency (as a wage or using currency exchanges), and it must be
7820 easy to spend it. At the moment BitCoin seem fairly easy to get
7821 access to, but there are very few places to spend it. I am not really
7822 a regular user of any of the vendor types currently accepting BitCoin,
7823 so I wonder when my kind of shop would start accepting BitCoins. I
7824 would like to buy electronics, travels and subway tickets, not herbs
7825 and books. :) The currency is young, and this will improve over time
7826 if it become popular, but I suspect regular banks will start to lobby
7827 to get BitCoin declared illegal if it become popular. I
'm sure they
7828 will claim it is helping fund terrorism and money laundering (which
7829 probably would be true, as is any currency in existence), but I
7830 believe the problems should be solved elsewhere and not by blaming
7831 currencies.
</p
>
7833 <p
>The process of creating new BitCoins is called mining, and it is
7834 CPU intensive process that depend on a bit of luck as well (as one is
7835 competing against all the other miners currently spending CPU cycles
7836 to see which one get the next lump of cash). The
"winner
" get
50
7837 BitCoin when this happen. Yesterday I came across the obvious way to
7838 join forces to increase ones changes of getting at least some coins,
7839 by coordinating the work on mining BitCoins across several machines
7840 and people, and sharing the result if one is lucky and get the
50
7842 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7843 if this sounds interesting. I have not had time to try to set up a
7844 machine to participate there yet, but have seen that running on ones
7845 own for a few days have not yield any BitCoins througth mining
7848 <p
>Update
2010-
12-
15: Found an
<a
7849 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7850 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7851 it was interesting to read. The arguments presented seem to be
7852 equally valid for gold, which was used as a currency for many years.
</p
>
7857 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7858 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7860 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7861 <description><p
>With this weeks lawless
7862 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7863 attacks
</a
> on Wikileak and
7864 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7865 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7866 not be trusted to handle money transactions.
7868 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7869 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7870 mine mentioned earlier. I decided to follow Simon
's example, and get
7871 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7872 some help from my friend to get it all running, and he even handed me
7873 some bitcoins to get started. I even donated a few bitcoins to Simon
7874 for helping me remember BitCoin.
</p
>
7876 <p
>So, what is bitcoins, you probably wonder? It is a digital
7877 crypto-currency, decentralised and handled using peer-to-peer
7878 networks. It allows anonymous transactions and prohibits central
7879 control over the transactions, making it impossible for governments
7880 and companies alike to block donations and other transactions. The
7881 source is free software, and while the key dependency wxWidgets
2.9
7882 for the graphical user interface is missing in Debian, the command
7883 line client builds just fine. Hopefully Jonas
7884 <a href=
"http://bugs.debian.org/
578157">will get the package into
7885 Debian
</a
> soon.
</p
>
7887 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7888 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7889 bitcoins
</a
> when selling services and goods, and there are even
7890 currency
"stock
" markets where the exchange rate is decided. There
7891 are not many users so far, but the concept seems promising. If you
7892 want to get started and lack a friend with any bitcoins to spare,
7894 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7895 bitcoin at the time of writing). Use
7896 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7897 on the current exchange rates.
</p
>
7899 <p
>As an experiment, I have decided to set up bitcoind on one of my
7900 machines. If you want to support my activity, please send Bitcoin
7901 donations to the address
7902 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7907 <title>Why isn
't Debian Edu using VLC?
</title>
7908 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7909 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7910 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7911 <description><p
>In the latest issue of Linux Journal, the readers choices were
7912 presented, and the winner among the multimedia player were VLC.
7913 Personally, I like VLC, and it is my player of choice when I first try
7914 to play a video file or stream. Only if VLC fail will I drag out
7915 gmplayer to see if it can do better. The reason is mostly the failure
7916 model and trust. When VLC fail, it normally pop up a error message
7917 reporting the problem. When mplayer fail, it normally segfault or
7918 just hangs. The latter failure mode drain my trust in the program.
<p
>
7920 <p
>But even if VLC is my player of choice, we have choosen to use
7921 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7922 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7923 plugin to play web videos seamlessly, and the VLC browser plugin is
7924 not very good. For example, it lack in-line control buttons, so there
7925 is no way for the user to pause the video. Also, when I
7926 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7927 tested the browser plugins
</a
> available in Debian, the VLC plugin
7928 failed on several video pages where mplayer based plugins worked. If
7929 the browser plugin for VLC was as good as the gecko-mediaplayer
7930 package (which uses mplayer), we would switch.
</P
>
7932 <p
>While VLC is a good player, its user interface is slightly
7933 annoying. The most annoying feature is its inconsistent use of
7934 keyboard shortcuts. When the player is in full screen mode, its
7935 shortcuts are different from when it is playing the video in a window.
7936 For example, space only work as pause when in full screen mode. I
7937 wish it had consisten shortcuts and that space also would work when in
7938 window mode. Another nice shortcut in gmplayer is [enter] to restart
7939 the current video. It is very nice when playing short videos from the
7940 web and want to restart it when new people arrive to have a look at
7941 what is going on.
</p
>
7946 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7947 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7948 <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>
7949 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7950 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7951 upgrade testing of the
7952 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7953 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7954 This seem like a very good idea, so I adjusted by test scripts and
7955 can now present the updated result from today:
</p
>
7957 <p
>This is for Gnome:
</p
>
7959 <p
>Installed using apt-get, missing with aptitude
</p
>
7961 <blockquote
><p
>
7966 browser-plugin-gnash
7973 freedesktop-sound-theme
7975 gconf-defaults-service
7990 gnome-desktop-environment
7994 gnome-session-canberra
7999 gstreamer0.10-fluendo-mp3
8005 libapache2-mod-dnssd
8008 libaprutil1-dbd-sqlite3
8011 libboost-date-time1.42
.0
8012 libboost-python1.42
.0
8013 libboost-thread1.42
.0
8015 libchamplain-gtk-
0.4-
0
8017 libclutter-gtk-
0.10-
0
8024 libfreerdp-plugins-standard
8039 libgnomepanel2.24-cil
8044 libgtksourceview2.0-common
8045 libmono-addins-gui0.2-cil
8046 libmono-addins0.2-cil
8047 libmono-cairo2.0-cil
8048 libmono-corlib2.0-cil
8049 libmono-i18n-west2.0-cil
8050 libmono-posix2.0-cil
8051 libmono-security2.0-cil
8052 libmono-sharpzip2.84-cil
8053 libmono-system2.0-cil
8056 libndesk-dbus-glib1.0-cil
8057 libndesk-dbus1.0-cil
8067 libtelepathy-farsight0
8076 nautilus-sendto-empathy
8080 python-aptdaemon-gtk
8082 python-beautifulsoup
8097 python-gtksourceview2
8108 python-pkg-resources
8115 python-twisted-conch
8121 python-zope.interface
8126 rhythmbox-plugin-cdrecorder
8133 system-config-printer-udev
8135 telepathy-mission-control-
5
8146 </p
></blockquote
>
8148 <p
>Installed using apt-get, removed with aptitude
</p
>
8150 <blockquote
><p
>
8156 fast-user-switch-applet
8175 libgtksourceview2.0-
0
8177 libsdl1.2debian-alsa
8183 system-config-printer
8188 </p
></blockquote
>
8190 <p
>Installed using aptitude, missing with apt-get
</p
>
8192 <blockquote
><p
>
8193 gstreamer0.10-gnomevfs
8194 </p
></blockquote
>
8196 <p
>Installed using aptitude, removed with apt-get
</p
>
8198 <blockquote
><p
>
8200 </p
></blockquote
>
8202 <p
>This is for KDE:
</p
>
8204 <p
>Installed using apt-get, missing with aptitude
</p
>
8206 <blockquote
><p
>
8208 </p
></blockquote
>
8210 <p
>Installed using apt-get, removed with aptitude
</p
>
8212 <blockquote
><p
>
8215 </p
></blockquote
>
8217 <p
>Installed using aptitude, missing with apt-get
</p
>
8219 <blockquote
><p
>
8233 kdeartwork-emoticons
8235 kdeartwork-theme-icon
8239 kdebase-workspace-bin
8240 kdebase-workspace-data
8254 kscreensaver-xsavers
8269 plasma-dataengines-workspace
8271 plasma-desktopthemes-artwork
8272 plasma-runners-addons
8273 plasma-scriptengine-googlegadgets
8274 plasma-scriptengine-python
8275 plasma-scriptengine-qedje
8276 plasma-scriptengine-ruby
8277 plasma-scriptengine-webkit
8278 plasma-scriptengines
8279 plasma-wallpapers-addons
8280 plasma-widget-folderview
8281 plasma-widget-networkmanagement
8285 xscreensaver-data-extra
8287 xscreensaver-gl-extra
8288 xscreensaver-screensaver-bsod
8289 </p
></blockquote
>
8291 <p
>Installed using aptitude, removed with apt-get
</p
>
8293 <blockquote
><p
>
8295 google-gadgets-common
8313 libggadget-qt-
1.0-
0b
8318 libkonqsidebarplugin4a
8327 libplasma-geolocation-interface4
8329 libplasmagenericshell4
8343 libsmokeknewstuff2-
3
8344 libsmokeknewstuff3-
3
8346 libsmokektexteditor3
8354 libsmokeqtnetwork4-
3
8360 libsmokeqtuitools4-
3
8372 plasma-dataengines-addons
8373 plasma-scriptengine-superkaramba
8374 plasma-widget-lancelot
8375 plasma-widgets-addons
8376 plasma-widgets-workspace
8380 update-notifier-common
8381 </p
></blockquote
>
8383 <p
>Running apt-get autoremove made the results using apt-get and
8384 aptitude a bit more similar, but there are still quite a lott of
8385 differences. I have no idea what packages should be installed after
8386 the upgrade, but hope those that do can have a look.
</p
>
8391 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8392 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8393 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8394 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8395 <description><p
>Most of the computers in use by the
8396 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8397 are virtual machines. And they have been Xen machines running on a
8398 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8399 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8400 bit harder that it could have been, because we set up the Xen virtual
8401 machines to get the virtual partitions from LVM, which as far as I
8402 know is not supported by KVM. So to migrate, we had to convert
8403 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8406 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8407 nice recipe
</a
> to do this, and wrote the following script to do the
8408 migration. It uses qemu-img from the qemu package to make the disk
8409 image, parted to partition it, losetup and kpartx to present the disk
8410 image partions as devices, and dd to copy the data. I NFS mounted the
8411 new servers storage area on the old server to do the migration.
</p
>
8417 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8422 if [ -z
"$
1" ] ; then
8423 echo
"Usage: $
0 &lt;hostname
&gt;
"
8429 if [ ! -e /dev/vg_data/$host-disk ] ; then
8430 echo
"error: unable to find LVM volume for $host
"
8434 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8435 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8436 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8437 totalsize=$(( ( $disksize + $swapsize ) ))
8440 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8441 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8443 parted $img mklabel msdos
8444 parted $img mkpart primary linux-swap
0 $disksize
8445 parted $img mkpart primary ext2 $disksize $totalsize
8446 parted $img set
1 boot on
8449 losetup /dev/loop0 $img
8450 kpartx -a /dev/loop0
8452 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8453 fsck.ext3 -f /dev/mapper/loop0p1 || true
8454 mkswap /dev/mapper/loop0p2
8456 kpartx -d /dev/loop0
8457 losetup -d /dev/loop0
8460 <p
>The script is perhaps so simple that it is not copyrightable, but
8461 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8463 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8464 the new disk image attached, installed grub-pc and linux-image-
686 and
8465 set up grub to boot from the disk image. After this, the KVM machines
8466 seem to work just fine.
</p
>
8471 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8472 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8473 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8474 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8475 <description><p
>I
'm still running upgrade testing of the
8476 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8477 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8478 status. Here is a short update based on a test I ran
20101118.
</p
>
8480 <p
>I still do not know what a correct migration should look like, so I
8481 report any differences between apt and aptitude and hope someone else
8482 can see if anything should be changed.
</p
>
8484 <p
>This is for Gnome:
</p
>
8486 <p
>Installed using apt-get, missing with aptitude
</p
>
8488 <blockquote
><p
>
8489 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8490 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8491 dmz-cursor-theme empathy empathy-common finger
8492 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8493 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8494 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8495 gnome-cards-data gnome-codec-install gnome-core
8496 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8497 gnome-search-tool gnome-session-canberra gnome-spell
8498 gnome-system-log gnome-themes-extras gnome-themes-more
8499 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8500 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8501 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8502 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8503 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8504 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8505 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8506 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8507 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8508 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8509 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8510 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8511 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8512 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8513 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8514 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8515 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8516 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8517 libmono-security2.0-cil libmono-sharpzip2.84-cil
8518 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8519 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8520 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8521 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8522 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8523 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8524 libxalan2-java libxerces2-java media-player-info mesa-utils
8525 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8526 nautilus-sendto-empathy openoffice.org-writer2latex
8527 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8528 python-aptdaemon python-aptdaemon-gtk python-axiom
8529 python-beautifulsoup python-bugbuddy python-clientform
8530 python-coherence python-configobj python-crypto python-cupshelpers
8531 python-cupsutils python-eggtrayicon python-elementtree
8532 python-epsilon python-evolution python-feedparser python-gdata
8533 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8534 python-gtksourceview2 python-httplib2 python-louie python-mako
8535 python-markupsafe python-mechanize python-nevow python-notify
8536 python-opengl python-openssl python-pam python-pkg-resources
8537 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8538 python-tagpy python-twisted-bin python-twisted-conch
8539 python-twisted-core python-twisted-web python-utidylib python-webkit
8540 python-xdg python-zope.interface remmina remmina-plugin-data
8541 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8542 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8543 software-center svgalibg1 system-config-printer-udev
8544 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8545 totem totem-coherence totem-mozilla totem-plugins
8546 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8548 </p
></blockquote
>
8550 Installed using apt-get, removed with aptitude
8552 <blockquote
><p
>
8553 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8554 epiphany-extensions epiphany-gecko evolution-exchange
8555 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8556 gedit-common gnome-app-install gnome-games gnome-games-data
8557 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8558 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8559 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8560 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8561 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8562 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8563 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8564 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8565 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8566 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8567 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8568 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8569 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8570 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8571 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8572 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8573 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8574 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8575 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8576 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8577 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8578 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8579 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8580 sound-juicer swfdec-gnome system-config-printer totem-common
8581 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8582 </p
></blockquote
>
8584 <p
>Installed using aptitude, missing with apt-get
</p
>
8586 <blockquote
><p
>
8587 gstreamer0.10-gnomevfs
8588 </p
></blockquote
>
8590 <p
>Installed using aptitude, removed with apt-get
</p
>
8592 <blockquote
><p
>
8594 </p
></blockquote
>
8596 <p
>This is for KDE:
</p
>
8598 <p
>Installed using apt-get, missing with aptitude
</p
>
8600 <blockquote
><p
>
8601 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8602 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8603 ghostscript-x git gnome-audio gnugo granatier gs-common
8604 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8605 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8606 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8607 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8608 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8609 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8610 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8611 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8612 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8613 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8614 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8615 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8616 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8617 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8618 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8619 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8620 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8621 libkrossui4 libmailtools-perl libmime-tools-perl
8622 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8623 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8624 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8625 lirc luatex marble networkstatus noatun-plugins
8626 openoffice.org-writer2latex palapeli palapeli-data parley
8627 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8628 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8629 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8631 </p
></blockquote
>
8633 <p
>Installed using apt-get, removed with aptitude
</p
>
8635 <blockquote
><p
>
8636 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8637 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8638 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8639 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8640 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8641 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8642 kitchensync kiten kjumpingcube klatin klettres klickety klines
8643 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8644 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8645 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8646 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8647 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8648 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8649 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8650 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8651 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8652 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8653 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8654 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8655 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8656 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8657 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8658 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8659 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8660 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8661 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8662 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8663 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8664 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8665 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8666 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8667 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8668 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8669 </p
></blockquote
>
8671 <p
>Installed using aptitude, missing with apt-get
</p
>
8673 <blockquote
><p
>
8674 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8675 kdeartwork kdebase kdebase-apps kdebase-workspace
8676 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8677 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8678 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8679 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8680 xscreensaver-screensaver-bsod
8681 </p
></blockquote
>
8683 <p
>Installed using aptitude, removed with apt-get
</p
>
8685 <blockquote
><p
>
8686 kdebase-bin konq-plugins konqueror
8687 </p
></blockquote
>
8692 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8693 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8694 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8695 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8696 <description><p
>Answering
8697 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8698 call from the Gnash project
</a
> for
8699 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8700 current source, I have set up a virtual KVM machine on the Debian
8701 Edu/Skolelinux virtualization host to test the git source on
8702 Debian/Squeeze. I hope this can help the developers in getting new
8703 releases out more often.
</p
>
8705 <p
>As the developers want less main-stream build platforms tested to,
8706 I have considered setting up a
<a
8707 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8708 machine as well. I have also considered using the kfreebsd
8709 architecture in Debian as a file server in NUUG to get access to the
5
8710 TB zfs volume we currently use to store DV video. Because of this, I
8711 finally got around to do a test installation of Debian/Squeeze with
8712 kfreebsd. Installation went fairly smooth, thought I noticed some
8713 visual glitches in the cdebconf dialogs (black cursor left on the
8714 screen at random locations). Have not gotten very far with the
8715 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8716 fatal problem. Have to spend some more time on it to see if it is
8717 useful as a file server for NUUG. Will try to find time to set up a
8718 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8723 <title>Debian in
3D
</title>
8724 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8725 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8726 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8727 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8729 <p
>3D printing is just great. I just came across this Debian logo in
8731 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8732 thingiverse blog
</a
>.
</p
>
8737 <title>Software updates
2010-
10-
24</title>
8738 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8739 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8740 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8741 <description><p
>Some updates.
</p
>
8743 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8744 raise money for the project is going well. The lower limit of
10
8745 signers was reached in
24 hours, and so far
13 people have signed it.
8746 More signers and more funding is most welcome, and I am really curious
8747 how far we can get before the time limit of December
24 is reached.
8750 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8751 about what appear to be a great code coverage tool capable of
8752 generating code coverage stats without any changes to the source code.
8754 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8755 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8756 It is missing in Debian, but the git source built just fine in Squeeze
8757 after I installed libelf-dev, libdwarf-dev, pkg-config and
8758 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8759 solvable. I hope kcov make it into Debian soon.
</p
>
8761 <p
>Finally found time to wrap up the release notes for
<a
8762 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8763 new alpha release of Debian Edu
</a
>, and just published the second
8764 alpha test release of the Squeeze based Debian Edu /
8765 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8766 release. Give it a try if you need a complete linux solution for your
8767 school, including central infrastructure server, workstations, thin
8768 client servers and diskless workstations. A nice touch added
8769 yesterday is RDP support on the thin client servers, for windows
8770 clients to get a Linux desktop on request.
</p
>
8775 <title>Some notes on Flash in Debian and Debian Edu
</title>
8776 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8777 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8778 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8779 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8780 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8781 second most popular used package that is missing in Debian. The sixth
8782 most popular is flashplayer-mozilla. This is a clear indication that
8783 working flash is important for Debian users. Around
10 percent of the
8784 users submitting data to popcon.debian.org have this package
8785 installed.
</p
>
8787 <p
>In the report written by Lars Risan in August
2008
8788 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8789 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8790 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8791 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8792 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8793 web sites require Flash to work, and lacking working Flash support in
8794 the web browser and the problems with installing it was perceived as a
8795 good reason to stay with Windows.
</p
>
8797 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8798 said to be the retarded cousin that did not really understand
8799 everything you told him but could work fairly well. This was a
8800 comment regarding the problems Linux have with proprietary formats and
8801 non-standard web pages, and is sad because it exposes a fairly common
8802 understanding of whose fault it is if web pages that only work in for
8803 example Internet Explorer
6 fail to work on Firefox, and funny because
8804 it explain very well how annoying it is for users when Linux
8805 distributions do not work with the documents they receive or the web
8806 pages they want to visit.
</p
>
8808 <p
>This is part of the reason why I believe it is important for Debian
8809 and Debian Edu to have a well working Flash implementation in the
8810 distribution, to get at least popular sites as Youtube and Google
8811 Video to working out of the box. For Squeeze, Debian have the chance
8812 to include the latest version of Gnash that will make this happen, as
8813 the new release
0.8.8 was published a few weeks ago and is resting in
8814 unstable. The new version work with more sites that version
0.8.7.
8815 The Gnash maintainers have asked for a freeze exception, but the
8816 release team have not had time to reply to it yet. I hope they agree
8817 with me that Flash is important for the Debian desktop users, and thus
8818 accept the new package into Squeeze.
</p
>
8823 <title>Circular package dependencies harms apt recovery
</title>
8824 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8825 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8826 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8827 <description><p
>I discovered this while doing
8828 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8829 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8830 in Debian still got circular dependencies, and it is often claimed
8831 that apt and aptitude should be able to handle this just fine, but
8832 some times these dependency loops causes apt to fail.
</p
>
8834 <p
>An example is from todays
8835 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8836 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8837 causes perl-modules to fail to upgrade. The cause is simple. If a
8838 package fail to unpack, then only part of packages with the circular
8839 dependency might end up being unpacked when unpacking aborts, and the
8840 ones already unpacked will fail to configure in the recovery phase
8841 because its dependencies are unavailable.
</p
>
8843 <p
>In this log, the problem manifest itself with this error:
</p
>
8845 <blockquote
><pre
>
8846 dpkg: dependency problems prevent configuration of perl-modules:
8847 perl-modules depends on perl (
>=
5.10.1-
1); however:
8848 Version of perl on system is
5.10.0-
19lenny
2.
8849 dpkg: error processing perl-modules (--configure):
8850 dependency problems - leaving unconfigured
8851 </pre
></blockquote
>
8853 <p
>The perl/perl-modules circular dependency is already
8854 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8855 hopefully be solved as soon as possible, but it is not the only one,
8856 and each one of these loops in the dependency tree can cause similar
8857 failures. Of course, they only occur when there are bugs in other
8858 packages causing the unpacking to fail, but it is rather nasty when
8859 the failure of one package causes the problem to become worse because
8860 of dependency loops.
</p
>
8863 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8864 tireless effort by Bill Allombert
</a
>, the number of circular
8866 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8867 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8869 <p
>Todays testing also exposed a bug in
8870 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8871 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8872 apt-get and aptitude, the latter possibly caused by some circular
8873 dependency. Reported both to BTS to try to get someone to look at
8879 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8880 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8881 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8882 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8883 <description><p
>This is a
8884 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8886 <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
8888 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8889 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8891 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8892 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8893 and dhcp3-server-ldap in Debian use the LDAP server. The two
8894 implementations are quite different in how they use LDAP.
</p
>
8896 To get this information, I started slapd with debugging enabled and
8897 dumped the debug output to a file to get the LDAP searches performed
8898 on a Debian Edu main-server. Here is a summary.
8900 <p
><strong
>powerdns
</strong
></p
>
8902 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8903 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8906 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8907 One
"strict
" mode where the forward and reverse DNS lookups are done
8908 using the same LDAP objects, and a
"tree
" mode where the forward and
8909 reverse entries are in two different subtrees in LDAP with a structure
8910 based on the DNS names, as in tjener.intern and
8911 2.2.0.10.in-addr.arpa.
</p
>
8913 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8914 base, and uses a
"base
" scoped search for the DNS name by adding
8915 "dc=tjener,dc=intern,
" to the base with a filter for
8916 "(associateddomain=tjener.intern)
" for the forward entry and
8917 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8918 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8919 forward entries, it is looking for attributes named dnsttl, arecord,
8920 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8921 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8922 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8923 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8924 spfrecord and modifytimestamp. For reverse entries it is looking for
8925 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8926 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8927 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8928 ldapsearch commands could look like this:
</p
>
8930 <blockquote
><pre
>
8931 ldapsearch -h ldap \
8932 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8933 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8934 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8935 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8936 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8937 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8939 ldapsearch -h ldap \
8940 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8941 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8942 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8943 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8944 srvrecord naptrrecord modifytimestamp
8945 </pre
></blockquote
>
8947 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8948 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8949 example LDAP objects used there. In addition to these objects, the
8950 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8951 also exist.
</p
>
8953 <blockquote
><pre
>
8954 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8956 objectclass: dnsdomain
8957 objectclass: domainrelatedobject
8960 associateddomain: tjener.intern
8962 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8964 objectclass: dnsdomain2
8965 objectclass: domainrelatedobject
8967 ptrrecord: tjener.intern
8968 associateddomain:
2.2.0.10.in-addr.arpa
8969 </pre
></blockquote
>
8971 <p
>In strict mode, the server behaves differently. When looking for
8972 forward DNS entries, it is doing a
"subtree
" scoped search with the
8973 same base as in the tree mode for a object with filter
8974 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8975 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8976 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8977 naptrrecord and modifytimestamp. For reverse entires it also do a
8978 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8979 and the requested attributes are associateddomain, dnsttl and
8980 modifytimestamp. In short, in strict mode the objects with ptrrecord
8981 go away, and the arecord attribute in the forward object is used
8984 <p
>The forward and reverse searches can be simulated using ldapsearch
8985 like this:
</p
>
8987 <blockquote
><pre
>
8988 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8989 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8990 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8991 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8992 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8993 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8995 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8996 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8997 </pre
></blockquote
>
8999 <p
>In addition to the forward and reverse searches , there is also a
9000 search for SOA records, which behave similar to the forward and
9001 reverse lookups.
</p
>
9003 <p
>A thing to note with the PowerDNS behaviour is that it do not
9004 specify any objectclass names, and instead look for the attributes it
9005 need to generate a DNS reply. This make it able to work with any
9006 objectclass that provide the needed attributes.
</p
>
9008 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9009 dnsdomain2 schemas. The latter is used for reverse entries like
9010 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9012 <p
>In Debian Edu, we have created DNS objects using the object classes
9013 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9014 attributes) and domainrelatedobject (for associatedDomain). The use
9015 of structural object classes make it impossible to combine these
9016 classes with the object classes used by DHCP.
</p
>
9018 <p
>There are other schemas that could be used too, for example the
9019 dnszone structural object class used by Gosa and bind-sdb for the DNS
9020 attributes combined with the domainrelatedobject object class, but in
9021 this case some unused attributes would have to be included as well
9022 (zonename and relativedomainname).
</p
>
9024 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9025 mode and not use any of the existing objectclasses (dnsdomain,
9026 dnsdomain2 and dnszone) when one want to combine the DNS information
9027 with DHCP information, and instead create a auxiliary object class
9028 defined something like this (using the attributes defined for
9029 dnsdomain and dnsdomain2 or dnszone):
</p
>
9031 <blockquote
><pre
>
9032 objectclass ( some-oid NAME
'dnsDomainAux
'
9035 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9036 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9037 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9038 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9039 A6Record $ DNAMERecord
9041 </pre
></blockquote
>
9043 <p
>This will allow any object to become a DNS entry when combined with
9044 the domainrelatedobject object class, and allow any entity to include
9045 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9046 developers asking for their view on this schema and if they are
9047 interested in providing such schema with PowerDNS, and I hope my
9048 message will be accepted into their mailing list soon.
</p
>
9050 <p
><strong
>ISC dhcp
</strong
></p
>
9052 <p
>The DHCP server searches for specific objectclass and requests all
9053 the object attributes, and then uses the attributes it want. This
9054 make it harder to figure out exactly what attributes are used, but
9055 thanks to the working example in Debian Edu I can at least get an idea
9056 what is needed without having to read the source code.
</p
>
9058 <p
>In the DHCP server configuration, the LDAP base to use and the
9059 search filter to use to locate the correct dhcpServer entity is
9060 stored. These are the relevant entries from
9061 /etc/dhcp3/dhcpd.conf:
</p
>
9063 <blockquote
><pre
>
9064 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9065 ldap-dhcp-server-cn
"dhcp
";
9066 </pre
></blockquote
>
9068 <p
>The DHCP server uses this information to nest all the DHCP
9069 configuration it need. The cn
"dhcp
" is located using the given LDAP
9070 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9071 search result is this entry:
</p
>
9073 <blockquote
><pre
>
9074 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9077 objectClass: dhcpServer
9078 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9079 </pre
></blockquote
>
9081 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9082 subtree with DHCP configuration. The DHCP configuration subtree base
9083 is located using a base scope search with base
"cn=DHCP
9084 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9085 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9086 The search result is this entry:
</p
>
9088 <blockquote
><pre
>
9089 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9092 objectClass: dhcpService
9093 objectClass: dhcpOptions
9094 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9095 dhcpStatements: ddns-update-style none
9096 dhcpStatements: authoritative
9097 dhcpOption: smtp-server code
69 = array of ip-address
9098 dhcpOption: www-server code
72 = array of ip-address
9099 dhcpOption: wpad-url code
252 = text
9100 </pre
></blockquote
>
9102 <p
>Next, the entire subtree is processed, one level at the time. When
9103 all the DHCP configuration is loaded, it is ready to receive requests.
9104 The subtree in Debian Edu contain objects with object classes
9105 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9106 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9107 and information about netmasks, dynamic range etc. Leaving out the
9108 details here because it is not relevant for the focus of my
9109 investigation, which is to see if it is possible to merge dns and dhcp
9110 related computer objects.
</p
>
9112 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9113 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9114 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9115 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9116 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9119 <blockquote
><pre
>
9120 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9123 objectClass: dhcpHost
9124 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9125 dhcpStatements: fixed-address hostname
9126 </pre
></blockquote
>
9128 <p
>There is less flexiblity in the way LDAP searches are done here.
9129 The object classes need to have fixed names, and the configuration
9130 need to be stored in a fairly specific LDAP structure. On the
9131 positive side, the invidiual dhcpHost entires can be anywhere without
9132 the DN pointed to by the dhcpServer entries. The latter should make
9133 it possible to group all host entries in a subtree next to the
9134 configuration entries, and this subtree can also be shared with the
9135 DNS server if the schema proposed above is combined with the dhcpHost
9136 structural object class.
9138 <p
><strong
>Conclusion
</strong
></p
>
9140 <p
>The PowerDNS implementation seem to be very flexible when it come
9141 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9142 come to the the LDAP structure, the
"strict
" mode is very flexible,
9143 allowing DNS objects to be stored anywhere under the base cn specified
9144 in the configuration.
</p
>
9146 <p
>The DHCP implementation on the other hand is very inflexible, both
9147 regarding which LDAP schemas to use and which LDAP structure to use.
9148 I guess one could implement ones own schema, as long as the
9149 objectclasses and attributes have the names used, but this do not
9150 really help when the DHCP subtree need to have a fairly fixed
9151 structure.
</p
>
9153 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9154 this might work for Debian Edu:
</p
>
9156 <blockquote
><pre
>
9158 cn=machine-info (dhcpService) - dhcpServiceDN points here
9159 cn=dhcp (dhcpServer)
9160 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9161 cn=
10.0.2.0 (dhcpSubnet)
9162 cn=group1 (dhcpGroup/dhcpOptions)
9163 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9164 cn=
192.168.0.0 (dhcpSubnet)
9165 cn=group1 (dhcpGroup/dhcpOptions)
9166 ou=machines - PowerDNS base points here
9167 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9168 </pre
></blockquote
>
9170 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9171 entries to be in the dhcpGroup subtrees, the entries can be stored
9172 there instead of a common machines subtree, and the PowerDNS base
9173 would have to be moved one level up to the machine-info subtree.
</p
>
9175 <p
>The combined object under the machines subtree would look something
9176 like this:
</p
>
9178 <blockquote
><pre
>
9179 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9182 objectClass: dhcpHost
9183 objectclass: domainrelatedobject
9184 objectclass: dnsDomainAux
9185 associateddomain: hostname.intern
9186 arecord:
10.11.12.13
9187 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9188 dhcpStatements: fixed-address hostname.intern
9189 </pre
></blockquote
>
9191 </p
>One could even add the LTSP configuration associated with a given
9192 machine, as long as the required attributes are available in a
9193 auxiliary object class.
</p
>
9198 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9199 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9200 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9201 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9202 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9203 DHCP services in Debian Edu to use the same LDAP objects for a given
9204 computer, to avoid the possibility of having a inconsistent state for
9205 a computer in LDAP (as in DHCP but no DNS entry or the other way
9206 around) and make it easier to add computers to LDAP.
</p
>
9208 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9209 information finally found a solution that seem to work.
</p
>
9211 <p
>The old setup required three LDAP objects for a given computer.
9212 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9213 we switch powerdns to use its strict LDAP method (ldap-method=strict
9214 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9215 merged into one while making it impossible to transfer the reverse map
9216 to a slave DNS server.
</p
>
9218 <p
>If we also replace the object class used to get the DNS related
9219 attributes to one allowing these attributes to be combined with the
9220 dhcphost object class, we can merge the DNS and DHCP entries into one.
9221 I
've written such object class in the dnsdomainaux.schema file (need
9222 proper OIDs, but that is a minor issue), and tested the setup. It
9223 seem to work.
</p
>
9225 <p
>With this test setup in place, we can get away with one LDAP object
9226 for both DNS and DHCP, and even the LTSP configuration I suggested in
9227 an earlier email. The combined LDAP object will look something like
9230 <blockquote
><pre
>
9231 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9233 objectClass: dhcphost
9234 objectclass: domainrelatedobject
9235 objectclass: dnsdomainaux
9236 associateddomain: hostname.intern
9237 arecord:
10.11.12.13
9238 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9239 dhcpstatements: fixed-address hostname
9241 </pre
></blockquote
>
9243 <p
>The DNS server uses the associateddomain and arecord entries, while
9244 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9245 before asking DNS to resolve the fixed-adddress. LTSP will use
9246 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9248 <p
>I am not yet sure if I can get the DHCP server to look for its
9249 dhcphost in a different location, to allow us to put the objects
9250 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9251 that. If I can
't figure out a way to do that, we can still get rid of
9252 the hosts subtree and move all its content into the DHCP Config tree
9253 (which probably should be renamed to be more related to the new
9254 content. I suspect cn=dnsdhcp,ou=services or something like that
9255 might be a good place to put it.
</p
>
9257 <p
>If you want to help out with implementing this for Debian Edu,
9258 please contact us on debian-edu@lists.debian.org.
</p
>
9263 <title>Idea for storing LTSP configuration in LDAP
</title>
9264 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9265 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9266 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9267 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9268 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9269 clients, and that this can be used to fetch configuration from LDAP if
9270 Debian Edu choose to store configuration there.
</p
>
9272 <p
>Armed with this information, I got inspired and wrote a test module
9273 to get configuration from LDAP. The idea is to look up the MAC
9274 address of the client in LDAP, and look for attributes on the form
9275 ltspconfigsetting=value, and use this to export SETTING=value to the
9276 LTSP clients.
</p
>
9278 <p
>The goal is to be able to store the LTSP configuration attributes
9279 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9280 allowing us to store all information about a computer in one place.
</p
>
9282 <p
>This is a untested draft implementation, and I welcome feedback on
9283 this approach. A real LDAP schema for the ltspClientAux objectclass
9284 need to be written. Comments, suggestions, etc?
</p
>
9286 <blockquote
><pre
>
9287 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9289 # Fetch LTSP client settings from LDAP based on MAC address
9291 # Uses ethernet address as stored in the dhcpHost objectclass using
9292 # the dhcpHWAddress attribute or ethernet address stored in the
9293 # ieee802Device objectclass with the macAddress attribute.
9295 # This module is written to be schema agnostic, and only depend on the
9296 # existence of attribute names.
9298 # The LTSP configuration variables are saved directly using a
9299 # ltspConfig prefix and uppercasing the rest of the attribute name.
9300 # To set the SERVER variable, set the ltspConfigServer attribute.
9302 # Some LDAP schema should be created with all the relevant
9303 # configuration settings. Something like this should work:
9305 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9308 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9310 LDAPSERVER=$(debian-edu-ldapserver)
9311 if [
"$LDAPSERVER
" ] ; then
9312 LDAPBASE=$(debian-edu-ldapserver -b)
9313 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9314 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9315 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9316 grep
'^ltspConfig
' | while read attr value ; do
9317 # Remove prefix and convert to upper case
9318 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9319 # bass value on to clients
9320 eval
"$attr=$value; export $attr
"
9324 </pre
></blockquote
>
9326 <p
>I
'm not sure this shell construction will work, because I suspect
9327 the while block might end up in a subshell causing the variables set
9328 there to not show up in ltsp-config, but if that is the case I am sure
9329 the code can be restructured to make sure the variables are passed on.
9330 I expect that can be solved with some testing. :)
</p
>
9332 <p
>If you want to help out with implementing this for Debian Edu,
9333 please contact us on debian-edu@lists.debian.org.
</p
>
9335 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9336 configuration in LDAP that was created around year
2000 by
9337 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9338 Xperience, Inc.,
2000</a
>. I found its
9339 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9340 personal home page over at redhat.com.
</p
>
9345 <title>jXplorer, a very nice LDAP GUI
</title>
9346 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9347 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9348 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9349 <description><p
>Since
9350 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9351 last post
</a
> about available LDAP tools in Debian, I was told about a
9352 LDAP GUI that is even better than luma. The java application
9353 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9354 moving LDAP objects and subtrees using drag-and-drop, and can
9355 authenticate using Kerberos. I have only tested the Kerberos
9356 authentication, but do not have a LDAP setup allowing me to rewrite
9357 LDAP with my test user yet. It is
9358 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9359 Debian
</a
> testing and unstable at the moment. The only problem I
9360 have with it is how it handle errors. If something go wrong, its
9361 non-intuitive behaviour require me to go through some query work list
9362 and remove the failing query. Nothing big, but very annoying.
</p
>
9367 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9368 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9369 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9370 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9371 <description><p
>Here is a short update on my
<a
9372 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9373 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9374 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9375 not reporting the status for KDE, because the upgrade crashes when
9376 aptitude try because of missing conflicts
9377 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9378 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9380 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9381 complete list of the installed packages. Based on this I see these
9382 differences when I did a test run today. As usual, I do not really
9383 know what the correct set of packages would be, but thought it best to
9384 publish the difference.
</p
>
9386 <p
>Installed using apt-get, missing with aptitude
</p
>
9388 <blockquote
><p
>
9389 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9390 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9391 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9392 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9393 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9394 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9395 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9396 python-gtkmozembed svgalibg1 xserver-xephyr zip
9397 </p
></blockquote
>
9399 <p
>Installed using apt-get, removed with aptitude
</p
>
9401 <blockquote
><p
>
9402 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9403 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9404 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9405 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9406 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9407 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9408 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9409 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9410 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9411 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9412 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9413 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9414 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9415 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9416 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9417 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9418 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9419 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9420 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9421 mysql-common swfdec-gnome totem-gstreamer wodim
9422 </p
></blockquote
>
9424 <p
>Installed using aptitude, missing with apt-get
</p
>
9426 <blockquote
><p
>
9427 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9428 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9429 xserver-xorg-input-all xserver-xorg-input-evdev
9430 xserver-xorg-input-kbd xserver-xorg-input-mouse
9431 xserver-xorg-input-synaptics xserver-xorg-video-all
9432 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9433 xserver-xorg-video-chips xserver-xorg-video-cirrus
9434 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9435 xserver-xorg-video-glint xserver-xorg-video-i128
9436 xserver-xorg-video-i740 xserver-xorg-video-mach64
9437 xserver-xorg-video-mga xserver-xorg-video-neomagic
9438 xserver-xorg-video-nouveau xserver-xorg-video-nv
9439 xserver-xorg-video-r128 xserver-xorg-video-radeon
9440 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9441 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9442 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9443 xserver-xorg-video-sis xserver-xorg-video-sisusb
9444 xserver-xorg-video-tdfx xserver-xorg-video-tga
9445 xserver-xorg-video-trident xserver-xorg-video-tseng
9446 xserver-xorg-video-vesa xserver-xorg-video-vmware
9447 xserver-xorg-video-voodoo
9448 </p
></blockquote
>
9450 <p
>Installed using aptitude, removed with apt-get
</p
>
9452 <blockquote
><p
>
9453 deskbar-applet xserver-xorg xserver-xorg-core
9454 xserver-xorg-input-wacom xserver-xorg-video-intel
9455 xserver-xorg-video-openchrome
9456 </p
></blockquote
>
9458 <p
>I was told on IRC that the xorg-xserver package was
9459 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9460 in git
</a
> today to try to get apt-get to not remove xorg completely.
9461 No idea when it hits Squeeze, but when it does I hope it will reduce
9462 the difference somewhat.
9467 <title>LUMA, a very nice LDAP GUI
</title>
9468 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9469 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9470 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9471 <description><p
>The last few days I have been looking into the status of the LDAP
9472 directory in Debian Edu, and in the process I started to miss a GUI
9473 tool to browse the LDAP tree. The only one I was able to find in
9474 Debian/Squeeze and Lenny is
9475 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9476 be a great tool to get a overview of the current LDAP directory
9477 populated by default in Skolelinux. Thanks to it, I have been able to
9478 find empty and obsolete subtrees, misplaced objects and duplicate
9479 objects. It will be installed by default in Debian/Squeeze. If you
9480 are working with LDAP, give it a go. :)
</p
>
9482 <p
>I did notice one problem with it I have not had time to report to
9483 the BTS yet. There is no .desktop file in the package, so the tool do
9484 not show up in the Gnome and KDE menus, but only deep down in in the
9485 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9488 <p
>I have not yet been able to get it to modify the tree yet. I would
9489 like to move objects and remove subtrees directly in the GUI, but have
9490 not found a way to do that with LUMA yet. So in the mean time, I use
9491 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9493 <p
>If you have tips on other GUI tools for LDAP that might be useful
9494 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9496 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9497 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9498 useful GUI alternative. It seem like a good tool, but is unmaintained
9499 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9500 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9505 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9506 <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>
9507 <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>
9508 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9509 <description><p
>A while back, I
9510 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9511 about the fact
</a
> that it is not possible with the provided schemas
9512 for storing DNS and DHCP information in LDAP to combine the two sets
9513 of information into one LDAP object representing a computer.
</p
>
9515 <p
>In the mean time, I discovered that a simple fix would be to make
9516 the dhcpHost object class auxiliary, to allow it to be combined with
9517 the dNSDomain object class, and thus forming one object for one
9518 computer when storing both DHCP and DNS information in LDAP.
</p
>
9520 <p
>If I understand this correctly, it is not safe to do this change
9521 without also changing the assigned number for the object class, and I
9522 do not know enough about LDAP schema design to do that properly for
9523 Debian Edu.
</p
>
9525 <p
>Anyway, for future reference, this is how I believe we could change
9527 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9528 schema
</a
> to solve at least part of the problem with the LDAP schemas
9529 available today from IETF.
</p
>
9532 --- dhcp.schema (revision
65192)
9533 +++ dhcp.schema (working copy)
9535 objectclass (
2.16.840.1.113719.1.203.6.6
9536 NAME
'dhcpHost
'
9537 DESC
'This represents information about a particular client
'
9541 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9542 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9545 <p
>I very much welcome clues on how to do this properly for Debian
9546 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9547 package, and should thus be free to rewrite it as we see fit.
</p
>
9549 <p
>If you want to help out with implementing this for Debian Edu,
9550 please contact us on debian-edu@lists.debian.org.
</p
>
9555 <title>Calling tasksel like the installer, while still getting useful output
</title>
9556 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9557 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9558 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9559 <description><p
>A few times I have had the need to simulate the way tasksel
9560 installs packages during the normal debian-installer run. Until now,
9561 I have ended up letting tasksel do the work, with the annoying problem
9562 of not getting any feedback at all when something fails (like a
9563 conffile question from dpkg or a download that fails), using code like
9566 <blockquote
><pre
>
9567 export DEBIAN_FRONTEND=noninteractive
9568 tasksel --new-install
9569 </pre
></blockquote
>
9571 This would invoke tasksel, let its automatic task selection pick the
9572 tasks to install, and continue to install the requested tasks without
9573 any output what so ever.
9575 Recently I revisited this problem while working on the automatic
9576 package upgrade testing, because tasksel would some times hang without
9577 any useful feedback, and I want to see what is going on when it
9578 happen. Then it occured to me, I can parse the output from tasksel
9579 when asked to run in test mode, and use that aptitude command line
9580 printed by tasksel then to simulate the tasksel run. I ended up using
9583 <blockquote
><pre
>
9584 export DEBIAN_FRONTEND=noninteractive
9585 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9587 </pre
></blockquote
>
9589 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9590 --without-recommends -o APT::Install-Recommends=no -y install
9591 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9592 ~pimportant
</tt
>", which will install the gnome desktop task, the
9593 laptop task and all packages with priority standard , required and
9594 important, just like tasksel would have done it during
9595 installation.
</p
>
9597 <p
>A better approach is probably to extend tasksel to be able to
9598 install packages without using debconf-apt-progress, for use cases
9599 like this.
</p
>
9604 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9605 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9606 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9607 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9608 <description><p
>My
9609 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9610 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9611 finally made the upgrade logs available from
9612 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9613 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9614 apt and aptitude, and found their differences interesting. This time
9615 I will only focus on their removal plans.
</p
>
9617 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9618 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9619 surprising part is that it want to remove xorg and all
9620 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9621 sure why. When asking aptitude to do the same, it want to remove
129
9622 packages, but most of them are library packages I suspect are no
9623 longer needed. Both of them want to remove bluetooth packages, which
9624 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9626 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9627 which seem like a bad idea and xorg the same way as with Gnome. Asking
9628 aptitude for the same, it wants to remove
192 packages, none which are
9629 too surprising.
</p
>
9631 <p
>I guess the removal of xorg during upgrades should be investigated
9632 and avoided, and perhaps others as well. Here are the complete list
9633 of planned removals. The complete logs is available from the URL
9634 above. Note if you want to repeat these tests, that the upgrade test
9635 for kde+apt-get hung in the tasksel setup because of dpkg asking
9636 conffile questions. No idea why. I worked around it by using
9637 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9640 <p
><b
>apt-get gnome
72</b
>
9641 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9642 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9643 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9644 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9645 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9646 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9647 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9648 xserver-xorg-input-kbd xserver-xorg-input-mouse
9649 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9650 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9651 xserver-xorg-video-ati xserver-xorg-video-chips
9652 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9653 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9654 xserver-xorg-video-glint xserver-xorg-video-i128
9655 xserver-xorg-video-i740 xserver-xorg-video-imstt
9656 xserver-xorg-video-intel xserver-xorg-video-mach64
9657 xserver-xorg-video-mga xserver-xorg-video-neomagic
9658 xserver-xorg-video-nsc xserver-xorg-video-nv
9659 xserver-xorg-video-openchrome xserver-xorg-video-r128
9660 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9661 xserver-xorg-video-rendition xserver-xorg-video-s3
9662 xserver-xorg-video-s3virge xserver-xorg-video-savage
9663 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9664 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9665 xserver-xorg-video-tga xserver-xorg-video-trident
9666 xserver-xorg-video-tseng xserver-xorg-video-v4l
9667 xserver-xorg-video-vesa xserver-xorg-video-vga
9668 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9669 xulrunner-
1.9-gnome-support
</p
>
9671 <p
><b
>aptitude gnome
129</b
>
9673 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9674 djvulibre-desktop finger gnome-app-install gnome-mount
9675 gnome-network-admin gnome-spell gnome-vfs-obexftp
9676 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9677 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9678 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9679 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9680 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9681 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9682 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9683 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9684 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9685 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9686 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9687 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9688 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9689 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9690 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9691 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9692 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9693 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9694 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9695 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9696 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9697 openoffice.org-writer2latex openssl-blacklist p7zip
9698 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9699 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9700 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9701 swfdec-mozilla totem-gstreamer update-manager wodim
9702 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9703 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9706 <p
><b
>apt-get kde
82</b
>
9708 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9709 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9710 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9711 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9712 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9713 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9714 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9715 xserver-xorg-input-kbd xserver-xorg-input-mouse
9716 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9717 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9718 xserver-xorg-video-ati xserver-xorg-video-chips
9719 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9720 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9721 xserver-xorg-video-glint xserver-xorg-video-i128
9722 xserver-xorg-video-i740 xserver-xorg-video-imstt
9723 xserver-xorg-video-intel xserver-xorg-video-mach64
9724 xserver-xorg-video-mga xserver-xorg-video-neomagic
9725 xserver-xorg-video-nsc xserver-xorg-video-nv
9726 xserver-xorg-video-openchrome xserver-xorg-video-r128
9727 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9728 xserver-xorg-video-rendition xserver-xorg-video-s3
9729 xserver-xorg-video-s3virge xserver-xorg-video-savage
9730 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9731 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9732 xserver-xorg-video-tga xserver-xorg-video-trident
9733 xserver-xorg-video-tseng xserver-xorg-video-v4l
9734 xserver-xorg-video-vesa xserver-xorg-video-vga
9735 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9737 <p
><b
>aptitude kde
192</b
>
9738 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9739 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9740 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9741 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9742 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9743 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9744 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9745 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9746 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9747 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9748 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9749 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9750 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9751 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9752 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9753 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9754 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9755 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9756 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9757 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9758 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9759 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9760 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9761 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9762 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9763 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9764 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9765 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9766 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9767 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9768 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9769 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9770 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9771 texlive-common texlive-doc-base texlive-fonts-recommended
9772 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9773 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9774 xulrunner-
1.9</p
>
9780 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9781 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9783 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9784 <description><p
>The last few days I have done some upgrade testing in Debian, to
9785 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9786 have been discovered and reported in the process
9787 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9788 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9789 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9790 kdebase-workspace-data), and to get a more regular testing going on, I
9791 am working on a script to automate the test.
</p
>
9793 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9794 Gnome or KDE desktop installation inside the chroot before upgrading
9795 it. To ensure no services are started in the chroot, a policy-rc.d
9796 script is inserted. To make sure tasksel believe it is to install a
9797 desktop on a laptop, the tasksel tests are replaced in the chroot
9798 (only acceptable because this is a throw-away chroot).
</p
>
9800 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9801 currently always fail because udev refuses to upgrade with the kernel
9802 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9803 is created. The bug report
9804 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9805 this problem do not trigger in a chroot, but I touch the file anyway
9806 to make sure the upgrade go well. Testing on virtual and real
9807 hardware have failed me because of udev so far, and creating this file
9808 do the trick in such settings anyway. This is a
9809 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9810 issue
</a
> and the current udev behaviour is intended by the udev
9811 maintainer because he lack the resources to rewrite udev to keep
9812 working with old kernels or something like that. I really wish the
9813 udev upstream would keep udev backwards compatible, to avoid such
9814 upgrade problem, but given that they fail to do so, I guess
9815 documenting the way out of this mess is the best option we got for
9816 Debian Squeeze.
</p
>
9818 <p
>Anyway, back to the task at hand, testing upgrades. This test
9819 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9822 <blockquote
><pre
>
9826 if [
"$
1" ] ; then
9835 exec
&lt; /dev/null
9837 mirror=http://ftp.skolelinux.org/debian
9838 tmpdir=chroot-$from-upgrade-$to-$desktop
9840 debootstrap $from $tmpdir $mirror
9841 chroot $tmpdir aptitude update
9842 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9846 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9850 mount -t proc proc $tmpdir/proc
9851 # Make sure proc is unmounted also on failure
9852 trap exit_cleanup EXIT INT
9854 chroot $tmpdir aptitude -y install debconf-utils
9856 # Make sure tasksel autoselection trigger. It need the test scripts
9857 # to return the correct answers.
9858 echo tasksel tasksel/desktop multiselect $desktop | \
9859 chroot $tmpdir debconf-set-selections
9861 # Include the desktop and laptop task
9862 for test in desktop laptop ; do
9863 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9867 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9870 DEBIAN_FRONTEND=noninteractive
9871 DEBIAN_PRIORITY=critical
9872 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9873 chroot $tmpdir tasksel --new-install
9875 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9876 chroot $tmpdir aptitude update
9877 touch $tmpdir/etc/udev/kernel-upgrade
9878 chroot $tmpdir aptitude -y dist-upgrade
9880 </pre
></blockquote
>
9882 <p
>I suspect it would be useful to test upgrades with both apt-get and
9883 with aptitude, but I have not had time to look at how they behave
9884 differently so far. I hope to get a cron job running to do the test
9885 regularly and post the result on the web. The Gnome upgrade currently
9886 work, while the KDE upgrade fail because of the bug in
9887 kdebase-workspace-data
</p
>
9889 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9890 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9891 post, so I will refrain from trying. I can report that for Gnome,
9892 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9893 remove and
1 not upgraded and
1024MB need to be downloaded while for
9894 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9895 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9897 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9898 is able to migrate to dependency based boot sequencing and parallel
9899 booting without a hitch. Was unsure if there were still bugs with
9900 packages failing to clean up their obsolete init.d script during
9901 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9907 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9908 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9909 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9910 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9911 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9912 scripts to migrate (some of) their operations to upstart job while
9913 keeping the init.d for hurd and kfreebsd. The packages with such
9914 needs will need a way to get their init.d scripts to behave
9915 differently when used with sysvinit and with upstart. Because of
9916 this, I had a look at the environment variables set when a init.d
9917 script is running under upstart, and when it is not.
</p
>
9919 <p
>With upstart, I notice these environment variables are set when a
9920 script is started from rcS.d/ (ignoring some irrelevant ones like
9923 <blockquote
><pre
>
9929 UPSTART_EVENTS=startup
9931 UPSTART_JOB=rc-sysinit
9932 </pre
></blockquote
>
9934 <p
>With sysvinit, these environment variables are set for the same
9937 <blockquote
><pre
>
9938 INIT_VERSION=sysvinit-
2.88
9943 </pre
></blockquote
>
9945 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9946 sysvinit are not set by upstart. Not sure if it is intentional or not
9947 to not be compatible with sysvinit in this regard.
</p
>
9949 <p
>For scripts needing to behave differently when upstart is used,
9950 looking for the UPSTART_JOB environment variable seem to be a good
9956 <title>A manual for standards wars...
</title>
9957 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9958 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9959 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9960 <description><p
>Via the
9961 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9962 of Rob Weir
</a
> I came across the very interesting essay named
9963 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9964 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9965 following the standards wars of today.
</p
>
9970 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9971 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9972 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9973 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9974 <description><p
>When using sitesummary at a site to track machines, it is possible
9975 to get a list of the machine types in use thanks to the DMI
9976 information extracted from each machine. The script to do so is
9977 included in the sitesummary package, and here is example output from
9978 the Skolelinux build servers:
</p
>
9980 <blockquote
><pre
>
9981 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9983 Dell Computer Corporation
1
9986 eserver xSeries
345 -[
8670M1X]-
1
9990 </pre
></blockquote
>
9992 <p
>The quality of the report depend on the quality of the DMI tables
9993 provided in each machine. Here there are Intel machines without model
9994 information listed with Intel as vendor and no model, and virtual Xen
9995 machines listed as [no-dmi-info]. One can add -l as a command line
9996 option to list the individual machines.
</p
>
9998 <p
>A larger list is
9999 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10000 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10001 provide the basic sitesummary report publicly. In their report there
10002 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10003 their machines, and as sitesummary is available in both distributions,
10004 it is trivial to get all of them to report to the same central
10005 collector.
</p
>
10010 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10011 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10012 <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>
10013 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10014 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10015 start at boot when an NVidia video card is used is handled. The
10016 problem seem to be that the nvidia X.org driver uses a long time to
10017 initialize, and this duration is longer than kdm is configured to
10020 <p
>I came across two bugs related to this issue,
10021 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10022 against initscripts and passed on to nvidia-glx when it became obvious
10023 that the nvidia drivers were involved, and
10024 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10025 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10027 <p
>To me, it seem that no-one is interested in actually solving the
10028 problem nvidia video card owners experience and make sure the Debian
10029 distribution work out of the box for these users. The nvidia driver
10030 maintainers expect kdm to be set up to wait longer, while kdm expect
10031 the nvidia driver maintainers to fix the driver to start faster, and
10032 while they wait for each other I guess the users end up switching to a
10033 distribution that work for them. I have no idea what the solution is,
10034 but I am pretty sure that waiting for each other is not it.
</p
>
10036 <p
>I wonder why we end up handling bugs this way.
</p
>
10041 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10042 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10043 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10044 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10045 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10046 The feature seem to hold up pretty well, but three fairly serious
10047 issues are known and should be solved:
10049 <p
><ul
>
10051 <li
>The wicd package seen to
10052 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10053 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10054 parallel booting is enabled. No idea why, but the wicd maintainer
10055 seem to be on the case.
</li
>
10057 <li
>The nvidia X driver seem to
10058 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10059 triggered more easily when parallel booting is in effect. The
10060 maintainer is on the case.
</li
>
10062 <li
>The sysv-rc package fail to properly enable dependency based boot
10063 sequencing (the shutdown is broken) when old file-rc users
10064 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10065 sysv-rc. One way to solve it would be for file-rc to create
10066 /etc/init.d/.legacy-bootordering, and another is to try to make
10067 sysv-rc more robust. Will investigate some more and probably upload a
10068 workaround in sysv-rc to help those trying to move from file-rc to
10069 sysv-rc get a working shutdown.
</li
>
10071 </ul
></p
>
10073 <p
>All in all not many surprising issues, and all of them seem
10074 solvable before Squeeze is released. In addition to these there are
10075 some packages with bugs in their dependencies and run level settings,
10076 which I expect will be fixed in a reasonable time span.
</p
>
10078 <p
>If you report any problems with dependencies in init.d scripts to
10079 the BTS, please usertag the report to get it to show up at
10080 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10081 list of usertagged bugs related to this
</a
>.
</p
>
10083 <p
>Update: Correct bug number to file-rc issue.
</p
>
10088 <title>More flexible firmware handling in debian-installer
</title>
10089 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10090 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10091 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10092 <description><p
>After a long break from debian-installer development, I finally
10093 found time today to return to the project. Having to spend less time
10094 working dependency based boot in debian, as it is almost complete now,
10095 definitely helped freeing some time.
</p
>
10097 <p
>A while back, I ran into a problem while working on Debian Edu. We
10098 include some firmware packages on the Debian Edu CDs, those needed to
10099 get disk and network controllers working. Without having these
10100 firmware packages available during installation, it is impossible to
10101 install Debian Edu on the given machine, and because our target group
10102 are non-technical people, asking them to provide firmware packages on
10103 an external medium is a support pain. Initially, I expected it to be
10104 enough to include the firmware packages on the CD to get
10105 debian-installer to find and use them. This proved to be wrong.
10106 Next, I hoped it was enough to symlink the relevant firmware packages
10107 to some useful location on the CD (tried /cdrom/ and
10108 /cdrom/firmware/). This also proved to not work, and at this point I
10109 found time to look at the debian-installer code to figure out what was
10110 going to work.
</p
>
10112 <p
>The firmware loading code is in the hw-detect package, and a closer
10113 look revealed that it would only look for firmware packages outside
10114 the installation media, so the CD was never checked for firmware
10115 packages. It would only check USB sticks, floppies and other
10116 "external
" media devices. Today I changed it to also look in the
10117 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10118 solve the problem I ran into with Debian edu. I also changed it to
10119 look in /firmware/, to make sure the installer also find firmware
10120 provided in the initrd when booting the installer via PXE, to allow us
10121 to provide the same feature in the PXE setup included in Debian
10124 <p
>To make sure firmware deb packages with a license questions are not
10125 activated without asking if the license is accepted, I extended
10126 hw-detect to look for preinst scripts in the firmware packages, and
10127 run these before activating the firmware during installation. The
10128 license question is asked using debconf in the preinst, so this should
10129 solve the issue for the firmware packages I have looked at so far.
</p
>
10131 <p
>If you want to discuss the details of these features, please
10132 contact us on debian-boot@lists.debian.org.
</p
>
10137 <title>Parallellized boot is now the default in Debian/unstable
</title>
10138 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10139 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10140 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10141 <description><p
>Since this evening, parallel booting is the default in
10142 Debian/unstable for machines using dependency based boot sequencing.
10143 Apparently the testing of concurrent booting has been wider than
10144 expected, if I am to believe the
10145 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10146 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10147 with the feature this weekend, to give us some time to detect any
10148 remaining problems before Squeeze is frozen. If serious problems are
10149 detected, it is simple to change the default back to sequential boot.
10150 The upload of the new sysvinit package also activate a new upstream
10153 More information about
10154 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10155 based boot sequencing
</a
> is available from the Debian wiki. It is
10156 currently possible to disable parallel booting when one run into
10157 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10159 <blockquote
><pre
>
10161 </pre
></blockquote
>
10163 <p
>If you report any problems with dependencies in init.d scripts to
10164 the BTS, please usertag the report to get it to show up at
10165 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10166 list of usertagged bugs related to this
</a
>.
</p
>
10171 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10172 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10173 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10174 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10175 <description><p
>In the recent Debian Edu versions, the
10176 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10177 system
</a
> is used to keep track of the machines in the school
10178 network. Each machine will automatically report its status to the
10179 central server after boot and once per night. The network setup is
10180 also reported, and using this information it is possible to get the
10181 MAC address of all network interfaces in the machines. This is useful
10182 to update the DHCP configuration.
</p
>
10184 <p
>To give some idea how to use sitesummary, here is a one-liner to
10185 ist all MAC addresses of all machines reporting to sitesummary. Run
10186 this on the collector host:
</p
>
10188 <blockquote
><pre
>
10189 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10190 </pre
></blockquote
>
10192 <p
>This will list all MAC addresses assosiated with all machine, one
10193 line per machine and with space between the MAC addresses.
</p
>
10195 <p
>To allow system administrators easier job at adding static DHCP
10196 addresses for hosts, it would be possible to extend this to fetch
10197 machine information from sitesummary and update the DHCP and DNS
10198 tables in LDAP using this information. Such tool is unfortunately not
10199 written yet.
</p
>
10204 <title>systemd, an interesting alternative to upstart
</title>
10205 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10207 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10208 <description><p
>The last few days a new boot system called
10209 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10211 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10213 to the free software world. I have not yet had time to play around
10214 with it, but it seem to be a very interesting alternative to
10215 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10216 a good alternative for Debian when we are able to switch to an event
10217 based boot system. Tollef is
10218 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10219 systemd into Debian, and I look forward to seeing how well it work. I
10220 like the fact that systemd handles init.d scripts with dependency
10221 information natively, allowing them to run in parallel where upstart
10222 at the moment do not.
</p
>
10224 <p
>Unfortunately do systemd have the same problem as upstart regarding
10225 platform support. It only work on recent Linux kernels, and also need
10226 some new kernel features enabled to function properly. This means
10227 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10228 system. Not sure how that will be handled if systemd proves to be the
10229 way forward.
</p
>
10231 <p
>In the mean time, based on the
10232 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10233 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10234 decided to enable full parallel booting as the default in Debian as
10235 soon as possible (probably this weekend or early next week), to see if
10236 there are any remaining serious bugs in the init.d dependencies. A
10237 new version of the sysvinit package implementing this change is
10238 already in experimental. If all go well, Squeeze will be released
10239 with parallel booting enabled by default.
</p
>
10244 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10245 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10246 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10247 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10248 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10249 complete, so complete that it is actually possible to run all the
10250 init.d scripts in parallell based on these dependencies. If you want
10251 to test your Squeeze system, make sure
10252 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10253 based boot sequencing
</a
> is enabled, and add this line to
10254 /etc/default/rcS:
</p
>
10256 <blockquote
><pre
>
10257 CONCURRENCY=makefile
10258 </pre
></blockquote
>
10260 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10261 scripts in parallel using the dependency information stored in
10262 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10263 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10264 to try to start the kdm and gdm scripts as early as possible, and will
10265 start the facilities required by kdm or gdm as early as possible to
10266 make this happen.
</p
>
10268 <p
>Give it a try, and see if you like the result. If some services
10269 fail to start properly, it is most likely because they have incomplete
10270 init.d script dependencies in their startup script (or some of their
10271 dependent scripts have incomplete dependencies). Report bugs and get
10272 the package maintainers to fix it. :)
</p
>
10274 <p
>Running scripts in parallel could be the default in Debian when we
10275 manage to get the init.d script dependencies complete and correct. I
10276 expect we will get there in Squeeze+
1, if we get manage to test and
10277 fix the remaining issues.
</p
>
10279 <p
>If you report any problems with dependencies in init.d scripts to
10280 the BTS, please usertag the report to get it to show up at
10281 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10282 list of usertagged bugs related to this
</a
>.
</p
>
10287 <title>Debian has switched to dependency based boot sequencing
</title>
10288 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10290 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10291 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10292 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10293 have been migrated to using dependency based boot sequencing. This
10294 conclude work me and others have been doing for the last three days.
10295 It feels great to see this finally part of the default Debian
10296 installation. Now we just need to weed out the last few problems that
10297 are bound to show up, to get everything ready for Squeeze.
</p
>
10299 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10300 fixing the more fundamental problem of handing the event based
10301 non-predictable kernel in the early boot.
</p
>
10306 <title>Taking over sysvinit development
</title>
10307 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10308 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10309 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10310 <description><p
>After several years of frustration with the lack of activity from
10311 the existing sysvinit upstream developer, I decided a few weeks ago to
10312 take over the package and become the new upstream. The number of
10313 patches to track for the Debian package was becoming a burden, and the
10314 lack of synchronization between the distribution made it hard to keep
10315 the package up to date.
</p
>
10317 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10318 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10319 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10320 and Fedora), based on the patches currently in use in these
10321 distributions. We Debian maintainers plan to move to this tarball as
10322 the new upstream as soon as we find time to do the merge. Since the
10323 new tarball was created, we agreed with Werner at SuSe to make a new
10324 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10325 development there. The project is registered and currently waiting
10326 for approval by the Savannah administrators, and as soon as it is
10327 approved, we will import the old versions from svn and continue
10328 working on the future release.
</p
>
10330 <p
>It is a bit ironic that this is done now, when some of the involved
10331 distributions are moving to upstart as a syvinit replacement.
</p
>
10336 <title>Debian boots quicker and quicker
</title>
10337 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10338 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10339 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10340 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10341 people involved in the boot system on Debian and Ubuntu, to see if we
10342 could find more ways to speed up the boot system. This was an Ubuntu
10344 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10345 gathering
</a
>. It was quite productive. We also discussed the future
10346 of boot systems, and ways to handle the increasing number of boot
10347 issues introduced by the Linux kernel becoming more and more
10348 asynchronous and event base. The Ubuntu approach using udev and
10349 upstart might be a good way forward. Time will show.
</p
>
10351 <p
>Anyway, there are a few ways at the moment to speed up the boot
10352 process in Debian. All of these should be applied to get a quick
10357 <li
>Use dash as /bin/sh.
</li
>
10359 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10360 clock is in UTC.
</li
>
10362 <li
>Install and activate the insserv package to enable
10363 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10364 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10368 These points are based on the Google summer of code work done by
10369 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10370 Villegas
</a
>.
10372 <p
>Support for makefile-style concurrency during boot was uploaded to
10373 unstable yesterday. When we tested it, we were able to cut
6 seconds
10374 from the boot sequence. It depend on very correct dependency
10375 declaration in all init.d scripts, so I expect us to find edge cases
10376 where the dependences in some scripts are slightly wrong when we start
10377 using this.
</p
>
10379 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10380 introduced by Raphael Geissert today, one that could affect the
10381 startup speed as well. Instead of starting some scripts concurrently
10382 from rcS.d/ and another set of scripts from rc2.d/, it would be
10383 possible to run a of them in the same process. A quick way to test
10384 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10385 insserv
'. Will need to test if that work. :)
</p
>
10390 <title>BSAs påstander om piratkopiering møter motstand
</title>
10391 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10392 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10393 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10394 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10395 programvareselskapene som Microsoft og Apple, publisert en rapport der
10396 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10397 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10399 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10400 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10401 dagene. Et spesielt interessant kommentar fra Sverige,
10402 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10403 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10406 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10407 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10408 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10409 exakta
", säger BSAs Sverigechef John Hugosson.
10410 </blockquote
>
10412 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10413 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10414 piracy figures need a shot of reality
</a
> og
<a
10415 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10416 Copyright Treaty Work?
</a
></p
>
10418 <p
>Fant lenkene via
<a
10419 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10420 på Slashdot
</a
>.
</p
>
10425 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10426 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10427 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10428 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10429 <description><p
>Kom over
10430 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10431 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10432 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10433 jobber til daglig. En rask opptelling forteller meg at vi har
490
10434 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10435 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10436 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10441 <title>Kryptert harddisk - naturligvis
</title>
10442 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10443 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10444 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10445 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10446 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10447 når en tar tap av arbeidstid, fortrolige dokumenter,
10448 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10449 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10450 til at jeg har kryptert harddisken på både kontormaskinen og min
10451 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10452 komme på avveie, den første informasjon relatert til jobben min ved
10453 Universitetet i Oslo, og den andre relatert til blant annet
10454 foreningsarbeide. Kryptering av diskene gjør at det er lite
10455 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10456 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10457 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10458 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10459 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10460 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10461 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10462 det er gjort slik jeg gjør det er minimale, og gevinstene er
10463 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10464 maskinen reinstalleres og alt er tapt.
</p
>
10466 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10467 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10468 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10469 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10470 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10471 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10472 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10473 betydelige.
</p
>
10478 <title>Two projects that have improved the quality of free software a lot
</title>
10479 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10480 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10481 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10482 <description><p
>There are two software projects that have had huge influence on the
10483 quality of free software, and I wanted to mention both in case someone
10484 do not yet know them.
</p
>
10486 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10487 tool to detect and expose errors in the memory handling of programs.
10488 It is easy to use, all one need to do is to run
'valgrind program
',
10489 and it will report any problems on stdout. It is even better if the
10490 program include debug information. With debug information, it is able
10491 to report the source file name and line number where the problem
10492 occurs. It can report things like
'reading past memory block in file
10493 X line N, the memory block was allocated in file Y, line M
', and
10494 'using uninitialised value in control logic
'. This tool has made it
10495 trivial to investigate reproducible crash bugs in programs, and have
10496 reduced the number of this kind of bugs in free software a lot.
10498 <p
>The second one is
10499 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10500 a source code checker. It is able to process the source of a program
10501 and find problems in the logic without running the program. It
10502 started out as the Stanford Checker and became well known when it was
10503 used to find bugs in the Linux kernel. It is now a commercial tool
10504 and the company behind it is running
10505 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10506 free software community, where a lot of free software projects get
10507 their source checked for free. Several thousand defects have been
10508 found and fixed so far. It can find errors like
'lock L taken in file
10509 X line N is never released if exiting in line M
', or
'the code in file
10510 Y lines O to P can never be executed
'. The projects included in the
10511 community service project have managed to get rid of a lot of
10512 reliability problems thanks to Coverity.
</p
>
10514 <p
>I believe tools like this, that are able to automatically find
10515 errors in the source, are vital to improve the quality of software and
10516 make sure we can get rid of the crashing and failing software we are
10517 surrounded by today.
</p
>
10522 <title>No patch is not better than a useless patch
</title>
10523 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10524 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10525 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10526 <description><p
>Julien Blache
10527 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10528 patch is better than a useless patch
</a
>. I completely disagree, as a
10529 patch allow one to discuss a concrete and proposed solution, and also
10530 prove that the issue at hand is important enough for someone to spent
10531 time on fixing it. No patch do not provide any of these positive
10532 properties.
</p
>
10537 <title>Standardize on protocols and formats, not vendors and applications
</title>
10538 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10539 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10540 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10541 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10542 very good one to form a long lived computer infrastructure. It is the
10543 simple one, lost by many in todays computer industry: Standardize on
10544 open network protocols and open exchange/storage formats, not applications.
10545 Applications come and go, while protocols and files tend to stay, and
10546 thus one want to make it easy to change application and vendor, while
10547 avoiding conversion costs and locking users to a specific platform or
10548 application.
</p
>
10550 <p
>This approach make it possible to replace the client applications
10551 independently of the server applications. One can even allow users to
10552 use several different applications as long as they handle the selected
10553 protocol and format. In the normal case, only one client application
10554 is recommended and users only get help if they choose to use this
10555 application, but those that want to deviate from the easy path are not
10556 blocked from doing so.
</p
>
10558 <p
>It also allow us to replace the server side without forcing the
10559 users to replace their applications, and thus allow us to select the
10560 best server implementation at any moment, when scale and resouce
10561 requirements change.
</p
>
10563 <p
>I strongly recommend standardizing - on open network protocols and
10564 open formats, but I would never recommend standardizing on a single
10565 application that do not use open network protocol or open formats.
</p
>
10570 <title>Returning from Skolelinux developer gathering
</title>
10571 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10572 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10573 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10574 <description><p
>I
'm sitting on the train going home from this weekends Debian
10575 Edu/Skolelinux development gathering. I got a bit done tuning the
10576 desktop, and looked into the dynamic service location protocol
10577 implementation avahi. It look like it could be useful for us. Almost
10578 30 people participated, and I believe it was a great environment to
10579 get to know the Skolelinux system. Walter Bender, involved in the
10580 development of the Sugar educational platform, presented his stuff and
10581 also helped me improve my OLPC installation. He also showed me that
10582 his Turtle Art application can be used in standalone mode, and we
10583 agreed that I would help getting it packaged for Debian. As a
10584 standalone application it would be great for Debian Edu. We also
10585 tried to get the video conferencing working with two OLPCs, but that
10586 proved to be too hard for us. The application seem to need more work
10587 before it is ready for me. I look forward to getting home and relax
10593 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10594 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10595 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10596 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10597 <description><p
>The state of standardized LDAP schemas on Linux is far from
10598 optimal. There is RFC
2307 documenting one way to store NIS maps in
10599 LDAP, and a modified version of this normally called RFC
2307bis, with
10600 some modifications to be compatible with Active Directory. The RFC
10601 specification handle the content of a lot of system databases, but do
10602 not handle DNS zones and DHCP configuration.
</p
>
10604 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10605 we would like to store information about users, SMB clients/hosts,
10606 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10607 and LTSP configuration in LDAP. These objects have a lot in common,
10608 but with the current LDAP schemas it is not possible to have one
10609 object per entity. For example, one need to have at least three LDAP
10610 objects for a given computer, one with the SMB related stuff, one with
10611 DNS information and another with DHCP information. The schemas
10612 provided for DNS and DHCP are impossible to combine into one LDAP
10613 object. In addition, it is impossible to implement quick queries for
10614 netgroup membership, because of the way NIS triples are implemented.
10615 It just do not scale. I believe it is time for a few RFC
10616 specifications to cleam up this mess.
</p
>
10618 <p
>I would like to have one LDAP object representing each computer in
10619 the network, and this object can then keep the SMB (ie host key), DHCP
10620 (mac address/name) and DNS (name/IP address) settings in one place.
10621 It need to be efficently stored to make sure it scale well.
</p
>
10623 <p
>I would also like to have a quick way to map from a user or
10624 computer and to the net group this user or computer is a member.
</p
>
10626 <p
>Active Directory have done a better job than unix heads like myself
10627 in this regard, and the unix side need to catch up. Time to start a
10628 new IETF work group?
</p
>
10633 <title>Endelig er Debian Lenny gitt ut
</title>
10634 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10636 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10637 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10638 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10639 Et langt steg videre for Debian-prosjektet, og en rekke nye
10640 programpakker blir nå tilgjengelig for de av oss som bruker den
10641 stabile utgaven av Debian. Neste steg er nå å få
10642 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10643 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10644 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10645 slippes løs på skolene. Takk til alle debian-utviklerne som har
10646 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10647 bootsekvens tilgjengelig i stabil utgave, vha pakken
10648 <tt
>insserv
</tt
>.
</p
>
10653 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10654 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10655 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10656 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10657 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10658 Oslo. Most of Saturday was used for the general assemly for the
10659 member organization, but the rest of the weekend I used to tune the
10660 LTSP installation. LTSP now work out of the box on the
10-network.
10661 Acer Aspire One proved to be a very nice thin client, with both
10662 screen, mouse and keybard in a small box. Was working on getting the
10663 diskless workstation setup configured out of the box, but did not
10664 finish it before the weekend was up.
</p
>
10666 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10667 the Brazilian group, so that will have to wait for the next
10668 development gathering. Would love to have the Debian Edu installer
10669 automatically detect and configure a multiseat setup when it find one
10670 of these cards.
</p
>
10675 <title>The sorry state of multimedia browser plugins in Debian
</title>
10676 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10677 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10678 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10679 <description><p
>Recently I have spent some time evaluating the multimedia browser
10680 plugins available in Debian Lenny, to see which one we should use by
10681 default in Debian Edu. We need an embedded video playing plugin with
10682 control buttons to pause or stop the video, and capable of streaming
10683 all the multimedia content available on the web. The test results and
10684 notes are available on
10685 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10686 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10687 fill this need. My personal video player favorite, VLC, has a really
10688 bad plugin which fail on a lot of the test pages. A lot of the MIME
10689 types I would expect to work with any free software player (like
10690 video/ogg), just do not work. And simple formats like the
10691 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10692 totem and vlc plugins. I hope the situation will improve soon. No
10693 wonder sites use the proprietary Adobe flash to play video.
</p
>
10695 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10696 be the only one fitting our needs. :/
</p
>