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>Easier recipe to observe the cell phones around you
</title>
11 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
13 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
14 <description><p
>A little more than a month ago I wrote
15 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
16 to observe the SIM card ID (aka IMSI number) of mobile phones talking
17 to nearby mobile phone base stations using Debian GNU/Linux and a
18 cheap USB software defined radio
</a
>, and thus being able to pinpoint
19 the location of people and equipment (like cars and trains) with an
20 accuracy of a few kilometer. Since then we have worked to make the
21 procedure even simpler, and it is now possible to do this without any
22 manual frequency tuning and without building your own packages.
</p
>
24 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
25 package is now included in Debian testing and unstable, and the
26 IMSI-catcher code no longer require root access to fetch and decode
27 the GSM data collected using gr-gsm.
</p
>
29 <p
>Here is an updated recipe, using packages built by Debian and a git
30 clone of two python scripts:
</p
>
34 <li
>Start with a Debian machine running the Buster version (aka
37 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
38 python-scapy
</tt
>' as root to install required packages.
</li
>
40 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
41 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
43 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
45 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
46 scan-and-livemon
</tt
>' to locate the frequency of nearby base
47 stations and start listening for GSM packages on one of them.
</li
>
49 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
50 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
54 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
55 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
56 program grgsm_scanner
</a
>) do not work with the HackRF radio. It do
57 work with RTL
8232 and other similar USB radio receivers you can get
59 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
60 from ebay
</a
>), so for now the solution is to scan using the RTL radio
61 and only use HackRF for fetching GSM data.
</p
>
63 <p
>As far as I can tell, a cell phone only show up on one of the
64 frequencies at the time, so if you are going to track and count every
65 cell phone around you, you need to listen to all the frequencies used.
66 To listen to several frequencies, use the --numrecv argument to
67 scan-and-livemon to use several receivers. Further, I am not sure if
68 phones using
3G or
4G will show as talking GSM to base stations, so
69 this approach might not see all phones around you. I typically see
70 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
72 <p
>I
've tried to run the scanner on a
73 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
74 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
75 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
76 stdout, I am told there it is caused by a buffer overflow between the
77 radio and GNU Radio, caused by the program being unable to read the
78 GSM data fast enough. If you see a stream of
'O
's from the terminal
79 where you started scan-and-livemon, you need a give the process more
80 CPU power. Perhaps someone are able to optimize the code to a point
81 where it become possible to set up RPi3 based GSM sniffers? I tried
82 using Raspbian instead of Debian, but there seem to be something wrong
83 with GNU Radio on raspbian, causing glibc to abort().
</p
>
88 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
89 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
90 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
91 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
92 <description><p
>On friday, I came across an interesting article in the Norwegian
93 web based ICT news magazine digi.no on
94 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
95 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
96 DVB-T software defined radios. The article refered to instructions
97 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
98 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
100 <p
>The instructions said to use Ubuntu, install pip using apt (to
101 bypass apt), use pip to install pybombs (to bypass both apt and pip),
102 and the ask pybombs to fetch and build everything you need from
103 scratch. I wanted to see if I could do the same on the most recent
104 Debian packages, but this did not work because pybombs tried to build
105 stuff that no longer build with the most recent openssl library or
106 some other version skew problem. While trying to get this recipe
107 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
108 and the only piece of software dependency missing in Debian was the
109 gr-gsm package. I also found out that the lead upstream developer of
110 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
111 Debian packages provided in an Ubuntu PPA repository. All I needed to
112 do was to dget the Debian source package and built it.
</p
>
114 <p
>The IMSI collector is a python script listening for packages on the
115 loopback network device and printing to the terminal some specific GSM
116 packages with IMSI numbers in them. The code is fairly short and easy
117 to understand. The reason this work is because gr-gsm include a tool
118 to read GSM data from a software defined radio like a DVB-T USB stick
119 and other software defined radios, decode them and inject them into a
120 network device on your Linux machine (using the loopback device by
121 default). This proved to work just fine, and I
've been testing the
122 collector for a few days now.
</p
>
124 <p
>The updated and simpler recipe is thus to
</p
>
128 <li
>start with a Debian machine running Stretch or newer,
</li
>
130 <li
>build and install the gr-gsm package available from
131 <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
>
133 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
135 <li
>run grgsm_livemon and adjust the frequency until the terminal
136 where it was started is filled with a stream of text (meaning you
137 found a GSM station).
</li
>
139 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
143 <p
>To make it even easier in the future to get this sniffer up and
144 running, I decided to package
145 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
146 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
147 #
871055</a
>), and the package was uploaded into the NEW queue today.
148 Luckily the gnuradio maintainer has promised to help me, as I do not
149 know much about gnuradio stuff yet.
</p
>
151 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
152 commercial tools like
153 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
154 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
155 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
156 Stingray
</a
>, but I hope the existance of cheap alternatives can make
157 more people realise how their whereabouts when carrying a cell phone
158 is easily tracked. Seeing the data flow on the screen, realizing that
159 I live close to a police station and knowing that the police is also
160 wearing cell phones, I wonder how hard it would be for criminals to
161 track the position of the police officers to discover when there are
162 police near by, or for foreign military forces to track the location
163 of the Norwegian military forces, or for anyone to track the location
164 of government officials...
</p
>
166 <p
>It is worth noting that the data reported by the IMSI-catcher
167 script mentioned above is only a fraction of the data broadcasted on
168 the GSM network. It will only collect one frequency at the time,
169 while a typical phone will be using several frequencies, and not all
170 phones will be using the frequencies tracked by the grgsm_livemod
171 program. Also, there is a lot of radio chatter being ignored by the
172 simple_IMSI-catcher script, which would be collected by extending the
173 parser code. I wonder if gr-gsm can be set up to listen to more than
174 one frequency?
</p
>
179 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
180 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
181 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
182 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
183 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
185 <p
>I finally received a copy of the Norwegian Bokmål edition of
186 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
187 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
188 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
189 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
190 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
191 price. The book is also available for download in electronic form as
192 PDF, EPUB and Mobipocket, as can be
193 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
194 as a web page
</a
>.
</p
>
196 <p
>This is the second book I publish (the first was the book
197 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
199 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
200 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
202 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
203 Bokmål
</a
>), and I am very excited to finally wrap up this
205 "<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
206 for Debian-administratoren
</a
>" will be well received.
</p
>
211 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
212 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
214 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
215 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
216 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
217 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
218 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
219 på om den fri oversetterløsningen
220 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
221 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
223 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
226 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
227 rolle og muligheter til å håndtere internasjonale utfordringer, som
228 for eksempel flykningekrisen.
</p
>
230 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
233 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
234 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
239 <p
>Dette oversetter Apertium slik:
</p
>
242 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
243 andre aktørar og høve til å handtera internasjonale utfordringar, som
244 til dømes *flykningekrisen.
</p
>
246 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
250 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
251 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
256 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
257 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
258 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
259 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
260 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
261 det er kanskje flisespikking. Det understreker vel bare at det alltid
262 trengs korrekturlesning etter automatisk oversettelse.
</p
>
267 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
268 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
270 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
271 <description><p
>Over the years, administrating thousand of NFS mounting linux
272 computers at the time, I often needed a way to detect if the machine
273 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
274 file or directory affected by the hang, the process (and possibly the
275 shell) will hang too. So you want to be able to detect this without
276 risking the detection process getting stuck too. It has not been
277 obvious how to do this. When the hang has lasted a while, it is
278 possible to find messages like these in dmesg:
</p
>
280 <p
><blockquote
>
281 nfs: server nfsserver not responding, still trying
282 <br
>nfs: server nfsserver OK
283 </blockquote
></p
>
285 <p
>It is hard to know if the hang is still going on, and it is hard to
286 be sure looking in dmesg is going to work. If there are lots of other
287 messages in dmesg the lines might have rotated out of site before they
288 are noticed.
</p
>
290 <p
>While reading through the nfs client implementation in linux kernel
291 code, I came across some statistics that seem to give a way to detect
292 it. The om_timeouts sunrpc value in the kernel will increase every
293 time the above log entry is inserted into dmesg. And after digging a
294 bit further, I discovered that this value show up in
295 /proc/self/mountstats on Linux.
</p
>
297 <p
>The mountstats content seem to be shared between files using the
298 same file system context, so it is enough to check one of the
299 mountstats files to get the state of the mount point for the machine.
300 I assume this will not show lazy umounted NFS points, nor NFS mount
301 points in a different process context (ie with a different filesystem
302 view), but that does not worry me.
</p
>
304 <p
>The content for a NFS mount point look similar to this:
</p
>
306 <p
><blockquote
><pre
>
308 device /dev/mapper/Debian-var mounted on /var with fstype ext3
309 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
310 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
312 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
313 sec: flavor=
1,pseudoflavor=
1
314 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
315 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
316 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
317 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
319 NULL:
0 0 0 0 0 0 0 0
320 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
321 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
322 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
323 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
324 READLINK:
125 125 0 20472 18620 0 1112 1118
325 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
326 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
327 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
328 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
329 SYMLINK:
903 903 0 233428 245488 6 5865 5917
330 MKNOD:
80 80 0 20148 21760 0 299 304
331 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
332 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
333 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
334 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
335 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
336 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
337 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
338 FSINFO:
2 2 0 232 328 0 1 1
339 PATHCONF:
1 1 0 116 140 0 0 0
340 COMMIT:
0 0 0 0 0 0 0 0
342 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
344 </pre
></blockquote
></p
>
346 <p
>The key number to look at is the third number in the per-op list.
347 It is the number of NFS timeouts experiences per file system
348 operation. Here
22 write timeouts and
5 access timeouts. If these
349 numbers are increasing, I believe the machine is experiencing NFS
350 hang. Unfortunately the timeout value do not start to increase right
351 away. The NFS operations need to time out first, and this can take a
352 while. The exact timeout value depend on the setup. For example the
353 defaults for TCP and UDP mount points are quite different, and the
354 timeout value is affected by the soft, hard, timeo and retrans NFS
355 mount options.
</p
>
357 <p
>The only way I have been able to get working on Debian and RedHat
358 Enterprise Linux for getting the timeout count is to peek in /proc/.
360 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
361 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
362 command can be used to get these timeout values. But this do not work
363 on Linux, as far as I can tell. I
364 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
365 but have not seen any replies yet.
</p
>
367 <p
>Is there a better way to figure out if a Linux NFS client is
368 experiencing NFS hangs? Is there a way to detect which processes are
369 affected? Is there a way to get the NFS mount going quickly once the
370 network problem causing the NFS hang has been cleared? I would very
371 much welcome some clues, as we regularly run into NFS hangs.
</p
>
376 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
377 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
378 <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>
379 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
380 <description><p
>For almost a year now, we have been working on making a Norwegian
381 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
382 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
383 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
384 we are working on the proof reading to ensure consistent language and
385 use of correct computer science terms. The plan is to make the book
386 available on paper, as well as in electronic form. For that to
387 happen, the proof reading must be completed and all the figures need
388 to be translated. If you want to help out, get in touch.
</p
>
390 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
392 fresh PDF edition
</a
> in A4 format (the final book will have smaller
393 pages) of the book created every morning is available for
394 proofreading. If you find any errors, please
395 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
396 Weblate and correct the error
</a
>. The
397 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
398 of the translation including figures
</a
> is a useful source for those
399 provide Norwegian bokmål screen shots and figures.
</p
>
404 <title>Unlimited randomness with the ChaosKey?
</title>
405 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
406 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
407 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
408 <description><p
>A few days ago I ordered a small batch of
409 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
410 USB dongle for generating entropy created by Bdale Garbee and Keith
411 Packard. Yesterday it arrived, and I am very happy to report that it
412 work great! According to its designers, to get it to work out of the
413 box, you need the Linux kernel version
4.1 or later. I tested on a
414 Debian Stretch machine (kernel version
4.9), and there it worked just
415 fine, increasing the available entropy very quickly. I wrote a small
416 test oneliner to test. It first print the current entropy level,
417 drain /dev/random, and then print the entropy level for five seconds.
418 Here is the situation without the ChaosKey inserted:
</p
>
420 <blockquote
><pre
>
421 % cat /proc/sys/kernel/random/entropy_avail; \
422 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
423 for n in $(seq
1 5); do \
424 cat /proc/sys/kernel/random/entropy_avail; \
430 28 byte kopiert,
0,
000264565 s,
106 kB/s
437 </pre
></blockquote
>
439 <p
>The entropy level increases by
3-
4 every second. In such case any
440 application requiring random bits (like a HTTPS enabled web server)
441 will halt and wait for more entrpy. And here is the situation with
442 the ChaosKey inserted:
</p
>
444 <blockquote
><pre
>
445 % cat /proc/sys/kernel/random/entropy_avail; \
446 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
447 for n in $(seq
1 5); do \
448 cat /proc/sys/kernel/random/entropy_avail; \
454 104 byte kopiert,
0,
000487647 s,
213 kB/s
461 </pre
></blockquote
>
463 <p
>Quite the difference. :) I bought a few more than I need, in case
464 someone want to buy one here in Norway. :)
</p
>
466 <p
>Update: The dongle was presented at Debconf last year. You might
467 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
468 recording illuminating
</a
>. It explains exactly what the source of
469 randomness is, if you are unable to spot it from the schema drawing
470 available from the ChaosKey web site linked at the start of this blog
476 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
477 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
478 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
479 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
480 <description><p
>Did you ever wonder where the web trafic really flow to reach the
481 web servers, and who own the network equipment it is flowing through?
482 It is possible to get a glimpse of this from using traceroute, but it
483 is hard to find all the details. Many years ago, I wrote a system to
484 map the Norwegian Internet (trying to figure out if our plans for a
485 network game service would get low enough latency, and who we needed
486 to talk to about setting up game servers close to the users. Back
487 then I used traceroute output from many locations (I asked my friends
488 to run a script and send me their traceroute output) to create the
489 graph and the map. The output from traceroute typically look like
493 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
494 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
495 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
496 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
497 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
498 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
499 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
500 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
504 </pre
></p
>
506 <p
>This show the DNS names and IP addresses of (at least some of the)
507 network equipment involved in getting the data traffic from me to the
508 www.stortinget.no server, and how long it took in milliseconds for a
509 package to reach the equipment and return to me. Three packages are
510 sent, and some times the packages do not follow the same path. This
511 is shown for hop
5, where three different IP addresses replied to the
512 traceroute request.
</p
>
514 <p
>There are many ways to measure trace routes. Other good traceroute
515 implementations I use are traceroute (using ICMP packages) mtr (can do
516 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
517 traceroute and a lot of other capabilities). All of them are easily
518 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
520 <p
>This time around, I wanted to know the geographic location of
521 different route points, to visualize how visiting a web page spread
522 information about the visit to a lot of servers around the globe. The
523 background is that a web site today often will ask the browser to get
524 from many servers the parts (for example HTML, JSON, fonts,
525 JavaScript, CSS, video) required to display the content. This will
526 leak information about the visit to those controlling these servers
527 and anyone able to peek at the data traffic passing by (like your ISP,
528 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
530 <p
>Lets pick an example, the Norwegian parliament web site
531 www.stortinget.no. It is read daily by all members of parliament and
532 their staff, as well as political journalists, activits and many other
533 citizens of Norway. A visit to the www.stortinget.no web site will
534 ask your browser to contact
8 other servers: ajax.googleapis.com,
535 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
536 stats.g.doubleclick.net, www.google-analytics.com,
537 www.googletagmanager.com and www.netigate.se. I extracted this by
538 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
539 Stortinget web page and tell me all the URLs PhantomJS downloaded to
540 render the page (in HAR format using
541 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
542 netsniff example
</a
>. I am very grateful to Gorm for showing me how
543 to do this). My goal is to visualize network traces to all IP
544 addresses behind these DNS names, do show where visitors personal
545 information is spread when visiting the page.
</p
>
547 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
548 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
>
550 <p
>When I had a look around for options, I could not find any good
551 free software tools to do this, and decided I needed my own traceroute
552 wrapper outputting KML based on locations looked up using GeoIP. KML
553 is easy to work with and easy to generate, and understood by several
554 of the GIS tools I have available. I got good help from by NUUG
555 colleague Anders Einar with this, and the result can be seen in
556 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
557 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
558 free GeoIP databases I could find (and the for-pay databases my
559 friends had access to) is not up to the task. The IP addresses of
560 central Internet infrastructure would typically be placed near the
561 controlling companies main office, and not where the router is really
562 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
563 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
565 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
566 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
>
568 <p
>I also had a look at the visual traceroute graph created by
569 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
570 showing IP network ownership (aka AS owner) for the IP address in
572 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
573 graph display a lot of useful information about the traceroute in SVG
574 format
</a
>, and give a good indication on who control the network
575 equipment involved, but it do not include geolocation. This graph
576 make it possible to see the information is made available at least for
577 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
578 3 Communications and NetDNA.
</p
>
580 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
581 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
>
583 <p
>In the process, I came across the
584 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
585 Salim Gasmi. Its methology of combining guesses based on DNS names,
586 various location databases and finally use latecy times to rule out
587 candidate locations seemed to do a very good job of guessing correct
588 geolocation. But it could only do one trace at the time, did not have
589 a sensor in Norway and did not make the geolocations easily available
590 for postprocessing. So I contacted the developer and asked if he
591 would be willing to share the code (he refused until he had time to
592 clean it up), but he was interested in providing the geolocations in a
593 machine readable format, and willing to set up a sensor in Norway. So
594 since yesterday, it is possible to run traces from Norway in this
595 service thanks to a sensor node set up by
596 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
597 trace in KML format for further processing.
</p
>
599 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
600 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
>
602 <p
>Here we can see a lot of trafic passes Sweden on its way to
603 Denmark, Germany, Holland and Ireland. Plenty of places where the
604 Snowden confirmations verified the traffic is read by various actors
605 without your best interest as their top priority.
</p
>
607 <p
>Combining KML files is trivial using a text editor, so I could loop
608 over all the hosts behind the urls imported by www.stortinget.no and
609 ask for the KML file from GeoTraceroute, and create a combined KML
610 file with all the traces (unfortunately only one of the IP addresses
611 behind the DNS name is traced this time. To get them all, one would
612 have to request traces using IP number instead of DNS names from
613 GeoTraceroute). That might be the next step in this project.
</p
>
615 <p
>Armed with these tools, I find it a lot easier to figure out where
616 the IP traffic moves and who control the boxes involved in moving it.
617 And every time the link crosses for example the Swedish border, we can
618 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
619 Britain and NSA in USA and cables around the globe. (Hm, what should
620 we tell them? :) Keep that in mind if you ever send anything
621 unencrypted over the Internet.
</p
>
623 <p
>PS: KML files are drawn using
624 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
625 Rublev
<a/
>, as it was less cluttered than the local Linux application
626 Marble. There are heaps of other options too.
</p
>
628 <p
>As usual, if you use Bitcoin and want to show your support of my
629 activities, please send Bitcoin donations to my address
630 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
635 <title>Appstream just learned how to map hardware to packages too!
</title>
636 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
637 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
638 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
639 <description><p
>I received a very nice Christmas present today. As my regular
640 readers probably know, I have been working on the
641 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
642 system
</a
> for many years. The goal of the Isenkram system is to make
643 it easier for users to figure out what to install to get a given piece
644 of hardware to work in Debian, and a key part of this system is a way
645 to map hardware to packages. Isenkram have its own mapping database,
646 and also uses data provided by each package using the AppStream
647 metadata format. And today,
648 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
649 Debian learned to look up hardware the same way Isenkram is doing it,
650 ie using fnmatch():
</p
>
653 % appstreamcli what-provides modalias \
654 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
655 Identifier: pymissile [generic]
657 Summary: Control original Striker USB Missile Launcher
659 % appstreamcli what-provides modalias usb:v0694p0002d0000
660 Identifier: libnxt [generic]
662 Summary: utility library for talking to the LEGO Mindstorms NXT brick
665 Identifier: t2n [generic]
667 Summary: Simple command-line tool for Lego NXT
670 Identifier: python-nxt [generic]
672 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
675 Identifier: nbc [generic]
677 Summary: C compiler for LEGO Mindstorms NXT bricks
680 </pre
></p
>
682 <p
>A similar query can be done using the combined AppStream and
683 Isenkram databases using the isenkram-lookup tool:
</p
>
686 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
688 % isenkram-lookup usb:v0694p0002d0000
694 </pre
></p
>
696 <p
>You can find modalias values relevant for your machine using
697 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
699 <p
>If you want to make this system a success and help Debian users
700 make the most of the hardware they have, please
701 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
702 AppStream metadata for your package following the guidelines
</a
>
703 documented in the wiki. So far only
11 packages provide such
704 information, among the several hundred hardware specific packages in
705 Debian. The Isenkram database on the other hand contain
101 packages,
706 mostly related to USB dongles. Most of the packages with hardware
707 mapping in AppStream are LEGO Mindstorms related, because I have, as
708 part of my involvement in
709 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
710 team
</a
> given priority to making sure LEGO users get proposed the
711 complete set of packages in Debian for that particular hardware. The
712 team also got a nice Christmas present today. The
713 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
714 package
</a
> made it into Debian. With this package in place, it is
715 now possible to use the LEGO Mindstorms NXT unit with only free
716 software, as the nxt-firmware package contain the source and firmware
717 binaries for the NXT brick.
</p
>
719 <p
>As usual, if you use Bitcoin and want to show your support of my
720 activities, please send Bitcoin donations to my address
721 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
726 <title>Isenkram updated with a lot more hardware-package mappings
</title>
727 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
728 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
729 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
730 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
731 system
</a
> I wrote two years ago to make it easier in Debian to find
732 and install packages to get your hardware dongles to work, is still
733 going strong. It is a system to look up the hardware present on or
734 connected to the current system, and map the hardware to Debian
735 packages. It can either be done using the tools in isenkram-cli or
736 using the user space daemon in the isenkram package. The latter will
737 notify you, when inserting new hardware, about what packages to
738 install to get the dongle working. It will even provide a button to
739 click on to ask packagekit to install the packages.
</p
>
741 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
760 </pre
></p
>
762 <p
>It can also list the firware package providing firmware requested
763 by the load kernel modules, which in my case is an empty list because
764 I have all the firmware my machine need:
767 % /usr/sbin/isenkram-autoinstall-firmware -l
768 info: did not find any firmware files requested by loaded kernel modules. exiting
770 </pre
></p
>
772 <p
>The last few days I had a look at several of the around
250
773 packages in Debian with udev rules. These seem like good candidates
774 to install when a given hardware dongle is inserted, and I found
775 several that should be proposed by isenkram. I have not had time to
776 check all of them, but am happy to report that now there are
97
777 packages packages mapped to hardware by Isenkram.
11 of these
778 packages provide hardware mapping using AppStream, while the rest are
779 listed in the modaliases file provided in isenkram.
</p
>
781 <p
>These are the packages with hardware mappings at the moment. The
782 <strong
>marked packages
</strong
> are also announcing their hardware
783 support using AppStream, for everyone to use:
</p
>
785 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
786 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
787 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
788 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
789 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
790 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
791 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
792 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
793 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
794 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
795 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
796 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
797 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
798 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
799 pcscd, pidgin-blinklight, printer-driver-splix,
800 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
801 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
802 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
803 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
804 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
805 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
806 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
807 xserver-xorg-video-vmware, yubikey-personalization and
808 zd1211-firmware
</p
>
810 <p
>If you know of other packages, please let me know with a wishlist
811 bug report against the isenkram-cli package, and ask the package
813 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
814 metadata according to the guidelines
</a
> to provide the information
815 for everyone. In time, I hope to get rid of the isenkram specific
816 hardware mapping and depend exclusively on AppStream.
</p
>
818 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
819 much hardware, and suggest that the package with with any ethernet
820 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
821 the details. I hope the maintainer find time to address it soon. In
822 the mean time I provide an override in isenkram.
</p
>
827 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
828 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
829 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
830 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
831 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
833 <p
>In my early years, I played
834 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
835 Elite
</a
> on my PC. I spent many months trading and fighting in
836 space, and reached the
'elite
' fighting status before I moved on. The
837 original Elite game was available on Commodore
64 and the IBM PC
838 edition I played had a
64 KB executable. I am still impressed today
839 that the authors managed to squeeze both a
3D engine and details about
840 more than
2000 planet systems across
7 galaxies into a binary so
843 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
844 software game Oolite inspired by Elite
</a
> for a while, but did not
845 really have time to test it properly until a few days ago. It was
846 great to discover that my old knowledge about trading routes were
847 still valid. But my fighting and flying abilities were gone, so I had
848 to retrain to be able to dock on a space station. And I am still not
849 able to make much resistance when I am attacked by pirates, so I
850 bougth and mounted the most powerful laser in the rear to be able to
851 put up at least some resistance while fleeing for my life. :)
</p
>
853 <p
>When playing Elite in the late eighties, I had to discover
854 everything on my own, and I had long lists of prices seen on different
855 planets to be able to decide where to trade what. This time I had the
857 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
858 where information about each planet is easily available with common
859 price ranges and suggested trading routes. This improved my ability
860 to earn money and I have been able to earn enough to buy a lot of
861 useful equipent in a few days. I believe I originally played for
862 months before I could get a docking computer, while now I could get it
863 after less then a week.
</p
>
865 <p
>If you like science fiction and dreamed of a life as a vagabond in
866 space, you should try out Oolite. It is available for Linux, MacOSX
867 and Windows, and is included in Debian and derivatives since
2011.
</p
>
869 <p
>As usual, if you use Bitcoin and want to show your support of my
870 activities, please send Bitcoin donations to my address
871 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
876 <title>Quicker Debian installations using eatmydata
</title>
877 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
879 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
880 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
881 installation system, observing how using
882 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
883 could speed up the installation
</a
> quite a bit. My testing measured
884 speedup around
20-
40 percent for Debian Edu, where we install around
885 1000 packages from within the installer. The eatmydata package
886 provide a way to disable/delay file system flushing. This is a bit
887 risky in the general case, as files that should be stored on disk will
888 stay only in memory a bit longer than expected, causing problems if a
889 machine crashes at an inconvenient time. But for an installation, if
890 the machine crashes during installation the process is normally
891 restarted, and avoiding disk operations as much as possible to speed
892 up the process make perfect sense.
894 <p
>I added code in the Debian Edu specific installation code to enable
895 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
896 but did not have time to push it any further. But a few months ago I
897 picked it up again and worked with the libeatmydata package maintainer
898 Mattia Rizzolo to make it easier for everyone to get this installation
899 speedup in Debian. Thanks to our cooperation There is now an
900 eatmydata-udeb package in Debian testing and unstable, and simply
901 enabling/installing it in debian-installer (d-i) is enough to get the
902 quicker installations. It can be enabled using preseeding. The
903 following untested kernel argument should do the trick:
</p
>
905 <blockquote
><pre
>
906 preseed/early_command=
"anna-install eatmydata-udeb
"
907 </pre
></blockquote
>
909 <p
>This should ask d-i to install the package inside the d-i
910 environment early in the installation sequence. Having it installed
911 in d-i in turn will make sure the relevant scripts are called just
912 after debootstrap filled /target/ with the freshly installed Debian
913 system to configure apt to run dpkg with eatmydata. This is enough to
914 speed up the installation process. There is a proposal to
915 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
916 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
917 tested its impact.
</p
>
923 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
924 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
925 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
926 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
927 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
928 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
929 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
930 elever over det ganske land skal levere inn hvert år. Det mange ikke
931 vet er at selv om de kommersielle alternativene
932 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
933 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
934 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
935 utmerket fri programvarealternativ som kan. Oversetterverktøyet
936 Apertium har støtte for en rekke språkkombinasjoner, og takket være
937 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
938 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
939 nynorsk, og få den automatoversatt til det andre skriftspråket.
940 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
941 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
942 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
943 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
944 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
945 teksten din i webskjemaet der.
947 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
948 teknologien kan du enten installere pakken
949 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
950 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
952 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
953 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
954 denne teksten som ble skrevet på bokmål over maskinoversatt til
959 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
960 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
961 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
962 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
963 veit er at sjølv om dei kommersielle alternativa
964 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
965 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
966 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
967 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
968 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
969 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
970 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
971 nynorsk, og få den *automatoversatt til det andre skriftspråket.
972 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
973 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
974 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
975 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
976 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
977 teksta di i *webskjemaet der.
979 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
980 teknologien kan du anten installera pakken
981 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
982 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
983 *api.*apertium.org. Sjå
984 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
985 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
986 for denne teksta som vart skreva på bokmål over *maskinoversatt til
992 <title>Coz profiler for multi-threaded software is now in Debian
</title>
993 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
994 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
995 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
996 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
997 profiler able to run benchmarking experiments on the instrumented
998 multi-threaded program, finally
999 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1000 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1002 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1003 blogged about the coz tool
</a
> in August working with upstream to make
1004 it suitable for Debian. There are still issues with clang
1005 compatibility, inline assembly only working x86 and minimized
1006 JavaScript libraries.
</p
>
1008 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1010 <p
><blockquote
>
1011 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1012 </blockquote
></p
>
1014 <p
>This will produce a profile.coz file in the current working
1015 directory with the profiling information. This is then given to a
1016 JavaScript application provided in the package and available from
1017 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1018 To start the local copy, invoke it in a browser like this:
</p
>
1020 <p
><blockquote
>
1021 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1022 </blockquote
></p
>
1024 <p
>See the project home page and the
1025 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1026 ;login: article on Coz
</a
> for more information on how it is
1032 <title>My own self balancing Lego Segway
</title>
1033 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1034 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1035 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1036 <description><p
>A while back I received a Gyro sensor for the NXT
1037 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1038 present. It had been on my wishlist for a while, because I wanted to
1039 build a Segway like balancing lego robot. I had already built
1040 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1041 robot
</a
> with the kids, using the light/color sensor included in the
1042 NXT kit as the balance sensor, but it was not working very well. It
1043 could balance for a while, but was very sensitive to the light
1044 condition in the room and the reflective properties of the surface and
1045 would fall over after a short while. I wanted something more robust,
1047 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1048 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1049 wishlist for some years before it suddenly showed up as a gift from my
1050 loved ones. :)
</p
>
1052 <p
>Unfortunately I have not had time to sit down and play with it
1053 since then. But that changed some days ago, when I was searching for
1054 lego segway information and came across a recipe from HiTechnic for
1056 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1057 HTWay
</a
>, a segway like balancing robot. Build instructions and
1058 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1059 code
</a
> was included, so it was just a question of putting it all
1060 together. And thanks to the great work of many Debian developers, the
1061 compiler needed to build the source for the NXT is already included in
1062 Debian, so I was read to go in less than an hour. The resulting robot
1063 do not look very impressive in its simplicity:
</p
>
1065 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1067 <p
>Because I lack the infrared sensor used to control the robot in the
1068 design from HiTechnic, I had to comment out the last task
1069 (taskControl). I simply placed /* and */ around it get the program
1070 working without that sensor present. Now it balances just fine until
1071 the battery status run low:
</p
>
1073 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1074 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1075 </video
></p
>
1077 <p
>Now we would like to teach it how to follow a line and take remote
1078 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1080 <p
>If you, like me, love LEGO and want to make sure we find the tools
1081 they need to work with LEGO in Debian and all our derivative
1082 distributions like Ubuntu, check out
1083 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1084 project page
</a
> and join the Debian LEGO team. Personally I own a
1085 RCX and NXT controller (no EV3), and would like to make sure the
1086 Debian tools needed to program the systems I own work as they
1092 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1093 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1094 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1095 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1096 <description><p
>In July
1097 <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
1098 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1099 the ability to receive SMS messages (aka without a cell phone). It is
1100 time to share some experiences and provide an updated setup.
</p
>
1102 <p
>The Signal app have worked fine for several months now, and I use
1103 it regularly to chat with my loved ones. I had a major snag at the
1104 end of my summer vacation, when the the app completely forgot my
1105 setup, identity and keys. The reason behind this major mess was
1106 running out of disk space. To avoid that ever happening again I have
1107 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1108 roll back to an earlier version if the files are wiped by mistake. I
1109 had to use it once after introducing the git backup. When rolling
1110 back to an earlier version, one need to use the
'reset session
' option
1111 in Signal to get going, and notify the people you talk with about the
1112 problem. I assume there is some sequence number tracking in the
1113 protocol to detect rollback attacks. The git repository is rather big
1114 (
674 MiB so far), but I have not tried to figure out if some of the
1115 content can be added to a .gitignore file due to lack of spare
1118 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1119 make it impossible to send messages using Signal. I could still
1120 receive them, but had to patch the code with a new timestamp to send.
1121 I believe the timeout is added by the developers to force people to
1122 upgrade to the latest version of the app, even when there is no
1123 protocol changes, to reduce the version skew among the user base and
1124 thus try to keep the number of support requests down.
</p
>
1126 <p
>Since my original recipe, the Signal source code changed slightly,
1127 making the old patch fail to apply cleanly. Below is an updated
1128 patch, including the shell wrapper I use to start Signal. The
1129 original version required a new user to locate the JavaScript console
1130 and call a function from there. I got help from a friend with more
1131 JavaScript knowledge than me to modify the code to provide a GUI
1132 button instead. This mean that to get started you just need to run
1133 the wrapper and click the
'Register without mobile phone
' to get going
1134 now. I
've also modified the timeout code to always set it to
90 days
1135 in the future, to avoid having to patch the code regularly.
</p
>
1137 <p
>So, the updated recipe for Debian Jessie:
</p
>
1141 <li
>First, install required packages to get the source code and the
1142 browser you need. Signal only work with Chrome/Chromium, as far as I
1143 know, so you need to install it.
1146 apt install git tor chromium
1147 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1148 </pre
></li
>
1150 <li
>Modify the source code using command listed in the the patch
1151 block below.
</li
>
1153 <li
>Start Signal using the run-signal-app wrapper (for example using
1154 <tt
>`pwd`/run-signal-app
</tt
>).
1156 <li
>Click on the
'Register without mobile phone
', will in a phone
1157 number you can receive calls to the next minute, receive the
1158 verification code and enter it into the form field and press
1159 'Register
'. Note, the phone number you use will be user Signal
1160 username, ie the way others can find you on Signal.
</li
>
1162 <li
>You can now use Signal to contact others. Note, new contacts do
1163 not show up in the contact list until you restart Signal, and there is
1164 no way to assign names to Contacts. There is also no way to create or
1165 update chat groups. I suspect this is because the web app do not have
1166 a associated contact database.
</li
>
1170 <p
>I am still a bit uneasy about using Signal, because of the way its
1171 main author moxie0 reject federation and accept dependencies to major
1172 corporations like Google (part of the code is fetched from Google) and
1173 Amazon (the central coordination point is owned by Amazon). See for
1175 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1176 LibreSignal issue tracker
</a
> for a thread documenting the authors
1177 view on these issues. But the network effect is strong in this case,
1178 and several of the people I want to communicate with already use
1179 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1180 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1181 laptop
</a
>? It already work on Windows and Android, and is included
1182 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1183 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1184 working on Debian Stable.
</p
>
1186 <p
>Anyway, this is the patch I apply to the Signal code to get it
1187 working. It switch to the production servers, disable to timeout,
1188 make registration easier and add the shell wrapper:
</p
>
1191 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1192 diff --git a/js/background.js b/js/background.js
1193 index
24b4c1d.
.579345f
100644
1194 --- a/js/background.js
1195 +++ b/js/background.js
1200 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1201 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1202 var SERVER_PORTS = [
80,
4433,
8443];
1203 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1204 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1205 var messageReceiver;
1206 window.getSocketStatus = function() {
1207 if (messageReceiver) {
1208 diff --git a/js/expire.js b/js/expire.js
1209 index
639aeae..beb91c3
100644
1214 'use strict
';
1215 - var BUILD_EXPIRATION =
0;
1216 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1218 window.extension = window.extension || {};
1220 diff --git a/js/views/install_view.js b/js/views/install_view.js
1221 index
7816f4f.
.1d6233b
100644
1222 --- a/js/views/install_view.js
1223 +++ b/js/views/install_view.js
1226 'click .step1
': this.selectStep.bind(this,
1),
1227 'click .step2
': this.selectStep.bind(this,
2),
1228 -
'click .step3
': this.selectStep.bind(this,
3)
1229 +
'click .step3
': this.selectStep.bind(this,
3),
1230 +
'click .callreg
': function() { extension.install(
'standalone
') },
1233 clearQR: function() {
1234 diff --git a/options.html b/options.html
1235 index dc0f28e.
.8d709f6
100644
1239 &lt;div class=
'nav
'>
1240 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1241 &lt;p
>{{ installTagline }}
&lt;/p
>
1242 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1243 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1244 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1247 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1248 &lt;span class=
'dot step2
'>&lt;/span
>
1249 &lt;span class=
'dot step3
'>&lt;/span
>
1250 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1251 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1257 +userdata=
"`pwd`/userdata
"
1258 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1259 + (cd $userdata
&& git init)
1261 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1263 + --proxy-server=
"socks://localhost:
9050" \
1264 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1266 chmod a+rx run-signal-app
1269 <p
>As usual, if you use Bitcoin and want to show your support of my
1270 activities, please send Bitcoin donations to my address
1271 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1276 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1277 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1278 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1279 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1280 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1281 system
</a
> provide a practical and easy way to figure out which
1282 packages support the hardware in a given machine. The command line
1283 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1284 convenient way to list and install packages relevant for the current
1285 hardware during system installation, both user space packages and
1286 firmware packages. The GUI background daemon on the other hand provide
1287 a pop-up proposing to install packages when a new dongle is inserted
1288 while using the computer. For example, if you plug in a smart card
1289 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1290 that package isn
't already installed, and if you plug in a USB video
1291 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1292 cheese is currently missing. This already work just fine.
</p
>
1294 <p
>But Isenkram depend on a database mapping from hardware IDs to
1295 package names. When I started no such database existed in Debian, so
1296 I made my own data set and included it with the isenkram package and
1297 made isenkram fetch the latest version of this database from git using
1298 http. This way the isenkram users would get updated package proposals
1299 as soon as I learned more about hardware related packages.
</p
>
1301 <p
>The hardware is identified using modalias strings. The modalias
1302 design is from the Linux kernel where most hardware descriptors are
1303 made available as a strings that can be matched using filename style
1304 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1305 identifiers.
</p
>
1307 <p
>The downside to the Isenkram specific database is that there is no
1308 information about relevant distribution / Debian version, making
1309 isenkram propose obsolete packages too. But along came AppStream, a
1310 cross distribution mechanism to store and collect metadata about
1311 software packages. When I heard about the proposal, I contacted the
1312 people involved and suggested to add a hardware matching rule using
1313 modalias strings in the specification, to be able to use AppStream for
1314 mapping hardware to packages. This idea was accepted and AppStream is
1315 now a great way for a package to announce the hardware it support in a
1316 distribution neutral way. I wrote
1317 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1318 recipe on how to add such meta-information
</a
> in a blog post last
1319 December. If you have a hardware related package in Debian, please
1320 announce the relevant hardware IDs using AppStream.
</p
>
1322 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1323 RCX or NXT unit, announce this support using AppStream. The effect is
1324 that when you insert such LEGO robot controller into your Debian
1325 machine, Isenkram will propose to install the packages needed to get
1326 it working. The intention is that this should allow the local user to
1327 start programming his robot controller right away without having to
1328 guess what packages to use or which permissions to fix.
</p
>
1330 <p
>But when I sat down with my son the other day to program our NXT
1331 unit using his Debian Stretch computer, I discovered something
1332 annoying. The local console user (ie my son) did not get access to
1333 the USB device for programming the unit. This used to work, but no
1334 longer in Jessie and Stretch. After some investigation and asking
1335 around on #debian-devel, I discovered that this was because udev had
1336 changed the mechanism used to grant access to local devices. The
1337 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1338 no longer applied, because LDAP users no longer was added to the
1339 plugdev group during login. Michael Biebl told me that this method
1340 was obsolete and the new method used ACLs instead. This was good
1341 news, as the plugdev mechanism is a mess when using a remote user
1342 directory like LDAP. Using ACLs would make sure a user lost device
1343 access when she logged out, even if the user left behind a background
1344 process which would retain the plugdev membership with the ConsoleKit
1345 setup. Armed with this knowledge I moved on to fix the access problem
1346 for the LEGO Mindstorms related packages.
</p
>
1348 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1349 applied directly for a device, or is applied in
1350 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1351 LEGO Mindstorms udev rules did not have a class, I decided to add the
1352 tag directly in the udev rules files included in the packages. Here
1353 is one example. For the nqc C compiler for the RCX, the
1354 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1356 <p
><pre
>
1357 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1358 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1359 </pre
></p
>
1361 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1362 packages using plugdev in their /lib/udev/rules.d/ files should be
1363 changed to use this tag (either directly or indirectly via
1364 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1365 to detect this?
</p
>
1367 <p
>I
've been unable to find good documentation on the uaccess feature.
1368 It is unclear to me if the uaccess tag is an internal implementation
1369 detail like the udev-acl tag used by
1370 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1371 indirect method is the preferred way. Michael
1372 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1373 documentation from the systemd project
</a
> and I hope it will make
1374 this clearer. For now I use the generic classes when they exist and
1375 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1376 directly if no such class exist.
</p
>
1378 <p
>To learn more about the isenkram system, please check out
1379 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1380 blog posts tagged isenkram
</a
>.
</p
>
1382 <p
>To help out making life for LEGO constructors in Debian easier,
1383 please join us on our IRC channel
1384 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1385 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1386 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1387 list is not yet created, but we are working on it. :)
</p
>
1389 <p
>As usual, if you use Bitcoin and want to show your support of my
1390 activities, please send Bitcoin donations to my address
1391 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1396 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1397 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1398 <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>
1399 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1400 <description><p
>In April we
1401 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1402 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1403 how to set up and administrate a Debian system. Today I am happy to
1404 report that the first draft is now publicly available. You can find
1405 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1406 Administrator
's Handbook page
</a
> (under Other languages). The first
1407 eight chapters have a first draft translation, and we are working on
1408 proofreading the content. If you want to help out, please start
1410 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1411 hosted weblate project page
</a
>, and get in touch using
1412 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1413 translators mailing list
</a
>. Please also check out
1414 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1415 contributors
</a
>. A good way to contribute is to proofread the text
1416 and update weblate if you find errors.
</p
>
1418 <p
>Our goal is still to make the Norwegian book available on paper as well as
1419 electronic form.
</p
>
1424 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1425 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1426 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1427 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1428 <description><p
>This summer, I read a great article
1429 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1430 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1431 how to profile multi-threaded programs. It presented a system for
1432 profiling software by running experiences in the running program,
1433 testing how run time performance is affected by
"speeding up
" parts of
1434 the code to various degrees compared to a normal run. It does this by
1435 slowing down parallel threads while the
"faster up
" code is running
1436 and measure how this affect processing time. The processing time is
1437 measured using probes inserted into the code, either using progress
1438 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1439 can also measure unmodified code by measuring complete the program
1440 runtime and running the program several times instead.
</p
>
1442 <p
>The project and presentation was so inspiring that I would like to
1443 get the system into Debian. I
1444 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1445 a WNPP request for it
</a
> and contacted upstream to try to make the
1446 system ready for Debian by sending patches. The build process need to
1447 be changed a bit to avoid running
'git clone
' to get dependencies, and
1448 to include the JavaScript web page used to visualize the collected
1449 profiling information included in the source package.
1450 But I expect that should work out fairly soon.
</p
>
1452 <p
>The way the system work is fairly simple. To run an coz experiment
1453 on a binary with debug symbols available, start the program like this:
1455 <p
><blockquote
><pre
>
1456 coz run --- program-to-run
1457 </pre
></blockquote
></p
>
1459 <p
>This will create a text file profile.coz with the instrumentation
1460 information. To show what part of the code affect the performance
1461 most, use a web browser and either point it to
1462 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1463 or use the copy from git (in the gh-pages branch). Check out this web
1464 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
1465 profiling more useful you include
&lt;coz.h
&gt; and insert the
1466 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1467 code, rebuild and run the profiler. This allow coz to do more
1468 targeted experiments.
</p
>
1470 <p
>A video published by ACM
1471 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1472 Coz profiler
</a
> is available from Youtube. There is also a paper
1473 from the
25th Symposium on Operating Systems Principles available
1475 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1476 finding code that counts with causal profiling
</a
>.
</p
>
1478 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1479 for Coz is available from github. It will only build with clang
1481 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1482 feature missing in GCC
</a
>, but I
've submitted
1483 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1484 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1486 <p
>Please get in touch if you, like me, would like to see this piece
1487 of software in Debian. I would very much like some help with the
1488 packaging effort, as I lack the in depth knowledge on how to package
1489 C++ libraries.
</p
>
1494 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1495 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1496 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1497 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1498 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1499 to be a slight challenge. Here is the recipe if I ever need to do it
1500 again. It all started by me wanting to try the recipe to set up
1501 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1502 hardened Android installation
</a
> from the Tor project blog on a
1503 device I had access to. It is a old mobile phone with a broken
1504 microphone The initial idea had been to just
1505 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1506 CyanogenMod on it
</a
>, but did not quite find time to start on it
1507 until a few days ago.
</p
>
1509 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1510 loader (press volume down and power at the same time), (
2) select
1511 'fastboot
' before (
3) connecting the device via USB to a Linux
1512 machine, (
4) request the device identifier token by running
'fastboot
1513 oem get_identifier_token
', (
5) request the device unlocking key using
1514 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1515 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1517 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1518 or newer, and the device I was working on had
2.00.0027. This
1519 apparently can be easily fixed by downloading a Windows program and
1520 running it on your Windows machine, if you accept the terms Microsoft
1521 require you to accept to use Windows - which I do not. So I had to
1522 come up with a different approach. I got a lot of help from AndyCap
1523 on #nuug, and would not have been able to get this working without
1526 <p
>First I needed to extract the hboot firmware from
1527 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1528 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1529 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1530 project named unruu
</a
> using libunshield. The unshield tool did not
1531 recognise the file format, but unruu worked and extracted rom.zip,
1532 containing the new hboot firmware and a text file describing which
1533 devices it would work for.
</p
>
1535 <p
>Next, I needed to get the new firmware into the device. For this I
1536 followed some instructions
1537 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1538 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1539 machine with Debian testing:
</p
>
1541 <p
><pre
>
1542 adb reboot-bootloader
1543 fastboot oem rebootRUU
1544 fastboot flash zip rom.zip
1545 fastboot flash zip rom.zip
1547 </pre
></p
>
1549 <p
>The flash command apparently need to be done twice to take effect,
1550 as the first is just preparations and the second one do the flashing.
1551 The adb command is just to get to the boot loader menu, so turning the
1552 device on while holding volume down and the power button should work
1555 <p
>With the new hboot version in place I could start following the
1556 instructions on the HTC developer web site. I got the device token
1557 like this:
</p
>
1559 <p
><pre
>
1560 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1563 <p
>And once I got the unlock code via email, I could use it like
1566 <p
><pre
>
1567 fastboot flash unlocktoken Unlock_code.bin
1568 </pre
></p
>
1570 <p
>And with that final step in place, the phone was unlocked and I
1571 could start stuffing the software of my own choosing into the device.
1572 So far I only inserted a replacement recovery image to wipe the phone
1573 before I start. We will see what happen next. Perhaps I should
1574 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1579 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1580 <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>
1581 <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>
1582 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1583 <description><p
>For a while now, I have wanted to test
1584 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1585 said to provide end to end encrypted communication and several of my
1586 friends and family are already using it. As I by choice do not own a
1587 mobile phone, this proved to be harder than expected. And I wanted to
1588 have the source of the client and know that it was the code used on my
1589 machine. But yesterday I managed to get it working. I used the
1590 Github source, compared it to the source in
1591 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1592 Signal Chrome app
</a
> available from the Chrome web store, applied
1593 patches to use the production Signal servers, started the app and
1594 asked for the hidden
"register without a smart phone
" form. Here is
1595 the recipe how I did it.
</p
>
1597 <p
>First, I fetched the Signal desktop source from Github, using
1600 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1603 <p
>Next, I patched the source to use the production servers, to be
1604 able to talk to other Signal users:
</p
>
1607 cat
&lt;
&lt;EOF | patch -p0
1608 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1609 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1610 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1615 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1616 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1617 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1618 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1619 var messageReceiver;
1620 window.getSocketStatus = function() {
1621 if (messageReceiver) {
1622 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1623 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1624 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1627 'use strict
';
1628 - var BUILD_EXPIRATION =
0;
1629 + var BUILD_EXPIRATION =
1474492690000;
1631 window.extension = window.extension || {};
1636 <p
>The first part is changing the servers, and the second is updating
1637 an expiration timestamp. This timestamp need to be updated regularly.
1638 It is set
90 days in the future by the build process (Gruntfile.js).
1639 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1641 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1642 script to launch Signal in Chromium.
</p
>
1649 --proxy-server=
"socks://localhost:
9050" \
1650 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1653 <p
> The script start the app and configure Chromium to use the Tor
1654 SOCKS5 proxy to make sure those controlling the Signal servers (today
1655 Amazon and Whisper Systems) as well as those listening on the lines
1656 will have a harder time location my laptop based on the Signal
1657 connections if they use source IP address.
</p
>
1659 <p
>When the script starts, one need to follow the instructions under
1660 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1661 repository. I right clicked on the Signal window to get up the
1662 Chromium debugging tool, visited the
'Console
' tab and wrote
1663 'extension.install(
"standalone
")
' on the console prompt to get the
1664 registration form. Then I entered by land line phone number and
1665 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1666 repeated the verification code three times. After entering the number
1667 into the verification code field in the form, I could start using
1668 Signal from my laptop.
1670 <p
>As far as I can tell, The Signal app will leak who is talking to
1671 whom and thus who know who to those controlling the central server,
1672 but such leakage is hard to avoid with a centrally controlled server
1673 setup. It is something to keep in mind when using Signal - the
1674 content of your chats are harder to intercept, but the meta data
1675 exposing your contact network is available to people you do not know.
1676 So better than many options, but not great. And sadly the usage is
1677 connected to my land line, thus allowing those controlling the server
1678 to associate it to my home and person. I would prefer it if only
1679 those I knew could tell who I was on Signal. There are options
1680 avoiding such information leakage, but most of my friends are not
1681 using them, so I am stuck with Signal for now.
</p
>
1683 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1685 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1686 and updated recipe for using the Signal app without a mobile
1687 phone
</a
>.
</p
>
1692 <title>The new
"best
" multimedia player in Debian?
</title>
1693 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1694 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1695 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1696 <description><p
>When I set out a few weeks ago to figure out
1697 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1698 multimedia player in Debian claimed to support most file formats /
1699 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1700 the various players claimed support for. The range was from
55 to
130
1701 MIME types. I suspect most media formats are supported by all
1702 players, but this is not really reflected in the MimeTypes values in
1703 their desktop files. There are probably also some bogus MIME types
1704 listed, but it is hard to identify which one this is.
</p
>
1706 <p
>Anyway, in the mean time I got in touch with upstream for some of
1707 the players suggesting to add more MIME types to their desktop files,
1708 and decided to spend some time myself improving the situation for my
1709 favorite media player VLC. The fixes for VLC entered Debian unstable
1710 yesterday. The complete list of MIME types can be seen on the
1711 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1712 player MIME type support status
</a
> Debian wiki page.
</p
>
1714 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1715 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1716 kmplayer. I am sure some of the other players desktop files support
1717 several of the formats currently listed as working only with vlc,
1718 toten and parole.
</p
>
1720 <p
>A sad observation is that only
14 MIME types are listed as
1721 supported by all the tested multimedia players in Debian in their
1722 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1723 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1724 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1725 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1726 it sad that video/ogg and video/webm is not supported by all the media
1727 players in Debian. As far as I can tell, all of them can handle both
1733 <title>A program should be able to open its own files on Linux
</title>
1734 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1735 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1736 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1737 <description><p
>Many years ago, when koffice was fresh and with few users, I
1738 decided to test its presentation tool when making the slides for a
1739 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1740 wrote the first draft of the slides, saved the result and went to bed
1741 the day before I would give the talk. The next day I took a plane to
1742 the location where the meeting should take place, and on the plane I
1743 started up koffice again to polish the talk a bit, only to discover
1744 that kpresenter refused to load its own data file. I cursed a bit and
1745 started making the slides again from memory, to have something to
1746 present when I arrived. I tested that the saved files could be
1747 loaded, and the day seemed to be rescued. I continued to polish the
1748 slides until I suddenly discovered that the saved file could no longer
1749 be loaded into kpresenter. In the end I had to rewrite the slides
1750 three times, condensing the content until the talk became shorter and
1751 shorter. After the talk I was able to pinpoint the problem
&ndash;
1752 kpresenter wrote inline images in a way itself could not understand.
1753 Eventually that bug was fixed and kpresenter ended up being a great
1754 program to make slides. The point I
'm trying to make is that we
1755 expect a program to be able to load its own data files, and it is
1756 embarrassing to its developers if it can
't.
</p
>
1758 <p
>Did you ever experience a program failing to load its own data
1759 files from the desktop file browser? It is not a uncommon problem. A
1760 while back I discovered that the screencast recorder
1761 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1762 browser would refuse to open. No video player claimed to understand
1763 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1764 returning the application/ogg MIME type, which no video player I had
1765 installed listed as a MIME type they would understand. I asked for
1766 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1767 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1768 several video players to add video/ogg to their desktop files, to give
1769 the file browser an idea what to do about Ogg Theora files. After a
1770 while, the desktop file browsers in Debian started to handle the
1771 output from gtk-recordmydesktop properly.
</p
>
1773 <p
>But history repeats itself. A few days ago I tested the music
1774 system Rosegarden again, and I discovered that the KDE and xfce file
1775 browsers did not know what to do with the Rosegarden project files
1776 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1777 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1778 included in the next upload. To increase the chance of me remembering
1779 how to fix the problem next time some program fail to load its files
1780 from the file browser, here are some notes on how to fix it.
</p
>
1782 <p
>The file browsers in Debian in general operates on MIME types.
1783 There are two sources for the MIME type of a given file. The output from
1784 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1785 shared MIME type registry (under /usr/share/mime/). The file MIME
1786 type is mapped to programs supporting the MIME type, and this
1787 information is collected from
1788 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1789 desktop files
</a
> available in /usr/share/applications/. If there is
1790 one desktop file claiming support for the MIME type of the file, it is
1791 activated when asking to open a given file. If there are more, one
1792 can normally select which one to use by right-clicking on the file and
1793 selecting the wanted one using
'Open with
' or similar. In general
1794 this work well. But it depend on each program picking a good MIME
1796 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1797 MIME type registered with IANA
</a
>), file and/or the shared MIME
1798 registry recognizing the file and the desktop file to list the MIME
1799 type in its list of supported MIME types.
</p
>
1801 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1802 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1803 Shared MIME database
</a
> look like this:
</p
>
1805 <p
><blockquote
><pre
>
1806 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1807 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1808 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1809 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1810 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1811 &lt;glob pattern=
"*.rg
"/
&gt;
1812 &lt;/mime-type
&gt;
1813 &lt;/mime-info
&gt;
1814 </pre
></blockquote
></p
>
1816 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1817 (it is a gzipped XML file). Note, it is much better to use an
1818 official MIME type registered with IANA than it is to make up ones own
1819 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1821 <p
>The desktop file of the rosegarden program failed to list
1822 audio/x-rosegarden in its list of supported MIME types, causing the
1823 file browsers to have no idea what to do with *.rg files:
</p
>
1825 <p
><blockquote
><pre
>
1826 % grep Mime /usr/share/applications/rosegarden.desktop
1827 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1828 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1830 </pre
></blockquote
></p
>
1832 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1833 MimeType= line.
</p
>
1835 <p
>If you run into a file which fail to open the correct program when
1836 selected from the file browser, please check out the output from
1837 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1838 MIME type is registered somewhere under /usr/share/mime/ and check
1839 that some desktop file under /usr/share/applications/ is claiming
1840 support for this MIME type. If not, please report a bug to have it
1846 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1847 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1848 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1849 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1850 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1851 system
</a
> is a user-focused solution in Debian for handling hardware
1852 related packages. The idea is to have a database of mappings between
1853 hardware and packages, and pop up a dialog suggesting for the user to
1854 install the packages to use a given hardware dongle. Some use cases
1855 are when you insert a Yubikey, it proposes to install the software
1856 needed to control it; when you insert a braille reader list it
1857 proposes to install the packages needed to send text to the reader;
1858 and when you insert a ColorHug screen calibrator it suggests to
1859 install the driver for it. The system work well, and even have a few
1860 command line tools to install firmware packages and packages for the
1861 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1863 <p
>The system was initially written using aptdaemon, because I found
1864 good documentation and example code on how to use it. But aptdaemon
1865 is going away and is generally being replaced by
1866 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1867 so Isenkram needed a rewrite. And today, thanks to the great patch
1868 from my college Sunil Mohan Adapa in the FreedomBox project, the
1869 rewrite finally took place. I
've just uploaded a new version of
1870 Isenkram into Debian Unstable with the patch included, and the default
1871 for the background daemon is now to use PackageKit. To check it out,
1872 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1873 and see if it is recognised.
</p
>
1875 <p
>If you want to know what kind of packages isenkram would propose for
1876 the machine it is running on, you can check out the isenkram-lookup
1877 program. This is what it look like on a Thinkpad X230:
</p
>
1879 <p
><blockquote
><pre
>
1895 </pre
></blockquote
></p
>
1897 <p
>The hardware mappings come from several places. The preferred way
1898 is for packages to announce their hardware support using
1899 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1900 cross distribution appstream system
</a
>.
1902 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1903 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1908 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1909 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1910 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1911 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1912 <description><p
>Yesterday I updated the
1913 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1914 package in Debian
</a
> with a few patches sent to me by skilled and
1915 enterprising users. There were some nice user and visible changes.
1916 First of all, both desktop menu entries now work. A design flaw in
1917 one of the script made the history graph fail to show up (its PNG was
1918 dumped in ~/.xsession-errors) if no controlling TTY was available.
1919 The script worked when called from the command line, but not when
1920 called from the desktop menu. I changed this to look for a DISPLAY
1921 variable or a TTY before deciding where to draw the graph, and now the
1922 graph window pop up as expected.
</p
>
1924 <p
>The next new feature is a discharge rate estimator in one of the
1925 graphs (the one showing the last few hours). New is also the user of
1926 colours showing charging in blue and discharge in red. The percentages
1927 of this graph is relative to last full charge, not battery design
1930 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1932 <p
>The other graph show the entire history of the collected battery
1933 statistics, comparing it to the design capacity of the battery to
1934 visualise how the battery life time get shorter over time. The red
1935 line in this graph is what the previous graph considers
100 percent:
1937 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1939 <p
>In this graph you can see that I only charge the battery to
80
1940 percent of last full capacity, and how the capacity of the battery is
1941 shrinking. :(
</p
>
1943 <p
>The last new feature is in the collector, which now will handle
1944 more hardware models. On some hardware, Linux power supply
1945 information is stored in /sys/class/power_supply/ACAD/, while the
1946 collector previously only looked in /sys/class/power_supply/AC/. Now
1947 both are checked to figure if there is power connected to the
1950 <p
>If you are interested in how your laptop battery is doing, please
1952 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1953 in Debian unstable, or rebuild it on Jessie to get it working on
1954 Debian stable. :) The upstream source is available from
<a
1955 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1956 Patches are very welcome.
</p
>
1958 <p
>As usual, if you use Bitcoin and want to show your support of my
1959 activities, please send Bitcoin donations to my address
1960 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1965 <title>Debian now with ZFS on Linux included
</title>
1966 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1967 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1968 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1969 <description><p
>Today, after many years of hard work from many people,
1970 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1971 Debian. The package status can be seen on
1972 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1973 for zfs-linux
</a
>. and
1974 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1975 team status page
</a
>. If you want to help out, please join us.
1976 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1977 source code
</a
> is available via git on Alioth. It would also be
1978 great if you could help out with
1979 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1980 it is an important piece of the puzzle to get ZFS working.
</p
>
1985 <title>What is the best multimedia player in Debian?
</title>
1986 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1988 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1989 <description><p
><strong
>Where I set out to figure out which multimedia player in
1990 Debian claim support for most file formats.
</strong
></p
>
1992 <p
>A few years ago, I had a look at the media support for Browser
1993 plugins in Debian, to get an idea which plugins to include in Debian
1994 Edu. I created a script to extract the set of supported MIME types
1995 for each plugin, and used this to find out which multimedia browser
1996 plugin supported most file formats / media types.
1997 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1998 result
</a
> can still be seen on the Debian wiki, even though it have
1999 not been updated for a while. But browser plugins are less relevant
2000 these days, so I thought it was time to look at standalone
2003 <p
>A few days ago I was tired of VLC not being listed as a viable
2004 player when I wanted to play videos from the Norwegian National
2005 Broadcasting Company, and decided to investigate why. The cause is a
2006 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2007 desktop file
</a
>. In the process I wrote a script to compare the set
2008 of MIME types announced in the desktop file and the browser plugin,
2009 only to discover that there is quite a large difference between the
2010 two for VLC. This discovery made me dig up the script I used to
2011 compare browser plugins, and adjust it to compare desktop files
2012 instead, to try to figure out which multimedia player in Debian
2013 support most file formats.
</p
>
2015 <p
>The result can be seen on the Debian Wiki, as
2016 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2017 table listing all MIME types supported by one of the packages included
2018 in the table
</a
>, with the package supporting most MIME types being
2019 listed first in the table.
</p
>
2021 </p
>The best multimedia player in Debian? It is totem, followed by
2022 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2023 kmplayer. Time for the other players to update their announced MIME
2029 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2030 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2031 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2032 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2033 <description>A friend of mine made me aware of
2034 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2035 handheld computer which will be delivered with Debian preinstalled. I
2036 would love to get one of those for my birthday. :)
</p
>
2038 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2039 plugs and many others connectors, and include a full keyboard and a
5"
2040 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2041 day of battery life time, but I have not seen any independent tests
2042 confirming this. The vendor is still collecting preorders, and the
2043 last I heard last night was that
22 more orders were needed before
2044 production started.
</p
>
2046 <p
>As far as I know, this is the first handheld preinstalled with
2047 Debian. Please let me know if you know of any others. Is it the
2048 first computer being sold with Debian preinstalled?
</p
>
2053 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2054 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2055 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2056 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2057 <description><p
>During this weekends
2058 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2059 squashing party and developer gathering
</a
>, we decided to do our part
2060 to make sure there are good books about Debian available in Norwegian
2061 Bokmål, and got in touch with the people behind the
2062 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2063 project
</a
> to get started. If you want to help out, please start
2065 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2066 hosted weblate project page
</a
>, and get in touch using
2067 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2068 translators mailing list
</a
>. Please also check out
2069 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2070 contributors
</a
>.
</p
>
2072 <p
>The book is already available on paper in English, French and
2073 Japanese, and our goal is to get it available on paper in Norwegian
2074 Bokmål too. In addition to the paper edition, there are also EPUB and
2075 Mobi versions available. And there are incomplete translations
2076 available for many more languages.
</p
>
2081 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2082 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2083 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2084 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2085 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2086 packages in Debian, and was quite surprised with what I found. I use
2087 ZFS myself at home, but did not really expect many others to do so.
2088 But I might be wrong.
</p
>
2090 <p
>According to
2091 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2092 results for spl-linux
</a
>, there are
1019 Debian installations, or
2093 0.53% of the population, with the package installed. As far as I know
2094 the only use of the spl-linux package is as a support library for ZFS
2095 on Linux, so I use it here as proxy for measuring the number of ZFS
2096 installation on Linux in Debian. In the kFreeBSD variant of Debian
2097 the ZFS feature is already available, and there
2098 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2099 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2100 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2102 <p
>But even though the Debian project leader Lucas Nussbaum
2103 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2104 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2105 cleared, the package is still not in Debian. The package is again in
2106 the NEW queue. Several uploads have been rejected so far because the
2107 debian/copyright file was incomplete or wrong, but there is no reason
2108 to give up. The current status can be seen on
2109 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2110 team status page
</a
>, and
2111 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2112 source code
</a
> is available on Alioth.
</p
>
2114 <p
>As I want ZFS to be included in next version of Debian to make sure
2115 my home server can function in the future using only official Debian
2116 packages, and the current blocker is to get the debian/copyright file
2117 accepted by the FTP masters in Debian, I decided a while back to try
2118 to help out the team. This was the background for my blog post about
2119 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2120 updating and checking debian/copyright semi-automatically
</a
>, and I
2121 used the techniques I explored there to try to find any errors in the
2122 copyright file. It is not very easy to check every one of the around
2123 2000 files in the source package, but I hope we this time got it
2124 right. If you want to help out, check out the git source and try to
2125 find missing entries in the debian/copyright file.
</p
>
2130 <title>Full battery stats collector is now available in Debian
</title>
2131 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2132 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2133 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2134 <description><p
>Since this morning, the battery-stats package in Debian include an
2135 extended collector that will collect the complete battery history for
2136 later processing and graphing. The original collector store the
2137 battery level as percentage of last full level, while the new
2138 collector also record battery vendor, model, serial number, design
2139 full level, last full level and current battery level. This make it
2140 possible to predict the lifetime of the battery as well as visualise
2141 the energy flow when the battery is charging or discharging.
</p
>
2143 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2144 in the version
0.5.1 package in unstable. Get the new battery level graph
2145 and lifetime prediction by running:
2147 <p
><pre
>
2148 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2149 </pre
></p
>
2151 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2153 <p
>The flow in/out of the battery can be seen by running (no menu
2154 entry yet):
</p
>
2156 <p
><pre
>
2157 /usr/share/battery-stats/battery-stats-graph-flow
2158 </pre
></p
>
2160 <p
>I
'm not quite happy with the way the data is visualised, at least
2161 when there are few data points. The graphs look a bit better with a
2162 few years of data.
</p
>
2164 <p
>A while back one important feature I use in the battery stats
2165 collector broke in Debian. The scripts in
2166 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2167 suspect it happened when Jessie started using systemd, but I do not
2168 know. The issue is reported as
2169 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2170 pm-utils. I managed to work around it by adding an udev rule to call
2171 the collector script every time the power connector is connected and
2172 disconnected. With this fix in place it was finally time to make a
2173 new release of the package, and get it into Debian.
</p
>
2175 <p
>If you are interested in how your laptop battery is doing, please
2177 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2178 in Debian unstable, or rebuild it on Jessie to get it working on
2179 Debian stable. :) The upstream source is available from
2180 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2181 As always, patches are very welcome.
</p
>
2186 <title>Making battery measurements a little easier in Debian
</title>
2187 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2188 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2189 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2190 <description><p
>Back in September, I blogged about
2191 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2192 system I wrote to collect statistics about my laptop battery
</a
>, and
2193 how it showed the decay and death of this battery (now replaced). I
2194 created a simple deb package to handle the collection and graphing,
2195 but did not want to upload it to Debian as there were already
2196 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2197 package in Debian
</a
> that should do the same thing, and I did not see
2198 a point of uploading a competing package when battery-stats could be
2199 fixed instead. I reported a few bugs about its non-function, and
2200 hoped someone would step in and fix it. But no-one did.
</p
>
2202 <p
>I got tired of waiting a few days ago, and took matters in my own
2203 hands. The end result is that I am now the new upstream developer of
2204 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2205 battery-stats in Debian, and the package in Debian unstable is finally
2206 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2207 information provided by the Linux kernel. If you install the
2208 battery-stats package from unstable now, you will be able to get a
2209 graph of the current battery fill level, to get some idea about the
2210 status of the battery. The source package build and work just fine in
2211 Debian testing and stable (and probably oldstable too, but I have not
2212 tested). The default graph you get for that system look like this:
</p
>
2214 <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
>
2216 <p
>My plans for the future is to merge my old scripts into the
2217 battery-stats package, as my old scripts collected a lot more details
2218 about the battery. The scripts are merged into the upstream
2219 battery-stats git repository already, but I am not convinced they work
2220 yet, as I changed a lot of paths along the way. Will have to test a
2221 bit more before I make a new release.
</p
>
2223 <p
>I will also consider changing the file format slightly, as I
2224 suspect the way I combine several values into one field might make it
2225 impossible to know the type of the value when using it for processing
2226 and graphing.
</p
>
2228 <p
>If you would like I would like to keep an close eye on your laptop
2229 battery, check out the battery-stats package in
2230 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2232 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2233 I would love some help to improve the system further.
</p
>
2238 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2239 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2240 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2241 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2242 <description><p
>Making packages for Debian requires quite a lot of attention to
2243 details. And one of the details is the content of the
2244 debian/copyright file, which should list all relevant licenses used by
2245 the code in the package in question, preferably in
2246 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2247 readable DEP5 format
</a
>.
</p
>
2249 <p
>For large packages with lots of contributors it is hard to write
2250 and update this file manually, and if you get some detail wrong, the
2251 package is normally rejected by the ftpmasters. So getting it right
2252 the first time around get the package into Debian faster, and save
2253 both you and the ftpmasters some work.. Today, while trying to figure
2254 out what was wrong with
2255 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2256 zfsonlinux copyright file
</a
>, I decided to spend some time on
2257 figuring out the options for doing this job automatically, or at least
2258 semi-automatically.
</p
>
2260 <p
>Lucikly, there are at least two tools available for generating the
2261 file based on the code in the source package,
2262 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2263 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2264 not sure which one of them came first, but both seem to be able to
2265 create a sensible draft file. As far as I can tell, none of them can
2266 be trusted to get the result just right, so the content need to be
2267 polished a bit before the file is OK to upload. I found the debmake
2269 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2270 blog posts from
2014</a
>.
2272 <p
>To generate using debmake, use the -cc option:
2274 <p
><pre
>
2275 debmake -cc
> debian/copyright
2276 </pre
></p
>
2278 <p
>Note there are some problems with python and non-ASCII names, so
2279 this might not be the best option.
</p
>
2281 <p
>The cme option is based on a config parsing library, and I found
2283 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2284 blog post from
2015</a
>. To generate using cme, use the
'update
2285 dpkg-copyright
' option:
2287 <p
><pre
>
2288 cme update dpkg-copyright
2289 </pre
></p
>
2291 <p
>This will create or update debian/copyright. The cme tool seem to
2292 handle UTF-
8 names better than debmake.
</p
>
2294 <p
>When the copyright file is created, I would also like some help to
2295 check if the file is correct. For this I found two good options,
2296 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2297 to focus on license types and file matching, and is able to detect
2298 ineffective blocks in the copyright file. The latter reports missing
2299 copyright holders and years, but was confused by inconsistent license
2300 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2301 fix all issues reported by them before uploading. But I do not know
2302 if the tools and the ftpmasters agree on what is important to fix in a
2303 copyright file, so the package might still be rejected.
</p
>
2305 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2306 will read through the source and try to find all copyright statements.
2307 It is not comparing the result to the content of debian/copyright, but
2308 can be useful when verifying the content of the copyright file.
</p
>
2310 <p
>Are you aware of better tools in Debian to create and update
2311 debian/copyright file. Please let me know, or blog about it on
2312 planet.debian.org.
</p
>
2314 <p
>As usual, if you use Bitcoin and want to show your support of my
2315 activities, please send Bitcoin donations to my address
2316 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2318 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2319 on how to use licensecheck and cdbs to create a draft copyright file
2321 <p
><pre
>
2322 licensecheck --copyright -r `find * -type f` | \
2323 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2324 </pre
></p
>
2326 <p
>He mentioned that he normally check the generated file into the
2327 version control system to make it easier to discover license and
2328 copyright changes in the upstream source. I will try to do the same
2329 with my packages in the future.
</p
>
2331 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2332 against using -quiet for new users, so I removed it from the proposed
2333 command line.
</p
>
2338 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2339 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2340 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2341 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2342 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2343 is taking shape in Debian, and one provided feature is a very
2344 convenient way to tell you which package to install to make a given
2345 firmware file available when the kernel is looking for it. This can
2346 be done using apt-file too, but that is for someone else to blog
2349 <p
>Here is a small recipe to find the package with a given firmware
2350 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2351 picked from the set of firmware announced using appstream in Debian
2352 unstable. In general you would be looking for the firmware requested
2353 by the kernel during kernel module loading. To find the package
2354 providing the example file, do like this:
</p
>
2356 <blockquote
><pre
>
2357 % apt install appstream
2361 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2362 awk
'/Package:/ {print $
2}
'
2365 </pre
></blockquote
>
2367 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2368 appstream wiki
</a
> page to learn how to embed the package metadata in
2369 a way appstream can use.
</p
>
2371 <p
>This same approach can be used to find any package supporting a
2372 given MIME type. This is very useful when you get a file you do not
2373 know how to handle. First find the mime type using
<tt
>file
2374 --mime-type
</tt
>, and next look up the package providing support for
2375 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2376 and you can find all packages handling this type like this:
</p
>
2378 <blockquote
><pre
>
2379 % apt install appstream
2383 % appstreamcli what-provides mimetype image/svg+xml | \
2384 awk
'/Package:/ {print $
2}
'
2406 </pre
></blockquote
>
2408 <p
>I believe the MIME types are fetched from the desktop file for
2409 packages providing appstream metadata.
</p
>
2414 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2415 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2416 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2417 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2418 <description><p
>Most people seem not to realise that every time they walk around
2419 with the computerised radio beacon known as a mobile phone their
2420 position is tracked by the phone company and often stored for a long
2421 time (like every time a SMS is received or sent). And if their
2422 computerised radio beacon is capable of running programs (often called
2423 mobile apps) downloaded from the Internet, these programs are often
2424 also capable of tracking their location (if the app requested access
2425 during installation). And when these programs send out information to
2426 central collection points, the location is often included, unless
2427 extra care is taken to not send the location. The provided
2428 information is used by several entities, for good and bad (what is
2429 good and bad, depend on your point of view). What is certain, is that
2430 the private sphere and the right to free movement is challenged and
2431 perhaps even eradicated for those announcing their location this way,
2432 when they share their whereabouts with private and public
2435 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2437 <p
>The phone company logs provide a register of locations to check out
2438 when one want to figure out what the tracked person was doing. It is
2439 unavailable for most of us, but provided to selected government
2440 officials, company staff, those illegally buying information from
2441 unfaithful servants and crackers stealing the information. But the
2442 public information can be collected and analysed, and a free software
2443 tool to do so is called
2444 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2445 discovered it when I read
2446 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2447 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2448 November
2014, and decided to check if it was available in Debian.
2449 The python program was in Debian, but
2450 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2451 Debian
</a
> was completely broken and practically unmaintained. I
2452 uploaded a new version which did not work quite right, but did not
2453 have time to fix it then. This Christmas I decided to finally try to
2454 get Creepy operational in Debian. Now a fixed version is available in
2455 Debian unstable and testing, and almost all Debian specific patches
2457 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2459 <p
>The Creepy program visualises geolocation information fetched from
2460 Twitter, Instagram, Flickr and Google+, and allow one to get a
2461 complete picture of every social media message posted recently in a
2462 given area, or track the movement of a given individual across all
2463 these services. Earlier it was possible to use the search API of at
2464 least some of these services without identifying oneself, but these
2465 days it is impossible. This mean that to use Creepy, you need to
2466 configure it to log in as yourself on these services, and provide
2467 information to them about your search interests. This should be taken
2468 into account when using Creepy, as it will also share information
2469 about yourself with the services.
</p
>
2471 <p
>The picture above show the twitter messages sent from (or at least
2472 geotagged with a position from) the city centre of Oslo, the capital
2473 of Norway. One useful way to use Creepy is to first look at
2474 information tagged with an area of interest, and next look at all the
2475 information provided by one or more individuals who was in the area.
2476 I tested it by checking out which celebrity provide their location in
2477 twitter messages by checkout out who sent twitter messages near a
2478 Norwegian TV station, and next could track their position over time,
2479 making it possible to locate their home and work place, among other
2480 things. A similar technique have been
2481 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2482 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2483 tool to discover lying governments, and a useful tool to help people
2484 understand the value of the private information they provide to the
2487 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2488 it depend on several python modules currently missing in Jessie (at
2489 least python-instagram, python-flickrapi and
2490 python-requests-toolbelt).
</p
>
2492 <p
>(I have uploaded
2493 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2494 screenshots.debian.net
</a
> and licensed it under the same terms as the
2495 Creepy program in Debian.)
</p
>
2500 <title>Always download Debian packages using Tor - the simple recipe
</title>
2501 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2502 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2503 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2504 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2505 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2506 that those listening on the Internet lines would have good reason to
2507 believe a computer have a given security hole
</a
> if it download a
2508 security fix from a Debian mirror. This is a good reason to always
2509 use encrypted connections to the Debian mirror, to make sure those
2510 listening do not know which IP address to attack. In August, Richard
2511 Hartmann observed that encryption was not enough, when it was possible
2512 to interfere download size to security patches or the fact that
2513 download took place shortly after a security fix was released, and
2514 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2515 to always use Tor to download packages from the Debian mirror
</a
>. He
2516 was not the first to propose this, as the
2517 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2518 package by Tim Retout already existed to make it easy to convince apt
2519 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2520 aware of that package when I read the blog post from Richard.
</p
>
2522 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2523 sysadmins, and he set up a Tor hidden service on one of the central
2524 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2525 it possible to download packages directly between two tor nodes,
2526 making sure the network traffic always were encrypted.
</p
>
2528 <p
>Here is a short recipe for enabling this on your machine, by
2529 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2530 urls with tor+http and tor+https, and using the hidden service instead
2531 of the official Debian mirror site. I recommend installing
2532 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2533 done in /etc/.
</p
>
2535 <blockquote
><pre
>
2536 apt install apt-transport-tor
2537 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2538 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2539 </pre
></blockquote
>
2541 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2542 the sed commands for these too. The sed command is assuming your are
2543 using the ftp.debian.org Debian mirror. Adjust the command (or just
2544 edit the file manually) to match your mirror.
</p
>
2546 <p
>This work in Debian Jessie and later. Note that tools like
2547 <tt
>apt-file
</tt
> only recently started using the apt transport
2548 system, and do not work with these tor+http URLs. For
2549 <tt
>apt-file
</tt
> you need the version currently in experimental,
2550 which need a recent apt version currently only in unstable. So if you
2551 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2553 <p
>Another advantage from this change is that your machine will start
2554 using Tor regularly and at fairly random intervals (every time you
2555 update the package lists or upgrade or install a new package), thus
2556 masking other Tor traffic done from the same machine. Using Tor will
2557 become normal for the machine in question.
</p
>
2559 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2560 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2561 enabled. It would be great if it was the default on any Debian
2567 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2568 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2569 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2570 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2571 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2572 call the car license plate numbers in those days. I would write the
2573 numbers down in my little book and compare notes with the other kids
2574 to see how many region codes we had seen and if we had seen some
2575 exotic or special region codes and numbers. It was a fun game to pass
2576 time, as we kids have plenty of it.
</p
>
2578 <p
>A few days I came across
2579 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2580 project
</a
>, a free software project to automatically discover and
2581 report license plates in images and video streams, and provide the
2582 "car numbers
" in a machine readable format. I
've been looking for
2583 such system for a while now, because I believe it is a bad idea that the
2584 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2585 number plate recognition
</a
> tool only is available in the hands of
2586 the powerful, and want it to be available also for the powerless to
2587 even the score when it comes to surveillance and sousveillance. I
2588 discovered the developer
2589 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2590 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2591 help him get it into shape to get the package uploaded into the Debian
2594 <p
>Today we finally managed to get the package into shape and uploaded
2595 it into Debian, where it currently
2596 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2597 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2599 <p
>I guess you are wondering why on earth such tool would be useful
2600 for the common folks, ie those not running a large government
2601 surveillance system? Well, I plan to put it in a computer on my bike
2602 and in my car, tracking the cars nearby and allowing me to be notified
2603 when number plates on my watch list are discovered. Another use case
2604 was suggested by a friend of mine, who wanted to set it up at his home
2605 to open the car port automatically when it discovered the plate on his
2606 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2607 capable of placing his license plate number of a piece of cardboard to
2608 open his car port, men replied that it was always unlocked anyway. I
2609 guess for such use case it make sense. I am sure there are other use
2610 cases too, for those with imagination and a vision.
</p
>
2612 <p
>If you want to build your own version of the Debian package, check
2613 out the upstream git source and symlink ./distros/debian to ./debian/
2614 before running
"debuild
" to build the source. Or wait a bit until the
2615 package show up in unstable.
</p
>
2620 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2621 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2622 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2623 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2624 <description><p
>Around three years ago, I created
2625 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2626 system
</a
> to get a more practical solution in Debian for handing
2627 hardware related packages. A GUI system in the isenkram package will
2628 present a pop-up dialog when some hardware dongle supported by
2629 relevant packages in Debian is inserted into the machine. The same
2630 lookup mechanism to detect packages is available as command line
2631 tools in the isenkram-cli package. In addition to mapping hardware,
2632 it will also map kernel firmware files to packages and make it easy to
2633 install needed firmware packages automatically. The key for this
2634 system to work is a good way to map hardware to packages, in other
2635 words, allow packages to announce what hardware they will work
2638 <p
>I started by providing data files in the isenkram source, and
2639 adding code to download the latest version of these data files at run
2640 time, to ensure every user had the most up to date mapping available.
2641 I also added support for storing the mapping in the Packages file in
2642 the apt repositories, but did not push this approach because while I
2643 was trying to figure out how to best store hardware/package mappings,
2644 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2645 appstream system
</a
> was announced. I got in touch and suggested to
2646 add the hardware mapping into that data set to be able to use
2647 appstream as a data source, and this was accepted at least for the
2648 Debian version of appstream.
</p
>
2650 <p
>A few days ago using appstream in Debian for this became possible,
2651 and today I uploaded a new version
0.20 of isenkram adding support for
2652 appstream as a data source for mapping hardware to packages. The only
2653 package so far using appstream to announce its hardware support is my
2654 pymissile package. I got help from Matthias Klumpp with figuring out
2655 how do add the required
2656 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2657 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2658 this content:
</p
>
2660 <blockquote
><pre
>
2661 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2662 &lt;component
&gt;
2663 &lt;id
&gt;pymissile
&lt;/id
&gt;
2664 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2665 &lt;name
&gt;pymissile
&lt;/name
&gt;
2666 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2667 &lt;description
&gt;
2669 Pymissile provides a curses interface to control an original
2670 Marks and Spencer / Striker USB Missile Launcher, as well as a
2671 motion control script to allow a webcamera to control the
2674 &lt;/description
&gt;
2675 &lt;provides
&gt;
2676 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2677 &lt;/provides
&gt;
2678 &lt;/component
&gt;
2679 </pre
></blockquote
>
2681 <p
>The key for isenkram is the component/provides/modalias value,
2682 which is a glob style match rule for hardware specific strings
2683 (modalias strings) provided by the Linux kernel. In this case, it
2684 will map to all USB devices with vendor code
1130 and product code
2687 <p
>Note, it is important that the license of all the metadata files
2688 are compatible to have permissions to aggregate them into archive wide
2689 appstream files. Matthias suggested to use MIT or BSD licenses for
2690 these files. A challenge is figuring out a good id for the data, as
2691 it is supposed to be globally unique and shared across distributions
2692 (in other words, best to coordinate with upstream what to use). But
2693 it can be changed later or, so we went with the package name as
2694 upstream for this project is dormant.
</p
>
2696 <p
>To get the metadata file installed in the correct location for the
2697 mirror update scripts to pick it up and include its content the
2698 appstream data source, the file must be installed in the binary
2699 package under /usr/share/appdata/. I did this by adding the following
2700 line to debian/pymissile.install:
</p
>
2702 <blockquote
><pre
>
2703 debian/pymissile.metainfo.xml usr/share/appdata
2704 </pre
></blockquote
>
2706 <p
>With that in place, the command line tool isenkram-lookup will list
2707 all packages useful on the current computer automatically, and the GUI
2708 pop-up handler will propose to install the package not already
2709 installed if a hardware dongle is inserted into the machine in
2712 <p
>Details of the modalias field in appstream is available from the
2713 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2715 <p
>To locate the modalias values of all hardware present in a machine,
2716 try running this command on the command line:
</p
>
2718 <blockquote
><pre
>
2719 cat $(find /sys/devices/|grep modalias)
2720 </pre
></blockquote
>
2722 <p
>To learn more about the isenkram system, please check out
2723 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2724 blog posts tagged isenkram
</a
>.
</p
>
2729 <title>The GNU General Public License is not magic pixie dust
</title>
2730 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2731 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2732 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2733 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2734 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2735 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2736 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2737 I quote the blog post from Paul in full here with his permission:
<p
>
2741 <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
>
2744 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2746 The first step is to choose a
2747 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2750 The next step is, when someone fails to follow that copyleft license,
2751 <b
>it must be enforced
</b
><br/
>
2753 and its a simple fact of our modern society that such type of
2756 is incredibly expensive to do and incredibly difficult to do.
2759 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2760 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2761 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2762 0x57</a
></small
></p
>
2764 <p
>As the Debian Website
2765 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2766 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2767 imply, public domain and permissively licensed software can lead to
2768 the production of more proprietary software as people discover useful
2769 software, extend it and or incorporate it into their hardware or
2770 software products. Copyleft licenses such as the GNU GPL were created
2771 to close off this avenue to the production of proprietary software but
2772 such licenses are not enough. With the ongoing adoption of Free
2773 Software by individuals and groups, inevitably the community
's
2774 expectations of license compliance are violated, usually out of
2775 ignorance of the way Free Software works, but not always. As Karen
2776 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2777 Freedom
">FaiF
</a
>
2778 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2779 copyleft is nothing if no-one is willing and able to stand up in court
2780 to protect it. The reality of today
's world is that legal
2781 representation is expensive, difficult and time consuming. With
2782 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2783 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2784 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2785 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2786 of the Linux project, Debian and other groups against GPL violations.
2787 In March the SFC supported a
2788 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2789 by Christoph Hellwig
</a
> against VMware for refusing to
2790 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2791 with the GPL
</a
> in relation to their use of parts of the Linux
2792 kernel. Since then two of their sponsors pulled corporate funding and
2794 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2795 or cancelled their talks
</a
>. As a result they have decided to rely
2796 less on corporate funding and more on the broad community of
2797 individuals who support Free Software and copyleft. So the SFC has
2798 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2799 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2800 a community of folks who stand up for copyleft and the GPL by
2801 supporting their work on promoting and supporting copyleft and Free
2804 <p
>If you support Free Software,
2805 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2806 what the SFC do, agree with their
2807 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2808 principles
</a
>, are happy about their
2809 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2810 work on a project that is an SFC
2811 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2812 just want to stand up for copyleft, please join
2813 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2814 Allan Webber
</a
>,
2815 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2817 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2818 Bacon
</a
>, myself and
2819 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2821 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2822 next week your donation will be
2823 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2824 by an anonymous donor. Please also consider asking your employer to
2825 match your donation or become a sponsor of SFC. Don
't forget to
2826 spread the word about your support for SFC via email, your blog and or
2827 social media accounts.
</p
>
2831 <p
>I agree with Paul on this topic and just signed up as a Supporter
2832 of Software Freedom Conservancy myself. Perhaps you should be a
2833 supporter too?
</p
>
2838 <title>PGP key transition statement for key EE4E02F9
</title>
2839 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2840 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2841 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2842 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2843 set it up properly. I wanted to generate it offline and have it
2844 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2845 smart card
</a
> for daily use, and learning how to do it and finding
2846 time to sit down with an offline machine almost took forever. But
2847 finally I
've been able to complete the process, and have now moved
2848 from my old GPG key to a new GPG key. See
2849 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2850 full transition statement, signed with both my old and new key
</a
> for
2851 the details. This is my new key:
</p
>
2854 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2855 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2856 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2857 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2858 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2859 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2860 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2863 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2864 my old key.
</p
>
2866 <p
>If you signed my old key
2867 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2868 I
'd very much appreciate a signature on my new key, details and
2869 instructions in the transition statement. I m happy to reciprocate if
2870 you have a similarly signed transition statement to present.
</p
>
2875 <title>The life and death of a laptop battery
</title>
2876 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2878 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2879 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2880 But this do not last. The last few laptops gave me a feeling that
2881 within a year, the life time is just a fraction of what it used to be,
2882 and it slowly become painful to use the laptop without power connected
2883 all the time. Because of this, when I got a new Thinkpad X230 laptop
2884 about two years ago, I decided to monitor its battery state to have
2885 more hard facts when the battery started to fail.
</p
>
2887 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2889 <p
>First I tried to find a sensible Debian package to record the
2890 battery status, assuming that this must be a problem already handled
2891 by someone else. I found
2892 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2893 which collects statistics from the battery, but it was completely
2894 broken. I sent a few suggestions to the maintainer, but decided to
2895 write my own collector as a shell script while I waited for feedback
2897 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2898 blog post about the battery development on a MacBook Air
</a
> I also
2900 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2901 available in Debian.
</p
>
2903 <p
>I started my collector
2013-
07-
15, and it has been collecting
2904 battery stats ever since. Now my
2905 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2906 measurements, from the time the battery was working great until now,
2907 when it is unable to charge above
7% of original capacity. My
2908 collector shell script is quite simple and look like this:
</p
>
2913 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2915 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2916 logfile=/var/log/hjemmenett-battery-status.log
2918 files=
"manufacturer model_name technology serial_number \
2919 energy_full energy_full_design energy_now cycle_count status
"
2921 if [ ! -e
"$logfile
" ] ; then
2923 printf
"timestamp,
"
2925 printf
"%s,
" $f
2928 )
> "$logfile
"
2932 # Print complete message in one echo call, to avoid race condition
2933 # when several log processes run in parallel.
2934 msg=$(printf
"%s,
" $(date +%s); \
2935 for f in $files; do \
2936 printf
"%s,
" $(cat $f); \
2938 echo
"$msg
"
2941 cd /sys/class/power_supply
2944 (cd $bat
&& log_battery
>> "$logfile
")
2948 <p
>The script is called when the power management system detect a
2949 change in the power status (power plug in or out), and when going into
2950 and out of hibernation and suspend. In addition, it collect a value
2951 every
10 minutes. This make it possible for me know when the battery
2952 is discharging, charging and how the maximum charge change over time.
2953 The code for the Debian package
2954 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2955 available on github
</a
>.
</p
>
2957 <p
>The collected log file look like this:
</p
>
2960 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2961 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2963 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2964 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2967 <p
>I wrote a small script to create a graph of the charge development
2968 over time. This graph depicted above show the slow death of my laptop
2971 <p
>But why is this happening? Why are my laptop batteries always
2972 dying in a year or two, while the batteries of space probes and
2973 satellites keep working year after year. If we are to believe
2974 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2975 University
</a
>, the cause is me charging the battery whenever I have a
2976 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2977 all the time, but to stay below
90% of full charge most of the time.
2978 I
've been told that the Tesla electric cars
2979 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2980 the charge of their batteries to
80%
</a
>, with the option to charge to
2981 100% when preparing for a longer trip (not that I would want a car
2982 like Tesla where rights to privacy is abandoned, but that is another
2983 story), which I guess is the option we should have for laptops on
2984 Linux too.
</p
>
2986 <p
>Is there a good and generic way with Linux to tell the battery to
2987 stop charging at
80%, unless requested to charge to
100% once in
2988 preparation for a longer trip? I found
2989 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2990 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2991 80%
</a
>, but could not get it to work (kernel module refused to
2994 <p
>I wonder why the battery capacity was reported to be more than
100%
2995 at the start. I also wonder why the
"full capacity
" increases some
2996 times, and if it is possible to repeat the process to get the battery
2997 back to design capacity. And I wonder if the discharge and charge
2998 speed change over time, or if this stay the same. I did not yet try
2999 to write a tool to calculate the derivative values of the battery
3000 level, but suspect some interesting insights might be learned from
3003 <p
>Update
2015-
09-
24: I got a tip to install the packages
3004 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3005 packages instead of the tp-smapi-dkms package I had tried to use
3006 initially, and use
'tlp setcharge
40 80' to change when charging start
3007 and stop. I
've done so now, but expect my existing battery is toast
3008 and need to be replaced. The proposal is unfortunately Thinkpad
3014 <title>New laptop - some more clues and ideas based on feedback
</title>
3015 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3016 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3017 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3018 <description><p
>Several people contacted me after my previous blog post about my
3019 need for a new laptop, and provided very useful feedback. I wish to
3020 thank every one of these. Several pointed me to the possibility of
3021 fixing my X230, and I am already in the process of getting Lenovo to
3022 do so thanks to the on site, next day support contract covering the
3023 machine. But the battery is almost useless (I expect to replace it
3024 with a non-official battery) and I do not expect the machine to live
3025 for many more years, so it is time to plan its replacement. If I did
3026 not have a support contract, it was suggested to find replacement parts
3027 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3028 might present a language barrier as I do not understand French.
</p
>
3030 <p
>One tip I got was to use the
3031 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3032 compare laptop models. It seem to have more models available than
3033 prisjakt.no. Another tip I got from someone I know have similar
3034 keyboard preferences was that the HP EliteBook
840 keyboard is not
3035 very good, and this matches my experience with earlier EliteBook
3036 keyboards I tested. Because of this, I will not consider it any further.
3038 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3039 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3040 (which is missing from the X240), and is working fairly well with
3041 Debian Sid/Unstable according to
3042 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3043 got on the keyboard quality are not consistent. Some say the keyboard
3044 is good, others say it is ok, while others say it is not very good.
3045 Those with experience from X41 and and X60 agree that the X250
3046 keyboard is not as good as those trusty old laptops, and suggest I
3047 keep and fix my X230 instead of upgrading, or get a used X230 to
3048 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3049 activity and battery status, which is very convenient on my X230. I
'm
3050 also told that the CPU fan is running very often, making it a bit
3051 noisy. In any case, the X250 do not work out of the box with Debian
3052 Stable/Jessie, one of my requirements.
</p
>
3054 <p
>I have also gotten a few vendor proposals, one was
3055 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3056 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3057 The latter look very attractive to me.
</p
>
3059 <p
>Again, thank you all for the very useful feedback. It help a lot
3060 as I keep looking for a replacement.
</p
>
3062 <p
>Update
2015-
07-
06: I was recommended to check out the
3063 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3065 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3066 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3071 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3072 <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>
3073 <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>
3074 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3075 <description><p
>My primary work horse laptop is failing, and will need a
3076 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3077 started flickering yesterday, and I suspect the cause is a broken
3078 cable, as changing the angle of the screen some times get rid of the
3079 flickering.
</p
>
3081 <p
>My requirements have not really changed since I bought it, and is
3083 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3084 described them in
2013</a
>. The last time I bought a laptop, I had
3086 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3087 where I could select at least a few of the requirements (mouse pin,
3088 wifi, weight) and go through the rest manually. Three button mouse
3089 and a good keyboard is not available as an option, and all the three
3090 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3091 G2) lack three mouse buttons). It is also unclear to me how good the
3092 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3093 the keyboard, even if the quality and robustness in the X series have
3094 deteriorated since X41.
</p
>
3096 <p
>I wonder how I can find a sensible laptop when none of the options
3097 seem sensible to me? Are there better services around to search the
3098 set of available laptops for features? Please send me an email if you
3099 have suggestions.
</p
>
3101 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3102 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3103 of endorsed hardware
</a
>, which is useful background information.
</p
>
3108 <title>How to stay with sysvinit in Debian Jessie
</title>
3109 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3110 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3111 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3112 <description><p
>By now, it is well known that Debian Jessie will not be using
3113 sysvinit as its boot system by default. But how can one keep using
3114 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3116 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3117 Schubert
</a
> and
3118 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3121 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3122 keep sysvinit as your boot system, create a file
3123 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3124 you upgrade:
</p
>
3126 <p
><blockquote
><pre
>
3127 Package: systemd-sysv
3128 Pin: release o=Debian
3130 </pre
></blockquote
><p
>
3132 <p
>This file content will tell apt and aptitude to not consider
3133 installing systemd-sysv as part of any installation and upgrade
3134 solution when resolving dependencies, and thus tell it to avoid
3135 systemd as a default boot system. The end result should be that the
3136 upgraded system keep using sysvinit.
</p
>
3138 <p
>If you are installing Jessie for the first time, there is no way to
3139 get sysvinit installed by default (debootstrap used by
3140 debian-installer have no option for this), but one can tell the
3141 installer to switch to sysvinit before the first boot. Either by
3142 using a kernel argument to the installer, or by adding a line to the
3143 preseed file used. First, the kernel command line argument:
3145 <p
><blockquote
><pre
>
3146 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3147 </pre
></blockquote
><p
>
3149 <p
>Next, the line to use in a preseed file:
</p
>
3151 <p
><blockquote
><pre
>
3152 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3153 </pre
></blockquote
><p
>
3155 <p
>One can of course also do this after the first boot by installing
3156 the sysvinit-core package.
</p
>
3158 <p
>I recommend only using sysvinit if you really need it, as the
3159 sysvinit boot sequence in Debian have several hardware specific bugs
3160 on Linux caused by the fact that it is unpredictable when hardware
3161 devices show up during boot. But on the other hand, the new default
3162 boot system still have a few rough edges I hope will be fixed before
3163 Jessie is released.
</p
>
3165 <p
>Update
2014-
11-
26: Inspired by
3166 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3167 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3173 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3174 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3175 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3176 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3177 <description><p
>The right to communicate with your friends and family in private,
3178 without anyone snooping, is a right every citicen have in a liberal
3179 democracy. But this right is under serious attack these days.
</p
>
3181 <p
>A while back it occurred to me that one way to make the dragnet
3182 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3183 the whisleblower Snowden) more expensive for Internet email,
3184 is to deliver all email using SMTP via Tor. Such SMTP option would be
3185 a nice addition to the FreedomBox project if we could send email
3186 between FreedomBox machines without leaking metadata about the emails
3187 to the people peeking on the wire. I
3188 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3189 this on the FreedomBox project mailing list in October
</a
> and got a
3190 lot of useful feedback and suggestions. It also became obvious to me
3191 that this was not a novel idea, as the same idea was tested and
3192 documented by Johannes Berg as early as
2006, and both
3193 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3194 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3195 propose a similar method / protocol to pass emails between users.
</p
>
3197 <p
>To implement such system one need to set up a Tor hidden service
3198 providing the SMTP protocol on port
25, and use email addresses
3199 looking like username@hidden-service-name.onion. With such addresses
3200 the connections to port
25 on hidden-service-name.onion using Tor will
3201 go to the correct SMTP server. To do this, one need to configure the
3202 Tor daemon to provide the hidden service and the mail server to accept
3203 emails for this .onion domain. To learn more about Exim configuration
3204 in Debian and test the design provided by Johannes Berg in his FAQ, I
3205 set out yesterday to create a Debian package for making it trivial to
3206 set up such SMTP over Tor service based on Debian. Getting it to work
3207 were fairly easy, and
3208 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3209 source code for the Debian package
</a
> is available from github. I
3210 plan to move it into Debian if further testing prove this to be a
3211 useful approach.
</p
>
3213 <p
>If you want to test this, set up a blank Debian machine without any
3214 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3215 get rid of exim4). Install tor, clone the git repository mentioned
3216 above, build the deb and install it on the machine. Next, run
3217 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3218 the instructions to get the service up and running. Restart tor and
3219 exim when it is done, and test mail delivery using swaks like
3222 <p
><blockquote
><pre
>
3223 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3224 --to fbx@dutlqrrmjhtfa3vp.onion
3225 </pre
></blockquote
></p
>
3227 <p
>This will test the SMTP delivery using tor. Replace the email
3228 address with your own address to test your server. :)
</p
>
3230 <p
>The setup procedure is still to complex, and I hope it can be made
3231 easier and more automatic. Especially the tor setup need more work.
3232 Also, the package include a tor-smtp tool written in C, but its task
3233 should probably be rewritten in some script language to make the deb
3234 architecture independent. It would probably also make the code easier
3235 to review. The tor-smtp tool currently need to listen on a socket for
3236 exim to talk to it and is started using xinetd. It would be better if
3237 no daemon and no socket is needed. I suspect it is possible to get
3238 exim to run a command line tool for delivery instead of talking to a
3239 socket, and hope to figure out how in a future version of this
3242 <p
>Until I wipe my test machine, I can be reached using the
3243 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3244 SMTorP. :)
</p
>
3249 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3250 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3251 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3252 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3253 <description><p
>If you ever had to moderate a mailman list, like the ones on
3254 alioth.debian.org, you know the web interface is fairly slow to
3255 operate. First you visit one web page, enter the moderation password
3256 and get a new page shown with a list of all the messages to moderate
3257 and various options for each email address. This take a while for
3258 every list you moderate, and you need to do it regularly to do a good
3259 job as a list moderator. But there is a quick alternative,
3260 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3261 listadmin program
</a
>. It allow you to check lists for new messages
3262 to moderate in a fraction of a second. Here is a test run on two
3263 lists I recently took over:
</p
>
3265 <p
><blockquote
><pre
>
3266 % time listadmin xiph
3267 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3268 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3274 </pre
></blockquote
></p
>
3276 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3277 there are no message in the moderation queue. Every morning I
3278 currently moderate
68 mailman lists, and it normally take around two
3279 minutes. When I took over the two pkg-xiph lists above a few days
3280 ago, there were
400 emails waiting in the moderator queue. It took me
3281 less than
15 minutes to process them all using the listadmin
3284 <p
>If you install
3285 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3286 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3287 with content like this, the moderation task is a breeze:
</p
>
3289 <p
><blockquote
><pre
>
3290 username username@example.org
3293 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3296 adminurl https://{domain}/mailman/admindb/{list}
3297 mailman-list@lists.example.com
3300 other-list@otherserver.example.org
3301 </pre
></blockquote
></p
>
3303 <p
>There are other options to set as well. Check the manual page to
3304 learn the details.
</p
>
3306 <p
>If you are forced to moderate lists on a mailman installation where
3307 the SSL certificate is self signed or not properly signed by a
3308 generally accepted signing authority, you can set a environment
3309 variable when calling listadmin to disable SSL verification:
</p
>
3311 <p
><blockquote
><pre
>
3312 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3313 </pre
></blockquote
></p
>
3315 <p
>If you want to moderate a subset of the lists you take care of, you
3316 can provide an argument to the listadmin script like I do in the
3317 initial screen dump (the xiph argument). Using an argument, only
3318 lists matching the argument string will be processed. This make it
3319 quick to accept messages if you notice the moderation request in your
3322 <p
>Without the listadmin program, I would never be the moderator of
68
3323 mailing lists, as I simply do not have time to spend on that if the
3324 process was any slower. The listadmin program have saved me hours of
3325 time I could spend elsewhere over the years. It truly is nice free
3328 <p
>As usual, if you use Bitcoin and want to show your support of my
3329 activities, please send Bitcoin donations to my address
3330 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3332 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3333 configuration example. Also, I
've been told that the
3334 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3340 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3341 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3342 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3343 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3344 <description><p
>When PXE installing laptops with Debian, I often run into the
3345 problem that the WiFi card require some firmware to work properly.
3346 And it has been a pain to fix this using preseeding in Debian.
3347 Normally something more is needed. But thanks to
3348 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3349 package
</a
> and its recent tasksel extension, it has now become easy
3350 to do this using simple preseeding.
</p
>
3352 <p
>The isenkram-cli package provide tasksel tasks which will install
3353 firmware for the hardware found in the machine (actually, requested by
3354 the kernel modules for the hardware). (It can also install user space
3355 programs supporting the hardware detected, but that is not the focus
3356 of this story.)
</p
>
3358 <p
>To get this working in the default installation, two preeseding
3359 values are needed. First, the isenkram-cli package must be installed
3360 into the target chroot (aka the hard drive) before tasksel is executed
3361 in the pkgsel step of the debian-installer system. This is done by
3362 preseeding the base-installer/includes debconf value to include the
3363 isenkram-cli package. The package name is next passed to debootstrap
3364 for installation. With the isenkram-cli package in place, tasksel
3365 will automatically use the isenkram tasks to detect hardware specific
3366 packages for the machine being installed and install them, because
3367 isenkram-cli contain tasksel tasks.
</p
>
3369 <p
>Second, one need to enable the non-free APT repository, because
3370 most firmware unfortunately is non-free. This is done by preseeding
3371 the apt-mirror-setup step. This is unfortunate, but for a lot of
3372 hardware it is the only option in Debian.
</p
>
3374 <p
>The end result is two lines needed in your preseeding file to get
3375 firmware installed automatically by the installer:
</p
>
3377 <p
><blockquote
><pre
>
3378 base-installer base-installer/includes string isenkram-cli
3379 apt-mirror-setup apt-setup/non-free boolean true
3380 </pre
></blockquote
></p
>
3382 <p
>The current version of isenkram-cli in testing/jessie will install
3383 both firmware and user space packages when using this method. It also
3384 do not work well, so use version
0.15 or later. Installing both
3385 firmware and user space packages might give you a bit more than you
3386 want, so I decided to split the tasksel task in two, one for firmware
3387 and one for user space programs. The firmware task is enabled by
3388 default, while the one for user space programs is not. This split is
3389 implemented in the package currently in unstable.
</p
>
3391 <p
>If you decide to give this a go, please let me know (via email) how
3392 this recipe work for you. :)
</p
>
3394 <p
>So, I bet you are wondering, how can this work. First and
3395 foremost, it work because tasksel is modular, and driven by whatever
3396 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3397 isenkram-cli package place two files for tasksel to find. First there
3398 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3400 <p
><blockquote
><pre
>
3401 Task: isenkram-packages
3403 Description: Hardware specific packages (autodetected by isenkram)
3404 Based on the detected hardware various hardware specific packages are
3406 Test-new-install: show show
3408 Packages: for-current-hardware
3410 Task: isenkram-firmware
3412 Description: Hardware specific firmware packages (autodetected by isenkram)
3413 Based on the detected hardware various hardware specific firmware
3414 packages are proposed.
3415 Test-new-install: mark show
3417 Packages: for-current-hardware-firmware
3418 </pre
></blockquote
></p
>
3420 <p
>The key parts are Test-new-install which indicate how the task
3421 should be handled and the Packages line referencing to a script in
3422 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3423 list of packages to install. The for-current-hardware-firmware script
3424 look like this to list relevant firmware for the machine:
3426 <p
><blockquote
><pre
>
3429 PATH=/usr/sbin:$PATH
3431 isenkram-autoinstall-firmware -l
3432 </pre
></blockquote
></p
>
3434 <p
>With those two pieces in place, the firmware is installed by
3435 tasksel during the normal d-i run. :)
</p
>
3437 <p
>If you want to test what tasksel will install when isenkram-cli is
3438 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3439 --new-install
</tt
> to get the list of packages that tasksel would
3442 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3443 pilots in testing this feature, as isenkram is used there now to
3444 install firmware, replacing the earlier scripts.
</p
>
3449 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3450 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3451 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3452 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3453 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3454 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3455 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3456 on a screen normally showing the bread types and prizes:
</p
>
3458 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3460 <p
>If it had booted as it was supposed to, I would never had known
3461 about this hidden Linux installation. It is interesting what
3462 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3467 <title>New lsdvd release version
0.17 is ready
</title>
3468 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3469 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3470 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3471 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3472 got a new set of developers a few weeks ago, after the original
3473 developer decided to step down and pass the project to fresh blood.
3474 This project is now maintained by Petter Reinholdtsen and Steve
3477 <p
>I just wrapped up
3478 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3479 new lsdvd release
</a
>, available in git or from
3480 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3481 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3486 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3487 <li
>Check for garbage in the program chains, which indicate that a track is
3488 non-existant, to work around additional copy protection
</li
>
3489 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3490 <li
>Fix pallete display of first entry
</li
>
3491 <li
>Fix include orders
</li
>
3492 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3493 <li
>Fix the chapter count
</li
>
3494 <li
>Make sure the array size and the array limit used when initialising
3495 the palette size is the same.
</li
>
3496 <li
>Fix array printing.
</li
>
3497 <li
>Correct subsecond calculations.
</li
>
3498 <li
>Add sector information to the output format.
</li
>
3499 <li
>Clean up code to be closer to ANSI C and compile without warnings
3500 with more GCC compiler warnings.
</li
>
3504 <p
>This change bring together patches for lsdvd in use in various
3505 Linux and Unix distributions, as well as patches submitted to the
3506 project the last nine years. Please check it out. :)
</p
>
3511 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3512 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3514 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3515 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3516 project
</a
> provide a Linux solution for schools, including a
3517 powerful desktop with education software, a central server providing
3518 web pages, user database, user home directories, central login and PXE
3519 boot of both clients without disk and the installation to install Debian
3520 Edu on machines with disk (and a few other services perhaps to small
3521 to mention here). We in the Debian Edu team are currently working on
3522 the Jessie based version, trying to get everything in shape before the
3523 freeze, to avoid having to maintain our own package repository in the
3525 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3526 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3527 work left. Some fatal problems block testing, breaking the installer,
3528 but it is possible to work around these to get anyway. Here is a
3529 recipe on how to get the installation limping along.
</p
>
3531 <p
>First, download the test ISO via
3532 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3533 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3535 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3536 The ISO build was broken on Tuesday, so we do not get a new ISO every
3537 12 hours or so, but thankfully the ISO we already got we are able to
3538 install with some tweaking.
</p
>
3540 <p
>When you get to the Debian Edu profile question, go to tty2
3541 (use Alt-Ctrl-F2), run
</p
>
3543 <p
><blockquote
><pre
>
3544 nano /usr/bin/edu-eatmydata-install
3545 </pre
></blockquote
></p
>
3547 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3548 optimization. Return to the installation, select the profile you want
3549 and continue. Without this change, exim4-config will fail to install
3550 due to a known bug in eatmydata.
</p
>
3552 <p
>When you get the grub question at the end, answer /dev/sda (or if
3553 this do not work, figure out what your correct value would be. All my
3554 test machines need /dev/sda, so I have no advice if it do not fit
3555 your need.
</p
>
3557 <p
>If you installed a profile including a graphical desktop, log in as
3558 root after the initial boot from hard drive, and install the
3559 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3560 or mate. If you want several desktop options, install more than one
3561 metapackage. Once this is done, reboot and you should have a working
3562 graphical login screen. This workaround should no longer be needed
3563 once the education-tasks package version
1.801 enter testing in two
3566 <p
>I believe the ISO build will start working on two days when the new
3567 tasksel package enter testing and Steve McIntyre get a chance to
3568 update the debian-cd git repository. The eatmydata, grub and desktop
3569 issues are already fixed in unstable and testing, and should show up
3570 on the ISO as soon as the ISO build start working again. Well the
3571 eatmydata optimization is really just disabled. The proper fix
3572 require an upload by the eatmydata maintainer applying the patch
3573 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3574 The rest have proper fixes in unstable.
</p
>
3576 <p
>I hope this get you going with the installation testing, as we are
3577 quickly running out of time trying to get our Jessie based
3578 installation ready before the distribution freeze in a month.
</p
>
3583 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3584 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3585 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3586 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3587 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3588 to handle my fairly large DVD collection. It is a nice command line
3589 tool to get details about a DVD, like title, tracks, track length,
3590 etc, in XML, Perl or human readable format. But lsdvd have not seen
3591 any new development since
2006 and had a few irritating bugs affecting
3592 its use with some DVDs. Upstream seemed to be dead, and in January I
3593 sent a small probe asking for a version control repository for the
3594 project, without any reply. But I use it regularly and would like to
3595 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3596 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3597 the project admin, and after getting a reply from him explaining that
3598 he was no longer interested in the project, I asked if I could take
3599 over. And yesterday, I became project admin.
</p
>
3601 <p
>I
've been in touch with a Gentoo developer and the Debian
3602 maintainer interested in joining forces to maintain the upstream
3603 project, and I hope we can get a new release out fairly quickly,
3604 collecting the patches spread around on the internet into on place.
3605 I
've added the relevant Debian patches to the freshly created git
3606 repository, and expect the Gentoo patches to make it too. If you got
3607 a DVD collection and care about command line tools, check out
3608 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3609 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3610 list
</a
>. :)
</p
>
3615 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3616 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3618 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3619 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3620 a lot quicker. When we install more than
2000 packages in
3621 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3622 tasksel in the installer, unpacking the binary packages take forever.
3623 A part of the slow I/O issue was discussed in
3624 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3625 much file system sync-ing done by dpkg, which is the package
3626 responsible for unpacking the binary packages. Other parts (like code
3627 executed by postinst scripts) might also sync to disk during
3628 installation. All this sync-ing to disk do not really make sense to
3629 me. If the machine crash half-way through, I start over, I do not try
3630 to salvage the half installed system. So the failure sync-ing is
3631 supposed to protect against, hardware or system crash, is not really
3632 relevant while the installer is running.
</p
>
3634 <p
>A few days ago, I thought of a way to get rid of all the file
3635 system sync()-ing in a fairly non-intrusive way, without the need to
3636 change the code in several packages. The idea is not new, but I have
3637 not heard anyone propose the approach using dpkg-divert before. It
3638 depend on the small and clever package
3639 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3640 uses LD_PRELOAD to replace the system functions for syncing data to
3641 disk with functions doing nothing, thus allowing programs to live
3642 dangerous while speeding up disk I/O significantly. Instead of
3643 modifying the implementation of dpkg, apt and tasksel (which are the
3644 packages responsible for selecting, fetching and installing packages),
3645 it occurred to me that we could just divert the programs away, replace
3646 them with a simple shell wrapper calling
3647 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3648 Two days ago I decided to test the idea, and wrapped up a simple
3649 implementation for the Debian Edu udeb.
</p
>
3651 <p
>The effect was stunning. In my first test it reduced the running
3652 time of the pkgsel step (installing tasks) from
64 to less than
44
3653 minutes (
20 minutes shaved off the installation) on an old Dell
3654 Latitude D505 machine. I am not quite sure what the optimised time
3655 would have been, as I messed up the testing a bit, causing the debconf
3656 priority to get low enough for two questions to pop up during
3657 installation. As soon as I saw the questions I moved the installation
3658 along, but do not know how long the question were holding up the
3659 installation. I did some more measurements using Debian Edu Jessie,
3660 and got these results. The time measured is the time stamp in
3661 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3662 "pkgsel: finishing up
" lines, if you want to do the same measurement
3663 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3664 timing thus do not depend on how quickly the user handle the tasksel
3667 <p
><table
>
3670 <th
>Machine/setup
</th
>
3671 <th
>Original tasksel
</th
>
3672 <th
>Optimised tasksel
</th
>
3673 <th
>Reduction
</th
>
3677 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3678 <td
>64 min (
07:
46-
08:
50)
</td
>
3679 <td
><44 min (
11:
27-
12:
11)
</td
>
3680 <td
>>20 min
18%
</td
>
3684 <td
>Latitude D505 Roaming LXDE
</td
>
3685 <td
>57 min (
08:
48-
09:
45)
</td
>
3686 <td
>34 min (
07:
43-
08:
17)
</td
>
3687 <td
>23 min
40%
</td
>
3691 <td
>Latitude D505 Minimal
</td
>
3692 <td
>22 min (
10:
37-
10:
59)
</td
>
3693 <td
>11 min (
11:
16-
11:
27)
</td
>
3694 <td
>11 min
50%
</td
>
3698 <td
>Thinkpad X200 Minimal
</td
>
3699 <td
>6 min (
08:
19-
08:
25)
</td
>
3700 <td
>4 min (
08:
04-
08:
08)
</td
>
3701 <td
>2 min
33%
</td
>
3705 <td
>Thinkpad X200 Roaming KDE
</td
>
3706 <td
>19 min (
09:
21-
09:
40)
</td
>
3707 <td
>15 min (
10:
25-
10:
40)
</td
>
3708 <td
>4 min
21%
</td
>
3711 </table
></p
>
3713 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3714 time is spent downloading packages. The connection to the Internet
3715 was
100Mbit/s during testing, so downloading should not be a
3716 significant factor in the measurement. Download typically took a few
3717 seconds to a few minutes, depending on the amount of packages being
3718 installed.
</p
>
3720 <p
>The speedup is implemented by using two hooks in
3721 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3722 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3723 finish-install.d hook to remove the divert at the end of the
3724 installation. I picked the pre-pkgsel.d hook instead of the
3725 post-base-installer.d hook because I test using an ISO without the
3726 eatmydata package included, and the post-base-installer.d hook in
3727 Debian Edu can only operate on packages included in the ISO. The
3728 negative effect of this is that I am unable to activate this
3729 optimization for the kernel installation step in d-i. If the code is
3730 moved to the post-base-installer.d hook, the speedup would be larger
3731 for the entire installation.
</p
>
3733 <p
>I
've implemented this in the
3734 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3735 git repository, and plan to provide the optimization as part of the
3736 Debian Edu installation. If you want to test this yourself, you can
3737 create two files in the installer (or in an udeb). One shell script
3738 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3740 <p
><blockquote
><pre
>
3743 . /usr/share/debconf/confmodule
3745 logger -t my-pkgsel
"info: $*
"
3748 logger -t my-pkgsel
"error: $*
"
3750 override_install() {
3751 apt-install eatmydata || true
3752 if [ -x /target/usr/bin/eatmydata ] ; then
3753 for bin in dpkg apt-get aptitude tasksel ; do
3755 # Test that the file exist and have not been diverted already.
3756 if [ -f /target$file ] ; then
3757 info
"diverting $file using eatmydata
"
3758 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3759 > /target$file.edu
3760 chmod
755 /target$file.edu
3761 in-target dpkg-divert --package debian-edu-config \
3762 --rename --quiet --add $file
3763 ln -sf ./$bin.edu /target$file
3765 error
"unable to divert $file, as it is missing.
"
3769 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3774 </pre
></blockquote
></p
>
3776 <p
>To clean up, another shell script should go into
3777 /usr/lib/finish-install.d/ with code like this:
3779 <p
><blockquote
><pre
>
3781 . /usr/share/debconf/confmodule
3783 logger -t my-finish-install
"error: $@
"
3785 remove_install_override() {
3786 for bin in dpkg apt-get aptitude tasksel ; do
3788 if [ -x /target$file.edu ] ; then
3790 in-target dpkg-divert --package debian-edu-config \
3791 --rename --quiet --remove $file
3794 error
"Missing divert for $file.
"
3797 sync # Flush file buffers before continuing
3800 remove_install_override
3801 </pre
></blockquote
></p
>
3803 <p
>In Debian Edu, I placed both code fragments in a separate script
3804 edu-eatmydata-install and call it from the pre-pkgsel.d and
3805 finish-install.d scripts.
</p
>
3807 <p
>By now you might ask if this change should get into the normal
3808 Debian installer too? I suspect it should, but am not sure the
3809 current debian-installer coordinators find it useful enough. It also
3810 depend on the side effects of the change. I
'm not aware of any, but I
3811 guess we will see if the change is safe after some more testing.
3812 Perhaps there is some package in Debian depending on sync() and
3813 fsync() having effect? Perhaps it should go into its own udeb, to
3814 allow those of us wanting to enable it to do so without affecting
3817 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3818 will break installation of all programs using gnutls because of
3819 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3820 eatmydata package in Debian will solve it.
</p
>
3822 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3823 the optimization work again. And I have discovered that the
3824 dpkg-divert trick is not really needed and implemented a slightly
3825 simpler approach as part of the debian-edu-install package. See
3826 tools/edu-eatmydata-install in the source package.
</p
>
3828 <p
>Update
2014-
11-
11: Unfortunately, a new
3829 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3830 triggering on i386 made it into testing, and broke this installation
3831 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3832 request
768893</a
> is accepted, it should be working again.
</p
>
3837 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3838 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3839 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3840 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3841 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3842 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3843 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3844 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3845 learn that there is a large set of publicly available key servers to
3846 use when looking for peoples public key. So far I have used
3847 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3848 were misbehaving, but those days are ended. The servers I have used
3849 up until yesterday have been slow and some times unavailable. I hope
3850 those problems are gone now.
</p
>
3852 <p
>Behind the round robin DNS entry of the
3853 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3854 there is a pool of more than
100 keyservers which are checked every
3855 day to ensure they are well connected and up to date. It must be
3856 better than what I have used so far. :)
</p
>
3858 <p
>Yesterdays speaker told me that the service is the default
3859 keyserver provided by the default configuration in GnuPG, but this do
3860 not seem to be used in Debian. Perhaps it should?
</p
>
3862 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3865 <p
><blockquote
><pre
>
3866 keyserver pool.sks-keyservers.net
3867 </pre
></blockquote
></p
>
3869 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3870 entries in DNS. Just for fun, I did just that at work, so now every
3871 user of GnuPG at the University of Oslo should find a OpenGPG
3872 keyserver automatically should their need it:
</p
>
3874 <p
><blockquote
><pre
>
3875 % host -t srv _pgpkey-http._tcp.uio.no
3876 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3878 </pre
></blockquote
></p
>
3880 <p
>Now if only
3881 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3882 HKP lookup protocol
</a
> supported finding signature paths, I would be
3883 very happy. It can look up a given key or search for a user ID, but I
3884 normally do not want that, but to find a trust path from my key to
3885 another key. Given a user ID or key ID, I would like to find (and
3886 download) the keys representing a signature path from my key to the
3887 key in question, to be able to get a trust path between the two keys.
3888 This is as far as I can tell not possible today. Perhaps something
3889 for a future version of the protocol?
</p
>
3894 <title>From English wiki to translated PDF and epub via Docbook
</title>
3895 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3896 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3897 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3898 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3899 project
</a
> provide an instruction manual for teachers, system
3900 administrators and other users that contain useful tips for setting up
3901 and maintaining a Debian Edu installation. This text is about how the
3902 text processing of this manual is handled in the project.
</p
>
3904 <p
>One goal of the project is to provide information in the native
3905 language of its users, and for this we need to handle translations.
3906 But we also want to make sure each language contain the same
3907 information, so for this we need a good way to keep the translations
3908 in sync. And we want it to be easy for our users to improve the
3909 documentation, avoiding the need to learn special formats or tools to
3910 contribute, and the obvious way to do this is to make it possible to
3911 edit the documentation using a web browser. We also want it to be
3912 easy for translators to keep the translation up to date, and give them
3913 help in figuring out what need to be translated. Here is the list of
3914 tools and the process we have found trying to reach all these
3917 <p
>We maintain the authoritative source of our manual in the
3918 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3919 wiki
</a
>, as several wiki pages written in English. It consist of one
3920 front page with references to the different chapters, several pages
3921 for each chapter, and finally one
"collection page
" gluing all the
3922 chapters together into one large web page (aka
3923 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3924 AllInOne page
</a
>). The AllInOne page is the one used for further
3925 processing and translations. Thanks to the fact that the
3926 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3927 wiki.debian.org support exporting pages in
3928 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3929 the list of pages to export using the raw version of the AllInOne
3930 page, loop over each of them to generate a Docbook XML version of the
3931 manual. This process also download images and transform image
3932 references to use the locally downloaded images. The generated
3933 Docbook XML files are slightly broken, so some post-processing is done
3934 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3935 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3936 a handfull of images. The XML file can now be used to generate PDF, HTML
3937 and epub versions of the English manual. This is the basic step of
3938 our process, making PDF (using dblatex), HTML (using xsltproc) and
3939 epub (using dbtoepub) version from Docbook XML, and the resulting files
3940 are placed in the debian-edu-doc-en binary package.
</p
>
3942 <p
>But English documentation is not enough for us. We want translated
3943 documentation too, and we want to make it easy for translators to
3944 track the English original. For this we use the
3945 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3946 which allow us to transform the English Docbook XML file into a
3947 translation file (a .pot file), usable with the normal gettext based
3948 translation tools used by those translating free software. The pot
3949 file is used to create and maintain translation files (several .po
3950 files), which the translations update with the native language
3951 translations of all titles, paragraphs and blocks of text in the
3952 original. The next step is combining the original English Docbook XML
3953 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3954 create a translated Docbook XML file (in this case
3955 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3956 translated, if the translation is not complete) Docbook XML file can
3957 then be used like the original to create a PDF, HTML and epub version
3958 of the documentation.
</p
>
3960 <p
>The translators use different tools to edit the .po files. We
3962 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3963 while some use emacs and vi, others can use web based editors like
3964 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3965 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3966 is where the .po file end up, in our git repository. Updated
3967 translations can either be committed directly to git, or submitted as
3968 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3969 against the debian-edu-doc package
</a
>.
</p
>
3971 <p
>One challenge is images, which both might need to be translated (if
3972 they show translated user applications), and are needed in different
3973 formats when creating PDF and HTML versions (epub is a HTML version in
3974 this regard). For this we transform the original PNG images to the
3975 needed density and format during build, and have a way to provide
3976 translated images by storing translated versions in
3977 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3978 package maintainers know more.
</p
>
3980 <p
>If you wonder what the result look like, we provide
3981 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3982 of the documentation packages on the web
</a
>. See for example the
3983 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3984 PDF version
</a
> or the
3985 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3986 HTML version
</a
>. We do not yet build the epub version by default,
3987 but perhaps it will be done in the future.
</p
>
3989 <p
>To learn more, check out
3990 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3991 debian-edu-doc package
</a
>,
3992 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3993 manual on the wiki
</a
> and
3994 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3995 translation instructions
</a
> in the manual.
</p
>
4000 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4001 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4002 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4003 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4004 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4005 related packages relevant for the computer installed automatically.
4006 So I implemented one, using
4007 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4008 package
</a
>. To use it, install the tasksel and isenkram packages and
4009 run tasksel as user root. You should be presented with a new option,
4010 "Hardware specific packages (autodetected by isenkram)
". When you
4011 select it, tasksel will install the packages isenkram claim is fit for
4012 the current hardware, hot pluggable or not.
<p
>
4014 <p
>The implementation is in two files, one is the tasksel menu entry
4015 description, and the other is the script used to extract the list of
4016 packages to install. The first part is in
4017 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4020 <p
><blockquote
><pre
>
4023 Description: Hardware specific packages (autodetected by isenkram)
4024 Based on the detected hardware various hardware specific packages are
4026 Test-new-install: mark show
4028 Packages: for-current-hardware
4029 </pre
></blockquote
></p
>
4031 <p
>The second part is in
4032 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4035 <p
><blockquote
><pre
>
4040 isenkram-autoinstall-firmware -l
4042 </pre
></blockquote
></p
>
4044 <p
>All in all, a very short and simple implementation making it
4045 trivial to install the hardware dependent package we all may want to
4046 have installed on our machines. I
've not been able to find a way to
4047 get tasksel to tell you exactly which packages it plan to install
4048 before doing the installation. So if you are curious or careful,
4049 check the output from the isenkram-* command line tools first.
</p
>
4051 <p
>The information about which packages are handling which hardware is
4052 fetched either from the isenkram package itself in
4053 /usr/share/isenkram/, from git.debian.org or from the APT package
4054 database (using the Modaliases header). The APT package database
4055 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4056 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4057 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4058 the python-apt code (bug
4059 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4060 workaround I was able to get rid of the file descriptor leak and
4061 reduce the memory leak from ~
30 MiB per hardware detection down to
4062 around
2 MiB per hardware detection. It should make the desktop
4063 daemon a lot more useful. The fix is in version
0.7 uploaded to
4064 unstable today.
</p
>
4066 <p
>I believe the current way of mapping hardware to packages in
4067 Isenkram is is a good draft, but in the future I expect isenkram to
4068 use the AppStream data source for this. A proposal for getting proper
4069 AppStream support into Debian is floating around as
4070 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4071 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4072 project
</a
> will take place this summer to improve the situation. I
4073 look forward to seeing the result, and welcome patches for isenkram to
4074 start using the information when it is ready.
</p
>
4076 <p
>If you want your package to map to some specific hardware, either
4077 add a
"Xb-Modaliases
" header to your control file like I did in
4078 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4079 package
</a
> or submit a bug report with the details to the isenkram
4081 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4082 blog posts tagged isenkram
</a
> for details on the notation. I expect
4083 the information will be migrated to AppStream eventually, but for the
4084 moment I got no better place to store it.
</p
>
4089 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4090 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4091 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4092 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4093 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4094 project
</a
> is working on providing the software and hardware to make
4095 it easy for non-technical people to host their data and communication
4096 at home, and being able to communicate with their friends and family
4097 encrypted and away from prying eyes. It is still going strong, and
4098 today a major mile stone was reached.
</p
>
4100 <p
>Today, the last of the packages currently used by the project to
4101 created the system images were accepted into Debian Unstable. It was
4102 the freedombox-setup package, which is used to configure the images
4103 during build and on the first boot. Now all one need to get going is
4104 the build code from the freedom-maker git repository and packages from
4105 Debian. And once the freedombox-setup package enter testing, we can
4106 build everything directly from Debian. :)
</p
>
4108 <p
>Some key packages used by Freedombox are
4109 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4110 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4111 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4112 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4113 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4114 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4115 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4116 are plans to integrate more packages into the setup. User
4117 documentation is maintained on the Debian wiki. Please
4118 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4119 the manual
</a
> and help us improve it.
</p
>
4121 <p
>To test for yourself and create boot images with the FreedomBox
4122 setup, run this on a Debian machine using a user with sudo rights to
4123 become root:
</p
>
4125 <p
><pre
>
4126 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4127 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4129 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4131 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4132 </pre
></p
>
4134 <p
>Root access is needed to run debootstrap and mount loopback
4135 devices. See the README in the freedom-maker git repo for more
4136 details on the build. If you do not want all three images, trim the
4137 make line. Note that the virtualbox-image target is not really
4138 virtualbox specific. It create a x86 image usable in kvm, qemu,
4139 vmware and any other x86 virtual machine environment. You might need
4140 the version of vmdebootstrap in Jessie to get the build working, as it
4141 include fixes for a race condition with kpartx.
</p
>
4143 <p
>If you instead want to install using a Debian CD and the preseed
4144 method, boot a Debian Wheezy ISO and use this boot argument to load
4145 the preseed values:
</p
>
4147 <p
><pre
>
4148 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4149 </pre
></p
>
4151 <p
>I have not tested it myself the last few weeks, so I do not know if
4152 it still work.
</p
>
4154 <p
>If you wonder how to help, one task you could look at is using
4155 systemd as the boot system. It will become the default for Linux in
4156 Jessie, so we need to make sure it is usable on the Freedombox. I did
4157 a simple test a few weeks ago, and noticed dnsmasq failed to start
4158 during boot when using systemd. I suspect there are other problems
4159 too. :) To detect problems, there is a test suite included, which can
4160 be run from the plinth web interface.
</p
>
4162 <p
>Give it a go and let us know how it goes on the mailing list, and help
4163 us get the new release published. :) Please join us on
4164 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4165 irc.debian.org)
</a
> and
4166 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4167 mailing list
</a
> if you want to help make this vision come true.
</p
>
4172 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4173 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4174 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4175 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4176 <description><p
>For a while now, I have been looking for a sensible offsite backup
4177 solution for use at home. My requirements are simple, it must be
4178 cheap and locally encrypted (in other words, I keep the encryption
4179 keys, the storage provider do not have access to my private files).
4180 One idea me and my friends had many years ago, before the cloud
4181 storage providers showed up, was to use Google mail as storage,
4182 writing a Linux block device storing blocks as emails in the mail
4183 service provided by Google, and thus get heaps of free space. On top
4184 of this one can add encryption, RAID and volume management to have
4185 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4186 I never found time to implement such system. But the last few weeks I
4187 have looked at a system called
4188 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4189 mounted network backed file system with the features I need.
</p
>
4191 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4192 handling several different storage providers, any with Amazon S3,
4193 Google Drive or OpenStack API. There are heaps of such storage
4194 providers. S3QL can also use a local directory as storage, which
4195 combined with sshfs allow for file storage on any ssh server. S3QL
4196 include support for encryption, compression, de-duplication, snapshots
4197 and immutable file systems, allowing me to mount the remote storage as
4198 a local mount point, look at and use the files as if they were local,
4199 while the content is stored in the cloud as well. This allow me to
4200 have a backup that should survive fire. The file system can not be
4201 shared between several machines at the same time, as only one can
4202 mount it at the time, but any machine with the encryption key and
4203 access to the storage service can mount it if it is unmounted.
</p
>
4205 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4206 package is included already. So to get started, run
<tt
>apt-get
4207 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4208 Greenqloud, after reading their nice recipe on
4209 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4210 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4211 in Iceland more than those in USA when it come to keeping my personal
4212 data safe and private, and thus would rather spend money on a company
4213 in Iceland. Another nice recipe is available from the article
4214 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4215 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4216 Admin magazine. When the provider is picked, figure out how to get
4217 the API key needed to connect to the storage API. With Greencloud,
4218 the key did not show up until I had added payment details to my
4221 <p
>Armed with the API access details, it is time to create the file
4222 system. First, create a new bucket in the cloud. This bucket is the
4223 file system storage area. I picked a bucket name reflecting the
4224 machine that was going to store data there, but any name will do.
4225 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4226 the API login and password, and a locally created password. Store it
4227 all in ~root/.s3ql/authinfo2 like this:
4229 <p
><blockquote
><pre
>
4231 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4232 backend-login: API-login
4233 backend-password: API-password
4234 fs-passphrase: local-password
4235 </pre
></blockquote
></p
>
4237 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4238 but any sensible way to create a fairly random password should do it.
4239 Armed with these details, it is now time to run mkfs, entering the API
4240 details and password to create it:
</p
>
4242 <p
><blockquote
><pre
>
4243 # mkdir -m
700 /var/lib/s3ql-cache
4244 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4245 --ssl s3c://s.greenqloud.com:
443/bucket-name
4246 Enter backend login:
4247 Enter backend password:
4248 Before using S3QL, make sure to read the user
's guide, especially
4249 the
'Important Rules to Avoid Loosing Data
' section.
4250 Enter encryption password:
4251 Confirm encryption password:
4252 Generating random encryption key...
4253 Creating metadata tables...
4263 Compressing and uploading metadata...
4264 Wrote
0.00 MB of compressed metadata.
4265 #
</pre
></blockquote
></p
>
4267 <p
>The next step is mounting the file system to make the storage available.
4269 <p
><blockquote
><pre
>
4270 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4271 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4272 Using
4 upload threads.
4273 Downloading and decompressing metadata...
4283 Mounting filesystem...
4285 Filesystem Size Used Avail Use% Mounted on
4286 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4288 </pre
></blockquote
></p
>
4290 <p
>The file system is now ready for use. I use rsync to store my
4291 backups in it, and as the metadata used by rsync is downloaded at
4292 mount time, no network traffic (and storage cost) is triggered by
4293 running rsync. To unmount, one should not use the normal umount
4294 command, as this will not flush the cache to the cloud storage, but
4295 instead running the umount.s3ql command like this:
4297 <p
><blockquote
><pre
>
4300 </pre
></blockquote
></p
>
4302 <p
>There is a fsck command available to check the file system and
4303 correct any problems detected. This can be used if the local server
4304 crashes while the file system is mounted, to reset the
"already
4305 mounted
" flag. This is what it look like when processing a working
4306 file system:
</p
>
4308 <p
><blockquote
><pre
>
4309 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4310 Using cached metadata.
4311 File system seems clean, checking anyway.
4312 Checking DB integrity...
4313 Creating temporary extra indices...
4314 Checking lost+found...
4315 Checking cached objects...
4316 Checking names (refcounts)...
4317 Checking contents (names)...
4318 Checking contents (inodes)...
4319 Checking contents (parent inodes)...
4320 Checking objects (reference counts)...
4321 Checking objects (backend)...
4322 ..processed
5000 objects so far..
4323 ..processed
10000 objects so far..
4324 ..processed
15000 objects so far..
4325 Checking objects (sizes)...
4326 Checking blocks (referenced objects)...
4327 Checking blocks (refcounts)...
4328 Checking inode-block mapping (blocks)...
4329 Checking inode-block mapping (inodes)...
4330 Checking inodes (refcounts)...
4331 Checking inodes (sizes)...
4332 Checking extended attributes (names)...
4333 Checking extended attributes (inodes)...
4334 Checking symlinks (inodes)...
4335 Checking directory reachability...
4336 Checking unix conventions...
4337 Checking referential integrity...
4338 Dropping temporary indices...
4339 Backing up old metadata...
4349 Compressing and uploading metadata...
4350 Wrote
0.89 MB of compressed metadata.
4352 </pre
></blockquote
></p
>
4354 <p
>Thanks to the cache, working on files that fit in the cache is very
4355 quick, about the same speed as local file access. Uploading large
4356 amount of data is to me limited by the bandwidth out of and into my
4357 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4358 which is very close to my upload speed, and downloading the same
4359 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4360 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4361 network, not the file system code. I do not know what a good cache
4362 size would be, but suspect that the cache should e larger than your
4363 working set.
</p
>
4365 <p
>I mentioned that only one machine can mount the file system at the
4366 time. If another machine try, it is told that the file system is
4369 <p
><blockquote
><pre
>
4370 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4371 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4372 Using
8 upload threads.
4373 Backend reports that fs is still mounted elsewhere, aborting.
4375 </pre
></blockquote
></p
>
4377 <p
>The file content is uploaded when the cache is full, while the
4378 metadata is uploaded once every
24 hour by default. To ensure the
4379 file system content is flushed to the cloud, one can either umount the
4380 file system, or ask S3QL to flush the cache and metadata using
4383 <p
><blockquote
><pre
>
4384 # s3qlctrl upload-meta /s3ql
4385 # s3qlctrl flushcache /s3ql
4387 </pre
></blockquote
></p
>
4389 <p
>If you are curious about how much space your data uses in the
4390 cloud, and how much compression and deduplication cut down on the
4391 storage usage, you can use s3qlstat on the mounted file system to get
4394 <p
><blockquote
><pre
>
4396 Directory entries:
9141
4399 Total data size:
22049.38 MB
4400 After de-duplication:
21955.46 MB (
99.57% of total)
4401 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4402 Database size:
2.39 MB (uncompressed)
4403 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4405 </pre
></blockquote
></p
>
4407 <p
>I mentioned earlier that there are several possible suppliers of
4408 storage. I did not try to locate them all, but am aware of at least
4409 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4410 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4411 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4412 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4413 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4414 accept payment in Bitcoin. Pick one that suit your need. Some of
4415 them provide several GiB of free storage, but the prize models are
4416 quite different and you will have to figure out what suits you
4419 <p
>While researching this blog post, I had a look at research papers
4420 and posters discussing the S3QL file system. There are several, which
4421 told me that the file system is getting a critical check by the
4422 science community and increased my confidence in using it. One nice
4424 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4425 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4426 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4427 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4428 and Pamela Smith. Please have a look.
</p
>
4430 <p
>Given my problems with different file systems earlier, I decided to
4431 check out the mounted S3QL file system to see if it would be usable as
4432 a home directory (in other word, that it provided POSIX semantics when
4433 it come to locking and umask handling etc). Running
4434 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4435 test code to check file system semantics
</a
>, I was happy to discover that
4436 no error was found. So the file system can be used for home
4437 directories, if one chooses to do so.
</p
>
4439 <p
>If you do not want a locally file system, and want something that
4440 work without the Linux fuse file system, I would like to mention the
4441 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4442 provide locally encrypted backup using a command line client. It have
4443 a nicer access control system, where one can split out read and write
4444 access, allowing some systems to write to the backup and others to
4445 only read from it.
</p
>
4447 <p
>As usual, if you use Bitcoin and want to show your support of my
4448 activities, please send Bitcoin donations to my address
4449 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4454 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4455 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4457 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4458 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4459 project
</a
> is working on providing the software and hardware for
4460 making it easy for non-technical people to host their data and
4461 communication at home, and being able to communicate with their
4462 friends and family encrypted and away from prying eyes. It has been
4463 going on for a while, and is slowly progressing towards a new test
4464 release (
0.2).
</p
>
4466 <p
>And what day could be better than the Pi day to announce that the
4467 new version will provide
"hard drive
" / SD card / USB stick images for
4468 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4469 system), and can also be installed using a Debian installer preseed
4470 file. The Debian based Freedombox is now based on Debian Jessie,
4471 where most of the needed packages used are already present. Only one,
4472 the freedombox-setup package, is missing. To try to build your own
4473 boot image to test the current status, fetch the freedom-maker scripts
4475 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4476 with a user with sudo access to become root:
4479 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4481 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4482 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4484 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4487 <p
>Root access is needed to run debootstrap and mount loopback
4488 devices. See the README for more details on the build. If you do not
4489 want all three images, trim the make line. But note that thanks to
<a
4490 href=
"https://bugs.debian.org/
741407">a race condition in
4491 vmdebootstrap
</a
>, the build might fail without the patch to the
4492 kpartx call.
</p
>
4494 <p
>If you instead want to install using a Debian CD and the preseed
4495 method, boot a Debian Wheezy ISO and use this boot argument to load
4496 the preseed values:
</p
>
4499 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4502 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4503 recently introduced bug in apt in Jessie
</a
>, the installer will
4504 currently hang while setting up APT sources. Killing the
4505 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4506 installation will get the installation going. This affect all
4507 installations in Jessie, and I expect it will be fixed soon.
</p
>
4509 <p
>Give it a go and let us know how it goes on the mailing list, and help
4510 us get the new release published. :) Please join us on
4511 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4512 irc.debian.org)
</a
> and
4513 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4514 mailing list
</a
> if you want to help make this vision come true.
</p
>
4519 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4520 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4522 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4523 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4524 innetgr tools, because I needed them in
4525 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4526 ng-utils, and it has served me well. I placed the project under the
4527 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4528 repository. But many years ago, the CVS repository was dropped (lost,
4529 not migrated to new hardware, not sure), and the project have lacked a
4530 proper home since then.
</p
>
4532 <p
>Last summer, I had a look at the package and made a new release
4533 fixing a irritating crash bug, but was unable to store the changes in
4534 a proper source control system. I applied for a project on
4535 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4536 to follow up on it. Until today. :)
</p
>
4538 <p
>After many hours of cleaning and migration, the ng-utils project
4539 now have a new home, and a git repository with the highlight of the
4540 history of the project. I published all release tarballs and imported
4541 them into the git repository. As the project is really stable and not
4542 expected to gain new features any time soon, I decided to make a new
4543 release and call it
1.0. Visit the new project home on
4544 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4545 if you want to check it out. The new version is also uploaded into
4546 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4551 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4552 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4553 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4554 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4555 <description><p
>A few days ago I decided to try to help the Hurd people to get
4556 their changes into sysvinit, to allow them to use the normal sysvinit
4557 boot system instead of their old one. This follow up on the
4558 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4559 Google Summer of Code work
</a
> done last summer by Justus Winter to
4560 get Debian on Hurd working more like Debian on Linux. To get started,
4561 I downloaded a prebuilt hard disk image from
4562 <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
>,
4563 and started it using virt-manager.
</p
>
4565 <p
>The first think I had to do after logging in (root without any
4566 password) was to get the network operational. I followed
4567 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4568 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4569 commands as root to get the machine to accept a IP address from the
4570 kvm internal DHCP server:
</p
>
4572 <p
><blockquote
><pre
>
4573 settrans -fgap /dev/netdde /hurd/netdde
4574 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4575 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4577 </pre
></blockquote
></p
>
4579 <p
>After this, the machine had internet connectivity, and I could
4580 upgrade it and install the sysvinit packages from experimental and
4581 enable it as the default boot system in Hurd.
</p
>
4583 <p
>But before I did that, I set a password on the root user, as ssh is
4584 running on the machine it for ssh login to work a password need to be
4585 set. Also, note that a bug somewhere in openssh on Hurd block
4586 compression from working. Remember to turn that off on the client
4589 <p
>Run these commands as root to upgrade and test the new sysvinit
4592 <p
><blockquote
><pre
>
4593 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4594 deb http://http.debian.net/debian/ experimental main
4597 apt-get dist-upgrade
4598 apt-get install -t experimental initscripts sysv-rc sysvinit \
4599 sysvinit-core sysvinit-utils
4600 update-alternatives --config runsystem
4601 </pre
></blockquote
></p
>
4603 <p
>To reboot after switching boot system, you have to use
4604 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4605 yet a sysvinit process able to receive the signals from the normal
4606 'reboot
' command. After switching to sysvinit as the boot system,
4607 upgrading every package and rebooting, the network come up with DHCP
4608 after boot as it should, and the settrans/pkill hack mentioned at the
4609 start is no longer needed. But for some strange reason, there are no
4610 longer any login prompt in the virtual console, so I logged in using
4613 <p
>Note that there are some race conditions in Hurd making the boot
4614 fail some times. No idea what the cause is, but hope the Hurd porters
4615 figure it out. At least Justus said on IRC (#debian-hurd on
4616 irc.debian.org) that they are aware of the problem. A way to reduce
4617 the impact is to upgrade to the Hurd packages built by Justus by
4618 adding this repository to the machine:
</p
>
4620 <p
><blockquote
><pre
>
4621 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4622 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4624 </pre
></blockquote
></p
>
4626 <p
>At the moment the prebuilt virtual machine get some packages from
4627 http://ftp.debian-ports.org/debian, because some of the packages in
4628 unstable do not yet include the required patches that are lingering in
4629 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4631 <p
><blockquote
><pre
>
4632 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4633 i emacs - GNU Emacs editor (metapackage)
4634 i gdb - GNU Debugger
4635 i hurd-recommended - Miscellaneous translators
4636 i isc-dhcp-client - ISC DHCP client
4637 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4638 i libc-bin - Embedded GNU C Library: Binaries
4639 i libc-dev-bin - Embedded GNU C Library: Development binaries
4640 i libc0.3 - Embedded GNU C Library: Shared libraries
4641 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4642 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4643 i multiarch-support - Transitional package to ensure multiarch compatibilit
4644 i A x11-common - X Window System (X.Org) infrastructure
4645 i xorg - X.Org X Window System
4646 i A xserver-xorg - X.Org X server
4647 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4649 </pre
></blockquote
></p
>
4651 <p
>All in all, testing hurd has been an interesting experience. :)
4652 X.org did not work out of the box and I never took the time to follow
4653 the porters instructions to fix it. This time I was interested in the
4654 command line stuff.
<p
>
4659 <title>New chrpath release
0.16</title>
4660 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4661 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4662 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4663 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4664 find problems in C, C++ and Java code using static source code
4665 analysis. It can detect a lot of different problems, and is very
4666 useful to find memory and locking bugs in the error handling part of
4667 the source. The company behind it provide
4668 <a href=
"https://scan.coverity.com/
">check of free software projects as
4669 a community service
</a
>, and many hundred free software projects are
4670 already checked. A few days ago I decided to have a closer look at
4671 the Coverity system, and discovered that the
4672 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4673 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4674 projects I am involved with was already registered. But these are
4675 fairly big, and I would also like to have a small and easy project to
4676 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4677 checking of the chrpath project
</a
>. It was
4678 added to the checker and discovered seven potential defects. Six of
4679 these were real, mostly resource
"leak
" when the program detected an
4680 error. Nothing serious, as the resources would be released a fraction
4681 of a second later when the program exited because of the error, but it
4682 is nice to do it right in case the source of the program some time in
4683 the future end up in a library. Having fixed all defects and added
4684 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4685 mailing list for the chrpath developers
</a
>, I decided it was time to
4686 publish a new release. These are the release notes:
</p
>
4688 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4692 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4693 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4694 <li
>Mention new project mailing list in the documentation.
</li
>
4699 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4700 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4701 project if something is wrong with the new release. The test suite
4702 did not discover any old errors, so if you find a new one, please also
4703 include a test suite check.
</p
>
4708 <title>New chrpath release
0.15</title>
4709 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4710 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4711 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4712 <description><p
>After many years break from the package and a vain hope that
4713 development would be continued by someone else, I finally pulled my
4714 acts together this morning and wrapped up a new release of chrpath,
4715 the command line tool to modify the rpath and runpath of already
4716 compiled ELF programs. The update was triggered by the persistence of
4717 Isha Vishnoi at IBM, which needed a new config.guess file to get
4718 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4719 is working on. I checked the
4720 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4721 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4722 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4723 packages for interesting patches (failed to find the source from
4724 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4725 These are the release notes:
</p
>
4727 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4731 <li
>Updated config.sub and config.guess from the GNU project to work
4732 with newer architectures. Thanks to isha vishnoi for the heads
4735 <li
>Updated README with current URLs.
</li
>
4737 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4738 Matthias Klose.
</li
>
4740 <li
>Added missing help for -k|--keepgoing option, using patch by
4741 Petr Machata found in Fedora.
</li
>
4743 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4744 .dynamic is a NULL terminated string. Based on patch found in
4745 Fedora credited Axel Thimm and Christian Krause.
</li
>
4750 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4751 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4752 project if something is wrong with the new release. The test suite
4753 did not discover any old errors, so if you find a new one, please also
4754 include a testsuite check.
</p
>
4759 <title>Debian init.d boot script example for rsyslog
</title>
4760 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4762 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4763 <description><p
>If one of the points of switching to a new init system in Debian is
4764 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4765 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4766 init.d scripts at all. Here is an example init.d script, ie a rewrite
4767 of /etc/init.d/rsyslog:
</p
>
4769 <p
><pre
>
4770 #!/lib/init/init-d-script
4773 # Required-Start: $remote_fs $time
4774 # Required-Stop: umountnfs $time
4775 # X-Stop-After: sendsigs
4776 # Default-Start:
2 3 4 5
4777 # Default-Stop:
0 1 6
4778 # Short-Description: enhanced syslogd
4779 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4780 # It is quite compatible to stock sysklogd and can be
4781 # used as a drop-in replacement.
4783 DESC=
"enhanced syslogd
"
4784 DAEMON=/usr/sbin/rsyslogd
4785 </pre
></p
>
4787 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4788 script was
137 lines, and the above is just
15 lines, most of it meta
4789 info/comments.
</p
>
4791 <p
>How to do this, you ask? Well, one create a new script
4792 /lib/init/init-d-script looking something like this:
4794 <p
><pre
>
4797 # Define LSB log_* functions.
4798 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4799 # and status_of_proc is working.
4800 . /lib/lsb/init-functions
4803 # Function that starts the daemon/service
4809 #
0 if daemon has been started
4810 #
1 if daemon was already running
4811 #
2 if daemon could not be started
4812 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4814 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4817 # Add code here, if necessary, that waits for the process to be ready
4818 # to handle requests from services started subsequently which depend
4819 # on this one. As a last resort, sleep for some time.
4823 # Function that stops the daemon/service
4828 #
0 if daemon has been stopped
4829 #
1 if daemon was already stopped
4830 #
2 if daemon could not be stopped
4831 # other if a failure occurred
4832 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4833 RETVAL=
"$?
"
4834 [
"$RETVAL
" =
2 ]
&& return
2
4835 # Wait for children to finish too if this is a daemon that forks
4836 # and if the daemon is only ever run from this initscript.
4837 # If the above conditions are not satisfied then add some other code
4838 # that waits for the process to drop all resources that could be
4839 # needed by services started subsequently. A last resort is to
4840 # sleep for some time.
4841 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4842 [
"$?
" =
2 ]
&& return
2
4843 # Many daemons don
't delete their pidfiles when they exit.
4845 return
"$RETVAL
"
4849 # Function that sends a SIGHUP to the daemon/service
4853 # If the daemon can reload its configuration without
4854 # restarting (for example, when it is sent a SIGHUP),
4855 # then implement that here.
4857 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4862 scriptbasename=
"$(basename $
1)
"
4863 echo
"SN: $scriptbasename
"
4864 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4865 script=
"$
1"
4872 NAME=$(basename $DAEMON)
4873 PIDFILE=/var/run/$NAME.pid
4875 # Exit if the package is not installed
4876 #[ -x
"$DAEMON
" ] || exit
0
4878 # Read configuration variable file if it is present
4879 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4881 # Load the VERBOSE setting and other rcS variables
4884 case
"$
1" in
4886 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4888 case
"$?
" in
4889 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4890 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4894 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4896 case
"$?
" in
4897 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4898 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4902 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4904 #reload|force-reload)
4906 # If do_reload() is not implemented then leave this commented out
4907 # and leave
'force-reload
' as an alias for
'restart
'.
4909 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4913 restart|force-reload)
4915 # If the
"reload
" option is implemented then remove the
4916 #
'force-reload
' alias
4918 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4920 case
"$?
" in
4923 case
"$?
" in
4925 1) log_end_msg
1 ;; # Old process is still running
4926 *) log_end_msg
1 ;; # Failed to start
4936 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4942 </pre
></p
>
4944 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4945 lot. I did not really polish the approach, so it might not always
4946 work out of the box, but you get the idea. I did not try very hard to
4947 optimize it nor make it more robust either.
</p
>
4949 <p
>A better argument for switching init system in Debian than reducing
4950 the size of init scripts (which is a good thing to do anyway), is to
4951 get boot system that is able to handle the kernel events sensibly and
4952 robustly, and do not depend on the boot to run sequentially. The boot
4953 and the kernel have not behaved sequentially in years.
</p
>
4958 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4959 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4960 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4961 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4962 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4963 remote display access is the preferred solution with oVirt and RedHat
4964 Enterprise Virtualization, and I was sad to discover the other day
4965 that the browser plugin needed to use these systems seamlessly was
4966 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4967 for a package
</a
> was from
2012-
04-
10 with no progress since
4968 2013-
04-
01, so I decided to wrap up a package based on the great work
4969 from Cajus Pollmeier and put it in a collab-maint maintained git
4970 repository to get a package I could use. I would very much like
4971 others to help me maintain the package (or just take over, I do not
4972 mind), but as no-one had volunteered so far, I just uploaded it to
4973 NEW. I hope it will be available in Debian in a few days.
</p
>
4975 <p
>The source is now available from
4976 <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
>
4981 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4982 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4983 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4984 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4985 <description><p
>The
4986 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4987 program is a a very nice system to create virtual machine images. It
4988 create a image file, add a partition table, mount it and run
4989 debootstrap in the mounted directory to create a Debian system on a
4990 stick. Yesterday, I decided to try to teach it how to make images for
4991 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4992 of a plan to simplify the build system for
4993 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4994 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4995 the virtualbox images, but its current build system made multistrap
4996 based system for Dreamplug images, and it is lacking support for
4997 Raspberry Pi.
</p
>
4999 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5000 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5001 code and adjusted it to be able to build armel images on my amd64
5002 Debian laptop. I ended up giving vmdebootstrap five new options,
5003 allowing me to replicate the image creation process I use to make
5004 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5005 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5006 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5007 call debootstrap with --foreign and to copy the handler into the
5008 generated chroot before running the second stage. This allow
5009 vmdebootstrap to create armel images on an amd64 host. Next I added
5010 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5011 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5012 given file system type, allowing me to create an image with a vfat
5013 partition for the /boot/ stuff. I also added a
<tt
>--variant
5014 variant
</tt
> option to allow me to create smaller images without the
5015 Debian base system packages installed. Finally, I added an option
5016 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5017 as a boot loader. It is not needed on the Raspberry Pi and probably
5018 most other non-x86 architectures. The changes were accepted by the
5019 upstream author of vmdebootstrap yesterday and today, and is now
5021 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5022 upstream project page
</a
>.
</p
>
5024 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5025 create a small script (the customize script) to add the non-free
5026 binary blob needed to boot the Raspberry Pi and the APT source
5029 <p
><pre
>
5031 set -e # Exit on first error
5032 rootdir=
"$
1"
5033 cd
"$rootdir
"
5034 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5035 deb http://http.debian.net/debian/ jessie main contrib non-free
5037 # Install non-free binary blob needed to boot Raspberry Pi. This
5038 # install a kernel somewhere too.
5039 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5040 -O $rootdir/usr/bin/rpi-update
5041 chmod a+x $rootdir/usr/bin/rpi-update
5042 mkdir -p $rootdir/lib/modules
5043 touch $rootdir/boot/start.elf
5044 chroot $rootdir rpi-update
5045 </pre
></p
>
5047 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5048 to build the image:
</p
>
5051 sudo ./vmdebootstrap \
5054 --distribution jessie \
5055 --mirror http://http.debian.net/debian \
5064 --root-password raspberry \
5065 --hostname raspberrypi \
5066 --foreign /usr/bin/qemu-arm-static \
5067 --customize `pwd`/customize \
5069 --package git-core \
5070 --package binutils \
5071 --package ca-certificates \
5074 </pre
></p
>
5076 <p
>The list of packages being installed are the ones needed by
5077 rpi-update to make the image bootable on the Raspberry Pi, with the
5078 exception of netbase, which is needed by debootstrap to find
5079 /etc/hosts with the minbase variant. I really wish there was a way to
5080 set up an Raspberry Pi using only packages in the Debian archive, but
5081 that is not possible as far as I know, because it boots from the GPU
5082 using a non-free binary blob.
</p
>
5084 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5085 probably a few others installed. I have not checked the complete
5086 build dependency list.
</p
>
5088 <p
>The resulting image will not use the hardware floating point unit
5089 on the Raspberry PI, because the armel architecture in Debian is not
5090 optimized for that use. So the images created will be a bit slower
5091 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5096 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5097 <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>
5098 <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>
5099 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5100 <description><p
>The last few days I came across a few good causes that should get
5101 wider attention. I recommend signing and donating to each one of
5104 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5105 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5106 Women program which is a Google Summer of Code like initiative to get
5107 more women involved in free software. One debian sponsor has offered
5108 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5109 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5110 hope you will to. :)
</p
>
5112 <p
>And the Electronic Frontier Foundation just announced plans to
5113 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5114 documentaries about the excessive spying
</a
> on every Internet user that
5115 take place these days, and their need to fund the work. I
've already
5116 donated. Are you next?
</p
>
5118 <p
>For my Norwegian audience, the organisation Studentenes og
5119 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5120 statement under the heading
5121 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5122 Access
</a
> for those of us asking for more focus on open access in the
5123 Norwegian government. So far
499 signatures. I hope you will sign it
5129 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5130 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5132 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5133 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5134 project
</a
> have been going on for a while, and have presented the
5135 vision, ideas and solution several places. Here is a little
5136 collection of videos of talks and presentation of the project.
</p
>
5140 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5141 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5143 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5144 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5146 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5147 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5148 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5149 (Youtube)
</li
>
5151 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5152 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5154 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5155 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5157 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5158 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5159 York City in
2012</a
> (Youtube)
</li
>
5161 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5162 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5163 (Youtube)
</li
>
5165 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5166 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5168 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5169 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5171 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5172 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5173 2013</a
> (Youtube)
</li
>
5177 <p
>A larger list is available from
5178 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5179 Freedombox Wiki
</a
>.
</p
>
5181 <p
>On other news, I am happy to report that Freedombox based on Debian
5182 Jessie is coming along quite well, and soon both Owncloud and using
5183 Tor should be available for testers of the Freedombox solution. :) In
5184 a few weeks I hope everything needed to test it is included in Debian.
5185 The withsqlite package is already in Debian, and the plinth package is
5186 pending in NEW. The third and vital part of that puzzle is the
5187 metapackage/setup framework, which is still pending an upload. Join
5188 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5189 (#freedombox on irc.debian.org)
</a
> and
5190 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5191 mailing list
</a
> if you want to help make this vision come true.
</p
>
5196 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5197 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5199 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5200 <description><p
>I was introduced to the
5201 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5202 in
2010, when Eben Moglen presented his vision about serving the need
5203 of non-technical people to keep their personal information private and
5204 within the legal protection of their own homes. The idea is to give
5205 people back the power over their network and machines, and return
5206 Internet back to its intended peer-to-peer architecture. Instead of
5207 depending on a central service, the Freedombox will give everyone
5208 control over their own basic infrastructure.
</p
>
5210 <p
>I
've intended to join the effort since then, but other tasks have
5211 taken priority. But this summers nasty news about the misuse of trust
5212 and privilege exercised by the
"western
" intelligence gathering
5213 communities increased my eagerness to contribute to a point where I
5214 actually started working on the project a while back.
</p
>
5216 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5217 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5218 create a simple and cheap Debian based appliance that anyone can hook
5219 up in their home and get access to secure and private services and
5220 communication. The initial deployment platform have been the
5221 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5222 which is a piece of hardware I do not own. So to be able to test what
5223 the current Freedombox setup look like, I had to come up with a way to install
5224 it on some hardware I do have access to. I have rewritten the
5225 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5226 image build framework to use .deb packages instead of only copying
5227 setup into the boot images, and thanks to this rewrite I am able to
5228 set up any machine supported by Debian Wheezy as a Freedombox, using
5229 the previously mentioned deb (and a few support debs for packages
5230 missing in Debian).
</p
>
5232 <p
>The current Freedombox setup consist of a set of bootstrapping
5234 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5235 and a administrative web interface
5236 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5237 withsqlite), as well as a privacy enhancing proxy based on
5238 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5239 (freedombox-privoxy). There is also a web/javascript based XMPP
5240 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5241 trying (unsuccessfully so far) to talk to the XMPP server
5242 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5243 web interface is pluggable, and the goal is to use it to enable OpenID
5244 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5245 this is really working yet, see
5246 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5247 project TODO
</a
> for links to GIT repositories. Most of the code is
5248 on github at the moment. The HTTP proxy is operational out of the
5249 box, and the admin web interface can be used to add/remove plinth
5250 users. I
've not been able to do anything else with it so far, but
5251 know there are several branches spread around github and other places
5252 with lots of half baked features.
</p
>
5254 <p
>Anyway, if you want to have a look at the current state, the
5255 following recipes should work to give you a test machine to poke
5258 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5262 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5263 <li
>Boot from it, either as CD or USB stick.
</li
>
5264 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5265 to the Debian installer:
<p
>
5266 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5268 <li
>Answer the few language/region/password questions and pick disk to
5269 install on.
</li
>
5271 <li
>When the installation is finished and the machine have rebooted a
5272 few times, your Freedombox is ready for testing.
</li
>
5276 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5280 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5281 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5282 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5284 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5285 </pre
></li
>
5286 <li
><p
>Run this as root:
</p
>
5288 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5291 apt-get install freedombox-setup
5292 /usr/lib/freedombox/setup
5293 </pre
></li
>
5294 <li
>Reboot into your freshly created Freedombox.
</li
>
5298 <p
>You can test it on other architectures too, but because the
5299 freedombox-privoxy package is binary, it will only work as intended on
5300 the architectures where I have had time to build the binary and put it
5301 in my APT repository. But do not let this stop you. It is only a
5302 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5304 <p
>Note that by default Freedombox is a DHCP server on the
5305 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5306 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5307 disable
</tt
>" as root.
</p
>
5309 <p
>Please let me know if this works for you, or if you have any
5310 problems. We gather on the IRC channel
5311 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5312 irc.debian.org and the
5313 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5314 mailing list
</a
>.
</p
>
5316 <p
>Once you get your freedombox operational, you can visit
5317 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5318 welcome screen (dead end - do not be surprised if you are unable to
5319 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5320 to look at the rest of plinth. The default user is
'admin
' and the
5321 default password is
'secret
'.
</p
>
5326 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5327 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5329 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5330 <description><p
>Earlier, I reported about
5331 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5332 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5333 told by IBM that the original disk should be thrown away. And as
5334 there no longer was a problem if I bricked the firmware, I decided
5335 today to try to install Intel firmware to replace the Lenovo firmware
5336 currently on the disk.
</p
>
5338 <p
>I searched the Intel site for firmware, and found
5339 <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
>
5340 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5341 according to the site should contain the latest firmware for SSD
5342 disks. I inserted the broken disk in one of my spare laptops and
5343 booted the ISO from a USB stick. The disk was recognized, but the
5344 program claimed the newest firmware already were installed and refused
5345 to insert any Intel firmware. So no change, and the disk is still
5346 unable to handle write load. :( I guess the only way to get them
5347 working would be if Lenovo releases new firmware. No idea how likely
5348 that is. Anyway, just blogging about this test for completeness. I
5349 got a working Samsung disk, and see no point in spending more time on
5350 the broken disks.
</p
>
5355 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5356 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5358 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5359 <description><p
>Today I switched to
5360 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5361 new laptop
</a
>. I
've previously written about the problems I had with
5362 my new Thinkpad X230, which was delivered with an
5363 <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
5364 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5365 sustained writes. My hardware supplier have been very forthcoming in
5366 trying to find a solution, and after first trying with another
5367 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5368 disk instead to fix it once and for all. The Samsung disk survived
5369 the installation of Debian with encrypted disks (filling the disk with
5370 random data during installation killed the first two), and I thus
5371 decided to trust it with my data. I have installed it as a Debian Edu
5372 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5373 server at home using Kerberos and LDAP, and will use it as my work
5374 station from now on.
</p
>
5376 <p
>As this is a solid state disk with no moving parts, I believe the
5377 Debian Wheezy default installation need to be tuned a bit to increase
5378 performance and increase life time of the disk. The Linux kernel and
5379 user space applications do not yet adjust automatically to such
5380 environment. To make it easier for my self, I created a draft Debian
5381 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5382 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5383 for the ssd-setup package
</a
> is available from collab-maint, and it
5384 is set up to adjust the setup of the machine by just installing the
5385 package. If there is any non-SSD disk in the machine, the package
5386 will refuse to install, as I did not try to write any logic to sort
5387 file systems in SSD and non-SSD file systems.
</p
>
5389 <p
>I consider the package a draft, as I am a bit unsure how to best
5390 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5391 where I set up the machine with one large encrypted partition (in
5392 addition to /boot), put LVM on top of this and set up partitions on
5393 top of this again. See the README file in the package source for the
5394 references I used to pick the settings. At the moment these
5395 parameters are tuned:
</p
>
5399 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5400 (adding discard to /etc/crypttab)
</li
>
5402 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5403 this case a cryptsetup partition) by changing issue_discards from
5404 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5406 <li
>Set relatime as a file system option for ext3 and ext4 file
5409 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5410 /etc/fstab.
</li
>
5412 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5414 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5415 cron.daily).
</li
>
5417 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5418 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5422 <p
>During installation, I cancelled the part where the installer fill
5423 the disk with random data, as this would kill the SSD performance for
5424 little gain. My goal with the encrypted file system is to ensure
5425 those stealing my laptop end up with a brick and not a working
5426 computer. I have no hope in keeping the really resourceful people
5427 from getting the data on the disk (see
5428 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5429 Thus I concluded that adding the discard option to crypttab is the
5430 right thing to do.
</p
>
5432 <p
>I considered using the noop I/O scheduler, as several recommended
5433 it for SSD, but others recommended deadline and a benchmark I found
5434 indicated that deadline might be better for interactive use.
</p
>
5436 <p
>I also considered using the
'discard
' file system option for ext3
5437 and ext4, but read that it would give a performance hit ever time a
5438 file is removed, and thought it best to that that slowdown once a day
5439 instead of during my work.
</p
>
5441 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5442 this is already done by Debian Edu.
</p
>
5444 <p
>I have not yet started on the user space tuning. I expect
5445 iceweasel need some tuning, and perhaps other applications too, but
5446 have not yet had time to investigate those parts.
</p
>
5448 <p
>The package should work on Ubuntu too, but I have not yet tested it
5451 <p
>As for the answer to the question in the title of this blog post,
5452 as far as I know, the only solution I know about is to replace the
5453 disk. It might be possible to flash it with Intel firmware instead of
5454 the Lenovo firmware. But I have not tried and did not want to do so
5455 without approval from Lenovo as I wanted to keep the warranty on the
5456 disk until a solution was found and they wanted the broken disks
5462 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5463 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5464 <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>
5465 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5466 <description><p
>A few days ago, I wrote about
5467 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5468 problems I experienced with my new X230 and its SSD disk
</a
>, which
5469 was dying during installation because it is unable to cope with
5470 sustained write. My supplier is in contact with
5471 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5472 replacement disk to try to fix the problem. They decided to send an
5473 identical model, so my hopes for a permanent fix was slim.
</p
>
5475 <p
>Anyway, today I got the replacement disk and tried to install
5476 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5477 same firmware version as the original. This time my hope raised
5478 slightly as the installation progressed, as the original disk used to
5479 die after
4-
7% of the disk was written to, while this time it kept
5480 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5481 died again and I was back on square one. I still do not have a new
5482 laptop with a disk I can trust. I can not live with a disk that might
5483 lock up when I download a new
5484 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5485 other large files. I look forward to hearing from my supplier with
5486 the next proposal from Lenovo.
</p
>
5488 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5489 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5490 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5491 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5492 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5493 P/N
45N8295, P0C38732.
</p
>
5495 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5496 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5497 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5498 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5499 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5500 P/N
45N8295, P0C38732.
</p
>
5502 <p
>The only difference is in the first number (serial number?), ISN,
5503 SA, date and WNPP values. Mentioning all the details here in case
5504 someone is able to use the information to find a way to identify the
5505 failing disk among working ones (if any such working disk actually
5511 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5512 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5514 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5515 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5516 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5517 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5518 member assosiation NUUG
</a
> and
5519 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5520 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5521 Bitraf
</a
>.
</p
>
5523 <p
>It starts
10:
00 and continue until late evening. Everyone is
5524 welcome, and there is no fee to participate. There is on the other
5525 hand limited space, and only room for
30 people. Please put your name
5526 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5527 wiki page
</a
> if you plan to join us.
</p
>
5532 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5533 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5534 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5535 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5536 <description><p
>Half a year ago, I reported that I had to find a
5537 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5538 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5539 time to spend on it, and it took a while to find a model I believe
5540 will do the job, but two days ago the replacement finally arrived. I
5542 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5543 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5544 a roaming workstation, and it seemed to work flawlessly. But my
5545 second installation with encrypted disk was not as successful. More
5546 on that below.
</p
>
5548 <p
>I had a hard time trying to track down a good laptop, as my most
5549 important requirements (robust and with a good keyboard) are never
5550 listed in the feature list. But I did get good help from the search
5551 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5552 allowed me to limit the list of interesting laptops based on my other
5553 requirements. A bit surprising that SSD disk are not disks according
5554 to that search interface, so I had to drop specifying the number of
5555 disks from my search parameters. I also asked around among friends to
5556 get their impression on keyboards and robustness.
</p
>
5558 <p
>So the new laptop arrived, and it is quite a lot wider than the
5559 X41. I am not quite convinced about the keyboard, as it is
5560 significantly wider than my old keyboard, and I have to stretch my
5561 hand a lot more to reach the edges. But the key response is fairly
5562 good and the individual key shape is fairly easy to handle, so I hope
5563 I will get used to it. My old X40 was starting to fail, and I really
5564 needed a new laptop now. :)
</p
>
5566 <p
>Turning off the touch pad was simple. All it took was a quick
5567 visit to the BIOS during boot it disable it.
</p
>
5569 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5570 lock up during load. And this happen when installing Debian Wheezy
5571 with encrypted disk, while the disk is being filled with random data.
5572 I also tested to install Ubuntu Raring, and it happen there too if I
5573 reenable the code to fill the disk with random data (it is disabled by
5574 default in Ubuntu). And the bug with is already known. It was
5575 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5576 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5577 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5578 kernel developers as
5579 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5580 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5581 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5582 Lenovo forums, both for
5583 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5584 2012-
11-
10</a
> and for
5585 <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
5586 03-
20-
2013</a
>. The problem do not only affect installation. The
5587 reports state that the disk lock up during use if many writes are done
5588 on the disk, so it is much no use to work around the installation
5589 problem and end up with a computer that can lock up at any moment.
5591 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5592 available
</a
> that will lock up the hard drive after running a few
5593 minutes by writing to a file.
</p
>
5595 <p
>I
've contacted my supplier and asked how to handle this, and after
5596 contacting PCHELP Norway (request
01D1FDP) which handle support
5597 requests for Lenovo, his first suggestion was to upgrade the disk
5598 firmware. Unfortunately there is no newer firmware available from
5599 Lenovo, as my disk already have the most recent one (version LF1i). I
5600 hope to hear more from him today and hope the problem can be
5606 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5607 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5608 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5609 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5610 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5611 trusty old Thinkpad X41. Unfortunately I did not have much time to
5612 spend on it, but today the replacement finally arrived. I ended up
5613 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5614 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5615 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5616 this, it is installing what I hope will be a more final installation,
5617 with a encrypted hard drive to ensure any dope head stealing it end up
5618 with an expencive door stop.
</p
>
5620 <p
>I had a hard time trying to track down a good laptop, as my most
5621 important requirements (robust and with a good keyboard) are never
5622 listed in the feature list. But I did get good help from the search
5623 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5624 allowed me to limit the list of interesting laptops based on my other
5625 requirements. A bit surprising that SSD disk are not disks, so I had
5626 to drop number of disks from my search parameters.
</p
>
5628 <p
>I am not quite convinced about the keyboard, as it is significantly
5629 wider than my old keyboard, and I have to stretch my hand a lot more
5630 to reach the edges. But the key response is fairly good and the
5631 individual key shape is fairly easy to handle, so I hope I will get
5632 used to it. My old X40 was starting to fail, and I really needed a
5633 new laptop now. :)
</p
>
5635 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5640 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5641 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5642 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5643 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5644 <description><p
>It annoys me when the computer fail to do automatically what it is
5645 perfectly capable of, and I have to do it manually to get things
5646 working. One such task is to find out what firmware packages are
5647 needed to get the hardware on my computer working. Most often this
5648 affect the wifi card, but some times it even affect the RAID
5649 controller or the ethernet card. Today I pushed version
0.4 of the
5650 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5651 including a new script isenkram-autoinstall-firmware handling the
5652 process of asking all the loaded kernel modules what firmware files
5653 they want, find debian packages providing these files and install the
5654 debian packages. Here is a test run on my laptop:
</p
>
5656 <p
><pre
>
5657 # isenkram-autoinstall-firmware
5658 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5659 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5660 info: locating packages with the requested firmware files
5661 info: Updating APT sources after adding non-free APT source
5662 info: trying to install firmware-ipw2x00
5665 Preconfiguring packages ...
5666 Selecting previously deselected package firmware-ipw2x00.
5667 (Reading database ...
259727 files and directories currently installed.)
5668 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5669 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5671 </pre
></p
>
5673 <p
>When all the requested firmware is present, a simple message is
5674 printed instead:
</p
>
5676 <p
><pre
>
5677 # isenkram-autoinstall-firmware
5678 info: did not find any firmware files requested by loaded kernel modules. exiting
5680 </pre
></p
>
5682 <p
>It could use some polish, but it is already working well and saving
5683 me some time when setting up new machines. :)
</p
>
5685 <p
>So, how does it work? It look at the set of currently loaded
5686 kernel modules, and look up each one of them using modinfo, to find
5687 the firmware files listed in the module meta-information. Next, it
5688 download the Contents file from a nearby APT mirror, and search for
5689 the firmware files in this file to locate the package with the
5690 requested firmware file. If the package is in the non-free section, a
5691 non-free APT source is added and the package is installed using
5692 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5695 <p
>I hope someone find time to implement a more polished version of
5696 this script as part of the hw-detect debian-installer module, to
5697 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5698 #
655507</a
>. There really is no need to insert USB sticks with
5699 firmware during a PXE install when the packages already are available
5700 from the nearby Debian mirror.
</p
>
5705 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5706 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5707 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5708 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5709 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5710 the screen just turn black when Linux boot, either during installation
5711 or on first boot from the hard disk. I
've seen it once in a while the
5712 last few years, but only recently understood the cause. I
've seen it
5713 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5714 The reason seem to be in the wiring of some laptops. The system to
5715 control the screen background light is inverted, so when Linux try to
5716 turn the brightness fully on, it end up turning it off instead. I do
5717 not know which Linux drivers are affected, but this post is about the
5718 i915 driver used by the
5719 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5720 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5722 <p
>The problem can be worked around two ways. Either by adding
5723 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5724 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5725 option when it load the i915 kernel module. On Debian and Ubuntu, it
5726 can be done by running these commands as root:
</p
>
5729 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5730 update-initramfs -u -k all
5733 <p
>Since March
2012 there is
5734 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5735 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5736 hardware have this problem, and get the driver to invert the
5737 brightness setting automatically. To use it, one need to add a row in
5738 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5739 intel_quirks array
</a
> in the driver source
5740 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5741 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5742 number (vendor number
8086 is assumed) and subdevice vendor and device
5745 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5746 -vvnn
</tt
> for the video card in question:
</p
>
5748 <p
><pre
>
5749 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5750 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5751 (rev
09) (prog-if
00 [VGA controller])
5752 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5753 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5754 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5755 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5756 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5758 Interrupt: pin A routed to IRQ
42
5759 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5760 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5761 Region
4: I/O ports at
4000 [size=
64]
5762 Expansion ROM at
<unassigned
> [disabled]
5763 Capabilities:
<access denied
>
5764 Kernel driver in use: i915
5765 </pre
></p
>
5767 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5769 <p
><pre
>
5770 struct intel_quirk intel_quirks[] = {
5772 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5773 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5776 </pre
></p
>
5778 <p
>According to the kernel module instructions (as seen using
5779 <tt
>modinfo i915
</tt
>), information about hardware needing the
5780 invert_brightness flag should be sent to the
5781 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5782 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5783 developers. But my email about the laptop sent
2013-
06-
03 have not
5785 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5786 web archive for the mailing list
</a
>, so I suspect they do not accept
5787 emails from non-subscribers. Because of this, I sent my patch also to
5788 the Debian bug tracking system instead as
5789 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5790 sure the patch is not lost.
</p
>
5792 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5793 with this problem working properly with Linux. If you use Gnome, your
5794 worries should be over at this point. But if you use KDE, there is
5795 something in KDE ignoring the invert_brightness setting and turning on
5796 the screen during login. I
've reported it to Debian as
5797 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5798 have no idea yet how to figure out exactly what subsystem is doing
5799 this. Perhaps you can help? Perhaps you know what the Gnome
5800 developers did to handle this, and this can give a clue to the KDE
5801 developers? Or you know where in KDE the screen brightness is changed
5802 during login? If so, please update the BTS report (or get in touch if
5803 you do not know how to update BTS).
</p
>
5805 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5806 acpi_backlight=vendor, to disable ACPI backlight support completely,
5807 as the ACPI information on the machine is trash and it is better to
5808 leave it to the intel video driver to control the screen
5809 backlight.
</p
>
5814 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5815 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5816 <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>
5817 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5818 <description><p
>Two days ago, I asked
5819 <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
5820 I could install Linux on a Packard Bell EasyNote LV computer
5821 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5822 with the obstacles put in the way of Linux users on a laptop with UEFI
5823 and Windows
8.
</p
>
5825 <p
>I never found out if the cause of my problems were the use of UEFI
5826 secure booting or fast boot. I suspect fast boot was the problem,
5827 causing the firmware to boot directly from HD without considering any
5828 key presses and alternative devices, but do not know UEFI settings
5829 enough to tell.
</p
>
5831 <p
>There is no way to install Linux on the machine in question without
5832 opening the box and disconnecting the hard drive! This is as far as I
5833 can tell, the only way to get access to the firmware setup menu
5834 without accepting the Windows
8 license agreement. I am told (and
5835 found description on how to) that it is possible to configure the
5836 firmware setup once booted into Windows
8. But as I believe the terms
5837 of that agreement are completely unacceptable, accepting the license
5838 was never an alternative. I do not enter agreements I do not intend
5839 to follow.
</p
>
5841 <p
>I feared I had to return the laptops and ask for a refund, and
5842 waste many hours on this, but luckily there was a way to get it to
5843 work. But I would not recommend it to anyone planning to run Linux on
5844 it, and I have become sceptical to Windows
8 certified laptops. Is
5845 this the way Linux will be forced out of the market place, by making
5846 it close to impossible for
"normal
" users to install Linux without
5847 accepting the Microsoft Windows license terms? Or at least not
5848 without risking to loose the warranty?
</p
>
5850 <p
>I
've updated the
5851 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5852 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5853 do not have to struggle as much as I did to get Linux into the
5856 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5857 Michael Tokarev and others for feedback and ideas.
</p
>
5862 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5863 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5864 <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>
5865 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5866 <description><p
>I
've run into quite a problem the last few days. I bought three
5867 new laptops for my parents and a few others. I bought Packard Bell
5868 Easynote LV to run Kubuntu on and use as their home computer. But I
5869 am completely unable to figure out how to install Linux on it. The
5870 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5871 instead of a BIOS to boot.
</p
>
5873 <p
>The problem is that I am unable to get it to PXE boot, and unable
5874 to get it to boot the Linux installer from my USB stick. I have yet
5875 to try the DVD install, and still hope it will work. when I turn on
5876 the computer, there is no information on what buttons to press to get
5877 the normal boot menu. I expect to get some boot menu to select PXE or
5878 USB stick booting. When booting, it first ask for the language to
5879 use, then for some regional settings, and finally if I will accept the
5880 Windows
8 terms of use. As these terms are completely unacceptable to
5881 me, I have no other choice but to turn off the computer and try again
5882 to get it to boot the Linux installer.
</p
>
5884 <p
>I have gathered my findings so far on a Linlap page about the
5885 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5886 EasyNote LV
</a
> model. If you have any idea how to get Linux
5887 installed on this machine, please get in touch or update that wiki
5888 page. If I can
't find a way to install Linux, I will have to return
5889 the laptop to the seller and find another machine for my parents.
</p
>
5891 <p
>I wonder, is this the way Linux will be forced out of the market
5892 using UEFI and
"secure boot
" by making it impossible to install Linux
5893 on new Laptops?
</p
>
5898 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5899 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5900 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5901 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5902 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5903 an operating system based on Debian intended for use in schools. It
5904 contain a turn-key solution for the computer network provided to
5905 pupils in the primary schools. It provide both the central server,
5906 network boot servers and desktop environments with heaps of
5907 educational software. The project was founded almost
12 years ago,
5908 2001-
07-
02. If you want to support the project, which is in need for
5909 cash to fund developer gatherings and other project related activity,
5910 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5911 donate some money
</a
>.
5913 <p
>A topic that come up again and again on the Debian Edu mailing
5914 lists and elsewhere, is the question on how to transform a Debian or
5915 Ubuntu installation into a Debian Edu installation. It isn
't very
5916 hard, and last week I wrote a script to replicate the steps done by
5917 the Debian Edu installer.
</p
>
5919 <p
>The script,
5920 <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/
>
5921 in the debian-edu-config package, will go through these six steps and
5922 transform an existing Debian Wheezy or Ubuntu (untested) installation
5923 into a Debian Edu Workstation:
</p
>
5927 <li
>Add skolelinux related APT sources.
</li
>
5928 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5929 <li
>Install debian-edu-install to load preseeding values and pull in
5930 our configuration.
</li
>
5931 <li
>Preseed debconf database with profile setup in
5932 /etc/debian-edu/config, and run tasksel to install packages
5933 according to the profile specified in the config above,
5934 overriding some of the Debian automation machinery.
</li
>
5935 <li
>Run debian-edu-cfengine-D installation to configure everything
5936 that could not be done using preseeding.
</li
>
5937 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5941 <p
>There are some steps in the Debian Edu installation that can not be
5942 replicated like this. Disk partitioning and LVM setup, for example.
5943 So this script just assume there is enough disk space to install all
5944 the needed packages.
</p
>
5946 <p
>The script was created to help a Debian Edu student working on
5947 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5948 Debian Edu client, and using it he can take the existing
5949 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5950 transform it into a fully functioning Debian Edu Workstation (or
5951 Roaming Workstation, or whatever :).
</p
>
5953 <p
>The default setting in the script is to create a KDE Workstation.
5954 If a LXDE based Roaming workstation is wanted instead, modify the
5955 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5957 <p
><pre
>
5958 PROFILE=
"Roaming-Workstation
"
5959 DESKTOP=
"lxde
"
5960 </pre
></p
>
5962 <p
>The script could even become useful to set up Debian Edu servers in
5963 the cloud, by starting with a virtual Debian installation at some
5964 virtual hosting service and setting up all the services on first
5970 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5971 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5972 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5973 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5974 <description><P
>In January,
5975 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5976 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5977 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5978 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5979 marvellous construction system from Denmark. We also created
5980 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5981 a place to take notes and write down our plans and hopes. And several
5982 people showed up to help. I was very happy to see the effect of my
5983 call. Since the small start, we have a debtags tag
5984 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5985 tag for LEGO related packages, and now count
10 packages related to
5986 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5988 <p
><table
>
5989 <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
>
5990 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5991 <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
>
5992 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5993 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5994 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5995 <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
>
5996 <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
>
5997 <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
>
5998 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5999 </table
></p
>
6001 <p
>Some of these are available in Wheezy, and all but one are
6002 currently available in Jessie/testing. leocad is so far only
6003 available in experimental.
</p
>
6005 <p
>If you care about LEGO in Debian, please join us on IRC and help
6006 adding the rest of the great free software tools available on Linux
6007 for LEGO designers.
</p
>
6012 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6013 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6014 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6015 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6016 <description><p
>When I woke up this morning, I was very happy to see that the
6017 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6018 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6019 Debian release, and I expect to move my machines at home over to it fairly
6022 <p
>The new debian release contain heaps of new stuff, and one program
6023 in particular make me very happy to see included. The
6024 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6025 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6026 included for the first time. Alongside similar programs like
6027 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6028 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6029 it allow for visual programming where syntax errors can not happen,
6030 and a friendly programming environment for learning to control the
6031 computer. Scratch will also be included in the next release of Debian
6034 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6035 Edu/Skolelinux release too. The
6036 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6037 alpha release
</a
> went out last week, and the next should soon
6043 <title>Isenkram
0.2 finally in the Debian archive
</title>
6044 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6045 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6046 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6047 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6048 package
</a
> finally made it into the archive, after lingering in NEW
6049 for many months. I uploaded it to the Debian experimental suite
6050 2013-
01-
27, and today it was accepted into the archive.
</p
>
6052 <p
>Isenkram is a system for suggesting to users what packages to
6053 install to work with a pluggable hardware device. The suggestion pop
6054 up when the device is plugged in. For example if a Lego Mindstorm NXT
6055 is inserted, it will suggest to install the program needed to program
6056 the NXT controller. Give it a go, and report bugs and suggestions to
6062 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6063 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6064 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6065 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6066 <description><p
>My
6067 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6068 bitcoin related blog post
</a
> mentioned that the new
6069 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6070 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6071 2013-
01-
19, and have been available in unstable since then. It was
6072 automatically copied to Ubuntu, and is available in their Raring
6073 version too.
</p
>
6075 <p
>But there is a strange problem with the build that block this new
6076 version from being available on the i386 and kfreebsd-i386
6077 architectures. For some strange reason, the autobuilders in Debian
6078 for these architectures fail to run the test suite on these
6079 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6080 We are so far unable to reproduce it when building it manually, and
6081 no-one have been able to propose a fix. If you got an idea what is
6082 failing, please let us know via the BTS.
</p
>
6084 <p
>One feature that is annoying me with of the bitcoin client, because
6085 I often run low on disk space, is the fact that the client will exit
6086 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6087 #
696715</a
>). So make sure you have enough disk space when you run
6090 <p
>As usual, if you use bitcoin and want to show your support of my
6091 activities, please send Bitcoin donations to my address
6092 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6097 <title>Welcome to the world, Isenkram!
</title>
6098 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6099 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6100 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6101 <description><p
>Yesterday, I
6102 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6103 for testers
</a
> for my prototype for making Debian better at handling
6104 pluggable hardware devices, which I
6105 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6106 out to create
</a
> earlier this month. Several valuable testers showed
6107 up, and caused me to really want to to open up the development to more
6108 people. But before I did this, I want to come up with a sensible name
6109 for this project. Today I finally decided on a new name, and I have
6110 renamed the project from hw-support-handler to this new name. In the
6111 process, I moved the source to git and made it available as a
6112 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6113 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6114 To fetch and build the latest version of the source, use
</p
>
6117 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6118 cd isenkram
&& git-buildpackage -us -uc
6121 <p
>I have not yet adjusted all files to use the new name yet. If you
6122 want to hack on the source or improve the package, please go ahead.
6123 But please talk to me first on IRC or via email before you do major
6124 changes, to make sure we do not step on each others toes. :)
</p
>
6126 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6127 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6128 stuff, in other words. I
've been told it is the Norwegian variant of
6129 the German word eisenkram, for those that are familiar with that
6132 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6133 instructions, to avoid confusing people with an error from the signing
6136 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6137 clone argument to avoid the need for authentication.
</p
>
6142 <title>First prototype ready making hardware easier to use in Debian
</title>
6143 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6144 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6145 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6146 <description><p
>Early this month I set out to try to
6147 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6148 the Debian support for pluggable hardware devices
</a
>. Now my
6149 prototype is working, and it is ready for a larger audience. To test
6151 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6152 from the Debian Edu subversion repository
</a
>, build and install the
6153 package. You might have to log out and in again activate the
6154 autostart script.
</p
>
6156 <p
>The design is simple:
</p
>
6160 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6161 hw-support-handlerd to start when the user log in.
</li
>
6163 <li
>This program listen for kernel events about new hardware (directly
6164 from the kernel like udev does), not using HAL dbus events as I
6165 initially did.
</li
>
6167 <li
>When new hardware is inserted, look up the hardware modalias in
6168 the APT database, a database
6169 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6170 via HTTP
</a
> and a database available as part of the package.
</li
>
6172 <li
>If a package is mapped to the hardware in question, the package
6173 isn
't installed yet and this is the first time the hardware was
6174 plugged in, show a desktop notification suggesting to install the
6175 package or packages.
</li
>
6177 <li
>If the user click on the
'install package now
' button, ask
6178 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6180 <li
>aptdaemon ask for root password or sudo password, and install the
6181 package while showing progress information in a window.
</li
>
6185 <p
>I still need to come up with a better name for the system. Here
6186 are some screen shots showing the prototype in action. First the
6187 notification, then the password request, and finally the request to
6188 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6190 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6191 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6192 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6193 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6194 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6196 <p
>The prototype still need to be improved with longer timeouts, but
6197 is already useful. The database of hardware to package mappings also
6198 need more work. It is currently compatible with the Ubuntu way of
6199 storing such information in the package control file, but could be
6200 changed to use other formats instead or in addition to the current
6201 method. I
've dropped the use of discover for this mapping, as the
6202 modalias approach is more flexible and easier to use on Linux as long
6203 as the Linux kernel expose its modalias strings directly.
</p
>
6205 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6206 here is the command required to check out and build the source: Use
6207 '<tt
>svn checkout
6208 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6209 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6210 devscripts package.
</p
>
6212 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6213 renamed to Isenkram and the source moved from the Debian Edu
6214 subversion repository to a Debian collab-maint git repository. See
6215 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6216 instructions
</a
> for details.
</p
>
6221 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6222 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6224 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6225 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6226 suddenly in bed. With a quiet whimper, it went completely quiet and
6227 black. The power button was no longer able to turn it on. It was a
6228 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6229 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6230 Compaq I had before that. Now I need to find a replacement. To keep
6231 going during Christmas, I moved the one year old SSD disk to my old
6232 X40 where it fitted (only one I had left that could use it), but it is
6233 not a durable solution.
6235 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6236 got a new one more than
10 years ago. It still holds true.:)
</p
>
6240 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6241 than A4).
</li
>
6242 <li
>Robust, it will be in my backpack every day.
</li
>
6243 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6244 <li
>Long battery life time. Preferable a week.
</li
>
6245 <li
>Internal WIFI network card.
</li
>
6246 <li
>Internal Twisted Pair network card.
</li
>
6247 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6248 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6249 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6251 <li
>Hardware supported by Debian Stable, ie the default kernel and
6252 X.org packages.
</li
>
6253 <li
>Quiet, preferably fan free (or at least not using the fan most of
6258 <p
>You will notice that there are no RAM and CPU requirements in the
6259 list. The reason is simply that the specifications on laptops the
6260 last
10-
15 years have been sufficient for my needs, and I have to look
6261 at other features to choose my laptop. But are there still made as
6262 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6263 robust, and Thinkpads seem to be heading in the wrong direction since
6264 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6265 still be useful.
</p
>
6267 <p
>Perhaps I should rethink my needs, and look for a pad with an
6268 external keyboard? I
'll have to check the
6269 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6270 well-supported laptops, or perhaps just buy one preinstalled from one
6271 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6272 Pre-loaded site
</a
>.
</p
>
6277 <title>How to find a browser plugin supporting a given MIME type
</title>
6278 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6279 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6280 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6281 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6282 install to get support for a given MIME type. Thanks to
6283 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6284 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6285 Unfortunately, not very many packages provide the needed meta
6286 information, Anyway, here is a small script to look up all browser
6287 plugin packages announcing ther MIME support using this specification:
</p
>
6293 def pkgs_handling_mimetype(mimetype):
6298 version = pkg.candidate
6300 version = pkg.installed
6303 record = version.record
6304 if not record.has_key(
'Npp-MimeType
'):
6306 mime_types = record[
'Npp-MimeType
'].split(
',
')
6307 for t in mime_types:
6308 t = t.rstrip().strip()
6310 thepkgs.append(pkg.name)
6312 mimetype =
"audio/ogg
"
6313 if
1 < len(sys.argv):
6314 mimetype = sys.argv[
1]
6315 print
"Browser plugin packages supporting %s:
" % mimetype
6316 for pkg in pkgs_handling_mimetype(mimetype):
6317 print
" %s
" %pkg
6320 <p
>It can be used like this to look up a given MIME type:
</p
>
6323 % ./apt-find-browserplug-for-mimetype
6324 Browser plugin packages supporting audio/ogg:
6326 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6327 Browser plugin packages supporting application/x-shockwave-flash:
6328 browser-plugin-gnash
6332 <p
>In Ubuntu this mechanism is combined with support in the browser
6333 itself to query for plugins and propose to install the needed
6334 packages. It would be great if Debian supported such feature too. Is
6335 anyone working on adding it?
</p
>
6337 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6338 request for icweasel support for this feature is
6339 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6340 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6341 of manpower and wish for a different design is the reason thus feature
6342 is not yet in iceweasel from Debian.
</p
>
6347 <title>What is the most supported MIME type in Debian?
</title>
6348 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6349 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6350 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6351 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6352 proposal to add AppStream information to the Debian archive
</a
>, is a
6353 proposal to make it possible for a Desktop application to propose to
6354 the user some package to install to gain support for a given MIME
6355 type, font, library etc. that is currently missing. With such
6356 mechanism in place, it would be possible for the desktop to
6357 automatically propose and install leocad if some LDraw file is
6358 downloaded by the browser.
</p
>
6360 <p
>To get some idea about the current content of the archive, I decided
6361 to write a simple program to extract all .desktop files from the
6362 Debian archive and look up the claimed MIME support there. The result
6364 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6365 site
</a
>. Using the collected information, it become possible to
6366 answer the question in the title. Here are the
20 most supported MIME
6367 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6368 The complete list is available from the link above.
</p
>
6370 <p
><strong
>Debian Stable:
</strong
></p
>
6374 ----- -----------------------
6390 18 application/x-ogg
6397 <p
><strong
>Debian Testing:
</strong
></p
>
6401 ----- -----------------------
6417 18 application/x-ogg
6424 <p
><strong
>Debian Unstable:
</strong
></p
>
6428 ----- -----------------------
6445 18 application/x-ogg
6451 <p
>I am told that PackageKit can provide an API to access the kind of
6452 information mentioned in DEP-
11. I have not yet had time to look at
6453 it, but hope the PackageKit people in Debian are on top of these
6456 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6457 discovering a typo in my script.
</p
>
6462 <title>Using modalias info to find packages handling my hardware
</title>
6463 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6464 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6465 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6466 <description><p
>Yesterday, I wrote about the
6467 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6468 values provided by the Linux kernel
</a
> following my hope for
6469 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6470 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6471 modalias values attached to package names can be used to map packages
6472 to hardware. This allow the system to look up and suggest relevant
6473 packages when I plug in some new hardware into my machine, and replace
6474 discover and discover-data as the database used to map hardware to
6477 <p
>I create a modaliases file with entries like the following,
6478 containing package name, kernel module name (if relevant, otherwise
6479 the package name) and globs matching the relevant hardware
6482 <p
><blockquote
>
6483 Package: package-name
6484 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6485 </blockquote
></p
>
6487 <p
>It is fairly trivial to write code to find the relevant packages
6488 for a given modalias value using this file.
</p
>
6490 <p
>An entry like this would suggest the video and picture application
6491 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6493 <p
><blockquote
>
6495 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6496 </blockquote
></p
>
6498 <p
>An entry like this would suggest the pcmciautils package when a
6499 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6501 <p
><blockquote
>
6502 Package: pcmciautils
6503 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6504 </blockquote
></p
>
6506 <p
>An entry like this would suggest the package colorhug-client when
6507 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6509 <p
><blockquote
>
6510 Package: colorhug-client
6511 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6512 </blockquote
></p
>
6514 <p
>I believe the format is compatible with the format of the Packages
6515 file in the Debian archive. Ubuntu already uses their Packages file
6516 to store their mappings from packages to hardware.
</p
>
6518 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6519 announce the hardware it support in a way my prototype understand.
6520 This allow those publishing packages in an APT source outside the
6521 Debian archive as well as those backporting packages to make sure the
6522 hardware mapping are included in the package meta information. I
've
6523 tested such header in the pymissile package, and its modalias mapping
6524 is working as it should with my prototype. It even made it to Ubuntu
6527 <p
>To test if it was possible to look up supported hardware using only
6528 the shell tools available in the Debian installer, I wrote a shell
6529 implementation of the lookup code. The idea is to create files for
6530 each modalias and let the shell do the matching. Please check out and
6532 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6533 shell script. It run without any extra dependencies and fetch the
6534 hardware mappings from the Debian archive and the subversion
6535 repository where I currently work on my prototype.
</p
>
6537 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6538 install yubikey-personalization:
</p
>
6540 <p
><blockquote
>
6541 % ./hw-support-lookup
6542 <br
>yubikey-personalization
6544 </blockquote
></p
>
6546 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6547 propose to install the pcmciautils package:
</p
>
6549 <p
><blockquote
>
6550 % ./hw-support-lookup
6551 <br
>pcmciautils
6553 </blockquote
></p
>
6555 <p
>If you know of any hardware-package mapping that should be added to
6556 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6557 database
</a
>, please tell me about it.
</p
>
6559 <p
>It could be possible to generate several of the mappings between
6560 packages and hardware. One source would be to look at packages with
6561 kernel modules, ie packages with *.ko files in /lib/modules/, and
6562 extract their modalias information. Another would be to look at
6563 packages with udev rules, ie packages with files in
6564 /lib/udev/rules.d/, and extract their vendor/model information to
6565 generate a modalias matching rule. I have not tested any of these to
6566 see if it work.
</p
>
6568 <p
>If you want to help implementing a system to let us propose what
6569 packages to install when new hardware is plugged into a Debian
6570 machine, please send me an email or talk to me on
6571 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6576 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6577 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6578 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6579 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6580 <description><p
>While looking into how to look up Debian packages based on hardware
6581 information, to find the packages that support a given piece of
6582 hardware, I refreshed my memory regarding modalias values, and decided
6583 to document the details. Here are my findings so far, also available
6585 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6586 Debian Edu subversion repository
</a
>:
6588 <p
><strong
>Modalias decoded
</strong
></p
>
6590 <p
>This document try to explain what the different types of modalias
6591 values stands for. It is in part based on information from
6592 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6593 &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;,
6594 &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
6595 &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;.
6597 <p
>The modalias entries for a given Linux machine can be found using
6598 this shell script:
</p
>
6601 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6604 <p
>The supported modalias globs for a given kernel module can be found
6605 using modinfo:
</p
>
6608 % /sbin/modinfo psmouse | grep alias:
6609 alias: serio:ty05pr*id*ex*
6610 alias: serio:ty01pr*id*ex*
6614 <p
><strong
>PCI subtype
</strong
></p
>
6616 <p
>A typical PCI entry can look like this. This is an Intel Host
6617 Bridge memory controller:
</p
>
6619 <p
><blockquote
>
6620 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6621 </blockquote
></p
>
6623 <p
>This represent these values:
</p
>
6628 sv
00001028 (subvendor)
6629 sd
000001AD (subdevice)
6631 sc
00 (bus subclass)
6635 <p
>The vendor/device values are the same values outputted from
'lspci
6636 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6637 0600. The
0600 class is a host bridge. Other useful bus values are
6638 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6640 <p
>Not sure how to figure out the interface value, nor what it
6643 <p
><strong
>USB subtype
</strong
></p
>
6645 <p
>Some typical USB entries can look like this. This is an internal
6646 USB hub in a laptop:
</p
>
6648 <p
><blockquote
>
6649 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6650 </blockquote
></p
>
6652 <p
>Here is the values included in this alias:
</p
>
6655 v
1D6B (device vendor)
6656 p
0001 (device product)
6658 dc
09 (device class)
6659 dsc
00 (device subclass)
6660 dp
00 (device protocol)
6661 ic
09 (interface class)
6662 isc
00 (interface subclass)
6663 ip
00 (interface protocol)
6666 <p
>The
0900 device class/subclass means hub. Some times the relevant
6667 class is in the interface class section. For a simple USB web camera,
6668 these alias entries show up:
</p
>
6670 <p
><blockquote
>
6671 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6672 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6673 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6674 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6675 </blockquote
></p
>
6677 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6678 camera),
0101 is audio control device and
0102 is audio streaming (aka
6679 microphone). Thus this is a camera with microphone included.
</p
>
6681 <p
><strong
>ACPI subtype
</strong
></p
>
6683 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6684 receiver in a Thinkpad X40:
</p
>
6686 <p
><blockquote
>
6687 acpi:IBM0071:PNP0511:
6688 </blockquote
></p
>
6690 <p
>The values between the colons are IDs.
</p
>
6692 <p
><strong
>DMI subtype
</strong
></p
>
6694 <p
>The DMI table contain lots of information about the computer case
6695 and model. This is an entry for a IBM Thinkpad X40, fetched from
6696 /sys/devices/virtual/dmi/id/modalias:
</p
>
6698 <p
><blockquote
>
6699 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6700 </blockquote
></p
>
6702 <p
>The values present are
</p
>
6705 bvn IBM (BIOS vendor)
6706 bvr
1UETB
6WW(
1.66) (BIOS version)
6707 bd
06/
15/
2005 (BIOS date)
6708 svn IBM (system vendor)
6709 pn
2371H4G (product name)
6710 pvr ThinkPadX40 (product version)
6711 rvn IBM (board vendor)
6712 rn
2371H4G (board name)
6713 rvr NotAvailable (board version)
6714 cvn IBM (chassis vendor)
6715 ct
10 (chassis type)
6716 cvr NotAvailable (chassis version)
6719 <p
>The chassis type
10 is Notebook. Other interesting values can be
6720 found in the dmidecode source:
</p
>
6724 4 Low Profile Desktop
6737 17 Main Server Chassis
6738 18 Expansion Chassis
6740 20 Bus Expansion Chassis
6741 21 Peripheral Chassis
6743 23 Rack Mount Chassis
6752 <p
>The chassis type values are not always accurately set in the DMI
6753 table. For example my home server is a tower, but the DMI modalias
6754 claim it is a desktop.
</p
>
6756 <p
><strong
>SerIO subtype
</strong
></p
>
6758 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6759 test machine:
</p
>
6761 <p
><blockquote
>
6762 serio:ty01pr00id00ex00
6763 </blockquote
></p
>
6765 <p
>The values present are
</p
>
6774 <p
>This type is supported by the psmouse driver. I am not sure what
6775 the valid values are.
</p
>
6777 <p
><strong
>Other subtypes
</strong
></p
>
6779 <p
>There are heaps of other modalias subtypes according to
6780 file2alias.c. There is the rest of the list from that source: amba,
6781 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6782 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6783 vmbus, x86cpu and zorro. I did not spend time documenting all of
6784 these, as they do not seem relevant for my intended use with mapping
6785 hardware to packages when new stuff is inserted during run time.
</p
>
6787 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6789 <p
>To check which kernel modules provide support for a given modalias,
6790 one can use the following shell script:
</p
>
6793 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6794 echo
"$id
" ; \
6795 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6799 <p
>The output can look like this (only the first few entries as the
6800 list is very long on my test machine):
</p
>
6804 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6806 FATAL: Module acpi:device: not found.
6808 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6809 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6810 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6811 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6812 acpi:IBM0071:PNP0511:
6813 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6814 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6815 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6819 <p
>If you want to help implementing a system to let us propose what
6820 packages to install when new hardware is plugged into a Debian
6821 machine, please send me an email or talk to me on
6822 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6824 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6825 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6826 in /sys/ with space in them.
</p
>
6831 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6832 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6833 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6834 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6835 <description><p
>As part of my investigation on how to improve the support in Debian
6836 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6837 Launcher and updated the Debian package
6838 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6839 sure udev will fix the device permissions when it is plugged in. I
6840 also added a
"Modaliases
" header to test it in the Debian archive and
6841 hopefully make the package be proposed by jockey in Ubuntu when a user
6842 plug in his rocket launcher. In the process I moved the source to a
6843 git repository under collab-maint, to make it easier for any DD to
6844 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6845 is not very active, but the software still work for me even after five
6846 years of relative silence. The new git repository is not listed in
6847 the uploaded package yet, because I want to test the other changes a
6848 bit more before I upload the new version. If you want to check out
6849 the new version with a .desktop file included, visit the
6850 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6851 view
</a
> or use
"<tt
>git clone
6852 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6857 <title>Lets make hardware dongles easier to use in Debian
</title>
6858 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6859 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6860 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6861 <description><p
>One thing that annoys me with Debian and Linux distributions in
6862 general, is that there is a great package management system with the
6863 ability to automatically install software packages by downloading them
6864 from the distribution mirrors, but no way to get it to automatically
6865 install the packages I need to use the hardware I plug into my
6866 machine. Even if the package to use it is easily available from the
6867 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6868 suggest to automatically install the python-nxt, nbc and t2n packages
6869 I need to talk to it. When I plug in a Yubikey, it could propose the
6870 yubikey-personalization package. The information required to do this
6871 is available, but no-one have pulled all the pieces together.
</p
>
6873 <p
>Some years ago, I proposed to
6874 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6875 the discover subsystem to implement this
</a
>. The idea is fairly
6880 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6881 starting when a user log in.
</li
>
6883 <li
>Set this program up to listen for kernel events emitted when new
6884 hardware is inserted into the computer.
</li
>
6886 <li
>When new hardware is inserted, look up the hardware ID in a
6887 database mapping to packages, and take note of any non-installed
6888 packages.
</li
>
6890 <li
>Show a message to the user proposing to install the discovered
6891 package, and make it easy to install it.
</li
>
6895 <p
>I am not sure what the best way to implement this is, but my
6896 initial idea was to use dbus events to discover new hardware, the
6897 discover database to find packages and
6898 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6901 <p
>Yesterday, I found time to try to implement this idea, and the
6902 draft package is now checked into
6903 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6904 Debian Edu subversion repository
</a
>. In the process, I updated the
6905 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6906 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6907 the relevant packages in Debian, and uploaded a new version
6908 2.2013.01.09 to unstable. I also discovered that the current
6909 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6910 package in Debian no longer discovered any USB devices, because
6911 /proc/bus/usb/devices is no longer present. I ported it to use
6912 libusb as a fall back option to get it working. The fixed package
6913 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6914 because of the freeze).
</p
>
6916 <p
>With this prototype in place, I can insert my Yubikey, and get this
6917 desktop notification to show up (only once, the first time it is
6918 inserted):
</p
>
6920 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6922 <p
>For this prototype to be really useful, some way to automatically
6923 install the proposed packages by pressing the
"Please install
6924 program(s)
" button should to be implemented.
</p
>
6926 <p
>If this idea seem useful to you, and you want to help make it
6927 happen, please help me update the discover-data database with mappings
6928 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6929 list the package you would like to have installed when a given
6930 hardware device is inserted into your computer, and report bugs using
6931 reportbug if it isn
't. Or, if you know of a better way to provide
6932 such mapping, please let me know.
</p
>
6934 <p
>This prototype need more work, and there are several questions that
6935 should be considered before it is ready for production use. Is dbus
6936 the correct way to detect new hardware? At the moment I look for HAL
6937 dbus events on the system bus, because that is the events I could see
6938 on my Debian Squeeze KDE desktop. Are there better events to use?
6939 How should the user be notified? Is the desktop notification
6940 mechanism the best option, or should the background daemon raise a
6941 popup instead? How should packages be installed? When should they
6942 not be installed?
</p
>
6944 <p
>If you want to help getting such feature implemented in Debian,
6945 please send me an email. :)
</p
>
6950 <title>New IRC channel for LEGO designers using Debian
</title>
6951 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6952 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6953 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6954 <description><p
>During Christmas, I have worked a bit on the Debian support for
6955 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6956 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6957 discovered I had to build all the tools myself because none were
6958 already in Debian Squeeze. If Debian support for LEGO is something
6959 you care about, please join me on the IRC channel
6960 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6961 irc.debian.org). There is a lot that could be done to improve the
6962 Debian support for LEGO designers. For example both CAD software
6963 and Mindstorm compilers are missing. :)
</p
>
6965 <p
>Update
2012-
01-
03: A
6966 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6967 including links to Lego related packages is now available.
</p
>
6972 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6973 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6974 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6975 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6976 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6977 year! I hope next year will prove to be a good year.
</p
>
6979 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6980 decentralised
"currency
" that allow people to transfer bitcoins
6981 between each other with minimal overhead, is a very interesting
6982 experiment. And as I wrote a few days ago, the bitcoin situation in
6983 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6984 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6985 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6986 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6987 for one of the ftpmasters to approve the new bitcoin-qt package
6990 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6991 team in Debian, you can easily test the package in Debian Squeeze
6992 using the following steps to get a set of working packages:
</p
>
6994 <blockquote
><pre
>
6995 git clone git://git.debian.org/git/collab-maint/bitcoin
6997 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6998 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6999 </pre
></blockquote
>
7001 <p
>You might have to install some build dependencies as well. The
7002 list of commands should give you two packages, bitcoind and
7003 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7004 client will download the complete set of bitcoin
"blocks
", which need
7005 around
5.6 GiB of data on my machine at the moment. Make sure your
7006 ~/.bitcoin/ directory have lots of spare room if you want to download
7007 all the blocks. The client will warn if the disk is getting full, so
7008 there is not really a problem if you got too little room, but you will
7009 not be able to get all the features out of the client.
</p
>
7011 <p
>As usual, if you use bitcoin and want to show your support of my
7012 activities, please send Bitcoin donations to my address
7013 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7018 <title>A word on bitcoin support in Debian
</title>
7019 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7020 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7021 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7022 <description><p
>It has been a while since I wrote about
7023 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7024 peer-to-peer based crypto-currency, and the reason is simply that I
7025 have been busy elsewhere. But two days ago, I started looking at the
7026 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7027 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7028 is now maintained by a
7029 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7030 people
</a
>, and the grunt work had already been done by this team. We
7031 owe a huge thank you to all these team members. :)
7032 But I was sad to discover that the bitcoin client is missing in
7033 Wheezy. It is only available in Sid (and an outdated client from
7034 backports). The client had several RC bugs registered in BTS blocking
7035 it from entering testing. To try to help the team and improve the
7036 situation, I spent some time providing patches and triaging the bug
7037 reports. I also had a look at the bitcoin package available from Matt
7039 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7040 Ubuntu
</a
>, and moved the useful pieces from that version into the
7041 Debian package.
</p
>
7043 <p
>After checking with the main package maintainer Jonas Smedegaard on
7044 IRC, I pushed several patches into the collab-maint git repository to
7045 improve the package. It now contains fixes for the RC issues (not from
7046 me, but fixed by Scott Howard), build rules for a Qt GUI client
7047 package, konqueror support for the bitcoin: URI and bash completion
7048 setup. As I work on Debian Squeeze, I also created
7049 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7050 patch to backport
</a
> the latest version. Jonas is going to look at
7051 it and try to integrate it into the git repository before uploading a
7052 new version to unstable.
7054 <p
>I would very much like bitcoin to succeed, to get rid of the
7055 centralized control currently exercised in the monetary system. I
7056 find it completely unacceptable that the USA government is collecting
7057 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7058 that the major credit card companies can block legal money
7059 transactions to Wikileaks. But for bitcoin to succeed, more people
7060 need to use bitcoins, and more people need to accept bitcoins when
7061 they sell products and services. Improving the bitcoin support in
7062 Debian is a small step in the right direction, but not enough.
7063 Unfortunately the user experience when browsing the web and wanting to
7064 pay with bitcoin is still not very good. The bitcoin: URI is a step
7065 in the right direction, but need to work in most or every browser in
7066 use. Also the bitcoin-qt client is too heavy to fire up to do a
7067 quick transaction. I believe there are other clients available, but
7068 have not tested them.
</p
>
7071 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7072 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7073 I received
20.15 BTC so far on the address I provided in my blog two
7074 years ago, as can be
7075 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7076 on the blockexplorer service
</a
>. Thank you everyone for your
7077 donation. The blockexplorer service demonstrates quite well that
7078 bitcoin is not quite anonymous and untracked. :) I wonder if the
7079 number of users have gone up since then. If you use bitcoin and want
7080 to show your support of my activity, please send Bitcoin donations to
7081 the same address as last time,
7082 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7087 <title>Git repository for song book for Computer Scientists
</title>
7088 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7090 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7091 <description><p
>As I
7092 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7093 this summer
</a
>, I have created a Computer Science song book a few
7094 years ago, and today I finally found time to create a public
7095 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7096 repository for the project
</a
>.
</p
>
7098 <p
>If you want to help out, please clone the source and submit patches
7099 to the HTML version. To generate the PDF and PostScript version,
7100 please use prince XML, or let me know about a useful free software
7101 processor capable of creating a good looking PDF from the HTML.
</p
>
7103 <p
>Want to sing? You can still find the song book in HTML, PDF and
7104 PostScript formats at
7105 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7106 Science Songbook
</a
>.
</p
>
7111 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7112 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7113 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7114 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7115 <description><p
>I dag fyller
7116 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7117 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7118 si gratulerer med dagen, Debian!
</p
>
7123 <title>Song book for Computer Scientists
</title>
7124 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7125 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7126 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7127 <description><p
>Many years ago, while studying Computer Science at the
7128 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7129 collecting computer related songs for use at parties. The original
7130 version was written in LaTeX, but a few years ago I got help from
7131 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7132 while keeping the ability to create a nice book in PDF format. I have
7133 not had time to maintain the book for a while now, and guess I should
7134 put it up on some public version control repository where others can
7135 help me extend and update the book. If anyone is volunteering to help
7136 me with this, send me an email. Also let me know if there are songs
7137 missing in my book.
</p
>
7139 <p
>I have not mentioned the book on my blog so far, and it occured to
7140 me today that I really should let all my readers share the joys of
7141 singing out load about programming, computers and computer networks.
7142 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7143 12</a
> is about to start (and I am not going). Want to sing? Check
7144 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7145 Computer Science Songbook
</a
>.
7150 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7151 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7153 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7154 <description><p
>At work we have heaps of servers. I believe the total count is
7155 around
1000 at the moment. To be able to get help from the vendors
7156 when something go wrong, we want to keep the firmware on the servers
7157 up to date. If the firmware isn
't the latest and greatest, the
7158 vendors typically refuse to start debugging any problems until the
7159 firmware is upgraded. So before every reboot, we want to upgrade the
7160 firmware, and we would really like everyone handling servers at the
7161 university to do this themselves when they plan to reboot a machine.
7162 For that to happen we at the unix server admin group need to provide
7163 the tools to do so.
</p
>
7165 <p
>To make firmware upgrading easier, I am working on a script to
7166 fetch and install the latest firmware for the servers we got. Most of
7167 our hardware are from Dell and HP, so I have focused on these servers
7168 so far. This blog post is about the Dell part.
</P
>
7170 <p
>On the Dell FTP site I was lucky enough to find
7171 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7172 with firmware information for all
11th generation servers, listing
7173 which firmware should be used on a given model and where on the FTP
7174 site I can find it. Using a simple perl XML parser I can then
7175 download the shell scripts Dell provides to do firmware upgrades from
7176 within Linux and reboot when all the firmware is primed and ready to
7177 be activated on the first reboot.
</p
>
7179 <p
>This is the Dell related fragment of the perl code I am working on.
7180 Are there anyone working on similar tools for firmware upgrading all
7181 servers at a site? Please get in touch and lets share resources.
</p
>
7183 <p
><pre
>
7187 use File::Temp qw(tempdir);
7189 # Install needed RHEL packages if missing
7191 'XML::Simple
' =
> 'perl-XML-Simple
',
7193 for my $module (keys %rhelmodules) {
7194 eval
"use $module;
";
7196 my $pkg = $rhelmodules{$module};
7197 system(
"yum install -y $pkg
");
7198 eval
"use $module;
";
7202 my $errorsto =
'pere@hungry.com
';
7208 sub run_firmware_script {
7209 my ($opts, $script) = @_;
7211 print STDERR
"fail: missing script name\n
";
7214 print STDERR
"Running $script\n\n
";
7216 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7217 print STDERR
"success: firmware script ran succcessfully\n
";
7219 print STDERR
"fail: firmware script returned error\n
";
7223 sub run_firmware_scripts {
7224 my ($opts, @dirs) = @_;
7225 # Run firmware packages
7226 for my $dir (@dirs) {
7227 print STDERR
"info: Running scripts in $dir\n
";
7228 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7229 while (my $s = readdir $dh) {
7230 next if $s =~ m/^\.\.?/;
7231 run_firmware_script($opts,
"$dir/$s
");
7239 print STDERR
"info: Downloading $url\n
";
7240 system(
"wget --quiet \
"$url\
"");
7245 my $product = `dmidecode -s system-product-name`;
7248 if ($product =~ m/PowerEdge/) {
7250 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7251 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7253 my $tmpdir = tempdir(
7257 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7258 system(
'gunzip Catalog.xml.gz
');
7259 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7260 # -q is quiet, disabling interactivity and reducing console output
7261 my $fwopts =
"-q
";
7263 for my $url (@paths) {
7264 fetch_dell_fw($url);
7266 run_firmware_scripts($fwopts, $tmpdir);
7268 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7269 print STDERR
"error: Please report to $errorsto.\n
";
7273 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7274 print STDERR
"error: Please report to $errorsto.\n
";
7280 my $url =
"ftp://ftp.us.dell.com/$path
";
7284 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7285 # firmware packages to download from Dell. Only work for Linux
7286 # machines and
11th generation Dell servers.
7287 sub fetch_dell_fw_list {
7288 my $filename = shift;
7290 my $product = `dmidecode -s system-product-name`;
7292 my ($mybrand, $mymodel) = split(/\s+/, $product);
7294 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7296 my $xml = XMLin($filename);
7298 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7299 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7300 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7302 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7303 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7305 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7307 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7309 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7312 for my $component (@{$xml-
>{SoftwareComponent}}) {
7313 my $componenttype = $component-
>{ComponentType}-
>{value};
7315 # Drop application packages, only firmware and BIOS
7316 next if
'APAC
' eq $componenttype;
7318 my $cpath = $component-
>{path};
7319 for my $path (@paths) {
7320 if ($cpath =~ m%/$path$%) {
7321 push(@paths, $cpath);
7329 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7330 it could work on other platforms with some tweaking. Anyone know a
7331 index like Catalog.xml is available from HP for HP servers? At the
7332 moment I maintain a similar list manually and it is quickly getting
7338 <title>How is booting into runlevel
1 different from single user boots?
</title>
7339 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7340 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7341 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7342 <description><p
>Wouter Verhelst have some
7343 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7344 comments and opinions
</a
> on my blog post on
7345 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7346 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7347 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7348 default KDE desktop in Debian
</a
>. I only have time to address one
7349 small piece of his comment now, and though it best to address the
7350 misunderstanding he bring forward:
</p
>
7352 <p
><blockquote
>
7353 Currently, a system admin has four options: [...] boot to a
7354 single-user system (by adding
'single
' to the kernel command line;
7355 this runs rcS and rc1 scripts)
7356 </blockquote
></p
>
7358 <p
>This make me believe Wouter believe booting into single user mode
7359 and booting into runlevel
1 is the same. I am not surprised he
7360 believe this, because it would make sense and is a quite sensible
7361 thing to believe. But because the boot in Debian is slightly broken,
7362 runlevel
1 do not work properly and it isn
't the same as single user
7363 mode. I
'll try to explain what is actually happing, but it is a bit
7364 hard to explain.
</p
>
7366 <p
>Single user mode is defined like this in /etc/inittab:
7367 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7368 executed in single user mode is sulogin. Single user mode is a boot
7369 state
"between
" the runlevels, and when booting into single user mode,
7370 only the scripts in /etc/rcS.d/ are executed before the init process
7371 enters the single user state. When switching to runlevel
1, the state
7372 is in fact not ending in runlevel
1, but it passes through runlevel
1
7373 and end up in the single user mode (see /etc/rc1.d/S03single, which
7374 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7375 1. It is confusing that the
'S
' (single user) init mode is not the
7376 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7379 <p
>This summary might make it clearer. When booting for the first
7380 time into single user mode, the following commands are executed:
7381 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7382 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7383 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7384 trying to continue after visiting single user mode. Not all services
7385 are started again as they should, causing the machine to end up in an
7386 unpredicatble state. This is why Debian admins recommend rebooting
7387 after visiting single user mode.
</p
>
7389 <p
>A similar problem with runlevel
1 is caused by the amount of
7390 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7391 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7392 stopped when passing through the scripts in /etc/rc1.d/, and not
7393 started again when switching away from runlevel
1 to the runlevels
7394 2-
5. I believe the problem is best fixed by moving all the scripts
7395 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7396 functioning single user mode during boot.
</p
>
7398 <p
>I have spent several years investigating the Debian boot system,
7399 and discovered this problem a few years ago. I suspect it originates
7400 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7405 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7406 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7407 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7408 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7409 <description><p
>In the Debian boot system, several packages include scripts that
7410 are started from /etc/rcS.d/. In fact, there is a bite more of them
7411 than make sense, and this causes a few problems. What kind of
7412 problems, you might ask. There are at least two problems. The first
7413 is that it is not possible to recover a machine after switching to
7414 runlevel
1. One need to actually reboot to get the machine back to
7415 the expected state. The other is that single user boot will sometimes
7416 run into problems because some of the subsystems are activated before
7417 the root login is presented, causing problems when trying to recover a
7418 machine from a problem in that subsystem. A minor additional point is
7419 that moving more scripts out of rcS.d/ and into the other rc#.d/
7420 directories will increase the amount of scripts that can run in
7421 parallel during boot, and thus decrease the boot time.
</p
>
7423 <p
>So, which scripts should start from rcS.d/. In short, only the
7424 scripts that _have_ to execute before the root login prompt is
7425 presented during a single user boot should go there. Everything else
7426 should go into the numeric runlevels. This means things like
7427 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7428 the numeric runlevels. Today in Debian, there are around
115 init.d
7429 scripts that are started from rcS.d/, and most of them should be moved
7430 out. Do your package have one of them? Please help us make single
7431 user and runlevel
1 better by moving it.
</p
>
7433 <p
>Scripts setting up the screen, keyboard, system partitions
7434 etc. should still be started from rcS.d/, but there is for example no
7435 need to have the network enabled before the single user login prompt
7436 is presented.
</p
>
7438 <p
>As always, things are not so easy to fix as they sound. To keep
7439 Debian systems working while scripts migrate and during upgrades, the
7440 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7441 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7442 and the next ones can only be moved when their dependencies have been
7443 moved first. This migration must be done sequentially while we ensure
7444 that the package system upgrade packages in the right order to keep
7445 the system state correct. This will require some coordination when it
7446 comes to network related packages, but most of the packages with
7447 scripts that should migrate do not have anything in rcS.d/ depending
7448 on them. Some packages have already been updated, like the sudo
7449 package, while others are still left to do. I wish I had time to work
7450 on this myself, but real live constrains make it unlikely that I will
7451 find time to push this forward.
</p
>
7456 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7457 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7458 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7459 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7460 <description><p
>While at Debconf11, I have several times during discussions
7461 mentioned the issues I believe should be improved in Debian for its
7462 desktop to be useful for more people. The use case for this is my
7463 parents, which are currently running Kubuntu which solve the
7466 <p
>I suspect these four missing features are not very hard to
7467 implement. After all, they are present in Ubuntu, so if we wanted to
7468 do this in Debian we would have a source.
</p
>
7472 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7473 are new packages available for upgrades, a icon in the KDE status bar
7474 indicate this, and clicking on it will activate the simple upgrade
7475 tool to handle it. I have no problem guiding both of my parents
7476 through the process over the phone. If a kernel reboot is required,
7477 this too is indicated by the status bars and the upgrade tool. Last
7478 time I checked, nothing with the same features was working in KDE in
7481 <li
><strong
>Simple handling of missing Firefox browser
7482 plugins.
</strong
> When the browser encounter a MIME type it do not
7483 currently have a handler for, it will ask the user if the system
7484 should search for a package that would add support for this MIME type,
7485 and if the user say yes, the APT sources will be searched for packages
7486 advertising the MIME type in their control file (visible in the
7487 Packages file in the APT archive). If one or more packages are found,
7488 it is a simple click of the mouse to add support for the missing mime
7489 type. If the package require the user to accept some non-free
7490 license, this is explained to the user. The entire process make it
7491 more clear to the user why something do not work in the browser, and
7492 make the chances higher for the user to blame the web page authors and
7493 not the browser for any missing features.
</li
>
7495 <li
><strong
>Simple handling of missing multimedia codec/format
7496 handlers.
</strong
> When the media players encounter a format or codec
7497 it is not supporting, a dialog pop up asking the user if the system
7498 should search for a package that would add support for it. This
7499 happen with things like MP3, Windows Media or H
.264. The selection
7500 and installation procedure is very similar to the Firefox browser
7501 plugin handling. This is as far as I know implemented using a
7502 gstreamer hook. The end result is that the user easily get access to
7503 the codecs that are present from the APT archives available, while
7504 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7506 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7507 displaying a text/plain file in my Debian browser, it will propose to
7508 start emacs to show it. If I remember correctly, when doing the same
7509 in Kunbutu it show the file as a text file in the browser. At least I
7510 know Opera will show text files within the browser. I much prefer the
7511 latter behaviour.
</li
>
7515 <p
>There are other nice features as well, like the simplified suite
7516 upgrader, but given that I am the one mostly doing the dist-upgrade,
7517 it do not matter much.
</p
>
7519 <p
>I really hope we could get these features in place for the next
7520 Debian release. It would require the coordinated effort of several
7521 maintainers, but would make the end user experience a lot better.
</p
>
7526 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7527 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7528 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7529 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7530 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7531 site is build on Debian/Squeeze, and this platform was chosen because
7532 I am most familiar with Debian (being a Debian Developer for around
10
7533 years) because it is the latest stable Debian release which should get
7534 security support for a few years.
</p
>
7536 <p
>The web service is written in Perl, and depend on some perl modules
7537 that are missing in Debian at the moment. It would be great if these
7538 modules were added to the Debian archive, allowing anyone to set up
7539 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7540 in their own country using only Debian packages. The list of modules
7541 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7542 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7543 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7544 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7545 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7546 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7547 easier in the future.
</p
>
7549 <p
>Thanks to the great tools in Debian, getting the missing modules
7550 installed on my server was a simple call to
'cpan2deb Module::Name
'
7551 and
'dpkg -i
' to install the resulting package. But this leave me
7552 with the responsibility of tracking security problems, which I really
7553 do not have time for.
</p
>
7558 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7559 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7561 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7562 <description><p
>Here is a small update for my English readers. Most of my blog
7563 posts have been in Norwegian the last few weeks, so here is a short
7564 update in English.
</p
>
7566 <p
>The kids still keep me too busy to get much free software work
7567 done, but I did manage to organise a project to get a Norwegian port
7568 of the British service
7569 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7570 and it has been running for a month now. The entire project has been
7571 organised by me and two others. Around Christmas we gathered sponsors
7572 to fund the development work. In January I drafted a contract with
7573 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7574 and in February the development took place. Most of it involved
7575 converting the source to use GPS coordinates instead of British
7576 easting/northing, and the resulting code should be a lot easier to get
7577 running in any country by now. The Norwegian
7578 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7579 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7580 source and the source for administrative borders in Norway, and
7581 support for this had to be added/fixed.
</p
>
7583 <p
>The Norwegian version went live March
3th, and we spent the weekend
7584 polishing the system before we announced it March
7th. The system is
7585 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7586 problem reports in a few weeks. Soon we hope to announce the Android
7587 and iPhone versions making it even easier to report problems with the
7588 public infrastructure.
</p
>
7590 <p
>Perhaps something to consider for those of you in countries without
7591 such service?
</p
>
7596 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7597 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7599 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7600 <description><p
>The last few days I have looked at ways to track open security
7601 issues here at my work with the University of Oslo. My idea is that
7602 it should be possible to use the information about security issues
7603 available on the Internet, and check our locally
7604 maintained/distributed software against this information. It should
7605 allow us to verify that no known security issues are forgotten. The
7606 CVE database listing vulnerabilities seem like a great central point,
7607 and by using the package lists from Debian mapped to CVEs provided by
7608 the testing security team, I believed it should be possible to figure
7609 out which security holes were present in our free software
7610 collection.
</p
>
7612 <p
>After reading up on the topic, it became obvious that the first
7613 building block is to be able to name software packages in a unique and
7614 consistent way across data sources. I considered several ways to do
7615 this, for example coming up with my own naming scheme like using URLs
7616 to project home pages or URLs to the Freshmeat entries, or using some
7617 existing naming scheme. And it seem like I am not the first one to
7618 come across this problem, as MITRE already proposed and implemented a
7619 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7620 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7621 software, hardware and other platform components. The CPE ids are
7622 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7623 Vulnerability Database
</a
>, allowing me to look up know security
7624 issues for any CPE name. With this in place, all I need to do is to
7625 locate the CPE id for the software packages we use at the university.
7626 This is fairly trivial (I google for
'cve cpe $package
' and check the
7627 NVD entry if a CVE for the package exist).
</p
>
7629 <p
>To give you an example. The GNU gzip source package have the CPE
7630 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7631 check out, one could look up
7632 <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
7633 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7634 The most recent one is
7635 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7636 and at the bottom of the NVD page for this vulnerability the complete
7637 list of affected versions is provided.
</p
>
7639 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7640 for offline processing of issues. Using this dump, I
've written a
7641 small script taking a list of CPEs as input and list all CVEs
7642 affecting the packages represented by these CPEs. One give it CPEs
7643 with version numbers as specified above and get a list of open
7644 security issues out.
</p
>
7646 <p
>Of course for this approach to be useful, the quality of the NVD
7647 information need to be high. For that to happen, I believe as many as
7648 possible need to use and contribute to the NVD database. I notice
7650 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7651 map from CVE to CPE
</a
>, indicating that they are using the CPE
7652 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7654 <p
>To get an idea about the quality for free software, I spent some
7655 time making it possible to compare the CVE database from Debian with
7656 the CVE database in NVD. The result look fairly good, but there are
7657 some inconsistencies in NVD (same software package having several
7658 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7659 Debian believe are affected by a CVE). Hope to find time to improve
7660 the quality of NVD, but that require being able to get in touch with
7661 someone maintaining it. So far my three emails with questions and
7662 corrections have not seen any reply, but I hope contact can be
7663 established soon.
</p
>
7665 <p
>An interesting application for CPEs is cross platform package
7666 mapping. It would be useful to know which packages in for example
7667 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7668 this would be trivial if all linux distributions provided CPE entries
7669 for their packages.
</p
>
7674 <title>Which module is loaded for a given PCI and USB device?
</title>
7675 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7676 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7677 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7678 <description><p
>In the
7679 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7680 package in Debian, there is a script to report useful information
7681 about the running hardware for use when people report missing
7682 information. One part of this script that I find very useful when
7683 debugging hardware problems, is the part mapping loaded kernel module
7684 to the PCI device it claims. It allow me to quickly see if the kernel
7685 module I expect is driving the hardware I am struggling with. To see
7686 the output, make sure discover-data is installed and run
7687 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7688 one of my machines like this:
</p
>
7692 10de:
03eb i2c_nforce2
7695 10de:
03f0 snd_hda_intel
7704 <p
>The code in question look like this, slightly modified for
7705 readability and to drop the output to file descriptor
3:
</p
>
7708 if [ -d /sys/bus/pci/devices/ ] ; then
7709 echo loaded pci modules:
7711 cd /sys/bus/pci/devices/
7712 for address in * ; do
7713 if [ -d
"$address/driver/module
" ] ; then
7714 module=`cd $address/driver/module ; pwd -P | xargs basename`
7715 if grep -q
"^$module
" /proc/modules ; then
7716 address=$(echo $address |sed s/
0000://)
7717 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7718 echo
"$id $module
"
7727 <p
>Similar code could be used to extract USB device module
7731 if [ -d /sys/bus/usb/devices/ ] ; then
7732 echo loaded usb modules:
7734 cd /sys/bus/usb/devices/
7735 for address in * ; do
7736 if [ -d
"$address/driver/module
" ] ; then
7737 module=`cd $address/driver/module ; pwd -P | xargs basename`
7738 if grep -q
"^$module
" /proc/modules ; then
7739 address=$(echo $address |sed s/
0000://)
7740 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7741 if [
"$id
" ] ; then
7742 echo
"$id $module
"
7752 <p
>This might perhaps be something to include in other tools as
7758 <title>How to test if a laptop is working with Linux
</title>
7759 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7760 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7761 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7762 <description><p
>The last few days I have spent at work here at the
<a
7763 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7764 batch of computers will work with Linux. Every year for the last few
7765 years the university have organised shared bid of a few thousand
7766 computers, and this year HP won the bid. Two different desktops and
7767 five different laptops are on the list this year. We in the UNIX
7768 group want to know which one of these computers work well with RHEL
7769 and Ubuntu, the two Linux distributions we currently handle at the
7770 university.
</p
>
7772 <p
>My test method is simple, and I share it here to get feedback and
7773 perhaps inspire others to test hardware as well. To test, I PXE
7774 install the OS version of choice, and log in as my normal user and run
7775 a few applications and plug in selected pieces of hardware. When
7776 something fail, I make a note about this in the test matrix and move
7777 on. If I have some spare time I try to report the bug to the OS
7778 vendor, but as I only have the machines for a short time, I rarely
7779 have the time to do this for all the problems I find.
</p
>
7781 <p
>Anyway, to get to the point of this post. Here is the simple tests
7782 I perform on a new model.
</p
>
7786 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7787 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7788 RHEL5 and Debian Edu/Squeeze.
</li
>
7790 <li
>Is X.org working? If the graphical login screen show up after
7791 installation, X.org is working.
</li
>
7793 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7794 package mesa-utils on Ubuntu) and writing down the frames per second
7795 reported by the program.
</li
>
7797 <li
>Is sound working? With Gnome and KDE, a sound is played when
7798 logging in, and if I can hear this the test is successful. If there
7799 are several audio exits on the machine, I try them all and check if
7800 the Gnome/KDE audio mixer can control where to send the sound. I
7801 normally test this by playing
7802 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7803 video
</a
> in Firefox/Iceweasel.
</li
>
7805 <li
>Is the USB subsystem working? I test this by plugging in a USB
7806 memory stick and see if Gnome/KDE notices this.
</li
>
7808 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7809 I have lying around, and see if Gnome/KDE notices this.
</li
>
7811 <li
>Is any built in camera working? Test using cheese, and see if a
7812 picture from the v4l device show up.
</li
>
7814 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7815 any bluetooth devices are discovered. In my office, I normally see a
7818 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7819 memory modules lying around, and stick them in and see if Gnome/KDE
7820 notice this.
</li
>
7822 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7823 special button work, and if the laptop continue to work after
7826 <li
>For laptops, is the extra buttons working, like audio level,
7827 adjusting background light, switching on/off external video output,
7828 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7829 laptop to laptop, so I just write down which are working and which are
7832 <li
>Some laptops have smart card readers, finger print readers,
7833 acceleration sensors etc. I rarely test these, as I do not know how
7834 to quickly test if they are working or not, so I only document their
7835 existence.
</li
>
7839 <p
>By now I suspect you are really curious what the test results are
7840 for the HP machines I am testing. I
'm not done yet, so I will report
7841 the test results later. For now I can report that HP
8100 Elite work
7842 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7843 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7844 can see, I have most machines left to test. One interesting
7845 observation is that Ubuntu Lucid has almost twice the frame rate than
7846 RHEL6 with glxgears. No idea why.
</p
>
7851 <title>Some thoughts on BitCoins
</title>
7852 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7854 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7855 <description><p
>As I continue to explore
7856 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7857 what properties the system have, and how it will be affected by laws
7858 and regulations here in Norway. Here are some random notes.
</p
>
7860 <p
>One interesting thing to note is that since the transactions are
7861 verified using a peer to peer network, all details about a transaction
7862 is known to everyone. This means that if a BitCoin address has been
7863 published like I did with mine in my initial post about BitCoin, it is
7864 possible for everyone to see how many BitCoins have been transfered to
7865 that address. There is even a web service to look at the details for
7866 all transactions. There I can see that my address
7867 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7868 have received
16.06 Bitcoin, the
7869 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7870 address of Simon Phipps have received
181.97 BitCoin and the address
7871 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7872 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7873 every one of you that donated bitcoins to support my activity. The
7874 fact that anyone can see how much money was transfered to a given
7875 address make it more obvious why the BitCoin community recommend to
7876 generate and hand out a new address for each transaction. I
'm told
7877 there is no way to track which addresses belong to a given person or
7878 organisation without the person or organisation revealing it
7879 themselves, as Simon, EFF and I have done.
</p
>
7881 <p
>In Norway, and in most other countries, there are laws and
7882 regulations limiting how much money one can transfer across the border
7883 without declaring it. There are money laundering, tax and accounting
7884 laws and regulations I would expect to apply to the use of BitCoin.
7885 If the Skolelinux foundation
7886 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7887 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7888 normal bank transfers like EFF is doing, how should this be accounted?
7889 Given that it is impossible to know if money can cross the border or
7890 not, should everything or nothing be declared? What exchange rate
7891 should be used when calculating taxes? Would receivers have to pay
7892 income tax if the foundation were to pay Skolelinux contributors in
7893 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7895 <p
>For a currency to be useful and successful, it must be trusted and
7896 accepted by a lot of users. It must be possible to get easy access to
7897 the currency (as a wage or using currency exchanges), and it must be
7898 easy to spend it. At the moment BitCoin seem fairly easy to get
7899 access to, but there are very few places to spend it. I am not really
7900 a regular user of any of the vendor types currently accepting BitCoin,
7901 so I wonder when my kind of shop would start accepting BitCoins. I
7902 would like to buy electronics, travels and subway tickets, not herbs
7903 and books. :) The currency is young, and this will improve over time
7904 if it become popular, but I suspect regular banks will start to lobby
7905 to get BitCoin declared illegal if it become popular. I
'm sure they
7906 will claim it is helping fund terrorism and money laundering (which
7907 probably would be true, as is any currency in existence), but I
7908 believe the problems should be solved elsewhere and not by blaming
7909 currencies.
</p
>
7911 <p
>The process of creating new BitCoins is called mining, and it is
7912 CPU intensive process that depend on a bit of luck as well (as one is
7913 competing against all the other miners currently spending CPU cycles
7914 to see which one get the next lump of cash). The
"winner
" get
50
7915 BitCoin when this happen. Yesterday I came across the obvious way to
7916 join forces to increase ones changes of getting at least some coins,
7917 by coordinating the work on mining BitCoins across several machines
7918 and people, and sharing the result if one is lucky and get the
50
7920 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7921 if this sounds interesting. I have not had time to try to set up a
7922 machine to participate there yet, but have seen that running on ones
7923 own for a few days have not yield any BitCoins througth mining
7926 <p
>Update
2010-
12-
15: Found an
<a
7927 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7928 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7929 it was interesting to read. The arguments presented seem to be
7930 equally valid for gold, which was used as a currency for many years.
</p
>
7935 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7936 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7937 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7938 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7939 <description><p
>With this weeks lawless
7940 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7941 attacks
</a
> on Wikileak and
7942 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7943 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7944 not be trusted to handle money transactions.
7946 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7947 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7948 mine mentioned earlier. I decided to follow Simon
's example, and get
7949 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7950 some help from my friend to get it all running, and he even handed me
7951 some bitcoins to get started. I even donated a few bitcoins to Simon
7952 for helping me remember BitCoin.
</p
>
7954 <p
>So, what is bitcoins, you probably wonder? It is a digital
7955 crypto-currency, decentralised and handled using peer-to-peer
7956 networks. It allows anonymous transactions and prohibits central
7957 control over the transactions, making it impossible for governments
7958 and companies alike to block donations and other transactions. The
7959 source is free software, and while the key dependency wxWidgets
2.9
7960 for the graphical user interface is missing in Debian, the command
7961 line client builds just fine. Hopefully Jonas
7962 <a href=
"http://bugs.debian.org/
578157">will get the package into
7963 Debian
</a
> soon.
</p
>
7965 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7966 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7967 bitcoins
</a
> when selling services and goods, and there are even
7968 currency
"stock
" markets where the exchange rate is decided. There
7969 are not many users so far, but the concept seems promising. If you
7970 want to get started and lack a friend with any bitcoins to spare,
7972 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7973 bitcoin at the time of writing). Use
7974 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7975 on the current exchange rates.
</p
>
7977 <p
>As an experiment, I have decided to set up bitcoind on one of my
7978 machines. If you want to support my activity, please send Bitcoin
7979 donations to the address
7980 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7985 <title>Why isn
't Debian Edu using VLC?
</title>
7986 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7988 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7989 <description><p
>In the latest issue of Linux Journal, the readers choices were
7990 presented, and the winner among the multimedia player were VLC.
7991 Personally, I like VLC, and it is my player of choice when I first try
7992 to play a video file or stream. Only if VLC fail will I drag out
7993 gmplayer to see if it can do better. The reason is mostly the failure
7994 model and trust. When VLC fail, it normally pop up a error message
7995 reporting the problem. When mplayer fail, it normally segfault or
7996 just hangs. The latter failure mode drain my trust in the program.
<p
>
7998 <p
>But even if VLC is my player of choice, we have choosen to use
7999 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8000 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8001 plugin to play web videos seamlessly, and the VLC browser plugin is
8002 not very good. For example, it lack in-line control buttons, so there
8003 is no way for the user to pause the video. Also, when I
8004 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8005 tested the browser plugins
</a
> available in Debian, the VLC plugin
8006 failed on several video pages where mplayer based plugins worked. If
8007 the browser plugin for VLC was as good as the gecko-mediaplayer
8008 package (which uses mplayer), we would switch.
</P
>
8010 <p
>While VLC is a good player, its user interface is slightly
8011 annoying. The most annoying feature is its inconsistent use of
8012 keyboard shortcuts. When the player is in full screen mode, its
8013 shortcuts are different from when it is playing the video in a window.
8014 For example, space only work as pause when in full screen mode. I
8015 wish it had consisten shortcuts and that space also would work when in
8016 window mode. Another nice shortcut in gmplayer is [enter] to restart
8017 the current video. It is very nice when playing short videos from the
8018 web and want to restart it when new people arrive to have a look at
8019 what is going on.
</p
>
8024 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8025 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8026 <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>
8027 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8028 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8029 upgrade testing of the
8030 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8031 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8032 This seem like a very good idea, so I adjusted by test scripts and
8033 can now present the updated result from today:
</p
>
8035 <p
>This is for Gnome:
</p
>
8037 <p
>Installed using apt-get, missing with aptitude
</p
>
8039 <blockquote
><p
>
8044 browser-plugin-gnash
8051 freedesktop-sound-theme
8053 gconf-defaults-service
8068 gnome-desktop-environment
8072 gnome-session-canberra
8077 gstreamer0.10-fluendo-mp3
8083 libapache2-mod-dnssd
8086 libaprutil1-dbd-sqlite3
8089 libboost-date-time1.42
.0
8090 libboost-python1.42
.0
8091 libboost-thread1.42
.0
8093 libchamplain-gtk-
0.4-
0
8095 libclutter-gtk-
0.10-
0
8102 libfreerdp-plugins-standard
8117 libgnomepanel2.24-cil
8122 libgtksourceview2.0-common
8123 libmono-addins-gui0.2-cil
8124 libmono-addins0.2-cil
8125 libmono-cairo2.0-cil
8126 libmono-corlib2.0-cil
8127 libmono-i18n-west2.0-cil
8128 libmono-posix2.0-cil
8129 libmono-security2.0-cil
8130 libmono-sharpzip2.84-cil
8131 libmono-system2.0-cil
8134 libndesk-dbus-glib1.0-cil
8135 libndesk-dbus1.0-cil
8145 libtelepathy-farsight0
8154 nautilus-sendto-empathy
8158 python-aptdaemon-gtk
8160 python-beautifulsoup
8175 python-gtksourceview2
8186 python-pkg-resources
8193 python-twisted-conch
8199 python-zope.interface
8204 rhythmbox-plugin-cdrecorder
8211 system-config-printer-udev
8213 telepathy-mission-control-
5
8224 </p
></blockquote
>
8226 <p
>Installed using apt-get, removed with aptitude
</p
>
8228 <blockquote
><p
>
8234 fast-user-switch-applet
8253 libgtksourceview2.0-
0
8255 libsdl1.2debian-alsa
8261 system-config-printer
8266 </p
></blockquote
>
8268 <p
>Installed using aptitude, missing with apt-get
</p
>
8270 <blockquote
><p
>
8271 gstreamer0.10-gnomevfs
8272 </p
></blockquote
>
8274 <p
>Installed using aptitude, removed with apt-get
</p
>
8276 <blockquote
><p
>
8278 </p
></blockquote
>
8280 <p
>This is for KDE:
</p
>
8282 <p
>Installed using apt-get, missing with aptitude
</p
>
8284 <blockquote
><p
>
8286 </p
></blockquote
>
8288 <p
>Installed using apt-get, removed with aptitude
</p
>
8290 <blockquote
><p
>
8293 </p
></blockquote
>
8295 <p
>Installed using aptitude, missing with apt-get
</p
>
8297 <blockquote
><p
>
8311 kdeartwork-emoticons
8313 kdeartwork-theme-icon
8317 kdebase-workspace-bin
8318 kdebase-workspace-data
8332 kscreensaver-xsavers
8347 plasma-dataengines-workspace
8349 plasma-desktopthemes-artwork
8350 plasma-runners-addons
8351 plasma-scriptengine-googlegadgets
8352 plasma-scriptengine-python
8353 plasma-scriptengine-qedje
8354 plasma-scriptengine-ruby
8355 plasma-scriptengine-webkit
8356 plasma-scriptengines
8357 plasma-wallpapers-addons
8358 plasma-widget-folderview
8359 plasma-widget-networkmanagement
8363 xscreensaver-data-extra
8365 xscreensaver-gl-extra
8366 xscreensaver-screensaver-bsod
8367 </p
></blockquote
>
8369 <p
>Installed using aptitude, removed with apt-get
</p
>
8371 <blockquote
><p
>
8373 google-gadgets-common
8391 libggadget-qt-
1.0-
0b
8396 libkonqsidebarplugin4a
8405 libplasma-geolocation-interface4
8407 libplasmagenericshell4
8421 libsmokeknewstuff2-
3
8422 libsmokeknewstuff3-
3
8424 libsmokektexteditor3
8432 libsmokeqtnetwork4-
3
8438 libsmokeqtuitools4-
3
8450 plasma-dataengines-addons
8451 plasma-scriptengine-superkaramba
8452 plasma-widget-lancelot
8453 plasma-widgets-addons
8454 plasma-widgets-workspace
8458 update-notifier-common
8459 </p
></blockquote
>
8461 <p
>Running apt-get autoremove made the results using apt-get and
8462 aptitude a bit more similar, but there are still quite a lott of
8463 differences. I have no idea what packages should be installed after
8464 the upgrade, but hope those that do can have a look.
</p
>
8469 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8470 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8471 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8472 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8473 <description><p
>Most of the computers in use by the
8474 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8475 are virtual machines. And they have been Xen machines running on a
8476 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8477 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8478 bit harder that it could have been, because we set up the Xen virtual
8479 machines to get the virtual partitions from LVM, which as far as I
8480 know is not supported by KVM. So to migrate, we had to convert
8481 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8484 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8485 nice recipe
</a
> to do this, and wrote the following script to do the
8486 migration. It uses qemu-img from the qemu package to make the disk
8487 image, parted to partition it, losetup and kpartx to present the disk
8488 image partions as devices, and dd to copy the data. I NFS mounted the
8489 new servers storage area on the old server to do the migration.
</p
>
8495 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8500 if [ -z
"$
1" ] ; then
8501 echo
"Usage: $
0 &lt;hostname
&gt;
"
8507 if [ ! -e /dev/vg_data/$host-disk ] ; then
8508 echo
"error: unable to find LVM volume for $host
"
8512 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8513 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8514 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8515 totalsize=$(( ( $disksize + $swapsize ) ))
8518 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8519 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8521 parted $img mklabel msdos
8522 parted $img mkpart primary linux-swap
0 $disksize
8523 parted $img mkpart primary ext2 $disksize $totalsize
8524 parted $img set
1 boot on
8527 losetup /dev/loop0 $img
8528 kpartx -a /dev/loop0
8530 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8531 fsck.ext3 -f /dev/mapper/loop0p1 || true
8532 mkswap /dev/mapper/loop0p2
8534 kpartx -d /dev/loop0
8535 losetup -d /dev/loop0
8538 <p
>The script is perhaps so simple that it is not copyrightable, but
8539 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8541 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8542 the new disk image attached, installed grub-pc and linux-image-
686 and
8543 set up grub to boot from the disk image. After this, the KVM machines
8544 seem to work just fine.
</p
>
8549 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8550 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8551 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8552 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8553 <description><p
>I
'm still running upgrade testing of the
8554 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8555 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8556 status. Here is a short update based on a test I ran
20101118.
</p
>
8558 <p
>I still do not know what a correct migration should look like, so I
8559 report any differences between apt and aptitude and hope someone else
8560 can see if anything should be changed.
</p
>
8562 <p
>This is for Gnome:
</p
>
8564 <p
>Installed using apt-get, missing with aptitude
</p
>
8566 <blockquote
><p
>
8567 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8568 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8569 dmz-cursor-theme empathy empathy-common finger
8570 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8571 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8572 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8573 gnome-cards-data gnome-codec-install gnome-core
8574 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8575 gnome-search-tool gnome-session-canberra gnome-spell
8576 gnome-system-log gnome-themes-extras gnome-themes-more
8577 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8578 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8579 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8580 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8581 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8582 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8583 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8584 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8585 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8586 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8587 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8588 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8589 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8590 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8591 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8592 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8593 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8594 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8595 libmono-security2.0-cil libmono-sharpzip2.84-cil
8596 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8597 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8598 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8599 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8600 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8601 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8602 libxalan2-java libxerces2-java media-player-info mesa-utils
8603 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8604 nautilus-sendto-empathy openoffice.org-writer2latex
8605 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8606 python-aptdaemon python-aptdaemon-gtk python-axiom
8607 python-beautifulsoup python-bugbuddy python-clientform
8608 python-coherence python-configobj python-crypto python-cupshelpers
8609 python-cupsutils python-eggtrayicon python-elementtree
8610 python-epsilon python-evolution python-feedparser python-gdata
8611 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8612 python-gtksourceview2 python-httplib2 python-louie python-mako
8613 python-markupsafe python-mechanize python-nevow python-notify
8614 python-opengl python-openssl python-pam python-pkg-resources
8615 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8616 python-tagpy python-twisted-bin python-twisted-conch
8617 python-twisted-core python-twisted-web python-utidylib python-webkit
8618 python-xdg python-zope.interface remmina remmina-plugin-data
8619 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8620 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8621 software-center svgalibg1 system-config-printer-udev
8622 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8623 totem totem-coherence totem-mozilla totem-plugins
8624 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8626 </p
></blockquote
>
8628 Installed using apt-get, removed with aptitude
8630 <blockquote
><p
>
8631 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8632 epiphany-extensions epiphany-gecko evolution-exchange
8633 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8634 gedit-common gnome-app-install gnome-games gnome-games-data
8635 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8636 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8637 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8638 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8639 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8640 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8641 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8642 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8643 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8644 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8645 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8646 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8647 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8648 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8649 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8650 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8651 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8652 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8653 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8654 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8655 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8656 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8657 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8658 sound-juicer swfdec-gnome system-config-printer totem-common
8659 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8660 </p
></blockquote
>
8662 <p
>Installed using aptitude, missing with apt-get
</p
>
8664 <blockquote
><p
>
8665 gstreamer0.10-gnomevfs
8666 </p
></blockquote
>
8668 <p
>Installed using aptitude, removed with apt-get
</p
>
8670 <blockquote
><p
>
8672 </p
></blockquote
>
8674 <p
>This is for KDE:
</p
>
8676 <p
>Installed using apt-get, missing with aptitude
</p
>
8678 <blockquote
><p
>
8679 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8680 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8681 ghostscript-x git gnome-audio gnugo granatier gs-common
8682 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8683 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8684 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8685 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8686 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8687 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8688 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8689 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8690 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8691 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8692 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8693 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8694 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8695 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8696 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8697 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8698 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8699 libkrossui4 libmailtools-perl libmime-tools-perl
8700 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8701 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8702 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8703 lirc luatex marble networkstatus noatun-plugins
8704 openoffice.org-writer2latex palapeli palapeli-data parley
8705 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8706 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8707 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8709 </p
></blockquote
>
8711 <p
>Installed using apt-get, removed with aptitude
</p
>
8713 <blockquote
><p
>
8714 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8715 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8716 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8717 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8718 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8719 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8720 kitchensync kiten kjumpingcube klatin klettres klickety klines
8721 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8722 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8723 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8724 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8725 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8726 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8727 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8728 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8729 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8730 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8731 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8732 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8733 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8734 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8735 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8736 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8737 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8738 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8739 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8740 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8741 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8742 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8743 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8744 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8745 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8746 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8747 </p
></blockquote
>
8749 <p
>Installed using aptitude, missing with apt-get
</p
>
8751 <blockquote
><p
>
8752 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8753 kdeartwork kdebase kdebase-apps kdebase-workspace
8754 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8755 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8756 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8757 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8758 xscreensaver-screensaver-bsod
8759 </p
></blockquote
>
8761 <p
>Installed using aptitude, removed with apt-get
</p
>
8763 <blockquote
><p
>
8764 kdebase-bin konq-plugins konqueror
8765 </p
></blockquote
>
8770 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8771 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8773 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8774 <description><p
>Answering
8775 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8776 call from the Gnash project
</a
> for
8777 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8778 current source, I have set up a virtual KVM machine on the Debian
8779 Edu/Skolelinux virtualization host to test the git source on
8780 Debian/Squeeze. I hope this can help the developers in getting new
8781 releases out more often.
</p
>
8783 <p
>As the developers want less main-stream build platforms tested to,
8784 I have considered setting up a
<a
8785 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8786 machine as well. I have also considered using the kfreebsd
8787 architecture in Debian as a file server in NUUG to get access to the
5
8788 TB zfs volume we currently use to store DV video. Because of this, I
8789 finally got around to do a test installation of Debian/Squeeze with
8790 kfreebsd. Installation went fairly smooth, thought I noticed some
8791 visual glitches in the cdebconf dialogs (black cursor left on the
8792 screen at random locations). Have not gotten very far with the
8793 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8794 fatal problem. Have to spend some more time on it to see if it is
8795 useful as a file server for NUUG. Will try to find time to set up a
8796 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8801 <title>Debian in
3D
</title>
8802 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8803 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8804 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8805 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8807 <p
>3D printing is just great. I just came across this Debian logo in
8809 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8810 thingiverse blog
</a
>.
</p
>
8815 <title>Software updates
2010-
10-
24</title>
8816 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8817 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8818 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8819 <description><p
>Some updates.
</p
>
8821 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8822 raise money for the project is going well. The lower limit of
10
8823 signers was reached in
24 hours, and so far
13 people have signed it.
8824 More signers and more funding is most welcome, and I am really curious
8825 how far we can get before the time limit of December
24 is reached.
8828 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8829 about what appear to be a great code coverage tool capable of
8830 generating code coverage stats without any changes to the source code.
8832 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8833 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8834 It is missing in Debian, but the git source built just fine in Squeeze
8835 after I installed libelf-dev, libdwarf-dev, pkg-config and
8836 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8837 solvable. I hope kcov make it into Debian soon.
</p
>
8839 <p
>Finally found time to wrap up the release notes for
<a
8840 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8841 new alpha release of Debian Edu
</a
>, and just published the second
8842 alpha test release of the Squeeze based Debian Edu /
8843 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8844 release. Give it a try if you need a complete linux solution for your
8845 school, including central infrastructure server, workstations, thin
8846 client servers and diskless workstations. A nice touch added
8847 yesterday is RDP support on the thin client servers, for windows
8848 clients to get a Linux desktop on request.
</p
>
8853 <title>Some notes on Flash in Debian and Debian Edu
</title>
8854 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8855 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8856 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8857 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8858 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8859 second most popular used package that is missing in Debian. The sixth
8860 most popular is flashplayer-mozilla. This is a clear indication that
8861 working flash is important for Debian users. Around
10 percent of the
8862 users submitting data to popcon.debian.org have this package
8863 installed.
</p
>
8865 <p
>In the report written by Lars Risan in August
2008
8866 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8867 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8868 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8869 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8870 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8871 web sites require Flash to work, and lacking working Flash support in
8872 the web browser and the problems with installing it was perceived as a
8873 good reason to stay with Windows.
</p
>
8875 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8876 said to be the retarded cousin that did not really understand
8877 everything you told him but could work fairly well. This was a
8878 comment regarding the problems Linux have with proprietary formats and
8879 non-standard web pages, and is sad because it exposes a fairly common
8880 understanding of whose fault it is if web pages that only work in for
8881 example Internet Explorer
6 fail to work on Firefox, and funny because
8882 it explain very well how annoying it is for users when Linux
8883 distributions do not work with the documents they receive or the web
8884 pages they want to visit.
</p
>
8886 <p
>This is part of the reason why I believe it is important for Debian
8887 and Debian Edu to have a well working Flash implementation in the
8888 distribution, to get at least popular sites as Youtube and Google
8889 Video to working out of the box. For Squeeze, Debian have the chance
8890 to include the latest version of Gnash that will make this happen, as
8891 the new release
0.8.8 was published a few weeks ago and is resting in
8892 unstable. The new version work with more sites that version
0.8.7.
8893 The Gnash maintainers have asked for a freeze exception, but the
8894 release team have not had time to reply to it yet. I hope they agree
8895 with me that Flash is important for the Debian desktop users, and thus
8896 accept the new package into Squeeze.
</p
>
8901 <title>Circular package dependencies harms apt recovery
</title>
8902 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8903 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8904 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8905 <description><p
>I discovered this while doing
8906 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8907 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8908 in Debian still got circular dependencies, and it is often claimed
8909 that apt and aptitude should be able to handle this just fine, but
8910 some times these dependency loops causes apt to fail.
</p
>
8912 <p
>An example is from todays
8913 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8914 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8915 causes perl-modules to fail to upgrade. The cause is simple. If a
8916 package fail to unpack, then only part of packages with the circular
8917 dependency might end up being unpacked when unpacking aborts, and the
8918 ones already unpacked will fail to configure in the recovery phase
8919 because its dependencies are unavailable.
</p
>
8921 <p
>In this log, the problem manifest itself with this error:
</p
>
8923 <blockquote
><pre
>
8924 dpkg: dependency problems prevent configuration of perl-modules:
8925 perl-modules depends on perl (
>=
5.10.1-
1); however:
8926 Version of perl on system is
5.10.0-
19lenny
2.
8927 dpkg: error processing perl-modules (--configure):
8928 dependency problems - leaving unconfigured
8929 </pre
></blockquote
>
8931 <p
>The perl/perl-modules circular dependency is already
8932 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8933 hopefully be solved as soon as possible, but it is not the only one,
8934 and each one of these loops in the dependency tree can cause similar
8935 failures. Of course, they only occur when there are bugs in other
8936 packages causing the unpacking to fail, but it is rather nasty when
8937 the failure of one package causes the problem to become worse because
8938 of dependency loops.
</p
>
8941 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8942 tireless effort by Bill Allombert
</a
>, the number of circular
8944 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8945 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8947 <p
>Todays testing also exposed a bug in
8948 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8949 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8950 apt-get and aptitude, the latter possibly caused by some circular
8951 dependency. Reported both to BTS to try to get someone to look at
8957 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8958 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8959 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8960 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8961 <description><p
>This is a
8962 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8964 <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
8966 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8967 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8969 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8970 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8971 and dhcp3-server-ldap in Debian use the LDAP server. The two
8972 implementations are quite different in how they use LDAP.
</p
>
8974 To get this information, I started slapd with debugging enabled and
8975 dumped the debug output to a file to get the LDAP searches performed
8976 on a Debian Edu main-server. Here is a summary.
8978 <p
><strong
>powerdns
</strong
></p
>
8980 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8981 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8984 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8985 One
"strict
" mode where the forward and reverse DNS lookups are done
8986 using the same LDAP objects, and a
"tree
" mode where the forward and
8987 reverse entries are in two different subtrees in LDAP with a structure
8988 based on the DNS names, as in tjener.intern and
8989 2.2.0.10.in-addr.arpa.
</p
>
8991 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8992 base, and uses a
"base
" scoped search for the DNS name by adding
8993 "dc=tjener,dc=intern,
" to the base with a filter for
8994 "(associateddomain=tjener.intern)
" for the forward entry and
8995 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8996 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8997 forward entries, it is looking for attributes named dnsttl, arecord,
8998 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8999 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9000 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9001 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9002 spfrecord and modifytimestamp. For reverse entries it is looking for
9003 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9004 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9005 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9006 ldapsearch commands could look like this:
</p
>
9008 <blockquote
><pre
>
9009 ldapsearch -h ldap \
9010 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9011 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9012 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9013 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9014 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9015 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9017 ldapsearch -h ldap \
9018 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9019 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9020 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9021 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9022 srvrecord naptrrecord modifytimestamp
9023 </pre
></blockquote
>
9025 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9026 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9027 example LDAP objects used there. In addition to these objects, the
9028 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9029 also exist.
</p
>
9031 <blockquote
><pre
>
9032 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9034 objectclass: dnsdomain
9035 objectclass: domainrelatedobject
9038 associateddomain: tjener.intern
9040 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9042 objectclass: dnsdomain2
9043 objectclass: domainrelatedobject
9045 ptrrecord: tjener.intern
9046 associateddomain:
2.2.0.10.in-addr.arpa
9047 </pre
></blockquote
>
9049 <p
>In strict mode, the server behaves differently. When looking for
9050 forward DNS entries, it is doing a
"subtree
" scoped search with the
9051 same base as in the tree mode for a object with filter
9052 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9053 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9054 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9055 naptrrecord and modifytimestamp. For reverse entires it also do a
9056 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9057 and the requested attributes are associateddomain, dnsttl and
9058 modifytimestamp. In short, in strict mode the objects with ptrrecord
9059 go away, and the arecord attribute in the forward object is used
9062 <p
>The forward and reverse searches can be simulated using ldapsearch
9063 like this:
</p
>
9065 <blockquote
><pre
>
9066 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9067 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9068 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9069 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9070 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9071 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9073 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9074 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9075 </pre
></blockquote
>
9077 <p
>In addition to the forward and reverse searches , there is also a
9078 search for SOA records, which behave similar to the forward and
9079 reverse lookups.
</p
>
9081 <p
>A thing to note with the PowerDNS behaviour is that it do not
9082 specify any objectclass names, and instead look for the attributes it
9083 need to generate a DNS reply. This make it able to work with any
9084 objectclass that provide the needed attributes.
</p
>
9086 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9087 dnsdomain2 schemas. The latter is used for reverse entries like
9088 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9090 <p
>In Debian Edu, we have created DNS objects using the object classes
9091 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9092 attributes) and domainrelatedobject (for associatedDomain). The use
9093 of structural object classes make it impossible to combine these
9094 classes with the object classes used by DHCP.
</p
>
9096 <p
>There are other schemas that could be used too, for example the
9097 dnszone structural object class used by Gosa and bind-sdb for the DNS
9098 attributes combined with the domainrelatedobject object class, but in
9099 this case some unused attributes would have to be included as well
9100 (zonename and relativedomainname).
</p
>
9102 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9103 mode and not use any of the existing objectclasses (dnsdomain,
9104 dnsdomain2 and dnszone) when one want to combine the DNS information
9105 with DHCP information, and instead create a auxiliary object class
9106 defined something like this (using the attributes defined for
9107 dnsdomain and dnsdomain2 or dnszone):
</p
>
9109 <blockquote
><pre
>
9110 objectclass ( some-oid NAME
'dnsDomainAux
'
9113 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9114 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9115 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9116 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9117 A6Record $ DNAMERecord
9119 </pre
></blockquote
>
9121 <p
>This will allow any object to become a DNS entry when combined with
9122 the domainrelatedobject object class, and allow any entity to include
9123 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9124 developers asking for their view on this schema and if they are
9125 interested in providing such schema with PowerDNS, and I hope my
9126 message will be accepted into their mailing list soon.
</p
>
9128 <p
><strong
>ISC dhcp
</strong
></p
>
9130 <p
>The DHCP server searches for specific objectclass and requests all
9131 the object attributes, and then uses the attributes it want. This
9132 make it harder to figure out exactly what attributes are used, but
9133 thanks to the working example in Debian Edu I can at least get an idea
9134 what is needed without having to read the source code.
</p
>
9136 <p
>In the DHCP server configuration, the LDAP base to use and the
9137 search filter to use to locate the correct dhcpServer entity is
9138 stored. These are the relevant entries from
9139 /etc/dhcp3/dhcpd.conf:
</p
>
9141 <blockquote
><pre
>
9142 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9143 ldap-dhcp-server-cn
"dhcp
";
9144 </pre
></blockquote
>
9146 <p
>The DHCP server uses this information to nest all the DHCP
9147 configuration it need. The cn
"dhcp
" is located using the given LDAP
9148 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9149 search result is this entry:
</p
>
9151 <blockquote
><pre
>
9152 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9155 objectClass: dhcpServer
9156 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9157 </pre
></blockquote
>
9159 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9160 subtree with DHCP configuration. The DHCP configuration subtree base
9161 is located using a base scope search with base
"cn=DHCP
9162 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9163 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9164 The search result is this entry:
</p
>
9166 <blockquote
><pre
>
9167 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9170 objectClass: dhcpService
9171 objectClass: dhcpOptions
9172 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9173 dhcpStatements: ddns-update-style none
9174 dhcpStatements: authoritative
9175 dhcpOption: smtp-server code
69 = array of ip-address
9176 dhcpOption: www-server code
72 = array of ip-address
9177 dhcpOption: wpad-url code
252 = text
9178 </pre
></blockquote
>
9180 <p
>Next, the entire subtree is processed, one level at the time. When
9181 all the DHCP configuration is loaded, it is ready to receive requests.
9182 The subtree in Debian Edu contain objects with object classes
9183 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9184 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9185 and information about netmasks, dynamic range etc. Leaving out the
9186 details here because it is not relevant for the focus of my
9187 investigation, which is to see if it is possible to merge dns and dhcp
9188 related computer objects.
</p
>
9190 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9191 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9192 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9193 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9194 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9197 <blockquote
><pre
>
9198 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9201 objectClass: dhcpHost
9202 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9203 dhcpStatements: fixed-address hostname
9204 </pre
></blockquote
>
9206 <p
>There is less flexiblity in the way LDAP searches are done here.
9207 The object classes need to have fixed names, and the configuration
9208 need to be stored in a fairly specific LDAP structure. On the
9209 positive side, the invidiual dhcpHost entires can be anywhere without
9210 the DN pointed to by the dhcpServer entries. The latter should make
9211 it possible to group all host entries in a subtree next to the
9212 configuration entries, and this subtree can also be shared with the
9213 DNS server if the schema proposed above is combined with the dhcpHost
9214 structural object class.
9216 <p
><strong
>Conclusion
</strong
></p
>
9218 <p
>The PowerDNS implementation seem to be very flexible when it come
9219 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9220 come to the the LDAP structure, the
"strict
" mode is very flexible,
9221 allowing DNS objects to be stored anywhere under the base cn specified
9222 in the configuration.
</p
>
9224 <p
>The DHCP implementation on the other hand is very inflexible, both
9225 regarding which LDAP schemas to use and which LDAP structure to use.
9226 I guess one could implement ones own schema, as long as the
9227 objectclasses and attributes have the names used, but this do not
9228 really help when the DHCP subtree need to have a fairly fixed
9229 structure.
</p
>
9231 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9232 this might work for Debian Edu:
</p
>
9234 <blockquote
><pre
>
9236 cn=machine-info (dhcpService) - dhcpServiceDN points here
9237 cn=dhcp (dhcpServer)
9238 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9239 cn=
10.0.2.0 (dhcpSubnet)
9240 cn=group1 (dhcpGroup/dhcpOptions)
9241 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9242 cn=
192.168.0.0 (dhcpSubnet)
9243 cn=group1 (dhcpGroup/dhcpOptions)
9244 ou=machines - PowerDNS base points here
9245 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9246 </pre
></blockquote
>
9248 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9249 entries to be in the dhcpGroup subtrees, the entries can be stored
9250 there instead of a common machines subtree, and the PowerDNS base
9251 would have to be moved one level up to the machine-info subtree.
</p
>
9253 <p
>The combined object under the machines subtree would look something
9254 like this:
</p
>
9256 <blockquote
><pre
>
9257 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9260 objectClass: dhcpHost
9261 objectclass: domainrelatedobject
9262 objectclass: dnsDomainAux
9263 associateddomain: hostname.intern
9264 arecord:
10.11.12.13
9265 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9266 dhcpStatements: fixed-address hostname.intern
9267 </pre
></blockquote
>
9269 </p
>One could even add the LTSP configuration associated with a given
9270 machine, as long as the required attributes are available in a
9271 auxiliary object class.
</p
>
9276 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9277 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9278 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9279 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9280 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9281 DHCP services in Debian Edu to use the same LDAP objects for a given
9282 computer, to avoid the possibility of having a inconsistent state for
9283 a computer in LDAP (as in DHCP but no DNS entry or the other way
9284 around) and make it easier to add computers to LDAP.
</p
>
9286 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9287 information finally found a solution that seem to work.
</p
>
9289 <p
>The old setup required three LDAP objects for a given computer.
9290 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9291 we switch powerdns to use its strict LDAP method (ldap-method=strict
9292 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9293 merged into one while making it impossible to transfer the reverse map
9294 to a slave DNS server.
</p
>
9296 <p
>If we also replace the object class used to get the DNS related
9297 attributes to one allowing these attributes to be combined with the
9298 dhcphost object class, we can merge the DNS and DHCP entries into one.
9299 I
've written such object class in the dnsdomainaux.schema file (need
9300 proper OIDs, but that is a minor issue), and tested the setup. It
9301 seem to work.
</p
>
9303 <p
>With this test setup in place, we can get away with one LDAP object
9304 for both DNS and DHCP, and even the LTSP configuration I suggested in
9305 an earlier email. The combined LDAP object will look something like
9308 <blockquote
><pre
>
9309 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9311 objectClass: dhcphost
9312 objectclass: domainrelatedobject
9313 objectclass: dnsdomainaux
9314 associateddomain: hostname.intern
9315 arecord:
10.11.12.13
9316 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9317 dhcpstatements: fixed-address hostname
9319 </pre
></blockquote
>
9321 <p
>The DNS server uses the associateddomain and arecord entries, while
9322 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9323 before asking DNS to resolve the fixed-adddress. LTSP will use
9324 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9326 <p
>I am not yet sure if I can get the DHCP server to look for its
9327 dhcphost in a different location, to allow us to put the objects
9328 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9329 that. If I can
't figure out a way to do that, we can still get rid of
9330 the hosts subtree and move all its content into the DHCP Config tree
9331 (which probably should be renamed to be more related to the new
9332 content. I suspect cn=dnsdhcp,ou=services or something like that
9333 might be a good place to put it.
</p
>
9335 <p
>If you want to help out with implementing this for Debian Edu,
9336 please contact us on debian-edu@lists.debian.org.
</p
>
9341 <title>Idea for storing LTSP configuration in LDAP
</title>
9342 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9343 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9344 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9345 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9346 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9347 clients, and that this can be used to fetch configuration from LDAP if
9348 Debian Edu choose to store configuration there.
</p
>
9350 <p
>Armed with this information, I got inspired and wrote a test module
9351 to get configuration from LDAP. The idea is to look up the MAC
9352 address of the client in LDAP, and look for attributes on the form
9353 ltspconfigsetting=value, and use this to export SETTING=value to the
9354 LTSP clients.
</p
>
9356 <p
>The goal is to be able to store the LTSP configuration attributes
9357 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9358 allowing us to store all information about a computer in one place.
</p
>
9360 <p
>This is a untested draft implementation, and I welcome feedback on
9361 this approach. A real LDAP schema for the ltspClientAux objectclass
9362 need to be written. Comments, suggestions, etc?
</p
>
9364 <blockquote
><pre
>
9365 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9367 # Fetch LTSP client settings from LDAP based on MAC address
9369 # Uses ethernet address as stored in the dhcpHost objectclass using
9370 # the dhcpHWAddress attribute or ethernet address stored in the
9371 # ieee802Device objectclass with the macAddress attribute.
9373 # This module is written to be schema agnostic, and only depend on the
9374 # existence of attribute names.
9376 # The LTSP configuration variables are saved directly using a
9377 # ltspConfig prefix and uppercasing the rest of the attribute name.
9378 # To set the SERVER variable, set the ltspConfigServer attribute.
9380 # Some LDAP schema should be created with all the relevant
9381 # configuration settings. Something like this should work:
9383 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9386 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9388 LDAPSERVER=$(debian-edu-ldapserver)
9389 if [
"$LDAPSERVER
" ] ; then
9390 LDAPBASE=$(debian-edu-ldapserver -b)
9391 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9392 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9393 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9394 grep
'^ltspConfig
' | while read attr value ; do
9395 # Remove prefix and convert to upper case
9396 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9397 # bass value on to clients
9398 eval
"$attr=$value; export $attr
"
9402 </pre
></blockquote
>
9404 <p
>I
'm not sure this shell construction will work, because I suspect
9405 the while block might end up in a subshell causing the variables set
9406 there to not show up in ltsp-config, but if that is the case I am sure
9407 the code can be restructured to make sure the variables are passed on.
9408 I expect that can be solved with some testing. :)
</p
>
9410 <p
>If you want to help out with implementing this for Debian Edu,
9411 please contact us on debian-edu@lists.debian.org.
</p
>
9413 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9414 configuration in LDAP that was created around year
2000 by
9415 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9416 Xperience, Inc.,
2000</a
>. I found its
9417 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9418 personal home page over at redhat.com.
</p
>
9423 <title>jXplorer, a very nice LDAP GUI
</title>
9424 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9425 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9426 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9427 <description><p
>Since
9428 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9429 last post
</a
> about available LDAP tools in Debian, I was told about a
9430 LDAP GUI that is even better than luma. The java application
9431 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9432 moving LDAP objects and subtrees using drag-and-drop, and can
9433 authenticate using Kerberos. I have only tested the Kerberos
9434 authentication, but do not have a LDAP setup allowing me to rewrite
9435 LDAP with my test user yet. It is
9436 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9437 Debian
</a
> testing and unstable at the moment. The only problem I
9438 have with it is how it handle errors. If something go wrong, its
9439 non-intuitive behaviour require me to go through some query work list
9440 and remove the failing query. Nothing big, but very annoying.
</p
>
9445 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9446 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9447 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9448 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9449 <description><p
>Here is a short update on my
<a
9450 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9451 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9452 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9453 not reporting the status for KDE, because the upgrade crashes when
9454 aptitude try because of missing conflicts
9455 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9456 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9458 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9459 complete list of the installed packages. Based on this I see these
9460 differences when I did a test run today. As usual, I do not really
9461 know what the correct set of packages would be, but thought it best to
9462 publish the difference.
</p
>
9464 <p
>Installed using apt-get, missing with aptitude
</p
>
9466 <blockquote
><p
>
9467 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9468 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9469 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9470 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9471 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9472 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9473 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9474 python-gtkmozembed svgalibg1 xserver-xephyr zip
9475 </p
></blockquote
>
9477 <p
>Installed using apt-get, removed with aptitude
</p
>
9479 <blockquote
><p
>
9480 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9481 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9482 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9483 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9484 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9485 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9486 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9487 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9488 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9489 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9490 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9491 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9492 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9493 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9494 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9495 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9496 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9497 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9498 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9499 mysql-common swfdec-gnome totem-gstreamer wodim
9500 </p
></blockquote
>
9502 <p
>Installed using aptitude, missing with apt-get
</p
>
9504 <blockquote
><p
>
9505 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9506 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9507 xserver-xorg-input-all xserver-xorg-input-evdev
9508 xserver-xorg-input-kbd xserver-xorg-input-mouse
9509 xserver-xorg-input-synaptics xserver-xorg-video-all
9510 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9511 xserver-xorg-video-chips xserver-xorg-video-cirrus
9512 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9513 xserver-xorg-video-glint xserver-xorg-video-i128
9514 xserver-xorg-video-i740 xserver-xorg-video-mach64
9515 xserver-xorg-video-mga xserver-xorg-video-neomagic
9516 xserver-xorg-video-nouveau xserver-xorg-video-nv
9517 xserver-xorg-video-r128 xserver-xorg-video-radeon
9518 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9519 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9520 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9521 xserver-xorg-video-sis xserver-xorg-video-sisusb
9522 xserver-xorg-video-tdfx xserver-xorg-video-tga
9523 xserver-xorg-video-trident xserver-xorg-video-tseng
9524 xserver-xorg-video-vesa xserver-xorg-video-vmware
9525 xserver-xorg-video-voodoo
9526 </p
></blockquote
>
9528 <p
>Installed using aptitude, removed with apt-get
</p
>
9530 <blockquote
><p
>
9531 deskbar-applet xserver-xorg xserver-xorg-core
9532 xserver-xorg-input-wacom xserver-xorg-video-intel
9533 xserver-xorg-video-openchrome
9534 </p
></blockquote
>
9536 <p
>I was told on IRC that the xorg-xserver package was
9537 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9538 in git
</a
> today to try to get apt-get to not remove xorg completely.
9539 No idea when it hits Squeeze, but when it does I hope it will reduce
9540 the difference somewhat.
9545 <title>LUMA, a very nice LDAP GUI
</title>
9546 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9547 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9548 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9549 <description><p
>The last few days I have been looking into the status of the LDAP
9550 directory in Debian Edu, and in the process I started to miss a GUI
9551 tool to browse the LDAP tree. The only one I was able to find in
9552 Debian/Squeeze and Lenny is
9553 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9554 be a great tool to get a overview of the current LDAP directory
9555 populated by default in Skolelinux. Thanks to it, I have been able to
9556 find empty and obsolete subtrees, misplaced objects and duplicate
9557 objects. It will be installed by default in Debian/Squeeze. If you
9558 are working with LDAP, give it a go. :)
</p
>
9560 <p
>I did notice one problem with it I have not had time to report to
9561 the BTS yet. There is no .desktop file in the package, so the tool do
9562 not show up in the Gnome and KDE menus, but only deep down in in the
9563 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9566 <p
>I have not yet been able to get it to modify the tree yet. I would
9567 like to move objects and remove subtrees directly in the GUI, but have
9568 not found a way to do that with LUMA yet. So in the mean time, I use
9569 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9571 <p
>If you have tips on other GUI tools for LDAP that might be useful
9572 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9574 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9575 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9576 useful GUI alternative. It seem like a good tool, but is unmaintained
9577 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9578 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9583 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9584 <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>
9585 <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>
9586 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9587 <description><p
>A while back, I
9588 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9589 about the fact
</a
> that it is not possible with the provided schemas
9590 for storing DNS and DHCP information in LDAP to combine the two sets
9591 of information into one LDAP object representing a computer.
</p
>
9593 <p
>In the mean time, I discovered that a simple fix would be to make
9594 the dhcpHost object class auxiliary, to allow it to be combined with
9595 the dNSDomain object class, and thus forming one object for one
9596 computer when storing both DHCP and DNS information in LDAP.
</p
>
9598 <p
>If I understand this correctly, it is not safe to do this change
9599 without also changing the assigned number for the object class, and I
9600 do not know enough about LDAP schema design to do that properly for
9601 Debian Edu.
</p
>
9603 <p
>Anyway, for future reference, this is how I believe we could change
9605 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9606 schema
</a
> to solve at least part of the problem with the LDAP schemas
9607 available today from IETF.
</p
>
9610 --- dhcp.schema (revision
65192)
9611 +++ dhcp.schema (working copy)
9613 objectclass (
2.16.840.1.113719.1.203.6.6
9614 NAME
'dhcpHost
'
9615 DESC
'This represents information about a particular client
'
9619 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9620 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9623 <p
>I very much welcome clues on how to do this properly for Debian
9624 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9625 package, and should thus be free to rewrite it as we see fit.
</p
>
9627 <p
>If you want to help out with implementing this for Debian Edu,
9628 please contact us on debian-edu@lists.debian.org.
</p
>
9633 <title>Calling tasksel like the installer, while still getting useful output
</title>
9634 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9636 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9637 <description><p
>A few times I have had the need to simulate the way tasksel
9638 installs packages during the normal debian-installer run. Until now,
9639 I have ended up letting tasksel do the work, with the annoying problem
9640 of not getting any feedback at all when something fails (like a
9641 conffile question from dpkg or a download that fails), using code like
9644 <blockquote
><pre
>
9645 export DEBIAN_FRONTEND=noninteractive
9646 tasksel --new-install
9647 </pre
></blockquote
>
9649 This would invoke tasksel, let its automatic task selection pick the
9650 tasks to install, and continue to install the requested tasks without
9651 any output what so ever.
9653 Recently I revisited this problem while working on the automatic
9654 package upgrade testing, because tasksel would some times hang without
9655 any useful feedback, and I want to see what is going on when it
9656 happen. Then it occured to me, I can parse the output from tasksel
9657 when asked to run in test mode, and use that aptitude command line
9658 printed by tasksel then to simulate the tasksel run. I ended up using
9661 <blockquote
><pre
>
9662 export DEBIAN_FRONTEND=noninteractive
9663 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9665 </pre
></blockquote
>
9667 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9668 --without-recommends -o APT::Install-Recommends=no -y install
9669 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9670 ~pimportant
</tt
>", which will install the gnome desktop task, the
9671 laptop task and all packages with priority standard , required and
9672 important, just like tasksel would have done it during
9673 installation.
</p
>
9675 <p
>A better approach is probably to extend tasksel to be able to
9676 install packages without using debconf-apt-progress, for use cases
9677 like this.
</p
>
9682 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9683 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9685 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9686 <description><p
>My
9687 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9688 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9689 finally made the upgrade logs available from
9690 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9691 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9692 apt and aptitude, and found their differences interesting. This time
9693 I will only focus on their removal plans.
</p
>
9695 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9696 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9697 surprising part is that it want to remove xorg and all
9698 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9699 sure why. When asking aptitude to do the same, it want to remove
129
9700 packages, but most of them are library packages I suspect are no
9701 longer needed. Both of them want to remove bluetooth packages, which
9702 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9704 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9705 which seem like a bad idea and xorg the same way as with Gnome. Asking
9706 aptitude for the same, it wants to remove
192 packages, none which are
9707 too surprising.
</p
>
9709 <p
>I guess the removal of xorg during upgrades should be investigated
9710 and avoided, and perhaps others as well. Here are the complete list
9711 of planned removals. The complete logs is available from the URL
9712 above. Note if you want to repeat these tests, that the upgrade test
9713 for kde+apt-get hung in the tasksel setup because of dpkg asking
9714 conffile questions. No idea why. I worked around it by using
9715 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9718 <p
><b
>apt-get gnome
72</b
>
9719 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9720 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9721 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9722 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9723 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9724 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9725 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9726 xserver-xorg-input-kbd xserver-xorg-input-mouse
9727 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9728 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9729 xserver-xorg-video-ati xserver-xorg-video-chips
9730 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9731 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9732 xserver-xorg-video-glint xserver-xorg-video-i128
9733 xserver-xorg-video-i740 xserver-xorg-video-imstt
9734 xserver-xorg-video-intel xserver-xorg-video-mach64
9735 xserver-xorg-video-mga xserver-xorg-video-neomagic
9736 xserver-xorg-video-nsc xserver-xorg-video-nv
9737 xserver-xorg-video-openchrome xserver-xorg-video-r128
9738 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9739 xserver-xorg-video-rendition xserver-xorg-video-s3
9740 xserver-xorg-video-s3virge xserver-xorg-video-savage
9741 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9742 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9743 xserver-xorg-video-tga xserver-xorg-video-trident
9744 xserver-xorg-video-tseng xserver-xorg-video-v4l
9745 xserver-xorg-video-vesa xserver-xorg-video-vga
9746 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9747 xulrunner-
1.9-gnome-support
</p
>
9749 <p
><b
>aptitude gnome
129</b
>
9751 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9752 djvulibre-desktop finger gnome-app-install gnome-mount
9753 gnome-network-admin gnome-spell gnome-vfs-obexftp
9754 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9755 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9756 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9757 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9758 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9759 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9760 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9761 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9762 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9763 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9764 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9765 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9766 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9767 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9768 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9769 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9770 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9771 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9772 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9773 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9774 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9775 openoffice.org-writer2latex openssl-blacklist p7zip
9776 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9777 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9778 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9779 swfdec-mozilla totem-gstreamer update-manager wodim
9780 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9781 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9784 <p
><b
>apt-get kde
82</b
>
9786 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9787 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9788 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9789 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9790 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9791 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9792 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9793 xserver-xorg-input-kbd xserver-xorg-input-mouse
9794 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9795 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9796 xserver-xorg-video-ati xserver-xorg-video-chips
9797 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9798 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9799 xserver-xorg-video-glint xserver-xorg-video-i128
9800 xserver-xorg-video-i740 xserver-xorg-video-imstt
9801 xserver-xorg-video-intel xserver-xorg-video-mach64
9802 xserver-xorg-video-mga xserver-xorg-video-neomagic
9803 xserver-xorg-video-nsc xserver-xorg-video-nv
9804 xserver-xorg-video-openchrome xserver-xorg-video-r128
9805 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9806 xserver-xorg-video-rendition xserver-xorg-video-s3
9807 xserver-xorg-video-s3virge xserver-xorg-video-savage
9808 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9809 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9810 xserver-xorg-video-tga xserver-xorg-video-trident
9811 xserver-xorg-video-tseng xserver-xorg-video-v4l
9812 xserver-xorg-video-vesa xserver-xorg-video-vga
9813 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9815 <p
><b
>aptitude kde
192</b
>
9816 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9817 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9818 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9819 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9820 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9821 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9822 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9823 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9824 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9825 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9826 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9827 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9828 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9829 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9830 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9831 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9832 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9833 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9834 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9835 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9836 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9837 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9838 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9839 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9840 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9841 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9842 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9843 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9844 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9845 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9846 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9847 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9848 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9849 texlive-common texlive-doc-base texlive-fonts-recommended
9850 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9851 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9852 xulrunner-
1.9</p
>
9858 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9859 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9860 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9861 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9862 <description><p
>The last few days I have done some upgrade testing in Debian, to
9863 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9864 have been discovered and reported in the process
9865 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9866 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9867 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9868 kdebase-workspace-data), and to get a more regular testing going on, I
9869 am working on a script to automate the test.
</p
>
9871 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9872 Gnome or KDE desktop installation inside the chroot before upgrading
9873 it. To ensure no services are started in the chroot, a policy-rc.d
9874 script is inserted. To make sure tasksel believe it is to install a
9875 desktop on a laptop, the tasksel tests are replaced in the chroot
9876 (only acceptable because this is a throw-away chroot).
</p
>
9878 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9879 currently always fail because udev refuses to upgrade with the kernel
9880 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9881 is created. The bug report
9882 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9883 this problem do not trigger in a chroot, but I touch the file anyway
9884 to make sure the upgrade go well. Testing on virtual and real
9885 hardware have failed me because of udev so far, and creating this file
9886 do the trick in such settings anyway. This is a
9887 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9888 issue
</a
> and the current udev behaviour is intended by the udev
9889 maintainer because he lack the resources to rewrite udev to keep
9890 working with old kernels or something like that. I really wish the
9891 udev upstream would keep udev backwards compatible, to avoid such
9892 upgrade problem, but given that they fail to do so, I guess
9893 documenting the way out of this mess is the best option we got for
9894 Debian Squeeze.
</p
>
9896 <p
>Anyway, back to the task at hand, testing upgrades. This test
9897 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9900 <blockquote
><pre
>
9904 if [
"$
1" ] ; then
9913 exec
&lt; /dev/null
9915 mirror=http://ftp.skolelinux.org/debian
9916 tmpdir=chroot-$from-upgrade-$to-$desktop
9918 debootstrap $from $tmpdir $mirror
9919 chroot $tmpdir aptitude update
9920 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9924 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9928 mount -t proc proc $tmpdir/proc
9929 # Make sure proc is unmounted also on failure
9930 trap exit_cleanup EXIT INT
9932 chroot $tmpdir aptitude -y install debconf-utils
9934 # Make sure tasksel autoselection trigger. It need the test scripts
9935 # to return the correct answers.
9936 echo tasksel tasksel/desktop multiselect $desktop | \
9937 chroot $tmpdir debconf-set-selections
9939 # Include the desktop and laptop task
9940 for test in desktop laptop ; do
9941 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9945 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9948 DEBIAN_FRONTEND=noninteractive
9949 DEBIAN_PRIORITY=critical
9950 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9951 chroot $tmpdir tasksel --new-install
9953 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9954 chroot $tmpdir aptitude update
9955 touch $tmpdir/etc/udev/kernel-upgrade
9956 chroot $tmpdir aptitude -y dist-upgrade
9958 </pre
></blockquote
>
9960 <p
>I suspect it would be useful to test upgrades with both apt-get and
9961 with aptitude, but I have not had time to look at how they behave
9962 differently so far. I hope to get a cron job running to do the test
9963 regularly and post the result on the web. The Gnome upgrade currently
9964 work, while the KDE upgrade fail because of the bug in
9965 kdebase-workspace-data
</p
>
9967 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9968 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9969 post, so I will refrain from trying. I can report that for Gnome,
9970 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9971 remove and
1 not upgraded and
1024MB need to be downloaded while for
9972 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9973 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9975 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9976 is able to migrate to dependency based boot sequencing and parallel
9977 booting without a hitch. Was unsure if there were still bugs with
9978 packages failing to clean up their obsolete init.d script during
9979 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9985 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9986 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9988 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9989 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9990 scripts to migrate (some of) their operations to upstart job while
9991 keeping the init.d for hurd and kfreebsd. The packages with such
9992 needs will need a way to get their init.d scripts to behave
9993 differently when used with sysvinit and with upstart. Because of
9994 this, I had a look at the environment variables set when a init.d
9995 script is running under upstart, and when it is not.
</p
>
9997 <p
>With upstart, I notice these environment variables are set when a
9998 script is started from rcS.d/ (ignoring some irrelevant ones like
10001 <blockquote
><pre
>
10007 UPSTART_EVENTS=startup
10009 UPSTART_JOB=rc-sysinit
10010 </pre
></blockquote
>
10012 <p
>With sysvinit, these environment variables are set for the same
10015 <blockquote
><pre
>
10016 INIT_VERSION=sysvinit-
2.88
10021 </pre
></blockquote
>
10023 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10024 sysvinit are not set by upstart. Not sure if it is intentional or not
10025 to not be compatible with sysvinit in this regard.
</p
>
10027 <p
>For scripts needing to behave differently when upstart is used,
10028 looking for the UPSTART_JOB environment variable seem to be a good
10034 <title>A manual for standards wars...
</title>
10035 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10036 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10037 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10038 <description><p
>Via the
10039 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10040 of Rob Weir
</a
> I came across the very interesting essay named
10041 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10042 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10043 following the standards wars of today.
</p
>
10048 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10049 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10050 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10051 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10052 <description><p
>When using sitesummary at a site to track machines, it is possible
10053 to get a list of the machine types in use thanks to the DMI
10054 information extracted from each machine. The script to do so is
10055 included in the sitesummary package, and here is example output from
10056 the Skolelinux build servers:
</p
>
10058 <blockquote
><pre
>
10059 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10061 Dell Computer Corporation
1
10064 eserver xSeries
345 -[
8670M1X]-
1
10068 </pre
></blockquote
>
10070 <p
>The quality of the report depend on the quality of the DMI tables
10071 provided in each machine. Here there are Intel machines without model
10072 information listed with Intel as vendor and no model, and virtual Xen
10073 machines listed as [no-dmi-info]. One can add -l as a command line
10074 option to list the individual machines.
</p
>
10076 <p
>A larger list is
10077 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10078 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10079 provide the basic sitesummary report publicly. In their report there
10080 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10081 their machines, and as sitesummary is available in both distributions,
10082 it is trivial to get all of them to report to the same central
10083 collector.
</p
>
10088 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10089 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10090 <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>
10091 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10092 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10093 start at boot when an NVidia video card is used is handled. The
10094 problem seem to be that the nvidia X.org driver uses a long time to
10095 initialize, and this duration is longer than kdm is configured to
10098 <p
>I came across two bugs related to this issue,
10099 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10100 against initscripts and passed on to nvidia-glx when it became obvious
10101 that the nvidia drivers were involved, and
10102 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10103 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10105 <p
>To me, it seem that no-one is interested in actually solving the
10106 problem nvidia video card owners experience and make sure the Debian
10107 distribution work out of the box for these users. The nvidia driver
10108 maintainers expect kdm to be set up to wait longer, while kdm expect
10109 the nvidia driver maintainers to fix the driver to start faster, and
10110 while they wait for each other I guess the users end up switching to a
10111 distribution that work for them. I have no idea what the solution is,
10112 but I am pretty sure that waiting for each other is not it.
</p
>
10114 <p
>I wonder why we end up handling bugs this way.
</p
>
10119 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10120 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10122 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10123 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10124 The feature seem to hold up pretty well, but three fairly serious
10125 issues are known and should be solved:
10127 <p
><ul
>
10129 <li
>The wicd package seen to
10130 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10131 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10132 parallel booting is enabled. No idea why, but the wicd maintainer
10133 seem to be on the case.
</li
>
10135 <li
>The nvidia X driver seem to
10136 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10137 triggered more easily when parallel booting is in effect. The
10138 maintainer is on the case.
</li
>
10140 <li
>The sysv-rc package fail to properly enable dependency based boot
10141 sequencing (the shutdown is broken) when old file-rc users
10142 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10143 sysv-rc. One way to solve it would be for file-rc to create
10144 /etc/init.d/.legacy-bootordering, and another is to try to make
10145 sysv-rc more robust. Will investigate some more and probably upload a
10146 workaround in sysv-rc to help those trying to move from file-rc to
10147 sysv-rc get a working shutdown.
</li
>
10149 </ul
></p
>
10151 <p
>All in all not many surprising issues, and all of them seem
10152 solvable before Squeeze is released. In addition to these there are
10153 some packages with bugs in their dependencies and run level settings,
10154 which I expect will be fixed in a reasonable time span.
</p
>
10156 <p
>If you report any problems with dependencies in init.d scripts to
10157 the BTS, please usertag the report to get it to show up at
10158 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10159 list of usertagged bugs related to this
</a
>.
</p
>
10161 <p
>Update: Correct bug number to file-rc issue.
</p
>
10166 <title>More flexible firmware handling in debian-installer
</title>
10167 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10168 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10169 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10170 <description><p
>After a long break from debian-installer development, I finally
10171 found time today to return to the project. Having to spend less time
10172 working dependency based boot in debian, as it is almost complete now,
10173 definitely helped freeing some time.
</p
>
10175 <p
>A while back, I ran into a problem while working on Debian Edu. We
10176 include some firmware packages on the Debian Edu CDs, those needed to
10177 get disk and network controllers working. Without having these
10178 firmware packages available during installation, it is impossible to
10179 install Debian Edu on the given machine, and because our target group
10180 are non-technical people, asking them to provide firmware packages on
10181 an external medium is a support pain. Initially, I expected it to be
10182 enough to include the firmware packages on the CD to get
10183 debian-installer to find and use them. This proved to be wrong.
10184 Next, I hoped it was enough to symlink the relevant firmware packages
10185 to some useful location on the CD (tried /cdrom/ and
10186 /cdrom/firmware/). This also proved to not work, and at this point I
10187 found time to look at the debian-installer code to figure out what was
10188 going to work.
</p
>
10190 <p
>The firmware loading code is in the hw-detect package, and a closer
10191 look revealed that it would only look for firmware packages outside
10192 the installation media, so the CD was never checked for firmware
10193 packages. It would only check USB sticks, floppies and other
10194 "external
" media devices. Today I changed it to also look in the
10195 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10196 solve the problem I ran into with Debian edu. I also changed it to
10197 look in /firmware/, to make sure the installer also find firmware
10198 provided in the initrd when booting the installer via PXE, to allow us
10199 to provide the same feature in the PXE setup included in Debian
10202 <p
>To make sure firmware deb packages with a license questions are not
10203 activated without asking if the license is accepted, I extended
10204 hw-detect to look for preinst scripts in the firmware packages, and
10205 run these before activating the firmware during installation. The
10206 license question is asked using debconf in the preinst, so this should
10207 solve the issue for the firmware packages I have looked at so far.
</p
>
10209 <p
>If you want to discuss the details of these features, please
10210 contact us on debian-boot@lists.debian.org.
</p
>
10215 <title>Parallellized boot is now the default in Debian/unstable
</title>
10216 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10217 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10218 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10219 <description><p
>Since this evening, parallel booting is the default in
10220 Debian/unstable for machines using dependency based boot sequencing.
10221 Apparently the testing of concurrent booting has been wider than
10222 expected, if I am to believe the
10223 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10224 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10225 with the feature this weekend, to give us some time to detect any
10226 remaining problems before Squeeze is frozen. If serious problems are
10227 detected, it is simple to change the default back to sequential boot.
10228 The upload of the new sysvinit package also activate a new upstream
10231 More information about
10232 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10233 based boot sequencing
</a
> is available from the Debian wiki. It is
10234 currently possible to disable parallel booting when one run into
10235 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10237 <blockquote
><pre
>
10239 </pre
></blockquote
>
10241 <p
>If you report any problems with dependencies in init.d scripts to
10242 the BTS, please usertag the report to get it to show up at
10243 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10244 list of usertagged bugs related to this
</a
>.
</p
>
10249 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10250 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10251 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10252 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10253 <description><p
>In the recent Debian Edu versions, the
10254 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10255 system
</a
> is used to keep track of the machines in the school
10256 network. Each machine will automatically report its status to the
10257 central server after boot and once per night. The network setup is
10258 also reported, and using this information it is possible to get the
10259 MAC address of all network interfaces in the machines. This is useful
10260 to update the DHCP configuration.
</p
>
10262 <p
>To give some idea how to use sitesummary, here is a one-liner to
10263 ist all MAC addresses of all machines reporting to sitesummary. Run
10264 this on the collector host:
</p
>
10266 <blockquote
><pre
>
10267 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10268 </pre
></blockquote
>
10270 <p
>This will list all MAC addresses assosiated with all machine, one
10271 line per machine and with space between the MAC addresses.
</p
>
10273 <p
>To allow system administrators easier job at adding static DHCP
10274 addresses for hosts, it would be possible to extend this to fetch
10275 machine information from sitesummary and update the DHCP and DNS
10276 tables in LDAP using this information. Such tool is unfortunately not
10277 written yet.
</p
>
10282 <title>systemd, an interesting alternative to upstart
</title>
10283 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10284 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10285 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10286 <description><p
>The last few days a new boot system called
10287 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10289 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10291 to the free software world. I have not yet had time to play around
10292 with it, but it seem to be a very interesting alternative to
10293 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10294 a good alternative for Debian when we are able to switch to an event
10295 based boot system. Tollef is
10296 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10297 systemd into Debian, and I look forward to seeing how well it work. I
10298 like the fact that systemd handles init.d scripts with dependency
10299 information natively, allowing them to run in parallel where upstart
10300 at the moment do not.
</p
>
10302 <p
>Unfortunately do systemd have the same problem as upstart regarding
10303 platform support. It only work on recent Linux kernels, and also need
10304 some new kernel features enabled to function properly. This means
10305 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10306 system. Not sure how that will be handled if systemd proves to be the
10307 way forward.
</p
>
10309 <p
>In the mean time, based on the
10310 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10311 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10312 decided to enable full parallel booting as the default in Debian as
10313 soon as possible (probably this weekend or early next week), to see if
10314 there are any remaining serious bugs in the init.d dependencies. A
10315 new version of the sysvinit package implementing this change is
10316 already in experimental. If all go well, Squeeze will be released
10317 with parallel booting enabled by default.
</p
>
10322 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10323 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10324 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10325 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10326 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10327 complete, so complete that it is actually possible to run all the
10328 init.d scripts in parallell based on these dependencies. If you want
10329 to test your Squeeze system, make sure
10330 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10331 based boot sequencing
</a
> is enabled, and add this line to
10332 /etc/default/rcS:
</p
>
10334 <blockquote
><pre
>
10335 CONCURRENCY=makefile
10336 </pre
></blockquote
>
10338 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10339 scripts in parallel using the dependency information stored in
10340 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10341 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10342 to try to start the kdm and gdm scripts as early as possible, and will
10343 start the facilities required by kdm or gdm as early as possible to
10344 make this happen.
</p
>
10346 <p
>Give it a try, and see if you like the result. If some services
10347 fail to start properly, it is most likely because they have incomplete
10348 init.d script dependencies in their startup script (or some of their
10349 dependent scripts have incomplete dependencies). Report bugs and get
10350 the package maintainers to fix it. :)
</p
>
10352 <p
>Running scripts in parallel could be the default in Debian when we
10353 manage to get the init.d script dependencies complete and correct. I
10354 expect we will get there in Squeeze+
1, if we get manage to test and
10355 fix the remaining issues.
</p
>
10357 <p
>If you report any problems with dependencies in init.d scripts to
10358 the BTS, please usertag the report to get it to show up at
10359 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10360 list of usertagged bugs related to this
</a
>.
</p
>
10365 <title>Debian has switched to dependency based boot sequencing
</title>
10366 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10367 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10368 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10369 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10370 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10371 have been migrated to using dependency based boot sequencing. This
10372 conclude work me and others have been doing for the last three days.
10373 It feels great to see this finally part of the default Debian
10374 installation. Now we just need to weed out the last few problems that
10375 are bound to show up, to get everything ready for Squeeze.
</p
>
10377 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10378 fixing the more fundamental problem of handing the event based
10379 non-predictable kernel in the early boot.
</p
>
10384 <title>Taking over sysvinit development
</title>
10385 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10386 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10387 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10388 <description><p
>After several years of frustration with the lack of activity from
10389 the existing sysvinit upstream developer, I decided a few weeks ago to
10390 take over the package and become the new upstream. The number of
10391 patches to track for the Debian package was becoming a burden, and the
10392 lack of synchronization between the distribution made it hard to keep
10393 the package up to date.
</p
>
10395 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10396 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10397 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10398 and Fedora), based on the patches currently in use in these
10399 distributions. We Debian maintainers plan to move to this tarball as
10400 the new upstream as soon as we find time to do the merge. Since the
10401 new tarball was created, we agreed with Werner at SuSe to make a new
10402 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10403 development there. The project is registered and currently waiting
10404 for approval by the Savannah administrators, and as soon as it is
10405 approved, we will import the old versions from svn and continue
10406 working on the future release.
</p
>
10408 <p
>It is a bit ironic that this is done now, when some of the involved
10409 distributions are moving to upstart as a syvinit replacement.
</p
>
10414 <title>Debian boots quicker and quicker
</title>
10415 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10416 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10417 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10418 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10419 people involved in the boot system on Debian and Ubuntu, to see if we
10420 could find more ways to speed up the boot system. This was an Ubuntu
10422 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10423 gathering
</a
>. It was quite productive. We also discussed the future
10424 of boot systems, and ways to handle the increasing number of boot
10425 issues introduced by the Linux kernel becoming more and more
10426 asynchronous and event base. The Ubuntu approach using udev and
10427 upstart might be a good way forward. Time will show.
</p
>
10429 <p
>Anyway, there are a few ways at the moment to speed up the boot
10430 process in Debian. All of these should be applied to get a quick
10435 <li
>Use dash as /bin/sh.
</li
>
10437 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10438 clock is in UTC.
</li
>
10440 <li
>Install and activate the insserv package to enable
10441 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10442 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10446 These points are based on the Google summer of code work done by
10447 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10448 Villegas
</a
>.
10450 <p
>Support for makefile-style concurrency during boot was uploaded to
10451 unstable yesterday. When we tested it, we were able to cut
6 seconds
10452 from the boot sequence. It depend on very correct dependency
10453 declaration in all init.d scripts, so I expect us to find edge cases
10454 where the dependences in some scripts are slightly wrong when we start
10455 using this.
</p
>
10457 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10458 introduced by Raphael Geissert today, one that could affect the
10459 startup speed as well. Instead of starting some scripts concurrently
10460 from rcS.d/ and another set of scripts from rc2.d/, it would be
10461 possible to run a of them in the same process. A quick way to test
10462 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10463 insserv
'. Will need to test if that work. :)
</p
>
10468 <title>BSAs påstander om piratkopiering møter motstand
</title>
10469 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10470 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10471 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10472 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10473 programvareselskapene som Microsoft og Apple, publisert en rapport der
10474 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10475 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10477 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10478 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10479 dagene. Et spesielt interessant kommentar fra Sverige,
10480 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10481 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10484 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10485 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10486 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10487 exakta
", säger BSAs Sverigechef John Hugosson.
10488 </blockquote
>
10490 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10491 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10492 piracy figures need a shot of reality
</a
> og
<a
10493 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10494 Copyright Treaty Work?
</a
></p
>
10496 <p
>Fant lenkene via
<a
10497 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10498 på Slashdot
</a
>.
</p
>
10503 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10504 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10505 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10506 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10507 <description><p
>Kom over
10508 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10509 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10510 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10511 jobber til daglig. En rask opptelling forteller meg at vi har
490
10512 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10513 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10514 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10519 <title>Kryptert harddisk - naturligvis
</title>
10520 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10522 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10523 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10524 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10525 når en tar tap av arbeidstid, fortrolige dokumenter,
10526 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10527 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10528 til at jeg har kryptert harddisken på både kontormaskinen og min
10529 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10530 komme på avveie, den første informasjon relatert til jobben min ved
10531 Universitetet i Oslo, og den andre relatert til blant annet
10532 foreningsarbeide. Kryptering av diskene gjør at det er lite
10533 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10534 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10535 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10536 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10537 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10538 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10539 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10540 det er gjort slik jeg gjør det er minimale, og gevinstene er
10541 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10542 maskinen reinstalleres og alt er tapt.
</p
>
10544 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10545 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10546 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10547 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10548 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10549 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10550 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10551 betydelige.
</p
>
10556 <title>Two projects that have improved the quality of free software a lot
</title>
10557 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10558 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10559 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10560 <description><p
>There are two software projects that have had huge influence on the
10561 quality of free software, and I wanted to mention both in case someone
10562 do not yet know them.
</p
>
10564 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10565 tool to detect and expose errors in the memory handling of programs.
10566 It is easy to use, all one need to do is to run
'valgrind program
',
10567 and it will report any problems on stdout. It is even better if the
10568 program include debug information. With debug information, it is able
10569 to report the source file name and line number where the problem
10570 occurs. It can report things like
'reading past memory block in file
10571 X line N, the memory block was allocated in file Y, line M
', and
10572 'using uninitialised value in control logic
'. This tool has made it
10573 trivial to investigate reproducible crash bugs in programs, and have
10574 reduced the number of this kind of bugs in free software a lot.
10576 <p
>The second one is
10577 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10578 a source code checker. It is able to process the source of a program
10579 and find problems in the logic without running the program. It
10580 started out as the Stanford Checker and became well known when it was
10581 used to find bugs in the Linux kernel. It is now a commercial tool
10582 and the company behind it is running
10583 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10584 free software community, where a lot of free software projects get
10585 their source checked for free. Several thousand defects have been
10586 found and fixed so far. It can find errors like
'lock L taken in file
10587 X line N is never released if exiting in line M
', or
'the code in file
10588 Y lines O to P can never be executed
'. The projects included in the
10589 community service project have managed to get rid of a lot of
10590 reliability problems thanks to Coverity.
</p
>
10592 <p
>I believe tools like this, that are able to automatically find
10593 errors in the source, are vital to improve the quality of software and
10594 make sure we can get rid of the crashing and failing software we are
10595 surrounded by today.
</p
>
10600 <title>No patch is not better than a useless patch
</title>
10601 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10602 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10603 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10604 <description><p
>Julien Blache
10605 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10606 patch is better than a useless patch
</a
>. I completely disagree, as a
10607 patch allow one to discuss a concrete and proposed solution, and also
10608 prove that the issue at hand is important enough for someone to spent
10609 time on fixing it. No patch do not provide any of these positive
10610 properties.
</p
>
10615 <title>Standardize on protocols and formats, not vendors and applications
</title>
10616 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10618 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10619 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10620 very good one to form a long lived computer infrastructure. It is the
10621 simple one, lost by many in todays computer industry: Standardize on
10622 open network protocols and open exchange/storage formats, not applications.
10623 Applications come and go, while protocols and files tend to stay, and
10624 thus one want to make it easy to change application and vendor, while
10625 avoiding conversion costs and locking users to a specific platform or
10626 application.
</p
>
10628 <p
>This approach make it possible to replace the client applications
10629 independently of the server applications. One can even allow users to
10630 use several different applications as long as they handle the selected
10631 protocol and format. In the normal case, only one client application
10632 is recommended and users only get help if they choose to use this
10633 application, but those that want to deviate from the easy path are not
10634 blocked from doing so.
</p
>
10636 <p
>It also allow us to replace the server side without forcing the
10637 users to replace their applications, and thus allow us to select the
10638 best server implementation at any moment, when scale and resouce
10639 requirements change.
</p
>
10641 <p
>I strongly recommend standardizing - on open network protocols and
10642 open formats, but I would never recommend standardizing on a single
10643 application that do not use open network protocol or open formats.
</p
>
10648 <title>Returning from Skolelinux developer gathering
</title>
10649 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10650 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10651 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10652 <description><p
>I
'm sitting on the train going home from this weekends Debian
10653 Edu/Skolelinux development gathering. I got a bit done tuning the
10654 desktop, and looked into the dynamic service location protocol
10655 implementation avahi. It look like it could be useful for us. Almost
10656 30 people participated, and I believe it was a great environment to
10657 get to know the Skolelinux system. Walter Bender, involved in the
10658 development of the Sugar educational platform, presented his stuff and
10659 also helped me improve my OLPC installation. He also showed me that
10660 his Turtle Art application can be used in standalone mode, and we
10661 agreed that I would help getting it packaged for Debian. As a
10662 standalone application it would be great for Debian Edu. We also
10663 tried to get the video conferencing working with two OLPCs, but that
10664 proved to be too hard for us. The application seem to need more work
10665 before it is ready for me. I look forward to getting home and relax
10671 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10672 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10673 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10674 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10675 <description><p
>The state of standardized LDAP schemas on Linux is far from
10676 optimal. There is RFC
2307 documenting one way to store NIS maps in
10677 LDAP, and a modified version of this normally called RFC
2307bis, with
10678 some modifications to be compatible with Active Directory. The RFC
10679 specification handle the content of a lot of system databases, but do
10680 not handle DNS zones and DHCP configuration.
</p
>
10682 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10683 we would like to store information about users, SMB clients/hosts,
10684 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10685 and LTSP configuration in LDAP. These objects have a lot in common,
10686 but with the current LDAP schemas it is not possible to have one
10687 object per entity. For example, one need to have at least three LDAP
10688 objects for a given computer, one with the SMB related stuff, one with
10689 DNS information and another with DHCP information. The schemas
10690 provided for DNS and DHCP are impossible to combine into one LDAP
10691 object. In addition, it is impossible to implement quick queries for
10692 netgroup membership, because of the way NIS triples are implemented.
10693 It just do not scale. I believe it is time for a few RFC
10694 specifications to cleam up this mess.
</p
>
10696 <p
>I would like to have one LDAP object representing each computer in
10697 the network, and this object can then keep the SMB (ie host key), DHCP
10698 (mac address/name) and DNS (name/IP address) settings in one place.
10699 It need to be efficently stored to make sure it scale well.
</p
>
10701 <p
>I would also like to have a quick way to map from a user or
10702 computer and to the net group this user or computer is a member.
</p
>
10704 <p
>Active Directory have done a better job than unix heads like myself
10705 in this regard, and the unix side need to catch up. Time to start a
10706 new IETF work group?
</p
>
10711 <title>Endelig er Debian Lenny gitt ut
</title>
10712 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10713 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10714 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10715 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10716 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10717 Et langt steg videre for Debian-prosjektet, og en rekke nye
10718 programpakker blir nå tilgjengelig for de av oss som bruker den
10719 stabile utgaven av Debian. Neste steg er nå å få
10720 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10721 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10722 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10723 slippes løs på skolene. Takk til alle debian-utviklerne som har
10724 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10725 bootsekvens tilgjengelig i stabil utgave, vha pakken
10726 <tt
>insserv
</tt
>.
</p
>
10731 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10732 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10733 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10734 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10735 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10736 Oslo. Most of Saturday was used for the general assemly for the
10737 member organization, but the rest of the weekend I used to tune the
10738 LTSP installation. LTSP now work out of the box on the
10-network.
10739 Acer Aspire One proved to be a very nice thin client, with both
10740 screen, mouse and keybard in a small box. Was working on getting the
10741 diskless workstation setup configured out of the box, but did not
10742 finish it before the weekend was up.
</p
>
10744 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10745 the Brazilian group, so that will have to wait for the next
10746 development gathering. Would love to have the Debian Edu installer
10747 automatically detect and configure a multiseat setup when it find one
10748 of these cards.
</p
>
10753 <title>The sorry state of multimedia browser plugins in Debian
</title>
10754 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10755 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10756 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10757 <description><p
>Recently I have spent some time evaluating the multimedia browser
10758 plugins available in Debian Lenny, to see which one we should use by
10759 default in Debian Edu. We need an embedded video playing plugin with
10760 control buttons to pause or stop the video, and capable of streaming
10761 all the multimedia content available on the web. The test results and
10762 notes are available on
10763 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10764 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10765 fill this need. My personal video player favorite, VLC, has a really
10766 bad plugin which fail on a lot of the test pages. A lot of the MIME
10767 types I would expect to work with any free software player (like
10768 video/ogg), just do not work. And simple formats like the
10769 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10770 totem and vlc plugins. I hope the situation will improve soon. No
10771 wonder sites use the proprietary Adobe flash to play video.
</p
>
10773 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10774 be the only one fitting our needs. :/
</p
>