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>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
11 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
13 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
14 <description><p
>After several months of working and waiting, I am happy to report
15 that the nice and user friendly
3D printer slicer software Cura just
16 entered Debian Unstable. It consist of five packages,
17 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
18 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
19 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
20 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
21 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
22 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
23 two, uranium and cura, entered Unstable yesterday. This should make
24 it easier for Debian users to print on at least the Ultimaker class of
25 3D printers. My closest
3D printer is an Ultimaker
2+, so it will
26 make life easier for at least me. :)
</p
>
28 <p
>The work to make this happen was done by Gregor Riepl, and I was
29 happy to assist him in sponsoring the packages. With the introduction
30 of Cura, Debian is up to three
3D printer slicers at your service,
31 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
32 printer, give it a go. :)
</p
>
34 <p
>The
3D printer software is maintained by the
3D printer Debian
35 team, flocking together on the
36 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
38 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
39 IRC channel.
</p
>
41 <p
>The next step for Cura in Debian is to update the cura package to
42 version
3.0.3 and then update the entire set of packages to version
43 3.1.0 which showed up the last few days.
</p
>
48 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
49 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
50 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
51 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
52 <description><p
>At my nearby maker space,
53 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
54 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
55 on Windows and MacOS X than Linux, because the software involved had
56 to be manually compiled and set up on Linux while premade packages
57 worked out of the box on Windows and MacOS X. I found this annoying,
58 as the software involved,
59 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
60 and should be trivial to get up and running on Linux if someone took
61 the time to package it for the relevant distributions. I even found
62 <a href=
"https://bugs.debian.org/
706656">a request for adding into
63 Debian
</a
> from
2013, which had seem some activity over the years but
64 never resulted in the software showing up in Debian. So a few days
65 ago I offered my help to try to improve the situation.
</p
>
67 <p
>Now I am very happy to see that all the packages required by a
68 working Cura in Debian are uploaded into Debian and waiting in the NEW
69 queue for the ftpmasters to have a look. You can track the progress
71 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
72 status page for the
3D printer team
</a
>.
</p
>
74 <p
>The uploaded packages are a bit behind upstream, and was uploaded
75 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
76 queue
</a
> while we work up updating the packages to the latest
77 upstream version.
</p
>
79 <p
>On a related note, two competitors for Cura, which I found harder
80 to use and was unable to configure correctly for Ultimaker
2+ in the
81 short time I spent on it, are already in Debian. If you are looking
82 for
3D printer
"slicers
" and want something already available in
84 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
85 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
86 The latter is a fork of the former.
</p
>
88 <p
>As usual, if you use Bitcoin and want to show your support of my
89 activities, please send Bitcoin donations to my address
90 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
95 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
96 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
97 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
98 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
99 <description><p
>Every mobile phone announce its existence over radio to the nearby
100 mobile cell towers. And this radio chatter is available for anyone
101 with a radio receiver capable of receiving them. Details about the
102 mobile phones with very good accuracy is of course collected by the
103 phone companies, but this is not the topic of this blog post. The
104 mobile phone radio chatter make it possible to figure out when a cell
105 phone is nearby, as it include the SIM card ID (IMSI). By paying
106 attention over time, one can see when a phone arrive and when it leave
107 an area. I believe it would be nice to make this information more
108 available to the general public, to make more people aware of how
109 their phones are announcing their whereabouts to anyone that care to
112 <p
>I am very happy to report that we managed to get something
113 visualizing this information up and running for
114 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
115 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
116 library. The solution is based on the
117 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
118 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
119 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
120 Sone from the Computer Science department of the University of
121 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
122 IMSIs) as dots in a web browser graph, with lines to the dot
123 representing mobile base station it is talking to. It was working in
124 the lab yesterday, and was moved into place this morning.
</p
>
126 <p
>We set up a fairly powerful desktop machine using Debian
127 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
128 connected and visualize the visible cell phone towers using an
129 <a href=
"https://github.com/marlow925/hopglass
">English version of
130 Hopglass
</a
>. A fairly powerfull machine is needed as the
131 grgsm_livemon_headless processes from
132 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
133 the radio signal to data packages is quite CPU intensive.
</p
>
135 <p
>The frequencies to listen to, are identified using a slightly
136 patched scan-and-livemon (to set the --args values for each receiver),
137 and the Hopglass data is generated using the
138 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
139 in my meshviewer-output branch
</a
>. For some reason we could not get
140 more than four SDRs working. There is also a geographical map trying
141 to show the location of the base stations, but I believe their
142 coordinates are hardcoded to some random location in Germany, I
143 believe. The code should be replaced with code to look up location in
144 a text file, a sqlite database or one of the online databases
146 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
147 issue for the topic
</a
>.
149 <p
>If this sound interesting, visit the stand at the festival!
</p
>
154 <title>Easier recipe to observe the cell phones around you
</title>
155 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
156 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
157 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
158 <description><p
>A little more than a month ago I wrote
159 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
160 to observe the SIM card ID (aka IMSI number) of mobile phones talking
161 to nearby mobile phone base stations using Debian GNU/Linux and a
162 cheap USB software defined radio
</a
>, and thus being able to pinpoint
163 the location of people and equipment (like cars and trains) with an
164 accuracy of a few kilometer. Since then we have worked to make the
165 procedure even simpler, and it is now possible to do this without any
166 manual frequency tuning and without building your own packages.
</p
>
168 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
169 package is now included in Debian testing and unstable, and the
170 IMSI-catcher code no longer require root access to fetch and decode
171 the GSM data collected using gr-gsm.
</p
>
173 <p
>Here is an updated recipe, using packages built by Debian and a git
174 clone of two python scripts:
</p
>
178 <li
>Start with a Debian machine running the Buster version (aka
181 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
182 python-scapy
</tt
>' as root to install required packages.
</li
>
184 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
185 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
187 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
189 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
190 scan-and-livemon
</tt
>' to locate the frequency of nearby base
191 stations and start listening for GSM packages on one of them.
</li
>
193 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
194 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
198 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
199 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
200 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
201 work with RTL
8232 and other similar USB radio receivers you can get
203 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
204 from ebay
</a
>), so for now the solution is to scan using the RTL radio
205 and only use HackRF for fetching GSM data.
</p
>
207 <p
>As far as I can tell, a cell phone only show up on one of the
208 frequencies at the time, so if you are going to track and count every
209 cell phone around you, you need to listen to all the frequencies used.
210 To listen to several frequencies, use the --numrecv argument to
211 scan-and-livemon to use several receivers. Further, I am not sure if
212 phones using
3G or
4G will show as talking GSM to base stations, so
213 this approach might not see all phones around you. I typically see
214 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
216 <p
>I
've tried to run the scanner on a
217 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
218 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
219 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
220 stdout, I am told there it is caused by a buffer overflow between the
221 radio and GNU Radio, caused by the program being unable to read the
222 GSM data fast enough. If you see a stream of
'O
's from the terminal
223 where you started scan-and-livemon, you need a give the process more
224 CPU power. Perhaps someone are able to optimize the code to a point
225 where it become possible to set up RPi3 based GSM sniffers? I tried
226 using Raspbian instead of Debian, but there seem to be something wrong
227 with GNU Radio on raspbian, causing glibc to abort().
</p
>
232 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
233 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
234 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
235 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
236 <description><p
>On friday, I came across an interesting article in the Norwegian
237 web based ICT news magazine digi.no on
238 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
239 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
240 DVB-T software defined radios. The article refered to instructions
241 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
242 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
244 <p
>The instructions said to use Ubuntu, install pip using apt (to
245 bypass apt), use pip to install pybombs (to bypass both apt and pip),
246 and the ask pybombs to fetch and build everything you need from
247 scratch. I wanted to see if I could do the same on the most recent
248 Debian packages, but this did not work because pybombs tried to build
249 stuff that no longer build with the most recent openssl library or
250 some other version skew problem. While trying to get this recipe
251 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
252 and the only piece of software dependency missing in Debian was the
253 gr-gsm package. I also found out that the lead upstream developer of
254 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
255 Debian packages provided in an Ubuntu PPA repository. All I needed to
256 do was to dget the Debian source package and built it.
</p
>
258 <p
>The IMSI collector is a python script listening for packages on the
259 loopback network device and printing to the terminal some specific GSM
260 packages with IMSI numbers in them. The code is fairly short and easy
261 to understand. The reason this work is because gr-gsm include a tool
262 to read GSM data from a software defined radio like a DVB-T USB stick
263 and other software defined radios, decode them and inject them into a
264 network device on your Linux machine (using the loopback device by
265 default). This proved to work just fine, and I
've been testing the
266 collector for a few days now.
</p
>
268 <p
>The updated and simpler recipe is thus to
</p
>
272 <li
>start with a Debian machine running Stretch or newer,
</li
>
274 <li
>build and install the gr-gsm package available from
275 <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
>
277 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
279 <li
>run grgsm_livemon and adjust the frequency until the terminal
280 where it was started is filled with a stream of text (meaning you
281 found a GSM station).
</li
>
283 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
287 <p
>To make it even easier in the future to get this sniffer up and
288 running, I decided to package
289 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
290 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
291 #
871055</a
>), and the package was uploaded into the NEW queue today.
292 Luckily the gnuradio maintainer has promised to help me, as I do not
293 know much about gnuradio stuff yet.
</p
>
295 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
296 commercial tools like
297 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
298 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
299 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
300 Stingray
</a
>, but I hope the existance of cheap alternatives can make
301 more people realise how their whereabouts when carrying a cell phone
302 is easily tracked. Seeing the data flow on the screen, realizing that
303 I live close to a police station and knowing that the police is also
304 wearing cell phones, I wonder how hard it would be for criminals to
305 track the position of the police officers to discover when there are
306 police near by, or for foreign military forces to track the location
307 of the Norwegian military forces, or for anyone to track the location
308 of government officials...
</p
>
310 <p
>It is worth noting that the data reported by the IMSI-catcher
311 script mentioned above is only a fraction of the data broadcasted on
312 the GSM network. It will only collect one frequency at the time,
313 while a typical phone will be using several frequencies, and not all
314 phones will be using the frequencies tracked by the grgsm_livemod
315 program. Also, there is a lot of radio chatter being ignored by the
316 simple_IMSI-catcher script, which would be collected by extending the
317 parser code. I wonder if gr-gsm can be set up to listen to more than
318 one frequency?
</p
>
323 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
324 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
325 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
326 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
327 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
329 <p
>I finally received a copy of the Norwegian Bokmål edition of
330 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
331 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
332 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
333 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
334 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
335 price. The book is also available for download in electronic form as
336 PDF, EPUB and Mobipocket, as can be
337 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
338 as a web page
</a
>.
</p
>
340 <p
>This is the second book I publish (the first was the book
341 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
343 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
344 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
346 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
347 Bokmål
</a
>), and I am very excited to finally wrap up this
349 "<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
350 for Debian-administratoren
</a
>" will be well received.
</p
>
355 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
356 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
358 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
359 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
360 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
361 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
362 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
363 på om den fri oversetterløsningen
364 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
365 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
367 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
370 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
371 rolle og muligheter til å håndtere internasjonale utfordringer, som
372 for eksempel flykningekrisen.
</p
>
374 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
377 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
378 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
383 <p
>Dette oversetter Apertium slik:
</p
>
386 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
387 andre aktørar og høve til å handtera internasjonale utfordringar, som
388 til dømes *flykningekrisen.
</p
>
390 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
394 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
395 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
400 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
401 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
402 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
403 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
404 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
405 det er kanskje flisespikking. Det understreker vel bare at det alltid
406 trengs korrekturlesning etter automatisk oversettelse.
</p
>
411 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
412 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
414 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
415 <description><p
>Over the years, administrating thousand of NFS mounting linux
416 computers at the time, I often needed a way to detect if the machine
417 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
418 file or directory affected by the hang, the process (and possibly the
419 shell) will hang too. So you want to be able to detect this without
420 risking the detection process getting stuck too. It has not been
421 obvious how to do this. When the hang has lasted a while, it is
422 possible to find messages like these in dmesg:
</p
>
424 <p
><blockquote
>
425 nfs: server nfsserver not responding, still trying
426 <br
>nfs: server nfsserver OK
427 </blockquote
></p
>
429 <p
>It is hard to know if the hang is still going on, and it is hard to
430 be sure looking in dmesg is going to work. If there are lots of other
431 messages in dmesg the lines might have rotated out of site before they
432 are noticed.
</p
>
434 <p
>While reading through the nfs client implementation in linux kernel
435 code, I came across some statistics that seem to give a way to detect
436 it. The om_timeouts sunrpc value in the kernel will increase every
437 time the above log entry is inserted into dmesg. And after digging a
438 bit further, I discovered that this value show up in
439 /proc/self/mountstats on Linux.
</p
>
441 <p
>The mountstats content seem to be shared between files using the
442 same file system context, so it is enough to check one of the
443 mountstats files to get the state of the mount point for the machine.
444 I assume this will not show lazy umounted NFS points, nor NFS mount
445 points in a different process context (ie with a different filesystem
446 view), but that does not worry me.
</p
>
448 <p
>The content for a NFS mount point look similar to this:
</p
>
450 <p
><blockquote
><pre
>
452 device /dev/mapper/Debian-var mounted on /var with fstype ext3
453 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
454 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
456 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
457 sec: flavor=
1,pseudoflavor=
1
458 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
459 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
460 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
461 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
463 NULL:
0 0 0 0 0 0 0 0
464 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
465 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
466 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
467 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
468 READLINK:
125 125 0 20472 18620 0 1112 1118
469 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
470 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
471 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
472 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
473 SYMLINK:
903 903 0 233428 245488 6 5865 5917
474 MKNOD:
80 80 0 20148 21760 0 299 304
475 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
476 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
477 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
478 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
479 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
480 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
481 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
482 FSINFO:
2 2 0 232 328 0 1 1
483 PATHCONF:
1 1 0 116 140 0 0 0
484 COMMIT:
0 0 0 0 0 0 0 0
486 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
488 </pre
></blockquote
></p
>
490 <p
>The key number to look at is the third number in the per-op list.
491 It is the number of NFS timeouts experiences per file system
492 operation. Here
22 write timeouts and
5 access timeouts. If these
493 numbers are increasing, I believe the machine is experiencing NFS
494 hang. Unfortunately the timeout value do not start to increase right
495 away. The NFS operations need to time out first, and this can take a
496 while. The exact timeout value depend on the setup. For example the
497 defaults for TCP and UDP mount points are quite different, and the
498 timeout value is affected by the soft, hard, timeo and retrans NFS
499 mount options.
</p
>
501 <p
>The only way I have been able to get working on Debian and RedHat
502 Enterprise Linux for getting the timeout count is to peek in /proc/.
504 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
505 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
506 command can be used to get these timeout values. But this do not work
507 on Linux, as far as I can tell. I
508 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
509 but have not seen any replies yet.
</p
>
511 <p
>Is there a better way to figure out if a Linux NFS client is
512 experiencing NFS hangs? Is there a way to detect which processes are
513 affected? Is there a way to get the NFS mount going quickly once the
514 network problem causing the NFS hang has been cleared? I would very
515 much welcome some clues, as we regularly run into NFS hangs.
</p
>
520 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
521 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
522 <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>
523 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
524 <description><p
>For almost a year now, we have been working on making a Norwegian
525 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
526 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
527 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
528 we are working on the proof reading to ensure consistent language and
529 use of correct computer science terms. The plan is to make the book
530 available on paper, as well as in electronic form. For that to
531 happen, the proof reading must be completed and all the figures need
532 to be translated. If you want to help out, get in touch.
</p
>
534 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
536 fresh PDF edition
</a
> in A4 format (the final book will have smaller
537 pages) of the book created every morning is available for
538 proofreading. If you find any errors, please
539 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
540 Weblate and correct the error
</a
>. The
541 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
542 of the translation including figures
</a
> is a useful source for those
543 provide Norwegian bokmål screen shots and figures.
</p
>
548 <title>Unlimited randomness with the ChaosKey?
</title>
549 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
551 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
552 <description><p
>A few days ago I ordered a small batch of
553 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
554 USB dongle for generating entropy created by Bdale Garbee and Keith
555 Packard. Yesterday it arrived, and I am very happy to report that it
556 work great! According to its designers, to get it to work out of the
557 box, you need the Linux kernel version
4.1 or later. I tested on a
558 Debian Stretch machine (kernel version
4.9), and there it worked just
559 fine, increasing the available entropy very quickly. I wrote a small
560 test oneliner to test. It first print the current entropy level,
561 drain /dev/random, and then print the entropy level for five seconds.
562 Here is the situation without the ChaosKey inserted:
</p
>
564 <blockquote
><pre
>
565 % cat /proc/sys/kernel/random/entropy_avail; \
566 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
567 for n in $(seq
1 5); do \
568 cat /proc/sys/kernel/random/entropy_avail; \
574 28 byte kopiert,
0,
000264565 s,
106 kB/s
581 </pre
></blockquote
>
583 <p
>The entropy level increases by
3-
4 every second. In such case any
584 application requiring random bits (like a HTTPS enabled web server)
585 will halt and wait for more entrpy. And here is the situation with
586 the ChaosKey inserted:
</p
>
588 <blockquote
><pre
>
589 % cat /proc/sys/kernel/random/entropy_avail; \
590 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
591 for n in $(seq
1 5); do \
592 cat /proc/sys/kernel/random/entropy_avail; \
598 104 byte kopiert,
0,
000487647 s,
213 kB/s
605 </pre
></blockquote
>
607 <p
>Quite the difference. :) I bought a few more than I need, in case
608 someone want to buy one here in Norway. :)
</p
>
610 <p
>Update: The dongle was presented at Debconf last year. You might
611 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
612 recording illuminating
</a
>. It explains exactly what the source of
613 randomness is, if you are unable to spot it from the schema drawing
614 available from the ChaosKey web site linked at the start of this blog
620 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
621 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
622 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
623 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
624 <description><p
>Did you ever wonder where the web trafic really flow to reach the
625 web servers, and who own the network equipment it is flowing through?
626 It is possible to get a glimpse of this from using traceroute, but it
627 is hard to find all the details. Many years ago, I wrote a system to
628 map the Norwegian Internet (trying to figure out if our plans for a
629 network game service would get low enough latency, and who we needed
630 to talk to about setting up game servers close to the users. Back
631 then I used traceroute output from many locations (I asked my friends
632 to run a script and send me their traceroute output) to create the
633 graph and the map. The output from traceroute typically look like
637 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
638 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
639 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
640 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
641 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
642 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
643 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
644 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
648 </pre
></p
>
650 <p
>This show the DNS names and IP addresses of (at least some of the)
651 network equipment involved in getting the data traffic from me to the
652 www.stortinget.no server, and how long it took in milliseconds for a
653 package to reach the equipment and return to me. Three packages are
654 sent, and some times the packages do not follow the same path. This
655 is shown for hop
5, where three different IP addresses replied to the
656 traceroute request.
</p
>
658 <p
>There are many ways to measure trace routes. Other good traceroute
659 implementations I use are traceroute (using ICMP packages) mtr (can do
660 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
661 traceroute and a lot of other capabilities). All of them are easily
662 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
664 <p
>This time around, I wanted to know the geographic location of
665 different route points, to visualize how visiting a web page spread
666 information about the visit to a lot of servers around the globe. The
667 background is that a web site today often will ask the browser to get
668 from many servers the parts (for example HTML, JSON, fonts,
669 JavaScript, CSS, video) required to display the content. This will
670 leak information about the visit to those controlling these servers
671 and anyone able to peek at the data traffic passing by (like your ISP,
672 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
674 <p
>Lets pick an example, the Norwegian parliament web site
675 www.stortinget.no. It is read daily by all members of parliament and
676 their staff, as well as political journalists, activits and many other
677 citizens of Norway. A visit to the www.stortinget.no web site will
678 ask your browser to contact
8 other servers: ajax.googleapis.com,
679 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
680 stats.g.doubleclick.net, www.google-analytics.com,
681 www.googletagmanager.com and www.netigate.se. I extracted this by
682 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
683 Stortinget web page and tell me all the URLs PhantomJS downloaded to
684 render the page (in HAR format using
685 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
686 netsniff example
</a
>. I am very grateful to Gorm for showing me how
687 to do this). My goal is to visualize network traces to all IP
688 addresses behind these DNS names, do show where visitors personal
689 information is spread when visiting the page.
</p
>
691 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
692 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
>
694 <p
>When I had a look around for options, I could not find any good
695 free software tools to do this, and decided I needed my own traceroute
696 wrapper outputting KML based on locations looked up using GeoIP. KML
697 is easy to work with and easy to generate, and understood by several
698 of the GIS tools I have available. I got good help from by NUUG
699 colleague Anders Einar with this, and the result can be seen in
700 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
701 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
702 free GeoIP databases I could find (and the for-pay databases my
703 friends had access to) is not up to the task. The IP addresses of
704 central Internet infrastructure would typically be placed near the
705 controlling companies main office, and not where the router is really
706 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
707 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
709 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
710 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
>
712 <p
>I also had a look at the visual traceroute graph created by
713 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
714 showing IP network ownership (aka AS owner) for the IP address in
716 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
717 graph display a lot of useful information about the traceroute in SVG
718 format
</a
>, and give a good indication on who control the network
719 equipment involved, but it do not include geolocation. This graph
720 make it possible to see the information is made available at least for
721 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
722 3 Communications and NetDNA.
</p
>
724 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
725 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
>
727 <p
>In the process, I came across the
728 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
729 Salim Gasmi. Its methology of combining guesses based on DNS names,
730 various location databases and finally use latecy times to rule out
731 candidate locations seemed to do a very good job of guessing correct
732 geolocation. But it could only do one trace at the time, did not have
733 a sensor in Norway and did not make the geolocations easily available
734 for postprocessing. So I contacted the developer and asked if he
735 would be willing to share the code (he refused until he had time to
736 clean it up), but he was interested in providing the geolocations in a
737 machine readable format, and willing to set up a sensor in Norway. So
738 since yesterday, it is possible to run traces from Norway in this
739 service thanks to a sensor node set up by
740 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
741 trace in KML format for further processing.
</p
>
743 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
744 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
>
746 <p
>Here we can see a lot of trafic passes Sweden on its way to
747 Denmark, Germany, Holland and Ireland. Plenty of places where the
748 Snowden confirmations verified the traffic is read by various actors
749 without your best interest as their top priority.
</p
>
751 <p
>Combining KML files is trivial using a text editor, so I could loop
752 over all the hosts behind the urls imported by www.stortinget.no and
753 ask for the KML file from GeoTraceroute, and create a combined KML
754 file with all the traces (unfortunately only one of the IP addresses
755 behind the DNS name is traced this time. To get them all, one would
756 have to request traces using IP number instead of DNS names from
757 GeoTraceroute). That might be the next step in this project.
</p
>
759 <p
>Armed with these tools, I find it a lot easier to figure out where
760 the IP traffic moves and who control the boxes involved in moving it.
761 And every time the link crosses for example the Swedish border, we can
762 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
763 Britain and NSA in USA and cables around the globe. (Hm, what should
764 we tell them? :) Keep that in mind if you ever send anything
765 unencrypted over the Internet.
</p
>
767 <p
>PS: KML files are drawn using
768 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
769 Rublev
<a/
>, as it was less cluttered than the local Linux application
770 Marble. There are heaps of other options too.
</p
>
772 <p
>As usual, if you use Bitcoin and want to show your support of my
773 activities, please send Bitcoin donations to my address
774 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
779 <title>Appstream just learned how to map hardware to packages too!
</title>
780 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
781 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
782 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
783 <description><p
>I received a very nice Christmas present today. As my regular
784 readers probably know, I have been working on the
785 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
786 system
</a
> for many years. The goal of the Isenkram system is to make
787 it easier for users to figure out what to install to get a given piece
788 of hardware to work in Debian, and a key part of this system is a way
789 to map hardware to packages. Isenkram have its own mapping database,
790 and also uses data provided by each package using the AppStream
791 metadata format. And today,
792 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
793 Debian learned to look up hardware the same way Isenkram is doing it,
794 ie using fnmatch():
</p
>
797 % appstreamcli what-provides modalias \
798 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
799 Identifier: pymissile [generic]
801 Summary: Control original Striker USB Missile Launcher
803 % appstreamcli what-provides modalias usb:v0694p0002d0000
804 Identifier: libnxt [generic]
806 Summary: utility library for talking to the LEGO Mindstorms NXT brick
809 Identifier: t2n [generic]
811 Summary: Simple command-line tool for Lego NXT
814 Identifier: python-nxt [generic]
816 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
819 Identifier: nbc [generic]
821 Summary: C compiler for LEGO Mindstorms NXT bricks
824 </pre
></p
>
826 <p
>A similar query can be done using the combined AppStream and
827 Isenkram databases using the isenkram-lookup tool:
</p
>
830 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
832 % isenkram-lookup usb:v0694p0002d0000
838 </pre
></p
>
840 <p
>You can find modalias values relevant for your machine using
841 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
843 <p
>If you want to make this system a success and help Debian users
844 make the most of the hardware they have, please
845 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
846 AppStream metadata for your package following the guidelines
</a
>
847 documented in the wiki. So far only
11 packages provide such
848 information, among the several hundred hardware specific packages in
849 Debian. The Isenkram database on the other hand contain
101 packages,
850 mostly related to USB dongles. Most of the packages with hardware
851 mapping in AppStream are LEGO Mindstorms related, because I have, as
852 part of my involvement in
853 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
854 team
</a
> given priority to making sure LEGO users get proposed the
855 complete set of packages in Debian for that particular hardware. The
856 team also got a nice Christmas present today. The
857 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
858 package
</a
> made it into Debian. With this package in place, it is
859 now possible to use the LEGO Mindstorms NXT unit with only free
860 software, as the nxt-firmware package contain the source and firmware
861 binaries for the NXT brick.
</p
>
863 <p
>As usual, if you use Bitcoin and want to show your support of my
864 activities, please send Bitcoin donations to my address
865 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
870 <title>Isenkram updated with a lot more hardware-package mappings
</title>
871 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
872 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
873 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
874 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
875 system
</a
> I wrote two years ago to make it easier in Debian to find
876 and install packages to get your hardware dongles to work, is still
877 going strong. It is a system to look up the hardware present on or
878 connected to the current system, and map the hardware to Debian
879 packages. It can either be done using the tools in isenkram-cli or
880 using the user space daemon in the isenkram package. The latter will
881 notify you, when inserting new hardware, about what packages to
882 install to get the dongle working. It will even provide a button to
883 click on to ask packagekit to install the packages.
</p
>
885 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
904 </pre
></p
>
906 <p
>It can also list the firware package providing firmware requested
907 by the load kernel modules, which in my case is an empty list because
908 I have all the firmware my machine need:
911 % /usr/sbin/isenkram-autoinstall-firmware -l
912 info: did not find any firmware files requested by loaded kernel modules. exiting
914 </pre
></p
>
916 <p
>The last few days I had a look at several of the around
250
917 packages in Debian with udev rules. These seem like good candidates
918 to install when a given hardware dongle is inserted, and I found
919 several that should be proposed by isenkram. I have not had time to
920 check all of them, but am happy to report that now there are
97
921 packages packages mapped to hardware by Isenkram.
11 of these
922 packages provide hardware mapping using AppStream, while the rest are
923 listed in the modaliases file provided in isenkram.
</p
>
925 <p
>These are the packages with hardware mappings at the moment. The
926 <strong
>marked packages
</strong
> are also announcing their hardware
927 support using AppStream, for everyone to use:
</p
>
929 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
930 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
931 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
932 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
933 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
934 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
935 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
936 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
937 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
938 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
939 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
940 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
941 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
942 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
943 pcscd, pidgin-blinklight, printer-driver-splix,
944 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
945 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
946 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
947 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
948 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
949 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
950 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
951 xserver-xorg-video-vmware, yubikey-personalization and
952 zd1211-firmware
</p
>
954 <p
>If you know of other packages, please let me know with a wishlist
955 bug report against the isenkram-cli package, and ask the package
957 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
958 metadata according to the guidelines
</a
> to provide the information
959 for everyone. In time, I hope to get rid of the isenkram specific
960 hardware mapping and depend exclusively on AppStream.
</p
>
962 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
963 much hardware, and suggest that the package with with any ethernet
964 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
965 the details. I hope the maintainer find time to address it soon. In
966 the mean time I provide an override in isenkram.
</p
>
971 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
972 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
973 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
974 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
975 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
977 <p
>In my early years, I played
978 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
979 Elite
</a
> on my PC. I spent many months trading and fighting in
980 space, and reached the
'elite
' fighting status before I moved on. The
981 original Elite game was available on Commodore
64 and the IBM PC
982 edition I played had a
64 KB executable. I am still impressed today
983 that the authors managed to squeeze both a
3D engine and details about
984 more than
2000 planet systems across
7 galaxies into a binary so
987 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
988 software game Oolite inspired by Elite
</a
> for a while, but did not
989 really have time to test it properly until a few days ago. It was
990 great to discover that my old knowledge about trading routes were
991 still valid. But my fighting and flying abilities were gone, so I had
992 to retrain to be able to dock on a space station. And I am still not
993 able to make much resistance when I am attacked by pirates, so I
994 bougth and mounted the most powerful laser in the rear to be able to
995 put up at least some resistance while fleeing for my life. :)
</p
>
997 <p
>When playing Elite in the late eighties, I had to discover
998 everything on my own, and I had long lists of prices seen on different
999 planets to be able to decide where to trade what. This time I had the
1001 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
1002 where information about each planet is easily available with common
1003 price ranges and suggested trading routes. This improved my ability
1004 to earn money and I have been able to earn enough to buy a lot of
1005 useful equipent in a few days. I believe I originally played for
1006 months before I could get a docking computer, while now I could get it
1007 after less then a week.
</p
>
1009 <p
>If you like science fiction and dreamed of a life as a vagabond in
1010 space, you should try out Oolite. It is available for Linux, MacOSX
1011 and Windows, and is included in Debian and derivatives since
2011.
</p
>
1013 <p
>As usual, if you use Bitcoin and want to show your support of my
1014 activities, please send Bitcoin donations to my address
1015 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1020 <title>Quicker Debian installations using eatmydata
</title>
1021 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
1022 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
1023 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
1024 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
1025 installation system, observing how using
1026 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
1027 could speed up the installation
</a
> quite a bit. My testing measured
1028 speedup around
20-
40 percent for Debian Edu, where we install around
1029 1000 packages from within the installer. The eatmydata package
1030 provide a way to disable/delay file system flushing. This is a bit
1031 risky in the general case, as files that should be stored on disk will
1032 stay only in memory a bit longer than expected, causing problems if a
1033 machine crashes at an inconvenient time. But for an installation, if
1034 the machine crashes during installation the process is normally
1035 restarted, and avoiding disk operations as much as possible to speed
1036 up the process make perfect sense.
1038 <p
>I added code in the Debian Edu specific installation code to enable
1039 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
1040 but did not have time to push it any further. But a few months ago I
1041 picked it up again and worked with the libeatmydata package maintainer
1042 Mattia Rizzolo to make it easier for everyone to get this installation
1043 speedup in Debian. Thanks to our cooperation There is now an
1044 eatmydata-udeb package in Debian testing and unstable, and simply
1045 enabling/installing it in debian-installer (d-i) is enough to get the
1046 quicker installations. It can be enabled using preseeding. The
1047 following untested kernel argument should do the trick:
</p
>
1049 <blockquote
><pre
>
1050 preseed/early_command=
"anna-install eatmydata-udeb
"
1051 </pre
></blockquote
>
1053 <p
>This should ask d-i to install the package inside the d-i
1054 environment early in the installation sequence. Having it installed
1055 in d-i in turn will make sure the relevant scripts are called just
1056 after debootstrap filled /target/ with the freshly installed Debian
1057 system to configure apt to run dpkg with eatmydata. This is enough to
1058 speed up the installation process. There is a proposal to
1059 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1060 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1061 tested its impact.
</p
>
1067 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1068 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1069 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1070 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1071 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1072 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1073 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1074 elever over det ganske land skal levere inn hvert år. Det mange ikke
1075 vet er at selv om de kommersielle alternativene
1076 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1077 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1078 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1079 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1080 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1081 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1082 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1083 nynorsk, og få den automatoversatt til det andre skriftspråket.
1084 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1085 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1086 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1087 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1088 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1089 teksten din i webskjemaet der.
1091 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1092 teknologien kan du enten installere pakken
1093 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1094 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1095 api.apertium.org. Se
1096 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1097 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1098 denne teksten som ble skrevet på bokmål over maskinoversatt til
1103 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1104 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1105 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1106 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1107 veit er at sjølv om dei kommersielle alternativa
1108 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1109 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1110 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1111 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1112 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1113 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1114 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1115 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1116 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1117 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1118 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1119 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1120 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1121 teksta di i *webskjemaet der.
1123 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1124 teknologien kan du anten installera pakken
1125 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1126 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1127 *api.*apertium.org. Sjå
1128 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1129 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1130 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1136 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1137 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1138 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1139 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1140 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1141 profiler able to run benchmarking experiments on the instrumented
1142 multi-threaded program, finally
1143 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1144 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1146 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1147 blogged about the coz tool
</a
> in August working with upstream to make
1148 it suitable for Debian. There are still issues with clang
1149 compatibility, inline assembly only working x86 and minimized
1150 JavaScript libraries.
</p
>
1152 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1154 <p
><blockquote
>
1155 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1156 </blockquote
></p
>
1158 <p
>This will produce a profile.coz file in the current working
1159 directory with the profiling information. This is then given to a
1160 JavaScript application provided in the package and available from
1161 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1162 To start the local copy, invoke it in a browser like this:
</p
>
1164 <p
><blockquote
>
1165 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1166 </blockquote
></p
>
1168 <p
>See the project home page and the
1169 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1170 ;login: article on Coz
</a
> for more information on how it is
1176 <title>My own self balancing Lego Segway
</title>
1177 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1179 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1180 <description><p
>A while back I received a Gyro sensor for the NXT
1181 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1182 present. It had been on my wishlist for a while, because I wanted to
1183 build a Segway like balancing lego robot. I had already built
1184 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1185 robot
</a
> with the kids, using the light/color sensor included in the
1186 NXT kit as the balance sensor, but it was not working very well. It
1187 could balance for a while, but was very sensitive to the light
1188 condition in the room and the reflective properties of the surface and
1189 would fall over after a short while. I wanted something more robust,
1191 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1192 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1193 wishlist for some years before it suddenly showed up as a gift from my
1194 loved ones. :)
</p
>
1196 <p
>Unfortunately I have not had time to sit down and play with it
1197 since then. But that changed some days ago, when I was searching for
1198 lego segway information and came across a recipe from HiTechnic for
1200 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1201 HTWay
</a
>, a segway like balancing robot. Build instructions and
1202 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1203 code
</a
> was included, so it was just a question of putting it all
1204 together. And thanks to the great work of many Debian developers, the
1205 compiler needed to build the source for the NXT is already included in
1206 Debian, so I was read to go in less than an hour. The resulting robot
1207 do not look very impressive in its simplicity:
</p
>
1209 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1211 <p
>Because I lack the infrared sensor used to control the robot in the
1212 design from HiTechnic, I had to comment out the last task
1213 (taskControl). I simply placed /* and */ around it get the program
1214 working without that sensor present. Now it balances just fine until
1215 the battery status run low:
</p
>
1217 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1218 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1219 </video
></p
>
1221 <p
>Now we would like to teach it how to follow a line and take remote
1222 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1224 <p
>If you, like me, love LEGO and want to make sure we find the tools
1225 they need to work with LEGO in Debian and all our derivative
1226 distributions like Ubuntu, check out
1227 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1228 project page
</a
> and join the Debian LEGO team. Personally I own a
1229 RCX and NXT controller (no EV3), and would like to make sure the
1230 Debian tools needed to program the systems I own work as they
1236 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1237 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1238 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1239 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1240 <description><p
>In July
1241 <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
1242 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1243 the ability to receive SMS messages (aka without a cell phone). It is
1244 time to share some experiences and provide an updated setup.
</p
>
1246 <p
>The Signal app have worked fine for several months now, and I use
1247 it regularly to chat with my loved ones. I had a major snag at the
1248 end of my summer vacation, when the the app completely forgot my
1249 setup, identity and keys. The reason behind this major mess was
1250 running out of disk space. To avoid that ever happening again I have
1251 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1252 roll back to an earlier version if the files are wiped by mistake. I
1253 had to use it once after introducing the git backup. When rolling
1254 back to an earlier version, one need to use the
'reset session
' option
1255 in Signal to get going, and notify the people you talk with about the
1256 problem. I assume there is some sequence number tracking in the
1257 protocol to detect rollback attacks. The git repository is rather big
1258 (
674 MiB so far), but I have not tried to figure out if some of the
1259 content can be added to a .gitignore file due to lack of spare
1262 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1263 make it impossible to send messages using Signal. I could still
1264 receive them, but had to patch the code with a new timestamp to send.
1265 I believe the timeout is added by the developers to force people to
1266 upgrade to the latest version of the app, even when there is no
1267 protocol changes, to reduce the version skew among the user base and
1268 thus try to keep the number of support requests down.
</p
>
1270 <p
>Since my original recipe, the Signal source code changed slightly,
1271 making the old patch fail to apply cleanly. Below is an updated
1272 patch, including the shell wrapper I use to start Signal. The
1273 original version required a new user to locate the JavaScript console
1274 and call a function from there. I got help from a friend with more
1275 JavaScript knowledge than me to modify the code to provide a GUI
1276 button instead. This mean that to get started you just need to run
1277 the wrapper and click the
'Register without mobile phone
' to get going
1278 now. I
've also modified the timeout code to always set it to
90 days
1279 in the future, to avoid having to patch the code regularly.
</p
>
1281 <p
>So, the updated recipe for Debian Jessie:
</p
>
1285 <li
>First, install required packages to get the source code and the
1286 browser you need. Signal only work with Chrome/Chromium, as far as I
1287 know, so you need to install it.
1290 apt install git tor chromium
1291 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1292 </pre
></li
>
1294 <li
>Modify the source code using command listed in the the patch
1295 block below.
</li
>
1297 <li
>Start Signal using the run-signal-app wrapper (for example using
1298 <tt
>`pwd`/run-signal-app
</tt
>).
1300 <li
>Click on the
'Register without mobile phone
', will in a phone
1301 number you can receive calls to the next minute, receive the
1302 verification code and enter it into the form field and press
1303 'Register
'. Note, the phone number you use will be user Signal
1304 username, ie the way others can find you on Signal.
</li
>
1306 <li
>You can now use Signal to contact others. Note, new contacts do
1307 not show up in the contact list until you restart Signal, and there is
1308 no way to assign names to Contacts. There is also no way to create or
1309 update chat groups. I suspect this is because the web app do not have
1310 a associated contact database.
</li
>
1314 <p
>I am still a bit uneasy about using Signal, because of the way its
1315 main author moxie0 reject federation and accept dependencies to major
1316 corporations like Google (part of the code is fetched from Google) and
1317 Amazon (the central coordination point is owned by Amazon). See for
1319 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1320 LibreSignal issue tracker
</a
> for a thread documenting the authors
1321 view on these issues. But the network effect is strong in this case,
1322 and several of the people I want to communicate with already use
1323 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1324 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1325 laptop
</a
>? It already work on Windows and Android, and is included
1326 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1327 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1328 working on Debian Stable.
</p
>
1330 <p
>Anyway, this is the patch I apply to the Signal code to get it
1331 working. It switch to the production servers, disable to timeout,
1332 make registration easier and add the shell wrapper:
</p
>
1335 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1336 diff --git a/js/background.js b/js/background.js
1337 index
24b4c1d.
.579345f
100644
1338 --- a/js/background.js
1339 +++ b/js/background.js
1344 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1345 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1346 var SERVER_PORTS = [
80,
4433,
8443];
1347 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1348 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1349 var messageReceiver;
1350 window.getSocketStatus = function() {
1351 if (messageReceiver) {
1352 diff --git a/js/expire.js b/js/expire.js
1353 index
639aeae..beb91c3
100644
1358 'use strict
';
1359 - var BUILD_EXPIRATION =
0;
1360 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1362 window.extension = window.extension || {};
1364 diff --git a/js/views/install_view.js b/js/views/install_view.js
1365 index
7816f4f.
.1d6233b
100644
1366 --- a/js/views/install_view.js
1367 +++ b/js/views/install_view.js
1370 'click .step1
': this.selectStep.bind(this,
1),
1371 'click .step2
': this.selectStep.bind(this,
2),
1372 -
'click .step3
': this.selectStep.bind(this,
3)
1373 +
'click .step3
': this.selectStep.bind(this,
3),
1374 +
'click .callreg
': function() { extension.install(
'standalone
') },
1377 clearQR: function() {
1378 diff --git a/options.html b/options.html
1379 index dc0f28e.
.8d709f6
100644
1383 &lt;div class=
'nav
'>
1384 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1385 &lt;p
>{{ installTagline }}
&lt;/p
>
1386 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1387 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1388 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1391 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1392 &lt;span class=
'dot step2
'>&lt;/span
>
1393 &lt;span class=
'dot step3
'>&lt;/span
>
1394 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1395 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1401 +userdata=
"`pwd`/userdata
"
1402 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1403 + (cd $userdata
&& git init)
1405 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1407 + --proxy-server=
"socks://localhost:
9050" \
1408 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1410 chmod a+rx run-signal-app
1413 <p
>As usual, if you use Bitcoin and want to show your support of my
1414 activities, please send Bitcoin donations to my address
1415 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1420 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1421 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1422 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1423 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1424 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1425 system
</a
> provide a practical and easy way to figure out which
1426 packages support the hardware in a given machine. The command line
1427 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1428 convenient way to list and install packages relevant for the current
1429 hardware during system installation, both user space packages and
1430 firmware packages. The GUI background daemon on the other hand provide
1431 a pop-up proposing to install packages when a new dongle is inserted
1432 while using the computer. For example, if you plug in a smart card
1433 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1434 that package isn
't already installed, and if you plug in a USB video
1435 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1436 cheese is currently missing. This already work just fine.
</p
>
1438 <p
>But Isenkram depend on a database mapping from hardware IDs to
1439 package names. When I started no such database existed in Debian, so
1440 I made my own data set and included it with the isenkram package and
1441 made isenkram fetch the latest version of this database from git using
1442 http. This way the isenkram users would get updated package proposals
1443 as soon as I learned more about hardware related packages.
</p
>
1445 <p
>The hardware is identified using modalias strings. The modalias
1446 design is from the Linux kernel where most hardware descriptors are
1447 made available as a strings that can be matched using filename style
1448 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1449 identifiers.
</p
>
1451 <p
>The downside to the Isenkram specific database is that there is no
1452 information about relevant distribution / Debian version, making
1453 isenkram propose obsolete packages too. But along came AppStream, a
1454 cross distribution mechanism to store and collect metadata about
1455 software packages. When I heard about the proposal, I contacted the
1456 people involved and suggested to add a hardware matching rule using
1457 modalias strings in the specification, to be able to use AppStream for
1458 mapping hardware to packages. This idea was accepted and AppStream is
1459 now a great way for a package to announce the hardware it support in a
1460 distribution neutral way. I wrote
1461 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1462 recipe on how to add such meta-information
</a
> in a blog post last
1463 December. If you have a hardware related package in Debian, please
1464 announce the relevant hardware IDs using AppStream.
</p
>
1466 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1467 RCX or NXT unit, announce this support using AppStream. The effect is
1468 that when you insert such LEGO robot controller into your Debian
1469 machine, Isenkram will propose to install the packages needed to get
1470 it working. The intention is that this should allow the local user to
1471 start programming his robot controller right away without having to
1472 guess what packages to use or which permissions to fix.
</p
>
1474 <p
>But when I sat down with my son the other day to program our NXT
1475 unit using his Debian Stretch computer, I discovered something
1476 annoying. The local console user (ie my son) did not get access to
1477 the USB device for programming the unit. This used to work, but no
1478 longer in Jessie and Stretch. After some investigation and asking
1479 around on #debian-devel, I discovered that this was because udev had
1480 changed the mechanism used to grant access to local devices. The
1481 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1482 no longer applied, because LDAP users no longer was added to the
1483 plugdev group during login. Michael Biebl told me that this method
1484 was obsolete and the new method used ACLs instead. This was good
1485 news, as the plugdev mechanism is a mess when using a remote user
1486 directory like LDAP. Using ACLs would make sure a user lost device
1487 access when she logged out, even if the user left behind a background
1488 process which would retain the plugdev membership with the ConsoleKit
1489 setup. Armed with this knowledge I moved on to fix the access problem
1490 for the LEGO Mindstorms related packages.
</p
>
1492 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1493 applied directly for a device, or is applied in
1494 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1495 LEGO Mindstorms udev rules did not have a class, I decided to add the
1496 tag directly in the udev rules files included in the packages. Here
1497 is one example. For the nqc C compiler for the RCX, the
1498 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1500 <p
><pre
>
1501 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1502 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1503 </pre
></p
>
1505 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1506 packages using plugdev in their /lib/udev/rules.d/ files should be
1507 changed to use this tag (either directly or indirectly via
1508 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1509 to detect this?
</p
>
1511 <p
>I
've been unable to find good documentation on the uaccess feature.
1512 It is unclear to me if the uaccess tag is an internal implementation
1513 detail like the udev-acl tag used by
1514 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1515 indirect method is the preferred way. Michael
1516 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1517 documentation from the systemd project
</a
> and I hope it will make
1518 this clearer. For now I use the generic classes when they exist and
1519 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1520 directly if no such class exist.
</p
>
1522 <p
>To learn more about the isenkram system, please check out
1523 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1524 blog posts tagged isenkram
</a
>.
</p
>
1526 <p
>To help out making life for LEGO constructors in Debian easier,
1527 please join us on our IRC channel
1528 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1529 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1530 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1531 list is not yet created, but we are working on it. :)
</p
>
1533 <p
>As usual, if you use Bitcoin and want to show your support of my
1534 activities, please send Bitcoin donations to my address
1535 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1540 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1541 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1542 <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>
1543 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1544 <description><p
>In April we
1545 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1546 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1547 how to set up and administrate a Debian system. Today I am happy to
1548 report that the first draft is now publicly available. You can find
1549 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1550 Administrator
's Handbook page
</a
> (under Other languages). The first
1551 eight chapters have a first draft translation, and we are working on
1552 proofreading the content. If you want to help out, please start
1554 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1555 hosted weblate project page
</a
>, and get in touch using
1556 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1557 translators mailing list
</a
>. Please also check out
1558 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1559 contributors
</a
>. A good way to contribute is to proofread the text
1560 and update weblate if you find errors.
</p
>
1562 <p
>Our goal is still to make the Norwegian book available on paper as well as
1563 electronic form.
</p
>
1568 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1569 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1570 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1571 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1572 <description><p
>This summer, I read a great article
1573 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1574 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1575 how to profile multi-threaded programs. It presented a system for
1576 profiling software by running experiences in the running program,
1577 testing how run time performance is affected by
"speeding up
" parts of
1578 the code to various degrees compared to a normal run. It does this by
1579 slowing down parallel threads while the
"faster up
" code is running
1580 and measure how this affect processing time. The processing time is
1581 measured using probes inserted into the code, either using progress
1582 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1583 can also measure unmodified code by measuring complete the program
1584 runtime and running the program several times instead.
</p
>
1586 <p
>The project and presentation was so inspiring that I would like to
1587 get the system into Debian. I
1588 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1589 a WNPP request for it
</a
> and contacted upstream to try to make the
1590 system ready for Debian by sending patches. The build process need to
1591 be changed a bit to avoid running
'git clone
' to get dependencies, and
1592 to include the JavaScript web page used to visualize the collected
1593 profiling information included in the source package.
1594 But I expect that should work out fairly soon.
</p
>
1596 <p
>The way the system work is fairly simple. To run an coz experiment
1597 on a binary with debug symbols available, start the program like this:
1599 <p
><blockquote
><pre
>
1600 coz run --- program-to-run
1601 </pre
></blockquote
></p
>
1603 <p
>This will create a text file profile.coz with the instrumentation
1604 information. To show what part of the code affect the performance
1605 most, use a web browser and either point it to
1606 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1607 or use the copy from git (in the gh-pages branch). Check out this web
1608 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
1609 profiling more useful you include
&lt;coz.h
&gt; and insert the
1610 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1611 code, rebuild and run the profiler. This allow coz to do more
1612 targeted experiments.
</p
>
1614 <p
>A video published by ACM
1615 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1616 Coz profiler
</a
> is available from Youtube. There is also a paper
1617 from the
25th Symposium on Operating Systems Principles available
1619 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1620 finding code that counts with causal profiling
</a
>.
</p
>
1622 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1623 for Coz is available from github. It will only build with clang
1625 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1626 feature missing in GCC
</a
>, but I
've submitted
1627 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1628 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1630 <p
>Please get in touch if you, like me, would like to see this piece
1631 of software in Debian. I would very much like some help with the
1632 packaging effort, as I lack the in depth knowledge on how to package
1633 C++ libraries.
</p
>
1638 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1639 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1640 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1641 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1642 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1643 to be a slight challenge. Here is the recipe if I ever need to do it
1644 again. It all started by me wanting to try the recipe to set up
1645 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1646 hardened Android installation
</a
> from the Tor project blog on a
1647 device I had access to. It is a old mobile phone with a broken
1648 microphone The initial idea had been to just
1649 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1650 CyanogenMod on it
</a
>, but did not quite find time to start on it
1651 until a few days ago.
</p
>
1653 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1654 loader (press volume down and power at the same time), (
2) select
1655 'fastboot
' before (
3) connecting the device via USB to a Linux
1656 machine, (
4) request the device identifier token by running
'fastboot
1657 oem get_identifier_token
', (
5) request the device unlocking key using
1658 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1659 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1661 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1662 or newer, and the device I was working on had
2.00.0027. This
1663 apparently can be easily fixed by downloading a Windows program and
1664 running it on your Windows machine, if you accept the terms Microsoft
1665 require you to accept to use Windows - which I do not. So I had to
1666 come up with a different approach. I got a lot of help from AndyCap
1667 on #nuug, and would not have been able to get this working without
1670 <p
>First I needed to extract the hboot firmware from
1671 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1672 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1673 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1674 project named unruu
</a
> using libunshield. The unshield tool did not
1675 recognise the file format, but unruu worked and extracted rom.zip,
1676 containing the new hboot firmware and a text file describing which
1677 devices it would work for.
</p
>
1679 <p
>Next, I needed to get the new firmware into the device. For this I
1680 followed some instructions
1681 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1682 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1683 machine with Debian testing:
</p
>
1685 <p
><pre
>
1686 adb reboot-bootloader
1687 fastboot oem rebootRUU
1688 fastboot flash zip rom.zip
1689 fastboot flash zip rom.zip
1691 </pre
></p
>
1693 <p
>The flash command apparently need to be done twice to take effect,
1694 as the first is just preparations and the second one do the flashing.
1695 The adb command is just to get to the boot loader menu, so turning the
1696 device on while holding volume down and the power button should work
1699 <p
>With the new hboot version in place I could start following the
1700 instructions on the HTC developer web site. I got the device token
1701 like this:
</p
>
1703 <p
><pre
>
1704 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1707 <p
>And once I got the unlock code via email, I could use it like
1710 <p
><pre
>
1711 fastboot flash unlocktoken Unlock_code.bin
1712 </pre
></p
>
1714 <p
>And with that final step in place, the phone was unlocked and I
1715 could start stuffing the software of my own choosing into the device.
1716 So far I only inserted a replacement recovery image to wipe the phone
1717 before I start. We will see what happen next. Perhaps I should
1718 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1723 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1724 <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>
1725 <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>
1726 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1727 <description><p
>For a while now, I have wanted to test
1728 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1729 said to provide end to end encrypted communication and several of my
1730 friends and family are already using it. As I by choice do not own a
1731 mobile phone, this proved to be harder than expected. And I wanted to
1732 have the source of the client and know that it was the code used on my
1733 machine. But yesterday I managed to get it working. I used the
1734 Github source, compared it to the source in
1735 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1736 Signal Chrome app
</a
> available from the Chrome web store, applied
1737 patches to use the production Signal servers, started the app and
1738 asked for the hidden
"register without a smart phone
" form. Here is
1739 the recipe how I did it.
</p
>
1741 <p
>First, I fetched the Signal desktop source from Github, using
1744 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1747 <p
>Next, I patched the source to use the production servers, to be
1748 able to talk to other Signal users:
</p
>
1751 cat
&lt;
&lt;EOF | patch -p0
1752 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1753 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1754 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1759 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1760 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1761 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1762 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1763 var messageReceiver;
1764 window.getSocketStatus = function() {
1765 if (messageReceiver) {
1766 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1767 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1768 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1771 'use strict
';
1772 - var BUILD_EXPIRATION =
0;
1773 + var BUILD_EXPIRATION =
1474492690000;
1775 window.extension = window.extension || {};
1780 <p
>The first part is changing the servers, and the second is updating
1781 an expiration timestamp. This timestamp need to be updated regularly.
1782 It is set
90 days in the future by the build process (Gruntfile.js).
1783 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1785 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1786 script to launch Signal in Chromium.
</p
>
1793 --proxy-server=
"socks://localhost:
9050" \
1794 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1797 <p
> The script start the app and configure Chromium to use the Tor
1798 SOCKS5 proxy to make sure those controlling the Signal servers (today
1799 Amazon and Whisper Systems) as well as those listening on the lines
1800 will have a harder time location my laptop based on the Signal
1801 connections if they use source IP address.
</p
>
1803 <p
>When the script starts, one need to follow the instructions under
1804 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1805 repository. I right clicked on the Signal window to get up the
1806 Chromium debugging tool, visited the
'Console
' tab and wrote
1807 'extension.install(
"standalone
")
' on the console prompt to get the
1808 registration form. Then I entered by land line phone number and
1809 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1810 repeated the verification code three times. After entering the number
1811 into the verification code field in the form, I could start using
1812 Signal from my laptop.
1814 <p
>As far as I can tell, The Signal app will leak who is talking to
1815 whom and thus who know who to those controlling the central server,
1816 but such leakage is hard to avoid with a centrally controlled server
1817 setup. It is something to keep in mind when using Signal - the
1818 content of your chats are harder to intercept, but the meta data
1819 exposing your contact network is available to people you do not know.
1820 So better than many options, but not great. And sadly the usage is
1821 connected to my land line, thus allowing those controlling the server
1822 to associate it to my home and person. I would prefer it if only
1823 those I knew could tell who I was on Signal. There are options
1824 avoiding such information leakage, but most of my friends are not
1825 using them, so I am stuck with Signal for now.
</p
>
1827 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1829 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1830 and updated recipe for using the Signal app without a mobile
1831 phone
</a
>.
</p
>
1836 <title>The new
"best
" multimedia player in Debian?
</title>
1837 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1838 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1839 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1840 <description><p
>When I set out a few weeks ago to figure out
1841 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1842 multimedia player in Debian claimed to support most file formats /
1843 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1844 the various players claimed support for. The range was from
55 to
130
1845 MIME types. I suspect most media formats are supported by all
1846 players, but this is not really reflected in the MimeTypes values in
1847 their desktop files. There are probably also some bogus MIME types
1848 listed, but it is hard to identify which one this is.
</p
>
1850 <p
>Anyway, in the mean time I got in touch with upstream for some of
1851 the players suggesting to add more MIME types to their desktop files,
1852 and decided to spend some time myself improving the situation for my
1853 favorite media player VLC. The fixes for VLC entered Debian unstable
1854 yesterday. The complete list of MIME types can be seen on the
1855 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1856 player MIME type support status
</a
> Debian wiki page.
</p
>
1858 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1859 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1860 kmplayer. I am sure some of the other players desktop files support
1861 several of the formats currently listed as working only with vlc,
1862 toten and parole.
</p
>
1864 <p
>A sad observation is that only
14 MIME types are listed as
1865 supported by all the tested multimedia players in Debian in their
1866 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1867 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1868 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1869 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1870 it sad that video/ogg and video/webm is not supported by all the media
1871 players in Debian. As far as I can tell, all of them can handle both
1877 <title>A program should be able to open its own files on Linux
</title>
1878 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1879 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1880 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1881 <description><p
>Many years ago, when koffice was fresh and with few users, I
1882 decided to test its presentation tool when making the slides for a
1883 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1884 wrote the first draft of the slides, saved the result and went to bed
1885 the day before I would give the talk. The next day I took a plane to
1886 the location where the meeting should take place, and on the plane I
1887 started up koffice again to polish the talk a bit, only to discover
1888 that kpresenter refused to load its own data file. I cursed a bit and
1889 started making the slides again from memory, to have something to
1890 present when I arrived. I tested that the saved files could be
1891 loaded, and the day seemed to be rescued. I continued to polish the
1892 slides until I suddenly discovered that the saved file could no longer
1893 be loaded into kpresenter. In the end I had to rewrite the slides
1894 three times, condensing the content until the talk became shorter and
1895 shorter. After the talk I was able to pinpoint the problem
&ndash;
1896 kpresenter wrote inline images in a way itself could not understand.
1897 Eventually that bug was fixed and kpresenter ended up being a great
1898 program to make slides. The point I
'm trying to make is that we
1899 expect a program to be able to load its own data files, and it is
1900 embarrassing to its developers if it can
't.
</p
>
1902 <p
>Did you ever experience a program failing to load its own data
1903 files from the desktop file browser? It is not a uncommon problem. A
1904 while back I discovered that the screencast recorder
1905 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1906 browser would refuse to open. No video player claimed to understand
1907 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1908 returning the application/ogg MIME type, which no video player I had
1909 installed listed as a MIME type they would understand. I asked for
1910 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1911 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1912 several video players to add video/ogg to their desktop files, to give
1913 the file browser an idea what to do about Ogg Theora files. After a
1914 while, the desktop file browsers in Debian started to handle the
1915 output from gtk-recordmydesktop properly.
</p
>
1917 <p
>But history repeats itself. A few days ago I tested the music
1918 system Rosegarden again, and I discovered that the KDE and xfce file
1919 browsers did not know what to do with the Rosegarden project files
1920 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1921 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1922 included in the next upload. To increase the chance of me remembering
1923 how to fix the problem next time some program fail to load its files
1924 from the file browser, here are some notes on how to fix it.
</p
>
1926 <p
>The file browsers in Debian in general operates on MIME types.
1927 There are two sources for the MIME type of a given file. The output from
1928 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1929 shared MIME type registry (under /usr/share/mime/). The file MIME
1930 type is mapped to programs supporting the MIME type, and this
1931 information is collected from
1932 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1933 desktop files
</a
> available in /usr/share/applications/. If there is
1934 one desktop file claiming support for the MIME type of the file, it is
1935 activated when asking to open a given file. If there are more, one
1936 can normally select which one to use by right-clicking on the file and
1937 selecting the wanted one using
'Open with
' or similar. In general
1938 this work well. But it depend on each program picking a good MIME
1940 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1941 MIME type registered with IANA
</a
>), file and/or the shared MIME
1942 registry recognizing the file and the desktop file to list the MIME
1943 type in its list of supported MIME types.
</p
>
1945 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1946 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1947 Shared MIME database
</a
> look like this:
</p
>
1949 <p
><blockquote
><pre
>
1950 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1951 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1952 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1953 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1954 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1955 &lt;glob pattern=
"*.rg
"/
&gt;
1956 &lt;/mime-type
&gt;
1957 &lt;/mime-info
&gt;
1958 </pre
></blockquote
></p
>
1960 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1961 (it is a gzipped XML file). Note, it is much better to use an
1962 official MIME type registered with IANA than it is to make up ones own
1963 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1965 <p
>The desktop file of the rosegarden program failed to list
1966 audio/x-rosegarden in its list of supported MIME types, causing the
1967 file browsers to have no idea what to do with *.rg files:
</p
>
1969 <p
><blockquote
><pre
>
1970 % grep Mime /usr/share/applications/rosegarden.desktop
1971 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1972 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1974 </pre
></blockquote
></p
>
1976 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1977 MimeType= line.
</p
>
1979 <p
>If you run into a file which fail to open the correct program when
1980 selected from the file browser, please check out the output from
1981 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1982 MIME type is registered somewhere under /usr/share/mime/ and check
1983 that some desktop file under /usr/share/applications/ is claiming
1984 support for this MIME type. If not, please report a bug to have it
1990 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1991 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1992 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1993 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1994 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1995 system
</a
> is a user-focused solution in Debian for handling hardware
1996 related packages. The idea is to have a database of mappings between
1997 hardware and packages, and pop up a dialog suggesting for the user to
1998 install the packages to use a given hardware dongle. Some use cases
1999 are when you insert a Yubikey, it proposes to install the software
2000 needed to control it; when you insert a braille reader list it
2001 proposes to install the packages needed to send text to the reader;
2002 and when you insert a ColorHug screen calibrator it suggests to
2003 install the driver for it. The system work well, and even have a few
2004 command line tools to install firmware packages and packages for the
2005 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
2007 <p
>The system was initially written using aptdaemon, because I found
2008 good documentation and example code on how to use it. But aptdaemon
2009 is going away and is generally being replaced by
2010 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
2011 so Isenkram needed a rewrite. And today, thanks to the great patch
2012 from my college Sunil Mohan Adapa in the FreedomBox project, the
2013 rewrite finally took place. I
've just uploaded a new version of
2014 Isenkram into Debian Unstable with the patch included, and the default
2015 for the background daemon is now to use PackageKit. To check it out,
2016 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
2017 and see if it is recognised.
</p
>
2019 <p
>If you want to know what kind of packages isenkram would propose for
2020 the machine it is running on, you can check out the isenkram-lookup
2021 program. This is what it look like on a Thinkpad X230:
</p
>
2023 <p
><blockquote
><pre
>
2039 </pre
></blockquote
></p
>
2041 <p
>The hardware mappings come from several places. The preferred way
2042 is for packages to announce their hardware support using
2043 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2044 cross distribution appstream system
</a
>.
2046 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2047 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2052 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2053 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2055 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2056 <description><p
>Yesterday I updated the
2057 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2058 package in Debian
</a
> with a few patches sent to me by skilled and
2059 enterprising users. There were some nice user and visible changes.
2060 First of all, both desktop menu entries now work. A design flaw in
2061 one of the script made the history graph fail to show up (its PNG was
2062 dumped in ~/.xsession-errors) if no controlling TTY was available.
2063 The script worked when called from the command line, but not when
2064 called from the desktop menu. I changed this to look for a DISPLAY
2065 variable or a TTY before deciding where to draw the graph, and now the
2066 graph window pop up as expected.
</p
>
2068 <p
>The next new feature is a discharge rate estimator in one of the
2069 graphs (the one showing the last few hours). New is also the user of
2070 colours showing charging in blue and discharge in red. The percentages
2071 of this graph is relative to last full charge, not battery design
2074 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2076 <p
>The other graph show the entire history of the collected battery
2077 statistics, comparing it to the design capacity of the battery to
2078 visualise how the battery life time get shorter over time. The red
2079 line in this graph is what the previous graph considers
100 percent:
2081 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2083 <p
>In this graph you can see that I only charge the battery to
80
2084 percent of last full capacity, and how the capacity of the battery is
2085 shrinking. :(
</p
>
2087 <p
>The last new feature is in the collector, which now will handle
2088 more hardware models. On some hardware, Linux power supply
2089 information is stored in /sys/class/power_supply/ACAD/, while the
2090 collector previously only looked in /sys/class/power_supply/AC/. Now
2091 both are checked to figure if there is power connected to the
2094 <p
>If you are interested in how your laptop battery is doing, please
2096 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2097 in Debian unstable, or rebuild it on Jessie to get it working on
2098 Debian stable. :) The upstream source is available from
<a
2099 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2100 Patches are very welcome.
</p
>
2102 <p
>As usual, if you use Bitcoin and want to show your support of my
2103 activities, please send Bitcoin donations to my address
2104 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2109 <title>Debian now with ZFS on Linux included
</title>
2110 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2111 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2112 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2113 <description><p
>Today, after many years of hard work from many people,
2114 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2115 Debian. The package status can be seen on
2116 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2117 for zfs-linux
</a
>. and
2118 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2119 team status page
</a
>. If you want to help out, please join us.
2120 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2121 source code
</a
> is available via git on Alioth. It would also be
2122 great if you could help out with
2123 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2124 it is an important piece of the puzzle to get ZFS working.
</p
>
2129 <title>What is the best multimedia player in Debian?
</title>
2130 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2132 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2133 <description><p
><strong
>Where I set out to figure out which multimedia player in
2134 Debian claim support for most file formats.
</strong
></p
>
2136 <p
>A few years ago, I had a look at the media support for Browser
2137 plugins in Debian, to get an idea which plugins to include in Debian
2138 Edu. I created a script to extract the set of supported MIME types
2139 for each plugin, and used this to find out which multimedia browser
2140 plugin supported most file formats / media types.
2141 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2142 result
</a
> can still be seen on the Debian wiki, even though it have
2143 not been updated for a while. But browser plugins are less relevant
2144 these days, so I thought it was time to look at standalone
2147 <p
>A few days ago I was tired of VLC not being listed as a viable
2148 player when I wanted to play videos from the Norwegian National
2149 Broadcasting Company, and decided to investigate why. The cause is a
2150 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2151 desktop file
</a
>. In the process I wrote a script to compare the set
2152 of MIME types announced in the desktop file and the browser plugin,
2153 only to discover that there is quite a large difference between the
2154 two for VLC. This discovery made me dig up the script I used to
2155 compare browser plugins, and adjust it to compare desktop files
2156 instead, to try to figure out which multimedia player in Debian
2157 support most file formats.
</p
>
2159 <p
>The result can be seen on the Debian Wiki, as
2160 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2161 table listing all MIME types supported by one of the packages included
2162 in the table
</a
>, with the package supporting most MIME types being
2163 listed first in the table.
</p
>
2165 </p
>The best multimedia player in Debian? It is totem, followed by
2166 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2167 kmplayer. Time for the other players to update their announced MIME
2173 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2174 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2175 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2176 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2177 <description>A friend of mine made me aware of
2178 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2179 handheld computer which will be delivered with Debian preinstalled. I
2180 would love to get one of those for my birthday. :)
</p
>
2182 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2183 plugs and many others connectors, and include a full keyboard and a
5"
2184 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2185 day of battery life time, but I have not seen any independent tests
2186 confirming this. The vendor is still collecting preorders, and the
2187 last I heard last night was that
22 more orders were needed before
2188 production started.
</p
>
2190 <p
>As far as I know, this is the first handheld preinstalled with
2191 Debian. Please let me know if you know of any others. Is it the
2192 first computer being sold with Debian preinstalled?
</p
>
2197 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2198 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2199 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2200 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2201 <description><p
>During this weekends
2202 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2203 squashing party and developer gathering
</a
>, we decided to do our part
2204 to make sure there are good books about Debian available in Norwegian
2205 Bokmål, and got in touch with the people behind the
2206 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2207 project
</a
> to get started. If you want to help out, please start
2209 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2210 hosted weblate project page
</a
>, and get in touch using
2211 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2212 translators mailing list
</a
>. Please also check out
2213 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2214 contributors
</a
>.
</p
>
2216 <p
>The book is already available on paper in English, French and
2217 Japanese, and our goal is to get it available on paper in Norwegian
2218 Bokmål too. In addition to the paper edition, there are also EPUB and
2219 Mobi versions available. And there are incomplete translations
2220 available for many more languages.
</p
>
2225 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2226 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2227 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2228 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2229 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2230 packages in Debian, and was quite surprised with what I found. I use
2231 ZFS myself at home, but did not really expect many others to do so.
2232 But I might be wrong.
</p
>
2234 <p
>According to
2235 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2236 results for spl-linux
</a
>, there are
1019 Debian installations, or
2237 0.53% of the population, with the package installed. As far as I know
2238 the only use of the spl-linux package is as a support library for ZFS
2239 on Linux, so I use it here as proxy for measuring the number of ZFS
2240 installation on Linux in Debian. In the kFreeBSD variant of Debian
2241 the ZFS feature is already available, and there
2242 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2243 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2244 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2246 <p
>But even though the Debian project leader Lucas Nussbaum
2247 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2248 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2249 cleared, the package is still not in Debian. The package is again in
2250 the NEW queue. Several uploads have been rejected so far because the
2251 debian/copyright file was incomplete or wrong, but there is no reason
2252 to give up. The current status can be seen on
2253 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2254 team status page
</a
>, and
2255 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2256 source code
</a
> is available on Alioth.
</p
>
2258 <p
>As I want ZFS to be included in next version of Debian to make sure
2259 my home server can function in the future using only official Debian
2260 packages, and the current blocker is to get the debian/copyright file
2261 accepted by the FTP masters in Debian, I decided a while back to try
2262 to help out the team. This was the background for my blog post about
2263 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2264 updating and checking debian/copyright semi-automatically
</a
>, and I
2265 used the techniques I explored there to try to find any errors in the
2266 copyright file. It is not very easy to check every one of the around
2267 2000 files in the source package, but I hope we this time got it
2268 right. If you want to help out, check out the git source and try to
2269 find missing entries in the debian/copyright file.
</p
>
2274 <title>Full battery stats collector is now available in Debian
</title>
2275 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2276 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2277 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2278 <description><p
>Since this morning, the battery-stats package in Debian include an
2279 extended collector that will collect the complete battery history for
2280 later processing and graphing. The original collector store the
2281 battery level as percentage of last full level, while the new
2282 collector also record battery vendor, model, serial number, design
2283 full level, last full level and current battery level. This make it
2284 possible to predict the lifetime of the battery as well as visualise
2285 the energy flow when the battery is charging or discharging.
</p
>
2287 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2288 in the version
0.5.1 package in unstable. Get the new battery level graph
2289 and lifetime prediction by running:
2291 <p
><pre
>
2292 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2293 </pre
></p
>
2295 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2297 <p
>The flow in/out of the battery can be seen by running (no menu
2298 entry yet):
</p
>
2300 <p
><pre
>
2301 /usr/share/battery-stats/battery-stats-graph-flow
2302 </pre
></p
>
2304 <p
>I
'm not quite happy with the way the data is visualised, at least
2305 when there are few data points. The graphs look a bit better with a
2306 few years of data.
</p
>
2308 <p
>A while back one important feature I use in the battery stats
2309 collector broke in Debian. The scripts in
2310 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2311 suspect it happened when Jessie started using systemd, but I do not
2312 know. The issue is reported as
2313 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2314 pm-utils. I managed to work around it by adding an udev rule to call
2315 the collector script every time the power connector is connected and
2316 disconnected. With this fix in place it was finally time to make a
2317 new release of the package, and get it into Debian.
</p
>
2319 <p
>If you are interested in how your laptop battery is doing, please
2321 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2322 in Debian unstable, or rebuild it on Jessie to get it working on
2323 Debian stable. :) The upstream source is available from
2324 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2325 As always, patches are very welcome.
</p
>
2330 <title>Making battery measurements a little easier in Debian
</title>
2331 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2333 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2334 <description><p
>Back in September, I blogged about
2335 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2336 system I wrote to collect statistics about my laptop battery
</a
>, and
2337 how it showed the decay and death of this battery (now replaced). I
2338 created a simple deb package to handle the collection and graphing,
2339 but did not want to upload it to Debian as there were already
2340 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2341 package in Debian
</a
> that should do the same thing, and I did not see
2342 a point of uploading a competing package when battery-stats could be
2343 fixed instead. I reported a few bugs about its non-function, and
2344 hoped someone would step in and fix it. But no-one did.
</p
>
2346 <p
>I got tired of waiting a few days ago, and took matters in my own
2347 hands. The end result is that I am now the new upstream developer of
2348 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2349 battery-stats in Debian, and the package in Debian unstable is finally
2350 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2351 information provided by the Linux kernel. If you install the
2352 battery-stats package from unstable now, you will be able to get a
2353 graph of the current battery fill level, to get some idea about the
2354 status of the battery. The source package build and work just fine in
2355 Debian testing and stable (and probably oldstable too, but I have not
2356 tested). The default graph you get for that system look like this:
</p
>
2358 <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
>
2360 <p
>My plans for the future is to merge my old scripts into the
2361 battery-stats package, as my old scripts collected a lot more details
2362 about the battery. The scripts are merged into the upstream
2363 battery-stats git repository already, but I am not convinced they work
2364 yet, as I changed a lot of paths along the way. Will have to test a
2365 bit more before I make a new release.
</p
>
2367 <p
>I will also consider changing the file format slightly, as I
2368 suspect the way I combine several values into one field might make it
2369 impossible to know the type of the value when using it for processing
2370 and graphing.
</p
>
2372 <p
>If you would like I would like to keep an close eye on your laptop
2373 battery, check out the battery-stats package in
2374 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2376 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2377 I would love some help to improve the system further.
</p
>
2382 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2383 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2384 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2385 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2386 <description><p
>Making packages for Debian requires quite a lot of attention to
2387 details. And one of the details is the content of the
2388 debian/copyright file, which should list all relevant licenses used by
2389 the code in the package in question, preferably in
2390 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2391 readable DEP5 format
</a
>.
</p
>
2393 <p
>For large packages with lots of contributors it is hard to write
2394 and update this file manually, and if you get some detail wrong, the
2395 package is normally rejected by the ftpmasters. So getting it right
2396 the first time around get the package into Debian faster, and save
2397 both you and the ftpmasters some work.. Today, while trying to figure
2398 out what was wrong with
2399 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2400 zfsonlinux copyright file
</a
>, I decided to spend some time on
2401 figuring out the options for doing this job automatically, or at least
2402 semi-automatically.
</p
>
2404 <p
>Lucikly, there are at least two tools available for generating the
2405 file based on the code in the source package,
2406 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2407 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2408 not sure which one of them came first, but both seem to be able to
2409 create a sensible draft file. As far as I can tell, none of them can
2410 be trusted to get the result just right, so the content need to be
2411 polished a bit before the file is OK to upload. I found the debmake
2413 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2414 blog posts from
2014</a
>.
2416 <p
>To generate using debmake, use the -cc option:
2418 <p
><pre
>
2419 debmake -cc
> debian/copyright
2420 </pre
></p
>
2422 <p
>Note there are some problems with python and non-ASCII names, so
2423 this might not be the best option.
</p
>
2425 <p
>The cme option is based on a config parsing library, and I found
2427 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2428 blog post from
2015</a
>. To generate using cme, use the
'update
2429 dpkg-copyright
' option:
2431 <p
><pre
>
2432 cme update dpkg-copyright
2433 </pre
></p
>
2435 <p
>This will create or update debian/copyright. The cme tool seem to
2436 handle UTF-
8 names better than debmake.
</p
>
2438 <p
>When the copyright file is created, I would also like some help to
2439 check if the file is correct. For this I found two good options,
2440 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2441 to focus on license types and file matching, and is able to detect
2442 ineffective blocks in the copyright file. The latter reports missing
2443 copyright holders and years, but was confused by inconsistent license
2444 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2445 fix all issues reported by them before uploading. But I do not know
2446 if the tools and the ftpmasters agree on what is important to fix in a
2447 copyright file, so the package might still be rejected.
</p
>
2449 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2450 will read through the source and try to find all copyright statements.
2451 It is not comparing the result to the content of debian/copyright, but
2452 can be useful when verifying the content of the copyright file.
</p
>
2454 <p
>Are you aware of better tools in Debian to create and update
2455 debian/copyright file. Please let me know, or blog about it on
2456 planet.debian.org.
</p
>
2458 <p
>As usual, if you use Bitcoin and want to show your support of my
2459 activities, please send Bitcoin donations to my address
2460 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2462 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2463 on how to use licensecheck and cdbs to create a draft copyright file
2465 <p
><pre
>
2466 licensecheck --copyright -r `find * -type f` | \
2467 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2468 </pre
></p
>
2470 <p
>He mentioned that he normally check the generated file into the
2471 version control system to make it easier to discover license and
2472 copyright changes in the upstream source. I will try to do the same
2473 with my packages in the future.
</p
>
2475 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2476 against using -quiet for new users, so I removed it from the proposed
2477 command line.
</p
>
2482 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2483 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2484 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2485 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2486 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2487 is taking shape in Debian, and one provided feature is a very
2488 convenient way to tell you which package to install to make a given
2489 firmware file available when the kernel is looking for it. This can
2490 be done using apt-file too, but that is for someone else to blog
2493 <p
>Here is a small recipe to find the package with a given firmware
2494 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2495 picked from the set of firmware announced using appstream in Debian
2496 unstable. In general you would be looking for the firmware requested
2497 by the kernel during kernel module loading. To find the package
2498 providing the example file, do like this:
</p
>
2500 <blockquote
><pre
>
2501 % apt install appstream
2505 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2506 awk
'/Package:/ {print $
2}
'
2509 </pre
></blockquote
>
2511 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2512 appstream wiki
</a
> page to learn how to embed the package metadata in
2513 a way appstream can use.
</p
>
2515 <p
>This same approach can be used to find any package supporting a
2516 given MIME type. This is very useful when you get a file you do not
2517 know how to handle. First find the mime type using
<tt
>file
2518 --mime-type
</tt
>, and next look up the package providing support for
2519 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2520 and you can find all packages handling this type like this:
</p
>
2522 <blockquote
><pre
>
2523 % apt install appstream
2527 % appstreamcli what-provides mimetype image/svg+xml | \
2528 awk
'/Package:/ {print $
2}
'
2550 </pre
></blockquote
>
2552 <p
>I believe the MIME types are fetched from the desktop file for
2553 packages providing appstream metadata.
</p
>
2558 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2559 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2561 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2562 <description><p
>Most people seem not to realise that every time they walk around
2563 with the computerised radio beacon known as a mobile phone their
2564 position is tracked by the phone company and often stored for a long
2565 time (like every time a SMS is received or sent). And if their
2566 computerised radio beacon is capable of running programs (often called
2567 mobile apps) downloaded from the Internet, these programs are often
2568 also capable of tracking their location (if the app requested access
2569 during installation). And when these programs send out information to
2570 central collection points, the location is often included, unless
2571 extra care is taken to not send the location. The provided
2572 information is used by several entities, for good and bad (what is
2573 good and bad, depend on your point of view). What is certain, is that
2574 the private sphere and the right to free movement is challenged and
2575 perhaps even eradicated for those announcing their location this way,
2576 when they share their whereabouts with private and public
2579 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2581 <p
>The phone company logs provide a register of locations to check out
2582 when one want to figure out what the tracked person was doing. It is
2583 unavailable for most of us, but provided to selected government
2584 officials, company staff, those illegally buying information from
2585 unfaithful servants and crackers stealing the information. But the
2586 public information can be collected and analysed, and a free software
2587 tool to do so is called
2588 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2589 discovered it when I read
2590 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2591 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2592 November
2014, and decided to check if it was available in Debian.
2593 The python program was in Debian, but
2594 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2595 Debian
</a
> was completely broken and practically unmaintained. I
2596 uploaded a new version which did not work quite right, but did not
2597 have time to fix it then. This Christmas I decided to finally try to
2598 get Creepy operational in Debian. Now a fixed version is available in
2599 Debian unstable and testing, and almost all Debian specific patches
2601 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2603 <p
>The Creepy program visualises geolocation information fetched from
2604 Twitter, Instagram, Flickr and Google+, and allow one to get a
2605 complete picture of every social media message posted recently in a
2606 given area, or track the movement of a given individual across all
2607 these services. Earlier it was possible to use the search API of at
2608 least some of these services without identifying oneself, but these
2609 days it is impossible. This mean that to use Creepy, you need to
2610 configure it to log in as yourself on these services, and provide
2611 information to them about your search interests. This should be taken
2612 into account when using Creepy, as it will also share information
2613 about yourself with the services.
</p
>
2615 <p
>The picture above show the twitter messages sent from (or at least
2616 geotagged with a position from) the city centre of Oslo, the capital
2617 of Norway. One useful way to use Creepy is to first look at
2618 information tagged with an area of interest, and next look at all the
2619 information provided by one or more individuals who was in the area.
2620 I tested it by checking out which celebrity provide their location in
2621 twitter messages by checkout out who sent twitter messages near a
2622 Norwegian TV station, and next could track their position over time,
2623 making it possible to locate their home and work place, among other
2624 things. A similar technique have been
2625 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2626 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2627 tool to discover lying governments, and a useful tool to help people
2628 understand the value of the private information they provide to the
2631 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2632 it depend on several python modules currently missing in Jessie (at
2633 least python-instagram, python-flickrapi and
2634 python-requests-toolbelt).
</p
>
2636 <p
>(I have uploaded
2637 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2638 screenshots.debian.net
</a
> and licensed it under the same terms as the
2639 Creepy program in Debian.)
</p
>
2644 <title>Always download Debian packages using Tor - the simple recipe
</title>
2645 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2646 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2647 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2648 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2649 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2650 that those listening on the Internet lines would have good reason to
2651 believe a computer have a given security hole
</a
> if it download a
2652 security fix from a Debian mirror. This is a good reason to always
2653 use encrypted connections to the Debian mirror, to make sure those
2654 listening do not know which IP address to attack. In August, Richard
2655 Hartmann observed that encryption was not enough, when it was possible
2656 to interfere download size to security patches or the fact that
2657 download took place shortly after a security fix was released, and
2658 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2659 to always use Tor to download packages from the Debian mirror
</a
>. He
2660 was not the first to propose this, as the
2661 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2662 package by Tim Retout already existed to make it easy to convince apt
2663 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2664 aware of that package when I read the blog post from Richard.
</p
>
2666 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2667 sysadmins, and he set up a Tor hidden service on one of the central
2668 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2669 it possible to download packages directly between two tor nodes,
2670 making sure the network traffic always were encrypted.
</p
>
2672 <p
>Here is a short recipe for enabling this on your machine, by
2673 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2674 urls with tor+http and tor+https, and using the hidden service instead
2675 of the official Debian mirror site. I recommend installing
2676 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2677 done in /etc/.
</p
>
2679 <blockquote
><pre
>
2680 apt install apt-transport-tor
2681 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2682 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2683 </pre
></blockquote
>
2685 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2686 the sed commands for these too. The sed command is assuming your are
2687 using the ftp.debian.org Debian mirror. Adjust the command (or just
2688 edit the file manually) to match your mirror.
</p
>
2690 <p
>This work in Debian Jessie and later. Note that tools like
2691 <tt
>apt-file
</tt
> only recently started using the apt transport
2692 system, and do not work with these tor+http URLs. For
2693 <tt
>apt-file
</tt
> you need the version currently in experimental,
2694 which need a recent apt version currently only in unstable. So if you
2695 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2697 <p
>Another advantage from this change is that your machine will start
2698 using Tor regularly and at fairly random intervals (every time you
2699 update the package lists or upgrade or install a new package), thus
2700 masking other Tor traffic done from the same machine. Using Tor will
2701 become normal for the machine in question.
</p
>
2703 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2704 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2705 enabled. It would be great if it was the default on any Debian
2711 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2712 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2713 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2714 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2715 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2716 call the car license plate numbers in those days. I would write the
2717 numbers down in my little book and compare notes with the other kids
2718 to see how many region codes we had seen and if we had seen some
2719 exotic or special region codes and numbers. It was a fun game to pass
2720 time, as we kids have plenty of it.
</p
>
2722 <p
>A few days I came across
2723 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2724 project
</a
>, a free software project to automatically discover and
2725 report license plates in images and video streams, and provide the
2726 "car numbers
" in a machine readable format. I
've been looking for
2727 such system for a while now, because I believe it is a bad idea that the
2728 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2729 number plate recognition
</a
> tool only is available in the hands of
2730 the powerful, and want it to be available also for the powerless to
2731 even the score when it comes to surveillance and sousveillance. I
2732 discovered the developer
2733 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2734 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2735 help him get it into shape to get the package uploaded into the Debian
2738 <p
>Today we finally managed to get the package into shape and uploaded
2739 it into Debian, where it currently
2740 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2741 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2743 <p
>I guess you are wondering why on earth such tool would be useful
2744 for the common folks, ie those not running a large government
2745 surveillance system? Well, I plan to put it in a computer on my bike
2746 and in my car, tracking the cars nearby and allowing me to be notified
2747 when number plates on my watch list are discovered. Another use case
2748 was suggested by a friend of mine, who wanted to set it up at his home
2749 to open the car port automatically when it discovered the plate on his
2750 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2751 capable of placing his license plate number of a piece of cardboard to
2752 open his car port, men replied that it was always unlocked anyway. I
2753 guess for such use case it make sense. I am sure there are other use
2754 cases too, for those with imagination and a vision.
</p
>
2756 <p
>If you want to build your own version of the Debian package, check
2757 out the upstream git source and symlink ./distros/debian to ./debian/
2758 before running
"debuild
" to build the source. Or wait a bit until the
2759 package show up in unstable.
</p
>
2764 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2765 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2766 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2767 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2768 <description><p
>Around three years ago, I created
2769 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2770 system
</a
> to get a more practical solution in Debian for handing
2771 hardware related packages. A GUI system in the isenkram package will
2772 present a pop-up dialog when some hardware dongle supported by
2773 relevant packages in Debian is inserted into the machine. The same
2774 lookup mechanism to detect packages is available as command line
2775 tools in the isenkram-cli package. In addition to mapping hardware,
2776 it will also map kernel firmware files to packages and make it easy to
2777 install needed firmware packages automatically. The key for this
2778 system to work is a good way to map hardware to packages, in other
2779 words, allow packages to announce what hardware they will work
2782 <p
>I started by providing data files in the isenkram source, and
2783 adding code to download the latest version of these data files at run
2784 time, to ensure every user had the most up to date mapping available.
2785 I also added support for storing the mapping in the Packages file in
2786 the apt repositories, but did not push this approach because while I
2787 was trying to figure out how to best store hardware/package mappings,
2788 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2789 appstream system
</a
> was announced. I got in touch and suggested to
2790 add the hardware mapping into that data set to be able to use
2791 appstream as a data source, and this was accepted at least for the
2792 Debian version of appstream.
</p
>
2794 <p
>A few days ago using appstream in Debian for this became possible,
2795 and today I uploaded a new version
0.20 of isenkram adding support for
2796 appstream as a data source for mapping hardware to packages. The only
2797 package so far using appstream to announce its hardware support is my
2798 pymissile package. I got help from Matthias Klumpp with figuring out
2799 how do add the required
2800 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2801 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2802 this content:
</p
>
2804 <blockquote
><pre
>
2805 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2806 &lt;component
&gt;
2807 &lt;id
&gt;pymissile
&lt;/id
&gt;
2808 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2809 &lt;name
&gt;pymissile
&lt;/name
&gt;
2810 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2811 &lt;description
&gt;
2813 Pymissile provides a curses interface to control an original
2814 Marks and Spencer / Striker USB Missile Launcher, as well as a
2815 motion control script to allow a webcamera to control the
2818 &lt;/description
&gt;
2819 &lt;provides
&gt;
2820 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2821 &lt;/provides
&gt;
2822 &lt;/component
&gt;
2823 </pre
></blockquote
>
2825 <p
>The key for isenkram is the component/provides/modalias value,
2826 which is a glob style match rule for hardware specific strings
2827 (modalias strings) provided by the Linux kernel. In this case, it
2828 will map to all USB devices with vendor code
1130 and product code
2831 <p
>Note, it is important that the license of all the metadata files
2832 are compatible to have permissions to aggregate them into archive wide
2833 appstream files. Matthias suggested to use MIT or BSD licenses for
2834 these files. A challenge is figuring out a good id for the data, as
2835 it is supposed to be globally unique and shared across distributions
2836 (in other words, best to coordinate with upstream what to use). But
2837 it can be changed later or, so we went with the package name as
2838 upstream for this project is dormant.
</p
>
2840 <p
>To get the metadata file installed in the correct location for the
2841 mirror update scripts to pick it up and include its content the
2842 appstream data source, the file must be installed in the binary
2843 package under /usr/share/appdata/. I did this by adding the following
2844 line to debian/pymissile.install:
</p
>
2846 <blockquote
><pre
>
2847 debian/pymissile.metainfo.xml usr/share/appdata
2848 </pre
></blockquote
>
2850 <p
>With that in place, the command line tool isenkram-lookup will list
2851 all packages useful on the current computer automatically, and the GUI
2852 pop-up handler will propose to install the package not already
2853 installed if a hardware dongle is inserted into the machine in
2856 <p
>Details of the modalias field in appstream is available from the
2857 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2859 <p
>To locate the modalias values of all hardware present in a machine,
2860 try running this command on the command line:
</p
>
2862 <blockquote
><pre
>
2863 cat $(find /sys/devices/|grep modalias)
2864 </pre
></blockquote
>
2866 <p
>To learn more about the isenkram system, please check out
2867 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2868 blog posts tagged isenkram
</a
>.
</p
>
2873 <title>The GNU General Public License is not magic pixie dust
</title>
2874 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2875 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2876 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2877 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2878 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2879 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2880 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2881 I quote the blog post from Paul in full here with his permission:
<p
>
2885 <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
>
2888 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2890 The first step is to choose a
2891 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2894 The next step is, when someone fails to follow that copyleft license,
2895 <b
>it must be enforced
</b
><br/
>
2897 and its a simple fact of our modern society that such type of
2900 is incredibly expensive to do and incredibly difficult to do.
2903 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2904 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2905 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2906 0x57</a
></small
></p
>
2908 <p
>As the Debian Website
2909 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2910 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2911 imply, public domain and permissively licensed software can lead to
2912 the production of more proprietary software as people discover useful
2913 software, extend it and or incorporate it into their hardware or
2914 software products. Copyleft licenses such as the GNU GPL were created
2915 to close off this avenue to the production of proprietary software but
2916 such licenses are not enough. With the ongoing adoption of Free
2917 Software by individuals and groups, inevitably the community
's
2918 expectations of license compliance are violated, usually out of
2919 ignorance of the way Free Software works, but not always. As Karen
2920 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2921 Freedom
">FaiF
</a
>
2922 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2923 copyleft is nothing if no-one is willing and able to stand up in court
2924 to protect it. The reality of today
's world is that legal
2925 representation is expensive, difficult and time consuming. With
2926 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2927 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2928 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2929 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2930 of the Linux project, Debian and other groups against GPL violations.
2931 In March the SFC supported a
2932 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2933 by Christoph Hellwig
</a
> against VMware for refusing to
2934 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2935 with the GPL
</a
> in relation to their use of parts of the Linux
2936 kernel. Since then two of their sponsors pulled corporate funding and
2938 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2939 or cancelled their talks
</a
>. As a result they have decided to rely
2940 less on corporate funding and more on the broad community of
2941 individuals who support Free Software and copyleft. So the SFC has
2942 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2943 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2944 a community of folks who stand up for copyleft and the GPL by
2945 supporting their work on promoting and supporting copyleft and Free
2948 <p
>If you support Free Software,
2949 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2950 what the SFC do, agree with their
2951 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2952 principles
</a
>, are happy about their
2953 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2954 work on a project that is an SFC
2955 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2956 just want to stand up for copyleft, please join
2957 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2958 Allan Webber
</a
>,
2959 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2961 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2962 Bacon
</a
>, myself and
2963 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2965 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2966 next week your donation will be
2967 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2968 by an anonymous donor. Please also consider asking your employer to
2969 match your donation or become a sponsor of SFC. Don
't forget to
2970 spread the word about your support for SFC via email, your blog and or
2971 social media accounts.
</p
>
2975 <p
>I agree with Paul on this topic and just signed up as a Supporter
2976 of Software Freedom Conservancy myself. Perhaps you should be a
2977 supporter too?
</p
>
2982 <title>PGP key transition statement for key EE4E02F9
</title>
2983 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2984 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2985 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2986 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2987 set it up properly. I wanted to generate it offline and have it
2988 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2989 smart card
</a
> for daily use, and learning how to do it and finding
2990 time to sit down with an offline machine almost took forever. But
2991 finally I
've been able to complete the process, and have now moved
2992 from my old GPG key to a new GPG key. See
2993 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2994 full transition statement, signed with both my old and new key
</a
> for
2995 the details. This is my new key:
</p
>
2998 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2999 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
3000 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
3001 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
3002 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
3003 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
3004 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
3007 <p
>The key can be downloaded from the OpenPGP key servers, signed by
3008 my old key.
</p
>
3010 <p
>If you signed my old key
3011 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
3012 I
'd very much appreciate a signature on my new key, details and
3013 instructions in the transition statement. I m happy to reciprocate if
3014 you have a similarly signed transition statement to present.
</p
>
3019 <title>The life and death of a laptop battery
</title>
3020 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
3021 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
3022 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
3023 <description><p
>When I get a new laptop, the battery life time at the start is OK.
3024 But this do not last. The last few laptops gave me a feeling that
3025 within a year, the life time is just a fraction of what it used to be,
3026 and it slowly become painful to use the laptop without power connected
3027 all the time. Because of this, when I got a new Thinkpad X230 laptop
3028 about two years ago, I decided to monitor its battery state to have
3029 more hard facts when the battery started to fail.
</p
>
3031 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
3033 <p
>First I tried to find a sensible Debian package to record the
3034 battery status, assuming that this must be a problem already handled
3035 by someone else. I found
3036 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
3037 which collects statistics from the battery, but it was completely
3038 broken. I sent a few suggestions to the maintainer, but decided to
3039 write my own collector as a shell script while I waited for feedback
3041 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3042 blog post about the battery development on a MacBook Air
</a
> I also
3044 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3045 available in Debian.
</p
>
3047 <p
>I started my collector
2013-
07-
15, and it has been collecting
3048 battery stats ever since. Now my
3049 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3050 measurements, from the time the battery was working great until now,
3051 when it is unable to charge above
7% of original capacity. My
3052 collector shell script is quite simple and look like this:
</p
>
3057 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3059 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3060 logfile=/var/log/hjemmenett-battery-status.log
3062 files=
"manufacturer model_name technology serial_number \
3063 energy_full energy_full_design energy_now cycle_count status
"
3065 if [ ! -e
"$logfile
" ] ; then
3067 printf
"timestamp,
"
3069 printf
"%s,
" $f
3072 )
> "$logfile
"
3076 # Print complete message in one echo call, to avoid race condition
3077 # when several log processes run in parallel.
3078 msg=$(printf
"%s,
" $(date +%s); \
3079 for f in $files; do \
3080 printf
"%s,
" $(cat $f); \
3082 echo
"$msg
"
3085 cd /sys/class/power_supply
3088 (cd $bat
&& log_battery
>> "$logfile
")
3092 <p
>The script is called when the power management system detect a
3093 change in the power status (power plug in or out), and when going into
3094 and out of hibernation and suspend. In addition, it collect a value
3095 every
10 minutes. This make it possible for me know when the battery
3096 is discharging, charging and how the maximum charge change over time.
3097 The code for the Debian package
3098 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3099 available on github
</a
>.
</p
>
3101 <p
>The collected log file look like this:
</p
>
3104 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3105 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3107 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3108 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3111 <p
>I wrote a small script to create a graph of the charge development
3112 over time. This graph depicted above show the slow death of my laptop
3115 <p
>But why is this happening? Why are my laptop batteries always
3116 dying in a year or two, while the batteries of space probes and
3117 satellites keep working year after year. If we are to believe
3118 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3119 University
</a
>, the cause is me charging the battery whenever I have a
3120 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3121 all the time, but to stay below
90% of full charge most of the time.
3122 I
've been told that the Tesla electric cars
3123 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3124 the charge of their batteries to
80%
</a
>, with the option to charge to
3125 100% when preparing for a longer trip (not that I would want a car
3126 like Tesla where rights to privacy is abandoned, but that is another
3127 story), which I guess is the option we should have for laptops on
3128 Linux too.
</p
>
3130 <p
>Is there a good and generic way with Linux to tell the battery to
3131 stop charging at
80%, unless requested to charge to
100% once in
3132 preparation for a longer trip? I found
3133 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3134 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3135 80%
</a
>, but could not get it to work (kernel module refused to
3138 <p
>I wonder why the battery capacity was reported to be more than
100%
3139 at the start. I also wonder why the
"full capacity
" increases some
3140 times, and if it is possible to repeat the process to get the battery
3141 back to design capacity. And I wonder if the discharge and charge
3142 speed change over time, or if this stay the same. I did not yet try
3143 to write a tool to calculate the derivative values of the battery
3144 level, but suspect some interesting insights might be learned from
3147 <p
>Update
2015-
09-
24: I got a tip to install the packages
3148 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3149 packages instead of the tp-smapi-dkms package I had tried to use
3150 initially, and use
'tlp setcharge
40 80' to change when charging start
3151 and stop. I
've done so now, but expect my existing battery is toast
3152 and need to be replaced. The proposal is unfortunately Thinkpad
3158 <title>New laptop - some more clues and ideas based on feedback
</title>
3159 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3160 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3161 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3162 <description><p
>Several people contacted me after my previous blog post about my
3163 need for a new laptop, and provided very useful feedback. I wish to
3164 thank every one of these. Several pointed me to the possibility of
3165 fixing my X230, and I am already in the process of getting Lenovo to
3166 do so thanks to the on site, next day support contract covering the
3167 machine. But the battery is almost useless (I expect to replace it
3168 with a non-official battery) and I do not expect the machine to live
3169 for many more years, so it is time to plan its replacement. If I did
3170 not have a support contract, it was suggested to find replacement parts
3171 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3172 might present a language barrier as I do not understand French.
</p
>
3174 <p
>One tip I got was to use the
3175 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3176 compare laptop models. It seem to have more models available than
3177 prisjakt.no. Another tip I got from someone I know have similar
3178 keyboard preferences was that the HP EliteBook
840 keyboard is not
3179 very good, and this matches my experience with earlier EliteBook
3180 keyboards I tested. Because of this, I will not consider it any further.
3182 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3183 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3184 (which is missing from the X240), and is working fairly well with
3185 Debian Sid/Unstable according to
3186 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3187 got on the keyboard quality are not consistent. Some say the keyboard
3188 is good, others say it is ok, while others say it is not very good.
3189 Those with experience from X41 and and X60 agree that the X250
3190 keyboard is not as good as those trusty old laptops, and suggest I
3191 keep and fix my X230 instead of upgrading, or get a used X230 to
3192 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3193 activity and battery status, which is very convenient on my X230. I
'm
3194 also told that the CPU fan is running very often, making it a bit
3195 noisy. In any case, the X250 do not work out of the box with Debian
3196 Stable/Jessie, one of my requirements.
</p
>
3198 <p
>I have also gotten a few vendor proposals, one was
3199 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3200 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3201 The latter look very attractive to me.
</p
>
3203 <p
>Again, thank you all for the very useful feedback. It help a lot
3204 as I keep looking for a replacement.
</p
>
3206 <p
>Update
2015-
07-
06: I was recommended to check out the
3207 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3209 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3210 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3215 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3216 <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>
3217 <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>
3218 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3219 <description><p
>My primary work horse laptop is failing, and will need a
3220 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3221 started flickering yesterday, and I suspect the cause is a broken
3222 cable, as changing the angle of the screen some times get rid of the
3223 flickering.
</p
>
3225 <p
>My requirements have not really changed since I bought it, and is
3227 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3228 described them in
2013</a
>. The last time I bought a laptop, I had
3230 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3231 where I could select at least a few of the requirements (mouse pin,
3232 wifi, weight) and go through the rest manually. Three button mouse
3233 and a good keyboard is not available as an option, and all the three
3234 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3235 G2) lack three mouse buttons). It is also unclear to me how good the
3236 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3237 the keyboard, even if the quality and robustness in the X series have
3238 deteriorated since X41.
</p
>
3240 <p
>I wonder how I can find a sensible laptop when none of the options
3241 seem sensible to me? Are there better services around to search the
3242 set of available laptops for features? Please send me an email if you
3243 have suggestions.
</p
>
3245 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3246 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3247 of endorsed hardware
</a
>, which is useful background information.
</p
>
3252 <title>How to stay with sysvinit in Debian Jessie
</title>
3253 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3254 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3255 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3256 <description><p
>By now, it is well known that Debian Jessie will not be using
3257 sysvinit as its boot system by default. But how can one keep using
3258 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3260 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3261 Schubert
</a
> and
3262 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3265 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3266 keep sysvinit as your boot system, create a file
3267 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3268 you upgrade:
</p
>
3270 <p
><blockquote
><pre
>
3271 Package: systemd-sysv
3272 Pin: release o=Debian
3274 </pre
></blockquote
><p
>
3276 <p
>This file content will tell apt and aptitude to not consider
3277 installing systemd-sysv as part of any installation and upgrade
3278 solution when resolving dependencies, and thus tell it to avoid
3279 systemd as a default boot system. The end result should be that the
3280 upgraded system keep using sysvinit.
</p
>
3282 <p
>If you are installing Jessie for the first time, there is no way to
3283 get sysvinit installed by default (debootstrap used by
3284 debian-installer have no option for this), but one can tell the
3285 installer to switch to sysvinit before the first boot. Either by
3286 using a kernel argument to the installer, or by adding a line to the
3287 preseed file used. First, the kernel command line argument:
3289 <p
><blockquote
><pre
>
3290 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3291 </pre
></blockquote
><p
>
3293 <p
>Next, the line to use in a preseed file:
</p
>
3295 <p
><blockquote
><pre
>
3296 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3297 </pre
></blockquote
><p
>
3299 <p
>One can of course also do this after the first boot by installing
3300 the sysvinit-core package.
</p
>
3302 <p
>I recommend only using sysvinit if you really need it, as the
3303 sysvinit boot sequence in Debian have several hardware specific bugs
3304 on Linux caused by the fact that it is unpredictable when hardware
3305 devices show up during boot. But on the other hand, the new default
3306 boot system still have a few rough edges I hope will be fixed before
3307 Jessie is released.
</p
>
3309 <p
>Update
2014-
11-
26: Inspired by
3310 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3311 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3317 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3318 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3320 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3321 <description><p
>The right to communicate with your friends and family in private,
3322 without anyone snooping, is a right every citicen have in a liberal
3323 democracy. But this right is under serious attack these days.
</p
>
3325 <p
>A while back it occurred to me that one way to make the dragnet
3326 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3327 the whisleblower Snowden) more expensive for Internet email,
3328 is to deliver all email using SMTP via Tor. Such SMTP option would be
3329 a nice addition to the FreedomBox project if we could send email
3330 between FreedomBox machines without leaking metadata about the emails
3331 to the people peeking on the wire. I
3332 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3333 this on the FreedomBox project mailing list in October
</a
> and got a
3334 lot of useful feedback and suggestions. It also became obvious to me
3335 that this was not a novel idea, as the same idea was tested and
3336 documented by Johannes Berg as early as
2006, and both
3337 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3338 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3339 propose a similar method / protocol to pass emails between users.
</p
>
3341 <p
>To implement such system one need to set up a Tor hidden service
3342 providing the SMTP protocol on port
25, and use email addresses
3343 looking like username@hidden-service-name.onion. With such addresses
3344 the connections to port
25 on hidden-service-name.onion using Tor will
3345 go to the correct SMTP server. To do this, one need to configure the
3346 Tor daemon to provide the hidden service and the mail server to accept
3347 emails for this .onion domain. To learn more about Exim configuration
3348 in Debian and test the design provided by Johannes Berg in his FAQ, I
3349 set out yesterday to create a Debian package for making it trivial to
3350 set up such SMTP over Tor service based on Debian. Getting it to work
3351 were fairly easy, and
3352 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3353 source code for the Debian package
</a
> is available from github. I
3354 plan to move it into Debian if further testing prove this to be a
3355 useful approach.
</p
>
3357 <p
>If you want to test this, set up a blank Debian machine without any
3358 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3359 get rid of exim4). Install tor, clone the git repository mentioned
3360 above, build the deb and install it on the machine. Next, run
3361 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3362 the instructions to get the service up and running. Restart tor and
3363 exim when it is done, and test mail delivery using swaks like
3366 <p
><blockquote
><pre
>
3367 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3368 --to fbx@dutlqrrmjhtfa3vp.onion
3369 </pre
></blockquote
></p
>
3371 <p
>This will test the SMTP delivery using tor. Replace the email
3372 address with your own address to test your server. :)
</p
>
3374 <p
>The setup procedure is still to complex, and I hope it can be made
3375 easier and more automatic. Especially the tor setup need more work.
3376 Also, the package include a tor-smtp tool written in C, but its task
3377 should probably be rewritten in some script language to make the deb
3378 architecture independent. It would probably also make the code easier
3379 to review. The tor-smtp tool currently need to listen on a socket for
3380 exim to talk to it and is started using xinetd. It would be better if
3381 no daemon and no socket is needed. I suspect it is possible to get
3382 exim to run a command line tool for delivery instead of talking to a
3383 socket, and hope to figure out how in a future version of this
3386 <p
>Until I wipe my test machine, I can be reached using the
3387 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3388 SMTorP. :)
</p
>
3393 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3394 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3395 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3396 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3397 <description><p
>If you ever had to moderate a mailman list, like the ones on
3398 alioth.debian.org, you know the web interface is fairly slow to
3399 operate. First you visit one web page, enter the moderation password
3400 and get a new page shown with a list of all the messages to moderate
3401 and various options for each email address. This take a while for
3402 every list you moderate, and you need to do it regularly to do a good
3403 job as a list moderator. But there is a quick alternative,
3404 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3405 listadmin program
</a
>. It allow you to check lists for new messages
3406 to moderate in a fraction of a second. Here is a test run on two
3407 lists I recently took over:
</p
>
3409 <p
><blockquote
><pre
>
3410 % time listadmin xiph
3411 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3412 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3418 </pre
></blockquote
></p
>
3420 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3421 there are no message in the moderation queue. Every morning I
3422 currently moderate
68 mailman lists, and it normally take around two
3423 minutes. When I took over the two pkg-xiph lists above a few days
3424 ago, there were
400 emails waiting in the moderator queue. It took me
3425 less than
15 minutes to process them all using the listadmin
3428 <p
>If you install
3429 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3430 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3431 with content like this, the moderation task is a breeze:
</p
>
3433 <p
><blockquote
><pre
>
3434 username username@example.org
3437 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3440 adminurl https://{domain}/mailman/admindb/{list}
3441 mailman-list@lists.example.com
3444 other-list@otherserver.example.org
3445 </pre
></blockquote
></p
>
3447 <p
>There are other options to set as well. Check the manual page to
3448 learn the details.
</p
>
3450 <p
>If you are forced to moderate lists on a mailman installation where
3451 the SSL certificate is self signed or not properly signed by a
3452 generally accepted signing authority, you can set a environment
3453 variable when calling listadmin to disable SSL verification:
</p
>
3455 <p
><blockquote
><pre
>
3456 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3457 </pre
></blockquote
></p
>
3459 <p
>If you want to moderate a subset of the lists you take care of, you
3460 can provide an argument to the listadmin script like I do in the
3461 initial screen dump (the xiph argument). Using an argument, only
3462 lists matching the argument string will be processed. This make it
3463 quick to accept messages if you notice the moderation request in your
3466 <p
>Without the listadmin program, I would never be the moderator of
68
3467 mailing lists, as I simply do not have time to spend on that if the
3468 process was any slower. The listadmin program have saved me hours of
3469 time I could spend elsewhere over the years. It truly is nice free
3472 <p
>As usual, if you use Bitcoin and want to show your support of my
3473 activities, please send Bitcoin donations to my address
3474 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3476 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3477 configuration example. Also, I
've been told that the
3478 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3484 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3485 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3486 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3487 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3488 <description><p
>When PXE installing laptops with Debian, I often run into the
3489 problem that the WiFi card require some firmware to work properly.
3490 And it has been a pain to fix this using preseeding in Debian.
3491 Normally something more is needed. But thanks to
3492 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3493 package
</a
> and its recent tasksel extension, it has now become easy
3494 to do this using simple preseeding.
</p
>
3496 <p
>The isenkram-cli package provide tasksel tasks which will install
3497 firmware for the hardware found in the machine (actually, requested by
3498 the kernel modules for the hardware). (It can also install user space
3499 programs supporting the hardware detected, but that is not the focus
3500 of this story.)
</p
>
3502 <p
>To get this working in the default installation, two preeseding
3503 values are needed. First, the isenkram-cli package must be installed
3504 into the target chroot (aka the hard drive) before tasksel is executed
3505 in the pkgsel step of the debian-installer system. This is done by
3506 preseeding the base-installer/includes debconf value to include the
3507 isenkram-cli package. The package name is next passed to debootstrap
3508 for installation. With the isenkram-cli package in place, tasksel
3509 will automatically use the isenkram tasks to detect hardware specific
3510 packages for the machine being installed and install them, because
3511 isenkram-cli contain tasksel tasks.
</p
>
3513 <p
>Second, one need to enable the non-free APT repository, because
3514 most firmware unfortunately is non-free. This is done by preseeding
3515 the apt-mirror-setup step. This is unfortunate, but for a lot of
3516 hardware it is the only option in Debian.
</p
>
3518 <p
>The end result is two lines needed in your preseeding file to get
3519 firmware installed automatically by the installer:
</p
>
3521 <p
><blockquote
><pre
>
3522 base-installer base-installer/includes string isenkram-cli
3523 apt-mirror-setup apt-setup/non-free boolean true
3524 </pre
></blockquote
></p
>
3526 <p
>The current version of isenkram-cli in testing/jessie will install
3527 both firmware and user space packages when using this method. It also
3528 do not work well, so use version
0.15 or later. Installing both
3529 firmware and user space packages might give you a bit more than you
3530 want, so I decided to split the tasksel task in two, one for firmware
3531 and one for user space programs. The firmware task is enabled by
3532 default, while the one for user space programs is not. This split is
3533 implemented in the package currently in unstable.
</p
>
3535 <p
>If you decide to give this a go, please let me know (via email) how
3536 this recipe work for you. :)
</p
>
3538 <p
>So, I bet you are wondering, how can this work. First and
3539 foremost, it work because tasksel is modular, and driven by whatever
3540 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3541 isenkram-cli package place two files for tasksel to find. First there
3542 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3544 <p
><blockquote
><pre
>
3545 Task: isenkram-packages
3547 Description: Hardware specific packages (autodetected by isenkram)
3548 Based on the detected hardware various hardware specific packages are
3550 Test-new-install: show show
3552 Packages: for-current-hardware
3554 Task: isenkram-firmware
3556 Description: Hardware specific firmware packages (autodetected by isenkram)
3557 Based on the detected hardware various hardware specific firmware
3558 packages are proposed.
3559 Test-new-install: mark show
3561 Packages: for-current-hardware-firmware
3562 </pre
></blockquote
></p
>
3564 <p
>The key parts are Test-new-install which indicate how the task
3565 should be handled and the Packages line referencing to a script in
3566 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3567 list of packages to install. The for-current-hardware-firmware script
3568 look like this to list relevant firmware for the machine:
3570 <p
><blockquote
><pre
>
3573 PATH=/usr/sbin:$PATH
3575 isenkram-autoinstall-firmware -l
3576 </pre
></blockquote
></p
>
3578 <p
>With those two pieces in place, the firmware is installed by
3579 tasksel during the normal d-i run. :)
</p
>
3581 <p
>If you want to test what tasksel will install when isenkram-cli is
3582 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3583 --new-install
</tt
> to get the list of packages that tasksel would
3586 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3587 pilots in testing this feature, as isenkram is used there now to
3588 install firmware, replacing the earlier scripts.
</p
>
3593 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3594 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3595 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3596 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3597 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3598 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3599 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3600 on a screen normally showing the bread types and prizes:
</p
>
3602 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3604 <p
>If it had booted as it was supposed to, I would never had known
3605 about this hidden Linux installation. It is interesting what
3606 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3611 <title>New lsdvd release version
0.17 is ready
</title>
3612 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3613 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3614 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3615 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3616 got a new set of developers a few weeks ago, after the original
3617 developer decided to step down and pass the project to fresh blood.
3618 This project is now maintained by Petter Reinholdtsen and Steve
3621 <p
>I just wrapped up
3622 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3623 new lsdvd release
</a
>, available in git or from
3624 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3625 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3630 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3631 <li
>Check for garbage in the program chains, which indicate that a track is
3632 non-existant, to work around additional copy protection
</li
>
3633 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3634 <li
>Fix pallete display of first entry
</li
>
3635 <li
>Fix include orders
</li
>
3636 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3637 <li
>Fix the chapter count
</li
>
3638 <li
>Make sure the array size and the array limit used when initialising
3639 the palette size is the same.
</li
>
3640 <li
>Fix array printing.
</li
>
3641 <li
>Correct subsecond calculations.
</li
>
3642 <li
>Add sector information to the output format.
</li
>
3643 <li
>Clean up code to be closer to ANSI C and compile without warnings
3644 with more GCC compiler warnings.
</li
>
3648 <p
>This change bring together patches for lsdvd in use in various
3649 Linux and Unix distributions, as well as patches submitted to the
3650 project the last nine years. Please check it out. :)
</p
>
3655 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3656 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3657 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3658 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3659 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3660 project
</a
> provide a Linux solution for schools, including a
3661 powerful desktop with education software, a central server providing
3662 web pages, user database, user home directories, central login and PXE
3663 boot of both clients without disk and the installation to install Debian
3664 Edu on machines with disk (and a few other services perhaps to small
3665 to mention here). We in the Debian Edu team are currently working on
3666 the Jessie based version, trying to get everything in shape before the
3667 freeze, to avoid having to maintain our own package repository in the
3669 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3670 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3671 work left. Some fatal problems block testing, breaking the installer,
3672 but it is possible to work around these to get anyway. Here is a
3673 recipe on how to get the installation limping along.
</p
>
3675 <p
>First, download the test ISO via
3676 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3677 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3679 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3680 The ISO build was broken on Tuesday, so we do not get a new ISO every
3681 12 hours or so, but thankfully the ISO we already got we are able to
3682 install with some tweaking.
</p
>
3684 <p
>When you get to the Debian Edu profile question, go to tty2
3685 (use Alt-Ctrl-F2), run
</p
>
3687 <p
><blockquote
><pre
>
3688 nano /usr/bin/edu-eatmydata-install
3689 </pre
></blockquote
></p
>
3691 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3692 optimization. Return to the installation, select the profile you want
3693 and continue. Without this change, exim4-config will fail to install
3694 due to a known bug in eatmydata.
</p
>
3696 <p
>When you get the grub question at the end, answer /dev/sda (or if
3697 this do not work, figure out what your correct value would be. All my
3698 test machines need /dev/sda, so I have no advice if it do not fit
3699 your need.
</p
>
3701 <p
>If you installed a profile including a graphical desktop, log in as
3702 root after the initial boot from hard drive, and install the
3703 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3704 or mate. If you want several desktop options, install more than one
3705 metapackage. Once this is done, reboot and you should have a working
3706 graphical login screen. This workaround should no longer be needed
3707 once the education-tasks package version
1.801 enter testing in two
3710 <p
>I believe the ISO build will start working on two days when the new
3711 tasksel package enter testing and Steve McIntyre get a chance to
3712 update the debian-cd git repository. The eatmydata, grub and desktop
3713 issues are already fixed in unstable and testing, and should show up
3714 on the ISO as soon as the ISO build start working again. Well the
3715 eatmydata optimization is really just disabled. The proper fix
3716 require an upload by the eatmydata maintainer applying the patch
3717 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3718 The rest have proper fixes in unstable.
</p
>
3720 <p
>I hope this get you going with the installation testing, as we are
3721 quickly running out of time trying to get our Jessie based
3722 installation ready before the distribution freeze in a month.
</p
>
3727 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3728 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3729 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3730 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3731 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3732 to handle my fairly large DVD collection. It is a nice command line
3733 tool to get details about a DVD, like title, tracks, track length,
3734 etc, in XML, Perl or human readable format. But lsdvd have not seen
3735 any new development since
2006 and had a few irritating bugs affecting
3736 its use with some DVDs. Upstream seemed to be dead, and in January I
3737 sent a small probe asking for a version control repository for the
3738 project, without any reply. But I use it regularly and would like to
3739 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3740 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3741 the project admin, and after getting a reply from him explaining that
3742 he was no longer interested in the project, I asked if I could take
3743 over. And yesterday, I became project admin.
</p
>
3745 <p
>I
've been in touch with a Gentoo developer and the Debian
3746 maintainer interested in joining forces to maintain the upstream
3747 project, and I hope we can get a new release out fairly quickly,
3748 collecting the patches spread around on the internet into on place.
3749 I
've added the relevant Debian patches to the freshly created git
3750 repository, and expect the Gentoo patches to make it too. If you got
3751 a DVD collection and care about command line tools, check out
3752 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3753 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3754 list
</a
>. :)
</p
>
3759 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3760 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3762 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3763 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3764 a lot quicker. When we install more than
2000 packages in
3765 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3766 tasksel in the installer, unpacking the binary packages take forever.
3767 A part of the slow I/O issue was discussed in
3768 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3769 much file system sync-ing done by dpkg, which is the package
3770 responsible for unpacking the binary packages. Other parts (like code
3771 executed by postinst scripts) might also sync to disk during
3772 installation. All this sync-ing to disk do not really make sense to
3773 me. If the machine crash half-way through, I start over, I do not try
3774 to salvage the half installed system. So the failure sync-ing is
3775 supposed to protect against, hardware or system crash, is not really
3776 relevant while the installer is running.
</p
>
3778 <p
>A few days ago, I thought of a way to get rid of all the file
3779 system sync()-ing in a fairly non-intrusive way, without the need to
3780 change the code in several packages. The idea is not new, but I have
3781 not heard anyone propose the approach using dpkg-divert before. It
3782 depend on the small and clever package
3783 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3784 uses LD_PRELOAD to replace the system functions for syncing data to
3785 disk with functions doing nothing, thus allowing programs to live
3786 dangerous while speeding up disk I/O significantly. Instead of
3787 modifying the implementation of dpkg, apt and tasksel (which are the
3788 packages responsible for selecting, fetching and installing packages),
3789 it occurred to me that we could just divert the programs away, replace
3790 them with a simple shell wrapper calling
3791 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3792 Two days ago I decided to test the idea, and wrapped up a simple
3793 implementation for the Debian Edu udeb.
</p
>
3795 <p
>The effect was stunning. In my first test it reduced the running
3796 time of the pkgsel step (installing tasks) from
64 to less than
44
3797 minutes (
20 minutes shaved off the installation) on an old Dell
3798 Latitude D505 machine. I am not quite sure what the optimised time
3799 would have been, as I messed up the testing a bit, causing the debconf
3800 priority to get low enough for two questions to pop up during
3801 installation. As soon as I saw the questions I moved the installation
3802 along, but do not know how long the question were holding up the
3803 installation. I did some more measurements using Debian Edu Jessie,
3804 and got these results. The time measured is the time stamp in
3805 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3806 "pkgsel: finishing up
" lines, if you want to do the same measurement
3807 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3808 timing thus do not depend on how quickly the user handle the tasksel
3811 <p
><table
>
3814 <th
>Machine/setup
</th
>
3815 <th
>Original tasksel
</th
>
3816 <th
>Optimised tasksel
</th
>
3817 <th
>Reduction
</th
>
3821 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3822 <td
>64 min (
07:
46-
08:
50)
</td
>
3823 <td
><44 min (
11:
27-
12:
11)
</td
>
3824 <td
>>20 min
18%
</td
>
3828 <td
>Latitude D505 Roaming LXDE
</td
>
3829 <td
>57 min (
08:
48-
09:
45)
</td
>
3830 <td
>34 min (
07:
43-
08:
17)
</td
>
3831 <td
>23 min
40%
</td
>
3835 <td
>Latitude D505 Minimal
</td
>
3836 <td
>22 min (
10:
37-
10:
59)
</td
>
3837 <td
>11 min (
11:
16-
11:
27)
</td
>
3838 <td
>11 min
50%
</td
>
3842 <td
>Thinkpad X200 Minimal
</td
>
3843 <td
>6 min (
08:
19-
08:
25)
</td
>
3844 <td
>4 min (
08:
04-
08:
08)
</td
>
3845 <td
>2 min
33%
</td
>
3849 <td
>Thinkpad X200 Roaming KDE
</td
>
3850 <td
>19 min (
09:
21-
09:
40)
</td
>
3851 <td
>15 min (
10:
25-
10:
40)
</td
>
3852 <td
>4 min
21%
</td
>
3855 </table
></p
>
3857 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3858 time is spent downloading packages. The connection to the Internet
3859 was
100Mbit/s during testing, so downloading should not be a
3860 significant factor in the measurement. Download typically took a few
3861 seconds to a few minutes, depending on the amount of packages being
3862 installed.
</p
>
3864 <p
>The speedup is implemented by using two hooks in
3865 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3866 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3867 finish-install.d hook to remove the divert at the end of the
3868 installation. I picked the pre-pkgsel.d hook instead of the
3869 post-base-installer.d hook because I test using an ISO without the
3870 eatmydata package included, and the post-base-installer.d hook in
3871 Debian Edu can only operate on packages included in the ISO. The
3872 negative effect of this is that I am unable to activate this
3873 optimization for the kernel installation step in d-i. If the code is
3874 moved to the post-base-installer.d hook, the speedup would be larger
3875 for the entire installation.
</p
>
3877 <p
>I
've implemented this in the
3878 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3879 git repository, and plan to provide the optimization as part of the
3880 Debian Edu installation. If you want to test this yourself, you can
3881 create two files in the installer (or in an udeb). One shell script
3882 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3884 <p
><blockquote
><pre
>
3887 . /usr/share/debconf/confmodule
3889 logger -t my-pkgsel
"info: $*
"
3892 logger -t my-pkgsel
"error: $*
"
3894 override_install() {
3895 apt-install eatmydata || true
3896 if [ -x /target/usr/bin/eatmydata ] ; then
3897 for bin in dpkg apt-get aptitude tasksel ; do
3899 # Test that the file exist and have not been diverted already.
3900 if [ -f /target$file ] ; then
3901 info
"diverting $file using eatmydata
"
3902 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3903 > /target$file.edu
3904 chmod
755 /target$file.edu
3905 in-target dpkg-divert --package debian-edu-config \
3906 --rename --quiet --add $file
3907 ln -sf ./$bin.edu /target$file
3909 error
"unable to divert $file, as it is missing.
"
3913 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3918 </pre
></blockquote
></p
>
3920 <p
>To clean up, another shell script should go into
3921 /usr/lib/finish-install.d/ with code like this:
3923 <p
><blockquote
><pre
>
3925 . /usr/share/debconf/confmodule
3927 logger -t my-finish-install
"error: $@
"
3929 remove_install_override() {
3930 for bin in dpkg apt-get aptitude tasksel ; do
3932 if [ -x /target$file.edu ] ; then
3934 in-target dpkg-divert --package debian-edu-config \
3935 --rename --quiet --remove $file
3938 error
"Missing divert for $file.
"
3941 sync # Flush file buffers before continuing
3944 remove_install_override
3945 </pre
></blockquote
></p
>
3947 <p
>In Debian Edu, I placed both code fragments in a separate script
3948 edu-eatmydata-install and call it from the pre-pkgsel.d and
3949 finish-install.d scripts.
</p
>
3951 <p
>By now you might ask if this change should get into the normal
3952 Debian installer too? I suspect it should, but am not sure the
3953 current debian-installer coordinators find it useful enough. It also
3954 depend on the side effects of the change. I
'm not aware of any, but I
3955 guess we will see if the change is safe after some more testing.
3956 Perhaps there is some package in Debian depending on sync() and
3957 fsync() having effect? Perhaps it should go into its own udeb, to
3958 allow those of us wanting to enable it to do so without affecting
3961 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3962 will break installation of all programs using gnutls because of
3963 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3964 eatmydata package in Debian will solve it.
</p
>
3966 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3967 the optimization work again. And I have discovered that the
3968 dpkg-divert trick is not really needed and implemented a slightly
3969 simpler approach as part of the debian-edu-install package. See
3970 tools/edu-eatmydata-install in the source package.
</p
>
3972 <p
>Update
2014-
11-
11: Unfortunately, a new
3973 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3974 triggering on i386 made it into testing, and broke this installation
3975 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3976 request
768893</a
> is accepted, it should be working again.
</p
>
3981 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3982 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3983 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3984 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3985 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3986 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3987 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3988 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3989 learn that there is a large set of publicly available key servers to
3990 use when looking for peoples public key. So far I have used
3991 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3992 were misbehaving, but those days are ended. The servers I have used
3993 up until yesterday have been slow and some times unavailable. I hope
3994 those problems are gone now.
</p
>
3996 <p
>Behind the round robin DNS entry of the
3997 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3998 there is a pool of more than
100 keyservers which are checked every
3999 day to ensure they are well connected and up to date. It must be
4000 better than what I have used so far. :)
</p
>
4002 <p
>Yesterdays speaker told me that the service is the default
4003 keyserver provided by the default configuration in GnuPG, but this do
4004 not seem to be used in Debian. Perhaps it should?
</p
>
4006 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
4009 <p
><blockquote
><pre
>
4010 keyserver pool.sks-keyservers.net
4011 </pre
></blockquote
></p
>
4013 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
4014 entries in DNS. Just for fun, I did just that at work, so now every
4015 user of GnuPG at the University of Oslo should find a OpenGPG
4016 keyserver automatically should their need it:
</p
>
4018 <p
><blockquote
><pre
>
4019 % host -t srv _pgpkey-http._tcp.uio.no
4020 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
4022 </pre
></blockquote
></p
>
4024 <p
>Now if only
4025 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
4026 HKP lookup protocol
</a
> supported finding signature paths, I would be
4027 very happy. It can look up a given key or search for a user ID, but I
4028 normally do not want that, but to find a trust path from my key to
4029 another key. Given a user ID or key ID, I would like to find (and
4030 download) the keys representing a signature path from my key to the
4031 key in question, to be able to get a trust path between the two keys.
4032 This is as far as I can tell not possible today. Perhaps something
4033 for a future version of the protocol?
</p
>
4038 <title>From English wiki to translated PDF and epub via Docbook
</title>
4039 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
4040 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
4041 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4042 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4043 project
</a
> provide an instruction manual for teachers, system
4044 administrators and other users that contain useful tips for setting up
4045 and maintaining a Debian Edu installation. This text is about how the
4046 text processing of this manual is handled in the project.
</p
>
4048 <p
>One goal of the project is to provide information in the native
4049 language of its users, and for this we need to handle translations.
4050 But we also want to make sure each language contain the same
4051 information, so for this we need a good way to keep the translations
4052 in sync. And we want it to be easy for our users to improve the
4053 documentation, avoiding the need to learn special formats or tools to
4054 contribute, and the obvious way to do this is to make it possible to
4055 edit the documentation using a web browser. We also want it to be
4056 easy for translators to keep the translation up to date, and give them
4057 help in figuring out what need to be translated. Here is the list of
4058 tools and the process we have found trying to reach all these
4061 <p
>We maintain the authoritative source of our manual in the
4062 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4063 wiki
</a
>, as several wiki pages written in English. It consist of one
4064 front page with references to the different chapters, several pages
4065 for each chapter, and finally one
"collection page
" gluing all the
4066 chapters together into one large web page (aka
4067 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4068 AllInOne page
</a
>). The AllInOne page is the one used for further
4069 processing and translations. Thanks to the fact that the
4070 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4071 wiki.debian.org support exporting pages in
4072 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4073 the list of pages to export using the raw version of the AllInOne
4074 page, loop over each of them to generate a Docbook XML version of the
4075 manual. This process also download images and transform image
4076 references to use the locally downloaded images. The generated
4077 Docbook XML files are slightly broken, so some post-processing is done
4078 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4079 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4080 a handfull of images. The XML file can now be used to generate PDF, HTML
4081 and epub versions of the English manual. This is the basic step of
4082 our process, making PDF (using dblatex), HTML (using xsltproc) and
4083 epub (using dbtoepub) version from Docbook XML, and the resulting files
4084 are placed in the debian-edu-doc-en binary package.
</p
>
4086 <p
>But English documentation is not enough for us. We want translated
4087 documentation too, and we want to make it easy for translators to
4088 track the English original. For this we use the
4089 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4090 which allow us to transform the English Docbook XML file into a
4091 translation file (a .pot file), usable with the normal gettext based
4092 translation tools used by those translating free software. The pot
4093 file is used to create and maintain translation files (several .po
4094 files), which the translations update with the native language
4095 translations of all titles, paragraphs and blocks of text in the
4096 original. The next step is combining the original English Docbook XML
4097 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4098 create a translated Docbook XML file (in this case
4099 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4100 translated, if the translation is not complete) Docbook XML file can
4101 then be used like the original to create a PDF, HTML and epub version
4102 of the documentation.
</p
>
4104 <p
>The translators use different tools to edit the .po files. We
4106 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4107 while some use emacs and vi, others can use web based editors like
4108 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4109 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4110 is where the .po file end up, in our git repository. Updated
4111 translations can either be committed directly to git, or submitted as
4112 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4113 against the debian-edu-doc package
</a
>.
</p
>
4115 <p
>One challenge is images, which both might need to be translated (if
4116 they show translated user applications), and are needed in different
4117 formats when creating PDF and HTML versions (epub is a HTML version in
4118 this regard). For this we transform the original PNG images to the
4119 needed density and format during build, and have a way to provide
4120 translated images by storing translated versions in
4121 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4122 package maintainers know more.
</p
>
4124 <p
>If you wonder what the result look like, we provide
4125 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4126 of the documentation packages on the web
</a
>. See for example the
4127 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4128 PDF version
</a
> or the
4129 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4130 HTML version
</a
>. We do not yet build the epub version by default,
4131 but perhaps it will be done in the future.
</p
>
4133 <p
>To learn more, check out
4134 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4135 debian-edu-doc package
</a
>,
4136 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4137 manual on the wiki
</a
> and
4138 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4139 translation instructions
</a
> in the manual.
</p
>
4144 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4145 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4146 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4147 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4148 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4149 related packages relevant for the computer installed automatically.
4150 So I implemented one, using
4151 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4152 package
</a
>. To use it, install the tasksel and isenkram packages and
4153 run tasksel as user root. You should be presented with a new option,
4154 "Hardware specific packages (autodetected by isenkram)
". When you
4155 select it, tasksel will install the packages isenkram claim is fit for
4156 the current hardware, hot pluggable or not.
<p
>
4158 <p
>The implementation is in two files, one is the tasksel menu entry
4159 description, and the other is the script used to extract the list of
4160 packages to install. The first part is in
4161 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4164 <p
><blockquote
><pre
>
4167 Description: Hardware specific packages (autodetected by isenkram)
4168 Based on the detected hardware various hardware specific packages are
4170 Test-new-install: mark show
4172 Packages: for-current-hardware
4173 </pre
></blockquote
></p
>
4175 <p
>The second part is in
4176 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4179 <p
><blockquote
><pre
>
4184 isenkram-autoinstall-firmware -l
4186 </pre
></blockquote
></p
>
4188 <p
>All in all, a very short and simple implementation making it
4189 trivial to install the hardware dependent package we all may want to
4190 have installed on our machines. I
've not been able to find a way to
4191 get tasksel to tell you exactly which packages it plan to install
4192 before doing the installation. So if you are curious or careful,
4193 check the output from the isenkram-* command line tools first.
</p
>
4195 <p
>The information about which packages are handling which hardware is
4196 fetched either from the isenkram package itself in
4197 /usr/share/isenkram/, from git.debian.org or from the APT package
4198 database (using the Modaliases header). The APT package database
4199 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4200 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4201 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4202 the python-apt code (bug
4203 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4204 workaround I was able to get rid of the file descriptor leak and
4205 reduce the memory leak from ~
30 MiB per hardware detection down to
4206 around
2 MiB per hardware detection. It should make the desktop
4207 daemon a lot more useful. The fix is in version
0.7 uploaded to
4208 unstable today.
</p
>
4210 <p
>I believe the current way of mapping hardware to packages in
4211 Isenkram is is a good draft, but in the future I expect isenkram to
4212 use the AppStream data source for this. A proposal for getting proper
4213 AppStream support into Debian is floating around as
4214 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4215 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4216 project
</a
> will take place this summer to improve the situation. I
4217 look forward to seeing the result, and welcome patches for isenkram to
4218 start using the information when it is ready.
</p
>
4220 <p
>If you want your package to map to some specific hardware, either
4221 add a
"Xb-Modaliases
" header to your control file like I did in
4222 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4223 package
</a
> or submit a bug report with the details to the isenkram
4225 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4226 blog posts tagged isenkram
</a
> for details on the notation. I expect
4227 the information will be migrated to AppStream eventually, but for the
4228 moment I got no better place to store it.
</p
>
4233 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4234 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4235 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4236 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4237 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4238 project
</a
> is working on providing the software and hardware to make
4239 it easy for non-technical people to host their data and communication
4240 at home, and being able to communicate with their friends and family
4241 encrypted and away from prying eyes. It is still going strong, and
4242 today a major mile stone was reached.
</p
>
4244 <p
>Today, the last of the packages currently used by the project to
4245 created the system images were accepted into Debian Unstable. It was
4246 the freedombox-setup package, which is used to configure the images
4247 during build and on the first boot. Now all one need to get going is
4248 the build code from the freedom-maker git repository and packages from
4249 Debian. And once the freedombox-setup package enter testing, we can
4250 build everything directly from Debian. :)
</p
>
4252 <p
>Some key packages used by Freedombox are
4253 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4254 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4255 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4256 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4257 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4258 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4259 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4260 are plans to integrate more packages into the setup. User
4261 documentation is maintained on the Debian wiki. Please
4262 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4263 the manual
</a
> and help us improve it.
</p
>
4265 <p
>To test for yourself and create boot images with the FreedomBox
4266 setup, run this on a Debian machine using a user with sudo rights to
4267 become root:
</p
>
4269 <p
><pre
>
4270 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4271 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4273 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4275 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4276 </pre
></p
>
4278 <p
>Root access is needed to run debootstrap and mount loopback
4279 devices. See the README in the freedom-maker git repo for more
4280 details on the build. If you do not want all three images, trim the
4281 make line. Note that the virtualbox-image target is not really
4282 virtualbox specific. It create a x86 image usable in kvm, qemu,
4283 vmware and any other x86 virtual machine environment. You might need
4284 the version of vmdebootstrap in Jessie to get the build working, as it
4285 include fixes for a race condition with kpartx.
</p
>
4287 <p
>If you instead want to install using a Debian CD and the preseed
4288 method, boot a Debian Wheezy ISO and use this boot argument to load
4289 the preseed values:
</p
>
4291 <p
><pre
>
4292 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4293 </pre
></p
>
4295 <p
>I have not tested it myself the last few weeks, so I do not know if
4296 it still work.
</p
>
4298 <p
>If you wonder how to help, one task you could look at is using
4299 systemd as the boot system. It will become the default for Linux in
4300 Jessie, so we need to make sure it is usable on the Freedombox. I did
4301 a simple test a few weeks ago, and noticed dnsmasq failed to start
4302 during boot when using systemd. I suspect there are other problems
4303 too. :) To detect problems, there is a test suite included, which can
4304 be run from the plinth web interface.
</p
>
4306 <p
>Give it a go and let us know how it goes on the mailing list, and help
4307 us get the new release published. :) Please join us on
4308 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4309 irc.debian.org)
</a
> and
4310 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4311 mailing list
</a
> if you want to help make this vision come true.
</p
>
4316 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4317 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4318 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4319 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4320 <description><p
>For a while now, I have been looking for a sensible offsite backup
4321 solution for use at home. My requirements are simple, it must be
4322 cheap and locally encrypted (in other words, I keep the encryption
4323 keys, the storage provider do not have access to my private files).
4324 One idea me and my friends had many years ago, before the cloud
4325 storage providers showed up, was to use Google mail as storage,
4326 writing a Linux block device storing blocks as emails in the mail
4327 service provided by Google, and thus get heaps of free space. On top
4328 of this one can add encryption, RAID and volume management to have
4329 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4330 I never found time to implement such system. But the last few weeks I
4331 have looked at a system called
4332 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4333 mounted network backed file system with the features I need.
</p
>
4335 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4336 handling several different storage providers, any with Amazon S3,
4337 Google Drive or OpenStack API. There are heaps of such storage
4338 providers. S3QL can also use a local directory as storage, which
4339 combined with sshfs allow for file storage on any ssh server. S3QL
4340 include support for encryption, compression, de-duplication, snapshots
4341 and immutable file systems, allowing me to mount the remote storage as
4342 a local mount point, look at and use the files as if they were local,
4343 while the content is stored in the cloud as well. This allow me to
4344 have a backup that should survive fire. The file system can not be
4345 shared between several machines at the same time, as only one can
4346 mount it at the time, but any machine with the encryption key and
4347 access to the storage service can mount it if it is unmounted.
</p
>
4349 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4350 package is included already. So to get started, run
<tt
>apt-get
4351 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4352 Greenqloud, after reading their nice recipe on
4353 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4354 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4355 in Iceland more than those in USA when it come to keeping my personal
4356 data safe and private, and thus would rather spend money on a company
4357 in Iceland. Another nice recipe is available from the article
4358 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4359 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4360 Admin magazine. When the provider is picked, figure out how to get
4361 the API key needed to connect to the storage API. With Greencloud,
4362 the key did not show up until I had added payment details to my
4365 <p
>Armed with the API access details, it is time to create the file
4366 system. First, create a new bucket in the cloud. This bucket is the
4367 file system storage area. I picked a bucket name reflecting the
4368 machine that was going to store data there, but any name will do.
4369 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4370 the API login and password, and a locally created password. Store it
4371 all in ~root/.s3ql/authinfo2 like this:
4373 <p
><blockquote
><pre
>
4375 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4376 backend-login: API-login
4377 backend-password: API-password
4378 fs-passphrase: local-password
4379 </pre
></blockquote
></p
>
4381 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4382 but any sensible way to create a fairly random password should do it.
4383 Armed with these details, it is now time to run mkfs, entering the API
4384 details and password to create it:
</p
>
4386 <p
><blockquote
><pre
>
4387 # mkdir -m
700 /var/lib/s3ql-cache
4388 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4389 --ssl s3c://s.greenqloud.com:
443/bucket-name
4390 Enter backend login:
4391 Enter backend password:
4392 Before using S3QL, make sure to read the user
's guide, especially
4393 the
'Important Rules to Avoid Loosing Data
' section.
4394 Enter encryption password:
4395 Confirm encryption password:
4396 Generating random encryption key...
4397 Creating metadata tables...
4407 Compressing and uploading metadata...
4408 Wrote
0.00 MB of compressed metadata.
4409 #
</pre
></blockquote
></p
>
4411 <p
>The next step is mounting the file system to make the storage available.
4413 <p
><blockquote
><pre
>
4414 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4415 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4416 Using
4 upload threads.
4417 Downloading and decompressing metadata...
4427 Mounting filesystem...
4429 Filesystem Size Used Avail Use% Mounted on
4430 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4432 </pre
></blockquote
></p
>
4434 <p
>The file system is now ready for use. I use rsync to store my
4435 backups in it, and as the metadata used by rsync is downloaded at
4436 mount time, no network traffic (and storage cost) is triggered by
4437 running rsync. To unmount, one should not use the normal umount
4438 command, as this will not flush the cache to the cloud storage, but
4439 instead running the umount.s3ql command like this:
4441 <p
><blockquote
><pre
>
4444 </pre
></blockquote
></p
>
4446 <p
>There is a fsck command available to check the file system and
4447 correct any problems detected. This can be used if the local server
4448 crashes while the file system is mounted, to reset the
"already
4449 mounted
" flag. This is what it look like when processing a working
4450 file system:
</p
>
4452 <p
><blockquote
><pre
>
4453 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4454 Using cached metadata.
4455 File system seems clean, checking anyway.
4456 Checking DB integrity...
4457 Creating temporary extra indices...
4458 Checking lost+found...
4459 Checking cached objects...
4460 Checking names (refcounts)...
4461 Checking contents (names)...
4462 Checking contents (inodes)...
4463 Checking contents (parent inodes)...
4464 Checking objects (reference counts)...
4465 Checking objects (backend)...
4466 ..processed
5000 objects so far..
4467 ..processed
10000 objects so far..
4468 ..processed
15000 objects so far..
4469 Checking objects (sizes)...
4470 Checking blocks (referenced objects)...
4471 Checking blocks (refcounts)...
4472 Checking inode-block mapping (blocks)...
4473 Checking inode-block mapping (inodes)...
4474 Checking inodes (refcounts)...
4475 Checking inodes (sizes)...
4476 Checking extended attributes (names)...
4477 Checking extended attributes (inodes)...
4478 Checking symlinks (inodes)...
4479 Checking directory reachability...
4480 Checking unix conventions...
4481 Checking referential integrity...
4482 Dropping temporary indices...
4483 Backing up old metadata...
4493 Compressing and uploading metadata...
4494 Wrote
0.89 MB of compressed metadata.
4496 </pre
></blockquote
></p
>
4498 <p
>Thanks to the cache, working on files that fit in the cache is very
4499 quick, about the same speed as local file access. Uploading large
4500 amount of data is to me limited by the bandwidth out of and into my
4501 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4502 which is very close to my upload speed, and downloading the same
4503 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4504 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4505 network, not the file system code. I do not know what a good cache
4506 size would be, but suspect that the cache should e larger than your
4507 working set.
</p
>
4509 <p
>I mentioned that only one machine can mount the file system at the
4510 time. If another machine try, it is told that the file system is
4513 <p
><blockquote
><pre
>
4514 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4515 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4516 Using
8 upload threads.
4517 Backend reports that fs is still mounted elsewhere, aborting.
4519 </pre
></blockquote
></p
>
4521 <p
>The file content is uploaded when the cache is full, while the
4522 metadata is uploaded once every
24 hour by default. To ensure the
4523 file system content is flushed to the cloud, one can either umount the
4524 file system, or ask S3QL to flush the cache and metadata using
4527 <p
><blockquote
><pre
>
4528 # s3qlctrl upload-meta /s3ql
4529 # s3qlctrl flushcache /s3ql
4531 </pre
></blockquote
></p
>
4533 <p
>If you are curious about how much space your data uses in the
4534 cloud, and how much compression and deduplication cut down on the
4535 storage usage, you can use s3qlstat on the mounted file system to get
4538 <p
><blockquote
><pre
>
4540 Directory entries:
9141
4543 Total data size:
22049.38 MB
4544 After de-duplication:
21955.46 MB (
99.57% of total)
4545 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4546 Database size:
2.39 MB (uncompressed)
4547 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4549 </pre
></blockquote
></p
>
4551 <p
>I mentioned earlier that there are several possible suppliers of
4552 storage. I did not try to locate them all, but am aware of at least
4553 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4554 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4555 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4556 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4557 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4558 accept payment in Bitcoin. Pick one that suit your need. Some of
4559 them provide several GiB of free storage, but the prize models are
4560 quite different and you will have to figure out what suits you
4563 <p
>While researching this blog post, I had a look at research papers
4564 and posters discussing the S3QL file system. There are several, which
4565 told me that the file system is getting a critical check by the
4566 science community and increased my confidence in using it. One nice
4568 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4569 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4570 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4571 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4572 and Pamela Smith. Please have a look.
</p
>
4574 <p
>Given my problems with different file systems earlier, I decided to
4575 check out the mounted S3QL file system to see if it would be usable as
4576 a home directory (in other word, that it provided POSIX semantics when
4577 it come to locking and umask handling etc). Running
4578 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4579 test code to check file system semantics
</a
>, I was happy to discover that
4580 no error was found. So the file system can be used for home
4581 directories, if one chooses to do so.
</p
>
4583 <p
>If you do not want a locally file system, and want something that
4584 work without the Linux fuse file system, I would like to mention the
4585 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4586 provide locally encrypted backup using a command line client. It have
4587 a nicer access control system, where one can split out read and write
4588 access, allowing some systems to write to the backup and others to
4589 only read from it.
</p
>
4591 <p
>As usual, if you use Bitcoin and want to show your support of my
4592 activities, please send Bitcoin donations to my address
4593 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4598 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4599 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4600 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4601 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4602 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4603 project
</a
> is working on providing the software and hardware for
4604 making it easy for non-technical people to host their data and
4605 communication at home, and being able to communicate with their
4606 friends and family encrypted and away from prying eyes. It has been
4607 going on for a while, and is slowly progressing towards a new test
4608 release (
0.2).
</p
>
4610 <p
>And what day could be better than the Pi day to announce that the
4611 new version will provide
"hard drive
" / SD card / USB stick images for
4612 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4613 system), and can also be installed using a Debian installer preseed
4614 file. The Debian based Freedombox is now based on Debian Jessie,
4615 where most of the needed packages used are already present. Only one,
4616 the freedombox-setup package, is missing. To try to build your own
4617 boot image to test the current status, fetch the freedom-maker scripts
4619 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4620 with a user with sudo access to become root:
4623 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4625 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4626 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4628 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4631 <p
>Root access is needed to run debootstrap and mount loopback
4632 devices. See the README for more details on the build. If you do not
4633 want all three images, trim the make line. But note that thanks to
<a
4634 href=
"https://bugs.debian.org/
741407">a race condition in
4635 vmdebootstrap
</a
>, the build might fail without the patch to the
4636 kpartx call.
</p
>
4638 <p
>If you instead want to install using a Debian CD and the preseed
4639 method, boot a Debian Wheezy ISO and use this boot argument to load
4640 the preseed values:
</p
>
4643 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4646 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4647 recently introduced bug in apt in Jessie
</a
>, the installer will
4648 currently hang while setting up APT sources. Killing the
4649 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4650 installation will get the installation going. This affect all
4651 installations in Jessie, and I expect it will be fixed soon.
</p
>
4653 <p
>Give it a go and let us know how it goes on the mailing list, and help
4654 us get the new release published. :) Please join us on
4655 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4656 irc.debian.org)
</a
> and
4657 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4658 mailing list
</a
> if you want to help make this vision come true.
</p
>
4663 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4664 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4665 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4666 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4667 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4668 innetgr tools, because I needed them in
4669 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4670 ng-utils, and it has served me well. I placed the project under the
4671 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4672 repository. But many years ago, the CVS repository was dropped (lost,
4673 not migrated to new hardware, not sure), and the project have lacked a
4674 proper home since then.
</p
>
4676 <p
>Last summer, I had a look at the package and made a new release
4677 fixing a irritating crash bug, but was unable to store the changes in
4678 a proper source control system. I applied for a project on
4679 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4680 to follow up on it. Until today. :)
</p
>
4682 <p
>After many hours of cleaning and migration, the ng-utils project
4683 now have a new home, and a git repository with the highlight of the
4684 history of the project. I published all release tarballs and imported
4685 them into the git repository. As the project is really stable and not
4686 expected to gain new features any time soon, I decided to make a new
4687 release and call it
1.0. Visit the new project home on
4688 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4689 if you want to check it out. The new version is also uploaded into
4690 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4695 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4696 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4697 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4698 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4699 <description><p
>A few days ago I decided to try to help the Hurd people to get
4700 their changes into sysvinit, to allow them to use the normal sysvinit
4701 boot system instead of their old one. This follow up on the
4702 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4703 Google Summer of Code work
</a
> done last summer by Justus Winter to
4704 get Debian on Hurd working more like Debian on Linux. To get started,
4705 I downloaded a prebuilt hard disk image from
4706 <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
>,
4707 and started it using virt-manager.
</p
>
4709 <p
>The first think I had to do after logging in (root without any
4710 password) was to get the network operational. I followed
4711 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4712 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4713 commands as root to get the machine to accept a IP address from the
4714 kvm internal DHCP server:
</p
>
4716 <p
><blockquote
><pre
>
4717 settrans -fgap /dev/netdde /hurd/netdde
4718 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4719 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4721 </pre
></blockquote
></p
>
4723 <p
>After this, the machine had internet connectivity, and I could
4724 upgrade it and install the sysvinit packages from experimental and
4725 enable it as the default boot system in Hurd.
</p
>
4727 <p
>But before I did that, I set a password on the root user, as ssh is
4728 running on the machine it for ssh login to work a password need to be
4729 set. Also, note that a bug somewhere in openssh on Hurd block
4730 compression from working. Remember to turn that off on the client
4733 <p
>Run these commands as root to upgrade and test the new sysvinit
4736 <p
><blockquote
><pre
>
4737 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4738 deb http://http.debian.net/debian/ experimental main
4741 apt-get dist-upgrade
4742 apt-get install -t experimental initscripts sysv-rc sysvinit \
4743 sysvinit-core sysvinit-utils
4744 update-alternatives --config runsystem
4745 </pre
></blockquote
></p
>
4747 <p
>To reboot after switching boot system, you have to use
4748 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4749 yet a sysvinit process able to receive the signals from the normal
4750 'reboot
' command. After switching to sysvinit as the boot system,
4751 upgrading every package and rebooting, the network come up with DHCP
4752 after boot as it should, and the settrans/pkill hack mentioned at the
4753 start is no longer needed. But for some strange reason, there are no
4754 longer any login prompt in the virtual console, so I logged in using
4757 <p
>Note that there are some race conditions in Hurd making the boot
4758 fail some times. No idea what the cause is, but hope the Hurd porters
4759 figure it out. At least Justus said on IRC (#debian-hurd on
4760 irc.debian.org) that they are aware of the problem. A way to reduce
4761 the impact is to upgrade to the Hurd packages built by Justus by
4762 adding this repository to the machine:
</p
>
4764 <p
><blockquote
><pre
>
4765 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4766 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4768 </pre
></blockquote
></p
>
4770 <p
>At the moment the prebuilt virtual machine get some packages from
4771 http://ftp.debian-ports.org/debian, because some of the packages in
4772 unstable do not yet include the required patches that are lingering in
4773 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4775 <p
><blockquote
><pre
>
4776 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4777 i emacs - GNU Emacs editor (metapackage)
4778 i gdb - GNU Debugger
4779 i hurd-recommended - Miscellaneous translators
4780 i isc-dhcp-client - ISC DHCP client
4781 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4782 i libc-bin - Embedded GNU C Library: Binaries
4783 i libc-dev-bin - Embedded GNU C Library: Development binaries
4784 i libc0.3 - Embedded GNU C Library: Shared libraries
4785 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4786 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4787 i multiarch-support - Transitional package to ensure multiarch compatibilit
4788 i A x11-common - X Window System (X.Org) infrastructure
4789 i xorg - X.Org X Window System
4790 i A xserver-xorg - X.Org X server
4791 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4793 </pre
></blockquote
></p
>
4795 <p
>All in all, testing hurd has been an interesting experience. :)
4796 X.org did not work out of the box and I never took the time to follow
4797 the porters instructions to fix it. This time I was interested in the
4798 command line stuff.
<p
>
4803 <title>New chrpath release
0.16</title>
4804 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4805 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4806 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4807 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4808 find problems in C, C++ and Java code using static source code
4809 analysis. It can detect a lot of different problems, and is very
4810 useful to find memory and locking bugs in the error handling part of
4811 the source. The company behind it provide
4812 <a href=
"https://scan.coverity.com/
">check of free software projects as
4813 a community service
</a
>, and many hundred free software projects are
4814 already checked. A few days ago I decided to have a closer look at
4815 the Coverity system, and discovered that the
4816 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4817 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4818 projects I am involved with was already registered. But these are
4819 fairly big, and I would also like to have a small and easy project to
4820 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4821 checking of the chrpath project
</a
>. It was
4822 added to the checker and discovered seven potential defects. Six of
4823 these were real, mostly resource
"leak
" when the program detected an
4824 error. Nothing serious, as the resources would be released a fraction
4825 of a second later when the program exited because of the error, but it
4826 is nice to do it right in case the source of the program some time in
4827 the future end up in a library. Having fixed all defects and added
4828 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4829 mailing list for the chrpath developers
</a
>, I decided it was time to
4830 publish a new release. These are the release notes:
</p
>
4832 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4836 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4837 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4838 <li
>Mention new project mailing list in the documentation.
</li
>
4843 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4844 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4845 project if something is wrong with the new release. The test suite
4846 did not discover any old errors, so if you find a new one, please also
4847 include a test suite check.
</p
>
4852 <title>New chrpath release
0.15</title>
4853 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4854 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4855 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4856 <description><p
>After many years break from the package and a vain hope that
4857 development would be continued by someone else, I finally pulled my
4858 acts together this morning and wrapped up a new release of chrpath,
4859 the command line tool to modify the rpath and runpath of already
4860 compiled ELF programs. The update was triggered by the persistence of
4861 Isha Vishnoi at IBM, which needed a new config.guess file to get
4862 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4863 is working on. I checked the
4864 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4865 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4866 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4867 packages for interesting patches (failed to find the source from
4868 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4869 These are the release notes:
</p
>
4871 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4875 <li
>Updated config.sub and config.guess from the GNU project to work
4876 with newer architectures. Thanks to isha vishnoi for the heads
4879 <li
>Updated README with current URLs.
</li
>
4881 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4882 Matthias Klose.
</li
>
4884 <li
>Added missing help for -k|--keepgoing option, using patch by
4885 Petr Machata found in Fedora.
</li
>
4887 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4888 .dynamic is a NULL terminated string. Based on patch found in
4889 Fedora credited Axel Thimm and Christian Krause.
</li
>
4894 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4895 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4896 project if something is wrong with the new release. The test suite
4897 did not discover any old errors, so if you find a new one, please also
4898 include a testsuite check.
</p
>
4903 <title>Debian init.d boot script example for rsyslog
</title>
4904 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4905 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4906 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4907 <description><p
>If one of the points of switching to a new init system in Debian is
4908 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4909 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4910 init.d scripts at all. Here is an example init.d script, ie a rewrite
4911 of /etc/init.d/rsyslog:
</p
>
4913 <p
><pre
>
4914 #!/lib/init/init-d-script
4917 # Required-Start: $remote_fs $time
4918 # Required-Stop: umountnfs $time
4919 # X-Stop-After: sendsigs
4920 # Default-Start:
2 3 4 5
4921 # Default-Stop:
0 1 6
4922 # Short-Description: enhanced syslogd
4923 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4924 # It is quite compatible to stock sysklogd and can be
4925 # used as a drop-in replacement.
4927 DESC=
"enhanced syslogd
"
4928 DAEMON=/usr/sbin/rsyslogd
4929 </pre
></p
>
4931 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4932 script was
137 lines, and the above is just
15 lines, most of it meta
4933 info/comments.
</p
>
4935 <p
>How to do this, you ask? Well, one create a new script
4936 /lib/init/init-d-script looking something like this:
4938 <p
><pre
>
4941 # Define LSB log_* functions.
4942 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4943 # and status_of_proc is working.
4944 . /lib/lsb/init-functions
4947 # Function that starts the daemon/service
4953 #
0 if daemon has been started
4954 #
1 if daemon was already running
4955 #
2 if daemon could not be started
4956 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4958 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4961 # Add code here, if necessary, that waits for the process to be ready
4962 # to handle requests from services started subsequently which depend
4963 # on this one. As a last resort, sleep for some time.
4967 # Function that stops the daemon/service
4972 #
0 if daemon has been stopped
4973 #
1 if daemon was already stopped
4974 #
2 if daemon could not be stopped
4975 # other if a failure occurred
4976 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4977 RETVAL=
"$?
"
4978 [
"$RETVAL
" =
2 ]
&& return
2
4979 # Wait for children to finish too if this is a daemon that forks
4980 # and if the daemon is only ever run from this initscript.
4981 # If the above conditions are not satisfied then add some other code
4982 # that waits for the process to drop all resources that could be
4983 # needed by services started subsequently. A last resort is to
4984 # sleep for some time.
4985 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4986 [
"$?
" =
2 ]
&& return
2
4987 # Many daemons don
't delete their pidfiles when they exit.
4989 return
"$RETVAL
"
4993 # Function that sends a SIGHUP to the daemon/service
4997 # If the daemon can reload its configuration without
4998 # restarting (for example, when it is sent a SIGHUP),
4999 # then implement that here.
5001 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
5006 scriptbasename=
"$(basename $
1)
"
5007 echo
"SN: $scriptbasename
"
5008 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
5009 script=
"$
1"
5016 NAME=$(basename $DAEMON)
5017 PIDFILE=/var/run/$NAME.pid
5019 # Exit if the package is not installed
5020 #[ -x
"$DAEMON
" ] || exit
0
5022 # Read configuration variable file if it is present
5023 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
5025 # Load the VERBOSE setting and other rcS variables
5028 case
"$
1" in
5030 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
5032 case
"$?
" in
5033 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5034 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5038 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
5040 case
"$?
" in
5041 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5042 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5046 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5048 #reload|force-reload)
5050 # If do_reload() is not implemented then leave this commented out
5051 # and leave
'force-reload
' as an alias for
'restart
'.
5053 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5057 restart|force-reload)
5059 # If the
"reload
" option is implemented then remove the
5060 #
'force-reload
' alias
5062 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5064 case
"$?
" in
5067 case
"$?
" in
5069 1) log_end_msg
1 ;; # Old process is still running
5070 *) log_end_msg
1 ;; # Failed to start
5080 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5086 </pre
></p
>
5088 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5089 lot. I did not really polish the approach, so it might not always
5090 work out of the box, but you get the idea. I did not try very hard to
5091 optimize it nor make it more robust either.
</p
>
5093 <p
>A better argument for switching init system in Debian than reducing
5094 the size of init scripts (which is a good thing to do anyway), is to
5095 get boot system that is able to handle the kernel events sensibly and
5096 robustly, and do not depend on the boot to run sequentially. The boot
5097 and the kernel have not behaved sequentially in years.
</p
>
5102 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5103 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5104 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5105 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5106 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5107 remote display access is the preferred solution with oVirt and RedHat
5108 Enterprise Virtualization, and I was sad to discover the other day
5109 that the browser plugin needed to use these systems seamlessly was
5110 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5111 for a package
</a
> was from
2012-
04-
10 with no progress since
5112 2013-
04-
01, so I decided to wrap up a package based on the great work
5113 from Cajus Pollmeier and put it in a collab-maint maintained git
5114 repository to get a package I could use. I would very much like
5115 others to help me maintain the package (or just take over, I do not
5116 mind), but as no-one had volunteered so far, I just uploaded it to
5117 NEW. I hope it will be available in Debian in a few days.
</p
>
5119 <p
>The source is now available from
5120 <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
>
5125 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5126 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5127 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5128 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5129 <description><p
>The
5130 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5131 program is a a very nice system to create virtual machine images. It
5132 create a image file, add a partition table, mount it and run
5133 debootstrap in the mounted directory to create a Debian system on a
5134 stick. Yesterday, I decided to try to teach it how to make images for
5135 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5136 of a plan to simplify the build system for
5137 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5138 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5139 the virtualbox images, but its current build system made multistrap
5140 based system for Dreamplug images, and it is lacking support for
5141 Raspberry Pi.
</p
>
5143 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5144 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5145 code and adjusted it to be able to build armel images on my amd64
5146 Debian laptop. I ended up giving vmdebootstrap five new options,
5147 allowing me to replicate the image creation process I use to make
5148 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5149 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5150 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5151 call debootstrap with --foreign and to copy the handler into the
5152 generated chroot before running the second stage. This allow
5153 vmdebootstrap to create armel images on an amd64 host. Next I added
5154 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5155 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5156 given file system type, allowing me to create an image with a vfat
5157 partition for the /boot/ stuff. I also added a
<tt
>--variant
5158 variant
</tt
> option to allow me to create smaller images without the
5159 Debian base system packages installed. Finally, I added an option
5160 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5161 as a boot loader. It is not needed on the Raspberry Pi and probably
5162 most other non-x86 architectures. The changes were accepted by the
5163 upstream author of vmdebootstrap yesterday and today, and is now
5165 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5166 upstream project page
</a
>.
</p
>
5168 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5169 create a small script (the customize script) to add the non-free
5170 binary blob needed to boot the Raspberry Pi and the APT source
5173 <p
><pre
>
5175 set -e # Exit on first error
5176 rootdir=
"$
1"
5177 cd
"$rootdir
"
5178 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5179 deb http://http.debian.net/debian/ jessie main contrib non-free
5181 # Install non-free binary blob needed to boot Raspberry Pi. This
5182 # install a kernel somewhere too.
5183 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5184 -O $rootdir/usr/bin/rpi-update
5185 chmod a+x $rootdir/usr/bin/rpi-update
5186 mkdir -p $rootdir/lib/modules
5187 touch $rootdir/boot/start.elf
5188 chroot $rootdir rpi-update
5189 </pre
></p
>
5191 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5192 to build the image:
</p
>
5195 sudo ./vmdebootstrap \
5198 --distribution jessie \
5199 --mirror http://http.debian.net/debian \
5208 --root-password raspberry \
5209 --hostname raspberrypi \
5210 --foreign /usr/bin/qemu-arm-static \
5211 --customize `pwd`/customize \
5213 --package git-core \
5214 --package binutils \
5215 --package ca-certificates \
5218 </pre
></p
>
5220 <p
>The list of packages being installed are the ones needed by
5221 rpi-update to make the image bootable on the Raspberry Pi, with the
5222 exception of netbase, which is needed by debootstrap to find
5223 /etc/hosts with the minbase variant. I really wish there was a way to
5224 set up an Raspberry Pi using only packages in the Debian archive, but
5225 that is not possible as far as I know, because it boots from the GPU
5226 using a non-free binary blob.
</p
>
5228 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5229 probably a few others installed. I have not checked the complete
5230 build dependency list.
</p
>
5232 <p
>The resulting image will not use the hardware floating point unit
5233 on the Raspberry PI, because the armel architecture in Debian is not
5234 optimized for that use. So the images created will be a bit slower
5235 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5240 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5241 <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>
5242 <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>
5243 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5244 <description><p
>The last few days I came across a few good causes that should get
5245 wider attention. I recommend signing and donating to each one of
5248 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5249 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5250 Women program which is a Google Summer of Code like initiative to get
5251 more women involved in free software. One debian sponsor has offered
5252 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5253 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5254 hope you will to. :)
</p
>
5256 <p
>And the Electronic Frontier Foundation just announced plans to
5257 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5258 documentaries about the excessive spying
</a
> on every Internet user that
5259 take place these days, and their need to fund the work. I
've already
5260 donated. Are you next?
</p
>
5262 <p
>For my Norwegian audience, the organisation Studentenes og
5263 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5264 statement under the heading
5265 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5266 Access
</a
> for those of us asking for more focus on open access in the
5267 Norwegian government. So far
499 signatures. I hope you will sign it
5273 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5274 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5275 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5276 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5277 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5278 project
</a
> have been going on for a while, and have presented the
5279 vision, ideas and solution several places. Here is a little
5280 collection of videos of talks and presentation of the project.
</p
>
5284 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5285 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5287 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5288 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5290 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5291 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5292 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5293 (Youtube)
</li
>
5295 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5296 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5298 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5299 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5301 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5302 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5303 York City in
2012</a
> (Youtube)
</li
>
5305 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5306 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5307 (Youtube)
</li
>
5309 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5310 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5312 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5313 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5315 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5316 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5317 2013</a
> (Youtube)
</li
>
5321 <p
>A larger list is available from
5322 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5323 Freedombox Wiki
</a
>.
</p
>
5325 <p
>On other news, I am happy to report that Freedombox based on Debian
5326 Jessie is coming along quite well, and soon both Owncloud and using
5327 Tor should be available for testers of the Freedombox solution. :) In
5328 a few weeks I hope everything needed to test it is included in Debian.
5329 The withsqlite package is already in Debian, and the plinth package is
5330 pending in NEW. The third and vital part of that puzzle is the
5331 metapackage/setup framework, which is still pending an upload. Join
5332 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5333 (#freedombox on irc.debian.org)
</a
> and
5334 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5335 mailing list
</a
> if you want to help make this vision come true.
</p
>
5340 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5341 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5342 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5343 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5344 <description><p
>I was introduced to the
5345 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5346 in
2010, when Eben Moglen presented his vision about serving the need
5347 of non-technical people to keep their personal information private and
5348 within the legal protection of their own homes. The idea is to give
5349 people back the power over their network and machines, and return
5350 Internet back to its intended peer-to-peer architecture. Instead of
5351 depending on a central service, the Freedombox will give everyone
5352 control over their own basic infrastructure.
</p
>
5354 <p
>I
've intended to join the effort since then, but other tasks have
5355 taken priority. But this summers nasty news about the misuse of trust
5356 and privilege exercised by the
"western
" intelligence gathering
5357 communities increased my eagerness to contribute to a point where I
5358 actually started working on the project a while back.
</p
>
5360 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5361 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5362 create a simple and cheap Debian based appliance that anyone can hook
5363 up in their home and get access to secure and private services and
5364 communication. The initial deployment platform have been the
5365 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5366 which is a piece of hardware I do not own. So to be able to test what
5367 the current Freedombox setup look like, I had to come up with a way to install
5368 it on some hardware I do have access to. I have rewritten the
5369 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5370 image build framework to use .deb packages instead of only copying
5371 setup into the boot images, and thanks to this rewrite I am able to
5372 set up any machine supported by Debian Wheezy as a Freedombox, using
5373 the previously mentioned deb (and a few support debs for packages
5374 missing in Debian).
</p
>
5376 <p
>The current Freedombox setup consist of a set of bootstrapping
5378 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5379 and a administrative web interface
5380 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5381 withsqlite), as well as a privacy enhancing proxy based on
5382 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5383 (freedombox-privoxy). There is also a web/javascript based XMPP
5384 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5385 trying (unsuccessfully so far) to talk to the XMPP server
5386 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5387 web interface is pluggable, and the goal is to use it to enable OpenID
5388 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5389 this is really working yet, see
5390 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5391 project TODO
</a
> for links to GIT repositories. Most of the code is
5392 on github at the moment. The HTTP proxy is operational out of the
5393 box, and the admin web interface can be used to add/remove plinth
5394 users. I
've not been able to do anything else with it so far, but
5395 know there are several branches spread around github and other places
5396 with lots of half baked features.
</p
>
5398 <p
>Anyway, if you want to have a look at the current state, the
5399 following recipes should work to give you a test machine to poke
5402 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5406 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5407 <li
>Boot from it, either as CD or USB stick.
</li
>
5408 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5409 to the Debian installer:
<p
>
5410 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5412 <li
>Answer the few language/region/password questions and pick disk to
5413 install on.
</li
>
5415 <li
>When the installation is finished and the machine have rebooted a
5416 few times, your Freedombox is ready for testing.
</li
>
5420 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5424 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5425 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5426 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5428 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5429 </pre
></li
>
5430 <li
><p
>Run this as root:
</p
>
5432 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5435 apt-get install freedombox-setup
5436 /usr/lib/freedombox/setup
5437 </pre
></li
>
5438 <li
>Reboot into your freshly created Freedombox.
</li
>
5442 <p
>You can test it on other architectures too, but because the
5443 freedombox-privoxy package is binary, it will only work as intended on
5444 the architectures where I have had time to build the binary and put it
5445 in my APT repository. But do not let this stop you. It is only a
5446 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5448 <p
>Note that by default Freedombox is a DHCP server on the
5449 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5450 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5451 disable
</tt
>" as root.
</p
>
5453 <p
>Please let me know if this works for you, or if you have any
5454 problems. We gather on the IRC channel
5455 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5456 irc.debian.org and the
5457 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5458 mailing list
</a
>.
</p
>
5460 <p
>Once you get your freedombox operational, you can visit
5461 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5462 welcome screen (dead end - do not be surprised if you are unable to
5463 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5464 to look at the rest of plinth. The default user is
'admin
' and the
5465 default password is
'secret
'.
</p
>
5470 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5471 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5472 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5473 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5474 <description><p
>Earlier, I reported about
5475 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5476 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5477 told by IBM that the original disk should be thrown away. And as
5478 there no longer was a problem if I bricked the firmware, I decided
5479 today to try to install Intel firmware to replace the Lenovo firmware
5480 currently on the disk.
</p
>
5482 <p
>I searched the Intel site for firmware, and found
5483 <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
>
5484 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5485 according to the site should contain the latest firmware for SSD
5486 disks. I inserted the broken disk in one of my spare laptops and
5487 booted the ISO from a USB stick. The disk was recognized, but the
5488 program claimed the newest firmware already were installed and refused
5489 to insert any Intel firmware. So no change, and the disk is still
5490 unable to handle write load. :( I guess the only way to get them
5491 working would be if Lenovo releases new firmware. No idea how likely
5492 that is. Anyway, just blogging about this test for completeness. I
5493 got a working Samsung disk, and see no point in spending more time on
5494 the broken disks.
</p
>
5499 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5500 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5501 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5502 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5503 <description><p
>Today I switched to
5504 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5505 new laptop
</a
>. I
've previously written about the problems I had with
5506 my new Thinkpad X230, which was delivered with an
5507 <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
5508 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5509 sustained writes. My hardware supplier have been very forthcoming in
5510 trying to find a solution, and after first trying with another
5511 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5512 disk instead to fix it once and for all. The Samsung disk survived
5513 the installation of Debian with encrypted disks (filling the disk with
5514 random data during installation killed the first two), and I thus
5515 decided to trust it with my data. I have installed it as a Debian Edu
5516 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5517 server at home using Kerberos and LDAP, and will use it as my work
5518 station from now on.
</p
>
5520 <p
>As this is a solid state disk with no moving parts, I believe the
5521 Debian Wheezy default installation need to be tuned a bit to increase
5522 performance and increase life time of the disk. The Linux kernel and
5523 user space applications do not yet adjust automatically to such
5524 environment. To make it easier for my self, I created a draft Debian
5525 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5526 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5527 for the ssd-setup package
</a
> is available from collab-maint, and it
5528 is set up to adjust the setup of the machine by just installing the
5529 package. If there is any non-SSD disk in the machine, the package
5530 will refuse to install, as I did not try to write any logic to sort
5531 file systems in SSD and non-SSD file systems.
</p
>
5533 <p
>I consider the package a draft, as I am a bit unsure how to best
5534 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5535 where I set up the machine with one large encrypted partition (in
5536 addition to /boot), put LVM on top of this and set up partitions on
5537 top of this again. See the README file in the package source for the
5538 references I used to pick the settings. At the moment these
5539 parameters are tuned:
</p
>
5543 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5544 (adding discard to /etc/crypttab)
</li
>
5546 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5547 this case a cryptsetup partition) by changing issue_discards from
5548 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5550 <li
>Set relatime as a file system option for ext3 and ext4 file
5553 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5554 /etc/fstab.
</li
>
5556 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5558 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5559 cron.daily).
</li
>
5561 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5562 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5566 <p
>During installation, I cancelled the part where the installer fill
5567 the disk with random data, as this would kill the SSD performance for
5568 little gain. My goal with the encrypted file system is to ensure
5569 those stealing my laptop end up with a brick and not a working
5570 computer. I have no hope in keeping the really resourceful people
5571 from getting the data on the disk (see
5572 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5573 Thus I concluded that adding the discard option to crypttab is the
5574 right thing to do.
</p
>
5576 <p
>I considered using the noop I/O scheduler, as several recommended
5577 it for SSD, but others recommended deadline and a benchmark I found
5578 indicated that deadline might be better for interactive use.
</p
>
5580 <p
>I also considered using the
'discard
' file system option for ext3
5581 and ext4, but read that it would give a performance hit ever time a
5582 file is removed, and thought it best to that that slowdown once a day
5583 instead of during my work.
</p
>
5585 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5586 this is already done by Debian Edu.
</p
>
5588 <p
>I have not yet started on the user space tuning. I expect
5589 iceweasel need some tuning, and perhaps other applications too, but
5590 have not yet had time to investigate those parts.
</p
>
5592 <p
>The package should work on Ubuntu too, but I have not yet tested it
5595 <p
>As for the answer to the question in the title of this blog post,
5596 as far as I know, the only solution I know about is to replace the
5597 disk. It might be possible to flash it with Intel firmware instead of
5598 the Lenovo firmware. But I have not tried and did not want to do so
5599 without approval from Lenovo as I wanted to keep the warranty on the
5600 disk until a solution was found and they wanted the broken disks
5606 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5607 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5608 <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>
5609 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5610 <description><p
>A few days ago, I wrote about
5611 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5612 problems I experienced with my new X230 and its SSD disk
</a
>, which
5613 was dying during installation because it is unable to cope with
5614 sustained write. My supplier is in contact with
5615 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5616 replacement disk to try to fix the problem. They decided to send an
5617 identical model, so my hopes for a permanent fix was slim.
</p
>
5619 <p
>Anyway, today I got the replacement disk and tried to install
5620 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5621 same firmware version as the original. This time my hope raised
5622 slightly as the installation progressed, as the original disk used to
5623 die after
4-
7% of the disk was written to, while this time it kept
5624 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5625 died again and I was back on square one. I still do not have a new
5626 laptop with a disk I can trust. I can not live with a disk that might
5627 lock up when I download a new
5628 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5629 other large files. I look forward to hearing from my supplier with
5630 the next proposal from Lenovo.
</p
>
5632 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5633 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5634 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5635 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5636 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5637 P/N
45N8295, P0C38732.
</p
>
5639 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5640 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5641 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5642 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5643 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5644 P/N
45N8295, P0C38732.
</p
>
5646 <p
>The only difference is in the first number (serial number?), ISN,
5647 SA, date and WNPP values. Mentioning all the details here in case
5648 someone is able to use the information to find a way to identify the
5649 failing disk among working ones (if any such working disk actually
5655 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5656 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5657 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5658 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5659 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5660 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5661 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5662 member assosiation NUUG
</a
> and
5663 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5664 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5665 Bitraf
</a
>.
</p
>
5667 <p
>It starts
10:
00 and continue until late evening. Everyone is
5668 welcome, and there is no fee to participate. There is on the other
5669 hand limited space, and only room for
30 people. Please put your name
5670 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5671 wiki page
</a
> if you plan to join us.
</p
>
5676 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5677 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5678 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5679 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5680 <description><p
>Half a year ago, I reported that I had to find a
5681 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5682 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5683 time to spend on it, and it took a while to find a model I believe
5684 will do the job, but two days ago the replacement finally arrived. I
5686 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5687 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5688 a roaming workstation, and it seemed to work flawlessly. But my
5689 second installation with encrypted disk was not as successful. More
5690 on that below.
</p
>
5692 <p
>I had a hard time trying to track down a good laptop, as my most
5693 important requirements (robust and with a good keyboard) are never
5694 listed in the feature list. But I did get good help from the search
5695 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5696 allowed me to limit the list of interesting laptops based on my other
5697 requirements. A bit surprising that SSD disk are not disks according
5698 to that search interface, so I had to drop specifying the number of
5699 disks from my search parameters. I also asked around among friends to
5700 get their impression on keyboards and robustness.
</p
>
5702 <p
>So the new laptop arrived, and it is quite a lot wider than the
5703 X41. I am not quite convinced about the keyboard, as it is
5704 significantly wider than my old keyboard, and I have to stretch my
5705 hand a lot more to reach the edges. But the key response is fairly
5706 good and the individual key shape is fairly easy to handle, so I hope
5707 I will get used to it. My old X40 was starting to fail, and I really
5708 needed a new laptop now. :)
</p
>
5710 <p
>Turning off the touch pad was simple. All it took was a quick
5711 visit to the BIOS during boot it disable it.
</p
>
5713 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5714 lock up during load. And this happen when installing Debian Wheezy
5715 with encrypted disk, while the disk is being filled with random data.
5716 I also tested to install Ubuntu Raring, and it happen there too if I
5717 reenable the code to fill the disk with random data (it is disabled by
5718 default in Ubuntu). And the bug with is already known. It was
5719 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5720 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5721 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5722 kernel developers as
5723 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5724 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5725 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5726 Lenovo forums, both for
5727 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5728 2012-
11-
10</a
> and for
5729 <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
5730 03-
20-
2013</a
>. The problem do not only affect installation. The
5731 reports state that the disk lock up during use if many writes are done
5732 on the disk, so it is much no use to work around the installation
5733 problem and end up with a computer that can lock up at any moment.
5735 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5736 available
</a
> that will lock up the hard drive after running a few
5737 minutes by writing to a file.
</p
>
5739 <p
>I
've contacted my supplier and asked how to handle this, and after
5740 contacting PCHELP Norway (request
01D1FDP) which handle support
5741 requests for Lenovo, his first suggestion was to upgrade the disk
5742 firmware. Unfortunately there is no newer firmware available from
5743 Lenovo, as my disk already have the most recent one (version LF1i). I
5744 hope to hear more from him today and hope the problem can be
5750 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5751 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5752 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5753 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5754 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5755 trusty old Thinkpad X41. Unfortunately I did not have much time to
5756 spend on it, but today the replacement finally arrived. I ended up
5757 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5758 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5759 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5760 this, it is installing what I hope will be a more final installation,
5761 with a encrypted hard drive to ensure any dope head stealing it end up
5762 with an expencive door stop.
</p
>
5764 <p
>I had a hard time trying to track down a good laptop, as my most
5765 important requirements (robust and with a good keyboard) are never
5766 listed in the feature list. But I did get good help from the search
5767 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5768 allowed me to limit the list of interesting laptops based on my other
5769 requirements. A bit surprising that SSD disk are not disks, so I had
5770 to drop number of disks from my search parameters.
</p
>
5772 <p
>I am not quite convinced about the keyboard, as it is significantly
5773 wider than my old keyboard, and I have to stretch my hand a lot more
5774 to reach the edges. But the key response is fairly good and the
5775 individual key shape is fairly easy to handle, so I hope I will get
5776 used to it. My old X40 was starting to fail, and I really needed a
5777 new laptop now. :)
</p
>
5779 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5784 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5785 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5786 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5787 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5788 <description><p
>It annoys me when the computer fail to do automatically what it is
5789 perfectly capable of, and I have to do it manually to get things
5790 working. One such task is to find out what firmware packages are
5791 needed to get the hardware on my computer working. Most often this
5792 affect the wifi card, but some times it even affect the RAID
5793 controller or the ethernet card. Today I pushed version
0.4 of the
5794 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5795 including a new script isenkram-autoinstall-firmware handling the
5796 process of asking all the loaded kernel modules what firmware files
5797 they want, find debian packages providing these files and install the
5798 debian packages. Here is a test run on my laptop:
</p
>
5800 <p
><pre
>
5801 # isenkram-autoinstall-firmware
5802 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5803 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5804 info: locating packages with the requested firmware files
5805 info: Updating APT sources after adding non-free APT source
5806 info: trying to install firmware-ipw2x00
5809 Preconfiguring packages ...
5810 Selecting previously deselected package firmware-ipw2x00.
5811 (Reading database ...
259727 files and directories currently installed.)
5812 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5813 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5815 </pre
></p
>
5817 <p
>When all the requested firmware is present, a simple message is
5818 printed instead:
</p
>
5820 <p
><pre
>
5821 # isenkram-autoinstall-firmware
5822 info: did not find any firmware files requested by loaded kernel modules. exiting
5824 </pre
></p
>
5826 <p
>It could use some polish, but it is already working well and saving
5827 me some time when setting up new machines. :)
</p
>
5829 <p
>So, how does it work? It look at the set of currently loaded
5830 kernel modules, and look up each one of them using modinfo, to find
5831 the firmware files listed in the module meta-information. Next, it
5832 download the Contents file from a nearby APT mirror, and search for
5833 the firmware files in this file to locate the package with the
5834 requested firmware file. If the package is in the non-free section, a
5835 non-free APT source is added and the package is installed using
5836 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5839 <p
>I hope someone find time to implement a more polished version of
5840 this script as part of the hw-detect debian-installer module, to
5841 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5842 #
655507</a
>. There really is no need to insert USB sticks with
5843 firmware during a PXE install when the packages already are available
5844 from the nearby Debian mirror.
</p
>
5849 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5850 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5851 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5852 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5853 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5854 the screen just turn black when Linux boot, either during installation
5855 or on first boot from the hard disk. I
've seen it once in a while the
5856 last few years, but only recently understood the cause. I
've seen it
5857 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5858 The reason seem to be in the wiring of some laptops. The system to
5859 control the screen background light is inverted, so when Linux try to
5860 turn the brightness fully on, it end up turning it off instead. I do
5861 not know which Linux drivers are affected, but this post is about the
5862 i915 driver used by the
5863 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5864 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5866 <p
>The problem can be worked around two ways. Either by adding
5867 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5868 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5869 option when it load the i915 kernel module. On Debian and Ubuntu, it
5870 can be done by running these commands as root:
</p
>
5873 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5874 update-initramfs -u -k all
5877 <p
>Since March
2012 there is
5878 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5879 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5880 hardware have this problem, and get the driver to invert the
5881 brightness setting automatically. To use it, one need to add a row in
5882 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5883 intel_quirks array
</a
> in the driver source
5884 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5885 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5886 number (vendor number
8086 is assumed) and subdevice vendor and device
5889 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5890 -vvnn
</tt
> for the video card in question:
</p
>
5892 <p
><pre
>
5893 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5894 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5895 (rev
09) (prog-if
00 [VGA controller])
5896 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5897 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5898 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5899 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5900 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5902 Interrupt: pin A routed to IRQ
42
5903 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5904 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5905 Region
4: I/O ports at
4000 [size=
64]
5906 Expansion ROM at
<unassigned
> [disabled]
5907 Capabilities:
<access denied
>
5908 Kernel driver in use: i915
5909 </pre
></p
>
5911 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5913 <p
><pre
>
5914 struct intel_quirk intel_quirks[] = {
5916 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5917 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5920 </pre
></p
>
5922 <p
>According to the kernel module instructions (as seen using
5923 <tt
>modinfo i915
</tt
>), information about hardware needing the
5924 invert_brightness flag should be sent to the
5925 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5926 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5927 developers. But my email about the laptop sent
2013-
06-
03 have not
5929 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5930 web archive for the mailing list
</a
>, so I suspect they do not accept
5931 emails from non-subscribers. Because of this, I sent my patch also to
5932 the Debian bug tracking system instead as
5933 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5934 sure the patch is not lost.
</p
>
5936 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5937 with this problem working properly with Linux. If you use Gnome, your
5938 worries should be over at this point. But if you use KDE, there is
5939 something in KDE ignoring the invert_brightness setting and turning on
5940 the screen during login. I
've reported it to Debian as
5941 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5942 have no idea yet how to figure out exactly what subsystem is doing
5943 this. Perhaps you can help? Perhaps you know what the Gnome
5944 developers did to handle this, and this can give a clue to the KDE
5945 developers? Or you know where in KDE the screen brightness is changed
5946 during login? If so, please update the BTS report (or get in touch if
5947 you do not know how to update BTS).
</p
>
5949 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5950 acpi_backlight=vendor, to disable ACPI backlight support completely,
5951 as the ACPI information on the machine is trash and it is better to
5952 leave it to the intel video driver to control the screen
5953 backlight.
</p
>
5958 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5959 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5960 <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>
5961 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5962 <description><p
>Two days ago, I asked
5963 <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
5964 I could install Linux on a Packard Bell EasyNote LV computer
5965 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5966 with the obstacles put in the way of Linux users on a laptop with UEFI
5967 and Windows
8.
</p
>
5969 <p
>I never found out if the cause of my problems were the use of UEFI
5970 secure booting or fast boot. I suspect fast boot was the problem,
5971 causing the firmware to boot directly from HD without considering any
5972 key presses and alternative devices, but do not know UEFI settings
5973 enough to tell.
</p
>
5975 <p
>There is no way to install Linux on the machine in question without
5976 opening the box and disconnecting the hard drive! This is as far as I
5977 can tell, the only way to get access to the firmware setup menu
5978 without accepting the Windows
8 license agreement. I am told (and
5979 found description on how to) that it is possible to configure the
5980 firmware setup once booted into Windows
8. But as I believe the terms
5981 of that agreement are completely unacceptable, accepting the license
5982 was never an alternative. I do not enter agreements I do not intend
5983 to follow.
</p
>
5985 <p
>I feared I had to return the laptops and ask for a refund, and
5986 waste many hours on this, but luckily there was a way to get it to
5987 work. But I would not recommend it to anyone planning to run Linux on
5988 it, and I have become sceptical to Windows
8 certified laptops. Is
5989 this the way Linux will be forced out of the market place, by making
5990 it close to impossible for
"normal
" users to install Linux without
5991 accepting the Microsoft Windows license terms? Or at least not
5992 without risking to loose the warranty?
</p
>
5994 <p
>I
've updated the
5995 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5996 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5997 do not have to struggle as much as I did to get Linux into the
6000 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6001 Michael Tokarev and others for feedback and ideas.
</p
>
6006 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
6007 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
6008 <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>
6009 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
6010 <description><p
>I
've run into quite a problem the last few days. I bought three
6011 new laptops for my parents and a few others. I bought Packard Bell
6012 Easynote LV to run Kubuntu on and use as their home computer. But I
6013 am completely unable to figure out how to install Linux on it. The
6014 computer is preinstalled with Windows
8, and I suspect it uses UEFI
6015 instead of a BIOS to boot.
</p
>
6017 <p
>The problem is that I am unable to get it to PXE boot, and unable
6018 to get it to boot the Linux installer from my USB stick. I have yet
6019 to try the DVD install, and still hope it will work. when I turn on
6020 the computer, there is no information on what buttons to press to get
6021 the normal boot menu. I expect to get some boot menu to select PXE or
6022 USB stick booting. When booting, it first ask for the language to
6023 use, then for some regional settings, and finally if I will accept the
6024 Windows
8 terms of use. As these terms are completely unacceptable to
6025 me, I have no other choice but to turn off the computer and try again
6026 to get it to boot the Linux installer.
</p
>
6028 <p
>I have gathered my findings so far on a Linlap page about the
6029 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6030 EasyNote LV
</a
> model. If you have any idea how to get Linux
6031 installed on this machine, please get in touch or update that wiki
6032 page. If I can
't find a way to install Linux, I will have to return
6033 the laptop to the seller and find another machine for my parents.
</p
>
6035 <p
>I wonder, is this the way Linux will be forced out of the market
6036 using UEFI and
"secure boot
" by making it impossible to install Linux
6037 on new Laptops?
</p
>
6042 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6043 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6045 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6046 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6047 an operating system based on Debian intended for use in schools. It
6048 contain a turn-key solution for the computer network provided to
6049 pupils in the primary schools. It provide both the central server,
6050 network boot servers and desktop environments with heaps of
6051 educational software. The project was founded almost
12 years ago,
6052 2001-
07-
02. If you want to support the project, which is in need for
6053 cash to fund developer gatherings and other project related activity,
6054 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6055 donate some money
</a
>.
6057 <p
>A topic that come up again and again on the Debian Edu mailing
6058 lists and elsewhere, is the question on how to transform a Debian or
6059 Ubuntu installation into a Debian Edu installation. It isn
't very
6060 hard, and last week I wrote a script to replicate the steps done by
6061 the Debian Edu installer.
</p
>
6063 <p
>The script,
6064 <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/
>
6065 in the debian-edu-config package, will go through these six steps and
6066 transform an existing Debian Wheezy or Ubuntu (untested) installation
6067 into a Debian Edu Workstation:
</p
>
6071 <li
>Add skolelinux related APT sources.
</li
>
6072 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6073 <li
>Install debian-edu-install to load preseeding values and pull in
6074 our configuration.
</li
>
6075 <li
>Preseed debconf database with profile setup in
6076 /etc/debian-edu/config, and run tasksel to install packages
6077 according to the profile specified in the config above,
6078 overriding some of the Debian automation machinery.
</li
>
6079 <li
>Run debian-edu-cfengine-D installation to configure everything
6080 that could not be done using preseeding.
</li
>
6081 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6085 <p
>There are some steps in the Debian Edu installation that can not be
6086 replicated like this. Disk partitioning and LVM setup, for example.
6087 So this script just assume there is enough disk space to install all
6088 the needed packages.
</p
>
6090 <p
>The script was created to help a Debian Edu student working on
6091 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6092 Debian Edu client, and using it he can take the existing
6093 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6094 transform it into a fully functioning Debian Edu Workstation (or
6095 Roaming Workstation, or whatever :).
</p
>
6097 <p
>The default setting in the script is to create a KDE Workstation.
6098 If a LXDE based Roaming workstation is wanted instead, modify the
6099 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6101 <p
><pre
>
6102 PROFILE=
"Roaming-Workstation
"
6103 DESKTOP=
"lxde
"
6104 </pre
></p
>
6106 <p
>The script could even become useful to set up Debian Edu servers in
6107 the cloud, by starting with a virtual Debian installation at some
6108 virtual hosting service and setting up all the services on first
6114 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6115 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6116 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6117 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6118 <description><P
>In January,
6119 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6120 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6121 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6122 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6123 marvellous construction system from Denmark. We also created
6124 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6125 a place to take notes and write down our plans and hopes. And several
6126 people showed up to help. I was very happy to see the effect of my
6127 call. Since the small start, we have a debtags tag
6128 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6129 tag for LEGO related packages, and now count
10 packages related to
6130 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6132 <p
><table
>
6133 <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
>
6134 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6135 <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
>
6136 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6137 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6138 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6139 <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
>
6140 <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
>
6141 <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
>
6142 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6143 </table
></p
>
6145 <p
>Some of these are available in Wheezy, and all but one are
6146 currently available in Jessie/testing. leocad is so far only
6147 available in experimental.
</p
>
6149 <p
>If you care about LEGO in Debian, please join us on IRC and help
6150 adding the rest of the great free software tools available on Linux
6151 for LEGO designers.
</p
>
6156 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6157 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6158 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6159 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6160 <description><p
>When I woke up this morning, I was very happy to see that the
6161 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6162 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6163 Debian release, and I expect to move my machines at home over to it fairly
6166 <p
>The new debian release contain heaps of new stuff, and one program
6167 in particular make me very happy to see included. The
6168 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6169 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6170 included for the first time. Alongside similar programs like
6171 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6172 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6173 it allow for visual programming where syntax errors can not happen,
6174 and a friendly programming environment for learning to control the
6175 computer. Scratch will also be included in the next release of Debian
6178 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6179 Edu/Skolelinux release too. The
6180 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6181 alpha release
</a
> went out last week, and the next should soon
6187 <title>Isenkram
0.2 finally in the Debian archive
</title>
6188 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6189 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6190 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6191 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6192 package
</a
> finally made it into the archive, after lingering in NEW
6193 for many months. I uploaded it to the Debian experimental suite
6194 2013-
01-
27, and today it was accepted into the archive.
</p
>
6196 <p
>Isenkram is a system for suggesting to users what packages to
6197 install to work with a pluggable hardware device. The suggestion pop
6198 up when the device is plugged in. For example if a Lego Mindstorm NXT
6199 is inserted, it will suggest to install the program needed to program
6200 the NXT controller. Give it a go, and report bugs and suggestions to
6206 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6207 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6208 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6209 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6210 <description><p
>My
6211 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6212 bitcoin related blog post
</a
> mentioned that the new
6213 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6214 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6215 2013-
01-
19, and have been available in unstable since then. It was
6216 automatically copied to Ubuntu, and is available in their Raring
6217 version too.
</p
>
6219 <p
>But there is a strange problem with the build that block this new
6220 version from being available on the i386 and kfreebsd-i386
6221 architectures. For some strange reason, the autobuilders in Debian
6222 for these architectures fail to run the test suite on these
6223 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6224 We are so far unable to reproduce it when building it manually, and
6225 no-one have been able to propose a fix. If you got an idea what is
6226 failing, please let us know via the BTS.
</p
>
6228 <p
>One feature that is annoying me with of the bitcoin client, because
6229 I often run low on disk space, is the fact that the client will exit
6230 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6231 #
696715</a
>). So make sure you have enough disk space when you run
6234 <p
>As usual, if you use bitcoin and want to show your support of my
6235 activities, please send Bitcoin donations to my address
6236 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6241 <title>Welcome to the world, Isenkram!
</title>
6242 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6244 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6245 <description><p
>Yesterday, I
6246 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6247 for testers
</a
> for my prototype for making Debian better at handling
6248 pluggable hardware devices, which I
6249 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6250 out to create
</a
> earlier this month. Several valuable testers showed
6251 up, and caused me to really want to to open up the development to more
6252 people. But before I did this, I want to come up with a sensible name
6253 for this project. Today I finally decided on a new name, and I have
6254 renamed the project from hw-support-handler to this new name. In the
6255 process, I moved the source to git and made it available as a
6256 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6257 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6258 To fetch and build the latest version of the source, use
</p
>
6261 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6262 cd isenkram
&& git-buildpackage -us -uc
6265 <p
>I have not yet adjusted all files to use the new name yet. If you
6266 want to hack on the source or improve the package, please go ahead.
6267 But please talk to me first on IRC or via email before you do major
6268 changes, to make sure we do not step on each others toes. :)
</p
>
6270 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6271 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6272 stuff, in other words. I
've been told it is the Norwegian variant of
6273 the German word eisenkram, for those that are familiar with that
6276 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6277 instructions, to avoid confusing people with an error from the signing
6280 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6281 clone argument to avoid the need for authentication.
</p
>
6286 <title>First prototype ready making hardware easier to use in Debian
</title>
6287 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6288 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6289 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6290 <description><p
>Early this month I set out to try to
6291 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6292 the Debian support for pluggable hardware devices
</a
>. Now my
6293 prototype is working, and it is ready for a larger audience. To test
6295 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6296 from the Debian Edu subversion repository
</a
>, build and install the
6297 package. You might have to log out and in again activate the
6298 autostart script.
</p
>
6300 <p
>The design is simple:
</p
>
6304 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6305 hw-support-handlerd to start when the user log in.
</li
>
6307 <li
>This program listen for kernel events about new hardware (directly
6308 from the kernel like udev does), not using HAL dbus events as I
6309 initially did.
</li
>
6311 <li
>When new hardware is inserted, look up the hardware modalias in
6312 the APT database, a database
6313 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6314 via HTTP
</a
> and a database available as part of the package.
</li
>
6316 <li
>If a package is mapped to the hardware in question, the package
6317 isn
't installed yet and this is the first time the hardware was
6318 plugged in, show a desktop notification suggesting to install the
6319 package or packages.
</li
>
6321 <li
>If the user click on the
'install package now
' button, ask
6322 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6324 <li
>aptdaemon ask for root password or sudo password, and install the
6325 package while showing progress information in a window.
</li
>
6329 <p
>I still need to come up with a better name for the system. Here
6330 are some screen shots showing the prototype in action. First the
6331 notification, then the password request, and finally the request to
6332 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6334 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6335 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6336 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6337 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6338 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6340 <p
>The prototype still need to be improved with longer timeouts, but
6341 is already useful. The database of hardware to package mappings also
6342 need more work. It is currently compatible with the Ubuntu way of
6343 storing such information in the package control file, but could be
6344 changed to use other formats instead or in addition to the current
6345 method. I
've dropped the use of discover for this mapping, as the
6346 modalias approach is more flexible and easier to use on Linux as long
6347 as the Linux kernel expose its modalias strings directly.
</p
>
6349 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6350 here is the command required to check out and build the source: Use
6351 '<tt
>svn checkout
6352 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6353 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6354 devscripts package.
</p
>
6356 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6357 renamed to Isenkram and the source moved from the Debian Edu
6358 subversion repository to a Debian collab-maint git repository. See
6359 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6360 instructions
</a
> for details.
</p
>
6365 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6366 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6367 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6368 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6369 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6370 suddenly in bed. With a quiet whimper, it went completely quiet and
6371 black. The power button was no longer able to turn it on. It was a
6372 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6373 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6374 Compaq I had before that. Now I need to find a replacement. To keep
6375 going during Christmas, I moved the one year old SSD disk to my old
6376 X40 where it fitted (only one I had left that could use it), but it is
6377 not a durable solution.
6379 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6380 got a new one more than
10 years ago. It still holds true.:)
</p
>
6384 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6385 than A4).
</li
>
6386 <li
>Robust, it will be in my backpack every day.
</li
>
6387 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6388 <li
>Long battery life time. Preferable a week.
</li
>
6389 <li
>Internal WIFI network card.
</li
>
6390 <li
>Internal Twisted Pair network card.
</li
>
6391 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6392 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6393 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6395 <li
>Hardware supported by Debian Stable, ie the default kernel and
6396 X.org packages.
</li
>
6397 <li
>Quiet, preferably fan free (or at least not using the fan most of
6402 <p
>You will notice that there are no RAM and CPU requirements in the
6403 list. The reason is simply that the specifications on laptops the
6404 last
10-
15 years have been sufficient for my needs, and I have to look
6405 at other features to choose my laptop. But are there still made as
6406 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6407 robust, and Thinkpads seem to be heading in the wrong direction since
6408 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6409 still be useful.
</p
>
6411 <p
>Perhaps I should rethink my needs, and look for a pad with an
6412 external keyboard? I
'll have to check the
6413 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6414 well-supported laptops, or perhaps just buy one preinstalled from one
6415 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6416 Pre-loaded site
</a
>.
</p
>
6421 <title>How to find a browser plugin supporting a given MIME type
</title>
6422 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6423 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6424 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6425 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6426 install to get support for a given MIME type. Thanks to
6427 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6428 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6429 Unfortunately, not very many packages provide the needed meta
6430 information, Anyway, here is a small script to look up all browser
6431 plugin packages announcing ther MIME support using this specification:
</p
>
6437 def pkgs_handling_mimetype(mimetype):
6442 version = pkg.candidate
6444 version = pkg.installed
6447 record = version.record
6448 if not record.has_key(
'Npp-MimeType
'):
6450 mime_types = record[
'Npp-MimeType
'].split(
',
')
6451 for t in mime_types:
6452 t = t.rstrip().strip()
6454 thepkgs.append(pkg.name)
6456 mimetype =
"audio/ogg
"
6457 if
1 < len(sys.argv):
6458 mimetype = sys.argv[
1]
6459 print
"Browser plugin packages supporting %s:
" % mimetype
6460 for pkg in pkgs_handling_mimetype(mimetype):
6461 print
" %s
" %pkg
6464 <p
>It can be used like this to look up a given MIME type:
</p
>
6467 % ./apt-find-browserplug-for-mimetype
6468 Browser plugin packages supporting audio/ogg:
6470 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6471 Browser plugin packages supporting application/x-shockwave-flash:
6472 browser-plugin-gnash
6476 <p
>In Ubuntu this mechanism is combined with support in the browser
6477 itself to query for plugins and propose to install the needed
6478 packages. It would be great if Debian supported such feature too. Is
6479 anyone working on adding it?
</p
>
6481 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6482 request for icweasel support for this feature is
6483 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6484 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6485 of manpower and wish for a different design is the reason thus feature
6486 is not yet in iceweasel from Debian.
</p
>
6491 <title>What is the most supported MIME type in Debian?
</title>
6492 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6493 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6494 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6495 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6496 proposal to add AppStream information to the Debian archive
</a
>, is a
6497 proposal to make it possible for a Desktop application to propose to
6498 the user some package to install to gain support for a given MIME
6499 type, font, library etc. that is currently missing. With such
6500 mechanism in place, it would be possible for the desktop to
6501 automatically propose and install leocad if some LDraw file is
6502 downloaded by the browser.
</p
>
6504 <p
>To get some idea about the current content of the archive, I decided
6505 to write a simple program to extract all .desktop files from the
6506 Debian archive and look up the claimed MIME support there. The result
6508 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6509 site
</a
>. Using the collected information, it become possible to
6510 answer the question in the title. Here are the
20 most supported MIME
6511 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6512 The complete list is available from the link above.
</p
>
6514 <p
><strong
>Debian Stable:
</strong
></p
>
6518 ----- -----------------------
6534 18 application/x-ogg
6541 <p
><strong
>Debian Testing:
</strong
></p
>
6545 ----- -----------------------
6561 18 application/x-ogg
6568 <p
><strong
>Debian Unstable:
</strong
></p
>
6572 ----- -----------------------
6589 18 application/x-ogg
6595 <p
>I am told that PackageKit can provide an API to access the kind of
6596 information mentioned in DEP-
11. I have not yet had time to look at
6597 it, but hope the PackageKit people in Debian are on top of these
6600 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6601 discovering a typo in my script.
</p
>
6606 <title>Using modalias info to find packages handling my hardware
</title>
6607 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6608 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6609 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6610 <description><p
>Yesterday, I wrote about the
6611 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6612 values provided by the Linux kernel
</a
> following my hope for
6613 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6614 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6615 modalias values attached to package names can be used to map packages
6616 to hardware. This allow the system to look up and suggest relevant
6617 packages when I plug in some new hardware into my machine, and replace
6618 discover and discover-data as the database used to map hardware to
6621 <p
>I create a modaliases file with entries like the following,
6622 containing package name, kernel module name (if relevant, otherwise
6623 the package name) and globs matching the relevant hardware
6626 <p
><blockquote
>
6627 Package: package-name
6628 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6629 </blockquote
></p
>
6631 <p
>It is fairly trivial to write code to find the relevant packages
6632 for a given modalias value using this file.
</p
>
6634 <p
>An entry like this would suggest the video and picture application
6635 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6637 <p
><blockquote
>
6639 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6640 </blockquote
></p
>
6642 <p
>An entry like this would suggest the pcmciautils package when a
6643 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6645 <p
><blockquote
>
6646 Package: pcmciautils
6647 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6648 </blockquote
></p
>
6650 <p
>An entry like this would suggest the package colorhug-client when
6651 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6653 <p
><blockquote
>
6654 Package: colorhug-client
6655 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6656 </blockquote
></p
>
6658 <p
>I believe the format is compatible with the format of the Packages
6659 file in the Debian archive. Ubuntu already uses their Packages file
6660 to store their mappings from packages to hardware.
</p
>
6662 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6663 announce the hardware it support in a way my prototype understand.
6664 This allow those publishing packages in an APT source outside the
6665 Debian archive as well as those backporting packages to make sure the
6666 hardware mapping are included in the package meta information. I
've
6667 tested such header in the pymissile package, and its modalias mapping
6668 is working as it should with my prototype. It even made it to Ubuntu
6671 <p
>To test if it was possible to look up supported hardware using only
6672 the shell tools available in the Debian installer, I wrote a shell
6673 implementation of the lookup code. The idea is to create files for
6674 each modalias and let the shell do the matching. Please check out and
6676 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6677 shell script. It run without any extra dependencies and fetch the
6678 hardware mappings from the Debian archive and the subversion
6679 repository where I currently work on my prototype.
</p
>
6681 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6682 install yubikey-personalization:
</p
>
6684 <p
><blockquote
>
6685 % ./hw-support-lookup
6686 <br
>yubikey-personalization
6688 </blockquote
></p
>
6690 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6691 propose to install the pcmciautils package:
</p
>
6693 <p
><blockquote
>
6694 % ./hw-support-lookup
6695 <br
>pcmciautils
6697 </blockquote
></p
>
6699 <p
>If you know of any hardware-package mapping that should be added to
6700 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6701 database
</a
>, please tell me about it.
</p
>
6703 <p
>It could be possible to generate several of the mappings between
6704 packages and hardware. One source would be to look at packages with
6705 kernel modules, ie packages with *.ko files in /lib/modules/, and
6706 extract their modalias information. Another would be to look at
6707 packages with udev rules, ie packages with files in
6708 /lib/udev/rules.d/, and extract their vendor/model information to
6709 generate a modalias matching rule. I have not tested any of these to
6710 see if it work.
</p
>
6712 <p
>If you want to help implementing a system to let us propose what
6713 packages to install when new hardware is plugged into a Debian
6714 machine, please send me an email or talk to me on
6715 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6720 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6721 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6722 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6723 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6724 <description><p
>While looking into how to look up Debian packages based on hardware
6725 information, to find the packages that support a given piece of
6726 hardware, I refreshed my memory regarding modalias values, and decided
6727 to document the details. Here are my findings so far, also available
6729 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6730 Debian Edu subversion repository
</a
>:
6732 <p
><strong
>Modalias decoded
</strong
></p
>
6734 <p
>This document try to explain what the different types of modalias
6735 values stands for. It is in part based on information from
6736 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6737 &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;,
6738 &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
6739 &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;.
6741 <p
>The modalias entries for a given Linux machine can be found using
6742 this shell script:
</p
>
6745 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6748 <p
>The supported modalias globs for a given kernel module can be found
6749 using modinfo:
</p
>
6752 % /sbin/modinfo psmouse | grep alias:
6753 alias: serio:ty05pr*id*ex*
6754 alias: serio:ty01pr*id*ex*
6758 <p
><strong
>PCI subtype
</strong
></p
>
6760 <p
>A typical PCI entry can look like this. This is an Intel Host
6761 Bridge memory controller:
</p
>
6763 <p
><blockquote
>
6764 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6765 </blockquote
></p
>
6767 <p
>This represent these values:
</p
>
6772 sv
00001028 (subvendor)
6773 sd
000001AD (subdevice)
6775 sc
00 (bus subclass)
6779 <p
>The vendor/device values are the same values outputted from
'lspci
6780 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6781 0600. The
0600 class is a host bridge. Other useful bus values are
6782 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6784 <p
>Not sure how to figure out the interface value, nor what it
6787 <p
><strong
>USB subtype
</strong
></p
>
6789 <p
>Some typical USB entries can look like this. This is an internal
6790 USB hub in a laptop:
</p
>
6792 <p
><blockquote
>
6793 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6794 </blockquote
></p
>
6796 <p
>Here is the values included in this alias:
</p
>
6799 v
1D6B (device vendor)
6800 p
0001 (device product)
6802 dc
09 (device class)
6803 dsc
00 (device subclass)
6804 dp
00 (device protocol)
6805 ic
09 (interface class)
6806 isc
00 (interface subclass)
6807 ip
00 (interface protocol)
6810 <p
>The
0900 device class/subclass means hub. Some times the relevant
6811 class is in the interface class section. For a simple USB web camera,
6812 these alias entries show up:
</p
>
6814 <p
><blockquote
>
6815 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6816 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6817 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6818 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6819 </blockquote
></p
>
6821 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6822 camera),
0101 is audio control device and
0102 is audio streaming (aka
6823 microphone). Thus this is a camera with microphone included.
</p
>
6825 <p
><strong
>ACPI subtype
</strong
></p
>
6827 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6828 receiver in a Thinkpad X40:
</p
>
6830 <p
><blockquote
>
6831 acpi:IBM0071:PNP0511:
6832 </blockquote
></p
>
6834 <p
>The values between the colons are IDs.
</p
>
6836 <p
><strong
>DMI subtype
</strong
></p
>
6838 <p
>The DMI table contain lots of information about the computer case
6839 and model. This is an entry for a IBM Thinkpad X40, fetched from
6840 /sys/devices/virtual/dmi/id/modalias:
</p
>
6842 <p
><blockquote
>
6843 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6844 </blockquote
></p
>
6846 <p
>The values present are
</p
>
6849 bvn IBM (BIOS vendor)
6850 bvr
1UETB
6WW(
1.66) (BIOS version)
6851 bd
06/
15/
2005 (BIOS date)
6852 svn IBM (system vendor)
6853 pn
2371H4G (product name)
6854 pvr ThinkPadX40 (product version)
6855 rvn IBM (board vendor)
6856 rn
2371H4G (board name)
6857 rvr NotAvailable (board version)
6858 cvn IBM (chassis vendor)
6859 ct
10 (chassis type)
6860 cvr NotAvailable (chassis version)
6863 <p
>The chassis type
10 is Notebook. Other interesting values can be
6864 found in the dmidecode source:
</p
>
6868 4 Low Profile Desktop
6881 17 Main Server Chassis
6882 18 Expansion Chassis
6884 20 Bus Expansion Chassis
6885 21 Peripheral Chassis
6887 23 Rack Mount Chassis
6896 <p
>The chassis type values are not always accurately set in the DMI
6897 table. For example my home server is a tower, but the DMI modalias
6898 claim it is a desktop.
</p
>
6900 <p
><strong
>SerIO subtype
</strong
></p
>
6902 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6903 test machine:
</p
>
6905 <p
><blockquote
>
6906 serio:ty01pr00id00ex00
6907 </blockquote
></p
>
6909 <p
>The values present are
</p
>
6918 <p
>This type is supported by the psmouse driver. I am not sure what
6919 the valid values are.
</p
>
6921 <p
><strong
>Other subtypes
</strong
></p
>
6923 <p
>There are heaps of other modalias subtypes according to
6924 file2alias.c. There is the rest of the list from that source: amba,
6925 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6926 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6927 vmbus, x86cpu and zorro. I did not spend time documenting all of
6928 these, as they do not seem relevant for my intended use with mapping
6929 hardware to packages when new stuff is inserted during run time.
</p
>
6931 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6933 <p
>To check which kernel modules provide support for a given modalias,
6934 one can use the following shell script:
</p
>
6937 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6938 echo
"$id
" ; \
6939 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6943 <p
>The output can look like this (only the first few entries as the
6944 list is very long on my test machine):
</p
>
6948 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6950 FATAL: Module acpi:device: not found.
6952 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6953 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6954 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6955 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6956 acpi:IBM0071:PNP0511:
6957 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6958 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6959 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6963 <p
>If you want to help implementing a system to let us propose what
6964 packages to install when new hardware is plugged into a Debian
6965 machine, please send me an email or talk to me on
6966 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6968 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6969 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6970 in /sys/ with space in them.
</p
>
6975 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6976 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6977 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6978 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6979 <description><p
>As part of my investigation on how to improve the support in Debian
6980 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6981 Launcher and updated the Debian package
6982 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6983 sure udev will fix the device permissions when it is plugged in. I
6984 also added a
"Modaliases
" header to test it in the Debian archive and
6985 hopefully make the package be proposed by jockey in Ubuntu when a user
6986 plug in his rocket launcher. In the process I moved the source to a
6987 git repository under collab-maint, to make it easier for any DD to
6988 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6989 is not very active, but the software still work for me even after five
6990 years of relative silence. The new git repository is not listed in
6991 the uploaded package yet, because I want to test the other changes a
6992 bit more before I upload the new version. If you want to check out
6993 the new version with a .desktop file included, visit the
6994 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6995 view
</a
> or use
"<tt
>git clone
6996 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
7001 <title>Lets make hardware dongles easier to use in Debian
</title>
7002 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
7003 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
7004 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
7005 <description><p
>One thing that annoys me with Debian and Linux distributions in
7006 general, is that there is a great package management system with the
7007 ability to automatically install software packages by downloading them
7008 from the distribution mirrors, but no way to get it to automatically
7009 install the packages I need to use the hardware I plug into my
7010 machine. Even if the package to use it is easily available from the
7011 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7012 suggest to automatically install the python-nxt, nbc and t2n packages
7013 I need to talk to it. When I plug in a Yubikey, it could propose the
7014 yubikey-personalization package. The information required to do this
7015 is available, but no-one have pulled all the pieces together.
</p
>
7017 <p
>Some years ago, I proposed to
7018 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
7019 the discover subsystem to implement this
</a
>. The idea is fairly
7024 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
7025 starting when a user log in.
</li
>
7027 <li
>Set this program up to listen for kernel events emitted when new
7028 hardware is inserted into the computer.
</li
>
7030 <li
>When new hardware is inserted, look up the hardware ID in a
7031 database mapping to packages, and take note of any non-installed
7032 packages.
</li
>
7034 <li
>Show a message to the user proposing to install the discovered
7035 package, and make it easy to install it.
</li
>
7039 <p
>I am not sure what the best way to implement this is, but my
7040 initial idea was to use dbus events to discover new hardware, the
7041 discover database to find packages and
7042 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7045 <p
>Yesterday, I found time to try to implement this idea, and the
7046 draft package is now checked into
7047 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7048 Debian Edu subversion repository
</a
>. In the process, I updated the
7049 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7050 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7051 the relevant packages in Debian, and uploaded a new version
7052 2.2013.01.09 to unstable. I also discovered that the current
7053 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7054 package in Debian no longer discovered any USB devices, because
7055 /proc/bus/usb/devices is no longer present. I ported it to use
7056 libusb as a fall back option to get it working. The fixed package
7057 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7058 because of the freeze).
</p
>
7060 <p
>With this prototype in place, I can insert my Yubikey, and get this
7061 desktop notification to show up (only once, the first time it is
7062 inserted):
</p
>
7064 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7066 <p
>For this prototype to be really useful, some way to automatically
7067 install the proposed packages by pressing the
"Please install
7068 program(s)
" button should to be implemented.
</p
>
7070 <p
>If this idea seem useful to you, and you want to help make it
7071 happen, please help me update the discover-data database with mappings
7072 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7073 list the package you would like to have installed when a given
7074 hardware device is inserted into your computer, and report bugs using
7075 reportbug if it isn
't. Or, if you know of a better way to provide
7076 such mapping, please let me know.
</p
>
7078 <p
>This prototype need more work, and there are several questions that
7079 should be considered before it is ready for production use. Is dbus
7080 the correct way to detect new hardware? At the moment I look for HAL
7081 dbus events on the system bus, because that is the events I could see
7082 on my Debian Squeeze KDE desktop. Are there better events to use?
7083 How should the user be notified? Is the desktop notification
7084 mechanism the best option, or should the background daemon raise a
7085 popup instead? How should packages be installed? When should they
7086 not be installed?
</p
>
7088 <p
>If you want to help getting such feature implemented in Debian,
7089 please send me an email. :)
</p
>
7094 <title>New IRC channel for LEGO designers using Debian
</title>
7095 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7096 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7097 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7098 <description><p
>During Christmas, I have worked a bit on the Debian support for
7099 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7100 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7101 discovered I had to build all the tools myself because none were
7102 already in Debian Squeeze. If Debian support for LEGO is something
7103 you care about, please join me on the IRC channel
7104 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7105 irc.debian.org). There is a lot that could be done to improve the
7106 Debian support for LEGO designers. For example both CAD software
7107 and Mindstorm compilers are missing. :)
</p
>
7109 <p
>Update
2012-
01-
03: A
7110 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7111 including links to Lego related packages is now available.
</p
>
7116 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7117 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7118 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7119 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7120 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7121 year! I hope next year will prove to be a good year.
</p
>
7123 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7124 decentralised
"currency
" that allow people to transfer bitcoins
7125 between each other with minimal overhead, is a very interesting
7126 experiment. And as I wrote a few days ago, the bitcoin situation in
7127 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7128 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7129 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7130 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7131 for one of the ftpmasters to approve the new bitcoin-qt package
7134 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7135 team in Debian, you can easily test the package in Debian Squeeze
7136 using the following steps to get a set of working packages:
</p
>
7138 <blockquote
><pre
>
7139 git clone git://git.debian.org/git/collab-maint/bitcoin
7141 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7142 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7143 </pre
></blockquote
>
7145 <p
>You might have to install some build dependencies as well. The
7146 list of commands should give you two packages, bitcoind and
7147 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7148 client will download the complete set of bitcoin
"blocks
", which need
7149 around
5.6 GiB of data on my machine at the moment. Make sure your
7150 ~/.bitcoin/ directory have lots of spare room if you want to download
7151 all the blocks. The client will warn if the disk is getting full, so
7152 there is not really a problem if you got too little room, but you will
7153 not be able to get all the features out of the client.
</p
>
7155 <p
>As usual, if you use bitcoin and want to show your support of my
7156 activities, please send Bitcoin donations to my address
7157 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7162 <title>A word on bitcoin support in Debian
</title>
7163 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7164 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7165 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7166 <description><p
>It has been a while since I wrote about
7167 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7168 peer-to-peer based crypto-currency, and the reason is simply that I
7169 have been busy elsewhere. But two days ago, I started looking at the
7170 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7171 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7172 is now maintained by a
7173 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7174 people
</a
>, and the grunt work had already been done by this team. We
7175 owe a huge thank you to all these team members. :)
7176 But I was sad to discover that the bitcoin client is missing in
7177 Wheezy. It is only available in Sid (and an outdated client from
7178 backports). The client had several RC bugs registered in BTS blocking
7179 it from entering testing. To try to help the team and improve the
7180 situation, I spent some time providing patches and triaging the bug
7181 reports. I also had a look at the bitcoin package available from Matt
7183 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7184 Ubuntu
</a
>, and moved the useful pieces from that version into the
7185 Debian package.
</p
>
7187 <p
>After checking with the main package maintainer Jonas Smedegaard on
7188 IRC, I pushed several patches into the collab-maint git repository to
7189 improve the package. It now contains fixes for the RC issues (not from
7190 me, but fixed by Scott Howard), build rules for a Qt GUI client
7191 package, konqueror support for the bitcoin: URI and bash completion
7192 setup. As I work on Debian Squeeze, I also created
7193 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7194 patch to backport
</a
> the latest version. Jonas is going to look at
7195 it and try to integrate it into the git repository before uploading a
7196 new version to unstable.
7198 <p
>I would very much like bitcoin to succeed, to get rid of the
7199 centralized control currently exercised in the monetary system. I
7200 find it completely unacceptable that the USA government is collecting
7201 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7202 that the major credit card companies can block legal money
7203 transactions to Wikileaks. But for bitcoin to succeed, more people
7204 need to use bitcoins, and more people need to accept bitcoins when
7205 they sell products and services. Improving the bitcoin support in
7206 Debian is a small step in the right direction, but not enough.
7207 Unfortunately the user experience when browsing the web and wanting to
7208 pay with bitcoin is still not very good. The bitcoin: URI is a step
7209 in the right direction, but need to work in most or every browser in
7210 use. Also the bitcoin-qt client is too heavy to fire up to do a
7211 quick transaction. I believe there are other clients available, but
7212 have not tested them.
</p
>
7215 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7216 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7217 I received
20.15 BTC so far on the address I provided in my blog two
7218 years ago, as can be
7219 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7220 on the blockexplorer service
</a
>. Thank you everyone for your
7221 donation. The blockexplorer service demonstrates quite well that
7222 bitcoin is not quite anonymous and untracked. :) I wonder if the
7223 number of users have gone up since then. If you use bitcoin and want
7224 to show your support of my activity, please send Bitcoin donations to
7225 the same address as last time,
7226 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7231 <title>Git repository for song book for Computer Scientists
</title>
7232 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7233 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7234 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7235 <description><p
>As I
7236 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7237 this summer
</a
>, I have created a Computer Science song book a few
7238 years ago, and today I finally found time to create a public
7239 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7240 repository for the project
</a
>.
</p
>
7242 <p
>If you want to help out, please clone the source and submit patches
7243 to the HTML version. To generate the PDF and PostScript version,
7244 please use prince XML, or let me know about a useful free software
7245 processor capable of creating a good looking PDF from the HTML.
</p
>
7247 <p
>Want to sing? You can still find the song book in HTML, PDF and
7248 PostScript formats at
7249 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7250 Science Songbook
</a
>.
</p
>
7255 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7256 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7257 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7258 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7259 <description><p
>I dag fyller
7260 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7261 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7262 si gratulerer med dagen, Debian!
</p
>
7267 <title>Song book for Computer Scientists
</title>
7268 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7270 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7271 <description><p
>Many years ago, while studying Computer Science at the
7272 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7273 collecting computer related songs for use at parties. The original
7274 version was written in LaTeX, but a few years ago I got help from
7275 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7276 while keeping the ability to create a nice book in PDF format. I have
7277 not had time to maintain the book for a while now, and guess I should
7278 put it up on some public version control repository where others can
7279 help me extend and update the book. If anyone is volunteering to help
7280 me with this, send me an email. Also let me know if there are songs
7281 missing in my book.
</p
>
7283 <p
>I have not mentioned the book on my blog so far, and it occured to
7284 me today that I really should let all my readers share the joys of
7285 singing out load about programming, computers and computer networks.
7286 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7287 12</a
> is about to start (and I am not going). Want to sing? Check
7288 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7289 Computer Science Songbook
</a
>.
7294 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7295 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7296 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7297 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7298 <description><p
>At work we have heaps of servers. I believe the total count is
7299 around
1000 at the moment. To be able to get help from the vendors
7300 when something go wrong, we want to keep the firmware on the servers
7301 up to date. If the firmware isn
't the latest and greatest, the
7302 vendors typically refuse to start debugging any problems until the
7303 firmware is upgraded. So before every reboot, we want to upgrade the
7304 firmware, and we would really like everyone handling servers at the
7305 university to do this themselves when they plan to reboot a machine.
7306 For that to happen we at the unix server admin group need to provide
7307 the tools to do so.
</p
>
7309 <p
>To make firmware upgrading easier, I am working on a script to
7310 fetch and install the latest firmware for the servers we got. Most of
7311 our hardware are from Dell and HP, so I have focused on these servers
7312 so far. This blog post is about the Dell part.
</P
>
7314 <p
>On the Dell FTP site I was lucky enough to find
7315 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7316 with firmware information for all
11th generation servers, listing
7317 which firmware should be used on a given model and where on the FTP
7318 site I can find it. Using a simple perl XML parser I can then
7319 download the shell scripts Dell provides to do firmware upgrades from
7320 within Linux and reboot when all the firmware is primed and ready to
7321 be activated on the first reboot.
</p
>
7323 <p
>This is the Dell related fragment of the perl code I am working on.
7324 Are there anyone working on similar tools for firmware upgrading all
7325 servers at a site? Please get in touch and lets share resources.
</p
>
7327 <p
><pre
>
7331 use File::Temp qw(tempdir);
7333 # Install needed RHEL packages if missing
7335 'XML::Simple
' =
> 'perl-XML-Simple
',
7337 for my $module (keys %rhelmodules) {
7338 eval
"use $module;
";
7340 my $pkg = $rhelmodules{$module};
7341 system(
"yum install -y $pkg
");
7342 eval
"use $module;
";
7346 my $errorsto =
'pere@hungry.com
';
7352 sub run_firmware_script {
7353 my ($opts, $script) = @_;
7355 print STDERR
"fail: missing script name\n
";
7358 print STDERR
"Running $script\n\n
";
7360 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7361 print STDERR
"success: firmware script ran succcessfully\n
";
7363 print STDERR
"fail: firmware script returned error\n
";
7367 sub run_firmware_scripts {
7368 my ($opts, @dirs) = @_;
7369 # Run firmware packages
7370 for my $dir (@dirs) {
7371 print STDERR
"info: Running scripts in $dir\n
";
7372 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7373 while (my $s = readdir $dh) {
7374 next if $s =~ m/^\.\.?/;
7375 run_firmware_script($opts,
"$dir/$s
");
7383 print STDERR
"info: Downloading $url\n
";
7384 system(
"wget --quiet \
"$url\
"");
7389 my $product = `dmidecode -s system-product-name`;
7392 if ($product =~ m/PowerEdge/) {
7394 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7395 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7397 my $tmpdir = tempdir(
7401 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7402 system(
'gunzip Catalog.xml.gz
');
7403 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7404 # -q is quiet, disabling interactivity and reducing console output
7405 my $fwopts =
"-q
";
7407 for my $url (@paths) {
7408 fetch_dell_fw($url);
7410 run_firmware_scripts($fwopts, $tmpdir);
7412 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7413 print STDERR
"error: Please report to $errorsto.\n
";
7417 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7418 print STDERR
"error: Please report to $errorsto.\n
";
7424 my $url =
"ftp://ftp.us.dell.com/$path
";
7428 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7429 # firmware packages to download from Dell. Only work for Linux
7430 # machines and
11th generation Dell servers.
7431 sub fetch_dell_fw_list {
7432 my $filename = shift;
7434 my $product = `dmidecode -s system-product-name`;
7436 my ($mybrand, $mymodel) = split(/\s+/, $product);
7438 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7440 my $xml = XMLin($filename);
7442 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7443 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7444 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7446 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7447 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7449 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7451 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7453 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7456 for my $component (@{$xml-
>{SoftwareComponent}}) {
7457 my $componenttype = $component-
>{ComponentType}-
>{value};
7459 # Drop application packages, only firmware and BIOS
7460 next if
'APAC
' eq $componenttype;
7462 my $cpath = $component-
>{path};
7463 for my $path (@paths) {
7464 if ($cpath =~ m%/$path$%) {
7465 push(@paths, $cpath);
7473 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7474 it could work on other platforms with some tweaking. Anyone know a
7475 index like Catalog.xml is available from HP for HP servers? At the
7476 moment I maintain a similar list manually and it is quickly getting
7482 <title>How is booting into runlevel
1 different from single user boots?
</title>
7483 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7484 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7485 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7486 <description><p
>Wouter Verhelst have some
7487 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7488 comments and opinions
</a
> on my blog post on
7489 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7490 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7491 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7492 default KDE desktop in Debian
</a
>. I only have time to address one
7493 small piece of his comment now, and though it best to address the
7494 misunderstanding he bring forward:
</p
>
7496 <p
><blockquote
>
7497 Currently, a system admin has four options: [...] boot to a
7498 single-user system (by adding
'single
' to the kernel command line;
7499 this runs rcS and rc1 scripts)
7500 </blockquote
></p
>
7502 <p
>This make me believe Wouter believe booting into single user mode
7503 and booting into runlevel
1 is the same. I am not surprised he
7504 believe this, because it would make sense and is a quite sensible
7505 thing to believe. But because the boot in Debian is slightly broken,
7506 runlevel
1 do not work properly and it isn
't the same as single user
7507 mode. I
'll try to explain what is actually happing, but it is a bit
7508 hard to explain.
</p
>
7510 <p
>Single user mode is defined like this in /etc/inittab:
7511 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7512 executed in single user mode is sulogin. Single user mode is a boot
7513 state
"between
" the runlevels, and when booting into single user mode,
7514 only the scripts in /etc/rcS.d/ are executed before the init process
7515 enters the single user state. When switching to runlevel
1, the state
7516 is in fact not ending in runlevel
1, but it passes through runlevel
1
7517 and end up in the single user mode (see /etc/rc1.d/S03single, which
7518 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7519 1. It is confusing that the
'S
' (single user) init mode is not the
7520 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7523 <p
>This summary might make it clearer. When booting for the first
7524 time into single user mode, the following commands are executed:
7525 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7526 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7527 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7528 trying to continue after visiting single user mode. Not all services
7529 are started again as they should, causing the machine to end up in an
7530 unpredicatble state. This is why Debian admins recommend rebooting
7531 after visiting single user mode.
</p
>
7533 <p
>A similar problem with runlevel
1 is caused by the amount of
7534 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7535 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7536 stopped when passing through the scripts in /etc/rc1.d/, and not
7537 started again when switching away from runlevel
1 to the runlevels
7538 2-
5. I believe the problem is best fixed by moving all the scripts
7539 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7540 functioning single user mode during boot.
</p
>
7542 <p
>I have spent several years investigating the Debian boot system,
7543 and discovered this problem a few years ago. I suspect it originates
7544 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7549 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7550 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7551 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7552 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7553 <description><p
>In the Debian boot system, several packages include scripts that
7554 are started from /etc/rcS.d/. In fact, there is a bite more of them
7555 than make sense, and this causes a few problems. What kind of
7556 problems, you might ask. There are at least two problems. The first
7557 is that it is not possible to recover a machine after switching to
7558 runlevel
1. One need to actually reboot to get the machine back to
7559 the expected state. The other is that single user boot will sometimes
7560 run into problems because some of the subsystems are activated before
7561 the root login is presented, causing problems when trying to recover a
7562 machine from a problem in that subsystem. A minor additional point is
7563 that moving more scripts out of rcS.d/ and into the other rc#.d/
7564 directories will increase the amount of scripts that can run in
7565 parallel during boot, and thus decrease the boot time.
</p
>
7567 <p
>So, which scripts should start from rcS.d/. In short, only the
7568 scripts that _have_ to execute before the root login prompt is
7569 presented during a single user boot should go there. Everything else
7570 should go into the numeric runlevels. This means things like
7571 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7572 the numeric runlevels. Today in Debian, there are around
115 init.d
7573 scripts that are started from rcS.d/, and most of them should be moved
7574 out. Do your package have one of them? Please help us make single
7575 user and runlevel
1 better by moving it.
</p
>
7577 <p
>Scripts setting up the screen, keyboard, system partitions
7578 etc. should still be started from rcS.d/, but there is for example no
7579 need to have the network enabled before the single user login prompt
7580 is presented.
</p
>
7582 <p
>As always, things are not so easy to fix as they sound. To keep
7583 Debian systems working while scripts migrate and during upgrades, the
7584 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7585 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7586 and the next ones can only be moved when their dependencies have been
7587 moved first. This migration must be done sequentially while we ensure
7588 that the package system upgrade packages in the right order to keep
7589 the system state correct. This will require some coordination when it
7590 comes to network related packages, but most of the packages with
7591 scripts that should migrate do not have anything in rcS.d/ depending
7592 on them. Some packages have already been updated, like the sudo
7593 package, while others are still left to do. I wish I had time to work
7594 on this myself, but real live constrains make it unlikely that I will
7595 find time to push this forward.
</p
>
7600 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7601 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7602 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7603 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7604 <description><p
>While at Debconf11, I have several times during discussions
7605 mentioned the issues I believe should be improved in Debian for its
7606 desktop to be useful for more people. The use case for this is my
7607 parents, which are currently running Kubuntu which solve the
7610 <p
>I suspect these four missing features are not very hard to
7611 implement. After all, they are present in Ubuntu, so if we wanted to
7612 do this in Debian we would have a source.
</p
>
7616 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7617 are new packages available for upgrades, a icon in the KDE status bar
7618 indicate this, and clicking on it will activate the simple upgrade
7619 tool to handle it. I have no problem guiding both of my parents
7620 through the process over the phone. If a kernel reboot is required,
7621 this too is indicated by the status bars and the upgrade tool. Last
7622 time I checked, nothing with the same features was working in KDE in
7625 <li
><strong
>Simple handling of missing Firefox browser
7626 plugins.
</strong
> When the browser encounter a MIME type it do not
7627 currently have a handler for, it will ask the user if the system
7628 should search for a package that would add support for this MIME type,
7629 and if the user say yes, the APT sources will be searched for packages
7630 advertising the MIME type in their control file (visible in the
7631 Packages file in the APT archive). If one or more packages are found,
7632 it is a simple click of the mouse to add support for the missing mime
7633 type. If the package require the user to accept some non-free
7634 license, this is explained to the user. The entire process make it
7635 more clear to the user why something do not work in the browser, and
7636 make the chances higher for the user to blame the web page authors and
7637 not the browser for any missing features.
</li
>
7639 <li
><strong
>Simple handling of missing multimedia codec/format
7640 handlers.
</strong
> When the media players encounter a format or codec
7641 it is not supporting, a dialog pop up asking the user if the system
7642 should search for a package that would add support for it. This
7643 happen with things like MP3, Windows Media or H
.264. The selection
7644 and installation procedure is very similar to the Firefox browser
7645 plugin handling. This is as far as I know implemented using a
7646 gstreamer hook. The end result is that the user easily get access to
7647 the codecs that are present from the APT archives available, while
7648 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7650 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7651 displaying a text/plain file in my Debian browser, it will propose to
7652 start emacs to show it. If I remember correctly, when doing the same
7653 in Kunbutu it show the file as a text file in the browser. At least I
7654 know Opera will show text files within the browser. I much prefer the
7655 latter behaviour.
</li
>
7659 <p
>There are other nice features as well, like the simplified suite
7660 upgrader, but given that I am the one mostly doing the dist-upgrade,
7661 it do not matter much.
</p
>
7663 <p
>I really hope we could get these features in place for the next
7664 Debian release. It would require the coordinated effort of several
7665 maintainers, but would make the end user experience a lot better.
</p
>
7670 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7671 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7672 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7673 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7674 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7675 site is build on Debian/Squeeze, and this platform was chosen because
7676 I am most familiar with Debian (being a Debian Developer for around
10
7677 years) because it is the latest stable Debian release which should get
7678 security support for a few years.
</p
>
7680 <p
>The web service is written in Perl, and depend on some perl modules
7681 that are missing in Debian at the moment. It would be great if these
7682 modules were added to the Debian archive, allowing anyone to set up
7683 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7684 in their own country using only Debian packages. The list of modules
7685 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7686 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7687 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7688 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7689 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7690 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7691 easier in the future.
</p
>
7693 <p
>Thanks to the great tools in Debian, getting the missing modules
7694 installed on my server was a simple call to
'cpan2deb Module::Name
'
7695 and
'dpkg -i
' to install the resulting package. But this leave me
7696 with the responsibility of tracking security problems, which I really
7697 do not have time for.
</p
>
7702 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7703 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7704 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7705 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7706 <description><p
>Here is a small update for my English readers. Most of my blog
7707 posts have been in Norwegian the last few weeks, so here is a short
7708 update in English.
</p
>
7710 <p
>The kids still keep me too busy to get much free software work
7711 done, but I did manage to organise a project to get a Norwegian port
7712 of the British service
7713 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7714 and it has been running for a month now. The entire project has been
7715 organised by me and two others. Around Christmas we gathered sponsors
7716 to fund the development work. In January I drafted a contract with
7717 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7718 and in February the development took place. Most of it involved
7719 converting the source to use GPS coordinates instead of British
7720 easting/northing, and the resulting code should be a lot easier to get
7721 running in any country by now. The Norwegian
7722 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7723 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7724 source and the source for administrative borders in Norway, and
7725 support for this had to be added/fixed.
</p
>
7727 <p
>The Norwegian version went live March
3th, and we spent the weekend
7728 polishing the system before we announced it March
7th. The system is
7729 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7730 problem reports in a few weeks. Soon we hope to announce the Android
7731 and iPhone versions making it even easier to report problems with the
7732 public infrastructure.
</p
>
7734 <p
>Perhaps something to consider for those of you in countries without
7735 such service?
</p
>
7740 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7741 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7742 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7743 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7744 <description><p
>The last few days I have looked at ways to track open security
7745 issues here at my work with the University of Oslo. My idea is that
7746 it should be possible to use the information about security issues
7747 available on the Internet, and check our locally
7748 maintained/distributed software against this information. It should
7749 allow us to verify that no known security issues are forgotten. The
7750 CVE database listing vulnerabilities seem like a great central point,
7751 and by using the package lists from Debian mapped to CVEs provided by
7752 the testing security team, I believed it should be possible to figure
7753 out which security holes were present in our free software
7754 collection.
</p
>
7756 <p
>After reading up on the topic, it became obvious that the first
7757 building block is to be able to name software packages in a unique and
7758 consistent way across data sources. I considered several ways to do
7759 this, for example coming up with my own naming scheme like using URLs
7760 to project home pages or URLs to the Freshmeat entries, or using some
7761 existing naming scheme. And it seem like I am not the first one to
7762 come across this problem, as MITRE already proposed and implemented a
7763 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7764 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7765 software, hardware and other platform components. The CPE ids are
7766 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7767 Vulnerability Database
</a
>, allowing me to look up know security
7768 issues for any CPE name. With this in place, all I need to do is to
7769 locate the CPE id for the software packages we use at the university.
7770 This is fairly trivial (I google for
'cve cpe $package
' and check the
7771 NVD entry if a CVE for the package exist).
</p
>
7773 <p
>To give you an example. The GNU gzip source package have the CPE
7774 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7775 check out, one could look up
7776 <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
7777 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7778 The most recent one is
7779 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7780 and at the bottom of the NVD page for this vulnerability the complete
7781 list of affected versions is provided.
</p
>
7783 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7784 for offline processing of issues. Using this dump, I
've written a
7785 small script taking a list of CPEs as input and list all CVEs
7786 affecting the packages represented by these CPEs. One give it CPEs
7787 with version numbers as specified above and get a list of open
7788 security issues out.
</p
>
7790 <p
>Of course for this approach to be useful, the quality of the NVD
7791 information need to be high. For that to happen, I believe as many as
7792 possible need to use and contribute to the NVD database. I notice
7794 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7795 map from CVE to CPE
</a
>, indicating that they are using the CPE
7796 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7798 <p
>To get an idea about the quality for free software, I spent some
7799 time making it possible to compare the CVE database from Debian with
7800 the CVE database in NVD. The result look fairly good, but there are
7801 some inconsistencies in NVD (same software package having several
7802 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7803 Debian believe are affected by a CVE). Hope to find time to improve
7804 the quality of NVD, but that require being able to get in touch with
7805 someone maintaining it. So far my three emails with questions and
7806 corrections have not seen any reply, but I hope contact can be
7807 established soon.
</p
>
7809 <p
>An interesting application for CPEs is cross platform package
7810 mapping. It would be useful to know which packages in for example
7811 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7812 this would be trivial if all linux distributions provided CPE entries
7813 for their packages.
</p
>
7818 <title>Which module is loaded for a given PCI and USB device?
</title>
7819 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7820 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7821 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7822 <description><p
>In the
7823 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7824 package in Debian, there is a script to report useful information
7825 about the running hardware for use when people report missing
7826 information. One part of this script that I find very useful when
7827 debugging hardware problems, is the part mapping loaded kernel module
7828 to the PCI device it claims. It allow me to quickly see if the kernel
7829 module I expect is driving the hardware I am struggling with. To see
7830 the output, make sure discover-data is installed and run
7831 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7832 one of my machines like this:
</p
>
7836 10de:
03eb i2c_nforce2
7839 10de:
03f0 snd_hda_intel
7848 <p
>The code in question look like this, slightly modified for
7849 readability and to drop the output to file descriptor
3:
</p
>
7852 if [ -d /sys/bus/pci/devices/ ] ; then
7853 echo loaded pci modules:
7855 cd /sys/bus/pci/devices/
7856 for address in * ; do
7857 if [ -d
"$address/driver/module
" ] ; then
7858 module=`cd $address/driver/module ; pwd -P | xargs basename`
7859 if grep -q
"^$module
" /proc/modules ; then
7860 address=$(echo $address |sed s/
0000://)
7861 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7862 echo
"$id $module
"
7871 <p
>Similar code could be used to extract USB device module
7875 if [ -d /sys/bus/usb/devices/ ] ; then
7876 echo loaded usb modules:
7878 cd /sys/bus/usb/devices/
7879 for address in * ; do
7880 if [ -d
"$address/driver/module
" ] ; then
7881 module=`cd $address/driver/module ; pwd -P | xargs basename`
7882 if grep -q
"^$module
" /proc/modules ; then
7883 address=$(echo $address |sed s/
0000://)
7884 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7885 if [
"$id
" ] ; then
7886 echo
"$id $module
"
7896 <p
>This might perhaps be something to include in other tools as
7902 <title>How to test if a laptop is working with Linux
</title>
7903 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7904 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7905 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7906 <description><p
>The last few days I have spent at work here at the
<a
7907 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7908 batch of computers will work with Linux. Every year for the last few
7909 years the university have organised shared bid of a few thousand
7910 computers, and this year HP won the bid. Two different desktops and
7911 five different laptops are on the list this year. We in the UNIX
7912 group want to know which one of these computers work well with RHEL
7913 and Ubuntu, the two Linux distributions we currently handle at the
7914 university.
</p
>
7916 <p
>My test method is simple, and I share it here to get feedback and
7917 perhaps inspire others to test hardware as well. To test, I PXE
7918 install the OS version of choice, and log in as my normal user and run
7919 a few applications and plug in selected pieces of hardware. When
7920 something fail, I make a note about this in the test matrix and move
7921 on. If I have some spare time I try to report the bug to the OS
7922 vendor, but as I only have the machines for a short time, I rarely
7923 have the time to do this for all the problems I find.
</p
>
7925 <p
>Anyway, to get to the point of this post. Here is the simple tests
7926 I perform on a new model.
</p
>
7930 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7931 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7932 RHEL5 and Debian Edu/Squeeze.
</li
>
7934 <li
>Is X.org working? If the graphical login screen show up after
7935 installation, X.org is working.
</li
>
7937 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7938 package mesa-utils on Ubuntu) and writing down the frames per second
7939 reported by the program.
</li
>
7941 <li
>Is sound working? With Gnome and KDE, a sound is played when
7942 logging in, and if I can hear this the test is successful. If there
7943 are several audio exits on the machine, I try them all and check if
7944 the Gnome/KDE audio mixer can control where to send the sound. I
7945 normally test this by playing
7946 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7947 video
</a
> in Firefox/Iceweasel.
</li
>
7949 <li
>Is the USB subsystem working? I test this by plugging in a USB
7950 memory stick and see if Gnome/KDE notices this.
</li
>
7952 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7953 I have lying around, and see if Gnome/KDE notices this.
</li
>
7955 <li
>Is any built in camera working? Test using cheese, and see if a
7956 picture from the v4l device show up.
</li
>
7958 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7959 any bluetooth devices are discovered. In my office, I normally see a
7962 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7963 memory modules lying around, and stick them in and see if Gnome/KDE
7964 notice this.
</li
>
7966 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7967 special button work, and if the laptop continue to work after
7970 <li
>For laptops, is the extra buttons working, like audio level,
7971 adjusting background light, switching on/off external video output,
7972 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7973 laptop to laptop, so I just write down which are working and which are
7976 <li
>Some laptops have smart card readers, finger print readers,
7977 acceleration sensors etc. I rarely test these, as I do not know how
7978 to quickly test if they are working or not, so I only document their
7979 existence.
</li
>
7983 <p
>By now I suspect you are really curious what the test results are
7984 for the HP machines I am testing. I
'm not done yet, so I will report
7985 the test results later. For now I can report that HP
8100 Elite work
7986 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7987 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7988 can see, I have most machines left to test. One interesting
7989 observation is that Ubuntu Lucid has almost twice the frame rate than
7990 RHEL6 with glxgears. No idea why.
</p
>
7995 <title>Some thoughts on BitCoins
</title>
7996 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7997 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7998 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7999 <description><p
>As I continue to explore
8000 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
8001 what properties the system have, and how it will be affected by laws
8002 and regulations here in Norway. Here are some random notes.
</p
>
8004 <p
>One interesting thing to note is that since the transactions are
8005 verified using a peer to peer network, all details about a transaction
8006 is known to everyone. This means that if a BitCoin address has been
8007 published like I did with mine in my initial post about BitCoin, it is
8008 possible for everyone to see how many BitCoins have been transfered to
8009 that address. There is even a web service to look at the details for
8010 all transactions. There I can see that my address
8011 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
8012 have received
16.06 Bitcoin, the
8013 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
8014 address of Simon Phipps have received
181.97 BitCoin and the address
8015 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
8016 of EFF have received
2447.38 BitCoins so far. Thank you to each and
8017 every one of you that donated bitcoins to support my activity. The
8018 fact that anyone can see how much money was transfered to a given
8019 address make it more obvious why the BitCoin community recommend to
8020 generate and hand out a new address for each transaction. I
'm told
8021 there is no way to track which addresses belong to a given person or
8022 organisation without the person or organisation revealing it
8023 themselves, as Simon, EFF and I have done.
</p
>
8025 <p
>In Norway, and in most other countries, there are laws and
8026 regulations limiting how much money one can transfer across the border
8027 without declaring it. There are money laundering, tax and accounting
8028 laws and regulations I would expect to apply to the use of BitCoin.
8029 If the Skolelinux foundation
8030 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
8031 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
8032 normal bank transfers like EFF is doing, how should this be accounted?
8033 Given that it is impossible to know if money can cross the border or
8034 not, should everything or nothing be declared? What exchange rate
8035 should be used when calculating taxes? Would receivers have to pay
8036 income tax if the foundation were to pay Skolelinux contributors in
8037 BitCoin? I have no idea, but it would be interesting to know.
</p
>
8039 <p
>For a currency to be useful and successful, it must be trusted and
8040 accepted by a lot of users. It must be possible to get easy access to
8041 the currency (as a wage or using currency exchanges), and it must be
8042 easy to spend it. At the moment BitCoin seem fairly easy to get
8043 access to, but there are very few places to spend it. I am not really
8044 a regular user of any of the vendor types currently accepting BitCoin,
8045 so I wonder when my kind of shop would start accepting BitCoins. I
8046 would like to buy electronics, travels and subway tickets, not herbs
8047 and books. :) The currency is young, and this will improve over time
8048 if it become popular, but I suspect regular banks will start to lobby
8049 to get BitCoin declared illegal if it become popular. I
'm sure they
8050 will claim it is helping fund terrorism and money laundering (which
8051 probably would be true, as is any currency in existence), but I
8052 believe the problems should be solved elsewhere and not by blaming
8053 currencies.
</p
>
8055 <p
>The process of creating new BitCoins is called mining, and it is
8056 CPU intensive process that depend on a bit of luck as well (as one is
8057 competing against all the other miners currently spending CPU cycles
8058 to see which one get the next lump of cash). The
"winner
" get
50
8059 BitCoin when this happen. Yesterday I came across the obvious way to
8060 join forces to increase ones changes of getting at least some coins,
8061 by coordinating the work on mining BitCoins across several machines
8062 and people, and sharing the result if one is lucky and get the
50
8064 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8065 if this sounds interesting. I have not had time to try to set up a
8066 machine to participate there yet, but have seen that running on ones
8067 own for a few days have not yield any BitCoins througth mining
8070 <p
>Update
2010-
12-
15: Found an
<a
8071 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8072 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8073 it was interesting to read. The arguments presented seem to be
8074 equally valid for gold, which was used as a currency for many years.
</p
>
8079 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8080 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8081 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8082 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8083 <description><p
>With this weeks lawless
8084 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8085 attacks
</a
> on Wikileak and
8086 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8087 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8088 not be trusted to handle money transactions.
8090 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8091 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8092 mine mentioned earlier. I decided to follow Simon
's example, and get
8093 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8094 some help from my friend to get it all running, and he even handed me
8095 some bitcoins to get started. I even donated a few bitcoins to Simon
8096 for helping me remember BitCoin.
</p
>
8098 <p
>So, what is bitcoins, you probably wonder? It is a digital
8099 crypto-currency, decentralised and handled using peer-to-peer
8100 networks. It allows anonymous transactions and prohibits central
8101 control over the transactions, making it impossible for governments
8102 and companies alike to block donations and other transactions. The
8103 source is free software, and while the key dependency wxWidgets
2.9
8104 for the graphical user interface is missing in Debian, the command
8105 line client builds just fine. Hopefully Jonas
8106 <a href=
"http://bugs.debian.org/
578157">will get the package into
8107 Debian
</a
> soon.
</p
>
8109 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8110 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8111 bitcoins
</a
> when selling services and goods, and there are even
8112 currency
"stock
" markets where the exchange rate is decided. There
8113 are not many users so far, but the concept seems promising. If you
8114 want to get started and lack a friend with any bitcoins to spare,
8116 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8117 bitcoin at the time of writing). Use
8118 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8119 on the current exchange rates.
</p
>
8121 <p
>As an experiment, I have decided to set up bitcoind on one of my
8122 machines. If you want to support my activity, please send Bitcoin
8123 donations to the address
8124 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8129 <title>Why isn
't Debian Edu using VLC?
</title>
8130 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8132 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8133 <description><p
>In the latest issue of Linux Journal, the readers choices were
8134 presented, and the winner among the multimedia player were VLC.
8135 Personally, I like VLC, and it is my player of choice when I first try
8136 to play a video file or stream. Only if VLC fail will I drag out
8137 gmplayer to see if it can do better. The reason is mostly the failure
8138 model and trust. When VLC fail, it normally pop up a error message
8139 reporting the problem. When mplayer fail, it normally segfault or
8140 just hangs. The latter failure mode drain my trust in the program.
<p
>
8142 <p
>But even if VLC is my player of choice, we have choosen to use
8143 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8144 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8145 plugin to play web videos seamlessly, and the VLC browser plugin is
8146 not very good. For example, it lack in-line control buttons, so there
8147 is no way for the user to pause the video. Also, when I
8148 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8149 tested the browser plugins
</a
> available in Debian, the VLC plugin
8150 failed on several video pages where mplayer based plugins worked. If
8151 the browser plugin for VLC was as good as the gecko-mediaplayer
8152 package (which uses mplayer), we would switch.
</P
>
8154 <p
>While VLC is a good player, its user interface is slightly
8155 annoying. The most annoying feature is its inconsistent use of
8156 keyboard shortcuts. When the player is in full screen mode, its
8157 shortcuts are different from when it is playing the video in a window.
8158 For example, space only work as pause when in full screen mode. I
8159 wish it had consisten shortcuts and that space also would work when in
8160 window mode. Another nice shortcut in gmplayer is [enter] to restart
8161 the current video. It is very nice when playing short videos from the
8162 web and want to restart it when new people arrive to have a look at
8163 what is going on.
</p
>
8168 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8169 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8170 <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>
8171 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8172 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8173 upgrade testing of the
8174 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8175 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8176 This seem like a very good idea, so I adjusted by test scripts and
8177 can now present the updated result from today:
</p
>
8179 <p
>This is for Gnome:
</p
>
8181 <p
>Installed using apt-get, missing with aptitude
</p
>
8183 <blockquote
><p
>
8188 browser-plugin-gnash
8195 freedesktop-sound-theme
8197 gconf-defaults-service
8212 gnome-desktop-environment
8216 gnome-session-canberra
8221 gstreamer0.10-fluendo-mp3
8227 libapache2-mod-dnssd
8230 libaprutil1-dbd-sqlite3
8233 libboost-date-time1.42
.0
8234 libboost-python1.42
.0
8235 libboost-thread1.42
.0
8237 libchamplain-gtk-
0.4-
0
8239 libclutter-gtk-
0.10-
0
8246 libfreerdp-plugins-standard
8261 libgnomepanel2.24-cil
8266 libgtksourceview2.0-common
8267 libmono-addins-gui0.2-cil
8268 libmono-addins0.2-cil
8269 libmono-cairo2.0-cil
8270 libmono-corlib2.0-cil
8271 libmono-i18n-west2.0-cil
8272 libmono-posix2.0-cil
8273 libmono-security2.0-cil
8274 libmono-sharpzip2.84-cil
8275 libmono-system2.0-cil
8278 libndesk-dbus-glib1.0-cil
8279 libndesk-dbus1.0-cil
8289 libtelepathy-farsight0
8298 nautilus-sendto-empathy
8302 python-aptdaemon-gtk
8304 python-beautifulsoup
8319 python-gtksourceview2
8330 python-pkg-resources
8337 python-twisted-conch
8343 python-zope.interface
8348 rhythmbox-plugin-cdrecorder
8355 system-config-printer-udev
8357 telepathy-mission-control-
5
8368 </p
></blockquote
>
8370 <p
>Installed using apt-get, removed with aptitude
</p
>
8372 <blockquote
><p
>
8378 fast-user-switch-applet
8397 libgtksourceview2.0-
0
8399 libsdl1.2debian-alsa
8405 system-config-printer
8410 </p
></blockquote
>
8412 <p
>Installed using aptitude, missing with apt-get
</p
>
8414 <blockquote
><p
>
8415 gstreamer0.10-gnomevfs
8416 </p
></blockquote
>
8418 <p
>Installed using aptitude, removed with apt-get
</p
>
8420 <blockquote
><p
>
8422 </p
></blockquote
>
8424 <p
>This is for KDE:
</p
>
8426 <p
>Installed using apt-get, missing with aptitude
</p
>
8428 <blockquote
><p
>
8430 </p
></blockquote
>
8432 <p
>Installed using apt-get, removed with aptitude
</p
>
8434 <blockquote
><p
>
8437 </p
></blockquote
>
8439 <p
>Installed using aptitude, missing with apt-get
</p
>
8441 <blockquote
><p
>
8455 kdeartwork-emoticons
8457 kdeartwork-theme-icon
8461 kdebase-workspace-bin
8462 kdebase-workspace-data
8476 kscreensaver-xsavers
8491 plasma-dataengines-workspace
8493 plasma-desktopthemes-artwork
8494 plasma-runners-addons
8495 plasma-scriptengine-googlegadgets
8496 plasma-scriptengine-python
8497 plasma-scriptengine-qedje
8498 plasma-scriptengine-ruby
8499 plasma-scriptengine-webkit
8500 plasma-scriptengines
8501 plasma-wallpapers-addons
8502 plasma-widget-folderview
8503 plasma-widget-networkmanagement
8507 xscreensaver-data-extra
8509 xscreensaver-gl-extra
8510 xscreensaver-screensaver-bsod
8511 </p
></blockquote
>
8513 <p
>Installed using aptitude, removed with apt-get
</p
>
8515 <blockquote
><p
>
8517 google-gadgets-common
8535 libggadget-qt-
1.0-
0b
8540 libkonqsidebarplugin4a
8549 libplasma-geolocation-interface4
8551 libplasmagenericshell4
8565 libsmokeknewstuff2-
3
8566 libsmokeknewstuff3-
3
8568 libsmokektexteditor3
8576 libsmokeqtnetwork4-
3
8582 libsmokeqtuitools4-
3
8594 plasma-dataengines-addons
8595 plasma-scriptengine-superkaramba
8596 plasma-widget-lancelot
8597 plasma-widgets-addons
8598 plasma-widgets-workspace
8602 update-notifier-common
8603 </p
></blockquote
>
8605 <p
>Running apt-get autoremove made the results using apt-get and
8606 aptitude a bit more similar, but there are still quite a lott of
8607 differences. I have no idea what packages should be installed after
8608 the upgrade, but hope those that do can have a look.
</p
>
8613 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8614 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8616 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8617 <description><p
>Most of the computers in use by the
8618 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8619 are virtual machines. And they have been Xen machines running on a
8620 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8621 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8622 bit harder that it could have been, because we set up the Xen virtual
8623 machines to get the virtual partitions from LVM, which as far as I
8624 know is not supported by KVM. So to migrate, we had to convert
8625 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8628 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8629 nice recipe
</a
> to do this, and wrote the following script to do the
8630 migration. It uses qemu-img from the qemu package to make the disk
8631 image, parted to partition it, losetup and kpartx to present the disk
8632 image partions as devices, and dd to copy the data. I NFS mounted the
8633 new servers storage area on the old server to do the migration.
</p
>
8639 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8644 if [ -z
"$
1" ] ; then
8645 echo
"Usage: $
0 &lt;hostname
&gt;
"
8651 if [ ! -e /dev/vg_data/$host-disk ] ; then
8652 echo
"error: unable to find LVM volume for $host
"
8656 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8657 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8658 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8659 totalsize=$(( ( $disksize + $swapsize ) ))
8662 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8663 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8665 parted $img mklabel msdos
8666 parted $img mkpart primary linux-swap
0 $disksize
8667 parted $img mkpart primary ext2 $disksize $totalsize
8668 parted $img set
1 boot on
8671 losetup /dev/loop0 $img
8672 kpartx -a /dev/loop0
8674 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8675 fsck.ext3 -f /dev/mapper/loop0p1 || true
8676 mkswap /dev/mapper/loop0p2
8678 kpartx -d /dev/loop0
8679 losetup -d /dev/loop0
8682 <p
>The script is perhaps so simple that it is not copyrightable, but
8683 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8685 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8686 the new disk image attached, installed grub-pc and linux-image-
686 and
8687 set up grub to boot from the disk image. After this, the KVM machines
8688 seem to work just fine.
</p
>
8693 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8694 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8695 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8696 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8697 <description><p
>I
'm still running upgrade testing of the
8698 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8699 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8700 status. Here is a short update based on a test I ran
20101118.
</p
>
8702 <p
>I still do not know what a correct migration should look like, so I
8703 report any differences between apt and aptitude and hope someone else
8704 can see if anything should be changed.
</p
>
8706 <p
>This is for Gnome:
</p
>
8708 <p
>Installed using apt-get, missing with aptitude
</p
>
8710 <blockquote
><p
>
8711 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8712 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8713 dmz-cursor-theme empathy empathy-common finger
8714 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8715 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8716 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8717 gnome-cards-data gnome-codec-install gnome-core
8718 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8719 gnome-search-tool gnome-session-canberra gnome-spell
8720 gnome-system-log gnome-themes-extras gnome-themes-more
8721 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8722 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8723 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8724 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8725 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8726 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8727 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8728 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8729 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8730 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8731 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8732 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8733 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8734 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8735 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8736 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8737 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8738 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8739 libmono-security2.0-cil libmono-sharpzip2.84-cil
8740 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8741 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8742 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8743 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8744 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8745 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8746 libxalan2-java libxerces2-java media-player-info mesa-utils
8747 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8748 nautilus-sendto-empathy openoffice.org-writer2latex
8749 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8750 python-aptdaemon python-aptdaemon-gtk python-axiom
8751 python-beautifulsoup python-bugbuddy python-clientform
8752 python-coherence python-configobj python-crypto python-cupshelpers
8753 python-cupsutils python-eggtrayicon python-elementtree
8754 python-epsilon python-evolution python-feedparser python-gdata
8755 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8756 python-gtksourceview2 python-httplib2 python-louie python-mako
8757 python-markupsafe python-mechanize python-nevow python-notify
8758 python-opengl python-openssl python-pam python-pkg-resources
8759 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8760 python-tagpy python-twisted-bin python-twisted-conch
8761 python-twisted-core python-twisted-web python-utidylib python-webkit
8762 python-xdg python-zope.interface remmina remmina-plugin-data
8763 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8764 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8765 software-center svgalibg1 system-config-printer-udev
8766 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8767 totem totem-coherence totem-mozilla totem-plugins
8768 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8770 </p
></blockquote
>
8772 Installed using apt-get, removed with aptitude
8774 <blockquote
><p
>
8775 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8776 epiphany-extensions epiphany-gecko evolution-exchange
8777 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8778 gedit-common gnome-app-install gnome-games gnome-games-data
8779 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8780 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8781 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8782 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8783 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8784 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8785 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8786 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8787 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8788 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8789 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8790 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8791 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8792 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8793 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8794 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8795 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8796 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8797 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8798 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8799 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8800 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8801 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8802 sound-juicer swfdec-gnome system-config-printer totem-common
8803 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8804 </p
></blockquote
>
8806 <p
>Installed using aptitude, missing with apt-get
</p
>
8808 <blockquote
><p
>
8809 gstreamer0.10-gnomevfs
8810 </p
></blockquote
>
8812 <p
>Installed using aptitude, removed with apt-get
</p
>
8814 <blockquote
><p
>
8816 </p
></blockquote
>
8818 <p
>This is for KDE:
</p
>
8820 <p
>Installed using apt-get, missing with aptitude
</p
>
8822 <blockquote
><p
>
8823 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8824 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8825 ghostscript-x git gnome-audio gnugo granatier gs-common
8826 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8827 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8828 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8829 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8830 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8831 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8832 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8833 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8834 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8835 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8836 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8837 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8838 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8839 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8840 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8841 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8842 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8843 libkrossui4 libmailtools-perl libmime-tools-perl
8844 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8845 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8846 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8847 lirc luatex marble networkstatus noatun-plugins
8848 openoffice.org-writer2latex palapeli palapeli-data parley
8849 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8850 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8851 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8853 </p
></blockquote
>
8855 <p
>Installed using apt-get, removed with aptitude
</p
>
8857 <blockquote
><p
>
8858 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8859 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8860 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8861 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8862 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8863 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8864 kitchensync kiten kjumpingcube klatin klettres klickety klines
8865 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8866 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8867 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8868 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8869 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8870 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8871 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8872 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8873 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8874 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8875 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8876 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8877 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8878 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8879 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8880 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8881 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8882 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8883 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8884 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8885 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8886 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8887 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8888 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8889 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8890 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8891 </p
></blockquote
>
8893 <p
>Installed using aptitude, missing with apt-get
</p
>
8895 <blockquote
><p
>
8896 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8897 kdeartwork kdebase kdebase-apps kdebase-workspace
8898 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8899 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8900 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8901 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8902 xscreensaver-screensaver-bsod
8903 </p
></blockquote
>
8905 <p
>Installed using aptitude, removed with apt-get
</p
>
8907 <blockquote
><p
>
8908 kdebase-bin konq-plugins konqueror
8909 </p
></blockquote
>
8914 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8915 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8916 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8917 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8918 <description><p
>Answering
8919 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8920 call from the Gnash project
</a
> for
8921 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8922 current source, I have set up a virtual KVM machine on the Debian
8923 Edu/Skolelinux virtualization host to test the git source on
8924 Debian/Squeeze. I hope this can help the developers in getting new
8925 releases out more often.
</p
>
8927 <p
>As the developers want less main-stream build platforms tested to,
8928 I have considered setting up a
<a
8929 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8930 machine as well. I have also considered using the kfreebsd
8931 architecture in Debian as a file server in NUUG to get access to the
5
8932 TB zfs volume we currently use to store DV video. Because of this, I
8933 finally got around to do a test installation of Debian/Squeeze with
8934 kfreebsd. Installation went fairly smooth, thought I noticed some
8935 visual glitches in the cdebconf dialogs (black cursor left on the
8936 screen at random locations). Have not gotten very far with the
8937 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8938 fatal problem. Have to spend some more time on it to see if it is
8939 useful as a file server for NUUG. Will try to find time to set up a
8940 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8945 <title>Debian in
3D
</title>
8946 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8947 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8948 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8949 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8951 <p
>3D printing is just great. I just came across this Debian logo in
8953 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8954 thingiverse blog
</a
>.
</p
>
8959 <title>Software updates
2010-
10-
24</title>
8960 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8961 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8962 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8963 <description><p
>Some updates.
</p
>
8965 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8966 raise money for the project is going well. The lower limit of
10
8967 signers was reached in
24 hours, and so far
13 people have signed it.
8968 More signers and more funding is most welcome, and I am really curious
8969 how far we can get before the time limit of December
24 is reached.
8972 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8973 about what appear to be a great code coverage tool capable of
8974 generating code coverage stats without any changes to the source code.
8976 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8977 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8978 It is missing in Debian, but the git source built just fine in Squeeze
8979 after I installed libelf-dev, libdwarf-dev, pkg-config and
8980 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8981 solvable. I hope kcov make it into Debian soon.
</p
>
8983 <p
>Finally found time to wrap up the release notes for
<a
8984 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8985 new alpha release of Debian Edu
</a
>, and just published the second
8986 alpha test release of the Squeeze based Debian Edu /
8987 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8988 release. Give it a try if you need a complete linux solution for your
8989 school, including central infrastructure server, workstations, thin
8990 client servers and diskless workstations. A nice touch added
8991 yesterday is RDP support on the thin client servers, for windows
8992 clients to get a Linux desktop on request.
</p
>
8997 <title>Some notes on Flash in Debian and Debian Edu
</title>
8998 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8999 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
9000 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
9001 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
9002 popularity-contest numbers
</a
>, the adobe-flashplugin package the
9003 second most popular used package that is missing in Debian. The sixth
9004 most popular is flashplayer-mozilla. This is a clear indication that
9005 working flash is important for Debian users. Around
10 percent of the
9006 users submitting data to popcon.debian.org have this package
9007 installed.
</p
>
9009 <p
>In the report written by Lars Risan in August
2008
9010 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
9011 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9012 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
9013 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
9014 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
9015 web sites require Flash to work, and lacking working Flash support in
9016 the web browser and the problems with installing it was perceived as a
9017 good reason to stay with Windows.
</p
>
9019 <p
>I once saw a funny and sad comment in a web forum, where Linux was
9020 said to be the retarded cousin that did not really understand
9021 everything you told him but could work fairly well. This was a
9022 comment regarding the problems Linux have with proprietary formats and
9023 non-standard web pages, and is sad because it exposes a fairly common
9024 understanding of whose fault it is if web pages that only work in for
9025 example Internet Explorer
6 fail to work on Firefox, and funny because
9026 it explain very well how annoying it is for users when Linux
9027 distributions do not work with the documents they receive or the web
9028 pages they want to visit.
</p
>
9030 <p
>This is part of the reason why I believe it is important for Debian
9031 and Debian Edu to have a well working Flash implementation in the
9032 distribution, to get at least popular sites as Youtube and Google
9033 Video to working out of the box. For Squeeze, Debian have the chance
9034 to include the latest version of Gnash that will make this happen, as
9035 the new release
0.8.8 was published a few weeks ago and is resting in
9036 unstable. The new version work with more sites that version
0.8.7.
9037 The Gnash maintainers have asked for a freeze exception, but the
9038 release team have not had time to reply to it yet. I hope they agree
9039 with me that Flash is important for the Debian desktop users, and thus
9040 accept the new package into Squeeze.
</p
>
9045 <title>Circular package dependencies harms apt recovery
</title>
9046 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9047 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9048 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9049 <description><p
>I discovered this while doing
9050 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9051 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9052 in Debian still got circular dependencies, and it is often claimed
9053 that apt and aptitude should be able to handle this just fine, but
9054 some times these dependency loops causes apt to fail.
</p
>
9056 <p
>An example is from todays
9057 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9058 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9059 causes perl-modules to fail to upgrade. The cause is simple. If a
9060 package fail to unpack, then only part of packages with the circular
9061 dependency might end up being unpacked when unpacking aborts, and the
9062 ones already unpacked will fail to configure in the recovery phase
9063 because its dependencies are unavailable.
</p
>
9065 <p
>In this log, the problem manifest itself with this error:
</p
>
9067 <blockquote
><pre
>
9068 dpkg: dependency problems prevent configuration of perl-modules:
9069 perl-modules depends on perl (
>=
5.10.1-
1); however:
9070 Version of perl on system is
5.10.0-
19lenny
2.
9071 dpkg: error processing perl-modules (--configure):
9072 dependency problems - leaving unconfigured
9073 </pre
></blockquote
>
9075 <p
>The perl/perl-modules circular dependency is already
9076 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9077 hopefully be solved as soon as possible, but it is not the only one,
9078 and each one of these loops in the dependency tree can cause similar
9079 failures. Of course, they only occur when there are bugs in other
9080 packages causing the unpacking to fail, but it is rather nasty when
9081 the failure of one package causes the problem to become worse because
9082 of dependency loops.
</p
>
9085 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9086 tireless effort by Bill Allombert
</a
>, the number of circular
9088 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9089 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9091 <p
>Todays testing also exposed a bug in
9092 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9093 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9094 apt-get and aptitude, the latter possibly caused by some circular
9095 dependency. Reported both to BTS to try to get someone to look at
9101 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9102 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9104 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9105 <description><p
>This is a
9106 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9108 <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
9110 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9111 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9113 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9114 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9115 and dhcp3-server-ldap in Debian use the LDAP server. The two
9116 implementations are quite different in how they use LDAP.
</p
>
9118 To get this information, I started slapd with debugging enabled and
9119 dumped the debug output to a file to get the LDAP searches performed
9120 on a Debian Edu main-server. Here is a summary.
9122 <p
><strong
>powerdns
</strong
></p
>
9124 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9125 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9128 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9129 One
"strict
" mode where the forward and reverse DNS lookups are done
9130 using the same LDAP objects, and a
"tree
" mode where the forward and
9131 reverse entries are in two different subtrees in LDAP with a structure
9132 based on the DNS names, as in tjener.intern and
9133 2.2.0.10.in-addr.arpa.
</p
>
9135 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9136 base, and uses a
"base
" scoped search for the DNS name by adding
9137 "dc=tjener,dc=intern,
" to the base with a filter for
9138 "(associateddomain=tjener.intern)
" for the forward entry and
9139 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9140 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9141 forward entries, it is looking for attributes named dnsttl, arecord,
9142 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9143 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9144 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9145 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9146 spfrecord and modifytimestamp. For reverse entries it is looking for
9147 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9148 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9149 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9150 ldapsearch commands could look like this:
</p
>
9152 <blockquote
><pre
>
9153 ldapsearch -h ldap \
9154 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9155 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9156 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9157 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9158 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9159 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9161 ldapsearch -h ldap \
9162 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9163 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9164 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9165 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9166 srvrecord naptrrecord modifytimestamp
9167 </pre
></blockquote
>
9169 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9170 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9171 example LDAP objects used there. In addition to these objects, the
9172 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9173 also exist.
</p
>
9175 <blockquote
><pre
>
9176 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9178 objectclass: dnsdomain
9179 objectclass: domainrelatedobject
9182 associateddomain: tjener.intern
9184 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9186 objectclass: dnsdomain2
9187 objectclass: domainrelatedobject
9189 ptrrecord: tjener.intern
9190 associateddomain:
2.2.0.10.in-addr.arpa
9191 </pre
></blockquote
>
9193 <p
>In strict mode, the server behaves differently. When looking for
9194 forward DNS entries, it is doing a
"subtree
" scoped search with the
9195 same base as in the tree mode for a object with filter
9196 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9197 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9198 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9199 naptrrecord and modifytimestamp. For reverse entires it also do a
9200 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9201 and the requested attributes are associateddomain, dnsttl and
9202 modifytimestamp. In short, in strict mode the objects with ptrrecord
9203 go away, and the arecord attribute in the forward object is used
9206 <p
>The forward and reverse searches can be simulated using ldapsearch
9207 like this:
</p
>
9209 <blockquote
><pre
>
9210 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9211 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9212 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9213 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9214 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9215 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9217 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9218 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9219 </pre
></blockquote
>
9221 <p
>In addition to the forward and reverse searches , there is also a
9222 search for SOA records, which behave similar to the forward and
9223 reverse lookups.
</p
>
9225 <p
>A thing to note with the PowerDNS behaviour is that it do not
9226 specify any objectclass names, and instead look for the attributes it
9227 need to generate a DNS reply. This make it able to work with any
9228 objectclass that provide the needed attributes.
</p
>
9230 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9231 dnsdomain2 schemas. The latter is used for reverse entries like
9232 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9234 <p
>In Debian Edu, we have created DNS objects using the object classes
9235 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9236 attributes) and domainrelatedobject (for associatedDomain). The use
9237 of structural object classes make it impossible to combine these
9238 classes with the object classes used by DHCP.
</p
>
9240 <p
>There are other schemas that could be used too, for example the
9241 dnszone structural object class used by Gosa and bind-sdb for the DNS
9242 attributes combined with the domainrelatedobject object class, but in
9243 this case some unused attributes would have to be included as well
9244 (zonename and relativedomainname).
</p
>
9246 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9247 mode and not use any of the existing objectclasses (dnsdomain,
9248 dnsdomain2 and dnszone) when one want to combine the DNS information
9249 with DHCP information, and instead create a auxiliary object class
9250 defined something like this (using the attributes defined for
9251 dnsdomain and dnsdomain2 or dnszone):
</p
>
9253 <blockquote
><pre
>
9254 objectclass ( some-oid NAME
'dnsDomainAux
'
9257 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9258 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9259 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9260 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9261 A6Record $ DNAMERecord
9263 </pre
></blockquote
>
9265 <p
>This will allow any object to become a DNS entry when combined with
9266 the domainrelatedobject object class, and allow any entity to include
9267 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9268 developers asking for their view on this schema and if they are
9269 interested in providing such schema with PowerDNS, and I hope my
9270 message will be accepted into their mailing list soon.
</p
>
9272 <p
><strong
>ISC dhcp
</strong
></p
>
9274 <p
>The DHCP server searches for specific objectclass and requests all
9275 the object attributes, and then uses the attributes it want. This
9276 make it harder to figure out exactly what attributes are used, but
9277 thanks to the working example in Debian Edu I can at least get an idea
9278 what is needed without having to read the source code.
</p
>
9280 <p
>In the DHCP server configuration, the LDAP base to use and the
9281 search filter to use to locate the correct dhcpServer entity is
9282 stored. These are the relevant entries from
9283 /etc/dhcp3/dhcpd.conf:
</p
>
9285 <blockquote
><pre
>
9286 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9287 ldap-dhcp-server-cn
"dhcp
";
9288 </pre
></blockquote
>
9290 <p
>The DHCP server uses this information to nest all the DHCP
9291 configuration it need. The cn
"dhcp
" is located using the given LDAP
9292 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9293 search result is this entry:
</p
>
9295 <blockquote
><pre
>
9296 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9299 objectClass: dhcpServer
9300 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9301 </pre
></blockquote
>
9303 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9304 subtree with DHCP configuration. The DHCP configuration subtree base
9305 is located using a base scope search with base
"cn=DHCP
9306 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9307 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9308 The search result is this entry:
</p
>
9310 <blockquote
><pre
>
9311 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9314 objectClass: dhcpService
9315 objectClass: dhcpOptions
9316 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9317 dhcpStatements: ddns-update-style none
9318 dhcpStatements: authoritative
9319 dhcpOption: smtp-server code
69 = array of ip-address
9320 dhcpOption: www-server code
72 = array of ip-address
9321 dhcpOption: wpad-url code
252 = text
9322 </pre
></blockquote
>
9324 <p
>Next, the entire subtree is processed, one level at the time. When
9325 all the DHCP configuration is loaded, it is ready to receive requests.
9326 The subtree in Debian Edu contain objects with object classes
9327 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9328 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9329 and information about netmasks, dynamic range etc. Leaving out the
9330 details here because it is not relevant for the focus of my
9331 investigation, which is to see if it is possible to merge dns and dhcp
9332 related computer objects.
</p
>
9334 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9335 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9336 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9337 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9338 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9341 <blockquote
><pre
>
9342 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9345 objectClass: dhcpHost
9346 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9347 dhcpStatements: fixed-address hostname
9348 </pre
></blockquote
>
9350 <p
>There is less flexiblity in the way LDAP searches are done here.
9351 The object classes need to have fixed names, and the configuration
9352 need to be stored in a fairly specific LDAP structure. On the
9353 positive side, the invidiual dhcpHost entires can be anywhere without
9354 the DN pointed to by the dhcpServer entries. The latter should make
9355 it possible to group all host entries in a subtree next to the
9356 configuration entries, and this subtree can also be shared with the
9357 DNS server if the schema proposed above is combined with the dhcpHost
9358 structural object class.
9360 <p
><strong
>Conclusion
</strong
></p
>
9362 <p
>The PowerDNS implementation seem to be very flexible when it come
9363 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9364 come to the the LDAP structure, the
"strict
" mode is very flexible,
9365 allowing DNS objects to be stored anywhere under the base cn specified
9366 in the configuration.
</p
>
9368 <p
>The DHCP implementation on the other hand is very inflexible, both
9369 regarding which LDAP schemas to use and which LDAP structure to use.
9370 I guess one could implement ones own schema, as long as the
9371 objectclasses and attributes have the names used, but this do not
9372 really help when the DHCP subtree need to have a fairly fixed
9373 structure.
</p
>
9375 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9376 this might work for Debian Edu:
</p
>
9378 <blockquote
><pre
>
9380 cn=machine-info (dhcpService) - dhcpServiceDN points here
9381 cn=dhcp (dhcpServer)
9382 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9383 cn=
10.0.2.0 (dhcpSubnet)
9384 cn=group1 (dhcpGroup/dhcpOptions)
9385 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9386 cn=
192.168.0.0 (dhcpSubnet)
9387 cn=group1 (dhcpGroup/dhcpOptions)
9388 ou=machines - PowerDNS base points here
9389 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9390 </pre
></blockquote
>
9392 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9393 entries to be in the dhcpGroup subtrees, the entries can be stored
9394 there instead of a common machines subtree, and the PowerDNS base
9395 would have to be moved one level up to the machine-info subtree.
</p
>
9397 <p
>The combined object under the machines subtree would look something
9398 like this:
</p
>
9400 <blockquote
><pre
>
9401 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9404 objectClass: dhcpHost
9405 objectclass: domainrelatedobject
9406 objectclass: dnsDomainAux
9407 associateddomain: hostname.intern
9408 arecord:
10.11.12.13
9409 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9410 dhcpStatements: fixed-address hostname.intern
9411 </pre
></blockquote
>
9413 </p
>One could even add the LTSP configuration associated with a given
9414 machine, as long as the required attributes are available in a
9415 auxiliary object class.
</p
>
9420 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9421 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9422 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9423 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9424 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9425 DHCP services in Debian Edu to use the same LDAP objects for a given
9426 computer, to avoid the possibility of having a inconsistent state for
9427 a computer in LDAP (as in DHCP but no DNS entry or the other way
9428 around) and make it easier to add computers to LDAP.
</p
>
9430 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9431 information finally found a solution that seem to work.
</p
>
9433 <p
>The old setup required three LDAP objects for a given computer.
9434 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9435 we switch powerdns to use its strict LDAP method (ldap-method=strict
9436 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9437 merged into one while making it impossible to transfer the reverse map
9438 to a slave DNS server.
</p
>
9440 <p
>If we also replace the object class used to get the DNS related
9441 attributes to one allowing these attributes to be combined with the
9442 dhcphost object class, we can merge the DNS and DHCP entries into one.
9443 I
've written such object class in the dnsdomainaux.schema file (need
9444 proper OIDs, but that is a minor issue), and tested the setup. It
9445 seem to work.
</p
>
9447 <p
>With this test setup in place, we can get away with one LDAP object
9448 for both DNS and DHCP, and even the LTSP configuration I suggested in
9449 an earlier email. The combined LDAP object will look something like
9452 <blockquote
><pre
>
9453 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9455 objectClass: dhcphost
9456 objectclass: domainrelatedobject
9457 objectclass: dnsdomainaux
9458 associateddomain: hostname.intern
9459 arecord:
10.11.12.13
9460 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9461 dhcpstatements: fixed-address hostname
9463 </pre
></blockquote
>
9465 <p
>The DNS server uses the associateddomain and arecord entries, while
9466 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9467 before asking DNS to resolve the fixed-adddress. LTSP will use
9468 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9470 <p
>I am not yet sure if I can get the DHCP server to look for its
9471 dhcphost in a different location, to allow us to put the objects
9472 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9473 that. If I can
't figure out a way to do that, we can still get rid of
9474 the hosts subtree and move all its content into the DHCP Config tree
9475 (which probably should be renamed to be more related to the new
9476 content. I suspect cn=dnsdhcp,ou=services or something like that
9477 might be a good place to put it.
</p
>
9479 <p
>If you want to help out with implementing this for Debian Edu,
9480 please contact us on debian-edu@lists.debian.org.
</p
>
9485 <title>Idea for storing LTSP configuration in LDAP
</title>
9486 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9487 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9488 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9489 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9490 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9491 clients, and that this can be used to fetch configuration from LDAP if
9492 Debian Edu choose to store configuration there.
</p
>
9494 <p
>Armed with this information, I got inspired and wrote a test module
9495 to get configuration from LDAP. The idea is to look up the MAC
9496 address of the client in LDAP, and look for attributes on the form
9497 ltspconfigsetting=value, and use this to export SETTING=value to the
9498 LTSP clients.
</p
>
9500 <p
>The goal is to be able to store the LTSP configuration attributes
9501 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9502 allowing us to store all information about a computer in one place.
</p
>
9504 <p
>This is a untested draft implementation, and I welcome feedback on
9505 this approach. A real LDAP schema for the ltspClientAux objectclass
9506 need to be written. Comments, suggestions, etc?
</p
>
9508 <blockquote
><pre
>
9509 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9511 # Fetch LTSP client settings from LDAP based on MAC address
9513 # Uses ethernet address as stored in the dhcpHost objectclass using
9514 # the dhcpHWAddress attribute or ethernet address stored in the
9515 # ieee802Device objectclass with the macAddress attribute.
9517 # This module is written to be schema agnostic, and only depend on the
9518 # existence of attribute names.
9520 # The LTSP configuration variables are saved directly using a
9521 # ltspConfig prefix and uppercasing the rest of the attribute name.
9522 # To set the SERVER variable, set the ltspConfigServer attribute.
9524 # Some LDAP schema should be created with all the relevant
9525 # configuration settings. Something like this should work:
9527 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9530 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9532 LDAPSERVER=$(debian-edu-ldapserver)
9533 if [
"$LDAPSERVER
" ] ; then
9534 LDAPBASE=$(debian-edu-ldapserver -b)
9535 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9536 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9537 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9538 grep
'^ltspConfig
' | while read attr value ; do
9539 # Remove prefix and convert to upper case
9540 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9541 # bass value on to clients
9542 eval
"$attr=$value; export $attr
"
9546 </pre
></blockquote
>
9548 <p
>I
'm not sure this shell construction will work, because I suspect
9549 the while block might end up in a subshell causing the variables set
9550 there to not show up in ltsp-config, but if that is the case I am sure
9551 the code can be restructured to make sure the variables are passed on.
9552 I expect that can be solved with some testing. :)
</p
>
9554 <p
>If you want to help out with implementing this for Debian Edu,
9555 please contact us on debian-edu@lists.debian.org.
</p
>
9557 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9558 configuration in LDAP that was created around year
2000 by
9559 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9560 Xperience, Inc.,
2000</a
>. I found its
9561 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9562 personal home page over at redhat.com.
</p
>
9567 <title>jXplorer, a very nice LDAP GUI
</title>
9568 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9569 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9570 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9571 <description><p
>Since
9572 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9573 last post
</a
> about available LDAP tools in Debian, I was told about a
9574 LDAP GUI that is even better than luma. The java application
9575 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9576 moving LDAP objects and subtrees using drag-and-drop, and can
9577 authenticate using Kerberos. I have only tested the Kerberos
9578 authentication, but do not have a LDAP setup allowing me to rewrite
9579 LDAP with my test user yet. It is
9580 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9581 Debian
</a
> testing and unstable at the moment. The only problem I
9582 have with it is how it handle errors. If something go wrong, its
9583 non-intuitive behaviour require me to go through some query work list
9584 and remove the failing query. Nothing big, but very annoying.
</p
>
9589 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9590 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9591 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9592 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9593 <description><p
>Here is a short update on my
<a
9594 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9595 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9596 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9597 not reporting the status for KDE, because the upgrade crashes when
9598 aptitude try because of missing conflicts
9599 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9600 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9602 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9603 complete list of the installed packages. Based on this I see these
9604 differences when I did a test run today. As usual, I do not really
9605 know what the correct set of packages would be, but thought it best to
9606 publish the difference.
</p
>
9608 <p
>Installed using apt-get, missing with aptitude
</p
>
9610 <blockquote
><p
>
9611 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9612 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9613 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9614 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9615 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9616 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9617 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9618 python-gtkmozembed svgalibg1 xserver-xephyr zip
9619 </p
></blockquote
>
9621 <p
>Installed using apt-get, removed with aptitude
</p
>
9623 <blockquote
><p
>
9624 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9625 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9626 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9627 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9628 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9629 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9630 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9631 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9632 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9633 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9634 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9635 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9636 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9637 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9638 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9639 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9640 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9641 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9642 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9643 mysql-common swfdec-gnome totem-gstreamer wodim
9644 </p
></blockquote
>
9646 <p
>Installed using aptitude, missing with apt-get
</p
>
9648 <blockquote
><p
>
9649 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9650 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9651 xserver-xorg-input-all xserver-xorg-input-evdev
9652 xserver-xorg-input-kbd xserver-xorg-input-mouse
9653 xserver-xorg-input-synaptics xserver-xorg-video-all
9654 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9655 xserver-xorg-video-chips xserver-xorg-video-cirrus
9656 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9657 xserver-xorg-video-glint xserver-xorg-video-i128
9658 xserver-xorg-video-i740 xserver-xorg-video-mach64
9659 xserver-xorg-video-mga xserver-xorg-video-neomagic
9660 xserver-xorg-video-nouveau xserver-xorg-video-nv
9661 xserver-xorg-video-r128 xserver-xorg-video-radeon
9662 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9663 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9664 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9665 xserver-xorg-video-sis xserver-xorg-video-sisusb
9666 xserver-xorg-video-tdfx xserver-xorg-video-tga
9667 xserver-xorg-video-trident xserver-xorg-video-tseng
9668 xserver-xorg-video-vesa xserver-xorg-video-vmware
9669 xserver-xorg-video-voodoo
9670 </p
></blockquote
>
9672 <p
>Installed using aptitude, removed with apt-get
</p
>
9674 <blockquote
><p
>
9675 deskbar-applet xserver-xorg xserver-xorg-core
9676 xserver-xorg-input-wacom xserver-xorg-video-intel
9677 xserver-xorg-video-openchrome
9678 </p
></blockquote
>
9680 <p
>I was told on IRC that the xorg-xserver package was
9681 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9682 in git
</a
> today to try to get apt-get to not remove xorg completely.
9683 No idea when it hits Squeeze, but when it does I hope it will reduce
9684 the difference somewhat.
9689 <title>LUMA, a very nice LDAP GUI
</title>
9690 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9691 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9692 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9693 <description><p
>The last few days I have been looking into the status of the LDAP
9694 directory in Debian Edu, and in the process I started to miss a GUI
9695 tool to browse the LDAP tree. The only one I was able to find in
9696 Debian/Squeeze and Lenny is
9697 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9698 be a great tool to get a overview of the current LDAP directory
9699 populated by default in Skolelinux. Thanks to it, I have been able to
9700 find empty and obsolete subtrees, misplaced objects and duplicate
9701 objects. It will be installed by default in Debian/Squeeze. If you
9702 are working with LDAP, give it a go. :)
</p
>
9704 <p
>I did notice one problem with it I have not had time to report to
9705 the BTS yet. There is no .desktop file in the package, so the tool do
9706 not show up in the Gnome and KDE menus, but only deep down in in the
9707 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9710 <p
>I have not yet been able to get it to modify the tree yet. I would
9711 like to move objects and remove subtrees directly in the GUI, but have
9712 not found a way to do that with LUMA yet. So in the mean time, I use
9713 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9715 <p
>If you have tips on other GUI tools for LDAP that might be useful
9716 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9718 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9719 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9720 useful GUI alternative. It seem like a good tool, but is unmaintained
9721 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9722 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9727 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9728 <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>
9729 <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>
9730 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9731 <description><p
>A while back, I
9732 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9733 about the fact
</a
> that it is not possible with the provided schemas
9734 for storing DNS and DHCP information in LDAP to combine the two sets
9735 of information into one LDAP object representing a computer.
</p
>
9737 <p
>In the mean time, I discovered that a simple fix would be to make
9738 the dhcpHost object class auxiliary, to allow it to be combined with
9739 the dNSDomain object class, and thus forming one object for one
9740 computer when storing both DHCP and DNS information in LDAP.
</p
>
9742 <p
>If I understand this correctly, it is not safe to do this change
9743 without also changing the assigned number for the object class, and I
9744 do not know enough about LDAP schema design to do that properly for
9745 Debian Edu.
</p
>
9747 <p
>Anyway, for future reference, this is how I believe we could change
9749 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9750 schema
</a
> to solve at least part of the problem with the LDAP schemas
9751 available today from IETF.
</p
>
9754 --- dhcp.schema (revision
65192)
9755 +++ dhcp.schema (working copy)
9757 objectclass (
2.16.840.1.113719.1.203.6.6
9758 NAME
'dhcpHost
'
9759 DESC
'This represents information about a particular client
'
9763 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9764 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9767 <p
>I very much welcome clues on how to do this properly for Debian
9768 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9769 package, and should thus be free to rewrite it as we see fit.
</p
>
9771 <p
>If you want to help out with implementing this for Debian Edu,
9772 please contact us on debian-edu@lists.debian.org.
</p
>
9777 <title>Calling tasksel like the installer, while still getting useful output
</title>
9778 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9780 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9781 <description><p
>A few times I have had the need to simulate the way tasksel
9782 installs packages during the normal debian-installer run. Until now,
9783 I have ended up letting tasksel do the work, with the annoying problem
9784 of not getting any feedback at all when something fails (like a
9785 conffile question from dpkg or a download that fails), using code like
9788 <blockquote
><pre
>
9789 export DEBIAN_FRONTEND=noninteractive
9790 tasksel --new-install
9791 </pre
></blockquote
>
9793 This would invoke tasksel, let its automatic task selection pick the
9794 tasks to install, and continue to install the requested tasks without
9795 any output what so ever.
9797 Recently I revisited this problem while working on the automatic
9798 package upgrade testing, because tasksel would some times hang without
9799 any useful feedback, and I want to see what is going on when it
9800 happen. Then it occured to me, I can parse the output from tasksel
9801 when asked to run in test mode, and use that aptitude command line
9802 printed by tasksel then to simulate the tasksel run. I ended up using
9805 <blockquote
><pre
>
9806 export DEBIAN_FRONTEND=noninteractive
9807 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9809 </pre
></blockquote
>
9811 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9812 --without-recommends -o APT::Install-Recommends=no -y install
9813 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9814 ~pimportant
</tt
>", which will install the gnome desktop task, the
9815 laptop task and all packages with priority standard , required and
9816 important, just like tasksel would have done it during
9817 installation.
</p
>
9819 <p
>A better approach is probably to extend tasksel to be able to
9820 install packages without using debconf-apt-progress, for use cases
9821 like this.
</p
>
9826 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9827 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9828 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9829 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9830 <description><p
>My
9831 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9832 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9833 finally made the upgrade logs available from
9834 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9835 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9836 apt and aptitude, and found their differences interesting. This time
9837 I will only focus on their removal plans.
</p
>
9839 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9840 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9841 surprising part is that it want to remove xorg and all
9842 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9843 sure why. When asking aptitude to do the same, it want to remove
129
9844 packages, but most of them are library packages I suspect are no
9845 longer needed. Both of them want to remove bluetooth packages, which
9846 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9848 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9849 which seem like a bad idea and xorg the same way as with Gnome. Asking
9850 aptitude for the same, it wants to remove
192 packages, none which are
9851 too surprising.
</p
>
9853 <p
>I guess the removal of xorg during upgrades should be investigated
9854 and avoided, and perhaps others as well. Here are the complete list
9855 of planned removals. The complete logs is available from the URL
9856 above. Note if you want to repeat these tests, that the upgrade test
9857 for kde+apt-get hung in the tasksel setup because of dpkg asking
9858 conffile questions. No idea why. I worked around it by using
9859 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9862 <p
><b
>apt-get gnome
72</b
>
9863 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9864 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9865 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9866 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9867 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9868 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9869 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9870 xserver-xorg-input-kbd xserver-xorg-input-mouse
9871 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9872 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9873 xserver-xorg-video-ati xserver-xorg-video-chips
9874 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9875 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9876 xserver-xorg-video-glint xserver-xorg-video-i128
9877 xserver-xorg-video-i740 xserver-xorg-video-imstt
9878 xserver-xorg-video-intel xserver-xorg-video-mach64
9879 xserver-xorg-video-mga xserver-xorg-video-neomagic
9880 xserver-xorg-video-nsc xserver-xorg-video-nv
9881 xserver-xorg-video-openchrome xserver-xorg-video-r128
9882 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9883 xserver-xorg-video-rendition xserver-xorg-video-s3
9884 xserver-xorg-video-s3virge xserver-xorg-video-savage
9885 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9886 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9887 xserver-xorg-video-tga xserver-xorg-video-trident
9888 xserver-xorg-video-tseng xserver-xorg-video-v4l
9889 xserver-xorg-video-vesa xserver-xorg-video-vga
9890 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9891 xulrunner-
1.9-gnome-support
</p
>
9893 <p
><b
>aptitude gnome
129</b
>
9895 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9896 djvulibre-desktop finger gnome-app-install gnome-mount
9897 gnome-network-admin gnome-spell gnome-vfs-obexftp
9898 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9899 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9900 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9901 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9902 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9903 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9904 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9905 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9906 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9907 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9908 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9909 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9910 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9911 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9912 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9913 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9914 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9915 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9916 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9917 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9918 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9919 openoffice.org-writer2latex openssl-blacklist p7zip
9920 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9921 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9922 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9923 swfdec-mozilla totem-gstreamer update-manager wodim
9924 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9925 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9928 <p
><b
>apt-get kde
82</b
>
9930 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9931 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9932 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9933 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9934 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9935 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9936 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9937 xserver-xorg-input-kbd xserver-xorg-input-mouse
9938 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9939 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9940 xserver-xorg-video-ati xserver-xorg-video-chips
9941 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9942 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9943 xserver-xorg-video-glint xserver-xorg-video-i128
9944 xserver-xorg-video-i740 xserver-xorg-video-imstt
9945 xserver-xorg-video-intel xserver-xorg-video-mach64
9946 xserver-xorg-video-mga xserver-xorg-video-neomagic
9947 xserver-xorg-video-nsc xserver-xorg-video-nv
9948 xserver-xorg-video-openchrome xserver-xorg-video-r128
9949 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9950 xserver-xorg-video-rendition xserver-xorg-video-s3
9951 xserver-xorg-video-s3virge xserver-xorg-video-savage
9952 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9953 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9954 xserver-xorg-video-tga xserver-xorg-video-trident
9955 xserver-xorg-video-tseng xserver-xorg-video-v4l
9956 xserver-xorg-video-vesa xserver-xorg-video-vga
9957 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9959 <p
><b
>aptitude kde
192</b
>
9960 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9961 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9962 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9963 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9964 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9965 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9966 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9967 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9968 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9969 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9970 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9971 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9972 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9973 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9974 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9975 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9976 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9977 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9978 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9979 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9980 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9981 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9982 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9983 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9984 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9985 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9986 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9987 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9988 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9989 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9990 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9991 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9992 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9993 texlive-common texlive-doc-base texlive-fonts-recommended
9994 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9995 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9996 xulrunner-
1.9</p
>
10002 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
10003 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
10004 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
10005 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
10006 <description><p
>The last few days I have done some upgrade testing in Debian, to
10007 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10008 have been discovered and reported in the process
10009 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
10010 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
10011 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
10012 kdebase-workspace-data), and to get a more regular testing going on, I
10013 am working on a script to automate the test.
</p
>
10015 <p
>The idea is to create a Lenny chroot and use tasksel to install a
10016 Gnome or KDE desktop installation inside the chroot before upgrading
10017 it. To ensure no services are started in the chroot, a policy-rc.d
10018 script is inserted. To make sure tasksel believe it is to install a
10019 desktop on a laptop, the tasksel tests are replaced in the chroot
10020 (only acceptable because this is a throw-away chroot).
</p
>
10022 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10023 currently always fail because udev refuses to upgrade with the kernel
10024 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10025 is created. The bug report
10026 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
10027 this problem do not trigger in a chroot, but I touch the file anyway
10028 to make sure the upgrade go well. Testing on virtual and real
10029 hardware have failed me because of udev so far, and creating this file
10030 do the trick in such settings anyway. This is a
10031 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
10032 issue
</a
> and the current udev behaviour is intended by the udev
10033 maintainer because he lack the resources to rewrite udev to keep
10034 working with old kernels or something like that. I really wish the
10035 udev upstream would keep udev backwards compatible, to avoid such
10036 upgrade problem, but given that they fail to do so, I guess
10037 documenting the way out of this mess is the best option we got for
10038 Debian Squeeze.
</p
>
10040 <p
>Anyway, back to the task at hand, testing upgrades. This test
10041 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10044 <blockquote
><pre
>
10048 if [
"$
1" ] ; then
10057 exec
&lt; /dev/null
10059 mirror=http://ftp.skolelinux.org/debian
10060 tmpdir=chroot-$from-upgrade-$to-$desktop
10062 debootstrap $from $tmpdir $mirror
10063 chroot $tmpdir aptitude update
10064 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10068 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10070 umount $tmpdir/proc
10072 mount -t proc proc $tmpdir/proc
10073 # Make sure proc is unmounted also on failure
10074 trap exit_cleanup EXIT INT
10076 chroot $tmpdir aptitude -y install debconf-utils
10078 # Make sure tasksel autoselection trigger. It need the test scripts
10079 # to return the correct answers.
10080 echo tasksel tasksel/desktop multiselect $desktop | \
10081 chroot $tmpdir debconf-set-selections
10083 # Include the desktop and laptop task
10084 for test in desktop laptop ; do
10085 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10089 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10092 DEBIAN_FRONTEND=noninteractive
10093 DEBIAN_PRIORITY=critical
10094 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10095 chroot $tmpdir tasksel --new-install
10097 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10098 chroot $tmpdir aptitude update
10099 touch $tmpdir/etc/udev/kernel-upgrade
10100 chroot $tmpdir aptitude -y dist-upgrade
10102 </pre
></blockquote
>
10104 <p
>I suspect it would be useful to test upgrades with both apt-get and
10105 with aptitude, but I have not had time to look at how they behave
10106 differently so far. I hope to get a cron job running to do the test
10107 regularly and post the result on the web. The Gnome upgrade currently
10108 work, while the KDE upgrade fail because of the bug in
10109 kdebase-workspace-data
</p
>
10111 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10112 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10113 post, so I will refrain from trying. I can report that for Gnome,
10114 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10115 remove and
1 not upgraded and
1024MB need to be downloaded while for
10116 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10117 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10119 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10120 is able to migrate to dependency based boot sequencing and parallel
10121 booting without a hitch. Was unsure if there were still bugs with
10122 packages failing to clean up their obsolete init.d script during
10123 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10124 packages.
</p
>
10129 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10130 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10132 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10133 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10134 scripts to migrate (some of) their operations to upstart job while
10135 keeping the init.d for hurd and kfreebsd. The packages with such
10136 needs will need a way to get their init.d scripts to behave
10137 differently when used with sysvinit and with upstart. Because of
10138 this, I had a look at the environment variables set when a init.d
10139 script is running under upstart, and when it is not.
</p
>
10141 <p
>With upstart, I notice these environment variables are set when a
10142 script is started from rcS.d/ (ignoring some irrelevant ones like
10143 COLUMNS):
</p
>
10145 <blockquote
><pre
>
10151 UPSTART_EVENTS=startup
10153 UPSTART_JOB=rc-sysinit
10154 </pre
></blockquote
>
10156 <p
>With sysvinit, these environment variables are set for the same
10159 <blockquote
><pre
>
10160 INIT_VERSION=sysvinit-
2.88
10165 </pre
></blockquote
>
10167 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10168 sysvinit are not set by upstart. Not sure if it is intentional or not
10169 to not be compatible with sysvinit in this regard.
</p
>
10171 <p
>For scripts needing to behave differently when upstart is used,
10172 looking for the UPSTART_JOB environment variable seem to be a good
10178 <title>A manual for standards wars...
</title>
10179 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10180 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10181 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10182 <description><p
>Via the
10183 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10184 of Rob Weir
</a
> I came across the very interesting essay named
10185 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10186 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10187 following the standards wars of today.
</p
>
10192 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10193 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10195 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10196 <description><p
>When using sitesummary at a site to track machines, it is possible
10197 to get a list of the machine types in use thanks to the DMI
10198 information extracted from each machine. The script to do so is
10199 included in the sitesummary package, and here is example output from
10200 the Skolelinux build servers:
</p
>
10202 <blockquote
><pre
>
10203 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10205 Dell Computer Corporation
1
10208 eserver xSeries
345 -[
8670M1X]-
1
10212 </pre
></blockquote
>
10214 <p
>The quality of the report depend on the quality of the DMI tables
10215 provided in each machine. Here there are Intel machines without model
10216 information listed with Intel as vendor and no model, and virtual Xen
10217 machines listed as [no-dmi-info]. One can add -l as a command line
10218 option to list the individual machines.
</p
>
10220 <p
>A larger list is
10221 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10222 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10223 provide the basic sitesummary report publicly. In their report there
10224 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10225 their machines, and as sitesummary is available in both distributions,
10226 it is trivial to get all of them to report to the same central
10227 collector.
</p
>
10232 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10233 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10234 <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>
10235 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10236 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10237 start at boot when an NVidia video card is used is handled. The
10238 problem seem to be that the nvidia X.org driver uses a long time to
10239 initialize, and this duration is longer than kdm is configured to
10242 <p
>I came across two bugs related to this issue,
10243 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10244 against initscripts and passed on to nvidia-glx when it became obvious
10245 that the nvidia drivers were involved, and
10246 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10247 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10249 <p
>To me, it seem that no-one is interested in actually solving the
10250 problem nvidia video card owners experience and make sure the Debian
10251 distribution work out of the box for these users. The nvidia driver
10252 maintainers expect kdm to be set up to wait longer, while kdm expect
10253 the nvidia driver maintainers to fix the driver to start faster, and
10254 while they wait for each other I guess the users end up switching to a
10255 distribution that work for them. I have no idea what the solution is,
10256 but I am pretty sure that waiting for each other is not it.
</p
>
10258 <p
>I wonder why we end up handling bugs this way.
</p
>
10263 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10264 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10265 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10266 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10267 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10268 The feature seem to hold up pretty well, but three fairly serious
10269 issues are known and should be solved:
10271 <p
><ul
>
10273 <li
>The wicd package seen to
10274 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10275 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10276 parallel booting is enabled. No idea why, but the wicd maintainer
10277 seem to be on the case.
</li
>
10279 <li
>The nvidia X driver seem to
10280 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10281 triggered more easily when parallel booting is in effect. The
10282 maintainer is on the case.
</li
>
10284 <li
>The sysv-rc package fail to properly enable dependency based boot
10285 sequencing (the shutdown is broken) when old file-rc users
10286 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10287 sysv-rc. One way to solve it would be for file-rc to create
10288 /etc/init.d/.legacy-bootordering, and another is to try to make
10289 sysv-rc more robust. Will investigate some more and probably upload a
10290 workaround in sysv-rc to help those trying to move from file-rc to
10291 sysv-rc get a working shutdown.
</li
>
10293 </ul
></p
>
10295 <p
>All in all not many surprising issues, and all of them seem
10296 solvable before Squeeze is released. In addition to these there are
10297 some packages with bugs in their dependencies and run level settings,
10298 which I expect will be fixed in a reasonable time span.
</p
>
10300 <p
>If you report any problems with dependencies in init.d scripts to
10301 the BTS, please usertag the report to get it to show up at
10302 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10303 list of usertagged bugs related to this
</a
>.
</p
>
10305 <p
>Update: Correct bug number to file-rc issue.
</p
>
10310 <title>More flexible firmware handling in debian-installer
</title>
10311 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10312 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10313 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10314 <description><p
>After a long break from debian-installer development, I finally
10315 found time today to return to the project. Having to spend less time
10316 working dependency based boot in debian, as it is almost complete now,
10317 definitely helped freeing some time.
</p
>
10319 <p
>A while back, I ran into a problem while working on Debian Edu. We
10320 include some firmware packages on the Debian Edu CDs, those needed to
10321 get disk and network controllers working. Without having these
10322 firmware packages available during installation, it is impossible to
10323 install Debian Edu on the given machine, and because our target group
10324 are non-technical people, asking them to provide firmware packages on
10325 an external medium is a support pain. Initially, I expected it to be
10326 enough to include the firmware packages on the CD to get
10327 debian-installer to find and use them. This proved to be wrong.
10328 Next, I hoped it was enough to symlink the relevant firmware packages
10329 to some useful location on the CD (tried /cdrom/ and
10330 /cdrom/firmware/). This also proved to not work, and at this point I
10331 found time to look at the debian-installer code to figure out what was
10332 going to work.
</p
>
10334 <p
>The firmware loading code is in the hw-detect package, and a closer
10335 look revealed that it would only look for firmware packages outside
10336 the installation media, so the CD was never checked for firmware
10337 packages. It would only check USB sticks, floppies and other
10338 "external
" media devices. Today I changed it to also look in the
10339 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10340 solve the problem I ran into with Debian edu. I also changed it to
10341 look in /firmware/, to make sure the installer also find firmware
10342 provided in the initrd when booting the installer via PXE, to allow us
10343 to provide the same feature in the PXE setup included in Debian
10346 <p
>To make sure firmware deb packages with a license questions are not
10347 activated without asking if the license is accepted, I extended
10348 hw-detect to look for preinst scripts in the firmware packages, and
10349 run these before activating the firmware during installation. The
10350 license question is asked using debconf in the preinst, so this should
10351 solve the issue for the firmware packages I have looked at so far.
</p
>
10353 <p
>If you want to discuss the details of these features, please
10354 contact us on debian-boot@lists.debian.org.
</p
>
10359 <title>Parallellized boot is now the default in Debian/unstable
</title>
10360 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10361 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10362 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10363 <description><p
>Since this evening, parallel booting is the default in
10364 Debian/unstable for machines using dependency based boot sequencing.
10365 Apparently the testing of concurrent booting has been wider than
10366 expected, if I am to believe the
10367 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10368 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10369 with the feature this weekend, to give us some time to detect any
10370 remaining problems before Squeeze is frozen. If serious problems are
10371 detected, it is simple to change the default back to sequential boot.
10372 The upload of the new sysvinit package also activate a new upstream
10375 More information about
10376 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10377 based boot sequencing
</a
> is available from the Debian wiki. It is
10378 currently possible to disable parallel booting when one run into
10379 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10381 <blockquote
><pre
>
10383 </pre
></blockquote
>
10385 <p
>If you report any problems with dependencies in init.d scripts to
10386 the BTS, please usertag the report to get it to show up at
10387 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10388 list of usertagged bugs related to this
</a
>.
</p
>
10393 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10394 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10395 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10396 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10397 <description><p
>In the recent Debian Edu versions, the
10398 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10399 system
</a
> is used to keep track of the machines in the school
10400 network. Each machine will automatically report its status to the
10401 central server after boot and once per night. The network setup is
10402 also reported, and using this information it is possible to get the
10403 MAC address of all network interfaces in the machines. This is useful
10404 to update the DHCP configuration.
</p
>
10406 <p
>To give some idea how to use sitesummary, here is a one-liner to
10407 ist all MAC addresses of all machines reporting to sitesummary. Run
10408 this on the collector host:
</p
>
10410 <blockquote
><pre
>
10411 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10412 </pre
></blockquote
>
10414 <p
>This will list all MAC addresses assosiated with all machine, one
10415 line per machine and with space between the MAC addresses.
</p
>
10417 <p
>To allow system administrators easier job at adding static DHCP
10418 addresses for hosts, it would be possible to extend this to fetch
10419 machine information from sitesummary and update the DHCP and DNS
10420 tables in LDAP using this information. Such tool is unfortunately not
10421 written yet.
</p
>
10426 <title>systemd, an interesting alternative to upstart
</title>
10427 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10428 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10429 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10430 <description><p
>The last few days a new boot system called
10431 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10433 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10435 to the free software world. I have not yet had time to play around
10436 with it, but it seem to be a very interesting alternative to
10437 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10438 a good alternative for Debian when we are able to switch to an event
10439 based boot system. Tollef is
10440 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10441 systemd into Debian, and I look forward to seeing how well it work. I
10442 like the fact that systemd handles init.d scripts with dependency
10443 information natively, allowing them to run in parallel where upstart
10444 at the moment do not.
</p
>
10446 <p
>Unfortunately do systemd have the same problem as upstart regarding
10447 platform support. It only work on recent Linux kernels, and also need
10448 some new kernel features enabled to function properly. This means
10449 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10450 system. Not sure how that will be handled if systemd proves to be the
10451 way forward.
</p
>
10453 <p
>In the mean time, based on the
10454 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10455 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10456 decided to enable full parallel booting as the default in Debian as
10457 soon as possible (probably this weekend or early next week), to see if
10458 there are any remaining serious bugs in the init.d dependencies. A
10459 new version of the sysvinit package implementing this change is
10460 already in experimental. If all go well, Squeeze will be released
10461 with parallel booting enabled by default.
</p
>
10466 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10467 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10468 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10469 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10470 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10471 complete, so complete that it is actually possible to run all the
10472 init.d scripts in parallell based on these dependencies. If you want
10473 to test your Squeeze system, make sure
10474 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10475 based boot sequencing
</a
> is enabled, and add this line to
10476 /etc/default/rcS:
</p
>
10478 <blockquote
><pre
>
10479 CONCURRENCY=makefile
10480 </pre
></blockquote
>
10482 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10483 scripts in parallel using the dependency information stored in
10484 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10485 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10486 to try to start the kdm and gdm scripts as early as possible, and will
10487 start the facilities required by kdm or gdm as early as possible to
10488 make this happen.
</p
>
10490 <p
>Give it a try, and see if you like the result. If some services
10491 fail to start properly, it is most likely because they have incomplete
10492 init.d script dependencies in their startup script (or some of their
10493 dependent scripts have incomplete dependencies). Report bugs and get
10494 the package maintainers to fix it. :)
</p
>
10496 <p
>Running scripts in parallel could be the default in Debian when we
10497 manage to get the init.d script dependencies complete and correct. I
10498 expect we will get there in Squeeze+
1, if we get manage to test and
10499 fix the remaining issues.
</p
>
10501 <p
>If you report any problems with dependencies in init.d scripts to
10502 the BTS, please usertag the report to get it to show up at
10503 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10504 list of usertagged bugs related to this
</a
>.
</p
>
10509 <title>Debian has switched to dependency based boot sequencing
</title>
10510 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10512 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10513 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10514 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10515 have been migrated to using dependency based boot sequencing. This
10516 conclude work me and others have been doing for the last three days.
10517 It feels great to see this finally part of the default Debian
10518 installation. Now we just need to weed out the last few problems that
10519 are bound to show up, to get everything ready for Squeeze.
</p
>
10521 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10522 fixing the more fundamental problem of handing the event based
10523 non-predictable kernel in the early boot.
</p
>
10528 <title>Taking over sysvinit development
</title>
10529 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10530 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10531 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10532 <description><p
>After several years of frustration with the lack of activity from
10533 the existing sysvinit upstream developer, I decided a few weeks ago to
10534 take over the package and become the new upstream. The number of
10535 patches to track for the Debian package was becoming a burden, and the
10536 lack of synchronization between the distribution made it hard to keep
10537 the package up to date.
</p
>
10539 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10540 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10541 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10542 and Fedora), based on the patches currently in use in these
10543 distributions. We Debian maintainers plan to move to this tarball as
10544 the new upstream as soon as we find time to do the merge. Since the
10545 new tarball was created, we agreed with Werner at SuSe to make a new
10546 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10547 development there. The project is registered and currently waiting
10548 for approval by the Savannah administrators, and as soon as it is
10549 approved, we will import the old versions from svn and continue
10550 working on the future release.
</p
>
10552 <p
>It is a bit ironic that this is done now, when some of the involved
10553 distributions are moving to upstart as a syvinit replacement.
</p
>
10558 <title>Debian boots quicker and quicker
</title>
10559 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10561 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10562 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10563 people involved in the boot system on Debian and Ubuntu, to see if we
10564 could find more ways to speed up the boot system. This was an Ubuntu
10566 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10567 gathering
</a
>. It was quite productive. We also discussed the future
10568 of boot systems, and ways to handle the increasing number of boot
10569 issues introduced by the Linux kernel becoming more and more
10570 asynchronous and event base. The Ubuntu approach using udev and
10571 upstart might be a good way forward. Time will show.
</p
>
10573 <p
>Anyway, there are a few ways at the moment to speed up the boot
10574 process in Debian. All of these should be applied to get a quick
10579 <li
>Use dash as /bin/sh.
</li
>
10581 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10582 clock is in UTC.
</li
>
10584 <li
>Install and activate the insserv package to enable
10585 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10586 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10590 These points are based on the Google summer of code work done by
10591 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10592 Villegas
</a
>.
10594 <p
>Support for makefile-style concurrency during boot was uploaded to
10595 unstable yesterday. When we tested it, we were able to cut
6 seconds
10596 from the boot sequence. It depend on very correct dependency
10597 declaration in all init.d scripts, so I expect us to find edge cases
10598 where the dependences in some scripts are slightly wrong when we start
10599 using this.
</p
>
10601 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10602 introduced by Raphael Geissert today, one that could affect the
10603 startup speed as well. Instead of starting some scripts concurrently
10604 from rcS.d/ and another set of scripts from rc2.d/, it would be
10605 possible to run a of them in the same process. A quick way to test
10606 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10607 insserv
'. Will need to test if that work. :)
</p
>
10612 <title>BSAs påstander om piratkopiering møter motstand
</title>
10613 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10614 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10615 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10616 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10617 programvareselskapene som Microsoft og Apple, publisert en rapport der
10618 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10619 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10621 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10622 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10623 dagene. Et spesielt interessant kommentar fra Sverige,
10624 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10625 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10628 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10629 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10630 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10631 exakta
", säger BSAs Sverigechef John Hugosson.
10632 </blockquote
>
10634 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10635 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10636 piracy figures need a shot of reality
</a
> og
<a
10637 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10638 Copyright Treaty Work?
</a
></p
>
10640 <p
>Fant lenkene via
<a
10641 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10642 på Slashdot
</a
>.
</p
>
10647 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10648 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10649 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10650 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10651 <description><p
>Kom over
10652 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10653 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10654 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10655 jobber til daglig. En rask opptelling forteller meg at vi har
490
10656 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10657 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10658 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10663 <title>Kryptert harddisk - naturligvis
</title>
10664 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10665 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10666 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10667 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10668 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10669 når en tar tap av arbeidstid, fortrolige dokumenter,
10670 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10671 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10672 til at jeg har kryptert harddisken på både kontormaskinen og min
10673 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10674 komme på avveie, den første informasjon relatert til jobben min ved
10675 Universitetet i Oslo, og den andre relatert til blant annet
10676 foreningsarbeide. Kryptering av diskene gjør at det er lite
10677 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10678 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10679 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10680 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10681 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10682 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10683 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10684 det er gjort slik jeg gjør det er minimale, og gevinstene er
10685 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10686 maskinen reinstalleres og alt er tapt.
</p
>
10688 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10689 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10690 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10691 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10692 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10693 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10694 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10695 betydelige.
</p
>
10700 <title>Two projects that have improved the quality of free software a lot
</title>
10701 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10702 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10703 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10704 <description><p
>There are two software projects that have had huge influence on the
10705 quality of free software, and I wanted to mention both in case someone
10706 do not yet know them.
</p
>
10708 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10709 tool to detect and expose errors in the memory handling of programs.
10710 It is easy to use, all one need to do is to run
'valgrind program
',
10711 and it will report any problems on stdout. It is even better if the
10712 program include debug information. With debug information, it is able
10713 to report the source file name and line number where the problem
10714 occurs. It can report things like
'reading past memory block in file
10715 X line N, the memory block was allocated in file Y, line M
', and
10716 'using uninitialised value in control logic
'. This tool has made it
10717 trivial to investigate reproducible crash bugs in programs, and have
10718 reduced the number of this kind of bugs in free software a lot.
10720 <p
>The second one is
10721 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10722 a source code checker. It is able to process the source of a program
10723 and find problems in the logic without running the program. It
10724 started out as the Stanford Checker and became well known when it was
10725 used to find bugs in the Linux kernel. It is now a commercial tool
10726 and the company behind it is running
10727 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10728 free software community, where a lot of free software projects get
10729 their source checked for free. Several thousand defects have been
10730 found and fixed so far. It can find errors like
'lock L taken in file
10731 X line N is never released if exiting in line M
', or
'the code in file
10732 Y lines O to P can never be executed
'. The projects included in the
10733 community service project have managed to get rid of a lot of
10734 reliability problems thanks to Coverity.
</p
>
10736 <p
>I believe tools like this, that are able to automatically find
10737 errors in the source, are vital to improve the quality of software and
10738 make sure we can get rid of the crashing and failing software we are
10739 surrounded by today.
</p
>
10744 <title>No patch is not better than a useless patch
</title>
10745 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10746 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10747 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10748 <description><p
>Julien Blache
10749 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10750 patch is better than a useless patch
</a
>. I completely disagree, as a
10751 patch allow one to discuss a concrete and proposed solution, and also
10752 prove that the issue at hand is important enough for someone to spent
10753 time on fixing it. No patch do not provide any of these positive
10754 properties.
</p
>
10759 <title>Standardize on protocols and formats, not vendors and applications
</title>
10760 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10761 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10762 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10763 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10764 very good one to form a long lived computer infrastructure. It is the
10765 simple one, lost by many in todays computer industry: Standardize on
10766 open network protocols and open exchange/storage formats, not applications.
10767 Applications come and go, while protocols and files tend to stay, and
10768 thus one want to make it easy to change application and vendor, while
10769 avoiding conversion costs and locking users to a specific platform or
10770 application.
</p
>
10772 <p
>This approach make it possible to replace the client applications
10773 independently of the server applications. One can even allow users to
10774 use several different applications as long as they handle the selected
10775 protocol and format. In the normal case, only one client application
10776 is recommended and users only get help if they choose to use this
10777 application, but those that want to deviate from the easy path are not
10778 blocked from doing so.
</p
>
10780 <p
>It also allow us to replace the server side without forcing the
10781 users to replace their applications, and thus allow us to select the
10782 best server implementation at any moment, when scale and resouce
10783 requirements change.
</p
>
10785 <p
>I strongly recommend standardizing - on open network protocols and
10786 open formats, but I would never recommend standardizing on a single
10787 application that do not use open network protocol or open formats.
</p
>
10792 <title>Returning from Skolelinux developer gathering
</title>
10793 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10794 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10795 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10796 <description><p
>I
'm sitting on the train going home from this weekends Debian
10797 Edu/Skolelinux development gathering. I got a bit done tuning the
10798 desktop, and looked into the dynamic service location protocol
10799 implementation avahi. It look like it could be useful for us. Almost
10800 30 people participated, and I believe it was a great environment to
10801 get to know the Skolelinux system. Walter Bender, involved in the
10802 development of the Sugar educational platform, presented his stuff and
10803 also helped me improve my OLPC installation. He also showed me that
10804 his Turtle Art application can be used in standalone mode, and we
10805 agreed that I would help getting it packaged for Debian. As a
10806 standalone application it would be great for Debian Edu. We also
10807 tried to get the video conferencing working with two OLPCs, but that
10808 proved to be too hard for us. The application seem to need more work
10809 before it is ready for me. I look forward to getting home and relax
10815 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10816 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10817 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10818 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10819 <description><p
>The state of standardized LDAP schemas on Linux is far from
10820 optimal. There is RFC
2307 documenting one way to store NIS maps in
10821 LDAP, and a modified version of this normally called RFC
2307bis, with
10822 some modifications to be compatible with Active Directory. The RFC
10823 specification handle the content of a lot of system databases, but do
10824 not handle DNS zones and DHCP configuration.
</p
>
10826 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10827 we would like to store information about users, SMB clients/hosts,
10828 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10829 and LTSP configuration in LDAP. These objects have a lot in common,
10830 but with the current LDAP schemas it is not possible to have one
10831 object per entity. For example, one need to have at least three LDAP
10832 objects for a given computer, one with the SMB related stuff, one with
10833 DNS information and another with DHCP information. The schemas
10834 provided for DNS and DHCP are impossible to combine into one LDAP
10835 object. In addition, it is impossible to implement quick queries for
10836 netgroup membership, because of the way NIS triples are implemented.
10837 It just do not scale. I believe it is time for a few RFC
10838 specifications to cleam up this mess.
</p
>
10840 <p
>I would like to have one LDAP object representing each computer in
10841 the network, and this object can then keep the SMB (ie host key), DHCP
10842 (mac address/name) and DNS (name/IP address) settings in one place.
10843 It need to be efficently stored to make sure it scale well.
</p
>
10845 <p
>I would also like to have a quick way to map from a user or
10846 computer and to the net group this user or computer is a member.
</p
>
10848 <p
>Active Directory have done a better job than unix heads like myself
10849 in this regard, and the unix side need to catch up. Time to start a
10850 new IETF work group?
</p
>
10855 <title>Endelig er Debian Lenny gitt ut
</title>
10856 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10857 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10858 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10859 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10860 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10861 Et langt steg videre for Debian-prosjektet, og en rekke nye
10862 programpakker blir nå tilgjengelig for de av oss som bruker den
10863 stabile utgaven av Debian. Neste steg er nå å få
10864 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10865 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10866 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10867 slippes løs på skolene. Takk til alle debian-utviklerne som har
10868 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10869 bootsekvens tilgjengelig i stabil utgave, vha pakken
10870 <tt
>insserv
</tt
>.
</p
>
10875 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10876 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10878 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10879 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10880 Oslo. Most of Saturday was used for the general assemly for the
10881 member organization, but the rest of the weekend I used to tune the
10882 LTSP installation. LTSP now work out of the box on the
10-network.
10883 Acer Aspire One proved to be a very nice thin client, with both
10884 screen, mouse and keybard in a small box. Was working on getting the
10885 diskless workstation setup configured out of the box, but did not
10886 finish it before the weekend was up.
</p
>
10888 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10889 the Brazilian group, so that will have to wait for the next
10890 development gathering. Would love to have the Debian Edu installer
10891 automatically detect and configure a multiseat setup when it find one
10892 of these cards.
</p
>
10897 <title>The sorry state of multimedia browser plugins in Debian
</title>
10898 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10900 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10901 <description><p
>Recently I have spent some time evaluating the multimedia browser
10902 plugins available in Debian Lenny, to see which one we should use by
10903 default in Debian Edu. We need an embedded video playing plugin with
10904 control buttons to pause or stop the video, and capable of streaming
10905 all the multimedia content available on the web. The test results and
10906 notes are available on
10907 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10908 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10909 fill this need. My personal video player favorite, VLC, has a really
10910 bad plugin which fail on a lot of the test pages. A lot of the MIME
10911 types I would expect to work with any free software player (like
10912 video/ogg), just do not work. And simple formats like the
10913 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10914 totem and vlc plugins. I hope the situation will improve soon. No
10915 wonder sites use the proprietary Adobe flash to play video.
</p
>
10917 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10918 be the only one fitting our needs. :/
</p
>