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>What is the most supported MIME type in Debian in
2018?
</title>
11 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
13 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
14 <description><p
>Five years ago,
15 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
16 measured what the most supported MIME type in Debian was
</a
>, by
17 analysing the desktop files in all packages in the archive. Since
18 then, the DEP-
11 AppStream system has been put into production, making
19 the task a lot easier. This made me want to repeat the measurement,
20 to see how much things changed. Here are the new numbers, for
21 unstable only this time:
23 <p
><strong
>Debian Unstable:
</strong
></p
>
27 ----- -----------------------
40 29 image/x-portable-pixmap
42 27 image/x-portable-bitmap
50 <p
>The list was created like this using a sid chroot:
"cat
51 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
52 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
54 <p
>It is interesting to see how image formats have passed text/plain
55 as the most announced supported MIME type. These days, thanks to the
56 AppStream system, if you run into a file format you do not know, and
57 want to figure out which packages support the format, you can find the
58 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
59 look up all packages announcing support for this format in their
60 AppStream metadata (XML or .desktop file) using
"appstreamcli
61 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
62 me, want to know which packages support inode/directory, you can get a
63 list like this:
</p
>
65 <p
><blockquote
><pre
>
66 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
73 Package: doublecmd-common
75 Package: enlightenment
95 </pre
></blockquote
></p
>
97 <p
>Using the same method, I can quickly discover that the Sketchup file
98 format is not yet supported by any package in Debian:
</p
>
100 <p
><blockquote
><pre
>
101 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
102 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
104 </pre
></blockquote
></p
>
106 <p
>Yesterday I used it to figure out which packages support the STL
3D
109 <p
><blockquote
><pre
>
110 % appstreamcli what-provides mimetype application/sla|grep Package
115 </pre
></blockquote
></p
>
117 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
119 <p
>As usual, if you use Bitcoin and want to show your support of my
120 activities, please send Bitcoin donations to my address
121 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
126 <title>Debian APT upgrade without enough free space on the disk...
</title>
127 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
128 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
129 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
130 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
131 for a while, and when I need to update it there is not enough free
132 space on the disk for apt to do a normal
'apt upgrade
'. I normally
133 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
134 upgrade only some of the packages in one batch, until the amount of
135 packages to download fall below the amount of free space available.
136 Today, I had about
500 packages to upgrade, and after a while I got
137 tired of trying to install chunks of packages manually. I concluded
138 that I did not have the spare hours required to complete the task, and
139 decided to see if I could automate it. I came up with this small
140 script which I call
'apt-in-chunks
':
</p
>
142 <p
><blockquote
><pre
>
145 # Upgrade packages when the disk is too full to upgrade every
146 # upgradable package in one lump. Fetching packages to upgrade using
147 # apt, and then installing using dpkg, to avoid changing the package
148 # flag for manual/automatic.
153 if [
"$
1" ]; then
154 grep -v
"$
1"
160 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
161 echo
"Upgrading $p
"
163 apt install --download-only -y $p
164 for f in /var/cache/apt/archives/*.deb; do
165 if [ -e
"$f
" ]; then
166 dpkg -i /var/cache/apt/archives/*.deb
171 </pre
></blockquote
></p
>
173 <p
>The script will extract the list of packages to upgrade, try to
174 download the packages needed to upgrade one package, install the
175 downloaded packages using dpkg. The idea is to upgrade packages
176 without changing the APT mark for the package (ie the one recording of
177 the package was manually requested or pulled in as a dependency). To
178 use it, simply run it as root from the command line. If it fail, try
179 'apt install -f
' to clean up the mess and run the script again. This
180 might happen if the new packages conflict with one of the old
181 packages. dpkg is unable to remove, while apt can do this.
</p
>
183 <p
>It take one option, a package to ignore in the list of packages to
184 upgrade. The option to ignore a package is there to be able to skip
185 the packages that are simply too large to unpack. Today this was
186 'ghc
', but I have run into other large packages causing similar
187 problems earlier (like TeX).
</p
>
189 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
190 alternative ways to handle this. The
"unattended-upgrades
191 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
192 each package to upgrade, and then upgrade them in order, smallest set
193 first. It might be a better option than my above mentioned script.
194 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
195 the need for using
"dpkg -i
" in the script above.
</p
>
197 <p
>As usual, if you use Bitcoin and want to show your support of my
198 activities, please send Bitcoin donations to my address
199 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
204 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
205 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
207 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
208 <description><p
>A new version of the
209 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
210 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
211 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
212 useful. It was uploaded the last few days, and the last update will
213 enter testing tomorrow. See the
214 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
215 notes
</a
> for the list of bug fixes and new features. Version
3.2
216 was announced
6 days ago. We will try to get it into Debian as
219 <p
>More information related to
3D printing is available on the
220 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
221 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
224 <p
>As usual, if you use Bitcoin and want to show your support of my
225 activities, please send Bitcoin donations to my address
226 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
231 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
232 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
233 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
234 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
235 <description><p
>After several months of working and waiting, I am happy to report
236 that the nice and user friendly
3D printer slicer software Cura just
237 entered Debian Unstable. It consist of five packages,
238 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
239 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
240 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
241 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
242 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
243 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
244 two, uranium and cura, entered Unstable yesterday. This should make
245 it easier for Debian users to print on at least the Ultimaker class of
246 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
247 make life easier for at least me. :)
</p
>
249 <p
>The work to make this happen was done by Gregor Riepl, and I was
250 happy to assist him in sponsoring the packages. With the introduction
251 of Cura, Debian is up to three
3D printer slicers at your service,
252 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
253 printer, give it a go. :)
</p
>
255 <p
>The
3D printer software is maintained by the
3D printer Debian
256 team, flocking together on the
257 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
259 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
260 IRC channel.
</p
>
262 <p
>The next step for Cura in Debian is to update the cura package to
263 version
3.0.3 and then update the entire set of packages to version
264 3.1.0 which showed up the last few days.
</p
>
269 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
270 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
271 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
272 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
273 <description><p
>At my nearby maker space,
274 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
275 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
276 on Windows and MacOS X than Linux, because the software involved had
277 to be manually compiled and set up on Linux while premade packages
278 worked out of the box on Windows and MacOS X. I found this annoying,
279 as the software involved,
280 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
281 and should be trivial to get up and running on Linux if someone took
282 the time to package it for the relevant distributions. I even found
283 <a href=
"https://bugs.debian.org/
706656">a request for adding into
284 Debian
</a
> from
2013, which had seem some activity over the years but
285 never resulted in the software showing up in Debian. So a few days
286 ago I offered my help to try to improve the situation.
</p
>
288 <p
>Now I am very happy to see that all the packages required by a
289 working Cura in Debian are uploaded into Debian and waiting in the NEW
290 queue for the ftpmasters to have a look. You can track the progress
292 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
293 status page for the
3D printer team
</a
>.
</p
>
295 <p
>The uploaded packages are a bit behind upstream, and was uploaded
296 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
297 queue
</a
> while we work up updating the packages to the latest
298 upstream version.
</p
>
300 <p
>On a related note, two competitors for Cura, which I found harder
301 to use and was unable to configure correctly for Ultimaker
2+ in the
302 short time I spent on it, are already in Debian. If you are looking
303 for
3D printer
"slicers
" and want something already available in
305 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
306 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
307 The latter is a fork of the former.
</p
>
309 <p
>As usual, if you use Bitcoin and want to show your support of my
310 activities, please send Bitcoin donations to my address
311 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
316 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
317 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
318 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
319 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
320 <description><p
>Every mobile phone announce its existence over radio to the nearby
321 mobile cell towers. And this radio chatter is available for anyone
322 with a radio receiver capable of receiving them. Details about the
323 mobile phones with very good accuracy is of course collected by the
324 phone companies, but this is not the topic of this blog post. The
325 mobile phone radio chatter make it possible to figure out when a cell
326 phone is nearby, as it include the SIM card ID (IMSI). By paying
327 attention over time, one can see when a phone arrive and when it leave
328 an area. I believe it would be nice to make this information more
329 available to the general public, to make more people aware of how
330 their phones are announcing their whereabouts to anyone that care to
333 <p
>I am very happy to report that we managed to get something
334 visualizing this information up and running for
335 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
336 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
337 library. The solution is based on the
338 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
339 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
340 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
341 Sone from the Computer Science department of the University of
342 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
343 IMSIs) as dots in a web browser graph, with lines to the dot
344 representing mobile base station it is talking to. It was working in
345 the lab yesterday, and was moved into place this morning.
</p
>
347 <p
>We set up a fairly powerful desktop machine using Debian
348 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
349 connected and visualize the visible cell phone towers using an
350 <a href=
"https://github.com/marlow925/hopglass
">English version of
351 Hopglass
</a
>. A fairly powerfull machine is needed as the
352 grgsm_livemon_headless processes from
353 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
354 the radio signal to data packages is quite CPU intensive.
</p
>
356 <p
>The frequencies to listen to, are identified using a slightly
357 patched scan-and-livemon (to set the --args values for each receiver),
358 and the Hopglass data is generated using the
359 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
360 in my meshviewer-output branch
</a
>. For some reason we could not get
361 more than four SDRs working. There is also a geographical map trying
362 to show the location of the base stations, but I believe their
363 coordinates are hardcoded to some random location in Germany, I
364 believe. The code should be replaced with code to look up location in
365 a text file, a sqlite database or one of the online databases
367 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
368 issue for the topic
</a
>.
370 <p
>If this sound interesting, visit the stand at the festival!
</p
>
375 <title>Easier recipe to observe the cell phones around you
</title>
376 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
377 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
378 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
379 <description><p
>A little more than a month ago I wrote
380 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
381 to observe the SIM card ID (aka IMSI number) of mobile phones talking
382 to nearby mobile phone base stations using Debian GNU/Linux and a
383 cheap USB software defined radio
</a
>, and thus being able to pinpoint
384 the location of people and equipment (like cars and trains) with an
385 accuracy of a few kilometer. Since then we have worked to make the
386 procedure even simpler, and it is now possible to do this without any
387 manual frequency tuning and without building your own packages.
</p
>
389 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
390 package is now included in Debian testing and unstable, and the
391 IMSI-catcher code no longer require root access to fetch and decode
392 the GSM data collected using gr-gsm.
</p
>
394 <p
>Here is an updated recipe, using packages built by Debian and a git
395 clone of two python scripts:
</p
>
399 <li
>Start with a Debian machine running the Buster version (aka
402 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
403 python-scapy
</tt
>' as root to install required packages.
</li
>
405 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
406 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
408 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
410 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
411 scan-and-livemon
</tt
>' to locate the frequency of nearby base
412 stations and start listening for GSM packages on one of them.
</li
>
414 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
415 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
419 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
420 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
421 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
422 work with RTL
8232 and other similar USB radio receivers you can get
424 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
425 from ebay
</a
>), so for now the solution is to scan using the RTL radio
426 and only use HackRF for fetching GSM data.
</p
>
428 <p
>As far as I can tell, a cell phone only show up on one of the
429 frequencies at the time, so if you are going to track and count every
430 cell phone around you, you need to listen to all the frequencies used.
431 To listen to several frequencies, use the --numrecv argument to
432 scan-and-livemon to use several receivers. Further, I am not sure if
433 phones using
3G or
4G will show as talking GSM to base stations, so
434 this approach might not see all phones around you. I typically see
435 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
437 <p
>I
've tried to run the scanner on a
438 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
439 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
440 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
441 stdout, I am told there it is caused by a buffer overflow between the
442 radio and GNU Radio, caused by the program being unable to read the
443 GSM data fast enough. If you see a stream of
'O
's from the terminal
444 where you started scan-and-livemon, you need a give the process more
445 CPU power. Perhaps someone are able to optimize the code to a point
446 where it become possible to set up RPi3 based GSM sniffers? I tried
447 using Raspbian instead of Debian, but there seem to be something wrong
448 with GNU Radio on raspbian, causing glibc to abort().
</p
>
453 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
454 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
455 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
456 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
457 <description><p
>On friday, I came across an interesting article in the Norwegian
458 web based ICT news magazine digi.no on
459 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
460 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
461 DVB-T software defined radios. The article refered to instructions
462 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
463 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
465 <p
>The instructions said to use Ubuntu, install pip using apt (to
466 bypass apt), use pip to install pybombs (to bypass both apt and pip),
467 and the ask pybombs to fetch and build everything you need from
468 scratch. I wanted to see if I could do the same on the most recent
469 Debian packages, but this did not work because pybombs tried to build
470 stuff that no longer build with the most recent openssl library or
471 some other version skew problem. While trying to get this recipe
472 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
473 and the only piece of software dependency missing in Debian was the
474 gr-gsm package. I also found out that the lead upstream developer of
475 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
476 Debian packages provided in an Ubuntu PPA repository. All I needed to
477 do was to dget the Debian source package and built it.
</p
>
479 <p
>The IMSI collector is a python script listening for packages on the
480 loopback network device and printing to the terminal some specific GSM
481 packages with IMSI numbers in them. The code is fairly short and easy
482 to understand. The reason this work is because gr-gsm include a tool
483 to read GSM data from a software defined radio like a DVB-T USB stick
484 and other software defined radios, decode them and inject them into a
485 network device on your Linux machine (using the loopback device by
486 default). This proved to work just fine, and I
've been testing the
487 collector for a few days now.
</p
>
489 <p
>The updated and simpler recipe is thus to
</p
>
493 <li
>start with a Debian machine running Stretch or newer,
</li
>
495 <li
>build and install the gr-gsm package available from
496 <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
>
498 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
500 <li
>run grgsm_livemon and adjust the frequency until the terminal
501 where it was started is filled with a stream of text (meaning you
502 found a GSM station).
</li
>
504 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
508 <p
>To make it even easier in the future to get this sniffer up and
509 running, I decided to package
510 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
511 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
512 #
871055</a
>), and the package was uploaded into the NEW queue today.
513 Luckily the gnuradio maintainer has promised to help me, as I do not
514 know much about gnuradio stuff yet.
</p
>
516 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
517 commercial tools like
518 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
519 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
520 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
521 Stingray
</a
>, but I hope the existance of cheap alternatives can make
522 more people realise how their whereabouts when carrying a cell phone
523 is easily tracked. Seeing the data flow on the screen, realizing that
524 I live close to a police station and knowing that the police is also
525 wearing cell phones, I wonder how hard it would be for criminals to
526 track the position of the police officers to discover when there are
527 police near by, or for foreign military forces to track the location
528 of the Norwegian military forces, or for anyone to track the location
529 of government officials...
</p
>
531 <p
>It is worth noting that the data reported by the IMSI-catcher
532 script mentioned above is only a fraction of the data broadcasted on
533 the GSM network. It will only collect one frequency at the time,
534 while a typical phone will be using several frequencies, and not all
535 phones will be using the frequencies tracked by the grgsm_livemod
536 program. Also, there is a lot of radio chatter being ignored by the
537 simple_IMSI-catcher script, which would be collected by extending the
538 parser code. I wonder if gr-gsm can be set up to listen to more than
539 one frequency?
</p
>
544 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
545 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
546 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
547 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
548 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
550 <p
>I finally received a copy of the Norwegian Bokmål edition of
551 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
552 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
553 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
554 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
555 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
556 price. The book is also available for download in electronic form as
557 PDF, EPUB and Mobipocket, as can be
558 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
559 as a web page
</a
>.
</p
>
561 <p
>This is the second book I publish (the first was the book
562 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
564 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
565 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
567 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
568 Bokmål
</a
>), and I am very excited to finally wrap up this
570 "<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
571 for Debian-administratoren
</a
>" will be well received.
</p
>
576 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
577 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
578 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
579 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
580 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
581 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
582 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
583 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
584 på om den fri oversetterløsningen
585 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
586 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
588 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
591 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
592 rolle og muligheter til å håndtere internasjonale utfordringer, som
593 for eksempel flykningekrisen.
</p
>
595 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
598 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
599 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
604 <p
>Dette oversetter Apertium slik:
</p
>
607 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
608 andre aktørar og høve til å handtera internasjonale utfordringar, som
609 til dømes *flykningekrisen.
</p
>
611 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
615 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
616 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
621 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
622 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
623 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
624 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
625 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
626 det er kanskje flisespikking. Det understreker vel bare at det alltid
627 trengs korrekturlesning etter automatisk oversettelse.
</p
>
632 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
633 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
635 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
636 <description><p
>Over the years, administrating thousand of NFS mounting linux
637 computers at the time, I often needed a way to detect if the machine
638 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
639 file or directory affected by the hang, the process (and possibly the
640 shell) will hang too. So you want to be able to detect this without
641 risking the detection process getting stuck too. It has not been
642 obvious how to do this. When the hang has lasted a while, it is
643 possible to find messages like these in dmesg:
</p
>
645 <p
><blockquote
>
646 nfs: server nfsserver not responding, still trying
647 <br
>nfs: server nfsserver OK
648 </blockquote
></p
>
650 <p
>It is hard to know if the hang is still going on, and it is hard to
651 be sure looking in dmesg is going to work. If there are lots of other
652 messages in dmesg the lines might have rotated out of site before they
653 are noticed.
</p
>
655 <p
>While reading through the nfs client implementation in linux kernel
656 code, I came across some statistics that seem to give a way to detect
657 it. The om_timeouts sunrpc value in the kernel will increase every
658 time the above log entry is inserted into dmesg. And after digging a
659 bit further, I discovered that this value show up in
660 /proc/self/mountstats on Linux.
</p
>
662 <p
>The mountstats content seem to be shared between files using the
663 same file system context, so it is enough to check one of the
664 mountstats files to get the state of the mount point for the machine.
665 I assume this will not show lazy umounted NFS points, nor NFS mount
666 points in a different process context (ie with a different filesystem
667 view), but that does not worry me.
</p
>
669 <p
>The content for a NFS mount point look similar to this:
</p
>
671 <p
><blockquote
><pre
>
673 device /dev/mapper/Debian-var mounted on /var with fstype ext3
674 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
675 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
677 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
678 sec: flavor=
1,pseudoflavor=
1
679 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
680 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
681 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
682 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
684 NULL:
0 0 0 0 0 0 0 0
685 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
686 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
687 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
688 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
689 READLINK:
125 125 0 20472 18620 0 1112 1118
690 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
691 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
692 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
693 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
694 SYMLINK:
903 903 0 233428 245488 6 5865 5917
695 MKNOD:
80 80 0 20148 21760 0 299 304
696 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
697 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
698 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
699 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
700 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
701 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
702 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
703 FSINFO:
2 2 0 232 328 0 1 1
704 PATHCONF:
1 1 0 116 140 0 0 0
705 COMMIT:
0 0 0 0 0 0 0 0
707 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
709 </pre
></blockquote
></p
>
711 <p
>The key number to look at is the third number in the per-op list.
712 It is the number of NFS timeouts experiences per file system
713 operation. Here
22 write timeouts and
5 access timeouts. If these
714 numbers are increasing, I believe the machine is experiencing NFS
715 hang. Unfortunately the timeout value do not start to increase right
716 away. The NFS operations need to time out first, and this can take a
717 while. The exact timeout value depend on the setup. For example the
718 defaults for TCP and UDP mount points are quite different, and the
719 timeout value is affected by the soft, hard, timeo and retrans NFS
720 mount options.
</p
>
722 <p
>The only way I have been able to get working on Debian and RedHat
723 Enterprise Linux for getting the timeout count is to peek in /proc/.
725 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
726 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
727 command can be used to get these timeout values. But this do not work
728 on Linux, as far as I can tell. I
729 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
730 but have not seen any replies yet.
</p
>
732 <p
>Is there a better way to figure out if a Linux NFS client is
733 experiencing NFS hangs? Is there a way to detect which processes are
734 affected? Is there a way to get the NFS mount going quickly once the
735 network problem causing the NFS hang has been cleared? I would very
736 much welcome some clues, as we regularly run into NFS hangs.
</p
>
741 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
742 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
743 <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>
744 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
745 <description><p
>For almost a year now, we have been working on making a Norwegian
746 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
747 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
748 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
749 we are working on the proof reading to ensure consistent language and
750 use of correct computer science terms. The plan is to make the book
751 available on paper, as well as in electronic form. For that to
752 happen, the proof reading must be completed and all the figures need
753 to be translated. If you want to help out, get in touch.
</p
>
755 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
757 fresh PDF edition
</a
> in A4 format (the final book will have smaller
758 pages) of the book created every morning is available for
759 proofreading. If you find any errors, please
760 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
761 Weblate and correct the error
</a
>. The
762 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
763 of the translation including figures
</a
> is a useful source for those
764 provide Norwegian bokmål screen shots and figures.
</p
>
769 <title>Unlimited randomness with the ChaosKey?
</title>
770 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
771 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
772 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
773 <description><p
>A few days ago I ordered a small batch of
774 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
775 USB dongle for generating entropy created by Bdale Garbee and Keith
776 Packard. Yesterday it arrived, and I am very happy to report that it
777 work great! According to its designers, to get it to work out of the
778 box, you need the Linux kernel version
4.1 or later. I tested on a
779 Debian Stretch machine (kernel version
4.9), and there it worked just
780 fine, increasing the available entropy very quickly. I wrote a small
781 test oneliner to test. It first print the current entropy level,
782 drain /dev/random, and then print the entropy level for five seconds.
783 Here is the situation without the ChaosKey inserted:
</p
>
785 <blockquote
><pre
>
786 % cat /proc/sys/kernel/random/entropy_avail; \
787 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
788 for n in $(seq
1 5); do \
789 cat /proc/sys/kernel/random/entropy_avail; \
795 28 byte kopiert,
0,
000264565 s,
106 kB/s
802 </pre
></blockquote
>
804 <p
>The entropy level increases by
3-
4 every second. In such case any
805 application requiring random bits (like a HTTPS enabled web server)
806 will halt and wait for more entrpy. And here is the situation with
807 the ChaosKey inserted:
</p
>
809 <blockquote
><pre
>
810 % cat /proc/sys/kernel/random/entropy_avail; \
811 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
812 for n in $(seq
1 5); do \
813 cat /proc/sys/kernel/random/entropy_avail; \
819 104 byte kopiert,
0,
000487647 s,
213 kB/s
826 </pre
></blockquote
>
828 <p
>Quite the difference. :) I bought a few more than I need, in case
829 someone want to buy one here in Norway. :)
</p
>
831 <p
>Update: The dongle was presented at Debconf last year. You might
832 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
833 recording illuminating
</a
>. It explains exactly what the source of
834 randomness is, if you are unable to spot it from the schema drawing
835 available from the ChaosKey web site linked at the start of this blog
841 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
842 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
843 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
844 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
845 <description><p
>Did you ever wonder where the web trafic really flow to reach the
846 web servers, and who own the network equipment it is flowing through?
847 It is possible to get a glimpse of this from using traceroute, but it
848 is hard to find all the details. Many years ago, I wrote a system to
849 map the Norwegian Internet (trying to figure out if our plans for a
850 network game service would get low enough latency, and who we needed
851 to talk to about setting up game servers close to the users. Back
852 then I used traceroute output from many locations (I asked my friends
853 to run a script and send me their traceroute output) to create the
854 graph and the map. The output from traceroute typically look like
858 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
859 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
860 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
861 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
862 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
863 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
864 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
865 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
869 </pre
></p
>
871 <p
>This show the DNS names and IP addresses of (at least some of the)
872 network equipment involved in getting the data traffic from me to the
873 www.stortinget.no server, and how long it took in milliseconds for a
874 package to reach the equipment and return to me. Three packages are
875 sent, and some times the packages do not follow the same path. This
876 is shown for hop
5, where three different IP addresses replied to the
877 traceroute request.
</p
>
879 <p
>There are many ways to measure trace routes. Other good traceroute
880 implementations I use are traceroute (using ICMP packages) mtr (can do
881 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
882 traceroute and a lot of other capabilities). All of them are easily
883 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
885 <p
>This time around, I wanted to know the geographic location of
886 different route points, to visualize how visiting a web page spread
887 information about the visit to a lot of servers around the globe. The
888 background is that a web site today often will ask the browser to get
889 from many servers the parts (for example HTML, JSON, fonts,
890 JavaScript, CSS, video) required to display the content. This will
891 leak information about the visit to those controlling these servers
892 and anyone able to peek at the data traffic passing by (like your ISP,
893 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
895 <p
>Lets pick an example, the Norwegian parliament web site
896 www.stortinget.no. It is read daily by all members of parliament and
897 their staff, as well as political journalists, activits and many other
898 citizens of Norway. A visit to the www.stortinget.no web site will
899 ask your browser to contact
8 other servers: ajax.googleapis.com,
900 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
901 stats.g.doubleclick.net, www.google-analytics.com,
902 www.googletagmanager.com and www.netigate.se. I extracted this by
903 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
904 Stortinget web page and tell me all the URLs PhantomJS downloaded to
905 render the page (in HAR format using
906 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
907 netsniff example
</a
>. I am very grateful to Gorm for showing me how
908 to do this). My goal is to visualize network traces to all IP
909 addresses behind these DNS names, do show where visitors personal
910 information is spread when visiting the page.
</p
>
912 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
913 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
>
915 <p
>When I had a look around for options, I could not find any good
916 free software tools to do this, and decided I needed my own traceroute
917 wrapper outputting KML based on locations looked up using GeoIP. KML
918 is easy to work with and easy to generate, and understood by several
919 of the GIS tools I have available. I got good help from by NUUG
920 colleague Anders Einar with this, and the result can be seen in
921 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
922 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
923 free GeoIP databases I could find (and the for-pay databases my
924 friends had access to) is not up to the task. The IP addresses of
925 central Internet infrastructure would typically be placed near the
926 controlling companies main office, and not where the router is really
927 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
928 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
930 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
931 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
>
933 <p
>I also had a look at the visual traceroute graph created by
934 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
935 showing IP network ownership (aka AS owner) for the IP address in
937 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
938 graph display a lot of useful information about the traceroute in SVG
939 format
</a
>, and give a good indication on who control the network
940 equipment involved, but it do not include geolocation. This graph
941 make it possible to see the information is made available at least for
942 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
943 3 Communications and NetDNA.
</p
>
945 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
946 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
>
948 <p
>In the process, I came across the
949 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
950 Salim Gasmi. Its methology of combining guesses based on DNS names,
951 various location databases and finally use latecy times to rule out
952 candidate locations seemed to do a very good job of guessing correct
953 geolocation. But it could only do one trace at the time, did not have
954 a sensor in Norway and did not make the geolocations easily available
955 for postprocessing. So I contacted the developer and asked if he
956 would be willing to share the code (he refused until he had time to
957 clean it up), but he was interested in providing the geolocations in a
958 machine readable format, and willing to set up a sensor in Norway. So
959 since yesterday, it is possible to run traces from Norway in this
960 service thanks to a sensor node set up by
961 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
962 trace in KML format for further processing.
</p
>
964 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
965 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
>
967 <p
>Here we can see a lot of trafic passes Sweden on its way to
968 Denmark, Germany, Holland and Ireland. Plenty of places where the
969 Snowden confirmations verified the traffic is read by various actors
970 without your best interest as their top priority.
</p
>
972 <p
>Combining KML files is trivial using a text editor, so I could loop
973 over all the hosts behind the urls imported by www.stortinget.no and
974 ask for the KML file from GeoTraceroute, and create a combined KML
975 file with all the traces (unfortunately only one of the IP addresses
976 behind the DNS name is traced this time. To get them all, one would
977 have to request traces using IP number instead of DNS names from
978 GeoTraceroute). That might be the next step in this project.
</p
>
980 <p
>Armed with these tools, I find it a lot easier to figure out where
981 the IP traffic moves and who control the boxes involved in moving it.
982 And every time the link crosses for example the Swedish border, we can
983 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
984 Britain and NSA in USA and cables around the globe. (Hm, what should
985 we tell them? :) Keep that in mind if you ever send anything
986 unencrypted over the Internet.
</p
>
988 <p
>PS: KML files are drawn using
989 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
990 Rublev
<a/
>, as it was less cluttered than the local Linux application
991 Marble. There are heaps of other options too.
</p
>
993 <p
>As usual, if you use Bitcoin and want to show your support of my
994 activities, please send Bitcoin donations to my address
995 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1000 <title>Appstream just learned how to map hardware to packages too!
</title>
1001 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
1002 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
1003 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
1004 <description><p
>I received a very nice Christmas present today. As my regular
1005 readers probably know, I have been working on the
1006 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
1007 system
</a
> for many years. The goal of the Isenkram system is to make
1008 it easier for users to figure out what to install to get a given piece
1009 of hardware to work in Debian, and a key part of this system is a way
1010 to map hardware to packages. Isenkram have its own mapping database,
1011 and also uses data provided by each package using the AppStream
1012 metadata format. And today,
1013 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
1014 Debian learned to look up hardware the same way Isenkram is doing it,
1015 ie using fnmatch():
</p
>
1017 <p
><pre
>
1018 % appstreamcli what-provides modalias \
1019 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1020 Identifier: pymissile [generic]
1022 Summary: Control original Striker USB Missile Launcher
1024 % appstreamcli what-provides modalias usb:v0694p0002d0000
1025 Identifier: libnxt [generic]
1027 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1030 Identifier: t2n [generic]
1032 Summary: Simple command-line tool for Lego NXT
1035 Identifier: python-nxt [generic]
1037 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1040 Identifier: nbc [generic]
1042 Summary: C compiler for LEGO Mindstorms NXT bricks
1045 </pre
></p
>
1047 <p
>A similar query can be done using the combined AppStream and
1048 Isenkram databases using the isenkram-lookup tool:
</p
>
1050 <p
><pre
>
1051 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1053 % isenkram-lookup usb:v0694p0002d0000
1059 </pre
></p
>
1061 <p
>You can find modalias values relevant for your machine using
1062 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
1064 <p
>If you want to make this system a success and help Debian users
1065 make the most of the hardware they have, please
1066 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
1067 AppStream metadata for your package following the guidelines
</a
>
1068 documented in the wiki. So far only
11 packages provide such
1069 information, among the several hundred hardware specific packages in
1070 Debian. The Isenkram database on the other hand contain
101 packages,
1071 mostly related to USB dongles. Most of the packages with hardware
1072 mapping in AppStream are LEGO Mindstorms related, because I have, as
1073 part of my involvement in
1074 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
1075 team
</a
> given priority to making sure LEGO users get proposed the
1076 complete set of packages in Debian for that particular hardware. The
1077 team also got a nice Christmas present today. The
1078 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
1079 package
</a
> made it into Debian. With this package in place, it is
1080 now possible to use the LEGO Mindstorms NXT unit with only free
1081 software, as the nxt-firmware package contain the source and firmware
1082 binaries for the NXT brick.
</p
>
1084 <p
>As usual, if you use Bitcoin and want to show your support of my
1085 activities, please send Bitcoin donations to my address
1086 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1091 <title>Isenkram updated with a lot more hardware-package mappings
</title>
1092 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
1093 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
1094 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
1095 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1096 system
</a
> I wrote two years ago to make it easier in Debian to find
1097 and install packages to get your hardware dongles to work, is still
1098 going strong. It is a system to look up the hardware present on or
1099 connected to the current system, and map the hardware to Debian
1100 packages. It can either be done using the tools in isenkram-cli or
1101 using the user space daemon in the isenkram package. The latter will
1102 notify you, when inserting new hardware, about what packages to
1103 install to get the dongle working. It will even provide a button to
1104 click on to ask packagekit to install the packages.
</p
>
1106 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
1108 <p
><pre
>
1125 </pre
></p
>
1127 <p
>It can also list the firware package providing firmware requested
1128 by the load kernel modules, which in my case is an empty list because
1129 I have all the firmware my machine need:
1131 <p
><pre
>
1132 % /usr/sbin/isenkram-autoinstall-firmware -l
1133 info: did not find any firmware files requested by loaded kernel modules. exiting
1135 </pre
></p
>
1137 <p
>The last few days I had a look at several of the around
250
1138 packages in Debian with udev rules. These seem like good candidates
1139 to install when a given hardware dongle is inserted, and I found
1140 several that should be proposed by isenkram. I have not had time to
1141 check all of them, but am happy to report that now there are
97
1142 packages packages mapped to hardware by Isenkram.
11 of these
1143 packages provide hardware mapping using AppStream, while the rest are
1144 listed in the modaliases file provided in isenkram.
</p
>
1146 <p
>These are the packages with hardware mappings at the moment. The
1147 <strong
>marked packages
</strong
> are also announcing their hardware
1148 support using AppStream, for everyone to use:
</p
>
1150 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
1151 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
1152 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
1153 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
1154 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
1155 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1156 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
1157 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1158 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1159 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1160 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
1161 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1162 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
1163 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1164 pcscd, pidgin-blinklight, printer-driver-splix,
1165 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
1166 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1167 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1168 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1169 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1170 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1171 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1172 xserver-xorg-video-vmware, yubikey-personalization and
1173 zd1211-firmware
</p
>
1175 <p
>If you know of other packages, please let me know with a wishlist
1176 bug report against the isenkram-cli package, and ask the package
1178 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
1179 metadata according to the guidelines
</a
> to provide the information
1180 for everyone. In time, I hope to get rid of the isenkram specific
1181 hardware mapping and depend exclusively on AppStream.
</p
>
1183 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
1184 much hardware, and suggest that the package with with any ethernet
1185 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
1186 the details. I hope the maintainer find time to address it soon. In
1187 the mean time I provide an override in isenkram.
</p
>
1192 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
1193 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
1194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
1195 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
1196 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
1198 <p
>In my early years, I played
1199 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
1200 Elite
</a
> on my PC. I spent many months trading and fighting in
1201 space, and reached the
'elite
' fighting status before I moved on. The
1202 original Elite game was available on Commodore
64 and the IBM PC
1203 edition I played had a
64 KB executable. I am still impressed today
1204 that the authors managed to squeeze both a
3D engine and details about
1205 more than
2000 planet systems across
7 galaxies into a binary so
1208 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
1209 software game Oolite inspired by Elite
</a
> for a while, but did not
1210 really have time to test it properly until a few days ago. It was
1211 great to discover that my old knowledge about trading routes were
1212 still valid. But my fighting and flying abilities were gone, so I had
1213 to retrain to be able to dock on a space station. And I am still not
1214 able to make much resistance when I am attacked by pirates, so I
1215 bougth and mounted the most powerful laser in the rear to be able to
1216 put up at least some resistance while fleeing for my life. :)
</p
>
1218 <p
>When playing Elite in the late eighties, I had to discover
1219 everything on my own, and I had long lists of prices seen on different
1220 planets to be able to decide where to trade what. This time I had the
1222 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
1223 where information about each planet is easily available with common
1224 price ranges and suggested trading routes. This improved my ability
1225 to earn money and I have been able to earn enough to buy a lot of
1226 useful equipent in a few days. I believe I originally played for
1227 months before I could get a docking computer, while now I could get it
1228 after less then a week.
</p
>
1230 <p
>If you like science fiction and dreamed of a life as a vagabond in
1231 space, you should try out Oolite. It is available for Linux, MacOSX
1232 and Windows, and is included in Debian and derivatives since
2011.
</p
>
1234 <p
>As usual, if you use Bitcoin and want to show your support of my
1235 activities, please send Bitcoin donations to my address
1236 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1241 <title>Quicker Debian installations using eatmydata
</title>
1242 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
1243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
1244 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
1245 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
1246 installation system, observing how using
1247 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
1248 could speed up the installation
</a
> quite a bit. My testing measured
1249 speedup around
20-
40 percent for Debian Edu, where we install around
1250 1000 packages from within the installer. The eatmydata package
1251 provide a way to disable/delay file system flushing. This is a bit
1252 risky in the general case, as files that should be stored on disk will
1253 stay only in memory a bit longer than expected, causing problems if a
1254 machine crashes at an inconvenient time. But for an installation, if
1255 the machine crashes during installation the process is normally
1256 restarted, and avoiding disk operations as much as possible to speed
1257 up the process make perfect sense.
1259 <p
>I added code in the Debian Edu specific installation code to enable
1260 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
1261 but did not have time to push it any further. But a few months ago I
1262 picked it up again and worked with the libeatmydata package maintainer
1263 Mattia Rizzolo to make it easier for everyone to get this installation
1264 speedup in Debian. Thanks to our cooperation There is now an
1265 eatmydata-udeb package in Debian testing and unstable, and simply
1266 enabling/installing it in debian-installer (d-i) is enough to get the
1267 quicker installations. It can be enabled using preseeding. The
1268 following untested kernel argument should do the trick:
</p
>
1270 <blockquote
><pre
>
1271 preseed/early_command=
"anna-install eatmydata-udeb
"
1272 </pre
></blockquote
>
1274 <p
>This should ask d-i to install the package inside the d-i
1275 environment early in the installation sequence. Having it installed
1276 in d-i in turn will make sure the relevant scripts are called just
1277 after debootstrap filled /target/ with the freshly installed Debian
1278 system to configure apt to run dpkg with eatmydata. This is enough to
1279 speed up the installation process. There is a proposal to
1280 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1281 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1282 tested its impact.
</p
>
1288 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1289 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1290 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1291 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1292 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1293 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1294 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1295 elever over det ganske land skal levere inn hvert år. Det mange ikke
1296 vet er at selv om de kommersielle alternativene
1297 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1298 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1299 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1300 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1301 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1302 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1303 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1304 nynorsk, og få den automatoversatt til det andre skriftspråket.
1305 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1306 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1307 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1308 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1309 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1310 teksten din i webskjemaet der.
1312 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1313 teknologien kan du enten installere pakken
1314 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1315 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1316 api.apertium.org. Se
1317 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1318 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1319 denne teksten som ble skrevet på bokmål over maskinoversatt til
1324 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1325 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1326 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1327 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1328 veit er at sjølv om dei kommersielle alternativa
1329 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1330 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1331 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1332 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1333 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1334 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1335 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1336 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1337 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1338 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1339 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1340 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1341 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1342 teksta di i *webskjemaet der.
1344 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1345 teknologien kan du anten installera pakken
1346 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1347 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1348 *api.*apertium.org. Sjå
1349 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1350 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1351 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1357 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1358 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1360 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1361 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1362 profiler able to run benchmarking experiments on the instrumented
1363 multi-threaded program, finally
1364 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1365 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1367 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1368 blogged about the coz tool
</a
> in August working with upstream to make
1369 it suitable for Debian. There are still issues with clang
1370 compatibility, inline assembly only working x86 and minimized
1371 JavaScript libraries.
</p
>
1373 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1375 <p
><blockquote
>
1376 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1377 </blockquote
></p
>
1379 <p
>This will produce a profile.coz file in the current working
1380 directory with the profiling information. This is then given to a
1381 JavaScript application provided in the package and available from
1382 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1383 To start the local copy, invoke it in a browser like this:
</p
>
1385 <p
><blockquote
>
1386 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1387 </blockquote
></p
>
1389 <p
>See the project home page and the
1390 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1391 ;login: article on Coz
</a
> for more information on how it is
1397 <title>My own self balancing Lego Segway
</title>
1398 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1399 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1400 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1401 <description><p
>A while back I received a Gyro sensor for the NXT
1402 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1403 present. It had been on my wishlist for a while, because I wanted to
1404 build a Segway like balancing lego robot. I had already built
1405 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1406 robot
</a
> with the kids, using the light/color sensor included in the
1407 NXT kit as the balance sensor, but it was not working very well. It
1408 could balance for a while, but was very sensitive to the light
1409 condition in the room and the reflective properties of the surface and
1410 would fall over after a short while. I wanted something more robust,
1412 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1413 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1414 wishlist for some years before it suddenly showed up as a gift from my
1415 loved ones. :)
</p
>
1417 <p
>Unfortunately I have not had time to sit down and play with it
1418 since then. But that changed some days ago, when I was searching for
1419 lego segway information and came across a recipe from HiTechnic for
1421 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1422 HTWay
</a
>, a segway like balancing robot. Build instructions and
1423 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1424 code
</a
> was included, so it was just a question of putting it all
1425 together. And thanks to the great work of many Debian developers, the
1426 compiler needed to build the source for the NXT is already included in
1427 Debian, so I was read to go in less than an hour. The resulting robot
1428 do not look very impressive in its simplicity:
</p
>
1430 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1432 <p
>Because I lack the infrared sensor used to control the robot in the
1433 design from HiTechnic, I had to comment out the last task
1434 (taskControl). I simply placed /* and */ around it get the program
1435 working without that sensor present. Now it balances just fine until
1436 the battery status run low:
</p
>
1438 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1439 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1440 </video
></p
>
1442 <p
>Now we would like to teach it how to follow a line and take remote
1443 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1445 <p
>If you, like me, love LEGO and want to make sure we find the tools
1446 they need to work with LEGO in Debian and all our derivative
1447 distributions like Ubuntu, check out
1448 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1449 project page
</a
> and join the Debian LEGO team. Personally I own a
1450 RCX and NXT controller (no EV3), and would like to make sure the
1451 Debian tools needed to program the systems I own work as they
1457 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1458 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1459 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1460 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1461 <description><p
>In July
1462 <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
1463 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1464 the ability to receive SMS messages (aka without a cell phone). It is
1465 time to share some experiences and provide an updated setup.
</p
>
1467 <p
>The Signal app have worked fine for several months now, and I use
1468 it regularly to chat with my loved ones. I had a major snag at the
1469 end of my summer vacation, when the the app completely forgot my
1470 setup, identity and keys. The reason behind this major mess was
1471 running out of disk space. To avoid that ever happening again I have
1472 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1473 roll back to an earlier version if the files are wiped by mistake. I
1474 had to use it once after introducing the git backup. When rolling
1475 back to an earlier version, one need to use the
'reset session
' option
1476 in Signal to get going, and notify the people you talk with about the
1477 problem. I assume there is some sequence number tracking in the
1478 protocol to detect rollback attacks. The git repository is rather big
1479 (
674 MiB so far), but I have not tried to figure out if some of the
1480 content can be added to a .gitignore file due to lack of spare
1483 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1484 make it impossible to send messages using Signal. I could still
1485 receive them, but had to patch the code with a new timestamp to send.
1486 I believe the timeout is added by the developers to force people to
1487 upgrade to the latest version of the app, even when there is no
1488 protocol changes, to reduce the version skew among the user base and
1489 thus try to keep the number of support requests down.
</p
>
1491 <p
>Since my original recipe, the Signal source code changed slightly,
1492 making the old patch fail to apply cleanly. Below is an updated
1493 patch, including the shell wrapper I use to start Signal. The
1494 original version required a new user to locate the JavaScript console
1495 and call a function from there. I got help from a friend with more
1496 JavaScript knowledge than me to modify the code to provide a GUI
1497 button instead. This mean that to get started you just need to run
1498 the wrapper and click the
'Register without mobile phone
' to get going
1499 now. I
've also modified the timeout code to always set it to
90 days
1500 in the future, to avoid having to patch the code regularly.
</p
>
1502 <p
>So, the updated recipe for Debian Jessie:
</p
>
1506 <li
>First, install required packages to get the source code and the
1507 browser you need. Signal only work with Chrome/Chromium, as far as I
1508 know, so you need to install it.
1511 apt install git tor chromium
1512 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1513 </pre
></li
>
1515 <li
>Modify the source code using command listed in the the patch
1516 block below.
</li
>
1518 <li
>Start Signal using the run-signal-app wrapper (for example using
1519 <tt
>`pwd`/run-signal-app
</tt
>).
1521 <li
>Click on the
'Register without mobile phone
', will in a phone
1522 number you can receive calls to the next minute, receive the
1523 verification code and enter it into the form field and press
1524 'Register
'. Note, the phone number you use will be user Signal
1525 username, ie the way others can find you on Signal.
</li
>
1527 <li
>You can now use Signal to contact others. Note, new contacts do
1528 not show up in the contact list until you restart Signal, and there is
1529 no way to assign names to Contacts. There is also no way to create or
1530 update chat groups. I suspect this is because the web app do not have
1531 a associated contact database.
</li
>
1535 <p
>I am still a bit uneasy about using Signal, because of the way its
1536 main author moxie0 reject federation and accept dependencies to major
1537 corporations like Google (part of the code is fetched from Google) and
1538 Amazon (the central coordination point is owned by Amazon). See for
1540 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1541 LibreSignal issue tracker
</a
> for a thread documenting the authors
1542 view on these issues. But the network effect is strong in this case,
1543 and several of the people I want to communicate with already use
1544 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1545 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1546 laptop
</a
>? It already work on Windows and Android, and is included
1547 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1548 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1549 working on Debian Stable.
</p
>
1551 <p
>Anyway, this is the patch I apply to the Signal code to get it
1552 working. It switch to the production servers, disable to timeout,
1553 make registration easier and add the shell wrapper:
</p
>
1556 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1557 diff --git a/js/background.js b/js/background.js
1558 index
24b4c1d.
.579345f
100644
1559 --- a/js/background.js
1560 +++ b/js/background.js
1565 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1566 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1567 var SERVER_PORTS = [
80,
4433,
8443];
1568 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1569 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1570 var messageReceiver;
1571 window.getSocketStatus = function() {
1572 if (messageReceiver) {
1573 diff --git a/js/expire.js b/js/expire.js
1574 index
639aeae..beb91c3
100644
1579 'use strict
';
1580 - var BUILD_EXPIRATION =
0;
1581 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1583 window.extension = window.extension || {};
1585 diff --git a/js/views/install_view.js b/js/views/install_view.js
1586 index
7816f4f.
.1d6233b
100644
1587 --- a/js/views/install_view.js
1588 +++ b/js/views/install_view.js
1591 'click .step1
': this.selectStep.bind(this,
1),
1592 'click .step2
': this.selectStep.bind(this,
2),
1593 -
'click .step3
': this.selectStep.bind(this,
3)
1594 +
'click .step3
': this.selectStep.bind(this,
3),
1595 +
'click .callreg
': function() { extension.install(
'standalone
') },
1598 clearQR: function() {
1599 diff --git a/options.html b/options.html
1600 index dc0f28e.
.8d709f6
100644
1604 &lt;div class=
'nav
'>
1605 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1606 &lt;p
>{{ installTagline }}
&lt;/p
>
1607 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1608 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1609 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1612 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1613 &lt;span class=
'dot step2
'>&lt;/span
>
1614 &lt;span class=
'dot step3
'>&lt;/span
>
1615 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1616 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1622 +userdata=
"`pwd`/userdata
"
1623 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1624 + (cd $userdata
&& git init)
1626 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1628 + --proxy-server=
"socks://localhost:
9050" \
1629 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1631 chmod a+rx run-signal-app
1634 <p
>As usual, if you use Bitcoin and want to show your support of my
1635 activities, please send Bitcoin donations to my address
1636 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1641 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1642 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1643 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1644 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1645 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1646 system
</a
> provide a practical and easy way to figure out which
1647 packages support the hardware in a given machine. The command line
1648 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1649 convenient way to list and install packages relevant for the current
1650 hardware during system installation, both user space packages and
1651 firmware packages. The GUI background daemon on the other hand provide
1652 a pop-up proposing to install packages when a new dongle is inserted
1653 while using the computer. For example, if you plug in a smart card
1654 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1655 that package isn
't already installed, and if you plug in a USB video
1656 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1657 cheese is currently missing. This already work just fine.
</p
>
1659 <p
>But Isenkram depend on a database mapping from hardware IDs to
1660 package names. When I started no such database existed in Debian, so
1661 I made my own data set and included it with the isenkram package and
1662 made isenkram fetch the latest version of this database from git using
1663 http. This way the isenkram users would get updated package proposals
1664 as soon as I learned more about hardware related packages.
</p
>
1666 <p
>The hardware is identified using modalias strings. The modalias
1667 design is from the Linux kernel where most hardware descriptors are
1668 made available as a strings that can be matched using filename style
1669 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1670 identifiers.
</p
>
1672 <p
>The downside to the Isenkram specific database is that there is no
1673 information about relevant distribution / Debian version, making
1674 isenkram propose obsolete packages too. But along came AppStream, a
1675 cross distribution mechanism to store and collect metadata about
1676 software packages. When I heard about the proposal, I contacted the
1677 people involved and suggested to add a hardware matching rule using
1678 modalias strings in the specification, to be able to use AppStream for
1679 mapping hardware to packages. This idea was accepted and AppStream is
1680 now a great way for a package to announce the hardware it support in a
1681 distribution neutral way. I wrote
1682 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1683 recipe on how to add such meta-information
</a
> in a blog post last
1684 December. If you have a hardware related package in Debian, please
1685 announce the relevant hardware IDs using AppStream.
</p
>
1687 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1688 RCX or NXT unit, announce this support using AppStream. The effect is
1689 that when you insert such LEGO robot controller into your Debian
1690 machine, Isenkram will propose to install the packages needed to get
1691 it working. The intention is that this should allow the local user to
1692 start programming his robot controller right away without having to
1693 guess what packages to use or which permissions to fix.
</p
>
1695 <p
>But when I sat down with my son the other day to program our NXT
1696 unit using his Debian Stretch computer, I discovered something
1697 annoying. The local console user (ie my son) did not get access to
1698 the USB device for programming the unit. This used to work, but no
1699 longer in Jessie and Stretch. After some investigation and asking
1700 around on #debian-devel, I discovered that this was because udev had
1701 changed the mechanism used to grant access to local devices. The
1702 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1703 no longer applied, because LDAP users no longer was added to the
1704 plugdev group during login. Michael Biebl told me that this method
1705 was obsolete and the new method used ACLs instead. This was good
1706 news, as the plugdev mechanism is a mess when using a remote user
1707 directory like LDAP. Using ACLs would make sure a user lost device
1708 access when she logged out, even if the user left behind a background
1709 process which would retain the plugdev membership with the ConsoleKit
1710 setup. Armed with this knowledge I moved on to fix the access problem
1711 for the LEGO Mindstorms related packages.
</p
>
1713 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1714 applied directly for a device, or is applied in
1715 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1716 LEGO Mindstorms udev rules did not have a class, I decided to add the
1717 tag directly in the udev rules files included in the packages. Here
1718 is one example. For the nqc C compiler for the RCX, the
1719 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1721 <p
><pre
>
1722 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1723 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1724 </pre
></p
>
1726 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1727 packages using plugdev in their /lib/udev/rules.d/ files should be
1728 changed to use this tag (either directly or indirectly via
1729 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1730 to detect this?
</p
>
1732 <p
>I
've been unable to find good documentation on the uaccess feature.
1733 It is unclear to me if the uaccess tag is an internal implementation
1734 detail like the udev-acl tag used by
1735 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1736 indirect method is the preferred way. Michael
1737 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1738 documentation from the systemd project
</a
> and I hope it will make
1739 this clearer. For now I use the generic classes when they exist and
1740 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1741 directly if no such class exist.
</p
>
1743 <p
>To learn more about the isenkram system, please check out
1744 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1745 blog posts tagged isenkram
</a
>.
</p
>
1747 <p
>To help out making life for LEGO constructors in Debian easier,
1748 please join us on our IRC channel
1749 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1750 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1751 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1752 list is not yet created, but we are working on it. :)
</p
>
1754 <p
>As usual, if you use Bitcoin and want to show your support of my
1755 activities, please send Bitcoin donations to my address
1756 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1761 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1762 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1763 <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>
1764 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1765 <description><p
>In April we
1766 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1767 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1768 how to set up and administrate a Debian system. Today I am happy to
1769 report that the first draft is now publicly available. You can find
1770 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1771 Administrator
's Handbook page
</a
> (under Other languages). The first
1772 eight chapters have a first draft translation, and we are working on
1773 proofreading the content. If you want to help out, please start
1775 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1776 hosted weblate project page
</a
>, and get in touch using
1777 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1778 translators mailing list
</a
>. Please also check out
1779 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1780 contributors
</a
>. A good way to contribute is to proofread the text
1781 and update weblate if you find errors.
</p
>
1783 <p
>Our goal is still to make the Norwegian book available on paper as well as
1784 electronic form.
</p
>
1789 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1790 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1791 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1792 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1793 <description><p
>This summer, I read a great article
1794 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1795 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1796 how to profile multi-threaded programs. It presented a system for
1797 profiling software by running experiences in the running program,
1798 testing how run time performance is affected by
"speeding up
" parts of
1799 the code to various degrees compared to a normal run. It does this by
1800 slowing down parallel threads while the
"faster up
" code is running
1801 and measure how this affect processing time. The processing time is
1802 measured using probes inserted into the code, either using progress
1803 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1804 can also measure unmodified code by measuring complete the program
1805 runtime and running the program several times instead.
</p
>
1807 <p
>The project and presentation was so inspiring that I would like to
1808 get the system into Debian. I
1809 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1810 a WNPP request for it
</a
> and contacted upstream to try to make the
1811 system ready for Debian by sending patches. The build process need to
1812 be changed a bit to avoid running
'git clone
' to get dependencies, and
1813 to include the JavaScript web page used to visualize the collected
1814 profiling information included in the source package.
1815 But I expect that should work out fairly soon.
</p
>
1817 <p
>The way the system work is fairly simple. To run an coz experiment
1818 on a binary with debug symbols available, start the program like this:
1820 <p
><blockquote
><pre
>
1821 coz run --- program-to-run
1822 </pre
></blockquote
></p
>
1824 <p
>This will create a text file profile.coz with the instrumentation
1825 information. To show what part of the code affect the performance
1826 most, use a web browser and either point it to
1827 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1828 or use the copy from git (in the gh-pages branch). Check out this web
1829 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
1830 profiling more useful you include
&lt;coz.h
&gt; and insert the
1831 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1832 code, rebuild and run the profiler. This allow coz to do more
1833 targeted experiments.
</p
>
1835 <p
>A video published by ACM
1836 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1837 Coz profiler
</a
> is available from Youtube. There is also a paper
1838 from the
25th Symposium on Operating Systems Principles available
1840 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1841 finding code that counts with causal profiling
</a
>.
</p
>
1843 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1844 for Coz is available from github. It will only build with clang
1846 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1847 feature missing in GCC
</a
>, but I
've submitted
1848 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1849 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1851 <p
>Please get in touch if you, like me, would like to see this piece
1852 of software in Debian. I would very much like some help with the
1853 packaging effort, as I lack the in depth knowledge on how to package
1854 C++ libraries.
</p
>
1859 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1860 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1861 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1862 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1863 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1864 to be a slight challenge. Here is the recipe if I ever need to do it
1865 again. It all started by me wanting to try the recipe to set up
1866 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1867 hardened Android installation
</a
> from the Tor project blog on a
1868 device I had access to. It is a old mobile phone with a broken
1869 microphone The initial idea had been to just
1870 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1871 CyanogenMod on it
</a
>, but did not quite find time to start on it
1872 until a few days ago.
</p
>
1874 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1875 loader (press volume down and power at the same time), (
2) select
1876 'fastboot
' before (
3) connecting the device via USB to a Linux
1877 machine, (
4) request the device identifier token by running
'fastboot
1878 oem get_identifier_token
', (
5) request the device unlocking key using
1879 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1880 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1882 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1883 or newer, and the device I was working on had
2.00.0027. This
1884 apparently can be easily fixed by downloading a Windows program and
1885 running it on your Windows machine, if you accept the terms Microsoft
1886 require you to accept to use Windows - which I do not. So I had to
1887 come up with a different approach. I got a lot of help from AndyCap
1888 on #nuug, and would not have been able to get this working without
1891 <p
>First I needed to extract the hboot firmware from
1892 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1893 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1894 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1895 project named unruu
</a
> using libunshield. The unshield tool did not
1896 recognise the file format, but unruu worked and extracted rom.zip,
1897 containing the new hboot firmware and a text file describing which
1898 devices it would work for.
</p
>
1900 <p
>Next, I needed to get the new firmware into the device. For this I
1901 followed some instructions
1902 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1903 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1904 machine with Debian testing:
</p
>
1906 <p
><pre
>
1907 adb reboot-bootloader
1908 fastboot oem rebootRUU
1909 fastboot flash zip rom.zip
1910 fastboot flash zip rom.zip
1912 </pre
></p
>
1914 <p
>The flash command apparently need to be done twice to take effect,
1915 as the first is just preparations and the second one do the flashing.
1916 The adb command is just to get to the boot loader menu, so turning the
1917 device on while holding volume down and the power button should work
1920 <p
>With the new hboot version in place I could start following the
1921 instructions on the HTC developer web site. I got the device token
1922 like this:
</p
>
1924 <p
><pre
>
1925 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1928 <p
>And once I got the unlock code via email, I could use it like
1931 <p
><pre
>
1932 fastboot flash unlocktoken Unlock_code.bin
1933 </pre
></p
>
1935 <p
>And with that final step in place, the phone was unlocked and I
1936 could start stuffing the software of my own choosing into the device.
1937 So far I only inserted a replacement recovery image to wipe the phone
1938 before I start. We will see what happen next. Perhaps I should
1939 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1944 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1945 <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>
1946 <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>
1947 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1948 <description><p
>For a while now, I have wanted to test
1949 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1950 said to provide end to end encrypted communication and several of my
1951 friends and family are already using it. As I by choice do not own a
1952 mobile phone, this proved to be harder than expected. And I wanted to
1953 have the source of the client and know that it was the code used on my
1954 machine. But yesterday I managed to get it working. I used the
1955 Github source, compared it to the source in
1956 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1957 Signal Chrome app
</a
> available from the Chrome web store, applied
1958 patches to use the production Signal servers, started the app and
1959 asked for the hidden
"register without a smart phone
" form. Here is
1960 the recipe how I did it.
</p
>
1962 <p
>First, I fetched the Signal desktop source from Github, using
1965 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1968 <p
>Next, I patched the source to use the production servers, to be
1969 able to talk to other Signal users:
</p
>
1972 cat
&lt;
&lt;EOF | patch -p0
1973 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1974 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1975 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1980 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1981 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1982 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1983 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1984 var messageReceiver;
1985 window.getSocketStatus = function() {
1986 if (messageReceiver) {
1987 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1988 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1989 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1992 'use strict
';
1993 - var BUILD_EXPIRATION =
0;
1994 + var BUILD_EXPIRATION =
1474492690000;
1996 window.extension = window.extension || {};
2001 <p
>The first part is changing the servers, and the second is updating
2002 an expiration timestamp. This timestamp need to be updated regularly.
2003 It is set
90 days in the future by the build process (Gruntfile.js).
2004 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
2006 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
2007 script to launch Signal in Chromium.
</p
>
2014 --proxy-server=
"socks://localhost:
9050" \
2015 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2018 <p
> The script start the app and configure Chromium to use the Tor
2019 SOCKS5 proxy to make sure those controlling the Signal servers (today
2020 Amazon and Whisper Systems) as well as those listening on the lines
2021 will have a harder time location my laptop based on the Signal
2022 connections if they use source IP address.
</p
>
2024 <p
>When the script starts, one need to follow the instructions under
2025 "Standalone Registration
" in the CONTRIBUTING.md file in the git
2026 repository. I right clicked on the Signal window to get up the
2027 Chromium debugging tool, visited the
'Console
' tab and wrote
2028 'extension.install(
"standalone
")
' on the console prompt to get the
2029 registration form. Then I entered by land line phone number and
2030 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
2031 repeated the verification code three times. After entering the number
2032 into the verification code field in the form, I could start using
2033 Signal from my laptop.
2035 <p
>As far as I can tell, The Signal app will leak who is talking to
2036 whom and thus who know who to those controlling the central server,
2037 but such leakage is hard to avoid with a centrally controlled server
2038 setup. It is something to keep in mind when using Signal - the
2039 content of your chats are harder to intercept, but the meta data
2040 exposing your contact network is available to people you do not know.
2041 So better than many options, but not great. And sadly the usage is
2042 connected to my land line, thus allowing those controlling the server
2043 to associate it to my home and person. I would prefer it if only
2044 those I knew could tell who I was on Signal. There are options
2045 avoiding such information leakage, but most of my friends are not
2046 using them, so I am stuck with Signal for now.
</p
>
2048 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
2050 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
2051 and updated recipe for using the Signal app without a mobile
2052 phone
</a
>.
</p
>
2057 <title>The new
"best
" multimedia player in Debian?
</title>
2058 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
2059 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
2060 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
2061 <description><p
>When I set out a few weeks ago to figure out
2062 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
2063 multimedia player in Debian claimed to support most file formats /
2064 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
2065 the various players claimed support for. The range was from
55 to
130
2066 MIME types. I suspect most media formats are supported by all
2067 players, but this is not really reflected in the MimeTypes values in
2068 their desktop files. There are probably also some bogus MIME types
2069 listed, but it is hard to identify which one this is.
</p
>
2071 <p
>Anyway, in the mean time I got in touch with upstream for some of
2072 the players suggesting to add more MIME types to their desktop files,
2073 and decided to spend some time myself improving the situation for my
2074 favorite media player VLC. The fixes for VLC entered Debian unstable
2075 yesterday. The complete list of MIME types can be seen on the
2076 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
2077 player MIME type support status
</a
> Debian wiki page.
</p
>
2079 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
2080 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2081 kmplayer. I am sure some of the other players desktop files support
2082 several of the formats currently listed as working only with vlc,
2083 toten and parole.
</p
>
2085 <p
>A sad observation is that only
14 MIME types are listed as
2086 supported by all the tested multimedia players in Debian in their
2087 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2088 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2089 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2090 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2091 it sad that video/ogg and video/webm is not supported by all the media
2092 players in Debian. As far as I can tell, all of them can handle both
2098 <title>A program should be able to open its own files on Linux
</title>
2099 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
2100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
2101 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
2102 <description><p
>Many years ago, when koffice was fresh and with few users, I
2103 decided to test its presentation tool when making the slides for a
2104 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2105 wrote the first draft of the slides, saved the result and went to bed
2106 the day before I would give the talk. The next day I took a plane to
2107 the location where the meeting should take place, and on the plane I
2108 started up koffice again to polish the talk a bit, only to discover
2109 that kpresenter refused to load its own data file. I cursed a bit and
2110 started making the slides again from memory, to have something to
2111 present when I arrived. I tested that the saved files could be
2112 loaded, and the day seemed to be rescued. I continued to polish the
2113 slides until I suddenly discovered that the saved file could no longer
2114 be loaded into kpresenter. In the end I had to rewrite the slides
2115 three times, condensing the content until the talk became shorter and
2116 shorter. After the talk I was able to pinpoint the problem
&ndash;
2117 kpresenter wrote inline images in a way itself could not understand.
2118 Eventually that bug was fixed and kpresenter ended up being a great
2119 program to make slides. The point I
'm trying to make is that we
2120 expect a program to be able to load its own data files, and it is
2121 embarrassing to its developers if it can
't.
</p
>
2123 <p
>Did you ever experience a program failing to load its own data
2124 files from the desktop file browser? It is not a uncommon problem. A
2125 while back I discovered that the screencast recorder
2126 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2127 browser would refuse to open. No video player claimed to understand
2128 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
2129 returning the application/ogg MIME type, which no video player I had
2130 installed listed as a MIME type they would understand. I asked for
2131 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
2132 behavour
</a
> and use the MIME type video/ogg instead. I also asked
2133 several video players to add video/ogg to their desktop files, to give
2134 the file browser an idea what to do about Ogg Theora files. After a
2135 while, the desktop file browsers in Debian started to handle the
2136 output from gtk-recordmydesktop properly.
</p
>
2138 <p
>But history repeats itself. A few days ago I tested the music
2139 system Rosegarden again, and I discovered that the KDE and xfce file
2140 browsers did not know what to do with the Rosegarden project files
2141 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
2142 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
2143 included in the next upload. To increase the chance of me remembering
2144 how to fix the problem next time some program fail to load its files
2145 from the file browser, here are some notes on how to fix it.
</p
>
2147 <p
>The file browsers in Debian in general operates on MIME types.
2148 There are two sources for the MIME type of a given file. The output from
2149 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
2150 shared MIME type registry (under /usr/share/mime/). The file MIME
2151 type is mapped to programs supporting the MIME type, and this
2152 information is collected from
2153 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
2154 desktop files
</a
> available in /usr/share/applications/. If there is
2155 one desktop file claiming support for the MIME type of the file, it is
2156 activated when asking to open a given file. If there are more, one
2157 can normally select which one to use by right-clicking on the file and
2158 selecting the wanted one using
'Open with
' or similar. In general
2159 this work well. But it depend on each program picking a good MIME
2161 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
2162 MIME type registered with IANA
</a
>), file and/or the shared MIME
2163 registry recognizing the file and the desktop file to list the MIME
2164 type in its list of supported MIME types.
</p
>
2166 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
2167 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
2168 Shared MIME database
</a
> look like this:
</p
>
2170 <p
><blockquote
><pre
>
2171 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2172 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
2173 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
2174 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
2175 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
2176 &lt;glob pattern=
"*.rg
"/
&gt;
2177 &lt;/mime-type
&gt;
2178 &lt;/mime-info
&gt;
2179 </pre
></blockquote
></p
>
2181 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
2182 (it is a gzipped XML file). Note, it is much better to use an
2183 official MIME type registered with IANA than it is to make up ones own
2184 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
2186 <p
>The desktop file of the rosegarden program failed to list
2187 audio/x-rosegarden in its list of supported MIME types, causing the
2188 file browsers to have no idea what to do with *.rg files:
</p
>
2190 <p
><blockquote
><pre
>
2191 % grep Mime /usr/share/applications/rosegarden.desktop
2192 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2193 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2195 </pre
></blockquote
></p
>
2197 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
2198 MimeType= line.
</p
>
2200 <p
>If you run into a file which fail to open the correct program when
2201 selected from the file browser, please check out the output from
2202 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
2203 MIME type is registered somewhere under /usr/share/mime/ and check
2204 that some desktop file under /usr/share/applications/ is claiming
2205 support for this MIME type. If not, please report a bug to have it
2211 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
2212 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
2213 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
2214 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
2215 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
2216 system
</a
> is a user-focused solution in Debian for handling hardware
2217 related packages. The idea is to have a database of mappings between
2218 hardware and packages, and pop up a dialog suggesting for the user to
2219 install the packages to use a given hardware dongle. Some use cases
2220 are when you insert a Yubikey, it proposes to install the software
2221 needed to control it; when you insert a braille reader list it
2222 proposes to install the packages needed to send text to the reader;
2223 and when you insert a ColorHug screen calibrator it suggests to
2224 install the driver for it. The system work well, and even have a few
2225 command line tools to install firmware packages and packages for the
2226 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
2228 <p
>The system was initially written using aptdaemon, because I found
2229 good documentation and example code on how to use it. But aptdaemon
2230 is going away and is generally being replaced by
2231 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
2232 so Isenkram needed a rewrite. And today, thanks to the great patch
2233 from my college Sunil Mohan Adapa in the FreedomBox project, the
2234 rewrite finally took place. I
've just uploaded a new version of
2235 Isenkram into Debian Unstable with the patch included, and the default
2236 for the background daemon is now to use PackageKit. To check it out,
2237 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
2238 and see if it is recognised.
</p
>
2240 <p
>If you want to know what kind of packages isenkram would propose for
2241 the machine it is running on, you can check out the isenkram-lookup
2242 program. This is what it look like on a Thinkpad X230:
</p
>
2244 <p
><blockquote
><pre
>
2260 </pre
></blockquote
></p
>
2262 <p
>The hardware mappings come from several places. The preferred way
2263 is for packages to announce their hardware support using
2264 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2265 cross distribution appstream system
</a
>.
2267 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2268 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2273 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2274 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2275 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2276 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2277 <description><p
>Yesterday I updated the
2278 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2279 package in Debian
</a
> with a few patches sent to me by skilled and
2280 enterprising users. There were some nice user and visible changes.
2281 First of all, both desktop menu entries now work. A design flaw in
2282 one of the script made the history graph fail to show up (its PNG was
2283 dumped in ~/.xsession-errors) if no controlling TTY was available.
2284 The script worked when called from the command line, but not when
2285 called from the desktop menu. I changed this to look for a DISPLAY
2286 variable or a TTY before deciding where to draw the graph, and now the
2287 graph window pop up as expected.
</p
>
2289 <p
>The next new feature is a discharge rate estimator in one of the
2290 graphs (the one showing the last few hours). New is also the user of
2291 colours showing charging in blue and discharge in red. The percentages
2292 of this graph is relative to last full charge, not battery design
2295 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2297 <p
>The other graph show the entire history of the collected battery
2298 statistics, comparing it to the design capacity of the battery to
2299 visualise how the battery life time get shorter over time. The red
2300 line in this graph is what the previous graph considers
100 percent:
2302 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2304 <p
>In this graph you can see that I only charge the battery to
80
2305 percent of last full capacity, and how the capacity of the battery is
2306 shrinking. :(
</p
>
2308 <p
>The last new feature is in the collector, which now will handle
2309 more hardware models. On some hardware, Linux power supply
2310 information is stored in /sys/class/power_supply/ACAD/, while the
2311 collector previously only looked in /sys/class/power_supply/AC/. Now
2312 both are checked to figure if there is power connected to the
2315 <p
>If you are interested in how your laptop battery is doing, please
2317 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2318 in Debian unstable, or rebuild it on Jessie to get it working on
2319 Debian stable. :) The upstream source is available from
<a
2320 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2321 Patches are very welcome.
</p
>
2323 <p
>As usual, if you use Bitcoin and want to show your support of my
2324 activities, please send Bitcoin donations to my address
2325 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2330 <title>Debian now with ZFS on Linux included
</title>
2331 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2333 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2334 <description><p
>Today, after many years of hard work from many people,
2335 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2336 Debian. The package status can be seen on
2337 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2338 for zfs-linux
</a
>. and
2339 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2340 team status page
</a
>. If you want to help out, please join us.
2341 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2342 source code
</a
> is available via git on Alioth. It would also be
2343 great if you could help out with
2344 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2345 it is an important piece of the puzzle to get ZFS working.
</p
>
2350 <title>What is the best multimedia player in Debian?
</title>
2351 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2353 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2354 <description><p
><strong
>Where I set out to figure out which multimedia player in
2355 Debian claim support for most file formats.
</strong
></p
>
2357 <p
>A few years ago, I had a look at the media support for Browser
2358 plugins in Debian, to get an idea which plugins to include in Debian
2359 Edu. I created a script to extract the set of supported MIME types
2360 for each plugin, and used this to find out which multimedia browser
2361 plugin supported most file formats / media types.
2362 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2363 result
</a
> can still be seen on the Debian wiki, even though it have
2364 not been updated for a while. But browser plugins are less relevant
2365 these days, so I thought it was time to look at standalone
2368 <p
>A few days ago I was tired of VLC not being listed as a viable
2369 player when I wanted to play videos from the Norwegian National
2370 Broadcasting Company, and decided to investigate why. The cause is a
2371 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2372 desktop file
</a
>. In the process I wrote a script to compare the set
2373 of MIME types announced in the desktop file and the browser plugin,
2374 only to discover that there is quite a large difference between the
2375 two for VLC. This discovery made me dig up the script I used to
2376 compare browser plugins, and adjust it to compare desktop files
2377 instead, to try to figure out which multimedia player in Debian
2378 support most file formats.
</p
>
2380 <p
>The result can be seen on the Debian Wiki, as
2381 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2382 table listing all MIME types supported by one of the packages included
2383 in the table
</a
>, with the package supporting most MIME types being
2384 listed first in the table.
</p
>
2386 </p
>The best multimedia player in Debian? It is totem, followed by
2387 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2388 kmplayer. Time for the other players to update their announced MIME
2394 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2395 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2396 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2397 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2398 <description>A friend of mine made me aware of
2399 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2400 handheld computer which will be delivered with Debian preinstalled. I
2401 would love to get one of those for my birthday. :)
</p
>
2403 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2404 plugs and many others connectors, and include a full keyboard and a
5"
2405 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2406 day of battery life time, but I have not seen any independent tests
2407 confirming this. The vendor is still collecting preorders, and the
2408 last I heard last night was that
22 more orders were needed before
2409 production started.
</p
>
2411 <p
>As far as I know, this is the first handheld preinstalled with
2412 Debian. Please let me know if you know of any others. Is it the
2413 first computer being sold with Debian preinstalled?
</p
>
2418 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2419 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2420 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2421 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2422 <description><p
>During this weekends
2423 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2424 squashing party and developer gathering
</a
>, we decided to do our part
2425 to make sure there are good books about Debian available in Norwegian
2426 Bokmål, and got in touch with the people behind the
2427 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2428 project
</a
> to get started. If you want to help out, please start
2430 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2431 hosted weblate project page
</a
>, and get in touch using
2432 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2433 translators mailing list
</a
>. Please also check out
2434 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2435 contributors
</a
>.
</p
>
2437 <p
>The book is already available on paper in English, French and
2438 Japanese, and our goal is to get it available on paper in Norwegian
2439 Bokmål too. In addition to the paper edition, there are also EPUB and
2440 Mobi versions available. And there are incomplete translations
2441 available for many more languages.
</p
>
2446 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2447 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2448 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2449 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2450 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2451 packages in Debian, and was quite surprised with what I found. I use
2452 ZFS myself at home, but did not really expect many others to do so.
2453 But I might be wrong.
</p
>
2455 <p
>According to
2456 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2457 results for spl-linux
</a
>, there are
1019 Debian installations, or
2458 0.53% of the population, with the package installed. As far as I know
2459 the only use of the spl-linux package is as a support library for ZFS
2460 on Linux, so I use it here as proxy for measuring the number of ZFS
2461 installation on Linux in Debian. In the kFreeBSD variant of Debian
2462 the ZFS feature is already available, and there
2463 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2464 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2465 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2467 <p
>But even though the Debian project leader Lucas Nussbaum
2468 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2469 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2470 cleared, the package is still not in Debian. The package is again in
2471 the NEW queue. Several uploads have been rejected so far because the
2472 debian/copyright file was incomplete or wrong, but there is no reason
2473 to give up. The current status can be seen on
2474 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2475 team status page
</a
>, and
2476 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2477 source code
</a
> is available on Alioth.
</p
>
2479 <p
>As I want ZFS to be included in next version of Debian to make sure
2480 my home server can function in the future using only official Debian
2481 packages, and the current blocker is to get the debian/copyright file
2482 accepted by the FTP masters in Debian, I decided a while back to try
2483 to help out the team. This was the background for my blog post about
2484 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2485 updating and checking debian/copyright semi-automatically
</a
>, and I
2486 used the techniques I explored there to try to find any errors in the
2487 copyright file. It is not very easy to check every one of the around
2488 2000 files in the source package, but I hope we this time got it
2489 right. If you want to help out, check out the git source and try to
2490 find missing entries in the debian/copyright file.
</p
>
2495 <title>Full battery stats collector is now available in Debian
</title>
2496 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2498 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2499 <description><p
>Since this morning, the battery-stats package in Debian include an
2500 extended collector that will collect the complete battery history for
2501 later processing and graphing. The original collector store the
2502 battery level as percentage of last full level, while the new
2503 collector also record battery vendor, model, serial number, design
2504 full level, last full level and current battery level. This make it
2505 possible to predict the lifetime of the battery as well as visualise
2506 the energy flow when the battery is charging or discharging.
</p
>
2508 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2509 in the version
0.5.1 package in unstable. Get the new battery level graph
2510 and lifetime prediction by running:
2512 <p
><pre
>
2513 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2514 </pre
></p
>
2516 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2518 <p
>The flow in/out of the battery can be seen by running (no menu
2519 entry yet):
</p
>
2521 <p
><pre
>
2522 /usr/share/battery-stats/battery-stats-graph-flow
2523 </pre
></p
>
2525 <p
>I
'm not quite happy with the way the data is visualised, at least
2526 when there are few data points. The graphs look a bit better with a
2527 few years of data.
</p
>
2529 <p
>A while back one important feature I use in the battery stats
2530 collector broke in Debian. The scripts in
2531 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2532 suspect it happened when Jessie started using systemd, but I do not
2533 know. The issue is reported as
2534 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2535 pm-utils. I managed to work around it by adding an udev rule to call
2536 the collector script every time the power connector is connected and
2537 disconnected. With this fix in place it was finally time to make a
2538 new release of the package, and get it into Debian.
</p
>
2540 <p
>If you are interested in how your laptop battery is doing, please
2542 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2543 in Debian unstable, or rebuild it on Jessie to get it working on
2544 Debian stable. :) The upstream source is available from
2545 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2546 As always, patches are very welcome.
</p
>
2551 <title>Making battery measurements a little easier in Debian
</title>
2552 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2553 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2554 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2555 <description><p
>Back in September, I blogged about
2556 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2557 system I wrote to collect statistics about my laptop battery
</a
>, and
2558 how it showed the decay and death of this battery (now replaced). I
2559 created a simple deb package to handle the collection and graphing,
2560 but did not want to upload it to Debian as there were already
2561 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2562 package in Debian
</a
> that should do the same thing, and I did not see
2563 a point of uploading a competing package when battery-stats could be
2564 fixed instead. I reported a few bugs about its non-function, and
2565 hoped someone would step in and fix it. But no-one did.
</p
>
2567 <p
>I got tired of waiting a few days ago, and took matters in my own
2568 hands. The end result is that I am now the new upstream developer of
2569 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2570 battery-stats in Debian, and the package in Debian unstable is finally
2571 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2572 information provided by the Linux kernel. If you install the
2573 battery-stats package from unstable now, you will be able to get a
2574 graph of the current battery fill level, to get some idea about the
2575 status of the battery. The source package build and work just fine in
2576 Debian testing and stable (and probably oldstable too, but I have not
2577 tested). The default graph you get for that system look like this:
</p
>
2579 <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
>
2581 <p
>My plans for the future is to merge my old scripts into the
2582 battery-stats package, as my old scripts collected a lot more details
2583 about the battery. The scripts are merged into the upstream
2584 battery-stats git repository already, but I am not convinced they work
2585 yet, as I changed a lot of paths along the way. Will have to test a
2586 bit more before I make a new release.
</p
>
2588 <p
>I will also consider changing the file format slightly, as I
2589 suspect the way I combine several values into one field might make it
2590 impossible to know the type of the value when using it for processing
2591 and graphing.
</p
>
2593 <p
>If you would like I would like to keep an close eye on your laptop
2594 battery, check out the battery-stats package in
2595 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2597 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2598 I would love some help to improve the system further.
</p
>
2603 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2604 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2605 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2606 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2607 <description><p
>Making packages for Debian requires quite a lot of attention to
2608 details. And one of the details is the content of the
2609 debian/copyright file, which should list all relevant licenses used by
2610 the code in the package in question, preferably in
2611 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2612 readable DEP5 format
</a
>.
</p
>
2614 <p
>For large packages with lots of contributors it is hard to write
2615 and update this file manually, and if you get some detail wrong, the
2616 package is normally rejected by the ftpmasters. So getting it right
2617 the first time around get the package into Debian faster, and save
2618 both you and the ftpmasters some work.. Today, while trying to figure
2619 out what was wrong with
2620 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2621 zfsonlinux copyright file
</a
>, I decided to spend some time on
2622 figuring out the options for doing this job automatically, or at least
2623 semi-automatically.
</p
>
2625 <p
>Lucikly, there are at least two tools available for generating the
2626 file based on the code in the source package,
2627 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2628 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2629 not sure which one of them came first, but both seem to be able to
2630 create a sensible draft file. As far as I can tell, none of them can
2631 be trusted to get the result just right, so the content need to be
2632 polished a bit before the file is OK to upload. I found the debmake
2634 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2635 blog posts from
2014</a
>.
2637 <p
>To generate using debmake, use the -cc option:
2639 <p
><pre
>
2640 debmake -cc
> debian/copyright
2641 </pre
></p
>
2643 <p
>Note there are some problems with python and non-ASCII names, so
2644 this might not be the best option.
</p
>
2646 <p
>The cme option is based on a config parsing library, and I found
2648 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2649 blog post from
2015</a
>. To generate using cme, use the
'update
2650 dpkg-copyright
' option:
2652 <p
><pre
>
2653 cme update dpkg-copyright
2654 </pre
></p
>
2656 <p
>This will create or update debian/copyright. The cme tool seem to
2657 handle UTF-
8 names better than debmake.
</p
>
2659 <p
>When the copyright file is created, I would also like some help to
2660 check if the file is correct. For this I found two good options,
2661 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2662 to focus on license types and file matching, and is able to detect
2663 ineffective blocks in the copyright file. The latter reports missing
2664 copyright holders and years, but was confused by inconsistent license
2665 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2666 fix all issues reported by them before uploading. But I do not know
2667 if the tools and the ftpmasters agree on what is important to fix in a
2668 copyright file, so the package might still be rejected.
</p
>
2670 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2671 will read through the source and try to find all copyright statements.
2672 It is not comparing the result to the content of debian/copyright, but
2673 can be useful when verifying the content of the copyright file.
</p
>
2675 <p
>Are you aware of better tools in Debian to create and update
2676 debian/copyright file. Please let me know, or blog about it on
2677 planet.debian.org.
</p
>
2679 <p
>As usual, if you use Bitcoin and want to show your support of my
2680 activities, please send Bitcoin donations to my address
2681 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2683 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2684 on how to use licensecheck and cdbs to create a draft copyright file
2686 <p
><pre
>
2687 licensecheck --copyright -r `find * -type f` | \
2688 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2689 </pre
></p
>
2691 <p
>He mentioned that he normally check the generated file into the
2692 version control system to make it easier to discover license and
2693 copyright changes in the upstream source. I will try to do the same
2694 with my packages in the future.
</p
>
2696 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2697 against using -quiet for new users, so I removed it from the proposed
2698 command line.
</p
>
2703 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2704 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2706 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2707 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2708 is taking shape in Debian, and one provided feature is a very
2709 convenient way to tell you which package to install to make a given
2710 firmware file available when the kernel is looking for it. This can
2711 be done using apt-file too, but that is for someone else to blog
2714 <p
>Here is a small recipe to find the package with a given firmware
2715 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2716 picked from the set of firmware announced using appstream in Debian
2717 unstable. In general you would be looking for the firmware requested
2718 by the kernel during kernel module loading. To find the package
2719 providing the example file, do like this:
</p
>
2721 <blockquote
><pre
>
2722 % apt install appstream
2726 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2727 awk
'/Package:/ {print $
2}
'
2730 </pre
></blockquote
>
2732 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2733 appstream wiki
</a
> page to learn how to embed the package metadata in
2734 a way appstream can use.
</p
>
2736 <p
>This same approach can be used to find any package supporting a
2737 given MIME type. This is very useful when you get a file you do not
2738 know how to handle. First find the mime type using
<tt
>file
2739 --mime-type
</tt
>, and next look up the package providing support for
2740 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2741 and you can find all packages handling this type like this:
</p
>
2743 <blockquote
><pre
>
2744 % apt install appstream
2748 % appstreamcli what-provides mimetype image/svg+xml | \
2749 awk
'/Package:/ {print $
2}
'
2771 </pre
></blockquote
>
2773 <p
>I believe the MIME types are fetched from the desktop file for
2774 packages providing appstream metadata.
</p
>
2779 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2780 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2781 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2782 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2783 <description><p
>Most people seem not to realise that every time they walk around
2784 with the computerised radio beacon known as a mobile phone their
2785 position is tracked by the phone company and often stored for a long
2786 time (like every time a SMS is received or sent). And if their
2787 computerised radio beacon is capable of running programs (often called
2788 mobile apps) downloaded from the Internet, these programs are often
2789 also capable of tracking their location (if the app requested access
2790 during installation). And when these programs send out information to
2791 central collection points, the location is often included, unless
2792 extra care is taken to not send the location. The provided
2793 information is used by several entities, for good and bad (what is
2794 good and bad, depend on your point of view). What is certain, is that
2795 the private sphere and the right to free movement is challenged and
2796 perhaps even eradicated for those announcing their location this way,
2797 when they share their whereabouts with private and public
2800 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2802 <p
>The phone company logs provide a register of locations to check out
2803 when one want to figure out what the tracked person was doing. It is
2804 unavailable for most of us, but provided to selected government
2805 officials, company staff, those illegally buying information from
2806 unfaithful servants and crackers stealing the information. But the
2807 public information can be collected and analysed, and a free software
2808 tool to do so is called
2809 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2810 discovered it when I read
2811 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2812 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2813 November
2014, and decided to check if it was available in Debian.
2814 The python program was in Debian, but
2815 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2816 Debian
</a
> was completely broken and practically unmaintained. I
2817 uploaded a new version which did not work quite right, but did not
2818 have time to fix it then. This Christmas I decided to finally try to
2819 get Creepy operational in Debian. Now a fixed version is available in
2820 Debian unstable and testing, and almost all Debian specific patches
2822 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2824 <p
>The Creepy program visualises geolocation information fetched from
2825 Twitter, Instagram, Flickr and Google+, and allow one to get a
2826 complete picture of every social media message posted recently in a
2827 given area, or track the movement of a given individual across all
2828 these services. Earlier it was possible to use the search API of at
2829 least some of these services without identifying oneself, but these
2830 days it is impossible. This mean that to use Creepy, you need to
2831 configure it to log in as yourself on these services, and provide
2832 information to them about your search interests. This should be taken
2833 into account when using Creepy, as it will also share information
2834 about yourself with the services.
</p
>
2836 <p
>The picture above show the twitter messages sent from (or at least
2837 geotagged with a position from) the city centre of Oslo, the capital
2838 of Norway. One useful way to use Creepy is to first look at
2839 information tagged with an area of interest, and next look at all the
2840 information provided by one or more individuals who was in the area.
2841 I tested it by checking out which celebrity provide their location in
2842 twitter messages by checkout out who sent twitter messages near a
2843 Norwegian TV station, and next could track their position over time,
2844 making it possible to locate their home and work place, among other
2845 things. A similar technique have been
2846 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2847 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2848 tool to discover lying governments, and a useful tool to help people
2849 understand the value of the private information they provide to the
2852 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2853 it depend on several python modules currently missing in Jessie (at
2854 least python-instagram, python-flickrapi and
2855 python-requests-toolbelt).
</p
>
2857 <p
>(I have uploaded
2858 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2859 screenshots.debian.net
</a
> and licensed it under the same terms as the
2860 Creepy program in Debian.)
</p
>
2865 <title>Always download Debian packages using Tor - the simple recipe
</title>
2866 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2867 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2868 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2869 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2870 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2871 that those listening on the Internet lines would have good reason to
2872 believe a computer have a given security hole
</a
> if it download a
2873 security fix from a Debian mirror. This is a good reason to always
2874 use encrypted connections to the Debian mirror, to make sure those
2875 listening do not know which IP address to attack. In August, Richard
2876 Hartmann observed that encryption was not enough, when it was possible
2877 to interfere download size to security patches or the fact that
2878 download took place shortly after a security fix was released, and
2879 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2880 to always use Tor to download packages from the Debian mirror
</a
>. He
2881 was not the first to propose this, as the
2882 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2883 package by Tim Retout already existed to make it easy to convince apt
2884 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2885 aware of that package when I read the blog post from Richard.
</p
>
2887 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2888 sysadmins, and he set up a Tor hidden service on one of the central
2889 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2890 it possible to download packages directly between two tor nodes,
2891 making sure the network traffic always were encrypted.
</p
>
2893 <p
>Here is a short recipe for enabling this on your machine, by
2894 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2895 urls with tor+http and tor+https, and using the hidden service instead
2896 of the official Debian mirror site. I recommend installing
2897 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2898 done in /etc/.
</p
>
2900 <blockquote
><pre
>
2901 apt install apt-transport-tor
2902 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2903 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2904 </pre
></blockquote
>
2906 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2907 the sed commands for these too. The sed command is assuming your are
2908 using the ftp.debian.org Debian mirror. Adjust the command (or just
2909 edit the file manually) to match your mirror.
</p
>
2911 <p
>This work in Debian Jessie and later. Note that tools like
2912 <tt
>apt-file
</tt
> only recently started using the apt transport
2913 system, and do not work with these tor+http URLs. For
2914 <tt
>apt-file
</tt
> you need the version currently in experimental,
2915 which need a recent apt version currently only in unstable. So if you
2916 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2918 <p
>Another advantage from this change is that your machine will start
2919 using Tor regularly and at fairly random intervals (every time you
2920 update the package lists or upgrade or install a new package), thus
2921 masking other Tor traffic done from the same machine. Using Tor will
2922 become normal for the machine in question.
</p
>
2924 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2925 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2926 enabled. It would be great if it was the default on any Debian
2932 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2933 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2934 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2935 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2936 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2937 call the car license plate numbers in those days. I would write the
2938 numbers down in my little book and compare notes with the other kids
2939 to see how many region codes we had seen and if we had seen some
2940 exotic or special region codes and numbers. It was a fun game to pass
2941 time, as we kids have plenty of it.
</p
>
2943 <p
>A few days I came across
2944 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2945 project
</a
>, a free software project to automatically discover and
2946 report license plates in images and video streams, and provide the
2947 "car numbers
" in a machine readable format. I
've been looking for
2948 such system for a while now, because I believe it is a bad idea that the
2949 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2950 number plate recognition
</a
> tool only is available in the hands of
2951 the powerful, and want it to be available also for the powerless to
2952 even the score when it comes to surveillance and sousveillance. I
2953 discovered the developer
2954 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2955 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2956 help him get it into shape to get the package uploaded into the Debian
2959 <p
>Today we finally managed to get the package into shape and uploaded
2960 it into Debian, where it currently
2961 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2962 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2964 <p
>I guess you are wondering why on earth such tool would be useful
2965 for the common folks, ie those not running a large government
2966 surveillance system? Well, I plan to put it in a computer on my bike
2967 and in my car, tracking the cars nearby and allowing me to be notified
2968 when number plates on my watch list are discovered. Another use case
2969 was suggested by a friend of mine, who wanted to set it up at his home
2970 to open the car port automatically when it discovered the plate on his
2971 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2972 capable of placing his license plate number of a piece of cardboard to
2973 open his car port, men replied that it was always unlocked anyway. I
2974 guess for such use case it make sense. I am sure there are other use
2975 cases too, for those with imagination and a vision.
</p
>
2977 <p
>If you want to build your own version of the Debian package, check
2978 out the upstream git source and symlink ./distros/debian to ./debian/
2979 before running
"debuild
" to build the source. Or wait a bit until the
2980 package show up in unstable.
</p
>
2985 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2986 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2988 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2989 <description><p
>Around three years ago, I created
2990 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2991 system
</a
> to get a more practical solution in Debian for handing
2992 hardware related packages. A GUI system in the isenkram package will
2993 present a pop-up dialog when some hardware dongle supported by
2994 relevant packages in Debian is inserted into the machine. The same
2995 lookup mechanism to detect packages is available as command line
2996 tools in the isenkram-cli package. In addition to mapping hardware,
2997 it will also map kernel firmware files to packages and make it easy to
2998 install needed firmware packages automatically. The key for this
2999 system to work is a good way to map hardware to packages, in other
3000 words, allow packages to announce what hardware they will work
3003 <p
>I started by providing data files in the isenkram source, and
3004 adding code to download the latest version of these data files at run
3005 time, to ensure every user had the most up to date mapping available.
3006 I also added support for storing the mapping in the Packages file in
3007 the apt repositories, but did not push this approach because while I
3008 was trying to figure out how to best store hardware/package mappings,
3009 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
3010 appstream system
</a
> was announced. I got in touch and suggested to
3011 add the hardware mapping into that data set to be able to use
3012 appstream as a data source, and this was accepted at least for the
3013 Debian version of appstream.
</p
>
3015 <p
>A few days ago using appstream in Debian for this became possible,
3016 and today I uploaded a new version
0.20 of isenkram adding support for
3017 appstream as a data source for mapping hardware to packages. The only
3018 package so far using appstream to announce its hardware support is my
3019 pymissile package. I got help from Matthias Klumpp with figuring out
3020 how do add the required
3021 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
3022 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
3023 this content:
</p
>
3025 <blockquote
><pre
>
3026 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3027 &lt;component
&gt;
3028 &lt;id
&gt;pymissile
&lt;/id
&gt;
3029 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
3030 &lt;name
&gt;pymissile
&lt;/name
&gt;
3031 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
3032 &lt;description
&gt;
3034 Pymissile provides a curses interface to control an original
3035 Marks and Spencer / Striker USB Missile Launcher, as well as a
3036 motion control script to allow a webcamera to control the
3039 &lt;/description
&gt;
3040 &lt;provides
&gt;
3041 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
3042 &lt;/provides
&gt;
3043 &lt;/component
&gt;
3044 </pre
></blockquote
>
3046 <p
>The key for isenkram is the component/provides/modalias value,
3047 which is a glob style match rule for hardware specific strings
3048 (modalias strings) provided by the Linux kernel. In this case, it
3049 will map to all USB devices with vendor code
1130 and product code
3052 <p
>Note, it is important that the license of all the metadata files
3053 are compatible to have permissions to aggregate them into archive wide
3054 appstream files. Matthias suggested to use MIT or BSD licenses for
3055 these files. A challenge is figuring out a good id for the data, as
3056 it is supposed to be globally unique and shared across distributions
3057 (in other words, best to coordinate with upstream what to use). But
3058 it can be changed later or, so we went with the package name as
3059 upstream for this project is dormant.
</p
>
3061 <p
>To get the metadata file installed in the correct location for the
3062 mirror update scripts to pick it up and include its content the
3063 appstream data source, the file must be installed in the binary
3064 package under /usr/share/appdata/. I did this by adding the following
3065 line to debian/pymissile.install:
</p
>
3067 <blockquote
><pre
>
3068 debian/pymissile.metainfo.xml usr/share/appdata
3069 </pre
></blockquote
>
3071 <p
>With that in place, the command line tool isenkram-lookup will list
3072 all packages useful on the current computer automatically, and the GUI
3073 pop-up handler will propose to install the package not already
3074 installed if a hardware dongle is inserted into the machine in
3077 <p
>Details of the modalias field in appstream is available from the
3078 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
3080 <p
>To locate the modalias values of all hardware present in a machine,
3081 try running this command on the command line:
</p
>
3083 <blockquote
><pre
>
3084 cat $(find /sys/devices/|grep modalias)
3085 </pre
></blockquote
>
3087 <p
>To learn more about the isenkram system, please check out
3088 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3089 blog posts tagged isenkram
</a
>.
</p
>
3094 <title>The GNU General Public License is not magic pixie dust
</title>
3095 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
3096 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
3097 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
3098 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
3099 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
3100 GPL is not magic pixie dust
</a
>" explain the importance of making sure
3101 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
3102 I quote the blog post from Paul in full here with his permission:
<p
>
3106 <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
>
3109 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
3111 The first step is to choose a
3112 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
3115 The next step is, when someone fails to follow that copyleft license,
3116 <b
>it must be enforced
</b
><br/
>
3118 and its a simple fact of our modern society that such type of
3121 is incredibly expensive to do and incredibly difficult to do.
3124 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
3125 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
3126 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
3127 0x57</a
></small
></p
>
3129 <p
>As the Debian Website
3130 <a href=
"https://bugs.debian.org/
794116">used
</a
>
3131 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
3132 imply, public domain and permissively licensed software can lead to
3133 the production of more proprietary software as people discover useful
3134 software, extend it and or incorporate it into their hardware or
3135 software products. Copyleft licenses such as the GNU GPL were created
3136 to close off this avenue to the production of proprietary software but
3137 such licenses are not enough. With the ongoing adoption of Free
3138 Software by individuals and groups, inevitably the community
's
3139 expectations of license compliance are violated, usually out of
3140 ignorance of the way Free Software works, but not always. As Karen
3141 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
3142 Freedom
">FaiF
</a
>
3143 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
3144 copyleft is nothing if no-one is willing and able to stand up in court
3145 to protect it. The reality of today
's world is that legal
3146 representation is expensive, difficult and time consuming. With
3147 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
3148 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
3149 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
3150 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
3151 of the Linux project, Debian and other groups against GPL violations.
3152 In March the SFC supported a
3153 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
3154 by Christoph Hellwig
</a
> against VMware for refusing to
3155 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
3156 with the GPL
</a
> in relation to their use of parts of the Linux
3157 kernel. Since then two of their sponsors pulled corporate funding and
3159 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
3160 or cancelled their talks
</a
>. As a result they have decided to rely
3161 less on corporate funding and more on the broad community of
3162 individuals who support Free Software and copyleft. So the SFC has
3163 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
3164 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
3165 a community of folks who stand up for copyleft and the GPL by
3166 supporting their work on promoting and supporting copyleft and Free
3169 <p
>If you support Free Software,
3170 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
3171 what the SFC do, agree with their
3172 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
3173 principles
</a
>, are happy about their
3174 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
3175 work on a project that is an SFC
3176 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
3177 just want to stand up for copyleft, please join
3178 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
3179 Allan Webber
</a
>,
3180 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
3182 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
3183 Bacon
</a
>, myself and
3184 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
3186 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
3187 next week your donation will be
3188 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
3189 by an anonymous donor. Please also consider asking your employer to
3190 match your donation or become a sponsor of SFC. Don
't forget to
3191 spread the word about your support for SFC via email, your blog and or
3192 social media accounts.
</p
>
3196 <p
>I agree with Paul on this topic and just signed up as a Supporter
3197 of Software Freedom Conservancy myself. Perhaps you should be a
3198 supporter too?
</p
>
3203 <title>PGP key transition statement for key EE4E02F9
</title>
3204 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
3205 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
3206 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
3207 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
3208 set it up properly. I wanted to generate it offline and have it
3209 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
3210 smart card
</a
> for daily use, and learning how to do it and finding
3211 time to sit down with an offline machine almost took forever. But
3212 finally I
've been able to complete the process, and have now moved
3213 from my old GPG key to a new GPG key. See
3214 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
3215 full transition statement, signed with both my old and new key
</a
> for
3216 the details. This is my new key:
</p
>
3219 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
3220 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
3221 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
3222 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
3223 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
3224 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
3225 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
3228 <p
>The key can be downloaded from the OpenPGP key servers, signed by
3229 my old key.
</p
>
3231 <p
>If you signed my old key
3232 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
3233 I
'd very much appreciate a signature on my new key, details and
3234 instructions in the transition statement. I m happy to reciprocate if
3235 you have a similarly signed transition statement to present.
</p
>
3240 <title>The life and death of a laptop battery
</title>
3241 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
3242 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
3243 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
3244 <description><p
>When I get a new laptop, the battery life time at the start is OK.
3245 But this do not last. The last few laptops gave me a feeling that
3246 within a year, the life time is just a fraction of what it used to be,
3247 and it slowly become painful to use the laptop without power connected
3248 all the time. Because of this, when I got a new Thinkpad X230 laptop
3249 about two years ago, I decided to monitor its battery state to have
3250 more hard facts when the battery started to fail.
</p
>
3252 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
3254 <p
>First I tried to find a sensible Debian package to record the
3255 battery status, assuming that this must be a problem already handled
3256 by someone else. I found
3257 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
3258 which collects statistics from the battery, but it was completely
3259 broken. I sent a few suggestions to the maintainer, but decided to
3260 write my own collector as a shell script while I waited for feedback
3262 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3263 blog post about the battery development on a MacBook Air
</a
> I also
3265 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3266 available in Debian.
</p
>
3268 <p
>I started my collector
2013-
07-
15, and it has been collecting
3269 battery stats ever since. Now my
3270 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3271 measurements, from the time the battery was working great until now,
3272 when it is unable to charge above
7% of original capacity. My
3273 collector shell script is quite simple and look like this:
</p
>
3278 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3280 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3281 logfile=/var/log/hjemmenett-battery-status.log
3283 files=
"manufacturer model_name technology serial_number \
3284 energy_full energy_full_design energy_now cycle_count status
"
3286 if [ ! -e
"$logfile
" ] ; then
3288 printf
"timestamp,
"
3290 printf
"%s,
" $f
3293 )
> "$logfile
"
3297 # Print complete message in one echo call, to avoid race condition
3298 # when several log processes run in parallel.
3299 msg=$(printf
"%s,
" $(date +%s); \
3300 for f in $files; do \
3301 printf
"%s,
" $(cat $f); \
3303 echo
"$msg
"
3306 cd /sys/class/power_supply
3309 (cd $bat
&& log_battery
>> "$logfile
")
3313 <p
>The script is called when the power management system detect a
3314 change in the power status (power plug in or out), and when going into
3315 and out of hibernation and suspend. In addition, it collect a value
3316 every
10 minutes. This make it possible for me know when the battery
3317 is discharging, charging and how the maximum charge change over time.
3318 The code for the Debian package
3319 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3320 available on github
</a
>.
</p
>
3322 <p
>The collected log file look like this:
</p
>
3325 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3326 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3328 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3329 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3332 <p
>I wrote a small script to create a graph of the charge development
3333 over time. This graph depicted above show the slow death of my laptop
3336 <p
>But why is this happening? Why are my laptop batteries always
3337 dying in a year or two, while the batteries of space probes and
3338 satellites keep working year after year. If we are to believe
3339 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3340 University
</a
>, the cause is me charging the battery whenever I have a
3341 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3342 all the time, but to stay below
90% of full charge most of the time.
3343 I
've been told that the Tesla electric cars
3344 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3345 the charge of their batteries to
80%
</a
>, with the option to charge to
3346 100% when preparing for a longer trip (not that I would want a car
3347 like Tesla where rights to privacy is abandoned, but that is another
3348 story), which I guess is the option we should have for laptops on
3349 Linux too.
</p
>
3351 <p
>Is there a good and generic way with Linux to tell the battery to
3352 stop charging at
80%, unless requested to charge to
100% once in
3353 preparation for a longer trip? I found
3354 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3355 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3356 80%
</a
>, but could not get it to work (kernel module refused to
3359 <p
>I wonder why the battery capacity was reported to be more than
100%
3360 at the start. I also wonder why the
"full capacity
" increases some
3361 times, and if it is possible to repeat the process to get the battery
3362 back to design capacity. And I wonder if the discharge and charge
3363 speed change over time, or if this stay the same. I did not yet try
3364 to write a tool to calculate the derivative values of the battery
3365 level, but suspect some interesting insights might be learned from
3368 <p
>Update
2015-
09-
24: I got a tip to install the packages
3369 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3370 packages instead of the tp-smapi-dkms package I had tried to use
3371 initially, and use
'tlp setcharge
40 80' to change when charging start
3372 and stop. I
've done so now, but expect my existing battery is toast
3373 and need to be replaced. The proposal is unfortunately Thinkpad
3379 <title>New laptop - some more clues and ideas based on feedback
</title>
3380 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3381 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3382 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3383 <description><p
>Several people contacted me after my previous blog post about my
3384 need for a new laptop, and provided very useful feedback. I wish to
3385 thank every one of these. Several pointed me to the possibility of
3386 fixing my X230, and I am already in the process of getting Lenovo to
3387 do so thanks to the on site, next day support contract covering the
3388 machine. But the battery is almost useless (I expect to replace it
3389 with a non-official battery) and I do not expect the machine to live
3390 for many more years, so it is time to plan its replacement. If I did
3391 not have a support contract, it was suggested to find replacement parts
3392 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3393 might present a language barrier as I do not understand French.
</p
>
3395 <p
>One tip I got was to use the
3396 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3397 compare laptop models. It seem to have more models available than
3398 prisjakt.no. Another tip I got from someone I know have similar
3399 keyboard preferences was that the HP EliteBook
840 keyboard is not
3400 very good, and this matches my experience with earlier EliteBook
3401 keyboards I tested. Because of this, I will not consider it any further.
3403 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3404 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3405 (which is missing from the X240), and is working fairly well with
3406 Debian Sid/Unstable according to
3407 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3408 got on the keyboard quality are not consistent. Some say the keyboard
3409 is good, others say it is ok, while others say it is not very good.
3410 Those with experience from X41 and and X60 agree that the X250
3411 keyboard is not as good as those trusty old laptops, and suggest I
3412 keep and fix my X230 instead of upgrading, or get a used X230 to
3413 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3414 activity and battery status, which is very convenient on my X230. I
'm
3415 also told that the CPU fan is running very often, making it a bit
3416 noisy. In any case, the X250 do not work out of the box with Debian
3417 Stable/Jessie, one of my requirements.
</p
>
3419 <p
>I have also gotten a few vendor proposals, one was
3420 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3421 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3422 The latter look very attractive to me.
</p
>
3424 <p
>Again, thank you all for the very useful feedback. It help a lot
3425 as I keep looking for a replacement.
</p
>
3427 <p
>Update
2015-
07-
06: I was recommended to check out the
3428 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3430 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3431 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3436 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3437 <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>
3438 <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>
3439 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3440 <description><p
>My primary work horse laptop is failing, and will need a
3441 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3442 started flickering yesterday, and I suspect the cause is a broken
3443 cable, as changing the angle of the screen some times get rid of the
3444 flickering.
</p
>
3446 <p
>My requirements have not really changed since I bought it, and is
3448 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3449 described them in
2013</a
>. The last time I bought a laptop, I had
3451 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3452 where I could select at least a few of the requirements (mouse pin,
3453 wifi, weight) and go through the rest manually. Three button mouse
3454 and a good keyboard is not available as an option, and all the three
3455 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3456 G2) lack three mouse buttons). It is also unclear to me how good the
3457 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3458 the keyboard, even if the quality and robustness in the X series have
3459 deteriorated since X41.
</p
>
3461 <p
>I wonder how I can find a sensible laptop when none of the options
3462 seem sensible to me? Are there better services around to search the
3463 set of available laptops for features? Please send me an email if you
3464 have suggestions.
</p
>
3466 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3467 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3468 of endorsed hardware
</a
>, which is useful background information.
</p
>
3473 <title>How to stay with sysvinit in Debian Jessie
</title>
3474 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3475 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3476 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3477 <description><p
>By now, it is well known that Debian Jessie will not be using
3478 sysvinit as its boot system by default. But how can one keep using
3479 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3481 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3482 Schubert
</a
> and
3483 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3486 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3487 keep sysvinit as your boot system, create a file
3488 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3489 you upgrade:
</p
>
3491 <p
><blockquote
><pre
>
3492 Package: systemd-sysv
3493 Pin: release o=Debian
3495 </pre
></blockquote
><p
>
3497 <p
>This file content will tell apt and aptitude to not consider
3498 installing systemd-sysv as part of any installation and upgrade
3499 solution when resolving dependencies, and thus tell it to avoid
3500 systemd as a default boot system. The end result should be that the
3501 upgraded system keep using sysvinit.
</p
>
3503 <p
>If you are installing Jessie for the first time, there is no way to
3504 get sysvinit installed by default (debootstrap used by
3505 debian-installer have no option for this), but one can tell the
3506 installer to switch to sysvinit before the first boot. Either by
3507 using a kernel argument to the installer, or by adding a line to the
3508 preseed file used. First, the kernel command line argument:
3510 <p
><blockquote
><pre
>
3511 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3512 </pre
></blockquote
><p
>
3514 <p
>Next, the line to use in a preseed file:
</p
>
3516 <p
><blockquote
><pre
>
3517 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3518 </pre
></blockquote
><p
>
3520 <p
>One can of course also do this after the first boot by installing
3521 the sysvinit-core package.
</p
>
3523 <p
>I recommend only using sysvinit if you really need it, as the
3524 sysvinit boot sequence in Debian have several hardware specific bugs
3525 on Linux caused by the fact that it is unpredictable when hardware
3526 devices show up during boot. But on the other hand, the new default
3527 boot system still have a few rough edges I hope will be fixed before
3528 Jessie is released.
</p
>
3530 <p
>Update
2014-
11-
26: Inspired by
3531 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3532 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3538 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3539 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3540 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3541 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3542 <description><p
>The right to communicate with your friends and family in private,
3543 without anyone snooping, is a right every citicen have in a liberal
3544 democracy. But this right is under serious attack these days.
</p
>
3546 <p
>A while back it occurred to me that one way to make the dragnet
3547 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3548 the whisleblower Snowden) more expensive for Internet email,
3549 is to deliver all email using SMTP via Tor. Such SMTP option would be
3550 a nice addition to the FreedomBox project if we could send email
3551 between FreedomBox machines without leaking metadata about the emails
3552 to the people peeking on the wire. I
3553 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3554 this on the FreedomBox project mailing list in October
</a
> and got a
3555 lot of useful feedback and suggestions. It also became obvious to me
3556 that this was not a novel idea, as the same idea was tested and
3557 documented by Johannes Berg as early as
2006, and both
3558 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3559 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3560 propose a similar method / protocol to pass emails between users.
</p
>
3562 <p
>To implement such system one need to set up a Tor hidden service
3563 providing the SMTP protocol on port
25, and use email addresses
3564 looking like username@hidden-service-name.onion. With such addresses
3565 the connections to port
25 on hidden-service-name.onion using Tor will
3566 go to the correct SMTP server. To do this, one need to configure the
3567 Tor daemon to provide the hidden service and the mail server to accept
3568 emails for this .onion domain. To learn more about Exim configuration
3569 in Debian and test the design provided by Johannes Berg in his FAQ, I
3570 set out yesterday to create a Debian package for making it trivial to
3571 set up such SMTP over Tor service based on Debian. Getting it to work
3572 were fairly easy, and
3573 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3574 source code for the Debian package
</a
> is available from github. I
3575 plan to move it into Debian if further testing prove this to be a
3576 useful approach.
</p
>
3578 <p
>If you want to test this, set up a blank Debian machine without any
3579 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3580 get rid of exim4). Install tor, clone the git repository mentioned
3581 above, build the deb and install it on the machine. Next, run
3582 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3583 the instructions to get the service up and running. Restart tor and
3584 exim when it is done, and test mail delivery using swaks like
3587 <p
><blockquote
><pre
>
3588 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3589 --to fbx@dutlqrrmjhtfa3vp.onion
3590 </pre
></blockquote
></p
>
3592 <p
>This will test the SMTP delivery using tor. Replace the email
3593 address with your own address to test your server. :)
</p
>
3595 <p
>The setup procedure is still to complex, and I hope it can be made
3596 easier and more automatic. Especially the tor setup need more work.
3597 Also, the package include a tor-smtp tool written in C, but its task
3598 should probably be rewritten in some script language to make the deb
3599 architecture independent. It would probably also make the code easier
3600 to review. The tor-smtp tool currently need to listen on a socket for
3601 exim to talk to it and is started using xinetd. It would be better if
3602 no daemon and no socket is needed. I suspect it is possible to get
3603 exim to run a command line tool for delivery instead of talking to a
3604 socket, and hope to figure out how in a future version of this
3607 <p
>Until I wipe my test machine, I can be reached using the
3608 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3609 SMTorP. :)
</p
>
3614 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3615 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3616 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3617 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3618 <description><p
>If you ever had to moderate a mailman list, like the ones on
3619 alioth.debian.org, you know the web interface is fairly slow to
3620 operate. First you visit one web page, enter the moderation password
3621 and get a new page shown with a list of all the messages to moderate
3622 and various options for each email address. This take a while for
3623 every list you moderate, and you need to do it regularly to do a good
3624 job as a list moderator. But there is a quick alternative,
3625 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3626 listadmin program
</a
>. It allow you to check lists for new messages
3627 to moderate in a fraction of a second. Here is a test run on two
3628 lists I recently took over:
</p
>
3630 <p
><blockquote
><pre
>
3631 % time listadmin xiph
3632 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3633 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3639 </pre
></blockquote
></p
>
3641 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3642 there are no message in the moderation queue. Every morning I
3643 currently moderate
68 mailman lists, and it normally take around two
3644 minutes. When I took over the two pkg-xiph lists above a few days
3645 ago, there were
400 emails waiting in the moderator queue. It took me
3646 less than
15 minutes to process them all using the listadmin
3649 <p
>If you install
3650 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3651 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3652 with content like this, the moderation task is a breeze:
</p
>
3654 <p
><blockquote
><pre
>
3655 username username@example.org
3658 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3661 adminurl https://{domain}/mailman/admindb/{list}
3662 mailman-list@lists.example.com
3665 other-list@otherserver.example.org
3666 </pre
></blockquote
></p
>
3668 <p
>There are other options to set as well. Check the manual page to
3669 learn the details.
</p
>
3671 <p
>If you are forced to moderate lists on a mailman installation where
3672 the SSL certificate is self signed or not properly signed by a
3673 generally accepted signing authority, you can set a environment
3674 variable when calling listadmin to disable SSL verification:
</p
>
3676 <p
><blockquote
><pre
>
3677 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3678 </pre
></blockquote
></p
>
3680 <p
>If you want to moderate a subset of the lists you take care of, you
3681 can provide an argument to the listadmin script like I do in the
3682 initial screen dump (the xiph argument). Using an argument, only
3683 lists matching the argument string will be processed. This make it
3684 quick to accept messages if you notice the moderation request in your
3687 <p
>Without the listadmin program, I would never be the moderator of
68
3688 mailing lists, as I simply do not have time to spend on that if the
3689 process was any slower. The listadmin program have saved me hours of
3690 time I could spend elsewhere over the years. It truly is nice free
3693 <p
>As usual, if you use Bitcoin and want to show your support of my
3694 activities, please send Bitcoin donations to my address
3695 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3697 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3698 configuration example. Also, I
've been told that the
3699 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3705 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3706 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3707 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3708 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3709 <description><p
>When PXE installing laptops with Debian, I often run into the
3710 problem that the WiFi card require some firmware to work properly.
3711 And it has been a pain to fix this using preseeding in Debian.
3712 Normally something more is needed. But thanks to
3713 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3714 package
</a
> and its recent tasksel extension, it has now become easy
3715 to do this using simple preseeding.
</p
>
3717 <p
>The isenkram-cli package provide tasksel tasks which will install
3718 firmware for the hardware found in the machine (actually, requested by
3719 the kernel modules for the hardware). (It can also install user space
3720 programs supporting the hardware detected, but that is not the focus
3721 of this story.)
</p
>
3723 <p
>To get this working in the default installation, two preeseding
3724 values are needed. First, the isenkram-cli package must be installed
3725 into the target chroot (aka the hard drive) before tasksel is executed
3726 in the pkgsel step of the debian-installer system. This is done by
3727 preseeding the base-installer/includes debconf value to include the
3728 isenkram-cli package. The package name is next passed to debootstrap
3729 for installation. With the isenkram-cli package in place, tasksel
3730 will automatically use the isenkram tasks to detect hardware specific
3731 packages for the machine being installed and install them, because
3732 isenkram-cli contain tasksel tasks.
</p
>
3734 <p
>Second, one need to enable the non-free APT repository, because
3735 most firmware unfortunately is non-free. This is done by preseeding
3736 the apt-mirror-setup step. This is unfortunate, but for a lot of
3737 hardware it is the only option in Debian.
</p
>
3739 <p
>The end result is two lines needed in your preseeding file to get
3740 firmware installed automatically by the installer:
</p
>
3742 <p
><blockquote
><pre
>
3743 base-installer base-installer/includes string isenkram-cli
3744 apt-mirror-setup apt-setup/non-free boolean true
3745 </pre
></blockquote
></p
>
3747 <p
>The current version of isenkram-cli in testing/jessie will install
3748 both firmware and user space packages when using this method. It also
3749 do not work well, so use version
0.15 or later. Installing both
3750 firmware and user space packages might give you a bit more than you
3751 want, so I decided to split the tasksel task in two, one for firmware
3752 and one for user space programs. The firmware task is enabled by
3753 default, while the one for user space programs is not. This split is
3754 implemented in the package currently in unstable.
</p
>
3756 <p
>If you decide to give this a go, please let me know (via email) how
3757 this recipe work for you. :)
</p
>
3759 <p
>So, I bet you are wondering, how can this work. First and
3760 foremost, it work because tasksel is modular, and driven by whatever
3761 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3762 isenkram-cli package place two files for tasksel to find. First there
3763 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3765 <p
><blockquote
><pre
>
3766 Task: isenkram-packages
3768 Description: Hardware specific packages (autodetected by isenkram)
3769 Based on the detected hardware various hardware specific packages are
3771 Test-new-install: show show
3773 Packages: for-current-hardware
3775 Task: isenkram-firmware
3777 Description: Hardware specific firmware packages (autodetected by isenkram)
3778 Based on the detected hardware various hardware specific firmware
3779 packages are proposed.
3780 Test-new-install: mark show
3782 Packages: for-current-hardware-firmware
3783 </pre
></blockquote
></p
>
3785 <p
>The key parts are Test-new-install which indicate how the task
3786 should be handled and the Packages line referencing to a script in
3787 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3788 list of packages to install. The for-current-hardware-firmware script
3789 look like this to list relevant firmware for the machine:
3791 <p
><blockquote
><pre
>
3794 PATH=/usr/sbin:$PATH
3796 isenkram-autoinstall-firmware -l
3797 </pre
></blockquote
></p
>
3799 <p
>With those two pieces in place, the firmware is installed by
3800 tasksel during the normal d-i run. :)
</p
>
3802 <p
>If you want to test what tasksel will install when isenkram-cli is
3803 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3804 --new-install
</tt
> to get the list of packages that tasksel would
3807 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3808 pilots in testing this feature, as isenkram is used there now to
3809 install firmware, replacing the earlier scripts.
</p
>
3814 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3815 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3816 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3817 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3818 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3819 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3820 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3821 on a screen normally showing the bread types and prizes:
</p
>
3823 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3825 <p
>If it had booted as it was supposed to, I would never had known
3826 about this hidden Linux installation. It is interesting what
3827 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3832 <title>New lsdvd release version
0.17 is ready
</title>
3833 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3834 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3835 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3836 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3837 got a new set of developers a few weeks ago, after the original
3838 developer decided to step down and pass the project to fresh blood.
3839 This project is now maintained by Petter Reinholdtsen and Steve
3842 <p
>I just wrapped up
3843 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3844 new lsdvd release
</a
>, available in git or from
3845 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3846 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3851 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3852 <li
>Check for garbage in the program chains, which indicate that a track is
3853 non-existant, to work around additional copy protection
</li
>
3854 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3855 <li
>Fix pallete display of first entry
</li
>
3856 <li
>Fix include orders
</li
>
3857 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3858 <li
>Fix the chapter count
</li
>
3859 <li
>Make sure the array size and the array limit used when initialising
3860 the palette size is the same.
</li
>
3861 <li
>Fix array printing.
</li
>
3862 <li
>Correct subsecond calculations.
</li
>
3863 <li
>Add sector information to the output format.
</li
>
3864 <li
>Clean up code to be closer to ANSI C and compile without warnings
3865 with more GCC compiler warnings.
</li
>
3869 <p
>This change bring together patches for lsdvd in use in various
3870 Linux and Unix distributions, as well as patches submitted to the
3871 project the last nine years. Please check it out. :)
</p
>
3876 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3877 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3879 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3880 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3881 project
</a
> provide a Linux solution for schools, including a
3882 powerful desktop with education software, a central server providing
3883 web pages, user database, user home directories, central login and PXE
3884 boot of both clients without disk and the installation to install Debian
3885 Edu on machines with disk (and a few other services perhaps to small
3886 to mention here). We in the Debian Edu team are currently working on
3887 the Jessie based version, trying to get everything in shape before the
3888 freeze, to avoid having to maintain our own package repository in the
3890 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3891 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3892 work left. Some fatal problems block testing, breaking the installer,
3893 but it is possible to work around these to get anyway. Here is a
3894 recipe on how to get the installation limping along.
</p
>
3896 <p
>First, download the test ISO via
3897 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3898 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3900 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3901 The ISO build was broken on Tuesday, so we do not get a new ISO every
3902 12 hours or so, but thankfully the ISO we already got we are able to
3903 install with some tweaking.
</p
>
3905 <p
>When you get to the Debian Edu profile question, go to tty2
3906 (use Alt-Ctrl-F2), run
</p
>
3908 <p
><blockquote
><pre
>
3909 nano /usr/bin/edu-eatmydata-install
3910 </pre
></blockquote
></p
>
3912 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3913 optimization. Return to the installation, select the profile you want
3914 and continue. Without this change, exim4-config will fail to install
3915 due to a known bug in eatmydata.
</p
>
3917 <p
>When you get the grub question at the end, answer /dev/sda (or if
3918 this do not work, figure out what your correct value would be. All my
3919 test machines need /dev/sda, so I have no advice if it do not fit
3920 your need.
</p
>
3922 <p
>If you installed a profile including a graphical desktop, log in as
3923 root after the initial boot from hard drive, and install the
3924 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3925 or mate. If you want several desktop options, install more than one
3926 metapackage. Once this is done, reboot and you should have a working
3927 graphical login screen. This workaround should no longer be needed
3928 once the education-tasks package version
1.801 enter testing in two
3931 <p
>I believe the ISO build will start working on two days when the new
3932 tasksel package enter testing and Steve McIntyre get a chance to
3933 update the debian-cd git repository. The eatmydata, grub and desktop
3934 issues are already fixed in unstable and testing, and should show up
3935 on the ISO as soon as the ISO build start working again. Well the
3936 eatmydata optimization is really just disabled. The proper fix
3937 require an upload by the eatmydata maintainer applying the patch
3938 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3939 The rest have proper fixes in unstable.
</p
>
3941 <p
>I hope this get you going with the installation testing, as we are
3942 quickly running out of time trying to get our Jessie based
3943 installation ready before the distribution freeze in a month.
</p
>
3948 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3949 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3951 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3952 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3953 to handle my fairly large DVD collection. It is a nice command line
3954 tool to get details about a DVD, like title, tracks, track length,
3955 etc, in XML, Perl or human readable format. But lsdvd have not seen
3956 any new development since
2006 and had a few irritating bugs affecting
3957 its use with some DVDs. Upstream seemed to be dead, and in January I
3958 sent a small probe asking for a version control repository for the
3959 project, without any reply. But I use it regularly and would like to
3960 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3961 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3962 the project admin, and after getting a reply from him explaining that
3963 he was no longer interested in the project, I asked if I could take
3964 over. And yesterday, I became project admin.
</p
>
3966 <p
>I
've been in touch with a Gentoo developer and the Debian
3967 maintainer interested in joining forces to maintain the upstream
3968 project, and I hope we can get a new release out fairly quickly,
3969 collecting the patches spread around on the internet into on place.
3970 I
've added the relevant Debian patches to the freshly created git
3971 repository, and expect the Gentoo patches to make it too. If you got
3972 a DVD collection and care about command line tools, check out
3973 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3974 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3975 list
</a
>. :)
</p
>
3980 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3981 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3982 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3983 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3984 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3985 a lot quicker. When we install more than
2000 packages in
3986 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3987 tasksel in the installer, unpacking the binary packages take forever.
3988 A part of the slow I/O issue was discussed in
3989 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3990 much file system sync-ing done by dpkg, which is the package
3991 responsible for unpacking the binary packages. Other parts (like code
3992 executed by postinst scripts) might also sync to disk during
3993 installation. All this sync-ing to disk do not really make sense to
3994 me. If the machine crash half-way through, I start over, I do not try
3995 to salvage the half installed system. So the failure sync-ing is
3996 supposed to protect against, hardware or system crash, is not really
3997 relevant while the installer is running.
</p
>
3999 <p
>A few days ago, I thought of a way to get rid of all the file
4000 system sync()-ing in a fairly non-intrusive way, without the need to
4001 change the code in several packages. The idea is not new, but I have
4002 not heard anyone propose the approach using dpkg-divert before. It
4003 depend on the small and clever package
4004 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
4005 uses LD_PRELOAD to replace the system functions for syncing data to
4006 disk with functions doing nothing, thus allowing programs to live
4007 dangerous while speeding up disk I/O significantly. Instead of
4008 modifying the implementation of dpkg, apt and tasksel (which are the
4009 packages responsible for selecting, fetching and installing packages),
4010 it occurred to me that we could just divert the programs away, replace
4011 them with a simple shell wrapper calling
4012 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
4013 Two days ago I decided to test the idea, and wrapped up a simple
4014 implementation for the Debian Edu udeb.
</p
>
4016 <p
>The effect was stunning. In my first test it reduced the running
4017 time of the pkgsel step (installing tasks) from
64 to less than
44
4018 minutes (
20 minutes shaved off the installation) on an old Dell
4019 Latitude D505 machine. I am not quite sure what the optimised time
4020 would have been, as I messed up the testing a bit, causing the debconf
4021 priority to get low enough for two questions to pop up during
4022 installation. As soon as I saw the questions I moved the installation
4023 along, but do not know how long the question were holding up the
4024 installation. I did some more measurements using Debian Edu Jessie,
4025 and got these results. The time measured is the time stamp in
4026 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
4027 "pkgsel: finishing up
" lines, if you want to do the same measurement
4028 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4029 timing thus do not depend on how quickly the user handle the tasksel
4032 <p
><table
>
4035 <th
>Machine/setup
</th
>
4036 <th
>Original tasksel
</th
>
4037 <th
>Optimised tasksel
</th
>
4038 <th
>Reduction
</th
>
4042 <td
>Latitude D505 Main+LTSP LXDE
</td
>
4043 <td
>64 min (
07:
46-
08:
50)
</td
>
4044 <td
><44 min (
11:
27-
12:
11)
</td
>
4045 <td
>>20 min
18%
</td
>
4049 <td
>Latitude D505 Roaming LXDE
</td
>
4050 <td
>57 min (
08:
48-
09:
45)
</td
>
4051 <td
>34 min (
07:
43-
08:
17)
</td
>
4052 <td
>23 min
40%
</td
>
4056 <td
>Latitude D505 Minimal
</td
>
4057 <td
>22 min (
10:
37-
10:
59)
</td
>
4058 <td
>11 min (
11:
16-
11:
27)
</td
>
4059 <td
>11 min
50%
</td
>
4063 <td
>Thinkpad X200 Minimal
</td
>
4064 <td
>6 min (
08:
19-
08:
25)
</td
>
4065 <td
>4 min (
08:
04-
08:
08)
</td
>
4066 <td
>2 min
33%
</td
>
4070 <td
>Thinkpad X200 Roaming KDE
</td
>
4071 <td
>19 min (
09:
21-
09:
40)
</td
>
4072 <td
>15 min (
10:
25-
10:
40)
</td
>
4073 <td
>4 min
21%
</td
>
4076 </table
></p
>
4078 <p
>The test is done using a netinst ISO on a USB stick, so some of the
4079 time is spent downloading packages. The connection to the Internet
4080 was
100Mbit/s during testing, so downloading should not be a
4081 significant factor in the measurement. Download typically took a few
4082 seconds to a few minutes, depending on the amount of packages being
4083 installed.
</p
>
4085 <p
>The speedup is implemented by using two hooks in
4086 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
4087 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
4088 finish-install.d hook to remove the divert at the end of the
4089 installation. I picked the pre-pkgsel.d hook instead of the
4090 post-base-installer.d hook because I test using an ISO without the
4091 eatmydata package included, and the post-base-installer.d hook in
4092 Debian Edu can only operate on packages included in the ISO. The
4093 negative effect of this is that I am unable to activate this
4094 optimization for the kernel installation step in d-i. If the code is
4095 moved to the post-base-installer.d hook, the speedup would be larger
4096 for the entire installation.
</p
>
4098 <p
>I
've implemented this in the
4099 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
4100 git repository, and plan to provide the optimization as part of the
4101 Debian Edu installation. If you want to test this yourself, you can
4102 create two files in the installer (or in an udeb). One shell script
4103 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
4105 <p
><blockquote
><pre
>
4108 . /usr/share/debconf/confmodule
4110 logger -t my-pkgsel
"info: $*
"
4113 logger -t my-pkgsel
"error: $*
"
4115 override_install() {
4116 apt-install eatmydata || true
4117 if [ -x /target/usr/bin/eatmydata ] ; then
4118 for bin in dpkg apt-get aptitude tasksel ; do
4120 # Test that the file exist and have not been diverted already.
4121 if [ -f /target$file ] ; then
4122 info
"diverting $file using eatmydata
"
4123 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
4124 > /target$file.edu
4125 chmod
755 /target$file.edu
4126 in-target dpkg-divert --package debian-edu-config \
4127 --rename --quiet --add $file
4128 ln -sf ./$bin.edu /target$file
4130 error
"unable to divert $file, as it is missing.
"
4134 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
4139 </pre
></blockquote
></p
>
4141 <p
>To clean up, another shell script should go into
4142 /usr/lib/finish-install.d/ with code like this:
4144 <p
><blockquote
><pre
>
4146 . /usr/share/debconf/confmodule
4148 logger -t my-finish-install
"error: $@
"
4150 remove_install_override() {
4151 for bin in dpkg apt-get aptitude tasksel ; do
4153 if [ -x /target$file.edu ] ; then
4155 in-target dpkg-divert --package debian-edu-config \
4156 --rename --quiet --remove $file
4159 error
"Missing divert for $file.
"
4162 sync # Flush file buffers before continuing
4165 remove_install_override
4166 </pre
></blockquote
></p
>
4168 <p
>In Debian Edu, I placed both code fragments in a separate script
4169 edu-eatmydata-install and call it from the pre-pkgsel.d and
4170 finish-install.d scripts.
</p
>
4172 <p
>By now you might ask if this change should get into the normal
4173 Debian installer too? I suspect it should, but am not sure the
4174 current debian-installer coordinators find it useful enough. It also
4175 depend on the side effects of the change. I
'm not aware of any, but I
4176 guess we will see if the change is safe after some more testing.
4177 Perhaps there is some package in Debian depending on sync() and
4178 fsync() having effect? Perhaps it should go into its own udeb, to
4179 allow those of us wanting to enable it to do so without affecting
4182 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
4183 will break installation of all programs using gnutls because of
4184 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
4185 eatmydata package in Debian will solve it.
</p
>
4187 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
4188 the optimization work again. And I have discovered that the
4189 dpkg-divert trick is not really needed and implemented a slightly
4190 simpler approach as part of the debian-edu-install package. See
4191 tools/edu-eatmydata-install in the source package.
</p
>
4193 <p
>Update
2014-
11-
11: Unfortunately, a new
4194 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
4195 triggering on i386 made it into testing, and broke this installation
4196 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
4197 request
768893</a
> is accepted, it should be working again.
</p
>
4202 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
4203 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
4204 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
4205 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
4206 <description><p
>Yesterday, I had the pleasure of attending a talk with the
4207 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
4208 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
4209 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
4210 learn that there is a large set of publicly available key servers to
4211 use when looking for peoples public key. So far I have used
4212 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4213 were misbehaving, but those days are ended. The servers I have used
4214 up until yesterday have been slow and some times unavailable. I hope
4215 those problems are gone now.
</p
>
4217 <p
>Behind the round robin DNS entry of the
4218 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
4219 there is a pool of more than
100 keyservers which are checked every
4220 day to ensure they are well connected and up to date. It must be
4221 better than what I have used so far. :)
</p
>
4223 <p
>Yesterdays speaker told me that the service is the default
4224 keyserver provided by the default configuration in GnuPG, but this do
4225 not seem to be used in Debian. Perhaps it should?
</p
>
4227 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
4230 <p
><blockquote
><pre
>
4231 keyserver pool.sks-keyservers.net
4232 </pre
></blockquote
></p
>
4234 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
4235 entries in DNS. Just for fun, I did just that at work, so now every
4236 user of GnuPG at the University of Oslo should find a OpenGPG
4237 keyserver automatically should their need it:
</p
>
4239 <p
><blockquote
><pre
>
4240 % host -t srv _pgpkey-http._tcp.uio.no
4241 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
4243 </pre
></blockquote
></p
>
4245 <p
>Now if only
4246 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
4247 HKP lookup protocol
</a
> supported finding signature paths, I would be
4248 very happy. It can look up a given key or search for a user ID, but I
4249 normally do not want that, but to find a trust path from my key to
4250 another key. Given a user ID or key ID, I would like to find (and
4251 download) the keys representing a signature path from my key to the
4252 key in question, to be able to get a trust path between the two keys.
4253 This is as far as I can tell not possible today. Perhaps something
4254 for a future version of the protocol?
</p
>
4259 <title>From English wiki to translated PDF and epub via Docbook
</title>
4260 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
4261 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
4262 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4263 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4264 project
</a
> provide an instruction manual for teachers, system
4265 administrators and other users that contain useful tips for setting up
4266 and maintaining a Debian Edu installation. This text is about how the
4267 text processing of this manual is handled in the project.
</p
>
4269 <p
>One goal of the project is to provide information in the native
4270 language of its users, and for this we need to handle translations.
4271 But we also want to make sure each language contain the same
4272 information, so for this we need a good way to keep the translations
4273 in sync. And we want it to be easy for our users to improve the
4274 documentation, avoiding the need to learn special formats or tools to
4275 contribute, and the obvious way to do this is to make it possible to
4276 edit the documentation using a web browser. We also want it to be
4277 easy for translators to keep the translation up to date, and give them
4278 help in figuring out what need to be translated. Here is the list of
4279 tools and the process we have found trying to reach all these
4282 <p
>We maintain the authoritative source of our manual in the
4283 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4284 wiki
</a
>, as several wiki pages written in English. It consist of one
4285 front page with references to the different chapters, several pages
4286 for each chapter, and finally one
"collection page
" gluing all the
4287 chapters together into one large web page (aka
4288 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4289 AllInOne page
</a
>). The AllInOne page is the one used for further
4290 processing and translations. Thanks to the fact that the
4291 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4292 wiki.debian.org support exporting pages in
4293 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4294 the list of pages to export using the raw version of the AllInOne
4295 page, loop over each of them to generate a Docbook XML version of the
4296 manual. This process also download images and transform image
4297 references to use the locally downloaded images. The generated
4298 Docbook XML files are slightly broken, so some post-processing is done
4299 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4300 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4301 a handfull of images. The XML file can now be used to generate PDF, HTML
4302 and epub versions of the English manual. This is the basic step of
4303 our process, making PDF (using dblatex), HTML (using xsltproc) and
4304 epub (using dbtoepub) version from Docbook XML, and the resulting files
4305 are placed in the debian-edu-doc-en binary package.
</p
>
4307 <p
>But English documentation is not enough for us. We want translated
4308 documentation too, and we want to make it easy for translators to
4309 track the English original. For this we use the
4310 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4311 which allow us to transform the English Docbook XML file into a
4312 translation file (a .pot file), usable with the normal gettext based
4313 translation tools used by those translating free software. The pot
4314 file is used to create and maintain translation files (several .po
4315 files), which the translations update with the native language
4316 translations of all titles, paragraphs and blocks of text in the
4317 original. The next step is combining the original English Docbook XML
4318 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4319 create a translated Docbook XML file (in this case
4320 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4321 translated, if the translation is not complete) Docbook XML file can
4322 then be used like the original to create a PDF, HTML and epub version
4323 of the documentation.
</p
>
4325 <p
>The translators use different tools to edit the .po files. We
4327 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4328 while some use emacs and vi, others can use web based editors like
4329 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4330 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4331 is where the .po file end up, in our git repository. Updated
4332 translations can either be committed directly to git, or submitted as
4333 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4334 against the debian-edu-doc package
</a
>.
</p
>
4336 <p
>One challenge is images, which both might need to be translated (if
4337 they show translated user applications), and are needed in different
4338 formats when creating PDF and HTML versions (epub is a HTML version in
4339 this regard). For this we transform the original PNG images to the
4340 needed density and format during build, and have a way to provide
4341 translated images by storing translated versions in
4342 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4343 package maintainers know more.
</p
>
4345 <p
>If you wonder what the result look like, we provide
4346 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4347 of the documentation packages on the web
</a
>. See for example the
4348 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4349 PDF version
</a
> or the
4350 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4351 HTML version
</a
>. We do not yet build the epub version by default,
4352 but perhaps it will be done in the future.
</p
>
4354 <p
>To learn more, check out
4355 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4356 debian-edu-doc package
</a
>,
4357 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4358 manual on the wiki
</a
> and
4359 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4360 translation instructions
</a
> in the manual.
</p
>
4365 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4366 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4367 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4368 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4369 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4370 related packages relevant for the computer installed automatically.
4371 So I implemented one, using
4372 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4373 package
</a
>. To use it, install the tasksel and isenkram packages and
4374 run tasksel as user root. You should be presented with a new option,
4375 "Hardware specific packages (autodetected by isenkram)
". When you
4376 select it, tasksel will install the packages isenkram claim is fit for
4377 the current hardware, hot pluggable or not.
<p
>
4379 <p
>The implementation is in two files, one is the tasksel menu entry
4380 description, and the other is the script used to extract the list of
4381 packages to install. The first part is in
4382 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4385 <p
><blockquote
><pre
>
4388 Description: Hardware specific packages (autodetected by isenkram)
4389 Based on the detected hardware various hardware specific packages are
4391 Test-new-install: mark show
4393 Packages: for-current-hardware
4394 </pre
></blockquote
></p
>
4396 <p
>The second part is in
4397 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4400 <p
><blockquote
><pre
>
4405 isenkram-autoinstall-firmware -l
4407 </pre
></blockquote
></p
>
4409 <p
>All in all, a very short and simple implementation making it
4410 trivial to install the hardware dependent package we all may want to
4411 have installed on our machines. I
've not been able to find a way to
4412 get tasksel to tell you exactly which packages it plan to install
4413 before doing the installation. So if you are curious or careful,
4414 check the output from the isenkram-* command line tools first.
</p
>
4416 <p
>The information about which packages are handling which hardware is
4417 fetched either from the isenkram package itself in
4418 /usr/share/isenkram/, from git.debian.org or from the APT package
4419 database (using the Modaliases header). The APT package database
4420 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4421 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4422 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4423 the python-apt code (bug
4424 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4425 workaround I was able to get rid of the file descriptor leak and
4426 reduce the memory leak from ~
30 MiB per hardware detection down to
4427 around
2 MiB per hardware detection. It should make the desktop
4428 daemon a lot more useful. The fix is in version
0.7 uploaded to
4429 unstable today.
</p
>
4431 <p
>I believe the current way of mapping hardware to packages in
4432 Isenkram is is a good draft, but in the future I expect isenkram to
4433 use the AppStream data source for this. A proposal for getting proper
4434 AppStream support into Debian is floating around as
4435 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4436 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4437 project
</a
> will take place this summer to improve the situation. I
4438 look forward to seeing the result, and welcome patches for isenkram to
4439 start using the information when it is ready.
</p
>
4441 <p
>If you want your package to map to some specific hardware, either
4442 add a
"Xb-Modaliases
" header to your control file like I did in
4443 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4444 package
</a
> or submit a bug report with the details to the isenkram
4446 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4447 blog posts tagged isenkram
</a
> for details on the notation. I expect
4448 the information will be migrated to AppStream eventually, but for the
4449 moment I got no better place to store it.
</p
>
4454 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4455 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4456 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4457 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4458 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4459 project
</a
> is working on providing the software and hardware to make
4460 it easy for non-technical people to host their data and communication
4461 at home, and being able to communicate with their friends and family
4462 encrypted and away from prying eyes. It is still going strong, and
4463 today a major mile stone was reached.
</p
>
4465 <p
>Today, the last of the packages currently used by the project to
4466 created the system images were accepted into Debian Unstable. It was
4467 the freedombox-setup package, which is used to configure the images
4468 during build and on the first boot. Now all one need to get going is
4469 the build code from the freedom-maker git repository and packages from
4470 Debian. And once the freedombox-setup package enter testing, we can
4471 build everything directly from Debian. :)
</p
>
4473 <p
>Some key packages used by Freedombox are
4474 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4475 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4476 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4477 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4478 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4479 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4480 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4481 are plans to integrate more packages into the setup. User
4482 documentation is maintained on the Debian wiki. Please
4483 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4484 the manual
</a
> and help us improve it.
</p
>
4486 <p
>To test for yourself and create boot images with the FreedomBox
4487 setup, run this on a Debian machine using a user with sudo rights to
4488 become root:
</p
>
4490 <p
><pre
>
4491 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4492 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4494 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4496 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4497 </pre
></p
>
4499 <p
>Root access is needed to run debootstrap and mount loopback
4500 devices. See the README in the freedom-maker git repo for more
4501 details on the build. If you do not want all three images, trim the
4502 make line. Note that the virtualbox-image target is not really
4503 virtualbox specific. It create a x86 image usable in kvm, qemu,
4504 vmware and any other x86 virtual machine environment. You might need
4505 the version of vmdebootstrap in Jessie to get the build working, as it
4506 include fixes for a race condition with kpartx.
</p
>
4508 <p
>If you instead want to install using a Debian CD and the preseed
4509 method, boot a Debian Wheezy ISO and use this boot argument to load
4510 the preseed values:
</p
>
4512 <p
><pre
>
4513 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4514 </pre
></p
>
4516 <p
>I have not tested it myself the last few weeks, so I do not know if
4517 it still work.
</p
>
4519 <p
>If you wonder how to help, one task you could look at is using
4520 systemd as the boot system. It will become the default for Linux in
4521 Jessie, so we need to make sure it is usable on the Freedombox. I did
4522 a simple test a few weeks ago, and noticed dnsmasq failed to start
4523 during boot when using systemd. I suspect there are other problems
4524 too. :) To detect problems, there is a test suite included, which can
4525 be run from the plinth web interface.
</p
>
4527 <p
>Give it a go and let us know how it goes on the mailing list, and help
4528 us get the new release published. :) Please join us on
4529 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4530 irc.debian.org)
</a
> and
4531 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4532 mailing list
</a
> if you want to help make this vision come true.
</p
>
4537 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4538 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4539 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4540 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4541 <description><p
>For a while now, I have been looking for a sensible offsite backup
4542 solution for use at home. My requirements are simple, it must be
4543 cheap and locally encrypted (in other words, I keep the encryption
4544 keys, the storage provider do not have access to my private files).
4545 One idea me and my friends had many years ago, before the cloud
4546 storage providers showed up, was to use Google mail as storage,
4547 writing a Linux block device storing blocks as emails in the mail
4548 service provided by Google, and thus get heaps of free space. On top
4549 of this one can add encryption, RAID and volume management to have
4550 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4551 I never found time to implement such system. But the last few weeks I
4552 have looked at a system called
4553 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4554 mounted network backed file system with the features I need.
</p
>
4556 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4557 handling several different storage providers, any with Amazon S3,
4558 Google Drive or OpenStack API. There are heaps of such storage
4559 providers. S3QL can also use a local directory as storage, which
4560 combined with sshfs allow for file storage on any ssh server. S3QL
4561 include support for encryption, compression, de-duplication, snapshots
4562 and immutable file systems, allowing me to mount the remote storage as
4563 a local mount point, look at and use the files as if they were local,
4564 while the content is stored in the cloud as well. This allow me to
4565 have a backup that should survive fire. The file system can not be
4566 shared between several machines at the same time, as only one can
4567 mount it at the time, but any machine with the encryption key and
4568 access to the storage service can mount it if it is unmounted.
</p
>
4570 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4571 package is included already. So to get started, run
<tt
>apt-get
4572 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4573 Greenqloud, after reading their nice recipe on
4574 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4575 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4576 in Iceland more than those in USA when it come to keeping my personal
4577 data safe and private, and thus would rather spend money on a company
4578 in Iceland. Another nice recipe is available from the article
4579 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4580 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4581 Admin magazine. When the provider is picked, figure out how to get
4582 the API key needed to connect to the storage API. With Greencloud,
4583 the key did not show up until I had added payment details to my
4586 <p
>Armed with the API access details, it is time to create the file
4587 system. First, create a new bucket in the cloud. This bucket is the
4588 file system storage area. I picked a bucket name reflecting the
4589 machine that was going to store data there, but any name will do.
4590 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4591 the API login and password, and a locally created password. Store it
4592 all in ~root/.s3ql/authinfo2 like this:
4594 <p
><blockquote
><pre
>
4596 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4597 backend-login: API-login
4598 backend-password: API-password
4599 fs-passphrase: local-password
4600 </pre
></blockquote
></p
>
4602 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4603 but any sensible way to create a fairly random password should do it.
4604 Armed with these details, it is now time to run mkfs, entering the API
4605 details and password to create it:
</p
>
4607 <p
><blockquote
><pre
>
4608 # mkdir -m
700 /var/lib/s3ql-cache
4609 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4610 --ssl s3c://s.greenqloud.com:
443/bucket-name
4611 Enter backend login:
4612 Enter backend password:
4613 Before using S3QL, make sure to read the user
's guide, especially
4614 the
'Important Rules to Avoid Loosing Data
' section.
4615 Enter encryption password:
4616 Confirm encryption password:
4617 Generating random encryption key...
4618 Creating metadata tables...
4628 Compressing and uploading metadata...
4629 Wrote
0.00 MB of compressed metadata.
4630 #
</pre
></blockquote
></p
>
4632 <p
>The next step is mounting the file system to make the storage available.
4634 <p
><blockquote
><pre
>
4635 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4636 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4637 Using
4 upload threads.
4638 Downloading and decompressing metadata...
4648 Mounting filesystem...
4650 Filesystem Size Used Avail Use% Mounted on
4651 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4653 </pre
></blockquote
></p
>
4655 <p
>The file system is now ready for use. I use rsync to store my
4656 backups in it, and as the metadata used by rsync is downloaded at
4657 mount time, no network traffic (and storage cost) is triggered by
4658 running rsync. To unmount, one should not use the normal umount
4659 command, as this will not flush the cache to the cloud storage, but
4660 instead running the umount.s3ql command like this:
4662 <p
><blockquote
><pre
>
4665 </pre
></blockquote
></p
>
4667 <p
>There is a fsck command available to check the file system and
4668 correct any problems detected. This can be used if the local server
4669 crashes while the file system is mounted, to reset the
"already
4670 mounted
" flag. This is what it look like when processing a working
4671 file system:
</p
>
4673 <p
><blockquote
><pre
>
4674 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4675 Using cached metadata.
4676 File system seems clean, checking anyway.
4677 Checking DB integrity...
4678 Creating temporary extra indices...
4679 Checking lost+found...
4680 Checking cached objects...
4681 Checking names (refcounts)...
4682 Checking contents (names)...
4683 Checking contents (inodes)...
4684 Checking contents (parent inodes)...
4685 Checking objects (reference counts)...
4686 Checking objects (backend)...
4687 ..processed
5000 objects so far..
4688 ..processed
10000 objects so far..
4689 ..processed
15000 objects so far..
4690 Checking objects (sizes)...
4691 Checking blocks (referenced objects)...
4692 Checking blocks (refcounts)...
4693 Checking inode-block mapping (blocks)...
4694 Checking inode-block mapping (inodes)...
4695 Checking inodes (refcounts)...
4696 Checking inodes (sizes)...
4697 Checking extended attributes (names)...
4698 Checking extended attributes (inodes)...
4699 Checking symlinks (inodes)...
4700 Checking directory reachability...
4701 Checking unix conventions...
4702 Checking referential integrity...
4703 Dropping temporary indices...
4704 Backing up old metadata...
4714 Compressing and uploading metadata...
4715 Wrote
0.89 MB of compressed metadata.
4717 </pre
></blockquote
></p
>
4719 <p
>Thanks to the cache, working on files that fit in the cache is very
4720 quick, about the same speed as local file access. Uploading large
4721 amount of data is to me limited by the bandwidth out of and into my
4722 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4723 which is very close to my upload speed, and downloading the same
4724 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4725 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4726 network, not the file system code. I do not know what a good cache
4727 size would be, but suspect that the cache should e larger than your
4728 working set.
</p
>
4730 <p
>I mentioned that only one machine can mount the file system at the
4731 time. If another machine try, it is told that the file system is
4734 <p
><blockquote
><pre
>
4735 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4736 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4737 Using
8 upload threads.
4738 Backend reports that fs is still mounted elsewhere, aborting.
4740 </pre
></blockquote
></p
>
4742 <p
>The file content is uploaded when the cache is full, while the
4743 metadata is uploaded once every
24 hour by default. To ensure the
4744 file system content is flushed to the cloud, one can either umount the
4745 file system, or ask S3QL to flush the cache and metadata using
4748 <p
><blockquote
><pre
>
4749 # s3qlctrl upload-meta /s3ql
4750 # s3qlctrl flushcache /s3ql
4752 </pre
></blockquote
></p
>
4754 <p
>If you are curious about how much space your data uses in the
4755 cloud, and how much compression and deduplication cut down on the
4756 storage usage, you can use s3qlstat on the mounted file system to get
4759 <p
><blockquote
><pre
>
4761 Directory entries:
9141
4764 Total data size:
22049.38 MB
4765 After de-duplication:
21955.46 MB (
99.57% of total)
4766 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4767 Database size:
2.39 MB (uncompressed)
4768 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4770 </pre
></blockquote
></p
>
4772 <p
>I mentioned earlier that there are several possible suppliers of
4773 storage. I did not try to locate them all, but am aware of at least
4774 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4775 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4776 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4777 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4778 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4779 accept payment in Bitcoin. Pick one that suit your need. Some of
4780 them provide several GiB of free storage, but the prize models are
4781 quite different and you will have to figure out what suits you
4784 <p
>While researching this blog post, I had a look at research papers
4785 and posters discussing the S3QL file system. There are several, which
4786 told me that the file system is getting a critical check by the
4787 science community and increased my confidence in using it. One nice
4789 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4790 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4791 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4792 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4793 and Pamela Smith. Please have a look.
</p
>
4795 <p
>Given my problems with different file systems earlier, I decided to
4796 check out the mounted S3QL file system to see if it would be usable as
4797 a home directory (in other word, that it provided POSIX semantics when
4798 it come to locking and umask handling etc). Running
4799 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4800 test code to check file system semantics
</a
>, I was happy to discover that
4801 no error was found. So the file system can be used for home
4802 directories, if one chooses to do so.
</p
>
4804 <p
>If you do not want a locally file system, and want something that
4805 work without the Linux fuse file system, I would like to mention the
4806 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4807 provide locally encrypted backup using a command line client. It have
4808 a nicer access control system, where one can split out read and write
4809 access, allowing some systems to write to the backup and others to
4810 only read from it.
</p
>
4812 <p
>As usual, if you use Bitcoin and want to show your support of my
4813 activities, please send Bitcoin donations to my address
4814 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4819 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4820 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4821 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4822 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4823 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4824 project
</a
> is working on providing the software and hardware for
4825 making it easy for non-technical people to host their data and
4826 communication at home, and being able to communicate with their
4827 friends and family encrypted and away from prying eyes. It has been
4828 going on for a while, and is slowly progressing towards a new test
4829 release (
0.2).
</p
>
4831 <p
>And what day could be better than the Pi day to announce that the
4832 new version will provide
"hard drive
" / SD card / USB stick images for
4833 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4834 system), and can also be installed using a Debian installer preseed
4835 file. The Debian based Freedombox is now based on Debian Jessie,
4836 where most of the needed packages used are already present. Only one,
4837 the freedombox-setup package, is missing. To try to build your own
4838 boot image to test the current status, fetch the freedom-maker scripts
4840 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4841 with a user with sudo access to become root:
4844 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4846 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4847 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4849 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4852 <p
>Root access is needed to run debootstrap and mount loopback
4853 devices. See the README for more details on the build. If you do not
4854 want all three images, trim the make line. But note that thanks to
<a
4855 href=
"https://bugs.debian.org/
741407">a race condition in
4856 vmdebootstrap
</a
>, the build might fail without the patch to the
4857 kpartx call.
</p
>
4859 <p
>If you instead want to install using a Debian CD and the preseed
4860 method, boot a Debian Wheezy ISO and use this boot argument to load
4861 the preseed values:
</p
>
4864 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4867 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4868 recently introduced bug in apt in Jessie
</a
>, the installer will
4869 currently hang while setting up APT sources. Killing the
4870 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4871 installation will get the installation going. This affect all
4872 installations in Jessie, and I expect it will be fixed soon.
</p
>
4874 <p
>Give it a go and let us know how it goes on the mailing list, and help
4875 us get the new release published. :) Please join us on
4876 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4877 irc.debian.org)
</a
> and
4878 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4879 mailing list
</a
> if you want to help make this vision come true.
</p
>
4884 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4885 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4886 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4887 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4888 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4889 innetgr tools, because I needed them in
4890 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4891 ng-utils, and it has served me well. I placed the project under the
4892 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4893 repository. But many years ago, the CVS repository was dropped (lost,
4894 not migrated to new hardware, not sure), and the project have lacked a
4895 proper home since then.
</p
>
4897 <p
>Last summer, I had a look at the package and made a new release
4898 fixing a irritating crash bug, but was unable to store the changes in
4899 a proper source control system. I applied for a project on
4900 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4901 to follow up on it. Until today. :)
</p
>
4903 <p
>After many hours of cleaning and migration, the ng-utils project
4904 now have a new home, and a git repository with the highlight of the
4905 history of the project. I published all release tarballs and imported
4906 them into the git repository. As the project is really stable and not
4907 expected to gain new features any time soon, I decided to make a new
4908 release and call it
1.0. Visit the new project home on
4909 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4910 if you want to check it out. The new version is also uploaded into
4911 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4916 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4917 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4918 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4919 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4920 <description><p
>A few days ago I decided to try to help the Hurd people to get
4921 their changes into sysvinit, to allow them to use the normal sysvinit
4922 boot system instead of their old one. This follow up on the
4923 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4924 Google Summer of Code work
</a
> done last summer by Justus Winter to
4925 get Debian on Hurd working more like Debian on Linux. To get started,
4926 I downloaded a prebuilt hard disk image from
4927 <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
>,
4928 and started it using virt-manager.
</p
>
4930 <p
>The first think I had to do after logging in (root without any
4931 password) was to get the network operational. I followed
4932 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4933 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4934 commands as root to get the machine to accept a IP address from the
4935 kvm internal DHCP server:
</p
>
4937 <p
><blockquote
><pre
>
4938 settrans -fgap /dev/netdde /hurd/netdde
4939 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4940 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4942 </pre
></blockquote
></p
>
4944 <p
>After this, the machine had internet connectivity, and I could
4945 upgrade it and install the sysvinit packages from experimental and
4946 enable it as the default boot system in Hurd.
</p
>
4948 <p
>But before I did that, I set a password on the root user, as ssh is
4949 running on the machine it for ssh login to work a password need to be
4950 set. Also, note that a bug somewhere in openssh on Hurd block
4951 compression from working. Remember to turn that off on the client
4954 <p
>Run these commands as root to upgrade and test the new sysvinit
4957 <p
><blockquote
><pre
>
4958 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4959 deb http://http.debian.net/debian/ experimental main
4962 apt-get dist-upgrade
4963 apt-get install -t experimental initscripts sysv-rc sysvinit \
4964 sysvinit-core sysvinit-utils
4965 update-alternatives --config runsystem
4966 </pre
></blockquote
></p
>
4968 <p
>To reboot after switching boot system, you have to use
4969 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4970 yet a sysvinit process able to receive the signals from the normal
4971 'reboot
' command. After switching to sysvinit as the boot system,
4972 upgrading every package and rebooting, the network come up with DHCP
4973 after boot as it should, and the settrans/pkill hack mentioned at the
4974 start is no longer needed. But for some strange reason, there are no
4975 longer any login prompt in the virtual console, so I logged in using
4978 <p
>Note that there are some race conditions in Hurd making the boot
4979 fail some times. No idea what the cause is, but hope the Hurd porters
4980 figure it out. At least Justus said on IRC (#debian-hurd on
4981 irc.debian.org) that they are aware of the problem. A way to reduce
4982 the impact is to upgrade to the Hurd packages built by Justus by
4983 adding this repository to the machine:
</p
>
4985 <p
><blockquote
><pre
>
4986 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4987 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4989 </pre
></blockquote
></p
>
4991 <p
>At the moment the prebuilt virtual machine get some packages from
4992 http://ftp.debian-ports.org/debian, because some of the packages in
4993 unstable do not yet include the required patches that are lingering in
4994 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4996 <p
><blockquote
><pre
>
4997 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4998 i emacs - GNU Emacs editor (metapackage)
4999 i gdb - GNU Debugger
5000 i hurd-recommended - Miscellaneous translators
5001 i isc-dhcp-client - ISC DHCP client
5002 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5003 i libc-bin - Embedded GNU C Library: Binaries
5004 i libc-dev-bin - Embedded GNU C Library: Development binaries
5005 i libc0.3 - Embedded GNU C Library: Shared libraries
5006 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5007 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5008 i multiarch-support - Transitional package to ensure multiarch compatibilit
5009 i A x11-common - X Window System (X.Org) infrastructure
5010 i xorg - X.Org X Window System
5011 i A xserver-xorg - X.Org X server
5012 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5014 </pre
></blockquote
></p
>
5016 <p
>All in all, testing hurd has been an interesting experience. :)
5017 X.org did not work out of the box and I never took the time to follow
5018 the porters instructions to fix it. This time I was interested in the
5019 command line stuff.
<p
>
5024 <title>New chrpath release
0.16</title>
5025 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
5026 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
5027 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
5028 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
5029 find problems in C, C++ and Java code using static source code
5030 analysis. It can detect a lot of different problems, and is very
5031 useful to find memory and locking bugs in the error handling part of
5032 the source. The company behind it provide
5033 <a href=
"https://scan.coverity.com/
">check of free software projects as
5034 a community service
</a
>, and many hundred free software projects are
5035 already checked. A few days ago I decided to have a closer look at
5036 the Coverity system, and discovered that the
5037 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
5038 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
5039 projects I am involved with was already registered. But these are
5040 fairly big, and I would also like to have a small and easy project to
5041 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
5042 checking of the chrpath project
</a
>. It was
5043 added to the checker and discovered seven potential defects. Six of
5044 these were real, mostly resource
"leak
" when the program detected an
5045 error. Nothing serious, as the resources would be released a fraction
5046 of a second later when the program exited because of the error, but it
5047 is nice to do it right in case the source of the program some time in
5048 the future end up in a library. Having fixed all defects and added
5049 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
5050 mailing list for the chrpath developers
</a
>, I decided it was time to
5051 publish a new release. These are the release notes:
</p
>
5053 <p
>New in
0.16 released
2014-
01-
14:
</p
>
5057 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
5058 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
5059 <li
>Mention new project mailing list in the documentation.
</li
>
5064 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5065 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
5066 project if something is wrong with the new release. The test suite
5067 did not discover any old errors, so if you find a new one, please also
5068 include a test suite check.
</p
>
5073 <title>New chrpath release
0.15</title>
5074 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
5075 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
5076 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
5077 <description><p
>After many years break from the package and a vain hope that
5078 development would be continued by someone else, I finally pulled my
5079 acts together this morning and wrapped up a new release of chrpath,
5080 the command line tool to modify the rpath and runpath of already
5081 compiled ELF programs. The update was triggered by the persistence of
5082 Isha Vishnoi at IBM, which needed a new config.guess file to get
5083 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
5084 is working on. I checked the
5085 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
5086 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
5087 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
5088 packages for interesting patches (failed to find the source from
5089 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5090 These are the release notes:
</p
>
5092 <p
>New in
0.15 released
2013-
11-
24:
</p
>
5096 <li
>Updated config.sub and config.guess from the GNU project to work
5097 with newer architectures. Thanks to isha vishnoi for the heads
5100 <li
>Updated README with current URLs.
</li
>
5102 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5103 Matthias Klose.
</li
>
5105 <li
>Added missing help for -k|--keepgoing option, using patch by
5106 Petr Machata found in Fedora.
</li
>
5108 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
5109 .dynamic is a NULL terminated string. Based on patch found in
5110 Fedora credited Axel Thimm and Christian Krause.
</li
>
5115 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5116 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
5117 project if something is wrong with the new release. The test suite
5118 did not discover any old errors, so if you find a new one, please also
5119 include a testsuite check.
</p
>
5124 <title>Debian init.d boot script example for rsyslog
</title>
5125 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
5126 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
5127 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
5128 <description><p
>If one of the points of switching to a new init system in Debian is
5129 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
5130 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
5131 init.d scripts at all. Here is an example init.d script, ie a rewrite
5132 of /etc/init.d/rsyslog:
</p
>
5134 <p
><pre
>
5135 #!/lib/init/init-d-script
5138 # Required-Start: $remote_fs $time
5139 # Required-Stop: umountnfs $time
5140 # X-Stop-After: sendsigs
5141 # Default-Start:
2 3 4 5
5142 # Default-Stop:
0 1 6
5143 # Short-Description: enhanced syslogd
5144 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5145 # It is quite compatible to stock sysklogd and can be
5146 # used as a drop-in replacement.
5148 DESC=
"enhanced syslogd
"
5149 DAEMON=/usr/sbin/rsyslogd
5150 </pre
></p
>
5152 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
5153 script was
137 lines, and the above is just
15 lines, most of it meta
5154 info/comments.
</p
>
5156 <p
>How to do this, you ask? Well, one create a new script
5157 /lib/init/init-d-script looking something like this:
5159 <p
><pre
>
5162 # Define LSB log_* functions.
5163 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
5164 # and status_of_proc is working.
5165 . /lib/lsb/init-functions
5168 # Function that starts the daemon/service
5174 #
0 if daemon has been started
5175 #
1 if daemon was already running
5176 #
2 if daemon could not be started
5177 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
5179 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5182 # Add code here, if necessary, that waits for the process to be ready
5183 # to handle requests from services started subsequently which depend
5184 # on this one. As a last resort, sleep for some time.
5188 # Function that stops the daemon/service
5193 #
0 if daemon has been stopped
5194 #
1 if daemon was already stopped
5195 #
2 if daemon could not be stopped
5196 # other if a failure occurred
5197 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
5198 RETVAL=
"$?
"
5199 [
"$RETVAL
" =
2 ]
&& return
2
5200 # Wait for children to finish too if this is a daemon that forks
5201 # and if the daemon is only ever run from this initscript.
5202 # If the above conditions are not satisfied then add some other code
5203 # that waits for the process to drop all resources that could be
5204 # needed by services started subsequently. A last resort is to
5205 # sleep for some time.
5206 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
5207 [
"$?
" =
2 ]
&& return
2
5208 # Many daemons don
't delete their pidfiles when they exit.
5210 return
"$RETVAL
"
5214 # Function that sends a SIGHUP to the daemon/service
5218 # If the daemon can reload its configuration without
5219 # restarting (for example, when it is sent a SIGHUP),
5220 # then implement that here.
5222 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
5227 scriptbasename=
"$(basename $
1)
"
5228 echo
"SN: $scriptbasename
"
5229 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
5230 script=
"$
1"
5237 NAME=$(basename $DAEMON)
5238 PIDFILE=/var/run/$NAME.pid
5240 # Exit if the package is not installed
5241 #[ -x
"$DAEMON
" ] || exit
0
5243 # Read configuration variable file if it is present
5244 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
5246 # Load the VERBOSE setting and other rcS variables
5249 case
"$
1" in
5251 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
5253 case
"$?
" in
5254 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5255 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5259 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
5261 case
"$?
" in
5262 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5263 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5267 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5269 #reload|force-reload)
5271 # If do_reload() is not implemented then leave this commented out
5272 # and leave
'force-reload
' as an alias for
'restart
'.
5274 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5278 restart|force-reload)
5280 # If the
"reload
" option is implemented then remove the
5281 #
'force-reload
' alias
5283 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5285 case
"$?
" in
5288 case
"$?
" in
5290 1) log_end_msg
1 ;; # Old process is still running
5291 *) log_end_msg
1 ;; # Failed to start
5301 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5307 </pre
></p
>
5309 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5310 lot. I did not really polish the approach, so it might not always
5311 work out of the box, but you get the idea. I did not try very hard to
5312 optimize it nor make it more robust either.
</p
>
5314 <p
>A better argument for switching init system in Debian than reducing
5315 the size of init scripts (which is a good thing to do anyway), is to
5316 get boot system that is able to handle the kernel events sensibly and
5317 robustly, and do not depend on the boot to run sequentially. The boot
5318 and the kernel have not behaved sequentially in years.
</p
>
5323 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5324 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5325 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5326 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5327 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5328 remote display access is the preferred solution with oVirt and RedHat
5329 Enterprise Virtualization, and I was sad to discover the other day
5330 that the browser plugin needed to use these systems seamlessly was
5331 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5332 for a package
</a
> was from
2012-
04-
10 with no progress since
5333 2013-
04-
01, so I decided to wrap up a package based on the great work
5334 from Cajus Pollmeier and put it in a collab-maint maintained git
5335 repository to get a package I could use. I would very much like
5336 others to help me maintain the package (or just take over, I do not
5337 mind), but as no-one had volunteered so far, I just uploaded it to
5338 NEW. I hope it will be available in Debian in a few days.
</p
>
5340 <p
>The source is now available from
5341 <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
>
5346 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5347 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5348 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5349 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5350 <description><p
>The
5351 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5352 program is a a very nice system to create virtual machine images. It
5353 create a image file, add a partition table, mount it and run
5354 debootstrap in the mounted directory to create a Debian system on a
5355 stick. Yesterday, I decided to try to teach it how to make images for
5356 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5357 of a plan to simplify the build system for
5358 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5359 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5360 the virtualbox images, but its current build system made multistrap
5361 based system for Dreamplug images, and it is lacking support for
5362 Raspberry Pi.
</p
>
5364 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5365 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5366 code and adjusted it to be able to build armel images on my amd64
5367 Debian laptop. I ended up giving vmdebootstrap five new options,
5368 allowing me to replicate the image creation process I use to make
5369 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5370 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5371 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5372 call debootstrap with --foreign and to copy the handler into the
5373 generated chroot before running the second stage. This allow
5374 vmdebootstrap to create armel images on an amd64 host. Next I added
5375 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5376 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5377 given file system type, allowing me to create an image with a vfat
5378 partition for the /boot/ stuff. I also added a
<tt
>--variant
5379 variant
</tt
> option to allow me to create smaller images without the
5380 Debian base system packages installed. Finally, I added an option
5381 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5382 as a boot loader. It is not needed on the Raspberry Pi and probably
5383 most other non-x86 architectures. The changes were accepted by the
5384 upstream author of vmdebootstrap yesterday and today, and is now
5386 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5387 upstream project page
</a
>.
</p
>
5389 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5390 create a small script (the customize script) to add the non-free
5391 binary blob needed to boot the Raspberry Pi and the APT source
5394 <p
><pre
>
5396 set -e # Exit on first error
5397 rootdir=
"$
1"
5398 cd
"$rootdir
"
5399 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5400 deb http://http.debian.net/debian/ jessie main contrib non-free
5402 # Install non-free binary blob needed to boot Raspberry Pi. This
5403 # install a kernel somewhere too.
5404 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5405 -O $rootdir/usr/bin/rpi-update
5406 chmod a+x $rootdir/usr/bin/rpi-update
5407 mkdir -p $rootdir/lib/modules
5408 touch $rootdir/boot/start.elf
5409 chroot $rootdir rpi-update
5410 </pre
></p
>
5412 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5413 to build the image:
</p
>
5416 sudo ./vmdebootstrap \
5419 --distribution jessie \
5420 --mirror http://http.debian.net/debian \
5429 --root-password raspberry \
5430 --hostname raspberrypi \
5431 --foreign /usr/bin/qemu-arm-static \
5432 --customize `pwd`/customize \
5434 --package git-core \
5435 --package binutils \
5436 --package ca-certificates \
5439 </pre
></p
>
5441 <p
>The list of packages being installed are the ones needed by
5442 rpi-update to make the image bootable on the Raspberry Pi, with the
5443 exception of netbase, which is needed by debootstrap to find
5444 /etc/hosts with the minbase variant. I really wish there was a way to
5445 set up an Raspberry Pi using only packages in the Debian archive, but
5446 that is not possible as far as I know, because it boots from the GPU
5447 using a non-free binary blob.
</p
>
5449 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5450 probably a few others installed. I have not checked the complete
5451 build dependency list.
</p
>
5453 <p
>The resulting image will not use the hardware floating point unit
5454 on the Raspberry PI, because the armel architecture in Debian is not
5455 optimized for that use. So the images created will be a bit slower
5456 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5461 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5462 <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>
5463 <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>
5464 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5465 <description><p
>The last few days I came across a few good causes that should get
5466 wider attention. I recommend signing and donating to each one of
5469 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5470 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5471 Women program which is a Google Summer of Code like initiative to get
5472 more women involved in free software. One debian sponsor has offered
5473 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5474 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5475 hope you will to. :)
</p
>
5477 <p
>And the Electronic Frontier Foundation just announced plans to
5478 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5479 documentaries about the excessive spying
</a
> on every Internet user that
5480 take place these days, and their need to fund the work. I
've already
5481 donated. Are you next?
</p
>
5483 <p
>For my Norwegian audience, the organisation Studentenes og
5484 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5485 statement under the heading
5486 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5487 Access
</a
> for those of us asking for more focus on open access in the
5488 Norwegian government. So far
499 signatures. I hope you will sign it
5494 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5495 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5496 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5497 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5498 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5499 project
</a
> have been going on for a while, and have presented the
5500 vision, ideas and solution several places. Here is a little
5501 collection of videos of talks and presentation of the project.
</p
>
5505 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5506 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5508 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5509 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5511 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5512 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5513 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5514 (Youtube)
</li
>
5516 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5517 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5519 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5520 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5522 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5523 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5524 York City in
2012</a
> (Youtube)
</li
>
5526 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5527 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5528 (Youtube)
</li
>
5530 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5531 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5533 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5534 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5536 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5537 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5538 2013</a
> (Youtube)
</li
>
5542 <p
>A larger list is available from
5543 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5544 Freedombox Wiki
</a
>.
</p
>
5546 <p
>On other news, I am happy to report that Freedombox based on Debian
5547 Jessie is coming along quite well, and soon both Owncloud and using
5548 Tor should be available for testers of the Freedombox solution. :) In
5549 a few weeks I hope everything needed to test it is included in Debian.
5550 The withsqlite package is already in Debian, and the plinth package is
5551 pending in NEW. The third and vital part of that puzzle is the
5552 metapackage/setup framework, which is still pending an upload. Join
5553 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5554 (#freedombox on irc.debian.org)
</a
> and
5555 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5556 mailing list
</a
> if you want to help make this vision come true.
</p
>
5561 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5562 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5563 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5564 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5565 <description><p
>I was introduced to the
5566 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5567 in
2010, when Eben Moglen presented his vision about serving the need
5568 of non-technical people to keep their personal information private and
5569 within the legal protection of their own homes. The idea is to give
5570 people back the power over their network and machines, and return
5571 Internet back to its intended peer-to-peer architecture. Instead of
5572 depending on a central service, the Freedombox will give everyone
5573 control over their own basic infrastructure.
</p
>
5575 <p
>I
've intended to join the effort since then, but other tasks have
5576 taken priority. But this summers nasty news about the misuse of trust
5577 and privilege exercised by the
"western
" intelligence gathering
5578 communities increased my eagerness to contribute to a point where I
5579 actually started working on the project a while back.
</p
>
5581 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5582 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5583 create a simple and cheap Debian based appliance that anyone can hook
5584 up in their home and get access to secure and private services and
5585 communication. The initial deployment platform have been the
5586 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5587 which is a piece of hardware I do not own. So to be able to test what
5588 the current Freedombox setup look like, I had to come up with a way to install
5589 it on some hardware I do have access to. I have rewritten the
5590 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5591 image build framework to use .deb packages instead of only copying
5592 setup into the boot images, and thanks to this rewrite I am able to
5593 set up any machine supported by Debian Wheezy as a Freedombox, using
5594 the previously mentioned deb (and a few support debs for packages
5595 missing in Debian).
</p
>
5597 <p
>The current Freedombox setup consist of a set of bootstrapping
5599 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5600 and a administrative web interface
5601 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5602 withsqlite), as well as a privacy enhancing proxy based on
5603 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5604 (freedombox-privoxy). There is also a web/javascript based XMPP
5605 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5606 trying (unsuccessfully so far) to talk to the XMPP server
5607 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5608 web interface is pluggable, and the goal is to use it to enable OpenID
5609 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5610 this is really working yet, see
5611 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5612 project TODO
</a
> for links to GIT repositories. Most of the code is
5613 on github at the moment. The HTTP proxy is operational out of the
5614 box, and the admin web interface can be used to add/remove plinth
5615 users. I
've not been able to do anything else with it so far, but
5616 know there are several branches spread around github and other places
5617 with lots of half baked features.
</p
>
5619 <p
>Anyway, if you want to have a look at the current state, the
5620 following recipes should work to give you a test machine to poke
5623 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5627 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5628 <li
>Boot from it, either as CD or USB stick.
</li
>
5629 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5630 to the Debian installer:
<p
>
5631 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5633 <li
>Answer the few language/region/password questions and pick disk to
5634 install on.
</li
>
5636 <li
>When the installation is finished and the machine have rebooted a
5637 few times, your Freedombox is ready for testing.
</li
>
5641 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5645 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5646 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5647 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5649 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5650 </pre
></li
>
5651 <li
><p
>Run this as root:
</p
>
5653 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5656 apt-get install freedombox-setup
5657 /usr/lib/freedombox/setup
5658 </pre
></li
>
5659 <li
>Reboot into your freshly created Freedombox.
</li
>
5663 <p
>You can test it on other architectures too, but because the
5664 freedombox-privoxy package is binary, it will only work as intended on
5665 the architectures where I have had time to build the binary and put it
5666 in my APT repository. But do not let this stop you. It is only a
5667 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5669 <p
>Note that by default Freedombox is a DHCP server on the
5670 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5671 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5672 disable
</tt
>" as root.
</p
>
5674 <p
>Please let me know if this works for you, or if you have any
5675 problems. We gather on the IRC channel
5676 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5677 irc.debian.org and the
5678 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5679 mailing list
</a
>.
</p
>
5681 <p
>Once you get your freedombox operational, you can visit
5682 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5683 welcome screen (dead end - do not be surprised if you are unable to
5684 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5685 to look at the rest of plinth. The default user is
'admin
' and the
5686 default password is
'secret
'.
</p
>
5691 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5692 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5693 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5694 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5695 <description><p
>Earlier, I reported about
5696 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5697 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5698 told by IBM that the original disk should be thrown away. And as
5699 there no longer was a problem if I bricked the firmware, I decided
5700 today to try to install Intel firmware to replace the Lenovo firmware
5701 currently on the disk.
</p
>
5703 <p
>I searched the Intel site for firmware, and found
5704 <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
>
5705 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5706 according to the site should contain the latest firmware for SSD
5707 disks. I inserted the broken disk in one of my spare laptops and
5708 booted the ISO from a USB stick. The disk was recognized, but the
5709 program claimed the newest firmware already were installed and refused
5710 to insert any Intel firmware. So no change, and the disk is still
5711 unable to handle write load. :( I guess the only way to get them
5712 working would be if Lenovo releases new firmware. No idea how likely
5713 that is. Anyway, just blogging about this test for completeness. I
5714 got a working Samsung disk, and see no point in spending more time on
5715 the broken disks.
</p
>
5720 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5721 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5722 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5723 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5724 <description><p
>Today I switched to
5725 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5726 new laptop
</a
>. I
've previously written about the problems I had with
5727 my new Thinkpad X230, which was delivered with an
5728 <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
5729 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5730 sustained writes. My hardware supplier have been very forthcoming in
5731 trying to find a solution, and after first trying with another
5732 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5733 disk instead to fix it once and for all. The Samsung disk survived
5734 the installation of Debian with encrypted disks (filling the disk with
5735 random data during installation killed the first two), and I thus
5736 decided to trust it with my data. I have installed it as a Debian Edu
5737 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5738 server at home using Kerberos and LDAP, and will use it as my work
5739 station from now on.
</p
>
5741 <p
>As this is a solid state disk with no moving parts, I believe the
5742 Debian Wheezy default installation need to be tuned a bit to increase
5743 performance and increase life time of the disk. The Linux kernel and
5744 user space applications do not yet adjust automatically to such
5745 environment. To make it easier for my self, I created a draft Debian
5746 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5747 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5748 for the ssd-setup package
</a
> is available from collab-maint, and it
5749 is set up to adjust the setup of the machine by just installing the
5750 package. If there is any non-SSD disk in the machine, the package
5751 will refuse to install, as I did not try to write any logic to sort
5752 file systems in SSD and non-SSD file systems.
</p
>
5754 <p
>I consider the package a draft, as I am a bit unsure how to best
5755 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5756 where I set up the machine with one large encrypted partition (in
5757 addition to /boot), put LVM on top of this and set up partitions on
5758 top of this again. See the README file in the package source for the
5759 references I used to pick the settings. At the moment these
5760 parameters are tuned:
</p
>
5764 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5765 (adding discard to /etc/crypttab)
</li
>
5767 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5768 this case a cryptsetup partition) by changing issue_discards from
5769 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5771 <li
>Set relatime as a file system option for ext3 and ext4 file
5774 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5775 /etc/fstab.
</li
>
5777 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5779 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5780 cron.daily).
</li
>
5782 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5783 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5787 <p
>During installation, I cancelled the part where the installer fill
5788 the disk with random data, as this would kill the SSD performance for
5789 little gain. My goal with the encrypted file system is to ensure
5790 those stealing my laptop end up with a brick and not a working
5791 computer. I have no hope in keeping the really resourceful people
5792 from getting the data on the disk (see
5793 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5794 Thus I concluded that adding the discard option to crypttab is the
5795 right thing to do.
</p
>
5797 <p
>I considered using the noop I/O scheduler, as several recommended
5798 it for SSD, but others recommended deadline and a benchmark I found
5799 indicated that deadline might be better for interactive use.
</p
>
5801 <p
>I also considered using the
'discard
' file system option for ext3
5802 and ext4, but read that it would give a performance hit ever time a
5803 file is removed, and thought it best to that that slowdown once a day
5804 instead of during my work.
</p
>
5806 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5807 this is already done by Debian Edu.
</p
>
5809 <p
>I have not yet started on the user space tuning. I expect
5810 iceweasel need some tuning, and perhaps other applications too, but
5811 have not yet had time to investigate those parts.
</p
>
5813 <p
>The package should work on Ubuntu too, but I have not yet tested it
5816 <p
>As for the answer to the question in the title of this blog post,
5817 as far as I know, the only solution I know about is to replace the
5818 disk. It might be possible to flash it with Intel firmware instead of
5819 the Lenovo firmware. But I have not tried and did not want to do so
5820 without approval from Lenovo as I wanted to keep the warranty on the
5821 disk until a solution was found and they wanted the broken disks
5827 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5828 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5829 <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>
5830 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5831 <description><p
>A few days ago, I wrote about
5832 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5833 problems I experienced with my new X230 and its SSD disk
</a
>, which
5834 was dying during installation because it is unable to cope with
5835 sustained write. My supplier is in contact with
5836 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5837 replacement disk to try to fix the problem. They decided to send an
5838 identical model, so my hopes for a permanent fix was slim.
</p
>
5840 <p
>Anyway, today I got the replacement disk and tried to install
5841 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5842 same firmware version as the original. This time my hope raised
5843 slightly as the installation progressed, as the original disk used to
5844 die after
4-
7% of the disk was written to, while this time it kept
5845 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5846 died again and I was back on square one. I still do not have a new
5847 laptop with a disk I can trust. I can not live with a disk that might
5848 lock up when I download a new
5849 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5850 other large files. I look forward to hearing from my supplier with
5851 the next proposal from Lenovo.
</p
>
5853 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5854 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5855 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5856 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5857 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5858 P/N
45N8295, P0C38732.
</p
>
5860 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5861 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5862 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5863 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5864 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5865 P/N
45N8295, P0C38732.
</p
>
5867 <p
>The only difference is in the first number (serial number?), ISN,
5868 SA, date and WNPP values. Mentioning all the details here in case
5869 someone is able to use the information to find a way to identify the
5870 failing disk among working ones (if any such working disk actually
5876 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5877 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5879 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5880 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5881 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5882 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5883 member assosiation NUUG
</a
> and
5884 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5885 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5886 Bitraf
</a
>.
</p
>
5888 <p
>It starts
10:
00 and continue until late evening. Everyone is
5889 welcome, and there is no fee to participate. There is on the other
5890 hand limited space, and only room for
30 people. Please put your name
5891 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5892 wiki page
</a
> if you plan to join us.
</p
>
5897 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5898 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5900 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5901 <description><p
>Half a year ago, I reported that I had to find a
5902 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5903 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5904 time to spend on it, and it took a while to find a model I believe
5905 will do the job, but two days ago the replacement finally arrived. I
5907 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5908 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5909 a roaming workstation, and it seemed to work flawlessly. But my
5910 second installation with encrypted disk was not as successful. More
5911 on that below.
</p
>
5913 <p
>I had a hard time trying to track down a good laptop, as my most
5914 important requirements (robust and with a good keyboard) are never
5915 listed in the feature list. But I did get good help from the search
5916 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5917 allowed me to limit the list of interesting laptops based on my other
5918 requirements. A bit surprising that SSD disk are not disks according
5919 to that search interface, so I had to drop specifying the number of
5920 disks from my search parameters. I also asked around among friends to
5921 get their impression on keyboards and robustness.
</p
>
5923 <p
>So the new laptop arrived, and it is quite a lot wider than the
5924 X41. I am not quite convinced about the keyboard, as it is
5925 significantly wider than my old keyboard, and I have to stretch my
5926 hand a lot more to reach the edges. But the key response is fairly
5927 good and the individual key shape is fairly easy to handle, so I hope
5928 I will get used to it. My old X40 was starting to fail, and I really
5929 needed a new laptop now. :)
</p
>
5931 <p
>Turning off the touch pad was simple. All it took was a quick
5932 visit to the BIOS during boot it disable it.
</p
>
5934 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5935 lock up during load. And this happen when installing Debian Wheezy
5936 with encrypted disk, while the disk is being filled with random data.
5937 I also tested to install Ubuntu Raring, and it happen there too if I
5938 reenable the code to fill the disk with random data (it is disabled by
5939 default in Ubuntu). And the bug with is already known. It was
5940 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5941 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5942 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5943 kernel developers as
5944 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5945 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5946 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5947 Lenovo forums, both for
5948 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5949 2012-
11-
10</a
> and for
5950 <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
5951 03-
20-
2013</a
>. The problem do not only affect installation. The
5952 reports state that the disk lock up during use if many writes are done
5953 on the disk, so it is much no use to work around the installation
5954 problem and end up with a computer that can lock up at any moment.
5956 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5957 available
</a
> that will lock up the hard drive after running a few
5958 minutes by writing to a file.
</p
>
5960 <p
>I
've contacted my supplier and asked how to handle this, and after
5961 contacting PCHELP Norway (request
01D1FDP) which handle support
5962 requests for Lenovo, his first suggestion was to upgrade the disk
5963 firmware. Unfortunately there is no newer firmware available from
5964 Lenovo, as my disk already have the most recent one (version LF1i). I
5965 hope to hear more from him today and hope the problem can be
5971 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5972 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5973 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5974 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5975 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5976 trusty old Thinkpad X41. Unfortunately I did not have much time to
5977 spend on it, but today the replacement finally arrived. I ended up
5978 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5979 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5980 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5981 this, it is installing what I hope will be a more final installation,
5982 with a encrypted hard drive to ensure any dope head stealing it end up
5983 with an expencive door stop.
</p
>
5985 <p
>I had a hard time trying to track down a good laptop, as my most
5986 important requirements (robust and with a good keyboard) are never
5987 listed in the feature list. But I did get good help from the search
5988 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5989 allowed me to limit the list of interesting laptops based on my other
5990 requirements. A bit surprising that SSD disk are not disks, so I had
5991 to drop number of disks from my search parameters.
</p
>
5993 <p
>I am not quite convinced about the keyboard, as it is significantly
5994 wider than my old keyboard, and I have to stretch my hand a lot more
5995 to reach the edges. But the key response is fairly good and the
5996 individual key shape is fairly easy to handle, so I hope I will get
5997 used to it. My old X40 was starting to fail, and I really needed a
5998 new laptop now. :)
</p
>
6000 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
6005 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
6006 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
6007 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
6008 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
6009 <description><p
>It annoys me when the computer fail to do automatically what it is
6010 perfectly capable of, and I have to do it manually to get things
6011 working. One such task is to find out what firmware packages are
6012 needed to get the hardware on my computer working. Most often this
6013 affect the wifi card, but some times it even affect the RAID
6014 controller or the ethernet card. Today I pushed version
0.4 of the
6015 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
6016 including a new script isenkram-autoinstall-firmware handling the
6017 process of asking all the loaded kernel modules what firmware files
6018 they want, find debian packages providing these files and install the
6019 debian packages. Here is a test run on my laptop:
</p
>
6021 <p
><pre
>
6022 # isenkram-autoinstall-firmware
6023 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6024 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6025 info: locating packages with the requested firmware files
6026 info: Updating APT sources after adding non-free APT source
6027 info: trying to install firmware-ipw2x00
6030 Preconfiguring packages ...
6031 Selecting previously deselected package firmware-ipw2x00.
6032 (Reading database ...
259727 files and directories currently installed.)
6033 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6034 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
6036 </pre
></p
>
6038 <p
>When all the requested firmware is present, a simple message is
6039 printed instead:
</p
>
6041 <p
><pre
>
6042 # isenkram-autoinstall-firmware
6043 info: did not find any firmware files requested by loaded kernel modules. exiting
6045 </pre
></p
>
6047 <p
>It could use some polish, but it is already working well and saving
6048 me some time when setting up new machines. :)
</p
>
6050 <p
>So, how does it work? It look at the set of currently loaded
6051 kernel modules, and look up each one of them using modinfo, to find
6052 the firmware files listed in the module meta-information. Next, it
6053 download the Contents file from a nearby APT mirror, and search for
6054 the firmware files in this file to locate the package with the
6055 requested firmware file. If the package is in the non-free section, a
6056 non-free APT source is added and the package is installed using
6057 <tt
>apt-get install
</tt
>. The end result is a slightly better working
6060 <p
>I hope someone find time to implement a more polished version of
6061 this script as part of the hw-detect debian-installer module, to
6062 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
6063 #
655507</a
>. There really is no need to insert USB sticks with
6064 firmware during a PXE install when the packages already are available
6065 from the nearby Debian mirror.
</p
>
6070 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
6071 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
6072 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
6073 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
6074 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6075 the screen just turn black when Linux boot, either during installation
6076 or on first boot from the hard disk. I
've seen it once in a while the
6077 last few years, but only recently understood the cause. I
've seen it
6078 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6079 The reason seem to be in the wiring of some laptops. The system to
6080 control the screen background light is inverted, so when Linux try to
6081 turn the brightness fully on, it end up turning it off instead. I do
6082 not know which Linux drivers are affected, but this post is about the
6083 i915 driver used by the
6084 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6085 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
6087 <p
>The problem can be worked around two ways. Either by adding
6088 i915.invert_brightness=
1 as a kernel option, or by adding a file in
6089 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
6090 option when it load the i915 kernel module. On Debian and Ubuntu, it
6091 can be done by running these commands as root:
</p
>
6094 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
6095 update-initramfs -u -k all
6098 <p
>Since March
2012 there is
6099 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
6100 mechanism in the Linux kernel
</a
> to tell the i915 driver which
6101 hardware have this problem, and get the driver to invert the
6102 brightness setting automatically. To use it, one need to add a row in
6103 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
6104 intel_quirks array
</a
> in the driver source
6105 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
6106 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
6107 number (vendor number
8086 is assumed) and subdevice vendor and device
6110 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
6111 -vvnn
</tt
> for the video card in question:
</p
>
6113 <p
><pre
>
6114 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
6115 3rd Gen Core processor Graphics Controller [
8086:
0156] \
6116 (rev
09) (prog-if
00 [VGA controller])
6117 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
6118 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6119 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6120 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
6121 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
6123 Interrupt: pin A routed to IRQ
42
6124 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
6125 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
6126 Region
4: I/O ports at
4000 [size=
64]
6127 Expansion ROM at
<unassigned
> [disabled]
6128 Capabilities:
<access denied
>
6129 Kernel driver in use: i915
6130 </pre
></p
>
6132 <p
>The resulting intel_quirks entry would then look like this:
</p
>
6134 <p
><pre
>
6135 struct intel_quirk intel_quirks[] = {
6137 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6138 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
6141 </pre
></p
>
6143 <p
>According to the kernel module instructions (as seen using
6144 <tt
>modinfo i915
</tt
>), information about hardware needing the
6145 invert_brightness flag should be sent to the
6146 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
6147 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
6148 developers. But my email about the laptop sent
2013-
06-
03 have not
6150 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
6151 web archive for the mailing list
</a
>, so I suspect they do not accept
6152 emails from non-subscribers. Because of this, I sent my patch also to
6153 the Debian bug tracking system instead as
6154 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
6155 sure the patch is not lost.
</p
>
6157 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
6158 with this problem working properly with Linux. If you use Gnome, your
6159 worries should be over at this point. But if you use KDE, there is
6160 something in KDE ignoring the invert_brightness setting and turning on
6161 the screen during login. I
've reported it to Debian as
6162 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
6163 have no idea yet how to figure out exactly what subsystem is doing
6164 this. Perhaps you can help? Perhaps you know what the Gnome
6165 developers did to handle this, and this can give a clue to the KDE
6166 developers? Or you know where in KDE the screen brightness is changed
6167 during login? If so, please update the BTS report (or get in touch if
6168 you do not know how to update BTS).
</p
>
6170 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
6171 acpi_backlight=vendor, to disable ACPI backlight support completely,
6172 as the ACPI information on the machine is trash and it is better to
6173 leave it to the intel video driver to control the screen
6174 backlight.
</p
>
6179 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
6180 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
6181 <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>
6182 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
6183 <description><p
>Two days ago, I asked
6184 <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
6185 I could install Linux on a Packard Bell EasyNote LV computer
6186 preinstalled with Windows
8</a
>. I found a solution, but am horrified
6187 with the obstacles put in the way of Linux users on a laptop with UEFI
6188 and Windows
8.
</p
>
6190 <p
>I never found out if the cause of my problems were the use of UEFI
6191 secure booting or fast boot. I suspect fast boot was the problem,
6192 causing the firmware to boot directly from HD without considering any
6193 key presses and alternative devices, but do not know UEFI settings
6194 enough to tell.
</p
>
6196 <p
>There is no way to install Linux on the machine in question without
6197 opening the box and disconnecting the hard drive! This is as far as I
6198 can tell, the only way to get access to the firmware setup menu
6199 without accepting the Windows
8 license agreement. I am told (and
6200 found description on how to) that it is possible to configure the
6201 firmware setup once booted into Windows
8. But as I believe the terms
6202 of that agreement are completely unacceptable, accepting the license
6203 was never an alternative. I do not enter agreements I do not intend
6204 to follow.
</p
>
6206 <p
>I feared I had to return the laptops and ask for a refund, and
6207 waste many hours on this, but luckily there was a way to get it to
6208 work. But I would not recommend it to anyone planning to run Linux on
6209 it, and I have become sceptical to Windows
8 certified laptops. Is
6210 this the way Linux will be forced out of the market place, by making
6211 it close to impossible for
"normal
" users to install Linux without
6212 accepting the Microsoft Windows license terms? Or at least not
6213 without risking to loose the warranty?
</p
>
6215 <p
>I
've updated the
6216 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
6217 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
6218 do not have to struggle as much as I did to get Linux into the
6221 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6222 Michael Tokarev and others for feedback and ideas.
</p
>
6227 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
6228 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
6229 <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>
6230 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
6231 <description><p
>I
've run into quite a problem the last few days. I bought three
6232 new laptops for my parents and a few others. I bought Packard Bell
6233 Easynote LV to run Kubuntu on and use as their home computer. But I
6234 am completely unable to figure out how to install Linux on it. The
6235 computer is preinstalled with Windows
8, and I suspect it uses UEFI
6236 instead of a BIOS to boot.
</p
>
6238 <p
>The problem is that I am unable to get it to PXE boot, and unable
6239 to get it to boot the Linux installer from my USB stick. I have yet
6240 to try the DVD install, and still hope it will work. when I turn on
6241 the computer, there is no information on what buttons to press to get
6242 the normal boot menu. I expect to get some boot menu to select PXE or
6243 USB stick booting. When booting, it first ask for the language to
6244 use, then for some regional settings, and finally if I will accept the
6245 Windows
8 terms of use. As these terms are completely unacceptable to
6246 me, I have no other choice but to turn off the computer and try again
6247 to get it to boot the Linux installer.
</p
>
6249 <p
>I have gathered my findings so far on a Linlap page about the
6250 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6251 EasyNote LV
</a
> model. If you have any idea how to get Linux
6252 installed on this machine, please get in touch or update that wiki
6253 page. If I can
't find a way to install Linux, I will have to return
6254 the laptop to the seller and find another machine for my parents.
</p
>
6256 <p
>I wonder, is this the way Linux will be forced out of the market
6257 using UEFI and
"secure boot
" by making it impossible to install Linux
6258 on new Laptops?
</p
>
6263 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6264 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6265 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6266 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6267 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6268 an operating system based on Debian intended for use in schools. It
6269 contain a turn-key solution for the computer network provided to
6270 pupils in the primary schools. It provide both the central server,
6271 network boot servers and desktop environments with heaps of
6272 educational software. The project was founded almost
12 years ago,
6273 2001-
07-
02. If you want to support the project, which is in need for
6274 cash to fund developer gatherings and other project related activity,
6275 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6276 donate some money
</a
>.
6278 <p
>A topic that come up again and again on the Debian Edu mailing
6279 lists and elsewhere, is the question on how to transform a Debian or
6280 Ubuntu installation into a Debian Edu installation. It isn
't very
6281 hard, and last week I wrote a script to replicate the steps done by
6282 the Debian Edu installer.
</p
>
6284 <p
>The script,
6285 <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/
>
6286 in the debian-edu-config package, will go through these six steps and
6287 transform an existing Debian Wheezy or Ubuntu (untested) installation
6288 into a Debian Edu Workstation:
</p
>
6292 <li
>Add skolelinux related APT sources.
</li
>
6293 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6294 <li
>Install debian-edu-install to load preseeding values and pull in
6295 our configuration.
</li
>
6296 <li
>Preseed debconf database with profile setup in
6297 /etc/debian-edu/config, and run tasksel to install packages
6298 according to the profile specified in the config above,
6299 overriding some of the Debian automation machinery.
</li
>
6300 <li
>Run debian-edu-cfengine-D installation to configure everything
6301 that could not be done using preseeding.
</li
>
6302 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6306 <p
>There are some steps in the Debian Edu installation that can not be
6307 replicated like this. Disk partitioning and LVM setup, for example.
6308 So this script just assume there is enough disk space to install all
6309 the needed packages.
</p
>
6311 <p
>The script was created to help a Debian Edu student working on
6312 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6313 Debian Edu client, and using it he can take the existing
6314 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6315 transform it into a fully functioning Debian Edu Workstation (or
6316 Roaming Workstation, or whatever :).
</p
>
6318 <p
>The default setting in the script is to create a KDE Workstation.
6319 If a LXDE based Roaming workstation is wanted instead, modify the
6320 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6322 <p
><pre
>
6323 PROFILE=
"Roaming-Workstation
"
6324 DESKTOP=
"lxde
"
6325 </pre
></p
>
6327 <p
>The script could even become useful to set up Debian Edu servers in
6328 the cloud, by starting with a virtual Debian installation at some
6329 virtual hosting service and setting up all the services on first
6335 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6336 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6337 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6338 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6339 <description><P
>In January,
6340 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6341 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6342 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6343 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6344 marvellous construction system from Denmark. We also created
6345 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6346 a place to take notes and write down our plans and hopes. And several
6347 people showed up to help. I was very happy to see the effect of my
6348 call. Since the small start, we have a debtags tag
6349 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6350 tag for LEGO related packages, and now count
10 packages related to
6351 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6353 <p
><table
>
6354 <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
>
6355 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6356 <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
>
6357 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6358 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6359 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6360 <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
>
6361 <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
>
6362 <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
>
6363 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6364 </table
></p
>
6366 <p
>Some of these are available in Wheezy, and all but one are
6367 currently available in Jessie/testing. leocad is so far only
6368 available in experimental.
</p
>
6370 <p
>If you care about LEGO in Debian, please join us on IRC and help
6371 adding the rest of the great free software tools available on Linux
6372 for LEGO designers.
</p
>
6377 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6378 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6379 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6380 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6381 <description><p
>When I woke up this morning, I was very happy to see that the
6382 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6383 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6384 Debian release, and I expect to move my machines at home over to it fairly
6387 <p
>The new debian release contain heaps of new stuff, and one program
6388 in particular make me very happy to see included. The
6389 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6390 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6391 included for the first time. Alongside similar programs like
6392 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6393 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6394 it allow for visual programming where syntax errors can not happen,
6395 and a friendly programming environment for learning to control the
6396 computer. Scratch will also be included in the next release of Debian
6399 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6400 Edu/Skolelinux release too. The
6401 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6402 alpha release
</a
> went out last week, and the next should soon
6408 <title>Isenkram
0.2 finally in the Debian archive
</title>
6409 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6410 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6411 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6412 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6413 package
</a
> finally made it into the archive, after lingering in NEW
6414 for many months. I uploaded it to the Debian experimental suite
6415 2013-
01-
27, and today it was accepted into the archive.
</p
>
6417 <p
>Isenkram is a system for suggesting to users what packages to
6418 install to work with a pluggable hardware device. The suggestion pop
6419 up when the device is plugged in. For example if a Lego Mindstorm NXT
6420 is inserted, it will suggest to install the program needed to program
6421 the NXT controller. Give it a go, and report bugs and suggestions to
6427 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6428 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6429 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6430 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6431 <description><p
>My
6432 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6433 bitcoin related blog post
</a
> mentioned that the new
6434 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6435 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6436 2013-
01-
19, and have been available in unstable since then. It was
6437 automatically copied to Ubuntu, and is available in their Raring
6438 version too.
</p
>
6440 <p
>But there is a strange problem with the build that block this new
6441 version from being available on the i386 and kfreebsd-i386
6442 architectures. For some strange reason, the autobuilders in Debian
6443 for these architectures fail to run the test suite on these
6444 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6445 We are so far unable to reproduce it when building it manually, and
6446 no-one have been able to propose a fix. If you got an idea what is
6447 failing, please let us know via the BTS.
</p
>
6449 <p
>One feature that is annoying me with of the bitcoin client, because
6450 I often run low on disk space, is the fact that the client will exit
6451 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6452 #
696715</a
>). So make sure you have enough disk space when you run
6455 <p
>As usual, if you use bitcoin and want to show your support of my
6456 activities, please send Bitcoin donations to my address
6457 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6462 <title>Welcome to the world, Isenkram!
</title>
6463 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6464 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6465 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6466 <description><p
>Yesterday, I
6467 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6468 for testers
</a
> for my prototype for making Debian better at handling
6469 pluggable hardware devices, which I
6470 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6471 out to create
</a
> earlier this month. Several valuable testers showed
6472 up, and caused me to really want to to open up the development to more
6473 people. But before I did this, I want to come up with a sensible name
6474 for this project. Today I finally decided on a new name, and I have
6475 renamed the project from hw-support-handler to this new name. In the
6476 process, I moved the source to git and made it available as a
6477 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6478 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6479 To fetch and build the latest version of the source, use
</p
>
6482 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6483 cd isenkram
&& git-buildpackage -us -uc
6486 <p
>I have not yet adjusted all files to use the new name yet. If you
6487 want to hack on the source or improve the package, please go ahead.
6488 But please talk to me first on IRC or via email before you do major
6489 changes, to make sure we do not step on each others toes. :)
</p
>
6491 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6492 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6493 stuff, in other words. I
've been told it is the Norwegian variant of
6494 the German word eisenkram, for those that are familiar with that
6497 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6498 instructions, to avoid confusing people with an error from the signing
6501 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6502 clone argument to avoid the need for authentication.
</p
>
6507 <title>First prototype ready making hardware easier to use in Debian
</title>
6508 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6509 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6510 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6511 <description><p
>Early this month I set out to try to
6512 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6513 the Debian support for pluggable hardware devices
</a
>. Now my
6514 prototype is working, and it is ready for a larger audience. To test
6516 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6517 from the Debian Edu subversion repository
</a
>, build and install the
6518 package. You might have to log out and in again activate the
6519 autostart script.
</p
>
6521 <p
>The design is simple:
</p
>
6525 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6526 hw-support-handlerd to start when the user log in.
</li
>
6528 <li
>This program listen for kernel events about new hardware (directly
6529 from the kernel like udev does), not using HAL dbus events as I
6530 initially did.
</li
>
6532 <li
>When new hardware is inserted, look up the hardware modalias in
6533 the APT database, a database
6534 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6535 via HTTP
</a
> and a database available as part of the package.
</li
>
6537 <li
>If a package is mapped to the hardware in question, the package
6538 isn
't installed yet and this is the first time the hardware was
6539 plugged in, show a desktop notification suggesting to install the
6540 package or packages.
</li
>
6542 <li
>If the user click on the
'install package now
' button, ask
6543 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6545 <li
>aptdaemon ask for root password or sudo password, and install the
6546 package while showing progress information in a window.
</li
>
6550 <p
>I still need to come up with a better name for the system. Here
6551 are some screen shots showing the prototype in action. First the
6552 notification, then the password request, and finally the request to
6553 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6555 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6556 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6557 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6558 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6559 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6561 <p
>The prototype still need to be improved with longer timeouts, but
6562 is already useful. The database of hardware to package mappings also
6563 need more work. It is currently compatible with the Ubuntu way of
6564 storing such information in the package control file, but could be
6565 changed to use other formats instead or in addition to the current
6566 method. I
've dropped the use of discover for this mapping, as the
6567 modalias approach is more flexible and easier to use on Linux as long
6568 as the Linux kernel expose its modalias strings directly.
</p
>
6570 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6571 here is the command required to check out and build the source: Use
6572 '<tt
>svn checkout
6573 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6574 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6575 devscripts package.
</p
>
6577 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6578 renamed to Isenkram and the source moved from the Debian Edu
6579 subversion repository to a Debian collab-maint git repository. See
6580 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6581 instructions
</a
> for details.
</p
>
6586 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6587 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6588 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6589 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6590 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6591 suddenly in bed. With a quiet whimper, it went completely quiet and
6592 black. The power button was no longer able to turn it on. It was a
6593 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6594 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6595 Compaq I had before that. Now I need to find a replacement. To keep
6596 going during Christmas, I moved the one year old SSD disk to my old
6597 X40 where it fitted (only one I had left that could use it), but it is
6598 not a durable solution.
6600 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6601 got a new one more than
10 years ago. It still holds true.:)
</p
>
6605 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6606 than A4).
</li
>
6607 <li
>Robust, it will be in my backpack every day.
</li
>
6608 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6609 <li
>Long battery life time. Preferable a week.
</li
>
6610 <li
>Internal WIFI network card.
</li
>
6611 <li
>Internal Twisted Pair network card.
</li
>
6612 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6613 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6614 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6616 <li
>Hardware supported by Debian Stable, ie the default kernel and
6617 X.org packages.
</li
>
6618 <li
>Quiet, preferably fan free (or at least not using the fan most of
6623 <p
>You will notice that there are no RAM and CPU requirements in the
6624 list. The reason is simply that the specifications on laptops the
6625 last
10-
15 years have been sufficient for my needs, and I have to look
6626 at other features to choose my laptop. But are there still made as
6627 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6628 robust, and Thinkpads seem to be heading in the wrong direction since
6629 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6630 still be useful.
</p
>
6632 <p
>Perhaps I should rethink my needs, and look for a pad with an
6633 external keyboard? I
'll have to check the
6634 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6635 well-supported laptops, or perhaps just buy one preinstalled from one
6636 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6637 Pre-loaded site
</a
>.
</p
>
6642 <title>How to find a browser plugin supporting a given MIME type
</title>
6643 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6645 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6646 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6647 install to get support for a given MIME type. Thanks to
6648 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6649 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6650 Unfortunately, not very many packages provide the needed meta
6651 information, Anyway, here is a small script to look up all browser
6652 plugin packages announcing ther MIME support using this specification:
</p
>
6658 def pkgs_handling_mimetype(mimetype):
6663 version = pkg.candidate
6665 version = pkg.installed
6668 record = version.record
6669 if not record.has_key(
'Npp-MimeType
'):
6671 mime_types = record[
'Npp-MimeType
'].split(
',
')
6672 for t in mime_types:
6673 t = t.rstrip().strip()
6675 thepkgs.append(pkg.name)
6677 mimetype =
"audio/ogg
"
6678 if
1 < len(sys.argv):
6679 mimetype = sys.argv[
1]
6680 print
"Browser plugin packages supporting %s:
" % mimetype
6681 for pkg in pkgs_handling_mimetype(mimetype):
6682 print
" %s
" %pkg
6685 <p
>It can be used like this to look up a given MIME type:
</p
>
6688 % ./apt-find-browserplug-for-mimetype
6689 Browser plugin packages supporting audio/ogg:
6691 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6692 Browser plugin packages supporting application/x-shockwave-flash:
6693 browser-plugin-gnash
6697 <p
>In Ubuntu this mechanism is combined with support in the browser
6698 itself to query for plugins and propose to install the needed
6699 packages. It would be great if Debian supported such feature too. Is
6700 anyone working on adding it?
</p
>
6702 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6703 request for icweasel support for this feature is
6704 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6705 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6706 of manpower and wish for a different design is the reason thus feature
6707 is not yet in iceweasel from Debian.
</p
>
6712 <title>What is the most supported MIME type in Debian?
</title>
6713 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6715 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6716 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6717 proposal to add AppStream information to the Debian archive
</a
>, is a
6718 proposal to make it possible for a Desktop application to propose to
6719 the user some package to install to gain support for a given MIME
6720 type, font, library etc. that is currently missing. With such
6721 mechanism in place, it would be possible for the desktop to
6722 automatically propose and install leocad if some LDraw file is
6723 downloaded by the browser.
</p
>
6725 <p
>To get some idea about the current content of the archive, I decided
6726 to write a simple program to extract all .desktop files from the
6727 Debian archive and look up the claimed MIME support there. The result
6729 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6730 site
</a
>. Using the collected information, it become possible to
6731 answer the question in the title. Here are the
20 most supported MIME
6732 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6733 The complete list is available from the link above.
</p
>
6735 <p
><strong
>Debian Stable:
</strong
></p
>
6739 ----- -----------------------
6755 18 application/x-ogg
6762 <p
><strong
>Debian Testing:
</strong
></p
>
6766 ----- -----------------------
6782 18 application/x-ogg
6789 <p
><strong
>Debian Unstable:
</strong
></p
>
6793 ----- -----------------------
6810 18 application/x-ogg
6816 <p
>I am told that PackageKit can provide an API to access the kind of
6817 information mentioned in DEP-
11. I have not yet had time to look at
6818 it, but hope the PackageKit people in Debian are on top of these
6821 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6822 discovering a typo in my script.
</p
>
6827 <title>Using modalias info to find packages handling my hardware
</title>
6828 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6829 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6830 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6831 <description><p
>Yesterday, I wrote about the
6832 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6833 values provided by the Linux kernel
</a
> following my hope for
6834 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6835 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6836 modalias values attached to package names can be used to map packages
6837 to hardware. This allow the system to look up and suggest relevant
6838 packages when I plug in some new hardware into my machine, and replace
6839 discover and discover-data as the database used to map hardware to
6842 <p
>I create a modaliases file with entries like the following,
6843 containing package name, kernel module name (if relevant, otherwise
6844 the package name) and globs matching the relevant hardware
6847 <p
><blockquote
>
6848 Package: package-name
6849 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6850 </blockquote
></p
>
6852 <p
>It is fairly trivial to write code to find the relevant packages
6853 for a given modalias value using this file.
</p
>
6855 <p
>An entry like this would suggest the video and picture application
6856 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6858 <p
><blockquote
>
6860 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6861 </blockquote
></p
>
6863 <p
>An entry like this would suggest the pcmciautils package when a
6864 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6866 <p
><blockquote
>
6867 Package: pcmciautils
6868 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6869 </blockquote
></p
>
6871 <p
>An entry like this would suggest the package colorhug-client when
6872 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6874 <p
><blockquote
>
6875 Package: colorhug-client
6876 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6877 </blockquote
></p
>
6879 <p
>I believe the format is compatible with the format of the Packages
6880 file in the Debian archive. Ubuntu already uses their Packages file
6881 to store their mappings from packages to hardware.
</p
>
6883 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6884 announce the hardware it support in a way my prototype understand.
6885 This allow those publishing packages in an APT source outside the
6886 Debian archive as well as those backporting packages to make sure the
6887 hardware mapping are included in the package meta information. I
've
6888 tested such header in the pymissile package, and its modalias mapping
6889 is working as it should with my prototype. It even made it to Ubuntu
6892 <p
>To test if it was possible to look up supported hardware using only
6893 the shell tools available in the Debian installer, I wrote a shell
6894 implementation of the lookup code. The idea is to create files for
6895 each modalias and let the shell do the matching. Please check out and
6897 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6898 shell script. It run without any extra dependencies and fetch the
6899 hardware mappings from the Debian archive and the subversion
6900 repository where I currently work on my prototype.
</p
>
6902 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6903 install yubikey-personalization:
</p
>
6905 <p
><blockquote
>
6906 % ./hw-support-lookup
6907 <br
>yubikey-personalization
6909 </blockquote
></p
>
6911 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6912 propose to install the pcmciautils package:
</p
>
6914 <p
><blockquote
>
6915 % ./hw-support-lookup
6916 <br
>pcmciautils
6918 </blockquote
></p
>
6920 <p
>If you know of any hardware-package mapping that should be added to
6921 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6922 database
</a
>, please tell me about it.
</p
>
6924 <p
>It could be possible to generate several of the mappings between
6925 packages and hardware. One source would be to look at packages with
6926 kernel modules, ie packages with *.ko files in /lib/modules/, and
6927 extract their modalias information. Another would be to look at
6928 packages with udev rules, ie packages with files in
6929 /lib/udev/rules.d/, and extract their vendor/model information to
6930 generate a modalias matching rule. I have not tested any of these to
6931 see if it work.
</p
>
6933 <p
>If you want to help implementing a system to let us propose what
6934 packages to install when new hardware is plugged into a Debian
6935 machine, please send me an email or talk to me on
6936 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6941 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6942 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6943 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6944 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6945 <description><p
>While looking into how to look up Debian packages based on hardware
6946 information, to find the packages that support a given piece of
6947 hardware, I refreshed my memory regarding modalias values, and decided
6948 to document the details. Here are my findings so far, also available
6950 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6951 Debian Edu subversion repository
</a
>:
6953 <p
><strong
>Modalias decoded
</strong
></p
>
6955 <p
>This document try to explain what the different types of modalias
6956 values stands for. It is in part based on information from
6957 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6958 &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;,
6959 &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
6960 &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;.
6962 <p
>The modalias entries for a given Linux machine can be found using
6963 this shell script:
</p
>
6966 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6969 <p
>The supported modalias globs for a given kernel module can be found
6970 using modinfo:
</p
>
6973 % /sbin/modinfo psmouse | grep alias:
6974 alias: serio:ty05pr*id*ex*
6975 alias: serio:ty01pr*id*ex*
6979 <p
><strong
>PCI subtype
</strong
></p
>
6981 <p
>A typical PCI entry can look like this. This is an Intel Host
6982 Bridge memory controller:
</p
>
6984 <p
><blockquote
>
6985 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6986 </blockquote
></p
>
6988 <p
>This represent these values:
</p
>
6993 sv
00001028 (subvendor)
6994 sd
000001AD (subdevice)
6996 sc
00 (bus subclass)
7000 <p
>The vendor/device values are the same values outputted from
'lspci
7001 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
7002 0600. The
0600 class is a host bridge. Other useful bus values are
7003 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
7005 <p
>Not sure how to figure out the interface value, nor what it
7008 <p
><strong
>USB subtype
</strong
></p
>
7010 <p
>Some typical USB entries can look like this. This is an internal
7011 USB hub in a laptop:
</p
>
7013 <p
><blockquote
>
7014 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7015 </blockquote
></p
>
7017 <p
>Here is the values included in this alias:
</p
>
7020 v
1D6B (device vendor)
7021 p
0001 (device product)
7023 dc
09 (device class)
7024 dsc
00 (device subclass)
7025 dp
00 (device protocol)
7026 ic
09 (interface class)
7027 isc
00 (interface subclass)
7028 ip
00 (interface protocol)
7031 <p
>The
0900 device class/subclass means hub. Some times the relevant
7032 class is in the interface class section. For a simple USB web camera,
7033 these alias entries show up:
</p
>
7035 <p
><blockquote
>
7036 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7037 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7038 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7039 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7040 </blockquote
></p
>
7042 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
7043 camera),
0101 is audio control device and
0102 is audio streaming (aka
7044 microphone). Thus this is a camera with microphone included.
</p
>
7046 <p
><strong
>ACPI subtype
</strong
></p
>
7048 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
7049 receiver in a Thinkpad X40:
</p
>
7051 <p
><blockquote
>
7052 acpi:IBM0071:PNP0511:
7053 </blockquote
></p
>
7055 <p
>The values between the colons are IDs.
</p
>
7057 <p
><strong
>DMI subtype
</strong
></p
>
7059 <p
>The DMI table contain lots of information about the computer case
7060 and model. This is an entry for a IBM Thinkpad X40, fetched from
7061 /sys/devices/virtual/dmi/id/modalias:
</p
>
7063 <p
><blockquote
>
7064 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7065 </blockquote
></p
>
7067 <p
>The values present are
</p
>
7070 bvn IBM (BIOS vendor)
7071 bvr
1UETB
6WW(
1.66) (BIOS version)
7072 bd
06/
15/
2005 (BIOS date)
7073 svn IBM (system vendor)
7074 pn
2371H4G (product name)
7075 pvr ThinkPadX40 (product version)
7076 rvn IBM (board vendor)
7077 rn
2371H4G (board name)
7078 rvr NotAvailable (board version)
7079 cvn IBM (chassis vendor)
7080 ct
10 (chassis type)
7081 cvr NotAvailable (chassis version)
7084 <p
>The chassis type
10 is Notebook. Other interesting values can be
7085 found in the dmidecode source:
</p
>
7089 4 Low Profile Desktop
7102 17 Main Server Chassis
7103 18 Expansion Chassis
7105 20 Bus Expansion Chassis
7106 21 Peripheral Chassis
7108 23 Rack Mount Chassis
7117 <p
>The chassis type values are not always accurately set in the DMI
7118 table. For example my home server is a tower, but the DMI modalias
7119 claim it is a desktop.
</p
>
7121 <p
><strong
>SerIO subtype
</strong
></p
>
7123 <p
>This type is used for PS/
2 mouse plugs. One example is from my
7124 test machine:
</p
>
7126 <p
><blockquote
>
7127 serio:ty01pr00id00ex00
7128 </blockquote
></p
>
7130 <p
>The values present are
</p
>
7139 <p
>This type is supported by the psmouse driver. I am not sure what
7140 the valid values are.
</p
>
7142 <p
><strong
>Other subtypes
</strong
></p
>
7144 <p
>There are heaps of other modalias subtypes according to
7145 file2alias.c. There is the rest of the list from that source: amba,
7146 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7147 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7148 vmbus, x86cpu and zorro. I did not spend time documenting all of
7149 these, as they do not seem relevant for my intended use with mapping
7150 hardware to packages when new stuff is inserted during run time.
</p
>
7152 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
7154 <p
>To check which kernel modules provide support for a given modalias,
7155 one can use the following shell script:
</p
>
7158 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
7159 echo
"$id
" ; \
7160 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
7164 <p
>The output can look like this (only the first few entries as the
7165 list is very long on my test machine):
</p
>
7169 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
7171 FATAL: Module acpi:device: not found.
7173 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
7174 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
7175 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
7176 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7177 acpi:IBM0071:PNP0511:
7178 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
7179 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
7180 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
7184 <p
>If you want to help implementing a system to let us propose what
7185 packages to install when new hardware is plugged into a Debian
7186 machine, please send me an email or talk to me on
7187 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7189 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
7190 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
7191 in /sys/ with space in them.
</p
>
7196 <title>Moved the pymissile Debian packaging to collab-maint
</title>
7197 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
7198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
7199 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
7200 <description><p
>As part of my investigation on how to improve the support in Debian
7201 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7202 Launcher and updated the Debian package
7203 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
7204 sure udev will fix the device permissions when it is plugged in. I
7205 also added a
"Modaliases
" header to test it in the Debian archive and
7206 hopefully make the package be proposed by jockey in Ubuntu when a user
7207 plug in his rocket launcher. In the process I moved the source to a
7208 git repository under collab-maint, to make it easier for any DD to
7209 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
7210 is not very active, but the software still work for me even after five
7211 years of relative silence. The new git repository is not listed in
7212 the uploaded package yet, because I want to test the other changes a
7213 bit more before I upload the new version. If you want to check out
7214 the new version with a .desktop file included, visit the
7215 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
7216 view
</a
> or use
"<tt
>git clone
7217 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
7222 <title>Lets make hardware dongles easier to use in Debian
</title>
7223 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
7224 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
7225 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
7226 <description><p
>One thing that annoys me with Debian and Linux distributions in
7227 general, is that there is a great package management system with the
7228 ability to automatically install software packages by downloading them
7229 from the distribution mirrors, but no way to get it to automatically
7230 install the packages I need to use the hardware I plug into my
7231 machine. Even if the package to use it is easily available from the
7232 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7233 suggest to automatically install the python-nxt, nbc and t2n packages
7234 I need to talk to it. When I plug in a Yubikey, it could propose the
7235 yubikey-personalization package. The information required to do this
7236 is available, but no-one have pulled all the pieces together.
</p
>
7238 <p
>Some years ago, I proposed to
7239 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
7240 the discover subsystem to implement this
</a
>. The idea is fairly
7245 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
7246 starting when a user log in.
</li
>
7248 <li
>Set this program up to listen for kernel events emitted when new
7249 hardware is inserted into the computer.
</li
>
7251 <li
>When new hardware is inserted, look up the hardware ID in a
7252 database mapping to packages, and take note of any non-installed
7253 packages.
</li
>
7255 <li
>Show a message to the user proposing to install the discovered
7256 package, and make it easy to install it.
</li
>
7260 <p
>I am not sure what the best way to implement this is, but my
7261 initial idea was to use dbus events to discover new hardware, the
7262 discover database to find packages and
7263 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7266 <p
>Yesterday, I found time to try to implement this idea, and the
7267 draft package is now checked into
7268 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7269 Debian Edu subversion repository
</a
>. In the process, I updated the
7270 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7271 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7272 the relevant packages in Debian, and uploaded a new version
7273 2.2013.01.09 to unstable. I also discovered that the current
7274 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7275 package in Debian no longer discovered any USB devices, because
7276 /proc/bus/usb/devices is no longer present. I ported it to use
7277 libusb as a fall back option to get it working. The fixed package
7278 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7279 because of the freeze).
</p
>
7281 <p
>With this prototype in place, I can insert my Yubikey, and get this
7282 desktop notification to show up (only once, the first time it is
7283 inserted):
</p
>
7285 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7287 <p
>For this prototype to be really useful, some way to automatically
7288 install the proposed packages by pressing the
"Please install
7289 program(s)
" button should to be implemented.
</p
>
7291 <p
>If this idea seem useful to you, and you want to help make it
7292 happen, please help me update the discover-data database with mappings
7293 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7294 list the package you would like to have installed when a given
7295 hardware device is inserted into your computer, and report bugs using
7296 reportbug if it isn
't. Or, if you know of a better way to provide
7297 such mapping, please let me know.
</p
>
7299 <p
>This prototype need more work, and there are several questions that
7300 should be considered before it is ready for production use. Is dbus
7301 the correct way to detect new hardware? At the moment I look for HAL
7302 dbus events on the system bus, because that is the events I could see
7303 on my Debian Squeeze KDE desktop. Are there better events to use?
7304 How should the user be notified? Is the desktop notification
7305 mechanism the best option, or should the background daemon raise a
7306 popup instead? How should packages be installed? When should they
7307 not be installed?
</p
>
7309 <p
>If you want to help getting such feature implemented in Debian,
7310 please send me an email. :)
</p
>
7315 <title>New IRC channel for LEGO designers using Debian
</title>
7316 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7317 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7318 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7319 <description><p
>During Christmas, I have worked a bit on the Debian support for
7320 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7321 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7322 discovered I had to build all the tools myself because none were
7323 already in Debian Squeeze. If Debian support for LEGO is something
7324 you care about, please join me on the IRC channel
7325 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7326 irc.debian.org). There is a lot that could be done to improve the
7327 Debian support for LEGO designers. For example both CAD software
7328 and Mindstorm compilers are missing. :)
</p
>
7330 <p
>Update
2012-
01-
03: A
7331 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7332 including links to Lego related packages is now available.
</p
>
7337 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7338 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7339 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7340 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7341 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7342 year! I hope next year will prove to be a good year.
</p
>
7344 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7345 decentralised
"currency
" that allow people to transfer bitcoins
7346 between each other with minimal overhead, is a very interesting
7347 experiment. And as I wrote a few days ago, the bitcoin situation in
7348 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7349 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7350 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7351 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7352 for one of the ftpmasters to approve the new bitcoin-qt package
7355 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7356 team in Debian, you can easily test the package in Debian Squeeze
7357 using the following steps to get a set of working packages:
</p
>
7359 <blockquote
><pre
>
7360 git clone git://git.debian.org/git/collab-maint/bitcoin
7362 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7363 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7364 </pre
></blockquote
>
7366 <p
>You might have to install some build dependencies as well. The
7367 list of commands should give you two packages, bitcoind and
7368 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7369 client will download the complete set of bitcoin
"blocks
", which need
7370 around
5.6 GiB of data on my machine at the moment. Make sure your
7371 ~/.bitcoin/ directory have lots of spare room if you want to download
7372 all the blocks. The client will warn if the disk is getting full, so
7373 there is not really a problem if you got too little room, but you will
7374 not be able to get all the features out of the client.
</p
>
7376 <p
>As usual, if you use bitcoin and want to show your support of my
7377 activities, please send Bitcoin donations to my address
7378 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7383 <title>A word on bitcoin support in Debian
</title>
7384 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7385 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7386 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7387 <description><p
>It has been a while since I wrote about
7388 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7389 peer-to-peer based crypto-currency, and the reason is simply that I
7390 have been busy elsewhere. But two days ago, I started looking at the
7391 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7392 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7393 is now maintained by a
7394 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7395 people
</a
>, and the grunt work had already been done by this team. We
7396 owe a huge thank you to all these team members. :)
7397 But I was sad to discover that the bitcoin client is missing in
7398 Wheezy. It is only available in Sid (and an outdated client from
7399 backports). The client had several RC bugs registered in BTS blocking
7400 it from entering testing. To try to help the team and improve the
7401 situation, I spent some time providing patches and triaging the bug
7402 reports. I also had a look at the bitcoin package available from Matt
7404 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7405 Ubuntu
</a
>, and moved the useful pieces from that version into the
7406 Debian package.
</p
>
7408 <p
>After checking with the main package maintainer Jonas Smedegaard on
7409 IRC, I pushed several patches into the collab-maint git repository to
7410 improve the package. It now contains fixes for the RC issues (not from
7411 me, but fixed by Scott Howard), build rules for a Qt GUI client
7412 package, konqueror support for the bitcoin: URI and bash completion
7413 setup. As I work on Debian Squeeze, I also created
7414 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7415 patch to backport
</a
> the latest version. Jonas is going to look at
7416 it and try to integrate it into the git repository before uploading a
7417 new version to unstable.
7419 <p
>I would very much like bitcoin to succeed, to get rid of the
7420 centralized control currently exercised in the monetary system. I
7421 find it completely unacceptable that the USA government is collecting
7422 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7423 that the major credit card companies can block legal money
7424 transactions to Wikileaks. But for bitcoin to succeed, more people
7425 need to use bitcoins, and more people need to accept bitcoins when
7426 they sell products and services. Improving the bitcoin support in
7427 Debian is a small step in the right direction, but not enough.
7428 Unfortunately the user experience when browsing the web and wanting to
7429 pay with bitcoin is still not very good. The bitcoin: URI is a step
7430 in the right direction, but need to work in most or every browser in
7431 use. Also the bitcoin-qt client is too heavy to fire up to do a
7432 quick transaction. I believe there are other clients available, but
7433 have not tested them.
</p
>
7436 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7437 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7438 I received
20.15 BTC so far on the address I provided in my blog two
7439 years ago, as can be
7440 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7441 on the blockexplorer service
</a
>. Thank you everyone for your
7442 donation. The blockexplorer service demonstrates quite well that
7443 bitcoin is not quite anonymous and untracked. :) I wonder if the
7444 number of users have gone up since then. If you use bitcoin and want
7445 to show your support of my activity, please send Bitcoin donations to
7446 the same address as last time,
7447 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7452 <title>Git repository for song book for Computer Scientists
</title>
7453 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7454 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7455 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7456 <description><p
>As I
7457 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7458 this summer
</a
>, I have created a Computer Science song book a few
7459 years ago, and today I finally found time to create a public
7460 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7461 repository for the project
</a
>.
</p
>
7463 <p
>If you want to help out, please clone the source and submit patches
7464 to the HTML version. To generate the PDF and PostScript version,
7465 please use prince XML, or let me know about a useful free software
7466 processor capable of creating a good looking PDF from the HTML.
</p
>
7468 <p
>Want to sing? You can still find the song book in HTML, PDF and
7469 PostScript formats at
7470 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7471 Science Songbook
</a
>.
</p
>
7476 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7477 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7478 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7479 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7480 <description><p
>I dag fyller
7481 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7482 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7483 si gratulerer med dagen, Debian!
</p
>
7488 <title>Song book for Computer Scientists
</title>
7489 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7490 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7491 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7492 <description><p
>Many years ago, while studying Computer Science at the
7493 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7494 collecting computer related songs for use at parties. The original
7495 version was written in LaTeX, but a few years ago I got help from
7496 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7497 while keeping the ability to create a nice book in PDF format. I have
7498 not had time to maintain the book for a while now, and guess I should
7499 put it up on some public version control repository where others can
7500 help me extend and update the book. If anyone is volunteering to help
7501 me with this, send me an email. Also let me know if there are songs
7502 missing in my book.
</p
>
7504 <p
>I have not mentioned the book on my blog so far, and it occured to
7505 me today that I really should let all my readers share the joys of
7506 singing out load about programming, computers and computer networks.
7507 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7508 12</a
> is about to start (and I am not going). Want to sing? Check
7509 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7510 Computer Science Songbook
</a
>.
7515 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7516 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7517 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7518 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7519 <description><p
>At work we have heaps of servers. I believe the total count is
7520 around
1000 at the moment. To be able to get help from the vendors
7521 when something go wrong, we want to keep the firmware on the servers
7522 up to date. If the firmware isn
't the latest and greatest, the
7523 vendors typically refuse to start debugging any problems until the
7524 firmware is upgraded. So before every reboot, we want to upgrade the
7525 firmware, and we would really like everyone handling servers at the
7526 university to do this themselves when they plan to reboot a machine.
7527 For that to happen we at the unix server admin group need to provide
7528 the tools to do so.
</p
>
7530 <p
>To make firmware upgrading easier, I am working on a script to
7531 fetch and install the latest firmware for the servers we got. Most of
7532 our hardware are from Dell and HP, so I have focused on these servers
7533 so far. This blog post is about the Dell part.
</P
>
7535 <p
>On the Dell FTP site I was lucky enough to find
7536 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7537 with firmware information for all
11th generation servers, listing
7538 which firmware should be used on a given model and where on the FTP
7539 site I can find it. Using a simple perl XML parser I can then
7540 download the shell scripts Dell provides to do firmware upgrades from
7541 within Linux and reboot when all the firmware is primed and ready to
7542 be activated on the first reboot.
</p
>
7544 <p
>This is the Dell related fragment of the perl code I am working on.
7545 Are there anyone working on similar tools for firmware upgrading all
7546 servers at a site? Please get in touch and lets share resources.
</p
>
7548 <p
><pre
>
7552 use File::Temp qw(tempdir);
7554 # Install needed RHEL packages if missing
7556 'XML::Simple
' =
> 'perl-XML-Simple
',
7558 for my $module (keys %rhelmodules) {
7559 eval
"use $module;
";
7561 my $pkg = $rhelmodules{$module};
7562 system(
"yum install -y $pkg
");
7563 eval
"use $module;
";
7567 my $errorsto =
'pere@hungry.com
';
7573 sub run_firmware_script {
7574 my ($opts, $script) = @_;
7576 print STDERR
"fail: missing script name\n
";
7579 print STDERR
"Running $script\n\n
";
7581 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7582 print STDERR
"success: firmware script ran succcessfully\n
";
7584 print STDERR
"fail: firmware script returned error\n
";
7588 sub run_firmware_scripts {
7589 my ($opts, @dirs) = @_;
7590 # Run firmware packages
7591 for my $dir (@dirs) {
7592 print STDERR
"info: Running scripts in $dir\n
";
7593 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7594 while (my $s = readdir $dh) {
7595 next if $s =~ m/^\.\.?/;
7596 run_firmware_script($opts,
"$dir/$s
");
7604 print STDERR
"info: Downloading $url\n
";
7605 system(
"wget --quiet \
"$url\
"");
7610 my $product = `dmidecode -s system-product-name`;
7613 if ($product =~ m/PowerEdge/) {
7615 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7616 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7618 my $tmpdir = tempdir(
7622 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7623 system(
'gunzip Catalog.xml.gz
');
7624 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7625 # -q is quiet, disabling interactivity and reducing console output
7626 my $fwopts =
"-q
";
7628 for my $url (@paths) {
7629 fetch_dell_fw($url);
7631 run_firmware_scripts($fwopts, $tmpdir);
7633 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7634 print STDERR
"error: Please report to $errorsto.\n
";
7638 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7639 print STDERR
"error: Please report to $errorsto.\n
";
7645 my $url =
"ftp://ftp.us.dell.com/$path
";
7649 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7650 # firmware packages to download from Dell. Only work for Linux
7651 # machines and
11th generation Dell servers.
7652 sub fetch_dell_fw_list {
7653 my $filename = shift;
7655 my $product = `dmidecode -s system-product-name`;
7657 my ($mybrand, $mymodel) = split(/\s+/, $product);
7659 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7661 my $xml = XMLin($filename);
7663 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7664 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7665 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7667 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7668 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7670 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7672 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7674 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7677 for my $component (@{$xml-
>{SoftwareComponent}}) {
7678 my $componenttype = $component-
>{ComponentType}-
>{value};
7680 # Drop application packages, only firmware and BIOS
7681 next if
'APAC
' eq $componenttype;
7683 my $cpath = $component-
>{path};
7684 for my $path (@paths) {
7685 if ($cpath =~ m%/$path$%) {
7686 push(@paths, $cpath);
7694 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7695 it could work on other platforms with some tweaking. Anyone know a
7696 index like Catalog.xml is available from HP for HP servers? At the
7697 moment I maintain a similar list manually and it is quickly getting
7703 <title>How is booting into runlevel
1 different from single user boots?
</title>
7704 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7706 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7707 <description><p
>Wouter Verhelst have some
7708 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7709 comments and opinions
</a
> on my blog post on
7710 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7711 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7712 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7713 default KDE desktop in Debian
</a
>. I only have time to address one
7714 small piece of his comment now, and though it best to address the
7715 misunderstanding he bring forward:
</p
>
7717 <p
><blockquote
>
7718 Currently, a system admin has four options: [...] boot to a
7719 single-user system (by adding
'single
' to the kernel command line;
7720 this runs rcS and rc1 scripts)
7721 </blockquote
></p
>
7723 <p
>This make me believe Wouter believe booting into single user mode
7724 and booting into runlevel
1 is the same. I am not surprised he
7725 believe this, because it would make sense and is a quite sensible
7726 thing to believe. But because the boot in Debian is slightly broken,
7727 runlevel
1 do not work properly and it isn
't the same as single user
7728 mode. I
'll try to explain what is actually happing, but it is a bit
7729 hard to explain.
</p
>
7731 <p
>Single user mode is defined like this in /etc/inittab:
7732 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7733 executed in single user mode is sulogin. Single user mode is a boot
7734 state
"between
" the runlevels, and when booting into single user mode,
7735 only the scripts in /etc/rcS.d/ are executed before the init process
7736 enters the single user state. When switching to runlevel
1, the state
7737 is in fact not ending in runlevel
1, but it passes through runlevel
1
7738 and end up in the single user mode (see /etc/rc1.d/S03single, which
7739 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7740 1. It is confusing that the
'S
' (single user) init mode is not the
7741 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7744 <p
>This summary might make it clearer. When booting for the first
7745 time into single user mode, the following commands are executed:
7746 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7747 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7748 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7749 trying to continue after visiting single user mode. Not all services
7750 are started again as they should, causing the machine to end up in an
7751 unpredicatble state. This is why Debian admins recommend rebooting
7752 after visiting single user mode.
</p
>
7754 <p
>A similar problem with runlevel
1 is caused by the amount of
7755 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7756 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7757 stopped when passing through the scripts in /etc/rc1.d/, and not
7758 started again when switching away from runlevel
1 to the runlevels
7759 2-
5. I believe the problem is best fixed by moving all the scripts
7760 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7761 functioning single user mode during boot.
</p
>
7763 <p
>I have spent several years investigating the Debian boot system,
7764 and discovered this problem a few years ago. I suspect it originates
7765 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7770 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7771 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7773 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7774 <description><p
>In the Debian boot system, several packages include scripts that
7775 are started from /etc/rcS.d/. In fact, there is a bite more of them
7776 than make sense, and this causes a few problems. What kind of
7777 problems, you might ask. There are at least two problems. The first
7778 is that it is not possible to recover a machine after switching to
7779 runlevel
1. One need to actually reboot to get the machine back to
7780 the expected state. The other is that single user boot will sometimes
7781 run into problems because some of the subsystems are activated before
7782 the root login is presented, causing problems when trying to recover a
7783 machine from a problem in that subsystem. A minor additional point is
7784 that moving more scripts out of rcS.d/ and into the other rc#.d/
7785 directories will increase the amount of scripts that can run in
7786 parallel during boot, and thus decrease the boot time.
</p
>
7788 <p
>So, which scripts should start from rcS.d/. In short, only the
7789 scripts that _have_ to execute before the root login prompt is
7790 presented during a single user boot should go there. Everything else
7791 should go into the numeric runlevels. This means things like
7792 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7793 the numeric runlevels. Today in Debian, there are around
115 init.d
7794 scripts that are started from rcS.d/, and most of them should be moved
7795 out. Do your package have one of them? Please help us make single
7796 user and runlevel
1 better by moving it.
</p
>
7798 <p
>Scripts setting up the screen, keyboard, system partitions
7799 etc. should still be started from rcS.d/, but there is for example no
7800 need to have the network enabled before the single user login prompt
7801 is presented.
</p
>
7803 <p
>As always, things are not so easy to fix as they sound. To keep
7804 Debian systems working while scripts migrate and during upgrades, the
7805 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7806 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7807 and the next ones can only be moved when their dependencies have been
7808 moved first. This migration must be done sequentially while we ensure
7809 that the package system upgrade packages in the right order to keep
7810 the system state correct. This will require some coordination when it
7811 comes to network related packages, but most of the packages with
7812 scripts that should migrate do not have anything in rcS.d/ depending
7813 on them. Some packages have already been updated, like the sudo
7814 package, while others are still left to do. I wish I had time to work
7815 on this myself, but real live constrains make it unlikely that I will
7816 find time to push this forward.
</p
>
7821 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7822 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7823 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7824 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7825 <description><p
>While at Debconf11, I have several times during discussions
7826 mentioned the issues I believe should be improved in Debian for its
7827 desktop to be useful for more people. The use case for this is my
7828 parents, which are currently running Kubuntu which solve the
7831 <p
>I suspect these four missing features are not very hard to
7832 implement. After all, they are present in Ubuntu, so if we wanted to
7833 do this in Debian we would have a source.
</p
>
7837 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7838 are new packages available for upgrades, a icon in the KDE status bar
7839 indicate this, and clicking on it will activate the simple upgrade
7840 tool to handle it. I have no problem guiding both of my parents
7841 through the process over the phone. If a kernel reboot is required,
7842 this too is indicated by the status bars and the upgrade tool. Last
7843 time I checked, nothing with the same features was working in KDE in
7846 <li
><strong
>Simple handling of missing Firefox browser
7847 plugins.
</strong
> When the browser encounter a MIME type it do not
7848 currently have a handler for, it will ask the user if the system
7849 should search for a package that would add support for this MIME type,
7850 and if the user say yes, the APT sources will be searched for packages
7851 advertising the MIME type in their control file (visible in the
7852 Packages file in the APT archive). If one or more packages are found,
7853 it is a simple click of the mouse to add support for the missing mime
7854 type. If the package require the user to accept some non-free
7855 license, this is explained to the user. The entire process make it
7856 more clear to the user why something do not work in the browser, and
7857 make the chances higher for the user to blame the web page authors and
7858 not the browser for any missing features.
</li
>
7860 <li
><strong
>Simple handling of missing multimedia codec/format
7861 handlers.
</strong
> When the media players encounter a format or codec
7862 it is not supporting, a dialog pop up asking the user if the system
7863 should search for a package that would add support for it. This
7864 happen with things like MP3, Windows Media or H
.264. The selection
7865 and installation procedure is very similar to the Firefox browser
7866 plugin handling. This is as far as I know implemented using a
7867 gstreamer hook. The end result is that the user easily get access to
7868 the codecs that are present from the APT archives available, while
7869 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7871 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7872 displaying a text/plain file in my Debian browser, it will propose to
7873 start emacs to show it. If I remember correctly, when doing the same
7874 in Kunbutu it show the file as a text file in the browser. At least I
7875 know Opera will show text files within the browser. I much prefer the
7876 latter behaviour.
</li
>
7880 <p
>There are other nice features as well, like the simplified suite
7881 upgrader, but given that I am the one mostly doing the dist-upgrade,
7882 it do not matter much.
</p
>
7884 <p
>I really hope we could get these features in place for the next
7885 Debian release. It would require the coordinated effort of several
7886 maintainers, but would make the end user experience a lot better.
</p
>
7891 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7892 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7893 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7894 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7895 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7896 site is build on Debian/Squeeze, and this platform was chosen because
7897 I am most familiar with Debian (being a Debian Developer for around
10
7898 years) because it is the latest stable Debian release which should get
7899 security support for a few years.
</p
>
7901 <p
>The web service is written in Perl, and depend on some perl modules
7902 that are missing in Debian at the moment. It would be great if these
7903 modules were added to the Debian archive, allowing anyone to set up
7904 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7905 in their own country using only Debian packages. The list of modules
7906 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7907 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7908 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7909 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7910 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7911 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7912 easier in the future.
</p
>
7914 <p
>Thanks to the great tools in Debian, getting the missing modules
7915 installed on my server was a simple call to
'cpan2deb Module::Name
'
7916 and
'dpkg -i
' to install the resulting package. But this leave me
7917 with the responsibility of tracking security problems, which I really
7918 do not have time for.
</p
>
7923 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7924 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7925 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7926 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7927 <description><p
>Here is a small update for my English readers. Most of my blog
7928 posts have been in Norwegian the last few weeks, so here is a short
7929 update in English.
</p
>
7931 <p
>The kids still keep me too busy to get much free software work
7932 done, but I did manage to organise a project to get a Norwegian port
7933 of the British service
7934 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7935 and it has been running for a month now. The entire project has been
7936 organised by me and two others. Around Christmas we gathered sponsors
7937 to fund the development work. In January I drafted a contract with
7938 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7939 and in February the development took place. Most of it involved
7940 converting the source to use GPS coordinates instead of British
7941 easting/northing, and the resulting code should be a lot easier to get
7942 running in any country by now. The Norwegian
7943 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7944 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7945 source and the source for administrative borders in Norway, and
7946 support for this had to be added/fixed.
</p
>
7948 <p
>The Norwegian version went live March
3th, and we spent the weekend
7949 polishing the system before we announced it March
7th. The system is
7950 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7951 problem reports in a few weeks. Soon we hope to announce the Android
7952 and iPhone versions making it even easier to report problems with the
7953 public infrastructure.
</p
>
7955 <p
>Perhaps something to consider for those of you in countries without
7956 such service?
</p
>
7961 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7962 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7963 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7964 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7965 <description><p
>The last few days I have looked at ways to track open security
7966 issues here at my work with the University of Oslo. My idea is that
7967 it should be possible to use the information about security issues
7968 available on the Internet, and check our locally
7969 maintained/distributed software against this information. It should
7970 allow us to verify that no known security issues are forgotten. The
7971 CVE database listing vulnerabilities seem like a great central point,
7972 and by using the package lists from Debian mapped to CVEs provided by
7973 the testing security team, I believed it should be possible to figure
7974 out which security holes were present in our free software
7975 collection.
</p
>
7977 <p
>After reading up on the topic, it became obvious that the first
7978 building block is to be able to name software packages in a unique and
7979 consistent way across data sources. I considered several ways to do
7980 this, for example coming up with my own naming scheme like using URLs
7981 to project home pages or URLs to the Freshmeat entries, or using some
7982 existing naming scheme. And it seem like I am not the first one to
7983 come across this problem, as MITRE already proposed and implemented a
7984 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7985 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7986 software, hardware and other platform components. The CPE ids are
7987 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7988 Vulnerability Database
</a
>, allowing me to look up know security
7989 issues for any CPE name. With this in place, all I need to do is to
7990 locate the CPE id for the software packages we use at the university.
7991 This is fairly trivial (I google for
'cve cpe $package
' and check the
7992 NVD entry if a CVE for the package exist).
</p
>
7994 <p
>To give you an example. The GNU gzip source package have the CPE
7995 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7996 check out, one could look up
7997 <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
7998 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7999 The most recent one is
8000 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
8001 and at the bottom of the NVD page for this vulnerability the complete
8002 list of affected versions is provided.
</p
>
8004 <p
>The NVD database of CVEs is also available as a XML dump, allowing
8005 for offline processing of issues. Using this dump, I
've written a
8006 small script taking a list of CPEs as input and list all CVEs
8007 affecting the packages represented by these CPEs. One give it CPEs
8008 with version numbers as specified above and get a list of open
8009 security issues out.
</p
>
8011 <p
>Of course for this approach to be useful, the quality of the NVD
8012 information need to be high. For that to happen, I believe as many as
8013 possible need to use and contribute to the NVD database. I notice
8015 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
8016 map from CVE to CPE
</a
>, indicating that they are using the CPE
8017 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
8019 <p
>To get an idea about the quality for free software, I spent some
8020 time making it possible to compare the CVE database from Debian with
8021 the CVE database in NVD. The result look fairly good, but there are
8022 some inconsistencies in NVD (same software package having several
8023 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8024 Debian believe are affected by a CVE). Hope to find time to improve
8025 the quality of NVD, but that require being able to get in touch with
8026 someone maintaining it. So far my three emails with questions and
8027 corrections have not seen any reply, but I hope contact can be
8028 established soon.
</p
>
8030 <p
>An interesting application for CPEs is cross platform package
8031 mapping. It would be useful to know which packages in for example
8032 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8033 this would be trivial if all linux distributions provided CPE entries
8034 for their packages.
</p
>
8039 <title>Which module is loaded for a given PCI and USB device?
</title>
8040 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
8041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
8042 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
8043 <description><p
>In the
8044 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
8045 package in Debian, there is a script to report useful information
8046 about the running hardware for use when people report missing
8047 information. One part of this script that I find very useful when
8048 debugging hardware problems, is the part mapping loaded kernel module
8049 to the PCI device it claims. It allow me to quickly see if the kernel
8050 module I expect is driving the hardware I am struggling with. To see
8051 the output, make sure discover-data is installed and run
8052 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
8053 one of my machines like this:
</p
>
8057 10de:
03eb i2c_nforce2
8060 10de:
03f0 snd_hda_intel
8069 <p
>The code in question look like this, slightly modified for
8070 readability and to drop the output to file descriptor
3:
</p
>
8073 if [ -d /sys/bus/pci/devices/ ] ; then
8074 echo loaded pci modules:
8076 cd /sys/bus/pci/devices/
8077 for address in * ; do
8078 if [ -d
"$address/driver/module
" ] ; then
8079 module=`cd $address/driver/module ; pwd -P | xargs basename`
8080 if grep -q
"^$module
" /proc/modules ; then
8081 address=$(echo $address |sed s/
0000://)
8082 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
8083 echo
"$id $module
"
8092 <p
>Similar code could be used to extract USB device module
8096 if [ -d /sys/bus/usb/devices/ ] ; then
8097 echo loaded usb modules:
8099 cd /sys/bus/usb/devices/
8100 for address in * ; do
8101 if [ -d
"$address/driver/module
" ] ; then
8102 module=`cd $address/driver/module ; pwd -P | xargs basename`
8103 if grep -q
"^$module
" /proc/modules ; then
8104 address=$(echo $address |sed s/
0000://)
8105 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
8106 if [
"$id
" ] ; then
8107 echo
"$id $module
"
8117 <p
>This might perhaps be something to include in other tools as
8123 <title>How to test if a laptop is working with Linux
</title>
8124 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
8125 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
8126 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
8127 <description><p
>The last few days I have spent at work here at the
<a
8128 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
8129 batch of computers will work with Linux. Every year for the last few
8130 years the university have organised shared bid of a few thousand
8131 computers, and this year HP won the bid. Two different desktops and
8132 five different laptops are on the list this year. We in the UNIX
8133 group want to know which one of these computers work well with RHEL
8134 and Ubuntu, the two Linux distributions we currently handle at the
8135 university.
</p
>
8137 <p
>My test method is simple, and I share it here to get feedback and
8138 perhaps inspire others to test hardware as well. To test, I PXE
8139 install the OS version of choice, and log in as my normal user and run
8140 a few applications and plug in selected pieces of hardware. When
8141 something fail, I make a note about this in the test matrix and move
8142 on. If I have some spare time I try to report the bug to the OS
8143 vendor, but as I only have the machines for a short time, I rarely
8144 have the time to do this for all the problems I find.
</p
>
8146 <p
>Anyway, to get to the point of this post. Here is the simple tests
8147 I perform on a new model.
</p
>
8151 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
8152 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8153 RHEL5 and Debian Edu/Squeeze.
</li
>
8155 <li
>Is X.org working? If the graphical login screen show up after
8156 installation, X.org is working.
</li
>
8158 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
8159 package mesa-utils on Ubuntu) and writing down the frames per second
8160 reported by the program.
</li
>
8162 <li
>Is sound working? With Gnome and KDE, a sound is played when
8163 logging in, and if I can hear this the test is successful. If there
8164 are several audio exits on the machine, I try them all and check if
8165 the Gnome/KDE audio mixer can control where to send the sound. I
8166 normally test this by playing
8167 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
8168 video
</a
> in Firefox/Iceweasel.
</li
>
8170 <li
>Is the USB subsystem working? I test this by plugging in a USB
8171 memory stick and see if Gnome/KDE notices this.
</li
>
8173 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
8174 I have lying around, and see if Gnome/KDE notices this.
</li
>
8176 <li
>Is any built in camera working? Test using cheese, and see if a
8177 picture from the v4l device show up.
</li
>
8179 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8180 any bluetooth devices are discovered. In my office, I normally see a
8183 <li
>For laptops, is the SD or Compaq Flash reader working. I have
8184 memory modules lying around, and stick them in and see if Gnome/KDE
8185 notice this.
</li
>
8187 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
8188 special button work, and if the laptop continue to work after
8191 <li
>For laptops, is the extra buttons working, like audio level,
8192 adjusting background light, switching on/off external video output,
8193 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8194 laptop to laptop, so I just write down which are working and which are
8197 <li
>Some laptops have smart card readers, finger print readers,
8198 acceleration sensors etc. I rarely test these, as I do not know how
8199 to quickly test if they are working or not, so I only document their
8200 existence.
</li
>
8204 <p
>By now I suspect you are really curious what the test results are
8205 for the HP machines I am testing. I
'm not done yet, so I will report
8206 the test results later. For now I can report that HP
8100 Elite work
8207 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
8208 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
8209 can see, I have most machines left to test. One interesting
8210 observation is that Ubuntu Lucid has almost twice the frame rate than
8211 RHEL6 with glxgears. No idea why.
</p
>
8216 <title>Some thoughts on BitCoins
</title>
8217 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
8218 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
8219 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
8220 <description><p
>As I continue to explore
8221 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
8222 what properties the system have, and how it will be affected by laws
8223 and regulations here in Norway. Here are some random notes.
</p
>
8225 <p
>One interesting thing to note is that since the transactions are
8226 verified using a peer to peer network, all details about a transaction
8227 is known to everyone. This means that if a BitCoin address has been
8228 published like I did with mine in my initial post about BitCoin, it is
8229 possible for everyone to see how many BitCoins have been transfered to
8230 that address. There is even a web service to look at the details for
8231 all transactions. There I can see that my address
8232 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
8233 have received
16.06 Bitcoin, the
8234 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
8235 address of Simon Phipps have received
181.97 BitCoin and the address
8236 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
8237 of EFF have received
2447.38 BitCoins so far. Thank you to each and
8238 every one of you that donated bitcoins to support my activity. The
8239 fact that anyone can see how much money was transfered to a given
8240 address make it more obvious why the BitCoin community recommend to
8241 generate and hand out a new address for each transaction. I
'm told
8242 there is no way to track which addresses belong to a given person or
8243 organisation without the person or organisation revealing it
8244 themselves, as Simon, EFF and I have done.
</p
>
8246 <p
>In Norway, and in most other countries, there are laws and
8247 regulations limiting how much money one can transfer across the border
8248 without declaring it. There are money laundering, tax and accounting
8249 laws and regulations I would expect to apply to the use of BitCoin.
8250 If the Skolelinux foundation
8251 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
8252 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
8253 normal bank transfers like EFF is doing, how should this be accounted?
8254 Given that it is impossible to know if money can cross the border or
8255 not, should everything or nothing be declared? What exchange rate
8256 should be used when calculating taxes? Would receivers have to pay
8257 income tax if the foundation were to pay Skolelinux contributors in
8258 BitCoin? I have no idea, but it would be interesting to know.
</p
>
8260 <p
>For a currency to be useful and successful, it must be trusted and
8261 accepted by a lot of users. It must be possible to get easy access to
8262 the currency (as a wage or using currency exchanges), and it must be
8263 easy to spend it. At the moment BitCoin seem fairly easy to get
8264 access to, but there are very few places to spend it. I am not really
8265 a regular user of any of the vendor types currently accepting BitCoin,
8266 so I wonder when my kind of shop would start accepting BitCoins. I
8267 would like to buy electronics, travels and subway tickets, not herbs
8268 and books. :) The currency is young, and this will improve over time
8269 if it become popular, but I suspect regular banks will start to lobby
8270 to get BitCoin declared illegal if it become popular. I
'm sure they
8271 will claim it is helping fund terrorism and money laundering (which
8272 probably would be true, as is any currency in existence), but I
8273 believe the problems should be solved elsewhere and not by blaming
8274 currencies.
</p
>
8276 <p
>The process of creating new BitCoins is called mining, and it is
8277 CPU intensive process that depend on a bit of luck as well (as one is
8278 competing against all the other miners currently spending CPU cycles
8279 to see which one get the next lump of cash). The
"winner
" get
50
8280 BitCoin when this happen. Yesterday I came across the obvious way to
8281 join forces to increase ones changes of getting at least some coins,
8282 by coordinating the work on mining BitCoins across several machines
8283 and people, and sharing the result if one is lucky and get the
50
8285 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8286 if this sounds interesting. I have not had time to try to set up a
8287 machine to participate there yet, but have seen that running on ones
8288 own for a few days have not yield any BitCoins througth mining
8291 <p
>Update
2010-
12-
15: Found an
<a
8292 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8293 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8294 it was interesting to read. The arguments presented seem to be
8295 equally valid for gold, which was used as a currency for many years.
</p
>
8300 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8301 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8302 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8303 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8304 <description><p
>With this weeks lawless
8305 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8306 attacks
</a
> on Wikileak and
8307 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8308 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8309 not be trusted to handle money transactions.
8311 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8312 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8313 mine mentioned earlier. I decided to follow Simon
's example, and get
8314 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8315 some help from my friend to get it all running, and he even handed me
8316 some bitcoins to get started. I even donated a few bitcoins to Simon
8317 for helping me remember BitCoin.
</p
>
8319 <p
>So, what is bitcoins, you probably wonder? It is a digital
8320 crypto-currency, decentralised and handled using peer-to-peer
8321 networks. It allows anonymous transactions and prohibits central
8322 control over the transactions, making it impossible for governments
8323 and companies alike to block donations and other transactions. The
8324 source is free software, and while the key dependency wxWidgets
2.9
8325 for the graphical user interface is missing in Debian, the command
8326 line client builds just fine. Hopefully Jonas
8327 <a href=
"http://bugs.debian.org/
578157">will get the package into
8328 Debian
</a
> soon.
</p
>
8330 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8331 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8332 bitcoins
</a
> when selling services and goods, and there are even
8333 currency
"stock
" markets where the exchange rate is decided. There
8334 are not many users so far, but the concept seems promising. If you
8335 want to get started and lack a friend with any bitcoins to spare,
8337 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8338 bitcoin at the time of writing). Use
8339 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8340 on the current exchange rates.
</p
>
8342 <p
>As an experiment, I have decided to set up bitcoind on one of my
8343 machines. If you want to support my activity, please send Bitcoin
8344 donations to the address
8345 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8350 <title>Why isn
't Debian Edu using VLC?
</title>
8351 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8353 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8354 <description><p
>In the latest issue of Linux Journal, the readers choices were
8355 presented, and the winner among the multimedia player were VLC.
8356 Personally, I like VLC, and it is my player of choice when I first try
8357 to play a video file or stream. Only if VLC fail will I drag out
8358 gmplayer to see if it can do better. The reason is mostly the failure
8359 model and trust. When VLC fail, it normally pop up a error message
8360 reporting the problem. When mplayer fail, it normally segfault or
8361 just hangs. The latter failure mode drain my trust in the program.
<p
>
8363 <p
>But even if VLC is my player of choice, we have choosen to use
8364 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8365 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8366 plugin to play web videos seamlessly, and the VLC browser plugin is
8367 not very good. For example, it lack in-line control buttons, so there
8368 is no way for the user to pause the video. Also, when I
8369 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8370 tested the browser plugins
</a
> available in Debian, the VLC plugin
8371 failed on several video pages where mplayer based plugins worked. If
8372 the browser plugin for VLC was as good as the gecko-mediaplayer
8373 package (which uses mplayer), we would switch.
</P
>
8375 <p
>While VLC is a good player, its user interface is slightly
8376 annoying. The most annoying feature is its inconsistent use of
8377 keyboard shortcuts. When the player is in full screen mode, its
8378 shortcuts are different from when it is playing the video in a window.
8379 For example, space only work as pause when in full screen mode. I
8380 wish it had consisten shortcuts and that space also would work when in
8381 window mode. Another nice shortcut in gmplayer is [enter] to restart
8382 the current video. It is very nice when playing short videos from the
8383 web and want to restart it when new people arrive to have a look at
8384 what is going on.
</p
>
8389 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8390 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8391 <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>
8392 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8393 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8394 upgrade testing of the
8395 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8396 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8397 This seem like a very good idea, so I adjusted by test scripts and
8398 can now present the updated result from today:
</p
>
8400 <p
>This is for Gnome:
</p
>
8402 <p
>Installed using apt-get, missing with aptitude
</p
>
8404 <blockquote
><p
>
8409 browser-plugin-gnash
8416 freedesktop-sound-theme
8418 gconf-defaults-service
8433 gnome-desktop-environment
8437 gnome-session-canberra
8442 gstreamer0.10-fluendo-mp3
8448 libapache2-mod-dnssd
8451 libaprutil1-dbd-sqlite3
8454 libboost-date-time1.42
.0
8455 libboost-python1.42
.0
8456 libboost-thread1.42
.0
8458 libchamplain-gtk-
0.4-
0
8460 libclutter-gtk-
0.10-
0
8467 libfreerdp-plugins-standard
8482 libgnomepanel2.24-cil
8487 libgtksourceview2.0-common
8488 libmono-addins-gui0.2-cil
8489 libmono-addins0.2-cil
8490 libmono-cairo2.0-cil
8491 libmono-corlib2.0-cil
8492 libmono-i18n-west2.0-cil
8493 libmono-posix2.0-cil
8494 libmono-security2.0-cil
8495 libmono-sharpzip2.84-cil
8496 libmono-system2.0-cil
8499 libndesk-dbus-glib1.0-cil
8500 libndesk-dbus1.0-cil
8510 libtelepathy-farsight0
8519 nautilus-sendto-empathy
8523 python-aptdaemon-gtk
8525 python-beautifulsoup
8540 python-gtksourceview2
8551 python-pkg-resources
8558 python-twisted-conch
8564 python-zope.interface
8569 rhythmbox-plugin-cdrecorder
8576 system-config-printer-udev
8578 telepathy-mission-control-
5
8589 </p
></blockquote
>
8591 <p
>Installed using apt-get, removed with aptitude
</p
>
8593 <blockquote
><p
>
8599 fast-user-switch-applet
8618 libgtksourceview2.0-
0
8620 libsdl1.2debian-alsa
8626 system-config-printer
8631 </p
></blockquote
>
8633 <p
>Installed using aptitude, missing with apt-get
</p
>
8635 <blockquote
><p
>
8636 gstreamer0.10-gnomevfs
8637 </p
></blockquote
>
8639 <p
>Installed using aptitude, removed with apt-get
</p
>
8641 <blockquote
><p
>
8643 </p
></blockquote
>
8645 <p
>This is for KDE:
</p
>
8647 <p
>Installed using apt-get, missing with aptitude
</p
>
8649 <blockquote
><p
>
8651 </p
></blockquote
>
8653 <p
>Installed using apt-get, removed with aptitude
</p
>
8655 <blockquote
><p
>
8658 </p
></blockquote
>
8660 <p
>Installed using aptitude, missing with apt-get
</p
>
8662 <blockquote
><p
>
8676 kdeartwork-emoticons
8678 kdeartwork-theme-icon
8682 kdebase-workspace-bin
8683 kdebase-workspace-data
8697 kscreensaver-xsavers
8712 plasma-dataengines-workspace
8714 plasma-desktopthemes-artwork
8715 plasma-runners-addons
8716 plasma-scriptengine-googlegadgets
8717 plasma-scriptengine-python
8718 plasma-scriptengine-qedje
8719 plasma-scriptengine-ruby
8720 plasma-scriptengine-webkit
8721 plasma-scriptengines
8722 plasma-wallpapers-addons
8723 plasma-widget-folderview
8724 plasma-widget-networkmanagement
8728 xscreensaver-data-extra
8730 xscreensaver-gl-extra
8731 xscreensaver-screensaver-bsod
8732 </p
></blockquote
>
8734 <p
>Installed using aptitude, removed with apt-get
</p
>
8736 <blockquote
><p
>
8738 google-gadgets-common
8756 libggadget-qt-
1.0-
0b
8761 libkonqsidebarplugin4a
8770 libplasma-geolocation-interface4
8772 libplasmagenericshell4
8786 libsmokeknewstuff2-
3
8787 libsmokeknewstuff3-
3
8789 libsmokektexteditor3
8797 libsmokeqtnetwork4-
3
8803 libsmokeqtuitools4-
3
8815 plasma-dataengines-addons
8816 plasma-scriptengine-superkaramba
8817 plasma-widget-lancelot
8818 plasma-widgets-addons
8819 plasma-widgets-workspace
8823 update-notifier-common
8824 </p
></blockquote
>
8826 <p
>Running apt-get autoremove made the results using apt-get and
8827 aptitude a bit more similar, but there are still quite a lott of
8828 differences. I have no idea what packages should be installed after
8829 the upgrade, but hope those that do can have a look.
</p
>
8834 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8835 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8836 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8837 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8838 <description><p
>Most of the computers in use by the
8839 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8840 are virtual machines. And they have been Xen machines running on a
8841 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8842 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8843 bit harder that it could have been, because we set up the Xen virtual
8844 machines to get the virtual partitions from LVM, which as far as I
8845 know is not supported by KVM. So to migrate, we had to convert
8846 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8849 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8850 nice recipe
</a
> to do this, and wrote the following script to do the
8851 migration. It uses qemu-img from the qemu package to make the disk
8852 image, parted to partition it, losetup and kpartx to present the disk
8853 image partions as devices, and dd to copy the data. I NFS mounted the
8854 new servers storage area on the old server to do the migration.
</p
>
8860 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8865 if [ -z
"$
1" ] ; then
8866 echo
"Usage: $
0 &lt;hostname
&gt;
"
8872 if [ ! -e /dev/vg_data/$host-disk ] ; then
8873 echo
"error: unable to find LVM volume for $host
"
8877 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8878 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8879 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8880 totalsize=$(( ( $disksize + $swapsize ) ))
8883 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8884 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8886 parted $img mklabel msdos
8887 parted $img mkpart primary linux-swap
0 $disksize
8888 parted $img mkpart primary ext2 $disksize $totalsize
8889 parted $img set
1 boot on
8892 losetup /dev/loop0 $img
8893 kpartx -a /dev/loop0
8895 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8896 fsck.ext3 -f /dev/mapper/loop0p1 || true
8897 mkswap /dev/mapper/loop0p2
8899 kpartx -d /dev/loop0
8900 losetup -d /dev/loop0
8903 <p
>The script is perhaps so simple that it is not copyrightable, but
8904 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8906 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8907 the new disk image attached, installed grub-pc and linux-image-
686 and
8908 set up grub to boot from the disk image. After this, the KVM machines
8909 seem to work just fine.
</p
>
8914 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8915 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8916 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8917 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8918 <description><p
>I
'm still running upgrade testing of the
8919 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8920 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8921 status. Here is a short update based on a test I ran
20101118.
</p
>
8923 <p
>I still do not know what a correct migration should look like, so I
8924 report any differences between apt and aptitude and hope someone else
8925 can see if anything should be changed.
</p
>
8927 <p
>This is for Gnome:
</p
>
8929 <p
>Installed using apt-get, missing with aptitude
</p
>
8931 <blockquote
><p
>
8932 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8933 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8934 dmz-cursor-theme empathy empathy-common finger
8935 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8936 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8937 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8938 gnome-cards-data gnome-codec-install gnome-core
8939 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8940 gnome-search-tool gnome-session-canberra gnome-spell
8941 gnome-system-log gnome-themes-extras gnome-themes-more
8942 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8943 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8944 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8945 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8946 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8947 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8948 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8949 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8950 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8951 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8952 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8953 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8954 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8955 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8956 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8957 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8958 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8959 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8960 libmono-security2.0-cil libmono-sharpzip2.84-cil
8961 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8962 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8963 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8964 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8965 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8966 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8967 libxalan2-java libxerces2-java media-player-info mesa-utils
8968 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8969 nautilus-sendto-empathy openoffice.org-writer2latex
8970 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8971 python-aptdaemon python-aptdaemon-gtk python-axiom
8972 python-beautifulsoup python-bugbuddy python-clientform
8973 python-coherence python-configobj python-crypto python-cupshelpers
8974 python-cupsutils python-eggtrayicon python-elementtree
8975 python-epsilon python-evolution python-feedparser python-gdata
8976 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8977 python-gtksourceview2 python-httplib2 python-louie python-mako
8978 python-markupsafe python-mechanize python-nevow python-notify
8979 python-opengl python-openssl python-pam python-pkg-resources
8980 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8981 python-tagpy python-twisted-bin python-twisted-conch
8982 python-twisted-core python-twisted-web python-utidylib python-webkit
8983 python-xdg python-zope.interface remmina remmina-plugin-data
8984 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8985 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8986 software-center svgalibg1 system-config-printer-udev
8987 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8988 totem totem-coherence totem-mozilla totem-plugins
8989 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8991 </p
></blockquote
>
8993 Installed using apt-get, removed with aptitude
8995 <blockquote
><p
>
8996 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8997 epiphany-extensions epiphany-gecko evolution-exchange
8998 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8999 gedit-common gnome-app-install gnome-games gnome-games-data
9000 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9001 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9002 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9003 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
9004 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
9005 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
9006 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
9007 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9008 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9009 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9010 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
9011 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
9012 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9013 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9014 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9015 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9016 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
9017 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
9018 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
9019 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
9020 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
9021 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9022 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9023 sound-juicer swfdec-gnome system-config-printer totem-common
9024 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9025 </p
></blockquote
>
9027 <p
>Installed using aptitude, missing with apt-get
</p
>
9029 <blockquote
><p
>
9030 gstreamer0.10-gnomevfs
9031 </p
></blockquote
>
9033 <p
>Installed using aptitude, removed with apt-get
</p
>
9035 <blockquote
><p
>
9037 </p
></blockquote
>
9039 <p
>This is for KDE:
</p
>
9041 <p
>Installed using apt-get, missing with aptitude
</p
>
9043 <blockquote
><p
>
9044 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
9045 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9046 ghostscript-x git gnome-audio gnugo granatier gs-common
9047 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9048 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9049 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9050 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9051 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9052 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9053 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9054 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9055 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9056 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9057 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9058 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
9059 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9060 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9061 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9062 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9063 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9064 libkrossui4 libmailtools-perl libmime-tools-perl
9065 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9066 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9067 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9068 lirc luatex marble networkstatus noatun-plugins
9069 openoffice.org-writer2latex palapeli palapeli-data parley
9070 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9071 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9072 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9074 </p
></blockquote
>
9076 <p
>Installed using apt-get, removed with aptitude
</p
>
9078 <blockquote
><p
>
9079 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9080 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9081 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9082 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9083 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9084 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9085 kitchensync kiten kjumpingcube klatin klettres klickety klines
9086 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9087 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9088 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9089 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9090 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9091 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9092 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9093 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9094 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9095 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
9096 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
9097 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9098 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
9099 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
9100 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9101 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9102 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9103 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9104 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9105 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9106 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
9107 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
9108 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9109 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9110 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9111 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9112 </p
></blockquote
>
9114 <p
>Installed using aptitude, missing with apt-get
</p
>
9116 <blockquote
><p
>
9117 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9118 kdeartwork kdebase kdebase-apps kdebase-workspace
9119 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9120 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9121 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9122 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9123 xscreensaver-screensaver-bsod
9124 </p
></blockquote
>
9126 <p
>Installed using aptitude, removed with apt-get
</p
>
9128 <blockquote
><p
>
9129 kdebase-bin konq-plugins konqueror
9130 </p
></blockquote
>
9135 <title>Gnash buildbot slave and Debian kfreebsd
</title>
9136 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
9137 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
9138 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
9139 <description><p
>Answering
9140 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
9141 call from the Gnash project
</a
> for
9142 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
9143 current source, I have set up a virtual KVM machine on the Debian
9144 Edu/Skolelinux virtualization host to test the git source on
9145 Debian/Squeeze. I hope this can help the developers in getting new
9146 releases out more often.
</p
>
9148 <p
>As the developers want less main-stream build platforms tested to,
9149 I have considered setting up a
<a
9150 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
9151 machine as well. I have also considered using the kfreebsd
9152 architecture in Debian as a file server in NUUG to get access to the
5
9153 TB zfs volume we currently use to store DV video. Because of this, I
9154 finally got around to do a test installation of Debian/Squeeze with
9155 kfreebsd. Installation went fairly smooth, thought I noticed some
9156 visual glitches in the cdebconf dialogs (black cursor left on the
9157 screen at random locations). Have not gotten very far with the
9158 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9159 fatal problem. Have to spend some more time on it to see if it is
9160 useful as a file server for NUUG. Will try to find time to set up a
9161 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
9166 <title>Debian in
3D
</title>
9167 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
9168 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
9169 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
9170 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
9172 <p
>3D printing is just great. I just came across this Debian logo in
9174 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
9175 thingiverse blog
</a
>.
</p
>
9180 <title>Software updates
2010-
10-
24</title>
9181 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
9182 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
9183 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
9184 <description><p
>Some updates.
</p
>
9186 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
9187 raise money for the project is going well. The lower limit of
10
9188 signers was reached in
24 hours, and so far
13 people have signed it.
9189 More signers and more funding is most welcome, and I am really curious
9190 how far we can get before the time limit of December
24 is reached.
9193 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
9194 about what appear to be a great code coverage tool capable of
9195 generating code coverage stats without any changes to the source code.
9197 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
9198 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
9199 It is missing in Debian, but the git source built just fine in Squeeze
9200 after I installed libelf-dev, libdwarf-dev, pkg-config and
9201 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9202 solvable. I hope kcov make it into Debian soon.
</p
>
9204 <p
>Finally found time to wrap up the release notes for
<a
9205 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
9206 new alpha release of Debian Edu
</a
>, and just published the second
9207 alpha test release of the Squeeze based Debian Edu /
9208 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
9209 release. Give it a try if you need a complete linux solution for your
9210 school, including central infrastructure server, workstations, thin
9211 client servers and diskless workstations. A nice touch added
9212 yesterday is RDP support on the thin client servers, for windows
9213 clients to get a Linux desktop on request.
</p
>
9218 <title>Some notes on Flash in Debian and Debian Edu
</title>
9219 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
9220 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
9221 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
9222 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
9223 popularity-contest numbers
</a
>, the adobe-flashplugin package the
9224 second most popular used package that is missing in Debian. The sixth
9225 most popular is flashplayer-mozilla. This is a clear indication that
9226 working flash is important for Debian users. Around
10 percent of the
9227 users submitting data to popcon.debian.org have this package
9228 installed.
</p
>
9230 <p
>In the report written by Lars Risan in August
2008
9231 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
9232 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9233 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
9234 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
9235 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
9236 web sites require Flash to work, and lacking working Flash support in
9237 the web browser and the problems with installing it was perceived as a
9238 good reason to stay with Windows.
</p
>
9240 <p
>I once saw a funny and sad comment in a web forum, where Linux was
9241 said to be the retarded cousin that did not really understand
9242 everything you told him but could work fairly well. This was a
9243 comment regarding the problems Linux have with proprietary formats and
9244 non-standard web pages, and is sad because it exposes a fairly common
9245 understanding of whose fault it is if web pages that only work in for
9246 example Internet Explorer
6 fail to work on Firefox, and funny because
9247 it explain very well how annoying it is for users when Linux
9248 distributions do not work with the documents they receive or the web
9249 pages they want to visit.
</p
>
9251 <p
>This is part of the reason why I believe it is important for Debian
9252 and Debian Edu to have a well working Flash implementation in the
9253 distribution, to get at least popular sites as Youtube and Google
9254 Video to working out of the box. For Squeeze, Debian have the chance
9255 to include the latest version of Gnash that will make this happen, as
9256 the new release
0.8.8 was published a few weeks ago and is resting in
9257 unstable. The new version work with more sites that version
0.8.7.
9258 The Gnash maintainers have asked for a freeze exception, but the
9259 release team have not had time to reply to it yet. I hope they agree
9260 with me that Flash is important for the Debian desktop users, and thus
9261 accept the new package into Squeeze.
</p
>
9266 <title>Circular package dependencies harms apt recovery
</title>
9267 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9268 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9269 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9270 <description><p
>I discovered this while doing
9271 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9272 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9273 in Debian still got circular dependencies, and it is often claimed
9274 that apt and aptitude should be able to handle this just fine, but
9275 some times these dependency loops causes apt to fail.
</p
>
9277 <p
>An example is from todays
9278 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9279 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9280 causes perl-modules to fail to upgrade. The cause is simple. If a
9281 package fail to unpack, then only part of packages with the circular
9282 dependency might end up being unpacked when unpacking aborts, and the
9283 ones already unpacked will fail to configure in the recovery phase
9284 because its dependencies are unavailable.
</p
>
9286 <p
>In this log, the problem manifest itself with this error:
</p
>
9288 <blockquote
><pre
>
9289 dpkg: dependency problems prevent configuration of perl-modules:
9290 perl-modules depends on perl (
>=
5.10.1-
1); however:
9291 Version of perl on system is
5.10.0-
19lenny
2.
9292 dpkg: error processing perl-modules (--configure):
9293 dependency problems - leaving unconfigured
9294 </pre
></blockquote
>
9296 <p
>The perl/perl-modules circular dependency is already
9297 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9298 hopefully be solved as soon as possible, but it is not the only one,
9299 and each one of these loops in the dependency tree can cause similar
9300 failures. Of course, they only occur when there are bugs in other
9301 packages causing the unpacking to fail, but it is rather nasty when
9302 the failure of one package causes the problem to become worse because
9303 of dependency loops.
</p
>
9306 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9307 tireless effort by Bill Allombert
</a
>, the number of circular
9309 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9310 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9312 <p
>Todays testing also exposed a bug in
9313 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9314 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9315 apt-get and aptitude, the latter possibly caused by some circular
9316 dependency. Reported both to BTS to try to get someone to look at
9322 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9323 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9324 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9325 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9326 <description><p
>This is a
9327 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9329 <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
9331 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9332 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9334 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9335 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9336 and dhcp3-server-ldap in Debian use the LDAP server. The two
9337 implementations are quite different in how they use LDAP.
</p
>
9339 To get this information, I started slapd with debugging enabled and
9340 dumped the debug output to a file to get the LDAP searches performed
9341 on a Debian Edu main-server. Here is a summary.
9343 <p
><strong
>powerdns
</strong
></p
>
9345 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9346 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9349 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9350 One
"strict
" mode where the forward and reverse DNS lookups are done
9351 using the same LDAP objects, and a
"tree
" mode where the forward and
9352 reverse entries are in two different subtrees in LDAP with a structure
9353 based on the DNS names, as in tjener.intern and
9354 2.2.0.10.in-addr.arpa.
</p
>
9356 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9357 base, and uses a
"base
" scoped search for the DNS name by adding
9358 "dc=tjener,dc=intern,
" to the base with a filter for
9359 "(associateddomain=tjener.intern)
" for the forward entry and
9360 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9361 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9362 forward entries, it is looking for attributes named dnsttl, arecord,
9363 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9364 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9365 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9366 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9367 spfrecord and modifytimestamp. For reverse entries it is looking for
9368 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9369 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9370 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9371 ldapsearch commands could look like this:
</p
>
9373 <blockquote
><pre
>
9374 ldapsearch -h ldap \
9375 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9376 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9377 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9378 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9379 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9380 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9382 ldapsearch -h ldap \
9383 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9384 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9385 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9386 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9387 srvrecord naptrrecord modifytimestamp
9388 </pre
></blockquote
>
9390 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9391 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9392 example LDAP objects used there. In addition to these objects, the
9393 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9394 also exist.
</p
>
9396 <blockquote
><pre
>
9397 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9399 objectclass: dnsdomain
9400 objectclass: domainrelatedobject
9403 associateddomain: tjener.intern
9405 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9407 objectclass: dnsdomain2
9408 objectclass: domainrelatedobject
9410 ptrrecord: tjener.intern
9411 associateddomain:
2.2.0.10.in-addr.arpa
9412 </pre
></blockquote
>
9414 <p
>In strict mode, the server behaves differently. When looking for
9415 forward DNS entries, it is doing a
"subtree
" scoped search with the
9416 same base as in the tree mode for a object with filter
9417 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9418 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9419 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9420 naptrrecord and modifytimestamp. For reverse entires it also do a
9421 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9422 and the requested attributes are associateddomain, dnsttl and
9423 modifytimestamp. In short, in strict mode the objects with ptrrecord
9424 go away, and the arecord attribute in the forward object is used
9427 <p
>The forward and reverse searches can be simulated using ldapsearch
9428 like this:
</p
>
9430 <blockquote
><pre
>
9431 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9432 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9433 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9434 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9435 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9436 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9438 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9439 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9440 </pre
></blockquote
>
9442 <p
>In addition to the forward and reverse searches , there is also a
9443 search for SOA records, which behave similar to the forward and
9444 reverse lookups.
</p
>
9446 <p
>A thing to note with the PowerDNS behaviour is that it do not
9447 specify any objectclass names, and instead look for the attributes it
9448 need to generate a DNS reply. This make it able to work with any
9449 objectclass that provide the needed attributes.
</p
>
9451 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9452 dnsdomain2 schemas. The latter is used for reverse entries like
9453 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9455 <p
>In Debian Edu, we have created DNS objects using the object classes
9456 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9457 attributes) and domainrelatedobject (for associatedDomain). The use
9458 of structural object classes make it impossible to combine these
9459 classes with the object classes used by DHCP.
</p
>
9461 <p
>There are other schemas that could be used too, for example the
9462 dnszone structural object class used by Gosa and bind-sdb for the DNS
9463 attributes combined with the domainrelatedobject object class, but in
9464 this case some unused attributes would have to be included as well
9465 (zonename and relativedomainname).
</p
>
9467 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9468 mode and not use any of the existing objectclasses (dnsdomain,
9469 dnsdomain2 and dnszone) when one want to combine the DNS information
9470 with DHCP information, and instead create a auxiliary object class
9471 defined something like this (using the attributes defined for
9472 dnsdomain and dnsdomain2 or dnszone):
</p
>
9474 <blockquote
><pre
>
9475 objectclass ( some-oid NAME
'dnsDomainAux
'
9478 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9479 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9480 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9481 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9482 A6Record $ DNAMERecord
9484 </pre
></blockquote
>
9486 <p
>This will allow any object to become a DNS entry when combined with
9487 the domainrelatedobject object class, and allow any entity to include
9488 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9489 developers asking for their view on this schema and if they are
9490 interested in providing such schema with PowerDNS, and I hope my
9491 message will be accepted into their mailing list soon.
</p
>
9493 <p
><strong
>ISC dhcp
</strong
></p
>
9495 <p
>The DHCP server searches for specific objectclass and requests all
9496 the object attributes, and then uses the attributes it want. This
9497 make it harder to figure out exactly what attributes are used, but
9498 thanks to the working example in Debian Edu I can at least get an idea
9499 what is needed without having to read the source code.
</p
>
9501 <p
>In the DHCP server configuration, the LDAP base to use and the
9502 search filter to use to locate the correct dhcpServer entity is
9503 stored. These are the relevant entries from
9504 /etc/dhcp3/dhcpd.conf:
</p
>
9506 <blockquote
><pre
>
9507 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9508 ldap-dhcp-server-cn
"dhcp
";
9509 </pre
></blockquote
>
9511 <p
>The DHCP server uses this information to nest all the DHCP
9512 configuration it need. The cn
"dhcp
" is located using the given LDAP
9513 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9514 search result is this entry:
</p
>
9516 <blockquote
><pre
>
9517 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9520 objectClass: dhcpServer
9521 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9522 </pre
></blockquote
>
9524 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9525 subtree with DHCP configuration. The DHCP configuration subtree base
9526 is located using a base scope search with base
"cn=DHCP
9527 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9528 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9529 The search result is this entry:
</p
>
9531 <blockquote
><pre
>
9532 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9535 objectClass: dhcpService
9536 objectClass: dhcpOptions
9537 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9538 dhcpStatements: ddns-update-style none
9539 dhcpStatements: authoritative
9540 dhcpOption: smtp-server code
69 = array of ip-address
9541 dhcpOption: www-server code
72 = array of ip-address
9542 dhcpOption: wpad-url code
252 = text
9543 </pre
></blockquote
>
9545 <p
>Next, the entire subtree is processed, one level at the time. When
9546 all the DHCP configuration is loaded, it is ready to receive requests.
9547 The subtree in Debian Edu contain objects with object classes
9548 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9549 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9550 and information about netmasks, dynamic range etc. Leaving out the
9551 details here because it is not relevant for the focus of my
9552 investigation, which is to see if it is possible to merge dns and dhcp
9553 related computer objects.
</p
>
9555 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9556 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9557 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9558 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9559 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9562 <blockquote
><pre
>
9563 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9566 objectClass: dhcpHost
9567 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9568 dhcpStatements: fixed-address hostname
9569 </pre
></blockquote
>
9571 <p
>There is less flexiblity in the way LDAP searches are done here.
9572 The object classes need to have fixed names, and the configuration
9573 need to be stored in a fairly specific LDAP structure. On the
9574 positive side, the invidiual dhcpHost entires can be anywhere without
9575 the DN pointed to by the dhcpServer entries. The latter should make
9576 it possible to group all host entries in a subtree next to the
9577 configuration entries, and this subtree can also be shared with the
9578 DNS server if the schema proposed above is combined with the dhcpHost
9579 structural object class.
9581 <p
><strong
>Conclusion
</strong
></p
>
9583 <p
>The PowerDNS implementation seem to be very flexible when it come
9584 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9585 come to the the LDAP structure, the
"strict
" mode is very flexible,
9586 allowing DNS objects to be stored anywhere under the base cn specified
9587 in the configuration.
</p
>
9589 <p
>The DHCP implementation on the other hand is very inflexible, both
9590 regarding which LDAP schemas to use and which LDAP structure to use.
9591 I guess one could implement ones own schema, as long as the
9592 objectclasses and attributes have the names used, but this do not
9593 really help when the DHCP subtree need to have a fairly fixed
9594 structure.
</p
>
9596 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9597 this might work for Debian Edu:
</p
>
9599 <blockquote
><pre
>
9601 cn=machine-info (dhcpService) - dhcpServiceDN points here
9602 cn=dhcp (dhcpServer)
9603 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9604 cn=
10.0.2.0 (dhcpSubnet)
9605 cn=group1 (dhcpGroup/dhcpOptions)
9606 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9607 cn=
192.168.0.0 (dhcpSubnet)
9608 cn=group1 (dhcpGroup/dhcpOptions)
9609 ou=machines - PowerDNS base points here
9610 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9611 </pre
></blockquote
>
9613 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9614 entries to be in the dhcpGroup subtrees, the entries can be stored
9615 there instead of a common machines subtree, and the PowerDNS base
9616 would have to be moved one level up to the machine-info subtree.
</p
>
9618 <p
>The combined object under the machines subtree would look something
9619 like this:
</p
>
9621 <blockquote
><pre
>
9622 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9625 objectClass: dhcpHost
9626 objectclass: domainrelatedobject
9627 objectclass: dnsDomainAux
9628 associateddomain: hostname.intern
9629 arecord:
10.11.12.13
9630 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9631 dhcpStatements: fixed-address hostname.intern
9632 </pre
></blockquote
>
9634 </p
>One could even add the LTSP configuration associated with a given
9635 machine, as long as the required attributes are available in a
9636 auxiliary object class.
</p
>
9641 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9642 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9643 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9644 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9645 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9646 DHCP services in Debian Edu to use the same LDAP objects for a given
9647 computer, to avoid the possibility of having a inconsistent state for
9648 a computer in LDAP (as in DHCP but no DNS entry or the other way
9649 around) and make it easier to add computers to LDAP.
</p
>
9651 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9652 information finally found a solution that seem to work.
</p
>
9654 <p
>The old setup required three LDAP objects for a given computer.
9655 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9656 we switch powerdns to use its strict LDAP method (ldap-method=strict
9657 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9658 merged into one while making it impossible to transfer the reverse map
9659 to a slave DNS server.
</p
>
9661 <p
>If we also replace the object class used to get the DNS related
9662 attributes to one allowing these attributes to be combined with the
9663 dhcphost object class, we can merge the DNS and DHCP entries into one.
9664 I
've written such object class in the dnsdomainaux.schema file (need
9665 proper OIDs, but that is a minor issue), and tested the setup. It
9666 seem to work.
</p
>
9668 <p
>With this test setup in place, we can get away with one LDAP object
9669 for both DNS and DHCP, and even the LTSP configuration I suggested in
9670 an earlier email. The combined LDAP object will look something like
9673 <blockquote
><pre
>
9674 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9676 objectClass: dhcphost
9677 objectclass: domainrelatedobject
9678 objectclass: dnsdomainaux
9679 associateddomain: hostname.intern
9680 arecord:
10.11.12.13
9681 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9682 dhcpstatements: fixed-address hostname
9684 </pre
></blockquote
>
9686 <p
>The DNS server uses the associateddomain and arecord entries, while
9687 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9688 before asking DNS to resolve the fixed-adddress. LTSP will use
9689 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9691 <p
>I am not yet sure if I can get the DHCP server to look for its
9692 dhcphost in a different location, to allow us to put the objects
9693 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9694 that. If I can
't figure out a way to do that, we can still get rid of
9695 the hosts subtree and move all its content into the DHCP Config tree
9696 (which probably should be renamed to be more related to the new
9697 content. I suspect cn=dnsdhcp,ou=services or something like that
9698 might be a good place to put it.
</p
>
9700 <p
>If you want to help out with implementing this for Debian Edu,
9701 please contact us on debian-edu@lists.debian.org.
</p
>
9706 <title>Idea for storing LTSP configuration in LDAP
</title>
9707 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9708 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9709 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9710 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9711 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9712 clients, and that this can be used to fetch configuration from LDAP if
9713 Debian Edu choose to store configuration there.
</p
>
9715 <p
>Armed with this information, I got inspired and wrote a test module
9716 to get configuration from LDAP. The idea is to look up the MAC
9717 address of the client in LDAP, and look for attributes on the form
9718 ltspconfigsetting=value, and use this to export SETTING=value to the
9719 LTSP clients.
</p
>
9721 <p
>The goal is to be able to store the LTSP configuration attributes
9722 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9723 allowing us to store all information about a computer in one place.
</p
>
9725 <p
>This is a untested draft implementation, and I welcome feedback on
9726 this approach. A real LDAP schema for the ltspClientAux objectclass
9727 need to be written. Comments, suggestions, etc?
</p
>
9729 <blockquote
><pre
>
9730 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9732 # Fetch LTSP client settings from LDAP based on MAC address
9734 # Uses ethernet address as stored in the dhcpHost objectclass using
9735 # the dhcpHWAddress attribute or ethernet address stored in the
9736 # ieee802Device objectclass with the macAddress attribute.
9738 # This module is written to be schema agnostic, and only depend on the
9739 # existence of attribute names.
9741 # The LTSP configuration variables are saved directly using a
9742 # ltspConfig prefix and uppercasing the rest of the attribute name.
9743 # To set the SERVER variable, set the ltspConfigServer attribute.
9745 # Some LDAP schema should be created with all the relevant
9746 # configuration settings. Something like this should work:
9748 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9751 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9753 LDAPSERVER=$(debian-edu-ldapserver)
9754 if [
"$LDAPSERVER
" ] ; then
9755 LDAPBASE=$(debian-edu-ldapserver -b)
9756 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9757 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9758 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9759 grep
'^ltspConfig
' | while read attr value ; do
9760 # Remove prefix and convert to upper case
9761 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9762 # bass value on to clients
9763 eval
"$attr=$value; export $attr
"
9767 </pre
></blockquote
>
9769 <p
>I
'm not sure this shell construction will work, because I suspect
9770 the while block might end up in a subshell causing the variables set
9771 there to not show up in ltsp-config, but if that is the case I am sure
9772 the code can be restructured to make sure the variables are passed on.
9773 I expect that can be solved with some testing. :)
</p
>
9775 <p
>If you want to help out with implementing this for Debian Edu,
9776 please contact us on debian-edu@lists.debian.org.
</p
>
9778 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9779 configuration in LDAP that was created around year
2000 by
9780 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9781 Xperience, Inc.,
2000</a
>. I found its
9782 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9783 personal home page over at redhat.com.
</p
>
9788 <title>jXplorer, a very nice LDAP GUI
</title>
9789 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9790 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9791 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9792 <description><p
>Since
9793 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9794 last post
</a
> about available LDAP tools in Debian, I was told about a
9795 LDAP GUI that is even better than luma. The java application
9796 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9797 moving LDAP objects and subtrees using drag-and-drop, and can
9798 authenticate using Kerberos. I have only tested the Kerberos
9799 authentication, but do not have a LDAP setup allowing me to rewrite
9800 LDAP with my test user yet. It is
9801 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9802 Debian
</a
> testing and unstable at the moment. The only problem I
9803 have with it is how it handle errors. If something go wrong, its
9804 non-intuitive behaviour require me to go through some query work list
9805 and remove the failing query. Nothing big, but very annoying.
</p
>
9810 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9811 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9812 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9813 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9814 <description><p
>Here is a short update on my
<a
9815 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9816 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9817 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9818 not reporting the status for KDE, because the upgrade crashes when
9819 aptitude try because of missing conflicts
9820 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9821 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9823 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9824 complete list of the installed packages. Based on this I see these
9825 differences when I did a test run today. As usual, I do not really
9826 know what the correct set of packages would be, but thought it best to
9827 publish the difference.
</p
>
9829 <p
>Installed using apt-get, missing with aptitude
</p
>
9831 <blockquote
><p
>
9832 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9833 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9834 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9835 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9836 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9837 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9838 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9839 python-gtkmozembed svgalibg1 xserver-xephyr zip
9840 </p
></blockquote
>
9842 <p
>Installed using apt-get, removed with aptitude
</p
>
9844 <blockquote
><p
>
9845 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9846 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9847 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9848 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9849 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9850 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9851 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9852 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9853 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9854 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9855 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9856 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9857 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9858 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9859 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9860 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9861 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9862 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9863 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9864 mysql-common swfdec-gnome totem-gstreamer wodim
9865 </p
></blockquote
>
9867 <p
>Installed using aptitude, missing with apt-get
</p
>
9869 <blockquote
><p
>
9870 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9871 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9872 xserver-xorg-input-all xserver-xorg-input-evdev
9873 xserver-xorg-input-kbd xserver-xorg-input-mouse
9874 xserver-xorg-input-synaptics xserver-xorg-video-all
9875 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9876 xserver-xorg-video-chips xserver-xorg-video-cirrus
9877 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9878 xserver-xorg-video-glint xserver-xorg-video-i128
9879 xserver-xorg-video-i740 xserver-xorg-video-mach64
9880 xserver-xorg-video-mga xserver-xorg-video-neomagic
9881 xserver-xorg-video-nouveau xserver-xorg-video-nv
9882 xserver-xorg-video-r128 xserver-xorg-video-radeon
9883 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9884 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9885 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9886 xserver-xorg-video-sis xserver-xorg-video-sisusb
9887 xserver-xorg-video-tdfx xserver-xorg-video-tga
9888 xserver-xorg-video-trident xserver-xorg-video-tseng
9889 xserver-xorg-video-vesa xserver-xorg-video-vmware
9890 xserver-xorg-video-voodoo
9891 </p
></blockquote
>
9893 <p
>Installed using aptitude, removed with apt-get
</p
>
9895 <blockquote
><p
>
9896 deskbar-applet xserver-xorg xserver-xorg-core
9897 xserver-xorg-input-wacom xserver-xorg-video-intel
9898 xserver-xorg-video-openchrome
9899 </p
></blockquote
>
9901 <p
>I was told on IRC that the xorg-xserver package was
9902 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9903 in git
</a
> today to try to get apt-get to not remove xorg completely.
9904 No idea when it hits Squeeze, but when it does I hope it will reduce
9905 the difference somewhat.
9910 <title>LUMA, a very nice LDAP GUI
</title>
9911 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9912 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9913 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9914 <description><p
>The last few days I have been looking into the status of the LDAP
9915 directory in Debian Edu, and in the process I started to miss a GUI
9916 tool to browse the LDAP tree. The only one I was able to find in
9917 Debian/Squeeze and Lenny is
9918 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9919 be a great tool to get a overview of the current LDAP directory
9920 populated by default in Skolelinux. Thanks to it, I have been able to
9921 find empty and obsolete subtrees, misplaced objects and duplicate
9922 objects. It will be installed by default in Debian/Squeeze. If you
9923 are working with LDAP, give it a go. :)
</p
>
9925 <p
>I did notice one problem with it I have not had time to report to
9926 the BTS yet. There is no .desktop file in the package, so the tool do
9927 not show up in the Gnome and KDE menus, but only deep down in in the
9928 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9931 <p
>I have not yet been able to get it to modify the tree yet. I would
9932 like to move objects and remove subtrees directly in the GUI, but have
9933 not found a way to do that with LUMA yet. So in the mean time, I use
9934 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9936 <p
>If you have tips on other GUI tools for LDAP that might be useful
9937 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9939 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9940 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9941 useful GUI alternative. It seem like a good tool, but is unmaintained
9942 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9943 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9948 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9949 <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>
9950 <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>
9951 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9952 <description><p
>A while back, I
9953 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9954 about the fact
</a
> that it is not possible with the provided schemas
9955 for storing DNS and DHCP information in LDAP to combine the two sets
9956 of information into one LDAP object representing a computer.
</p
>
9958 <p
>In the mean time, I discovered that a simple fix would be to make
9959 the dhcpHost object class auxiliary, to allow it to be combined with
9960 the dNSDomain object class, and thus forming one object for one
9961 computer when storing both DHCP and DNS information in LDAP.
</p
>
9963 <p
>If I understand this correctly, it is not safe to do this change
9964 without also changing the assigned number for the object class, and I
9965 do not know enough about LDAP schema design to do that properly for
9966 Debian Edu.
</p
>
9968 <p
>Anyway, for future reference, this is how I believe we could change
9970 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9971 schema
</a
> to solve at least part of the problem with the LDAP schemas
9972 available today from IETF.
</p
>
9975 --- dhcp.schema (revision
65192)
9976 +++ dhcp.schema (working copy)
9978 objectclass (
2.16.840.1.113719.1.203.6.6
9979 NAME
'dhcpHost
'
9980 DESC
'This represents information about a particular client
'
9984 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9985 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9988 <p
>I very much welcome clues on how to do this properly for Debian
9989 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9990 package, and should thus be free to rewrite it as we see fit.
</p
>
9992 <p
>If you want to help out with implementing this for Debian Edu,
9993 please contact us on debian-edu@lists.debian.org.
</p
>
9998 <title>Calling tasksel like the installer, while still getting useful output
</title>
9999 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
10000 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
10001 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
10002 <description><p
>A few times I have had the need to simulate the way tasksel
10003 installs packages during the normal debian-installer run. Until now,
10004 I have ended up letting tasksel do the work, with the annoying problem
10005 of not getting any feedback at all when something fails (like a
10006 conffile question from dpkg or a download that fails), using code like
10009 <blockquote
><pre
>
10010 export DEBIAN_FRONTEND=noninteractive
10011 tasksel --new-install
10012 </pre
></blockquote
>
10014 This would invoke tasksel, let its automatic task selection pick the
10015 tasks to install, and continue to install the requested tasks without
10016 any output what so ever.
10018 Recently I revisited this problem while working on the automatic
10019 package upgrade testing, because tasksel would some times hang without
10020 any useful feedback, and I want to see what is going on when it
10021 happen. Then it occured to me, I can parse the output from tasksel
10022 when asked to run in test mode, and use that aptitude command line
10023 printed by tasksel then to simulate the tasksel run. I ended up using
10026 <blockquote
><pre
>
10027 export DEBIAN_FRONTEND=noninteractive
10028 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
10030 </pre
></blockquote
>
10032 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
10033 --without-recommends -o APT::Install-Recommends=no -y install
10034 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10035 ~pimportant
</tt
>", which will install the gnome desktop task, the
10036 laptop task and all packages with priority standard , required and
10037 important, just like tasksel would have done it during
10038 installation.
</p
>
10040 <p
>A better approach is probably to extend tasksel to be able to
10041 install packages without using debconf-apt-progress, for use cases
10042 like this.
</p
>
10047 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
10048 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
10049 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
10050 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
10051 <description><p
>My
10052 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
10053 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
10054 finally made the upgrade logs available from
10055 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
10056 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10057 apt and aptitude, and found their differences interesting. This time
10058 I will only focus on their removal plans.
</p
>
10060 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
10061 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
10062 surprising part is that it want to remove xorg and all
10063 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10064 sure why. When asking aptitude to do the same, it want to remove
129
10065 packages, but most of them are library packages I suspect are no
10066 longer needed. Both of them want to remove bluetooth packages, which
10067 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
10069 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
10070 which seem like a bad idea and xorg the same way as with Gnome. Asking
10071 aptitude for the same, it wants to remove
192 packages, none which are
10072 too surprising.
</p
>
10074 <p
>I guess the removal of xorg during upgrades should be investigated
10075 and avoided, and perhaps others as well. Here are the complete list
10076 of planned removals. The complete logs is available from the URL
10077 above. Note if you want to repeat these tests, that the upgrade test
10078 for kde+apt-get hung in the tasksel setup because of dpkg asking
10079 conffile questions. No idea why. I worked around it by using
10080 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
10081 continue.
</p
>
10083 <p
><b
>apt-get gnome
72</b
>
10084 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
10085 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10086 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
10087 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10088 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10089 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10090 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10091 xserver-xorg-input-kbd xserver-xorg-input-mouse
10092 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10093 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10094 xserver-xorg-video-ati xserver-xorg-video-chips
10095 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10096 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10097 xserver-xorg-video-glint xserver-xorg-video-i128
10098 xserver-xorg-video-i740 xserver-xorg-video-imstt
10099 xserver-xorg-video-intel xserver-xorg-video-mach64
10100 xserver-xorg-video-mga xserver-xorg-video-neomagic
10101 xserver-xorg-video-nsc xserver-xorg-video-nv
10102 xserver-xorg-video-openchrome xserver-xorg-video-r128
10103 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10104 xserver-xorg-video-rendition xserver-xorg-video-s3
10105 xserver-xorg-video-s3virge xserver-xorg-video-savage
10106 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10107 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10108 xserver-xorg-video-tga xserver-xorg-video-trident
10109 xserver-xorg-video-tseng xserver-xorg-video-v4l
10110 xserver-xorg-video-vesa xserver-xorg-video-vga
10111 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
10112 xulrunner-
1.9-gnome-support
</p
>
10114 <p
><b
>aptitude gnome
129</b
>
10116 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
10117 djvulibre-desktop finger gnome-app-install gnome-mount
10118 gnome-network-admin gnome-spell gnome-vfs-obexftp
10119 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10120 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10121 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10122 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
10123 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
10124 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
10125 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
10126 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
10127 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
10128 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
10129 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
10130 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
10131 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10132 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
10133 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
10134 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
10135 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
10136 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
10137 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10138 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10139 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10140 openoffice.org-writer2latex openssl-blacklist p7zip
10141 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
10142 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10143 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10144 swfdec-mozilla totem-gstreamer update-manager wodim
10145 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10146 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10149 <p
><b
>apt-get kde
82</b
>
10151 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10152 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10153 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10154 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10155 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10156 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10157 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10158 xserver-xorg-input-kbd xserver-xorg-input-mouse
10159 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10160 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10161 xserver-xorg-video-ati xserver-xorg-video-chips
10162 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10163 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10164 xserver-xorg-video-glint xserver-xorg-video-i128
10165 xserver-xorg-video-i740 xserver-xorg-video-imstt
10166 xserver-xorg-video-intel xserver-xorg-video-mach64
10167 xserver-xorg-video-mga xserver-xorg-video-neomagic
10168 xserver-xorg-video-nsc xserver-xorg-video-nv
10169 xserver-xorg-video-openchrome xserver-xorg-video-r128
10170 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10171 xserver-xorg-video-rendition xserver-xorg-video-s3
10172 xserver-xorg-video-s3virge xserver-xorg-video-savage
10173 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10174 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10175 xserver-xorg-video-tga xserver-xorg-video-trident
10176 xserver-xorg-video-tseng xserver-xorg-video-v4l
10177 xserver-xorg-video-vesa xserver-xorg-video-vga
10178 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
10180 <p
><b
>aptitude kde
192</b
>
10181 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
10182 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10183 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10184 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10185 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10186 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10187 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10188 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10189 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10190 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10191 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10192 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10193 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10194 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10195 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10196 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10197 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10198 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10199 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
10200 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10201 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10202 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
10203 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10204 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10205 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10206 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10207 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10208 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
10209 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
10210 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10211 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10212 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10213 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10214 texlive-common texlive-doc-base texlive-fonts-recommended
10215 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10216 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10217 xulrunner-
1.9</p
>
10223 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
10224 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
10225 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
10226 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
10227 <description><p
>The last few days I have done some upgrade testing in Debian, to
10228 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10229 have been discovered and reported in the process
10230 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
10231 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
10232 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
10233 kdebase-workspace-data), and to get a more regular testing going on, I
10234 am working on a script to automate the test.
</p
>
10236 <p
>The idea is to create a Lenny chroot and use tasksel to install a
10237 Gnome or KDE desktop installation inside the chroot before upgrading
10238 it. To ensure no services are started in the chroot, a policy-rc.d
10239 script is inserted. To make sure tasksel believe it is to install a
10240 desktop on a laptop, the tasksel tests are replaced in the chroot
10241 (only acceptable because this is a throw-away chroot).
</p
>
10243 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10244 currently always fail because udev refuses to upgrade with the kernel
10245 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10246 is created. The bug report
10247 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
10248 this problem do not trigger in a chroot, but I touch the file anyway
10249 to make sure the upgrade go well. Testing on virtual and real
10250 hardware have failed me because of udev so far, and creating this file
10251 do the trick in such settings anyway. This is a
10252 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
10253 issue
</a
> and the current udev behaviour is intended by the udev
10254 maintainer because he lack the resources to rewrite udev to keep
10255 working with old kernels or something like that. I really wish the
10256 udev upstream would keep udev backwards compatible, to avoid such
10257 upgrade problem, but given that they fail to do so, I guess
10258 documenting the way out of this mess is the best option we got for
10259 Debian Squeeze.
</p
>
10261 <p
>Anyway, back to the task at hand, testing upgrades. This test
10262 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10265 <blockquote
><pre
>
10269 if [
"$
1" ] ; then
10278 exec
&lt; /dev/null
10280 mirror=http://ftp.skolelinux.org/debian
10281 tmpdir=chroot-$from-upgrade-$to-$desktop
10283 debootstrap $from $tmpdir $mirror
10284 chroot $tmpdir aptitude update
10285 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10289 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10291 umount $tmpdir/proc
10293 mount -t proc proc $tmpdir/proc
10294 # Make sure proc is unmounted also on failure
10295 trap exit_cleanup EXIT INT
10297 chroot $tmpdir aptitude -y install debconf-utils
10299 # Make sure tasksel autoselection trigger. It need the test scripts
10300 # to return the correct answers.
10301 echo tasksel tasksel/desktop multiselect $desktop | \
10302 chroot $tmpdir debconf-set-selections
10304 # Include the desktop and laptop task
10305 for test in desktop laptop ; do
10306 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10310 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10313 DEBIAN_FRONTEND=noninteractive
10314 DEBIAN_PRIORITY=critical
10315 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10316 chroot $tmpdir tasksel --new-install
10318 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10319 chroot $tmpdir aptitude update
10320 touch $tmpdir/etc/udev/kernel-upgrade
10321 chroot $tmpdir aptitude -y dist-upgrade
10323 </pre
></blockquote
>
10325 <p
>I suspect it would be useful to test upgrades with both apt-get and
10326 with aptitude, but I have not had time to look at how they behave
10327 differently so far. I hope to get a cron job running to do the test
10328 regularly and post the result on the web. The Gnome upgrade currently
10329 work, while the KDE upgrade fail because of the bug in
10330 kdebase-workspace-data
</p
>
10332 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10333 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10334 post, so I will refrain from trying. I can report that for Gnome,
10335 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10336 remove and
1 not upgraded and
1024MB need to be downloaded while for
10337 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10338 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10340 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10341 is able to migrate to dependency based boot sequencing and parallel
10342 booting without a hitch. Was unsure if there were still bugs with
10343 packages failing to clean up their obsolete init.d script during
10344 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10345 packages.
</p
>
10350 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10351 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10353 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10354 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10355 scripts to migrate (some of) their operations to upstart job while
10356 keeping the init.d for hurd and kfreebsd. The packages with such
10357 needs will need a way to get their init.d scripts to behave
10358 differently when used with sysvinit and with upstart. Because of
10359 this, I had a look at the environment variables set when a init.d
10360 script is running under upstart, and when it is not.
</p
>
10362 <p
>With upstart, I notice these environment variables are set when a
10363 script is started from rcS.d/ (ignoring some irrelevant ones like
10364 COLUMNS):
</p
>
10366 <blockquote
><pre
>
10372 UPSTART_EVENTS=startup
10374 UPSTART_JOB=rc-sysinit
10375 </pre
></blockquote
>
10377 <p
>With sysvinit, these environment variables are set for the same
10380 <blockquote
><pre
>
10381 INIT_VERSION=sysvinit-
2.88
10386 </pre
></blockquote
>
10388 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10389 sysvinit are not set by upstart. Not sure if it is intentional or not
10390 to not be compatible with sysvinit in this regard.
</p
>
10392 <p
>For scripts needing to behave differently when upstart is used,
10393 looking for the UPSTART_JOB environment variable seem to be a good
10399 <title>A manual for standards wars...
</title>
10400 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10401 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10402 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10403 <description><p
>Via the
10404 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10405 of Rob Weir
</a
> I came across the very interesting essay named
10406 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10407 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10408 following the standards wars of today.
</p
>
10413 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10414 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10415 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10416 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10417 <description><p
>When using sitesummary at a site to track machines, it is possible
10418 to get a list of the machine types in use thanks to the DMI
10419 information extracted from each machine. The script to do so is
10420 included in the sitesummary package, and here is example output from
10421 the Skolelinux build servers:
</p
>
10423 <blockquote
><pre
>
10424 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10426 Dell Computer Corporation
1
10429 eserver xSeries
345 -[
8670M1X]-
1
10433 </pre
></blockquote
>
10435 <p
>The quality of the report depend on the quality of the DMI tables
10436 provided in each machine. Here there are Intel machines without model
10437 information listed with Intel as vendor and no model, and virtual Xen
10438 machines listed as [no-dmi-info]. One can add -l as a command line
10439 option to list the individual machines.
</p
>
10441 <p
>A larger list is
10442 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10443 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10444 provide the basic sitesummary report publicly. In their report there
10445 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10446 their machines, and as sitesummary is available in both distributions,
10447 it is trivial to get all of them to report to the same central
10448 collector.
</p
>
10453 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10454 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10455 <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>
10456 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10457 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10458 start at boot when an NVidia video card is used is handled. The
10459 problem seem to be that the nvidia X.org driver uses a long time to
10460 initialize, and this duration is longer than kdm is configured to
10463 <p
>I came across two bugs related to this issue,
10464 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10465 against initscripts and passed on to nvidia-glx when it became obvious
10466 that the nvidia drivers were involved, and
10467 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10468 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10470 <p
>To me, it seem that no-one is interested in actually solving the
10471 problem nvidia video card owners experience and make sure the Debian
10472 distribution work out of the box for these users. The nvidia driver
10473 maintainers expect kdm to be set up to wait longer, while kdm expect
10474 the nvidia driver maintainers to fix the driver to start faster, and
10475 while they wait for each other I guess the users end up switching to a
10476 distribution that work for them. I have no idea what the solution is,
10477 but I am pretty sure that waiting for each other is not it.
</p
>
10479 <p
>I wonder why we end up handling bugs this way.
</p
>
10484 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10485 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10486 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10487 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10488 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10489 The feature seem to hold up pretty well, but three fairly serious
10490 issues are known and should be solved:
10492 <p
><ul
>
10494 <li
>The wicd package seen to
10495 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10496 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10497 parallel booting is enabled. No idea why, but the wicd maintainer
10498 seem to be on the case.
</li
>
10500 <li
>The nvidia X driver seem to
10501 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10502 triggered more easily when parallel booting is in effect. The
10503 maintainer is on the case.
</li
>
10505 <li
>The sysv-rc package fail to properly enable dependency based boot
10506 sequencing (the shutdown is broken) when old file-rc users
10507 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10508 sysv-rc. One way to solve it would be for file-rc to create
10509 /etc/init.d/.legacy-bootordering, and another is to try to make
10510 sysv-rc more robust. Will investigate some more and probably upload a
10511 workaround in sysv-rc to help those trying to move from file-rc to
10512 sysv-rc get a working shutdown.
</li
>
10514 </ul
></p
>
10516 <p
>All in all not many surprising issues, and all of them seem
10517 solvable before Squeeze is released. In addition to these there are
10518 some packages with bugs in their dependencies and run level settings,
10519 which I expect will be fixed in a reasonable time span.
</p
>
10521 <p
>If you report any problems with dependencies in init.d scripts to
10522 the BTS, please usertag the report to get it to show up at
10523 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10524 list of usertagged bugs related to this
</a
>.
</p
>
10526 <p
>Update: Correct bug number to file-rc issue.
</p
>
10531 <title>More flexible firmware handling in debian-installer
</title>
10532 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10533 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10534 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10535 <description><p
>After a long break from debian-installer development, I finally
10536 found time today to return to the project. Having to spend less time
10537 working dependency based boot in debian, as it is almost complete now,
10538 definitely helped freeing some time.
</p
>
10540 <p
>A while back, I ran into a problem while working on Debian Edu. We
10541 include some firmware packages on the Debian Edu CDs, those needed to
10542 get disk and network controllers working. Without having these
10543 firmware packages available during installation, it is impossible to
10544 install Debian Edu on the given machine, and because our target group
10545 are non-technical people, asking them to provide firmware packages on
10546 an external medium is a support pain. Initially, I expected it to be
10547 enough to include the firmware packages on the CD to get
10548 debian-installer to find and use them. This proved to be wrong.
10549 Next, I hoped it was enough to symlink the relevant firmware packages
10550 to some useful location on the CD (tried /cdrom/ and
10551 /cdrom/firmware/). This also proved to not work, and at this point I
10552 found time to look at the debian-installer code to figure out what was
10553 going to work.
</p
>
10555 <p
>The firmware loading code is in the hw-detect package, and a closer
10556 look revealed that it would only look for firmware packages outside
10557 the installation media, so the CD was never checked for firmware
10558 packages. It would only check USB sticks, floppies and other
10559 "external
" media devices. Today I changed it to also look in the
10560 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10561 solve the problem I ran into with Debian edu. I also changed it to
10562 look in /firmware/, to make sure the installer also find firmware
10563 provided in the initrd when booting the installer via PXE, to allow us
10564 to provide the same feature in the PXE setup included in Debian
10567 <p
>To make sure firmware deb packages with a license questions are not
10568 activated without asking if the license is accepted, I extended
10569 hw-detect to look for preinst scripts in the firmware packages, and
10570 run these before activating the firmware during installation. The
10571 license question is asked using debconf in the preinst, so this should
10572 solve the issue for the firmware packages I have looked at so far.
</p
>
10574 <p
>If you want to discuss the details of these features, please
10575 contact us on debian-boot@lists.debian.org.
</p
>
10580 <title>Parallellized boot is now the default in Debian/unstable
</title>
10581 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10582 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10583 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10584 <description><p
>Since this evening, parallel booting is the default in
10585 Debian/unstable for machines using dependency based boot sequencing.
10586 Apparently the testing of concurrent booting has been wider than
10587 expected, if I am to believe the
10588 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10589 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10590 with the feature this weekend, to give us some time to detect any
10591 remaining problems before Squeeze is frozen. If serious problems are
10592 detected, it is simple to change the default back to sequential boot.
10593 The upload of the new sysvinit package also activate a new upstream
10596 More information about
10597 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10598 based boot sequencing
</a
> is available from the Debian wiki. It is
10599 currently possible to disable parallel booting when one run into
10600 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10602 <blockquote
><pre
>
10604 </pre
></blockquote
>
10606 <p
>If you report any problems with dependencies in init.d scripts to
10607 the BTS, please usertag the report to get it to show up at
10608 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10609 list of usertagged bugs related to this
</a
>.
</p
>
10614 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10615 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10616 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10617 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10618 <description><p
>In the recent Debian Edu versions, the
10619 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10620 system
</a
> is used to keep track of the machines in the school
10621 network. Each machine will automatically report its status to the
10622 central server after boot and once per night. The network setup is
10623 also reported, and using this information it is possible to get the
10624 MAC address of all network interfaces in the machines. This is useful
10625 to update the DHCP configuration.
</p
>
10627 <p
>To give some idea how to use sitesummary, here is a one-liner to
10628 ist all MAC addresses of all machines reporting to sitesummary. Run
10629 this on the collector host:
</p
>
10631 <blockquote
><pre
>
10632 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10633 </pre
></blockquote
>
10635 <p
>This will list all MAC addresses assosiated with all machine, one
10636 line per machine and with space between the MAC addresses.
</p
>
10638 <p
>To allow system administrators easier job at adding static DHCP
10639 addresses for hosts, it would be possible to extend this to fetch
10640 machine information from sitesummary and update the DHCP and DNS
10641 tables in LDAP using this information. Such tool is unfortunately not
10642 written yet.
</p
>
10647 <title>systemd, an interesting alternative to upstart
</title>
10648 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10649 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10650 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10651 <description><p
>The last few days a new boot system called
10652 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10654 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10656 to the free software world. I have not yet had time to play around
10657 with it, but it seem to be a very interesting alternative to
10658 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10659 a good alternative for Debian when we are able to switch to an event
10660 based boot system. Tollef is
10661 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10662 systemd into Debian, and I look forward to seeing how well it work. I
10663 like the fact that systemd handles init.d scripts with dependency
10664 information natively, allowing them to run in parallel where upstart
10665 at the moment do not.
</p
>
10667 <p
>Unfortunately do systemd have the same problem as upstart regarding
10668 platform support. It only work on recent Linux kernels, and also need
10669 some new kernel features enabled to function properly. This means
10670 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10671 system. Not sure how that will be handled if systemd proves to be the
10672 way forward.
</p
>
10674 <p
>In the mean time, based on the
10675 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10676 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10677 decided to enable full parallel booting as the default in Debian as
10678 soon as possible (probably this weekend or early next week), to see if
10679 there are any remaining serious bugs in the init.d dependencies. A
10680 new version of the sysvinit package implementing this change is
10681 already in experimental. If all go well, Squeeze will be released
10682 with parallel booting enabled by default.
</p
>
10687 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10688 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10689 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10690 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10691 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10692 complete, so complete that it is actually possible to run all the
10693 init.d scripts in parallell based on these dependencies. If you want
10694 to test your Squeeze system, make sure
10695 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10696 based boot sequencing
</a
> is enabled, and add this line to
10697 /etc/default/rcS:
</p
>
10699 <blockquote
><pre
>
10700 CONCURRENCY=makefile
10701 </pre
></blockquote
>
10703 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10704 scripts in parallel using the dependency information stored in
10705 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10706 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10707 to try to start the kdm and gdm scripts as early as possible, and will
10708 start the facilities required by kdm or gdm as early as possible to
10709 make this happen.
</p
>
10711 <p
>Give it a try, and see if you like the result. If some services
10712 fail to start properly, it is most likely because they have incomplete
10713 init.d script dependencies in their startup script (or some of their
10714 dependent scripts have incomplete dependencies). Report bugs and get
10715 the package maintainers to fix it. :)
</p
>
10717 <p
>Running scripts in parallel could be the default in Debian when we
10718 manage to get the init.d script dependencies complete and correct. I
10719 expect we will get there in Squeeze+
1, if we get manage to test and
10720 fix the remaining issues.
</p
>
10722 <p
>If you report any problems with dependencies in init.d scripts to
10723 the BTS, please usertag the report to get it to show up at
10724 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10725 list of usertagged bugs related to this
</a
>.
</p
>
10730 <title>Debian has switched to dependency based boot sequencing
</title>
10731 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10733 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10734 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10735 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10736 have been migrated to using dependency based boot sequencing. This
10737 conclude work me and others have been doing for the last three days.
10738 It feels great to see this finally part of the default Debian
10739 installation. Now we just need to weed out the last few problems that
10740 are bound to show up, to get everything ready for Squeeze.
</p
>
10742 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10743 fixing the more fundamental problem of handing the event based
10744 non-predictable kernel in the early boot.
</p
>
10749 <title>Taking over sysvinit development
</title>
10750 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10751 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10752 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10753 <description><p
>After several years of frustration with the lack of activity from
10754 the existing sysvinit upstream developer, I decided a few weeks ago to
10755 take over the package and become the new upstream. The number of
10756 patches to track for the Debian package was becoming a burden, and the
10757 lack of synchronization between the distribution made it hard to keep
10758 the package up to date.
</p
>
10760 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10761 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10762 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10763 and Fedora), based on the patches currently in use in these
10764 distributions. We Debian maintainers plan to move to this tarball as
10765 the new upstream as soon as we find time to do the merge. Since the
10766 new tarball was created, we agreed with Werner at SuSe to make a new
10767 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10768 development there. The project is registered and currently waiting
10769 for approval by the Savannah administrators, and as soon as it is
10770 approved, we will import the old versions from svn and continue
10771 working on the future release.
</p
>
10773 <p
>It is a bit ironic that this is done now, when some of the involved
10774 distributions are moving to upstart as a syvinit replacement.
</p
>
10779 <title>Debian boots quicker and quicker
</title>
10780 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10781 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10782 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10783 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10784 people involved in the boot system on Debian and Ubuntu, to see if we
10785 could find more ways to speed up the boot system. This was an Ubuntu
10787 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10788 gathering
</a
>. It was quite productive. We also discussed the future
10789 of boot systems, and ways to handle the increasing number of boot
10790 issues introduced by the Linux kernel becoming more and more
10791 asynchronous and event base. The Ubuntu approach using udev and
10792 upstart might be a good way forward. Time will show.
</p
>
10794 <p
>Anyway, there are a few ways at the moment to speed up the boot
10795 process in Debian. All of these should be applied to get a quick
10800 <li
>Use dash as /bin/sh.
</li
>
10802 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10803 clock is in UTC.
</li
>
10805 <li
>Install and activate the insserv package to enable
10806 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10807 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10811 These points are based on the Google summer of code work done by
10812 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10813 Villegas
</a
>.
10815 <p
>Support for makefile-style concurrency during boot was uploaded to
10816 unstable yesterday. When we tested it, we were able to cut
6 seconds
10817 from the boot sequence. It depend on very correct dependency
10818 declaration in all init.d scripts, so I expect us to find edge cases
10819 where the dependences in some scripts are slightly wrong when we start
10820 using this.
</p
>
10822 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10823 introduced by Raphael Geissert today, one that could affect the
10824 startup speed as well. Instead of starting some scripts concurrently
10825 from rcS.d/ and another set of scripts from rc2.d/, it would be
10826 possible to run a of them in the same process. A quick way to test
10827 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10828 insserv
'. Will need to test if that work. :)
</p
>
10833 <title>BSAs påstander om piratkopiering møter motstand
</title>
10834 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10835 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10836 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10837 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10838 programvareselskapene som Microsoft og Apple, publisert en rapport der
10839 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10840 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10842 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10843 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10844 dagene. Et spesielt interessant kommentar fra Sverige,
10845 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10846 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10849 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10850 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10851 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10852 exakta
", säger BSAs Sverigechef John Hugosson.
10853 </blockquote
>
10855 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10856 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10857 piracy figures need a shot of reality
</a
> og
<a
10858 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10859 Copyright Treaty Work?
</a
></p
>
10861 <p
>Fant lenkene via
<a
10862 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10863 på Slashdot
</a
>.
</p
>
10868 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10869 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10870 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10871 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10872 <description><p
>Kom over
10873 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10874 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10875 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10876 jobber til daglig. En rask opptelling forteller meg at vi har
490
10877 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10878 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10879 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10884 <title>Kryptert harddisk - naturligvis
</title>
10885 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10886 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10887 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10888 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10889 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10890 når en tar tap av arbeidstid, fortrolige dokumenter,
10891 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10892 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10893 til at jeg har kryptert harddisken på både kontormaskinen og min
10894 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10895 komme på avveie, den første informasjon relatert til jobben min ved
10896 Universitetet i Oslo, og den andre relatert til blant annet
10897 foreningsarbeide. Kryptering av diskene gjør at det er lite
10898 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10899 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10900 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10901 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10902 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10903 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10904 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10905 det er gjort slik jeg gjør det er minimale, og gevinstene er
10906 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10907 maskinen reinstalleres og alt er tapt.
</p
>
10909 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10910 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10911 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10912 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10913 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10914 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10915 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10916 betydelige.
</p
>
10921 <title>Two projects that have improved the quality of free software a lot
</title>
10922 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10924 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10925 <description><p
>There are two software projects that have had huge influence on the
10926 quality of free software, and I wanted to mention both in case someone
10927 do not yet know them.
</p
>
10929 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10930 tool to detect and expose errors in the memory handling of programs.
10931 It is easy to use, all one need to do is to run
'valgrind program
',
10932 and it will report any problems on stdout. It is even better if the
10933 program include debug information. With debug information, it is able
10934 to report the source file name and line number where the problem
10935 occurs. It can report things like
'reading past memory block in file
10936 X line N, the memory block was allocated in file Y, line M
', and
10937 'using uninitialised value in control logic
'. This tool has made it
10938 trivial to investigate reproducible crash bugs in programs, and have
10939 reduced the number of this kind of bugs in free software a lot.
10941 <p
>The second one is
10942 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10943 a source code checker. It is able to process the source of a program
10944 and find problems in the logic without running the program. It
10945 started out as the Stanford Checker and became well known when it was
10946 used to find bugs in the Linux kernel. It is now a commercial tool
10947 and the company behind it is running
10948 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10949 free software community, where a lot of free software projects get
10950 their source checked for free. Several thousand defects have been
10951 found and fixed so far. It can find errors like
'lock L taken in file
10952 X line N is never released if exiting in line M
', or
'the code in file
10953 Y lines O to P can never be executed
'. The projects included in the
10954 community service project have managed to get rid of a lot of
10955 reliability problems thanks to Coverity.
</p
>
10957 <p
>I believe tools like this, that are able to automatically find
10958 errors in the source, are vital to improve the quality of software and
10959 make sure we can get rid of the crashing and failing software we are
10960 surrounded by today.
</p
>
10965 <title>No patch is not better than a useless patch
</title>
10966 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10967 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10968 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10969 <description><p
>Julien Blache
10970 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10971 patch is better than a useless patch
</a
>. I completely disagree, as a
10972 patch allow one to discuss a concrete and proposed solution, and also
10973 prove that the issue at hand is important enough for someone to spent
10974 time on fixing it. No patch do not provide any of these positive
10975 properties.
</p
>
10980 <title>Standardize on protocols and formats, not vendors and applications
</title>
10981 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10982 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10983 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10984 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10985 very good one to form a long lived computer infrastructure. It is the
10986 simple one, lost by many in todays computer industry: Standardize on
10987 open network protocols and open exchange/storage formats, not applications.
10988 Applications come and go, while protocols and files tend to stay, and
10989 thus one want to make it easy to change application and vendor, while
10990 avoiding conversion costs and locking users to a specific platform or
10991 application.
</p
>
10993 <p
>This approach make it possible to replace the client applications
10994 independently of the server applications. One can even allow users to
10995 use several different applications as long as they handle the selected
10996 protocol and format. In the normal case, only one client application
10997 is recommended and users only get help if they choose to use this
10998 application, but those that want to deviate from the easy path are not
10999 blocked from doing so.
</p
>
11001 <p
>It also allow us to replace the server side without forcing the
11002 users to replace their applications, and thus allow us to select the
11003 best server implementation at any moment, when scale and resouce
11004 requirements change.
</p
>
11006 <p
>I strongly recommend standardizing - on open network protocols and
11007 open formats, but I would never recommend standardizing on a single
11008 application that do not use open network protocol or open formats.
</p
>
11013 <title>Returning from Skolelinux developer gathering
</title>
11014 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
11015 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
11016 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
11017 <description><p
>I
'm sitting on the train going home from this weekends Debian
11018 Edu/Skolelinux development gathering. I got a bit done tuning the
11019 desktop, and looked into the dynamic service location protocol
11020 implementation avahi. It look like it could be useful for us. Almost
11021 30 people participated, and I believe it was a great environment to
11022 get to know the Skolelinux system. Walter Bender, involved in the
11023 development of the Sugar educational platform, presented his stuff and
11024 also helped me improve my OLPC installation. He also showed me that
11025 his Turtle Art application can be used in standalone mode, and we
11026 agreed that I would help getting it packaged for Debian. As a
11027 standalone application it would be great for Debian Edu. We also
11028 tried to get the video conferencing working with two OLPCs, but that
11029 proved to be too hard for us. The application seem to need more work
11030 before it is ready for me. I look forward to getting home and relax
11036 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
11037 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
11038 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
11039 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
11040 <description><p
>The state of standardized LDAP schemas on Linux is far from
11041 optimal. There is RFC
2307 documenting one way to store NIS maps in
11042 LDAP, and a modified version of this normally called RFC
2307bis, with
11043 some modifications to be compatible with Active Directory. The RFC
11044 specification handle the content of a lot of system databases, but do
11045 not handle DNS zones and DHCP configuration.
</p
>
11047 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
11048 we would like to store information about users, SMB clients/hosts,
11049 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11050 and LTSP configuration in LDAP. These objects have a lot in common,
11051 but with the current LDAP schemas it is not possible to have one
11052 object per entity. For example, one need to have at least three LDAP
11053 objects for a given computer, one with the SMB related stuff, one with
11054 DNS information and another with DHCP information. The schemas
11055 provided for DNS and DHCP are impossible to combine into one LDAP
11056 object. In addition, it is impossible to implement quick queries for
11057 netgroup membership, because of the way NIS triples are implemented.
11058 It just do not scale. I believe it is time for a few RFC
11059 specifications to cleam up this mess.
</p
>
11061 <p
>I would like to have one LDAP object representing each computer in
11062 the network, and this object can then keep the SMB (ie host key), DHCP
11063 (mac address/name) and DNS (name/IP address) settings in one place.
11064 It need to be efficently stored to make sure it scale well.
</p
>
11066 <p
>I would also like to have a quick way to map from a user or
11067 computer and to the net group this user or computer is a member.
</p
>
11069 <p
>Active Directory have done a better job than unix heads like myself
11070 in this regard, and the unix side need to catch up. Time to start a
11071 new IETF work group?
</p
>
11076 <title>Endelig er Debian Lenny gitt ut
</title>
11077 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
11078 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
11079 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
11080 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
11081 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
11082 Et langt steg videre for Debian-prosjektet, og en rekke nye
11083 programpakker blir nå tilgjengelig for de av oss som bruker den
11084 stabile utgaven av Debian. Neste steg er nå å få
11085 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
11086 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
11087 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11088 slippes løs på skolene. Takk til alle debian-utviklerne som har
11089 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11090 bootsekvens tilgjengelig i stabil utgave, vha pakken
11091 <tt
>insserv
</tt
>.
</p
>
11096 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
11097 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
11098 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
11099 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
11100 <description><p
>This weekend we had a small developer gathering for Debian Edu in
11101 Oslo. Most of Saturday was used for the general assemly for the
11102 member organization, but the rest of the weekend I used to tune the
11103 LTSP installation. LTSP now work out of the box on the
10-network.
11104 Acer Aspire One proved to be a very nice thin client, with both
11105 screen, mouse and keybard in a small box. Was working on getting the
11106 diskless workstation setup configured out of the box, but did not
11107 finish it before the weekend was up.
</p
>
11109 <p
>Did not find time to look at the
4 VGA cards in one box we got from
11110 the Brazilian group, so that will have to wait for the next
11111 development gathering. Would love to have the Debian Edu installer
11112 automatically detect and configure a multiseat setup when it find one
11113 of these cards.
</p
>
11118 <title>The sorry state of multimedia browser plugins in Debian
</title>
11119 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
11120 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
11121 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
11122 <description><p
>Recently I have spent some time evaluating the multimedia browser
11123 plugins available in Debian Lenny, to see which one we should use by
11124 default in Debian Edu. We need an embedded video playing plugin with
11125 control buttons to pause or stop the video, and capable of streaming
11126 all the multimedia content available on the web. The test results and
11127 notes are available on
11128 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
11129 Debian wiki
</a
>. I was surprised how few of the plugins are able to
11130 fill this need. My personal video player favorite, VLC, has a really
11131 bad plugin which fail on a lot of the test pages. A lot of the MIME
11132 types I would expect to work with any free software player (like
11133 video/ogg), just do not work. And simple formats like the
11134 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
11135 totem and vlc plugins. I hope the situation will improve soon. No
11136 wonder sites use the proprietary Adobe flash to play video.
</p
>
11138 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
11139 be the only one fitting our needs. :/
</p
>