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=
"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
>
53 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
54 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
55 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
56 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
57 <description><p
>Every mobile phone announce its existence over radio to the nearby
58 mobile cell towers. And this radio chatter is available for anyone
59 with a radio receiver capable of receiving them. Details about the
60 mobile phones with very good accuracy is of course collected by the
61 phone companies, but this is not the topic of this blog post. The
62 mobile phone radio chatter make it possible to figure out when a cell
63 phone is nearby, as it include the SIM card ID (IMSI). By paying
64 attention over time, one can see when a phone arrive and when it leave
65 an area. I believe it would be nice to make this information more
66 available to the general public, to make more people aware of how
67 their phones are announcing their whereabouts to anyone that care to
70 <p
>I am very happy to report that we managed to get something
71 visualizing this information up and running for
72 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
73 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
74 library. The solution is based on the
75 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
76 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
77 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
78 Sone from the Computer Science department of the University of
79 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
80 IMSIs) as dots in a web browser graph, with lines to the dot
81 representing mobile base station it is talking to. It was working in
82 the lab yesterday, and was moved into place this morning.
</p
>
84 <p
>We set up a fairly powerful desktop machine using Debian
85 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
86 connected and visualize the visible cell phone towers using an
87 <a href=
"https://github.com/marlow925/hopglass
">English version of
88 Hopglass
</a
>. A fairly powerfull machine is needed as the
89 grgsm_livemon_headless processes from
90 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
91 the radio signal to data packages is quite CPU intensive.
</p
>
93 <p
>The frequencies to listen to, are identified using a slightly
94 patched scan-and-livemon (to set the --args values for each receiver),
95 and the Hopglass data is generated using the
96 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
97 in my meshviewer-output branch
</a
>. For some reason we could not get
98 more than four SDRs working. There is also a geographical map trying
99 to show the location of the base stations, but I believe their
100 coordinates are hardcoded to some random location in Germany, I
101 believe. The code should be replaced with code to look up location in
102 a text file, a sqlite database or one of the online databases
104 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
105 issue for the topic
</a
>.
107 <p
>If this sound interesting, visit the stand at the festival!
</p
>
112 <title>Easier recipe to observe the cell phones around you
</title>
113 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
114 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
115 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
116 <description><p
>A little more than a month ago I wrote
117 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
118 to observe the SIM card ID (aka IMSI number) of mobile phones talking
119 to nearby mobile phone base stations using Debian GNU/Linux and a
120 cheap USB software defined radio
</a
>, and thus being able to pinpoint
121 the location of people and equipment (like cars and trains) with an
122 accuracy of a few kilometer. Since then we have worked to make the
123 procedure even simpler, and it is now possible to do this without any
124 manual frequency tuning and without building your own packages.
</p
>
126 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
127 package is now included in Debian testing and unstable, and the
128 IMSI-catcher code no longer require root access to fetch and decode
129 the GSM data collected using gr-gsm.
</p
>
131 <p
>Here is an updated recipe, using packages built by Debian and a git
132 clone of two python scripts:
</p
>
136 <li
>Start with a Debian machine running the Buster version (aka
139 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
140 python-scapy
</tt
>' as root to install required packages.
</li
>
142 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
143 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
145 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
147 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
148 scan-and-livemon
</tt
>' to locate the frequency of nearby base
149 stations and start listening for GSM packages on one of them.
</li
>
151 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
152 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
156 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
157 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
158 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
159 work with RTL
8232 and other similar USB radio receivers you can get
161 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
162 from ebay
</a
>), so for now the solution is to scan using the RTL radio
163 and only use HackRF for fetching GSM data.
</p
>
165 <p
>As far as I can tell, a cell phone only show up on one of the
166 frequencies at the time, so if you are going to track and count every
167 cell phone around you, you need to listen to all the frequencies used.
168 To listen to several frequencies, use the --numrecv argument to
169 scan-and-livemon to use several receivers. Further, I am not sure if
170 phones using
3G or
4G will show as talking GSM to base stations, so
171 this approach might not see all phones around you. I typically see
172 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
174 <p
>I
've tried to run the scanner on a
175 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
176 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
177 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
178 stdout, I am told there it is caused by a buffer overflow between the
179 radio and GNU Radio, caused by the program being unable to read the
180 GSM data fast enough. If you see a stream of
'O
's from the terminal
181 where you started scan-and-livemon, you need a give the process more
182 CPU power. Perhaps someone are able to optimize the code to a point
183 where it become possible to set up RPi3 based GSM sniffers? I tried
184 using Raspbian instead of Debian, but there seem to be something wrong
185 with GNU Radio on raspbian, causing glibc to abort().
</p
>
190 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
191 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
192 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
193 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
194 <description><p
>On friday, I came across an interesting article in the Norwegian
195 web based ICT news magazine digi.no on
196 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
197 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
198 DVB-T software defined radios. The article refered to instructions
199 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
200 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
202 <p
>The instructions said to use Ubuntu, install pip using apt (to
203 bypass apt), use pip to install pybombs (to bypass both apt and pip),
204 and the ask pybombs to fetch and build everything you need from
205 scratch. I wanted to see if I could do the same on the most recent
206 Debian packages, but this did not work because pybombs tried to build
207 stuff that no longer build with the most recent openssl library or
208 some other version skew problem. While trying to get this recipe
209 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
210 and the only piece of software dependency missing in Debian was the
211 gr-gsm package. I also found out that the lead upstream developer of
212 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
213 Debian packages provided in an Ubuntu PPA repository. All I needed to
214 do was to dget the Debian source package and built it.
</p
>
216 <p
>The IMSI collector is a python script listening for packages on the
217 loopback network device and printing to the terminal some specific GSM
218 packages with IMSI numbers in them. The code is fairly short and easy
219 to understand. The reason this work is because gr-gsm include a tool
220 to read GSM data from a software defined radio like a DVB-T USB stick
221 and other software defined radios, decode them and inject them into a
222 network device on your Linux machine (using the loopback device by
223 default). This proved to work just fine, and I
've been testing the
224 collector for a few days now.
</p
>
226 <p
>The updated and simpler recipe is thus to
</p
>
230 <li
>start with a Debian machine running Stretch or newer,
</li
>
232 <li
>build and install the gr-gsm package available from
233 <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
>
235 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
237 <li
>run grgsm_livemon and adjust the frequency until the terminal
238 where it was started is filled with a stream of text (meaning you
239 found a GSM station).
</li
>
241 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
245 <p
>To make it even easier in the future to get this sniffer up and
246 running, I decided to package
247 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
248 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
249 #
871055</a
>), and the package was uploaded into the NEW queue today.
250 Luckily the gnuradio maintainer has promised to help me, as I do not
251 know much about gnuradio stuff yet.
</p
>
253 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
254 commercial tools like
255 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
256 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
257 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
258 Stingray
</a
>, but I hope the existance of cheap alternatives can make
259 more people realise how their whereabouts when carrying a cell phone
260 is easily tracked. Seeing the data flow on the screen, realizing that
261 I live close to a police station and knowing that the police is also
262 wearing cell phones, I wonder how hard it would be for criminals to
263 track the position of the police officers to discover when there are
264 police near by, or for foreign military forces to track the location
265 of the Norwegian military forces, or for anyone to track the location
266 of government officials...
</p
>
268 <p
>It is worth noting that the data reported by the IMSI-catcher
269 script mentioned above is only a fraction of the data broadcasted on
270 the GSM network. It will only collect one frequency at the time,
271 while a typical phone will be using several frequencies, and not all
272 phones will be using the frequencies tracked by the grgsm_livemod
273 program. Also, there is a lot of radio chatter being ignored by the
274 simple_IMSI-catcher script, which would be collected by extending the
275 parser code. I wonder if gr-gsm can be set up to listen to more than
276 one frequency?
</p
>
281 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
282 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
283 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
284 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
285 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
287 <p
>I finally received a copy of the Norwegian Bokmål edition of
288 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
289 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
290 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
291 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
292 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
293 price. The book is also available for download in electronic form as
294 PDF, EPUB and Mobipocket, as can be
295 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
296 as a web page
</a
>.
</p
>
298 <p
>This is the second book I publish (the first was the book
299 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
301 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
302 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
304 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
305 Bokmål
</a
>), and I am very excited to finally wrap up this
307 "<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
308 for Debian-administratoren
</a
>" will be well received.
</p
>
313 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
314 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
315 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
316 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
317 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
318 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
319 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
320 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
321 på om den fri oversetterløsningen
322 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
323 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
325 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
328 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
329 rolle og muligheter til å håndtere internasjonale utfordringer, som
330 for eksempel flykningekrisen.
</p
>
332 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
335 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
336 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
341 <p
>Dette oversetter Apertium slik:
</p
>
344 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
345 andre aktørar og høve til å handtera internasjonale utfordringar, som
346 til dømes *flykningekrisen.
</p
>
348 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
352 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
353 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
358 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
359 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
360 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
361 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
362 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
363 det er kanskje flisespikking. Det understreker vel bare at det alltid
364 trengs korrekturlesning etter automatisk oversettelse.
</p
>
369 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
370 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
371 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
372 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
373 <description><p
>Over the years, administrating thousand of NFS mounting linux
374 computers at the time, I often needed a way to detect if the machine
375 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
376 file or directory affected by the hang, the process (and possibly the
377 shell) will hang too. So you want to be able to detect this without
378 risking the detection process getting stuck too. It has not been
379 obvious how to do this. When the hang has lasted a while, it is
380 possible to find messages like these in dmesg:
</p
>
382 <p
><blockquote
>
383 nfs: server nfsserver not responding, still trying
384 <br
>nfs: server nfsserver OK
385 </blockquote
></p
>
387 <p
>It is hard to know if the hang is still going on, and it is hard to
388 be sure looking in dmesg is going to work. If there are lots of other
389 messages in dmesg the lines might have rotated out of site before they
390 are noticed.
</p
>
392 <p
>While reading through the nfs client implementation in linux kernel
393 code, I came across some statistics that seem to give a way to detect
394 it. The om_timeouts sunrpc value in the kernel will increase every
395 time the above log entry is inserted into dmesg. And after digging a
396 bit further, I discovered that this value show up in
397 /proc/self/mountstats on Linux.
</p
>
399 <p
>The mountstats content seem to be shared between files using the
400 same file system context, so it is enough to check one of the
401 mountstats files to get the state of the mount point for the machine.
402 I assume this will not show lazy umounted NFS points, nor NFS mount
403 points in a different process context (ie with a different filesystem
404 view), but that does not worry me.
</p
>
406 <p
>The content for a NFS mount point look similar to this:
</p
>
408 <p
><blockquote
><pre
>
410 device /dev/mapper/Debian-var mounted on /var with fstype ext3
411 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
412 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
414 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
415 sec: flavor=
1,pseudoflavor=
1
416 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
417 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
418 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
419 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
421 NULL:
0 0 0 0 0 0 0 0
422 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
423 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
424 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
425 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
426 READLINK:
125 125 0 20472 18620 0 1112 1118
427 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
428 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
429 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
430 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
431 SYMLINK:
903 903 0 233428 245488 6 5865 5917
432 MKNOD:
80 80 0 20148 21760 0 299 304
433 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
434 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
435 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
436 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
437 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
438 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
439 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
440 FSINFO:
2 2 0 232 328 0 1 1
441 PATHCONF:
1 1 0 116 140 0 0 0
442 COMMIT:
0 0 0 0 0 0 0 0
444 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
446 </pre
></blockquote
></p
>
448 <p
>The key number to look at is the third number in the per-op list.
449 It is the number of NFS timeouts experiences per file system
450 operation. Here
22 write timeouts and
5 access timeouts. If these
451 numbers are increasing, I believe the machine is experiencing NFS
452 hang. Unfortunately the timeout value do not start to increase right
453 away. The NFS operations need to time out first, and this can take a
454 while. The exact timeout value depend on the setup. For example the
455 defaults for TCP and UDP mount points are quite different, and the
456 timeout value is affected by the soft, hard, timeo and retrans NFS
457 mount options.
</p
>
459 <p
>The only way I have been able to get working on Debian and RedHat
460 Enterprise Linux for getting the timeout count is to peek in /proc/.
462 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
463 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
464 command can be used to get these timeout values. But this do not work
465 on Linux, as far as I can tell. I
466 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
467 but have not seen any replies yet.
</p
>
469 <p
>Is there a better way to figure out if a Linux NFS client is
470 experiencing NFS hangs? Is there a way to detect which processes are
471 affected? Is there a way to get the NFS mount going quickly once the
472 network problem causing the NFS hang has been cleared? I would very
473 much welcome some clues, as we regularly run into NFS hangs.
</p
>
478 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
479 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
480 <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>
481 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
482 <description><p
>For almost a year now, we have been working on making a Norwegian
483 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
484 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
485 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
486 we are working on the proof reading to ensure consistent language and
487 use of correct computer science terms. The plan is to make the book
488 available on paper, as well as in electronic form. For that to
489 happen, the proof reading must be completed and all the figures need
490 to be translated. If you want to help out, get in touch.
</p
>
492 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
494 fresh PDF edition
</a
> in A4 format (the final book will have smaller
495 pages) of the book created every morning is available for
496 proofreading. If you find any errors, please
497 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
498 Weblate and correct the error
</a
>. The
499 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
500 of the translation including figures
</a
> is a useful source for those
501 provide Norwegian bokmål screen shots and figures.
</p
>
506 <title>Unlimited randomness with the ChaosKey?
</title>
507 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
508 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
509 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
510 <description><p
>A few days ago I ordered a small batch of
511 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
512 USB dongle for generating entropy created by Bdale Garbee and Keith
513 Packard. Yesterday it arrived, and I am very happy to report that it
514 work great! According to its designers, to get it to work out of the
515 box, you need the Linux kernel version
4.1 or later. I tested on a
516 Debian Stretch machine (kernel version
4.9), and there it worked just
517 fine, increasing the available entropy very quickly. I wrote a small
518 test oneliner to test. It first print the current entropy level,
519 drain /dev/random, and then print the entropy level for five seconds.
520 Here is the situation without the ChaosKey inserted:
</p
>
522 <blockquote
><pre
>
523 % cat /proc/sys/kernel/random/entropy_avail; \
524 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
525 for n in $(seq
1 5); do \
526 cat /proc/sys/kernel/random/entropy_avail; \
532 28 byte kopiert,
0,
000264565 s,
106 kB/s
539 </pre
></blockquote
>
541 <p
>The entropy level increases by
3-
4 every second. In such case any
542 application requiring random bits (like a HTTPS enabled web server)
543 will halt and wait for more entrpy. And here is the situation with
544 the ChaosKey inserted:
</p
>
546 <blockquote
><pre
>
547 % cat /proc/sys/kernel/random/entropy_avail; \
548 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
549 for n in $(seq
1 5); do \
550 cat /proc/sys/kernel/random/entropy_avail; \
556 104 byte kopiert,
0,
000487647 s,
213 kB/s
563 </pre
></blockquote
>
565 <p
>Quite the difference. :) I bought a few more than I need, in case
566 someone want to buy one here in Norway. :)
</p
>
568 <p
>Update: The dongle was presented at Debconf last year. You might
569 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
570 recording illuminating
</a
>. It explains exactly what the source of
571 randomness is, if you are unable to spot it from the schema drawing
572 available from the ChaosKey web site linked at the start of this blog
578 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
579 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
580 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
581 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
582 <description><p
>Did you ever wonder where the web trafic really flow to reach the
583 web servers, and who own the network equipment it is flowing through?
584 It is possible to get a glimpse of this from using traceroute, but it
585 is hard to find all the details. Many years ago, I wrote a system to
586 map the Norwegian Internet (trying to figure out if our plans for a
587 network game service would get low enough latency, and who we needed
588 to talk to about setting up game servers close to the users. Back
589 then I used traceroute output from many locations (I asked my friends
590 to run a script and send me their traceroute output) to create the
591 graph and the map. The output from traceroute typically look like
595 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
596 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
597 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
598 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
599 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
600 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
601 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
602 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
606 </pre
></p
>
608 <p
>This show the DNS names and IP addresses of (at least some of the)
609 network equipment involved in getting the data traffic from me to the
610 www.stortinget.no server, and how long it took in milliseconds for a
611 package to reach the equipment and return to me. Three packages are
612 sent, and some times the packages do not follow the same path. This
613 is shown for hop
5, where three different IP addresses replied to the
614 traceroute request.
</p
>
616 <p
>There are many ways to measure trace routes. Other good traceroute
617 implementations I use are traceroute (using ICMP packages) mtr (can do
618 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
619 traceroute and a lot of other capabilities). All of them are easily
620 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
622 <p
>This time around, I wanted to know the geographic location of
623 different route points, to visualize how visiting a web page spread
624 information about the visit to a lot of servers around the globe. The
625 background is that a web site today often will ask the browser to get
626 from many servers the parts (for example HTML, JSON, fonts,
627 JavaScript, CSS, video) required to display the content. This will
628 leak information about the visit to those controlling these servers
629 and anyone able to peek at the data traffic passing by (like your ISP,
630 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
632 <p
>Lets pick an example, the Norwegian parliament web site
633 www.stortinget.no. It is read daily by all members of parliament and
634 their staff, as well as political journalists, activits and many other
635 citizens of Norway. A visit to the www.stortinget.no web site will
636 ask your browser to contact
8 other servers: ajax.googleapis.com,
637 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
638 stats.g.doubleclick.net, www.google-analytics.com,
639 www.googletagmanager.com and www.netigate.se. I extracted this by
640 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
641 Stortinget web page and tell me all the URLs PhantomJS downloaded to
642 render the page (in HAR format using
643 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
644 netsniff example
</a
>. I am very grateful to Gorm for showing me how
645 to do this). My goal is to visualize network traces to all IP
646 addresses behind these DNS names, do show where visitors personal
647 information is spread when visiting the page.
</p
>
649 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
650 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
>
652 <p
>When I had a look around for options, I could not find any good
653 free software tools to do this, and decided I needed my own traceroute
654 wrapper outputting KML based on locations looked up using GeoIP. KML
655 is easy to work with and easy to generate, and understood by several
656 of the GIS tools I have available. I got good help from by NUUG
657 colleague Anders Einar with this, and the result can be seen in
658 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
659 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
660 free GeoIP databases I could find (and the for-pay databases my
661 friends had access to) is not up to the task. The IP addresses of
662 central Internet infrastructure would typically be placed near the
663 controlling companies main office, and not where the router is really
664 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
665 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
667 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
668 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
>
670 <p
>I also had a look at the visual traceroute graph created by
671 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
672 showing IP network ownership (aka AS owner) for the IP address in
674 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
675 graph display a lot of useful information about the traceroute in SVG
676 format
</a
>, and give a good indication on who control the network
677 equipment involved, but it do not include geolocation. This graph
678 make it possible to see the information is made available at least for
679 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
680 3 Communications and NetDNA.
</p
>
682 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
683 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
>
685 <p
>In the process, I came across the
686 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
687 Salim Gasmi. Its methology of combining guesses based on DNS names,
688 various location databases and finally use latecy times to rule out
689 candidate locations seemed to do a very good job of guessing correct
690 geolocation. But it could only do one trace at the time, did not have
691 a sensor in Norway and did not make the geolocations easily available
692 for postprocessing. So I contacted the developer and asked if he
693 would be willing to share the code (he refused until he had time to
694 clean it up), but he was interested in providing the geolocations in a
695 machine readable format, and willing to set up a sensor in Norway. So
696 since yesterday, it is possible to run traces from Norway in this
697 service thanks to a sensor node set up by
698 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
699 trace in KML format for further processing.
</p
>
701 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
702 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
>
704 <p
>Here we can see a lot of trafic passes Sweden on its way to
705 Denmark, Germany, Holland and Ireland. Plenty of places where the
706 Snowden confirmations verified the traffic is read by various actors
707 without your best interest as their top priority.
</p
>
709 <p
>Combining KML files is trivial using a text editor, so I could loop
710 over all the hosts behind the urls imported by www.stortinget.no and
711 ask for the KML file from GeoTraceroute, and create a combined KML
712 file with all the traces (unfortunately only one of the IP addresses
713 behind the DNS name is traced this time. To get them all, one would
714 have to request traces using IP number instead of DNS names from
715 GeoTraceroute). That might be the next step in this project.
</p
>
717 <p
>Armed with these tools, I find it a lot easier to figure out where
718 the IP traffic moves and who control the boxes involved in moving it.
719 And every time the link crosses for example the Swedish border, we can
720 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
721 Britain and NSA in USA and cables around the globe. (Hm, what should
722 we tell them? :) Keep that in mind if you ever send anything
723 unencrypted over the Internet.
</p
>
725 <p
>PS: KML files are drawn using
726 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
727 Rublev
<a/
>, as it was less cluttered than the local Linux application
728 Marble. There are heaps of other options too.
</p
>
730 <p
>As usual, if you use Bitcoin and want to show your support of my
731 activities, please send Bitcoin donations to my address
732 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
737 <title>Appstream just learned how to map hardware to packages too!
</title>
738 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
739 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
740 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
741 <description><p
>I received a very nice Christmas present today. As my regular
742 readers probably know, I have been working on the
743 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
744 system
</a
> for many years. The goal of the Isenkram system is to make
745 it easier for users to figure out what to install to get a given piece
746 of hardware to work in Debian, and a key part of this system is a way
747 to map hardware to packages. Isenkram have its own mapping database,
748 and also uses data provided by each package using the AppStream
749 metadata format. And today,
750 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
751 Debian learned to look up hardware the same way Isenkram is doing it,
752 ie using fnmatch():
</p
>
755 % appstreamcli what-provides modalias \
756 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
757 Identifier: pymissile [generic]
759 Summary: Control original Striker USB Missile Launcher
761 % appstreamcli what-provides modalias usb:v0694p0002d0000
762 Identifier: libnxt [generic]
764 Summary: utility library for talking to the LEGO Mindstorms NXT brick
767 Identifier: t2n [generic]
769 Summary: Simple command-line tool for Lego NXT
772 Identifier: python-nxt [generic]
774 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
777 Identifier: nbc [generic]
779 Summary: C compiler for LEGO Mindstorms NXT bricks
782 </pre
></p
>
784 <p
>A similar query can be done using the combined AppStream and
785 Isenkram databases using the isenkram-lookup tool:
</p
>
788 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
790 % isenkram-lookup usb:v0694p0002d0000
796 </pre
></p
>
798 <p
>You can find modalias values relevant for your machine using
799 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
801 <p
>If you want to make this system a success and help Debian users
802 make the most of the hardware they have, please
803 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
804 AppStream metadata for your package following the guidelines
</a
>
805 documented in the wiki. So far only
11 packages provide such
806 information, among the several hundred hardware specific packages in
807 Debian. The Isenkram database on the other hand contain
101 packages,
808 mostly related to USB dongles. Most of the packages with hardware
809 mapping in AppStream are LEGO Mindstorms related, because I have, as
810 part of my involvement in
811 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
812 team
</a
> given priority to making sure LEGO users get proposed the
813 complete set of packages in Debian for that particular hardware. The
814 team also got a nice Christmas present today. The
815 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
816 package
</a
> made it into Debian. With this package in place, it is
817 now possible to use the LEGO Mindstorms NXT unit with only free
818 software, as the nxt-firmware package contain the source and firmware
819 binaries for the NXT brick.
</p
>
821 <p
>As usual, if you use Bitcoin and want to show your support of my
822 activities, please send Bitcoin donations to my address
823 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
828 <title>Isenkram updated with a lot more hardware-package mappings
</title>
829 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
830 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
831 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
832 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
833 system
</a
> I wrote two years ago to make it easier in Debian to find
834 and install packages to get your hardware dongles to work, is still
835 going strong. It is a system to look up the hardware present on or
836 connected to the current system, and map the hardware to Debian
837 packages. It can either be done using the tools in isenkram-cli or
838 using the user space daemon in the isenkram package. The latter will
839 notify you, when inserting new hardware, about what packages to
840 install to get the dongle working. It will even provide a button to
841 click on to ask packagekit to install the packages.
</p
>
843 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
862 </pre
></p
>
864 <p
>It can also list the firware package providing firmware requested
865 by the load kernel modules, which in my case is an empty list because
866 I have all the firmware my machine need:
869 % /usr/sbin/isenkram-autoinstall-firmware -l
870 info: did not find any firmware files requested by loaded kernel modules. exiting
872 </pre
></p
>
874 <p
>The last few days I had a look at several of the around
250
875 packages in Debian with udev rules. These seem like good candidates
876 to install when a given hardware dongle is inserted, and I found
877 several that should be proposed by isenkram. I have not had time to
878 check all of them, but am happy to report that now there are
97
879 packages packages mapped to hardware by Isenkram.
11 of these
880 packages provide hardware mapping using AppStream, while the rest are
881 listed in the modaliases file provided in isenkram.
</p
>
883 <p
>These are the packages with hardware mappings at the moment. The
884 <strong
>marked packages
</strong
> are also announcing their hardware
885 support using AppStream, for everyone to use:
</p
>
887 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
888 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
889 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
890 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
891 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
892 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
893 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
894 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
895 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
896 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
897 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
898 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
899 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
900 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
901 pcscd, pidgin-blinklight, printer-driver-splix,
902 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
903 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
904 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
905 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
906 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
907 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
908 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
909 xserver-xorg-video-vmware, yubikey-personalization and
910 zd1211-firmware
</p
>
912 <p
>If you know of other packages, please let me know with a wishlist
913 bug report against the isenkram-cli package, and ask the package
915 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
916 metadata according to the guidelines
</a
> to provide the information
917 for everyone. In time, I hope to get rid of the isenkram specific
918 hardware mapping and depend exclusively on AppStream.
</p
>
920 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
921 much hardware, and suggest that the package with with any ethernet
922 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
923 the details. I hope the maintainer find time to address it soon. In
924 the mean time I provide an override in isenkram.
</p
>
929 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
930 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
931 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
932 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
933 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
935 <p
>In my early years, I played
936 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
937 Elite
</a
> on my PC. I spent many months trading and fighting in
938 space, and reached the
'elite
' fighting status before I moved on. The
939 original Elite game was available on Commodore
64 and the IBM PC
940 edition I played had a
64 KB executable. I am still impressed today
941 that the authors managed to squeeze both a
3D engine and details about
942 more than
2000 planet systems across
7 galaxies into a binary so
945 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
946 software game Oolite inspired by Elite
</a
> for a while, but did not
947 really have time to test it properly until a few days ago. It was
948 great to discover that my old knowledge about trading routes were
949 still valid. But my fighting and flying abilities were gone, so I had
950 to retrain to be able to dock on a space station. And I am still not
951 able to make much resistance when I am attacked by pirates, so I
952 bougth and mounted the most powerful laser in the rear to be able to
953 put up at least some resistance while fleeing for my life. :)
</p
>
955 <p
>When playing Elite in the late eighties, I had to discover
956 everything on my own, and I had long lists of prices seen on different
957 planets to be able to decide where to trade what. This time I had the
959 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
960 where information about each planet is easily available with common
961 price ranges and suggested trading routes. This improved my ability
962 to earn money and I have been able to earn enough to buy a lot of
963 useful equipent in a few days. I believe I originally played for
964 months before I could get a docking computer, while now I could get it
965 after less then a week.
</p
>
967 <p
>If you like science fiction and dreamed of a life as a vagabond in
968 space, you should try out Oolite. It is available for Linux, MacOSX
969 and Windows, and is included in Debian and derivatives since
2011.
</p
>
971 <p
>As usual, if you use Bitcoin and want to show your support of my
972 activities, please send Bitcoin donations to my address
973 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
978 <title>Quicker Debian installations using eatmydata
</title>
979 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
980 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
981 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
982 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
983 installation system, observing how using
984 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
985 could speed up the installation
</a
> quite a bit. My testing measured
986 speedup around
20-
40 percent for Debian Edu, where we install around
987 1000 packages from within the installer. The eatmydata package
988 provide a way to disable/delay file system flushing. This is a bit
989 risky in the general case, as files that should be stored on disk will
990 stay only in memory a bit longer than expected, causing problems if a
991 machine crashes at an inconvenient time. But for an installation, if
992 the machine crashes during installation the process is normally
993 restarted, and avoiding disk operations as much as possible to speed
994 up the process make perfect sense.
996 <p
>I added code in the Debian Edu specific installation code to enable
997 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
998 but did not have time to push it any further. But a few months ago I
999 picked it up again and worked with the libeatmydata package maintainer
1000 Mattia Rizzolo to make it easier for everyone to get this installation
1001 speedup in Debian. Thanks to our cooperation There is now an
1002 eatmydata-udeb package in Debian testing and unstable, and simply
1003 enabling/installing it in debian-installer (d-i) is enough to get the
1004 quicker installations. It can be enabled using preseeding. The
1005 following untested kernel argument should do the trick:
</p
>
1007 <blockquote
><pre
>
1008 preseed/early_command=
"anna-install eatmydata-udeb
"
1009 </pre
></blockquote
>
1011 <p
>This should ask d-i to install the package inside the d-i
1012 environment early in the installation sequence. Having it installed
1013 in d-i in turn will make sure the relevant scripts are called just
1014 after debootstrap filled /target/ with the freshly installed Debian
1015 system to configure apt to run dpkg with eatmydata. This is enough to
1016 speed up the installation process. There is a proposal to
1017 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1018 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1019 tested its impact.
</p
>
1025 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1026 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1027 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1028 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1029 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1030 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1031 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1032 elever over det ganske land skal levere inn hvert år. Det mange ikke
1033 vet er at selv om de kommersielle alternativene
1034 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1035 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1036 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1037 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1038 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1039 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1040 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1041 nynorsk, og få den automatoversatt til det andre skriftspråket.
1042 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1043 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1044 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1045 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1046 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1047 teksten din i webskjemaet der.
1049 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1050 teknologien kan du enten installere pakken
1051 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1052 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1053 api.apertium.org. Se
1054 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1055 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1056 denne teksten som ble skrevet på bokmål over maskinoversatt til
1061 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1062 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1063 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1064 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1065 veit er at sjølv om dei kommersielle alternativa
1066 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1067 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1068 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1069 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1070 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1071 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1072 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1073 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1074 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1075 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1076 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1077 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1078 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1079 teksta di i *webskjemaet der.
1081 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1082 teknologien kan du anten installera pakken
1083 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1084 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1085 *api.*apertium.org. Sjå
1086 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1087 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1088 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1094 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1095 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1096 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1097 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1098 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1099 profiler able to run benchmarking experiments on the instrumented
1100 multi-threaded program, finally
1101 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1102 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1104 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1105 blogged about the coz tool
</a
> in August working with upstream to make
1106 it suitable for Debian. There are still issues with clang
1107 compatibility, inline assembly only working x86 and minimized
1108 JavaScript libraries.
</p
>
1110 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1112 <p
><blockquote
>
1113 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1114 </blockquote
></p
>
1116 <p
>This will produce a profile.coz file in the current working
1117 directory with the profiling information. This is then given to a
1118 JavaScript application provided in the package and available from
1119 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1120 To start the local copy, invoke it in a browser like this:
</p
>
1122 <p
><blockquote
>
1123 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1124 </blockquote
></p
>
1126 <p
>See the project home page and the
1127 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1128 ;login: article on Coz
</a
> for more information on how it is
1134 <title>My own self balancing Lego Segway
</title>
1135 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1137 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1138 <description><p
>A while back I received a Gyro sensor for the NXT
1139 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1140 present. It had been on my wishlist for a while, because I wanted to
1141 build a Segway like balancing lego robot. I had already built
1142 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1143 robot
</a
> with the kids, using the light/color sensor included in the
1144 NXT kit as the balance sensor, but it was not working very well. It
1145 could balance for a while, but was very sensitive to the light
1146 condition in the room and the reflective properties of the surface and
1147 would fall over after a short while. I wanted something more robust,
1149 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1150 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1151 wishlist for some years before it suddenly showed up as a gift from my
1152 loved ones. :)
</p
>
1154 <p
>Unfortunately I have not had time to sit down and play with it
1155 since then. But that changed some days ago, when I was searching for
1156 lego segway information and came across a recipe from HiTechnic for
1158 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1159 HTWay
</a
>, a segway like balancing robot. Build instructions and
1160 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1161 code
</a
> was included, so it was just a question of putting it all
1162 together. And thanks to the great work of many Debian developers, the
1163 compiler needed to build the source for the NXT is already included in
1164 Debian, so I was read to go in less than an hour. The resulting robot
1165 do not look very impressive in its simplicity:
</p
>
1167 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1169 <p
>Because I lack the infrared sensor used to control the robot in the
1170 design from HiTechnic, I had to comment out the last task
1171 (taskControl). I simply placed /* and */ around it get the program
1172 working without that sensor present. Now it balances just fine until
1173 the battery status run low:
</p
>
1175 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1176 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1177 </video
></p
>
1179 <p
>Now we would like to teach it how to follow a line and take remote
1180 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1182 <p
>If you, like me, love LEGO and want to make sure we find the tools
1183 they need to work with LEGO in Debian and all our derivative
1184 distributions like Ubuntu, check out
1185 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1186 project page
</a
> and join the Debian LEGO team. Personally I own a
1187 RCX and NXT controller (no EV3), and would like to make sure the
1188 Debian tools needed to program the systems I own work as they
1194 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1195 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1196 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1197 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1198 <description><p
>In July
1199 <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
1200 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1201 the ability to receive SMS messages (aka without a cell phone). It is
1202 time to share some experiences and provide an updated setup.
</p
>
1204 <p
>The Signal app have worked fine for several months now, and I use
1205 it regularly to chat with my loved ones. I had a major snag at the
1206 end of my summer vacation, when the the app completely forgot my
1207 setup, identity and keys. The reason behind this major mess was
1208 running out of disk space. To avoid that ever happening again I have
1209 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1210 roll back to an earlier version if the files are wiped by mistake. I
1211 had to use it once after introducing the git backup. When rolling
1212 back to an earlier version, one need to use the
'reset session
' option
1213 in Signal to get going, and notify the people you talk with about the
1214 problem. I assume there is some sequence number tracking in the
1215 protocol to detect rollback attacks. The git repository is rather big
1216 (
674 MiB so far), but I have not tried to figure out if some of the
1217 content can be added to a .gitignore file due to lack of spare
1220 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1221 make it impossible to send messages using Signal. I could still
1222 receive them, but had to patch the code with a new timestamp to send.
1223 I believe the timeout is added by the developers to force people to
1224 upgrade to the latest version of the app, even when there is no
1225 protocol changes, to reduce the version skew among the user base and
1226 thus try to keep the number of support requests down.
</p
>
1228 <p
>Since my original recipe, the Signal source code changed slightly,
1229 making the old patch fail to apply cleanly. Below is an updated
1230 patch, including the shell wrapper I use to start Signal. The
1231 original version required a new user to locate the JavaScript console
1232 and call a function from there. I got help from a friend with more
1233 JavaScript knowledge than me to modify the code to provide a GUI
1234 button instead. This mean that to get started you just need to run
1235 the wrapper and click the
'Register without mobile phone
' to get going
1236 now. I
've also modified the timeout code to always set it to
90 days
1237 in the future, to avoid having to patch the code regularly.
</p
>
1239 <p
>So, the updated recipe for Debian Jessie:
</p
>
1243 <li
>First, install required packages to get the source code and the
1244 browser you need. Signal only work with Chrome/Chromium, as far as I
1245 know, so you need to install it.
1248 apt install git tor chromium
1249 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1250 </pre
></li
>
1252 <li
>Modify the source code using command listed in the the patch
1253 block below.
</li
>
1255 <li
>Start Signal using the run-signal-app wrapper (for example using
1256 <tt
>`pwd`/run-signal-app
</tt
>).
1258 <li
>Click on the
'Register without mobile phone
', will in a phone
1259 number you can receive calls to the next minute, receive the
1260 verification code and enter it into the form field and press
1261 'Register
'. Note, the phone number you use will be user Signal
1262 username, ie the way others can find you on Signal.
</li
>
1264 <li
>You can now use Signal to contact others. Note, new contacts do
1265 not show up in the contact list until you restart Signal, and there is
1266 no way to assign names to Contacts. There is also no way to create or
1267 update chat groups. I suspect this is because the web app do not have
1268 a associated contact database.
</li
>
1272 <p
>I am still a bit uneasy about using Signal, because of the way its
1273 main author moxie0 reject federation and accept dependencies to major
1274 corporations like Google (part of the code is fetched from Google) and
1275 Amazon (the central coordination point is owned by Amazon). See for
1277 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1278 LibreSignal issue tracker
</a
> for a thread documenting the authors
1279 view on these issues. But the network effect is strong in this case,
1280 and several of the people I want to communicate with already use
1281 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1282 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1283 laptop
</a
>? It already work on Windows and Android, and is included
1284 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1285 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1286 working on Debian Stable.
</p
>
1288 <p
>Anyway, this is the patch I apply to the Signal code to get it
1289 working. It switch to the production servers, disable to timeout,
1290 make registration easier and add the shell wrapper:
</p
>
1293 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1294 diff --git a/js/background.js b/js/background.js
1295 index
24b4c1d.
.579345f
100644
1296 --- a/js/background.js
1297 +++ b/js/background.js
1302 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1303 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1304 var SERVER_PORTS = [
80,
4433,
8443];
1305 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1306 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1307 var messageReceiver;
1308 window.getSocketStatus = function() {
1309 if (messageReceiver) {
1310 diff --git a/js/expire.js b/js/expire.js
1311 index
639aeae..beb91c3
100644
1316 'use strict
';
1317 - var BUILD_EXPIRATION =
0;
1318 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1320 window.extension = window.extension || {};
1322 diff --git a/js/views/install_view.js b/js/views/install_view.js
1323 index
7816f4f.
.1d6233b
100644
1324 --- a/js/views/install_view.js
1325 +++ b/js/views/install_view.js
1328 'click .step1
': this.selectStep.bind(this,
1),
1329 'click .step2
': this.selectStep.bind(this,
2),
1330 -
'click .step3
': this.selectStep.bind(this,
3)
1331 +
'click .step3
': this.selectStep.bind(this,
3),
1332 +
'click .callreg
': function() { extension.install(
'standalone
') },
1335 clearQR: function() {
1336 diff --git a/options.html b/options.html
1337 index dc0f28e.
.8d709f6
100644
1341 &lt;div class=
'nav
'>
1342 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1343 &lt;p
>{{ installTagline }}
&lt;/p
>
1344 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1345 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1346 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1349 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1350 &lt;span class=
'dot step2
'>&lt;/span
>
1351 &lt;span class=
'dot step3
'>&lt;/span
>
1352 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1353 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1359 +userdata=
"`pwd`/userdata
"
1360 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1361 + (cd $userdata
&& git init)
1363 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1365 + --proxy-server=
"socks://localhost:
9050" \
1366 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1368 chmod a+rx run-signal-app
1371 <p
>As usual, if you use Bitcoin and want to show your support of my
1372 activities, please send Bitcoin donations to my address
1373 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1378 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1379 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1380 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1381 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1382 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1383 system
</a
> provide a practical and easy way to figure out which
1384 packages support the hardware in a given machine. The command line
1385 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1386 convenient way to list and install packages relevant for the current
1387 hardware during system installation, both user space packages and
1388 firmware packages. The GUI background daemon on the other hand provide
1389 a pop-up proposing to install packages when a new dongle is inserted
1390 while using the computer. For example, if you plug in a smart card
1391 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1392 that package isn
't already installed, and if you plug in a USB video
1393 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1394 cheese is currently missing. This already work just fine.
</p
>
1396 <p
>But Isenkram depend on a database mapping from hardware IDs to
1397 package names. When I started no such database existed in Debian, so
1398 I made my own data set and included it with the isenkram package and
1399 made isenkram fetch the latest version of this database from git using
1400 http. This way the isenkram users would get updated package proposals
1401 as soon as I learned more about hardware related packages.
</p
>
1403 <p
>The hardware is identified using modalias strings. The modalias
1404 design is from the Linux kernel where most hardware descriptors are
1405 made available as a strings that can be matched using filename style
1406 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1407 identifiers.
</p
>
1409 <p
>The downside to the Isenkram specific database is that there is no
1410 information about relevant distribution / Debian version, making
1411 isenkram propose obsolete packages too. But along came AppStream, a
1412 cross distribution mechanism to store and collect metadata about
1413 software packages. When I heard about the proposal, I contacted the
1414 people involved and suggested to add a hardware matching rule using
1415 modalias strings in the specification, to be able to use AppStream for
1416 mapping hardware to packages. This idea was accepted and AppStream is
1417 now a great way for a package to announce the hardware it support in a
1418 distribution neutral way. I wrote
1419 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1420 recipe on how to add such meta-information
</a
> in a blog post last
1421 December. If you have a hardware related package in Debian, please
1422 announce the relevant hardware IDs using AppStream.
</p
>
1424 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1425 RCX or NXT unit, announce this support using AppStream. The effect is
1426 that when you insert such LEGO robot controller into your Debian
1427 machine, Isenkram will propose to install the packages needed to get
1428 it working. The intention is that this should allow the local user to
1429 start programming his robot controller right away without having to
1430 guess what packages to use or which permissions to fix.
</p
>
1432 <p
>But when I sat down with my son the other day to program our NXT
1433 unit using his Debian Stretch computer, I discovered something
1434 annoying. The local console user (ie my son) did not get access to
1435 the USB device for programming the unit. This used to work, but no
1436 longer in Jessie and Stretch. After some investigation and asking
1437 around on #debian-devel, I discovered that this was because udev had
1438 changed the mechanism used to grant access to local devices. The
1439 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1440 no longer applied, because LDAP users no longer was added to the
1441 plugdev group during login. Michael Biebl told me that this method
1442 was obsolete and the new method used ACLs instead. This was good
1443 news, as the plugdev mechanism is a mess when using a remote user
1444 directory like LDAP. Using ACLs would make sure a user lost device
1445 access when she logged out, even if the user left behind a background
1446 process which would retain the plugdev membership with the ConsoleKit
1447 setup. Armed with this knowledge I moved on to fix the access problem
1448 for the LEGO Mindstorms related packages.
</p
>
1450 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1451 applied directly for a device, or is applied in
1452 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1453 LEGO Mindstorms udev rules did not have a class, I decided to add the
1454 tag directly in the udev rules files included in the packages. Here
1455 is one example. For the nqc C compiler for the RCX, the
1456 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1458 <p
><pre
>
1459 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1460 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1461 </pre
></p
>
1463 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1464 packages using plugdev in their /lib/udev/rules.d/ files should be
1465 changed to use this tag (either directly or indirectly via
1466 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1467 to detect this?
</p
>
1469 <p
>I
've been unable to find good documentation on the uaccess feature.
1470 It is unclear to me if the uaccess tag is an internal implementation
1471 detail like the udev-acl tag used by
1472 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1473 indirect method is the preferred way. Michael
1474 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1475 documentation from the systemd project
</a
> and I hope it will make
1476 this clearer. For now I use the generic classes when they exist and
1477 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1478 directly if no such class exist.
</p
>
1480 <p
>To learn more about the isenkram system, please check out
1481 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1482 blog posts tagged isenkram
</a
>.
</p
>
1484 <p
>To help out making life for LEGO constructors in Debian easier,
1485 please join us on our IRC channel
1486 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1487 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1488 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1489 list is not yet created, but we are working on it. :)
</p
>
1491 <p
>As usual, if you use Bitcoin and want to show your support of my
1492 activities, please send Bitcoin donations to my address
1493 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1498 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1499 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1500 <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>
1501 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1502 <description><p
>In April we
1503 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1504 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1505 how to set up and administrate a Debian system. Today I am happy to
1506 report that the first draft is now publicly available. You can find
1507 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1508 Administrator
's Handbook page
</a
> (under Other languages). The first
1509 eight chapters have a first draft translation, and we are working on
1510 proofreading the content. If you want to help out, please start
1512 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1513 hosted weblate project page
</a
>, and get in touch using
1514 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1515 translators mailing list
</a
>. Please also check out
1516 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1517 contributors
</a
>. A good way to contribute is to proofread the text
1518 and update weblate if you find errors.
</p
>
1520 <p
>Our goal is still to make the Norwegian book available on paper as well as
1521 electronic form.
</p
>
1526 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1527 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1528 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1529 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1530 <description><p
>This summer, I read a great article
1531 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1532 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1533 how to profile multi-threaded programs. It presented a system for
1534 profiling software by running experiences in the running program,
1535 testing how run time performance is affected by
"speeding up
" parts of
1536 the code to various degrees compared to a normal run. It does this by
1537 slowing down parallel threads while the
"faster up
" code is running
1538 and measure how this affect processing time. The processing time is
1539 measured using probes inserted into the code, either using progress
1540 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1541 can also measure unmodified code by measuring complete the program
1542 runtime and running the program several times instead.
</p
>
1544 <p
>The project and presentation was so inspiring that I would like to
1545 get the system into Debian. I
1546 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1547 a WNPP request for it
</a
> and contacted upstream to try to make the
1548 system ready for Debian by sending patches. The build process need to
1549 be changed a bit to avoid running
'git clone
' to get dependencies, and
1550 to include the JavaScript web page used to visualize the collected
1551 profiling information included in the source package.
1552 But I expect that should work out fairly soon.
</p
>
1554 <p
>The way the system work is fairly simple. To run an coz experiment
1555 on a binary with debug symbols available, start the program like this:
1557 <p
><blockquote
><pre
>
1558 coz run --- program-to-run
1559 </pre
></blockquote
></p
>
1561 <p
>This will create a text file profile.coz with the instrumentation
1562 information. To show what part of the code affect the performance
1563 most, use a web browser and either point it to
1564 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1565 or use the copy from git (in the gh-pages branch). Check out this web
1566 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
1567 profiling more useful you include
&lt;coz.h
&gt; and insert the
1568 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1569 code, rebuild and run the profiler. This allow coz to do more
1570 targeted experiments.
</p
>
1572 <p
>A video published by ACM
1573 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1574 Coz profiler
</a
> is available from Youtube. There is also a paper
1575 from the
25th Symposium on Operating Systems Principles available
1577 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1578 finding code that counts with causal profiling
</a
>.
</p
>
1580 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1581 for Coz is available from github. It will only build with clang
1583 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1584 feature missing in GCC
</a
>, but I
've submitted
1585 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1586 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1588 <p
>Please get in touch if you, like me, would like to see this piece
1589 of software in Debian. I would very much like some help with the
1590 packaging effort, as I lack the in depth knowledge on how to package
1591 C++ libraries.
</p
>
1596 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1597 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1599 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1600 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1601 to be a slight challenge. Here is the recipe if I ever need to do it
1602 again. It all started by me wanting to try the recipe to set up
1603 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1604 hardened Android installation
</a
> from the Tor project blog on a
1605 device I had access to. It is a old mobile phone with a broken
1606 microphone The initial idea had been to just
1607 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1608 CyanogenMod on it
</a
>, but did not quite find time to start on it
1609 until a few days ago.
</p
>
1611 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1612 loader (press volume down and power at the same time), (
2) select
1613 'fastboot
' before (
3) connecting the device via USB to a Linux
1614 machine, (
4) request the device identifier token by running
'fastboot
1615 oem get_identifier_token
', (
5) request the device unlocking key using
1616 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1617 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1619 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1620 or newer, and the device I was working on had
2.00.0027. This
1621 apparently can be easily fixed by downloading a Windows program and
1622 running it on your Windows machine, if you accept the terms Microsoft
1623 require you to accept to use Windows - which I do not. So I had to
1624 come up with a different approach. I got a lot of help from AndyCap
1625 on #nuug, and would not have been able to get this working without
1628 <p
>First I needed to extract the hboot firmware from
1629 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1630 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1631 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1632 project named unruu
</a
> using libunshield. The unshield tool did not
1633 recognise the file format, but unruu worked and extracted rom.zip,
1634 containing the new hboot firmware and a text file describing which
1635 devices it would work for.
</p
>
1637 <p
>Next, I needed to get the new firmware into the device. For this I
1638 followed some instructions
1639 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1640 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1641 machine with Debian testing:
</p
>
1643 <p
><pre
>
1644 adb reboot-bootloader
1645 fastboot oem rebootRUU
1646 fastboot flash zip rom.zip
1647 fastboot flash zip rom.zip
1649 </pre
></p
>
1651 <p
>The flash command apparently need to be done twice to take effect,
1652 as the first is just preparations and the second one do the flashing.
1653 The adb command is just to get to the boot loader menu, so turning the
1654 device on while holding volume down and the power button should work
1657 <p
>With the new hboot version in place I could start following the
1658 instructions on the HTC developer web site. I got the device token
1659 like this:
</p
>
1661 <p
><pre
>
1662 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1665 <p
>And once I got the unlock code via email, I could use it like
1668 <p
><pre
>
1669 fastboot flash unlocktoken Unlock_code.bin
1670 </pre
></p
>
1672 <p
>And with that final step in place, the phone was unlocked and I
1673 could start stuffing the software of my own choosing into the device.
1674 So far I only inserted a replacement recovery image to wipe the phone
1675 before I start. We will see what happen next. Perhaps I should
1676 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1681 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1682 <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>
1683 <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>
1684 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1685 <description><p
>For a while now, I have wanted to test
1686 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1687 said to provide end to end encrypted communication and several of my
1688 friends and family are already using it. As I by choice do not own a
1689 mobile phone, this proved to be harder than expected. And I wanted to
1690 have the source of the client and know that it was the code used on my
1691 machine. But yesterday I managed to get it working. I used the
1692 Github source, compared it to the source in
1693 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1694 Signal Chrome app
</a
> available from the Chrome web store, applied
1695 patches to use the production Signal servers, started the app and
1696 asked for the hidden
"register without a smart phone
" form. Here is
1697 the recipe how I did it.
</p
>
1699 <p
>First, I fetched the Signal desktop source from Github, using
1702 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1705 <p
>Next, I patched the source to use the production servers, to be
1706 able to talk to other Signal users:
</p
>
1709 cat
&lt;
&lt;EOF | patch -p0
1710 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1711 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1712 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1717 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1718 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1719 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1720 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1721 var messageReceiver;
1722 window.getSocketStatus = function() {
1723 if (messageReceiver) {
1724 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1725 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1726 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1729 'use strict
';
1730 - var BUILD_EXPIRATION =
0;
1731 + var BUILD_EXPIRATION =
1474492690000;
1733 window.extension = window.extension || {};
1738 <p
>The first part is changing the servers, and the second is updating
1739 an expiration timestamp. This timestamp need to be updated regularly.
1740 It is set
90 days in the future by the build process (Gruntfile.js).
1741 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1743 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1744 script to launch Signal in Chromium.
</p
>
1751 --proxy-server=
"socks://localhost:
9050" \
1752 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1755 <p
> The script start the app and configure Chromium to use the Tor
1756 SOCKS5 proxy to make sure those controlling the Signal servers (today
1757 Amazon and Whisper Systems) as well as those listening on the lines
1758 will have a harder time location my laptop based on the Signal
1759 connections if they use source IP address.
</p
>
1761 <p
>When the script starts, one need to follow the instructions under
1762 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1763 repository. I right clicked on the Signal window to get up the
1764 Chromium debugging tool, visited the
'Console
' tab and wrote
1765 'extension.install(
"standalone
")
' on the console prompt to get the
1766 registration form. Then I entered by land line phone number and
1767 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1768 repeated the verification code three times. After entering the number
1769 into the verification code field in the form, I could start using
1770 Signal from my laptop.
1772 <p
>As far as I can tell, The Signal app will leak who is talking to
1773 whom and thus who know who to those controlling the central server,
1774 but such leakage is hard to avoid with a centrally controlled server
1775 setup. It is something to keep in mind when using Signal - the
1776 content of your chats are harder to intercept, but the meta data
1777 exposing your contact network is available to people you do not know.
1778 So better than many options, but not great. And sadly the usage is
1779 connected to my land line, thus allowing those controlling the server
1780 to associate it to my home and person. I would prefer it if only
1781 those I knew could tell who I was on Signal. There are options
1782 avoiding such information leakage, but most of my friends are not
1783 using them, so I am stuck with Signal for now.
</p
>
1785 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1787 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1788 and updated recipe for using the Signal app without a mobile
1789 phone
</a
>.
</p
>
1794 <title>The new
"best
" multimedia player in Debian?
</title>
1795 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1796 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1797 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1798 <description><p
>When I set out a few weeks ago to figure out
1799 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1800 multimedia player in Debian claimed to support most file formats /
1801 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1802 the various players claimed support for. The range was from
55 to
130
1803 MIME types. I suspect most media formats are supported by all
1804 players, but this is not really reflected in the MimeTypes values in
1805 their desktop files. There are probably also some bogus MIME types
1806 listed, but it is hard to identify which one this is.
</p
>
1808 <p
>Anyway, in the mean time I got in touch with upstream for some of
1809 the players suggesting to add more MIME types to their desktop files,
1810 and decided to spend some time myself improving the situation for my
1811 favorite media player VLC. The fixes for VLC entered Debian unstable
1812 yesterday. The complete list of MIME types can be seen on the
1813 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1814 player MIME type support status
</a
> Debian wiki page.
</p
>
1816 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1817 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1818 kmplayer. I am sure some of the other players desktop files support
1819 several of the formats currently listed as working only with vlc,
1820 toten and parole.
</p
>
1822 <p
>A sad observation is that only
14 MIME types are listed as
1823 supported by all the tested multimedia players in Debian in their
1824 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1825 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1826 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1827 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1828 it sad that video/ogg and video/webm is not supported by all the media
1829 players in Debian. As far as I can tell, all of them can handle both
1835 <title>A program should be able to open its own files on Linux
</title>
1836 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1837 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1838 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1839 <description><p
>Many years ago, when koffice was fresh and with few users, I
1840 decided to test its presentation tool when making the slides for a
1841 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1842 wrote the first draft of the slides, saved the result and went to bed
1843 the day before I would give the talk. The next day I took a plane to
1844 the location where the meeting should take place, and on the plane I
1845 started up koffice again to polish the talk a bit, only to discover
1846 that kpresenter refused to load its own data file. I cursed a bit and
1847 started making the slides again from memory, to have something to
1848 present when I arrived. I tested that the saved files could be
1849 loaded, and the day seemed to be rescued. I continued to polish the
1850 slides until I suddenly discovered that the saved file could no longer
1851 be loaded into kpresenter. In the end I had to rewrite the slides
1852 three times, condensing the content until the talk became shorter and
1853 shorter. After the talk I was able to pinpoint the problem
&ndash;
1854 kpresenter wrote inline images in a way itself could not understand.
1855 Eventually that bug was fixed and kpresenter ended up being a great
1856 program to make slides. The point I
'm trying to make is that we
1857 expect a program to be able to load its own data files, and it is
1858 embarrassing to its developers if it can
't.
</p
>
1860 <p
>Did you ever experience a program failing to load its own data
1861 files from the desktop file browser? It is not a uncommon problem. A
1862 while back I discovered that the screencast recorder
1863 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1864 browser would refuse to open. No video player claimed to understand
1865 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1866 returning the application/ogg MIME type, which no video player I had
1867 installed listed as a MIME type they would understand. I asked for
1868 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1869 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1870 several video players to add video/ogg to their desktop files, to give
1871 the file browser an idea what to do about Ogg Theora files. After a
1872 while, the desktop file browsers in Debian started to handle the
1873 output from gtk-recordmydesktop properly.
</p
>
1875 <p
>But history repeats itself. A few days ago I tested the music
1876 system Rosegarden again, and I discovered that the KDE and xfce file
1877 browsers did not know what to do with the Rosegarden project files
1878 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1879 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1880 included in the next upload. To increase the chance of me remembering
1881 how to fix the problem next time some program fail to load its files
1882 from the file browser, here are some notes on how to fix it.
</p
>
1884 <p
>The file browsers in Debian in general operates on MIME types.
1885 There are two sources for the MIME type of a given file. The output from
1886 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1887 shared MIME type registry (under /usr/share/mime/). The file MIME
1888 type is mapped to programs supporting the MIME type, and this
1889 information is collected from
1890 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1891 desktop files
</a
> available in /usr/share/applications/. If there is
1892 one desktop file claiming support for the MIME type of the file, it is
1893 activated when asking to open a given file. If there are more, one
1894 can normally select which one to use by right-clicking on the file and
1895 selecting the wanted one using
'Open with
' or similar. In general
1896 this work well. But it depend on each program picking a good MIME
1898 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1899 MIME type registered with IANA
</a
>), file and/or the shared MIME
1900 registry recognizing the file and the desktop file to list the MIME
1901 type in its list of supported MIME types.
</p
>
1903 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1904 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1905 Shared MIME database
</a
> look like this:
</p
>
1907 <p
><blockquote
><pre
>
1908 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1909 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1910 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1911 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1912 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1913 &lt;glob pattern=
"*.rg
"/
&gt;
1914 &lt;/mime-type
&gt;
1915 &lt;/mime-info
&gt;
1916 </pre
></blockquote
></p
>
1918 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1919 (it is a gzipped XML file). Note, it is much better to use an
1920 official MIME type registered with IANA than it is to make up ones own
1921 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1923 <p
>The desktop file of the rosegarden program failed to list
1924 audio/x-rosegarden in its list of supported MIME types, causing the
1925 file browsers to have no idea what to do with *.rg files:
</p
>
1927 <p
><blockquote
><pre
>
1928 % grep Mime /usr/share/applications/rosegarden.desktop
1929 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1930 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1932 </pre
></blockquote
></p
>
1934 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1935 MimeType= line.
</p
>
1937 <p
>If you run into a file which fail to open the correct program when
1938 selected from the file browser, please check out the output from
1939 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1940 MIME type is registered somewhere under /usr/share/mime/ and check
1941 that some desktop file under /usr/share/applications/ is claiming
1942 support for this MIME type. If not, please report a bug to have it
1948 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1949 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1951 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1952 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1953 system
</a
> is a user-focused solution in Debian for handling hardware
1954 related packages. The idea is to have a database of mappings between
1955 hardware and packages, and pop up a dialog suggesting for the user to
1956 install the packages to use a given hardware dongle. Some use cases
1957 are when you insert a Yubikey, it proposes to install the software
1958 needed to control it; when you insert a braille reader list it
1959 proposes to install the packages needed to send text to the reader;
1960 and when you insert a ColorHug screen calibrator it suggests to
1961 install the driver for it. The system work well, and even have a few
1962 command line tools to install firmware packages and packages for the
1963 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1965 <p
>The system was initially written using aptdaemon, because I found
1966 good documentation and example code on how to use it. But aptdaemon
1967 is going away and is generally being replaced by
1968 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1969 so Isenkram needed a rewrite. And today, thanks to the great patch
1970 from my college Sunil Mohan Adapa in the FreedomBox project, the
1971 rewrite finally took place. I
've just uploaded a new version of
1972 Isenkram into Debian Unstable with the patch included, and the default
1973 for the background daemon is now to use PackageKit. To check it out,
1974 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1975 and see if it is recognised.
</p
>
1977 <p
>If you want to know what kind of packages isenkram would propose for
1978 the machine it is running on, you can check out the isenkram-lookup
1979 program. This is what it look like on a Thinkpad X230:
</p
>
1981 <p
><blockquote
><pre
>
1997 </pre
></blockquote
></p
>
1999 <p
>The hardware mappings come from several places. The preferred way
2000 is for packages to announce their hardware support using
2001 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2002 cross distribution appstream system
</a
>.
2004 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2005 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2010 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2011 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2012 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2013 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2014 <description><p
>Yesterday I updated the
2015 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2016 package in Debian
</a
> with a few patches sent to me by skilled and
2017 enterprising users. There were some nice user and visible changes.
2018 First of all, both desktop menu entries now work. A design flaw in
2019 one of the script made the history graph fail to show up (its PNG was
2020 dumped in ~/.xsession-errors) if no controlling TTY was available.
2021 The script worked when called from the command line, but not when
2022 called from the desktop menu. I changed this to look for a DISPLAY
2023 variable or a TTY before deciding where to draw the graph, and now the
2024 graph window pop up as expected.
</p
>
2026 <p
>The next new feature is a discharge rate estimator in one of the
2027 graphs (the one showing the last few hours). New is also the user of
2028 colours showing charging in blue and discharge in red. The percentages
2029 of this graph is relative to last full charge, not battery design
2032 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2034 <p
>The other graph show the entire history of the collected battery
2035 statistics, comparing it to the design capacity of the battery to
2036 visualise how the battery life time get shorter over time. The red
2037 line in this graph is what the previous graph considers
100 percent:
2039 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2041 <p
>In this graph you can see that I only charge the battery to
80
2042 percent of last full capacity, and how the capacity of the battery is
2043 shrinking. :(
</p
>
2045 <p
>The last new feature is in the collector, which now will handle
2046 more hardware models. On some hardware, Linux power supply
2047 information is stored in /sys/class/power_supply/ACAD/, while the
2048 collector previously only looked in /sys/class/power_supply/AC/. Now
2049 both are checked to figure if there is power connected to the
2052 <p
>If you are interested in how your laptop battery is doing, please
2054 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2055 in Debian unstable, or rebuild it on Jessie to get it working on
2056 Debian stable. :) The upstream source is available from
<a
2057 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2058 Patches are very welcome.
</p
>
2060 <p
>As usual, if you use Bitcoin and want to show your support of my
2061 activities, please send Bitcoin donations to my address
2062 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2067 <title>Debian now with ZFS on Linux included
</title>
2068 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2069 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2070 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2071 <description><p
>Today, after many years of hard work from many people,
2072 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2073 Debian. The package status can be seen on
2074 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2075 for zfs-linux
</a
>. and
2076 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2077 team status page
</a
>. If you want to help out, please join us.
2078 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2079 source code
</a
> is available via git on Alioth. It would also be
2080 great if you could help out with
2081 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2082 it is an important piece of the puzzle to get ZFS working.
</p
>
2087 <title>What is the best multimedia player in Debian?
</title>
2088 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2090 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2091 <description><p
><strong
>Where I set out to figure out which multimedia player in
2092 Debian claim support for most file formats.
</strong
></p
>
2094 <p
>A few years ago, I had a look at the media support for Browser
2095 plugins in Debian, to get an idea which plugins to include in Debian
2096 Edu. I created a script to extract the set of supported MIME types
2097 for each plugin, and used this to find out which multimedia browser
2098 plugin supported most file formats / media types.
2099 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2100 result
</a
> can still be seen on the Debian wiki, even though it have
2101 not been updated for a while. But browser plugins are less relevant
2102 these days, so I thought it was time to look at standalone
2105 <p
>A few days ago I was tired of VLC not being listed as a viable
2106 player when I wanted to play videos from the Norwegian National
2107 Broadcasting Company, and decided to investigate why. The cause is a
2108 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2109 desktop file
</a
>. In the process I wrote a script to compare the set
2110 of MIME types announced in the desktop file and the browser plugin,
2111 only to discover that there is quite a large difference between the
2112 two for VLC. This discovery made me dig up the script I used to
2113 compare browser plugins, and adjust it to compare desktop files
2114 instead, to try to figure out which multimedia player in Debian
2115 support most file formats.
</p
>
2117 <p
>The result can be seen on the Debian Wiki, as
2118 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2119 table listing all MIME types supported by one of the packages included
2120 in the table
</a
>, with the package supporting most MIME types being
2121 listed first in the table.
</p
>
2123 </p
>The best multimedia player in Debian? It is totem, followed by
2124 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2125 kmplayer. Time for the other players to update their announced MIME
2131 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2132 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2133 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2134 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2135 <description>A friend of mine made me aware of
2136 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2137 handheld computer which will be delivered with Debian preinstalled. I
2138 would love to get one of those for my birthday. :)
</p
>
2140 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2141 plugs and many others connectors, and include a full keyboard and a
5"
2142 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2143 day of battery life time, but I have not seen any independent tests
2144 confirming this. The vendor is still collecting preorders, and the
2145 last I heard last night was that
22 more orders were needed before
2146 production started.
</p
>
2148 <p
>As far as I know, this is the first handheld preinstalled with
2149 Debian. Please let me know if you know of any others. Is it the
2150 first computer being sold with Debian preinstalled?
</p
>
2155 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2156 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2157 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2158 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2159 <description><p
>During this weekends
2160 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2161 squashing party and developer gathering
</a
>, we decided to do our part
2162 to make sure there are good books about Debian available in Norwegian
2163 Bokmål, and got in touch with the people behind the
2164 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2165 project
</a
> to get started. If you want to help out, please start
2167 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2168 hosted weblate project page
</a
>, and get in touch using
2169 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2170 translators mailing list
</a
>. Please also check out
2171 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2172 contributors
</a
>.
</p
>
2174 <p
>The book is already available on paper in English, French and
2175 Japanese, and our goal is to get it available on paper in Norwegian
2176 Bokmål too. In addition to the paper edition, there are also EPUB and
2177 Mobi versions available. And there are incomplete translations
2178 available for many more languages.
</p
>
2183 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2184 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2185 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2186 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2187 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2188 packages in Debian, and was quite surprised with what I found. I use
2189 ZFS myself at home, but did not really expect many others to do so.
2190 But I might be wrong.
</p
>
2192 <p
>According to
2193 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2194 results for spl-linux
</a
>, there are
1019 Debian installations, or
2195 0.53% of the population, with the package installed. As far as I know
2196 the only use of the spl-linux package is as a support library for ZFS
2197 on Linux, so I use it here as proxy for measuring the number of ZFS
2198 installation on Linux in Debian. In the kFreeBSD variant of Debian
2199 the ZFS feature is already available, and there
2200 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2201 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2202 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2204 <p
>But even though the Debian project leader Lucas Nussbaum
2205 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2206 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2207 cleared, the package is still not in Debian. The package is again in
2208 the NEW queue. Several uploads have been rejected so far because the
2209 debian/copyright file was incomplete or wrong, but there is no reason
2210 to give up. The current status can be seen on
2211 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2212 team status page
</a
>, and
2213 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2214 source code
</a
> is available on Alioth.
</p
>
2216 <p
>As I want ZFS to be included in next version of Debian to make sure
2217 my home server can function in the future using only official Debian
2218 packages, and the current blocker is to get the debian/copyright file
2219 accepted by the FTP masters in Debian, I decided a while back to try
2220 to help out the team. This was the background for my blog post about
2221 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2222 updating and checking debian/copyright semi-automatically
</a
>, and I
2223 used the techniques I explored there to try to find any errors in the
2224 copyright file. It is not very easy to check every one of the around
2225 2000 files in the source package, but I hope we this time got it
2226 right. If you want to help out, check out the git source and try to
2227 find missing entries in the debian/copyright file.
</p
>
2232 <title>Full battery stats collector is now available in Debian
</title>
2233 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2234 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2235 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2236 <description><p
>Since this morning, the battery-stats package in Debian include an
2237 extended collector that will collect the complete battery history for
2238 later processing and graphing. The original collector store the
2239 battery level as percentage of last full level, while the new
2240 collector also record battery vendor, model, serial number, design
2241 full level, last full level and current battery level. This make it
2242 possible to predict the lifetime of the battery as well as visualise
2243 the energy flow when the battery is charging or discharging.
</p
>
2245 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2246 in the version
0.5.1 package in unstable. Get the new battery level graph
2247 and lifetime prediction by running:
2249 <p
><pre
>
2250 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2251 </pre
></p
>
2253 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2255 <p
>The flow in/out of the battery can be seen by running (no menu
2256 entry yet):
</p
>
2258 <p
><pre
>
2259 /usr/share/battery-stats/battery-stats-graph-flow
2260 </pre
></p
>
2262 <p
>I
'm not quite happy with the way the data is visualised, at least
2263 when there are few data points. The graphs look a bit better with a
2264 few years of data.
</p
>
2266 <p
>A while back one important feature I use in the battery stats
2267 collector broke in Debian. The scripts in
2268 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2269 suspect it happened when Jessie started using systemd, but I do not
2270 know. The issue is reported as
2271 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2272 pm-utils. I managed to work around it by adding an udev rule to call
2273 the collector script every time the power connector is connected and
2274 disconnected. With this fix in place it was finally time to make a
2275 new release of the package, and get it into Debian.
</p
>
2277 <p
>If you are interested in how your laptop battery is doing, please
2279 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2280 in Debian unstable, or rebuild it on Jessie to get it working on
2281 Debian stable. :) The upstream source is available from
2282 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2283 As always, patches are very welcome.
</p
>
2288 <title>Making battery measurements a little easier in Debian
</title>
2289 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2290 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2291 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2292 <description><p
>Back in September, I blogged about
2293 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2294 system I wrote to collect statistics about my laptop battery
</a
>, and
2295 how it showed the decay and death of this battery (now replaced). I
2296 created a simple deb package to handle the collection and graphing,
2297 but did not want to upload it to Debian as there were already
2298 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2299 package in Debian
</a
> that should do the same thing, and I did not see
2300 a point of uploading a competing package when battery-stats could be
2301 fixed instead. I reported a few bugs about its non-function, and
2302 hoped someone would step in and fix it. But no-one did.
</p
>
2304 <p
>I got tired of waiting a few days ago, and took matters in my own
2305 hands. The end result is that I am now the new upstream developer of
2306 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2307 battery-stats in Debian, and the package in Debian unstable is finally
2308 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2309 information provided by the Linux kernel. If you install the
2310 battery-stats package from unstable now, you will be able to get a
2311 graph of the current battery fill level, to get some idea about the
2312 status of the battery. The source package build and work just fine in
2313 Debian testing and stable (and probably oldstable too, but I have not
2314 tested). The default graph you get for that system look like this:
</p
>
2316 <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
>
2318 <p
>My plans for the future is to merge my old scripts into the
2319 battery-stats package, as my old scripts collected a lot more details
2320 about the battery. The scripts are merged into the upstream
2321 battery-stats git repository already, but I am not convinced they work
2322 yet, as I changed a lot of paths along the way. Will have to test a
2323 bit more before I make a new release.
</p
>
2325 <p
>I will also consider changing the file format slightly, as I
2326 suspect the way I combine several values into one field might make it
2327 impossible to know the type of the value when using it for processing
2328 and graphing.
</p
>
2330 <p
>If you would like I would like to keep an close eye on your laptop
2331 battery, check out the battery-stats package in
2332 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2334 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2335 I would love some help to improve the system further.
</p
>
2340 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2341 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2342 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2343 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2344 <description><p
>Making packages for Debian requires quite a lot of attention to
2345 details. And one of the details is the content of the
2346 debian/copyright file, which should list all relevant licenses used by
2347 the code in the package in question, preferably in
2348 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2349 readable DEP5 format
</a
>.
</p
>
2351 <p
>For large packages with lots of contributors it is hard to write
2352 and update this file manually, and if you get some detail wrong, the
2353 package is normally rejected by the ftpmasters. So getting it right
2354 the first time around get the package into Debian faster, and save
2355 both you and the ftpmasters some work.. Today, while trying to figure
2356 out what was wrong with
2357 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2358 zfsonlinux copyright file
</a
>, I decided to spend some time on
2359 figuring out the options for doing this job automatically, or at least
2360 semi-automatically.
</p
>
2362 <p
>Lucikly, there are at least two tools available for generating the
2363 file based on the code in the source package,
2364 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2365 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2366 not sure which one of them came first, but both seem to be able to
2367 create a sensible draft file. As far as I can tell, none of them can
2368 be trusted to get the result just right, so the content need to be
2369 polished a bit before the file is OK to upload. I found the debmake
2371 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2372 blog posts from
2014</a
>.
2374 <p
>To generate using debmake, use the -cc option:
2376 <p
><pre
>
2377 debmake -cc
> debian/copyright
2378 </pre
></p
>
2380 <p
>Note there are some problems with python and non-ASCII names, so
2381 this might not be the best option.
</p
>
2383 <p
>The cme option is based on a config parsing library, and I found
2385 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2386 blog post from
2015</a
>. To generate using cme, use the
'update
2387 dpkg-copyright
' option:
2389 <p
><pre
>
2390 cme update dpkg-copyright
2391 </pre
></p
>
2393 <p
>This will create or update debian/copyright. The cme tool seem to
2394 handle UTF-
8 names better than debmake.
</p
>
2396 <p
>When the copyright file is created, I would also like some help to
2397 check if the file is correct. For this I found two good options,
2398 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2399 to focus on license types and file matching, and is able to detect
2400 ineffective blocks in the copyright file. The latter reports missing
2401 copyright holders and years, but was confused by inconsistent license
2402 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2403 fix all issues reported by them before uploading. But I do not know
2404 if the tools and the ftpmasters agree on what is important to fix in a
2405 copyright file, so the package might still be rejected.
</p
>
2407 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2408 will read through the source and try to find all copyright statements.
2409 It is not comparing the result to the content of debian/copyright, but
2410 can be useful when verifying the content of the copyright file.
</p
>
2412 <p
>Are you aware of better tools in Debian to create and update
2413 debian/copyright file. Please let me know, or blog about it on
2414 planet.debian.org.
</p
>
2416 <p
>As usual, if you use Bitcoin and want to show your support of my
2417 activities, please send Bitcoin donations to my address
2418 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2420 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2421 on how to use licensecheck and cdbs to create a draft copyright file
2423 <p
><pre
>
2424 licensecheck --copyright -r `find * -type f` | \
2425 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2426 </pre
></p
>
2428 <p
>He mentioned that he normally check the generated file into the
2429 version control system to make it easier to discover license and
2430 copyright changes in the upstream source. I will try to do the same
2431 with my packages in the future.
</p
>
2433 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2434 against using -quiet for new users, so I removed it from the proposed
2435 command line.
</p
>
2440 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2441 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2442 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2443 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2444 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2445 is taking shape in Debian, and one provided feature is a very
2446 convenient way to tell you which package to install to make a given
2447 firmware file available when the kernel is looking for it. This can
2448 be done using apt-file too, but that is for someone else to blog
2451 <p
>Here is a small recipe to find the package with a given firmware
2452 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2453 picked from the set of firmware announced using appstream in Debian
2454 unstable. In general you would be looking for the firmware requested
2455 by the kernel during kernel module loading. To find the package
2456 providing the example file, do like this:
</p
>
2458 <blockquote
><pre
>
2459 % apt install appstream
2463 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2464 awk
'/Package:/ {print $
2}
'
2467 </pre
></blockquote
>
2469 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2470 appstream wiki
</a
> page to learn how to embed the package metadata in
2471 a way appstream can use.
</p
>
2473 <p
>This same approach can be used to find any package supporting a
2474 given MIME type. This is very useful when you get a file you do not
2475 know how to handle. First find the mime type using
<tt
>file
2476 --mime-type
</tt
>, and next look up the package providing support for
2477 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2478 and you can find all packages handling this type like this:
</p
>
2480 <blockquote
><pre
>
2481 % apt install appstream
2485 % appstreamcli what-provides mimetype image/svg+xml | \
2486 awk
'/Package:/ {print $
2}
'
2508 </pre
></blockquote
>
2510 <p
>I believe the MIME types are fetched from the desktop file for
2511 packages providing appstream metadata.
</p
>
2516 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2517 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2518 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2519 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2520 <description><p
>Most people seem not to realise that every time they walk around
2521 with the computerised radio beacon known as a mobile phone their
2522 position is tracked by the phone company and often stored for a long
2523 time (like every time a SMS is received or sent). And if their
2524 computerised radio beacon is capable of running programs (often called
2525 mobile apps) downloaded from the Internet, these programs are often
2526 also capable of tracking their location (if the app requested access
2527 during installation). And when these programs send out information to
2528 central collection points, the location is often included, unless
2529 extra care is taken to not send the location. The provided
2530 information is used by several entities, for good and bad (what is
2531 good and bad, depend on your point of view). What is certain, is that
2532 the private sphere and the right to free movement is challenged and
2533 perhaps even eradicated for those announcing their location this way,
2534 when they share their whereabouts with private and public
2537 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2539 <p
>The phone company logs provide a register of locations to check out
2540 when one want to figure out what the tracked person was doing. It is
2541 unavailable for most of us, but provided to selected government
2542 officials, company staff, those illegally buying information from
2543 unfaithful servants and crackers stealing the information. But the
2544 public information can be collected and analysed, and a free software
2545 tool to do so is called
2546 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2547 discovered it when I read
2548 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2549 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2550 November
2014, and decided to check if it was available in Debian.
2551 The python program was in Debian, but
2552 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2553 Debian
</a
> was completely broken and practically unmaintained. I
2554 uploaded a new version which did not work quite right, but did not
2555 have time to fix it then. This Christmas I decided to finally try to
2556 get Creepy operational in Debian. Now a fixed version is available in
2557 Debian unstable and testing, and almost all Debian specific patches
2559 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2561 <p
>The Creepy program visualises geolocation information fetched from
2562 Twitter, Instagram, Flickr and Google+, and allow one to get a
2563 complete picture of every social media message posted recently in a
2564 given area, or track the movement of a given individual across all
2565 these services. Earlier it was possible to use the search API of at
2566 least some of these services without identifying oneself, but these
2567 days it is impossible. This mean that to use Creepy, you need to
2568 configure it to log in as yourself on these services, and provide
2569 information to them about your search interests. This should be taken
2570 into account when using Creepy, as it will also share information
2571 about yourself with the services.
</p
>
2573 <p
>The picture above show the twitter messages sent from (or at least
2574 geotagged with a position from) the city centre of Oslo, the capital
2575 of Norway. One useful way to use Creepy is to first look at
2576 information tagged with an area of interest, and next look at all the
2577 information provided by one or more individuals who was in the area.
2578 I tested it by checking out which celebrity provide their location in
2579 twitter messages by checkout out who sent twitter messages near a
2580 Norwegian TV station, and next could track their position over time,
2581 making it possible to locate their home and work place, among other
2582 things. A similar technique have been
2583 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2584 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2585 tool to discover lying governments, and a useful tool to help people
2586 understand the value of the private information they provide to the
2589 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2590 it depend on several python modules currently missing in Jessie (at
2591 least python-instagram, python-flickrapi and
2592 python-requests-toolbelt).
</p
>
2594 <p
>(I have uploaded
2595 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2596 screenshots.debian.net
</a
> and licensed it under the same terms as the
2597 Creepy program in Debian.)
</p
>
2602 <title>Always download Debian packages using Tor - the simple recipe
</title>
2603 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2604 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2605 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2606 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2607 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2608 that those listening on the Internet lines would have good reason to
2609 believe a computer have a given security hole
</a
> if it download a
2610 security fix from a Debian mirror. This is a good reason to always
2611 use encrypted connections to the Debian mirror, to make sure those
2612 listening do not know which IP address to attack. In August, Richard
2613 Hartmann observed that encryption was not enough, when it was possible
2614 to interfere download size to security patches or the fact that
2615 download took place shortly after a security fix was released, and
2616 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2617 to always use Tor to download packages from the Debian mirror
</a
>. He
2618 was not the first to propose this, as the
2619 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2620 package by Tim Retout already existed to make it easy to convince apt
2621 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2622 aware of that package when I read the blog post from Richard.
</p
>
2624 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2625 sysadmins, and he set up a Tor hidden service on one of the central
2626 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2627 it possible to download packages directly between two tor nodes,
2628 making sure the network traffic always were encrypted.
</p
>
2630 <p
>Here is a short recipe for enabling this on your machine, by
2631 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2632 urls with tor+http and tor+https, and using the hidden service instead
2633 of the official Debian mirror site. I recommend installing
2634 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2635 done in /etc/.
</p
>
2637 <blockquote
><pre
>
2638 apt install apt-transport-tor
2639 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2640 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2641 </pre
></blockquote
>
2643 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2644 the sed commands for these too. The sed command is assuming your are
2645 using the ftp.debian.org Debian mirror. Adjust the command (or just
2646 edit the file manually) to match your mirror.
</p
>
2648 <p
>This work in Debian Jessie and later. Note that tools like
2649 <tt
>apt-file
</tt
> only recently started using the apt transport
2650 system, and do not work with these tor+http URLs. For
2651 <tt
>apt-file
</tt
> you need the version currently in experimental,
2652 which need a recent apt version currently only in unstable. So if you
2653 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2655 <p
>Another advantage from this change is that your machine will start
2656 using Tor regularly and at fairly random intervals (every time you
2657 update the package lists or upgrade or install a new package), thus
2658 masking other Tor traffic done from the same machine. Using Tor will
2659 become normal for the machine in question.
</p
>
2661 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2662 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2663 enabled. It would be great if it was the default on any Debian
2669 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2670 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2671 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2672 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2673 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2674 call the car license plate numbers in those days. I would write the
2675 numbers down in my little book and compare notes with the other kids
2676 to see how many region codes we had seen and if we had seen some
2677 exotic or special region codes and numbers. It was a fun game to pass
2678 time, as we kids have plenty of it.
</p
>
2680 <p
>A few days I came across
2681 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2682 project
</a
>, a free software project to automatically discover and
2683 report license plates in images and video streams, and provide the
2684 "car numbers
" in a machine readable format. I
've been looking for
2685 such system for a while now, because I believe it is a bad idea that the
2686 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2687 number plate recognition
</a
> tool only is available in the hands of
2688 the powerful, and want it to be available also for the powerless to
2689 even the score when it comes to surveillance and sousveillance. I
2690 discovered the developer
2691 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2692 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2693 help him get it into shape to get the package uploaded into the Debian
2696 <p
>Today we finally managed to get the package into shape and uploaded
2697 it into Debian, where it currently
2698 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2699 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2701 <p
>I guess you are wondering why on earth such tool would be useful
2702 for the common folks, ie those not running a large government
2703 surveillance system? Well, I plan to put it in a computer on my bike
2704 and in my car, tracking the cars nearby and allowing me to be notified
2705 when number plates on my watch list are discovered. Another use case
2706 was suggested by a friend of mine, who wanted to set it up at his home
2707 to open the car port automatically when it discovered the plate on his
2708 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2709 capable of placing his license plate number of a piece of cardboard to
2710 open his car port, men replied that it was always unlocked anyway. I
2711 guess for such use case it make sense. I am sure there are other use
2712 cases too, for those with imagination and a vision.
</p
>
2714 <p
>If you want to build your own version of the Debian package, check
2715 out the upstream git source and symlink ./distros/debian to ./debian/
2716 before running
"debuild
" to build the source. Or wait a bit until the
2717 package show up in unstable.
</p
>
2722 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2723 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2725 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2726 <description><p
>Around three years ago, I created
2727 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2728 system
</a
> to get a more practical solution in Debian for handing
2729 hardware related packages. A GUI system in the isenkram package will
2730 present a pop-up dialog when some hardware dongle supported by
2731 relevant packages in Debian is inserted into the machine. The same
2732 lookup mechanism to detect packages is available as command line
2733 tools in the isenkram-cli package. In addition to mapping hardware,
2734 it will also map kernel firmware files to packages and make it easy to
2735 install needed firmware packages automatically. The key for this
2736 system to work is a good way to map hardware to packages, in other
2737 words, allow packages to announce what hardware they will work
2740 <p
>I started by providing data files in the isenkram source, and
2741 adding code to download the latest version of these data files at run
2742 time, to ensure every user had the most up to date mapping available.
2743 I also added support for storing the mapping in the Packages file in
2744 the apt repositories, but did not push this approach because while I
2745 was trying to figure out how to best store hardware/package mappings,
2746 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2747 appstream system
</a
> was announced. I got in touch and suggested to
2748 add the hardware mapping into that data set to be able to use
2749 appstream as a data source, and this was accepted at least for the
2750 Debian version of appstream.
</p
>
2752 <p
>A few days ago using appstream in Debian for this became possible,
2753 and today I uploaded a new version
0.20 of isenkram adding support for
2754 appstream as a data source for mapping hardware to packages. The only
2755 package so far using appstream to announce its hardware support is my
2756 pymissile package. I got help from Matthias Klumpp with figuring out
2757 how do add the required
2758 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2759 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2760 this content:
</p
>
2762 <blockquote
><pre
>
2763 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2764 &lt;component
&gt;
2765 &lt;id
&gt;pymissile
&lt;/id
&gt;
2766 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2767 &lt;name
&gt;pymissile
&lt;/name
&gt;
2768 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2769 &lt;description
&gt;
2771 Pymissile provides a curses interface to control an original
2772 Marks and Spencer / Striker USB Missile Launcher, as well as a
2773 motion control script to allow a webcamera to control the
2776 &lt;/description
&gt;
2777 &lt;provides
&gt;
2778 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2779 &lt;/provides
&gt;
2780 &lt;/component
&gt;
2781 </pre
></blockquote
>
2783 <p
>The key for isenkram is the component/provides/modalias value,
2784 which is a glob style match rule for hardware specific strings
2785 (modalias strings) provided by the Linux kernel. In this case, it
2786 will map to all USB devices with vendor code
1130 and product code
2789 <p
>Note, it is important that the license of all the metadata files
2790 are compatible to have permissions to aggregate them into archive wide
2791 appstream files. Matthias suggested to use MIT or BSD licenses for
2792 these files. A challenge is figuring out a good id for the data, as
2793 it is supposed to be globally unique and shared across distributions
2794 (in other words, best to coordinate with upstream what to use). But
2795 it can be changed later or, so we went with the package name as
2796 upstream for this project is dormant.
</p
>
2798 <p
>To get the metadata file installed in the correct location for the
2799 mirror update scripts to pick it up and include its content the
2800 appstream data source, the file must be installed in the binary
2801 package under /usr/share/appdata/. I did this by adding the following
2802 line to debian/pymissile.install:
</p
>
2804 <blockquote
><pre
>
2805 debian/pymissile.metainfo.xml usr/share/appdata
2806 </pre
></blockquote
>
2808 <p
>With that in place, the command line tool isenkram-lookup will list
2809 all packages useful on the current computer automatically, and the GUI
2810 pop-up handler will propose to install the package not already
2811 installed if a hardware dongle is inserted into the machine in
2814 <p
>Details of the modalias field in appstream is available from the
2815 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2817 <p
>To locate the modalias values of all hardware present in a machine,
2818 try running this command on the command line:
</p
>
2820 <blockquote
><pre
>
2821 cat $(find /sys/devices/|grep modalias)
2822 </pre
></blockquote
>
2824 <p
>To learn more about the isenkram system, please check out
2825 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2826 blog posts tagged isenkram
</a
>.
</p
>
2831 <title>The GNU General Public License is not magic pixie dust
</title>
2832 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2833 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2834 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2835 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2836 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2837 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2838 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2839 I quote the blog post from Paul in full here with his permission:
<p
>
2843 <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
>
2846 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2848 The first step is to choose a
2849 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2852 The next step is, when someone fails to follow that copyleft license,
2853 <b
>it must be enforced
</b
><br/
>
2855 and its a simple fact of our modern society that such type of
2858 is incredibly expensive to do and incredibly difficult to do.
2861 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2862 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2863 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2864 0x57</a
></small
></p
>
2866 <p
>As the Debian Website
2867 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2868 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2869 imply, public domain and permissively licensed software can lead to
2870 the production of more proprietary software as people discover useful
2871 software, extend it and or incorporate it into their hardware or
2872 software products. Copyleft licenses such as the GNU GPL were created
2873 to close off this avenue to the production of proprietary software but
2874 such licenses are not enough. With the ongoing adoption of Free
2875 Software by individuals and groups, inevitably the community
's
2876 expectations of license compliance are violated, usually out of
2877 ignorance of the way Free Software works, but not always. As Karen
2878 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2879 Freedom
">FaiF
</a
>
2880 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2881 copyleft is nothing if no-one is willing and able to stand up in court
2882 to protect it. The reality of today
's world is that legal
2883 representation is expensive, difficult and time consuming. With
2884 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2885 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2886 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2887 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2888 of the Linux project, Debian and other groups against GPL violations.
2889 In March the SFC supported a
2890 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2891 by Christoph Hellwig
</a
> against VMware for refusing to
2892 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2893 with the GPL
</a
> in relation to their use of parts of the Linux
2894 kernel. Since then two of their sponsors pulled corporate funding and
2896 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2897 or cancelled their talks
</a
>. As a result they have decided to rely
2898 less on corporate funding and more on the broad community of
2899 individuals who support Free Software and copyleft. So the SFC has
2900 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2901 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2902 a community of folks who stand up for copyleft and the GPL by
2903 supporting their work on promoting and supporting copyleft and Free
2906 <p
>If you support Free Software,
2907 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2908 what the SFC do, agree with their
2909 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2910 principles
</a
>, are happy about their
2911 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2912 work on a project that is an SFC
2913 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2914 just want to stand up for copyleft, please join
2915 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2916 Allan Webber
</a
>,
2917 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2919 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2920 Bacon
</a
>, myself and
2921 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2923 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2924 next week your donation will be
2925 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2926 by an anonymous donor. Please also consider asking your employer to
2927 match your donation or become a sponsor of SFC. Don
't forget to
2928 spread the word about your support for SFC via email, your blog and or
2929 social media accounts.
</p
>
2933 <p
>I agree with Paul on this topic and just signed up as a Supporter
2934 of Software Freedom Conservancy myself. Perhaps you should be a
2935 supporter too?
</p
>
2940 <title>PGP key transition statement for key EE4E02F9
</title>
2941 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2942 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2943 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2944 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2945 set it up properly. I wanted to generate it offline and have it
2946 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2947 smart card
</a
> for daily use, and learning how to do it and finding
2948 time to sit down with an offline machine almost took forever. But
2949 finally I
've been able to complete the process, and have now moved
2950 from my old GPG key to a new GPG key. See
2951 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2952 full transition statement, signed with both my old and new key
</a
> for
2953 the details. This is my new key:
</p
>
2956 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2957 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2958 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2959 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2960 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2961 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2962 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2965 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2966 my old key.
</p
>
2968 <p
>If you signed my old key
2969 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2970 I
'd very much appreciate a signature on my new key, details and
2971 instructions in the transition statement. I m happy to reciprocate if
2972 you have a similarly signed transition statement to present.
</p
>
2977 <title>The life and death of a laptop battery
</title>
2978 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2980 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2981 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2982 But this do not last. The last few laptops gave me a feeling that
2983 within a year, the life time is just a fraction of what it used to be,
2984 and it slowly become painful to use the laptop without power connected
2985 all the time. Because of this, when I got a new Thinkpad X230 laptop
2986 about two years ago, I decided to monitor its battery state to have
2987 more hard facts when the battery started to fail.
</p
>
2989 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2991 <p
>First I tried to find a sensible Debian package to record the
2992 battery status, assuming that this must be a problem already handled
2993 by someone else. I found
2994 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2995 which collects statistics from the battery, but it was completely
2996 broken. I sent a few suggestions to the maintainer, but decided to
2997 write my own collector as a shell script while I waited for feedback
2999 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3000 blog post about the battery development on a MacBook Air
</a
> I also
3002 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3003 available in Debian.
</p
>
3005 <p
>I started my collector
2013-
07-
15, and it has been collecting
3006 battery stats ever since. Now my
3007 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3008 measurements, from the time the battery was working great until now,
3009 when it is unable to charge above
7% of original capacity. My
3010 collector shell script is quite simple and look like this:
</p
>
3015 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3017 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3018 logfile=/var/log/hjemmenett-battery-status.log
3020 files=
"manufacturer model_name technology serial_number \
3021 energy_full energy_full_design energy_now cycle_count status
"
3023 if [ ! -e
"$logfile
" ] ; then
3025 printf
"timestamp,
"
3027 printf
"%s,
" $f
3030 )
> "$logfile
"
3034 # Print complete message in one echo call, to avoid race condition
3035 # when several log processes run in parallel.
3036 msg=$(printf
"%s,
" $(date +%s); \
3037 for f in $files; do \
3038 printf
"%s,
" $(cat $f); \
3040 echo
"$msg
"
3043 cd /sys/class/power_supply
3046 (cd $bat
&& log_battery
>> "$logfile
")
3050 <p
>The script is called when the power management system detect a
3051 change in the power status (power plug in or out), and when going into
3052 and out of hibernation and suspend. In addition, it collect a value
3053 every
10 minutes. This make it possible for me know when the battery
3054 is discharging, charging and how the maximum charge change over time.
3055 The code for the Debian package
3056 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3057 available on github
</a
>.
</p
>
3059 <p
>The collected log file look like this:
</p
>
3062 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3063 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3065 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3066 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3069 <p
>I wrote a small script to create a graph of the charge development
3070 over time. This graph depicted above show the slow death of my laptop
3073 <p
>But why is this happening? Why are my laptop batteries always
3074 dying in a year or two, while the batteries of space probes and
3075 satellites keep working year after year. If we are to believe
3076 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3077 University
</a
>, the cause is me charging the battery whenever I have a
3078 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3079 all the time, but to stay below
90% of full charge most of the time.
3080 I
've been told that the Tesla electric cars
3081 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3082 the charge of their batteries to
80%
</a
>, with the option to charge to
3083 100% when preparing for a longer trip (not that I would want a car
3084 like Tesla where rights to privacy is abandoned, but that is another
3085 story), which I guess is the option we should have for laptops on
3086 Linux too.
</p
>
3088 <p
>Is there a good and generic way with Linux to tell the battery to
3089 stop charging at
80%, unless requested to charge to
100% once in
3090 preparation for a longer trip? I found
3091 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3092 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3093 80%
</a
>, but could not get it to work (kernel module refused to
3096 <p
>I wonder why the battery capacity was reported to be more than
100%
3097 at the start. I also wonder why the
"full capacity
" increases some
3098 times, and if it is possible to repeat the process to get the battery
3099 back to design capacity. And I wonder if the discharge and charge
3100 speed change over time, or if this stay the same. I did not yet try
3101 to write a tool to calculate the derivative values of the battery
3102 level, but suspect some interesting insights might be learned from
3105 <p
>Update
2015-
09-
24: I got a tip to install the packages
3106 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3107 packages instead of the tp-smapi-dkms package I had tried to use
3108 initially, and use
'tlp setcharge
40 80' to change when charging start
3109 and stop. I
've done so now, but expect my existing battery is toast
3110 and need to be replaced. The proposal is unfortunately Thinkpad
3116 <title>New laptop - some more clues and ideas based on feedback
</title>
3117 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3118 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3119 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3120 <description><p
>Several people contacted me after my previous blog post about my
3121 need for a new laptop, and provided very useful feedback. I wish to
3122 thank every one of these. Several pointed me to the possibility of
3123 fixing my X230, and I am already in the process of getting Lenovo to
3124 do so thanks to the on site, next day support contract covering the
3125 machine. But the battery is almost useless (I expect to replace it
3126 with a non-official battery) and I do not expect the machine to live
3127 for many more years, so it is time to plan its replacement. If I did
3128 not have a support contract, it was suggested to find replacement parts
3129 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3130 might present a language barrier as I do not understand French.
</p
>
3132 <p
>One tip I got was to use the
3133 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3134 compare laptop models. It seem to have more models available than
3135 prisjakt.no. Another tip I got from someone I know have similar
3136 keyboard preferences was that the HP EliteBook
840 keyboard is not
3137 very good, and this matches my experience with earlier EliteBook
3138 keyboards I tested. Because of this, I will not consider it any further.
3140 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3141 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3142 (which is missing from the X240), and is working fairly well with
3143 Debian Sid/Unstable according to
3144 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3145 got on the keyboard quality are not consistent. Some say the keyboard
3146 is good, others say it is ok, while others say it is not very good.
3147 Those with experience from X41 and and X60 agree that the X250
3148 keyboard is not as good as those trusty old laptops, and suggest I
3149 keep and fix my X230 instead of upgrading, or get a used X230 to
3150 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3151 activity and battery status, which is very convenient on my X230. I
'm
3152 also told that the CPU fan is running very often, making it a bit
3153 noisy. In any case, the X250 do not work out of the box with Debian
3154 Stable/Jessie, one of my requirements.
</p
>
3156 <p
>I have also gotten a few vendor proposals, one was
3157 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3158 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3159 The latter look very attractive to me.
</p
>
3161 <p
>Again, thank you all for the very useful feedback. It help a lot
3162 as I keep looking for a replacement.
</p
>
3164 <p
>Update
2015-
07-
06: I was recommended to check out the
3165 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3167 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3168 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3173 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3174 <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>
3175 <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>
3176 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3177 <description><p
>My primary work horse laptop is failing, and will need a
3178 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3179 started flickering yesterday, and I suspect the cause is a broken
3180 cable, as changing the angle of the screen some times get rid of the
3181 flickering.
</p
>
3183 <p
>My requirements have not really changed since I bought it, and is
3185 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3186 described them in
2013</a
>. The last time I bought a laptop, I had
3188 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3189 where I could select at least a few of the requirements (mouse pin,
3190 wifi, weight) and go through the rest manually. Three button mouse
3191 and a good keyboard is not available as an option, and all the three
3192 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3193 G2) lack three mouse buttons). It is also unclear to me how good the
3194 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3195 the keyboard, even if the quality and robustness in the X series have
3196 deteriorated since X41.
</p
>
3198 <p
>I wonder how I can find a sensible laptop when none of the options
3199 seem sensible to me? Are there better services around to search the
3200 set of available laptops for features? Please send me an email if you
3201 have suggestions.
</p
>
3203 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3204 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3205 of endorsed hardware
</a
>, which is useful background information.
</p
>
3210 <title>How to stay with sysvinit in Debian Jessie
</title>
3211 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3212 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3213 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3214 <description><p
>By now, it is well known that Debian Jessie will not be using
3215 sysvinit as its boot system by default. But how can one keep using
3216 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3218 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3219 Schubert
</a
> and
3220 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3223 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3224 keep sysvinit as your boot system, create a file
3225 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3226 you upgrade:
</p
>
3228 <p
><blockquote
><pre
>
3229 Package: systemd-sysv
3230 Pin: release o=Debian
3232 </pre
></blockquote
><p
>
3234 <p
>This file content will tell apt and aptitude to not consider
3235 installing systemd-sysv as part of any installation and upgrade
3236 solution when resolving dependencies, and thus tell it to avoid
3237 systemd as a default boot system. The end result should be that the
3238 upgraded system keep using sysvinit.
</p
>
3240 <p
>If you are installing Jessie for the first time, there is no way to
3241 get sysvinit installed by default (debootstrap used by
3242 debian-installer have no option for this), but one can tell the
3243 installer to switch to sysvinit before the first boot. Either by
3244 using a kernel argument to the installer, or by adding a line to the
3245 preseed file used. First, the kernel command line argument:
3247 <p
><blockquote
><pre
>
3248 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3249 </pre
></blockquote
><p
>
3251 <p
>Next, the line to use in a preseed file:
</p
>
3253 <p
><blockquote
><pre
>
3254 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3255 </pre
></blockquote
><p
>
3257 <p
>One can of course also do this after the first boot by installing
3258 the sysvinit-core package.
</p
>
3260 <p
>I recommend only using sysvinit if you really need it, as the
3261 sysvinit boot sequence in Debian have several hardware specific bugs
3262 on Linux caused by the fact that it is unpredictable when hardware
3263 devices show up during boot. But on the other hand, the new default
3264 boot system still have a few rough edges I hope will be fixed before
3265 Jessie is released.
</p
>
3267 <p
>Update
2014-
11-
26: Inspired by
3268 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3269 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3275 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3276 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3277 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3278 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3279 <description><p
>The right to communicate with your friends and family in private,
3280 without anyone snooping, is a right every citicen have in a liberal
3281 democracy. But this right is under serious attack these days.
</p
>
3283 <p
>A while back it occurred to me that one way to make the dragnet
3284 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3285 the whisleblower Snowden) more expensive for Internet email,
3286 is to deliver all email using SMTP via Tor. Such SMTP option would be
3287 a nice addition to the FreedomBox project if we could send email
3288 between FreedomBox machines without leaking metadata about the emails
3289 to the people peeking on the wire. I
3290 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3291 this on the FreedomBox project mailing list in October
</a
> and got a
3292 lot of useful feedback and suggestions. It also became obvious to me
3293 that this was not a novel idea, as the same idea was tested and
3294 documented by Johannes Berg as early as
2006, and both
3295 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3296 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3297 propose a similar method / protocol to pass emails between users.
</p
>
3299 <p
>To implement such system one need to set up a Tor hidden service
3300 providing the SMTP protocol on port
25, and use email addresses
3301 looking like username@hidden-service-name.onion. With such addresses
3302 the connections to port
25 on hidden-service-name.onion using Tor will
3303 go to the correct SMTP server. To do this, one need to configure the
3304 Tor daemon to provide the hidden service and the mail server to accept
3305 emails for this .onion domain. To learn more about Exim configuration
3306 in Debian and test the design provided by Johannes Berg in his FAQ, I
3307 set out yesterday to create a Debian package for making it trivial to
3308 set up such SMTP over Tor service based on Debian. Getting it to work
3309 were fairly easy, and
3310 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3311 source code for the Debian package
</a
> is available from github. I
3312 plan to move it into Debian if further testing prove this to be a
3313 useful approach.
</p
>
3315 <p
>If you want to test this, set up a blank Debian machine without any
3316 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3317 get rid of exim4). Install tor, clone the git repository mentioned
3318 above, build the deb and install it on the machine. Next, run
3319 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3320 the instructions to get the service up and running. Restart tor and
3321 exim when it is done, and test mail delivery using swaks like
3324 <p
><blockquote
><pre
>
3325 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3326 --to fbx@dutlqrrmjhtfa3vp.onion
3327 </pre
></blockquote
></p
>
3329 <p
>This will test the SMTP delivery using tor. Replace the email
3330 address with your own address to test your server. :)
</p
>
3332 <p
>The setup procedure is still to complex, and I hope it can be made
3333 easier and more automatic. Especially the tor setup need more work.
3334 Also, the package include a tor-smtp tool written in C, but its task
3335 should probably be rewritten in some script language to make the deb
3336 architecture independent. It would probably also make the code easier
3337 to review. The tor-smtp tool currently need to listen on a socket for
3338 exim to talk to it and is started using xinetd. It would be better if
3339 no daemon and no socket is needed. I suspect it is possible to get
3340 exim to run a command line tool for delivery instead of talking to a
3341 socket, and hope to figure out how in a future version of this
3344 <p
>Until I wipe my test machine, I can be reached using the
3345 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3346 SMTorP. :)
</p
>
3351 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3352 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3353 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3354 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3355 <description><p
>If you ever had to moderate a mailman list, like the ones on
3356 alioth.debian.org, you know the web interface is fairly slow to
3357 operate. First you visit one web page, enter the moderation password
3358 and get a new page shown with a list of all the messages to moderate
3359 and various options for each email address. This take a while for
3360 every list you moderate, and you need to do it regularly to do a good
3361 job as a list moderator. But there is a quick alternative,
3362 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3363 listadmin program
</a
>. It allow you to check lists for new messages
3364 to moderate in a fraction of a second. Here is a test run on two
3365 lists I recently took over:
</p
>
3367 <p
><blockquote
><pre
>
3368 % time listadmin xiph
3369 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3370 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3376 </pre
></blockquote
></p
>
3378 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3379 there are no message in the moderation queue. Every morning I
3380 currently moderate
68 mailman lists, and it normally take around two
3381 minutes. When I took over the two pkg-xiph lists above a few days
3382 ago, there were
400 emails waiting in the moderator queue. It took me
3383 less than
15 minutes to process them all using the listadmin
3386 <p
>If you install
3387 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3388 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3389 with content like this, the moderation task is a breeze:
</p
>
3391 <p
><blockquote
><pre
>
3392 username username@example.org
3395 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3398 adminurl https://{domain}/mailman/admindb/{list}
3399 mailman-list@lists.example.com
3402 other-list@otherserver.example.org
3403 </pre
></blockquote
></p
>
3405 <p
>There are other options to set as well. Check the manual page to
3406 learn the details.
</p
>
3408 <p
>If you are forced to moderate lists on a mailman installation where
3409 the SSL certificate is self signed or not properly signed by a
3410 generally accepted signing authority, you can set a environment
3411 variable when calling listadmin to disable SSL verification:
</p
>
3413 <p
><blockquote
><pre
>
3414 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3415 </pre
></blockquote
></p
>
3417 <p
>If you want to moderate a subset of the lists you take care of, you
3418 can provide an argument to the listadmin script like I do in the
3419 initial screen dump (the xiph argument). Using an argument, only
3420 lists matching the argument string will be processed. This make it
3421 quick to accept messages if you notice the moderation request in your
3424 <p
>Without the listadmin program, I would never be the moderator of
68
3425 mailing lists, as I simply do not have time to spend on that if the
3426 process was any slower. The listadmin program have saved me hours of
3427 time I could spend elsewhere over the years. It truly is nice free
3430 <p
>As usual, if you use Bitcoin and want to show your support of my
3431 activities, please send Bitcoin donations to my address
3432 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3434 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3435 configuration example. Also, I
've been told that the
3436 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3442 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3443 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3444 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3445 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3446 <description><p
>When PXE installing laptops with Debian, I often run into the
3447 problem that the WiFi card require some firmware to work properly.
3448 And it has been a pain to fix this using preseeding in Debian.
3449 Normally something more is needed. But thanks to
3450 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3451 package
</a
> and its recent tasksel extension, it has now become easy
3452 to do this using simple preseeding.
</p
>
3454 <p
>The isenkram-cli package provide tasksel tasks which will install
3455 firmware for the hardware found in the machine (actually, requested by
3456 the kernel modules for the hardware). (It can also install user space
3457 programs supporting the hardware detected, but that is not the focus
3458 of this story.)
</p
>
3460 <p
>To get this working in the default installation, two preeseding
3461 values are needed. First, the isenkram-cli package must be installed
3462 into the target chroot (aka the hard drive) before tasksel is executed
3463 in the pkgsel step of the debian-installer system. This is done by
3464 preseeding the base-installer/includes debconf value to include the
3465 isenkram-cli package. The package name is next passed to debootstrap
3466 for installation. With the isenkram-cli package in place, tasksel
3467 will automatically use the isenkram tasks to detect hardware specific
3468 packages for the machine being installed and install them, because
3469 isenkram-cli contain tasksel tasks.
</p
>
3471 <p
>Second, one need to enable the non-free APT repository, because
3472 most firmware unfortunately is non-free. This is done by preseeding
3473 the apt-mirror-setup step. This is unfortunate, but for a lot of
3474 hardware it is the only option in Debian.
</p
>
3476 <p
>The end result is two lines needed in your preseeding file to get
3477 firmware installed automatically by the installer:
</p
>
3479 <p
><blockquote
><pre
>
3480 base-installer base-installer/includes string isenkram-cli
3481 apt-mirror-setup apt-setup/non-free boolean true
3482 </pre
></blockquote
></p
>
3484 <p
>The current version of isenkram-cli in testing/jessie will install
3485 both firmware and user space packages when using this method. It also
3486 do not work well, so use version
0.15 or later. Installing both
3487 firmware and user space packages might give you a bit more than you
3488 want, so I decided to split the tasksel task in two, one for firmware
3489 and one for user space programs. The firmware task is enabled by
3490 default, while the one for user space programs is not. This split is
3491 implemented in the package currently in unstable.
</p
>
3493 <p
>If you decide to give this a go, please let me know (via email) how
3494 this recipe work for you. :)
</p
>
3496 <p
>So, I bet you are wondering, how can this work. First and
3497 foremost, it work because tasksel is modular, and driven by whatever
3498 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3499 isenkram-cli package place two files for tasksel to find. First there
3500 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3502 <p
><blockquote
><pre
>
3503 Task: isenkram-packages
3505 Description: Hardware specific packages (autodetected by isenkram)
3506 Based on the detected hardware various hardware specific packages are
3508 Test-new-install: show show
3510 Packages: for-current-hardware
3512 Task: isenkram-firmware
3514 Description: Hardware specific firmware packages (autodetected by isenkram)
3515 Based on the detected hardware various hardware specific firmware
3516 packages are proposed.
3517 Test-new-install: mark show
3519 Packages: for-current-hardware-firmware
3520 </pre
></blockquote
></p
>
3522 <p
>The key parts are Test-new-install which indicate how the task
3523 should be handled and the Packages line referencing to a script in
3524 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3525 list of packages to install. The for-current-hardware-firmware script
3526 look like this to list relevant firmware for the machine:
3528 <p
><blockquote
><pre
>
3531 PATH=/usr/sbin:$PATH
3533 isenkram-autoinstall-firmware -l
3534 </pre
></blockquote
></p
>
3536 <p
>With those two pieces in place, the firmware is installed by
3537 tasksel during the normal d-i run. :)
</p
>
3539 <p
>If you want to test what tasksel will install when isenkram-cli is
3540 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3541 --new-install
</tt
> to get the list of packages that tasksel would
3544 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3545 pilots in testing this feature, as isenkram is used there now to
3546 install firmware, replacing the earlier scripts.
</p
>
3551 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3552 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3553 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3554 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3555 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3556 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3557 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3558 on a screen normally showing the bread types and prizes:
</p
>
3560 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3562 <p
>If it had booted as it was supposed to, I would never had known
3563 about this hidden Linux installation. It is interesting what
3564 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3569 <title>New lsdvd release version
0.17 is ready
</title>
3570 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3571 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3572 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3573 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3574 got a new set of developers a few weeks ago, after the original
3575 developer decided to step down and pass the project to fresh blood.
3576 This project is now maintained by Petter Reinholdtsen and Steve
3579 <p
>I just wrapped up
3580 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3581 new lsdvd release
</a
>, available in git or from
3582 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3583 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3588 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3589 <li
>Check for garbage in the program chains, which indicate that a track is
3590 non-existant, to work around additional copy protection
</li
>
3591 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3592 <li
>Fix pallete display of first entry
</li
>
3593 <li
>Fix include orders
</li
>
3594 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3595 <li
>Fix the chapter count
</li
>
3596 <li
>Make sure the array size and the array limit used when initialising
3597 the palette size is the same.
</li
>
3598 <li
>Fix array printing.
</li
>
3599 <li
>Correct subsecond calculations.
</li
>
3600 <li
>Add sector information to the output format.
</li
>
3601 <li
>Clean up code to be closer to ANSI C and compile without warnings
3602 with more GCC compiler warnings.
</li
>
3606 <p
>This change bring together patches for lsdvd in use in various
3607 Linux and Unix distributions, as well as patches submitted to the
3608 project the last nine years. Please check it out. :)
</p
>
3613 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3614 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3616 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3617 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3618 project
</a
> provide a Linux solution for schools, including a
3619 powerful desktop with education software, a central server providing
3620 web pages, user database, user home directories, central login and PXE
3621 boot of both clients without disk and the installation to install Debian
3622 Edu on machines with disk (and a few other services perhaps to small
3623 to mention here). We in the Debian Edu team are currently working on
3624 the Jessie based version, trying to get everything in shape before the
3625 freeze, to avoid having to maintain our own package repository in the
3627 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3628 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3629 work left. Some fatal problems block testing, breaking the installer,
3630 but it is possible to work around these to get anyway. Here is a
3631 recipe on how to get the installation limping along.
</p
>
3633 <p
>First, download the test ISO via
3634 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3635 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3637 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3638 The ISO build was broken on Tuesday, so we do not get a new ISO every
3639 12 hours or so, but thankfully the ISO we already got we are able to
3640 install with some tweaking.
</p
>
3642 <p
>When you get to the Debian Edu profile question, go to tty2
3643 (use Alt-Ctrl-F2), run
</p
>
3645 <p
><blockquote
><pre
>
3646 nano /usr/bin/edu-eatmydata-install
3647 </pre
></blockquote
></p
>
3649 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3650 optimization. Return to the installation, select the profile you want
3651 and continue. Without this change, exim4-config will fail to install
3652 due to a known bug in eatmydata.
</p
>
3654 <p
>When you get the grub question at the end, answer /dev/sda (or if
3655 this do not work, figure out what your correct value would be. All my
3656 test machines need /dev/sda, so I have no advice if it do not fit
3657 your need.
</p
>
3659 <p
>If you installed a profile including a graphical desktop, log in as
3660 root after the initial boot from hard drive, and install the
3661 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3662 or mate. If you want several desktop options, install more than one
3663 metapackage. Once this is done, reboot and you should have a working
3664 graphical login screen. This workaround should no longer be needed
3665 once the education-tasks package version
1.801 enter testing in two
3668 <p
>I believe the ISO build will start working on two days when the new
3669 tasksel package enter testing and Steve McIntyre get a chance to
3670 update the debian-cd git repository. The eatmydata, grub and desktop
3671 issues are already fixed in unstable and testing, and should show up
3672 on the ISO as soon as the ISO build start working again. Well the
3673 eatmydata optimization is really just disabled. The proper fix
3674 require an upload by the eatmydata maintainer applying the patch
3675 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3676 The rest have proper fixes in unstable.
</p
>
3678 <p
>I hope this get you going with the installation testing, as we are
3679 quickly running out of time trying to get our Jessie based
3680 installation ready before the distribution freeze in a month.
</p
>
3685 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3686 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3687 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3688 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3689 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3690 to handle my fairly large DVD collection. It is a nice command line
3691 tool to get details about a DVD, like title, tracks, track length,
3692 etc, in XML, Perl or human readable format. But lsdvd have not seen
3693 any new development since
2006 and had a few irritating bugs affecting
3694 its use with some DVDs. Upstream seemed to be dead, and in January I
3695 sent a small probe asking for a version control repository for the
3696 project, without any reply. But I use it regularly and would like to
3697 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3698 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3699 the project admin, and after getting a reply from him explaining that
3700 he was no longer interested in the project, I asked if I could take
3701 over. And yesterday, I became project admin.
</p
>
3703 <p
>I
've been in touch with a Gentoo developer and the Debian
3704 maintainer interested in joining forces to maintain the upstream
3705 project, and I hope we can get a new release out fairly quickly,
3706 collecting the patches spread around on the internet into on place.
3707 I
've added the relevant Debian patches to the freshly created git
3708 repository, and expect the Gentoo patches to make it too. If you got
3709 a DVD collection and care about command line tools, check out
3710 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3711 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3712 list
</a
>. :)
</p
>
3717 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3718 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3719 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3720 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3721 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3722 a lot quicker. When we install more than
2000 packages in
3723 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3724 tasksel in the installer, unpacking the binary packages take forever.
3725 A part of the slow I/O issue was discussed in
3726 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3727 much file system sync-ing done by dpkg, which is the package
3728 responsible for unpacking the binary packages. Other parts (like code
3729 executed by postinst scripts) might also sync to disk during
3730 installation. All this sync-ing to disk do not really make sense to
3731 me. If the machine crash half-way through, I start over, I do not try
3732 to salvage the half installed system. So the failure sync-ing is
3733 supposed to protect against, hardware or system crash, is not really
3734 relevant while the installer is running.
</p
>
3736 <p
>A few days ago, I thought of a way to get rid of all the file
3737 system sync()-ing in a fairly non-intrusive way, without the need to
3738 change the code in several packages. The idea is not new, but I have
3739 not heard anyone propose the approach using dpkg-divert before. It
3740 depend on the small and clever package
3741 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3742 uses LD_PRELOAD to replace the system functions for syncing data to
3743 disk with functions doing nothing, thus allowing programs to live
3744 dangerous while speeding up disk I/O significantly. Instead of
3745 modifying the implementation of dpkg, apt and tasksel (which are the
3746 packages responsible for selecting, fetching and installing packages),
3747 it occurred to me that we could just divert the programs away, replace
3748 them with a simple shell wrapper calling
3749 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3750 Two days ago I decided to test the idea, and wrapped up a simple
3751 implementation for the Debian Edu udeb.
</p
>
3753 <p
>The effect was stunning. In my first test it reduced the running
3754 time of the pkgsel step (installing tasks) from
64 to less than
44
3755 minutes (
20 minutes shaved off the installation) on an old Dell
3756 Latitude D505 machine. I am not quite sure what the optimised time
3757 would have been, as I messed up the testing a bit, causing the debconf
3758 priority to get low enough for two questions to pop up during
3759 installation. As soon as I saw the questions I moved the installation
3760 along, but do not know how long the question were holding up the
3761 installation. I did some more measurements using Debian Edu Jessie,
3762 and got these results. The time measured is the time stamp in
3763 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3764 "pkgsel: finishing up
" lines, if you want to do the same measurement
3765 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3766 timing thus do not depend on how quickly the user handle the tasksel
3769 <p
><table
>
3772 <th
>Machine/setup
</th
>
3773 <th
>Original tasksel
</th
>
3774 <th
>Optimised tasksel
</th
>
3775 <th
>Reduction
</th
>
3779 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3780 <td
>64 min (
07:
46-
08:
50)
</td
>
3781 <td
><44 min (
11:
27-
12:
11)
</td
>
3782 <td
>>20 min
18%
</td
>
3786 <td
>Latitude D505 Roaming LXDE
</td
>
3787 <td
>57 min (
08:
48-
09:
45)
</td
>
3788 <td
>34 min (
07:
43-
08:
17)
</td
>
3789 <td
>23 min
40%
</td
>
3793 <td
>Latitude D505 Minimal
</td
>
3794 <td
>22 min (
10:
37-
10:
59)
</td
>
3795 <td
>11 min (
11:
16-
11:
27)
</td
>
3796 <td
>11 min
50%
</td
>
3800 <td
>Thinkpad X200 Minimal
</td
>
3801 <td
>6 min (
08:
19-
08:
25)
</td
>
3802 <td
>4 min (
08:
04-
08:
08)
</td
>
3803 <td
>2 min
33%
</td
>
3807 <td
>Thinkpad X200 Roaming KDE
</td
>
3808 <td
>19 min (
09:
21-
09:
40)
</td
>
3809 <td
>15 min (
10:
25-
10:
40)
</td
>
3810 <td
>4 min
21%
</td
>
3813 </table
></p
>
3815 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3816 time is spent downloading packages. The connection to the Internet
3817 was
100Mbit/s during testing, so downloading should not be a
3818 significant factor in the measurement. Download typically took a few
3819 seconds to a few minutes, depending on the amount of packages being
3820 installed.
</p
>
3822 <p
>The speedup is implemented by using two hooks in
3823 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3824 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3825 finish-install.d hook to remove the divert at the end of the
3826 installation. I picked the pre-pkgsel.d hook instead of the
3827 post-base-installer.d hook because I test using an ISO without the
3828 eatmydata package included, and the post-base-installer.d hook in
3829 Debian Edu can only operate on packages included in the ISO. The
3830 negative effect of this is that I am unable to activate this
3831 optimization for the kernel installation step in d-i. If the code is
3832 moved to the post-base-installer.d hook, the speedup would be larger
3833 for the entire installation.
</p
>
3835 <p
>I
've implemented this in the
3836 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3837 git repository, and plan to provide the optimization as part of the
3838 Debian Edu installation. If you want to test this yourself, you can
3839 create two files in the installer (or in an udeb). One shell script
3840 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3842 <p
><blockquote
><pre
>
3845 . /usr/share/debconf/confmodule
3847 logger -t my-pkgsel
"info: $*
"
3850 logger -t my-pkgsel
"error: $*
"
3852 override_install() {
3853 apt-install eatmydata || true
3854 if [ -x /target/usr/bin/eatmydata ] ; then
3855 for bin in dpkg apt-get aptitude tasksel ; do
3857 # Test that the file exist and have not been diverted already.
3858 if [ -f /target$file ] ; then
3859 info
"diverting $file using eatmydata
"
3860 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3861 > /target$file.edu
3862 chmod
755 /target$file.edu
3863 in-target dpkg-divert --package debian-edu-config \
3864 --rename --quiet --add $file
3865 ln -sf ./$bin.edu /target$file
3867 error
"unable to divert $file, as it is missing.
"
3871 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3876 </pre
></blockquote
></p
>
3878 <p
>To clean up, another shell script should go into
3879 /usr/lib/finish-install.d/ with code like this:
3881 <p
><blockquote
><pre
>
3883 . /usr/share/debconf/confmodule
3885 logger -t my-finish-install
"error: $@
"
3887 remove_install_override() {
3888 for bin in dpkg apt-get aptitude tasksel ; do
3890 if [ -x /target$file.edu ] ; then
3892 in-target dpkg-divert --package debian-edu-config \
3893 --rename --quiet --remove $file
3896 error
"Missing divert for $file.
"
3899 sync # Flush file buffers before continuing
3902 remove_install_override
3903 </pre
></blockquote
></p
>
3905 <p
>In Debian Edu, I placed both code fragments in a separate script
3906 edu-eatmydata-install and call it from the pre-pkgsel.d and
3907 finish-install.d scripts.
</p
>
3909 <p
>By now you might ask if this change should get into the normal
3910 Debian installer too? I suspect it should, but am not sure the
3911 current debian-installer coordinators find it useful enough. It also
3912 depend on the side effects of the change. I
'm not aware of any, but I
3913 guess we will see if the change is safe after some more testing.
3914 Perhaps there is some package in Debian depending on sync() and
3915 fsync() having effect? Perhaps it should go into its own udeb, to
3916 allow those of us wanting to enable it to do so without affecting
3919 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3920 will break installation of all programs using gnutls because of
3921 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3922 eatmydata package in Debian will solve it.
</p
>
3924 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3925 the optimization work again. And I have discovered that the
3926 dpkg-divert trick is not really needed and implemented a slightly
3927 simpler approach as part of the debian-edu-install package. See
3928 tools/edu-eatmydata-install in the source package.
</p
>
3930 <p
>Update
2014-
11-
11: Unfortunately, a new
3931 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3932 triggering on i386 made it into testing, and broke this installation
3933 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3934 request
768893</a
> is accepted, it should be working again.
</p
>
3939 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3940 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3941 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3942 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3943 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3944 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3945 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3946 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3947 learn that there is a large set of publicly available key servers to
3948 use when looking for peoples public key. So far I have used
3949 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3950 were misbehaving, but those days are ended. The servers I have used
3951 up until yesterday have been slow and some times unavailable. I hope
3952 those problems are gone now.
</p
>
3954 <p
>Behind the round robin DNS entry of the
3955 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3956 there is a pool of more than
100 keyservers which are checked every
3957 day to ensure they are well connected and up to date. It must be
3958 better than what I have used so far. :)
</p
>
3960 <p
>Yesterdays speaker told me that the service is the default
3961 keyserver provided by the default configuration in GnuPG, but this do
3962 not seem to be used in Debian. Perhaps it should?
</p
>
3964 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3967 <p
><blockquote
><pre
>
3968 keyserver pool.sks-keyservers.net
3969 </pre
></blockquote
></p
>
3971 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3972 entries in DNS. Just for fun, I did just that at work, so now every
3973 user of GnuPG at the University of Oslo should find a OpenGPG
3974 keyserver automatically should their need it:
</p
>
3976 <p
><blockquote
><pre
>
3977 % host -t srv _pgpkey-http._tcp.uio.no
3978 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3980 </pre
></blockquote
></p
>
3982 <p
>Now if only
3983 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3984 HKP lookup protocol
</a
> supported finding signature paths, I would be
3985 very happy. It can look up a given key or search for a user ID, but I
3986 normally do not want that, but to find a trust path from my key to
3987 another key. Given a user ID or key ID, I would like to find (and
3988 download) the keys representing a signature path from my key to the
3989 key in question, to be able to get a trust path between the two keys.
3990 This is as far as I can tell not possible today. Perhaps something
3991 for a future version of the protocol?
</p
>
3996 <title>From English wiki to translated PDF and epub via Docbook
</title>
3997 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3998 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3999 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4000 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4001 project
</a
> provide an instruction manual for teachers, system
4002 administrators and other users that contain useful tips for setting up
4003 and maintaining a Debian Edu installation. This text is about how the
4004 text processing of this manual is handled in the project.
</p
>
4006 <p
>One goal of the project is to provide information in the native
4007 language of its users, and for this we need to handle translations.
4008 But we also want to make sure each language contain the same
4009 information, so for this we need a good way to keep the translations
4010 in sync. And we want it to be easy for our users to improve the
4011 documentation, avoiding the need to learn special formats or tools to
4012 contribute, and the obvious way to do this is to make it possible to
4013 edit the documentation using a web browser. We also want it to be
4014 easy for translators to keep the translation up to date, and give them
4015 help in figuring out what need to be translated. Here is the list of
4016 tools and the process we have found trying to reach all these
4019 <p
>We maintain the authoritative source of our manual in the
4020 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4021 wiki
</a
>, as several wiki pages written in English. It consist of one
4022 front page with references to the different chapters, several pages
4023 for each chapter, and finally one
"collection page
" gluing all the
4024 chapters together into one large web page (aka
4025 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4026 AllInOne page
</a
>). The AllInOne page is the one used for further
4027 processing and translations. Thanks to the fact that the
4028 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4029 wiki.debian.org support exporting pages in
4030 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4031 the list of pages to export using the raw version of the AllInOne
4032 page, loop over each of them to generate a Docbook XML version of the
4033 manual. This process also download images and transform image
4034 references to use the locally downloaded images. The generated
4035 Docbook XML files are slightly broken, so some post-processing is done
4036 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4037 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4038 a handfull of images. The XML file can now be used to generate PDF, HTML
4039 and epub versions of the English manual. This is the basic step of
4040 our process, making PDF (using dblatex), HTML (using xsltproc) and
4041 epub (using dbtoepub) version from Docbook XML, and the resulting files
4042 are placed in the debian-edu-doc-en binary package.
</p
>
4044 <p
>But English documentation is not enough for us. We want translated
4045 documentation too, and we want to make it easy for translators to
4046 track the English original. For this we use the
4047 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4048 which allow us to transform the English Docbook XML file into a
4049 translation file (a .pot file), usable with the normal gettext based
4050 translation tools used by those translating free software. The pot
4051 file is used to create and maintain translation files (several .po
4052 files), which the translations update with the native language
4053 translations of all titles, paragraphs and blocks of text in the
4054 original. The next step is combining the original English Docbook XML
4055 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4056 create a translated Docbook XML file (in this case
4057 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4058 translated, if the translation is not complete) Docbook XML file can
4059 then be used like the original to create a PDF, HTML and epub version
4060 of the documentation.
</p
>
4062 <p
>The translators use different tools to edit the .po files. We
4064 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4065 while some use emacs and vi, others can use web based editors like
4066 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4067 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4068 is where the .po file end up, in our git repository. Updated
4069 translations can either be committed directly to git, or submitted as
4070 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4071 against the debian-edu-doc package
</a
>.
</p
>
4073 <p
>One challenge is images, which both might need to be translated (if
4074 they show translated user applications), and are needed in different
4075 formats when creating PDF and HTML versions (epub is a HTML version in
4076 this regard). For this we transform the original PNG images to the
4077 needed density and format during build, and have a way to provide
4078 translated images by storing translated versions in
4079 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4080 package maintainers know more.
</p
>
4082 <p
>If you wonder what the result look like, we provide
4083 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4084 of the documentation packages on the web
</a
>. See for example the
4085 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4086 PDF version
</a
> or the
4087 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4088 HTML version
</a
>. We do not yet build the epub version by default,
4089 but perhaps it will be done in the future.
</p
>
4091 <p
>To learn more, check out
4092 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4093 debian-edu-doc package
</a
>,
4094 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4095 manual on the wiki
</a
> and
4096 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4097 translation instructions
</a
> in the manual.
</p
>
4102 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4103 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4104 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4105 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4106 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4107 related packages relevant for the computer installed automatically.
4108 So I implemented one, using
4109 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4110 package
</a
>. To use it, install the tasksel and isenkram packages and
4111 run tasksel as user root. You should be presented with a new option,
4112 "Hardware specific packages (autodetected by isenkram)
". When you
4113 select it, tasksel will install the packages isenkram claim is fit for
4114 the current hardware, hot pluggable or not.
<p
>
4116 <p
>The implementation is in two files, one is the tasksel menu entry
4117 description, and the other is the script used to extract the list of
4118 packages to install. The first part is in
4119 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4122 <p
><blockquote
><pre
>
4125 Description: Hardware specific packages (autodetected by isenkram)
4126 Based on the detected hardware various hardware specific packages are
4128 Test-new-install: mark show
4130 Packages: for-current-hardware
4131 </pre
></blockquote
></p
>
4133 <p
>The second part is in
4134 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4137 <p
><blockquote
><pre
>
4142 isenkram-autoinstall-firmware -l
4144 </pre
></blockquote
></p
>
4146 <p
>All in all, a very short and simple implementation making it
4147 trivial to install the hardware dependent package we all may want to
4148 have installed on our machines. I
've not been able to find a way to
4149 get tasksel to tell you exactly which packages it plan to install
4150 before doing the installation. So if you are curious or careful,
4151 check the output from the isenkram-* command line tools first.
</p
>
4153 <p
>The information about which packages are handling which hardware is
4154 fetched either from the isenkram package itself in
4155 /usr/share/isenkram/, from git.debian.org or from the APT package
4156 database (using the Modaliases header). The APT package database
4157 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4158 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4159 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4160 the python-apt code (bug
4161 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4162 workaround I was able to get rid of the file descriptor leak and
4163 reduce the memory leak from ~
30 MiB per hardware detection down to
4164 around
2 MiB per hardware detection. It should make the desktop
4165 daemon a lot more useful. The fix is in version
0.7 uploaded to
4166 unstable today.
</p
>
4168 <p
>I believe the current way of mapping hardware to packages in
4169 Isenkram is is a good draft, but in the future I expect isenkram to
4170 use the AppStream data source for this. A proposal for getting proper
4171 AppStream support into Debian is floating around as
4172 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4173 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4174 project
</a
> will take place this summer to improve the situation. I
4175 look forward to seeing the result, and welcome patches for isenkram to
4176 start using the information when it is ready.
</p
>
4178 <p
>If you want your package to map to some specific hardware, either
4179 add a
"Xb-Modaliases
" header to your control file like I did in
4180 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4181 package
</a
> or submit a bug report with the details to the isenkram
4183 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4184 blog posts tagged isenkram
</a
> for details on the notation. I expect
4185 the information will be migrated to AppStream eventually, but for the
4186 moment I got no better place to store it.
</p
>
4191 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4192 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4193 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4194 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4195 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4196 project
</a
> is working on providing the software and hardware to make
4197 it easy for non-technical people to host their data and communication
4198 at home, and being able to communicate with their friends and family
4199 encrypted and away from prying eyes. It is still going strong, and
4200 today a major mile stone was reached.
</p
>
4202 <p
>Today, the last of the packages currently used by the project to
4203 created the system images were accepted into Debian Unstable. It was
4204 the freedombox-setup package, which is used to configure the images
4205 during build and on the first boot. Now all one need to get going is
4206 the build code from the freedom-maker git repository and packages from
4207 Debian. And once the freedombox-setup package enter testing, we can
4208 build everything directly from Debian. :)
</p
>
4210 <p
>Some key packages used by Freedombox are
4211 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4212 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4213 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4214 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4215 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4216 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4217 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4218 are plans to integrate more packages into the setup. User
4219 documentation is maintained on the Debian wiki. Please
4220 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4221 the manual
</a
> and help us improve it.
</p
>
4223 <p
>To test for yourself and create boot images with the FreedomBox
4224 setup, run this on a Debian machine using a user with sudo rights to
4225 become root:
</p
>
4227 <p
><pre
>
4228 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4229 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4231 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4233 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4234 </pre
></p
>
4236 <p
>Root access is needed to run debootstrap and mount loopback
4237 devices. See the README in the freedom-maker git repo for more
4238 details on the build. If you do not want all three images, trim the
4239 make line. Note that the virtualbox-image target is not really
4240 virtualbox specific. It create a x86 image usable in kvm, qemu,
4241 vmware and any other x86 virtual machine environment. You might need
4242 the version of vmdebootstrap in Jessie to get the build working, as it
4243 include fixes for a race condition with kpartx.
</p
>
4245 <p
>If you instead want to install using a Debian CD and the preseed
4246 method, boot a Debian Wheezy ISO and use this boot argument to load
4247 the preseed values:
</p
>
4249 <p
><pre
>
4250 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4251 </pre
></p
>
4253 <p
>I have not tested it myself the last few weeks, so I do not know if
4254 it still work.
</p
>
4256 <p
>If you wonder how to help, one task you could look at is using
4257 systemd as the boot system. It will become the default for Linux in
4258 Jessie, so we need to make sure it is usable on the Freedombox. I did
4259 a simple test a few weeks ago, and noticed dnsmasq failed to start
4260 during boot when using systemd. I suspect there are other problems
4261 too. :) To detect problems, there is a test suite included, which can
4262 be run from the plinth web interface.
</p
>
4264 <p
>Give it a go and let us know how it goes on the mailing list, and help
4265 us get the new release published. :) Please join us on
4266 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4267 irc.debian.org)
</a
> and
4268 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4269 mailing list
</a
> if you want to help make this vision come true.
</p
>
4274 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4275 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4276 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4277 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4278 <description><p
>For a while now, I have been looking for a sensible offsite backup
4279 solution for use at home. My requirements are simple, it must be
4280 cheap and locally encrypted (in other words, I keep the encryption
4281 keys, the storage provider do not have access to my private files).
4282 One idea me and my friends had many years ago, before the cloud
4283 storage providers showed up, was to use Google mail as storage,
4284 writing a Linux block device storing blocks as emails in the mail
4285 service provided by Google, and thus get heaps of free space. On top
4286 of this one can add encryption, RAID and volume management to have
4287 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4288 I never found time to implement such system. But the last few weeks I
4289 have looked at a system called
4290 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4291 mounted network backed file system with the features I need.
</p
>
4293 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4294 handling several different storage providers, any with Amazon S3,
4295 Google Drive or OpenStack API. There are heaps of such storage
4296 providers. S3QL can also use a local directory as storage, which
4297 combined with sshfs allow for file storage on any ssh server. S3QL
4298 include support for encryption, compression, de-duplication, snapshots
4299 and immutable file systems, allowing me to mount the remote storage as
4300 a local mount point, look at and use the files as if they were local,
4301 while the content is stored in the cloud as well. This allow me to
4302 have a backup that should survive fire. The file system can not be
4303 shared between several machines at the same time, as only one can
4304 mount it at the time, but any machine with the encryption key and
4305 access to the storage service can mount it if it is unmounted.
</p
>
4307 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4308 package is included already. So to get started, run
<tt
>apt-get
4309 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4310 Greenqloud, after reading their nice recipe on
4311 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4312 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4313 in Iceland more than those in USA when it come to keeping my personal
4314 data safe and private, and thus would rather spend money on a company
4315 in Iceland. Another nice recipe is available from the article
4316 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4317 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4318 Admin magazine. When the provider is picked, figure out how to get
4319 the API key needed to connect to the storage API. With Greencloud,
4320 the key did not show up until I had added payment details to my
4323 <p
>Armed with the API access details, it is time to create the file
4324 system. First, create a new bucket in the cloud. This bucket is the
4325 file system storage area. I picked a bucket name reflecting the
4326 machine that was going to store data there, but any name will do.
4327 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4328 the API login and password, and a locally created password. Store it
4329 all in ~root/.s3ql/authinfo2 like this:
4331 <p
><blockquote
><pre
>
4333 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4334 backend-login: API-login
4335 backend-password: API-password
4336 fs-passphrase: local-password
4337 </pre
></blockquote
></p
>
4339 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4340 but any sensible way to create a fairly random password should do it.
4341 Armed with these details, it is now time to run mkfs, entering the API
4342 details and password to create it:
</p
>
4344 <p
><blockquote
><pre
>
4345 # mkdir -m
700 /var/lib/s3ql-cache
4346 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4347 --ssl s3c://s.greenqloud.com:
443/bucket-name
4348 Enter backend login:
4349 Enter backend password:
4350 Before using S3QL, make sure to read the user
's guide, especially
4351 the
'Important Rules to Avoid Loosing Data
' section.
4352 Enter encryption password:
4353 Confirm encryption password:
4354 Generating random encryption key...
4355 Creating metadata tables...
4365 Compressing and uploading metadata...
4366 Wrote
0.00 MB of compressed metadata.
4367 #
</pre
></blockquote
></p
>
4369 <p
>The next step is mounting the file system to make the storage available.
4371 <p
><blockquote
><pre
>
4372 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4373 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4374 Using
4 upload threads.
4375 Downloading and decompressing metadata...
4385 Mounting filesystem...
4387 Filesystem Size Used Avail Use% Mounted on
4388 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4390 </pre
></blockquote
></p
>
4392 <p
>The file system is now ready for use. I use rsync to store my
4393 backups in it, and as the metadata used by rsync is downloaded at
4394 mount time, no network traffic (and storage cost) is triggered by
4395 running rsync. To unmount, one should not use the normal umount
4396 command, as this will not flush the cache to the cloud storage, but
4397 instead running the umount.s3ql command like this:
4399 <p
><blockquote
><pre
>
4402 </pre
></blockquote
></p
>
4404 <p
>There is a fsck command available to check the file system and
4405 correct any problems detected. This can be used if the local server
4406 crashes while the file system is mounted, to reset the
"already
4407 mounted
" flag. This is what it look like when processing a working
4408 file system:
</p
>
4410 <p
><blockquote
><pre
>
4411 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4412 Using cached metadata.
4413 File system seems clean, checking anyway.
4414 Checking DB integrity...
4415 Creating temporary extra indices...
4416 Checking lost+found...
4417 Checking cached objects...
4418 Checking names (refcounts)...
4419 Checking contents (names)...
4420 Checking contents (inodes)...
4421 Checking contents (parent inodes)...
4422 Checking objects (reference counts)...
4423 Checking objects (backend)...
4424 ..processed
5000 objects so far..
4425 ..processed
10000 objects so far..
4426 ..processed
15000 objects so far..
4427 Checking objects (sizes)...
4428 Checking blocks (referenced objects)...
4429 Checking blocks (refcounts)...
4430 Checking inode-block mapping (blocks)...
4431 Checking inode-block mapping (inodes)...
4432 Checking inodes (refcounts)...
4433 Checking inodes (sizes)...
4434 Checking extended attributes (names)...
4435 Checking extended attributes (inodes)...
4436 Checking symlinks (inodes)...
4437 Checking directory reachability...
4438 Checking unix conventions...
4439 Checking referential integrity...
4440 Dropping temporary indices...
4441 Backing up old metadata...
4451 Compressing and uploading metadata...
4452 Wrote
0.89 MB of compressed metadata.
4454 </pre
></blockquote
></p
>
4456 <p
>Thanks to the cache, working on files that fit in the cache is very
4457 quick, about the same speed as local file access. Uploading large
4458 amount of data is to me limited by the bandwidth out of and into my
4459 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4460 which is very close to my upload speed, and downloading the same
4461 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4462 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4463 network, not the file system code. I do not know what a good cache
4464 size would be, but suspect that the cache should e larger than your
4465 working set.
</p
>
4467 <p
>I mentioned that only one machine can mount the file system at the
4468 time. If another machine try, it is told that the file system is
4471 <p
><blockquote
><pre
>
4472 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4473 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4474 Using
8 upload threads.
4475 Backend reports that fs is still mounted elsewhere, aborting.
4477 </pre
></blockquote
></p
>
4479 <p
>The file content is uploaded when the cache is full, while the
4480 metadata is uploaded once every
24 hour by default. To ensure the
4481 file system content is flushed to the cloud, one can either umount the
4482 file system, or ask S3QL to flush the cache and metadata using
4485 <p
><blockquote
><pre
>
4486 # s3qlctrl upload-meta /s3ql
4487 # s3qlctrl flushcache /s3ql
4489 </pre
></blockquote
></p
>
4491 <p
>If you are curious about how much space your data uses in the
4492 cloud, and how much compression and deduplication cut down on the
4493 storage usage, you can use s3qlstat on the mounted file system to get
4496 <p
><blockquote
><pre
>
4498 Directory entries:
9141
4501 Total data size:
22049.38 MB
4502 After de-duplication:
21955.46 MB (
99.57% of total)
4503 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4504 Database size:
2.39 MB (uncompressed)
4505 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4507 </pre
></blockquote
></p
>
4509 <p
>I mentioned earlier that there are several possible suppliers of
4510 storage. I did not try to locate them all, but am aware of at least
4511 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4512 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4513 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4514 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4515 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4516 accept payment in Bitcoin. Pick one that suit your need. Some of
4517 them provide several GiB of free storage, but the prize models are
4518 quite different and you will have to figure out what suits you
4521 <p
>While researching this blog post, I had a look at research papers
4522 and posters discussing the S3QL file system. There are several, which
4523 told me that the file system is getting a critical check by the
4524 science community and increased my confidence in using it. One nice
4526 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4527 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4528 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4529 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4530 and Pamela Smith. Please have a look.
</p
>
4532 <p
>Given my problems with different file systems earlier, I decided to
4533 check out the mounted S3QL file system to see if it would be usable as
4534 a home directory (in other word, that it provided POSIX semantics when
4535 it come to locking and umask handling etc). Running
4536 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4537 test code to check file system semantics
</a
>, I was happy to discover that
4538 no error was found. So the file system can be used for home
4539 directories, if one chooses to do so.
</p
>
4541 <p
>If you do not want a locally file system, and want something that
4542 work without the Linux fuse file system, I would like to mention the
4543 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4544 provide locally encrypted backup using a command line client. It have
4545 a nicer access control system, where one can split out read and write
4546 access, allowing some systems to write to the backup and others to
4547 only read from it.
</p
>
4549 <p
>As usual, if you use Bitcoin and want to show your support of my
4550 activities, please send Bitcoin donations to my address
4551 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4556 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4557 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4558 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4559 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4560 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4561 project
</a
> is working on providing the software and hardware for
4562 making it easy for non-technical people to host their data and
4563 communication at home, and being able to communicate with their
4564 friends and family encrypted and away from prying eyes. It has been
4565 going on for a while, and is slowly progressing towards a new test
4566 release (
0.2).
</p
>
4568 <p
>And what day could be better than the Pi day to announce that the
4569 new version will provide
"hard drive
" / SD card / USB stick images for
4570 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4571 system), and can also be installed using a Debian installer preseed
4572 file. The Debian based Freedombox is now based on Debian Jessie,
4573 where most of the needed packages used are already present. Only one,
4574 the freedombox-setup package, is missing. To try to build your own
4575 boot image to test the current status, fetch the freedom-maker scripts
4577 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4578 with a user with sudo access to become root:
4581 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4583 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4584 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4586 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4589 <p
>Root access is needed to run debootstrap and mount loopback
4590 devices. See the README for more details on the build. If you do not
4591 want all three images, trim the make line. But note that thanks to
<a
4592 href=
"https://bugs.debian.org/
741407">a race condition in
4593 vmdebootstrap
</a
>, the build might fail without the patch to the
4594 kpartx call.
</p
>
4596 <p
>If you instead want to install using a Debian CD and the preseed
4597 method, boot a Debian Wheezy ISO and use this boot argument to load
4598 the preseed values:
</p
>
4601 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4604 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4605 recently introduced bug in apt in Jessie
</a
>, the installer will
4606 currently hang while setting up APT sources. Killing the
4607 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4608 installation will get the installation going. This affect all
4609 installations in Jessie, and I expect it will be fixed soon.
</p
>
4611 <p
>Give it a go and let us know how it goes on the mailing list, and help
4612 us get the new release published. :) Please join us on
4613 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4614 irc.debian.org)
</a
> and
4615 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4616 mailing list
</a
> if you want to help make this vision come true.
</p
>
4621 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4622 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4623 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4624 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4625 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4626 innetgr tools, because I needed them in
4627 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4628 ng-utils, and it has served me well. I placed the project under the
4629 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4630 repository. But many years ago, the CVS repository was dropped (lost,
4631 not migrated to new hardware, not sure), and the project have lacked a
4632 proper home since then.
</p
>
4634 <p
>Last summer, I had a look at the package and made a new release
4635 fixing a irritating crash bug, but was unable to store the changes in
4636 a proper source control system. I applied for a project on
4637 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4638 to follow up on it. Until today. :)
</p
>
4640 <p
>After many hours of cleaning and migration, the ng-utils project
4641 now have a new home, and a git repository with the highlight of the
4642 history of the project. I published all release tarballs and imported
4643 them into the git repository. As the project is really stable and not
4644 expected to gain new features any time soon, I decided to make a new
4645 release and call it
1.0. Visit the new project home on
4646 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4647 if you want to check it out. The new version is also uploaded into
4648 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4653 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4654 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4655 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4656 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4657 <description><p
>A few days ago I decided to try to help the Hurd people to get
4658 their changes into sysvinit, to allow them to use the normal sysvinit
4659 boot system instead of their old one. This follow up on the
4660 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4661 Google Summer of Code work
</a
> done last summer by Justus Winter to
4662 get Debian on Hurd working more like Debian on Linux. To get started,
4663 I downloaded a prebuilt hard disk image from
4664 <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
>,
4665 and started it using virt-manager.
</p
>
4667 <p
>The first think I had to do after logging in (root without any
4668 password) was to get the network operational. I followed
4669 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4670 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4671 commands as root to get the machine to accept a IP address from the
4672 kvm internal DHCP server:
</p
>
4674 <p
><blockquote
><pre
>
4675 settrans -fgap /dev/netdde /hurd/netdde
4676 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4677 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4679 </pre
></blockquote
></p
>
4681 <p
>After this, the machine had internet connectivity, and I could
4682 upgrade it and install the sysvinit packages from experimental and
4683 enable it as the default boot system in Hurd.
</p
>
4685 <p
>But before I did that, I set a password on the root user, as ssh is
4686 running on the machine it for ssh login to work a password need to be
4687 set. Also, note that a bug somewhere in openssh on Hurd block
4688 compression from working. Remember to turn that off on the client
4691 <p
>Run these commands as root to upgrade and test the new sysvinit
4694 <p
><blockquote
><pre
>
4695 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4696 deb http://http.debian.net/debian/ experimental main
4699 apt-get dist-upgrade
4700 apt-get install -t experimental initscripts sysv-rc sysvinit \
4701 sysvinit-core sysvinit-utils
4702 update-alternatives --config runsystem
4703 </pre
></blockquote
></p
>
4705 <p
>To reboot after switching boot system, you have to use
4706 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4707 yet a sysvinit process able to receive the signals from the normal
4708 'reboot
' command. After switching to sysvinit as the boot system,
4709 upgrading every package and rebooting, the network come up with DHCP
4710 after boot as it should, and the settrans/pkill hack mentioned at the
4711 start is no longer needed. But for some strange reason, there are no
4712 longer any login prompt in the virtual console, so I logged in using
4715 <p
>Note that there are some race conditions in Hurd making the boot
4716 fail some times. No idea what the cause is, but hope the Hurd porters
4717 figure it out. At least Justus said on IRC (#debian-hurd on
4718 irc.debian.org) that they are aware of the problem. A way to reduce
4719 the impact is to upgrade to the Hurd packages built by Justus by
4720 adding this repository to the machine:
</p
>
4722 <p
><blockquote
><pre
>
4723 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4724 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4726 </pre
></blockquote
></p
>
4728 <p
>At the moment the prebuilt virtual machine get some packages from
4729 http://ftp.debian-ports.org/debian, because some of the packages in
4730 unstable do not yet include the required patches that are lingering in
4731 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4733 <p
><blockquote
><pre
>
4734 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4735 i emacs - GNU Emacs editor (metapackage)
4736 i gdb - GNU Debugger
4737 i hurd-recommended - Miscellaneous translators
4738 i isc-dhcp-client - ISC DHCP client
4739 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4740 i libc-bin - Embedded GNU C Library: Binaries
4741 i libc-dev-bin - Embedded GNU C Library: Development binaries
4742 i libc0.3 - Embedded GNU C Library: Shared libraries
4743 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4744 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4745 i multiarch-support - Transitional package to ensure multiarch compatibilit
4746 i A x11-common - X Window System (X.Org) infrastructure
4747 i xorg - X.Org X Window System
4748 i A xserver-xorg - X.Org X server
4749 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4751 </pre
></blockquote
></p
>
4753 <p
>All in all, testing hurd has been an interesting experience. :)
4754 X.org did not work out of the box and I never took the time to follow
4755 the porters instructions to fix it. This time I was interested in the
4756 command line stuff.
<p
>
4761 <title>New chrpath release
0.16</title>
4762 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4763 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4764 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4765 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4766 find problems in C, C++ and Java code using static source code
4767 analysis. It can detect a lot of different problems, and is very
4768 useful to find memory and locking bugs in the error handling part of
4769 the source. The company behind it provide
4770 <a href=
"https://scan.coverity.com/
">check of free software projects as
4771 a community service
</a
>, and many hundred free software projects are
4772 already checked. A few days ago I decided to have a closer look at
4773 the Coverity system, and discovered that the
4774 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4775 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4776 projects I am involved with was already registered. But these are
4777 fairly big, and I would also like to have a small and easy project to
4778 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4779 checking of the chrpath project
</a
>. It was
4780 added to the checker and discovered seven potential defects. Six of
4781 these were real, mostly resource
"leak
" when the program detected an
4782 error. Nothing serious, as the resources would be released a fraction
4783 of a second later when the program exited because of the error, but it
4784 is nice to do it right in case the source of the program some time in
4785 the future end up in a library. Having fixed all defects and added
4786 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4787 mailing list for the chrpath developers
</a
>, I decided it was time to
4788 publish a new release. These are the release notes:
</p
>
4790 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4794 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4795 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4796 <li
>Mention new project mailing list in the documentation.
</li
>
4801 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4802 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4803 project if something is wrong with the new release. The test suite
4804 did not discover any old errors, so if you find a new one, please also
4805 include a test suite check.
</p
>
4810 <title>New chrpath release
0.15</title>
4811 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4812 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4813 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4814 <description><p
>After many years break from the package and a vain hope that
4815 development would be continued by someone else, I finally pulled my
4816 acts together this morning and wrapped up a new release of chrpath,
4817 the command line tool to modify the rpath and runpath of already
4818 compiled ELF programs. The update was triggered by the persistence of
4819 Isha Vishnoi at IBM, which needed a new config.guess file to get
4820 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4821 is working on. I checked the
4822 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4823 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4824 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4825 packages for interesting patches (failed to find the source from
4826 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4827 These are the release notes:
</p
>
4829 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4833 <li
>Updated config.sub and config.guess from the GNU project to work
4834 with newer architectures. Thanks to isha vishnoi for the heads
4837 <li
>Updated README with current URLs.
</li
>
4839 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4840 Matthias Klose.
</li
>
4842 <li
>Added missing help for -k|--keepgoing option, using patch by
4843 Petr Machata found in Fedora.
</li
>
4845 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4846 .dynamic is a NULL terminated string. Based on patch found in
4847 Fedora credited Axel Thimm and Christian Krause.
</li
>
4852 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4853 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4854 project if something is wrong with the new release. The test suite
4855 did not discover any old errors, so if you find a new one, please also
4856 include a testsuite check.
</p
>
4861 <title>Debian init.d boot script example for rsyslog
</title>
4862 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4863 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4864 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4865 <description><p
>If one of the points of switching to a new init system in Debian is
4866 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4867 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4868 init.d scripts at all. Here is an example init.d script, ie a rewrite
4869 of /etc/init.d/rsyslog:
</p
>
4871 <p
><pre
>
4872 #!/lib/init/init-d-script
4875 # Required-Start: $remote_fs $time
4876 # Required-Stop: umountnfs $time
4877 # X-Stop-After: sendsigs
4878 # Default-Start:
2 3 4 5
4879 # Default-Stop:
0 1 6
4880 # Short-Description: enhanced syslogd
4881 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4882 # It is quite compatible to stock sysklogd and can be
4883 # used as a drop-in replacement.
4885 DESC=
"enhanced syslogd
"
4886 DAEMON=/usr/sbin/rsyslogd
4887 </pre
></p
>
4889 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4890 script was
137 lines, and the above is just
15 lines, most of it meta
4891 info/comments.
</p
>
4893 <p
>How to do this, you ask? Well, one create a new script
4894 /lib/init/init-d-script looking something like this:
4896 <p
><pre
>
4899 # Define LSB log_* functions.
4900 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4901 # and status_of_proc is working.
4902 . /lib/lsb/init-functions
4905 # Function that starts the daemon/service
4911 #
0 if daemon has been started
4912 #
1 if daemon was already running
4913 #
2 if daemon could not be started
4914 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4916 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4919 # Add code here, if necessary, that waits for the process to be ready
4920 # to handle requests from services started subsequently which depend
4921 # on this one. As a last resort, sleep for some time.
4925 # Function that stops the daemon/service
4930 #
0 if daemon has been stopped
4931 #
1 if daemon was already stopped
4932 #
2 if daemon could not be stopped
4933 # other if a failure occurred
4934 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4935 RETVAL=
"$?
"
4936 [
"$RETVAL
" =
2 ]
&& return
2
4937 # Wait for children to finish too if this is a daemon that forks
4938 # and if the daemon is only ever run from this initscript.
4939 # If the above conditions are not satisfied then add some other code
4940 # that waits for the process to drop all resources that could be
4941 # needed by services started subsequently. A last resort is to
4942 # sleep for some time.
4943 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4944 [
"$?
" =
2 ]
&& return
2
4945 # Many daemons don
't delete their pidfiles when they exit.
4947 return
"$RETVAL
"
4951 # Function that sends a SIGHUP to the daemon/service
4955 # If the daemon can reload its configuration without
4956 # restarting (for example, when it is sent a SIGHUP),
4957 # then implement that here.
4959 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4964 scriptbasename=
"$(basename $
1)
"
4965 echo
"SN: $scriptbasename
"
4966 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4967 script=
"$
1"
4974 NAME=$(basename $DAEMON)
4975 PIDFILE=/var/run/$NAME.pid
4977 # Exit if the package is not installed
4978 #[ -x
"$DAEMON
" ] || exit
0
4980 # Read configuration variable file if it is present
4981 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4983 # Load the VERBOSE setting and other rcS variables
4986 case
"$
1" in
4988 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4990 case
"$?
" in
4991 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4992 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4996 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4998 case
"$?
" in
4999 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5000 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5004 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5006 #reload|force-reload)
5008 # If do_reload() is not implemented then leave this commented out
5009 # and leave
'force-reload
' as an alias for
'restart
'.
5011 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5015 restart|force-reload)
5017 # If the
"reload
" option is implemented then remove the
5018 #
'force-reload
' alias
5020 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5022 case
"$?
" in
5025 case
"$?
" in
5027 1) log_end_msg
1 ;; # Old process is still running
5028 *) log_end_msg
1 ;; # Failed to start
5038 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5044 </pre
></p
>
5046 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5047 lot. I did not really polish the approach, so it might not always
5048 work out of the box, but you get the idea. I did not try very hard to
5049 optimize it nor make it more robust either.
</p
>
5051 <p
>A better argument for switching init system in Debian than reducing
5052 the size of init scripts (which is a good thing to do anyway), is to
5053 get boot system that is able to handle the kernel events sensibly and
5054 robustly, and do not depend on the boot to run sequentially. The boot
5055 and the kernel have not behaved sequentially in years.
</p
>
5060 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5061 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5062 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5063 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5064 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5065 remote display access is the preferred solution with oVirt and RedHat
5066 Enterprise Virtualization, and I was sad to discover the other day
5067 that the browser plugin needed to use these systems seamlessly was
5068 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5069 for a package
</a
> was from
2012-
04-
10 with no progress since
5070 2013-
04-
01, so I decided to wrap up a package based on the great work
5071 from Cajus Pollmeier and put it in a collab-maint maintained git
5072 repository to get a package I could use. I would very much like
5073 others to help me maintain the package (or just take over, I do not
5074 mind), but as no-one had volunteered so far, I just uploaded it to
5075 NEW. I hope it will be available in Debian in a few days.
</p
>
5077 <p
>The source is now available from
5078 <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
>
5083 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5084 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5085 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5086 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5087 <description><p
>The
5088 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5089 program is a a very nice system to create virtual machine images. It
5090 create a image file, add a partition table, mount it and run
5091 debootstrap in the mounted directory to create a Debian system on a
5092 stick. Yesterday, I decided to try to teach it how to make images for
5093 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5094 of a plan to simplify the build system for
5095 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5096 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5097 the virtualbox images, but its current build system made multistrap
5098 based system for Dreamplug images, and it is lacking support for
5099 Raspberry Pi.
</p
>
5101 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5102 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5103 code and adjusted it to be able to build armel images on my amd64
5104 Debian laptop. I ended up giving vmdebootstrap five new options,
5105 allowing me to replicate the image creation process I use to make
5106 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5107 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5108 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5109 call debootstrap with --foreign and to copy the handler into the
5110 generated chroot before running the second stage. This allow
5111 vmdebootstrap to create armel images on an amd64 host. Next I added
5112 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5113 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5114 given file system type, allowing me to create an image with a vfat
5115 partition for the /boot/ stuff. I also added a
<tt
>--variant
5116 variant
</tt
> option to allow me to create smaller images without the
5117 Debian base system packages installed. Finally, I added an option
5118 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5119 as a boot loader. It is not needed on the Raspberry Pi and probably
5120 most other non-x86 architectures. The changes were accepted by the
5121 upstream author of vmdebootstrap yesterday and today, and is now
5123 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5124 upstream project page
</a
>.
</p
>
5126 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5127 create a small script (the customize script) to add the non-free
5128 binary blob needed to boot the Raspberry Pi and the APT source
5131 <p
><pre
>
5133 set -e # Exit on first error
5134 rootdir=
"$
1"
5135 cd
"$rootdir
"
5136 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5137 deb http://http.debian.net/debian/ jessie main contrib non-free
5139 # Install non-free binary blob needed to boot Raspberry Pi. This
5140 # install a kernel somewhere too.
5141 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5142 -O $rootdir/usr/bin/rpi-update
5143 chmod a+x $rootdir/usr/bin/rpi-update
5144 mkdir -p $rootdir/lib/modules
5145 touch $rootdir/boot/start.elf
5146 chroot $rootdir rpi-update
5147 </pre
></p
>
5149 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5150 to build the image:
</p
>
5153 sudo ./vmdebootstrap \
5156 --distribution jessie \
5157 --mirror http://http.debian.net/debian \
5166 --root-password raspberry \
5167 --hostname raspberrypi \
5168 --foreign /usr/bin/qemu-arm-static \
5169 --customize `pwd`/customize \
5171 --package git-core \
5172 --package binutils \
5173 --package ca-certificates \
5176 </pre
></p
>
5178 <p
>The list of packages being installed are the ones needed by
5179 rpi-update to make the image bootable on the Raspberry Pi, with the
5180 exception of netbase, which is needed by debootstrap to find
5181 /etc/hosts with the minbase variant. I really wish there was a way to
5182 set up an Raspberry Pi using only packages in the Debian archive, but
5183 that is not possible as far as I know, because it boots from the GPU
5184 using a non-free binary blob.
</p
>
5186 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5187 probably a few others installed. I have not checked the complete
5188 build dependency list.
</p
>
5190 <p
>The resulting image will not use the hardware floating point unit
5191 on the Raspberry PI, because the armel architecture in Debian is not
5192 optimized for that use. So the images created will be a bit slower
5193 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5198 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5199 <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>
5200 <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>
5201 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5202 <description><p
>The last few days I came across a few good causes that should get
5203 wider attention. I recommend signing and donating to each one of
5206 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5207 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5208 Women program which is a Google Summer of Code like initiative to get
5209 more women involved in free software. One debian sponsor has offered
5210 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5211 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5212 hope you will to. :)
</p
>
5214 <p
>And the Electronic Frontier Foundation just announced plans to
5215 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5216 documentaries about the excessive spying
</a
> on every Internet user that
5217 take place these days, and their need to fund the work. I
've already
5218 donated. Are you next?
</p
>
5220 <p
>For my Norwegian audience, the organisation Studentenes og
5221 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5222 statement under the heading
5223 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5224 Access
</a
> for those of us asking for more focus on open access in the
5225 Norwegian government. So far
499 signatures. I hope you will sign it
5231 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5232 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5233 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5234 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5235 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5236 project
</a
> have been going on for a while, and have presented the
5237 vision, ideas and solution several places. Here is a little
5238 collection of videos of talks and presentation of the project.
</p
>
5242 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5243 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5245 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5246 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5248 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5249 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5250 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5251 (Youtube)
</li
>
5253 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5254 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5256 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5257 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5259 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5260 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5261 York City in
2012</a
> (Youtube)
</li
>
5263 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5264 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5265 (Youtube)
</li
>
5267 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5268 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5270 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5271 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5273 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5274 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5275 2013</a
> (Youtube)
</li
>
5279 <p
>A larger list is available from
5280 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5281 Freedombox Wiki
</a
>.
</p
>
5283 <p
>On other news, I am happy to report that Freedombox based on Debian
5284 Jessie is coming along quite well, and soon both Owncloud and using
5285 Tor should be available for testers of the Freedombox solution. :) In
5286 a few weeks I hope everything needed to test it is included in Debian.
5287 The withsqlite package is already in Debian, and the plinth package is
5288 pending in NEW. The third and vital part of that puzzle is the
5289 metapackage/setup framework, which is still pending an upload. Join
5290 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5291 (#freedombox on irc.debian.org)
</a
> and
5292 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5293 mailing list
</a
> if you want to help make this vision come true.
</p
>
5298 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5299 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5300 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5301 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5302 <description><p
>I was introduced to the
5303 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5304 in
2010, when Eben Moglen presented his vision about serving the need
5305 of non-technical people to keep their personal information private and
5306 within the legal protection of their own homes. The idea is to give
5307 people back the power over their network and machines, and return
5308 Internet back to its intended peer-to-peer architecture. Instead of
5309 depending on a central service, the Freedombox will give everyone
5310 control over their own basic infrastructure.
</p
>
5312 <p
>I
've intended to join the effort since then, but other tasks have
5313 taken priority. But this summers nasty news about the misuse of trust
5314 and privilege exercised by the
"western
" intelligence gathering
5315 communities increased my eagerness to contribute to a point where I
5316 actually started working on the project a while back.
</p
>
5318 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5319 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5320 create a simple and cheap Debian based appliance that anyone can hook
5321 up in their home and get access to secure and private services and
5322 communication. The initial deployment platform have been the
5323 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5324 which is a piece of hardware I do not own. So to be able to test what
5325 the current Freedombox setup look like, I had to come up with a way to install
5326 it on some hardware I do have access to. I have rewritten the
5327 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5328 image build framework to use .deb packages instead of only copying
5329 setup into the boot images, and thanks to this rewrite I am able to
5330 set up any machine supported by Debian Wheezy as a Freedombox, using
5331 the previously mentioned deb (and a few support debs for packages
5332 missing in Debian).
</p
>
5334 <p
>The current Freedombox setup consist of a set of bootstrapping
5336 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5337 and a administrative web interface
5338 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5339 withsqlite), as well as a privacy enhancing proxy based on
5340 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5341 (freedombox-privoxy). There is also a web/javascript based XMPP
5342 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5343 trying (unsuccessfully so far) to talk to the XMPP server
5344 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5345 web interface is pluggable, and the goal is to use it to enable OpenID
5346 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5347 this is really working yet, see
5348 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5349 project TODO
</a
> for links to GIT repositories. Most of the code is
5350 on github at the moment. The HTTP proxy is operational out of the
5351 box, and the admin web interface can be used to add/remove plinth
5352 users. I
've not been able to do anything else with it so far, but
5353 know there are several branches spread around github and other places
5354 with lots of half baked features.
</p
>
5356 <p
>Anyway, if you want to have a look at the current state, the
5357 following recipes should work to give you a test machine to poke
5360 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5364 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5365 <li
>Boot from it, either as CD or USB stick.
</li
>
5366 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5367 to the Debian installer:
<p
>
5368 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5370 <li
>Answer the few language/region/password questions and pick disk to
5371 install on.
</li
>
5373 <li
>When the installation is finished and the machine have rebooted a
5374 few times, your Freedombox is ready for testing.
</li
>
5378 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5382 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5383 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5384 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5386 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5387 </pre
></li
>
5388 <li
><p
>Run this as root:
</p
>
5390 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5393 apt-get install freedombox-setup
5394 /usr/lib/freedombox/setup
5395 </pre
></li
>
5396 <li
>Reboot into your freshly created Freedombox.
</li
>
5400 <p
>You can test it on other architectures too, but because the
5401 freedombox-privoxy package is binary, it will only work as intended on
5402 the architectures where I have had time to build the binary and put it
5403 in my APT repository. But do not let this stop you. It is only a
5404 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5406 <p
>Note that by default Freedombox is a DHCP server on the
5407 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5408 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5409 disable
</tt
>" as root.
</p
>
5411 <p
>Please let me know if this works for you, or if you have any
5412 problems. We gather on the IRC channel
5413 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5414 irc.debian.org and the
5415 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5416 mailing list
</a
>.
</p
>
5418 <p
>Once you get your freedombox operational, you can visit
5419 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5420 welcome screen (dead end - do not be surprised if you are unable to
5421 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5422 to look at the rest of plinth. The default user is
'admin
' and the
5423 default password is
'secret
'.
</p
>
5428 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5429 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5430 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5431 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5432 <description><p
>Earlier, I reported about
5433 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5434 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5435 told by IBM that the original disk should be thrown away. And as
5436 there no longer was a problem if I bricked the firmware, I decided
5437 today to try to install Intel firmware to replace the Lenovo firmware
5438 currently on the disk.
</p
>
5440 <p
>I searched the Intel site for firmware, and found
5441 <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
>
5442 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5443 according to the site should contain the latest firmware for SSD
5444 disks. I inserted the broken disk in one of my spare laptops and
5445 booted the ISO from a USB stick. The disk was recognized, but the
5446 program claimed the newest firmware already were installed and refused
5447 to insert any Intel firmware. So no change, and the disk is still
5448 unable to handle write load. :( I guess the only way to get them
5449 working would be if Lenovo releases new firmware. No idea how likely
5450 that is. Anyway, just blogging about this test for completeness. I
5451 got a working Samsung disk, and see no point in spending more time on
5452 the broken disks.
</p
>
5457 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5458 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5459 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5460 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5461 <description><p
>Today I switched to
5462 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5463 new laptop
</a
>. I
've previously written about the problems I had with
5464 my new Thinkpad X230, which was delivered with an
5465 <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
5466 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5467 sustained writes. My hardware supplier have been very forthcoming in
5468 trying to find a solution, and after first trying with another
5469 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5470 disk instead to fix it once and for all. The Samsung disk survived
5471 the installation of Debian with encrypted disks (filling the disk with
5472 random data during installation killed the first two), and I thus
5473 decided to trust it with my data. I have installed it as a Debian Edu
5474 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5475 server at home using Kerberos and LDAP, and will use it as my work
5476 station from now on.
</p
>
5478 <p
>As this is a solid state disk with no moving parts, I believe the
5479 Debian Wheezy default installation need to be tuned a bit to increase
5480 performance and increase life time of the disk. The Linux kernel and
5481 user space applications do not yet adjust automatically to such
5482 environment. To make it easier for my self, I created a draft Debian
5483 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5484 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5485 for the ssd-setup package
</a
> is available from collab-maint, and it
5486 is set up to adjust the setup of the machine by just installing the
5487 package. If there is any non-SSD disk in the machine, the package
5488 will refuse to install, as I did not try to write any logic to sort
5489 file systems in SSD and non-SSD file systems.
</p
>
5491 <p
>I consider the package a draft, as I am a bit unsure how to best
5492 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5493 where I set up the machine with one large encrypted partition (in
5494 addition to /boot), put LVM on top of this and set up partitions on
5495 top of this again. See the README file in the package source for the
5496 references I used to pick the settings. At the moment these
5497 parameters are tuned:
</p
>
5501 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5502 (adding discard to /etc/crypttab)
</li
>
5504 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5505 this case a cryptsetup partition) by changing issue_discards from
5506 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5508 <li
>Set relatime as a file system option for ext3 and ext4 file
5511 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5512 /etc/fstab.
</li
>
5514 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5516 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5517 cron.daily).
</li
>
5519 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5520 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5524 <p
>During installation, I cancelled the part where the installer fill
5525 the disk with random data, as this would kill the SSD performance for
5526 little gain. My goal with the encrypted file system is to ensure
5527 those stealing my laptop end up with a brick and not a working
5528 computer. I have no hope in keeping the really resourceful people
5529 from getting the data on the disk (see
5530 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5531 Thus I concluded that adding the discard option to crypttab is the
5532 right thing to do.
</p
>
5534 <p
>I considered using the noop I/O scheduler, as several recommended
5535 it for SSD, but others recommended deadline and a benchmark I found
5536 indicated that deadline might be better for interactive use.
</p
>
5538 <p
>I also considered using the
'discard
' file system option for ext3
5539 and ext4, but read that it would give a performance hit ever time a
5540 file is removed, and thought it best to that that slowdown once a day
5541 instead of during my work.
</p
>
5543 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5544 this is already done by Debian Edu.
</p
>
5546 <p
>I have not yet started on the user space tuning. I expect
5547 iceweasel need some tuning, and perhaps other applications too, but
5548 have not yet had time to investigate those parts.
</p
>
5550 <p
>The package should work on Ubuntu too, but I have not yet tested it
5553 <p
>As for the answer to the question in the title of this blog post,
5554 as far as I know, the only solution I know about is to replace the
5555 disk. It might be possible to flash it with Intel firmware instead of
5556 the Lenovo firmware. But I have not tried and did not want to do so
5557 without approval from Lenovo as I wanted to keep the warranty on the
5558 disk until a solution was found and they wanted the broken disks
5564 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5565 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5566 <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>
5567 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5568 <description><p
>A few days ago, I wrote about
5569 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5570 problems I experienced with my new X230 and its SSD disk
</a
>, which
5571 was dying during installation because it is unable to cope with
5572 sustained write. My supplier is in contact with
5573 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5574 replacement disk to try to fix the problem. They decided to send an
5575 identical model, so my hopes for a permanent fix was slim.
</p
>
5577 <p
>Anyway, today I got the replacement disk and tried to install
5578 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5579 same firmware version as the original. This time my hope raised
5580 slightly as the installation progressed, as the original disk used to
5581 die after
4-
7% of the disk was written to, while this time it kept
5582 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5583 died again and I was back on square one. I still do not have a new
5584 laptop with a disk I can trust. I can not live with a disk that might
5585 lock up when I download a new
5586 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5587 other large files. I look forward to hearing from my supplier with
5588 the next proposal from Lenovo.
</p
>
5590 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5591 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5592 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5593 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5594 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5595 P/N
45N8295, P0C38732.
</p
>
5597 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5598 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5599 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5600 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5601 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5602 P/N
45N8295, P0C38732.
</p
>
5604 <p
>The only difference is in the first number (serial number?), ISN,
5605 SA, date and WNPP values. Mentioning all the details here in case
5606 someone is able to use the information to find a way to identify the
5607 failing disk among working ones (if any such working disk actually
5613 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5614 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5616 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5617 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5618 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5619 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5620 member assosiation NUUG
</a
> and
5621 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5622 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5623 Bitraf
</a
>.
</p
>
5625 <p
>It starts
10:
00 and continue until late evening. Everyone is
5626 welcome, and there is no fee to participate. There is on the other
5627 hand limited space, and only room for
30 people. Please put your name
5628 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5629 wiki page
</a
> if you plan to join us.
</p
>
5634 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5635 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5636 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5637 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5638 <description><p
>Half a year ago, I reported that I had to find a
5639 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5640 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5641 time to spend on it, and it took a while to find a model I believe
5642 will do the job, but two days ago the replacement finally arrived. I
5644 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5645 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5646 a roaming workstation, and it seemed to work flawlessly. But my
5647 second installation with encrypted disk was not as successful. More
5648 on that below.
</p
>
5650 <p
>I had a hard time trying to track down a good laptop, as my most
5651 important requirements (robust and with a good keyboard) are never
5652 listed in the feature list. But I did get good help from the search
5653 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5654 allowed me to limit the list of interesting laptops based on my other
5655 requirements. A bit surprising that SSD disk are not disks according
5656 to that search interface, so I had to drop specifying the number of
5657 disks from my search parameters. I also asked around among friends to
5658 get their impression on keyboards and robustness.
</p
>
5660 <p
>So the new laptop arrived, and it is quite a lot wider than the
5661 X41. I am not quite convinced about the keyboard, as it is
5662 significantly wider than my old keyboard, and I have to stretch my
5663 hand a lot more to reach the edges. But the key response is fairly
5664 good and the individual key shape is fairly easy to handle, so I hope
5665 I will get used to it. My old X40 was starting to fail, and I really
5666 needed a new laptop now. :)
</p
>
5668 <p
>Turning off the touch pad was simple. All it took was a quick
5669 visit to the BIOS during boot it disable it.
</p
>
5671 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5672 lock up during load. And this happen when installing Debian Wheezy
5673 with encrypted disk, while the disk is being filled with random data.
5674 I also tested to install Ubuntu Raring, and it happen there too if I
5675 reenable the code to fill the disk with random data (it is disabled by
5676 default in Ubuntu). And the bug with is already known. It was
5677 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5678 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5679 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5680 kernel developers as
5681 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5682 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5683 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5684 Lenovo forums, both for
5685 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5686 2012-
11-
10</a
> and for
5687 <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
5688 03-
20-
2013</a
>. The problem do not only affect installation. The
5689 reports state that the disk lock up during use if many writes are done
5690 on the disk, so it is much no use to work around the installation
5691 problem and end up with a computer that can lock up at any moment.
5693 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5694 available
</a
> that will lock up the hard drive after running a few
5695 minutes by writing to a file.
</p
>
5697 <p
>I
've contacted my supplier and asked how to handle this, and after
5698 contacting PCHELP Norway (request
01D1FDP) which handle support
5699 requests for Lenovo, his first suggestion was to upgrade the disk
5700 firmware. Unfortunately there is no newer firmware available from
5701 Lenovo, as my disk already have the most recent one (version LF1i). I
5702 hope to hear more from him today and hope the problem can be
5708 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5709 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5710 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5711 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5712 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5713 trusty old Thinkpad X41. Unfortunately I did not have much time to
5714 spend on it, but today the replacement finally arrived. I ended up
5715 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5716 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5717 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5718 this, it is installing what I hope will be a more final installation,
5719 with a encrypted hard drive to ensure any dope head stealing it end up
5720 with an expencive door stop.
</p
>
5722 <p
>I had a hard time trying to track down a good laptop, as my most
5723 important requirements (robust and with a good keyboard) are never
5724 listed in the feature list. But I did get good help from the search
5725 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5726 allowed me to limit the list of interesting laptops based on my other
5727 requirements. A bit surprising that SSD disk are not disks, so I had
5728 to drop number of disks from my search parameters.
</p
>
5730 <p
>I am not quite convinced about the keyboard, as it is significantly
5731 wider than my old keyboard, and I have to stretch my hand a lot more
5732 to reach the edges. But the key response is fairly good and the
5733 individual key shape is fairly easy to handle, so I hope I will get
5734 used to it. My old X40 was starting to fail, and I really needed a
5735 new laptop now. :)
</p
>
5737 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5742 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5743 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5744 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5745 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5746 <description><p
>It annoys me when the computer fail to do automatically what it is
5747 perfectly capable of, and I have to do it manually to get things
5748 working. One such task is to find out what firmware packages are
5749 needed to get the hardware on my computer working. Most often this
5750 affect the wifi card, but some times it even affect the RAID
5751 controller or the ethernet card. Today I pushed version
0.4 of the
5752 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5753 including a new script isenkram-autoinstall-firmware handling the
5754 process of asking all the loaded kernel modules what firmware files
5755 they want, find debian packages providing these files and install the
5756 debian packages. Here is a test run on my laptop:
</p
>
5758 <p
><pre
>
5759 # isenkram-autoinstall-firmware
5760 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5761 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5762 info: locating packages with the requested firmware files
5763 info: Updating APT sources after adding non-free APT source
5764 info: trying to install firmware-ipw2x00
5767 Preconfiguring packages ...
5768 Selecting previously deselected package firmware-ipw2x00.
5769 (Reading database ...
259727 files and directories currently installed.)
5770 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5771 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5773 </pre
></p
>
5775 <p
>When all the requested firmware is present, a simple message is
5776 printed instead:
</p
>
5778 <p
><pre
>
5779 # isenkram-autoinstall-firmware
5780 info: did not find any firmware files requested by loaded kernel modules. exiting
5782 </pre
></p
>
5784 <p
>It could use some polish, but it is already working well and saving
5785 me some time when setting up new machines. :)
</p
>
5787 <p
>So, how does it work? It look at the set of currently loaded
5788 kernel modules, and look up each one of them using modinfo, to find
5789 the firmware files listed in the module meta-information. Next, it
5790 download the Contents file from a nearby APT mirror, and search for
5791 the firmware files in this file to locate the package with the
5792 requested firmware file. If the package is in the non-free section, a
5793 non-free APT source is added and the package is installed using
5794 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5797 <p
>I hope someone find time to implement a more polished version of
5798 this script as part of the hw-detect debian-installer module, to
5799 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5800 #
655507</a
>. There really is no need to insert USB sticks with
5801 firmware during a PXE install when the packages already are available
5802 from the nearby Debian mirror.
</p
>
5807 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5808 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5809 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5810 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5811 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5812 the screen just turn black when Linux boot, either during installation
5813 or on first boot from the hard disk. I
've seen it once in a while the
5814 last few years, but only recently understood the cause. I
've seen it
5815 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5816 The reason seem to be in the wiring of some laptops. The system to
5817 control the screen background light is inverted, so when Linux try to
5818 turn the brightness fully on, it end up turning it off instead. I do
5819 not know which Linux drivers are affected, but this post is about the
5820 i915 driver used by the
5821 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5822 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5824 <p
>The problem can be worked around two ways. Either by adding
5825 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5826 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5827 option when it load the i915 kernel module. On Debian and Ubuntu, it
5828 can be done by running these commands as root:
</p
>
5831 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5832 update-initramfs -u -k all
5835 <p
>Since March
2012 there is
5836 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5837 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5838 hardware have this problem, and get the driver to invert the
5839 brightness setting automatically. To use it, one need to add a row in
5840 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5841 intel_quirks array
</a
> in the driver source
5842 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5843 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5844 number (vendor number
8086 is assumed) and subdevice vendor and device
5847 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5848 -vvnn
</tt
> for the video card in question:
</p
>
5850 <p
><pre
>
5851 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5852 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5853 (rev
09) (prog-if
00 [VGA controller])
5854 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5855 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5856 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5857 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5858 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5860 Interrupt: pin A routed to IRQ
42
5861 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5862 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5863 Region
4: I/O ports at
4000 [size=
64]
5864 Expansion ROM at
<unassigned
> [disabled]
5865 Capabilities:
<access denied
>
5866 Kernel driver in use: i915
5867 </pre
></p
>
5869 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5871 <p
><pre
>
5872 struct intel_quirk intel_quirks[] = {
5874 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5875 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5878 </pre
></p
>
5880 <p
>According to the kernel module instructions (as seen using
5881 <tt
>modinfo i915
</tt
>), information about hardware needing the
5882 invert_brightness flag should be sent to the
5883 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5884 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5885 developers. But my email about the laptop sent
2013-
06-
03 have not
5887 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5888 web archive for the mailing list
</a
>, so I suspect they do not accept
5889 emails from non-subscribers. Because of this, I sent my patch also to
5890 the Debian bug tracking system instead as
5891 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5892 sure the patch is not lost.
</p
>
5894 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5895 with this problem working properly with Linux. If you use Gnome, your
5896 worries should be over at this point. But if you use KDE, there is
5897 something in KDE ignoring the invert_brightness setting and turning on
5898 the screen during login. I
've reported it to Debian as
5899 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5900 have no idea yet how to figure out exactly what subsystem is doing
5901 this. Perhaps you can help? Perhaps you know what the Gnome
5902 developers did to handle this, and this can give a clue to the KDE
5903 developers? Or you know where in KDE the screen brightness is changed
5904 during login? If so, please update the BTS report (or get in touch if
5905 you do not know how to update BTS).
</p
>
5907 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5908 acpi_backlight=vendor, to disable ACPI backlight support completely,
5909 as the ACPI information on the machine is trash and it is better to
5910 leave it to the intel video driver to control the screen
5911 backlight.
</p
>
5916 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5917 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5918 <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>
5919 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5920 <description><p
>Two days ago, I asked
5921 <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
5922 I could install Linux on a Packard Bell EasyNote LV computer
5923 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5924 with the obstacles put in the way of Linux users on a laptop with UEFI
5925 and Windows
8.
</p
>
5927 <p
>I never found out if the cause of my problems were the use of UEFI
5928 secure booting or fast boot. I suspect fast boot was the problem,
5929 causing the firmware to boot directly from HD without considering any
5930 key presses and alternative devices, but do not know UEFI settings
5931 enough to tell.
</p
>
5933 <p
>There is no way to install Linux on the machine in question without
5934 opening the box and disconnecting the hard drive! This is as far as I
5935 can tell, the only way to get access to the firmware setup menu
5936 without accepting the Windows
8 license agreement. I am told (and
5937 found description on how to) that it is possible to configure the
5938 firmware setup once booted into Windows
8. But as I believe the terms
5939 of that agreement are completely unacceptable, accepting the license
5940 was never an alternative. I do not enter agreements I do not intend
5941 to follow.
</p
>
5943 <p
>I feared I had to return the laptops and ask for a refund, and
5944 waste many hours on this, but luckily there was a way to get it to
5945 work. But I would not recommend it to anyone planning to run Linux on
5946 it, and I have become sceptical to Windows
8 certified laptops. Is
5947 this the way Linux will be forced out of the market place, by making
5948 it close to impossible for
"normal
" users to install Linux without
5949 accepting the Microsoft Windows license terms? Or at least not
5950 without risking to loose the warranty?
</p
>
5952 <p
>I
've updated the
5953 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5954 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5955 do not have to struggle as much as I did to get Linux into the
5958 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5959 Michael Tokarev and others for feedback and ideas.
</p
>
5964 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5965 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5966 <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>
5967 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5968 <description><p
>I
've run into quite a problem the last few days. I bought three
5969 new laptops for my parents and a few others. I bought Packard Bell
5970 Easynote LV to run Kubuntu on and use as their home computer. But I
5971 am completely unable to figure out how to install Linux on it. The
5972 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5973 instead of a BIOS to boot.
</p
>
5975 <p
>The problem is that I am unable to get it to PXE boot, and unable
5976 to get it to boot the Linux installer from my USB stick. I have yet
5977 to try the DVD install, and still hope it will work. when I turn on
5978 the computer, there is no information on what buttons to press to get
5979 the normal boot menu. I expect to get some boot menu to select PXE or
5980 USB stick booting. When booting, it first ask for the language to
5981 use, then for some regional settings, and finally if I will accept the
5982 Windows
8 terms of use. As these terms are completely unacceptable to
5983 me, I have no other choice but to turn off the computer and try again
5984 to get it to boot the Linux installer.
</p
>
5986 <p
>I have gathered my findings so far on a Linlap page about the
5987 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5988 EasyNote LV
</a
> model. If you have any idea how to get Linux
5989 installed on this machine, please get in touch or update that wiki
5990 page. If I can
't find a way to install Linux, I will have to return
5991 the laptop to the seller and find another machine for my parents.
</p
>
5993 <p
>I wonder, is this the way Linux will be forced out of the market
5994 using UEFI and
"secure boot
" by making it impossible to install Linux
5995 on new Laptops?
</p
>
6000 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6001 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6002 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6003 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6004 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6005 an operating system based on Debian intended for use in schools. It
6006 contain a turn-key solution for the computer network provided to
6007 pupils in the primary schools. It provide both the central server,
6008 network boot servers and desktop environments with heaps of
6009 educational software. The project was founded almost
12 years ago,
6010 2001-
07-
02. If you want to support the project, which is in need for
6011 cash to fund developer gatherings and other project related activity,
6012 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6013 donate some money
</a
>.
6015 <p
>A topic that come up again and again on the Debian Edu mailing
6016 lists and elsewhere, is the question on how to transform a Debian or
6017 Ubuntu installation into a Debian Edu installation. It isn
't very
6018 hard, and last week I wrote a script to replicate the steps done by
6019 the Debian Edu installer.
</p
>
6021 <p
>The script,
6022 <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/
>
6023 in the debian-edu-config package, will go through these six steps and
6024 transform an existing Debian Wheezy or Ubuntu (untested) installation
6025 into a Debian Edu Workstation:
</p
>
6029 <li
>Add skolelinux related APT sources.
</li
>
6030 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6031 <li
>Install debian-edu-install to load preseeding values and pull in
6032 our configuration.
</li
>
6033 <li
>Preseed debconf database with profile setup in
6034 /etc/debian-edu/config, and run tasksel to install packages
6035 according to the profile specified in the config above,
6036 overriding some of the Debian automation machinery.
</li
>
6037 <li
>Run debian-edu-cfengine-D installation to configure everything
6038 that could not be done using preseeding.
</li
>
6039 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6043 <p
>There are some steps in the Debian Edu installation that can not be
6044 replicated like this. Disk partitioning and LVM setup, for example.
6045 So this script just assume there is enough disk space to install all
6046 the needed packages.
</p
>
6048 <p
>The script was created to help a Debian Edu student working on
6049 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6050 Debian Edu client, and using it he can take the existing
6051 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6052 transform it into a fully functioning Debian Edu Workstation (or
6053 Roaming Workstation, or whatever :).
</p
>
6055 <p
>The default setting in the script is to create a KDE Workstation.
6056 If a LXDE based Roaming workstation is wanted instead, modify the
6057 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6059 <p
><pre
>
6060 PROFILE=
"Roaming-Workstation
"
6061 DESKTOP=
"lxde
"
6062 </pre
></p
>
6064 <p
>The script could even become useful to set up Debian Edu servers in
6065 the cloud, by starting with a virtual Debian installation at some
6066 virtual hosting service and setting up all the services on first
6072 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6073 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6074 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6075 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6076 <description><P
>In January,
6077 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6078 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6079 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6080 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6081 marvellous construction system from Denmark. We also created
6082 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6083 a place to take notes and write down our plans and hopes. And several
6084 people showed up to help. I was very happy to see the effect of my
6085 call. Since the small start, we have a debtags tag
6086 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6087 tag for LEGO related packages, and now count
10 packages related to
6088 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6090 <p
><table
>
6091 <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
>
6092 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6093 <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
>
6094 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6095 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6096 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6097 <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
>
6098 <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
>
6099 <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
>
6100 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6101 </table
></p
>
6103 <p
>Some of these are available in Wheezy, and all but one are
6104 currently available in Jessie/testing. leocad is so far only
6105 available in experimental.
</p
>
6107 <p
>If you care about LEGO in Debian, please join us on IRC and help
6108 adding the rest of the great free software tools available on Linux
6109 for LEGO designers.
</p
>
6114 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6115 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6116 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6117 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6118 <description><p
>When I woke up this morning, I was very happy to see that the
6119 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6120 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6121 Debian release, and I expect to move my machines at home over to it fairly
6124 <p
>The new debian release contain heaps of new stuff, and one program
6125 in particular make me very happy to see included. The
6126 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6127 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6128 included for the first time. Alongside similar programs like
6129 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6130 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6131 it allow for visual programming where syntax errors can not happen,
6132 and a friendly programming environment for learning to control the
6133 computer. Scratch will also be included in the next release of Debian
6136 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6137 Edu/Skolelinux release too. The
6138 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6139 alpha release
</a
> went out last week, and the next should soon
6145 <title>Isenkram
0.2 finally in the Debian archive
</title>
6146 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6148 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6149 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6150 package
</a
> finally made it into the archive, after lingering in NEW
6151 for many months. I uploaded it to the Debian experimental suite
6152 2013-
01-
27, and today it was accepted into the archive.
</p
>
6154 <p
>Isenkram is a system for suggesting to users what packages to
6155 install to work with a pluggable hardware device. The suggestion pop
6156 up when the device is plugged in. For example if a Lego Mindstorm NXT
6157 is inserted, it will suggest to install the program needed to program
6158 the NXT controller. Give it a go, and report bugs and suggestions to
6164 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6165 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6167 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6168 <description><p
>My
6169 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6170 bitcoin related blog post
</a
> mentioned that the new
6171 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6172 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6173 2013-
01-
19, and have been available in unstable since then. It was
6174 automatically copied to Ubuntu, and is available in their Raring
6175 version too.
</p
>
6177 <p
>But there is a strange problem with the build that block this new
6178 version from being available on the i386 and kfreebsd-i386
6179 architectures. For some strange reason, the autobuilders in Debian
6180 for these architectures fail to run the test suite on these
6181 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6182 We are so far unable to reproduce it when building it manually, and
6183 no-one have been able to propose a fix. If you got an idea what is
6184 failing, please let us know via the BTS.
</p
>
6186 <p
>One feature that is annoying me with of the bitcoin client, because
6187 I often run low on disk space, is the fact that the client will exit
6188 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6189 #
696715</a
>). So make sure you have enough disk space when you run
6192 <p
>As usual, if you use bitcoin and want to show your support of my
6193 activities, please send Bitcoin donations to my address
6194 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6199 <title>Welcome to the world, Isenkram!
</title>
6200 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6201 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6202 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6203 <description><p
>Yesterday, I
6204 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6205 for testers
</a
> for my prototype for making Debian better at handling
6206 pluggable hardware devices, which I
6207 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6208 out to create
</a
> earlier this month. Several valuable testers showed
6209 up, and caused me to really want to to open up the development to more
6210 people. But before I did this, I want to come up with a sensible name
6211 for this project. Today I finally decided on a new name, and I have
6212 renamed the project from hw-support-handler to this new name. In the
6213 process, I moved the source to git and made it available as a
6214 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6215 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6216 To fetch and build the latest version of the source, use
</p
>
6219 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6220 cd isenkram
&& git-buildpackage -us -uc
6223 <p
>I have not yet adjusted all files to use the new name yet. If you
6224 want to hack on the source or improve the package, please go ahead.
6225 But please talk to me first on IRC or via email before you do major
6226 changes, to make sure we do not step on each others toes. :)
</p
>
6228 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6229 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6230 stuff, in other words. I
've been told it is the Norwegian variant of
6231 the German word eisenkram, for those that are familiar with that
6234 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6235 instructions, to avoid confusing people with an error from the signing
6238 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6239 clone argument to avoid the need for authentication.
</p
>
6244 <title>First prototype ready making hardware easier to use in Debian
</title>
6245 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6246 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6247 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6248 <description><p
>Early this month I set out to try to
6249 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6250 the Debian support for pluggable hardware devices
</a
>. Now my
6251 prototype is working, and it is ready for a larger audience. To test
6253 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6254 from the Debian Edu subversion repository
</a
>, build and install the
6255 package. You might have to log out and in again activate the
6256 autostart script.
</p
>
6258 <p
>The design is simple:
</p
>
6262 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6263 hw-support-handlerd to start when the user log in.
</li
>
6265 <li
>This program listen for kernel events about new hardware (directly
6266 from the kernel like udev does), not using HAL dbus events as I
6267 initially did.
</li
>
6269 <li
>When new hardware is inserted, look up the hardware modalias in
6270 the APT database, a database
6271 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6272 via HTTP
</a
> and a database available as part of the package.
</li
>
6274 <li
>If a package is mapped to the hardware in question, the package
6275 isn
't installed yet and this is the first time the hardware was
6276 plugged in, show a desktop notification suggesting to install the
6277 package or packages.
</li
>
6279 <li
>If the user click on the
'install package now
' button, ask
6280 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6282 <li
>aptdaemon ask for root password or sudo password, and install the
6283 package while showing progress information in a window.
</li
>
6287 <p
>I still need to come up with a better name for the system. Here
6288 are some screen shots showing the prototype in action. First the
6289 notification, then the password request, and finally the request to
6290 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6292 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6293 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6294 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6295 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6296 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6298 <p
>The prototype still need to be improved with longer timeouts, but
6299 is already useful. The database of hardware to package mappings also
6300 need more work. It is currently compatible with the Ubuntu way of
6301 storing such information in the package control file, but could be
6302 changed to use other formats instead or in addition to the current
6303 method. I
've dropped the use of discover for this mapping, as the
6304 modalias approach is more flexible and easier to use on Linux as long
6305 as the Linux kernel expose its modalias strings directly.
</p
>
6307 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6308 here is the command required to check out and build the source: Use
6309 '<tt
>svn checkout
6310 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6311 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6312 devscripts package.
</p
>
6314 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6315 renamed to Isenkram and the source moved from the Debian Edu
6316 subversion repository to a Debian collab-maint git repository. See
6317 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6318 instructions
</a
> for details.
</p
>
6323 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6324 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6325 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6326 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6327 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6328 suddenly in bed. With a quiet whimper, it went completely quiet and
6329 black. The power button was no longer able to turn it on. It was a
6330 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6331 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6332 Compaq I had before that. Now I need to find a replacement. To keep
6333 going during Christmas, I moved the one year old SSD disk to my old
6334 X40 where it fitted (only one I had left that could use it), but it is
6335 not a durable solution.
6337 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6338 got a new one more than
10 years ago. It still holds true.:)
</p
>
6342 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6343 than A4).
</li
>
6344 <li
>Robust, it will be in my backpack every day.
</li
>
6345 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6346 <li
>Long battery life time. Preferable a week.
</li
>
6347 <li
>Internal WIFI network card.
</li
>
6348 <li
>Internal Twisted Pair network card.
</li
>
6349 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6350 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6351 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6353 <li
>Hardware supported by Debian Stable, ie the default kernel and
6354 X.org packages.
</li
>
6355 <li
>Quiet, preferably fan free (or at least not using the fan most of
6360 <p
>You will notice that there are no RAM and CPU requirements in the
6361 list. The reason is simply that the specifications on laptops the
6362 last
10-
15 years have been sufficient for my needs, and I have to look
6363 at other features to choose my laptop. But are there still made as
6364 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6365 robust, and Thinkpads seem to be heading in the wrong direction since
6366 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6367 still be useful.
</p
>
6369 <p
>Perhaps I should rethink my needs, and look for a pad with an
6370 external keyboard? I
'll have to check the
6371 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6372 well-supported laptops, or perhaps just buy one preinstalled from one
6373 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6374 Pre-loaded site
</a
>.
</p
>
6379 <title>How to find a browser plugin supporting a given MIME type
</title>
6380 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6381 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6382 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6383 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6384 install to get support for a given MIME type. Thanks to
6385 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6386 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6387 Unfortunately, not very many packages provide the needed meta
6388 information, Anyway, here is a small script to look up all browser
6389 plugin packages announcing ther MIME support using this specification:
</p
>
6395 def pkgs_handling_mimetype(mimetype):
6400 version = pkg.candidate
6402 version = pkg.installed
6405 record = version.record
6406 if not record.has_key(
'Npp-MimeType
'):
6408 mime_types = record[
'Npp-MimeType
'].split(
',
')
6409 for t in mime_types:
6410 t = t.rstrip().strip()
6412 thepkgs.append(pkg.name)
6414 mimetype =
"audio/ogg
"
6415 if
1 < len(sys.argv):
6416 mimetype = sys.argv[
1]
6417 print
"Browser plugin packages supporting %s:
" % mimetype
6418 for pkg in pkgs_handling_mimetype(mimetype):
6419 print
" %s
" %pkg
6422 <p
>It can be used like this to look up a given MIME type:
</p
>
6425 % ./apt-find-browserplug-for-mimetype
6426 Browser plugin packages supporting audio/ogg:
6428 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6429 Browser plugin packages supporting application/x-shockwave-flash:
6430 browser-plugin-gnash
6434 <p
>In Ubuntu this mechanism is combined with support in the browser
6435 itself to query for plugins and propose to install the needed
6436 packages. It would be great if Debian supported such feature too. Is
6437 anyone working on adding it?
</p
>
6439 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6440 request for icweasel support for this feature is
6441 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6442 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6443 of manpower and wish for a different design is the reason thus feature
6444 is not yet in iceweasel from Debian.
</p
>
6449 <title>What is the most supported MIME type in Debian?
</title>
6450 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6451 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6452 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6453 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6454 proposal to add AppStream information to the Debian archive
</a
>, is a
6455 proposal to make it possible for a Desktop application to propose to
6456 the user some package to install to gain support for a given MIME
6457 type, font, library etc. that is currently missing. With such
6458 mechanism in place, it would be possible for the desktop to
6459 automatically propose and install leocad if some LDraw file is
6460 downloaded by the browser.
</p
>
6462 <p
>To get some idea about the current content of the archive, I decided
6463 to write a simple program to extract all .desktop files from the
6464 Debian archive and look up the claimed MIME support there. The result
6466 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6467 site
</a
>. Using the collected information, it become possible to
6468 answer the question in the title. Here are the
20 most supported MIME
6469 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6470 The complete list is available from the link above.
</p
>
6472 <p
><strong
>Debian Stable:
</strong
></p
>
6476 ----- -----------------------
6492 18 application/x-ogg
6499 <p
><strong
>Debian Testing:
</strong
></p
>
6503 ----- -----------------------
6519 18 application/x-ogg
6526 <p
><strong
>Debian Unstable:
</strong
></p
>
6530 ----- -----------------------
6547 18 application/x-ogg
6553 <p
>I am told that PackageKit can provide an API to access the kind of
6554 information mentioned in DEP-
11. I have not yet had time to look at
6555 it, but hope the PackageKit people in Debian are on top of these
6558 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6559 discovering a typo in my script.
</p
>
6564 <title>Using modalias info to find packages handling my hardware
</title>
6565 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6566 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6567 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6568 <description><p
>Yesterday, I wrote about the
6569 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6570 values provided by the Linux kernel
</a
> following my hope for
6571 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6572 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6573 modalias values attached to package names can be used to map packages
6574 to hardware. This allow the system to look up and suggest relevant
6575 packages when I plug in some new hardware into my machine, and replace
6576 discover and discover-data as the database used to map hardware to
6579 <p
>I create a modaliases file with entries like the following,
6580 containing package name, kernel module name (if relevant, otherwise
6581 the package name) and globs matching the relevant hardware
6584 <p
><blockquote
>
6585 Package: package-name
6586 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6587 </blockquote
></p
>
6589 <p
>It is fairly trivial to write code to find the relevant packages
6590 for a given modalias value using this file.
</p
>
6592 <p
>An entry like this would suggest the video and picture application
6593 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6595 <p
><blockquote
>
6597 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6598 </blockquote
></p
>
6600 <p
>An entry like this would suggest the pcmciautils package when a
6601 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6603 <p
><blockquote
>
6604 Package: pcmciautils
6605 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6606 </blockquote
></p
>
6608 <p
>An entry like this would suggest the package colorhug-client when
6609 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6611 <p
><blockquote
>
6612 Package: colorhug-client
6613 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6614 </blockquote
></p
>
6616 <p
>I believe the format is compatible with the format of the Packages
6617 file in the Debian archive. Ubuntu already uses their Packages file
6618 to store their mappings from packages to hardware.
</p
>
6620 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6621 announce the hardware it support in a way my prototype understand.
6622 This allow those publishing packages in an APT source outside the
6623 Debian archive as well as those backporting packages to make sure the
6624 hardware mapping are included in the package meta information. I
've
6625 tested such header in the pymissile package, and its modalias mapping
6626 is working as it should with my prototype. It even made it to Ubuntu
6629 <p
>To test if it was possible to look up supported hardware using only
6630 the shell tools available in the Debian installer, I wrote a shell
6631 implementation of the lookup code. The idea is to create files for
6632 each modalias and let the shell do the matching. Please check out and
6634 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6635 shell script. It run without any extra dependencies and fetch the
6636 hardware mappings from the Debian archive and the subversion
6637 repository where I currently work on my prototype.
</p
>
6639 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6640 install yubikey-personalization:
</p
>
6642 <p
><blockquote
>
6643 % ./hw-support-lookup
6644 <br
>yubikey-personalization
6646 </blockquote
></p
>
6648 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6649 propose to install the pcmciautils package:
</p
>
6651 <p
><blockquote
>
6652 % ./hw-support-lookup
6653 <br
>pcmciautils
6655 </blockquote
></p
>
6657 <p
>If you know of any hardware-package mapping that should be added to
6658 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6659 database
</a
>, please tell me about it.
</p
>
6661 <p
>It could be possible to generate several of the mappings between
6662 packages and hardware. One source would be to look at packages with
6663 kernel modules, ie packages with *.ko files in /lib/modules/, and
6664 extract their modalias information. Another would be to look at
6665 packages with udev rules, ie packages with files in
6666 /lib/udev/rules.d/, and extract their vendor/model information to
6667 generate a modalias matching rule. I have not tested any of these to
6668 see if it work.
</p
>
6670 <p
>If you want to help implementing a system to let us propose what
6671 packages to install when new hardware is plugged into a Debian
6672 machine, please send me an email or talk to me on
6673 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6678 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6679 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6680 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6681 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6682 <description><p
>While looking into how to look up Debian packages based on hardware
6683 information, to find the packages that support a given piece of
6684 hardware, I refreshed my memory regarding modalias values, and decided
6685 to document the details. Here are my findings so far, also available
6687 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6688 Debian Edu subversion repository
</a
>:
6690 <p
><strong
>Modalias decoded
</strong
></p
>
6692 <p
>This document try to explain what the different types of modalias
6693 values stands for. It is in part based on information from
6694 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6695 &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;,
6696 &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
6697 &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;.
6699 <p
>The modalias entries for a given Linux machine can be found using
6700 this shell script:
</p
>
6703 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6706 <p
>The supported modalias globs for a given kernel module can be found
6707 using modinfo:
</p
>
6710 % /sbin/modinfo psmouse | grep alias:
6711 alias: serio:ty05pr*id*ex*
6712 alias: serio:ty01pr*id*ex*
6716 <p
><strong
>PCI subtype
</strong
></p
>
6718 <p
>A typical PCI entry can look like this. This is an Intel Host
6719 Bridge memory controller:
</p
>
6721 <p
><blockquote
>
6722 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6723 </blockquote
></p
>
6725 <p
>This represent these values:
</p
>
6730 sv
00001028 (subvendor)
6731 sd
000001AD (subdevice)
6733 sc
00 (bus subclass)
6737 <p
>The vendor/device values are the same values outputted from
'lspci
6738 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6739 0600. The
0600 class is a host bridge. Other useful bus values are
6740 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6742 <p
>Not sure how to figure out the interface value, nor what it
6745 <p
><strong
>USB subtype
</strong
></p
>
6747 <p
>Some typical USB entries can look like this. This is an internal
6748 USB hub in a laptop:
</p
>
6750 <p
><blockquote
>
6751 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6752 </blockquote
></p
>
6754 <p
>Here is the values included in this alias:
</p
>
6757 v
1D6B (device vendor)
6758 p
0001 (device product)
6760 dc
09 (device class)
6761 dsc
00 (device subclass)
6762 dp
00 (device protocol)
6763 ic
09 (interface class)
6764 isc
00 (interface subclass)
6765 ip
00 (interface protocol)
6768 <p
>The
0900 device class/subclass means hub. Some times the relevant
6769 class is in the interface class section. For a simple USB web camera,
6770 these alias entries show up:
</p
>
6772 <p
><blockquote
>
6773 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6774 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6775 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6776 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6777 </blockquote
></p
>
6779 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6780 camera),
0101 is audio control device and
0102 is audio streaming (aka
6781 microphone). Thus this is a camera with microphone included.
</p
>
6783 <p
><strong
>ACPI subtype
</strong
></p
>
6785 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6786 receiver in a Thinkpad X40:
</p
>
6788 <p
><blockquote
>
6789 acpi:IBM0071:PNP0511:
6790 </blockquote
></p
>
6792 <p
>The values between the colons are IDs.
</p
>
6794 <p
><strong
>DMI subtype
</strong
></p
>
6796 <p
>The DMI table contain lots of information about the computer case
6797 and model. This is an entry for a IBM Thinkpad X40, fetched from
6798 /sys/devices/virtual/dmi/id/modalias:
</p
>
6800 <p
><blockquote
>
6801 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6802 </blockquote
></p
>
6804 <p
>The values present are
</p
>
6807 bvn IBM (BIOS vendor)
6808 bvr
1UETB
6WW(
1.66) (BIOS version)
6809 bd
06/
15/
2005 (BIOS date)
6810 svn IBM (system vendor)
6811 pn
2371H4G (product name)
6812 pvr ThinkPadX40 (product version)
6813 rvn IBM (board vendor)
6814 rn
2371H4G (board name)
6815 rvr NotAvailable (board version)
6816 cvn IBM (chassis vendor)
6817 ct
10 (chassis type)
6818 cvr NotAvailable (chassis version)
6821 <p
>The chassis type
10 is Notebook. Other interesting values can be
6822 found in the dmidecode source:
</p
>
6826 4 Low Profile Desktop
6839 17 Main Server Chassis
6840 18 Expansion Chassis
6842 20 Bus Expansion Chassis
6843 21 Peripheral Chassis
6845 23 Rack Mount Chassis
6854 <p
>The chassis type values are not always accurately set in the DMI
6855 table. For example my home server is a tower, but the DMI modalias
6856 claim it is a desktop.
</p
>
6858 <p
><strong
>SerIO subtype
</strong
></p
>
6860 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6861 test machine:
</p
>
6863 <p
><blockquote
>
6864 serio:ty01pr00id00ex00
6865 </blockquote
></p
>
6867 <p
>The values present are
</p
>
6876 <p
>This type is supported by the psmouse driver. I am not sure what
6877 the valid values are.
</p
>
6879 <p
><strong
>Other subtypes
</strong
></p
>
6881 <p
>There are heaps of other modalias subtypes according to
6882 file2alias.c. There is the rest of the list from that source: amba,
6883 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6884 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6885 vmbus, x86cpu and zorro. I did not spend time documenting all of
6886 these, as they do not seem relevant for my intended use with mapping
6887 hardware to packages when new stuff is inserted during run time.
</p
>
6889 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6891 <p
>To check which kernel modules provide support for a given modalias,
6892 one can use the following shell script:
</p
>
6895 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6896 echo
"$id
" ; \
6897 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6901 <p
>The output can look like this (only the first few entries as the
6902 list is very long on my test machine):
</p
>
6906 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6908 FATAL: Module acpi:device: not found.
6910 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6911 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6912 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6913 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6914 acpi:IBM0071:PNP0511:
6915 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6916 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6917 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6921 <p
>If you want to help implementing a system to let us propose what
6922 packages to install when new hardware is plugged into a Debian
6923 machine, please send me an email or talk to me on
6924 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6926 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6927 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6928 in /sys/ with space in them.
</p
>
6933 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6934 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6936 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6937 <description><p
>As part of my investigation on how to improve the support in Debian
6938 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6939 Launcher and updated the Debian package
6940 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6941 sure udev will fix the device permissions when it is plugged in. I
6942 also added a
"Modaliases
" header to test it in the Debian archive and
6943 hopefully make the package be proposed by jockey in Ubuntu when a user
6944 plug in his rocket launcher. In the process I moved the source to a
6945 git repository under collab-maint, to make it easier for any DD to
6946 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6947 is not very active, but the software still work for me even after five
6948 years of relative silence. The new git repository is not listed in
6949 the uploaded package yet, because I want to test the other changes a
6950 bit more before I upload the new version. If you want to check out
6951 the new version with a .desktop file included, visit the
6952 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6953 view
</a
> or use
"<tt
>git clone
6954 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6959 <title>Lets make hardware dongles easier to use in Debian
</title>
6960 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6961 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6962 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6963 <description><p
>One thing that annoys me with Debian and Linux distributions in
6964 general, is that there is a great package management system with the
6965 ability to automatically install software packages by downloading them
6966 from the distribution mirrors, but no way to get it to automatically
6967 install the packages I need to use the hardware I plug into my
6968 machine. Even if the package to use it is easily available from the
6969 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6970 suggest to automatically install the python-nxt, nbc and t2n packages
6971 I need to talk to it. When I plug in a Yubikey, it could propose the
6972 yubikey-personalization package. The information required to do this
6973 is available, but no-one have pulled all the pieces together.
</p
>
6975 <p
>Some years ago, I proposed to
6976 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6977 the discover subsystem to implement this
</a
>. The idea is fairly
6982 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6983 starting when a user log in.
</li
>
6985 <li
>Set this program up to listen for kernel events emitted when new
6986 hardware is inserted into the computer.
</li
>
6988 <li
>When new hardware is inserted, look up the hardware ID in a
6989 database mapping to packages, and take note of any non-installed
6990 packages.
</li
>
6992 <li
>Show a message to the user proposing to install the discovered
6993 package, and make it easy to install it.
</li
>
6997 <p
>I am not sure what the best way to implement this is, but my
6998 initial idea was to use dbus events to discover new hardware, the
6999 discover database to find packages and
7000 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7003 <p
>Yesterday, I found time to try to implement this idea, and the
7004 draft package is now checked into
7005 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7006 Debian Edu subversion repository
</a
>. In the process, I updated the
7007 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7008 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7009 the relevant packages in Debian, and uploaded a new version
7010 2.2013.01.09 to unstable. I also discovered that the current
7011 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7012 package in Debian no longer discovered any USB devices, because
7013 /proc/bus/usb/devices is no longer present. I ported it to use
7014 libusb as a fall back option to get it working. The fixed package
7015 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7016 because of the freeze).
</p
>
7018 <p
>With this prototype in place, I can insert my Yubikey, and get this
7019 desktop notification to show up (only once, the first time it is
7020 inserted):
</p
>
7022 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7024 <p
>For this prototype to be really useful, some way to automatically
7025 install the proposed packages by pressing the
"Please install
7026 program(s)
" button should to be implemented.
</p
>
7028 <p
>If this idea seem useful to you, and you want to help make it
7029 happen, please help me update the discover-data database with mappings
7030 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7031 list the package you would like to have installed when a given
7032 hardware device is inserted into your computer, and report bugs using
7033 reportbug if it isn
't. Or, if you know of a better way to provide
7034 such mapping, please let me know.
</p
>
7036 <p
>This prototype need more work, and there are several questions that
7037 should be considered before it is ready for production use. Is dbus
7038 the correct way to detect new hardware? At the moment I look for HAL
7039 dbus events on the system bus, because that is the events I could see
7040 on my Debian Squeeze KDE desktop. Are there better events to use?
7041 How should the user be notified? Is the desktop notification
7042 mechanism the best option, or should the background daemon raise a
7043 popup instead? How should packages be installed? When should they
7044 not be installed?
</p
>
7046 <p
>If you want to help getting such feature implemented in Debian,
7047 please send me an email. :)
</p
>
7052 <title>New IRC channel for LEGO designers using Debian
</title>
7053 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7055 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7056 <description><p
>During Christmas, I have worked a bit on the Debian support for
7057 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7058 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7059 discovered I had to build all the tools myself because none were
7060 already in Debian Squeeze. If Debian support for LEGO is something
7061 you care about, please join me on the IRC channel
7062 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7063 irc.debian.org). There is a lot that could be done to improve the
7064 Debian support for LEGO designers. For example both CAD software
7065 and Mindstorm compilers are missing. :)
</p
>
7067 <p
>Update
2012-
01-
03: A
7068 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7069 including links to Lego related packages is now available.
</p
>
7074 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7075 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7076 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7077 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7078 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7079 year! I hope next year will prove to be a good year.
</p
>
7081 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7082 decentralised
"currency
" that allow people to transfer bitcoins
7083 between each other with minimal overhead, is a very interesting
7084 experiment. And as I wrote a few days ago, the bitcoin situation in
7085 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7086 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7087 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7088 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7089 for one of the ftpmasters to approve the new bitcoin-qt package
7092 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7093 team in Debian, you can easily test the package in Debian Squeeze
7094 using the following steps to get a set of working packages:
</p
>
7096 <blockquote
><pre
>
7097 git clone git://git.debian.org/git/collab-maint/bitcoin
7099 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7100 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7101 </pre
></blockquote
>
7103 <p
>You might have to install some build dependencies as well. The
7104 list of commands should give you two packages, bitcoind and
7105 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7106 client will download the complete set of bitcoin
"blocks
", which need
7107 around
5.6 GiB of data on my machine at the moment. Make sure your
7108 ~/.bitcoin/ directory have lots of spare room if you want to download
7109 all the blocks. The client will warn if the disk is getting full, so
7110 there is not really a problem if you got too little room, but you will
7111 not be able to get all the features out of the client.
</p
>
7113 <p
>As usual, if you use bitcoin and want to show your support of my
7114 activities, please send Bitcoin donations to my address
7115 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7120 <title>A word on bitcoin support in Debian
</title>
7121 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7122 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7123 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7124 <description><p
>It has been a while since I wrote about
7125 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7126 peer-to-peer based crypto-currency, and the reason is simply that I
7127 have been busy elsewhere. But two days ago, I started looking at the
7128 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7129 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7130 is now maintained by a
7131 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7132 people
</a
>, and the grunt work had already been done by this team. We
7133 owe a huge thank you to all these team members. :)
7134 But I was sad to discover that the bitcoin client is missing in
7135 Wheezy. It is only available in Sid (and an outdated client from
7136 backports). The client had several RC bugs registered in BTS blocking
7137 it from entering testing. To try to help the team and improve the
7138 situation, I spent some time providing patches and triaging the bug
7139 reports. I also had a look at the bitcoin package available from Matt
7141 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7142 Ubuntu
</a
>, and moved the useful pieces from that version into the
7143 Debian package.
</p
>
7145 <p
>After checking with the main package maintainer Jonas Smedegaard on
7146 IRC, I pushed several patches into the collab-maint git repository to
7147 improve the package. It now contains fixes for the RC issues (not from
7148 me, but fixed by Scott Howard), build rules for a Qt GUI client
7149 package, konqueror support for the bitcoin: URI and bash completion
7150 setup. As I work on Debian Squeeze, I also created
7151 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7152 patch to backport
</a
> the latest version. Jonas is going to look at
7153 it and try to integrate it into the git repository before uploading a
7154 new version to unstable.
7156 <p
>I would very much like bitcoin to succeed, to get rid of the
7157 centralized control currently exercised in the monetary system. I
7158 find it completely unacceptable that the USA government is collecting
7159 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7160 that the major credit card companies can block legal money
7161 transactions to Wikileaks. But for bitcoin to succeed, more people
7162 need to use bitcoins, and more people need to accept bitcoins when
7163 they sell products and services. Improving the bitcoin support in
7164 Debian is a small step in the right direction, but not enough.
7165 Unfortunately the user experience when browsing the web and wanting to
7166 pay with bitcoin is still not very good. The bitcoin: URI is a step
7167 in the right direction, but need to work in most or every browser in
7168 use. Also the bitcoin-qt client is too heavy to fire up to do a
7169 quick transaction. I believe there are other clients available, but
7170 have not tested them.
</p
>
7173 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7174 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7175 I received
20.15 BTC so far on the address I provided in my blog two
7176 years ago, as can be
7177 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7178 on the blockexplorer service
</a
>. Thank you everyone for your
7179 donation. The blockexplorer service demonstrates quite well that
7180 bitcoin is not quite anonymous and untracked. :) I wonder if the
7181 number of users have gone up since then. If you use bitcoin and want
7182 to show your support of my activity, please send Bitcoin donations to
7183 the same address as last time,
7184 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7189 <title>Git repository for song book for Computer Scientists
</title>
7190 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7191 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7192 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7193 <description><p
>As I
7194 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7195 this summer
</a
>, I have created a Computer Science song book a few
7196 years ago, and today I finally found time to create a public
7197 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7198 repository for the project
</a
>.
</p
>
7200 <p
>If you want to help out, please clone the source and submit patches
7201 to the HTML version. To generate the PDF and PostScript version,
7202 please use prince XML, or let me know about a useful free software
7203 processor capable of creating a good looking PDF from the HTML.
</p
>
7205 <p
>Want to sing? You can still find the song book in HTML, PDF and
7206 PostScript formats at
7207 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7208 Science Songbook
</a
>.
</p
>
7213 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7214 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7215 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7216 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7217 <description><p
>I dag fyller
7218 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7219 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7220 si gratulerer med dagen, Debian!
</p
>
7225 <title>Song book for Computer Scientists
</title>
7226 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7227 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7228 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7229 <description><p
>Many years ago, while studying Computer Science at the
7230 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7231 collecting computer related songs for use at parties. The original
7232 version was written in LaTeX, but a few years ago I got help from
7233 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7234 while keeping the ability to create a nice book in PDF format. I have
7235 not had time to maintain the book for a while now, and guess I should
7236 put it up on some public version control repository where others can
7237 help me extend and update the book. If anyone is volunteering to help
7238 me with this, send me an email. Also let me know if there are songs
7239 missing in my book.
</p
>
7241 <p
>I have not mentioned the book on my blog so far, and it occured to
7242 me today that I really should let all my readers share the joys of
7243 singing out load about programming, computers and computer networks.
7244 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7245 12</a
> is about to start (and I am not going). Want to sing? Check
7246 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7247 Computer Science Songbook
</a
>.
7252 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7253 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7254 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7255 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7256 <description><p
>At work we have heaps of servers. I believe the total count is
7257 around
1000 at the moment. To be able to get help from the vendors
7258 when something go wrong, we want to keep the firmware on the servers
7259 up to date. If the firmware isn
't the latest and greatest, the
7260 vendors typically refuse to start debugging any problems until the
7261 firmware is upgraded. So before every reboot, we want to upgrade the
7262 firmware, and we would really like everyone handling servers at the
7263 university to do this themselves when they plan to reboot a machine.
7264 For that to happen we at the unix server admin group need to provide
7265 the tools to do so.
</p
>
7267 <p
>To make firmware upgrading easier, I am working on a script to
7268 fetch and install the latest firmware for the servers we got. Most of
7269 our hardware are from Dell and HP, so I have focused on these servers
7270 so far. This blog post is about the Dell part.
</P
>
7272 <p
>On the Dell FTP site I was lucky enough to find
7273 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7274 with firmware information for all
11th generation servers, listing
7275 which firmware should be used on a given model and where on the FTP
7276 site I can find it. Using a simple perl XML parser I can then
7277 download the shell scripts Dell provides to do firmware upgrades from
7278 within Linux and reboot when all the firmware is primed and ready to
7279 be activated on the first reboot.
</p
>
7281 <p
>This is the Dell related fragment of the perl code I am working on.
7282 Are there anyone working on similar tools for firmware upgrading all
7283 servers at a site? Please get in touch and lets share resources.
</p
>
7285 <p
><pre
>
7289 use File::Temp qw(tempdir);
7291 # Install needed RHEL packages if missing
7293 'XML::Simple
' =
> 'perl-XML-Simple
',
7295 for my $module (keys %rhelmodules) {
7296 eval
"use $module;
";
7298 my $pkg = $rhelmodules{$module};
7299 system(
"yum install -y $pkg
");
7300 eval
"use $module;
";
7304 my $errorsto =
'pere@hungry.com
';
7310 sub run_firmware_script {
7311 my ($opts, $script) = @_;
7313 print STDERR
"fail: missing script name\n
";
7316 print STDERR
"Running $script\n\n
";
7318 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7319 print STDERR
"success: firmware script ran succcessfully\n
";
7321 print STDERR
"fail: firmware script returned error\n
";
7325 sub run_firmware_scripts {
7326 my ($opts, @dirs) = @_;
7327 # Run firmware packages
7328 for my $dir (@dirs) {
7329 print STDERR
"info: Running scripts in $dir\n
";
7330 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7331 while (my $s = readdir $dh) {
7332 next if $s =~ m/^\.\.?/;
7333 run_firmware_script($opts,
"$dir/$s
");
7341 print STDERR
"info: Downloading $url\n
";
7342 system(
"wget --quiet \
"$url\
"");
7347 my $product = `dmidecode -s system-product-name`;
7350 if ($product =~ m/PowerEdge/) {
7352 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7353 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7355 my $tmpdir = tempdir(
7359 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7360 system(
'gunzip Catalog.xml.gz
');
7361 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7362 # -q is quiet, disabling interactivity and reducing console output
7363 my $fwopts =
"-q
";
7365 for my $url (@paths) {
7366 fetch_dell_fw($url);
7368 run_firmware_scripts($fwopts, $tmpdir);
7370 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7371 print STDERR
"error: Please report to $errorsto.\n
";
7375 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7376 print STDERR
"error: Please report to $errorsto.\n
";
7382 my $url =
"ftp://ftp.us.dell.com/$path
";
7386 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7387 # firmware packages to download from Dell. Only work for Linux
7388 # machines and
11th generation Dell servers.
7389 sub fetch_dell_fw_list {
7390 my $filename = shift;
7392 my $product = `dmidecode -s system-product-name`;
7394 my ($mybrand, $mymodel) = split(/\s+/, $product);
7396 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7398 my $xml = XMLin($filename);
7400 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7401 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7402 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7404 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7405 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7407 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7409 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7411 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7414 for my $component (@{$xml-
>{SoftwareComponent}}) {
7415 my $componenttype = $component-
>{ComponentType}-
>{value};
7417 # Drop application packages, only firmware and BIOS
7418 next if
'APAC
' eq $componenttype;
7420 my $cpath = $component-
>{path};
7421 for my $path (@paths) {
7422 if ($cpath =~ m%/$path$%) {
7423 push(@paths, $cpath);
7431 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7432 it could work on other platforms with some tweaking. Anyone know a
7433 index like Catalog.xml is available from HP for HP servers? At the
7434 moment I maintain a similar list manually and it is quickly getting
7440 <title>How is booting into runlevel
1 different from single user boots?
</title>
7441 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7442 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7443 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7444 <description><p
>Wouter Verhelst have some
7445 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7446 comments and opinions
</a
> on my blog post on
7447 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7448 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7449 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7450 default KDE desktop in Debian
</a
>. I only have time to address one
7451 small piece of his comment now, and though it best to address the
7452 misunderstanding he bring forward:
</p
>
7454 <p
><blockquote
>
7455 Currently, a system admin has four options: [...] boot to a
7456 single-user system (by adding
'single
' to the kernel command line;
7457 this runs rcS and rc1 scripts)
7458 </blockquote
></p
>
7460 <p
>This make me believe Wouter believe booting into single user mode
7461 and booting into runlevel
1 is the same. I am not surprised he
7462 believe this, because it would make sense and is a quite sensible
7463 thing to believe. But because the boot in Debian is slightly broken,
7464 runlevel
1 do not work properly and it isn
't the same as single user
7465 mode. I
'll try to explain what is actually happing, but it is a bit
7466 hard to explain.
</p
>
7468 <p
>Single user mode is defined like this in /etc/inittab:
7469 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7470 executed in single user mode is sulogin. Single user mode is a boot
7471 state
"between
" the runlevels, and when booting into single user mode,
7472 only the scripts in /etc/rcS.d/ are executed before the init process
7473 enters the single user state. When switching to runlevel
1, the state
7474 is in fact not ending in runlevel
1, but it passes through runlevel
1
7475 and end up in the single user mode (see /etc/rc1.d/S03single, which
7476 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7477 1. It is confusing that the
'S
' (single user) init mode is not the
7478 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7481 <p
>This summary might make it clearer. When booting for the first
7482 time into single user mode, the following commands are executed:
7483 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7484 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7485 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7486 trying to continue after visiting single user mode. Not all services
7487 are started again as they should, causing the machine to end up in an
7488 unpredicatble state. This is why Debian admins recommend rebooting
7489 after visiting single user mode.
</p
>
7491 <p
>A similar problem with runlevel
1 is caused by the amount of
7492 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7493 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7494 stopped when passing through the scripts in /etc/rc1.d/, and not
7495 started again when switching away from runlevel
1 to the runlevels
7496 2-
5. I believe the problem is best fixed by moving all the scripts
7497 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7498 functioning single user mode during boot.
</p
>
7500 <p
>I have spent several years investigating the Debian boot system,
7501 and discovered this problem a few years ago. I suspect it originates
7502 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7507 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7508 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7509 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7510 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7511 <description><p
>In the Debian boot system, several packages include scripts that
7512 are started from /etc/rcS.d/. In fact, there is a bite more of them
7513 than make sense, and this causes a few problems. What kind of
7514 problems, you might ask. There are at least two problems. The first
7515 is that it is not possible to recover a machine after switching to
7516 runlevel
1. One need to actually reboot to get the machine back to
7517 the expected state. The other is that single user boot will sometimes
7518 run into problems because some of the subsystems are activated before
7519 the root login is presented, causing problems when trying to recover a
7520 machine from a problem in that subsystem. A minor additional point is
7521 that moving more scripts out of rcS.d/ and into the other rc#.d/
7522 directories will increase the amount of scripts that can run in
7523 parallel during boot, and thus decrease the boot time.
</p
>
7525 <p
>So, which scripts should start from rcS.d/. In short, only the
7526 scripts that _have_ to execute before the root login prompt is
7527 presented during a single user boot should go there. Everything else
7528 should go into the numeric runlevels. This means things like
7529 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7530 the numeric runlevels. Today in Debian, there are around
115 init.d
7531 scripts that are started from rcS.d/, and most of them should be moved
7532 out. Do your package have one of them? Please help us make single
7533 user and runlevel
1 better by moving it.
</p
>
7535 <p
>Scripts setting up the screen, keyboard, system partitions
7536 etc. should still be started from rcS.d/, but there is for example no
7537 need to have the network enabled before the single user login prompt
7538 is presented.
</p
>
7540 <p
>As always, things are not so easy to fix as they sound. To keep
7541 Debian systems working while scripts migrate and during upgrades, the
7542 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7543 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7544 and the next ones can only be moved when their dependencies have been
7545 moved first. This migration must be done sequentially while we ensure
7546 that the package system upgrade packages in the right order to keep
7547 the system state correct. This will require some coordination when it
7548 comes to network related packages, but most of the packages with
7549 scripts that should migrate do not have anything in rcS.d/ depending
7550 on them. Some packages have already been updated, like the sudo
7551 package, while others are still left to do. I wish I had time to work
7552 on this myself, but real live constrains make it unlikely that I will
7553 find time to push this forward.
</p
>
7558 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7559 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7561 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7562 <description><p
>While at Debconf11, I have several times during discussions
7563 mentioned the issues I believe should be improved in Debian for its
7564 desktop to be useful for more people. The use case for this is my
7565 parents, which are currently running Kubuntu which solve the
7568 <p
>I suspect these four missing features are not very hard to
7569 implement. After all, they are present in Ubuntu, so if we wanted to
7570 do this in Debian we would have a source.
</p
>
7574 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7575 are new packages available for upgrades, a icon in the KDE status bar
7576 indicate this, and clicking on it will activate the simple upgrade
7577 tool to handle it. I have no problem guiding both of my parents
7578 through the process over the phone. If a kernel reboot is required,
7579 this too is indicated by the status bars and the upgrade tool. Last
7580 time I checked, nothing with the same features was working in KDE in
7583 <li
><strong
>Simple handling of missing Firefox browser
7584 plugins.
</strong
> When the browser encounter a MIME type it do not
7585 currently have a handler for, it will ask the user if the system
7586 should search for a package that would add support for this MIME type,
7587 and if the user say yes, the APT sources will be searched for packages
7588 advertising the MIME type in their control file (visible in the
7589 Packages file in the APT archive). If one or more packages are found,
7590 it is a simple click of the mouse to add support for the missing mime
7591 type. If the package require the user to accept some non-free
7592 license, this is explained to the user. The entire process make it
7593 more clear to the user why something do not work in the browser, and
7594 make the chances higher for the user to blame the web page authors and
7595 not the browser for any missing features.
</li
>
7597 <li
><strong
>Simple handling of missing multimedia codec/format
7598 handlers.
</strong
> When the media players encounter a format or codec
7599 it is not supporting, a dialog pop up asking the user if the system
7600 should search for a package that would add support for it. This
7601 happen with things like MP3, Windows Media or H
.264. The selection
7602 and installation procedure is very similar to the Firefox browser
7603 plugin handling. This is as far as I know implemented using a
7604 gstreamer hook. The end result is that the user easily get access to
7605 the codecs that are present from the APT archives available, while
7606 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7608 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7609 displaying a text/plain file in my Debian browser, it will propose to
7610 start emacs to show it. If I remember correctly, when doing the same
7611 in Kunbutu it show the file as a text file in the browser. At least I
7612 know Opera will show text files within the browser. I much prefer the
7613 latter behaviour.
</li
>
7617 <p
>There are other nice features as well, like the simplified suite
7618 upgrader, but given that I am the one mostly doing the dist-upgrade,
7619 it do not matter much.
</p
>
7621 <p
>I really hope we could get these features in place for the next
7622 Debian release. It would require the coordinated effort of several
7623 maintainers, but would make the end user experience a lot better.
</p
>
7628 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7629 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7630 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7631 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7632 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7633 site is build on Debian/Squeeze, and this platform was chosen because
7634 I am most familiar with Debian (being a Debian Developer for around
10
7635 years) because it is the latest stable Debian release which should get
7636 security support for a few years.
</p
>
7638 <p
>The web service is written in Perl, and depend on some perl modules
7639 that are missing in Debian at the moment. It would be great if these
7640 modules were added to the Debian archive, allowing anyone to set up
7641 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7642 in their own country using only Debian packages. The list of modules
7643 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7644 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7645 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7646 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7647 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7648 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7649 easier in the future.
</p
>
7651 <p
>Thanks to the great tools in Debian, getting the missing modules
7652 installed on my server was a simple call to
'cpan2deb Module::Name
'
7653 and
'dpkg -i
' to install the resulting package. But this leave me
7654 with the responsibility of tracking security problems, which I really
7655 do not have time for.
</p
>
7660 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7661 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7662 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7663 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7664 <description><p
>Here is a small update for my English readers. Most of my blog
7665 posts have been in Norwegian the last few weeks, so here is a short
7666 update in English.
</p
>
7668 <p
>The kids still keep me too busy to get much free software work
7669 done, but I did manage to organise a project to get a Norwegian port
7670 of the British service
7671 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7672 and it has been running for a month now. The entire project has been
7673 organised by me and two others. Around Christmas we gathered sponsors
7674 to fund the development work. In January I drafted a contract with
7675 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7676 and in February the development took place. Most of it involved
7677 converting the source to use GPS coordinates instead of British
7678 easting/northing, and the resulting code should be a lot easier to get
7679 running in any country by now. The Norwegian
7680 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7681 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7682 source and the source for administrative borders in Norway, and
7683 support for this had to be added/fixed.
</p
>
7685 <p
>The Norwegian version went live March
3th, and we spent the weekend
7686 polishing the system before we announced it March
7th. The system is
7687 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7688 problem reports in a few weeks. Soon we hope to announce the Android
7689 and iPhone versions making it even easier to report problems with the
7690 public infrastructure.
</p
>
7692 <p
>Perhaps something to consider for those of you in countries without
7693 such service?
</p
>
7698 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7699 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7700 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7701 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7702 <description><p
>The last few days I have looked at ways to track open security
7703 issues here at my work with the University of Oslo. My idea is that
7704 it should be possible to use the information about security issues
7705 available on the Internet, and check our locally
7706 maintained/distributed software against this information. It should
7707 allow us to verify that no known security issues are forgotten. The
7708 CVE database listing vulnerabilities seem like a great central point,
7709 and by using the package lists from Debian mapped to CVEs provided by
7710 the testing security team, I believed it should be possible to figure
7711 out which security holes were present in our free software
7712 collection.
</p
>
7714 <p
>After reading up on the topic, it became obvious that the first
7715 building block is to be able to name software packages in a unique and
7716 consistent way across data sources. I considered several ways to do
7717 this, for example coming up with my own naming scheme like using URLs
7718 to project home pages or URLs to the Freshmeat entries, or using some
7719 existing naming scheme. And it seem like I am not the first one to
7720 come across this problem, as MITRE already proposed and implemented a
7721 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7722 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7723 software, hardware and other platform components. The CPE ids are
7724 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7725 Vulnerability Database
</a
>, allowing me to look up know security
7726 issues for any CPE name. With this in place, all I need to do is to
7727 locate the CPE id for the software packages we use at the university.
7728 This is fairly trivial (I google for
'cve cpe $package
' and check the
7729 NVD entry if a CVE for the package exist).
</p
>
7731 <p
>To give you an example. The GNU gzip source package have the CPE
7732 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7733 check out, one could look up
7734 <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
7735 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7736 The most recent one is
7737 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7738 and at the bottom of the NVD page for this vulnerability the complete
7739 list of affected versions is provided.
</p
>
7741 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7742 for offline processing of issues. Using this dump, I
've written a
7743 small script taking a list of CPEs as input and list all CVEs
7744 affecting the packages represented by these CPEs. One give it CPEs
7745 with version numbers as specified above and get a list of open
7746 security issues out.
</p
>
7748 <p
>Of course for this approach to be useful, the quality of the NVD
7749 information need to be high. For that to happen, I believe as many as
7750 possible need to use and contribute to the NVD database. I notice
7752 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7753 map from CVE to CPE
</a
>, indicating that they are using the CPE
7754 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7756 <p
>To get an idea about the quality for free software, I spent some
7757 time making it possible to compare the CVE database from Debian with
7758 the CVE database in NVD. The result look fairly good, but there are
7759 some inconsistencies in NVD (same software package having several
7760 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7761 Debian believe are affected by a CVE). Hope to find time to improve
7762 the quality of NVD, but that require being able to get in touch with
7763 someone maintaining it. So far my three emails with questions and
7764 corrections have not seen any reply, but I hope contact can be
7765 established soon.
</p
>
7767 <p
>An interesting application for CPEs is cross platform package
7768 mapping. It would be useful to know which packages in for example
7769 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7770 this would be trivial if all linux distributions provided CPE entries
7771 for their packages.
</p
>
7776 <title>Which module is loaded for a given PCI and USB device?
</title>
7777 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7778 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7779 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7780 <description><p
>In the
7781 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7782 package in Debian, there is a script to report useful information
7783 about the running hardware for use when people report missing
7784 information. One part of this script that I find very useful when
7785 debugging hardware problems, is the part mapping loaded kernel module
7786 to the PCI device it claims. It allow me to quickly see if the kernel
7787 module I expect is driving the hardware I am struggling with. To see
7788 the output, make sure discover-data is installed and run
7789 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7790 one of my machines like this:
</p
>
7794 10de:
03eb i2c_nforce2
7797 10de:
03f0 snd_hda_intel
7806 <p
>The code in question look like this, slightly modified for
7807 readability and to drop the output to file descriptor
3:
</p
>
7810 if [ -d /sys/bus/pci/devices/ ] ; then
7811 echo loaded pci modules:
7813 cd /sys/bus/pci/devices/
7814 for address in * ; do
7815 if [ -d
"$address/driver/module
" ] ; then
7816 module=`cd $address/driver/module ; pwd -P | xargs basename`
7817 if grep -q
"^$module
" /proc/modules ; then
7818 address=$(echo $address |sed s/
0000://)
7819 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7820 echo
"$id $module
"
7829 <p
>Similar code could be used to extract USB device module
7833 if [ -d /sys/bus/usb/devices/ ] ; then
7834 echo loaded usb modules:
7836 cd /sys/bus/usb/devices/
7837 for address in * ; do
7838 if [ -d
"$address/driver/module
" ] ; then
7839 module=`cd $address/driver/module ; pwd -P | xargs basename`
7840 if grep -q
"^$module
" /proc/modules ; then
7841 address=$(echo $address |sed s/
0000://)
7842 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7843 if [
"$id
" ] ; then
7844 echo
"$id $module
"
7854 <p
>This might perhaps be something to include in other tools as
7860 <title>How to test if a laptop is working with Linux
</title>
7861 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7862 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7863 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7864 <description><p
>The last few days I have spent at work here at the
<a
7865 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7866 batch of computers will work with Linux. Every year for the last few
7867 years the university have organised shared bid of a few thousand
7868 computers, and this year HP won the bid. Two different desktops and
7869 five different laptops are on the list this year. We in the UNIX
7870 group want to know which one of these computers work well with RHEL
7871 and Ubuntu, the two Linux distributions we currently handle at the
7872 university.
</p
>
7874 <p
>My test method is simple, and I share it here to get feedback and
7875 perhaps inspire others to test hardware as well. To test, I PXE
7876 install the OS version of choice, and log in as my normal user and run
7877 a few applications and plug in selected pieces of hardware. When
7878 something fail, I make a note about this in the test matrix and move
7879 on. If I have some spare time I try to report the bug to the OS
7880 vendor, but as I only have the machines for a short time, I rarely
7881 have the time to do this for all the problems I find.
</p
>
7883 <p
>Anyway, to get to the point of this post. Here is the simple tests
7884 I perform on a new model.
</p
>
7888 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7889 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7890 RHEL5 and Debian Edu/Squeeze.
</li
>
7892 <li
>Is X.org working? If the graphical login screen show up after
7893 installation, X.org is working.
</li
>
7895 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7896 package mesa-utils on Ubuntu) and writing down the frames per second
7897 reported by the program.
</li
>
7899 <li
>Is sound working? With Gnome and KDE, a sound is played when
7900 logging in, and if I can hear this the test is successful. If there
7901 are several audio exits on the machine, I try them all and check if
7902 the Gnome/KDE audio mixer can control where to send the sound. I
7903 normally test this by playing
7904 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7905 video
</a
> in Firefox/Iceweasel.
</li
>
7907 <li
>Is the USB subsystem working? I test this by plugging in a USB
7908 memory stick and see if Gnome/KDE notices this.
</li
>
7910 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7911 I have lying around, and see if Gnome/KDE notices this.
</li
>
7913 <li
>Is any built in camera working? Test using cheese, and see if a
7914 picture from the v4l device show up.
</li
>
7916 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7917 any bluetooth devices are discovered. In my office, I normally see a
7920 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7921 memory modules lying around, and stick them in and see if Gnome/KDE
7922 notice this.
</li
>
7924 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7925 special button work, and if the laptop continue to work after
7928 <li
>For laptops, is the extra buttons working, like audio level,
7929 adjusting background light, switching on/off external video output,
7930 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7931 laptop to laptop, so I just write down which are working and which are
7934 <li
>Some laptops have smart card readers, finger print readers,
7935 acceleration sensors etc. I rarely test these, as I do not know how
7936 to quickly test if they are working or not, so I only document their
7937 existence.
</li
>
7941 <p
>By now I suspect you are really curious what the test results are
7942 for the HP machines I am testing. I
'm not done yet, so I will report
7943 the test results later. For now I can report that HP
8100 Elite work
7944 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7945 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7946 can see, I have most machines left to test. One interesting
7947 observation is that Ubuntu Lucid has almost twice the frame rate than
7948 RHEL6 with glxgears. No idea why.
</p
>
7953 <title>Some thoughts on BitCoins
</title>
7954 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7955 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7956 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7957 <description><p
>As I continue to explore
7958 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7959 what properties the system have, and how it will be affected by laws
7960 and regulations here in Norway. Here are some random notes.
</p
>
7962 <p
>One interesting thing to note is that since the transactions are
7963 verified using a peer to peer network, all details about a transaction
7964 is known to everyone. This means that if a BitCoin address has been
7965 published like I did with mine in my initial post about BitCoin, it is
7966 possible for everyone to see how many BitCoins have been transfered to
7967 that address. There is even a web service to look at the details for
7968 all transactions. There I can see that my address
7969 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7970 have received
16.06 Bitcoin, the
7971 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7972 address of Simon Phipps have received
181.97 BitCoin and the address
7973 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7974 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7975 every one of you that donated bitcoins to support my activity. The
7976 fact that anyone can see how much money was transfered to a given
7977 address make it more obvious why the BitCoin community recommend to
7978 generate and hand out a new address for each transaction. I
'm told
7979 there is no way to track which addresses belong to a given person or
7980 organisation without the person or organisation revealing it
7981 themselves, as Simon, EFF and I have done.
</p
>
7983 <p
>In Norway, and in most other countries, there are laws and
7984 regulations limiting how much money one can transfer across the border
7985 without declaring it. There are money laundering, tax and accounting
7986 laws and regulations I would expect to apply to the use of BitCoin.
7987 If the Skolelinux foundation
7988 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7989 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7990 normal bank transfers like EFF is doing, how should this be accounted?
7991 Given that it is impossible to know if money can cross the border or
7992 not, should everything or nothing be declared? What exchange rate
7993 should be used when calculating taxes? Would receivers have to pay
7994 income tax if the foundation were to pay Skolelinux contributors in
7995 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7997 <p
>For a currency to be useful and successful, it must be trusted and
7998 accepted by a lot of users. It must be possible to get easy access to
7999 the currency (as a wage or using currency exchanges), and it must be
8000 easy to spend it. At the moment BitCoin seem fairly easy to get
8001 access to, but there are very few places to spend it. I am not really
8002 a regular user of any of the vendor types currently accepting BitCoin,
8003 so I wonder when my kind of shop would start accepting BitCoins. I
8004 would like to buy electronics, travels and subway tickets, not herbs
8005 and books. :) The currency is young, and this will improve over time
8006 if it become popular, but I suspect regular banks will start to lobby
8007 to get BitCoin declared illegal if it become popular. I
'm sure they
8008 will claim it is helping fund terrorism and money laundering (which
8009 probably would be true, as is any currency in existence), but I
8010 believe the problems should be solved elsewhere and not by blaming
8011 currencies.
</p
>
8013 <p
>The process of creating new BitCoins is called mining, and it is
8014 CPU intensive process that depend on a bit of luck as well (as one is
8015 competing against all the other miners currently spending CPU cycles
8016 to see which one get the next lump of cash). The
"winner
" get
50
8017 BitCoin when this happen. Yesterday I came across the obvious way to
8018 join forces to increase ones changes of getting at least some coins,
8019 by coordinating the work on mining BitCoins across several machines
8020 and people, and sharing the result if one is lucky and get the
50
8022 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8023 if this sounds interesting. I have not had time to try to set up a
8024 machine to participate there yet, but have seen that running on ones
8025 own for a few days have not yield any BitCoins througth mining
8028 <p
>Update
2010-
12-
15: Found an
<a
8029 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8030 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8031 it was interesting to read. The arguments presented seem to be
8032 equally valid for gold, which was used as a currency for many years.
</p
>
8037 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8038 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8039 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8040 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8041 <description><p
>With this weeks lawless
8042 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8043 attacks
</a
> on Wikileak and
8044 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8045 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8046 not be trusted to handle money transactions.
8048 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8049 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8050 mine mentioned earlier. I decided to follow Simon
's example, and get
8051 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8052 some help from my friend to get it all running, and he even handed me
8053 some bitcoins to get started. I even donated a few bitcoins to Simon
8054 for helping me remember BitCoin.
</p
>
8056 <p
>So, what is bitcoins, you probably wonder? It is a digital
8057 crypto-currency, decentralised and handled using peer-to-peer
8058 networks. It allows anonymous transactions and prohibits central
8059 control over the transactions, making it impossible for governments
8060 and companies alike to block donations and other transactions. The
8061 source is free software, and while the key dependency wxWidgets
2.9
8062 for the graphical user interface is missing in Debian, the command
8063 line client builds just fine. Hopefully Jonas
8064 <a href=
"http://bugs.debian.org/
578157">will get the package into
8065 Debian
</a
> soon.
</p
>
8067 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8068 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8069 bitcoins
</a
> when selling services and goods, and there are even
8070 currency
"stock
" markets where the exchange rate is decided. There
8071 are not many users so far, but the concept seems promising. If you
8072 want to get started and lack a friend with any bitcoins to spare,
8074 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8075 bitcoin at the time of writing). Use
8076 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8077 on the current exchange rates.
</p
>
8079 <p
>As an experiment, I have decided to set up bitcoind on one of my
8080 machines. If you want to support my activity, please send Bitcoin
8081 donations to the address
8082 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8087 <title>Why isn
't Debian Edu using VLC?
</title>
8088 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8090 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8091 <description><p
>In the latest issue of Linux Journal, the readers choices were
8092 presented, and the winner among the multimedia player were VLC.
8093 Personally, I like VLC, and it is my player of choice when I first try
8094 to play a video file or stream. Only if VLC fail will I drag out
8095 gmplayer to see if it can do better. The reason is mostly the failure
8096 model and trust. When VLC fail, it normally pop up a error message
8097 reporting the problem. When mplayer fail, it normally segfault or
8098 just hangs. The latter failure mode drain my trust in the program.
<p
>
8100 <p
>But even if VLC is my player of choice, we have choosen to use
8101 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8102 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8103 plugin to play web videos seamlessly, and the VLC browser plugin is
8104 not very good. For example, it lack in-line control buttons, so there
8105 is no way for the user to pause the video. Also, when I
8106 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8107 tested the browser plugins
</a
> available in Debian, the VLC plugin
8108 failed on several video pages where mplayer based plugins worked. If
8109 the browser plugin for VLC was as good as the gecko-mediaplayer
8110 package (which uses mplayer), we would switch.
</P
>
8112 <p
>While VLC is a good player, its user interface is slightly
8113 annoying. The most annoying feature is its inconsistent use of
8114 keyboard shortcuts. When the player is in full screen mode, its
8115 shortcuts are different from when it is playing the video in a window.
8116 For example, space only work as pause when in full screen mode. I
8117 wish it had consisten shortcuts and that space also would work when in
8118 window mode. Another nice shortcut in gmplayer is [enter] to restart
8119 the current video. It is very nice when playing short videos from the
8120 web and want to restart it when new people arrive to have a look at
8121 what is going on.
</p
>
8126 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8127 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8128 <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>
8129 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8130 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8131 upgrade testing of the
8132 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8133 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8134 This seem like a very good idea, so I adjusted by test scripts and
8135 can now present the updated result from today:
</p
>
8137 <p
>This is for Gnome:
</p
>
8139 <p
>Installed using apt-get, missing with aptitude
</p
>
8141 <blockquote
><p
>
8146 browser-plugin-gnash
8153 freedesktop-sound-theme
8155 gconf-defaults-service
8170 gnome-desktop-environment
8174 gnome-session-canberra
8179 gstreamer0.10-fluendo-mp3
8185 libapache2-mod-dnssd
8188 libaprutil1-dbd-sqlite3
8191 libboost-date-time1.42
.0
8192 libboost-python1.42
.0
8193 libboost-thread1.42
.0
8195 libchamplain-gtk-
0.4-
0
8197 libclutter-gtk-
0.10-
0
8204 libfreerdp-plugins-standard
8219 libgnomepanel2.24-cil
8224 libgtksourceview2.0-common
8225 libmono-addins-gui0.2-cil
8226 libmono-addins0.2-cil
8227 libmono-cairo2.0-cil
8228 libmono-corlib2.0-cil
8229 libmono-i18n-west2.0-cil
8230 libmono-posix2.0-cil
8231 libmono-security2.0-cil
8232 libmono-sharpzip2.84-cil
8233 libmono-system2.0-cil
8236 libndesk-dbus-glib1.0-cil
8237 libndesk-dbus1.0-cil
8247 libtelepathy-farsight0
8256 nautilus-sendto-empathy
8260 python-aptdaemon-gtk
8262 python-beautifulsoup
8277 python-gtksourceview2
8288 python-pkg-resources
8295 python-twisted-conch
8301 python-zope.interface
8306 rhythmbox-plugin-cdrecorder
8313 system-config-printer-udev
8315 telepathy-mission-control-
5
8326 </p
></blockquote
>
8328 <p
>Installed using apt-get, removed with aptitude
</p
>
8330 <blockquote
><p
>
8336 fast-user-switch-applet
8355 libgtksourceview2.0-
0
8357 libsdl1.2debian-alsa
8363 system-config-printer
8368 </p
></blockquote
>
8370 <p
>Installed using aptitude, missing with apt-get
</p
>
8372 <blockquote
><p
>
8373 gstreamer0.10-gnomevfs
8374 </p
></blockquote
>
8376 <p
>Installed using aptitude, removed with apt-get
</p
>
8378 <blockquote
><p
>
8380 </p
></blockquote
>
8382 <p
>This is for KDE:
</p
>
8384 <p
>Installed using apt-get, missing with aptitude
</p
>
8386 <blockquote
><p
>
8388 </p
></blockquote
>
8390 <p
>Installed using apt-get, removed with aptitude
</p
>
8392 <blockquote
><p
>
8395 </p
></blockquote
>
8397 <p
>Installed using aptitude, missing with apt-get
</p
>
8399 <blockquote
><p
>
8413 kdeartwork-emoticons
8415 kdeartwork-theme-icon
8419 kdebase-workspace-bin
8420 kdebase-workspace-data
8434 kscreensaver-xsavers
8449 plasma-dataengines-workspace
8451 plasma-desktopthemes-artwork
8452 plasma-runners-addons
8453 plasma-scriptengine-googlegadgets
8454 plasma-scriptengine-python
8455 plasma-scriptengine-qedje
8456 plasma-scriptengine-ruby
8457 plasma-scriptengine-webkit
8458 plasma-scriptengines
8459 plasma-wallpapers-addons
8460 plasma-widget-folderview
8461 plasma-widget-networkmanagement
8465 xscreensaver-data-extra
8467 xscreensaver-gl-extra
8468 xscreensaver-screensaver-bsod
8469 </p
></blockquote
>
8471 <p
>Installed using aptitude, removed with apt-get
</p
>
8473 <blockquote
><p
>
8475 google-gadgets-common
8493 libggadget-qt-
1.0-
0b
8498 libkonqsidebarplugin4a
8507 libplasma-geolocation-interface4
8509 libplasmagenericshell4
8523 libsmokeknewstuff2-
3
8524 libsmokeknewstuff3-
3
8526 libsmokektexteditor3
8534 libsmokeqtnetwork4-
3
8540 libsmokeqtuitools4-
3
8552 plasma-dataengines-addons
8553 plasma-scriptengine-superkaramba
8554 plasma-widget-lancelot
8555 plasma-widgets-addons
8556 plasma-widgets-workspace
8560 update-notifier-common
8561 </p
></blockquote
>
8563 <p
>Running apt-get autoremove made the results using apt-get and
8564 aptitude a bit more similar, but there are still quite a lott of
8565 differences. I have no idea what packages should be installed after
8566 the upgrade, but hope those that do can have a look.
</p
>
8571 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8572 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8573 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8574 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8575 <description><p
>Most of the computers in use by the
8576 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8577 are virtual machines. And they have been Xen machines running on a
8578 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8579 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8580 bit harder that it could have been, because we set up the Xen virtual
8581 machines to get the virtual partitions from LVM, which as far as I
8582 know is not supported by KVM. So to migrate, we had to convert
8583 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8586 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8587 nice recipe
</a
> to do this, and wrote the following script to do the
8588 migration. It uses qemu-img from the qemu package to make the disk
8589 image, parted to partition it, losetup and kpartx to present the disk
8590 image partions as devices, and dd to copy the data. I NFS mounted the
8591 new servers storage area on the old server to do the migration.
</p
>
8597 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8602 if [ -z
"$
1" ] ; then
8603 echo
"Usage: $
0 &lt;hostname
&gt;
"
8609 if [ ! -e /dev/vg_data/$host-disk ] ; then
8610 echo
"error: unable to find LVM volume for $host
"
8614 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8615 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8616 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8617 totalsize=$(( ( $disksize + $swapsize ) ))
8620 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8621 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8623 parted $img mklabel msdos
8624 parted $img mkpart primary linux-swap
0 $disksize
8625 parted $img mkpart primary ext2 $disksize $totalsize
8626 parted $img set
1 boot on
8629 losetup /dev/loop0 $img
8630 kpartx -a /dev/loop0
8632 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8633 fsck.ext3 -f /dev/mapper/loop0p1 || true
8634 mkswap /dev/mapper/loop0p2
8636 kpartx -d /dev/loop0
8637 losetup -d /dev/loop0
8640 <p
>The script is perhaps so simple that it is not copyrightable, but
8641 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8643 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8644 the new disk image attached, installed grub-pc and linux-image-
686 and
8645 set up grub to boot from the disk image. After this, the KVM machines
8646 seem to work just fine.
</p
>
8651 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8652 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8654 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8655 <description><p
>I
'm still running upgrade testing of the
8656 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8657 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8658 status. Here is a short update based on a test I ran
20101118.
</p
>
8660 <p
>I still do not know what a correct migration should look like, so I
8661 report any differences between apt and aptitude and hope someone else
8662 can see if anything should be changed.
</p
>
8664 <p
>This is for Gnome:
</p
>
8666 <p
>Installed using apt-get, missing with aptitude
</p
>
8668 <blockquote
><p
>
8669 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8670 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8671 dmz-cursor-theme empathy empathy-common finger
8672 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8673 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8674 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8675 gnome-cards-data gnome-codec-install gnome-core
8676 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8677 gnome-search-tool gnome-session-canberra gnome-spell
8678 gnome-system-log gnome-themes-extras gnome-themes-more
8679 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8680 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8681 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8682 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8683 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8684 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8685 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8686 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8687 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8688 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8689 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8690 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8691 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8692 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8693 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8694 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8695 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8696 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8697 libmono-security2.0-cil libmono-sharpzip2.84-cil
8698 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8699 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8700 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8701 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8702 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8703 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8704 libxalan2-java libxerces2-java media-player-info mesa-utils
8705 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8706 nautilus-sendto-empathy openoffice.org-writer2latex
8707 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8708 python-aptdaemon python-aptdaemon-gtk python-axiom
8709 python-beautifulsoup python-bugbuddy python-clientform
8710 python-coherence python-configobj python-crypto python-cupshelpers
8711 python-cupsutils python-eggtrayicon python-elementtree
8712 python-epsilon python-evolution python-feedparser python-gdata
8713 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8714 python-gtksourceview2 python-httplib2 python-louie python-mako
8715 python-markupsafe python-mechanize python-nevow python-notify
8716 python-opengl python-openssl python-pam python-pkg-resources
8717 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8718 python-tagpy python-twisted-bin python-twisted-conch
8719 python-twisted-core python-twisted-web python-utidylib python-webkit
8720 python-xdg python-zope.interface remmina remmina-plugin-data
8721 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8722 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8723 software-center svgalibg1 system-config-printer-udev
8724 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8725 totem totem-coherence totem-mozilla totem-plugins
8726 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8728 </p
></blockquote
>
8730 Installed using apt-get, removed with aptitude
8732 <blockquote
><p
>
8733 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8734 epiphany-extensions epiphany-gecko evolution-exchange
8735 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8736 gedit-common gnome-app-install gnome-games gnome-games-data
8737 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8738 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8739 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8740 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8741 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8742 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8743 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8744 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8745 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8746 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8747 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8748 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8749 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8750 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8751 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8752 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8753 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8754 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8755 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8756 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8757 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8758 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8759 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8760 sound-juicer swfdec-gnome system-config-printer totem-common
8761 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8762 </p
></blockquote
>
8764 <p
>Installed using aptitude, missing with apt-get
</p
>
8766 <blockquote
><p
>
8767 gstreamer0.10-gnomevfs
8768 </p
></blockquote
>
8770 <p
>Installed using aptitude, removed with apt-get
</p
>
8772 <blockquote
><p
>
8774 </p
></blockquote
>
8776 <p
>This is for KDE:
</p
>
8778 <p
>Installed using apt-get, missing with aptitude
</p
>
8780 <blockquote
><p
>
8781 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8782 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8783 ghostscript-x git gnome-audio gnugo granatier gs-common
8784 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8785 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8786 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8787 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8788 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8789 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8790 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8791 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8792 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8793 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8794 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8795 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8796 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8797 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8798 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8799 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8800 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8801 libkrossui4 libmailtools-perl libmime-tools-perl
8802 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8803 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8804 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8805 lirc luatex marble networkstatus noatun-plugins
8806 openoffice.org-writer2latex palapeli palapeli-data parley
8807 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8808 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8809 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8811 </p
></blockquote
>
8813 <p
>Installed using apt-get, removed with aptitude
</p
>
8815 <blockquote
><p
>
8816 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8817 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8818 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8819 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8820 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8821 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8822 kitchensync kiten kjumpingcube klatin klettres klickety klines
8823 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8824 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8825 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8826 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8827 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8828 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8829 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8830 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8831 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8832 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8833 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8834 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8835 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8836 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8837 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8838 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8839 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8840 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8841 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8842 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8843 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8844 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8845 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8846 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8847 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8848 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8849 </p
></blockquote
>
8851 <p
>Installed using aptitude, missing with apt-get
</p
>
8853 <blockquote
><p
>
8854 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8855 kdeartwork kdebase kdebase-apps kdebase-workspace
8856 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8857 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8858 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8859 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8860 xscreensaver-screensaver-bsod
8861 </p
></blockquote
>
8863 <p
>Installed using aptitude, removed with apt-get
</p
>
8865 <blockquote
><p
>
8866 kdebase-bin konq-plugins konqueror
8867 </p
></blockquote
>
8872 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8873 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8875 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8876 <description><p
>Answering
8877 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8878 call from the Gnash project
</a
> for
8879 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8880 current source, I have set up a virtual KVM machine on the Debian
8881 Edu/Skolelinux virtualization host to test the git source on
8882 Debian/Squeeze. I hope this can help the developers in getting new
8883 releases out more often.
</p
>
8885 <p
>As the developers want less main-stream build platforms tested to,
8886 I have considered setting up a
<a
8887 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8888 machine as well. I have also considered using the kfreebsd
8889 architecture in Debian as a file server in NUUG to get access to the
5
8890 TB zfs volume we currently use to store DV video. Because of this, I
8891 finally got around to do a test installation of Debian/Squeeze with
8892 kfreebsd. Installation went fairly smooth, thought I noticed some
8893 visual glitches in the cdebconf dialogs (black cursor left on the
8894 screen at random locations). Have not gotten very far with the
8895 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8896 fatal problem. Have to spend some more time on it to see if it is
8897 useful as a file server for NUUG. Will try to find time to set up a
8898 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8903 <title>Debian in
3D
</title>
8904 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8905 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8906 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8907 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8909 <p
>3D printing is just great. I just came across this Debian logo in
8911 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8912 thingiverse blog
</a
>.
</p
>
8917 <title>Software updates
2010-
10-
24</title>
8918 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8919 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8920 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8921 <description><p
>Some updates.
</p
>
8923 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8924 raise money for the project is going well. The lower limit of
10
8925 signers was reached in
24 hours, and so far
13 people have signed it.
8926 More signers and more funding is most welcome, and I am really curious
8927 how far we can get before the time limit of December
24 is reached.
8930 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8931 about what appear to be a great code coverage tool capable of
8932 generating code coverage stats without any changes to the source code.
8934 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8935 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8936 It is missing in Debian, but the git source built just fine in Squeeze
8937 after I installed libelf-dev, libdwarf-dev, pkg-config and
8938 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8939 solvable. I hope kcov make it into Debian soon.
</p
>
8941 <p
>Finally found time to wrap up the release notes for
<a
8942 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8943 new alpha release of Debian Edu
</a
>, and just published the second
8944 alpha test release of the Squeeze based Debian Edu /
8945 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8946 release. Give it a try if you need a complete linux solution for your
8947 school, including central infrastructure server, workstations, thin
8948 client servers and diskless workstations. A nice touch added
8949 yesterday is RDP support on the thin client servers, for windows
8950 clients to get a Linux desktop on request.
</p
>
8955 <title>Some notes on Flash in Debian and Debian Edu
</title>
8956 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8957 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8958 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8959 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8960 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8961 second most popular used package that is missing in Debian. The sixth
8962 most popular is flashplayer-mozilla. This is a clear indication that
8963 working flash is important for Debian users. Around
10 percent of the
8964 users submitting data to popcon.debian.org have this package
8965 installed.
</p
>
8967 <p
>In the report written by Lars Risan in August
2008
8968 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8969 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8970 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8971 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8972 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8973 web sites require Flash to work, and lacking working Flash support in
8974 the web browser and the problems with installing it was perceived as a
8975 good reason to stay with Windows.
</p
>
8977 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8978 said to be the retarded cousin that did not really understand
8979 everything you told him but could work fairly well. This was a
8980 comment regarding the problems Linux have with proprietary formats and
8981 non-standard web pages, and is sad because it exposes a fairly common
8982 understanding of whose fault it is if web pages that only work in for
8983 example Internet Explorer
6 fail to work on Firefox, and funny because
8984 it explain very well how annoying it is for users when Linux
8985 distributions do not work with the documents they receive or the web
8986 pages they want to visit.
</p
>
8988 <p
>This is part of the reason why I believe it is important for Debian
8989 and Debian Edu to have a well working Flash implementation in the
8990 distribution, to get at least popular sites as Youtube and Google
8991 Video to working out of the box. For Squeeze, Debian have the chance
8992 to include the latest version of Gnash that will make this happen, as
8993 the new release
0.8.8 was published a few weeks ago and is resting in
8994 unstable. The new version work with more sites that version
0.8.7.
8995 The Gnash maintainers have asked for a freeze exception, but the
8996 release team have not had time to reply to it yet. I hope they agree
8997 with me that Flash is important for the Debian desktop users, and thus
8998 accept the new package into Squeeze.
</p
>
9003 <title>Circular package dependencies harms apt recovery
</title>
9004 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9005 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9006 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9007 <description><p
>I discovered this while doing
9008 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9009 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9010 in Debian still got circular dependencies, and it is often claimed
9011 that apt and aptitude should be able to handle this just fine, but
9012 some times these dependency loops causes apt to fail.
</p
>
9014 <p
>An example is from todays
9015 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9016 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9017 causes perl-modules to fail to upgrade. The cause is simple. If a
9018 package fail to unpack, then only part of packages with the circular
9019 dependency might end up being unpacked when unpacking aborts, and the
9020 ones already unpacked will fail to configure in the recovery phase
9021 because its dependencies are unavailable.
</p
>
9023 <p
>In this log, the problem manifest itself with this error:
</p
>
9025 <blockquote
><pre
>
9026 dpkg: dependency problems prevent configuration of perl-modules:
9027 perl-modules depends on perl (
>=
5.10.1-
1); however:
9028 Version of perl on system is
5.10.0-
19lenny
2.
9029 dpkg: error processing perl-modules (--configure):
9030 dependency problems - leaving unconfigured
9031 </pre
></blockquote
>
9033 <p
>The perl/perl-modules circular dependency is already
9034 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9035 hopefully be solved as soon as possible, but it is not the only one,
9036 and each one of these loops in the dependency tree can cause similar
9037 failures. Of course, they only occur when there are bugs in other
9038 packages causing the unpacking to fail, but it is rather nasty when
9039 the failure of one package causes the problem to become worse because
9040 of dependency loops.
</p
>
9043 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9044 tireless effort by Bill Allombert
</a
>, the number of circular
9046 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9047 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9049 <p
>Todays testing also exposed a bug in
9050 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9051 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9052 apt-get and aptitude, the latter possibly caused by some circular
9053 dependency. Reported both to BTS to try to get someone to look at
9059 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9060 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9061 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9062 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9063 <description><p
>This is a
9064 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9066 <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
9068 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9069 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9071 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9072 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9073 and dhcp3-server-ldap in Debian use the LDAP server. The two
9074 implementations are quite different in how they use LDAP.
</p
>
9076 To get this information, I started slapd with debugging enabled and
9077 dumped the debug output to a file to get the LDAP searches performed
9078 on a Debian Edu main-server. Here is a summary.
9080 <p
><strong
>powerdns
</strong
></p
>
9082 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9083 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9086 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9087 One
"strict
" mode where the forward and reverse DNS lookups are done
9088 using the same LDAP objects, and a
"tree
" mode where the forward and
9089 reverse entries are in two different subtrees in LDAP with a structure
9090 based on the DNS names, as in tjener.intern and
9091 2.2.0.10.in-addr.arpa.
</p
>
9093 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9094 base, and uses a
"base
" scoped search for the DNS name by adding
9095 "dc=tjener,dc=intern,
" to the base with a filter for
9096 "(associateddomain=tjener.intern)
" for the forward entry and
9097 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9098 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9099 forward entries, it is looking for attributes named dnsttl, arecord,
9100 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9101 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9102 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9103 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9104 spfrecord and modifytimestamp. For reverse entries it is looking for
9105 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9106 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9107 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9108 ldapsearch commands could look like this:
</p
>
9110 <blockquote
><pre
>
9111 ldapsearch -h ldap \
9112 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9113 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9114 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9115 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9116 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9117 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9119 ldapsearch -h ldap \
9120 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9121 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9122 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9123 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9124 srvrecord naptrrecord modifytimestamp
9125 </pre
></blockquote
>
9127 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9128 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9129 example LDAP objects used there. In addition to these objects, the
9130 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9131 also exist.
</p
>
9133 <blockquote
><pre
>
9134 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9136 objectclass: dnsdomain
9137 objectclass: domainrelatedobject
9140 associateddomain: tjener.intern
9142 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9144 objectclass: dnsdomain2
9145 objectclass: domainrelatedobject
9147 ptrrecord: tjener.intern
9148 associateddomain:
2.2.0.10.in-addr.arpa
9149 </pre
></blockquote
>
9151 <p
>In strict mode, the server behaves differently. When looking for
9152 forward DNS entries, it is doing a
"subtree
" scoped search with the
9153 same base as in the tree mode for a object with filter
9154 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9155 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9156 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9157 naptrrecord and modifytimestamp. For reverse entires it also do a
9158 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9159 and the requested attributes are associateddomain, dnsttl and
9160 modifytimestamp. In short, in strict mode the objects with ptrrecord
9161 go away, and the arecord attribute in the forward object is used
9164 <p
>The forward and reverse searches can be simulated using ldapsearch
9165 like this:
</p
>
9167 <blockquote
><pre
>
9168 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9169 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9170 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9171 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9172 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9173 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9175 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9176 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9177 </pre
></blockquote
>
9179 <p
>In addition to the forward and reverse searches , there is also a
9180 search for SOA records, which behave similar to the forward and
9181 reverse lookups.
</p
>
9183 <p
>A thing to note with the PowerDNS behaviour is that it do not
9184 specify any objectclass names, and instead look for the attributes it
9185 need to generate a DNS reply. This make it able to work with any
9186 objectclass that provide the needed attributes.
</p
>
9188 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9189 dnsdomain2 schemas. The latter is used for reverse entries like
9190 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9192 <p
>In Debian Edu, we have created DNS objects using the object classes
9193 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9194 attributes) and domainrelatedobject (for associatedDomain). The use
9195 of structural object classes make it impossible to combine these
9196 classes with the object classes used by DHCP.
</p
>
9198 <p
>There are other schemas that could be used too, for example the
9199 dnszone structural object class used by Gosa and bind-sdb for the DNS
9200 attributes combined with the domainrelatedobject object class, but in
9201 this case some unused attributes would have to be included as well
9202 (zonename and relativedomainname).
</p
>
9204 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9205 mode and not use any of the existing objectclasses (dnsdomain,
9206 dnsdomain2 and dnszone) when one want to combine the DNS information
9207 with DHCP information, and instead create a auxiliary object class
9208 defined something like this (using the attributes defined for
9209 dnsdomain and dnsdomain2 or dnszone):
</p
>
9211 <blockquote
><pre
>
9212 objectclass ( some-oid NAME
'dnsDomainAux
'
9215 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9216 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9217 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9218 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9219 A6Record $ DNAMERecord
9221 </pre
></blockquote
>
9223 <p
>This will allow any object to become a DNS entry when combined with
9224 the domainrelatedobject object class, and allow any entity to include
9225 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9226 developers asking for their view on this schema and if they are
9227 interested in providing such schema with PowerDNS, and I hope my
9228 message will be accepted into their mailing list soon.
</p
>
9230 <p
><strong
>ISC dhcp
</strong
></p
>
9232 <p
>The DHCP server searches for specific objectclass and requests all
9233 the object attributes, and then uses the attributes it want. This
9234 make it harder to figure out exactly what attributes are used, but
9235 thanks to the working example in Debian Edu I can at least get an idea
9236 what is needed without having to read the source code.
</p
>
9238 <p
>In the DHCP server configuration, the LDAP base to use and the
9239 search filter to use to locate the correct dhcpServer entity is
9240 stored. These are the relevant entries from
9241 /etc/dhcp3/dhcpd.conf:
</p
>
9243 <blockquote
><pre
>
9244 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9245 ldap-dhcp-server-cn
"dhcp
";
9246 </pre
></blockquote
>
9248 <p
>The DHCP server uses this information to nest all the DHCP
9249 configuration it need. The cn
"dhcp
" is located using the given LDAP
9250 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9251 search result is this entry:
</p
>
9253 <blockquote
><pre
>
9254 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9257 objectClass: dhcpServer
9258 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9259 </pre
></blockquote
>
9261 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9262 subtree with DHCP configuration. The DHCP configuration subtree base
9263 is located using a base scope search with base
"cn=DHCP
9264 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9265 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9266 The search result is this entry:
</p
>
9268 <blockquote
><pre
>
9269 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9272 objectClass: dhcpService
9273 objectClass: dhcpOptions
9274 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9275 dhcpStatements: ddns-update-style none
9276 dhcpStatements: authoritative
9277 dhcpOption: smtp-server code
69 = array of ip-address
9278 dhcpOption: www-server code
72 = array of ip-address
9279 dhcpOption: wpad-url code
252 = text
9280 </pre
></blockquote
>
9282 <p
>Next, the entire subtree is processed, one level at the time. When
9283 all the DHCP configuration is loaded, it is ready to receive requests.
9284 The subtree in Debian Edu contain objects with object classes
9285 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9286 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9287 and information about netmasks, dynamic range etc. Leaving out the
9288 details here because it is not relevant for the focus of my
9289 investigation, which is to see if it is possible to merge dns and dhcp
9290 related computer objects.
</p
>
9292 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9293 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9294 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9295 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9296 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9299 <blockquote
><pre
>
9300 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9303 objectClass: dhcpHost
9304 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9305 dhcpStatements: fixed-address hostname
9306 </pre
></blockquote
>
9308 <p
>There is less flexiblity in the way LDAP searches are done here.
9309 The object classes need to have fixed names, and the configuration
9310 need to be stored in a fairly specific LDAP structure. On the
9311 positive side, the invidiual dhcpHost entires can be anywhere without
9312 the DN pointed to by the dhcpServer entries. The latter should make
9313 it possible to group all host entries in a subtree next to the
9314 configuration entries, and this subtree can also be shared with the
9315 DNS server if the schema proposed above is combined with the dhcpHost
9316 structural object class.
9318 <p
><strong
>Conclusion
</strong
></p
>
9320 <p
>The PowerDNS implementation seem to be very flexible when it come
9321 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9322 come to the the LDAP structure, the
"strict
" mode is very flexible,
9323 allowing DNS objects to be stored anywhere under the base cn specified
9324 in the configuration.
</p
>
9326 <p
>The DHCP implementation on the other hand is very inflexible, both
9327 regarding which LDAP schemas to use and which LDAP structure to use.
9328 I guess one could implement ones own schema, as long as the
9329 objectclasses and attributes have the names used, but this do not
9330 really help when the DHCP subtree need to have a fairly fixed
9331 structure.
</p
>
9333 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9334 this might work for Debian Edu:
</p
>
9336 <blockquote
><pre
>
9338 cn=machine-info (dhcpService) - dhcpServiceDN points here
9339 cn=dhcp (dhcpServer)
9340 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9341 cn=
10.0.2.0 (dhcpSubnet)
9342 cn=group1 (dhcpGroup/dhcpOptions)
9343 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9344 cn=
192.168.0.0 (dhcpSubnet)
9345 cn=group1 (dhcpGroup/dhcpOptions)
9346 ou=machines - PowerDNS base points here
9347 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9348 </pre
></blockquote
>
9350 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9351 entries to be in the dhcpGroup subtrees, the entries can be stored
9352 there instead of a common machines subtree, and the PowerDNS base
9353 would have to be moved one level up to the machine-info subtree.
</p
>
9355 <p
>The combined object under the machines subtree would look something
9356 like this:
</p
>
9358 <blockquote
><pre
>
9359 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9362 objectClass: dhcpHost
9363 objectclass: domainrelatedobject
9364 objectclass: dnsDomainAux
9365 associateddomain: hostname.intern
9366 arecord:
10.11.12.13
9367 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9368 dhcpStatements: fixed-address hostname.intern
9369 </pre
></blockquote
>
9371 </p
>One could even add the LTSP configuration associated with a given
9372 machine, as long as the required attributes are available in a
9373 auxiliary object class.
</p
>
9378 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9379 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9380 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9381 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9382 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9383 DHCP services in Debian Edu to use the same LDAP objects for a given
9384 computer, to avoid the possibility of having a inconsistent state for
9385 a computer in LDAP (as in DHCP but no DNS entry or the other way
9386 around) and make it easier to add computers to LDAP.
</p
>
9388 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9389 information finally found a solution that seem to work.
</p
>
9391 <p
>The old setup required three LDAP objects for a given computer.
9392 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9393 we switch powerdns to use its strict LDAP method (ldap-method=strict
9394 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9395 merged into one while making it impossible to transfer the reverse map
9396 to a slave DNS server.
</p
>
9398 <p
>If we also replace the object class used to get the DNS related
9399 attributes to one allowing these attributes to be combined with the
9400 dhcphost object class, we can merge the DNS and DHCP entries into one.
9401 I
've written such object class in the dnsdomainaux.schema file (need
9402 proper OIDs, but that is a minor issue), and tested the setup. It
9403 seem to work.
</p
>
9405 <p
>With this test setup in place, we can get away with one LDAP object
9406 for both DNS and DHCP, and even the LTSP configuration I suggested in
9407 an earlier email. The combined LDAP object will look something like
9410 <blockquote
><pre
>
9411 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9413 objectClass: dhcphost
9414 objectclass: domainrelatedobject
9415 objectclass: dnsdomainaux
9416 associateddomain: hostname.intern
9417 arecord:
10.11.12.13
9418 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9419 dhcpstatements: fixed-address hostname
9421 </pre
></blockquote
>
9423 <p
>The DNS server uses the associateddomain and arecord entries, while
9424 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9425 before asking DNS to resolve the fixed-adddress. LTSP will use
9426 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9428 <p
>I am not yet sure if I can get the DHCP server to look for its
9429 dhcphost in a different location, to allow us to put the objects
9430 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9431 that. If I can
't figure out a way to do that, we can still get rid of
9432 the hosts subtree and move all its content into the DHCP Config tree
9433 (which probably should be renamed to be more related to the new
9434 content. I suspect cn=dnsdhcp,ou=services or something like that
9435 might be a good place to put it.
</p
>
9437 <p
>If you want to help out with implementing this for Debian Edu,
9438 please contact us on debian-edu@lists.debian.org.
</p
>
9443 <title>Idea for storing LTSP configuration in LDAP
</title>
9444 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9445 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9446 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9447 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9448 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9449 clients, and that this can be used to fetch configuration from LDAP if
9450 Debian Edu choose to store configuration there.
</p
>
9452 <p
>Armed with this information, I got inspired and wrote a test module
9453 to get configuration from LDAP. The idea is to look up the MAC
9454 address of the client in LDAP, and look for attributes on the form
9455 ltspconfigsetting=value, and use this to export SETTING=value to the
9456 LTSP clients.
</p
>
9458 <p
>The goal is to be able to store the LTSP configuration attributes
9459 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9460 allowing us to store all information about a computer in one place.
</p
>
9462 <p
>This is a untested draft implementation, and I welcome feedback on
9463 this approach. A real LDAP schema for the ltspClientAux objectclass
9464 need to be written. Comments, suggestions, etc?
</p
>
9466 <blockquote
><pre
>
9467 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9469 # Fetch LTSP client settings from LDAP based on MAC address
9471 # Uses ethernet address as stored in the dhcpHost objectclass using
9472 # the dhcpHWAddress attribute or ethernet address stored in the
9473 # ieee802Device objectclass with the macAddress attribute.
9475 # This module is written to be schema agnostic, and only depend on the
9476 # existence of attribute names.
9478 # The LTSP configuration variables are saved directly using a
9479 # ltspConfig prefix and uppercasing the rest of the attribute name.
9480 # To set the SERVER variable, set the ltspConfigServer attribute.
9482 # Some LDAP schema should be created with all the relevant
9483 # configuration settings. Something like this should work:
9485 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9488 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9490 LDAPSERVER=$(debian-edu-ldapserver)
9491 if [
"$LDAPSERVER
" ] ; then
9492 LDAPBASE=$(debian-edu-ldapserver -b)
9493 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9494 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9495 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9496 grep
'^ltspConfig
' | while read attr value ; do
9497 # Remove prefix and convert to upper case
9498 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9499 # bass value on to clients
9500 eval
"$attr=$value; export $attr
"
9504 </pre
></blockquote
>
9506 <p
>I
'm not sure this shell construction will work, because I suspect
9507 the while block might end up in a subshell causing the variables set
9508 there to not show up in ltsp-config, but if that is the case I am sure
9509 the code can be restructured to make sure the variables are passed on.
9510 I expect that can be solved with some testing. :)
</p
>
9512 <p
>If you want to help out with implementing this for Debian Edu,
9513 please contact us on debian-edu@lists.debian.org.
</p
>
9515 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9516 configuration in LDAP that was created around year
2000 by
9517 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9518 Xperience, Inc.,
2000</a
>. I found its
9519 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9520 personal home page over at redhat.com.
</p
>
9525 <title>jXplorer, a very nice LDAP GUI
</title>
9526 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9527 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9528 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9529 <description><p
>Since
9530 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9531 last post
</a
> about available LDAP tools in Debian, I was told about a
9532 LDAP GUI that is even better than luma. The java application
9533 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9534 moving LDAP objects and subtrees using drag-and-drop, and can
9535 authenticate using Kerberos. I have only tested the Kerberos
9536 authentication, but do not have a LDAP setup allowing me to rewrite
9537 LDAP with my test user yet. It is
9538 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9539 Debian
</a
> testing and unstable at the moment. The only problem I
9540 have with it is how it handle errors. If something go wrong, its
9541 non-intuitive behaviour require me to go through some query work list
9542 and remove the failing query. Nothing big, but very annoying.
</p
>
9547 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9548 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9549 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9550 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9551 <description><p
>Here is a short update on my
<a
9552 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9553 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9554 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9555 not reporting the status for KDE, because the upgrade crashes when
9556 aptitude try because of missing conflicts
9557 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9558 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9560 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9561 complete list of the installed packages. Based on this I see these
9562 differences when I did a test run today. As usual, I do not really
9563 know what the correct set of packages would be, but thought it best to
9564 publish the difference.
</p
>
9566 <p
>Installed using apt-get, missing with aptitude
</p
>
9568 <blockquote
><p
>
9569 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9570 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9571 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9572 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9573 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9574 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9575 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9576 python-gtkmozembed svgalibg1 xserver-xephyr zip
9577 </p
></blockquote
>
9579 <p
>Installed using apt-get, removed with aptitude
</p
>
9581 <blockquote
><p
>
9582 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9583 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9584 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9585 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9586 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9587 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9588 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9589 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9590 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9591 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9592 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9593 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9594 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9595 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9596 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9597 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9598 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9599 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9600 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9601 mysql-common swfdec-gnome totem-gstreamer wodim
9602 </p
></blockquote
>
9604 <p
>Installed using aptitude, missing with apt-get
</p
>
9606 <blockquote
><p
>
9607 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9608 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9609 xserver-xorg-input-all xserver-xorg-input-evdev
9610 xserver-xorg-input-kbd xserver-xorg-input-mouse
9611 xserver-xorg-input-synaptics xserver-xorg-video-all
9612 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9613 xserver-xorg-video-chips xserver-xorg-video-cirrus
9614 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9615 xserver-xorg-video-glint xserver-xorg-video-i128
9616 xserver-xorg-video-i740 xserver-xorg-video-mach64
9617 xserver-xorg-video-mga xserver-xorg-video-neomagic
9618 xserver-xorg-video-nouveau xserver-xorg-video-nv
9619 xserver-xorg-video-r128 xserver-xorg-video-radeon
9620 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9621 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9622 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9623 xserver-xorg-video-sis xserver-xorg-video-sisusb
9624 xserver-xorg-video-tdfx xserver-xorg-video-tga
9625 xserver-xorg-video-trident xserver-xorg-video-tseng
9626 xserver-xorg-video-vesa xserver-xorg-video-vmware
9627 xserver-xorg-video-voodoo
9628 </p
></blockquote
>
9630 <p
>Installed using aptitude, removed with apt-get
</p
>
9632 <blockquote
><p
>
9633 deskbar-applet xserver-xorg xserver-xorg-core
9634 xserver-xorg-input-wacom xserver-xorg-video-intel
9635 xserver-xorg-video-openchrome
9636 </p
></blockquote
>
9638 <p
>I was told on IRC that the xorg-xserver package was
9639 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9640 in git
</a
> today to try to get apt-get to not remove xorg completely.
9641 No idea when it hits Squeeze, but when it does I hope it will reduce
9642 the difference somewhat.
9647 <title>LUMA, a very nice LDAP GUI
</title>
9648 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9649 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9650 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9651 <description><p
>The last few days I have been looking into the status of the LDAP
9652 directory in Debian Edu, and in the process I started to miss a GUI
9653 tool to browse the LDAP tree. The only one I was able to find in
9654 Debian/Squeeze and Lenny is
9655 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9656 be a great tool to get a overview of the current LDAP directory
9657 populated by default in Skolelinux. Thanks to it, I have been able to
9658 find empty and obsolete subtrees, misplaced objects and duplicate
9659 objects. It will be installed by default in Debian/Squeeze. If you
9660 are working with LDAP, give it a go. :)
</p
>
9662 <p
>I did notice one problem with it I have not had time to report to
9663 the BTS yet. There is no .desktop file in the package, so the tool do
9664 not show up in the Gnome and KDE menus, but only deep down in in the
9665 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9668 <p
>I have not yet been able to get it to modify the tree yet. I would
9669 like to move objects and remove subtrees directly in the GUI, but have
9670 not found a way to do that with LUMA yet. So in the mean time, I use
9671 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9673 <p
>If you have tips on other GUI tools for LDAP that might be useful
9674 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9676 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9677 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9678 useful GUI alternative. It seem like a good tool, but is unmaintained
9679 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9680 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9685 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9686 <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>
9687 <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>
9688 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9689 <description><p
>A while back, I
9690 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9691 about the fact
</a
> that it is not possible with the provided schemas
9692 for storing DNS and DHCP information in LDAP to combine the two sets
9693 of information into one LDAP object representing a computer.
</p
>
9695 <p
>In the mean time, I discovered that a simple fix would be to make
9696 the dhcpHost object class auxiliary, to allow it to be combined with
9697 the dNSDomain object class, and thus forming one object for one
9698 computer when storing both DHCP and DNS information in LDAP.
</p
>
9700 <p
>If I understand this correctly, it is not safe to do this change
9701 without also changing the assigned number for the object class, and I
9702 do not know enough about LDAP schema design to do that properly for
9703 Debian Edu.
</p
>
9705 <p
>Anyway, for future reference, this is how I believe we could change
9707 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9708 schema
</a
> to solve at least part of the problem with the LDAP schemas
9709 available today from IETF.
</p
>
9712 --- dhcp.schema (revision
65192)
9713 +++ dhcp.schema (working copy)
9715 objectclass (
2.16.840.1.113719.1.203.6.6
9716 NAME
'dhcpHost
'
9717 DESC
'This represents information about a particular client
'
9721 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9722 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9725 <p
>I very much welcome clues on how to do this properly for Debian
9726 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9727 package, and should thus be free to rewrite it as we see fit.
</p
>
9729 <p
>If you want to help out with implementing this for Debian Edu,
9730 please contact us on debian-edu@lists.debian.org.
</p
>
9735 <title>Calling tasksel like the installer, while still getting useful output
</title>
9736 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9737 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9738 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9739 <description><p
>A few times I have had the need to simulate the way tasksel
9740 installs packages during the normal debian-installer run. Until now,
9741 I have ended up letting tasksel do the work, with the annoying problem
9742 of not getting any feedback at all when something fails (like a
9743 conffile question from dpkg or a download that fails), using code like
9746 <blockquote
><pre
>
9747 export DEBIAN_FRONTEND=noninteractive
9748 tasksel --new-install
9749 </pre
></blockquote
>
9751 This would invoke tasksel, let its automatic task selection pick the
9752 tasks to install, and continue to install the requested tasks without
9753 any output what so ever.
9755 Recently I revisited this problem while working on the automatic
9756 package upgrade testing, because tasksel would some times hang without
9757 any useful feedback, and I want to see what is going on when it
9758 happen. Then it occured to me, I can parse the output from tasksel
9759 when asked to run in test mode, and use that aptitude command line
9760 printed by tasksel then to simulate the tasksel run. I ended up using
9763 <blockquote
><pre
>
9764 export DEBIAN_FRONTEND=noninteractive
9765 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9767 </pre
></blockquote
>
9769 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9770 --without-recommends -o APT::Install-Recommends=no -y install
9771 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9772 ~pimportant
</tt
>", which will install the gnome desktop task, the
9773 laptop task and all packages with priority standard , required and
9774 important, just like tasksel would have done it during
9775 installation.
</p
>
9777 <p
>A better approach is probably to extend tasksel to be able to
9778 install packages without using debconf-apt-progress, for use cases
9779 like this.
</p
>
9784 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9785 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9786 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9787 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9788 <description><p
>My
9789 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9790 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9791 finally made the upgrade logs available from
9792 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9793 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9794 apt and aptitude, and found their differences interesting. This time
9795 I will only focus on their removal plans.
</p
>
9797 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9798 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9799 surprising part is that it want to remove xorg and all
9800 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9801 sure why. When asking aptitude to do the same, it want to remove
129
9802 packages, but most of them are library packages I suspect are no
9803 longer needed. Both of them want to remove bluetooth packages, which
9804 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9806 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9807 which seem like a bad idea and xorg the same way as with Gnome. Asking
9808 aptitude for the same, it wants to remove
192 packages, none which are
9809 too surprising.
</p
>
9811 <p
>I guess the removal of xorg during upgrades should be investigated
9812 and avoided, and perhaps others as well. Here are the complete list
9813 of planned removals. The complete logs is available from the URL
9814 above. Note if you want to repeat these tests, that the upgrade test
9815 for kde+apt-get hung in the tasksel setup because of dpkg asking
9816 conffile questions. No idea why. I worked around it by using
9817 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9820 <p
><b
>apt-get gnome
72</b
>
9821 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9822 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9823 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9824 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9825 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9826 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9827 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9828 xserver-xorg-input-kbd xserver-xorg-input-mouse
9829 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9830 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9831 xserver-xorg-video-ati xserver-xorg-video-chips
9832 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9833 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9834 xserver-xorg-video-glint xserver-xorg-video-i128
9835 xserver-xorg-video-i740 xserver-xorg-video-imstt
9836 xserver-xorg-video-intel xserver-xorg-video-mach64
9837 xserver-xorg-video-mga xserver-xorg-video-neomagic
9838 xserver-xorg-video-nsc xserver-xorg-video-nv
9839 xserver-xorg-video-openchrome xserver-xorg-video-r128
9840 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9841 xserver-xorg-video-rendition xserver-xorg-video-s3
9842 xserver-xorg-video-s3virge xserver-xorg-video-savage
9843 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9844 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9845 xserver-xorg-video-tga xserver-xorg-video-trident
9846 xserver-xorg-video-tseng xserver-xorg-video-v4l
9847 xserver-xorg-video-vesa xserver-xorg-video-vga
9848 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9849 xulrunner-
1.9-gnome-support
</p
>
9851 <p
><b
>aptitude gnome
129</b
>
9853 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9854 djvulibre-desktop finger gnome-app-install gnome-mount
9855 gnome-network-admin gnome-spell gnome-vfs-obexftp
9856 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9857 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9858 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9859 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9860 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9861 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9862 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9863 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9864 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9865 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9866 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9867 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9868 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9869 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9870 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9871 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9872 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9873 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9874 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9875 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9876 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9877 openoffice.org-writer2latex openssl-blacklist p7zip
9878 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9879 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9880 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9881 swfdec-mozilla totem-gstreamer update-manager wodim
9882 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9883 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9886 <p
><b
>apt-get kde
82</b
>
9888 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9889 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9890 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9891 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9892 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9893 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9894 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9895 xserver-xorg-input-kbd xserver-xorg-input-mouse
9896 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9897 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9898 xserver-xorg-video-ati xserver-xorg-video-chips
9899 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9900 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9901 xserver-xorg-video-glint xserver-xorg-video-i128
9902 xserver-xorg-video-i740 xserver-xorg-video-imstt
9903 xserver-xorg-video-intel xserver-xorg-video-mach64
9904 xserver-xorg-video-mga xserver-xorg-video-neomagic
9905 xserver-xorg-video-nsc xserver-xorg-video-nv
9906 xserver-xorg-video-openchrome xserver-xorg-video-r128
9907 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9908 xserver-xorg-video-rendition xserver-xorg-video-s3
9909 xserver-xorg-video-s3virge xserver-xorg-video-savage
9910 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9911 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9912 xserver-xorg-video-tga xserver-xorg-video-trident
9913 xserver-xorg-video-tseng xserver-xorg-video-v4l
9914 xserver-xorg-video-vesa xserver-xorg-video-vga
9915 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9917 <p
><b
>aptitude kde
192</b
>
9918 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9919 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9920 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9921 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9922 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9923 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9924 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9925 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9926 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9927 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9928 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9929 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9930 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9931 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9932 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9933 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9934 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9935 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9936 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9937 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9938 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9939 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9940 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9941 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9942 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9943 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9944 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9945 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9946 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9947 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9948 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9949 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9950 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9951 texlive-common texlive-doc-base texlive-fonts-recommended
9952 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9953 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9954 xulrunner-
1.9</p
>
9960 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9961 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9962 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9963 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9964 <description><p
>The last few days I have done some upgrade testing in Debian, to
9965 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9966 have been discovered and reported in the process
9967 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9968 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9969 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9970 kdebase-workspace-data), and to get a more regular testing going on, I
9971 am working on a script to automate the test.
</p
>
9973 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9974 Gnome or KDE desktop installation inside the chroot before upgrading
9975 it. To ensure no services are started in the chroot, a policy-rc.d
9976 script is inserted. To make sure tasksel believe it is to install a
9977 desktop on a laptop, the tasksel tests are replaced in the chroot
9978 (only acceptable because this is a throw-away chroot).
</p
>
9980 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9981 currently always fail because udev refuses to upgrade with the kernel
9982 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9983 is created. The bug report
9984 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9985 this problem do not trigger in a chroot, but I touch the file anyway
9986 to make sure the upgrade go well. Testing on virtual and real
9987 hardware have failed me because of udev so far, and creating this file
9988 do the trick in such settings anyway. This is a
9989 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9990 issue
</a
> and the current udev behaviour is intended by the udev
9991 maintainer because he lack the resources to rewrite udev to keep
9992 working with old kernels or something like that. I really wish the
9993 udev upstream would keep udev backwards compatible, to avoid such
9994 upgrade problem, but given that they fail to do so, I guess
9995 documenting the way out of this mess is the best option we got for
9996 Debian Squeeze.
</p
>
9998 <p
>Anyway, back to the task at hand, testing upgrades. This test
9999 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10002 <blockquote
><pre
>
10006 if [
"$
1" ] ; then
10015 exec
&lt; /dev/null
10017 mirror=http://ftp.skolelinux.org/debian
10018 tmpdir=chroot-$from-upgrade-$to-$desktop
10020 debootstrap $from $tmpdir $mirror
10021 chroot $tmpdir aptitude update
10022 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10026 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10028 umount $tmpdir/proc
10030 mount -t proc proc $tmpdir/proc
10031 # Make sure proc is unmounted also on failure
10032 trap exit_cleanup EXIT INT
10034 chroot $tmpdir aptitude -y install debconf-utils
10036 # Make sure tasksel autoselection trigger. It need the test scripts
10037 # to return the correct answers.
10038 echo tasksel tasksel/desktop multiselect $desktop | \
10039 chroot $tmpdir debconf-set-selections
10041 # Include the desktop and laptop task
10042 for test in desktop laptop ; do
10043 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10047 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10050 DEBIAN_FRONTEND=noninteractive
10051 DEBIAN_PRIORITY=critical
10052 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10053 chroot $tmpdir tasksel --new-install
10055 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10056 chroot $tmpdir aptitude update
10057 touch $tmpdir/etc/udev/kernel-upgrade
10058 chroot $tmpdir aptitude -y dist-upgrade
10060 </pre
></blockquote
>
10062 <p
>I suspect it would be useful to test upgrades with both apt-get and
10063 with aptitude, but I have not had time to look at how they behave
10064 differently so far. I hope to get a cron job running to do the test
10065 regularly and post the result on the web. The Gnome upgrade currently
10066 work, while the KDE upgrade fail because of the bug in
10067 kdebase-workspace-data
</p
>
10069 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10070 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10071 post, so I will refrain from trying. I can report that for Gnome,
10072 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10073 remove and
1 not upgraded and
1024MB need to be downloaded while for
10074 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10075 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10077 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10078 is able to migrate to dependency based boot sequencing and parallel
10079 booting without a hitch. Was unsure if there were still bugs with
10080 packages failing to clean up their obsolete init.d script during
10081 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10082 packages.
</p
>
10087 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10088 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10090 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10091 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10092 scripts to migrate (some of) their operations to upstart job while
10093 keeping the init.d for hurd and kfreebsd. The packages with such
10094 needs will need a way to get their init.d scripts to behave
10095 differently when used with sysvinit and with upstart. Because of
10096 this, I had a look at the environment variables set when a init.d
10097 script is running under upstart, and when it is not.
</p
>
10099 <p
>With upstart, I notice these environment variables are set when a
10100 script is started from rcS.d/ (ignoring some irrelevant ones like
10101 COLUMNS):
</p
>
10103 <blockquote
><pre
>
10109 UPSTART_EVENTS=startup
10111 UPSTART_JOB=rc-sysinit
10112 </pre
></blockquote
>
10114 <p
>With sysvinit, these environment variables are set for the same
10117 <blockquote
><pre
>
10118 INIT_VERSION=sysvinit-
2.88
10123 </pre
></blockquote
>
10125 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10126 sysvinit are not set by upstart. Not sure if it is intentional or not
10127 to not be compatible with sysvinit in this regard.
</p
>
10129 <p
>For scripts needing to behave differently when upstart is used,
10130 looking for the UPSTART_JOB environment variable seem to be a good
10136 <title>A manual for standards wars...
</title>
10137 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10138 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10139 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10140 <description><p
>Via the
10141 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10142 of Rob Weir
</a
> I came across the very interesting essay named
10143 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10144 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10145 following the standards wars of today.
</p
>
10150 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10151 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10153 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10154 <description><p
>When using sitesummary at a site to track machines, it is possible
10155 to get a list of the machine types in use thanks to the DMI
10156 information extracted from each machine. The script to do so is
10157 included in the sitesummary package, and here is example output from
10158 the Skolelinux build servers:
</p
>
10160 <blockquote
><pre
>
10161 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10163 Dell Computer Corporation
1
10166 eserver xSeries
345 -[
8670M1X]-
1
10170 </pre
></blockquote
>
10172 <p
>The quality of the report depend on the quality of the DMI tables
10173 provided in each machine. Here there are Intel machines without model
10174 information listed with Intel as vendor and no model, and virtual Xen
10175 machines listed as [no-dmi-info]. One can add -l as a command line
10176 option to list the individual machines.
</p
>
10178 <p
>A larger list is
10179 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10180 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10181 provide the basic sitesummary report publicly. In their report there
10182 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10183 their machines, and as sitesummary is available in both distributions,
10184 it is trivial to get all of them to report to the same central
10185 collector.
</p
>
10190 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10191 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10192 <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>
10193 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10194 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10195 start at boot when an NVidia video card is used is handled. The
10196 problem seem to be that the nvidia X.org driver uses a long time to
10197 initialize, and this duration is longer than kdm is configured to
10200 <p
>I came across two bugs related to this issue,
10201 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10202 against initscripts and passed on to nvidia-glx when it became obvious
10203 that the nvidia drivers were involved, and
10204 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10205 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10207 <p
>To me, it seem that no-one is interested in actually solving the
10208 problem nvidia video card owners experience and make sure the Debian
10209 distribution work out of the box for these users. The nvidia driver
10210 maintainers expect kdm to be set up to wait longer, while kdm expect
10211 the nvidia driver maintainers to fix the driver to start faster, and
10212 while they wait for each other I guess the users end up switching to a
10213 distribution that work for them. I have no idea what the solution is,
10214 but I am pretty sure that waiting for each other is not it.
</p
>
10216 <p
>I wonder why we end up handling bugs this way.
</p
>
10221 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10222 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10224 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10225 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10226 The feature seem to hold up pretty well, but three fairly serious
10227 issues are known and should be solved:
10229 <p
><ul
>
10231 <li
>The wicd package seen to
10232 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10233 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10234 parallel booting is enabled. No idea why, but the wicd maintainer
10235 seem to be on the case.
</li
>
10237 <li
>The nvidia X driver seem to
10238 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10239 triggered more easily when parallel booting is in effect. The
10240 maintainer is on the case.
</li
>
10242 <li
>The sysv-rc package fail to properly enable dependency based boot
10243 sequencing (the shutdown is broken) when old file-rc users
10244 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10245 sysv-rc. One way to solve it would be for file-rc to create
10246 /etc/init.d/.legacy-bootordering, and another is to try to make
10247 sysv-rc more robust. Will investigate some more and probably upload a
10248 workaround in sysv-rc to help those trying to move from file-rc to
10249 sysv-rc get a working shutdown.
</li
>
10251 </ul
></p
>
10253 <p
>All in all not many surprising issues, and all of them seem
10254 solvable before Squeeze is released. In addition to these there are
10255 some packages with bugs in their dependencies and run level settings,
10256 which I expect will be fixed in a reasonable time span.
</p
>
10258 <p
>If you report any problems with dependencies in init.d scripts to
10259 the BTS, please usertag the report to get it to show up at
10260 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10261 list of usertagged bugs related to this
</a
>.
</p
>
10263 <p
>Update: Correct bug number to file-rc issue.
</p
>
10268 <title>More flexible firmware handling in debian-installer
</title>
10269 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10271 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10272 <description><p
>After a long break from debian-installer development, I finally
10273 found time today to return to the project. Having to spend less time
10274 working dependency based boot in debian, as it is almost complete now,
10275 definitely helped freeing some time.
</p
>
10277 <p
>A while back, I ran into a problem while working on Debian Edu. We
10278 include some firmware packages on the Debian Edu CDs, those needed to
10279 get disk and network controllers working. Without having these
10280 firmware packages available during installation, it is impossible to
10281 install Debian Edu on the given machine, and because our target group
10282 are non-technical people, asking them to provide firmware packages on
10283 an external medium is a support pain. Initially, I expected it to be
10284 enough to include the firmware packages on the CD to get
10285 debian-installer to find and use them. This proved to be wrong.
10286 Next, I hoped it was enough to symlink the relevant firmware packages
10287 to some useful location on the CD (tried /cdrom/ and
10288 /cdrom/firmware/). This also proved to not work, and at this point I
10289 found time to look at the debian-installer code to figure out what was
10290 going to work.
</p
>
10292 <p
>The firmware loading code is in the hw-detect package, and a closer
10293 look revealed that it would only look for firmware packages outside
10294 the installation media, so the CD was never checked for firmware
10295 packages. It would only check USB sticks, floppies and other
10296 "external
" media devices. Today I changed it to also look in the
10297 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10298 solve the problem I ran into with Debian edu. I also changed it to
10299 look in /firmware/, to make sure the installer also find firmware
10300 provided in the initrd when booting the installer via PXE, to allow us
10301 to provide the same feature in the PXE setup included in Debian
10304 <p
>To make sure firmware deb packages with a license questions are not
10305 activated without asking if the license is accepted, I extended
10306 hw-detect to look for preinst scripts in the firmware packages, and
10307 run these before activating the firmware during installation. The
10308 license question is asked using debconf in the preinst, so this should
10309 solve the issue for the firmware packages I have looked at so far.
</p
>
10311 <p
>If you want to discuss the details of these features, please
10312 contact us on debian-boot@lists.debian.org.
</p
>
10317 <title>Parallellized boot is now the default in Debian/unstable
</title>
10318 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10320 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10321 <description><p
>Since this evening, parallel booting is the default in
10322 Debian/unstable for machines using dependency based boot sequencing.
10323 Apparently the testing of concurrent booting has been wider than
10324 expected, if I am to believe the
10325 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10326 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10327 with the feature this weekend, to give us some time to detect any
10328 remaining problems before Squeeze is frozen. If serious problems are
10329 detected, it is simple to change the default back to sequential boot.
10330 The upload of the new sysvinit package also activate a new upstream
10333 More information about
10334 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10335 based boot sequencing
</a
> is available from the Debian wiki. It is
10336 currently possible to disable parallel booting when one run into
10337 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10339 <blockquote
><pre
>
10341 </pre
></blockquote
>
10343 <p
>If you report any problems with dependencies in init.d scripts to
10344 the BTS, please usertag the report to get it to show up at
10345 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10346 list of usertagged bugs related to this
</a
>.
</p
>
10351 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10352 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10353 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10354 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10355 <description><p
>In the recent Debian Edu versions, the
10356 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10357 system
</a
> is used to keep track of the machines in the school
10358 network. Each machine will automatically report its status to the
10359 central server after boot and once per night. The network setup is
10360 also reported, and using this information it is possible to get the
10361 MAC address of all network interfaces in the machines. This is useful
10362 to update the DHCP configuration.
</p
>
10364 <p
>To give some idea how to use sitesummary, here is a one-liner to
10365 ist all MAC addresses of all machines reporting to sitesummary. Run
10366 this on the collector host:
</p
>
10368 <blockquote
><pre
>
10369 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10370 </pre
></blockquote
>
10372 <p
>This will list all MAC addresses assosiated with all machine, one
10373 line per machine and with space between the MAC addresses.
</p
>
10375 <p
>To allow system administrators easier job at adding static DHCP
10376 addresses for hosts, it would be possible to extend this to fetch
10377 machine information from sitesummary and update the DHCP and DNS
10378 tables in LDAP using this information. Such tool is unfortunately not
10379 written yet.
</p
>
10384 <title>systemd, an interesting alternative to upstart
</title>
10385 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10386 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10387 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10388 <description><p
>The last few days a new boot system called
10389 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10391 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10393 to the free software world. I have not yet had time to play around
10394 with it, but it seem to be a very interesting alternative to
10395 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10396 a good alternative for Debian when we are able to switch to an event
10397 based boot system. Tollef is
10398 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10399 systemd into Debian, and I look forward to seeing how well it work. I
10400 like the fact that systemd handles init.d scripts with dependency
10401 information natively, allowing them to run in parallel where upstart
10402 at the moment do not.
</p
>
10404 <p
>Unfortunately do systemd have the same problem as upstart regarding
10405 platform support. It only work on recent Linux kernels, and also need
10406 some new kernel features enabled to function properly. This means
10407 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10408 system. Not sure how that will be handled if systemd proves to be the
10409 way forward.
</p
>
10411 <p
>In the mean time, based on the
10412 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10413 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10414 decided to enable full parallel booting as the default in Debian as
10415 soon as possible (probably this weekend or early next week), to see if
10416 there are any remaining serious bugs in the init.d dependencies. A
10417 new version of the sysvinit package implementing this change is
10418 already in experimental. If all go well, Squeeze will be released
10419 with parallel booting enabled by default.
</p
>
10424 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10425 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10426 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10427 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10428 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10429 complete, so complete that it is actually possible to run all the
10430 init.d scripts in parallell based on these dependencies. If you want
10431 to test your Squeeze system, make sure
10432 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10433 based boot sequencing
</a
> is enabled, and add this line to
10434 /etc/default/rcS:
</p
>
10436 <blockquote
><pre
>
10437 CONCURRENCY=makefile
10438 </pre
></blockquote
>
10440 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10441 scripts in parallel using the dependency information stored in
10442 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10443 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10444 to try to start the kdm and gdm scripts as early as possible, and will
10445 start the facilities required by kdm or gdm as early as possible to
10446 make this happen.
</p
>
10448 <p
>Give it a try, and see if you like the result. If some services
10449 fail to start properly, it is most likely because they have incomplete
10450 init.d script dependencies in their startup script (or some of their
10451 dependent scripts have incomplete dependencies). Report bugs and get
10452 the package maintainers to fix it. :)
</p
>
10454 <p
>Running scripts in parallel could be the default in Debian when we
10455 manage to get the init.d script dependencies complete and correct. I
10456 expect we will get there in Squeeze+
1, if we get manage to test and
10457 fix the remaining issues.
</p
>
10459 <p
>If you report any problems with dependencies in init.d scripts to
10460 the BTS, please usertag the report to get it to show up at
10461 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10462 list of usertagged bugs related to this
</a
>.
</p
>
10467 <title>Debian has switched to dependency based boot sequencing
</title>
10468 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10469 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10470 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10471 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10472 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10473 have been migrated to using dependency based boot sequencing. This
10474 conclude work me and others have been doing for the last three days.
10475 It feels great to see this finally part of the default Debian
10476 installation. Now we just need to weed out the last few problems that
10477 are bound to show up, to get everything ready for Squeeze.
</p
>
10479 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10480 fixing the more fundamental problem of handing the event based
10481 non-predictable kernel in the early boot.
</p
>
10486 <title>Taking over sysvinit development
</title>
10487 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10489 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10490 <description><p
>After several years of frustration with the lack of activity from
10491 the existing sysvinit upstream developer, I decided a few weeks ago to
10492 take over the package and become the new upstream. The number of
10493 patches to track for the Debian package was becoming a burden, and the
10494 lack of synchronization between the distribution made it hard to keep
10495 the package up to date.
</p
>
10497 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10498 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10499 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10500 and Fedora), based on the patches currently in use in these
10501 distributions. We Debian maintainers plan to move to this tarball as
10502 the new upstream as soon as we find time to do the merge. Since the
10503 new tarball was created, we agreed with Werner at SuSe to make a new
10504 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10505 development there. The project is registered and currently waiting
10506 for approval by the Savannah administrators, and as soon as it is
10507 approved, we will import the old versions from svn and continue
10508 working on the future release.
</p
>
10510 <p
>It is a bit ironic that this is done now, when some of the involved
10511 distributions are moving to upstart as a syvinit replacement.
</p
>
10516 <title>Debian boots quicker and quicker
</title>
10517 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10518 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10519 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10520 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10521 people involved in the boot system on Debian and Ubuntu, to see if we
10522 could find more ways to speed up the boot system. This was an Ubuntu
10524 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10525 gathering
</a
>. It was quite productive. We also discussed the future
10526 of boot systems, and ways to handle the increasing number of boot
10527 issues introduced by the Linux kernel becoming more and more
10528 asynchronous and event base. The Ubuntu approach using udev and
10529 upstart might be a good way forward. Time will show.
</p
>
10531 <p
>Anyway, there are a few ways at the moment to speed up the boot
10532 process in Debian. All of these should be applied to get a quick
10537 <li
>Use dash as /bin/sh.
</li
>
10539 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10540 clock is in UTC.
</li
>
10542 <li
>Install and activate the insserv package to enable
10543 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10544 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10548 These points are based on the Google summer of code work done by
10549 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10550 Villegas
</a
>.
10552 <p
>Support for makefile-style concurrency during boot was uploaded to
10553 unstable yesterday. When we tested it, we were able to cut
6 seconds
10554 from the boot sequence. It depend on very correct dependency
10555 declaration in all init.d scripts, so I expect us to find edge cases
10556 where the dependences in some scripts are slightly wrong when we start
10557 using this.
</p
>
10559 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10560 introduced by Raphael Geissert today, one that could affect the
10561 startup speed as well. Instead of starting some scripts concurrently
10562 from rcS.d/ and another set of scripts from rc2.d/, it would be
10563 possible to run a of them in the same process. A quick way to test
10564 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10565 insserv
'. Will need to test if that work. :)
</p
>
10570 <title>BSAs påstander om piratkopiering møter motstand
</title>
10571 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10572 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10573 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10574 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10575 programvareselskapene som Microsoft og Apple, publisert en rapport der
10576 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10577 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10579 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10580 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10581 dagene. Et spesielt interessant kommentar fra Sverige,
10582 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10583 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10586 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10587 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10588 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10589 exakta
", säger BSAs Sverigechef John Hugosson.
10590 </blockquote
>
10592 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10593 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10594 piracy figures need a shot of reality
</a
> og
<a
10595 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10596 Copyright Treaty Work?
</a
></p
>
10598 <p
>Fant lenkene via
<a
10599 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10600 på Slashdot
</a
>.
</p
>
10605 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10606 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10607 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10608 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10609 <description><p
>Kom over
10610 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10611 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10612 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10613 jobber til daglig. En rask opptelling forteller meg at vi har
490
10614 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10615 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10616 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10621 <title>Kryptert harddisk - naturligvis
</title>
10622 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10623 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10624 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10625 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10626 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10627 når en tar tap av arbeidstid, fortrolige dokumenter,
10628 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10629 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10630 til at jeg har kryptert harddisken på både kontormaskinen og min
10631 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10632 komme på avveie, den første informasjon relatert til jobben min ved
10633 Universitetet i Oslo, og den andre relatert til blant annet
10634 foreningsarbeide. Kryptering av diskene gjør at det er lite
10635 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10636 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10637 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10638 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10639 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10640 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10641 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10642 det er gjort slik jeg gjør det er minimale, og gevinstene er
10643 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10644 maskinen reinstalleres og alt er tapt.
</p
>
10646 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10647 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10648 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10649 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10650 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10651 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10652 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10653 betydelige.
</p
>
10658 <title>Two projects that have improved the quality of free software a lot
</title>
10659 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10660 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10661 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10662 <description><p
>There are two software projects that have had huge influence on the
10663 quality of free software, and I wanted to mention both in case someone
10664 do not yet know them.
</p
>
10666 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10667 tool to detect and expose errors in the memory handling of programs.
10668 It is easy to use, all one need to do is to run
'valgrind program
',
10669 and it will report any problems on stdout. It is even better if the
10670 program include debug information. With debug information, it is able
10671 to report the source file name and line number where the problem
10672 occurs. It can report things like
'reading past memory block in file
10673 X line N, the memory block was allocated in file Y, line M
', and
10674 'using uninitialised value in control logic
'. This tool has made it
10675 trivial to investigate reproducible crash bugs in programs, and have
10676 reduced the number of this kind of bugs in free software a lot.
10678 <p
>The second one is
10679 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10680 a source code checker. It is able to process the source of a program
10681 and find problems in the logic without running the program. It
10682 started out as the Stanford Checker and became well known when it was
10683 used to find bugs in the Linux kernel. It is now a commercial tool
10684 and the company behind it is running
10685 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10686 free software community, where a lot of free software projects get
10687 their source checked for free. Several thousand defects have been
10688 found and fixed so far. It can find errors like
'lock L taken in file
10689 X line N is never released if exiting in line M
', or
'the code in file
10690 Y lines O to P can never be executed
'. The projects included in the
10691 community service project have managed to get rid of a lot of
10692 reliability problems thanks to Coverity.
</p
>
10694 <p
>I believe tools like this, that are able to automatically find
10695 errors in the source, are vital to improve the quality of software and
10696 make sure we can get rid of the crashing and failing software we are
10697 surrounded by today.
</p
>
10702 <title>No patch is not better than a useless patch
</title>
10703 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10704 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10705 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10706 <description><p
>Julien Blache
10707 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10708 patch is better than a useless patch
</a
>. I completely disagree, as a
10709 patch allow one to discuss a concrete and proposed solution, and also
10710 prove that the issue at hand is important enough for someone to spent
10711 time on fixing it. No patch do not provide any of these positive
10712 properties.
</p
>
10717 <title>Standardize on protocols and formats, not vendors and applications
</title>
10718 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10719 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10720 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10721 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10722 very good one to form a long lived computer infrastructure. It is the
10723 simple one, lost by many in todays computer industry: Standardize on
10724 open network protocols and open exchange/storage formats, not applications.
10725 Applications come and go, while protocols and files tend to stay, and
10726 thus one want to make it easy to change application and vendor, while
10727 avoiding conversion costs and locking users to a specific platform or
10728 application.
</p
>
10730 <p
>This approach make it possible to replace the client applications
10731 independently of the server applications. One can even allow users to
10732 use several different applications as long as they handle the selected
10733 protocol and format. In the normal case, only one client application
10734 is recommended and users only get help if they choose to use this
10735 application, but those that want to deviate from the easy path are not
10736 blocked from doing so.
</p
>
10738 <p
>It also allow us to replace the server side without forcing the
10739 users to replace their applications, and thus allow us to select the
10740 best server implementation at any moment, when scale and resouce
10741 requirements change.
</p
>
10743 <p
>I strongly recommend standardizing - on open network protocols and
10744 open formats, but I would never recommend standardizing on a single
10745 application that do not use open network protocol or open formats.
</p
>
10750 <title>Returning from Skolelinux developer gathering
</title>
10751 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10752 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10753 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10754 <description><p
>I
'm sitting on the train going home from this weekends Debian
10755 Edu/Skolelinux development gathering. I got a bit done tuning the
10756 desktop, and looked into the dynamic service location protocol
10757 implementation avahi. It look like it could be useful for us. Almost
10758 30 people participated, and I believe it was a great environment to
10759 get to know the Skolelinux system. Walter Bender, involved in the
10760 development of the Sugar educational platform, presented his stuff and
10761 also helped me improve my OLPC installation. He also showed me that
10762 his Turtle Art application can be used in standalone mode, and we
10763 agreed that I would help getting it packaged for Debian. As a
10764 standalone application it would be great for Debian Edu. We also
10765 tried to get the video conferencing working with two OLPCs, but that
10766 proved to be too hard for us. The application seem to need more work
10767 before it is ready for me. I look forward to getting home and relax
10773 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10774 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10775 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10776 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10777 <description><p
>The state of standardized LDAP schemas on Linux is far from
10778 optimal. There is RFC
2307 documenting one way to store NIS maps in
10779 LDAP, and a modified version of this normally called RFC
2307bis, with
10780 some modifications to be compatible with Active Directory. The RFC
10781 specification handle the content of a lot of system databases, but do
10782 not handle DNS zones and DHCP configuration.
</p
>
10784 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10785 we would like to store information about users, SMB clients/hosts,
10786 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10787 and LTSP configuration in LDAP. These objects have a lot in common,
10788 but with the current LDAP schemas it is not possible to have one
10789 object per entity. For example, one need to have at least three LDAP
10790 objects for a given computer, one with the SMB related stuff, one with
10791 DNS information and another with DHCP information. The schemas
10792 provided for DNS and DHCP are impossible to combine into one LDAP
10793 object. In addition, it is impossible to implement quick queries for
10794 netgroup membership, because of the way NIS triples are implemented.
10795 It just do not scale. I believe it is time for a few RFC
10796 specifications to cleam up this mess.
</p
>
10798 <p
>I would like to have one LDAP object representing each computer in
10799 the network, and this object can then keep the SMB (ie host key), DHCP
10800 (mac address/name) and DNS (name/IP address) settings in one place.
10801 It need to be efficently stored to make sure it scale well.
</p
>
10803 <p
>I would also like to have a quick way to map from a user or
10804 computer and to the net group this user or computer is a member.
</p
>
10806 <p
>Active Directory have done a better job than unix heads like myself
10807 in this regard, and the unix side need to catch up. Time to start a
10808 new IETF work group?
</p
>
10813 <title>Endelig er Debian Lenny gitt ut
</title>
10814 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10815 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10816 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10817 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10818 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10819 Et langt steg videre for Debian-prosjektet, og en rekke nye
10820 programpakker blir nå tilgjengelig for de av oss som bruker den
10821 stabile utgaven av Debian. Neste steg er nå å få
10822 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10823 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10824 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10825 slippes løs på skolene. Takk til alle debian-utviklerne som har
10826 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10827 bootsekvens tilgjengelig i stabil utgave, vha pakken
10828 <tt
>insserv
</tt
>.
</p
>
10833 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10834 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10835 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10836 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10837 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10838 Oslo. Most of Saturday was used for the general assemly for the
10839 member organization, but the rest of the weekend I used to tune the
10840 LTSP installation. LTSP now work out of the box on the
10-network.
10841 Acer Aspire One proved to be a very nice thin client, with both
10842 screen, mouse and keybard in a small box. Was working on getting the
10843 diskless workstation setup configured out of the box, but did not
10844 finish it before the weekend was up.
</p
>
10846 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10847 the Brazilian group, so that will have to wait for the next
10848 development gathering. Would love to have the Debian Edu installer
10849 automatically detect and configure a multiseat setup when it find one
10850 of these cards.
</p
>
10855 <title>The sorry state of multimedia browser plugins in Debian
</title>
10856 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10857 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10858 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10859 <description><p
>Recently I have spent some time evaluating the multimedia browser
10860 plugins available in Debian Lenny, to see which one we should use by
10861 default in Debian Edu. We need an embedded video playing plugin with
10862 control buttons to pause or stop the video, and capable of streaming
10863 all the multimedia content available on the web. The test results and
10864 notes are available on
10865 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10866 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10867 fill this need. My personal video player favorite, VLC, has a really
10868 bad plugin which fail on a lot of the test pages. A lot of the MIME
10869 types I would expect to work with any free software player (like
10870 video/ogg), just do not work. And simple formats like the
10871 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10872 totem and vlc plugins. I hope the situation will improve soon. No
10873 wonder sites use the proprietary Adobe flash to play video.
</p
>
10875 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10876 be the only one fitting our needs. :/
</p
>