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>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
11 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
13 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
14 <description><p
>At my nearby maker space,
15 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
16 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
17 on Windows and MacOS X than Linux, because the software involved had
18 to be manually compiled and set up on Linux while premade packages
19 worked out of the box on Windows and MacOS X. I found this annoying,
20 as the software involved,
21 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
22 and should be trivial to get up and running on Linux if someone took
23 the time to package it for the relevant distributions. I even found
24 <a href=
"https://bugs.debian.org/
706656">a request for adding into
25 Debian
</a
> from
2013, which had seem some activity over the years but
26 never resulted in the software showing up in Debian. So a few days
27 ago I offered my help to try to improve the situation.
</p
>
29 <p
>Now I am very happy to see that all the packages required by a
30 working Cura in Debian are uploaded into Debian and waiting in the NEW
31 queue for the ftpmasters to have a look. You can track the progress
33 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
34 status page for the
3D printer team
</a
>.
</p
>
36 <p
>The uploaded packages are a bit behind upstream, and was uploaded
37 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
38 queue
</a
> while we work up updating the packages to the latest
39 upstream version.
</p
>
41 <p
>On a related note, two competitors for Cura, which I found harder
42 to use and was unable to configure correctly for Ultimaker
2+ in the
43 short time I spent on it, are already in Debian. If you are looking
44 for
3D printer
"slicers
" and want something already available in
46 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
47 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
48 The latter is a fork of the former.
</p
>
50 <p
>As usual, if you use Bitcoin and want to show your support of my
51 activities, please send Bitcoin donations to my address
52 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
57 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
58 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
59 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
60 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
61 <description><p
>Every mobile phone announce its existence over radio to the nearby
62 mobile cell towers. And this radio chatter is available for anyone
63 with a radio receiver capable of receiving them. Details about the
64 mobile phones with very good accuracy is of course collected by the
65 phone companies, but this is not the topic of this blog post. The
66 mobile phone radio chatter make it possible to figure out when a cell
67 phone is nearby, as it include the SIM card ID (IMSI). By paying
68 attention over time, one can see when a phone arrive and when it leave
69 an area. I believe it would be nice to make this information more
70 available to the general public, to make more people aware of how
71 their phones are announcing their whereabouts to anyone that care to
74 <p
>I am very happy to report that we managed to get something
75 visualizing this information up and running for
76 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
77 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
78 library. The solution is based on the
79 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
80 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
81 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
82 Sone from the Computer Science department of the University of
83 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
84 IMSIs) as dots in a web browser graph, with lines to the dot
85 representing mobile base station it is talking to. It was working in
86 the lab yesterday, and was moved into place this morning.
</p
>
88 <p
>We set up a fairly powerful desktop machine using Debian
89 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
90 connected and visualize the visible cell phone towers using an
91 <a href=
"https://github.com/marlow925/hopglass
">English version of
92 Hopglass
</a
>. A fairly powerfull machine is needed as the
93 grgsm_livemon_headless processes from
94 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
95 the radio signal to data packages is quite CPU intensive.
</p
>
97 <p
>The frequencies to listen to, are identified using a slightly
98 patched scan-and-livemon (to set the --args values for each receiver),
99 and the Hopglass data is generated using the
100 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
101 in my meshviewer-output branch
</a
>. For some reason we could not get
102 more than four SDRs working. There is also a geographical map trying
103 to show the location of the base stations, but I believe their
104 coordinates are hardcoded to some random location in Germany, I
105 believe. The code should be replaced with code to look up location in
106 a text file, a sqlite database or one of the online databases
108 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
109 issue for the topic
</a
>.
111 <p
>If this sound interesting, visit the stand at the festival!
</p
>
116 <title>Easier recipe to observe the cell phones around you
</title>
117 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
118 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
119 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
120 <description><p
>A little more than a month ago I wrote
121 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
122 to observe the SIM card ID (aka IMSI number) of mobile phones talking
123 to nearby mobile phone base stations using Debian GNU/Linux and a
124 cheap USB software defined radio
</a
>, and thus being able to pinpoint
125 the location of people and equipment (like cars and trains) with an
126 accuracy of a few kilometer. Since then we have worked to make the
127 procedure even simpler, and it is now possible to do this without any
128 manual frequency tuning and without building your own packages.
</p
>
130 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
131 package is now included in Debian testing and unstable, and the
132 IMSI-catcher code no longer require root access to fetch and decode
133 the GSM data collected using gr-gsm.
</p
>
135 <p
>Here is an updated recipe, using packages built by Debian and a git
136 clone of two python scripts:
</p
>
140 <li
>Start with a Debian machine running the Buster version (aka
143 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
144 python-scapy
</tt
>' as root to install required packages.
</li
>
146 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
147 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
149 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
151 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
152 scan-and-livemon
</tt
>' to locate the frequency of nearby base
153 stations and start listening for GSM packages on one of them.
</li
>
155 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
156 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
160 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
161 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
162 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
163 work with RTL
8232 and other similar USB radio receivers you can get
165 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
166 from ebay
</a
>), so for now the solution is to scan using the RTL radio
167 and only use HackRF for fetching GSM data.
</p
>
169 <p
>As far as I can tell, a cell phone only show up on one of the
170 frequencies at the time, so if you are going to track and count every
171 cell phone around you, you need to listen to all the frequencies used.
172 To listen to several frequencies, use the --numrecv argument to
173 scan-and-livemon to use several receivers. Further, I am not sure if
174 phones using
3G or
4G will show as talking GSM to base stations, so
175 this approach might not see all phones around you. I typically see
176 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
178 <p
>I
've tried to run the scanner on a
179 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
180 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
181 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
182 stdout, I am told there it is caused by a buffer overflow between the
183 radio and GNU Radio, caused by the program being unable to read the
184 GSM data fast enough. If you see a stream of
'O
's from the terminal
185 where you started scan-and-livemon, you need a give the process more
186 CPU power. Perhaps someone are able to optimize the code to a point
187 where it become possible to set up RPi3 based GSM sniffers? I tried
188 using Raspbian instead of Debian, but there seem to be something wrong
189 with GNU Radio on raspbian, causing glibc to abort().
</p
>
194 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
195 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
196 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
197 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
198 <description><p
>On friday, I came across an interesting article in the Norwegian
199 web based ICT news magazine digi.no on
200 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
201 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
202 DVB-T software defined radios. The article refered to instructions
203 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
204 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
206 <p
>The instructions said to use Ubuntu, install pip using apt (to
207 bypass apt), use pip to install pybombs (to bypass both apt and pip),
208 and the ask pybombs to fetch and build everything you need from
209 scratch. I wanted to see if I could do the same on the most recent
210 Debian packages, but this did not work because pybombs tried to build
211 stuff that no longer build with the most recent openssl library or
212 some other version skew problem. While trying to get this recipe
213 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
214 and the only piece of software dependency missing in Debian was the
215 gr-gsm package. I also found out that the lead upstream developer of
216 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
217 Debian packages provided in an Ubuntu PPA repository. All I needed to
218 do was to dget the Debian source package and built it.
</p
>
220 <p
>The IMSI collector is a python script listening for packages on the
221 loopback network device and printing to the terminal some specific GSM
222 packages with IMSI numbers in them. The code is fairly short and easy
223 to understand. The reason this work is because gr-gsm include a tool
224 to read GSM data from a software defined radio like a DVB-T USB stick
225 and other software defined radios, decode them and inject them into a
226 network device on your Linux machine (using the loopback device by
227 default). This proved to work just fine, and I
've been testing the
228 collector for a few days now.
</p
>
230 <p
>The updated and simpler recipe is thus to
</p
>
234 <li
>start with a Debian machine running Stretch or newer,
</li
>
236 <li
>build and install the gr-gsm package available from
237 <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
>
239 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
241 <li
>run grgsm_livemon and adjust the frequency until the terminal
242 where it was started is filled with a stream of text (meaning you
243 found a GSM station).
</li
>
245 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
249 <p
>To make it even easier in the future to get this sniffer up and
250 running, I decided to package
251 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
252 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
253 #
871055</a
>), and the package was uploaded into the NEW queue today.
254 Luckily the gnuradio maintainer has promised to help me, as I do not
255 know much about gnuradio stuff yet.
</p
>
257 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
258 commercial tools like
259 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
260 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
261 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
262 Stingray
</a
>, but I hope the existance of cheap alternatives can make
263 more people realise how their whereabouts when carrying a cell phone
264 is easily tracked. Seeing the data flow on the screen, realizing that
265 I live close to a police station and knowing that the police is also
266 wearing cell phones, I wonder how hard it would be for criminals to
267 track the position of the police officers to discover when there are
268 police near by, or for foreign military forces to track the location
269 of the Norwegian military forces, or for anyone to track the location
270 of government officials...
</p
>
272 <p
>It is worth noting that the data reported by the IMSI-catcher
273 script mentioned above is only a fraction of the data broadcasted on
274 the GSM network. It will only collect one frequency at the time,
275 while a typical phone will be using several frequencies, and not all
276 phones will be using the frequencies tracked by the grgsm_livemod
277 program. Also, there is a lot of radio chatter being ignored by the
278 simple_IMSI-catcher script, which would be collected by extending the
279 parser code. I wonder if gr-gsm can be set up to listen to more than
280 one frequency?
</p
>
285 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
286 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
287 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
288 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
289 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
291 <p
>I finally received a copy of the Norwegian Bokmål edition of
292 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
293 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
294 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
295 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
296 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
297 price. The book is also available for download in electronic form as
298 PDF, EPUB and Mobipocket, as can be
299 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
300 as a web page
</a
>.
</p
>
302 <p
>This is the second book I publish (the first was the book
303 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
305 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
306 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
308 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
309 Bokmål
</a
>), and I am very excited to finally wrap up this
311 "<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
312 for Debian-administratoren
</a
>" will be well received.
</p
>
317 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
318 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
320 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
321 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
322 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
323 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
324 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
325 på om den fri oversetterløsningen
326 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
327 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
329 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
332 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
333 rolle og muligheter til å håndtere internasjonale utfordringer, som
334 for eksempel flykningekrisen.
</p
>
336 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
339 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
340 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
345 <p
>Dette oversetter Apertium slik:
</p
>
348 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
349 andre aktørar og høve til å handtera internasjonale utfordringar, som
350 til dømes *flykningekrisen.
</p
>
352 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
356 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
357 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
362 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
363 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
364 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
365 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
366 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
367 det er kanskje flisespikking. Det understreker vel bare at det alltid
368 trengs korrekturlesning etter automatisk oversettelse.
</p
>
373 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
374 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
375 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
376 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
377 <description><p
>Over the years, administrating thousand of NFS mounting linux
378 computers at the time, I often needed a way to detect if the machine
379 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
380 file or directory affected by the hang, the process (and possibly the
381 shell) will hang too. So you want to be able to detect this without
382 risking the detection process getting stuck too. It has not been
383 obvious how to do this. When the hang has lasted a while, it is
384 possible to find messages like these in dmesg:
</p
>
386 <p
><blockquote
>
387 nfs: server nfsserver not responding, still trying
388 <br
>nfs: server nfsserver OK
389 </blockquote
></p
>
391 <p
>It is hard to know if the hang is still going on, and it is hard to
392 be sure looking in dmesg is going to work. If there are lots of other
393 messages in dmesg the lines might have rotated out of site before they
394 are noticed.
</p
>
396 <p
>While reading through the nfs client implementation in linux kernel
397 code, I came across some statistics that seem to give a way to detect
398 it. The om_timeouts sunrpc value in the kernel will increase every
399 time the above log entry is inserted into dmesg. And after digging a
400 bit further, I discovered that this value show up in
401 /proc/self/mountstats on Linux.
</p
>
403 <p
>The mountstats content seem to be shared between files using the
404 same file system context, so it is enough to check one of the
405 mountstats files to get the state of the mount point for the machine.
406 I assume this will not show lazy umounted NFS points, nor NFS mount
407 points in a different process context (ie with a different filesystem
408 view), but that does not worry me.
</p
>
410 <p
>The content for a NFS mount point look similar to this:
</p
>
412 <p
><blockquote
><pre
>
414 device /dev/mapper/Debian-var mounted on /var with fstype ext3
415 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
416 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
418 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
419 sec: flavor=
1,pseudoflavor=
1
420 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
421 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
422 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
423 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
425 NULL:
0 0 0 0 0 0 0 0
426 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
427 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
428 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
429 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
430 READLINK:
125 125 0 20472 18620 0 1112 1118
431 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
432 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
433 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
434 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
435 SYMLINK:
903 903 0 233428 245488 6 5865 5917
436 MKNOD:
80 80 0 20148 21760 0 299 304
437 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
438 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
439 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
440 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
441 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
442 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
443 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
444 FSINFO:
2 2 0 232 328 0 1 1
445 PATHCONF:
1 1 0 116 140 0 0 0
446 COMMIT:
0 0 0 0 0 0 0 0
448 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
450 </pre
></blockquote
></p
>
452 <p
>The key number to look at is the third number in the per-op list.
453 It is the number of NFS timeouts experiences per file system
454 operation. Here
22 write timeouts and
5 access timeouts. If these
455 numbers are increasing, I believe the machine is experiencing NFS
456 hang. Unfortunately the timeout value do not start to increase right
457 away. The NFS operations need to time out first, and this can take a
458 while. The exact timeout value depend on the setup. For example the
459 defaults for TCP and UDP mount points are quite different, and the
460 timeout value is affected by the soft, hard, timeo and retrans NFS
461 mount options.
</p
>
463 <p
>The only way I have been able to get working on Debian and RedHat
464 Enterprise Linux for getting the timeout count is to peek in /proc/.
466 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
467 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
468 command can be used to get these timeout values. But this do not work
469 on Linux, as far as I can tell. I
470 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
471 but have not seen any replies yet.
</p
>
473 <p
>Is there a better way to figure out if a Linux NFS client is
474 experiencing NFS hangs? Is there a way to detect which processes are
475 affected? Is there a way to get the NFS mount going quickly once the
476 network problem causing the NFS hang has been cleared? I would very
477 much welcome some clues, as we regularly run into NFS hangs.
</p
>
482 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
483 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
484 <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>
485 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
486 <description><p
>For almost a year now, we have been working on making a Norwegian
487 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
488 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
489 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
490 we are working on the proof reading to ensure consistent language and
491 use of correct computer science terms. The plan is to make the book
492 available on paper, as well as in electronic form. For that to
493 happen, the proof reading must be completed and all the figures need
494 to be translated. If you want to help out, get in touch.
</p
>
496 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
498 fresh PDF edition
</a
> in A4 format (the final book will have smaller
499 pages) of the book created every morning is available for
500 proofreading. If you find any errors, please
501 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
502 Weblate and correct the error
</a
>. The
503 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
504 of the translation including figures
</a
> is a useful source for those
505 provide Norwegian bokmål screen shots and figures.
</p
>
510 <title>Unlimited randomness with the ChaosKey?
</title>
511 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
512 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
513 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
514 <description><p
>A few days ago I ordered a small batch of
515 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
516 USB dongle for generating entropy created by Bdale Garbee and Keith
517 Packard. Yesterday it arrived, and I am very happy to report that it
518 work great! According to its designers, to get it to work out of the
519 box, you need the Linux kernel version
4.1 or later. I tested on a
520 Debian Stretch machine (kernel version
4.9), and there it worked just
521 fine, increasing the available entropy very quickly. I wrote a small
522 test oneliner to test. It first print the current entropy level,
523 drain /dev/random, and then print the entropy level for five seconds.
524 Here is the situation without the ChaosKey inserted:
</p
>
526 <blockquote
><pre
>
527 % cat /proc/sys/kernel/random/entropy_avail; \
528 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
529 for n in $(seq
1 5); do \
530 cat /proc/sys/kernel/random/entropy_avail; \
536 28 byte kopiert,
0,
000264565 s,
106 kB/s
543 </pre
></blockquote
>
545 <p
>The entropy level increases by
3-
4 every second. In such case any
546 application requiring random bits (like a HTTPS enabled web server)
547 will halt and wait for more entrpy. And here is the situation with
548 the ChaosKey inserted:
</p
>
550 <blockquote
><pre
>
551 % cat /proc/sys/kernel/random/entropy_avail; \
552 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
553 for n in $(seq
1 5); do \
554 cat /proc/sys/kernel/random/entropy_avail; \
560 104 byte kopiert,
0,
000487647 s,
213 kB/s
567 </pre
></blockquote
>
569 <p
>Quite the difference. :) I bought a few more than I need, in case
570 someone want to buy one here in Norway. :)
</p
>
572 <p
>Update: The dongle was presented at Debconf last year. You might
573 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
574 recording illuminating
</a
>. It explains exactly what the source of
575 randomness is, if you are unable to spot it from the schema drawing
576 available from the ChaosKey web site linked at the start of this blog
582 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
583 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
584 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
585 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
586 <description><p
>Did you ever wonder where the web trafic really flow to reach the
587 web servers, and who own the network equipment it is flowing through?
588 It is possible to get a glimpse of this from using traceroute, but it
589 is hard to find all the details. Many years ago, I wrote a system to
590 map the Norwegian Internet (trying to figure out if our plans for a
591 network game service would get low enough latency, and who we needed
592 to talk to about setting up game servers close to the users. Back
593 then I used traceroute output from many locations (I asked my friends
594 to run a script and send me their traceroute output) to create the
595 graph and the map. The output from traceroute typically look like
599 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
600 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
601 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
602 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
603 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
604 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
605 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
606 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
610 </pre
></p
>
612 <p
>This show the DNS names and IP addresses of (at least some of the)
613 network equipment involved in getting the data traffic from me to the
614 www.stortinget.no server, and how long it took in milliseconds for a
615 package to reach the equipment and return to me. Three packages are
616 sent, and some times the packages do not follow the same path. This
617 is shown for hop
5, where three different IP addresses replied to the
618 traceroute request.
</p
>
620 <p
>There are many ways to measure trace routes. Other good traceroute
621 implementations I use are traceroute (using ICMP packages) mtr (can do
622 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
623 traceroute and a lot of other capabilities). All of them are easily
624 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
626 <p
>This time around, I wanted to know the geographic location of
627 different route points, to visualize how visiting a web page spread
628 information about the visit to a lot of servers around the globe. The
629 background is that a web site today often will ask the browser to get
630 from many servers the parts (for example HTML, JSON, fonts,
631 JavaScript, CSS, video) required to display the content. This will
632 leak information about the visit to those controlling these servers
633 and anyone able to peek at the data traffic passing by (like your ISP,
634 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
636 <p
>Lets pick an example, the Norwegian parliament web site
637 www.stortinget.no. It is read daily by all members of parliament and
638 their staff, as well as political journalists, activits and many other
639 citizens of Norway. A visit to the www.stortinget.no web site will
640 ask your browser to contact
8 other servers: ajax.googleapis.com,
641 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
642 stats.g.doubleclick.net, www.google-analytics.com,
643 www.googletagmanager.com and www.netigate.se. I extracted this by
644 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
645 Stortinget web page and tell me all the URLs PhantomJS downloaded to
646 render the page (in HAR format using
647 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
648 netsniff example
</a
>. I am very grateful to Gorm for showing me how
649 to do this). My goal is to visualize network traces to all IP
650 addresses behind these DNS names, do show where visitors personal
651 information is spread when visiting the page.
</p
>
653 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
654 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
>
656 <p
>When I had a look around for options, I could not find any good
657 free software tools to do this, and decided I needed my own traceroute
658 wrapper outputting KML based on locations looked up using GeoIP. KML
659 is easy to work with and easy to generate, and understood by several
660 of the GIS tools I have available. I got good help from by NUUG
661 colleague Anders Einar with this, and the result can be seen in
662 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
663 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
664 free GeoIP databases I could find (and the for-pay databases my
665 friends had access to) is not up to the task. The IP addresses of
666 central Internet infrastructure would typically be placed near the
667 controlling companies main office, and not where the router is really
668 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
669 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
671 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
672 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
>
674 <p
>I also had a look at the visual traceroute graph created by
675 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
676 showing IP network ownership (aka AS owner) for the IP address in
678 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
679 graph display a lot of useful information about the traceroute in SVG
680 format
</a
>, and give a good indication on who control the network
681 equipment involved, but it do not include geolocation. This graph
682 make it possible to see the information is made available at least for
683 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
684 3 Communications and NetDNA.
</p
>
686 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
687 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
>
689 <p
>In the process, I came across the
690 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
691 Salim Gasmi. Its methology of combining guesses based on DNS names,
692 various location databases and finally use latecy times to rule out
693 candidate locations seemed to do a very good job of guessing correct
694 geolocation. But it could only do one trace at the time, did not have
695 a sensor in Norway and did not make the geolocations easily available
696 for postprocessing. So I contacted the developer and asked if he
697 would be willing to share the code (he refused until he had time to
698 clean it up), but he was interested in providing the geolocations in a
699 machine readable format, and willing to set up a sensor in Norway. So
700 since yesterday, it is possible to run traces from Norway in this
701 service thanks to a sensor node set up by
702 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
703 trace in KML format for further processing.
</p
>
705 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
706 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
>
708 <p
>Here we can see a lot of trafic passes Sweden on its way to
709 Denmark, Germany, Holland and Ireland. Plenty of places where the
710 Snowden confirmations verified the traffic is read by various actors
711 without your best interest as their top priority.
</p
>
713 <p
>Combining KML files is trivial using a text editor, so I could loop
714 over all the hosts behind the urls imported by www.stortinget.no and
715 ask for the KML file from GeoTraceroute, and create a combined KML
716 file with all the traces (unfortunately only one of the IP addresses
717 behind the DNS name is traced this time. To get them all, one would
718 have to request traces using IP number instead of DNS names from
719 GeoTraceroute). That might be the next step in this project.
</p
>
721 <p
>Armed with these tools, I find it a lot easier to figure out where
722 the IP traffic moves and who control the boxes involved in moving it.
723 And every time the link crosses for example the Swedish border, we can
724 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
725 Britain and NSA in USA and cables around the globe. (Hm, what should
726 we tell them? :) Keep that in mind if you ever send anything
727 unencrypted over the Internet.
</p
>
729 <p
>PS: KML files are drawn using
730 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
731 Rublev
<a/
>, as it was less cluttered than the local Linux application
732 Marble. There are heaps of other options too.
</p
>
734 <p
>As usual, if you use Bitcoin and want to show your support of my
735 activities, please send Bitcoin donations to my address
736 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
741 <title>Appstream just learned how to map hardware to packages too!
</title>
742 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
743 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
744 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
745 <description><p
>I received a very nice Christmas present today. As my regular
746 readers probably know, I have been working on the
747 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
748 system
</a
> for many years. The goal of the Isenkram system is to make
749 it easier for users to figure out what to install to get a given piece
750 of hardware to work in Debian, and a key part of this system is a way
751 to map hardware to packages. Isenkram have its own mapping database,
752 and also uses data provided by each package using the AppStream
753 metadata format. And today,
754 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
755 Debian learned to look up hardware the same way Isenkram is doing it,
756 ie using fnmatch():
</p
>
759 % appstreamcli what-provides modalias \
760 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
761 Identifier: pymissile [generic]
763 Summary: Control original Striker USB Missile Launcher
765 % appstreamcli what-provides modalias usb:v0694p0002d0000
766 Identifier: libnxt [generic]
768 Summary: utility library for talking to the LEGO Mindstorms NXT brick
771 Identifier: t2n [generic]
773 Summary: Simple command-line tool for Lego NXT
776 Identifier: python-nxt [generic]
778 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
781 Identifier: nbc [generic]
783 Summary: C compiler for LEGO Mindstorms NXT bricks
786 </pre
></p
>
788 <p
>A similar query can be done using the combined AppStream and
789 Isenkram databases using the isenkram-lookup tool:
</p
>
792 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
794 % isenkram-lookup usb:v0694p0002d0000
800 </pre
></p
>
802 <p
>You can find modalias values relevant for your machine using
803 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
805 <p
>If you want to make this system a success and help Debian users
806 make the most of the hardware they have, please
807 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
808 AppStream metadata for your package following the guidelines
</a
>
809 documented in the wiki. So far only
11 packages provide such
810 information, among the several hundred hardware specific packages in
811 Debian. The Isenkram database on the other hand contain
101 packages,
812 mostly related to USB dongles. Most of the packages with hardware
813 mapping in AppStream are LEGO Mindstorms related, because I have, as
814 part of my involvement in
815 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
816 team
</a
> given priority to making sure LEGO users get proposed the
817 complete set of packages in Debian for that particular hardware. The
818 team also got a nice Christmas present today. The
819 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
820 package
</a
> made it into Debian. With this package in place, it is
821 now possible to use the LEGO Mindstorms NXT unit with only free
822 software, as the nxt-firmware package contain the source and firmware
823 binaries for the NXT brick.
</p
>
825 <p
>As usual, if you use Bitcoin and want to show your support of my
826 activities, please send Bitcoin donations to my address
827 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
832 <title>Isenkram updated with a lot more hardware-package mappings
</title>
833 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
834 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
835 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
836 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
837 system
</a
> I wrote two years ago to make it easier in Debian to find
838 and install packages to get your hardware dongles to work, is still
839 going strong. It is a system to look up the hardware present on or
840 connected to the current system, and map the hardware to Debian
841 packages. It can either be done using the tools in isenkram-cli or
842 using the user space daemon in the isenkram package. The latter will
843 notify you, when inserting new hardware, about what packages to
844 install to get the dongle working. It will even provide a button to
845 click on to ask packagekit to install the packages.
</p
>
847 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
866 </pre
></p
>
868 <p
>It can also list the firware package providing firmware requested
869 by the load kernel modules, which in my case is an empty list because
870 I have all the firmware my machine need:
873 % /usr/sbin/isenkram-autoinstall-firmware -l
874 info: did not find any firmware files requested by loaded kernel modules. exiting
876 </pre
></p
>
878 <p
>The last few days I had a look at several of the around
250
879 packages in Debian with udev rules. These seem like good candidates
880 to install when a given hardware dongle is inserted, and I found
881 several that should be proposed by isenkram. I have not had time to
882 check all of them, but am happy to report that now there are
97
883 packages packages mapped to hardware by Isenkram.
11 of these
884 packages provide hardware mapping using AppStream, while the rest are
885 listed in the modaliases file provided in isenkram.
</p
>
887 <p
>These are the packages with hardware mappings at the moment. The
888 <strong
>marked packages
</strong
> are also announcing their hardware
889 support using AppStream, for everyone to use:
</p
>
891 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
892 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
893 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
894 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
895 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
896 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
897 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
898 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
899 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
900 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
901 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
902 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
903 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
904 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
905 pcscd, pidgin-blinklight, printer-driver-splix,
906 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
907 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
908 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
909 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
910 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
911 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
912 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
913 xserver-xorg-video-vmware, yubikey-personalization and
914 zd1211-firmware
</p
>
916 <p
>If you know of other packages, please let me know with a wishlist
917 bug report against the isenkram-cli package, and ask the package
919 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
920 metadata according to the guidelines
</a
> to provide the information
921 for everyone. In time, I hope to get rid of the isenkram specific
922 hardware mapping and depend exclusively on AppStream.
</p
>
924 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
925 much hardware, and suggest that the package with with any ethernet
926 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
927 the details. I hope the maintainer find time to address it soon. In
928 the mean time I provide an override in isenkram.
</p
>
933 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
934 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
936 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
937 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
939 <p
>In my early years, I played
940 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
941 Elite
</a
> on my PC. I spent many months trading and fighting in
942 space, and reached the
'elite
' fighting status before I moved on. The
943 original Elite game was available on Commodore
64 and the IBM PC
944 edition I played had a
64 KB executable. I am still impressed today
945 that the authors managed to squeeze both a
3D engine and details about
946 more than
2000 planet systems across
7 galaxies into a binary so
949 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
950 software game Oolite inspired by Elite
</a
> for a while, but did not
951 really have time to test it properly until a few days ago. It was
952 great to discover that my old knowledge about trading routes were
953 still valid. But my fighting and flying abilities were gone, so I had
954 to retrain to be able to dock on a space station. And I am still not
955 able to make much resistance when I am attacked by pirates, so I
956 bougth and mounted the most powerful laser in the rear to be able to
957 put up at least some resistance while fleeing for my life. :)
</p
>
959 <p
>When playing Elite in the late eighties, I had to discover
960 everything on my own, and I had long lists of prices seen on different
961 planets to be able to decide where to trade what. This time I had the
963 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
964 where information about each planet is easily available with common
965 price ranges and suggested trading routes. This improved my ability
966 to earn money and I have been able to earn enough to buy a lot of
967 useful equipent in a few days. I believe I originally played for
968 months before I could get a docking computer, while now I could get it
969 after less then a week.
</p
>
971 <p
>If you like science fiction and dreamed of a life as a vagabond in
972 space, you should try out Oolite. It is available for Linux, MacOSX
973 and Windows, and is included in Debian and derivatives since
2011.
</p
>
975 <p
>As usual, if you use Bitcoin and want to show your support of my
976 activities, please send Bitcoin donations to my address
977 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
982 <title>Quicker Debian installations using eatmydata
</title>
983 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
984 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
985 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
986 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
987 installation system, observing how using
988 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
989 could speed up the installation
</a
> quite a bit. My testing measured
990 speedup around
20-
40 percent for Debian Edu, where we install around
991 1000 packages from within the installer. The eatmydata package
992 provide a way to disable/delay file system flushing. This is a bit
993 risky in the general case, as files that should be stored on disk will
994 stay only in memory a bit longer than expected, causing problems if a
995 machine crashes at an inconvenient time. But for an installation, if
996 the machine crashes during installation the process is normally
997 restarted, and avoiding disk operations as much as possible to speed
998 up the process make perfect sense.
1000 <p
>I added code in the Debian Edu specific installation code to enable
1001 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
1002 but did not have time to push it any further. But a few months ago I
1003 picked it up again and worked with the libeatmydata package maintainer
1004 Mattia Rizzolo to make it easier for everyone to get this installation
1005 speedup in Debian. Thanks to our cooperation There is now an
1006 eatmydata-udeb package in Debian testing and unstable, and simply
1007 enabling/installing it in debian-installer (d-i) is enough to get the
1008 quicker installations. It can be enabled using preseeding. The
1009 following untested kernel argument should do the trick:
</p
>
1011 <blockquote
><pre
>
1012 preseed/early_command=
"anna-install eatmydata-udeb
"
1013 </pre
></blockquote
>
1015 <p
>This should ask d-i to install the package inside the d-i
1016 environment early in the installation sequence. Having it installed
1017 in d-i in turn will make sure the relevant scripts are called just
1018 after debootstrap filled /target/ with the freshly installed Debian
1019 system to configure apt to run dpkg with eatmydata. This is enough to
1020 speed up the installation process. There is a proposal to
1021 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1022 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1023 tested its impact.
</p
>
1029 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1030 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1031 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1032 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1033 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1034 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1035 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1036 elever over det ganske land skal levere inn hvert år. Det mange ikke
1037 vet er at selv om de kommersielle alternativene
1038 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1039 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1040 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1041 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1042 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1043 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1044 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1045 nynorsk, og få den automatoversatt til det andre skriftspråket.
1046 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1047 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1048 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1049 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1050 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1051 teksten din i webskjemaet der.
1053 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1054 teknologien kan du enten installere pakken
1055 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1056 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1057 api.apertium.org. Se
1058 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1059 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1060 denne teksten som ble skrevet på bokmål over maskinoversatt til
1065 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1066 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1067 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1068 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1069 veit er at sjølv om dei kommersielle alternativa
1070 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1071 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1072 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1073 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1074 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1075 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1076 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1077 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1078 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1079 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1080 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1081 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1082 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1083 teksta di i *webskjemaet der.
1085 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1086 teknologien kan du anten installera pakken
1087 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1088 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1089 *api.*apertium.org. Sjå
1090 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1091 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1092 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1098 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1099 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1101 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1102 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1103 profiler able to run benchmarking experiments on the instrumented
1104 multi-threaded program, finally
1105 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1106 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1108 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1109 blogged about the coz tool
</a
> in August working with upstream to make
1110 it suitable for Debian. There are still issues with clang
1111 compatibility, inline assembly only working x86 and minimized
1112 JavaScript libraries.
</p
>
1114 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1116 <p
><blockquote
>
1117 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1118 </blockquote
></p
>
1120 <p
>This will produce a profile.coz file in the current working
1121 directory with the profiling information. This is then given to a
1122 JavaScript application provided in the package and available from
1123 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1124 To start the local copy, invoke it in a browser like this:
</p
>
1126 <p
><blockquote
>
1127 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1128 </blockquote
></p
>
1130 <p
>See the project home page and the
1131 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1132 ;login: article on Coz
</a
> for more information on how it is
1138 <title>My own self balancing Lego Segway
</title>
1139 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1140 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1141 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1142 <description><p
>A while back I received a Gyro sensor for the NXT
1143 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1144 present. It had been on my wishlist for a while, because I wanted to
1145 build a Segway like balancing lego robot. I had already built
1146 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1147 robot
</a
> with the kids, using the light/color sensor included in the
1148 NXT kit as the balance sensor, but it was not working very well. It
1149 could balance for a while, but was very sensitive to the light
1150 condition in the room and the reflective properties of the surface and
1151 would fall over after a short while. I wanted something more robust,
1153 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1154 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1155 wishlist for some years before it suddenly showed up as a gift from my
1156 loved ones. :)
</p
>
1158 <p
>Unfortunately I have not had time to sit down and play with it
1159 since then. But that changed some days ago, when I was searching for
1160 lego segway information and came across a recipe from HiTechnic for
1162 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1163 HTWay
</a
>, a segway like balancing robot. Build instructions and
1164 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1165 code
</a
> was included, so it was just a question of putting it all
1166 together. And thanks to the great work of many Debian developers, the
1167 compiler needed to build the source for the NXT is already included in
1168 Debian, so I was read to go in less than an hour. The resulting robot
1169 do not look very impressive in its simplicity:
</p
>
1171 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1173 <p
>Because I lack the infrared sensor used to control the robot in the
1174 design from HiTechnic, I had to comment out the last task
1175 (taskControl). I simply placed /* and */ around it get the program
1176 working without that sensor present. Now it balances just fine until
1177 the battery status run low:
</p
>
1179 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1180 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1181 </video
></p
>
1183 <p
>Now we would like to teach it how to follow a line and take remote
1184 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1186 <p
>If you, like me, love LEGO and want to make sure we find the tools
1187 they need to work with LEGO in Debian and all our derivative
1188 distributions like Ubuntu, check out
1189 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1190 project page
</a
> and join the Debian LEGO team. Personally I own a
1191 RCX and NXT controller (no EV3), and would like to make sure the
1192 Debian tools needed to program the systems I own work as they
1198 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1199 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1200 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1201 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1202 <description><p
>In July
1203 <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
1204 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1205 the ability to receive SMS messages (aka without a cell phone). It is
1206 time to share some experiences and provide an updated setup.
</p
>
1208 <p
>The Signal app have worked fine for several months now, and I use
1209 it regularly to chat with my loved ones. I had a major snag at the
1210 end of my summer vacation, when the the app completely forgot my
1211 setup, identity and keys. The reason behind this major mess was
1212 running out of disk space. To avoid that ever happening again I have
1213 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1214 roll back to an earlier version if the files are wiped by mistake. I
1215 had to use it once after introducing the git backup. When rolling
1216 back to an earlier version, one need to use the
'reset session
' option
1217 in Signal to get going, and notify the people you talk with about the
1218 problem. I assume there is some sequence number tracking in the
1219 protocol to detect rollback attacks. The git repository is rather big
1220 (
674 MiB so far), but I have not tried to figure out if some of the
1221 content can be added to a .gitignore file due to lack of spare
1224 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1225 make it impossible to send messages using Signal. I could still
1226 receive them, but had to patch the code with a new timestamp to send.
1227 I believe the timeout is added by the developers to force people to
1228 upgrade to the latest version of the app, even when there is no
1229 protocol changes, to reduce the version skew among the user base and
1230 thus try to keep the number of support requests down.
</p
>
1232 <p
>Since my original recipe, the Signal source code changed slightly,
1233 making the old patch fail to apply cleanly. Below is an updated
1234 patch, including the shell wrapper I use to start Signal. The
1235 original version required a new user to locate the JavaScript console
1236 and call a function from there. I got help from a friend with more
1237 JavaScript knowledge than me to modify the code to provide a GUI
1238 button instead. This mean that to get started you just need to run
1239 the wrapper and click the
'Register without mobile phone
' to get going
1240 now. I
've also modified the timeout code to always set it to
90 days
1241 in the future, to avoid having to patch the code regularly.
</p
>
1243 <p
>So, the updated recipe for Debian Jessie:
</p
>
1247 <li
>First, install required packages to get the source code and the
1248 browser you need. Signal only work with Chrome/Chromium, as far as I
1249 know, so you need to install it.
1252 apt install git tor chromium
1253 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1254 </pre
></li
>
1256 <li
>Modify the source code using command listed in the the patch
1257 block below.
</li
>
1259 <li
>Start Signal using the run-signal-app wrapper (for example using
1260 <tt
>`pwd`/run-signal-app
</tt
>).
1262 <li
>Click on the
'Register without mobile phone
', will in a phone
1263 number you can receive calls to the next minute, receive the
1264 verification code and enter it into the form field and press
1265 'Register
'. Note, the phone number you use will be user Signal
1266 username, ie the way others can find you on Signal.
</li
>
1268 <li
>You can now use Signal to contact others. Note, new contacts do
1269 not show up in the contact list until you restart Signal, and there is
1270 no way to assign names to Contacts. There is also no way to create or
1271 update chat groups. I suspect this is because the web app do not have
1272 a associated contact database.
</li
>
1276 <p
>I am still a bit uneasy about using Signal, because of the way its
1277 main author moxie0 reject federation and accept dependencies to major
1278 corporations like Google (part of the code is fetched from Google) and
1279 Amazon (the central coordination point is owned by Amazon). See for
1281 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1282 LibreSignal issue tracker
</a
> for a thread documenting the authors
1283 view on these issues. But the network effect is strong in this case,
1284 and several of the people I want to communicate with already use
1285 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1286 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1287 laptop
</a
>? It already work on Windows and Android, and is included
1288 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1289 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1290 working on Debian Stable.
</p
>
1292 <p
>Anyway, this is the patch I apply to the Signal code to get it
1293 working. It switch to the production servers, disable to timeout,
1294 make registration easier and add the shell wrapper:
</p
>
1297 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1298 diff --git a/js/background.js b/js/background.js
1299 index
24b4c1d.
.579345f
100644
1300 --- a/js/background.js
1301 +++ b/js/background.js
1306 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1307 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1308 var SERVER_PORTS = [
80,
4433,
8443];
1309 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1310 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1311 var messageReceiver;
1312 window.getSocketStatus = function() {
1313 if (messageReceiver) {
1314 diff --git a/js/expire.js b/js/expire.js
1315 index
639aeae..beb91c3
100644
1320 'use strict
';
1321 - var BUILD_EXPIRATION =
0;
1322 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1324 window.extension = window.extension || {};
1326 diff --git a/js/views/install_view.js b/js/views/install_view.js
1327 index
7816f4f.
.1d6233b
100644
1328 --- a/js/views/install_view.js
1329 +++ b/js/views/install_view.js
1332 'click .step1
': this.selectStep.bind(this,
1),
1333 'click .step2
': this.selectStep.bind(this,
2),
1334 -
'click .step3
': this.selectStep.bind(this,
3)
1335 +
'click .step3
': this.selectStep.bind(this,
3),
1336 +
'click .callreg
': function() { extension.install(
'standalone
') },
1339 clearQR: function() {
1340 diff --git a/options.html b/options.html
1341 index dc0f28e.
.8d709f6
100644
1345 &lt;div class=
'nav
'>
1346 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1347 &lt;p
>{{ installTagline }}
&lt;/p
>
1348 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1349 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1350 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1353 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1354 &lt;span class=
'dot step2
'>&lt;/span
>
1355 &lt;span class=
'dot step3
'>&lt;/span
>
1356 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1357 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1363 +userdata=
"`pwd`/userdata
"
1364 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1365 + (cd $userdata
&& git init)
1367 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1369 + --proxy-server=
"socks://localhost:
9050" \
1370 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1372 chmod a+rx run-signal-app
1375 <p
>As usual, if you use Bitcoin and want to show your support of my
1376 activities, please send Bitcoin donations to my address
1377 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1382 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1383 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1384 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1385 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1386 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1387 system
</a
> provide a practical and easy way to figure out which
1388 packages support the hardware in a given machine. The command line
1389 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1390 convenient way to list and install packages relevant for the current
1391 hardware during system installation, both user space packages and
1392 firmware packages. The GUI background daemon on the other hand provide
1393 a pop-up proposing to install packages when a new dongle is inserted
1394 while using the computer. For example, if you plug in a smart card
1395 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1396 that package isn
't already installed, and if you plug in a USB video
1397 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1398 cheese is currently missing. This already work just fine.
</p
>
1400 <p
>But Isenkram depend on a database mapping from hardware IDs to
1401 package names. When I started no such database existed in Debian, so
1402 I made my own data set and included it with the isenkram package and
1403 made isenkram fetch the latest version of this database from git using
1404 http. This way the isenkram users would get updated package proposals
1405 as soon as I learned more about hardware related packages.
</p
>
1407 <p
>The hardware is identified using modalias strings. The modalias
1408 design is from the Linux kernel where most hardware descriptors are
1409 made available as a strings that can be matched using filename style
1410 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1411 identifiers.
</p
>
1413 <p
>The downside to the Isenkram specific database is that there is no
1414 information about relevant distribution / Debian version, making
1415 isenkram propose obsolete packages too. But along came AppStream, a
1416 cross distribution mechanism to store and collect metadata about
1417 software packages. When I heard about the proposal, I contacted the
1418 people involved and suggested to add a hardware matching rule using
1419 modalias strings in the specification, to be able to use AppStream for
1420 mapping hardware to packages. This idea was accepted and AppStream is
1421 now a great way for a package to announce the hardware it support in a
1422 distribution neutral way. I wrote
1423 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1424 recipe on how to add such meta-information
</a
> in a blog post last
1425 December. If you have a hardware related package in Debian, please
1426 announce the relevant hardware IDs using AppStream.
</p
>
1428 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1429 RCX or NXT unit, announce this support using AppStream. The effect is
1430 that when you insert such LEGO robot controller into your Debian
1431 machine, Isenkram will propose to install the packages needed to get
1432 it working. The intention is that this should allow the local user to
1433 start programming his robot controller right away without having to
1434 guess what packages to use or which permissions to fix.
</p
>
1436 <p
>But when I sat down with my son the other day to program our NXT
1437 unit using his Debian Stretch computer, I discovered something
1438 annoying. The local console user (ie my son) did not get access to
1439 the USB device for programming the unit. This used to work, but no
1440 longer in Jessie and Stretch. After some investigation and asking
1441 around on #debian-devel, I discovered that this was because udev had
1442 changed the mechanism used to grant access to local devices. The
1443 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1444 no longer applied, because LDAP users no longer was added to the
1445 plugdev group during login. Michael Biebl told me that this method
1446 was obsolete and the new method used ACLs instead. This was good
1447 news, as the plugdev mechanism is a mess when using a remote user
1448 directory like LDAP. Using ACLs would make sure a user lost device
1449 access when she logged out, even if the user left behind a background
1450 process which would retain the plugdev membership with the ConsoleKit
1451 setup. Armed with this knowledge I moved on to fix the access problem
1452 for the LEGO Mindstorms related packages.
</p
>
1454 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1455 applied directly for a device, or is applied in
1456 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1457 LEGO Mindstorms udev rules did not have a class, I decided to add the
1458 tag directly in the udev rules files included in the packages. Here
1459 is one example. For the nqc C compiler for the RCX, the
1460 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1462 <p
><pre
>
1463 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1464 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1465 </pre
></p
>
1467 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1468 packages using plugdev in their /lib/udev/rules.d/ files should be
1469 changed to use this tag (either directly or indirectly via
1470 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1471 to detect this?
</p
>
1473 <p
>I
've been unable to find good documentation on the uaccess feature.
1474 It is unclear to me if the uaccess tag is an internal implementation
1475 detail like the udev-acl tag used by
1476 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1477 indirect method is the preferred way. Michael
1478 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1479 documentation from the systemd project
</a
> and I hope it will make
1480 this clearer. For now I use the generic classes when they exist and
1481 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1482 directly if no such class exist.
</p
>
1484 <p
>To learn more about the isenkram system, please check out
1485 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1486 blog posts tagged isenkram
</a
>.
</p
>
1488 <p
>To help out making life for LEGO constructors in Debian easier,
1489 please join us on our IRC channel
1490 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1491 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1492 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1493 list is not yet created, but we are working on it. :)
</p
>
1495 <p
>As usual, if you use Bitcoin and want to show your support of my
1496 activities, please send Bitcoin donations to my address
1497 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1502 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1503 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1504 <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>
1505 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1506 <description><p
>In April we
1507 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1508 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1509 how to set up and administrate a Debian system. Today I am happy to
1510 report that the first draft is now publicly available. You can find
1511 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1512 Administrator
's Handbook page
</a
> (under Other languages). The first
1513 eight chapters have a first draft translation, and we are working on
1514 proofreading the content. If you want to help out, please start
1516 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1517 hosted weblate project page
</a
>, and get in touch using
1518 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1519 translators mailing list
</a
>. Please also check out
1520 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1521 contributors
</a
>. A good way to contribute is to proofread the text
1522 and update weblate if you find errors.
</p
>
1524 <p
>Our goal is still to make the Norwegian book available on paper as well as
1525 electronic form.
</p
>
1530 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1531 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1532 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1533 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1534 <description><p
>This summer, I read a great article
1535 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1536 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1537 how to profile multi-threaded programs. It presented a system for
1538 profiling software by running experiences in the running program,
1539 testing how run time performance is affected by
"speeding up
" parts of
1540 the code to various degrees compared to a normal run. It does this by
1541 slowing down parallel threads while the
"faster up
" code is running
1542 and measure how this affect processing time. The processing time is
1543 measured using probes inserted into the code, either using progress
1544 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1545 can also measure unmodified code by measuring complete the program
1546 runtime and running the program several times instead.
</p
>
1548 <p
>The project and presentation was so inspiring that I would like to
1549 get the system into Debian. I
1550 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1551 a WNPP request for it
</a
> and contacted upstream to try to make the
1552 system ready for Debian by sending patches. The build process need to
1553 be changed a bit to avoid running
'git clone
' to get dependencies, and
1554 to include the JavaScript web page used to visualize the collected
1555 profiling information included in the source package.
1556 But I expect that should work out fairly soon.
</p
>
1558 <p
>The way the system work is fairly simple. To run an coz experiment
1559 on a binary with debug symbols available, start the program like this:
1561 <p
><blockquote
><pre
>
1562 coz run --- program-to-run
1563 </pre
></blockquote
></p
>
1565 <p
>This will create a text file profile.coz with the instrumentation
1566 information. To show what part of the code affect the performance
1567 most, use a web browser and either point it to
1568 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1569 or use the copy from git (in the gh-pages branch). Check out this web
1570 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
1571 profiling more useful you include
&lt;coz.h
&gt; and insert the
1572 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1573 code, rebuild and run the profiler. This allow coz to do more
1574 targeted experiments.
</p
>
1576 <p
>A video published by ACM
1577 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1578 Coz profiler
</a
> is available from Youtube. There is also a paper
1579 from the
25th Symposium on Operating Systems Principles available
1581 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1582 finding code that counts with causal profiling
</a
>.
</p
>
1584 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1585 for Coz is available from github. It will only build with clang
1587 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1588 feature missing in GCC
</a
>, but I
've submitted
1589 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1590 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1592 <p
>Please get in touch if you, like me, would like to see this piece
1593 of software in Debian. I would very much like some help with the
1594 packaging effort, as I lack the in depth knowledge on how to package
1595 C++ libraries.
</p
>
1600 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1601 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1602 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1603 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1604 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1605 to be a slight challenge. Here is the recipe if I ever need to do it
1606 again. It all started by me wanting to try the recipe to set up
1607 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1608 hardened Android installation
</a
> from the Tor project blog on a
1609 device I had access to. It is a old mobile phone with a broken
1610 microphone The initial idea had been to just
1611 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1612 CyanogenMod on it
</a
>, but did not quite find time to start on it
1613 until a few days ago.
</p
>
1615 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1616 loader (press volume down and power at the same time), (
2) select
1617 'fastboot
' before (
3) connecting the device via USB to a Linux
1618 machine, (
4) request the device identifier token by running
'fastboot
1619 oem get_identifier_token
', (
5) request the device unlocking key using
1620 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1621 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1623 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1624 or newer, and the device I was working on had
2.00.0027. This
1625 apparently can be easily fixed by downloading a Windows program and
1626 running it on your Windows machine, if you accept the terms Microsoft
1627 require you to accept to use Windows - which I do not. So I had to
1628 come up with a different approach. I got a lot of help from AndyCap
1629 on #nuug, and would not have been able to get this working without
1632 <p
>First I needed to extract the hboot firmware from
1633 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1634 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1635 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1636 project named unruu
</a
> using libunshield. The unshield tool did not
1637 recognise the file format, but unruu worked and extracted rom.zip,
1638 containing the new hboot firmware and a text file describing which
1639 devices it would work for.
</p
>
1641 <p
>Next, I needed to get the new firmware into the device. For this I
1642 followed some instructions
1643 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1644 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1645 machine with Debian testing:
</p
>
1647 <p
><pre
>
1648 adb reboot-bootloader
1649 fastboot oem rebootRUU
1650 fastboot flash zip rom.zip
1651 fastboot flash zip rom.zip
1653 </pre
></p
>
1655 <p
>The flash command apparently need to be done twice to take effect,
1656 as the first is just preparations and the second one do the flashing.
1657 The adb command is just to get to the boot loader menu, so turning the
1658 device on while holding volume down and the power button should work
1661 <p
>With the new hboot version in place I could start following the
1662 instructions on the HTC developer web site. I got the device token
1663 like this:
</p
>
1665 <p
><pre
>
1666 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1669 <p
>And once I got the unlock code via email, I could use it like
1672 <p
><pre
>
1673 fastboot flash unlocktoken Unlock_code.bin
1674 </pre
></p
>
1676 <p
>And with that final step in place, the phone was unlocked and I
1677 could start stuffing the software of my own choosing into the device.
1678 So far I only inserted a replacement recovery image to wipe the phone
1679 before I start. We will see what happen next. Perhaps I should
1680 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1685 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1686 <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>
1687 <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>
1688 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1689 <description><p
>For a while now, I have wanted to test
1690 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1691 said to provide end to end encrypted communication and several of my
1692 friends and family are already using it. As I by choice do not own a
1693 mobile phone, this proved to be harder than expected. And I wanted to
1694 have the source of the client and know that it was the code used on my
1695 machine. But yesterday I managed to get it working. I used the
1696 Github source, compared it to the source in
1697 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1698 Signal Chrome app
</a
> available from the Chrome web store, applied
1699 patches to use the production Signal servers, started the app and
1700 asked for the hidden
"register without a smart phone
" form. Here is
1701 the recipe how I did it.
</p
>
1703 <p
>First, I fetched the Signal desktop source from Github, using
1706 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1709 <p
>Next, I patched the source to use the production servers, to be
1710 able to talk to other Signal users:
</p
>
1713 cat
&lt;
&lt;EOF | patch -p0
1714 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1715 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1716 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1721 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1722 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1723 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1724 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1725 var messageReceiver;
1726 window.getSocketStatus = function() {
1727 if (messageReceiver) {
1728 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1729 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1730 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1733 'use strict
';
1734 - var BUILD_EXPIRATION =
0;
1735 + var BUILD_EXPIRATION =
1474492690000;
1737 window.extension = window.extension || {};
1742 <p
>The first part is changing the servers, and the second is updating
1743 an expiration timestamp. This timestamp need to be updated regularly.
1744 It is set
90 days in the future by the build process (Gruntfile.js).
1745 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1747 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1748 script to launch Signal in Chromium.
</p
>
1755 --proxy-server=
"socks://localhost:
9050" \
1756 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1759 <p
> The script start the app and configure Chromium to use the Tor
1760 SOCKS5 proxy to make sure those controlling the Signal servers (today
1761 Amazon and Whisper Systems) as well as those listening on the lines
1762 will have a harder time location my laptop based on the Signal
1763 connections if they use source IP address.
</p
>
1765 <p
>When the script starts, one need to follow the instructions under
1766 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1767 repository. I right clicked on the Signal window to get up the
1768 Chromium debugging tool, visited the
'Console
' tab and wrote
1769 'extension.install(
"standalone
")
' on the console prompt to get the
1770 registration form. Then I entered by land line phone number and
1771 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1772 repeated the verification code three times. After entering the number
1773 into the verification code field in the form, I could start using
1774 Signal from my laptop.
1776 <p
>As far as I can tell, The Signal app will leak who is talking to
1777 whom and thus who know who to those controlling the central server,
1778 but such leakage is hard to avoid with a centrally controlled server
1779 setup. It is something to keep in mind when using Signal - the
1780 content of your chats are harder to intercept, but the meta data
1781 exposing your contact network is available to people you do not know.
1782 So better than many options, but not great. And sadly the usage is
1783 connected to my land line, thus allowing those controlling the server
1784 to associate it to my home and person. I would prefer it if only
1785 those I knew could tell who I was on Signal. There are options
1786 avoiding such information leakage, but most of my friends are not
1787 using them, so I am stuck with Signal for now.
</p
>
1789 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1791 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1792 and updated recipe for using the Signal app without a mobile
1793 phone
</a
>.
</p
>
1798 <title>The new
"best
" multimedia player in Debian?
</title>
1799 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1800 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1801 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1802 <description><p
>When I set out a few weeks ago to figure out
1803 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1804 multimedia player in Debian claimed to support most file formats /
1805 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1806 the various players claimed support for. The range was from
55 to
130
1807 MIME types. I suspect most media formats are supported by all
1808 players, but this is not really reflected in the MimeTypes values in
1809 their desktop files. There are probably also some bogus MIME types
1810 listed, but it is hard to identify which one this is.
</p
>
1812 <p
>Anyway, in the mean time I got in touch with upstream for some of
1813 the players suggesting to add more MIME types to their desktop files,
1814 and decided to spend some time myself improving the situation for my
1815 favorite media player VLC. The fixes for VLC entered Debian unstable
1816 yesterday. The complete list of MIME types can be seen on the
1817 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1818 player MIME type support status
</a
> Debian wiki page.
</p
>
1820 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1821 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1822 kmplayer. I am sure some of the other players desktop files support
1823 several of the formats currently listed as working only with vlc,
1824 toten and parole.
</p
>
1826 <p
>A sad observation is that only
14 MIME types are listed as
1827 supported by all the tested multimedia players in Debian in their
1828 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1829 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1830 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1831 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1832 it sad that video/ogg and video/webm is not supported by all the media
1833 players in Debian. As far as I can tell, all of them can handle both
1839 <title>A program should be able to open its own files on Linux
</title>
1840 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1841 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1842 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1843 <description><p
>Many years ago, when koffice was fresh and with few users, I
1844 decided to test its presentation tool when making the slides for a
1845 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1846 wrote the first draft of the slides, saved the result and went to bed
1847 the day before I would give the talk. The next day I took a plane to
1848 the location where the meeting should take place, and on the plane I
1849 started up koffice again to polish the talk a bit, only to discover
1850 that kpresenter refused to load its own data file. I cursed a bit and
1851 started making the slides again from memory, to have something to
1852 present when I arrived. I tested that the saved files could be
1853 loaded, and the day seemed to be rescued. I continued to polish the
1854 slides until I suddenly discovered that the saved file could no longer
1855 be loaded into kpresenter. In the end I had to rewrite the slides
1856 three times, condensing the content until the talk became shorter and
1857 shorter. After the talk I was able to pinpoint the problem
&ndash;
1858 kpresenter wrote inline images in a way itself could not understand.
1859 Eventually that bug was fixed and kpresenter ended up being a great
1860 program to make slides. The point I
'm trying to make is that we
1861 expect a program to be able to load its own data files, and it is
1862 embarrassing to its developers if it can
't.
</p
>
1864 <p
>Did you ever experience a program failing to load its own data
1865 files from the desktop file browser? It is not a uncommon problem. A
1866 while back I discovered that the screencast recorder
1867 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1868 browser would refuse to open. No video player claimed to understand
1869 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1870 returning the application/ogg MIME type, which no video player I had
1871 installed listed as a MIME type they would understand. I asked for
1872 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1873 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1874 several video players to add video/ogg to their desktop files, to give
1875 the file browser an idea what to do about Ogg Theora files. After a
1876 while, the desktop file browsers in Debian started to handle the
1877 output from gtk-recordmydesktop properly.
</p
>
1879 <p
>But history repeats itself. A few days ago I tested the music
1880 system Rosegarden again, and I discovered that the KDE and xfce file
1881 browsers did not know what to do with the Rosegarden project files
1882 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1883 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1884 included in the next upload. To increase the chance of me remembering
1885 how to fix the problem next time some program fail to load its files
1886 from the file browser, here are some notes on how to fix it.
</p
>
1888 <p
>The file browsers in Debian in general operates on MIME types.
1889 There are two sources for the MIME type of a given file. The output from
1890 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1891 shared MIME type registry (under /usr/share/mime/). The file MIME
1892 type is mapped to programs supporting the MIME type, and this
1893 information is collected from
1894 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1895 desktop files
</a
> available in /usr/share/applications/. If there is
1896 one desktop file claiming support for the MIME type of the file, it is
1897 activated when asking to open a given file. If there are more, one
1898 can normally select which one to use by right-clicking on the file and
1899 selecting the wanted one using
'Open with
' or similar. In general
1900 this work well. But it depend on each program picking a good MIME
1902 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1903 MIME type registered with IANA
</a
>), file and/or the shared MIME
1904 registry recognizing the file and the desktop file to list the MIME
1905 type in its list of supported MIME types.
</p
>
1907 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1908 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1909 Shared MIME database
</a
> look like this:
</p
>
1911 <p
><blockquote
><pre
>
1912 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1913 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1914 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1915 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1916 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1917 &lt;glob pattern=
"*.rg
"/
&gt;
1918 &lt;/mime-type
&gt;
1919 &lt;/mime-info
&gt;
1920 </pre
></blockquote
></p
>
1922 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1923 (it is a gzipped XML file). Note, it is much better to use an
1924 official MIME type registered with IANA than it is to make up ones own
1925 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1927 <p
>The desktop file of the rosegarden program failed to list
1928 audio/x-rosegarden in its list of supported MIME types, causing the
1929 file browsers to have no idea what to do with *.rg files:
</p
>
1931 <p
><blockquote
><pre
>
1932 % grep Mime /usr/share/applications/rosegarden.desktop
1933 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1934 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1936 </pre
></blockquote
></p
>
1938 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1939 MimeType= line.
</p
>
1941 <p
>If you run into a file which fail to open the correct program when
1942 selected from the file browser, please check out the output from
1943 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1944 MIME type is registered somewhere under /usr/share/mime/ and check
1945 that some desktop file under /usr/share/applications/ is claiming
1946 support for this MIME type. If not, please report a bug to have it
1952 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1953 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1954 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1955 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1956 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1957 system
</a
> is a user-focused solution in Debian for handling hardware
1958 related packages. The idea is to have a database of mappings between
1959 hardware and packages, and pop up a dialog suggesting for the user to
1960 install the packages to use a given hardware dongle. Some use cases
1961 are when you insert a Yubikey, it proposes to install the software
1962 needed to control it; when you insert a braille reader list it
1963 proposes to install the packages needed to send text to the reader;
1964 and when you insert a ColorHug screen calibrator it suggests to
1965 install the driver for it. The system work well, and even have a few
1966 command line tools to install firmware packages and packages for the
1967 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1969 <p
>The system was initially written using aptdaemon, because I found
1970 good documentation and example code on how to use it. But aptdaemon
1971 is going away and is generally being replaced by
1972 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1973 so Isenkram needed a rewrite. And today, thanks to the great patch
1974 from my college Sunil Mohan Adapa in the FreedomBox project, the
1975 rewrite finally took place. I
've just uploaded a new version of
1976 Isenkram into Debian Unstable with the patch included, and the default
1977 for the background daemon is now to use PackageKit. To check it out,
1978 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1979 and see if it is recognised.
</p
>
1981 <p
>If you want to know what kind of packages isenkram would propose for
1982 the machine it is running on, you can check out the isenkram-lookup
1983 program. This is what it look like on a Thinkpad X230:
</p
>
1985 <p
><blockquote
><pre
>
2001 </pre
></blockquote
></p
>
2003 <p
>The hardware mappings come from several places. The preferred way
2004 is for packages to announce their hardware support using
2005 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2006 cross distribution appstream system
</a
>.
2008 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2009 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2014 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2015 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2016 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2017 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2018 <description><p
>Yesterday I updated the
2019 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2020 package in Debian
</a
> with a few patches sent to me by skilled and
2021 enterprising users. There were some nice user and visible changes.
2022 First of all, both desktop menu entries now work. A design flaw in
2023 one of the script made the history graph fail to show up (its PNG was
2024 dumped in ~/.xsession-errors) if no controlling TTY was available.
2025 The script worked when called from the command line, but not when
2026 called from the desktop menu. I changed this to look for a DISPLAY
2027 variable or a TTY before deciding where to draw the graph, and now the
2028 graph window pop up as expected.
</p
>
2030 <p
>The next new feature is a discharge rate estimator in one of the
2031 graphs (the one showing the last few hours). New is also the user of
2032 colours showing charging in blue and discharge in red. The percentages
2033 of this graph is relative to last full charge, not battery design
2036 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2038 <p
>The other graph show the entire history of the collected battery
2039 statistics, comparing it to the design capacity of the battery to
2040 visualise how the battery life time get shorter over time. The red
2041 line in this graph is what the previous graph considers
100 percent:
2043 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2045 <p
>In this graph you can see that I only charge the battery to
80
2046 percent of last full capacity, and how the capacity of the battery is
2047 shrinking. :(
</p
>
2049 <p
>The last new feature is in the collector, which now will handle
2050 more hardware models. On some hardware, Linux power supply
2051 information is stored in /sys/class/power_supply/ACAD/, while the
2052 collector previously only looked in /sys/class/power_supply/AC/. Now
2053 both are checked to figure if there is power connected to the
2056 <p
>If you are interested in how your laptop battery is doing, please
2058 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2059 in Debian unstable, or rebuild it on Jessie to get it working on
2060 Debian stable. :) The upstream source is available from
<a
2061 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2062 Patches are very welcome.
</p
>
2064 <p
>As usual, if you use Bitcoin and want to show your support of my
2065 activities, please send Bitcoin donations to my address
2066 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2071 <title>Debian now with ZFS on Linux included
</title>
2072 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2073 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2074 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2075 <description><p
>Today, after many years of hard work from many people,
2076 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2077 Debian. The package status can be seen on
2078 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2079 for zfs-linux
</a
>. and
2080 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2081 team status page
</a
>. If you want to help out, please join us.
2082 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2083 source code
</a
> is available via git on Alioth. It would also be
2084 great if you could help out with
2085 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2086 it is an important piece of the puzzle to get ZFS working.
</p
>
2091 <title>What is the best multimedia player in Debian?
</title>
2092 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2093 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2094 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2095 <description><p
><strong
>Where I set out to figure out which multimedia player in
2096 Debian claim support for most file formats.
</strong
></p
>
2098 <p
>A few years ago, I had a look at the media support for Browser
2099 plugins in Debian, to get an idea which plugins to include in Debian
2100 Edu. I created a script to extract the set of supported MIME types
2101 for each plugin, and used this to find out which multimedia browser
2102 plugin supported most file formats / media types.
2103 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2104 result
</a
> can still be seen on the Debian wiki, even though it have
2105 not been updated for a while. But browser plugins are less relevant
2106 these days, so I thought it was time to look at standalone
2109 <p
>A few days ago I was tired of VLC not being listed as a viable
2110 player when I wanted to play videos from the Norwegian National
2111 Broadcasting Company, and decided to investigate why. The cause is a
2112 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2113 desktop file
</a
>. In the process I wrote a script to compare the set
2114 of MIME types announced in the desktop file and the browser plugin,
2115 only to discover that there is quite a large difference between the
2116 two for VLC. This discovery made me dig up the script I used to
2117 compare browser plugins, and adjust it to compare desktop files
2118 instead, to try to figure out which multimedia player in Debian
2119 support most file formats.
</p
>
2121 <p
>The result can be seen on the Debian Wiki, as
2122 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2123 table listing all MIME types supported by one of the packages included
2124 in the table
</a
>, with the package supporting most MIME types being
2125 listed first in the table.
</p
>
2127 </p
>The best multimedia player in Debian? It is totem, followed by
2128 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2129 kmplayer. Time for the other players to update their announced MIME
2135 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2136 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2137 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2138 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2139 <description>A friend of mine made me aware of
2140 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2141 handheld computer which will be delivered with Debian preinstalled. I
2142 would love to get one of those for my birthday. :)
</p
>
2144 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2145 plugs and many others connectors, and include a full keyboard and a
5"
2146 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2147 day of battery life time, but I have not seen any independent tests
2148 confirming this. The vendor is still collecting preorders, and the
2149 last I heard last night was that
22 more orders were needed before
2150 production started.
</p
>
2152 <p
>As far as I know, this is the first handheld preinstalled with
2153 Debian. Please let me know if you know of any others. Is it the
2154 first computer being sold with Debian preinstalled?
</p
>
2159 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2160 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2161 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2162 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2163 <description><p
>During this weekends
2164 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2165 squashing party and developer gathering
</a
>, we decided to do our part
2166 to make sure there are good books about Debian available in Norwegian
2167 Bokmål, and got in touch with the people behind the
2168 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2169 project
</a
> to get started. If you want to help out, please start
2171 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2172 hosted weblate project page
</a
>, and get in touch using
2173 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2174 translators mailing list
</a
>. Please also check out
2175 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2176 contributors
</a
>.
</p
>
2178 <p
>The book is already available on paper in English, French and
2179 Japanese, and our goal is to get it available on paper in Norwegian
2180 Bokmål too. In addition to the paper edition, there are also EPUB and
2181 Mobi versions available. And there are incomplete translations
2182 available for many more languages.
</p
>
2187 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2188 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2189 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2190 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2191 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2192 packages in Debian, and was quite surprised with what I found. I use
2193 ZFS myself at home, but did not really expect many others to do so.
2194 But I might be wrong.
</p
>
2196 <p
>According to
2197 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2198 results for spl-linux
</a
>, there are
1019 Debian installations, or
2199 0.53% of the population, with the package installed. As far as I know
2200 the only use of the spl-linux package is as a support library for ZFS
2201 on Linux, so I use it here as proxy for measuring the number of ZFS
2202 installation on Linux in Debian. In the kFreeBSD variant of Debian
2203 the ZFS feature is already available, and there
2204 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2205 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2206 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2208 <p
>But even though the Debian project leader Lucas Nussbaum
2209 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2210 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2211 cleared, the package is still not in Debian. The package is again in
2212 the NEW queue. Several uploads have been rejected so far because the
2213 debian/copyright file was incomplete or wrong, but there is no reason
2214 to give up. The current status can be seen on
2215 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2216 team status page
</a
>, and
2217 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2218 source code
</a
> is available on Alioth.
</p
>
2220 <p
>As I want ZFS to be included in next version of Debian to make sure
2221 my home server can function in the future using only official Debian
2222 packages, and the current blocker is to get the debian/copyright file
2223 accepted by the FTP masters in Debian, I decided a while back to try
2224 to help out the team. This was the background for my blog post about
2225 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2226 updating and checking debian/copyright semi-automatically
</a
>, and I
2227 used the techniques I explored there to try to find any errors in the
2228 copyright file. It is not very easy to check every one of the around
2229 2000 files in the source package, but I hope we this time got it
2230 right. If you want to help out, check out the git source and try to
2231 find missing entries in the debian/copyright file.
</p
>
2236 <title>Full battery stats collector is now available in Debian
</title>
2237 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2238 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2239 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2240 <description><p
>Since this morning, the battery-stats package in Debian include an
2241 extended collector that will collect the complete battery history for
2242 later processing and graphing. The original collector store the
2243 battery level as percentage of last full level, while the new
2244 collector also record battery vendor, model, serial number, design
2245 full level, last full level and current battery level. This make it
2246 possible to predict the lifetime of the battery as well as visualise
2247 the energy flow when the battery is charging or discharging.
</p
>
2249 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2250 in the version
0.5.1 package in unstable. Get the new battery level graph
2251 and lifetime prediction by running:
2253 <p
><pre
>
2254 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2255 </pre
></p
>
2257 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2259 <p
>The flow in/out of the battery can be seen by running (no menu
2260 entry yet):
</p
>
2262 <p
><pre
>
2263 /usr/share/battery-stats/battery-stats-graph-flow
2264 </pre
></p
>
2266 <p
>I
'm not quite happy with the way the data is visualised, at least
2267 when there are few data points. The graphs look a bit better with a
2268 few years of data.
</p
>
2270 <p
>A while back one important feature I use in the battery stats
2271 collector broke in Debian. The scripts in
2272 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2273 suspect it happened when Jessie started using systemd, but I do not
2274 know. The issue is reported as
2275 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2276 pm-utils. I managed to work around it by adding an udev rule to call
2277 the collector script every time the power connector is connected and
2278 disconnected. With this fix in place it was finally time to make a
2279 new release of the package, and get it into Debian.
</p
>
2281 <p
>If you are interested in how your laptop battery is doing, please
2283 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2284 in Debian unstable, or rebuild it on Jessie to get it working on
2285 Debian stable. :) The upstream source is available from
2286 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2287 As always, patches are very welcome.
</p
>
2292 <title>Making battery measurements a little easier in Debian
</title>
2293 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2294 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2295 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2296 <description><p
>Back in September, I blogged about
2297 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2298 system I wrote to collect statistics about my laptop battery
</a
>, and
2299 how it showed the decay and death of this battery (now replaced). I
2300 created a simple deb package to handle the collection and graphing,
2301 but did not want to upload it to Debian as there were already
2302 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2303 package in Debian
</a
> that should do the same thing, and I did not see
2304 a point of uploading a competing package when battery-stats could be
2305 fixed instead. I reported a few bugs about its non-function, and
2306 hoped someone would step in and fix it. But no-one did.
</p
>
2308 <p
>I got tired of waiting a few days ago, and took matters in my own
2309 hands. The end result is that I am now the new upstream developer of
2310 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2311 battery-stats in Debian, and the package in Debian unstable is finally
2312 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2313 information provided by the Linux kernel. If you install the
2314 battery-stats package from unstable now, you will be able to get a
2315 graph of the current battery fill level, to get some idea about the
2316 status of the battery. The source package build and work just fine in
2317 Debian testing and stable (and probably oldstable too, but I have not
2318 tested). The default graph you get for that system look like this:
</p
>
2320 <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
>
2322 <p
>My plans for the future is to merge my old scripts into the
2323 battery-stats package, as my old scripts collected a lot more details
2324 about the battery. The scripts are merged into the upstream
2325 battery-stats git repository already, but I am not convinced they work
2326 yet, as I changed a lot of paths along the way. Will have to test a
2327 bit more before I make a new release.
</p
>
2329 <p
>I will also consider changing the file format slightly, as I
2330 suspect the way I combine several values into one field might make it
2331 impossible to know the type of the value when using it for processing
2332 and graphing.
</p
>
2334 <p
>If you would like I would like to keep an close eye on your laptop
2335 battery, check out the battery-stats package in
2336 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2338 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2339 I would love some help to improve the system further.
</p
>
2344 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2345 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2346 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2347 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2348 <description><p
>Making packages for Debian requires quite a lot of attention to
2349 details. And one of the details is the content of the
2350 debian/copyright file, which should list all relevant licenses used by
2351 the code in the package in question, preferably in
2352 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2353 readable DEP5 format
</a
>.
</p
>
2355 <p
>For large packages with lots of contributors it is hard to write
2356 and update this file manually, and if you get some detail wrong, the
2357 package is normally rejected by the ftpmasters. So getting it right
2358 the first time around get the package into Debian faster, and save
2359 both you and the ftpmasters some work.. Today, while trying to figure
2360 out what was wrong with
2361 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2362 zfsonlinux copyright file
</a
>, I decided to spend some time on
2363 figuring out the options for doing this job automatically, or at least
2364 semi-automatically.
</p
>
2366 <p
>Lucikly, there are at least two tools available for generating the
2367 file based on the code in the source package,
2368 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2369 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2370 not sure which one of them came first, but both seem to be able to
2371 create a sensible draft file. As far as I can tell, none of them can
2372 be trusted to get the result just right, so the content need to be
2373 polished a bit before the file is OK to upload. I found the debmake
2375 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2376 blog posts from
2014</a
>.
2378 <p
>To generate using debmake, use the -cc option:
2380 <p
><pre
>
2381 debmake -cc
> debian/copyright
2382 </pre
></p
>
2384 <p
>Note there are some problems with python and non-ASCII names, so
2385 this might not be the best option.
</p
>
2387 <p
>The cme option is based on a config parsing library, and I found
2389 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2390 blog post from
2015</a
>. To generate using cme, use the
'update
2391 dpkg-copyright
' option:
2393 <p
><pre
>
2394 cme update dpkg-copyright
2395 </pre
></p
>
2397 <p
>This will create or update debian/copyright. The cme tool seem to
2398 handle UTF-
8 names better than debmake.
</p
>
2400 <p
>When the copyright file is created, I would also like some help to
2401 check if the file is correct. For this I found two good options,
2402 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2403 to focus on license types and file matching, and is able to detect
2404 ineffective blocks in the copyright file. The latter reports missing
2405 copyright holders and years, but was confused by inconsistent license
2406 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2407 fix all issues reported by them before uploading. But I do not know
2408 if the tools and the ftpmasters agree on what is important to fix in a
2409 copyright file, so the package might still be rejected.
</p
>
2411 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2412 will read through the source and try to find all copyright statements.
2413 It is not comparing the result to the content of debian/copyright, but
2414 can be useful when verifying the content of the copyright file.
</p
>
2416 <p
>Are you aware of better tools in Debian to create and update
2417 debian/copyright file. Please let me know, or blog about it on
2418 planet.debian.org.
</p
>
2420 <p
>As usual, if you use Bitcoin and want to show your support of my
2421 activities, please send Bitcoin donations to my address
2422 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2424 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2425 on how to use licensecheck and cdbs to create a draft copyright file
2427 <p
><pre
>
2428 licensecheck --copyright -r `find * -type f` | \
2429 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2430 </pre
></p
>
2432 <p
>He mentioned that he normally check the generated file into the
2433 version control system to make it easier to discover license and
2434 copyright changes in the upstream source. I will try to do the same
2435 with my packages in the future.
</p
>
2437 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2438 against using -quiet for new users, so I removed it from the proposed
2439 command line.
</p
>
2444 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2445 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2446 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2447 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2448 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2449 is taking shape in Debian, and one provided feature is a very
2450 convenient way to tell you which package to install to make a given
2451 firmware file available when the kernel is looking for it. This can
2452 be done using apt-file too, but that is for someone else to blog
2455 <p
>Here is a small recipe to find the package with a given firmware
2456 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2457 picked from the set of firmware announced using appstream in Debian
2458 unstable. In general you would be looking for the firmware requested
2459 by the kernel during kernel module loading. To find the package
2460 providing the example file, do like this:
</p
>
2462 <blockquote
><pre
>
2463 % apt install appstream
2467 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2468 awk
'/Package:/ {print $
2}
'
2471 </pre
></blockquote
>
2473 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2474 appstream wiki
</a
> page to learn how to embed the package metadata in
2475 a way appstream can use.
</p
>
2477 <p
>This same approach can be used to find any package supporting a
2478 given MIME type. This is very useful when you get a file you do not
2479 know how to handle. First find the mime type using
<tt
>file
2480 --mime-type
</tt
>, and next look up the package providing support for
2481 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2482 and you can find all packages handling this type like this:
</p
>
2484 <blockquote
><pre
>
2485 % apt install appstream
2489 % appstreamcli what-provides mimetype image/svg+xml | \
2490 awk
'/Package:/ {print $
2}
'
2512 </pre
></blockquote
>
2514 <p
>I believe the MIME types are fetched from the desktop file for
2515 packages providing appstream metadata.
</p
>
2520 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2521 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2522 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2523 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2524 <description><p
>Most people seem not to realise that every time they walk around
2525 with the computerised radio beacon known as a mobile phone their
2526 position is tracked by the phone company and often stored for a long
2527 time (like every time a SMS is received or sent). And if their
2528 computerised radio beacon is capable of running programs (often called
2529 mobile apps) downloaded from the Internet, these programs are often
2530 also capable of tracking their location (if the app requested access
2531 during installation). And when these programs send out information to
2532 central collection points, the location is often included, unless
2533 extra care is taken to not send the location. The provided
2534 information is used by several entities, for good and bad (what is
2535 good and bad, depend on your point of view). What is certain, is that
2536 the private sphere and the right to free movement is challenged and
2537 perhaps even eradicated for those announcing their location this way,
2538 when they share their whereabouts with private and public
2541 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2543 <p
>The phone company logs provide a register of locations to check out
2544 when one want to figure out what the tracked person was doing. It is
2545 unavailable for most of us, but provided to selected government
2546 officials, company staff, those illegally buying information from
2547 unfaithful servants and crackers stealing the information. But the
2548 public information can be collected and analysed, and a free software
2549 tool to do so is called
2550 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2551 discovered it when I read
2552 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2553 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2554 November
2014, and decided to check if it was available in Debian.
2555 The python program was in Debian, but
2556 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2557 Debian
</a
> was completely broken and practically unmaintained. I
2558 uploaded a new version which did not work quite right, but did not
2559 have time to fix it then. This Christmas I decided to finally try to
2560 get Creepy operational in Debian. Now a fixed version is available in
2561 Debian unstable and testing, and almost all Debian specific patches
2563 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2565 <p
>The Creepy program visualises geolocation information fetched from
2566 Twitter, Instagram, Flickr and Google+, and allow one to get a
2567 complete picture of every social media message posted recently in a
2568 given area, or track the movement of a given individual across all
2569 these services. Earlier it was possible to use the search API of at
2570 least some of these services without identifying oneself, but these
2571 days it is impossible. This mean that to use Creepy, you need to
2572 configure it to log in as yourself on these services, and provide
2573 information to them about your search interests. This should be taken
2574 into account when using Creepy, as it will also share information
2575 about yourself with the services.
</p
>
2577 <p
>The picture above show the twitter messages sent from (or at least
2578 geotagged with a position from) the city centre of Oslo, the capital
2579 of Norway. One useful way to use Creepy is to first look at
2580 information tagged with an area of interest, and next look at all the
2581 information provided by one or more individuals who was in the area.
2582 I tested it by checking out which celebrity provide their location in
2583 twitter messages by checkout out who sent twitter messages near a
2584 Norwegian TV station, and next could track their position over time,
2585 making it possible to locate their home and work place, among other
2586 things. A similar technique have been
2587 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2588 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2589 tool to discover lying governments, and a useful tool to help people
2590 understand the value of the private information they provide to the
2593 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2594 it depend on several python modules currently missing in Jessie (at
2595 least python-instagram, python-flickrapi and
2596 python-requests-toolbelt).
</p
>
2598 <p
>(I have uploaded
2599 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2600 screenshots.debian.net
</a
> and licensed it under the same terms as the
2601 Creepy program in Debian.)
</p
>
2606 <title>Always download Debian packages using Tor - the simple recipe
</title>
2607 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2608 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2609 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2610 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2611 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2612 that those listening on the Internet lines would have good reason to
2613 believe a computer have a given security hole
</a
> if it download a
2614 security fix from a Debian mirror. This is a good reason to always
2615 use encrypted connections to the Debian mirror, to make sure those
2616 listening do not know which IP address to attack. In August, Richard
2617 Hartmann observed that encryption was not enough, when it was possible
2618 to interfere download size to security patches or the fact that
2619 download took place shortly after a security fix was released, and
2620 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2621 to always use Tor to download packages from the Debian mirror
</a
>. He
2622 was not the first to propose this, as the
2623 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2624 package by Tim Retout already existed to make it easy to convince apt
2625 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2626 aware of that package when I read the blog post from Richard.
</p
>
2628 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2629 sysadmins, and he set up a Tor hidden service on one of the central
2630 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2631 it possible to download packages directly between two tor nodes,
2632 making sure the network traffic always were encrypted.
</p
>
2634 <p
>Here is a short recipe for enabling this on your machine, by
2635 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2636 urls with tor+http and tor+https, and using the hidden service instead
2637 of the official Debian mirror site. I recommend installing
2638 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2639 done in /etc/.
</p
>
2641 <blockquote
><pre
>
2642 apt install apt-transport-tor
2643 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2644 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2645 </pre
></blockquote
>
2647 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2648 the sed commands for these too. The sed command is assuming your are
2649 using the ftp.debian.org Debian mirror. Adjust the command (or just
2650 edit the file manually) to match your mirror.
</p
>
2652 <p
>This work in Debian Jessie and later. Note that tools like
2653 <tt
>apt-file
</tt
> only recently started using the apt transport
2654 system, and do not work with these tor+http URLs. For
2655 <tt
>apt-file
</tt
> you need the version currently in experimental,
2656 which need a recent apt version currently only in unstable. So if you
2657 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2659 <p
>Another advantage from this change is that your machine will start
2660 using Tor regularly and at fairly random intervals (every time you
2661 update the package lists or upgrade or install a new package), thus
2662 masking other Tor traffic done from the same machine. Using Tor will
2663 become normal for the machine in question.
</p
>
2665 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2666 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2667 enabled. It would be great if it was the default on any Debian
2673 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2674 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2675 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2676 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2677 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2678 call the car license plate numbers in those days. I would write the
2679 numbers down in my little book and compare notes with the other kids
2680 to see how many region codes we had seen and if we had seen some
2681 exotic or special region codes and numbers. It was a fun game to pass
2682 time, as we kids have plenty of it.
</p
>
2684 <p
>A few days I came across
2685 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2686 project
</a
>, a free software project to automatically discover and
2687 report license plates in images and video streams, and provide the
2688 "car numbers
" in a machine readable format. I
've been looking for
2689 such system for a while now, because I believe it is a bad idea that the
2690 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2691 number plate recognition
</a
> tool only is available in the hands of
2692 the powerful, and want it to be available also for the powerless to
2693 even the score when it comes to surveillance and sousveillance. I
2694 discovered the developer
2695 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2696 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2697 help him get it into shape to get the package uploaded into the Debian
2700 <p
>Today we finally managed to get the package into shape and uploaded
2701 it into Debian, where it currently
2702 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2703 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2705 <p
>I guess you are wondering why on earth such tool would be useful
2706 for the common folks, ie those not running a large government
2707 surveillance system? Well, I plan to put it in a computer on my bike
2708 and in my car, tracking the cars nearby and allowing me to be notified
2709 when number plates on my watch list are discovered. Another use case
2710 was suggested by a friend of mine, who wanted to set it up at his home
2711 to open the car port automatically when it discovered the plate on his
2712 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2713 capable of placing his license plate number of a piece of cardboard to
2714 open his car port, men replied that it was always unlocked anyway. I
2715 guess for such use case it make sense. I am sure there are other use
2716 cases too, for those with imagination and a vision.
</p
>
2718 <p
>If you want to build your own version of the Debian package, check
2719 out the upstream git source and symlink ./distros/debian to ./debian/
2720 before running
"debuild
" to build the source. Or wait a bit until the
2721 package show up in unstable.
</p
>
2726 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2727 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2728 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2729 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2730 <description><p
>Around three years ago, I created
2731 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2732 system
</a
> to get a more practical solution in Debian for handing
2733 hardware related packages. A GUI system in the isenkram package will
2734 present a pop-up dialog when some hardware dongle supported by
2735 relevant packages in Debian is inserted into the machine. The same
2736 lookup mechanism to detect packages is available as command line
2737 tools in the isenkram-cli package. In addition to mapping hardware,
2738 it will also map kernel firmware files to packages and make it easy to
2739 install needed firmware packages automatically. The key for this
2740 system to work is a good way to map hardware to packages, in other
2741 words, allow packages to announce what hardware they will work
2744 <p
>I started by providing data files in the isenkram source, and
2745 adding code to download the latest version of these data files at run
2746 time, to ensure every user had the most up to date mapping available.
2747 I also added support for storing the mapping in the Packages file in
2748 the apt repositories, but did not push this approach because while I
2749 was trying to figure out how to best store hardware/package mappings,
2750 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2751 appstream system
</a
> was announced. I got in touch and suggested to
2752 add the hardware mapping into that data set to be able to use
2753 appstream as a data source, and this was accepted at least for the
2754 Debian version of appstream.
</p
>
2756 <p
>A few days ago using appstream in Debian for this became possible,
2757 and today I uploaded a new version
0.20 of isenkram adding support for
2758 appstream as a data source for mapping hardware to packages. The only
2759 package so far using appstream to announce its hardware support is my
2760 pymissile package. I got help from Matthias Klumpp with figuring out
2761 how do add the required
2762 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2763 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2764 this content:
</p
>
2766 <blockquote
><pre
>
2767 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2768 &lt;component
&gt;
2769 &lt;id
&gt;pymissile
&lt;/id
&gt;
2770 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2771 &lt;name
&gt;pymissile
&lt;/name
&gt;
2772 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2773 &lt;description
&gt;
2775 Pymissile provides a curses interface to control an original
2776 Marks and Spencer / Striker USB Missile Launcher, as well as a
2777 motion control script to allow a webcamera to control the
2780 &lt;/description
&gt;
2781 &lt;provides
&gt;
2782 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2783 &lt;/provides
&gt;
2784 &lt;/component
&gt;
2785 </pre
></blockquote
>
2787 <p
>The key for isenkram is the component/provides/modalias value,
2788 which is a glob style match rule for hardware specific strings
2789 (modalias strings) provided by the Linux kernel. In this case, it
2790 will map to all USB devices with vendor code
1130 and product code
2793 <p
>Note, it is important that the license of all the metadata files
2794 are compatible to have permissions to aggregate them into archive wide
2795 appstream files. Matthias suggested to use MIT or BSD licenses for
2796 these files. A challenge is figuring out a good id for the data, as
2797 it is supposed to be globally unique and shared across distributions
2798 (in other words, best to coordinate with upstream what to use). But
2799 it can be changed later or, so we went with the package name as
2800 upstream for this project is dormant.
</p
>
2802 <p
>To get the metadata file installed in the correct location for the
2803 mirror update scripts to pick it up and include its content the
2804 appstream data source, the file must be installed in the binary
2805 package under /usr/share/appdata/. I did this by adding the following
2806 line to debian/pymissile.install:
</p
>
2808 <blockquote
><pre
>
2809 debian/pymissile.metainfo.xml usr/share/appdata
2810 </pre
></blockquote
>
2812 <p
>With that in place, the command line tool isenkram-lookup will list
2813 all packages useful on the current computer automatically, and the GUI
2814 pop-up handler will propose to install the package not already
2815 installed if a hardware dongle is inserted into the machine in
2818 <p
>Details of the modalias field in appstream is available from the
2819 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2821 <p
>To locate the modalias values of all hardware present in a machine,
2822 try running this command on the command line:
</p
>
2824 <blockquote
><pre
>
2825 cat $(find /sys/devices/|grep modalias)
2826 </pre
></blockquote
>
2828 <p
>To learn more about the isenkram system, please check out
2829 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2830 blog posts tagged isenkram
</a
>.
</p
>
2835 <title>The GNU General Public License is not magic pixie dust
</title>
2836 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2837 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2838 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2839 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2840 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2841 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2842 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2843 I quote the blog post from Paul in full here with his permission:
<p
>
2847 <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
>
2850 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2852 The first step is to choose a
2853 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2856 The next step is, when someone fails to follow that copyleft license,
2857 <b
>it must be enforced
</b
><br/
>
2859 and its a simple fact of our modern society that such type of
2862 is incredibly expensive to do and incredibly difficult to do.
2865 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2866 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2867 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2868 0x57</a
></small
></p
>
2870 <p
>As the Debian Website
2871 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2872 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2873 imply, public domain and permissively licensed software can lead to
2874 the production of more proprietary software as people discover useful
2875 software, extend it and or incorporate it into their hardware or
2876 software products. Copyleft licenses such as the GNU GPL were created
2877 to close off this avenue to the production of proprietary software but
2878 such licenses are not enough. With the ongoing adoption of Free
2879 Software by individuals and groups, inevitably the community
's
2880 expectations of license compliance are violated, usually out of
2881 ignorance of the way Free Software works, but not always. As Karen
2882 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2883 Freedom
">FaiF
</a
>
2884 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2885 copyleft is nothing if no-one is willing and able to stand up in court
2886 to protect it. The reality of today
's world is that legal
2887 representation is expensive, difficult and time consuming. With
2888 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2889 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2890 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2891 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2892 of the Linux project, Debian and other groups against GPL violations.
2893 In March the SFC supported a
2894 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2895 by Christoph Hellwig
</a
> against VMware for refusing to
2896 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2897 with the GPL
</a
> in relation to their use of parts of the Linux
2898 kernel. Since then two of their sponsors pulled corporate funding and
2900 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2901 or cancelled their talks
</a
>. As a result they have decided to rely
2902 less on corporate funding and more on the broad community of
2903 individuals who support Free Software and copyleft. So the SFC has
2904 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2905 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2906 a community of folks who stand up for copyleft and the GPL by
2907 supporting their work on promoting and supporting copyleft and Free
2910 <p
>If you support Free Software,
2911 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2912 what the SFC do, agree with their
2913 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2914 principles
</a
>, are happy about their
2915 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2916 work on a project that is an SFC
2917 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2918 just want to stand up for copyleft, please join
2919 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2920 Allan Webber
</a
>,
2921 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2923 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2924 Bacon
</a
>, myself and
2925 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2927 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2928 next week your donation will be
2929 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2930 by an anonymous donor. Please also consider asking your employer to
2931 match your donation or become a sponsor of SFC. Don
't forget to
2932 spread the word about your support for SFC via email, your blog and or
2933 social media accounts.
</p
>
2937 <p
>I agree with Paul on this topic and just signed up as a Supporter
2938 of Software Freedom Conservancy myself. Perhaps you should be a
2939 supporter too?
</p
>
2944 <title>PGP key transition statement for key EE4E02F9
</title>
2945 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2946 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2947 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2948 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2949 set it up properly. I wanted to generate it offline and have it
2950 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2951 smart card
</a
> for daily use, and learning how to do it and finding
2952 time to sit down with an offline machine almost took forever. But
2953 finally I
've been able to complete the process, and have now moved
2954 from my old GPG key to a new GPG key. See
2955 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2956 full transition statement, signed with both my old and new key
</a
> for
2957 the details. This is my new key:
</p
>
2960 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2961 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2962 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2963 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2964 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2965 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2966 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2969 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2970 my old key.
</p
>
2972 <p
>If you signed my old key
2973 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2974 I
'd very much appreciate a signature on my new key, details and
2975 instructions in the transition statement. I m happy to reciprocate if
2976 you have a similarly signed transition statement to present.
</p
>
2981 <title>The life and death of a laptop battery
</title>
2982 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2983 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2984 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2985 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2986 But this do not last. The last few laptops gave me a feeling that
2987 within a year, the life time is just a fraction of what it used to be,
2988 and it slowly become painful to use the laptop without power connected
2989 all the time. Because of this, when I got a new Thinkpad X230 laptop
2990 about two years ago, I decided to monitor its battery state to have
2991 more hard facts when the battery started to fail.
</p
>
2993 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2995 <p
>First I tried to find a sensible Debian package to record the
2996 battery status, assuming that this must be a problem already handled
2997 by someone else. I found
2998 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2999 which collects statistics from the battery, but it was completely
3000 broken. I sent a few suggestions to the maintainer, but decided to
3001 write my own collector as a shell script while I waited for feedback
3003 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3004 blog post about the battery development on a MacBook Air
</a
> I also
3006 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3007 available in Debian.
</p
>
3009 <p
>I started my collector
2013-
07-
15, and it has been collecting
3010 battery stats ever since. Now my
3011 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3012 measurements, from the time the battery was working great until now,
3013 when it is unable to charge above
7% of original capacity. My
3014 collector shell script is quite simple and look like this:
</p
>
3019 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3021 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3022 logfile=/var/log/hjemmenett-battery-status.log
3024 files=
"manufacturer model_name technology serial_number \
3025 energy_full energy_full_design energy_now cycle_count status
"
3027 if [ ! -e
"$logfile
" ] ; then
3029 printf
"timestamp,
"
3031 printf
"%s,
" $f
3034 )
> "$logfile
"
3038 # Print complete message in one echo call, to avoid race condition
3039 # when several log processes run in parallel.
3040 msg=$(printf
"%s,
" $(date +%s); \
3041 for f in $files; do \
3042 printf
"%s,
" $(cat $f); \
3044 echo
"$msg
"
3047 cd /sys/class/power_supply
3050 (cd $bat
&& log_battery
>> "$logfile
")
3054 <p
>The script is called when the power management system detect a
3055 change in the power status (power plug in or out), and when going into
3056 and out of hibernation and suspend. In addition, it collect a value
3057 every
10 minutes. This make it possible for me know when the battery
3058 is discharging, charging and how the maximum charge change over time.
3059 The code for the Debian package
3060 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3061 available on github
</a
>.
</p
>
3063 <p
>The collected log file look like this:
</p
>
3066 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3067 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3069 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3070 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3073 <p
>I wrote a small script to create a graph of the charge development
3074 over time. This graph depicted above show the slow death of my laptop
3077 <p
>But why is this happening? Why are my laptop batteries always
3078 dying in a year or two, while the batteries of space probes and
3079 satellites keep working year after year. If we are to believe
3080 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3081 University
</a
>, the cause is me charging the battery whenever I have a
3082 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3083 all the time, but to stay below
90% of full charge most of the time.
3084 I
've been told that the Tesla electric cars
3085 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3086 the charge of their batteries to
80%
</a
>, with the option to charge to
3087 100% when preparing for a longer trip (not that I would want a car
3088 like Tesla where rights to privacy is abandoned, but that is another
3089 story), which I guess is the option we should have for laptops on
3090 Linux too.
</p
>
3092 <p
>Is there a good and generic way with Linux to tell the battery to
3093 stop charging at
80%, unless requested to charge to
100% once in
3094 preparation for a longer trip? I found
3095 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3096 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3097 80%
</a
>, but could not get it to work (kernel module refused to
3100 <p
>I wonder why the battery capacity was reported to be more than
100%
3101 at the start. I also wonder why the
"full capacity
" increases some
3102 times, and if it is possible to repeat the process to get the battery
3103 back to design capacity. And I wonder if the discharge and charge
3104 speed change over time, or if this stay the same. I did not yet try
3105 to write a tool to calculate the derivative values of the battery
3106 level, but suspect some interesting insights might be learned from
3109 <p
>Update
2015-
09-
24: I got a tip to install the packages
3110 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3111 packages instead of the tp-smapi-dkms package I had tried to use
3112 initially, and use
'tlp setcharge
40 80' to change when charging start
3113 and stop. I
've done so now, but expect my existing battery is toast
3114 and need to be replaced. The proposal is unfortunately Thinkpad
3120 <title>New laptop - some more clues and ideas based on feedback
</title>
3121 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3122 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3123 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3124 <description><p
>Several people contacted me after my previous blog post about my
3125 need for a new laptop, and provided very useful feedback. I wish to
3126 thank every one of these. Several pointed me to the possibility of
3127 fixing my X230, and I am already in the process of getting Lenovo to
3128 do so thanks to the on site, next day support contract covering the
3129 machine. But the battery is almost useless (I expect to replace it
3130 with a non-official battery) and I do not expect the machine to live
3131 for many more years, so it is time to plan its replacement. If I did
3132 not have a support contract, it was suggested to find replacement parts
3133 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3134 might present a language barrier as I do not understand French.
</p
>
3136 <p
>One tip I got was to use the
3137 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3138 compare laptop models. It seem to have more models available than
3139 prisjakt.no. Another tip I got from someone I know have similar
3140 keyboard preferences was that the HP EliteBook
840 keyboard is not
3141 very good, and this matches my experience with earlier EliteBook
3142 keyboards I tested. Because of this, I will not consider it any further.
3144 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3145 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3146 (which is missing from the X240), and is working fairly well with
3147 Debian Sid/Unstable according to
3148 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3149 got on the keyboard quality are not consistent. Some say the keyboard
3150 is good, others say it is ok, while others say it is not very good.
3151 Those with experience from X41 and and X60 agree that the X250
3152 keyboard is not as good as those trusty old laptops, and suggest I
3153 keep and fix my X230 instead of upgrading, or get a used X230 to
3154 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3155 activity and battery status, which is very convenient on my X230. I
'm
3156 also told that the CPU fan is running very often, making it a bit
3157 noisy. In any case, the X250 do not work out of the box with Debian
3158 Stable/Jessie, one of my requirements.
</p
>
3160 <p
>I have also gotten a few vendor proposals, one was
3161 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3162 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3163 The latter look very attractive to me.
</p
>
3165 <p
>Again, thank you all for the very useful feedback. It help a lot
3166 as I keep looking for a replacement.
</p
>
3168 <p
>Update
2015-
07-
06: I was recommended to check out the
3169 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3171 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3172 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3177 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3178 <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>
3179 <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>
3180 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3181 <description><p
>My primary work horse laptop is failing, and will need a
3182 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3183 started flickering yesterday, and I suspect the cause is a broken
3184 cable, as changing the angle of the screen some times get rid of the
3185 flickering.
</p
>
3187 <p
>My requirements have not really changed since I bought it, and is
3189 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3190 described them in
2013</a
>. The last time I bought a laptop, I had
3192 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3193 where I could select at least a few of the requirements (mouse pin,
3194 wifi, weight) and go through the rest manually. Three button mouse
3195 and a good keyboard is not available as an option, and all the three
3196 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3197 G2) lack three mouse buttons). It is also unclear to me how good the
3198 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3199 the keyboard, even if the quality and robustness in the X series have
3200 deteriorated since X41.
</p
>
3202 <p
>I wonder how I can find a sensible laptop when none of the options
3203 seem sensible to me? Are there better services around to search the
3204 set of available laptops for features? Please send me an email if you
3205 have suggestions.
</p
>
3207 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3208 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3209 of endorsed hardware
</a
>, which is useful background information.
</p
>
3214 <title>How to stay with sysvinit in Debian Jessie
</title>
3215 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3216 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3217 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3218 <description><p
>By now, it is well known that Debian Jessie will not be using
3219 sysvinit as its boot system by default. But how can one keep using
3220 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3222 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3223 Schubert
</a
> and
3224 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3227 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3228 keep sysvinit as your boot system, create a file
3229 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3230 you upgrade:
</p
>
3232 <p
><blockquote
><pre
>
3233 Package: systemd-sysv
3234 Pin: release o=Debian
3236 </pre
></blockquote
><p
>
3238 <p
>This file content will tell apt and aptitude to not consider
3239 installing systemd-sysv as part of any installation and upgrade
3240 solution when resolving dependencies, and thus tell it to avoid
3241 systemd as a default boot system. The end result should be that the
3242 upgraded system keep using sysvinit.
</p
>
3244 <p
>If you are installing Jessie for the first time, there is no way to
3245 get sysvinit installed by default (debootstrap used by
3246 debian-installer have no option for this), but one can tell the
3247 installer to switch to sysvinit before the first boot. Either by
3248 using a kernel argument to the installer, or by adding a line to the
3249 preseed file used. First, the kernel command line argument:
3251 <p
><blockquote
><pre
>
3252 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3253 </pre
></blockquote
><p
>
3255 <p
>Next, the line to use in a preseed file:
</p
>
3257 <p
><blockquote
><pre
>
3258 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3259 </pre
></blockquote
><p
>
3261 <p
>One can of course also do this after the first boot by installing
3262 the sysvinit-core package.
</p
>
3264 <p
>I recommend only using sysvinit if you really need it, as the
3265 sysvinit boot sequence in Debian have several hardware specific bugs
3266 on Linux caused by the fact that it is unpredictable when hardware
3267 devices show up during boot. But on the other hand, the new default
3268 boot system still have a few rough edges I hope will be fixed before
3269 Jessie is released.
</p
>
3271 <p
>Update
2014-
11-
26: Inspired by
3272 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3273 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3279 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3280 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3281 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3282 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3283 <description><p
>The right to communicate with your friends and family in private,
3284 without anyone snooping, is a right every citicen have in a liberal
3285 democracy. But this right is under serious attack these days.
</p
>
3287 <p
>A while back it occurred to me that one way to make the dragnet
3288 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3289 the whisleblower Snowden) more expensive for Internet email,
3290 is to deliver all email using SMTP via Tor. Such SMTP option would be
3291 a nice addition to the FreedomBox project if we could send email
3292 between FreedomBox machines without leaking metadata about the emails
3293 to the people peeking on the wire. I
3294 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3295 this on the FreedomBox project mailing list in October
</a
> and got a
3296 lot of useful feedback and suggestions. It also became obvious to me
3297 that this was not a novel idea, as the same idea was tested and
3298 documented by Johannes Berg as early as
2006, and both
3299 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3300 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3301 propose a similar method / protocol to pass emails between users.
</p
>
3303 <p
>To implement such system one need to set up a Tor hidden service
3304 providing the SMTP protocol on port
25, and use email addresses
3305 looking like username@hidden-service-name.onion. With such addresses
3306 the connections to port
25 on hidden-service-name.onion using Tor will
3307 go to the correct SMTP server. To do this, one need to configure the
3308 Tor daemon to provide the hidden service and the mail server to accept
3309 emails for this .onion domain. To learn more about Exim configuration
3310 in Debian and test the design provided by Johannes Berg in his FAQ, I
3311 set out yesterday to create a Debian package for making it trivial to
3312 set up such SMTP over Tor service based on Debian. Getting it to work
3313 were fairly easy, and
3314 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3315 source code for the Debian package
</a
> is available from github. I
3316 plan to move it into Debian if further testing prove this to be a
3317 useful approach.
</p
>
3319 <p
>If you want to test this, set up a blank Debian machine without any
3320 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3321 get rid of exim4). Install tor, clone the git repository mentioned
3322 above, build the deb and install it on the machine. Next, run
3323 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3324 the instructions to get the service up and running. Restart tor and
3325 exim when it is done, and test mail delivery using swaks like
3328 <p
><blockquote
><pre
>
3329 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3330 --to fbx@dutlqrrmjhtfa3vp.onion
3331 </pre
></blockquote
></p
>
3333 <p
>This will test the SMTP delivery using tor. Replace the email
3334 address with your own address to test your server. :)
</p
>
3336 <p
>The setup procedure is still to complex, and I hope it can be made
3337 easier and more automatic. Especially the tor setup need more work.
3338 Also, the package include a tor-smtp tool written in C, but its task
3339 should probably be rewritten in some script language to make the deb
3340 architecture independent. It would probably also make the code easier
3341 to review. The tor-smtp tool currently need to listen on a socket for
3342 exim to talk to it and is started using xinetd. It would be better if
3343 no daemon and no socket is needed. I suspect it is possible to get
3344 exim to run a command line tool for delivery instead of talking to a
3345 socket, and hope to figure out how in a future version of this
3348 <p
>Until I wipe my test machine, I can be reached using the
3349 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3350 SMTorP. :)
</p
>
3355 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3356 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3358 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3359 <description><p
>If you ever had to moderate a mailman list, like the ones on
3360 alioth.debian.org, you know the web interface is fairly slow to
3361 operate. First you visit one web page, enter the moderation password
3362 and get a new page shown with a list of all the messages to moderate
3363 and various options for each email address. This take a while for
3364 every list you moderate, and you need to do it regularly to do a good
3365 job as a list moderator. But there is a quick alternative,
3366 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3367 listadmin program
</a
>. It allow you to check lists for new messages
3368 to moderate in a fraction of a second. Here is a test run on two
3369 lists I recently took over:
</p
>
3371 <p
><blockquote
><pre
>
3372 % time listadmin xiph
3373 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3374 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3380 </pre
></blockquote
></p
>
3382 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3383 there are no message in the moderation queue. Every morning I
3384 currently moderate
68 mailman lists, and it normally take around two
3385 minutes. When I took over the two pkg-xiph lists above a few days
3386 ago, there were
400 emails waiting in the moderator queue. It took me
3387 less than
15 minutes to process them all using the listadmin
3390 <p
>If you install
3391 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3392 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3393 with content like this, the moderation task is a breeze:
</p
>
3395 <p
><blockquote
><pre
>
3396 username username@example.org
3399 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3402 adminurl https://{domain}/mailman/admindb/{list}
3403 mailman-list@lists.example.com
3406 other-list@otherserver.example.org
3407 </pre
></blockquote
></p
>
3409 <p
>There are other options to set as well. Check the manual page to
3410 learn the details.
</p
>
3412 <p
>If you are forced to moderate lists on a mailman installation where
3413 the SSL certificate is self signed or not properly signed by a
3414 generally accepted signing authority, you can set a environment
3415 variable when calling listadmin to disable SSL verification:
</p
>
3417 <p
><blockquote
><pre
>
3418 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3419 </pre
></blockquote
></p
>
3421 <p
>If you want to moderate a subset of the lists you take care of, you
3422 can provide an argument to the listadmin script like I do in the
3423 initial screen dump (the xiph argument). Using an argument, only
3424 lists matching the argument string will be processed. This make it
3425 quick to accept messages if you notice the moderation request in your
3428 <p
>Without the listadmin program, I would never be the moderator of
68
3429 mailing lists, as I simply do not have time to spend on that if the
3430 process was any slower. The listadmin program have saved me hours of
3431 time I could spend elsewhere over the years. It truly is nice free
3434 <p
>As usual, if you use Bitcoin and want to show your support of my
3435 activities, please send Bitcoin donations to my address
3436 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3438 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3439 configuration example. Also, I
've been told that the
3440 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3446 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3447 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3449 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3450 <description><p
>When PXE installing laptops with Debian, I often run into the
3451 problem that the WiFi card require some firmware to work properly.
3452 And it has been a pain to fix this using preseeding in Debian.
3453 Normally something more is needed. But thanks to
3454 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3455 package
</a
> and its recent tasksel extension, it has now become easy
3456 to do this using simple preseeding.
</p
>
3458 <p
>The isenkram-cli package provide tasksel tasks which will install
3459 firmware for the hardware found in the machine (actually, requested by
3460 the kernel modules for the hardware). (It can also install user space
3461 programs supporting the hardware detected, but that is not the focus
3462 of this story.)
</p
>
3464 <p
>To get this working in the default installation, two preeseding
3465 values are needed. First, the isenkram-cli package must be installed
3466 into the target chroot (aka the hard drive) before tasksel is executed
3467 in the pkgsel step of the debian-installer system. This is done by
3468 preseeding the base-installer/includes debconf value to include the
3469 isenkram-cli package. The package name is next passed to debootstrap
3470 for installation. With the isenkram-cli package in place, tasksel
3471 will automatically use the isenkram tasks to detect hardware specific
3472 packages for the machine being installed and install them, because
3473 isenkram-cli contain tasksel tasks.
</p
>
3475 <p
>Second, one need to enable the non-free APT repository, because
3476 most firmware unfortunately is non-free. This is done by preseeding
3477 the apt-mirror-setup step. This is unfortunate, but for a lot of
3478 hardware it is the only option in Debian.
</p
>
3480 <p
>The end result is two lines needed in your preseeding file to get
3481 firmware installed automatically by the installer:
</p
>
3483 <p
><blockquote
><pre
>
3484 base-installer base-installer/includes string isenkram-cli
3485 apt-mirror-setup apt-setup/non-free boolean true
3486 </pre
></blockquote
></p
>
3488 <p
>The current version of isenkram-cli in testing/jessie will install
3489 both firmware and user space packages when using this method. It also
3490 do not work well, so use version
0.15 or later. Installing both
3491 firmware and user space packages might give you a bit more than you
3492 want, so I decided to split the tasksel task in two, one for firmware
3493 and one for user space programs. The firmware task is enabled by
3494 default, while the one for user space programs is not. This split is
3495 implemented in the package currently in unstable.
</p
>
3497 <p
>If you decide to give this a go, please let me know (via email) how
3498 this recipe work for you. :)
</p
>
3500 <p
>So, I bet you are wondering, how can this work. First and
3501 foremost, it work because tasksel is modular, and driven by whatever
3502 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3503 isenkram-cli package place two files for tasksel to find. First there
3504 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3506 <p
><blockquote
><pre
>
3507 Task: isenkram-packages
3509 Description: Hardware specific packages (autodetected by isenkram)
3510 Based on the detected hardware various hardware specific packages are
3512 Test-new-install: show show
3514 Packages: for-current-hardware
3516 Task: isenkram-firmware
3518 Description: Hardware specific firmware packages (autodetected by isenkram)
3519 Based on the detected hardware various hardware specific firmware
3520 packages are proposed.
3521 Test-new-install: mark show
3523 Packages: for-current-hardware-firmware
3524 </pre
></blockquote
></p
>
3526 <p
>The key parts are Test-new-install which indicate how the task
3527 should be handled and the Packages line referencing to a script in
3528 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3529 list of packages to install. The for-current-hardware-firmware script
3530 look like this to list relevant firmware for the machine:
3532 <p
><blockquote
><pre
>
3535 PATH=/usr/sbin:$PATH
3537 isenkram-autoinstall-firmware -l
3538 </pre
></blockquote
></p
>
3540 <p
>With those two pieces in place, the firmware is installed by
3541 tasksel during the normal d-i run. :)
</p
>
3543 <p
>If you want to test what tasksel will install when isenkram-cli is
3544 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3545 --new-install
</tt
> to get the list of packages that tasksel would
3548 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3549 pilots in testing this feature, as isenkram is used there now to
3550 install firmware, replacing the earlier scripts.
</p
>
3555 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3556 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3557 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3558 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3559 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3560 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3561 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3562 on a screen normally showing the bread types and prizes:
</p
>
3564 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3566 <p
>If it had booted as it was supposed to, I would never had known
3567 about this hidden Linux installation. It is interesting what
3568 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3573 <title>New lsdvd release version
0.17 is ready
</title>
3574 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3576 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3577 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3578 got a new set of developers a few weeks ago, after the original
3579 developer decided to step down and pass the project to fresh blood.
3580 This project is now maintained by Petter Reinholdtsen and Steve
3583 <p
>I just wrapped up
3584 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3585 new lsdvd release
</a
>, available in git or from
3586 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3587 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3592 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3593 <li
>Check for garbage in the program chains, which indicate that a track is
3594 non-existant, to work around additional copy protection
</li
>
3595 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3596 <li
>Fix pallete display of first entry
</li
>
3597 <li
>Fix include orders
</li
>
3598 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3599 <li
>Fix the chapter count
</li
>
3600 <li
>Make sure the array size and the array limit used when initialising
3601 the palette size is the same.
</li
>
3602 <li
>Fix array printing.
</li
>
3603 <li
>Correct subsecond calculations.
</li
>
3604 <li
>Add sector information to the output format.
</li
>
3605 <li
>Clean up code to be closer to ANSI C and compile without warnings
3606 with more GCC compiler warnings.
</li
>
3610 <p
>This change bring together patches for lsdvd in use in various
3611 Linux and Unix distributions, as well as patches submitted to the
3612 project the last nine years. Please check it out. :)
</p
>
3617 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3618 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3620 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3621 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3622 project
</a
> provide a Linux solution for schools, including a
3623 powerful desktop with education software, a central server providing
3624 web pages, user database, user home directories, central login and PXE
3625 boot of both clients without disk and the installation to install Debian
3626 Edu on machines with disk (and a few other services perhaps to small
3627 to mention here). We in the Debian Edu team are currently working on
3628 the Jessie based version, trying to get everything in shape before the
3629 freeze, to avoid having to maintain our own package repository in the
3631 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3632 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3633 work left. Some fatal problems block testing, breaking the installer,
3634 but it is possible to work around these to get anyway. Here is a
3635 recipe on how to get the installation limping along.
</p
>
3637 <p
>First, download the test ISO via
3638 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3639 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3641 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3642 The ISO build was broken on Tuesday, so we do not get a new ISO every
3643 12 hours or so, but thankfully the ISO we already got we are able to
3644 install with some tweaking.
</p
>
3646 <p
>When you get to the Debian Edu profile question, go to tty2
3647 (use Alt-Ctrl-F2), run
</p
>
3649 <p
><blockquote
><pre
>
3650 nano /usr/bin/edu-eatmydata-install
3651 </pre
></blockquote
></p
>
3653 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3654 optimization. Return to the installation, select the profile you want
3655 and continue. Without this change, exim4-config will fail to install
3656 due to a known bug in eatmydata.
</p
>
3658 <p
>When you get the grub question at the end, answer /dev/sda (or if
3659 this do not work, figure out what your correct value would be. All my
3660 test machines need /dev/sda, so I have no advice if it do not fit
3661 your need.
</p
>
3663 <p
>If you installed a profile including a graphical desktop, log in as
3664 root after the initial boot from hard drive, and install the
3665 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3666 or mate. If you want several desktop options, install more than one
3667 metapackage. Once this is done, reboot and you should have a working
3668 graphical login screen. This workaround should no longer be needed
3669 once the education-tasks package version
1.801 enter testing in two
3672 <p
>I believe the ISO build will start working on two days when the new
3673 tasksel package enter testing and Steve McIntyre get a chance to
3674 update the debian-cd git repository. The eatmydata, grub and desktop
3675 issues are already fixed in unstable and testing, and should show up
3676 on the ISO as soon as the ISO build start working again. Well the
3677 eatmydata optimization is really just disabled. The proper fix
3678 require an upload by the eatmydata maintainer applying the patch
3679 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3680 The rest have proper fixes in unstable.
</p
>
3682 <p
>I hope this get you going with the installation testing, as we are
3683 quickly running out of time trying to get our Jessie based
3684 installation ready before the distribution freeze in a month.
</p
>
3689 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3690 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3691 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3692 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3693 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3694 to handle my fairly large DVD collection. It is a nice command line
3695 tool to get details about a DVD, like title, tracks, track length,
3696 etc, in XML, Perl or human readable format. But lsdvd have not seen
3697 any new development since
2006 and had a few irritating bugs affecting
3698 its use with some DVDs. Upstream seemed to be dead, and in January I
3699 sent a small probe asking for a version control repository for the
3700 project, without any reply. But I use it regularly and would like to
3701 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3702 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3703 the project admin, and after getting a reply from him explaining that
3704 he was no longer interested in the project, I asked if I could take
3705 over. And yesterday, I became project admin.
</p
>
3707 <p
>I
've been in touch with a Gentoo developer and the Debian
3708 maintainer interested in joining forces to maintain the upstream
3709 project, and I hope we can get a new release out fairly quickly,
3710 collecting the patches spread around on the internet into on place.
3711 I
've added the relevant Debian patches to the freshly created git
3712 repository, and expect the Gentoo patches to make it too. If you got
3713 a DVD collection and care about command line tools, check out
3714 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3715 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3716 list
</a
>. :)
</p
>
3721 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3722 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3723 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3724 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3725 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3726 a lot quicker. When we install more than
2000 packages in
3727 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3728 tasksel in the installer, unpacking the binary packages take forever.
3729 A part of the slow I/O issue was discussed in
3730 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3731 much file system sync-ing done by dpkg, which is the package
3732 responsible for unpacking the binary packages. Other parts (like code
3733 executed by postinst scripts) might also sync to disk during
3734 installation. All this sync-ing to disk do not really make sense to
3735 me. If the machine crash half-way through, I start over, I do not try
3736 to salvage the half installed system. So the failure sync-ing is
3737 supposed to protect against, hardware or system crash, is not really
3738 relevant while the installer is running.
</p
>
3740 <p
>A few days ago, I thought of a way to get rid of all the file
3741 system sync()-ing in a fairly non-intrusive way, without the need to
3742 change the code in several packages. The idea is not new, but I have
3743 not heard anyone propose the approach using dpkg-divert before. It
3744 depend on the small and clever package
3745 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3746 uses LD_PRELOAD to replace the system functions for syncing data to
3747 disk with functions doing nothing, thus allowing programs to live
3748 dangerous while speeding up disk I/O significantly. Instead of
3749 modifying the implementation of dpkg, apt and tasksel (which are the
3750 packages responsible for selecting, fetching and installing packages),
3751 it occurred to me that we could just divert the programs away, replace
3752 them with a simple shell wrapper calling
3753 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3754 Two days ago I decided to test the idea, and wrapped up a simple
3755 implementation for the Debian Edu udeb.
</p
>
3757 <p
>The effect was stunning. In my first test it reduced the running
3758 time of the pkgsel step (installing tasks) from
64 to less than
44
3759 minutes (
20 minutes shaved off the installation) on an old Dell
3760 Latitude D505 machine. I am not quite sure what the optimised time
3761 would have been, as I messed up the testing a bit, causing the debconf
3762 priority to get low enough for two questions to pop up during
3763 installation. As soon as I saw the questions I moved the installation
3764 along, but do not know how long the question were holding up the
3765 installation. I did some more measurements using Debian Edu Jessie,
3766 and got these results. The time measured is the time stamp in
3767 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3768 "pkgsel: finishing up
" lines, if you want to do the same measurement
3769 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3770 timing thus do not depend on how quickly the user handle the tasksel
3773 <p
><table
>
3776 <th
>Machine/setup
</th
>
3777 <th
>Original tasksel
</th
>
3778 <th
>Optimised tasksel
</th
>
3779 <th
>Reduction
</th
>
3783 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3784 <td
>64 min (
07:
46-
08:
50)
</td
>
3785 <td
><44 min (
11:
27-
12:
11)
</td
>
3786 <td
>>20 min
18%
</td
>
3790 <td
>Latitude D505 Roaming LXDE
</td
>
3791 <td
>57 min (
08:
48-
09:
45)
</td
>
3792 <td
>34 min (
07:
43-
08:
17)
</td
>
3793 <td
>23 min
40%
</td
>
3797 <td
>Latitude D505 Minimal
</td
>
3798 <td
>22 min (
10:
37-
10:
59)
</td
>
3799 <td
>11 min (
11:
16-
11:
27)
</td
>
3800 <td
>11 min
50%
</td
>
3804 <td
>Thinkpad X200 Minimal
</td
>
3805 <td
>6 min (
08:
19-
08:
25)
</td
>
3806 <td
>4 min (
08:
04-
08:
08)
</td
>
3807 <td
>2 min
33%
</td
>
3811 <td
>Thinkpad X200 Roaming KDE
</td
>
3812 <td
>19 min (
09:
21-
09:
40)
</td
>
3813 <td
>15 min (
10:
25-
10:
40)
</td
>
3814 <td
>4 min
21%
</td
>
3817 </table
></p
>
3819 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3820 time is spent downloading packages. The connection to the Internet
3821 was
100Mbit/s during testing, so downloading should not be a
3822 significant factor in the measurement. Download typically took a few
3823 seconds to a few minutes, depending on the amount of packages being
3824 installed.
</p
>
3826 <p
>The speedup is implemented by using two hooks in
3827 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3828 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3829 finish-install.d hook to remove the divert at the end of the
3830 installation. I picked the pre-pkgsel.d hook instead of the
3831 post-base-installer.d hook because I test using an ISO without the
3832 eatmydata package included, and the post-base-installer.d hook in
3833 Debian Edu can only operate on packages included in the ISO. The
3834 negative effect of this is that I am unable to activate this
3835 optimization for the kernel installation step in d-i. If the code is
3836 moved to the post-base-installer.d hook, the speedup would be larger
3837 for the entire installation.
</p
>
3839 <p
>I
've implemented this in the
3840 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3841 git repository, and plan to provide the optimization as part of the
3842 Debian Edu installation. If you want to test this yourself, you can
3843 create two files in the installer (or in an udeb). One shell script
3844 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3846 <p
><blockquote
><pre
>
3849 . /usr/share/debconf/confmodule
3851 logger -t my-pkgsel
"info: $*
"
3854 logger -t my-pkgsel
"error: $*
"
3856 override_install() {
3857 apt-install eatmydata || true
3858 if [ -x /target/usr/bin/eatmydata ] ; then
3859 for bin in dpkg apt-get aptitude tasksel ; do
3861 # Test that the file exist and have not been diverted already.
3862 if [ -f /target$file ] ; then
3863 info
"diverting $file using eatmydata
"
3864 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3865 > /target$file.edu
3866 chmod
755 /target$file.edu
3867 in-target dpkg-divert --package debian-edu-config \
3868 --rename --quiet --add $file
3869 ln -sf ./$bin.edu /target$file
3871 error
"unable to divert $file, as it is missing.
"
3875 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3880 </pre
></blockquote
></p
>
3882 <p
>To clean up, another shell script should go into
3883 /usr/lib/finish-install.d/ with code like this:
3885 <p
><blockquote
><pre
>
3887 . /usr/share/debconf/confmodule
3889 logger -t my-finish-install
"error: $@
"
3891 remove_install_override() {
3892 for bin in dpkg apt-get aptitude tasksel ; do
3894 if [ -x /target$file.edu ] ; then
3896 in-target dpkg-divert --package debian-edu-config \
3897 --rename --quiet --remove $file
3900 error
"Missing divert for $file.
"
3903 sync # Flush file buffers before continuing
3906 remove_install_override
3907 </pre
></blockquote
></p
>
3909 <p
>In Debian Edu, I placed both code fragments in a separate script
3910 edu-eatmydata-install and call it from the pre-pkgsel.d and
3911 finish-install.d scripts.
</p
>
3913 <p
>By now you might ask if this change should get into the normal
3914 Debian installer too? I suspect it should, but am not sure the
3915 current debian-installer coordinators find it useful enough. It also
3916 depend on the side effects of the change. I
'm not aware of any, but I
3917 guess we will see if the change is safe after some more testing.
3918 Perhaps there is some package in Debian depending on sync() and
3919 fsync() having effect? Perhaps it should go into its own udeb, to
3920 allow those of us wanting to enable it to do so without affecting
3923 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3924 will break installation of all programs using gnutls because of
3925 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3926 eatmydata package in Debian will solve it.
</p
>
3928 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3929 the optimization work again. And I have discovered that the
3930 dpkg-divert trick is not really needed and implemented a slightly
3931 simpler approach as part of the debian-edu-install package. See
3932 tools/edu-eatmydata-install in the source package.
</p
>
3934 <p
>Update
2014-
11-
11: Unfortunately, a new
3935 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3936 triggering on i386 made it into testing, and broke this installation
3937 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3938 request
768893</a
> is accepted, it should be working again.
</p
>
3943 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3944 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3945 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3946 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3947 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3948 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3949 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3950 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3951 learn that there is a large set of publicly available key servers to
3952 use when looking for peoples public key. So far I have used
3953 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3954 were misbehaving, but those days are ended. The servers I have used
3955 up until yesterday have been slow and some times unavailable. I hope
3956 those problems are gone now.
</p
>
3958 <p
>Behind the round robin DNS entry of the
3959 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3960 there is a pool of more than
100 keyservers which are checked every
3961 day to ensure they are well connected and up to date. It must be
3962 better than what I have used so far. :)
</p
>
3964 <p
>Yesterdays speaker told me that the service is the default
3965 keyserver provided by the default configuration in GnuPG, but this do
3966 not seem to be used in Debian. Perhaps it should?
</p
>
3968 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3971 <p
><blockquote
><pre
>
3972 keyserver pool.sks-keyservers.net
3973 </pre
></blockquote
></p
>
3975 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3976 entries in DNS. Just for fun, I did just that at work, so now every
3977 user of GnuPG at the University of Oslo should find a OpenGPG
3978 keyserver automatically should their need it:
</p
>
3980 <p
><blockquote
><pre
>
3981 % host -t srv _pgpkey-http._tcp.uio.no
3982 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3984 </pre
></blockquote
></p
>
3986 <p
>Now if only
3987 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3988 HKP lookup protocol
</a
> supported finding signature paths, I would be
3989 very happy. It can look up a given key or search for a user ID, but I
3990 normally do not want that, but to find a trust path from my key to
3991 another key. Given a user ID or key ID, I would like to find (and
3992 download) the keys representing a signature path from my key to the
3993 key in question, to be able to get a trust path between the two keys.
3994 This is as far as I can tell not possible today. Perhaps something
3995 for a future version of the protocol?
</p
>
4000 <title>From English wiki to translated PDF and epub via Docbook
</title>
4001 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
4002 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
4003 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4004 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4005 project
</a
> provide an instruction manual for teachers, system
4006 administrators and other users that contain useful tips for setting up
4007 and maintaining a Debian Edu installation. This text is about how the
4008 text processing of this manual is handled in the project.
</p
>
4010 <p
>One goal of the project is to provide information in the native
4011 language of its users, and for this we need to handle translations.
4012 But we also want to make sure each language contain the same
4013 information, so for this we need a good way to keep the translations
4014 in sync. And we want it to be easy for our users to improve the
4015 documentation, avoiding the need to learn special formats or tools to
4016 contribute, and the obvious way to do this is to make it possible to
4017 edit the documentation using a web browser. We also want it to be
4018 easy for translators to keep the translation up to date, and give them
4019 help in figuring out what need to be translated. Here is the list of
4020 tools and the process we have found trying to reach all these
4023 <p
>We maintain the authoritative source of our manual in the
4024 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4025 wiki
</a
>, as several wiki pages written in English. It consist of one
4026 front page with references to the different chapters, several pages
4027 for each chapter, and finally one
"collection page
" gluing all the
4028 chapters together into one large web page (aka
4029 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4030 AllInOne page
</a
>). The AllInOne page is the one used for further
4031 processing and translations. Thanks to the fact that the
4032 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4033 wiki.debian.org support exporting pages in
4034 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4035 the list of pages to export using the raw version of the AllInOne
4036 page, loop over each of them to generate a Docbook XML version of the
4037 manual. This process also download images and transform image
4038 references to use the locally downloaded images. The generated
4039 Docbook XML files are slightly broken, so some post-processing is done
4040 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4041 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4042 a handfull of images. The XML file can now be used to generate PDF, HTML
4043 and epub versions of the English manual. This is the basic step of
4044 our process, making PDF (using dblatex), HTML (using xsltproc) and
4045 epub (using dbtoepub) version from Docbook XML, and the resulting files
4046 are placed in the debian-edu-doc-en binary package.
</p
>
4048 <p
>But English documentation is not enough for us. We want translated
4049 documentation too, and we want to make it easy for translators to
4050 track the English original. For this we use the
4051 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4052 which allow us to transform the English Docbook XML file into a
4053 translation file (a .pot file), usable with the normal gettext based
4054 translation tools used by those translating free software. The pot
4055 file is used to create and maintain translation files (several .po
4056 files), which the translations update with the native language
4057 translations of all titles, paragraphs and blocks of text in the
4058 original. The next step is combining the original English Docbook XML
4059 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4060 create a translated Docbook XML file (in this case
4061 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4062 translated, if the translation is not complete) Docbook XML file can
4063 then be used like the original to create a PDF, HTML and epub version
4064 of the documentation.
</p
>
4066 <p
>The translators use different tools to edit the .po files. We
4068 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4069 while some use emacs and vi, others can use web based editors like
4070 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4071 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4072 is where the .po file end up, in our git repository. Updated
4073 translations can either be committed directly to git, or submitted as
4074 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4075 against the debian-edu-doc package
</a
>.
</p
>
4077 <p
>One challenge is images, which both might need to be translated (if
4078 they show translated user applications), and are needed in different
4079 formats when creating PDF and HTML versions (epub is a HTML version in
4080 this regard). For this we transform the original PNG images to the
4081 needed density and format during build, and have a way to provide
4082 translated images by storing translated versions in
4083 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4084 package maintainers know more.
</p
>
4086 <p
>If you wonder what the result look like, we provide
4087 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4088 of the documentation packages on the web
</a
>. See for example the
4089 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4090 PDF version
</a
> or the
4091 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4092 HTML version
</a
>. We do not yet build the epub version by default,
4093 but perhaps it will be done in the future.
</p
>
4095 <p
>To learn more, check out
4096 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4097 debian-edu-doc package
</a
>,
4098 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4099 manual on the wiki
</a
> and
4100 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4101 translation instructions
</a
> in the manual.
</p
>
4106 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4107 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4108 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4109 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4110 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4111 related packages relevant for the computer installed automatically.
4112 So I implemented one, using
4113 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4114 package
</a
>. To use it, install the tasksel and isenkram packages and
4115 run tasksel as user root. You should be presented with a new option,
4116 "Hardware specific packages (autodetected by isenkram)
". When you
4117 select it, tasksel will install the packages isenkram claim is fit for
4118 the current hardware, hot pluggable or not.
<p
>
4120 <p
>The implementation is in two files, one is the tasksel menu entry
4121 description, and the other is the script used to extract the list of
4122 packages to install. The first part is in
4123 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4126 <p
><blockquote
><pre
>
4129 Description: Hardware specific packages (autodetected by isenkram)
4130 Based on the detected hardware various hardware specific packages are
4132 Test-new-install: mark show
4134 Packages: for-current-hardware
4135 </pre
></blockquote
></p
>
4137 <p
>The second part is in
4138 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4141 <p
><blockquote
><pre
>
4146 isenkram-autoinstall-firmware -l
4148 </pre
></blockquote
></p
>
4150 <p
>All in all, a very short and simple implementation making it
4151 trivial to install the hardware dependent package we all may want to
4152 have installed on our machines. I
've not been able to find a way to
4153 get tasksel to tell you exactly which packages it plan to install
4154 before doing the installation. So if you are curious or careful,
4155 check the output from the isenkram-* command line tools first.
</p
>
4157 <p
>The information about which packages are handling which hardware is
4158 fetched either from the isenkram package itself in
4159 /usr/share/isenkram/, from git.debian.org or from the APT package
4160 database (using the Modaliases header). The APT package database
4161 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4162 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4163 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4164 the python-apt code (bug
4165 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4166 workaround I was able to get rid of the file descriptor leak and
4167 reduce the memory leak from ~
30 MiB per hardware detection down to
4168 around
2 MiB per hardware detection. It should make the desktop
4169 daemon a lot more useful. The fix is in version
0.7 uploaded to
4170 unstable today.
</p
>
4172 <p
>I believe the current way of mapping hardware to packages in
4173 Isenkram is is a good draft, but in the future I expect isenkram to
4174 use the AppStream data source for this. A proposal for getting proper
4175 AppStream support into Debian is floating around as
4176 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4177 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4178 project
</a
> will take place this summer to improve the situation. I
4179 look forward to seeing the result, and welcome patches for isenkram to
4180 start using the information when it is ready.
</p
>
4182 <p
>If you want your package to map to some specific hardware, either
4183 add a
"Xb-Modaliases
" header to your control file like I did in
4184 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4185 package
</a
> or submit a bug report with the details to the isenkram
4187 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4188 blog posts tagged isenkram
</a
> for details on the notation. I expect
4189 the information will be migrated to AppStream eventually, but for the
4190 moment I got no better place to store it.
</p
>
4195 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4196 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4197 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4198 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4199 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4200 project
</a
> is working on providing the software and hardware to make
4201 it easy for non-technical people to host their data and communication
4202 at home, and being able to communicate with their friends and family
4203 encrypted and away from prying eyes. It is still going strong, and
4204 today a major mile stone was reached.
</p
>
4206 <p
>Today, the last of the packages currently used by the project to
4207 created the system images were accepted into Debian Unstable. It was
4208 the freedombox-setup package, which is used to configure the images
4209 during build and on the first boot. Now all one need to get going is
4210 the build code from the freedom-maker git repository and packages from
4211 Debian. And once the freedombox-setup package enter testing, we can
4212 build everything directly from Debian. :)
</p
>
4214 <p
>Some key packages used by Freedombox are
4215 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4216 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4217 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4218 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4219 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4220 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4221 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4222 are plans to integrate more packages into the setup. User
4223 documentation is maintained on the Debian wiki. Please
4224 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4225 the manual
</a
> and help us improve it.
</p
>
4227 <p
>To test for yourself and create boot images with the FreedomBox
4228 setup, run this on a Debian machine using a user with sudo rights to
4229 become root:
</p
>
4231 <p
><pre
>
4232 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4233 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4235 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4237 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4238 </pre
></p
>
4240 <p
>Root access is needed to run debootstrap and mount loopback
4241 devices. See the README in the freedom-maker git repo for more
4242 details on the build. If you do not want all three images, trim the
4243 make line. Note that the virtualbox-image target is not really
4244 virtualbox specific. It create a x86 image usable in kvm, qemu,
4245 vmware and any other x86 virtual machine environment. You might need
4246 the version of vmdebootstrap in Jessie to get the build working, as it
4247 include fixes for a race condition with kpartx.
</p
>
4249 <p
>If you instead want to install using a Debian CD and the preseed
4250 method, boot a Debian Wheezy ISO and use this boot argument to load
4251 the preseed values:
</p
>
4253 <p
><pre
>
4254 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4255 </pre
></p
>
4257 <p
>I have not tested it myself the last few weeks, so I do not know if
4258 it still work.
</p
>
4260 <p
>If you wonder how to help, one task you could look at is using
4261 systemd as the boot system. It will become the default for Linux in
4262 Jessie, so we need to make sure it is usable on the Freedombox. I did
4263 a simple test a few weeks ago, and noticed dnsmasq failed to start
4264 during boot when using systemd. I suspect there are other problems
4265 too. :) To detect problems, there is a test suite included, which can
4266 be run from the plinth web interface.
</p
>
4268 <p
>Give it a go and let us know how it goes on the mailing list, and help
4269 us get the new release published. :) Please join us on
4270 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4271 irc.debian.org)
</a
> and
4272 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4273 mailing list
</a
> if you want to help make this vision come true.
</p
>
4278 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4279 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4280 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4281 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4282 <description><p
>For a while now, I have been looking for a sensible offsite backup
4283 solution for use at home. My requirements are simple, it must be
4284 cheap and locally encrypted (in other words, I keep the encryption
4285 keys, the storage provider do not have access to my private files).
4286 One idea me and my friends had many years ago, before the cloud
4287 storage providers showed up, was to use Google mail as storage,
4288 writing a Linux block device storing blocks as emails in the mail
4289 service provided by Google, and thus get heaps of free space. On top
4290 of this one can add encryption, RAID and volume management to have
4291 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4292 I never found time to implement such system. But the last few weeks I
4293 have looked at a system called
4294 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4295 mounted network backed file system with the features I need.
</p
>
4297 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4298 handling several different storage providers, any with Amazon S3,
4299 Google Drive or OpenStack API. There are heaps of such storage
4300 providers. S3QL can also use a local directory as storage, which
4301 combined with sshfs allow for file storage on any ssh server. S3QL
4302 include support for encryption, compression, de-duplication, snapshots
4303 and immutable file systems, allowing me to mount the remote storage as
4304 a local mount point, look at and use the files as if they were local,
4305 while the content is stored in the cloud as well. This allow me to
4306 have a backup that should survive fire. The file system can not be
4307 shared between several machines at the same time, as only one can
4308 mount it at the time, but any machine with the encryption key and
4309 access to the storage service can mount it if it is unmounted.
</p
>
4311 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4312 package is included already. So to get started, run
<tt
>apt-get
4313 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4314 Greenqloud, after reading their nice recipe on
4315 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4316 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4317 in Iceland more than those in USA when it come to keeping my personal
4318 data safe and private, and thus would rather spend money on a company
4319 in Iceland. Another nice recipe is available from the article
4320 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4321 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4322 Admin magazine. When the provider is picked, figure out how to get
4323 the API key needed to connect to the storage API. With Greencloud,
4324 the key did not show up until I had added payment details to my
4327 <p
>Armed with the API access details, it is time to create the file
4328 system. First, create a new bucket in the cloud. This bucket is the
4329 file system storage area. I picked a bucket name reflecting the
4330 machine that was going to store data there, but any name will do.
4331 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4332 the API login and password, and a locally created password. Store it
4333 all in ~root/.s3ql/authinfo2 like this:
4335 <p
><blockquote
><pre
>
4337 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4338 backend-login: API-login
4339 backend-password: API-password
4340 fs-passphrase: local-password
4341 </pre
></blockquote
></p
>
4343 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4344 but any sensible way to create a fairly random password should do it.
4345 Armed with these details, it is now time to run mkfs, entering the API
4346 details and password to create it:
</p
>
4348 <p
><blockquote
><pre
>
4349 # mkdir -m
700 /var/lib/s3ql-cache
4350 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4351 --ssl s3c://s.greenqloud.com:
443/bucket-name
4352 Enter backend login:
4353 Enter backend password:
4354 Before using S3QL, make sure to read the user
's guide, especially
4355 the
'Important Rules to Avoid Loosing Data
' section.
4356 Enter encryption password:
4357 Confirm encryption password:
4358 Generating random encryption key...
4359 Creating metadata tables...
4369 Compressing and uploading metadata...
4370 Wrote
0.00 MB of compressed metadata.
4371 #
</pre
></blockquote
></p
>
4373 <p
>The next step is mounting the file system to make the storage available.
4375 <p
><blockquote
><pre
>
4376 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4377 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4378 Using
4 upload threads.
4379 Downloading and decompressing metadata...
4389 Mounting filesystem...
4391 Filesystem Size Used Avail Use% Mounted on
4392 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4394 </pre
></blockquote
></p
>
4396 <p
>The file system is now ready for use. I use rsync to store my
4397 backups in it, and as the metadata used by rsync is downloaded at
4398 mount time, no network traffic (and storage cost) is triggered by
4399 running rsync. To unmount, one should not use the normal umount
4400 command, as this will not flush the cache to the cloud storage, but
4401 instead running the umount.s3ql command like this:
4403 <p
><blockquote
><pre
>
4406 </pre
></blockquote
></p
>
4408 <p
>There is a fsck command available to check the file system and
4409 correct any problems detected. This can be used if the local server
4410 crashes while the file system is mounted, to reset the
"already
4411 mounted
" flag. This is what it look like when processing a working
4412 file system:
</p
>
4414 <p
><blockquote
><pre
>
4415 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4416 Using cached metadata.
4417 File system seems clean, checking anyway.
4418 Checking DB integrity...
4419 Creating temporary extra indices...
4420 Checking lost+found...
4421 Checking cached objects...
4422 Checking names (refcounts)...
4423 Checking contents (names)...
4424 Checking contents (inodes)...
4425 Checking contents (parent inodes)...
4426 Checking objects (reference counts)...
4427 Checking objects (backend)...
4428 ..processed
5000 objects so far..
4429 ..processed
10000 objects so far..
4430 ..processed
15000 objects so far..
4431 Checking objects (sizes)...
4432 Checking blocks (referenced objects)...
4433 Checking blocks (refcounts)...
4434 Checking inode-block mapping (blocks)...
4435 Checking inode-block mapping (inodes)...
4436 Checking inodes (refcounts)...
4437 Checking inodes (sizes)...
4438 Checking extended attributes (names)...
4439 Checking extended attributes (inodes)...
4440 Checking symlinks (inodes)...
4441 Checking directory reachability...
4442 Checking unix conventions...
4443 Checking referential integrity...
4444 Dropping temporary indices...
4445 Backing up old metadata...
4455 Compressing and uploading metadata...
4456 Wrote
0.89 MB of compressed metadata.
4458 </pre
></blockquote
></p
>
4460 <p
>Thanks to the cache, working on files that fit in the cache is very
4461 quick, about the same speed as local file access. Uploading large
4462 amount of data is to me limited by the bandwidth out of and into my
4463 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4464 which is very close to my upload speed, and downloading the same
4465 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4466 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4467 network, not the file system code. I do not know what a good cache
4468 size would be, but suspect that the cache should e larger than your
4469 working set.
</p
>
4471 <p
>I mentioned that only one machine can mount the file system at the
4472 time. If another machine try, it is told that the file system is
4475 <p
><blockquote
><pre
>
4476 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4477 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4478 Using
8 upload threads.
4479 Backend reports that fs is still mounted elsewhere, aborting.
4481 </pre
></blockquote
></p
>
4483 <p
>The file content is uploaded when the cache is full, while the
4484 metadata is uploaded once every
24 hour by default. To ensure the
4485 file system content is flushed to the cloud, one can either umount the
4486 file system, or ask S3QL to flush the cache and metadata using
4489 <p
><blockquote
><pre
>
4490 # s3qlctrl upload-meta /s3ql
4491 # s3qlctrl flushcache /s3ql
4493 </pre
></blockquote
></p
>
4495 <p
>If you are curious about how much space your data uses in the
4496 cloud, and how much compression and deduplication cut down on the
4497 storage usage, you can use s3qlstat on the mounted file system to get
4500 <p
><blockquote
><pre
>
4502 Directory entries:
9141
4505 Total data size:
22049.38 MB
4506 After de-duplication:
21955.46 MB (
99.57% of total)
4507 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4508 Database size:
2.39 MB (uncompressed)
4509 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4511 </pre
></blockquote
></p
>
4513 <p
>I mentioned earlier that there are several possible suppliers of
4514 storage. I did not try to locate them all, but am aware of at least
4515 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4516 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4517 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4518 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4519 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4520 accept payment in Bitcoin. Pick one that suit your need. Some of
4521 them provide several GiB of free storage, but the prize models are
4522 quite different and you will have to figure out what suits you
4525 <p
>While researching this blog post, I had a look at research papers
4526 and posters discussing the S3QL file system. There are several, which
4527 told me that the file system is getting a critical check by the
4528 science community and increased my confidence in using it. One nice
4530 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4531 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4532 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4533 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4534 and Pamela Smith. Please have a look.
</p
>
4536 <p
>Given my problems with different file systems earlier, I decided to
4537 check out the mounted S3QL file system to see if it would be usable as
4538 a home directory (in other word, that it provided POSIX semantics when
4539 it come to locking and umask handling etc). Running
4540 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4541 test code to check file system semantics
</a
>, I was happy to discover that
4542 no error was found. So the file system can be used for home
4543 directories, if one chooses to do so.
</p
>
4545 <p
>If you do not want a locally file system, and want something that
4546 work without the Linux fuse file system, I would like to mention the
4547 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4548 provide locally encrypted backup using a command line client. It have
4549 a nicer access control system, where one can split out read and write
4550 access, allowing some systems to write to the backup and others to
4551 only read from it.
</p
>
4553 <p
>As usual, if you use Bitcoin and want to show your support of my
4554 activities, please send Bitcoin donations to my address
4555 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4560 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4561 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4562 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4563 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4564 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4565 project
</a
> is working on providing the software and hardware for
4566 making it easy for non-technical people to host their data and
4567 communication at home, and being able to communicate with their
4568 friends and family encrypted and away from prying eyes. It has been
4569 going on for a while, and is slowly progressing towards a new test
4570 release (
0.2).
</p
>
4572 <p
>And what day could be better than the Pi day to announce that the
4573 new version will provide
"hard drive
" / SD card / USB stick images for
4574 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4575 system), and can also be installed using a Debian installer preseed
4576 file. The Debian based Freedombox is now based on Debian Jessie,
4577 where most of the needed packages used are already present. Only one,
4578 the freedombox-setup package, is missing. To try to build your own
4579 boot image to test the current status, fetch the freedom-maker scripts
4581 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4582 with a user with sudo access to become root:
4585 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4587 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4588 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4590 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4593 <p
>Root access is needed to run debootstrap and mount loopback
4594 devices. See the README for more details on the build. If you do not
4595 want all three images, trim the make line. But note that thanks to
<a
4596 href=
"https://bugs.debian.org/
741407">a race condition in
4597 vmdebootstrap
</a
>, the build might fail without the patch to the
4598 kpartx call.
</p
>
4600 <p
>If you instead want to install using a Debian CD and the preseed
4601 method, boot a Debian Wheezy ISO and use this boot argument to load
4602 the preseed values:
</p
>
4605 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4608 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4609 recently introduced bug in apt in Jessie
</a
>, the installer will
4610 currently hang while setting up APT sources. Killing the
4611 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4612 installation will get the installation going. This affect all
4613 installations in Jessie, and I expect it will be fixed soon.
</p
>
4615 <p
>Give it a go and let us know how it goes on the mailing list, and help
4616 us get the new release published. :) Please join us on
4617 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4618 irc.debian.org)
</a
> and
4619 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4620 mailing list
</a
> if you want to help make this vision come true.
</p
>
4625 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4626 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4628 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4629 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4630 innetgr tools, because I needed them in
4631 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4632 ng-utils, and it has served me well. I placed the project under the
4633 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4634 repository. But many years ago, the CVS repository was dropped (lost,
4635 not migrated to new hardware, not sure), and the project have lacked a
4636 proper home since then.
</p
>
4638 <p
>Last summer, I had a look at the package and made a new release
4639 fixing a irritating crash bug, but was unable to store the changes in
4640 a proper source control system. I applied for a project on
4641 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4642 to follow up on it. Until today. :)
</p
>
4644 <p
>After many hours of cleaning and migration, the ng-utils project
4645 now have a new home, and a git repository with the highlight of the
4646 history of the project. I published all release tarballs and imported
4647 them into the git repository. As the project is really stable and not
4648 expected to gain new features any time soon, I decided to make a new
4649 release and call it
1.0. Visit the new project home on
4650 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4651 if you want to check it out. The new version is also uploaded into
4652 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4657 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4658 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4660 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4661 <description><p
>A few days ago I decided to try to help the Hurd people to get
4662 their changes into sysvinit, to allow them to use the normal sysvinit
4663 boot system instead of their old one. This follow up on the
4664 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4665 Google Summer of Code work
</a
> done last summer by Justus Winter to
4666 get Debian on Hurd working more like Debian on Linux. To get started,
4667 I downloaded a prebuilt hard disk image from
4668 <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
>,
4669 and started it using virt-manager.
</p
>
4671 <p
>The first think I had to do after logging in (root without any
4672 password) was to get the network operational. I followed
4673 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4674 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4675 commands as root to get the machine to accept a IP address from the
4676 kvm internal DHCP server:
</p
>
4678 <p
><blockquote
><pre
>
4679 settrans -fgap /dev/netdde /hurd/netdde
4680 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4681 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4683 </pre
></blockquote
></p
>
4685 <p
>After this, the machine had internet connectivity, and I could
4686 upgrade it and install the sysvinit packages from experimental and
4687 enable it as the default boot system in Hurd.
</p
>
4689 <p
>But before I did that, I set a password on the root user, as ssh is
4690 running on the machine it for ssh login to work a password need to be
4691 set. Also, note that a bug somewhere in openssh on Hurd block
4692 compression from working. Remember to turn that off on the client
4695 <p
>Run these commands as root to upgrade and test the new sysvinit
4698 <p
><blockquote
><pre
>
4699 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4700 deb http://http.debian.net/debian/ experimental main
4703 apt-get dist-upgrade
4704 apt-get install -t experimental initscripts sysv-rc sysvinit \
4705 sysvinit-core sysvinit-utils
4706 update-alternatives --config runsystem
4707 </pre
></blockquote
></p
>
4709 <p
>To reboot after switching boot system, you have to use
4710 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4711 yet a sysvinit process able to receive the signals from the normal
4712 'reboot
' command. After switching to sysvinit as the boot system,
4713 upgrading every package and rebooting, the network come up with DHCP
4714 after boot as it should, and the settrans/pkill hack mentioned at the
4715 start is no longer needed. But for some strange reason, there are no
4716 longer any login prompt in the virtual console, so I logged in using
4719 <p
>Note that there are some race conditions in Hurd making the boot
4720 fail some times. No idea what the cause is, but hope the Hurd porters
4721 figure it out. At least Justus said on IRC (#debian-hurd on
4722 irc.debian.org) that they are aware of the problem. A way to reduce
4723 the impact is to upgrade to the Hurd packages built by Justus by
4724 adding this repository to the machine:
</p
>
4726 <p
><blockquote
><pre
>
4727 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4728 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4730 </pre
></blockquote
></p
>
4732 <p
>At the moment the prebuilt virtual machine get some packages from
4733 http://ftp.debian-ports.org/debian, because some of the packages in
4734 unstable do not yet include the required patches that are lingering in
4735 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4737 <p
><blockquote
><pre
>
4738 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4739 i emacs - GNU Emacs editor (metapackage)
4740 i gdb - GNU Debugger
4741 i hurd-recommended - Miscellaneous translators
4742 i isc-dhcp-client - ISC DHCP client
4743 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4744 i libc-bin - Embedded GNU C Library: Binaries
4745 i libc-dev-bin - Embedded GNU C Library: Development binaries
4746 i libc0.3 - Embedded GNU C Library: Shared libraries
4747 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4748 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4749 i multiarch-support - Transitional package to ensure multiarch compatibilit
4750 i A x11-common - X Window System (X.Org) infrastructure
4751 i xorg - X.Org X Window System
4752 i A xserver-xorg - X.Org X server
4753 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4755 </pre
></blockquote
></p
>
4757 <p
>All in all, testing hurd has been an interesting experience. :)
4758 X.org did not work out of the box and I never took the time to follow
4759 the porters instructions to fix it. This time I was interested in the
4760 command line stuff.
<p
>
4765 <title>New chrpath release
0.16</title>
4766 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4767 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4768 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4769 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4770 find problems in C, C++ and Java code using static source code
4771 analysis. It can detect a lot of different problems, and is very
4772 useful to find memory and locking bugs in the error handling part of
4773 the source. The company behind it provide
4774 <a href=
"https://scan.coverity.com/
">check of free software projects as
4775 a community service
</a
>, and many hundred free software projects are
4776 already checked. A few days ago I decided to have a closer look at
4777 the Coverity system, and discovered that the
4778 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4779 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4780 projects I am involved with was already registered. But these are
4781 fairly big, and I would also like to have a small and easy project to
4782 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4783 checking of the chrpath project
</a
>. It was
4784 added to the checker and discovered seven potential defects. Six of
4785 these were real, mostly resource
"leak
" when the program detected an
4786 error. Nothing serious, as the resources would be released a fraction
4787 of a second later when the program exited because of the error, but it
4788 is nice to do it right in case the source of the program some time in
4789 the future end up in a library. Having fixed all defects and added
4790 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4791 mailing list for the chrpath developers
</a
>, I decided it was time to
4792 publish a new release. These are the release notes:
</p
>
4794 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4798 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4799 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4800 <li
>Mention new project mailing list in the documentation.
</li
>
4805 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4806 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4807 project if something is wrong with the new release. The test suite
4808 did not discover any old errors, so if you find a new one, please also
4809 include a test suite check.
</p
>
4814 <title>New chrpath release
0.15</title>
4815 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4816 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4817 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4818 <description><p
>After many years break from the package and a vain hope that
4819 development would be continued by someone else, I finally pulled my
4820 acts together this morning and wrapped up a new release of chrpath,
4821 the command line tool to modify the rpath and runpath of already
4822 compiled ELF programs. The update was triggered by the persistence of
4823 Isha Vishnoi at IBM, which needed a new config.guess file to get
4824 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4825 is working on. I checked the
4826 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4827 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4828 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4829 packages for interesting patches (failed to find the source from
4830 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4831 These are the release notes:
</p
>
4833 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4837 <li
>Updated config.sub and config.guess from the GNU project to work
4838 with newer architectures. Thanks to isha vishnoi for the heads
4841 <li
>Updated README with current URLs.
</li
>
4843 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4844 Matthias Klose.
</li
>
4846 <li
>Added missing help for -k|--keepgoing option, using patch by
4847 Petr Machata found in Fedora.
</li
>
4849 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4850 .dynamic is a NULL terminated string. Based on patch found in
4851 Fedora credited Axel Thimm and Christian Krause.
</li
>
4856 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4857 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4858 project if something is wrong with the new release. The test suite
4859 did not discover any old errors, so if you find a new one, please also
4860 include a testsuite check.
</p
>
4865 <title>Debian init.d boot script example for rsyslog
</title>
4866 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4867 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4868 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4869 <description><p
>If one of the points of switching to a new init system in Debian is
4870 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4871 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4872 init.d scripts at all. Here is an example init.d script, ie a rewrite
4873 of /etc/init.d/rsyslog:
</p
>
4875 <p
><pre
>
4876 #!/lib/init/init-d-script
4879 # Required-Start: $remote_fs $time
4880 # Required-Stop: umountnfs $time
4881 # X-Stop-After: sendsigs
4882 # Default-Start:
2 3 4 5
4883 # Default-Stop:
0 1 6
4884 # Short-Description: enhanced syslogd
4885 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4886 # It is quite compatible to stock sysklogd and can be
4887 # used as a drop-in replacement.
4889 DESC=
"enhanced syslogd
"
4890 DAEMON=/usr/sbin/rsyslogd
4891 </pre
></p
>
4893 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4894 script was
137 lines, and the above is just
15 lines, most of it meta
4895 info/comments.
</p
>
4897 <p
>How to do this, you ask? Well, one create a new script
4898 /lib/init/init-d-script looking something like this:
4900 <p
><pre
>
4903 # Define LSB log_* functions.
4904 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4905 # and status_of_proc is working.
4906 . /lib/lsb/init-functions
4909 # Function that starts the daemon/service
4915 #
0 if daemon has been started
4916 #
1 if daemon was already running
4917 #
2 if daemon could not be started
4918 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4920 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4923 # Add code here, if necessary, that waits for the process to be ready
4924 # to handle requests from services started subsequently which depend
4925 # on this one. As a last resort, sleep for some time.
4929 # Function that stops the daemon/service
4934 #
0 if daemon has been stopped
4935 #
1 if daemon was already stopped
4936 #
2 if daemon could not be stopped
4937 # other if a failure occurred
4938 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4939 RETVAL=
"$?
"
4940 [
"$RETVAL
" =
2 ]
&& return
2
4941 # Wait for children to finish too if this is a daemon that forks
4942 # and if the daemon is only ever run from this initscript.
4943 # If the above conditions are not satisfied then add some other code
4944 # that waits for the process to drop all resources that could be
4945 # needed by services started subsequently. A last resort is to
4946 # sleep for some time.
4947 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4948 [
"$?
" =
2 ]
&& return
2
4949 # Many daemons don
't delete their pidfiles when they exit.
4951 return
"$RETVAL
"
4955 # Function that sends a SIGHUP to the daemon/service
4959 # If the daemon can reload its configuration without
4960 # restarting (for example, when it is sent a SIGHUP),
4961 # then implement that here.
4963 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4968 scriptbasename=
"$(basename $
1)
"
4969 echo
"SN: $scriptbasename
"
4970 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4971 script=
"$
1"
4978 NAME=$(basename $DAEMON)
4979 PIDFILE=/var/run/$NAME.pid
4981 # Exit if the package is not installed
4982 #[ -x
"$DAEMON
" ] || exit
0
4984 # Read configuration variable file if it is present
4985 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4987 # Load the VERBOSE setting and other rcS variables
4990 case
"$
1" in
4992 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4994 case
"$?
" in
4995 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4996 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5000 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
5002 case
"$?
" in
5003 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5004 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5008 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5010 #reload|force-reload)
5012 # If do_reload() is not implemented then leave this commented out
5013 # and leave
'force-reload
' as an alias for
'restart
'.
5015 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5019 restart|force-reload)
5021 # If the
"reload
" option is implemented then remove the
5022 #
'force-reload
' alias
5024 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5026 case
"$?
" in
5029 case
"$?
" in
5031 1) log_end_msg
1 ;; # Old process is still running
5032 *) log_end_msg
1 ;; # Failed to start
5042 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5048 </pre
></p
>
5050 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5051 lot. I did not really polish the approach, so it might not always
5052 work out of the box, but you get the idea. I did not try very hard to
5053 optimize it nor make it more robust either.
</p
>
5055 <p
>A better argument for switching init system in Debian than reducing
5056 the size of init scripts (which is a good thing to do anyway), is to
5057 get boot system that is able to handle the kernel events sensibly and
5058 robustly, and do not depend on the boot to run sequentially. The boot
5059 and the kernel have not behaved sequentially in years.
</p
>
5064 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5065 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5066 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5067 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5068 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5069 remote display access is the preferred solution with oVirt and RedHat
5070 Enterprise Virtualization, and I was sad to discover the other day
5071 that the browser plugin needed to use these systems seamlessly was
5072 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5073 for a package
</a
> was from
2012-
04-
10 with no progress since
5074 2013-
04-
01, so I decided to wrap up a package based on the great work
5075 from Cajus Pollmeier and put it in a collab-maint maintained git
5076 repository to get a package I could use. I would very much like
5077 others to help me maintain the package (or just take over, I do not
5078 mind), but as no-one had volunteered so far, I just uploaded it to
5079 NEW. I hope it will be available in Debian in a few days.
</p
>
5081 <p
>The source is now available from
5082 <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
>
5087 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5088 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5090 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5091 <description><p
>The
5092 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5093 program is a a very nice system to create virtual machine images. It
5094 create a image file, add a partition table, mount it and run
5095 debootstrap in the mounted directory to create a Debian system on a
5096 stick. Yesterday, I decided to try to teach it how to make images for
5097 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5098 of a plan to simplify the build system for
5099 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5100 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5101 the virtualbox images, but its current build system made multistrap
5102 based system for Dreamplug images, and it is lacking support for
5103 Raspberry Pi.
</p
>
5105 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5106 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5107 code and adjusted it to be able to build armel images on my amd64
5108 Debian laptop. I ended up giving vmdebootstrap five new options,
5109 allowing me to replicate the image creation process I use to make
5110 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5111 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5112 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5113 call debootstrap with --foreign and to copy the handler into the
5114 generated chroot before running the second stage. This allow
5115 vmdebootstrap to create armel images on an amd64 host. Next I added
5116 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5117 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5118 given file system type, allowing me to create an image with a vfat
5119 partition for the /boot/ stuff. I also added a
<tt
>--variant
5120 variant
</tt
> option to allow me to create smaller images without the
5121 Debian base system packages installed. Finally, I added an option
5122 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5123 as a boot loader. It is not needed on the Raspberry Pi and probably
5124 most other non-x86 architectures. The changes were accepted by the
5125 upstream author of vmdebootstrap yesterday and today, and is now
5127 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5128 upstream project page
</a
>.
</p
>
5130 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5131 create a small script (the customize script) to add the non-free
5132 binary blob needed to boot the Raspberry Pi and the APT source
5135 <p
><pre
>
5137 set -e # Exit on first error
5138 rootdir=
"$
1"
5139 cd
"$rootdir
"
5140 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5141 deb http://http.debian.net/debian/ jessie main contrib non-free
5143 # Install non-free binary blob needed to boot Raspberry Pi. This
5144 # install a kernel somewhere too.
5145 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5146 -O $rootdir/usr/bin/rpi-update
5147 chmod a+x $rootdir/usr/bin/rpi-update
5148 mkdir -p $rootdir/lib/modules
5149 touch $rootdir/boot/start.elf
5150 chroot $rootdir rpi-update
5151 </pre
></p
>
5153 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5154 to build the image:
</p
>
5157 sudo ./vmdebootstrap \
5160 --distribution jessie \
5161 --mirror http://http.debian.net/debian \
5170 --root-password raspberry \
5171 --hostname raspberrypi \
5172 --foreign /usr/bin/qemu-arm-static \
5173 --customize `pwd`/customize \
5175 --package git-core \
5176 --package binutils \
5177 --package ca-certificates \
5180 </pre
></p
>
5182 <p
>The list of packages being installed are the ones needed by
5183 rpi-update to make the image bootable on the Raspberry Pi, with the
5184 exception of netbase, which is needed by debootstrap to find
5185 /etc/hosts with the minbase variant. I really wish there was a way to
5186 set up an Raspberry Pi using only packages in the Debian archive, but
5187 that is not possible as far as I know, because it boots from the GPU
5188 using a non-free binary blob.
</p
>
5190 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5191 probably a few others installed. I have not checked the complete
5192 build dependency list.
</p
>
5194 <p
>The resulting image will not use the hardware floating point unit
5195 on the Raspberry PI, because the armel architecture in Debian is not
5196 optimized for that use. So the images created will be a bit slower
5197 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5202 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5203 <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>
5204 <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>
5205 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5206 <description><p
>The last few days I came across a few good causes that should get
5207 wider attention. I recommend signing and donating to each one of
5210 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5211 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5212 Women program which is a Google Summer of Code like initiative to get
5213 more women involved in free software. One debian sponsor has offered
5214 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5215 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5216 hope you will to. :)
</p
>
5218 <p
>And the Electronic Frontier Foundation just announced plans to
5219 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5220 documentaries about the excessive spying
</a
> on every Internet user that
5221 take place these days, and their need to fund the work. I
've already
5222 donated. Are you next?
</p
>
5224 <p
>For my Norwegian audience, the organisation Studentenes og
5225 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5226 statement under the heading
5227 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5228 Access
</a
> for those of us asking for more focus on open access in the
5229 Norwegian government. So far
499 signatures. I hope you will sign it
5235 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5236 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5237 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5238 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5239 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5240 project
</a
> have been going on for a while, and have presented the
5241 vision, ideas and solution several places. Here is a little
5242 collection of videos of talks and presentation of the project.
</p
>
5246 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5247 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5249 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5250 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5252 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5253 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5254 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5255 (Youtube)
</li
>
5257 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5258 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5260 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5261 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5263 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5264 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5265 York City in
2012</a
> (Youtube)
</li
>
5267 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5268 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5269 (Youtube)
</li
>
5271 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5272 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5274 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5275 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5277 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5278 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5279 2013</a
> (Youtube)
</li
>
5283 <p
>A larger list is available from
5284 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5285 Freedombox Wiki
</a
>.
</p
>
5287 <p
>On other news, I am happy to report that Freedombox based on Debian
5288 Jessie is coming along quite well, and soon both Owncloud and using
5289 Tor should be available for testers of the Freedombox solution. :) In
5290 a few weeks I hope everything needed to test it is included in Debian.
5291 The withsqlite package is already in Debian, and the plinth package is
5292 pending in NEW. The third and vital part of that puzzle is the
5293 metapackage/setup framework, which is still pending an upload. Join
5294 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5295 (#freedombox on irc.debian.org)
</a
> and
5296 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5297 mailing list
</a
> if you want to help make this vision come true.
</p
>
5302 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5303 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5304 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5305 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5306 <description><p
>I was introduced to the
5307 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5308 in
2010, when Eben Moglen presented his vision about serving the need
5309 of non-technical people to keep their personal information private and
5310 within the legal protection of their own homes. The idea is to give
5311 people back the power over their network and machines, and return
5312 Internet back to its intended peer-to-peer architecture. Instead of
5313 depending on a central service, the Freedombox will give everyone
5314 control over their own basic infrastructure.
</p
>
5316 <p
>I
've intended to join the effort since then, but other tasks have
5317 taken priority. But this summers nasty news about the misuse of trust
5318 and privilege exercised by the
"western
" intelligence gathering
5319 communities increased my eagerness to contribute to a point where I
5320 actually started working on the project a while back.
</p
>
5322 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5323 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5324 create a simple and cheap Debian based appliance that anyone can hook
5325 up in their home and get access to secure and private services and
5326 communication. The initial deployment platform have been the
5327 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5328 which is a piece of hardware I do not own. So to be able to test what
5329 the current Freedombox setup look like, I had to come up with a way to install
5330 it on some hardware I do have access to. I have rewritten the
5331 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5332 image build framework to use .deb packages instead of only copying
5333 setup into the boot images, and thanks to this rewrite I am able to
5334 set up any machine supported by Debian Wheezy as a Freedombox, using
5335 the previously mentioned deb (and a few support debs for packages
5336 missing in Debian).
</p
>
5338 <p
>The current Freedombox setup consist of a set of bootstrapping
5340 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5341 and a administrative web interface
5342 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5343 withsqlite), as well as a privacy enhancing proxy based on
5344 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5345 (freedombox-privoxy). There is also a web/javascript based XMPP
5346 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5347 trying (unsuccessfully so far) to talk to the XMPP server
5348 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5349 web interface is pluggable, and the goal is to use it to enable OpenID
5350 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5351 this is really working yet, see
5352 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5353 project TODO
</a
> for links to GIT repositories. Most of the code is
5354 on github at the moment. The HTTP proxy is operational out of the
5355 box, and the admin web interface can be used to add/remove plinth
5356 users. I
've not been able to do anything else with it so far, but
5357 know there are several branches spread around github and other places
5358 with lots of half baked features.
</p
>
5360 <p
>Anyway, if you want to have a look at the current state, the
5361 following recipes should work to give you a test machine to poke
5364 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5368 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5369 <li
>Boot from it, either as CD or USB stick.
</li
>
5370 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5371 to the Debian installer:
<p
>
5372 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5374 <li
>Answer the few language/region/password questions and pick disk to
5375 install on.
</li
>
5377 <li
>When the installation is finished and the machine have rebooted a
5378 few times, your Freedombox is ready for testing.
</li
>
5382 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5386 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5387 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5388 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5390 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5391 </pre
></li
>
5392 <li
><p
>Run this as root:
</p
>
5394 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5397 apt-get install freedombox-setup
5398 /usr/lib/freedombox/setup
5399 </pre
></li
>
5400 <li
>Reboot into your freshly created Freedombox.
</li
>
5404 <p
>You can test it on other architectures too, but because the
5405 freedombox-privoxy package is binary, it will only work as intended on
5406 the architectures where I have had time to build the binary and put it
5407 in my APT repository. But do not let this stop you. It is only a
5408 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5410 <p
>Note that by default Freedombox is a DHCP server on the
5411 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5412 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5413 disable
</tt
>" as root.
</p
>
5415 <p
>Please let me know if this works for you, or if you have any
5416 problems. We gather on the IRC channel
5417 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5418 irc.debian.org and the
5419 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5420 mailing list
</a
>.
</p
>
5422 <p
>Once you get your freedombox operational, you can visit
5423 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5424 welcome screen (dead end - do not be surprised if you are unable to
5425 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5426 to look at the rest of plinth. The default user is
'admin
' and the
5427 default password is
'secret
'.
</p
>
5432 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5433 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5434 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5435 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5436 <description><p
>Earlier, I reported about
5437 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5438 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5439 told by IBM that the original disk should be thrown away. And as
5440 there no longer was a problem if I bricked the firmware, I decided
5441 today to try to install Intel firmware to replace the Lenovo firmware
5442 currently on the disk.
</p
>
5444 <p
>I searched the Intel site for firmware, and found
5445 <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
>
5446 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5447 according to the site should contain the latest firmware for SSD
5448 disks. I inserted the broken disk in one of my spare laptops and
5449 booted the ISO from a USB stick. The disk was recognized, but the
5450 program claimed the newest firmware already were installed and refused
5451 to insert any Intel firmware. So no change, and the disk is still
5452 unable to handle write load. :( I guess the only way to get them
5453 working would be if Lenovo releases new firmware. No idea how likely
5454 that is. Anyway, just blogging about this test for completeness. I
5455 got a working Samsung disk, and see no point in spending more time on
5456 the broken disks.
</p
>
5461 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5462 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5463 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5464 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5465 <description><p
>Today I switched to
5466 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5467 new laptop
</a
>. I
've previously written about the problems I had with
5468 my new Thinkpad X230, which was delivered with an
5469 <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
5470 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5471 sustained writes. My hardware supplier have been very forthcoming in
5472 trying to find a solution, and after first trying with another
5473 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5474 disk instead to fix it once and for all. The Samsung disk survived
5475 the installation of Debian with encrypted disks (filling the disk with
5476 random data during installation killed the first two), and I thus
5477 decided to trust it with my data. I have installed it as a Debian Edu
5478 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5479 server at home using Kerberos and LDAP, and will use it as my work
5480 station from now on.
</p
>
5482 <p
>As this is a solid state disk with no moving parts, I believe the
5483 Debian Wheezy default installation need to be tuned a bit to increase
5484 performance and increase life time of the disk. The Linux kernel and
5485 user space applications do not yet adjust automatically to such
5486 environment. To make it easier for my self, I created a draft Debian
5487 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5488 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5489 for the ssd-setup package
</a
> is available from collab-maint, and it
5490 is set up to adjust the setup of the machine by just installing the
5491 package. If there is any non-SSD disk in the machine, the package
5492 will refuse to install, as I did not try to write any logic to sort
5493 file systems in SSD and non-SSD file systems.
</p
>
5495 <p
>I consider the package a draft, as I am a bit unsure how to best
5496 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5497 where I set up the machine with one large encrypted partition (in
5498 addition to /boot), put LVM on top of this and set up partitions on
5499 top of this again. See the README file in the package source for the
5500 references I used to pick the settings. At the moment these
5501 parameters are tuned:
</p
>
5505 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5506 (adding discard to /etc/crypttab)
</li
>
5508 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5509 this case a cryptsetup partition) by changing issue_discards from
5510 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5512 <li
>Set relatime as a file system option for ext3 and ext4 file
5515 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5516 /etc/fstab.
</li
>
5518 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5520 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5521 cron.daily).
</li
>
5523 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5524 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5528 <p
>During installation, I cancelled the part where the installer fill
5529 the disk with random data, as this would kill the SSD performance for
5530 little gain. My goal with the encrypted file system is to ensure
5531 those stealing my laptop end up with a brick and not a working
5532 computer. I have no hope in keeping the really resourceful people
5533 from getting the data on the disk (see
5534 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5535 Thus I concluded that adding the discard option to crypttab is the
5536 right thing to do.
</p
>
5538 <p
>I considered using the noop I/O scheduler, as several recommended
5539 it for SSD, but others recommended deadline and a benchmark I found
5540 indicated that deadline might be better for interactive use.
</p
>
5542 <p
>I also considered using the
'discard
' file system option for ext3
5543 and ext4, but read that it would give a performance hit ever time a
5544 file is removed, and thought it best to that that slowdown once a day
5545 instead of during my work.
</p
>
5547 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5548 this is already done by Debian Edu.
</p
>
5550 <p
>I have not yet started on the user space tuning. I expect
5551 iceweasel need some tuning, and perhaps other applications too, but
5552 have not yet had time to investigate those parts.
</p
>
5554 <p
>The package should work on Ubuntu too, but I have not yet tested it
5557 <p
>As for the answer to the question in the title of this blog post,
5558 as far as I know, the only solution I know about is to replace the
5559 disk. It might be possible to flash it with Intel firmware instead of
5560 the Lenovo firmware. But I have not tried and did not want to do so
5561 without approval from Lenovo as I wanted to keep the warranty on the
5562 disk until a solution was found and they wanted the broken disks
5568 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5569 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5570 <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>
5571 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5572 <description><p
>A few days ago, I wrote about
5573 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5574 problems I experienced with my new X230 and its SSD disk
</a
>, which
5575 was dying during installation because it is unable to cope with
5576 sustained write. My supplier is in contact with
5577 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5578 replacement disk to try to fix the problem. They decided to send an
5579 identical model, so my hopes for a permanent fix was slim.
</p
>
5581 <p
>Anyway, today I got the replacement disk and tried to install
5582 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5583 same firmware version as the original. This time my hope raised
5584 slightly as the installation progressed, as the original disk used to
5585 die after
4-
7% of the disk was written to, while this time it kept
5586 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5587 died again and I was back on square one. I still do not have a new
5588 laptop with a disk I can trust. I can not live with a disk that might
5589 lock up when I download a new
5590 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5591 other large files. I look forward to hearing from my supplier with
5592 the next proposal from Lenovo.
</p
>
5594 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5595 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5596 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5597 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5598 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5599 P/N
45N8295, P0C38732.
</p
>
5601 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5602 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5603 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5604 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5605 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5606 P/N
45N8295, P0C38732.
</p
>
5608 <p
>The only difference is in the first number (serial number?), ISN,
5609 SA, date and WNPP values. Mentioning all the details here in case
5610 someone is able to use the information to find a way to identify the
5611 failing disk among working ones (if any such working disk actually
5617 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5618 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5620 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5621 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5622 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5623 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5624 member assosiation NUUG
</a
> and
5625 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5626 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5627 Bitraf
</a
>.
</p
>
5629 <p
>It starts
10:
00 and continue until late evening. Everyone is
5630 welcome, and there is no fee to participate. There is on the other
5631 hand limited space, and only room for
30 people. Please put your name
5632 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5633 wiki page
</a
> if you plan to join us.
</p
>
5638 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5639 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5640 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5641 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5642 <description><p
>Half a year ago, I reported that I had to find a
5643 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5644 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5645 time to spend on it, and it took a while to find a model I believe
5646 will do the job, but two days ago the replacement finally arrived. I
5648 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5649 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5650 a roaming workstation, and it seemed to work flawlessly. But my
5651 second installation with encrypted disk was not as successful. More
5652 on that below.
</p
>
5654 <p
>I had a hard time trying to track down a good laptop, as my most
5655 important requirements (robust and with a good keyboard) are never
5656 listed in the feature list. But I did get good help from the search
5657 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5658 allowed me to limit the list of interesting laptops based on my other
5659 requirements. A bit surprising that SSD disk are not disks according
5660 to that search interface, so I had to drop specifying the number of
5661 disks from my search parameters. I also asked around among friends to
5662 get their impression on keyboards and robustness.
</p
>
5664 <p
>So the new laptop arrived, and it is quite a lot wider than the
5665 X41. I am not quite convinced about the keyboard, as it is
5666 significantly wider than my old keyboard, and I have to stretch my
5667 hand a lot more to reach the edges. But the key response is fairly
5668 good and the individual key shape is fairly easy to handle, so I hope
5669 I will get used to it. My old X40 was starting to fail, and I really
5670 needed a new laptop now. :)
</p
>
5672 <p
>Turning off the touch pad was simple. All it took was a quick
5673 visit to the BIOS during boot it disable it.
</p
>
5675 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5676 lock up during load. And this happen when installing Debian Wheezy
5677 with encrypted disk, while the disk is being filled with random data.
5678 I also tested to install Ubuntu Raring, and it happen there too if I
5679 reenable the code to fill the disk with random data (it is disabled by
5680 default in Ubuntu). And the bug with is already known. It was
5681 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5682 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5683 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5684 kernel developers as
5685 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5686 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5687 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5688 Lenovo forums, both for
5689 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5690 2012-
11-
10</a
> and for
5691 <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
5692 03-
20-
2013</a
>. The problem do not only affect installation. The
5693 reports state that the disk lock up during use if many writes are done
5694 on the disk, so it is much no use to work around the installation
5695 problem and end up with a computer that can lock up at any moment.
5697 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5698 available
</a
> that will lock up the hard drive after running a few
5699 minutes by writing to a file.
</p
>
5701 <p
>I
've contacted my supplier and asked how to handle this, and after
5702 contacting PCHELP Norway (request
01D1FDP) which handle support
5703 requests for Lenovo, his first suggestion was to upgrade the disk
5704 firmware. Unfortunately there is no newer firmware available from
5705 Lenovo, as my disk already have the most recent one (version LF1i). I
5706 hope to hear more from him today and hope the problem can be
5712 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5713 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5715 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5716 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5717 trusty old Thinkpad X41. Unfortunately I did not have much time to
5718 spend on it, but today the replacement finally arrived. I ended up
5719 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5720 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5721 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5722 this, it is installing what I hope will be a more final installation,
5723 with a encrypted hard drive to ensure any dope head stealing it end up
5724 with an expencive door stop.
</p
>
5726 <p
>I had a hard time trying to track down a good laptop, as my most
5727 important requirements (robust and with a good keyboard) are never
5728 listed in the feature list. But I did get good help from the search
5729 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5730 allowed me to limit the list of interesting laptops based on my other
5731 requirements. A bit surprising that SSD disk are not disks, so I had
5732 to drop number of disks from my search parameters.
</p
>
5734 <p
>I am not quite convinced about the keyboard, as it is significantly
5735 wider than my old keyboard, and I have to stretch my hand a lot more
5736 to reach the edges. But the key response is fairly good and the
5737 individual key shape is fairly easy to handle, so I hope I will get
5738 used to it. My old X40 was starting to fail, and I really needed a
5739 new laptop now. :)
</p
>
5741 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5746 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5747 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5748 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5749 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5750 <description><p
>It annoys me when the computer fail to do automatically what it is
5751 perfectly capable of, and I have to do it manually to get things
5752 working. One such task is to find out what firmware packages are
5753 needed to get the hardware on my computer working. Most often this
5754 affect the wifi card, but some times it even affect the RAID
5755 controller or the ethernet card. Today I pushed version
0.4 of the
5756 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5757 including a new script isenkram-autoinstall-firmware handling the
5758 process of asking all the loaded kernel modules what firmware files
5759 they want, find debian packages providing these files and install the
5760 debian packages. Here is a test run on my laptop:
</p
>
5762 <p
><pre
>
5763 # isenkram-autoinstall-firmware
5764 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5765 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5766 info: locating packages with the requested firmware files
5767 info: Updating APT sources after adding non-free APT source
5768 info: trying to install firmware-ipw2x00
5771 Preconfiguring packages ...
5772 Selecting previously deselected package firmware-ipw2x00.
5773 (Reading database ...
259727 files and directories currently installed.)
5774 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5775 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5777 </pre
></p
>
5779 <p
>When all the requested firmware is present, a simple message is
5780 printed instead:
</p
>
5782 <p
><pre
>
5783 # isenkram-autoinstall-firmware
5784 info: did not find any firmware files requested by loaded kernel modules. exiting
5786 </pre
></p
>
5788 <p
>It could use some polish, but it is already working well and saving
5789 me some time when setting up new machines. :)
</p
>
5791 <p
>So, how does it work? It look at the set of currently loaded
5792 kernel modules, and look up each one of them using modinfo, to find
5793 the firmware files listed in the module meta-information. Next, it
5794 download the Contents file from a nearby APT mirror, and search for
5795 the firmware files in this file to locate the package with the
5796 requested firmware file. If the package is in the non-free section, a
5797 non-free APT source is added and the package is installed using
5798 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5801 <p
>I hope someone find time to implement a more polished version of
5802 this script as part of the hw-detect debian-installer module, to
5803 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5804 #
655507</a
>. There really is no need to insert USB sticks with
5805 firmware during a PXE install when the packages already are available
5806 from the nearby Debian mirror.
</p
>
5811 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5812 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5813 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5814 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5815 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5816 the screen just turn black when Linux boot, either during installation
5817 or on first boot from the hard disk. I
've seen it once in a while the
5818 last few years, but only recently understood the cause. I
've seen it
5819 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5820 The reason seem to be in the wiring of some laptops. The system to
5821 control the screen background light is inverted, so when Linux try to
5822 turn the brightness fully on, it end up turning it off instead. I do
5823 not know which Linux drivers are affected, but this post is about the
5824 i915 driver used by the
5825 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5826 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5828 <p
>The problem can be worked around two ways. Either by adding
5829 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5830 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5831 option when it load the i915 kernel module. On Debian and Ubuntu, it
5832 can be done by running these commands as root:
</p
>
5835 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5836 update-initramfs -u -k all
5839 <p
>Since March
2012 there is
5840 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5841 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5842 hardware have this problem, and get the driver to invert the
5843 brightness setting automatically. To use it, one need to add a row in
5844 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5845 intel_quirks array
</a
> in the driver source
5846 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5847 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5848 number (vendor number
8086 is assumed) and subdevice vendor and device
5851 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5852 -vvnn
</tt
> for the video card in question:
</p
>
5854 <p
><pre
>
5855 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5856 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5857 (rev
09) (prog-if
00 [VGA controller])
5858 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5859 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5860 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5861 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5862 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5864 Interrupt: pin A routed to IRQ
42
5865 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5866 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5867 Region
4: I/O ports at
4000 [size=
64]
5868 Expansion ROM at
<unassigned
> [disabled]
5869 Capabilities:
<access denied
>
5870 Kernel driver in use: i915
5871 </pre
></p
>
5873 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5875 <p
><pre
>
5876 struct intel_quirk intel_quirks[] = {
5878 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5879 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5882 </pre
></p
>
5884 <p
>According to the kernel module instructions (as seen using
5885 <tt
>modinfo i915
</tt
>), information about hardware needing the
5886 invert_brightness flag should be sent to the
5887 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5888 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5889 developers. But my email about the laptop sent
2013-
06-
03 have not
5891 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5892 web archive for the mailing list
</a
>, so I suspect they do not accept
5893 emails from non-subscribers. Because of this, I sent my patch also to
5894 the Debian bug tracking system instead as
5895 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5896 sure the patch is not lost.
</p
>
5898 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5899 with this problem working properly with Linux. If you use Gnome, your
5900 worries should be over at this point. But if you use KDE, there is
5901 something in KDE ignoring the invert_brightness setting and turning on
5902 the screen during login. I
've reported it to Debian as
5903 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5904 have no idea yet how to figure out exactly what subsystem is doing
5905 this. Perhaps you can help? Perhaps you know what the Gnome
5906 developers did to handle this, and this can give a clue to the KDE
5907 developers? Or you know where in KDE the screen brightness is changed
5908 during login? If so, please update the BTS report (or get in touch if
5909 you do not know how to update BTS).
</p
>
5911 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5912 acpi_backlight=vendor, to disable ACPI backlight support completely,
5913 as the ACPI information on the machine is trash and it is better to
5914 leave it to the intel video driver to control the screen
5915 backlight.
</p
>
5920 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5921 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5922 <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>
5923 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5924 <description><p
>Two days ago, I asked
5925 <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
5926 I could install Linux on a Packard Bell EasyNote LV computer
5927 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5928 with the obstacles put in the way of Linux users on a laptop with UEFI
5929 and Windows
8.
</p
>
5931 <p
>I never found out if the cause of my problems were the use of UEFI
5932 secure booting or fast boot. I suspect fast boot was the problem,
5933 causing the firmware to boot directly from HD without considering any
5934 key presses and alternative devices, but do not know UEFI settings
5935 enough to tell.
</p
>
5937 <p
>There is no way to install Linux on the machine in question without
5938 opening the box and disconnecting the hard drive! This is as far as I
5939 can tell, the only way to get access to the firmware setup menu
5940 without accepting the Windows
8 license agreement. I am told (and
5941 found description on how to) that it is possible to configure the
5942 firmware setup once booted into Windows
8. But as I believe the terms
5943 of that agreement are completely unacceptable, accepting the license
5944 was never an alternative. I do not enter agreements I do not intend
5945 to follow.
</p
>
5947 <p
>I feared I had to return the laptops and ask for a refund, and
5948 waste many hours on this, but luckily there was a way to get it to
5949 work. But I would not recommend it to anyone planning to run Linux on
5950 it, and I have become sceptical to Windows
8 certified laptops. Is
5951 this the way Linux will be forced out of the market place, by making
5952 it close to impossible for
"normal
" users to install Linux without
5953 accepting the Microsoft Windows license terms? Or at least not
5954 without risking to loose the warranty?
</p
>
5956 <p
>I
've updated the
5957 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5958 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5959 do not have to struggle as much as I did to get Linux into the
5962 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5963 Michael Tokarev and others for feedback and ideas.
</p
>
5968 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5969 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5970 <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>
5971 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5972 <description><p
>I
've run into quite a problem the last few days. I bought three
5973 new laptops for my parents and a few others. I bought Packard Bell
5974 Easynote LV to run Kubuntu on and use as their home computer. But I
5975 am completely unable to figure out how to install Linux on it. The
5976 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5977 instead of a BIOS to boot.
</p
>
5979 <p
>The problem is that I am unable to get it to PXE boot, and unable
5980 to get it to boot the Linux installer from my USB stick. I have yet
5981 to try the DVD install, and still hope it will work. when I turn on
5982 the computer, there is no information on what buttons to press to get
5983 the normal boot menu. I expect to get some boot menu to select PXE or
5984 USB stick booting. When booting, it first ask for the language to
5985 use, then for some regional settings, and finally if I will accept the
5986 Windows
8 terms of use. As these terms are completely unacceptable to
5987 me, I have no other choice but to turn off the computer and try again
5988 to get it to boot the Linux installer.
</p
>
5990 <p
>I have gathered my findings so far on a Linlap page about the
5991 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5992 EasyNote LV
</a
> model. If you have any idea how to get Linux
5993 installed on this machine, please get in touch or update that wiki
5994 page. If I can
't find a way to install Linux, I will have to return
5995 the laptop to the seller and find another machine for my parents.
</p
>
5997 <p
>I wonder, is this the way Linux will be forced out of the market
5998 using UEFI and
"secure boot
" by making it impossible to install Linux
5999 on new Laptops?
</p
>
6004 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6005 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6006 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6007 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6008 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6009 an operating system based on Debian intended for use in schools. It
6010 contain a turn-key solution for the computer network provided to
6011 pupils in the primary schools. It provide both the central server,
6012 network boot servers and desktop environments with heaps of
6013 educational software. The project was founded almost
12 years ago,
6014 2001-
07-
02. If you want to support the project, which is in need for
6015 cash to fund developer gatherings and other project related activity,
6016 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6017 donate some money
</a
>.
6019 <p
>A topic that come up again and again on the Debian Edu mailing
6020 lists and elsewhere, is the question on how to transform a Debian or
6021 Ubuntu installation into a Debian Edu installation. It isn
't very
6022 hard, and last week I wrote a script to replicate the steps done by
6023 the Debian Edu installer.
</p
>
6025 <p
>The script,
6026 <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/
>
6027 in the debian-edu-config package, will go through these six steps and
6028 transform an existing Debian Wheezy or Ubuntu (untested) installation
6029 into a Debian Edu Workstation:
</p
>
6033 <li
>Add skolelinux related APT sources.
</li
>
6034 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6035 <li
>Install debian-edu-install to load preseeding values and pull in
6036 our configuration.
</li
>
6037 <li
>Preseed debconf database with profile setup in
6038 /etc/debian-edu/config, and run tasksel to install packages
6039 according to the profile specified in the config above,
6040 overriding some of the Debian automation machinery.
</li
>
6041 <li
>Run debian-edu-cfengine-D installation to configure everything
6042 that could not be done using preseeding.
</li
>
6043 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6047 <p
>There are some steps in the Debian Edu installation that can not be
6048 replicated like this. Disk partitioning and LVM setup, for example.
6049 So this script just assume there is enough disk space to install all
6050 the needed packages.
</p
>
6052 <p
>The script was created to help a Debian Edu student working on
6053 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6054 Debian Edu client, and using it he can take the existing
6055 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6056 transform it into a fully functioning Debian Edu Workstation (or
6057 Roaming Workstation, or whatever :).
</p
>
6059 <p
>The default setting in the script is to create a KDE Workstation.
6060 If a LXDE based Roaming workstation is wanted instead, modify the
6061 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6063 <p
><pre
>
6064 PROFILE=
"Roaming-Workstation
"
6065 DESKTOP=
"lxde
"
6066 </pre
></p
>
6068 <p
>The script could even become useful to set up Debian Edu servers in
6069 the cloud, by starting with a virtual Debian installation at some
6070 virtual hosting service and setting up all the services on first
6076 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6077 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6078 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6079 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6080 <description><P
>In January,
6081 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6082 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6083 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6084 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6085 marvellous construction system from Denmark. We also created
6086 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6087 a place to take notes and write down our plans and hopes. And several
6088 people showed up to help. I was very happy to see the effect of my
6089 call. Since the small start, we have a debtags tag
6090 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6091 tag for LEGO related packages, and now count
10 packages related to
6092 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6094 <p
><table
>
6095 <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
>
6096 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6097 <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
>
6098 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6099 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6100 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6101 <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
>
6102 <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
>
6103 <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
>
6104 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6105 </table
></p
>
6107 <p
>Some of these are available in Wheezy, and all but one are
6108 currently available in Jessie/testing. leocad is so far only
6109 available in experimental.
</p
>
6111 <p
>If you care about LEGO in Debian, please join us on IRC and help
6112 adding the rest of the great free software tools available on Linux
6113 for LEGO designers.
</p
>
6118 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6119 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6120 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6121 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6122 <description><p
>When I woke up this morning, I was very happy to see that the
6123 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6124 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6125 Debian release, and I expect to move my machines at home over to it fairly
6128 <p
>The new debian release contain heaps of new stuff, and one program
6129 in particular make me very happy to see included. The
6130 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6131 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6132 included for the first time. Alongside similar programs like
6133 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6134 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6135 it allow for visual programming where syntax errors can not happen,
6136 and a friendly programming environment for learning to control the
6137 computer. Scratch will also be included in the next release of Debian
6140 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6141 Edu/Skolelinux release too. The
6142 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6143 alpha release
</a
> went out last week, and the next should soon
6149 <title>Isenkram
0.2 finally in the Debian archive
</title>
6150 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6152 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6153 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6154 package
</a
> finally made it into the archive, after lingering in NEW
6155 for many months. I uploaded it to the Debian experimental suite
6156 2013-
01-
27, and today it was accepted into the archive.
</p
>
6158 <p
>Isenkram is a system for suggesting to users what packages to
6159 install to work with a pluggable hardware device. The suggestion pop
6160 up when the device is plugged in. For example if a Lego Mindstorm NXT
6161 is inserted, it will suggest to install the program needed to program
6162 the NXT controller. Give it a go, and report bugs and suggestions to
6168 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6169 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6170 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6171 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6172 <description><p
>My
6173 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6174 bitcoin related blog post
</a
> mentioned that the new
6175 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6176 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6177 2013-
01-
19, and have been available in unstable since then. It was
6178 automatically copied to Ubuntu, and is available in their Raring
6179 version too.
</p
>
6181 <p
>But there is a strange problem with the build that block this new
6182 version from being available on the i386 and kfreebsd-i386
6183 architectures. For some strange reason, the autobuilders in Debian
6184 for these architectures fail to run the test suite on these
6185 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6186 We are so far unable to reproduce it when building it manually, and
6187 no-one have been able to propose a fix. If you got an idea what is
6188 failing, please let us know via the BTS.
</p
>
6190 <p
>One feature that is annoying me with of the bitcoin client, because
6191 I often run low on disk space, is the fact that the client will exit
6192 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6193 #
696715</a
>). So make sure you have enough disk space when you run
6196 <p
>As usual, if you use bitcoin and want to show your support of my
6197 activities, please send Bitcoin donations to my address
6198 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6203 <title>Welcome to the world, Isenkram!
</title>
6204 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6205 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6206 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6207 <description><p
>Yesterday, I
6208 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6209 for testers
</a
> for my prototype for making Debian better at handling
6210 pluggable hardware devices, which I
6211 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6212 out to create
</a
> earlier this month. Several valuable testers showed
6213 up, and caused me to really want to to open up the development to more
6214 people. But before I did this, I want to come up with a sensible name
6215 for this project. Today I finally decided on a new name, and I have
6216 renamed the project from hw-support-handler to this new name. In the
6217 process, I moved the source to git and made it available as a
6218 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6219 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6220 To fetch and build the latest version of the source, use
</p
>
6223 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6224 cd isenkram
&& git-buildpackage -us -uc
6227 <p
>I have not yet adjusted all files to use the new name yet. If you
6228 want to hack on the source or improve the package, please go ahead.
6229 But please talk to me first on IRC or via email before you do major
6230 changes, to make sure we do not step on each others toes. :)
</p
>
6232 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6233 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6234 stuff, in other words. I
've been told it is the Norwegian variant of
6235 the German word eisenkram, for those that are familiar with that
6238 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6239 instructions, to avoid confusing people with an error from the signing
6242 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6243 clone argument to avoid the need for authentication.
</p
>
6248 <title>First prototype ready making hardware easier to use in Debian
</title>
6249 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6250 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6251 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6252 <description><p
>Early this month I set out to try to
6253 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6254 the Debian support for pluggable hardware devices
</a
>. Now my
6255 prototype is working, and it is ready for a larger audience. To test
6257 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6258 from the Debian Edu subversion repository
</a
>, build and install the
6259 package. You might have to log out and in again activate the
6260 autostart script.
</p
>
6262 <p
>The design is simple:
</p
>
6266 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6267 hw-support-handlerd to start when the user log in.
</li
>
6269 <li
>This program listen for kernel events about new hardware (directly
6270 from the kernel like udev does), not using HAL dbus events as I
6271 initially did.
</li
>
6273 <li
>When new hardware is inserted, look up the hardware modalias in
6274 the APT database, a database
6275 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6276 via HTTP
</a
> and a database available as part of the package.
</li
>
6278 <li
>If a package is mapped to the hardware in question, the package
6279 isn
't installed yet and this is the first time the hardware was
6280 plugged in, show a desktop notification suggesting to install the
6281 package or packages.
</li
>
6283 <li
>If the user click on the
'install package now
' button, ask
6284 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6286 <li
>aptdaemon ask for root password or sudo password, and install the
6287 package while showing progress information in a window.
</li
>
6291 <p
>I still need to come up with a better name for the system. Here
6292 are some screen shots showing the prototype in action. First the
6293 notification, then the password request, and finally the request to
6294 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6296 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6297 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6298 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6299 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6300 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6302 <p
>The prototype still need to be improved with longer timeouts, but
6303 is already useful. The database of hardware to package mappings also
6304 need more work. It is currently compatible with the Ubuntu way of
6305 storing such information in the package control file, but could be
6306 changed to use other formats instead or in addition to the current
6307 method. I
've dropped the use of discover for this mapping, as the
6308 modalias approach is more flexible and easier to use on Linux as long
6309 as the Linux kernel expose its modalias strings directly.
</p
>
6311 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6312 here is the command required to check out and build the source: Use
6313 '<tt
>svn checkout
6314 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6315 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6316 devscripts package.
</p
>
6318 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6319 renamed to Isenkram and the source moved from the Debian Edu
6320 subversion repository to a Debian collab-maint git repository. See
6321 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6322 instructions
</a
> for details.
</p
>
6327 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6328 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6329 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6330 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6331 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6332 suddenly in bed. With a quiet whimper, it went completely quiet and
6333 black. The power button was no longer able to turn it on. It was a
6334 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6335 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6336 Compaq I had before that. Now I need to find a replacement. To keep
6337 going during Christmas, I moved the one year old SSD disk to my old
6338 X40 where it fitted (only one I had left that could use it), but it is
6339 not a durable solution.
6341 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6342 got a new one more than
10 years ago. It still holds true.:)
</p
>
6346 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6347 than A4).
</li
>
6348 <li
>Robust, it will be in my backpack every day.
</li
>
6349 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6350 <li
>Long battery life time. Preferable a week.
</li
>
6351 <li
>Internal WIFI network card.
</li
>
6352 <li
>Internal Twisted Pair network card.
</li
>
6353 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6354 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6355 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6357 <li
>Hardware supported by Debian Stable, ie the default kernel and
6358 X.org packages.
</li
>
6359 <li
>Quiet, preferably fan free (or at least not using the fan most of
6364 <p
>You will notice that there are no RAM and CPU requirements in the
6365 list. The reason is simply that the specifications on laptops the
6366 last
10-
15 years have been sufficient for my needs, and I have to look
6367 at other features to choose my laptop. But are there still made as
6368 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6369 robust, and Thinkpads seem to be heading in the wrong direction since
6370 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6371 still be useful.
</p
>
6373 <p
>Perhaps I should rethink my needs, and look for a pad with an
6374 external keyboard? I
'll have to check the
6375 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6376 well-supported laptops, or perhaps just buy one preinstalled from one
6377 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6378 Pre-loaded site
</a
>.
</p
>
6383 <title>How to find a browser plugin supporting a given MIME type
</title>
6384 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6385 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6386 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6387 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6388 install to get support for a given MIME type. Thanks to
6389 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6390 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6391 Unfortunately, not very many packages provide the needed meta
6392 information, Anyway, here is a small script to look up all browser
6393 plugin packages announcing ther MIME support using this specification:
</p
>
6399 def pkgs_handling_mimetype(mimetype):
6404 version = pkg.candidate
6406 version = pkg.installed
6409 record = version.record
6410 if not record.has_key(
'Npp-MimeType
'):
6412 mime_types = record[
'Npp-MimeType
'].split(
',
')
6413 for t in mime_types:
6414 t = t.rstrip().strip()
6416 thepkgs.append(pkg.name)
6418 mimetype =
"audio/ogg
"
6419 if
1 < len(sys.argv):
6420 mimetype = sys.argv[
1]
6421 print
"Browser plugin packages supporting %s:
" % mimetype
6422 for pkg in pkgs_handling_mimetype(mimetype):
6423 print
" %s
" %pkg
6426 <p
>It can be used like this to look up a given MIME type:
</p
>
6429 % ./apt-find-browserplug-for-mimetype
6430 Browser plugin packages supporting audio/ogg:
6432 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6433 Browser plugin packages supporting application/x-shockwave-flash:
6434 browser-plugin-gnash
6438 <p
>In Ubuntu this mechanism is combined with support in the browser
6439 itself to query for plugins and propose to install the needed
6440 packages. It would be great if Debian supported such feature too. Is
6441 anyone working on adding it?
</p
>
6443 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6444 request for icweasel support for this feature is
6445 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6446 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6447 of manpower and wish for a different design is the reason thus feature
6448 is not yet in iceweasel from Debian.
</p
>
6453 <title>What is the most supported MIME type in Debian?
</title>
6454 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6455 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6456 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6457 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6458 proposal to add AppStream information to the Debian archive
</a
>, is a
6459 proposal to make it possible for a Desktop application to propose to
6460 the user some package to install to gain support for a given MIME
6461 type, font, library etc. that is currently missing. With such
6462 mechanism in place, it would be possible for the desktop to
6463 automatically propose and install leocad if some LDraw file is
6464 downloaded by the browser.
</p
>
6466 <p
>To get some idea about the current content of the archive, I decided
6467 to write a simple program to extract all .desktop files from the
6468 Debian archive and look up the claimed MIME support there. The result
6470 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6471 site
</a
>. Using the collected information, it become possible to
6472 answer the question in the title. Here are the
20 most supported MIME
6473 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6474 The complete list is available from the link above.
</p
>
6476 <p
><strong
>Debian Stable:
</strong
></p
>
6480 ----- -----------------------
6496 18 application/x-ogg
6503 <p
><strong
>Debian Testing:
</strong
></p
>
6507 ----- -----------------------
6523 18 application/x-ogg
6530 <p
><strong
>Debian Unstable:
</strong
></p
>
6534 ----- -----------------------
6551 18 application/x-ogg
6557 <p
>I am told that PackageKit can provide an API to access the kind of
6558 information mentioned in DEP-
11. I have not yet had time to look at
6559 it, but hope the PackageKit people in Debian are on top of these
6562 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6563 discovering a typo in my script.
</p
>
6568 <title>Using modalias info to find packages handling my hardware
</title>
6569 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6570 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6571 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6572 <description><p
>Yesterday, I wrote about the
6573 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6574 values provided by the Linux kernel
</a
> following my hope for
6575 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6576 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6577 modalias values attached to package names can be used to map packages
6578 to hardware. This allow the system to look up and suggest relevant
6579 packages when I plug in some new hardware into my machine, and replace
6580 discover and discover-data as the database used to map hardware to
6583 <p
>I create a modaliases file with entries like the following,
6584 containing package name, kernel module name (if relevant, otherwise
6585 the package name) and globs matching the relevant hardware
6588 <p
><blockquote
>
6589 Package: package-name
6590 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6591 </blockquote
></p
>
6593 <p
>It is fairly trivial to write code to find the relevant packages
6594 for a given modalias value using this file.
</p
>
6596 <p
>An entry like this would suggest the video and picture application
6597 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6599 <p
><blockquote
>
6601 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6602 </blockquote
></p
>
6604 <p
>An entry like this would suggest the pcmciautils package when a
6605 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6607 <p
><blockquote
>
6608 Package: pcmciautils
6609 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6610 </blockquote
></p
>
6612 <p
>An entry like this would suggest the package colorhug-client when
6613 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6615 <p
><blockquote
>
6616 Package: colorhug-client
6617 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6618 </blockquote
></p
>
6620 <p
>I believe the format is compatible with the format of the Packages
6621 file in the Debian archive. Ubuntu already uses their Packages file
6622 to store their mappings from packages to hardware.
</p
>
6624 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6625 announce the hardware it support in a way my prototype understand.
6626 This allow those publishing packages in an APT source outside the
6627 Debian archive as well as those backporting packages to make sure the
6628 hardware mapping are included in the package meta information. I
've
6629 tested such header in the pymissile package, and its modalias mapping
6630 is working as it should with my prototype. It even made it to Ubuntu
6633 <p
>To test if it was possible to look up supported hardware using only
6634 the shell tools available in the Debian installer, I wrote a shell
6635 implementation of the lookup code. The idea is to create files for
6636 each modalias and let the shell do the matching. Please check out and
6638 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6639 shell script. It run without any extra dependencies and fetch the
6640 hardware mappings from the Debian archive and the subversion
6641 repository where I currently work on my prototype.
</p
>
6643 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6644 install yubikey-personalization:
</p
>
6646 <p
><blockquote
>
6647 % ./hw-support-lookup
6648 <br
>yubikey-personalization
6650 </blockquote
></p
>
6652 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6653 propose to install the pcmciautils package:
</p
>
6655 <p
><blockquote
>
6656 % ./hw-support-lookup
6657 <br
>pcmciautils
6659 </blockquote
></p
>
6661 <p
>If you know of any hardware-package mapping that should be added to
6662 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6663 database
</a
>, please tell me about it.
</p
>
6665 <p
>It could be possible to generate several of the mappings between
6666 packages and hardware. One source would be to look at packages with
6667 kernel modules, ie packages with *.ko files in /lib/modules/, and
6668 extract their modalias information. Another would be to look at
6669 packages with udev rules, ie packages with files in
6670 /lib/udev/rules.d/, and extract their vendor/model information to
6671 generate a modalias matching rule. I have not tested any of these to
6672 see if it work.
</p
>
6674 <p
>If you want to help implementing a system to let us propose what
6675 packages to install when new hardware is plugged into a Debian
6676 machine, please send me an email or talk to me on
6677 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6682 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6683 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6685 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6686 <description><p
>While looking into how to look up Debian packages based on hardware
6687 information, to find the packages that support a given piece of
6688 hardware, I refreshed my memory regarding modalias values, and decided
6689 to document the details. Here are my findings so far, also available
6691 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6692 Debian Edu subversion repository
</a
>:
6694 <p
><strong
>Modalias decoded
</strong
></p
>
6696 <p
>This document try to explain what the different types of modalias
6697 values stands for. It is in part based on information from
6698 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6699 &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;,
6700 &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
6701 &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;.
6703 <p
>The modalias entries for a given Linux machine can be found using
6704 this shell script:
</p
>
6707 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6710 <p
>The supported modalias globs for a given kernel module can be found
6711 using modinfo:
</p
>
6714 % /sbin/modinfo psmouse | grep alias:
6715 alias: serio:ty05pr*id*ex*
6716 alias: serio:ty01pr*id*ex*
6720 <p
><strong
>PCI subtype
</strong
></p
>
6722 <p
>A typical PCI entry can look like this. This is an Intel Host
6723 Bridge memory controller:
</p
>
6725 <p
><blockquote
>
6726 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6727 </blockquote
></p
>
6729 <p
>This represent these values:
</p
>
6734 sv
00001028 (subvendor)
6735 sd
000001AD (subdevice)
6737 sc
00 (bus subclass)
6741 <p
>The vendor/device values are the same values outputted from
'lspci
6742 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6743 0600. The
0600 class is a host bridge. Other useful bus values are
6744 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6746 <p
>Not sure how to figure out the interface value, nor what it
6749 <p
><strong
>USB subtype
</strong
></p
>
6751 <p
>Some typical USB entries can look like this. This is an internal
6752 USB hub in a laptop:
</p
>
6754 <p
><blockquote
>
6755 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6756 </blockquote
></p
>
6758 <p
>Here is the values included in this alias:
</p
>
6761 v
1D6B (device vendor)
6762 p
0001 (device product)
6764 dc
09 (device class)
6765 dsc
00 (device subclass)
6766 dp
00 (device protocol)
6767 ic
09 (interface class)
6768 isc
00 (interface subclass)
6769 ip
00 (interface protocol)
6772 <p
>The
0900 device class/subclass means hub. Some times the relevant
6773 class is in the interface class section. For a simple USB web camera,
6774 these alias entries show up:
</p
>
6776 <p
><blockquote
>
6777 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6778 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6779 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6780 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6781 </blockquote
></p
>
6783 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6784 camera),
0101 is audio control device and
0102 is audio streaming (aka
6785 microphone). Thus this is a camera with microphone included.
</p
>
6787 <p
><strong
>ACPI subtype
</strong
></p
>
6789 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6790 receiver in a Thinkpad X40:
</p
>
6792 <p
><blockquote
>
6793 acpi:IBM0071:PNP0511:
6794 </blockquote
></p
>
6796 <p
>The values between the colons are IDs.
</p
>
6798 <p
><strong
>DMI subtype
</strong
></p
>
6800 <p
>The DMI table contain lots of information about the computer case
6801 and model. This is an entry for a IBM Thinkpad X40, fetched from
6802 /sys/devices/virtual/dmi/id/modalias:
</p
>
6804 <p
><blockquote
>
6805 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6806 </blockquote
></p
>
6808 <p
>The values present are
</p
>
6811 bvn IBM (BIOS vendor)
6812 bvr
1UETB
6WW(
1.66) (BIOS version)
6813 bd
06/
15/
2005 (BIOS date)
6814 svn IBM (system vendor)
6815 pn
2371H4G (product name)
6816 pvr ThinkPadX40 (product version)
6817 rvn IBM (board vendor)
6818 rn
2371H4G (board name)
6819 rvr NotAvailable (board version)
6820 cvn IBM (chassis vendor)
6821 ct
10 (chassis type)
6822 cvr NotAvailable (chassis version)
6825 <p
>The chassis type
10 is Notebook. Other interesting values can be
6826 found in the dmidecode source:
</p
>
6830 4 Low Profile Desktop
6843 17 Main Server Chassis
6844 18 Expansion Chassis
6846 20 Bus Expansion Chassis
6847 21 Peripheral Chassis
6849 23 Rack Mount Chassis
6858 <p
>The chassis type values are not always accurately set in the DMI
6859 table. For example my home server is a tower, but the DMI modalias
6860 claim it is a desktop.
</p
>
6862 <p
><strong
>SerIO subtype
</strong
></p
>
6864 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6865 test machine:
</p
>
6867 <p
><blockquote
>
6868 serio:ty01pr00id00ex00
6869 </blockquote
></p
>
6871 <p
>The values present are
</p
>
6880 <p
>This type is supported by the psmouse driver. I am not sure what
6881 the valid values are.
</p
>
6883 <p
><strong
>Other subtypes
</strong
></p
>
6885 <p
>There are heaps of other modalias subtypes according to
6886 file2alias.c. There is the rest of the list from that source: amba,
6887 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6888 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6889 vmbus, x86cpu and zorro. I did not spend time documenting all of
6890 these, as they do not seem relevant for my intended use with mapping
6891 hardware to packages when new stuff is inserted during run time.
</p
>
6893 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6895 <p
>To check which kernel modules provide support for a given modalias,
6896 one can use the following shell script:
</p
>
6899 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6900 echo
"$id
" ; \
6901 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6905 <p
>The output can look like this (only the first few entries as the
6906 list is very long on my test machine):
</p
>
6910 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6912 FATAL: Module acpi:device: not found.
6914 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6915 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6916 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6917 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6918 acpi:IBM0071:PNP0511:
6919 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6920 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6921 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6925 <p
>If you want to help implementing a system to let us propose what
6926 packages to install when new hardware is plugged into a Debian
6927 machine, please send me an email or talk to me on
6928 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6930 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6931 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6932 in /sys/ with space in them.
</p
>
6937 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6938 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6939 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6940 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6941 <description><p
>As part of my investigation on how to improve the support in Debian
6942 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6943 Launcher and updated the Debian package
6944 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6945 sure udev will fix the device permissions when it is plugged in. I
6946 also added a
"Modaliases
" header to test it in the Debian archive and
6947 hopefully make the package be proposed by jockey in Ubuntu when a user
6948 plug in his rocket launcher. In the process I moved the source to a
6949 git repository under collab-maint, to make it easier for any DD to
6950 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6951 is not very active, but the software still work for me even after five
6952 years of relative silence. The new git repository is not listed in
6953 the uploaded package yet, because I want to test the other changes a
6954 bit more before I upload the new version. If you want to check out
6955 the new version with a .desktop file included, visit the
6956 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6957 view
</a
> or use
"<tt
>git clone
6958 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6963 <title>Lets make hardware dongles easier to use in Debian
</title>
6964 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6965 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6966 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6967 <description><p
>One thing that annoys me with Debian and Linux distributions in
6968 general, is that there is a great package management system with the
6969 ability to automatically install software packages by downloading them
6970 from the distribution mirrors, but no way to get it to automatically
6971 install the packages I need to use the hardware I plug into my
6972 machine. Even if the package to use it is easily available from the
6973 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6974 suggest to automatically install the python-nxt, nbc and t2n packages
6975 I need to talk to it. When I plug in a Yubikey, it could propose the
6976 yubikey-personalization package. The information required to do this
6977 is available, but no-one have pulled all the pieces together.
</p
>
6979 <p
>Some years ago, I proposed to
6980 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6981 the discover subsystem to implement this
</a
>. The idea is fairly
6986 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6987 starting when a user log in.
</li
>
6989 <li
>Set this program up to listen for kernel events emitted when new
6990 hardware is inserted into the computer.
</li
>
6992 <li
>When new hardware is inserted, look up the hardware ID in a
6993 database mapping to packages, and take note of any non-installed
6994 packages.
</li
>
6996 <li
>Show a message to the user proposing to install the discovered
6997 package, and make it easy to install it.
</li
>
7001 <p
>I am not sure what the best way to implement this is, but my
7002 initial idea was to use dbus events to discover new hardware, the
7003 discover database to find packages and
7004 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7007 <p
>Yesterday, I found time to try to implement this idea, and the
7008 draft package is now checked into
7009 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7010 Debian Edu subversion repository
</a
>. In the process, I updated the
7011 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7012 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7013 the relevant packages in Debian, and uploaded a new version
7014 2.2013.01.09 to unstable. I also discovered that the current
7015 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7016 package in Debian no longer discovered any USB devices, because
7017 /proc/bus/usb/devices is no longer present. I ported it to use
7018 libusb as a fall back option to get it working. The fixed package
7019 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7020 because of the freeze).
</p
>
7022 <p
>With this prototype in place, I can insert my Yubikey, and get this
7023 desktop notification to show up (only once, the first time it is
7024 inserted):
</p
>
7026 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7028 <p
>For this prototype to be really useful, some way to automatically
7029 install the proposed packages by pressing the
"Please install
7030 program(s)
" button should to be implemented.
</p
>
7032 <p
>If this idea seem useful to you, and you want to help make it
7033 happen, please help me update the discover-data database with mappings
7034 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7035 list the package you would like to have installed when a given
7036 hardware device is inserted into your computer, and report bugs using
7037 reportbug if it isn
't. Or, if you know of a better way to provide
7038 such mapping, please let me know.
</p
>
7040 <p
>This prototype need more work, and there are several questions that
7041 should be considered before it is ready for production use. Is dbus
7042 the correct way to detect new hardware? At the moment I look for HAL
7043 dbus events on the system bus, because that is the events I could see
7044 on my Debian Squeeze KDE desktop. Are there better events to use?
7045 How should the user be notified? Is the desktop notification
7046 mechanism the best option, or should the background daemon raise a
7047 popup instead? How should packages be installed? When should they
7048 not be installed?
</p
>
7050 <p
>If you want to help getting such feature implemented in Debian,
7051 please send me an email. :)
</p
>
7056 <title>New IRC channel for LEGO designers using Debian
</title>
7057 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7058 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7059 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7060 <description><p
>During Christmas, I have worked a bit on the Debian support for
7061 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7062 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7063 discovered I had to build all the tools myself because none were
7064 already in Debian Squeeze. If Debian support for LEGO is something
7065 you care about, please join me on the IRC channel
7066 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7067 irc.debian.org). There is a lot that could be done to improve the
7068 Debian support for LEGO designers. For example both CAD software
7069 and Mindstorm compilers are missing. :)
</p
>
7071 <p
>Update
2012-
01-
03: A
7072 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7073 including links to Lego related packages is now available.
</p
>
7078 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7079 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7080 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7081 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7082 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7083 year! I hope next year will prove to be a good year.
</p
>
7085 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7086 decentralised
"currency
" that allow people to transfer bitcoins
7087 between each other with minimal overhead, is a very interesting
7088 experiment. And as I wrote a few days ago, the bitcoin situation in
7089 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7090 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7091 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7092 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7093 for one of the ftpmasters to approve the new bitcoin-qt package
7096 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7097 team in Debian, you can easily test the package in Debian Squeeze
7098 using the following steps to get a set of working packages:
</p
>
7100 <blockquote
><pre
>
7101 git clone git://git.debian.org/git/collab-maint/bitcoin
7103 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7104 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7105 </pre
></blockquote
>
7107 <p
>You might have to install some build dependencies as well. The
7108 list of commands should give you two packages, bitcoind and
7109 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7110 client will download the complete set of bitcoin
"blocks
", which need
7111 around
5.6 GiB of data on my machine at the moment. Make sure your
7112 ~/.bitcoin/ directory have lots of spare room if you want to download
7113 all the blocks. The client will warn if the disk is getting full, so
7114 there is not really a problem if you got too little room, but you will
7115 not be able to get all the features out of the client.
</p
>
7117 <p
>As usual, if you use bitcoin and want to show your support of my
7118 activities, please send Bitcoin donations to my address
7119 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7124 <title>A word on bitcoin support in Debian
</title>
7125 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7126 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7127 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7128 <description><p
>It has been a while since I wrote about
7129 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7130 peer-to-peer based crypto-currency, and the reason is simply that I
7131 have been busy elsewhere. But two days ago, I started looking at the
7132 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7133 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7134 is now maintained by a
7135 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7136 people
</a
>, and the grunt work had already been done by this team. We
7137 owe a huge thank you to all these team members. :)
7138 But I was sad to discover that the bitcoin client is missing in
7139 Wheezy. It is only available in Sid (and an outdated client from
7140 backports). The client had several RC bugs registered in BTS blocking
7141 it from entering testing. To try to help the team and improve the
7142 situation, I spent some time providing patches and triaging the bug
7143 reports. I also had a look at the bitcoin package available from Matt
7145 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7146 Ubuntu
</a
>, and moved the useful pieces from that version into the
7147 Debian package.
</p
>
7149 <p
>After checking with the main package maintainer Jonas Smedegaard on
7150 IRC, I pushed several patches into the collab-maint git repository to
7151 improve the package. It now contains fixes for the RC issues (not from
7152 me, but fixed by Scott Howard), build rules for a Qt GUI client
7153 package, konqueror support for the bitcoin: URI and bash completion
7154 setup. As I work on Debian Squeeze, I also created
7155 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7156 patch to backport
</a
> the latest version. Jonas is going to look at
7157 it and try to integrate it into the git repository before uploading a
7158 new version to unstable.
7160 <p
>I would very much like bitcoin to succeed, to get rid of the
7161 centralized control currently exercised in the monetary system. I
7162 find it completely unacceptable that the USA government is collecting
7163 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7164 that the major credit card companies can block legal money
7165 transactions to Wikileaks. But for bitcoin to succeed, more people
7166 need to use bitcoins, and more people need to accept bitcoins when
7167 they sell products and services. Improving the bitcoin support in
7168 Debian is a small step in the right direction, but not enough.
7169 Unfortunately the user experience when browsing the web and wanting to
7170 pay with bitcoin is still not very good. The bitcoin: URI is a step
7171 in the right direction, but need to work in most or every browser in
7172 use. Also the bitcoin-qt client is too heavy to fire up to do a
7173 quick transaction. I believe there are other clients available, but
7174 have not tested them.
</p
>
7177 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7178 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7179 I received
20.15 BTC so far on the address I provided in my blog two
7180 years ago, as can be
7181 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7182 on the blockexplorer service
</a
>. Thank you everyone for your
7183 donation. The blockexplorer service demonstrates quite well that
7184 bitcoin is not quite anonymous and untracked. :) I wonder if the
7185 number of users have gone up since then. If you use bitcoin and want
7186 to show your support of my activity, please send Bitcoin donations to
7187 the same address as last time,
7188 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7193 <title>Git repository for song book for Computer Scientists
</title>
7194 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7195 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7196 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7197 <description><p
>As I
7198 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7199 this summer
</a
>, I have created a Computer Science song book a few
7200 years ago, and today I finally found time to create a public
7201 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7202 repository for the project
</a
>.
</p
>
7204 <p
>If you want to help out, please clone the source and submit patches
7205 to the HTML version. To generate the PDF and PostScript version,
7206 please use prince XML, or let me know about a useful free software
7207 processor capable of creating a good looking PDF from the HTML.
</p
>
7209 <p
>Want to sing? You can still find the song book in HTML, PDF and
7210 PostScript formats at
7211 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7212 Science Songbook
</a
>.
</p
>
7217 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7218 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7219 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7220 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7221 <description><p
>I dag fyller
7222 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7223 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7224 si gratulerer med dagen, Debian!
</p
>
7229 <title>Song book for Computer Scientists
</title>
7230 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7231 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7232 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7233 <description><p
>Many years ago, while studying Computer Science at the
7234 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7235 collecting computer related songs for use at parties. The original
7236 version was written in LaTeX, but a few years ago I got help from
7237 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7238 while keeping the ability to create a nice book in PDF format. I have
7239 not had time to maintain the book for a while now, and guess I should
7240 put it up on some public version control repository where others can
7241 help me extend and update the book. If anyone is volunteering to help
7242 me with this, send me an email. Also let me know if there are songs
7243 missing in my book.
</p
>
7245 <p
>I have not mentioned the book on my blog so far, and it occured to
7246 me today that I really should let all my readers share the joys of
7247 singing out load about programming, computers and computer networks.
7248 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7249 12</a
> is about to start (and I am not going). Want to sing? Check
7250 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7251 Computer Science Songbook
</a
>.
7256 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7257 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7258 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7259 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7260 <description><p
>At work we have heaps of servers. I believe the total count is
7261 around
1000 at the moment. To be able to get help from the vendors
7262 when something go wrong, we want to keep the firmware on the servers
7263 up to date. If the firmware isn
't the latest and greatest, the
7264 vendors typically refuse to start debugging any problems until the
7265 firmware is upgraded. So before every reboot, we want to upgrade the
7266 firmware, and we would really like everyone handling servers at the
7267 university to do this themselves when they plan to reboot a machine.
7268 For that to happen we at the unix server admin group need to provide
7269 the tools to do so.
</p
>
7271 <p
>To make firmware upgrading easier, I am working on a script to
7272 fetch and install the latest firmware for the servers we got. Most of
7273 our hardware are from Dell and HP, so I have focused on these servers
7274 so far. This blog post is about the Dell part.
</P
>
7276 <p
>On the Dell FTP site I was lucky enough to find
7277 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7278 with firmware information for all
11th generation servers, listing
7279 which firmware should be used on a given model and where on the FTP
7280 site I can find it. Using a simple perl XML parser I can then
7281 download the shell scripts Dell provides to do firmware upgrades from
7282 within Linux and reboot when all the firmware is primed and ready to
7283 be activated on the first reboot.
</p
>
7285 <p
>This is the Dell related fragment of the perl code I am working on.
7286 Are there anyone working on similar tools for firmware upgrading all
7287 servers at a site? Please get in touch and lets share resources.
</p
>
7289 <p
><pre
>
7293 use File::Temp qw(tempdir);
7295 # Install needed RHEL packages if missing
7297 'XML::Simple
' =
> 'perl-XML-Simple
',
7299 for my $module (keys %rhelmodules) {
7300 eval
"use $module;
";
7302 my $pkg = $rhelmodules{$module};
7303 system(
"yum install -y $pkg
");
7304 eval
"use $module;
";
7308 my $errorsto =
'pere@hungry.com
';
7314 sub run_firmware_script {
7315 my ($opts, $script) = @_;
7317 print STDERR
"fail: missing script name\n
";
7320 print STDERR
"Running $script\n\n
";
7322 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7323 print STDERR
"success: firmware script ran succcessfully\n
";
7325 print STDERR
"fail: firmware script returned error\n
";
7329 sub run_firmware_scripts {
7330 my ($opts, @dirs) = @_;
7331 # Run firmware packages
7332 for my $dir (@dirs) {
7333 print STDERR
"info: Running scripts in $dir\n
";
7334 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7335 while (my $s = readdir $dh) {
7336 next if $s =~ m/^\.\.?/;
7337 run_firmware_script($opts,
"$dir/$s
");
7345 print STDERR
"info: Downloading $url\n
";
7346 system(
"wget --quiet \
"$url\
"");
7351 my $product = `dmidecode -s system-product-name`;
7354 if ($product =~ m/PowerEdge/) {
7356 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7357 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7359 my $tmpdir = tempdir(
7363 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7364 system(
'gunzip Catalog.xml.gz
');
7365 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7366 # -q is quiet, disabling interactivity and reducing console output
7367 my $fwopts =
"-q
";
7369 for my $url (@paths) {
7370 fetch_dell_fw($url);
7372 run_firmware_scripts($fwopts, $tmpdir);
7374 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7375 print STDERR
"error: Please report to $errorsto.\n
";
7379 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7380 print STDERR
"error: Please report to $errorsto.\n
";
7386 my $url =
"ftp://ftp.us.dell.com/$path
";
7390 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7391 # firmware packages to download from Dell. Only work for Linux
7392 # machines and
11th generation Dell servers.
7393 sub fetch_dell_fw_list {
7394 my $filename = shift;
7396 my $product = `dmidecode -s system-product-name`;
7398 my ($mybrand, $mymodel) = split(/\s+/, $product);
7400 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7402 my $xml = XMLin($filename);
7404 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7405 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7406 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7408 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7409 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7411 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7413 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7415 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7418 for my $component (@{$xml-
>{SoftwareComponent}}) {
7419 my $componenttype = $component-
>{ComponentType}-
>{value};
7421 # Drop application packages, only firmware and BIOS
7422 next if
'APAC
' eq $componenttype;
7424 my $cpath = $component-
>{path};
7425 for my $path (@paths) {
7426 if ($cpath =~ m%/$path$%) {
7427 push(@paths, $cpath);
7435 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7436 it could work on other platforms with some tweaking. Anyone know a
7437 index like Catalog.xml is available from HP for HP servers? At the
7438 moment I maintain a similar list manually and it is quickly getting
7444 <title>How is booting into runlevel
1 different from single user boots?
</title>
7445 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7446 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7447 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7448 <description><p
>Wouter Verhelst have some
7449 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7450 comments and opinions
</a
> on my blog post on
7451 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7452 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7453 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7454 default KDE desktop in Debian
</a
>. I only have time to address one
7455 small piece of his comment now, and though it best to address the
7456 misunderstanding he bring forward:
</p
>
7458 <p
><blockquote
>
7459 Currently, a system admin has four options: [...] boot to a
7460 single-user system (by adding
'single
' to the kernel command line;
7461 this runs rcS and rc1 scripts)
7462 </blockquote
></p
>
7464 <p
>This make me believe Wouter believe booting into single user mode
7465 and booting into runlevel
1 is the same. I am not surprised he
7466 believe this, because it would make sense and is a quite sensible
7467 thing to believe. But because the boot in Debian is slightly broken,
7468 runlevel
1 do not work properly and it isn
't the same as single user
7469 mode. I
'll try to explain what is actually happing, but it is a bit
7470 hard to explain.
</p
>
7472 <p
>Single user mode is defined like this in /etc/inittab:
7473 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7474 executed in single user mode is sulogin. Single user mode is a boot
7475 state
"between
" the runlevels, and when booting into single user mode,
7476 only the scripts in /etc/rcS.d/ are executed before the init process
7477 enters the single user state. When switching to runlevel
1, the state
7478 is in fact not ending in runlevel
1, but it passes through runlevel
1
7479 and end up in the single user mode (see /etc/rc1.d/S03single, which
7480 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7481 1. It is confusing that the
'S
' (single user) init mode is not the
7482 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7485 <p
>This summary might make it clearer. When booting for the first
7486 time into single user mode, the following commands are executed:
7487 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7488 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7489 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7490 trying to continue after visiting single user mode. Not all services
7491 are started again as they should, causing the machine to end up in an
7492 unpredicatble state. This is why Debian admins recommend rebooting
7493 after visiting single user mode.
</p
>
7495 <p
>A similar problem with runlevel
1 is caused by the amount of
7496 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7497 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7498 stopped when passing through the scripts in /etc/rc1.d/, and not
7499 started again when switching away from runlevel
1 to the runlevels
7500 2-
5. I believe the problem is best fixed by moving all the scripts
7501 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7502 functioning single user mode during boot.
</p
>
7504 <p
>I have spent several years investigating the Debian boot system,
7505 and discovered this problem a few years ago. I suspect it originates
7506 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7511 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7512 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7514 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7515 <description><p
>In the Debian boot system, several packages include scripts that
7516 are started from /etc/rcS.d/. In fact, there is a bite more of them
7517 than make sense, and this causes a few problems. What kind of
7518 problems, you might ask. There are at least two problems. The first
7519 is that it is not possible to recover a machine after switching to
7520 runlevel
1. One need to actually reboot to get the machine back to
7521 the expected state. The other is that single user boot will sometimes
7522 run into problems because some of the subsystems are activated before
7523 the root login is presented, causing problems when trying to recover a
7524 machine from a problem in that subsystem. A minor additional point is
7525 that moving more scripts out of rcS.d/ and into the other rc#.d/
7526 directories will increase the amount of scripts that can run in
7527 parallel during boot, and thus decrease the boot time.
</p
>
7529 <p
>So, which scripts should start from rcS.d/. In short, only the
7530 scripts that _have_ to execute before the root login prompt is
7531 presented during a single user boot should go there. Everything else
7532 should go into the numeric runlevels. This means things like
7533 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7534 the numeric runlevels. Today in Debian, there are around
115 init.d
7535 scripts that are started from rcS.d/, and most of them should be moved
7536 out. Do your package have one of them? Please help us make single
7537 user and runlevel
1 better by moving it.
</p
>
7539 <p
>Scripts setting up the screen, keyboard, system partitions
7540 etc. should still be started from rcS.d/, but there is for example no
7541 need to have the network enabled before the single user login prompt
7542 is presented.
</p
>
7544 <p
>As always, things are not so easy to fix as they sound. To keep
7545 Debian systems working while scripts migrate and during upgrades, the
7546 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7547 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7548 and the next ones can only be moved when their dependencies have been
7549 moved first. This migration must be done sequentially while we ensure
7550 that the package system upgrade packages in the right order to keep
7551 the system state correct. This will require some coordination when it
7552 comes to network related packages, but most of the packages with
7553 scripts that should migrate do not have anything in rcS.d/ depending
7554 on them. Some packages have already been updated, like the sudo
7555 package, while others are still left to do. I wish I had time to work
7556 on this myself, but real live constrains make it unlikely that I will
7557 find time to push this forward.
</p
>
7562 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7563 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7564 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7565 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7566 <description><p
>While at Debconf11, I have several times during discussions
7567 mentioned the issues I believe should be improved in Debian for its
7568 desktop to be useful for more people. The use case for this is my
7569 parents, which are currently running Kubuntu which solve the
7572 <p
>I suspect these four missing features are not very hard to
7573 implement. After all, they are present in Ubuntu, so if we wanted to
7574 do this in Debian we would have a source.
</p
>
7578 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7579 are new packages available for upgrades, a icon in the KDE status bar
7580 indicate this, and clicking on it will activate the simple upgrade
7581 tool to handle it. I have no problem guiding both of my parents
7582 through the process over the phone. If a kernel reboot is required,
7583 this too is indicated by the status bars and the upgrade tool. Last
7584 time I checked, nothing with the same features was working in KDE in
7587 <li
><strong
>Simple handling of missing Firefox browser
7588 plugins.
</strong
> When the browser encounter a MIME type it do not
7589 currently have a handler for, it will ask the user if the system
7590 should search for a package that would add support for this MIME type,
7591 and if the user say yes, the APT sources will be searched for packages
7592 advertising the MIME type in their control file (visible in the
7593 Packages file in the APT archive). If one or more packages are found,
7594 it is a simple click of the mouse to add support for the missing mime
7595 type. If the package require the user to accept some non-free
7596 license, this is explained to the user. The entire process make it
7597 more clear to the user why something do not work in the browser, and
7598 make the chances higher for the user to blame the web page authors and
7599 not the browser for any missing features.
</li
>
7601 <li
><strong
>Simple handling of missing multimedia codec/format
7602 handlers.
</strong
> When the media players encounter a format or codec
7603 it is not supporting, a dialog pop up asking the user if the system
7604 should search for a package that would add support for it. This
7605 happen with things like MP3, Windows Media or H
.264. The selection
7606 and installation procedure is very similar to the Firefox browser
7607 plugin handling. This is as far as I know implemented using a
7608 gstreamer hook. The end result is that the user easily get access to
7609 the codecs that are present from the APT archives available, while
7610 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7612 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7613 displaying a text/plain file in my Debian browser, it will propose to
7614 start emacs to show it. If I remember correctly, when doing the same
7615 in Kunbutu it show the file as a text file in the browser. At least I
7616 know Opera will show text files within the browser. I much prefer the
7617 latter behaviour.
</li
>
7621 <p
>There are other nice features as well, like the simplified suite
7622 upgrader, but given that I am the one mostly doing the dist-upgrade,
7623 it do not matter much.
</p
>
7625 <p
>I really hope we could get these features in place for the next
7626 Debian release. It would require the coordinated effort of several
7627 maintainers, but would make the end user experience a lot better.
</p
>
7632 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7633 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7635 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7636 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7637 site is build on Debian/Squeeze, and this platform was chosen because
7638 I am most familiar with Debian (being a Debian Developer for around
10
7639 years) because it is the latest stable Debian release which should get
7640 security support for a few years.
</p
>
7642 <p
>The web service is written in Perl, and depend on some perl modules
7643 that are missing in Debian at the moment. It would be great if these
7644 modules were added to the Debian archive, allowing anyone to set up
7645 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7646 in their own country using only Debian packages. The list of modules
7647 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7648 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7649 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7650 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7651 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7652 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7653 easier in the future.
</p
>
7655 <p
>Thanks to the great tools in Debian, getting the missing modules
7656 installed on my server was a simple call to
'cpan2deb Module::Name
'
7657 and
'dpkg -i
' to install the resulting package. But this leave me
7658 with the responsibility of tracking security problems, which I really
7659 do not have time for.
</p
>
7664 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7665 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7666 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7667 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7668 <description><p
>Here is a small update for my English readers. Most of my blog
7669 posts have been in Norwegian the last few weeks, so here is a short
7670 update in English.
</p
>
7672 <p
>The kids still keep me too busy to get much free software work
7673 done, but I did manage to organise a project to get a Norwegian port
7674 of the British service
7675 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7676 and it has been running for a month now. The entire project has been
7677 organised by me and two others. Around Christmas we gathered sponsors
7678 to fund the development work. In January I drafted a contract with
7679 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7680 and in February the development took place. Most of it involved
7681 converting the source to use GPS coordinates instead of British
7682 easting/northing, and the resulting code should be a lot easier to get
7683 running in any country by now. The Norwegian
7684 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7685 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7686 source and the source for administrative borders in Norway, and
7687 support for this had to be added/fixed.
</p
>
7689 <p
>The Norwegian version went live March
3th, and we spent the weekend
7690 polishing the system before we announced it March
7th. The system is
7691 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7692 problem reports in a few weeks. Soon we hope to announce the Android
7693 and iPhone versions making it even easier to report problems with the
7694 public infrastructure.
</p
>
7696 <p
>Perhaps something to consider for those of you in countries without
7697 such service?
</p
>
7702 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7703 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7704 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7705 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7706 <description><p
>The last few days I have looked at ways to track open security
7707 issues here at my work with the University of Oslo. My idea is that
7708 it should be possible to use the information about security issues
7709 available on the Internet, and check our locally
7710 maintained/distributed software against this information. It should
7711 allow us to verify that no known security issues are forgotten. The
7712 CVE database listing vulnerabilities seem like a great central point,
7713 and by using the package lists from Debian mapped to CVEs provided by
7714 the testing security team, I believed it should be possible to figure
7715 out which security holes were present in our free software
7716 collection.
</p
>
7718 <p
>After reading up on the topic, it became obvious that the first
7719 building block is to be able to name software packages in a unique and
7720 consistent way across data sources. I considered several ways to do
7721 this, for example coming up with my own naming scheme like using URLs
7722 to project home pages or URLs to the Freshmeat entries, or using some
7723 existing naming scheme. And it seem like I am not the first one to
7724 come across this problem, as MITRE already proposed and implemented a
7725 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7726 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7727 software, hardware and other platform components. The CPE ids are
7728 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7729 Vulnerability Database
</a
>, allowing me to look up know security
7730 issues for any CPE name. With this in place, all I need to do is to
7731 locate the CPE id for the software packages we use at the university.
7732 This is fairly trivial (I google for
'cve cpe $package
' and check the
7733 NVD entry if a CVE for the package exist).
</p
>
7735 <p
>To give you an example. The GNU gzip source package have the CPE
7736 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7737 check out, one could look up
7738 <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
7739 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7740 The most recent one is
7741 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7742 and at the bottom of the NVD page for this vulnerability the complete
7743 list of affected versions is provided.
</p
>
7745 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7746 for offline processing of issues. Using this dump, I
've written a
7747 small script taking a list of CPEs as input and list all CVEs
7748 affecting the packages represented by these CPEs. One give it CPEs
7749 with version numbers as specified above and get a list of open
7750 security issues out.
</p
>
7752 <p
>Of course for this approach to be useful, the quality of the NVD
7753 information need to be high. For that to happen, I believe as many as
7754 possible need to use and contribute to the NVD database. I notice
7756 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7757 map from CVE to CPE
</a
>, indicating that they are using the CPE
7758 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7760 <p
>To get an idea about the quality for free software, I spent some
7761 time making it possible to compare the CVE database from Debian with
7762 the CVE database in NVD. The result look fairly good, but there are
7763 some inconsistencies in NVD (same software package having several
7764 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7765 Debian believe are affected by a CVE). Hope to find time to improve
7766 the quality of NVD, but that require being able to get in touch with
7767 someone maintaining it. So far my three emails with questions and
7768 corrections have not seen any reply, but I hope contact can be
7769 established soon.
</p
>
7771 <p
>An interesting application for CPEs is cross platform package
7772 mapping. It would be useful to know which packages in for example
7773 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7774 this would be trivial if all linux distributions provided CPE entries
7775 for their packages.
</p
>
7780 <title>Which module is loaded for a given PCI and USB device?
</title>
7781 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7783 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7784 <description><p
>In the
7785 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7786 package in Debian, there is a script to report useful information
7787 about the running hardware for use when people report missing
7788 information. One part of this script that I find very useful when
7789 debugging hardware problems, is the part mapping loaded kernel module
7790 to the PCI device it claims. It allow me to quickly see if the kernel
7791 module I expect is driving the hardware I am struggling with. To see
7792 the output, make sure discover-data is installed and run
7793 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7794 one of my machines like this:
</p
>
7798 10de:
03eb i2c_nforce2
7801 10de:
03f0 snd_hda_intel
7810 <p
>The code in question look like this, slightly modified for
7811 readability and to drop the output to file descriptor
3:
</p
>
7814 if [ -d /sys/bus/pci/devices/ ] ; then
7815 echo loaded pci modules:
7817 cd /sys/bus/pci/devices/
7818 for address in * ; do
7819 if [ -d
"$address/driver/module
" ] ; then
7820 module=`cd $address/driver/module ; pwd -P | xargs basename`
7821 if grep -q
"^$module
" /proc/modules ; then
7822 address=$(echo $address |sed s/
0000://)
7823 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7824 echo
"$id $module
"
7833 <p
>Similar code could be used to extract USB device module
7837 if [ -d /sys/bus/usb/devices/ ] ; then
7838 echo loaded usb modules:
7840 cd /sys/bus/usb/devices/
7841 for address in * ; do
7842 if [ -d
"$address/driver/module
" ] ; then
7843 module=`cd $address/driver/module ; pwd -P | xargs basename`
7844 if grep -q
"^$module
" /proc/modules ; then
7845 address=$(echo $address |sed s/
0000://)
7846 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7847 if [
"$id
" ] ; then
7848 echo
"$id $module
"
7858 <p
>This might perhaps be something to include in other tools as
7864 <title>How to test if a laptop is working with Linux
</title>
7865 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7866 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7867 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7868 <description><p
>The last few days I have spent at work here at the
<a
7869 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7870 batch of computers will work with Linux. Every year for the last few
7871 years the university have organised shared bid of a few thousand
7872 computers, and this year HP won the bid. Two different desktops and
7873 five different laptops are on the list this year. We in the UNIX
7874 group want to know which one of these computers work well with RHEL
7875 and Ubuntu, the two Linux distributions we currently handle at the
7876 university.
</p
>
7878 <p
>My test method is simple, and I share it here to get feedback and
7879 perhaps inspire others to test hardware as well. To test, I PXE
7880 install the OS version of choice, and log in as my normal user and run
7881 a few applications and plug in selected pieces of hardware. When
7882 something fail, I make a note about this in the test matrix and move
7883 on. If I have some spare time I try to report the bug to the OS
7884 vendor, but as I only have the machines for a short time, I rarely
7885 have the time to do this for all the problems I find.
</p
>
7887 <p
>Anyway, to get to the point of this post. Here is the simple tests
7888 I perform on a new model.
</p
>
7892 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7893 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7894 RHEL5 and Debian Edu/Squeeze.
</li
>
7896 <li
>Is X.org working? If the graphical login screen show up after
7897 installation, X.org is working.
</li
>
7899 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7900 package mesa-utils on Ubuntu) and writing down the frames per second
7901 reported by the program.
</li
>
7903 <li
>Is sound working? With Gnome and KDE, a sound is played when
7904 logging in, and if I can hear this the test is successful. If there
7905 are several audio exits on the machine, I try them all and check if
7906 the Gnome/KDE audio mixer can control where to send the sound. I
7907 normally test this by playing
7908 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7909 video
</a
> in Firefox/Iceweasel.
</li
>
7911 <li
>Is the USB subsystem working? I test this by plugging in a USB
7912 memory stick and see if Gnome/KDE notices this.
</li
>
7914 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7915 I have lying around, and see if Gnome/KDE notices this.
</li
>
7917 <li
>Is any built in camera working? Test using cheese, and see if a
7918 picture from the v4l device show up.
</li
>
7920 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7921 any bluetooth devices are discovered. In my office, I normally see a
7924 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7925 memory modules lying around, and stick them in and see if Gnome/KDE
7926 notice this.
</li
>
7928 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7929 special button work, and if the laptop continue to work after
7932 <li
>For laptops, is the extra buttons working, like audio level,
7933 adjusting background light, switching on/off external video output,
7934 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7935 laptop to laptop, so I just write down which are working and which are
7938 <li
>Some laptops have smart card readers, finger print readers,
7939 acceleration sensors etc. I rarely test these, as I do not know how
7940 to quickly test if they are working or not, so I only document their
7941 existence.
</li
>
7945 <p
>By now I suspect you are really curious what the test results are
7946 for the HP machines I am testing. I
'm not done yet, so I will report
7947 the test results later. For now I can report that HP
8100 Elite work
7948 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7949 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7950 can see, I have most machines left to test. One interesting
7951 observation is that Ubuntu Lucid has almost twice the frame rate than
7952 RHEL6 with glxgears. No idea why.
</p
>
7957 <title>Some thoughts on BitCoins
</title>
7958 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7959 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7960 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7961 <description><p
>As I continue to explore
7962 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7963 what properties the system have, and how it will be affected by laws
7964 and regulations here in Norway. Here are some random notes.
</p
>
7966 <p
>One interesting thing to note is that since the transactions are
7967 verified using a peer to peer network, all details about a transaction
7968 is known to everyone. This means that if a BitCoin address has been
7969 published like I did with mine in my initial post about BitCoin, it is
7970 possible for everyone to see how many BitCoins have been transfered to
7971 that address. There is even a web service to look at the details for
7972 all transactions. There I can see that my address
7973 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7974 have received
16.06 Bitcoin, the
7975 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7976 address of Simon Phipps have received
181.97 BitCoin and the address
7977 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7978 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7979 every one of you that donated bitcoins to support my activity. The
7980 fact that anyone can see how much money was transfered to a given
7981 address make it more obvious why the BitCoin community recommend to
7982 generate and hand out a new address for each transaction. I
'm told
7983 there is no way to track which addresses belong to a given person or
7984 organisation without the person or organisation revealing it
7985 themselves, as Simon, EFF and I have done.
</p
>
7987 <p
>In Norway, and in most other countries, there are laws and
7988 regulations limiting how much money one can transfer across the border
7989 without declaring it. There are money laundering, tax and accounting
7990 laws and regulations I would expect to apply to the use of BitCoin.
7991 If the Skolelinux foundation
7992 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7993 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7994 normal bank transfers like EFF is doing, how should this be accounted?
7995 Given that it is impossible to know if money can cross the border or
7996 not, should everything or nothing be declared? What exchange rate
7997 should be used when calculating taxes? Would receivers have to pay
7998 income tax if the foundation were to pay Skolelinux contributors in
7999 BitCoin? I have no idea, but it would be interesting to know.
</p
>
8001 <p
>For a currency to be useful and successful, it must be trusted and
8002 accepted by a lot of users. It must be possible to get easy access to
8003 the currency (as a wage or using currency exchanges), and it must be
8004 easy to spend it. At the moment BitCoin seem fairly easy to get
8005 access to, but there are very few places to spend it. I am not really
8006 a regular user of any of the vendor types currently accepting BitCoin,
8007 so I wonder when my kind of shop would start accepting BitCoins. I
8008 would like to buy electronics, travels and subway tickets, not herbs
8009 and books. :) The currency is young, and this will improve over time
8010 if it become popular, but I suspect regular banks will start to lobby
8011 to get BitCoin declared illegal if it become popular. I
'm sure they
8012 will claim it is helping fund terrorism and money laundering (which
8013 probably would be true, as is any currency in existence), but I
8014 believe the problems should be solved elsewhere and not by blaming
8015 currencies.
</p
>
8017 <p
>The process of creating new BitCoins is called mining, and it is
8018 CPU intensive process that depend on a bit of luck as well (as one is
8019 competing against all the other miners currently spending CPU cycles
8020 to see which one get the next lump of cash). The
"winner
" get
50
8021 BitCoin when this happen. Yesterday I came across the obvious way to
8022 join forces to increase ones changes of getting at least some coins,
8023 by coordinating the work on mining BitCoins across several machines
8024 and people, and sharing the result if one is lucky and get the
50
8026 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8027 if this sounds interesting. I have not had time to try to set up a
8028 machine to participate there yet, but have seen that running on ones
8029 own for a few days have not yield any BitCoins througth mining
8032 <p
>Update
2010-
12-
15: Found an
<a
8033 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8034 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8035 it was interesting to read. The arguments presented seem to be
8036 equally valid for gold, which was used as a currency for many years.
</p
>
8041 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8042 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8043 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8044 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8045 <description><p
>With this weeks lawless
8046 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8047 attacks
</a
> on Wikileak and
8048 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8049 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8050 not be trusted to handle money transactions.
8052 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8053 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8054 mine mentioned earlier. I decided to follow Simon
's example, and get
8055 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8056 some help from my friend to get it all running, and he even handed me
8057 some bitcoins to get started. I even donated a few bitcoins to Simon
8058 for helping me remember BitCoin.
</p
>
8060 <p
>So, what is bitcoins, you probably wonder? It is a digital
8061 crypto-currency, decentralised and handled using peer-to-peer
8062 networks. It allows anonymous transactions and prohibits central
8063 control over the transactions, making it impossible for governments
8064 and companies alike to block donations and other transactions. The
8065 source is free software, and while the key dependency wxWidgets
2.9
8066 for the graphical user interface is missing in Debian, the command
8067 line client builds just fine. Hopefully Jonas
8068 <a href=
"http://bugs.debian.org/
578157">will get the package into
8069 Debian
</a
> soon.
</p
>
8071 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8072 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8073 bitcoins
</a
> when selling services and goods, and there are even
8074 currency
"stock
" markets where the exchange rate is decided. There
8075 are not many users so far, but the concept seems promising. If you
8076 want to get started and lack a friend with any bitcoins to spare,
8078 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8079 bitcoin at the time of writing). Use
8080 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8081 on the current exchange rates.
</p
>
8083 <p
>As an experiment, I have decided to set up bitcoind on one of my
8084 machines. If you want to support my activity, please send Bitcoin
8085 donations to the address
8086 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8091 <title>Why isn
't Debian Edu using VLC?
</title>
8092 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8093 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8094 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8095 <description><p
>In the latest issue of Linux Journal, the readers choices were
8096 presented, and the winner among the multimedia player were VLC.
8097 Personally, I like VLC, and it is my player of choice when I first try
8098 to play a video file or stream. Only if VLC fail will I drag out
8099 gmplayer to see if it can do better. The reason is mostly the failure
8100 model and trust. When VLC fail, it normally pop up a error message
8101 reporting the problem. When mplayer fail, it normally segfault or
8102 just hangs. The latter failure mode drain my trust in the program.
<p
>
8104 <p
>But even if VLC is my player of choice, we have choosen to use
8105 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8106 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8107 plugin to play web videos seamlessly, and the VLC browser plugin is
8108 not very good. For example, it lack in-line control buttons, so there
8109 is no way for the user to pause the video. Also, when I
8110 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8111 tested the browser plugins
</a
> available in Debian, the VLC plugin
8112 failed on several video pages where mplayer based plugins worked. If
8113 the browser plugin for VLC was as good as the gecko-mediaplayer
8114 package (which uses mplayer), we would switch.
</P
>
8116 <p
>While VLC is a good player, its user interface is slightly
8117 annoying. The most annoying feature is its inconsistent use of
8118 keyboard shortcuts. When the player is in full screen mode, its
8119 shortcuts are different from when it is playing the video in a window.
8120 For example, space only work as pause when in full screen mode. I
8121 wish it had consisten shortcuts and that space also would work when in
8122 window mode. Another nice shortcut in gmplayer is [enter] to restart
8123 the current video. It is very nice when playing short videos from the
8124 web and want to restart it when new people arrive to have a look at
8125 what is going on.
</p
>
8130 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8131 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8132 <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>
8133 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8134 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8135 upgrade testing of the
8136 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8137 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8138 This seem like a very good idea, so I adjusted by test scripts and
8139 can now present the updated result from today:
</p
>
8141 <p
>This is for Gnome:
</p
>
8143 <p
>Installed using apt-get, missing with aptitude
</p
>
8145 <blockquote
><p
>
8150 browser-plugin-gnash
8157 freedesktop-sound-theme
8159 gconf-defaults-service
8174 gnome-desktop-environment
8178 gnome-session-canberra
8183 gstreamer0.10-fluendo-mp3
8189 libapache2-mod-dnssd
8192 libaprutil1-dbd-sqlite3
8195 libboost-date-time1.42
.0
8196 libboost-python1.42
.0
8197 libboost-thread1.42
.0
8199 libchamplain-gtk-
0.4-
0
8201 libclutter-gtk-
0.10-
0
8208 libfreerdp-plugins-standard
8223 libgnomepanel2.24-cil
8228 libgtksourceview2.0-common
8229 libmono-addins-gui0.2-cil
8230 libmono-addins0.2-cil
8231 libmono-cairo2.0-cil
8232 libmono-corlib2.0-cil
8233 libmono-i18n-west2.0-cil
8234 libmono-posix2.0-cil
8235 libmono-security2.0-cil
8236 libmono-sharpzip2.84-cil
8237 libmono-system2.0-cil
8240 libndesk-dbus-glib1.0-cil
8241 libndesk-dbus1.0-cil
8251 libtelepathy-farsight0
8260 nautilus-sendto-empathy
8264 python-aptdaemon-gtk
8266 python-beautifulsoup
8281 python-gtksourceview2
8292 python-pkg-resources
8299 python-twisted-conch
8305 python-zope.interface
8310 rhythmbox-plugin-cdrecorder
8317 system-config-printer-udev
8319 telepathy-mission-control-
5
8330 </p
></blockquote
>
8332 <p
>Installed using apt-get, removed with aptitude
</p
>
8334 <blockquote
><p
>
8340 fast-user-switch-applet
8359 libgtksourceview2.0-
0
8361 libsdl1.2debian-alsa
8367 system-config-printer
8372 </p
></blockquote
>
8374 <p
>Installed using aptitude, missing with apt-get
</p
>
8376 <blockquote
><p
>
8377 gstreamer0.10-gnomevfs
8378 </p
></blockquote
>
8380 <p
>Installed using aptitude, removed with apt-get
</p
>
8382 <blockquote
><p
>
8384 </p
></blockquote
>
8386 <p
>This is for KDE:
</p
>
8388 <p
>Installed using apt-get, missing with aptitude
</p
>
8390 <blockquote
><p
>
8392 </p
></blockquote
>
8394 <p
>Installed using apt-get, removed with aptitude
</p
>
8396 <blockquote
><p
>
8399 </p
></blockquote
>
8401 <p
>Installed using aptitude, missing with apt-get
</p
>
8403 <blockquote
><p
>
8417 kdeartwork-emoticons
8419 kdeartwork-theme-icon
8423 kdebase-workspace-bin
8424 kdebase-workspace-data
8438 kscreensaver-xsavers
8453 plasma-dataengines-workspace
8455 plasma-desktopthemes-artwork
8456 plasma-runners-addons
8457 plasma-scriptengine-googlegadgets
8458 plasma-scriptengine-python
8459 plasma-scriptengine-qedje
8460 plasma-scriptengine-ruby
8461 plasma-scriptengine-webkit
8462 plasma-scriptengines
8463 plasma-wallpapers-addons
8464 plasma-widget-folderview
8465 plasma-widget-networkmanagement
8469 xscreensaver-data-extra
8471 xscreensaver-gl-extra
8472 xscreensaver-screensaver-bsod
8473 </p
></blockquote
>
8475 <p
>Installed using aptitude, removed with apt-get
</p
>
8477 <blockquote
><p
>
8479 google-gadgets-common
8497 libggadget-qt-
1.0-
0b
8502 libkonqsidebarplugin4a
8511 libplasma-geolocation-interface4
8513 libplasmagenericshell4
8527 libsmokeknewstuff2-
3
8528 libsmokeknewstuff3-
3
8530 libsmokektexteditor3
8538 libsmokeqtnetwork4-
3
8544 libsmokeqtuitools4-
3
8556 plasma-dataengines-addons
8557 plasma-scriptengine-superkaramba
8558 plasma-widget-lancelot
8559 plasma-widgets-addons
8560 plasma-widgets-workspace
8564 update-notifier-common
8565 </p
></blockquote
>
8567 <p
>Running apt-get autoremove made the results using apt-get and
8568 aptitude a bit more similar, but there are still quite a lott of
8569 differences. I have no idea what packages should be installed after
8570 the upgrade, but hope those that do can have a look.
</p
>
8575 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8576 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8577 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8578 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8579 <description><p
>Most of the computers in use by the
8580 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8581 are virtual machines. And they have been Xen machines running on a
8582 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8583 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8584 bit harder that it could have been, because we set up the Xen virtual
8585 machines to get the virtual partitions from LVM, which as far as I
8586 know is not supported by KVM. So to migrate, we had to convert
8587 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8590 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8591 nice recipe
</a
> to do this, and wrote the following script to do the
8592 migration. It uses qemu-img from the qemu package to make the disk
8593 image, parted to partition it, losetup and kpartx to present the disk
8594 image partions as devices, and dd to copy the data. I NFS mounted the
8595 new servers storage area on the old server to do the migration.
</p
>
8601 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8606 if [ -z
"$
1" ] ; then
8607 echo
"Usage: $
0 &lt;hostname
&gt;
"
8613 if [ ! -e /dev/vg_data/$host-disk ] ; then
8614 echo
"error: unable to find LVM volume for $host
"
8618 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8619 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8620 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8621 totalsize=$(( ( $disksize + $swapsize ) ))
8624 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8625 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8627 parted $img mklabel msdos
8628 parted $img mkpart primary linux-swap
0 $disksize
8629 parted $img mkpart primary ext2 $disksize $totalsize
8630 parted $img set
1 boot on
8633 losetup /dev/loop0 $img
8634 kpartx -a /dev/loop0
8636 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8637 fsck.ext3 -f /dev/mapper/loop0p1 || true
8638 mkswap /dev/mapper/loop0p2
8640 kpartx -d /dev/loop0
8641 losetup -d /dev/loop0
8644 <p
>The script is perhaps so simple that it is not copyrightable, but
8645 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8647 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8648 the new disk image attached, installed grub-pc and linux-image-
686 and
8649 set up grub to boot from the disk image. After this, the KVM machines
8650 seem to work just fine.
</p
>
8655 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8656 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8657 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8658 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8659 <description><p
>I
'm still running upgrade testing of the
8660 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8661 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8662 status. Here is a short update based on a test I ran
20101118.
</p
>
8664 <p
>I still do not know what a correct migration should look like, so I
8665 report any differences between apt and aptitude and hope someone else
8666 can see if anything should be changed.
</p
>
8668 <p
>This is for Gnome:
</p
>
8670 <p
>Installed using apt-get, missing with aptitude
</p
>
8672 <blockquote
><p
>
8673 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8674 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8675 dmz-cursor-theme empathy empathy-common finger
8676 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8677 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8678 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8679 gnome-cards-data gnome-codec-install gnome-core
8680 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8681 gnome-search-tool gnome-session-canberra gnome-spell
8682 gnome-system-log gnome-themes-extras gnome-themes-more
8683 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8684 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8685 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8686 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8687 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8688 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8689 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8690 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8691 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8692 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8693 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8694 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8695 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8696 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8697 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8698 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8699 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8700 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8701 libmono-security2.0-cil libmono-sharpzip2.84-cil
8702 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8703 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8704 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8705 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8706 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8707 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8708 libxalan2-java libxerces2-java media-player-info mesa-utils
8709 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8710 nautilus-sendto-empathy openoffice.org-writer2latex
8711 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8712 python-aptdaemon python-aptdaemon-gtk python-axiom
8713 python-beautifulsoup python-bugbuddy python-clientform
8714 python-coherence python-configobj python-crypto python-cupshelpers
8715 python-cupsutils python-eggtrayicon python-elementtree
8716 python-epsilon python-evolution python-feedparser python-gdata
8717 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8718 python-gtksourceview2 python-httplib2 python-louie python-mako
8719 python-markupsafe python-mechanize python-nevow python-notify
8720 python-opengl python-openssl python-pam python-pkg-resources
8721 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8722 python-tagpy python-twisted-bin python-twisted-conch
8723 python-twisted-core python-twisted-web python-utidylib python-webkit
8724 python-xdg python-zope.interface remmina remmina-plugin-data
8725 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8726 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8727 software-center svgalibg1 system-config-printer-udev
8728 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8729 totem totem-coherence totem-mozilla totem-plugins
8730 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8732 </p
></blockquote
>
8734 Installed using apt-get, removed with aptitude
8736 <blockquote
><p
>
8737 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8738 epiphany-extensions epiphany-gecko evolution-exchange
8739 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8740 gedit-common gnome-app-install gnome-games gnome-games-data
8741 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8742 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8743 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8744 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8745 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8746 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8747 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8748 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8749 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8750 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8751 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8752 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8753 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8754 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8755 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8756 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8757 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8758 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8759 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8760 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8761 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8762 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8763 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8764 sound-juicer swfdec-gnome system-config-printer totem-common
8765 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8766 </p
></blockquote
>
8768 <p
>Installed using aptitude, missing with apt-get
</p
>
8770 <blockquote
><p
>
8771 gstreamer0.10-gnomevfs
8772 </p
></blockquote
>
8774 <p
>Installed using aptitude, removed with apt-get
</p
>
8776 <blockquote
><p
>
8778 </p
></blockquote
>
8780 <p
>This is for KDE:
</p
>
8782 <p
>Installed using apt-get, missing with aptitude
</p
>
8784 <blockquote
><p
>
8785 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8786 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8787 ghostscript-x git gnome-audio gnugo granatier gs-common
8788 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8789 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8790 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8791 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8792 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8793 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8794 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8795 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8796 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8797 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8798 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8799 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8800 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8801 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8802 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8803 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8804 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8805 libkrossui4 libmailtools-perl libmime-tools-perl
8806 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8807 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8808 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8809 lirc luatex marble networkstatus noatun-plugins
8810 openoffice.org-writer2latex palapeli palapeli-data parley
8811 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8812 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8813 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8815 </p
></blockquote
>
8817 <p
>Installed using apt-get, removed with aptitude
</p
>
8819 <blockquote
><p
>
8820 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8821 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8822 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8823 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8824 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8825 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8826 kitchensync kiten kjumpingcube klatin klettres klickety klines
8827 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8828 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8829 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8830 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8831 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8832 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8833 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8834 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8835 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8836 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8837 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8838 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8839 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8840 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8841 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8842 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8843 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8844 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8845 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8846 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8847 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8848 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8849 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8850 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8851 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8852 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8853 </p
></blockquote
>
8855 <p
>Installed using aptitude, missing with apt-get
</p
>
8857 <blockquote
><p
>
8858 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8859 kdeartwork kdebase kdebase-apps kdebase-workspace
8860 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8861 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8862 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8863 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8864 xscreensaver-screensaver-bsod
8865 </p
></blockquote
>
8867 <p
>Installed using aptitude, removed with apt-get
</p
>
8869 <blockquote
><p
>
8870 kdebase-bin konq-plugins konqueror
8871 </p
></blockquote
>
8876 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8877 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8879 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8880 <description><p
>Answering
8881 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8882 call from the Gnash project
</a
> for
8883 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8884 current source, I have set up a virtual KVM machine on the Debian
8885 Edu/Skolelinux virtualization host to test the git source on
8886 Debian/Squeeze. I hope this can help the developers in getting new
8887 releases out more often.
</p
>
8889 <p
>As the developers want less main-stream build platforms tested to,
8890 I have considered setting up a
<a
8891 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8892 machine as well. I have also considered using the kfreebsd
8893 architecture in Debian as a file server in NUUG to get access to the
5
8894 TB zfs volume we currently use to store DV video. Because of this, I
8895 finally got around to do a test installation of Debian/Squeeze with
8896 kfreebsd. Installation went fairly smooth, thought I noticed some
8897 visual glitches in the cdebconf dialogs (black cursor left on the
8898 screen at random locations). Have not gotten very far with the
8899 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8900 fatal problem. Have to spend some more time on it to see if it is
8901 useful as a file server for NUUG. Will try to find time to set up a
8902 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8907 <title>Debian in
3D
</title>
8908 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8909 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8910 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8911 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8913 <p
>3D printing is just great. I just came across this Debian logo in
8915 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8916 thingiverse blog
</a
>.
</p
>
8921 <title>Software updates
2010-
10-
24</title>
8922 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8924 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8925 <description><p
>Some updates.
</p
>
8927 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8928 raise money for the project is going well. The lower limit of
10
8929 signers was reached in
24 hours, and so far
13 people have signed it.
8930 More signers and more funding is most welcome, and I am really curious
8931 how far we can get before the time limit of December
24 is reached.
8934 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8935 about what appear to be a great code coverage tool capable of
8936 generating code coverage stats without any changes to the source code.
8938 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8939 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8940 It is missing in Debian, but the git source built just fine in Squeeze
8941 after I installed libelf-dev, libdwarf-dev, pkg-config and
8942 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8943 solvable. I hope kcov make it into Debian soon.
</p
>
8945 <p
>Finally found time to wrap up the release notes for
<a
8946 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8947 new alpha release of Debian Edu
</a
>, and just published the second
8948 alpha test release of the Squeeze based Debian Edu /
8949 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8950 release. Give it a try if you need a complete linux solution for your
8951 school, including central infrastructure server, workstations, thin
8952 client servers and diskless workstations. A nice touch added
8953 yesterday is RDP support on the thin client servers, for windows
8954 clients to get a Linux desktop on request.
</p
>
8959 <title>Some notes on Flash in Debian and Debian Edu
</title>
8960 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8961 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8962 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8963 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8964 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8965 second most popular used package that is missing in Debian. The sixth
8966 most popular is flashplayer-mozilla. This is a clear indication that
8967 working flash is important for Debian users. Around
10 percent of the
8968 users submitting data to popcon.debian.org have this package
8969 installed.
</p
>
8971 <p
>In the report written by Lars Risan in August
2008
8972 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8973 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8974 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8975 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8976 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8977 web sites require Flash to work, and lacking working Flash support in
8978 the web browser and the problems with installing it was perceived as a
8979 good reason to stay with Windows.
</p
>
8981 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8982 said to be the retarded cousin that did not really understand
8983 everything you told him but could work fairly well. This was a
8984 comment regarding the problems Linux have with proprietary formats and
8985 non-standard web pages, and is sad because it exposes a fairly common
8986 understanding of whose fault it is if web pages that only work in for
8987 example Internet Explorer
6 fail to work on Firefox, and funny because
8988 it explain very well how annoying it is for users when Linux
8989 distributions do not work with the documents they receive or the web
8990 pages they want to visit.
</p
>
8992 <p
>This is part of the reason why I believe it is important for Debian
8993 and Debian Edu to have a well working Flash implementation in the
8994 distribution, to get at least popular sites as Youtube and Google
8995 Video to working out of the box. For Squeeze, Debian have the chance
8996 to include the latest version of Gnash that will make this happen, as
8997 the new release
0.8.8 was published a few weeks ago and is resting in
8998 unstable. The new version work with more sites that version
0.8.7.
8999 The Gnash maintainers have asked for a freeze exception, but the
9000 release team have not had time to reply to it yet. I hope they agree
9001 with me that Flash is important for the Debian desktop users, and thus
9002 accept the new package into Squeeze.
</p
>
9007 <title>Circular package dependencies harms apt recovery
</title>
9008 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9009 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9010 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9011 <description><p
>I discovered this while doing
9012 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9013 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9014 in Debian still got circular dependencies, and it is often claimed
9015 that apt and aptitude should be able to handle this just fine, but
9016 some times these dependency loops causes apt to fail.
</p
>
9018 <p
>An example is from todays
9019 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9020 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9021 causes perl-modules to fail to upgrade. The cause is simple. If a
9022 package fail to unpack, then only part of packages with the circular
9023 dependency might end up being unpacked when unpacking aborts, and the
9024 ones already unpacked will fail to configure in the recovery phase
9025 because its dependencies are unavailable.
</p
>
9027 <p
>In this log, the problem manifest itself with this error:
</p
>
9029 <blockquote
><pre
>
9030 dpkg: dependency problems prevent configuration of perl-modules:
9031 perl-modules depends on perl (
>=
5.10.1-
1); however:
9032 Version of perl on system is
5.10.0-
19lenny
2.
9033 dpkg: error processing perl-modules (--configure):
9034 dependency problems - leaving unconfigured
9035 </pre
></blockquote
>
9037 <p
>The perl/perl-modules circular dependency is already
9038 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9039 hopefully be solved as soon as possible, but it is not the only one,
9040 and each one of these loops in the dependency tree can cause similar
9041 failures. Of course, they only occur when there are bugs in other
9042 packages causing the unpacking to fail, but it is rather nasty when
9043 the failure of one package causes the problem to become worse because
9044 of dependency loops.
</p
>
9047 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9048 tireless effort by Bill Allombert
</a
>, the number of circular
9050 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9051 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9053 <p
>Todays testing also exposed a bug in
9054 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9055 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9056 apt-get and aptitude, the latter possibly caused by some circular
9057 dependency. Reported both to BTS to try to get someone to look at
9063 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9064 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9065 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9066 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9067 <description><p
>This is a
9068 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9070 <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
9072 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9073 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9075 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9076 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9077 and dhcp3-server-ldap in Debian use the LDAP server. The two
9078 implementations are quite different in how they use LDAP.
</p
>
9080 To get this information, I started slapd with debugging enabled and
9081 dumped the debug output to a file to get the LDAP searches performed
9082 on a Debian Edu main-server. Here is a summary.
9084 <p
><strong
>powerdns
</strong
></p
>
9086 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9087 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9090 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9091 One
"strict
" mode where the forward and reverse DNS lookups are done
9092 using the same LDAP objects, and a
"tree
" mode where the forward and
9093 reverse entries are in two different subtrees in LDAP with a structure
9094 based on the DNS names, as in tjener.intern and
9095 2.2.0.10.in-addr.arpa.
</p
>
9097 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9098 base, and uses a
"base
" scoped search for the DNS name by adding
9099 "dc=tjener,dc=intern,
" to the base with a filter for
9100 "(associateddomain=tjener.intern)
" for the forward entry and
9101 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9102 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9103 forward entries, it is looking for attributes named dnsttl, arecord,
9104 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9105 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9106 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9107 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9108 spfrecord and modifytimestamp. For reverse entries it is looking for
9109 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9110 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9111 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9112 ldapsearch commands could look like this:
</p
>
9114 <blockquote
><pre
>
9115 ldapsearch -h ldap \
9116 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9117 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9118 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9119 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9120 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9121 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9123 ldapsearch -h ldap \
9124 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9125 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9126 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9127 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9128 srvrecord naptrrecord modifytimestamp
9129 </pre
></blockquote
>
9131 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9132 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9133 example LDAP objects used there. In addition to these objects, the
9134 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9135 also exist.
</p
>
9137 <blockquote
><pre
>
9138 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9140 objectclass: dnsdomain
9141 objectclass: domainrelatedobject
9144 associateddomain: tjener.intern
9146 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9148 objectclass: dnsdomain2
9149 objectclass: domainrelatedobject
9151 ptrrecord: tjener.intern
9152 associateddomain:
2.2.0.10.in-addr.arpa
9153 </pre
></blockquote
>
9155 <p
>In strict mode, the server behaves differently. When looking for
9156 forward DNS entries, it is doing a
"subtree
" scoped search with the
9157 same base as in the tree mode for a object with filter
9158 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9159 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9160 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9161 naptrrecord and modifytimestamp. For reverse entires it also do a
9162 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9163 and the requested attributes are associateddomain, dnsttl and
9164 modifytimestamp. In short, in strict mode the objects with ptrrecord
9165 go away, and the arecord attribute in the forward object is used
9168 <p
>The forward and reverse searches can be simulated using ldapsearch
9169 like this:
</p
>
9171 <blockquote
><pre
>
9172 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9173 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9174 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9175 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9176 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9177 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9179 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9180 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9181 </pre
></blockquote
>
9183 <p
>In addition to the forward and reverse searches , there is also a
9184 search for SOA records, which behave similar to the forward and
9185 reverse lookups.
</p
>
9187 <p
>A thing to note with the PowerDNS behaviour is that it do not
9188 specify any objectclass names, and instead look for the attributes it
9189 need to generate a DNS reply. This make it able to work with any
9190 objectclass that provide the needed attributes.
</p
>
9192 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9193 dnsdomain2 schemas. The latter is used for reverse entries like
9194 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9196 <p
>In Debian Edu, we have created DNS objects using the object classes
9197 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9198 attributes) and domainrelatedobject (for associatedDomain). The use
9199 of structural object classes make it impossible to combine these
9200 classes with the object classes used by DHCP.
</p
>
9202 <p
>There are other schemas that could be used too, for example the
9203 dnszone structural object class used by Gosa and bind-sdb for the DNS
9204 attributes combined with the domainrelatedobject object class, but in
9205 this case some unused attributes would have to be included as well
9206 (zonename and relativedomainname).
</p
>
9208 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9209 mode and not use any of the existing objectclasses (dnsdomain,
9210 dnsdomain2 and dnszone) when one want to combine the DNS information
9211 with DHCP information, and instead create a auxiliary object class
9212 defined something like this (using the attributes defined for
9213 dnsdomain and dnsdomain2 or dnszone):
</p
>
9215 <blockquote
><pre
>
9216 objectclass ( some-oid NAME
'dnsDomainAux
'
9219 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9220 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9221 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9222 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9223 A6Record $ DNAMERecord
9225 </pre
></blockquote
>
9227 <p
>This will allow any object to become a DNS entry when combined with
9228 the domainrelatedobject object class, and allow any entity to include
9229 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9230 developers asking for their view on this schema and if they are
9231 interested in providing such schema with PowerDNS, and I hope my
9232 message will be accepted into their mailing list soon.
</p
>
9234 <p
><strong
>ISC dhcp
</strong
></p
>
9236 <p
>The DHCP server searches for specific objectclass and requests all
9237 the object attributes, and then uses the attributes it want. This
9238 make it harder to figure out exactly what attributes are used, but
9239 thanks to the working example in Debian Edu I can at least get an idea
9240 what is needed without having to read the source code.
</p
>
9242 <p
>In the DHCP server configuration, the LDAP base to use and the
9243 search filter to use to locate the correct dhcpServer entity is
9244 stored. These are the relevant entries from
9245 /etc/dhcp3/dhcpd.conf:
</p
>
9247 <blockquote
><pre
>
9248 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9249 ldap-dhcp-server-cn
"dhcp
";
9250 </pre
></blockquote
>
9252 <p
>The DHCP server uses this information to nest all the DHCP
9253 configuration it need. The cn
"dhcp
" is located using the given LDAP
9254 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9255 search result is this entry:
</p
>
9257 <blockquote
><pre
>
9258 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9261 objectClass: dhcpServer
9262 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9263 </pre
></blockquote
>
9265 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9266 subtree with DHCP configuration. The DHCP configuration subtree base
9267 is located using a base scope search with base
"cn=DHCP
9268 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9269 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9270 The search result is this entry:
</p
>
9272 <blockquote
><pre
>
9273 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9276 objectClass: dhcpService
9277 objectClass: dhcpOptions
9278 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9279 dhcpStatements: ddns-update-style none
9280 dhcpStatements: authoritative
9281 dhcpOption: smtp-server code
69 = array of ip-address
9282 dhcpOption: www-server code
72 = array of ip-address
9283 dhcpOption: wpad-url code
252 = text
9284 </pre
></blockquote
>
9286 <p
>Next, the entire subtree is processed, one level at the time. When
9287 all the DHCP configuration is loaded, it is ready to receive requests.
9288 The subtree in Debian Edu contain objects with object classes
9289 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9290 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9291 and information about netmasks, dynamic range etc. Leaving out the
9292 details here because it is not relevant for the focus of my
9293 investigation, which is to see if it is possible to merge dns and dhcp
9294 related computer objects.
</p
>
9296 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9297 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9298 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9299 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9300 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9303 <blockquote
><pre
>
9304 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9307 objectClass: dhcpHost
9308 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9309 dhcpStatements: fixed-address hostname
9310 </pre
></blockquote
>
9312 <p
>There is less flexiblity in the way LDAP searches are done here.
9313 The object classes need to have fixed names, and the configuration
9314 need to be stored in a fairly specific LDAP structure. On the
9315 positive side, the invidiual dhcpHost entires can be anywhere without
9316 the DN pointed to by the dhcpServer entries. The latter should make
9317 it possible to group all host entries in a subtree next to the
9318 configuration entries, and this subtree can also be shared with the
9319 DNS server if the schema proposed above is combined with the dhcpHost
9320 structural object class.
9322 <p
><strong
>Conclusion
</strong
></p
>
9324 <p
>The PowerDNS implementation seem to be very flexible when it come
9325 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9326 come to the the LDAP structure, the
"strict
" mode is very flexible,
9327 allowing DNS objects to be stored anywhere under the base cn specified
9328 in the configuration.
</p
>
9330 <p
>The DHCP implementation on the other hand is very inflexible, both
9331 regarding which LDAP schemas to use and which LDAP structure to use.
9332 I guess one could implement ones own schema, as long as the
9333 objectclasses and attributes have the names used, but this do not
9334 really help when the DHCP subtree need to have a fairly fixed
9335 structure.
</p
>
9337 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9338 this might work for Debian Edu:
</p
>
9340 <blockquote
><pre
>
9342 cn=machine-info (dhcpService) - dhcpServiceDN points here
9343 cn=dhcp (dhcpServer)
9344 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9345 cn=
10.0.2.0 (dhcpSubnet)
9346 cn=group1 (dhcpGroup/dhcpOptions)
9347 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9348 cn=
192.168.0.0 (dhcpSubnet)
9349 cn=group1 (dhcpGroup/dhcpOptions)
9350 ou=machines - PowerDNS base points here
9351 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9352 </pre
></blockquote
>
9354 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9355 entries to be in the dhcpGroup subtrees, the entries can be stored
9356 there instead of a common machines subtree, and the PowerDNS base
9357 would have to be moved one level up to the machine-info subtree.
</p
>
9359 <p
>The combined object under the machines subtree would look something
9360 like this:
</p
>
9362 <blockquote
><pre
>
9363 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9366 objectClass: dhcpHost
9367 objectclass: domainrelatedobject
9368 objectclass: dnsDomainAux
9369 associateddomain: hostname.intern
9370 arecord:
10.11.12.13
9371 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9372 dhcpStatements: fixed-address hostname.intern
9373 </pre
></blockquote
>
9375 </p
>One could even add the LTSP configuration associated with a given
9376 machine, as long as the required attributes are available in a
9377 auxiliary object class.
</p
>
9382 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9383 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9384 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9385 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9386 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9387 DHCP services in Debian Edu to use the same LDAP objects for a given
9388 computer, to avoid the possibility of having a inconsistent state for
9389 a computer in LDAP (as in DHCP but no DNS entry or the other way
9390 around) and make it easier to add computers to LDAP.
</p
>
9392 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9393 information finally found a solution that seem to work.
</p
>
9395 <p
>The old setup required three LDAP objects for a given computer.
9396 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9397 we switch powerdns to use its strict LDAP method (ldap-method=strict
9398 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9399 merged into one while making it impossible to transfer the reverse map
9400 to a slave DNS server.
</p
>
9402 <p
>If we also replace the object class used to get the DNS related
9403 attributes to one allowing these attributes to be combined with the
9404 dhcphost object class, we can merge the DNS and DHCP entries into one.
9405 I
've written such object class in the dnsdomainaux.schema file (need
9406 proper OIDs, but that is a minor issue), and tested the setup. It
9407 seem to work.
</p
>
9409 <p
>With this test setup in place, we can get away with one LDAP object
9410 for both DNS and DHCP, and even the LTSP configuration I suggested in
9411 an earlier email. The combined LDAP object will look something like
9414 <blockquote
><pre
>
9415 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9417 objectClass: dhcphost
9418 objectclass: domainrelatedobject
9419 objectclass: dnsdomainaux
9420 associateddomain: hostname.intern
9421 arecord:
10.11.12.13
9422 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9423 dhcpstatements: fixed-address hostname
9425 </pre
></blockquote
>
9427 <p
>The DNS server uses the associateddomain and arecord entries, while
9428 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9429 before asking DNS to resolve the fixed-adddress. LTSP will use
9430 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9432 <p
>I am not yet sure if I can get the DHCP server to look for its
9433 dhcphost in a different location, to allow us to put the objects
9434 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9435 that. If I can
't figure out a way to do that, we can still get rid of
9436 the hosts subtree and move all its content into the DHCP Config tree
9437 (which probably should be renamed to be more related to the new
9438 content. I suspect cn=dnsdhcp,ou=services or something like that
9439 might be a good place to put it.
</p
>
9441 <p
>If you want to help out with implementing this for Debian Edu,
9442 please contact us on debian-edu@lists.debian.org.
</p
>
9447 <title>Idea for storing LTSP configuration in LDAP
</title>
9448 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9449 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9450 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9451 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9452 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9453 clients, and that this can be used to fetch configuration from LDAP if
9454 Debian Edu choose to store configuration there.
</p
>
9456 <p
>Armed with this information, I got inspired and wrote a test module
9457 to get configuration from LDAP. The idea is to look up the MAC
9458 address of the client in LDAP, and look for attributes on the form
9459 ltspconfigsetting=value, and use this to export SETTING=value to the
9460 LTSP clients.
</p
>
9462 <p
>The goal is to be able to store the LTSP configuration attributes
9463 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9464 allowing us to store all information about a computer in one place.
</p
>
9466 <p
>This is a untested draft implementation, and I welcome feedback on
9467 this approach. A real LDAP schema for the ltspClientAux objectclass
9468 need to be written. Comments, suggestions, etc?
</p
>
9470 <blockquote
><pre
>
9471 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9473 # Fetch LTSP client settings from LDAP based on MAC address
9475 # Uses ethernet address as stored in the dhcpHost objectclass using
9476 # the dhcpHWAddress attribute or ethernet address stored in the
9477 # ieee802Device objectclass with the macAddress attribute.
9479 # This module is written to be schema agnostic, and only depend on the
9480 # existence of attribute names.
9482 # The LTSP configuration variables are saved directly using a
9483 # ltspConfig prefix and uppercasing the rest of the attribute name.
9484 # To set the SERVER variable, set the ltspConfigServer attribute.
9486 # Some LDAP schema should be created with all the relevant
9487 # configuration settings. Something like this should work:
9489 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9492 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9494 LDAPSERVER=$(debian-edu-ldapserver)
9495 if [
"$LDAPSERVER
" ] ; then
9496 LDAPBASE=$(debian-edu-ldapserver -b)
9497 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9498 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9499 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9500 grep
'^ltspConfig
' | while read attr value ; do
9501 # Remove prefix and convert to upper case
9502 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9503 # bass value on to clients
9504 eval
"$attr=$value; export $attr
"
9508 </pre
></blockquote
>
9510 <p
>I
'm not sure this shell construction will work, because I suspect
9511 the while block might end up in a subshell causing the variables set
9512 there to not show up in ltsp-config, but if that is the case I am sure
9513 the code can be restructured to make sure the variables are passed on.
9514 I expect that can be solved with some testing. :)
</p
>
9516 <p
>If you want to help out with implementing this for Debian Edu,
9517 please contact us on debian-edu@lists.debian.org.
</p
>
9519 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9520 configuration in LDAP that was created around year
2000 by
9521 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9522 Xperience, Inc.,
2000</a
>. I found its
9523 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9524 personal home page over at redhat.com.
</p
>
9529 <title>jXplorer, a very nice LDAP GUI
</title>
9530 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9531 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9532 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9533 <description><p
>Since
9534 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9535 last post
</a
> about available LDAP tools in Debian, I was told about a
9536 LDAP GUI that is even better than luma. The java application
9537 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9538 moving LDAP objects and subtrees using drag-and-drop, and can
9539 authenticate using Kerberos. I have only tested the Kerberos
9540 authentication, but do not have a LDAP setup allowing me to rewrite
9541 LDAP with my test user yet. It is
9542 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9543 Debian
</a
> testing and unstable at the moment. The only problem I
9544 have with it is how it handle errors. If something go wrong, its
9545 non-intuitive behaviour require me to go through some query work list
9546 and remove the failing query. Nothing big, but very annoying.
</p
>
9551 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9552 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9553 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9554 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9555 <description><p
>Here is a short update on my
<a
9556 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9557 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9558 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9559 not reporting the status for KDE, because the upgrade crashes when
9560 aptitude try because of missing conflicts
9561 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9562 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9564 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9565 complete list of the installed packages. Based on this I see these
9566 differences when I did a test run today. As usual, I do not really
9567 know what the correct set of packages would be, but thought it best to
9568 publish the difference.
</p
>
9570 <p
>Installed using apt-get, missing with aptitude
</p
>
9572 <blockquote
><p
>
9573 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9574 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9575 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9576 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9577 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9578 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9579 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9580 python-gtkmozembed svgalibg1 xserver-xephyr zip
9581 </p
></blockquote
>
9583 <p
>Installed using apt-get, removed with aptitude
</p
>
9585 <blockquote
><p
>
9586 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9587 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9588 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9589 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9590 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9591 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9592 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9593 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9594 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9595 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9596 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9597 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9598 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9599 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9600 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9601 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9602 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9603 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9604 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9605 mysql-common swfdec-gnome totem-gstreamer wodim
9606 </p
></blockquote
>
9608 <p
>Installed using aptitude, missing with apt-get
</p
>
9610 <blockquote
><p
>
9611 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9612 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9613 xserver-xorg-input-all xserver-xorg-input-evdev
9614 xserver-xorg-input-kbd xserver-xorg-input-mouse
9615 xserver-xorg-input-synaptics xserver-xorg-video-all
9616 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9617 xserver-xorg-video-chips xserver-xorg-video-cirrus
9618 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9619 xserver-xorg-video-glint xserver-xorg-video-i128
9620 xserver-xorg-video-i740 xserver-xorg-video-mach64
9621 xserver-xorg-video-mga xserver-xorg-video-neomagic
9622 xserver-xorg-video-nouveau xserver-xorg-video-nv
9623 xserver-xorg-video-r128 xserver-xorg-video-radeon
9624 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9625 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9626 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9627 xserver-xorg-video-sis xserver-xorg-video-sisusb
9628 xserver-xorg-video-tdfx xserver-xorg-video-tga
9629 xserver-xorg-video-trident xserver-xorg-video-tseng
9630 xserver-xorg-video-vesa xserver-xorg-video-vmware
9631 xserver-xorg-video-voodoo
9632 </p
></blockquote
>
9634 <p
>Installed using aptitude, removed with apt-get
</p
>
9636 <blockquote
><p
>
9637 deskbar-applet xserver-xorg xserver-xorg-core
9638 xserver-xorg-input-wacom xserver-xorg-video-intel
9639 xserver-xorg-video-openchrome
9640 </p
></blockquote
>
9642 <p
>I was told on IRC that the xorg-xserver package was
9643 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9644 in git
</a
> today to try to get apt-get to not remove xorg completely.
9645 No idea when it hits Squeeze, but when it does I hope it will reduce
9646 the difference somewhat.
9651 <title>LUMA, a very nice LDAP GUI
</title>
9652 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9654 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9655 <description><p
>The last few days I have been looking into the status of the LDAP
9656 directory in Debian Edu, and in the process I started to miss a GUI
9657 tool to browse the LDAP tree. The only one I was able to find in
9658 Debian/Squeeze and Lenny is
9659 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9660 be a great tool to get a overview of the current LDAP directory
9661 populated by default in Skolelinux. Thanks to it, I have been able to
9662 find empty and obsolete subtrees, misplaced objects and duplicate
9663 objects. It will be installed by default in Debian/Squeeze. If you
9664 are working with LDAP, give it a go. :)
</p
>
9666 <p
>I did notice one problem with it I have not had time to report to
9667 the BTS yet. There is no .desktop file in the package, so the tool do
9668 not show up in the Gnome and KDE menus, but only deep down in in the
9669 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9672 <p
>I have not yet been able to get it to modify the tree yet. I would
9673 like to move objects and remove subtrees directly in the GUI, but have
9674 not found a way to do that with LUMA yet. So in the mean time, I use
9675 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9677 <p
>If you have tips on other GUI tools for LDAP that might be useful
9678 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9680 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9681 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9682 useful GUI alternative. It seem like a good tool, but is unmaintained
9683 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9684 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9689 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9690 <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>
9691 <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>
9692 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9693 <description><p
>A while back, I
9694 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9695 about the fact
</a
> that it is not possible with the provided schemas
9696 for storing DNS and DHCP information in LDAP to combine the two sets
9697 of information into one LDAP object representing a computer.
</p
>
9699 <p
>In the mean time, I discovered that a simple fix would be to make
9700 the dhcpHost object class auxiliary, to allow it to be combined with
9701 the dNSDomain object class, and thus forming one object for one
9702 computer when storing both DHCP and DNS information in LDAP.
</p
>
9704 <p
>If I understand this correctly, it is not safe to do this change
9705 without also changing the assigned number for the object class, and I
9706 do not know enough about LDAP schema design to do that properly for
9707 Debian Edu.
</p
>
9709 <p
>Anyway, for future reference, this is how I believe we could change
9711 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9712 schema
</a
> to solve at least part of the problem with the LDAP schemas
9713 available today from IETF.
</p
>
9716 --- dhcp.schema (revision
65192)
9717 +++ dhcp.schema (working copy)
9719 objectclass (
2.16.840.1.113719.1.203.6.6
9720 NAME
'dhcpHost
'
9721 DESC
'This represents information about a particular client
'
9725 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9726 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9729 <p
>I very much welcome clues on how to do this properly for Debian
9730 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9731 package, and should thus be free to rewrite it as we see fit.
</p
>
9733 <p
>If you want to help out with implementing this for Debian Edu,
9734 please contact us on debian-edu@lists.debian.org.
</p
>
9739 <title>Calling tasksel like the installer, while still getting useful output
</title>
9740 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9741 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9742 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9743 <description><p
>A few times I have had the need to simulate the way tasksel
9744 installs packages during the normal debian-installer run. Until now,
9745 I have ended up letting tasksel do the work, with the annoying problem
9746 of not getting any feedback at all when something fails (like a
9747 conffile question from dpkg or a download that fails), using code like
9750 <blockquote
><pre
>
9751 export DEBIAN_FRONTEND=noninteractive
9752 tasksel --new-install
9753 </pre
></blockquote
>
9755 This would invoke tasksel, let its automatic task selection pick the
9756 tasks to install, and continue to install the requested tasks without
9757 any output what so ever.
9759 Recently I revisited this problem while working on the automatic
9760 package upgrade testing, because tasksel would some times hang without
9761 any useful feedback, and I want to see what is going on when it
9762 happen. Then it occured to me, I can parse the output from tasksel
9763 when asked to run in test mode, and use that aptitude command line
9764 printed by tasksel then to simulate the tasksel run. I ended up using
9767 <blockquote
><pre
>
9768 export DEBIAN_FRONTEND=noninteractive
9769 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9771 </pre
></blockquote
>
9773 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9774 --without-recommends -o APT::Install-Recommends=no -y install
9775 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9776 ~pimportant
</tt
>", which will install the gnome desktop task, the
9777 laptop task and all packages with priority standard , required and
9778 important, just like tasksel would have done it during
9779 installation.
</p
>
9781 <p
>A better approach is probably to extend tasksel to be able to
9782 install packages without using debconf-apt-progress, for use cases
9783 like this.
</p
>
9788 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9789 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9790 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9791 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9792 <description><p
>My
9793 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9794 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9795 finally made the upgrade logs available from
9796 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9797 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9798 apt and aptitude, and found their differences interesting. This time
9799 I will only focus on their removal plans.
</p
>
9801 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9802 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9803 surprising part is that it want to remove xorg and all
9804 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9805 sure why. When asking aptitude to do the same, it want to remove
129
9806 packages, but most of them are library packages I suspect are no
9807 longer needed. Both of them want to remove bluetooth packages, which
9808 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9810 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9811 which seem like a bad idea and xorg the same way as with Gnome. Asking
9812 aptitude for the same, it wants to remove
192 packages, none which are
9813 too surprising.
</p
>
9815 <p
>I guess the removal of xorg during upgrades should be investigated
9816 and avoided, and perhaps others as well. Here are the complete list
9817 of planned removals. The complete logs is available from the URL
9818 above. Note if you want to repeat these tests, that the upgrade test
9819 for kde+apt-get hung in the tasksel setup because of dpkg asking
9820 conffile questions. No idea why. I worked around it by using
9821 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9824 <p
><b
>apt-get gnome
72</b
>
9825 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9826 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9827 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9828 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9829 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9830 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9831 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9832 xserver-xorg-input-kbd xserver-xorg-input-mouse
9833 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9834 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9835 xserver-xorg-video-ati xserver-xorg-video-chips
9836 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9837 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9838 xserver-xorg-video-glint xserver-xorg-video-i128
9839 xserver-xorg-video-i740 xserver-xorg-video-imstt
9840 xserver-xorg-video-intel xserver-xorg-video-mach64
9841 xserver-xorg-video-mga xserver-xorg-video-neomagic
9842 xserver-xorg-video-nsc xserver-xorg-video-nv
9843 xserver-xorg-video-openchrome xserver-xorg-video-r128
9844 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9845 xserver-xorg-video-rendition xserver-xorg-video-s3
9846 xserver-xorg-video-s3virge xserver-xorg-video-savage
9847 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9848 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9849 xserver-xorg-video-tga xserver-xorg-video-trident
9850 xserver-xorg-video-tseng xserver-xorg-video-v4l
9851 xserver-xorg-video-vesa xserver-xorg-video-vga
9852 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9853 xulrunner-
1.9-gnome-support
</p
>
9855 <p
><b
>aptitude gnome
129</b
>
9857 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9858 djvulibre-desktop finger gnome-app-install gnome-mount
9859 gnome-network-admin gnome-spell gnome-vfs-obexftp
9860 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9861 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9862 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9863 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9864 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9865 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9866 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9867 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9868 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9869 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9870 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9871 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9872 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9873 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9874 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9875 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9876 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9877 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9878 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9879 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9880 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9881 openoffice.org-writer2latex openssl-blacklist p7zip
9882 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9883 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9884 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9885 swfdec-mozilla totem-gstreamer update-manager wodim
9886 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9887 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9890 <p
><b
>apt-get kde
82</b
>
9892 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9893 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9894 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9895 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9896 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9897 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9898 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9899 xserver-xorg-input-kbd xserver-xorg-input-mouse
9900 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9901 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9902 xserver-xorg-video-ati xserver-xorg-video-chips
9903 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9904 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9905 xserver-xorg-video-glint xserver-xorg-video-i128
9906 xserver-xorg-video-i740 xserver-xorg-video-imstt
9907 xserver-xorg-video-intel xserver-xorg-video-mach64
9908 xserver-xorg-video-mga xserver-xorg-video-neomagic
9909 xserver-xorg-video-nsc xserver-xorg-video-nv
9910 xserver-xorg-video-openchrome xserver-xorg-video-r128
9911 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9912 xserver-xorg-video-rendition xserver-xorg-video-s3
9913 xserver-xorg-video-s3virge xserver-xorg-video-savage
9914 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9915 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9916 xserver-xorg-video-tga xserver-xorg-video-trident
9917 xserver-xorg-video-tseng xserver-xorg-video-v4l
9918 xserver-xorg-video-vesa xserver-xorg-video-vga
9919 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9921 <p
><b
>aptitude kde
192</b
>
9922 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9923 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9924 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9925 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9926 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9927 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9928 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9929 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9930 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9931 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9932 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9933 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9934 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9935 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9936 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9937 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9938 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9939 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9940 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9941 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9942 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9943 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9944 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9945 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9946 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9947 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9948 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9949 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9950 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9951 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9952 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9953 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9954 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9955 texlive-common texlive-doc-base texlive-fonts-recommended
9956 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9957 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9958 xulrunner-
1.9</p
>
9964 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9965 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9966 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9967 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9968 <description><p
>The last few days I have done some upgrade testing in Debian, to
9969 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9970 have been discovered and reported in the process
9971 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9972 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9973 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9974 kdebase-workspace-data), and to get a more regular testing going on, I
9975 am working on a script to automate the test.
</p
>
9977 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9978 Gnome or KDE desktop installation inside the chroot before upgrading
9979 it. To ensure no services are started in the chroot, a policy-rc.d
9980 script is inserted. To make sure tasksel believe it is to install a
9981 desktop on a laptop, the tasksel tests are replaced in the chroot
9982 (only acceptable because this is a throw-away chroot).
</p
>
9984 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9985 currently always fail because udev refuses to upgrade with the kernel
9986 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9987 is created. The bug report
9988 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9989 this problem do not trigger in a chroot, but I touch the file anyway
9990 to make sure the upgrade go well. Testing on virtual and real
9991 hardware have failed me because of udev so far, and creating this file
9992 do the trick in such settings anyway. This is a
9993 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9994 issue
</a
> and the current udev behaviour is intended by the udev
9995 maintainer because he lack the resources to rewrite udev to keep
9996 working with old kernels or something like that. I really wish the
9997 udev upstream would keep udev backwards compatible, to avoid such
9998 upgrade problem, but given that they fail to do so, I guess
9999 documenting the way out of this mess is the best option we got for
10000 Debian Squeeze.
</p
>
10002 <p
>Anyway, back to the task at hand, testing upgrades. This test
10003 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10006 <blockquote
><pre
>
10010 if [
"$
1" ] ; then
10019 exec
&lt; /dev/null
10021 mirror=http://ftp.skolelinux.org/debian
10022 tmpdir=chroot-$from-upgrade-$to-$desktop
10024 debootstrap $from $tmpdir $mirror
10025 chroot $tmpdir aptitude update
10026 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10030 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10032 umount $tmpdir/proc
10034 mount -t proc proc $tmpdir/proc
10035 # Make sure proc is unmounted also on failure
10036 trap exit_cleanup EXIT INT
10038 chroot $tmpdir aptitude -y install debconf-utils
10040 # Make sure tasksel autoselection trigger. It need the test scripts
10041 # to return the correct answers.
10042 echo tasksel tasksel/desktop multiselect $desktop | \
10043 chroot $tmpdir debconf-set-selections
10045 # Include the desktop and laptop task
10046 for test in desktop laptop ; do
10047 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10051 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10054 DEBIAN_FRONTEND=noninteractive
10055 DEBIAN_PRIORITY=critical
10056 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10057 chroot $tmpdir tasksel --new-install
10059 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10060 chroot $tmpdir aptitude update
10061 touch $tmpdir/etc/udev/kernel-upgrade
10062 chroot $tmpdir aptitude -y dist-upgrade
10064 </pre
></blockquote
>
10066 <p
>I suspect it would be useful to test upgrades with both apt-get and
10067 with aptitude, but I have not had time to look at how they behave
10068 differently so far. I hope to get a cron job running to do the test
10069 regularly and post the result on the web. The Gnome upgrade currently
10070 work, while the KDE upgrade fail because of the bug in
10071 kdebase-workspace-data
</p
>
10073 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10074 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10075 post, so I will refrain from trying. I can report that for Gnome,
10076 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10077 remove and
1 not upgraded and
1024MB need to be downloaded while for
10078 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10079 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10081 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10082 is able to migrate to dependency based boot sequencing and parallel
10083 booting without a hitch. Was unsure if there were still bugs with
10084 packages failing to clean up their obsolete init.d script during
10085 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10086 packages.
</p
>
10091 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10092 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10093 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10094 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10095 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10096 scripts to migrate (some of) their operations to upstart job while
10097 keeping the init.d for hurd and kfreebsd. The packages with such
10098 needs will need a way to get their init.d scripts to behave
10099 differently when used with sysvinit and with upstart. Because of
10100 this, I had a look at the environment variables set when a init.d
10101 script is running under upstart, and when it is not.
</p
>
10103 <p
>With upstart, I notice these environment variables are set when a
10104 script is started from rcS.d/ (ignoring some irrelevant ones like
10105 COLUMNS):
</p
>
10107 <blockquote
><pre
>
10113 UPSTART_EVENTS=startup
10115 UPSTART_JOB=rc-sysinit
10116 </pre
></blockquote
>
10118 <p
>With sysvinit, these environment variables are set for the same
10121 <blockquote
><pre
>
10122 INIT_VERSION=sysvinit-
2.88
10127 </pre
></blockquote
>
10129 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10130 sysvinit are not set by upstart. Not sure if it is intentional or not
10131 to not be compatible with sysvinit in this regard.
</p
>
10133 <p
>For scripts needing to behave differently when upstart is used,
10134 looking for the UPSTART_JOB environment variable seem to be a good
10140 <title>A manual for standards wars...
</title>
10141 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10142 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10143 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10144 <description><p
>Via the
10145 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10146 of Rob Weir
</a
> I came across the very interesting essay named
10147 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10148 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10149 following the standards wars of today.
</p
>
10154 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10155 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10156 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10157 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10158 <description><p
>When using sitesummary at a site to track machines, it is possible
10159 to get a list of the machine types in use thanks to the DMI
10160 information extracted from each machine. The script to do so is
10161 included in the sitesummary package, and here is example output from
10162 the Skolelinux build servers:
</p
>
10164 <blockquote
><pre
>
10165 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10167 Dell Computer Corporation
1
10170 eserver xSeries
345 -[
8670M1X]-
1
10174 </pre
></blockquote
>
10176 <p
>The quality of the report depend on the quality of the DMI tables
10177 provided in each machine. Here there are Intel machines without model
10178 information listed with Intel as vendor and no model, and virtual Xen
10179 machines listed as [no-dmi-info]. One can add -l as a command line
10180 option to list the individual machines.
</p
>
10182 <p
>A larger list is
10183 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10184 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10185 provide the basic sitesummary report publicly. In their report there
10186 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10187 their machines, and as sitesummary is available in both distributions,
10188 it is trivial to get all of them to report to the same central
10189 collector.
</p
>
10194 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10195 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10196 <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>
10197 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10198 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10199 start at boot when an NVidia video card is used is handled. The
10200 problem seem to be that the nvidia X.org driver uses a long time to
10201 initialize, and this duration is longer than kdm is configured to
10204 <p
>I came across two bugs related to this issue,
10205 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10206 against initscripts and passed on to nvidia-glx when it became obvious
10207 that the nvidia drivers were involved, and
10208 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10209 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10211 <p
>To me, it seem that no-one is interested in actually solving the
10212 problem nvidia video card owners experience and make sure the Debian
10213 distribution work out of the box for these users. The nvidia driver
10214 maintainers expect kdm to be set up to wait longer, while kdm expect
10215 the nvidia driver maintainers to fix the driver to start faster, and
10216 while they wait for each other I guess the users end up switching to a
10217 distribution that work for them. I have no idea what the solution is,
10218 but I am pretty sure that waiting for each other is not it.
</p
>
10220 <p
>I wonder why we end up handling bugs this way.
</p
>
10225 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10226 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10227 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10228 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10229 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10230 The feature seem to hold up pretty well, but three fairly serious
10231 issues are known and should be solved:
10233 <p
><ul
>
10235 <li
>The wicd package seen to
10236 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10237 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10238 parallel booting is enabled. No idea why, but the wicd maintainer
10239 seem to be on the case.
</li
>
10241 <li
>The nvidia X driver seem to
10242 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10243 triggered more easily when parallel booting is in effect. The
10244 maintainer is on the case.
</li
>
10246 <li
>The sysv-rc package fail to properly enable dependency based boot
10247 sequencing (the shutdown is broken) when old file-rc users
10248 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10249 sysv-rc. One way to solve it would be for file-rc to create
10250 /etc/init.d/.legacy-bootordering, and another is to try to make
10251 sysv-rc more robust. Will investigate some more and probably upload a
10252 workaround in sysv-rc to help those trying to move from file-rc to
10253 sysv-rc get a working shutdown.
</li
>
10255 </ul
></p
>
10257 <p
>All in all not many surprising issues, and all of them seem
10258 solvable before Squeeze is released. In addition to these there are
10259 some packages with bugs in their dependencies and run level settings,
10260 which I expect will be fixed in a reasonable time span.
</p
>
10262 <p
>If you report any problems with dependencies in init.d scripts to
10263 the BTS, please usertag the report to get it to show up at
10264 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10265 list of usertagged bugs related to this
</a
>.
</p
>
10267 <p
>Update: Correct bug number to file-rc issue.
</p
>
10272 <title>More flexible firmware handling in debian-installer
</title>
10273 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10274 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10275 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10276 <description><p
>After a long break from debian-installer development, I finally
10277 found time today to return to the project. Having to spend less time
10278 working dependency based boot in debian, as it is almost complete now,
10279 definitely helped freeing some time.
</p
>
10281 <p
>A while back, I ran into a problem while working on Debian Edu. We
10282 include some firmware packages on the Debian Edu CDs, those needed to
10283 get disk and network controllers working. Without having these
10284 firmware packages available during installation, it is impossible to
10285 install Debian Edu on the given machine, and because our target group
10286 are non-technical people, asking them to provide firmware packages on
10287 an external medium is a support pain. Initially, I expected it to be
10288 enough to include the firmware packages on the CD to get
10289 debian-installer to find and use them. This proved to be wrong.
10290 Next, I hoped it was enough to symlink the relevant firmware packages
10291 to some useful location on the CD (tried /cdrom/ and
10292 /cdrom/firmware/). This also proved to not work, and at this point I
10293 found time to look at the debian-installer code to figure out what was
10294 going to work.
</p
>
10296 <p
>The firmware loading code is in the hw-detect package, and a closer
10297 look revealed that it would only look for firmware packages outside
10298 the installation media, so the CD was never checked for firmware
10299 packages. It would only check USB sticks, floppies and other
10300 "external
" media devices. Today I changed it to also look in the
10301 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10302 solve the problem I ran into with Debian edu. I also changed it to
10303 look in /firmware/, to make sure the installer also find firmware
10304 provided in the initrd when booting the installer via PXE, to allow us
10305 to provide the same feature in the PXE setup included in Debian
10308 <p
>To make sure firmware deb packages with a license questions are not
10309 activated without asking if the license is accepted, I extended
10310 hw-detect to look for preinst scripts in the firmware packages, and
10311 run these before activating the firmware during installation. The
10312 license question is asked using debconf in the preinst, so this should
10313 solve the issue for the firmware packages I have looked at so far.
</p
>
10315 <p
>If you want to discuss the details of these features, please
10316 contact us on debian-boot@lists.debian.org.
</p
>
10321 <title>Parallellized boot is now the default in Debian/unstable
</title>
10322 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10323 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10324 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10325 <description><p
>Since this evening, parallel booting is the default in
10326 Debian/unstable for machines using dependency based boot sequencing.
10327 Apparently the testing of concurrent booting has been wider than
10328 expected, if I am to believe the
10329 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10330 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10331 with the feature this weekend, to give us some time to detect any
10332 remaining problems before Squeeze is frozen. If serious problems are
10333 detected, it is simple to change the default back to sequential boot.
10334 The upload of the new sysvinit package also activate a new upstream
10337 More information about
10338 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10339 based boot sequencing
</a
> is available from the Debian wiki. It is
10340 currently possible to disable parallel booting when one run into
10341 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10343 <blockquote
><pre
>
10345 </pre
></blockquote
>
10347 <p
>If you report any problems with dependencies in init.d scripts to
10348 the BTS, please usertag the report to get it to show up at
10349 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10350 list of usertagged bugs related to this
</a
>.
</p
>
10355 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10356 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10358 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10359 <description><p
>In the recent Debian Edu versions, the
10360 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10361 system
</a
> is used to keep track of the machines in the school
10362 network. Each machine will automatically report its status to the
10363 central server after boot and once per night. The network setup is
10364 also reported, and using this information it is possible to get the
10365 MAC address of all network interfaces in the machines. This is useful
10366 to update the DHCP configuration.
</p
>
10368 <p
>To give some idea how to use sitesummary, here is a one-liner to
10369 ist all MAC addresses of all machines reporting to sitesummary. Run
10370 this on the collector host:
</p
>
10372 <blockquote
><pre
>
10373 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10374 </pre
></blockquote
>
10376 <p
>This will list all MAC addresses assosiated with all machine, one
10377 line per machine and with space between the MAC addresses.
</p
>
10379 <p
>To allow system administrators easier job at adding static DHCP
10380 addresses for hosts, it would be possible to extend this to fetch
10381 machine information from sitesummary and update the DHCP and DNS
10382 tables in LDAP using this information. Such tool is unfortunately not
10383 written yet.
</p
>
10388 <title>systemd, an interesting alternative to upstart
</title>
10389 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10390 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10391 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10392 <description><p
>The last few days a new boot system called
10393 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10395 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10397 to the free software world. I have not yet had time to play around
10398 with it, but it seem to be a very interesting alternative to
10399 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10400 a good alternative for Debian when we are able to switch to an event
10401 based boot system. Tollef is
10402 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10403 systemd into Debian, and I look forward to seeing how well it work. I
10404 like the fact that systemd handles init.d scripts with dependency
10405 information natively, allowing them to run in parallel where upstart
10406 at the moment do not.
</p
>
10408 <p
>Unfortunately do systemd have the same problem as upstart regarding
10409 platform support. It only work on recent Linux kernels, and also need
10410 some new kernel features enabled to function properly. This means
10411 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10412 system. Not sure how that will be handled if systemd proves to be the
10413 way forward.
</p
>
10415 <p
>In the mean time, based on the
10416 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10417 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10418 decided to enable full parallel booting as the default in Debian as
10419 soon as possible (probably this weekend or early next week), to see if
10420 there are any remaining serious bugs in the init.d dependencies. A
10421 new version of the sysvinit package implementing this change is
10422 already in experimental. If all go well, Squeeze will be released
10423 with parallel booting enabled by default.
</p
>
10428 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10429 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10430 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10431 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10432 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10433 complete, so complete that it is actually possible to run all the
10434 init.d scripts in parallell based on these dependencies. If you want
10435 to test your Squeeze system, make sure
10436 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10437 based boot sequencing
</a
> is enabled, and add this line to
10438 /etc/default/rcS:
</p
>
10440 <blockquote
><pre
>
10441 CONCURRENCY=makefile
10442 </pre
></blockquote
>
10444 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10445 scripts in parallel using the dependency information stored in
10446 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10447 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10448 to try to start the kdm and gdm scripts as early as possible, and will
10449 start the facilities required by kdm or gdm as early as possible to
10450 make this happen.
</p
>
10452 <p
>Give it a try, and see if you like the result. If some services
10453 fail to start properly, it is most likely because they have incomplete
10454 init.d script dependencies in their startup script (or some of their
10455 dependent scripts have incomplete dependencies). Report bugs and get
10456 the package maintainers to fix it. :)
</p
>
10458 <p
>Running scripts in parallel could be the default in Debian when we
10459 manage to get the init.d script dependencies complete and correct. I
10460 expect we will get there in Squeeze+
1, if we get manage to test and
10461 fix the remaining issues.
</p
>
10463 <p
>If you report any problems with dependencies in init.d scripts to
10464 the BTS, please usertag the report to get it to show up at
10465 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10466 list of usertagged bugs related to this
</a
>.
</p
>
10471 <title>Debian has switched to dependency based boot sequencing
</title>
10472 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10473 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10474 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10475 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10476 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10477 have been migrated to using dependency based boot sequencing. This
10478 conclude work me and others have been doing for the last three days.
10479 It feels great to see this finally part of the default Debian
10480 installation. Now we just need to weed out the last few problems that
10481 are bound to show up, to get everything ready for Squeeze.
</p
>
10483 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10484 fixing the more fundamental problem of handing the event based
10485 non-predictable kernel in the early boot.
</p
>
10490 <title>Taking over sysvinit development
</title>
10491 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10492 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10493 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10494 <description><p
>After several years of frustration with the lack of activity from
10495 the existing sysvinit upstream developer, I decided a few weeks ago to
10496 take over the package and become the new upstream. The number of
10497 patches to track for the Debian package was becoming a burden, and the
10498 lack of synchronization between the distribution made it hard to keep
10499 the package up to date.
</p
>
10501 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10502 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10503 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10504 and Fedora), based on the patches currently in use in these
10505 distributions. We Debian maintainers plan to move to this tarball as
10506 the new upstream as soon as we find time to do the merge. Since the
10507 new tarball was created, we agreed with Werner at SuSe to make a new
10508 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10509 development there. The project is registered and currently waiting
10510 for approval by the Savannah administrators, and as soon as it is
10511 approved, we will import the old versions from svn and continue
10512 working on the future release.
</p
>
10514 <p
>It is a bit ironic that this is done now, when some of the involved
10515 distributions are moving to upstart as a syvinit replacement.
</p
>
10520 <title>Debian boots quicker and quicker
</title>
10521 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10522 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10523 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10524 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10525 people involved in the boot system on Debian and Ubuntu, to see if we
10526 could find more ways to speed up the boot system. This was an Ubuntu
10528 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10529 gathering
</a
>. It was quite productive. We also discussed the future
10530 of boot systems, and ways to handle the increasing number of boot
10531 issues introduced by the Linux kernel becoming more and more
10532 asynchronous and event base. The Ubuntu approach using udev and
10533 upstart might be a good way forward. Time will show.
</p
>
10535 <p
>Anyway, there are a few ways at the moment to speed up the boot
10536 process in Debian. All of these should be applied to get a quick
10541 <li
>Use dash as /bin/sh.
</li
>
10543 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10544 clock is in UTC.
</li
>
10546 <li
>Install and activate the insserv package to enable
10547 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10548 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10552 These points are based on the Google summer of code work done by
10553 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10554 Villegas
</a
>.
10556 <p
>Support for makefile-style concurrency during boot was uploaded to
10557 unstable yesterday. When we tested it, we were able to cut
6 seconds
10558 from the boot sequence. It depend on very correct dependency
10559 declaration in all init.d scripts, so I expect us to find edge cases
10560 where the dependences in some scripts are slightly wrong when we start
10561 using this.
</p
>
10563 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10564 introduced by Raphael Geissert today, one that could affect the
10565 startup speed as well. Instead of starting some scripts concurrently
10566 from rcS.d/ and another set of scripts from rc2.d/, it would be
10567 possible to run a of them in the same process. A quick way to test
10568 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10569 insserv
'. Will need to test if that work. :)
</p
>
10574 <title>BSAs påstander om piratkopiering møter motstand
</title>
10575 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10576 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10577 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10578 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10579 programvareselskapene som Microsoft og Apple, publisert en rapport der
10580 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10581 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10583 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10584 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10585 dagene. Et spesielt interessant kommentar fra Sverige,
10586 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10587 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10590 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10591 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10592 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10593 exakta
", säger BSAs Sverigechef John Hugosson.
10594 </blockquote
>
10596 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10597 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10598 piracy figures need a shot of reality
</a
> og
<a
10599 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10600 Copyright Treaty Work?
</a
></p
>
10602 <p
>Fant lenkene via
<a
10603 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10604 på Slashdot
</a
>.
</p
>
10609 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10610 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10611 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10612 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10613 <description><p
>Kom over
10614 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10615 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10616 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10617 jobber til daglig. En rask opptelling forteller meg at vi har
490
10618 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10619 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10620 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10625 <title>Kryptert harddisk - naturligvis
</title>
10626 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10628 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10629 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10630 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10631 når en tar tap av arbeidstid, fortrolige dokumenter,
10632 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10633 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10634 til at jeg har kryptert harddisken på både kontormaskinen og min
10635 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10636 komme på avveie, den første informasjon relatert til jobben min ved
10637 Universitetet i Oslo, og den andre relatert til blant annet
10638 foreningsarbeide. Kryptering av diskene gjør at det er lite
10639 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10640 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10641 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10642 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10643 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10644 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10645 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10646 det er gjort slik jeg gjør det er minimale, og gevinstene er
10647 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10648 maskinen reinstalleres og alt er tapt.
</p
>
10650 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10651 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10652 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10653 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10654 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10655 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10656 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10657 betydelige.
</p
>
10662 <title>Two projects that have improved the quality of free software a lot
</title>
10663 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10664 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10665 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10666 <description><p
>There are two software projects that have had huge influence on the
10667 quality of free software, and I wanted to mention both in case someone
10668 do not yet know them.
</p
>
10670 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10671 tool to detect and expose errors in the memory handling of programs.
10672 It is easy to use, all one need to do is to run
'valgrind program
',
10673 and it will report any problems on stdout. It is even better if the
10674 program include debug information. With debug information, it is able
10675 to report the source file name and line number where the problem
10676 occurs. It can report things like
'reading past memory block in file
10677 X line N, the memory block was allocated in file Y, line M
', and
10678 'using uninitialised value in control logic
'. This tool has made it
10679 trivial to investigate reproducible crash bugs in programs, and have
10680 reduced the number of this kind of bugs in free software a lot.
10682 <p
>The second one is
10683 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10684 a source code checker. It is able to process the source of a program
10685 and find problems in the logic without running the program. It
10686 started out as the Stanford Checker and became well known when it was
10687 used to find bugs in the Linux kernel. It is now a commercial tool
10688 and the company behind it is running
10689 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10690 free software community, where a lot of free software projects get
10691 their source checked for free. Several thousand defects have been
10692 found and fixed so far. It can find errors like
'lock L taken in file
10693 X line N is never released if exiting in line M
', or
'the code in file
10694 Y lines O to P can never be executed
'. The projects included in the
10695 community service project have managed to get rid of a lot of
10696 reliability problems thanks to Coverity.
</p
>
10698 <p
>I believe tools like this, that are able to automatically find
10699 errors in the source, are vital to improve the quality of software and
10700 make sure we can get rid of the crashing and failing software we are
10701 surrounded by today.
</p
>
10706 <title>No patch is not better than a useless patch
</title>
10707 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10708 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10709 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10710 <description><p
>Julien Blache
10711 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10712 patch is better than a useless patch
</a
>. I completely disagree, as a
10713 patch allow one to discuss a concrete and proposed solution, and also
10714 prove that the issue at hand is important enough for someone to spent
10715 time on fixing it. No patch do not provide any of these positive
10716 properties.
</p
>
10721 <title>Standardize on protocols and formats, not vendors and applications
</title>
10722 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10723 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10724 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10725 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10726 very good one to form a long lived computer infrastructure. It is the
10727 simple one, lost by many in todays computer industry: Standardize on
10728 open network protocols and open exchange/storage formats, not applications.
10729 Applications come and go, while protocols and files tend to stay, and
10730 thus one want to make it easy to change application and vendor, while
10731 avoiding conversion costs and locking users to a specific platform or
10732 application.
</p
>
10734 <p
>This approach make it possible to replace the client applications
10735 independently of the server applications. One can even allow users to
10736 use several different applications as long as they handle the selected
10737 protocol and format. In the normal case, only one client application
10738 is recommended and users only get help if they choose to use this
10739 application, but those that want to deviate from the easy path are not
10740 blocked from doing so.
</p
>
10742 <p
>It also allow us to replace the server side without forcing the
10743 users to replace their applications, and thus allow us to select the
10744 best server implementation at any moment, when scale and resouce
10745 requirements change.
</p
>
10747 <p
>I strongly recommend standardizing - on open network protocols and
10748 open formats, but I would never recommend standardizing on a single
10749 application that do not use open network protocol or open formats.
</p
>
10754 <title>Returning from Skolelinux developer gathering
</title>
10755 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10756 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10757 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10758 <description><p
>I
'm sitting on the train going home from this weekends Debian
10759 Edu/Skolelinux development gathering. I got a bit done tuning the
10760 desktop, and looked into the dynamic service location protocol
10761 implementation avahi. It look like it could be useful for us. Almost
10762 30 people participated, and I believe it was a great environment to
10763 get to know the Skolelinux system. Walter Bender, involved in the
10764 development of the Sugar educational platform, presented his stuff and
10765 also helped me improve my OLPC installation. He also showed me that
10766 his Turtle Art application can be used in standalone mode, and we
10767 agreed that I would help getting it packaged for Debian. As a
10768 standalone application it would be great for Debian Edu. We also
10769 tried to get the video conferencing working with two OLPCs, but that
10770 proved to be too hard for us. The application seem to need more work
10771 before it is ready for me. I look forward to getting home and relax
10777 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10778 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10780 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10781 <description><p
>The state of standardized LDAP schemas on Linux is far from
10782 optimal. There is RFC
2307 documenting one way to store NIS maps in
10783 LDAP, and a modified version of this normally called RFC
2307bis, with
10784 some modifications to be compatible with Active Directory. The RFC
10785 specification handle the content of a lot of system databases, but do
10786 not handle DNS zones and DHCP configuration.
</p
>
10788 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10789 we would like to store information about users, SMB clients/hosts,
10790 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10791 and LTSP configuration in LDAP. These objects have a lot in common,
10792 but with the current LDAP schemas it is not possible to have one
10793 object per entity. For example, one need to have at least three LDAP
10794 objects for a given computer, one with the SMB related stuff, one with
10795 DNS information and another with DHCP information. The schemas
10796 provided for DNS and DHCP are impossible to combine into one LDAP
10797 object. In addition, it is impossible to implement quick queries for
10798 netgroup membership, because of the way NIS triples are implemented.
10799 It just do not scale. I believe it is time for a few RFC
10800 specifications to cleam up this mess.
</p
>
10802 <p
>I would like to have one LDAP object representing each computer in
10803 the network, and this object can then keep the SMB (ie host key), DHCP
10804 (mac address/name) and DNS (name/IP address) settings in one place.
10805 It need to be efficently stored to make sure it scale well.
</p
>
10807 <p
>I would also like to have a quick way to map from a user or
10808 computer and to the net group this user or computer is a member.
</p
>
10810 <p
>Active Directory have done a better job than unix heads like myself
10811 in this regard, and the unix side need to catch up. Time to start a
10812 new IETF work group?
</p
>
10817 <title>Endelig er Debian Lenny gitt ut
</title>
10818 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10819 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10820 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10821 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10822 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10823 Et langt steg videre for Debian-prosjektet, og en rekke nye
10824 programpakker blir nå tilgjengelig for de av oss som bruker den
10825 stabile utgaven av Debian. Neste steg er nå å få
10826 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10827 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10828 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10829 slippes løs på skolene. Takk til alle debian-utviklerne som har
10830 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10831 bootsekvens tilgjengelig i stabil utgave, vha pakken
10832 <tt
>insserv
</tt
>.
</p
>
10837 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10838 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10839 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10840 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10841 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10842 Oslo. Most of Saturday was used for the general assemly for the
10843 member organization, but the rest of the weekend I used to tune the
10844 LTSP installation. LTSP now work out of the box on the
10-network.
10845 Acer Aspire One proved to be a very nice thin client, with both
10846 screen, mouse and keybard in a small box. Was working on getting the
10847 diskless workstation setup configured out of the box, but did not
10848 finish it before the weekend was up.
</p
>
10850 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10851 the Brazilian group, so that will have to wait for the next
10852 development gathering. Would love to have the Debian Edu installer
10853 automatically detect and configure a multiseat setup when it find one
10854 of these cards.
</p
>
10859 <title>The sorry state of multimedia browser plugins in Debian
</title>
10860 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10861 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10862 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10863 <description><p
>Recently I have spent some time evaluating the multimedia browser
10864 plugins available in Debian Lenny, to see which one we should use by
10865 default in Debian Edu. We need an embedded video playing plugin with
10866 control buttons to pause or stop the video, and capable of streaming
10867 all the multimedia content available on the web. The test results and
10868 notes are available on
10869 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10870 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10871 fill this need. My personal video player favorite, VLC, has a really
10872 bad plugin which fail on a lot of the test pages. A lot of the MIME
10873 types I would expect to work with any free software player (like
10874 video/ogg), just do not work. And simple formats like the
10875 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10876 totem and vlc plugins. I hope the situation will improve soon. No
10877 wonder sites use the proprietary Adobe flash to play video.
</p
>
10879 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10880 be the only one fitting our needs. :/
</p
>