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>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
11 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
13 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
14 <description><p
>A while back, I was asked by a friend how to stream the desktop to
15 my projector connected to Kodi. I sadly had to admit that I had no
16 idea, as it was a task I never had tried. Since then, I have been
17 looking for a way to do so, preferable without much extra software to
18 install on either side. Today I found a way that seem to kind of
19 work. Not great, but it is a start.
</p
>
21 <p
>I had a look at several approaches, for example
22 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
23 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
24 local storage enough to store the stream locally. This is not going
25 to work well for me, lacking enough free space, and it would
26 impossible for my friend to get working.
</p
>
28 <p
>Next, it occurred to me that perhaps I could use VLC to create a
29 video stream that Kodi could play. Preferably using
30 broadcast/multicast, to avoid having to change any setup on the Kodi
31 side when starting such stream. Unfortunately, the only recipe I
32 could find using multicast used the rtp protocol, and this protocol
33 seem to not be supported by Kodi.
</p
>
35 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
36 have to specify the IP address of the streaming machine in both the
37 sending command and the file on the Kodi server. But it is showing my
38 desktop, and thus allow us to have a shared look on the big screen at
39 the programs I work on.
</p
>
41 <p
>I did not spend much time investigating codeces. I combined the
42 rtp and rtsp recipes from
43 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
44 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
45 this working on the desktop/streaming end.
</p
>
47 <blockquote
><pre
>
48 vlc screen:// --sout \
49 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
50 </pre
></blockquote
>
52 <p
>I ssh-ed into my Kodi box and created a file like this with the
53 same IP address:
</p
>
55 <blockquote
><pre
>
56 echo rtsp://
192.168.11.4:
8080/test.sdp \
57 > /storage/videos/screenstream.m3u
58 </pre
></blockquote
>
60 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
61 as I can tell the IP must be hardcoded for this to work. In other
62 words, if someone elses machine is going to do the steaming, you have
63 to update screenstream.m4u on the Kodi machine and adjust the vlc
64 recipe. To get started, locate the file in Kodi and select the m3u
65 file while the VLC stream is running. The desktop then show up in my
66 big screen. :)
</p
>
68 <p
>When using the same technique to stream a video file with audio,
69 the audio quality is really bad. No idea if the problem is package
70 loss or bad parameters for the transcode. I do not know VLC nor Kodi
71 enough to tell.
</p
>
73 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
74 succestions and reminded me about an important step. The
"screen:
"
75 input source is only available once the vlc-plugin-access-extra
76 package is installed on Debian. Without it, you will see this error
77 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
78 for details.
" He further found that it is possible to drop some parts
79 of the VLC command line to reduce the amount of hardcoded information.
80 It is also useful to consider using cvlc to avoid having the VLC
81 window in the desktop view. In sum, this give us this command line on
84 <blockquote
><pre
>
85 cvlc screen:// --sout \
86 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
87 </pre
></blockquote
>
89 <p
>and this on the Kodi end
<p
>
91 <blockquote
><pre
>
92 echo rtsp://
192.168.11.4:
8080/ \
93 > /storage/videos/screenstream.m3u
94 </pre
></blockquote
>
96 <p
>Still bad image quality, though. But I did discover that streaming
97 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
98 audio quality, so I guess the issue is in the input or transcoding
99 parts, not the rtsp part. I
've tried to change the vb and ab
100 parameters to use more bandwidth, but it did not make a
101 difference.
</p
>
103 <p
>I further received a suggestion from Einar Haraldseid to try using
104 gstreamer instead of VLC, and this proved to work great! He also
105 provided me with the trick to get Kodi to use a multicast stream as
106 its source. By using this monstrous oneliner, I can stream my desktop
107 with good video quality in reasonable framerate to the
239.255.0.1
108 multicast address on port
1234:
110 <blockquote
><pre
>
111 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
112 videoconvert ! queue2 ! \
113 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
114 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
115 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
116 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
0 auto-multicast=
1 sync=
0 \
117 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
118 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
119 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
120 </pre
></blockquote
>
122 <p
>and this on the Kodi end
<p
>
124 <blockquote
><pre
>
125 echo udp://@
239.255.0.1:
1234 \
126 > /storage/videos/screenstream.m3u
127 </pre
></blockquote
>
129 <p
>Note the trick to pick a valid pulseaudio source. It might not
130 pick the one you need. This approach will of course lead to trouble
131 if more than one source uses the same multicast port and address.
132 Note the ttl-mc=
0 setting, which limit the multicast packages to the
133 local network. If the value is increased, your screen will be
134 broadcasted further, one network
"hop
" for each increase (read up on
135 multicast to learn more. :)!
</p
>
137 <p
>Having cracked how to get Kodi to receive multicast streams, I
138 could use this VLC command to stream to the same multicast address.
139 The image quality is way better than the rtsp approach.
</p
>
141 <blockquote
><pre
>
142 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
143 </pre
></blockquote
>
145 <p
>As usual, if you use Bitcoin and want to show your support of my
146 activities, please send Bitcoin donations to my address
147 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
152 <title>What is the most supported MIME type in Debian in
2018?
</title>
153 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
154 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
155 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
156 <description><p
>Five years ago,
157 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
158 measured what the most supported MIME type in Debian was
</a
>, by
159 analysing the desktop files in all packages in the archive. Since
160 then, the DEP-
11 AppStream system has been put into production, making
161 the task a lot easier. This made me want to repeat the measurement,
162 to see how much things changed. Here are the new numbers, for
163 unstable only this time:
165 <p
><strong
>Debian Unstable:
</strong
></p
>
169 ----- -----------------------
181 30 audio/x-vorbis+ogg
182 29 image/x-portable-pixmap
184 27 image/x-portable-bitmap
192 <p
>The list was created like this using a sid chroot:
"cat
193 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
194 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
196 <p
>It is interesting to see how image formats have passed text/plain
197 as the most announced supported MIME type. These days, thanks to the
198 AppStream system, if you run into a file format you do not know, and
199 want to figure out which packages support the format, you can find the
200 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
201 look up all packages announcing support for this format in their
202 AppStream metadata (XML or .desktop file) using
"appstreamcli
203 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
204 me, want to know which packages support inode/directory, you can get a
205 list like this:
</p
>
207 <p
><blockquote
><pre
>
208 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
215 Package: doublecmd-common
217 Package: enlightenment
237 </pre
></blockquote
></p
>
239 <p
>Using the same method, I can quickly discover that the Sketchup file
240 format is not yet supported by any package in Debian:
</p
>
242 <p
><blockquote
><pre
>
243 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
244 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
246 </pre
></blockquote
></p
>
248 <p
>Yesterday I used it to figure out which packages support the STL
3D
251 <p
><blockquote
><pre
>
252 % appstreamcli what-provides mimetype application/sla|grep Package
257 </pre
></blockquote
></p
>
259 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
261 <p
>As usual, if you use Bitcoin and want to show your support of my
262 activities, please send Bitcoin donations to my address
263 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
268 <title>Debian APT upgrade without enough free space on the disk...
</title>
269 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
271 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
272 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
273 for a while, and when I need to update it there is not enough free
274 space on the disk for apt to do a normal
'apt upgrade
'. I normally
275 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
276 upgrade only some of the packages in one batch, until the amount of
277 packages to download fall below the amount of free space available.
278 Today, I had about
500 packages to upgrade, and after a while I got
279 tired of trying to install chunks of packages manually. I concluded
280 that I did not have the spare hours required to complete the task, and
281 decided to see if I could automate it. I came up with this small
282 script which I call
'apt-in-chunks
':
</p
>
284 <p
><blockquote
><pre
>
287 # Upgrade packages when the disk is too full to upgrade every
288 # upgradable package in one lump. Fetching packages to upgrade using
289 # apt, and then installing using dpkg, to avoid changing the package
290 # flag for manual/automatic.
295 if [
"$
1" ]; then
296 grep -v
"$
1"
302 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
303 echo
"Upgrading $p
"
305 apt install --download-only -y $p
306 for f in /var/cache/apt/archives/*.deb; do
307 if [ -e
"$f
" ]; then
308 dpkg -i /var/cache/apt/archives/*.deb
313 </pre
></blockquote
></p
>
315 <p
>The script will extract the list of packages to upgrade, try to
316 download the packages needed to upgrade one package, install the
317 downloaded packages using dpkg. The idea is to upgrade packages
318 without changing the APT mark for the package (ie the one recording of
319 the package was manually requested or pulled in as a dependency). To
320 use it, simply run it as root from the command line. If it fail, try
321 'apt install -f
' to clean up the mess and run the script again. This
322 might happen if the new packages conflict with one of the old
323 packages. dpkg is unable to remove, while apt can do this.
</p
>
325 <p
>It take one option, a package to ignore in the list of packages to
326 upgrade. The option to ignore a package is there to be able to skip
327 the packages that are simply too large to unpack. Today this was
328 'ghc
', but I have run into other large packages causing similar
329 problems earlier (like TeX).
</p
>
331 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
332 alternative ways to handle this. The
"unattended-upgrades
333 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
334 each package to upgrade, and then upgrade them in order, smallest set
335 first. It might be a better option than my above mentioned script.
336 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
337 the need for using
"dpkg -i
" in the script above.
</p
>
339 <p
>As usual, if you use Bitcoin and want to show your support of my
340 activities, please send Bitcoin donations to my address
341 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
346 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
347 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
348 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
349 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
350 <description><p
>A new version of the
351 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
352 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
353 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
354 useful. It was uploaded the last few days, and the last update will
355 enter testing tomorrow. See the
356 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
357 notes
</a
> for the list of bug fixes and new features. Version
3.2
358 was announced
6 days ago. We will try to get it into Debian as
361 <p
>More information related to
3D printing is available on the
362 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
363 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
366 <p
>As usual, if you use Bitcoin and want to show your support of my
367 activities, please send Bitcoin donations to my address
368 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
373 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
374 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
375 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
376 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
377 <description><p
>After several months of working and waiting, I am happy to report
378 that the nice and user friendly
3D printer slicer software Cura just
379 entered Debian Unstable. It consist of five packages,
380 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
381 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
382 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
383 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
384 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
385 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
386 two, uranium and cura, entered Unstable yesterday. This should make
387 it easier for Debian users to print on at least the Ultimaker class of
388 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
389 make life easier for at least me. :)
</p
>
391 <p
>The work to make this happen was done by Gregor Riepl, and I was
392 happy to assist him in sponsoring the packages. With the introduction
393 of Cura, Debian is up to three
3D printer slicers at your service,
394 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
395 printer, give it a go. :)
</p
>
397 <p
>The
3D printer software is maintained by the
3D printer Debian
398 team, flocking together on the
399 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
401 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
402 IRC channel.
</p
>
404 <p
>The next step for Cura in Debian is to update the cura package to
405 version
3.0.3 and then update the entire set of packages to version
406 3.1.0 which showed up the last few days.
</p
>
411 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
412 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
414 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
415 <description><p
>At my nearby maker space,
416 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
417 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
418 on Windows and MacOS X than Linux, because the software involved had
419 to be manually compiled and set up on Linux while premade packages
420 worked out of the box on Windows and MacOS X. I found this annoying,
421 as the software involved,
422 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
423 and should be trivial to get up and running on Linux if someone took
424 the time to package it for the relevant distributions. I even found
425 <a href=
"https://bugs.debian.org/
706656">a request for adding into
426 Debian
</a
> from
2013, which had seem some activity over the years but
427 never resulted in the software showing up in Debian. So a few days
428 ago I offered my help to try to improve the situation.
</p
>
430 <p
>Now I am very happy to see that all the packages required by a
431 working Cura in Debian are uploaded into Debian and waiting in the NEW
432 queue for the ftpmasters to have a look. You can track the progress
434 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
435 status page for the
3D printer team
</a
>.
</p
>
437 <p
>The uploaded packages are a bit behind upstream, and was uploaded
438 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
439 queue
</a
> while we work up updating the packages to the latest
440 upstream version.
</p
>
442 <p
>On a related note, two competitors for Cura, which I found harder
443 to use and was unable to configure correctly for Ultimaker
2+ in the
444 short time I spent on it, are already in Debian. If you are looking
445 for
3D printer
"slicers
" and want something already available in
447 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
448 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
449 The latter is a fork of the former.
</p
>
451 <p
>As usual, if you use Bitcoin and want to show your support of my
452 activities, please send Bitcoin donations to my address
453 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
458 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
459 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
460 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
461 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
462 <description><p
>Every mobile phone announce its existence over radio to the nearby
463 mobile cell towers. And this radio chatter is available for anyone
464 with a radio receiver capable of receiving them. Details about the
465 mobile phones with very good accuracy is of course collected by the
466 phone companies, but this is not the topic of this blog post. The
467 mobile phone radio chatter make it possible to figure out when a cell
468 phone is nearby, as it include the SIM card ID (IMSI). By paying
469 attention over time, one can see when a phone arrive and when it leave
470 an area. I believe it would be nice to make this information more
471 available to the general public, to make more people aware of how
472 their phones are announcing their whereabouts to anyone that care to
475 <p
>I am very happy to report that we managed to get something
476 visualizing this information up and running for
477 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
478 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
479 library. The solution is based on the
480 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
481 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
482 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
483 Sone from the Computer Science department of the University of
484 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
485 IMSIs) as dots in a web browser graph, with lines to the dot
486 representing mobile base station it is talking to. It was working in
487 the lab yesterday, and was moved into place this morning.
</p
>
489 <p
>We set up a fairly powerful desktop machine using Debian
490 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
491 connected and visualize the visible cell phone towers using an
492 <a href=
"https://github.com/marlow925/hopglass
">English version of
493 Hopglass
</a
>. A fairly powerfull machine is needed as the
494 grgsm_livemon_headless processes from
495 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
496 the radio signal to data packages is quite CPU intensive.
</p
>
498 <p
>The frequencies to listen to, are identified using a slightly
499 patched scan-and-livemon (to set the --args values for each receiver),
500 and the Hopglass data is generated using the
501 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
502 in my meshviewer-output branch
</a
>. For some reason we could not get
503 more than four SDRs working. There is also a geographical map trying
504 to show the location of the base stations, but I believe their
505 coordinates are hardcoded to some random location in Germany, I
506 believe. The code should be replaced with code to look up location in
507 a text file, a sqlite database or one of the online databases
509 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
510 issue for the topic
</a
>.
512 <p
>If this sound interesting, visit the stand at the festival!
</p
>
517 <title>Easier recipe to observe the cell phones around you
</title>
518 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
519 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
520 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
521 <description><p
>A little more than a month ago I wrote
522 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
523 to observe the SIM card ID (aka IMSI number) of mobile phones talking
524 to nearby mobile phone base stations using Debian GNU/Linux and a
525 cheap USB software defined radio
</a
>, and thus being able to pinpoint
526 the location of people and equipment (like cars and trains) with an
527 accuracy of a few kilometer. Since then we have worked to make the
528 procedure even simpler, and it is now possible to do this without any
529 manual frequency tuning and without building your own packages.
</p
>
531 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
532 package is now included in Debian testing and unstable, and the
533 IMSI-catcher code no longer require root access to fetch and decode
534 the GSM data collected using gr-gsm.
</p
>
536 <p
>Here is an updated recipe, using packages built by Debian and a git
537 clone of two python scripts:
</p
>
541 <li
>Start with a Debian machine running the Buster version (aka
544 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
545 python-scapy
</tt
>' as root to install required packages.
</li
>
547 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
548 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
550 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
552 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
553 scan-and-livemon
</tt
>' to locate the frequency of nearby base
554 stations and start listening for GSM packages on one of them.
</li
>
556 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
557 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
561 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
562 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
563 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
564 work with RTL
8232 and other similar USB radio receivers you can get
566 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
567 from ebay
</a
>), so for now the solution is to scan using the RTL radio
568 and only use HackRF for fetching GSM data.
</p
>
570 <p
>As far as I can tell, a cell phone only show up on one of the
571 frequencies at the time, so if you are going to track and count every
572 cell phone around you, you need to listen to all the frequencies used.
573 To listen to several frequencies, use the --numrecv argument to
574 scan-and-livemon to use several receivers. Further, I am not sure if
575 phones using
3G or
4G will show as talking GSM to base stations, so
576 this approach might not see all phones around you. I typically see
577 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
579 <p
>I
've tried to run the scanner on a
580 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
581 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
582 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
583 stdout, I am told there it is caused by a buffer overflow between the
584 radio and GNU Radio, caused by the program being unable to read the
585 GSM data fast enough. If you see a stream of
'O
's from the terminal
586 where you started scan-and-livemon, you need a give the process more
587 CPU power. Perhaps someone are able to optimize the code to a point
588 where it become possible to set up RPi3 based GSM sniffers? I tried
589 using Raspbian instead of Debian, but there seem to be something wrong
590 with GNU Radio on raspbian, causing glibc to abort().
</p
>
595 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
596 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
597 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
598 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
599 <description><p
>On friday, I came across an interesting article in the Norwegian
600 web based ICT news magazine digi.no on
601 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
602 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
603 DVB-T software defined radios. The article refered to instructions
604 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
605 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
607 <p
>The instructions said to use Ubuntu, install pip using apt (to
608 bypass apt), use pip to install pybombs (to bypass both apt and pip),
609 and the ask pybombs to fetch and build everything you need from
610 scratch. I wanted to see if I could do the same on the most recent
611 Debian packages, but this did not work because pybombs tried to build
612 stuff that no longer build with the most recent openssl library or
613 some other version skew problem. While trying to get this recipe
614 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
615 and the only piece of software dependency missing in Debian was the
616 gr-gsm package. I also found out that the lead upstream developer of
617 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
618 Debian packages provided in an Ubuntu PPA repository. All I needed to
619 do was to dget the Debian source package and built it.
</p
>
621 <p
>The IMSI collector is a python script listening for packages on the
622 loopback network device and printing to the terminal some specific GSM
623 packages with IMSI numbers in them. The code is fairly short and easy
624 to understand. The reason this work is because gr-gsm include a tool
625 to read GSM data from a software defined radio like a DVB-T USB stick
626 and other software defined radios, decode them and inject them into a
627 network device on your Linux machine (using the loopback device by
628 default). This proved to work just fine, and I
've been testing the
629 collector for a few days now.
</p
>
631 <p
>The updated and simpler recipe is thus to
</p
>
635 <li
>start with a Debian machine running Stretch or newer,
</li
>
637 <li
>build and install the gr-gsm package available from
638 <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
>
640 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
642 <li
>run grgsm_livemon and adjust the frequency until the terminal
643 where it was started is filled with a stream of text (meaning you
644 found a GSM station).
</li
>
646 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
650 <p
>To make it even easier in the future to get this sniffer up and
651 running, I decided to package
652 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
653 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
654 #
871055</a
>), and the package was uploaded into the NEW queue today.
655 Luckily the gnuradio maintainer has promised to help me, as I do not
656 know much about gnuradio stuff yet.
</p
>
658 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
659 commercial tools like
660 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
661 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
662 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
663 Stingray
</a
>, but I hope the existance of cheap alternatives can make
664 more people realise how their whereabouts when carrying a cell phone
665 is easily tracked. Seeing the data flow on the screen, realizing that
666 I live close to a police station and knowing that the police is also
667 wearing cell phones, I wonder how hard it would be for criminals to
668 track the position of the police officers to discover when there are
669 police near by, or for foreign military forces to track the location
670 of the Norwegian military forces, or for anyone to track the location
671 of government officials...
</p
>
673 <p
>It is worth noting that the data reported by the IMSI-catcher
674 script mentioned above is only a fraction of the data broadcasted on
675 the GSM network. It will only collect one frequency at the time,
676 while a typical phone will be using several frequencies, and not all
677 phones will be using the frequencies tracked by the grgsm_livemod
678 program. Also, there is a lot of radio chatter being ignored by the
679 simple_IMSI-catcher script, which would be collected by extending the
680 parser code. I wonder if gr-gsm can be set up to listen to more than
681 one frequency?
</p
>
686 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
687 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
688 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
689 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
690 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
692 <p
>I finally received a copy of the Norwegian Bokmål edition of
693 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
694 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
695 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
696 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
697 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
698 price. The book is also available for download in electronic form as
699 PDF, EPUB and Mobipocket, as can be
700 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
701 as a web page
</a
>.
</p
>
703 <p
>This is the second book I publish (the first was the book
704 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
706 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
707 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
709 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
710 Bokmål
</a
>), and I am very excited to finally wrap up this
712 "<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
713 for Debian-administratoren
</a
>" will be well received.
</p
>
718 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
719 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
720 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
721 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
722 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
723 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
724 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
725 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
726 på om den fri oversetterløsningen
727 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
728 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
730 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
733 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
734 rolle og muligheter til å håndtere internasjonale utfordringer, som
735 for eksempel flykningekrisen.
</p
>
737 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
740 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
741 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
746 <p
>Dette oversetter Apertium slik:
</p
>
749 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
750 andre aktørar og høve til å handtera internasjonale utfordringar, som
751 til dømes *flykningekrisen.
</p
>
753 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
757 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
758 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
763 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
764 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
765 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
766 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
767 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
768 det er kanskje flisespikking. Det understreker vel bare at det alltid
769 trengs korrekturlesning etter automatisk oversettelse.
</p
>
774 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
775 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
777 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
778 <description><p
>Over the years, administrating thousand of NFS mounting linux
779 computers at the time, I often needed a way to detect if the machine
780 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
781 file or directory affected by the hang, the process (and possibly the
782 shell) will hang too. So you want to be able to detect this without
783 risking the detection process getting stuck too. It has not been
784 obvious how to do this. When the hang has lasted a while, it is
785 possible to find messages like these in dmesg:
</p
>
787 <p
><blockquote
>
788 nfs: server nfsserver not responding, still trying
789 <br
>nfs: server nfsserver OK
790 </blockquote
></p
>
792 <p
>It is hard to know if the hang is still going on, and it is hard to
793 be sure looking in dmesg is going to work. If there are lots of other
794 messages in dmesg the lines might have rotated out of site before they
795 are noticed.
</p
>
797 <p
>While reading through the nfs client implementation in linux kernel
798 code, I came across some statistics that seem to give a way to detect
799 it. The om_timeouts sunrpc value in the kernel will increase every
800 time the above log entry is inserted into dmesg. And after digging a
801 bit further, I discovered that this value show up in
802 /proc/self/mountstats on Linux.
</p
>
804 <p
>The mountstats content seem to be shared between files using the
805 same file system context, so it is enough to check one of the
806 mountstats files to get the state of the mount point for the machine.
807 I assume this will not show lazy umounted NFS points, nor NFS mount
808 points in a different process context (ie with a different filesystem
809 view), but that does not worry me.
</p
>
811 <p
>The content for a NFS mount point look similar to this:
</p
>
813 <p
><blockquote
><pre
>
815 device /dev/mapper/Debian-var mounted on /var with fstype ext3
816 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
817 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
819 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
820 sec: flavor=
1,pseudoflavor=
1
821 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
822 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
823 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
824 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
826 NULL:
0 0 0 0 0 0 0 0
827 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
828 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
829 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
830 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
831 READLINK:
125 125 0 20472 18620 0 1112 1118
832 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
833 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
834 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
835 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
836 SYMLINK:
903 903 0 233428 245488 6 5865 5917
837 MKNOD:
80 80 0 20148 21760 0 299 304
838 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
839 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
840 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
841 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
842 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
843 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
844 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
845 FSINFO:
2 2 0 232 328 0 1 1
846 PATHCONF:
1 1 0 116 140 0 0 0
847 COMMIT:
0 0 0 0 0 0 0 0
849 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
851 </pre
></blockquote
></p
>
853 <p
>The key number to look at is the third number in the per-op list.
854 It is the number of NFS timeouts experiences per file system
855 operation. Here
22 write timeouts and
5 access timeouts. If these
856 numbers are increasing, I believe the machine is experiencing NFS
857 hang. Unfortunately the timeout value do not start to increase right
858 away. The NFS operations need to time out first, and this can take a
859 while. The exact timeout value depend on the setup. For example the
860 defaults for TCP and UDP mount points are quite different, and the
861 timeout value is affected by the soft, hard, timeo and retrans NFS
862 mount options.
</p
>
864 <p
>The only way I have been able to get working on Debian and RedHat
865 Enterprise Linux for getting the timeout count is to peek in /proc/.
867 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
868 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
869 command can be used to get these timeout values. But this do not work
870 on Linux, as far as I can tell. I
871 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
872 but have not seen any replies yet.
</p
>
874 <p
>Is there a better way to figure out if a Linux NFS client is
875 experiencing NFS hangs? Is there a way to detect which processes are
876 affected? Is there a way to get the NFS mount going quickly once the
877 network problem causing the NFS hang has been cleared? I would very
878 much welcome some clues, as we regularly run into NFS hangs.
</p
>
883 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
884 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
885 <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>
886 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
887 <description><p
>For almost a year now, we have been working on making a Norwegian
888 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
889 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
890 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
891 we are working on the proof reading to ensure consistent language and
892 use of correct computer science terms. The plan is to make the book
893 available on paper, as well as in electronic form. For that to
894 happen, the proof reading must be completed and all the figures need
895 to be translated. If you want to help out, get in touch.
</p
>
897 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
899 fresh PDF edition
</a
> in A4 format (the final book will have smaller
900 pages) of the book created every morning is available for
901 proofreading. If you find any errors, please
902 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
903 Weblate and correct the error
</a
>. The
904 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
905 of the translation including figures
</a
> is a useful source for those
906 provide Norwegian bokmål screen shots and figures.
</p
>
911 <title>Unlimited randomness with the ChaosKey?
</title>
912 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
913 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
914 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
915 <description><p
>A few days ago I ordered a small batch of
916 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
917 USB dongle for generating entropy created by Bdale Garbee and Keith
918 Packard. Yesterday it arrived, and I am very happy to report that it
919 work great! According to its designers, to get it to work out of the
920 box, you need the Linux kernel version
4.1 or later. I tested on a
921 Debian Stretch machine (kernel version
4.9), and there it worked just
922 fine, increasing the available entropy very quickly. I wrote a small
923 test oneliner to test. It first print the current entropy level,
924 drain /dev/random, and then print the entropy level for five seconds.
925 Here is the situation without the ChaosKey inserted:
</p
>
927 <blockquote
><pre
>
928 % cat /proc/sys/kernel/random/entropy_avail; \
929 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
930 for n in $(seq
1 5); do \
931 cat /proc/sys/kernel/random/entropy_avail; \
937 28 byte kopiert,
0,
000264565 s,
106 kB/s
944 </pre
></blockquote
>
946 <p
>The entropy level increases by
3-
4 every second. In such case any
947 application requiring random bits (like a HTTPS enabled web server)
948 will halt and wait for more entrpy. And here is the situation with
949 the ChaosKey inserted:
</p
>
951 <blockquote
><pre
>
952 % cat /proc/sys/kernel/random/entropy_avail; \
953 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
954 for n in $(seq
1 5); do \
955 cat /proc/sys/kernel/random/entropy_avail; \
961 104 byte kopiert,
0,
000487647 s,
213 kB/s
968 </pre
></blockquote
>
970 <p
>Quite the difference. :) I bought a few more than I need, in case
971 someone want to buy one here in Norway. :)
</p
>
973 <p
>Update: The dongle was presented at Debconf last year. You might
974 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
975 recording illuminating
</a
>. It explains exactly what the source of
976 randomness is, if you are unable to spot it from the schema drawing
977 available from the ChaosKey web site linked at the start of this blog
983 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
984 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
985 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
986 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
987 <description><p
>Did you ever wonder where the web trafic really flow to reach the
988 web servers, and who own the network equipment it is flowing through?
989 It is possible to get a glimpse of this from using traceroute, but it
990 is hard to find all the details. Many years ago, I wrote a system to
991 map the Norwegian Internet (trying to figure out if our plans for a
992 network game service would get low enough latency, and who we needed
993 to talk to about setting up game servers close to the users. Back
994 then I used traceroute output from many locations (I asked my friends
995 to run a script and send me their traceroute output) to create the
996 graph and the map. The output from traceroute typically look like
1000 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
1001 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
1002 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
1003 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
1004 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
1005 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
1006 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
1007 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
1011 </pre
></p
>
1013 <p
>This show the DNS names and IP addresses of (at least some of the)
1014 network equipment involved in getting the data traffic from me to the
1015 www.stortinget.no server, and how long it took in milliseconds for a
1016 package to reach the equipment and return to me. Three packages are
1017 sent, and some times the packages do not follow the same path. This
1018 is shown for hop
5, where three different IP addresses replied to the
1019 traceroute request.
</p
>
1021 <p
>There are many ways to measure trace routes. Other good traceroute
1022 implementations I use are traceroute (using ICMP packages) mtr (can do
1023 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1024 traceroute and a lot of other capabilities). All of them are easily
1025 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
1027 <p
>This time around, I wanted to know the geographic location of
1028 different route points, to visualize how visiting a web page spread
1029 information about the visit to a lot of servers around the globe. The
1030 background is that a web site today often will ask the browser to get
1031 from many servers the parts (for example HTML, JSON, fonts,
1032 JavaScript, CSS, video) required to display the content. This will
1033 leak information about the visit to those controlling these servers
1034 and anyone able to peek at the data traffic passing by (like your ISP,
1035 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
1037 <p
>Lets pick an example, the Norwegian parliament web site
1038 www.stortinget.no. It is read daily by all members of parliament and
1039 their staff, as well as political journalists, activits and many other
1040 citizens of Norway. A visit to the www.stortinget.no web site will
1041 ask your browser to contact
8 other servers: ajax.googleapis.com,
1042 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1043 stats.g.doubleclick.net, www.google-analytics.com,
1044 www.googletagmanager.com and www.netigate.se. I extracted this by
1045 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
1046 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1047 render the page (in HAR format using
1048 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
1049 netsniff example
</a
>. I am very grateful to Gorm for showing me how
1050 to do this). My goal is to visualize network traces to all IP
1051 addresses behind these DNS names, do show where visitors personal
1052 information is spread when visiting the page.
</p
>
1054 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
1055 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
>
1057 <p
>When I had a look around for options, I could not find any good
1058 free software tools to do this, and decided I needed my own traceroute
1059 wrapper outputting KML based on locations looked up using GeoIP. KML
1060 is easy to work with and easy to generate, and understood by several
1061 of the GIS tools I have available. I got good help from by NUUG
1062 colleague Anders Einar with this, and the result can be seen in
1063 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
1064 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
1065 free GeoIP databases I could find (and the for-pay databases my
1066 friends had access to) is not up to the task. The IP addresses of
1067 central Internet infrastructure would typically be placed near the
1068 controlling companies main office, and not where the router is really
1069 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
1070 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
1072 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
1073 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
>
1075 <p
>I also had a look at the visual traceroute graph created by
1076 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
1077 showing IP network ownership (aka AS owner) for the IP address in
1079 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
1080 graph display a lot of useful information about the traceroute in SVG
1081 format
</a
>, and give a good indication on who control the network
1082 equipment involved, but it do not include geolocation. This graph
1083 make it possible to see the information is made available at least for
1084 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1085 3 Communications and NetDNA.
</p
>
1087 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
1088 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
>
1090 <p
>In the process, I came across the
1091 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
1092 Salim Gasmi. Its methology of combining guesses based on DNS names,
1093 various location databases and finally use latecy times to rule out
1094 candidate locations seemed to do a very good job of guessing correct
1095 geolocation. But it could only do one trace at the time, did not have
1096 a sensor in Norway and did not make the geolocations easily available
1097 for postprocessing. So I contacted the developer and asked if he
1098 would be willing to share the code (he refused until he had time to
1099 clean it up), but he was interested in providing the geolocations in a
1100 machine readable format, and willing to set up a sensor in Norway. So
1101 since yesterday, it is possible to run traces from Norway in this
1102 service thanks to a sensor node set up by
1103 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
1104 trace in KML format for further processing.
</p
>
1106 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
1107 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
>
1109 <p
>Here we can see a lot of trafic passes Sweden on its way to
1110 Denmark, Germany, Holland and Ireland. Plenty of places where the
1111 Snowden confirmations verified the traffic is read by various actors
1112 without your best interest as their top priority.
</p
>
1114 <p
>Combining KML files is trivial using a text editor, so I could loop
1115 over all the hosts behind the urls imported by www.stortinget.no and
1116 ask for the KML file from GeoTraceroute, and create a combined KML
1117 file with all the traces (unfortunately only one of the IP addresses
1118 behind the DNS name is traced this time. To get them all, one would
1119 have to request traces using IP number instead of DNS names from
1120 GeoTraceroute). That might be the next step in this project.
</p
>
1122 <p
>Armed with these tools, I find it a lot easier to figure out where
1123 the IP traffic moves and who control the boxes involved in moving it.
1124 And every time the link crosses for example the Swedish border, we can
1125 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1126 Britain and NSA in USA and cables around the globe. (Hm, what should
1127 we tell them? :) Keep that in mind if you ever send anything
1128 unencrypted over the Internet.
</p
>
1130 <p
>PS: KML files are drawn using
1131 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
1132 Rublev
<a/
>, as it was less cluttered than the local Linux application
1133 Marble. There are heaps of other options too.
</p
>
1135 <p
>As usual, if you use Bitcoin and want to show your support of my
1136 activities, please send Bitcoin donations to my address
1137 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1142 <title>Appstream just learned how to map hardware to packages too!
</title>
1143 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
1144 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
1145 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
1146 <description><p
>I received a very nice Christmas present today. As my regular
1147 readers probably know, I have been working on the
1148 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
1149 system
</a
> for many years. The goal of the Isenkram system is to make
1150 it easier for users to figure out what to install to get a given piece
1151 of hardware to work in Debian, and a key part of this system is a way
1152 to map hardware to packages. Isenkram have its own mapping database,
1153 and also uses data provided by each package using the AppStream
1154 metadata format. And today,
1155 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
1156 Debian learned to look up hardware the same way Isenkram is doing it,
1157 ie using fnmatch():
</p
>
1159 <p
><pre
>
1160 % appstreamcli what-provides modalias \
1161 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1162 Identifier: pymissile [generic]
1164 Summary: Control original Striker USB Missile Launcher
1166 % appstreamcli what-provides modalias usb:v0694p0002d0000
1167 Identifier: libnxt [generic]
1169 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1172 Identifier: t2n [generic]
1174 Summary: Simple command-line tool for Lego NXT
1177 Identifier: python-nxt [generic]
1179 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1182 Identifier: nbc [generic]
1184 Summary: C compiler for LEGO Mindstorms NXT bricks
1187 </pre
></p
>
1189 <p
>A similar query can be done using the combined AppStream and
1190 Isenkram databases using the isenkram-lookup tool:
</p
>
1192 <p
><pre
>
1193 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1195 % isenkram-lookup usb:v0694p0002d0000
1201 </pre
></p
>
1203 <p
>You can find modalias values relevant for your machine using
1204 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
1206 <p
>If you want to make this system a success and help Debian users
1207 make the most of the hardware they have, please
1208 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
1209 AppStream metadata for your package following the guidelines
</a
>
1210 documented in the wiki. So far only
11 packages provide such
1211 information, among the several hundred hardware specific packages in
1212 Debian. The Isenkram database on the other hand contain
101 packages,
1213 mostly related to USB dongles. Most of the packages with hardware
1214 mapping in AppStream are LEGO Mindstorms related, because I have, as
1215 part of my involvement in
1216 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
1217 team
</a
> given priority to making sure LEGO users get proposed the
1218 complete set of packages in Debian for that particular hardware. The
1219 team also got a nice Christmas present today. The
1220 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
1221 package
</a
> made it into Debian. With this package in place, it is
1222 now possible to use the LEGO Mindstorms NXT unit with only free
1223 software, as the nxt-firmware package contain the source and firmware
1224 binaries for the NXT brick.
</p
>
1226 <p
>As usual, if you use Bitcoin and want to show your support of my
1227 activities, please send Bitcoin donations to my address
1228 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1233 <title>Isenkram updated with a lot more hardware-package mappings
</title>
1234 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
1235 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
1236 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
1237 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1238 system
</a
> I wrote two years ago to make it easier in Debian to find
1239 and install packages to get your hardware dongles to work, is still
1240 going strong. It is a system to look up the hardware present on or
1241 connected to the current system, and map the hardware to Debian
1242 packages. It can either be done using the tools in isenkram-cli or
1243 using the user space daemon in the isenkram package. The latter will
1244 notify you, when inserting new hardware, about what packages to
1245 install to get the dongle working. It will even provide a button to
1246 click on to ask packagekit to install the packages.
</p
>
1248 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
1250 <p
><pre
>
1267 </pre
></p
>
1269 <p
>It can also list the firware package providing firmware requested
1270 by the load kernel modules, which in my case is an empty list because
1271 I have all the firmware my machine need:
1273 <p
><pre
>
1274 % /usr/sbin/isenkram-autoinstall-firmware -l
1275 info: did not find any firmware files requested by loaded kernel modules. exiting
1277 </pre
></p
>
1279 <p
>The last few days I had a look at several of the around
250
1280 packages in Debian with udev rules. These seem like good candidates
1281 to install when a given hardware dongle is inserted, and I found
1282 several that should be proposed by isenkram. I have not had time to
1283 check all of them, but am happy to report that now there are
97
1284 packages packages mapped to hardware by Isenkram.
11 of these
1285 packages provide hardware mapping using AppStream, while the rest are
1286 listed in the modaliases file provided in isenkram.
</p
>
1288 <p
>These are the packages with hardware mappings at the moment. The
1289 <strong
>marked packages
</strong
> are also announcing their hardware
1290 support using AppStream, for everyone to use:
</p
>
1292 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
1293 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
1294 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
1295 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
1296 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
1297 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1298 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
1299 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1300 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1301 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1302 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
1303 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1304 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
1305 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1306 pcscd, pidgin-blinklight, printer-driver-splix,
1307 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
1308 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1309 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1310 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1311 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1312 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1313 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1314 xserver-xorg-video-vmware, yubikey-personalization and
1315 zd1211-firmware
</p
>
1317 <p
>If you know of other packages, please let me know with a wishlist
1318 bug report against the isenkram-cli package, and ask the package
1320 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
1321 metadata according to the guidelines
</a
> to provide the information
1322 for everyone. In time, I hope to get rid of the isenkram specific
1323 hardware mapping and depend exclusively on AppStream.
</p
>
1325 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
1326 much hardware, and suggest that the package with with any ethernet
1327 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
1328 the details. I hope the maintainer find time to address it soon. In
1329 the mean time I provide an override in isenkram.
</p
>
1334 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
1335 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
1336 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
1337 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
1338 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
1340 <p
>In my early years, I played
1341 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
1342 Elite
</a
> on my PC. I spent many months trading and fighting in
1343 space, and reached the
'elite
' fighting status before I moved on. The
1344 original Elite game was available on Commodore
64 and the IBM PC
1345 edition I played had a
64 KB executable. I am still impressed today
1346 that the authors managed to squeeze both a
3D engine and details about
1347 more than
2000 planet systems across
7 galaxies into a binary so
1350 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
1351 software game Oolite inspired by Elite
</a
> for a while, but did not
1352 really have time to test it properly until a few days ago. It was
1353 great to discover that my old knowledge about trading routes were
1354 still valid. But my fighting and flying abilities were gone, so I had
1355 to retrain to be able to dock on a space station. And I am still not
1356 able to make much resistance when I am attacked by pirates, so I
1357 bougth and mounted the most powerful laser in the rear to be able to
1358 put up at least some resistance while fleeing for my life. :)
</p
>
1360 <p
>When playing Elite in the late eighties, I had to discover
1361 everything on my own, and I had long lists of prices seen on different
1362 planets to be able to decide where to trade what. This time I had the
1364 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
1365 where information about each planet is easily available with common
1366 price ranges and suggested trading routes. This improved my ability
1367 to earn money and I have been able to earn enough to buy a lot of
1368 useful equipent in a few days. I believe I originally played for
1369 months before I could get a docking computer, while now I could get it
1370 after less then a week.
</p
>
1372 <p
>If you like science fiction and dreamed of a life as a vagabond in
1373 space, you should try out Oolite. It is available for Linux, MacOSX
1374 and Windows, and is included in Debian and derivatives since
2011.
</p
>
1376 <p
>As usual, if you use Bitcoin and want to show your support of my
1377 activities, please send Bitcoin donations to my address
1378 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1383 <title>Quicker Debian installations using eatmydata
</title>
1384 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
1385 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
1386 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
1387 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
1388 installation system, observing how using
1389 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
1390 could speed up the installation
</a
> quite a bit. My testing measured
1391 speedup around
20-
40 percent for Debian Edu, where we install around
1392 1000 packages from within the installer. The eatmydata package
1393 provide a way to disable/delay file system flushing. This is a bit
1394 risky in the general case, as files that should be stored on disk will
1395 stay only in memory a bit longer than expected, causing problems if a
1396 machine crashes at an inconvenient time. But for an installation, if
1397 the machine crashes during installation the process is normally
1398 restarted, and avoiding disk operations as much as possible to speed
1399 up the process make perfect sense.
1401 <p
>I added code in the Debian Edu specific installation code to enable
1402 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
1403 but did not have time to push it any further. But a few months ago I
1404 picked it up again and worked with the libeatmydata package maintainer
1405 Mattia Rizzolo to make it easier for everyone to get this installation
1406 speedup in Debian. Thanks to our cooperation There is now an
1407 eatmydata-udeb package in Debian testing and unstable, and simply
1408 enabling/installing it in debian-installer (d-i) is enough to get the
1409 quicker installations. It can be enabled using preseeding. The
1410 following untested kernel argument should do the trick:
</p
>
1412 <blockquote
><pre
>
1413 preseed/early_command=
"anna-install eatmydata-udeb
"
1414 </pre
></blockquote
>
1416 <p
>This should ask d-i to install the package inside the d-i
1417 environment early in the installation sequence. Having it installed
1418 in d-i in turn will make sure the relevant scripts are called just
1419 after debootstrap filled /target/ with the freshly installed Debian
1420 system to configure apt to run dpkg with eatmydata. This is enough to
1421 speed up the installation process. There is a proposal to
1422 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1423 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1424 tested its impact.
</p
>
1430 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1431 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1432 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1433 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1434 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1435 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1436 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1437 elever over det ganske land skal levere inn hvert år. Det mange ikke
1438 vet er at selv om de kommersielle alternativene
1439 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1440 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1441 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1442 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1443 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1444 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1445 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1446 nynorsk, og få den automatoversatt til det andre skriftspråket.
1447 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1448 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1449 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1450 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1451 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1452 teksten din i webskjemaet der.
1454 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1455 teknologien kan du enten installere pakken
1456 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1457 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1458 api.apertium.org. Se
1459 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1460 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1461 denne teksten som ble skrevet på bokmål over maskinoversatt til
1466 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1467 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1468 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1469 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1470 veit er at sjølv om dei kommersielle alternativa
1471 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1472 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1473 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1474 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1475 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1476 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1477 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1478 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1479 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1480 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1481 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1482 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1483 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1484 teksta di i *webskjemaet der.
1486 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1487 teknologien kan du anten installera pakken
1488 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1489 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1490 *api.*apertium.org. Sjå
1491 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1492 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1493 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1499 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1500 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1501 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1502 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1503 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1504 profiler able to run benchmarking experiments on the instrumented
1505 multi-threaded program, finally
1506 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1507 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1509 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1510 blogged about the coz tool
</a
> in August working with upstream to make
1511 it suitable for Debian. There are still issues with clang
1512 compatibility, inline assembly only working x86 and minimized
1513 JavaScript libraries.
</p
>
1515 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1517 <p
><blockquote
>
1518 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1519 </blockquote
></p
>
1521 <p
>This will produce a profile.coz file in the current working
1522 directory with the profiling information. This is then given to a
1523 JavaScript application provided in the package and available from
1524 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1525 To start the local copy, invoke it in a browser like this:
</p
>
1527 <p
><blockquote
>
1528 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1529 </blockquote
></p
>
1531 <p
>See the project home page and the
1532 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1533 ;login: article on Coz
</a
> for more information on how it is
1539 <title>My own self balancing Lego Segway
</title>
1540 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1541 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1542 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1543 <description><p
>A while back I received a Gyro sensor for the NXT
1544 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1545 present. It had been on my wishlist for a while, because I wanted to
1546 build a Segway like balancing lego robot. I had already built
1547 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1548 robot
</a
> with the kids, using the light/color sensor included in the
1549 NXT kit as the balance sensor, but it was not working very well. It
1550 could balance for a while, but was very sensitive to the light
1551 condition in the room and the reflective properties of the surface and
1552 would fall over after a short while. I wanted something more robust,
1554 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1555 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1556 wishlist for some years before it suddenly showed up as a gift from my
1557 loved ones. :)
</p
>
1559 <p
>Unfortunately I have not had time to sit down and play with it
1560 since then. But that changed some days ago, when I was searching for
1561 lego segway information and came across a recipe from HiTechnic for
1563 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1564 HTWay
</a
>, a segway like balancing robot. Build instructions and
1565 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1566 code
</a
> was included, so it was just a question of putting it all
1567 together. And thanks to the great work of many Debian developers, the
1568 compiler needed to build the source for the NXT is already included in
1569 Debian, so I was read to go in less than an hour. The resulting robot
1570 do not look very impressive in its simplicity:
</p
>
1572 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1574 <p
>Because I lack the infrared sensor used to control the robot in the
1575 design from HiTechnic, I had to comment out the last task
1576 (taskControl). I simply placed /* and */ around it get the program
1577 working without that sensor present. Now it balances just fine until
1578 the battery status run low:
</p
>
1580 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1581 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1582 </video
></p
>
1584 <p
>Now we would like to teach it how to follow a line and take remote
1585 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1587 <p
>If you, like me, love LEGO and want to make sure we find the tools
1588 they need to work with LEGO in Debian and all our derivative
1589 distributions like Ubuntu, check out
1590 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1591 project page
</a
> and join the Debian LEGO team. Personally I own a
1592 RCX and NXT controller (no EV3), and would like to make sure the
1593 Debian tools needed to program the systems I own work as they
1599 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1600 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1601 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1602 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1603 <description><p
>In July
1604 <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
1605 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1606 the ability to receive SMS messages (aka without a cell phone). It is
1607 time to share some experiences and provide an updated setup.
</p
>
1609 <p
>The Signal app have worked fine for several months now, and I use
1610 it regularly to chat with my loved ones. I had a major snag at the
1611 end of my summer vacation, when the the app completely forgot my
1612 setup, identity and keys. The reason behind this major mess was
1613 running out of disk space. To avoid that ever happening again I have
1614 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1615 roll back to an earlier version if the files are wiped by mistake. I
1616 had to use it once after introducing the git backup. When rolling
1617 back to an earlier version, one need to use the
'reset session
' option
1618 in Signal to get going, and notify the people you talk with about the
1619 problem. I assume there is some sequence number tracking in the
1620 protocol to detect rollback attacks. The git repository is rather big
1621 (
674 MiB so far), but I have not tried to figure out if some of the
1622 content can be added to a .gitignore file due to lack of spare
1625 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1626 make it impossible to send messages using Signal. I could still
1627 receive them, but had to patch the code with a new timestamp to send.
1628 I believe the timeout is added by the developers to force people to
1629 upgrade to the latest version of the app, even when there is no
1630 protocol changes, to reduce the version skew among the user base and
1631 thus try to keep the number of support requests down.
</p
>
1633 <p
>Since my original recipe, the Signal source code changed slightly,
1634 making the old patch fail to apply cleanly. Below is an updated
1635 patch, including the shell wrapper I use to start Signal. The
1636 original version required a new user to locate the JavaScript console
1637 and call a function from there. I got help from a friend with more
1638 JavaScript knowledge than me to modify the code to provide a GUI
1639 button instead. This mean that to get started you just need to run
1640 the wrapper and click the
'Register without mobile phone
' to get going
1641 now. I
've also modified the timeout code to always set it to
90 days
1642 in the future, to avoid having to patch the code regularly.
</p
>
1644 <p
>So, the updated recipe for Debian Jessie:
</p
>
1648 <li
>First, install required packages to get the source code and the
1649 browser you need. Signal only work with Chrome/Chromium, as far as I
1650 know, so you need to install it.
1653 apt install git tor chromium
1654 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1655 </pre
></li
>
1657 <li
>Modify the source code using command listed in the the patch
1658 block below.
</li
>
1660 <li
>Start Signal using the run-signal-app wrapper (for example using
1661 <tt
>`pwd`/run-signal-app
</tt
>).
1663 <li
>Click on the
'Register without mobile phone
', will in a phone
1664 number you can receive calls to the next minute, receive the
1665 verification code and enter it into the form field and press
1666 'Register
'. Note, the phone number you use will be user Signal
1667 username, ie the way others can find you on Signal.
</li
>
1669 <li
>You can now use Signal to contact others. Note, new contacts do
1670 not show up in the contact list until you restart Signal, and there is
1671 no way to assign names to Contacts. There is also no way to create or
1672 update chat groups. I suspect this is because the web app do not have
1673 a associated contact database.
</li
>
1677 <p
>I am still a bit uneasy about using Signal, because of the way its
1678 main author moxie0 reject federation and accept dependencies to major
1679 corporations like Google (part of the code is fetched from Google) and
1680 Amazon (the central coordination point is owned by Amazon). See for
1682 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1683 LibreSignal issue tracker
</a
> for a thread documenting the authors
1684 view on these issues. But the network effect is strong in this case,
1685 and several of the people I want to communicate with already use
1686 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1687 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1688 laptop
</a
>? It already work on Windows and Android, and is included
1689 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1690 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1691 working on Debian Stable.
</p
>
1693 <p
>Anyway, this is the patch I apply to the Signal code to get it
1694 working. It switch to the production servers, disable to timeout,
1695 make registration easier and add the shell wrapper:
</p
>
1698 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1699 diff --git a/js/background.js b/js/background.js
1700 index
24b4c1d.
.579345f
100644
1701 --- a/js/background.js
1702 +++ b/js/background.js
1707 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1708 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1709 var SERVER_PORTS = [
80,
4433,
8443];
1710 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1711 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1712 var messageReceiver;
1713 window.getSocketStatus = function() {
1714 if (messageReceiver) {
1715 diff --git a/js/expire.js b/js/expire.js
1716 index
639aeae..beb91c3
100644
1721 'use strict
';
1722 - var BUILD_EXPIRATION =
0;
1723 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1725 window.extension = window.extension || {};
1727 diff --git a/js/views/install_view.js b/js/views/install_view.js
1728 index
7816f4f.
.1d6233b
100644
1729 --- a/js/views/install_view.js
1730 +++ b/js/views/install_view.js
1733 'click .step1
': this.selectStep.bind(this,
1),
1734 'click .step2
': this.selectStep.bind(this,
2),
1735 -
'click .step3
': this.selectStep.bind(this,
3)
1736 +
'click .step3
': this.selectStep.bind(this,
3),
1737 +
'click .callreg
': function() { extension.install(
'standalone
') },
1740 clearQR: function() {
1741 diff --git a/options.html b/options.html
1742 index dc0f28e.
.8d709f6
100644
1746 &lt;div class=
'nav
'>
1747 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1748 &lt;p
>{{ installTagline }}
&lt;/p
>
1749 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1750 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1751 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1754 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1755 &lt;span class=
'dot step2
'>&lt;/span
>
1756 &lt;span class=
'dot step3
'>&lt;/span
>
1757 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1758 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1764 +userdata=
"`pwd`/userdata
"
1765 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1766 + (cd $userdata
&& git init)
1768 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1770 + --proxy-server=
"socks://localhost:
9050" \
1771 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1773 chmod a+rx run-signal-app
1776 <p
>As usual, if you use Bitcoin and want to show your support of my
1777 activities, please send Bitcoin donations to my address
1778 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1783 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1784 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1785 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1786 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1787 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1788 system
</a
> provide a practical and easy way to figure out which
1789 packages support the hardware in a given machine. The command line
1790 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1791 convenient way to list and install packages relevant for the current
1792 hardware during system installation, both user space packages and
1793 firmware packages. The GUI background daemon on the other hand provide
1794 a pop-up proposing to install packages when a new dongle is inserted
1795 while using the computer. For example, if you plug in a smart card
1796 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1797 that package isn
't already installed, and if you plug in a USB video
1798 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1799 cheese is currently missing. This already work just fine.
</p
>
1801 <p
>But Isenkram depend on a database mapping from hardware IDs to
1802 package names. When I started no such database existed in Debian, so
1803 I made my own data set and included it with the isenkram package and
1804 made isenkram fetch the latest version of this database from git using
1805 http. This way the isenkram users would get updated package proposals
1806 as soon as I learned more about hardware related packages.
</p
>
1808 <p
>The hardware is identified using modalias strings. The modalias
1809 design is from the Linux kernel where most hardware descriptors are
1810 made available as a strings that can be matched using filename style
1811 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1812 identifiers.
</p
>
1814 <p
>The downside to the Isenkram specific database is that there is no
1815 information about relevant distribution / Debian version, making
1816 isenkram propose obsolete packages too. But along came AppStream, a
1817 cross distribution mechanism to store and collect metadata about
1818 software packages. When I heard about the proposal, I contacted the
1819 people involved and suggested to add a hardware matching rule using
1820 modalias strings in the specification, to be able to use AppStream for
1821 mapping hardware to packages. This idea was accepted and AppStream is
1822 now a great way for a package to announce the hardware it support in a
1823 distribution neutral way. I wrote
1824 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
1825 recipe on how to add such meta-information
</a
> in a blog post last
1826 December. If you have a hardware related package in Debian, please
1827 announce the relevant hardware IDs using AppStream.
</p
>
1829 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
1830 RCX or NXT unit, announce this support using AppStream. The effect is
1831 that when you insert such LEGO robot controller into your Debian
1832 machine, Isenkram will propose to install the packages needed to get
1833 it working. The intention is that this should allow the local user to
1834 start programming his robot controller right away without having to
1835 guess what packages to use or which permissions to fix.
</p
>
1837 <p
>But when I sat down with my son the other day to program our NXT
1838 unit using his Debian Stretch computer, I discovered something
1839 annoying. The local console user (ie my son) did not get access to
1840 the USB device for programming the unit. This used to work, but no
1841 longer in Jessie and Stretch. After some investigation and asking
1842 around on #debian-devel, I discovered that this was because udev had
1843 changed the mechanism used to grant access to local devices. The
1844 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
1845 no longer applied, because LDAP users no longer was added to the
1846 plugdev group during login. Michael Biebl told me that this method
1847 was obsolete and the new method used ACLs instead. This was good
1848 news, as the plugdev mechanism is a mess when using a remote user
1849 directory like LDAP. Using ACLs would make sure a user lost device
1850 access when she logged out, even if the user left behind a background
1851 process which would retain the plugdev membership with the ConsoleKit
1852 setup. Armed with this knowledge I moved on to fix the access problem
1853 for the LEGO Mindstorms related packages.
</p
>
1855 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
1856 applied directly for a device, or is applied in
1857 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
1858 LEGO Mindstorms udev rules did not have a class, I decided to add the
1859 tag directly in the udev rules files included in the packages. Here
1860 is one example. For the nqc C compiler for the RCX, the
1861 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
1863 <p
><pre
>
1864 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
1865 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
1866 </pre
></p
>
1868 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
1869 packages using plugdev in their /lib/udev/rules.d/ files should be
1870 changed to use this tag (either directly or indirectly via
1871 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
1872 to detect this?
</p
>
1874 <p
>I
've been unable to find good documentation on the uaccess feature.
1875 It is unclear to me if the uaccess tag is an internal implementation
1876 detail like the udev-acl tag used by
1877 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1878 indirect method is the preferred way. Michael
1879 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1880 documentation from the systemd project
</a
> and I hope it will make
1881 this clearer. For now I use the generic classes when they exist and
1882 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1883 directly if no such class exist.
</p
>
1885 <p
>To learn more about the isenkram system, please check out
1886 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1887 blog posts tagged isenkram
</a
>.
</p
>
1889 <p
>To help out making life for LEGO constructors in Debian easier,
1890 please join us on our IRC channel
1891 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1892 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1893 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1894 list is not yet created, but we are working on it. :)
</p
>
1896 <p
>As usual, if you use Bitcoin and want to show your support of my
1897 activities, please send Bitcoin donations to my address
1898 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1903 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1904 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1905 <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>
1906 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1907 <description><p
>In April we
1908 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1909 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1910 how to set up and administrate a Debian system. Today I am happy to
1911 report that the first draft is now publicly available. You can find
1912 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1913 Administrator
's Handbook page
</a
> (under Other languages). The first
1914 eight chapters have a first draft translation, and we are working on
1915 proofreading the content. If you want to help out, please start
1917 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1918 hosted weblate project page
</a
>, and get in touch using
1919 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1920 translators mailing list
</a
>. Please also check out
1921 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1922 contributors
</a
>. A good way to contribute is to proofread the text
1923 and update weblate if you find errors.
</p
>
1925 <p
>Our goal is still to make the Norwegian book available on paper as well as
1926 electronic form.
</p
>
1931 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1932 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1933 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1934 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1935 <description><p
>This summer, I read a great article
1936 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1937 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1938 how to profile multi-threaded programs. It presented a system for
1939 profiling software by running experiences in the running program,
1940 testing how run time performance is affected by
"speeding up
" parts of
1941 the code to various degrees compared to a normal run. It does this by
1942 slowing down parallel threads while the
"faster up
" code is running
1943 and measure how this affect processing time. The processing time is
1944 measured using probes inserted into the code, either using progress
1945 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1946 can also measure unmodified code by measuring complete the program
1947 runtime and running the program several times instead.
</p
>
1949 <p
>The project and presentation was so inspiring that I would like to
1950 get the system into Debian. I
1951 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1952 a WNPP request for it
</a
> and contacted upstream to try to make the
1953 system ready for Debian by sending patches. The build process need to
1954 be changed a bit to avoid running
'git clone
' to get dependencies, and
1955 to include the JavaScript web page used to visualize the collected
1956 profiling information included in the source package.
1957 But I expect that should work out fairly soon.
</p
>
1959 <p
>The way the system work is fairly simple. To run an coz experiment
1960 on a binary with debug symbols available, start the program like this:
1962 <p
><blockquote
><pre
>
1963 coz run --- program-to-run
1964 </pre
></blockquote
></p
>
1966 <p
>This will create a text file profile.coz with the instrumentation
1967 information. To show what part of the code affect the performance
1968 most, use a web browser and either point it to
1969 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1970 or use the copy from git (in the gh-pages branch). Check out this web
1971 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
1972 profiling more useful you include
&lt;coz.h
&gt; and insert the
1973 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1974 code, rebuild and run the profiler. This allow coz to do more
1975 targeted experiments.
</p
>
1977 <p
>A video published by ACM
1978 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1979 Coz profiler
</a
> is available from Youtube. There is also a paper
1980 from the
25th Symposium on Operating Systems Principles available
1982 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1983 finding code that counts with causal profiling
</a
>.
</p
>
1985 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1986 for Coz is available from github. It will only build with clang
1988 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1989 feature missing in GCC
</a
>, but I
've submitted
1990 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1991 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1993 <p
>Please get in touch if you, like me, would like to see this piece
1994 of software in Debian. I would very much like some help with the
1995 packaging effort, as I lack the in depth knowledge on how to package
1996 C++ libraries.
</p
>
2001 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
2002 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
2003 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
2004 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
2005 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2006 to be a slight challenge. Here is the recipe if I ever need to do it
2007 again. It all started by me wanting to try the recipe to set up
2008 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
2009 hardened Android installation
</a
> from the Tor project blog on a
2010 device I had access to. It is a old mobile phone with a broken
2011 microphone The initial idea had been to just
2012 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
2013 CyanogenMod on it
</a
>, but did not quite find time to start on it
2014 until a few days ago.
</p
>
2016 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
2017 loader (press volume down and power at the same time), (
2) select
2018 'fastboot
' before (
3) connecting the device via USB to a Linux
2019 machine, (
4) request the device identifier token by running
'fastboot
2020 oem get_identifier_token
', (
5) request the device unlocking key using
2021 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
2022 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
2024 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
2025 or newer, and the device I was working on had
2.00.0027. This
2026 apparently can be easily fixed by downloading a Windows program and
2027 running it on your Windows machine, if you accept the terms Microsoft
2028 require you to accept to use Windows - which I do not. So I had to
2029 come up with a different approach. I got a lot of help from AndyCap
2030 on #nuug, and would not have been able to get this working without
2033 <p
>First I needed to extract the hboot firmware from
2034 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
2035 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
2036 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
2037 project named unruu
</a
> using libunshield. The unshield tool did not
2038 recognise the file format, but unruu worked and extracted rom.zip,
2039 containing the new hboot firmware and a text file describing which
2040 devices it would work for.
</p
>
2042 <p
>Next, I needed to get the new firmware into the device. For this I
2043 followed some instructions
2044 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
2045 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
2046 machine with Debian testing:
</p
>
2048 <p
><pre
>
2049 adb reboot-bootloader
2050 fastboot oem rebootRUU
2051 fastboot flash zip rom.zip
2052 fastboot flash zip rom.zip
2054 </pre
></p
>
2056 <p
>The flash command apparently need to be done twice to take effect,
2057 as the first is just preparations and the second one do the flashing.
2058 The adb command is just to get to the boot loader menu, so turning the
2059 device on while holding volume down and the power button should work
2062 <p
>With the new hboot version in place I could start following the
2063 instructions on the HTC developer web site. I got the device token
2064 like this:
</p
>
2066 <p
><pre
>
2067 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
2070 <p
>And once I got the unlock code via email, I could use it like
2073 <p
><pre
>
2074 fastboot flash unlocktoken Unlock_code.bin
2075 </pre
></p
>
2077 <p
>And with that final step in place, the phone was unlocked and I
2078 could start stuffing the software of my own choosing into the device.
2079 So far I only inserted a replacement recovery image to wipe the phone
2080 before I start. We will see what happen next. Perhaps I should
2081 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
2086 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
2087 <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>
2088 <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>
2089 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
2090 <description><p
>For a while now, I have wanted to test
2091 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
2092 said to provide end to end encrypted communication and several of my
2093 friends and family are already using it. As I by choice do not own a
2094 mobile phone, this proved to be harder than expected. And I wanted to
2095 have the source of the client and know that it was the code used on my
2096 machine. But yesterday I managed to get it working. I used the
2097 Github source, compared it to the source in
2098 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
2099 Signal Chrome app
</a
> available from the Chrome web store, applied
2100 patches to use the production Signal servers, started the app and
2101 asked for the hidden
"register without a smart phone
" form. Here is
2102 the recipe how I did it.
</p
>
2104 <p
>First, I fetched the Signal desktop source from Github, using
2107 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2110 <p
>Next, I patched the source to use the production servers, to be
2111 able to talk to other Signal users:
</p
>
2114 cat
&lt;
&lt;EOF | patch -p0
2115 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2116 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2117 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
2122 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
2123 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
2124 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
2125 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
2126 var messageReceiver;
2127 window.getSocketStatus = function() {
2128 if (messageReceiver) {
2129 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
2130 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2131 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
2134 'use strict
';
2135 - var BUILD_EXPIRATION =
0;
2136 + var BUILD_EXPIRATION =
1474492690000;
2138 window.extension = window.extension || {};
2143 <p
>The first part is changing the servers, and the second is updating
2144 an expiration timestamp. This timestamp need to be updated regularly.
2145 It is set
90 days in the future by the build process (Gruntfile.js).
2146 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
2148 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
2149 script to launch Signal in Chromium.
</p
>
2156 --proxy-server=
"socks://localhost:
9050" \
2157 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2160 <p
> The script start the app and configure Chromium to use the Tor
2161 SOCKS5 proxy to make sure those controlling the Signal servers (today
2162 Amazon and Whisper Systems) as well as those listening on the lines
2163 will have a harder time location my laptop based on the Signal
2164 connections if they use source IP address.
</p
>
2166 <p
>When the script starts, one need to follow the instructions under
2167 "Standalone Registration
" in the CONTRIBUTING.md file in the git
2168 repository. I right clicked on the Signal window to get up the
2169 Chromium debugging tool, visited the
'Console
' tab and wrote
2170 'extension.install(
"standalone
")
' on the console prompt to get the
2171 registration form. Then I entered by land line phone number and
2172 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
2173 repeated the verification code three times. After entering the number
2174 into the verification code field in the form, I could start using
2175 Signal from my laptop.
2177 <p
>As far as I can tell, The Signal app will leak who is talking to
2178 whom and thus who know who to those controlling the central server,
2179 but such leakage is hard to avoid with a centrally controlled server
2180 setup. It is something to keep in mind when using Signal - the
2181 content of your chats are harder to intercept, but the meta data
2182 exposing your contact network is available to people you do not know.
2183 So better than many options, but not great. And sadly the usage is
2184 connected to my land line, thus allowing those controlling the server
2185 to associate it to my home and person. I would prefer it if only
2186 those I knew could tell who I was on Signal. There are options
2187 avoiding such information leakage, but most of my friends are not
2188 using them, so I am stuck with Signal for now.
</p
>
2190 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
2192 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
2193 and updated recipe for using the Signal app without a mobile
2194 phone
</a
>.
</p
>
2199 <title>The new
"best
" multimedia player in Debian?
</title>
2200 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
2201 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
2202 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
2203 <description><p
>When I set out a few weeks ago to figure out
2204 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
2205 multimedia player in Debian claimed to support most file formats /
2206 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
2207 the various players claimed support for. The range was from
55 to
130
2208 MIME types. I suspect most media formats are supported by all
2209 players, but this is not really reflected in the MimeTypes values in
2210 their desktop files. There are probably also some bogus MIME types
2211 listed, but it is hard to identify which one this is.
</p
>
2213 <p
>Anyway, in the mean time I got in touch with upstream for some of
2214 the players suggesting to add more MIME types to their desktop files,
2215 and decided to spend some time myself improving the situation for my
2216 favorite media player VLC. The fixes for VLC entered Debian unstable
2217 yesterday. The complete list of MIME types can be seen on the
2218 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
2219 player MIME type support status
</a
> Debian wiki page.
</p
>
2221 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
2222 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2223 kmplayer. I am sure some of the other players desktop files support
2224 several of the formats currently listed as working only with vlc,
2225 toten and parole.
</p
>
2227 <p
>A sad observation is that only
14 MIME types are listed as
2228 supported by all the tested multimedia players in Debian in their
2229 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2230 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2231 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2232 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2233 it sad that video/ogg and video/webm is not supported by all the media
2234 players in Debian. As far as I can tell, all of them can handle both
2240 <title>A program should be able to open its own files on Linux
</title>
2241 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
2242 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
2243 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
2244 <description><p
>Many years ago, when koffice was fresh and with few users, I
2245 decided to test its presentation tool when making the slides for a
2246 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2247 wrote the first draft of the slides, saved the result and went to bed
2248 the day before I would give the talk. The next day I took a plane to
2249 the location where the meeting should take place, and on the plane I
2250 started up koffice again to polish the talk a bit, only to discover
2251 that kpresenter refused to load its own data file. I cursed a bit and
2252 started making the slides again from memory, to have something to
2253 present when I arrived. I tested that the saved files could be
2254 loaded, and the day seemed to be rescued. I continued to polish the
2255 slides until I suddenly discovered that the saved file could no longer
2256 be loaded into kpresenter. In the end I had to rewrite the slides
2257 three times, condensing the content until the talk became shorter and
2258 shorter. After the talk I was able to pinpoint the problem
&ndash;
2259 kpresenter wrote inline images in a way itself could not understand.
2260 Eventually that bug was fixed and kpresenter ended up being a great
2261 program to make slides. The point I
'm trying to make is that we
2262 expect a program to be able to load its own data files, and it is
2263 embarrassing to its developers if it can
't.
</p
>
2265 <p
>Did you ever experience a program failing to load its own data
2266 files from the desktop file browser? It is not a uncommon problem. A
2267 while back I discovered that the screencast recorder
2268 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2269 browser would refuse to open. No video player claimed to understand
2270 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
2271 returning the application/ogg MIME type, which no video player I had
2272 installed listed as a MIME type they would understand. I asked for
2273 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
2274 behavour
</a
> and use the MIME type video/ogg instead. I also asked
2275 several video players to add video/ogg to their desktop files, to give
2276 the file browser an idea what to do about Ogg Theora files. After a
2277 while, the desktop file browsers in Debian started to handle the
2278 output from gtk-recordmydesktop properly.
</p
>
2280 <p
>But history repeats itself. A few days ago I tested the music
2281 system Rosegarden again, and I discovered that the KDE and xfce file
2282 browsers did not know what to do with the Rosegarden project files
2283 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
2284 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
2285 included in the next upload. To increase the chance of me remembering
2286 how to fix the problem next time some program fail to load its files
2287 from the file browser, here are some notes on how to fix it.
</p
>
2289 <p
>The file browsers in Debian in general operates on MIME types.
2290 There are two sources for the MIME type of a given file. The output from
2291 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
2292 shared MIME type registry (under /usr/share/mime/). The file MIME
2293 type is mapped to programs supporting the MIME type, and this
2294 information is collected from
2295 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
2296 desktop files
</a
> available in /usr/share/applications/. If there is
2297 one desktop file claiming support for the MIME type of the file, it is
2298 activated when asking to open a given file. If there are more, one
2299 can normally select which one to use by right-clicking on the file and
2300 selecting the wanted one using
'Open with
' or similar. In general
2301 this work well. But it depend on each program picking a good MIME
2303 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
2304 MIME type registered with IANA
</a
>), file and/or the shared MIME
2305 registry recognizing the file and the desktop file to list the MIME
2306 type in its list of supported MIME types.
</p
>
2308 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
2309 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
2310 Shared MIME database
</a
> look like this:
</p
>
2312 <p
><blockquote
><pre
>
2313 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2314 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
2315 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
2316 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
2317 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
2318 &lt;glob pattern=
"*.rg
"/
&gt;
2319 &lt;/mime-type
&gt;
2320 &lt;/mime-info
&gt;
2321 </pre
></blockquote
></p
>
2323 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
2324 (it is a gzipped XML file). Note, it is much better to use an
2325 official MIME type registered with IANA than it is to make up ones own
2326 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
2328 <p
>The desktop file of the rosegarden program failed to list
2329 audio/x-rosegarden in its list of supported MIME types, causing the
2330 file browsers to have no idea what to do with *.rg files:
</p
>
2332 <p
><blockquote
><pre
>
2333 % grep Mime /usr/share/applications/rosegarden.desktop
2334 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2335 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2337 </pre
></blockquote
></p
>
2339 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
2340 MimeType= line.
</p
>
2342 <p
>If you run into a file which fail to open the correct program when
2343 selected from the file browser, please check out the output from
2344 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
2345 MIME type is registered somewhere under /usr/share/mime/ and check
2346 that some desktop file under /usr/share/applications/ is claiming
2347 support for this MIME type. If not, please report a bug to have it
2353 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
2354 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
2355 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
2356 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
2357 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
2358 system
</a
> is a user-focused solution in Debian for handling hardware
2359 related packages. The idea is to have a database of mappings between
2360 hardware and packages, and pop up a dialog suggesting for the user to
2361 install the packages to use a given hardware dongle. Some use cases
2362 are when you insert a Yubikey, it proposes to install the software
2363 needed to control it; when you insert a braille reader list it
2364 proposes to install the packages needed to send text to the reader;
2365 and when you insert a ColorHug screen calibrator it suggests to
2366 install the driver for it. The system work well, and even have a few
2367 command line tools to install firmware packages and packages for the
2368 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
2370 <p
>The system was initially written using aptdaemon, because I found
2371 good documentation and example code on how to use it. But aptdaemon
2372 is going away and is generally being replaced by
2373 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
2374 so Isenkram needed a rewrite. And today, thanks to the great patch
2375 from my college Sunil Mohan Adapa in the FreedomBox project, the
2376 rewrite finally took place. I
've just uploaded a new version of
2377 Isenkram into Debian Unstable with the patch included, and the default
2378 for the background daemon is now to use PackageKit. To check it out,
2379 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
2380 and see if it is recognised.
</p
>
2382 <p
>If you want to know what kind of packages isenkram would propose for
2383 the machine it is running on, you can check out the isenkram-lookup
2384 program. This is what it look like on a Thinkpad X230:
</p
>
2386 <p
><blockquote
><pre
>
2402 </pre
></blockquote
></p
>
2404 <p
>The hardware mappings come from several places. The preferred way
2405 is for packages to announce their hardware support using
2406 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2407 cross distribution appstream system
</a
>.
2409 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2410 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2415 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2416 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2417 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2418 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2419 <description><p
>Yesterday I updated the
2420 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2421 package in Debian
</a
> with a few patches sent to me by skilled and
2422 enterprising users. There were some nice user and visible changes.
2423 First of all, both desktop menu entries now work. A design flaw in
2424 one of the script made the history graph fail to show up (its PNG was
2425 dumped in ~/.xsession-errors) if no controlling TTY was available.
2426 The script worked when called from the command line, but not when
2427 called from the desktop menu. I changed this to look for a DISPLAY
2428 variable or a TTY before deciding where to draw the graph, and now the
2429 graph window pop up as expected.
</p
>
2431 <p
>The next new feature is a discharge rate estimator in one of the
2432 graphs (the one showing the last few hours). New is also the user of
2433 colours showing charging in blue and discharge in red. The percentages
2434 of this graph is relative to last full charge, not battery design
2437 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2439 <p
>The other graph show the entire history of the collected battery
2440 statistics, comparing it to the design capacity of the battery to
2441 visualise how the battery life time get shorter over time. The red
2442 line in this graph is what the previous graph considers
100 percent:
2444 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2446 <p
>In this graph you can see that I only charge the battery to
80
2447 percent of last full capacity, and how the capacity of the battery is
2448 shrinking. :(
</p
>
2450 <p
>The last new feature is in the collector, which now will handle
2451 more hardware models. On some hardware, Linux power supply
2452 information is stored in /sys/class/power_supply/ACAD/, while the
2453 collector previously only looked in /sys/class/power_supply/AC/. Now
2454 both are checked to figure if there is power connected to the
2457 <p
>If you are interested in how your laptop battery is doing, please
2459 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2460 in Debian unstable, or rebuild it on Jessie to get it working on
2461 Debian stable. :) The upstream source is available from
<a
2462 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2463 Patches are very welcome.
</p
>
2465 <p
>As usual, if you use Bitcoin and want to show your support of my
2466 activities, please send Bitcoin donations to my address
2467 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2472 <title>Debian now with ZFS on Linux included
</title>
2473 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2474 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2475 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2476 <description><p
>Today, after many years of hard work from many people,
2477 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2478 Debian. The package status can be seen on
2479 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2480 for zfs-linux
</a
>. and
2481 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2482 team status page
</a
>. If you want to help out, please join us.
2483 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2484 source code
</a
> is available via git on Alioth. It would also be
2485 great if you could help out with
2486 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2487 it is an important piece of the puzzle to get ZFS working.
</p
>
2492 <title>What is the best multimedia player in Debian?
</title>
2493 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2494 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2495 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2496 <description><p
><strong
>Where I set out to figure out which multimedia player in
2497 Debian claim support for most file formats.
</strong
></p
>
2499 <p
>A few years ago, I had a look at the media support for Browser
2500 plugins in Debian, to get an idea which plugins to include in Debian
2501 Edu. I created a script to extract the set of supported MIME types
2502 for each plugin, and used this to find out which multimedia browser
2503 plugin supported most file formats / media types.
2504 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2505 result
</a
> can still be seen on the Debian wiki, even though it have
2506 not been updated for a while. But browser plugins are less relevant
2507 these days, so I thought it was time to look at standalone
2510 <p
>A few days ago I was tired of VLC not being listed as a viable
2511 player when I wanted to play videos from the Norwegian National
2512 Broadcasting Company, and decided to investigate why. The cause is a
2513 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2514 desktop file
</a
>. In the process I wrote a script to compare the set
2515 of MIME types announced in the desktop file and the browser plugin,
2516 only to discover that there is quite a large difference between the
2517 two for VLC. This discovery made me dig up the script I used to
2518 compare browser plugins, and adjust it to compare desktop files
2519 instead, to try to figure out which multimedia player in Debian
2520 support most file formats.
</p
>
2522 <p
>The result can be seen on the Debian Wiki, as
2523 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2524 table listing all MIME types supported by one of the packages included
2525 in the table
</a
>, with the package supporting most MIME types being
2526 listed first in the table.
</p
>
2528 </p
>The best multimedia player in Debian? It is totem, followed by
2529 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2530 kmplayer. Time for the other players to update their announced MIME
2536 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2537 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2538 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2539 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2540 <description>A friend of mine made me aware of
2541 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2542 handheld computer which will be delivered with Debian preinstalled. I
2543 would love to get one of those for my birthday. :)
</p
>
2545 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2546 plugs and many others connectors, and include a full keyboard and a
5"
2547 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2548 day of battery life time, but I have not seen any independent tests
2549 confirming this. The vendor is still collecting preorders, and the
2550 last I heard last night was that
22 more orders were needed before
2551 production started.
</p
>
2553 <p
>As far as I know, this is the first handheld preinstalled with
2554 Debian. Please let me know if you know of any others. Is it the
2555 first computer being sold with Debian preinstalled?
</p
>
2560 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2561 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2562 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2563 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2564 <description><p
>During this weekends
2565 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2566 squashing party and developer gathering
</a
>, we decided to do our part
2567 to make sure there are good books about Debian available in Norwegian
2568 Bokmål, and got in touch with the people behind the
2569 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2570 project
</a
> to get started. If you want to help out, please start
2572 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2573 hosted weblate project page
</a
>, and get in touch using
2574 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2575 translators mailing list
</a
>. Please also check out
2576 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2577 contributors
</a
>.
</p
>
2579 <p
>The book is already available on paper in English, French and
2580 Japanese, and our goal is to get it available on paper in Norwegian
2581 Bokmål too. In addition to the paper edition, there are also EPUB and
2582 Mobi versions available. And there are incomplete translations
2583 available for many more languages.
</p
>
2588 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2589 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2590 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2591 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2592 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2593 packages in Debian, and was quite surprised with what I found. I use
2594 ZFS myself at home, but did not really expect many others to do so.
2595 But I might be wrong.
</p
>
2597 <p
>According to
2598 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2599 results for spl-linux
</a
>, there are
1019 Debian installations, or
2600 0.53% of the population, with the package installed. As far as I know
2601 the only use of the spl-linux package is as a support library for ZFS
2602 on Linux, so I use it here as proxy for measuring the number of ZFS
2603 installation on Linux in Debian. In the kFreeBSD variant of Debian
2604 the ZFS feature is already available, and there
2605 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2606 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2607 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2609 <p
>But even though the Debian project leader Lucas Nussbaum
2610 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2611 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2612 cleared, the package is still not in Debian. The package is again in
2613 the NEW queue. Several uploads have been rejected so far because the
2614 debian/copyright file was incomplete or wrong, but there is no reason
2615 to give up. The current status can be seen on
2616 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2617 team status page
</a
>, and
2618 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2619 source code
</a
> is available on Alioth.
</p
>
2621 <p
>As I want ZFS to be included in next version of Debian to make sure
2622 my home server can function in the future using only official Debian
2623 packages, and the current blocker is to get the debian/copyright file
2624 accepted by the FTP masters in Debian, I decided a while back to try
2625 to help out the team. This was the background for my blog post about
2626 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2627 updating and checking debian/copyright semi-automatically
</a
>, and I
2628 used the techniques I explored there to try to find any errors in the
2629 copyright file. It is not very easy to check every one of the around
2630 2000 files in the source package, but I hope we this time got it
2631 right. If you want to help out, check out the git source and try to
2632 find missing entries in the debian/copyright file.
</p
>
2637 <title>Full battery stats collector is now available in Debian
</title>
2638 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2639 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2640 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2641 <description><p
>Since this morning, the battery-stats package in Debian include an
2642 extended collector that will collect the complete battery history for
2643 later processing and graphing. The original collector store the
2644 battery level as percentage of last full level, while the new
2645 collector also record battery vendor, model, serial number, design
2646 full level, last full level and current battery level. This make it
2647 possible to predict the lifetime of the battery as well as visualise
2648 the energy flow when the battery is charging or discharging.
</p
>
2650 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2651 in the version
0.5.1 package in unstable. Get the new battery level graph
2652 and lifetime prediction by running:
2654 <p
><pre
>
2655 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2656 </pre
></p
>
2658 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2660 <p
>The flow in/out of the battery can be seen by running (no menu
2661 entry yet):
</p
>
2663 <p
><pre
>
2664 /usr/share/battery-stats/battery-stats-graph-flow
2665 </pre
></p
>
2667 <p
>I
'm not quite happy with the way the data is visualised, at least
2668 when there are few data points. The graphs look a bit better with a
2669 few years of data.
</p
>
2671 <p
>A while back one important feature I use in the battery stats
2672 collector broke in Debian. The scripts in
2673 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2674 suspect it happened when Jessie started using systemd, but I do not
2675 know. The issue is reported as
2676 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2677 pm-utils. I managed to work around it by adding an udev rule to call
2678 the collector script every time the power connector is connected and
2679 disconnected. With this fix in place it was finally time to make a
2680 new release of the package, and get it into Debian.
</p
>
2682 <p
>If you are interested in how your laptop battery is doing, please
2684 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2685 in Debian unstable, or rebuild it on Jessie to get it working on
2686 Debian stable. :) The upstream source is available from
2687 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2688 As always, patches are very welcome.
</p
>
2693 <title>Making battery measurements a little easier in Debian
</title>
2694 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2695 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2696 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2697 <description><p
>Back in September, I blogged about
2698 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2699 system I wrote to collect statistics about my laptop battery
</a
>, and
2700 how it showed the decay and death of this battery (now replaced). I
2701 created a simple deb package to handle the collection and graphing,
2702 but did not want to upload it to Debian as there were already
2703 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2704 package in Debian
</a
> that should do the same thing, and I did not see
2705 a point of uploading a competing package when battery-stats could be
2706 fixed instead. I reported a few bugs about its non-function, and
2707 hoped someone would step in and fix it. But no-one did.
</p
>
2709 <p
>I got tired of waiting a few days ago, and took matters in my own
2710 hands. The end result is that I am now the new upstream developer of
2711 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2712 battery-stats in Debian, and the package in Debian unstable is finally
2713 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2714 information provided by the Linux kernel. If you install the
2715 battery-stats package from unstable now, you will be able to get a
2716 graph of the current battery fill level, to get some idea about the
2717 status of the battery. The source package build and work just fine in
2718 Debian testing and stable (and probably oldstable too, but I have not
2719 tested). The default graph you get for that system look like this:
</p
>
2721 <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
>
2723 <p
>My plans for the future is to merge my old scripts into the
2724 battery-stats package, as my old scripts collected a lot more details
2725 about the battery. The scripts are merged into the upstream
2726 battery-stats git repository already, but I am not convinced they work
2727 yet, as I changed a lot of paths along the way. Will have to test a
2728 bit more before I make a new release.
</p
>
2730 <p
>I will also consider changing the file format slightly, as I
2731 suspect the way I combine several values into one field might make it
2732 impossible to know the type of the value when using it for processing
2733 and graphing.
</p
>
2735 <p
>If you would like I would like to keep an close eye on your laptop
2736 battery, check out the battery-stats package in
2737 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2739 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2740 I would love some help to improve the system further.
</p
>
2745 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2746 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2748 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2749 <description><p
>Making packages for Debian requires quite a lot of attention to
2750 details. And one of the details is the content of the
2751 debian/copyright file, which should list all relevant licenses used by
2752 the code in the package in question, preferably in
2753 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2754 readable DEP5 format
</a
>.
</p
>
2756 <p
>For large packages with lots of contributors it is hard to write
2757 and update this file manually, and if you get some detail wrong, the
2758 package is normally rejected by the ftpmasters. So getting it right
2759 the first time around get the package into Debian faster, and save
2760 both you and the ftpmasters some work.. Today, while trying to figure
2761 out what was wrong with
2762 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2763 zfsonlinux copyright file
</a
>, I decided to spend some time on
2764 figuring out the options for doing this job automatically, or at least
2765 semi-automatically.
</p
>
2767 <p
>Lucikly, there are at least two tools available for generating the
2768 file based on the code in the source package,
2769 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2770 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2771 not sure which one of them came first, but both seem to be able to
2772 create a sensible draft file. As far as I can tell, none of them can
2773 be trusted to get the result just right, so the content need to be
2774 polished a bit before the file is OK to upload. I found the debmake
2776 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2777 blog posts from
2014</a
>.
2779 <p
>To generate using debmake, use the -cc option:
2781 <p
><pre
>
2782 debmake -cc
> debian/copyright
2783 </pre
></p
>
2785 <p
>Note there are some problems with python and non-ASCII names, so
2786 this might not be the best option.
</p
>
2788 <p
>The cme option is based on a config parsing library, and I found
2790 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2791 blog post from
2015</a
>. To generate using cme, use the
'update
2792 dpkg-copyright
' option:
2794 <p
><pre
>
2795 cme update dpkg-copyright
2796 </pre
></p
>
2798 <p
>This will create or update debian/copyright. The cme tool seem to
2799 handle UTF-
8 names better than debmake.
</p
>
2801 <p
>When the copyright file is created, I would also like some help to
2802 check if the file is correct. For this I found two good options,
2803 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2804 to focus on license types and file matching, and is able to detect
2805 ineffective blocks in the copyright file. The latter reports missing
2806 copyright holders and years, but was confused by inconsistent license
2807 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2808 fix all issues reported by them before uploading. But I do not know
2809 if the tools and the ftpmasters agree on what is important to fix in a
2810 copyright file, so the package might still be rejected.
</p
>
2812 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2813 will read through the source and try to find all copyright statements.
2814 It is not comparing the result to the content of debian/copyright, but
2815 can be useful when verifying the content of the copyright file.
</p
>
2817 <p
>Are you aware of better tools in Debian to create and update
2818 debian/copyright file. Please let me know, or blog about it on
2819 planet.debian.org.
</p
>
2821 <p
>As usual, if you use Bitcoin and want to show your support of my
2822 activities, please send Bitcoin donations to my address
2823 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2825 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
2826 on how to use licensecheck and cdbs to create a draft copyright file
2828 <p
><pre
>
2829 licensecheck --copyright -r `find * -type f` | \
2830 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
2831 </pre
></p
>
2833 <p
>He mentioned that he normally check the generated file into the
2834 version control system to make it easier to discover license and
2835 copyright changes in the upstream source. I will try to do the same
2836 with my packages in the future.
</p
>
2838 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
2839 against using -quiet for new users, so I removed it from the proposed
2840 command line.
</p
>
2845 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
2846 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
2847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
2848 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
2849 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
2850 is taking shape in Debian, and one provided feature is a very
2851 convenient way to tell you which package to install to make a given
2852 firmware file available when the kernel is looking for it. This can
2853 be done using apt-file too, but that is for someone else to blog
2856 <p
>Here is a small recipe to find the package with a given firmware
2857 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
2858 picked from the set of firmware announced using appstream in Debian
2859 unstable. In general you would be looking for the firmware requested
2860 by the kernel during kernel module loading. To find the package
2861 providing the example file, do like this:
</p
>
2863 <blockquote
><pre
>
2864 % apt install appstream
2868 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
2869 awk
'/Package:/ {print $
2}
'
2872 </pre
></blockquote
>
2874 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2875 appstream wiki
</a
> page to learn how to embed the package metadata in
2876 a way appstream can use.
</p
>
2878 <p
>This same approach can be used to find any package supporting a
2879 given MIME type. This is very useful when you get a file you do not
2880 know how to handle. First find the mime type using
<tt
>file
2881 --mime-type
</tt
>, and next look up the package providing support for
2882 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2883 and you can find all packages handling this type like this:
</p
>
2885 <blockquote
><pre
>
2886 % apt install appstream
2890 % appstreamcli what-provides mimetype image/svg+xml | \
2891 awk
'/Package:/ {print $
2}
'
2913 </pre
></blockquote
>
2915 <p
>I believe the MIME types are fetched from the desktop file for
2916 packages providing appstream metadata.
</p
>
2921 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2922 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2924 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2925 <description><p
>Most people seem not to realise that every time they walk around
2926 with the computerised radio beacon known as a mobile phone their
2927 position is tracked by the phone company and often stored for a long
2928 time (like every time a SMS is received or sent). And if their
2929 computerised radio beacon is capable of running programs (often called
2930 mobile apps) downloaded from the Internet, these programs are often
2931 also capable of tracking their location (if the app requested access
2932 during installation). And when these programs send out information to
2933 central collection points, the location is often included, unless
2934 extra care is taken to not send the location. The provided
2935 information is used by several entities, for good and bad (what is
2936 good and bad, depend on your point of view). What is certain, is that
2937 the private sphere and the right to free movement is challenged and
2938 perhaps even eradicated for those announcing their location this way,
2939 when they share their whereabouts with private and public
2942 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2944 <p
>The phone company logs provide a register of locations to check out
2945 when one want to figure out what the tracked person was doing. It is
2946 unavailable for most of us, but provided to selected government
2947 officials, company staff, those illegally buying information from
2948 unfaithful servants and crackers stealing the information. But the
2949 public information can be collected and analysed, and a free software
2950 tool to do so is called
2951 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2952 discovered it when I read
2953 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2954 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2955 November
2014, and decided to check if it was available in Debian.
2956 The python program was in Debian, but
2957 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2958 Debian
</a
> was completely broken and practically unmaintained. I
2959 uploaded a new version which did not work quite right, but did not
2960 have time to fix it then. This Christmas I decided to finally try to
2961 get Creepy operational in Debian. Now a fixed version is available in
2962 Debian unstable and testing, and almost all Debian specific patches
2964 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2966 <p
>The Creepy program visualises geolocation information fetched from
2967 Twitter, Instagram, Flickr and Google+, and allow one to get a
2968 complete picture of every social media message posted recently in a
2969 given area, or track the movement of a given individual across all
2970 these services. Earlier it was possible to use the search API of at
2971 least some of these services without identifying oneself, but these
2972 days it is impossible. This mean that to use Creepy, you need to
2973 configure it to log in as yourself on these services, and provide
2974 information to them about your search interests. This should be taken
2975 into account when using Creepy, as it will also share information
2976 about yourself with the services.
</p
>
2978 <p
>The picture above show the twitter messages sent from (or at least
2979 geotagged with a position from) the city centre of Oslo, the capital
2980 of Norway. One useful way to use Creepy is to first look at
2981 information tagged with an area of interest, and next look at all the
2982 information provided by one or more individuals who was in the area.
2983 I tested it by checking out which celebrity provide their location in
2984 twitter messages by checkout out who sent twitter messages near a
2985 Norwegian TV station, and next could track their position over time,
2986 making it possible to locate their home and work place, among other
2987 things. A similar technique have been
2988 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2989 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2990 tool to discover lying governments, and a useful tool to help people
2991 understand the value of the private information they provide to the
2994 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2995 it depend on several python modules currently missing in Jessie (at
2996 least python-instagram, python-flickrapi and
2997 python-requests-toolbelt).
</p
>
2999 <p
>(I have uploaded
3000 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
3001 screenshots.debian.net
</a
> and licensed it under the same terms as the
3002 Creepy program in Debian.)
</p
>
3007 <title>Always download Debian packages using Tor - the simple recipe
</title>
3008 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
3009 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
3010 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
3011 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
3012 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
3013 that those listening on the Internet lines would have good reason to
3014 believe a computer have a given security hole
</a
> if it download a
3015 security fix from a Debian mirror. This is a good reason to always
3016 use encrypted connections to the Debian mirror, to make sure those
3017 listening do not know which IP address to attack. In August, Richard
3018 Hartmann observed that encryption was not enough, when it was possible
3019 to interfere download size to security patches or the fact that
3020 download took place shortly after a security fix was released, and
3021 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
3022 to always use Tor to download packages from the Debian mirror
</a
>. He
3023 was not the first to propose this, as the
3024 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
3025 package by Tim Retout already existed to make it easy to convince apt
3026 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
3027 aware of that package when I read the blog post from Richard.
</p
>
3029 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
3030 sysadmins, and he set up a Tor hidden service on one of the central
3031 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3032 it possible to download packages directly between two tor nodes,
3033 making sure the network traffic always were encrypted.
</p
>
3035 <p
>Here is a short recipe for enabling this on your machine, by
3036 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
3037 urls with tor+http and tor+https, and using the hidden service instead
3038 of the official Debian mirror site. I recommend installing
3039 <tt
>etckeeper
</tt
> before you start to have a history of the changes
3040 done in /etc/.
</p
>
3042 <blockquote
><pre
>
3043 apt install apt-transport-tor
3044 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
3045 sed -i
's% http% tor+http%
' /etc/apt/sources.list
3046 </pre
></blockquote
>
3048 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
3049 the sed commands for these too. The sed command is assuming your are
3050 using the ftp.debian.org Debian mirror. Adjust the command (or just
3051 edit the file manually) to match your mirror.
</p
>
3053 <p
>This work in Debian Jessie and later. Note that tools like
3054 <tt
>apt-file
</tt
> only recently started using the apt transport
3055 system, and do not work with these tor+http URLs. For
3056 <tt
>apt-file
</tt
> you need the version currently in experimental,
3057 which need a recent apt version currently only in unstable. So if you
3058 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
3060 <p
>Another advantage from this change is that your machine will start
3061 using Tor regularly and at fairly random intervals (every time you
3062 update the package lists or upgrade or install a new package), thus
3063 masking other Tor traffic done from the same machine. Using Tor will
3064 become normal for the machine in question.
</p
>
3066 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
3067 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
3068 enabled. It would be great if it was the default on any Debian
3074 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
3075 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
3076 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
3077 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
3078 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
3079 call the car license plate numbers in those days. I would write the
3080 numbers down in my little book and compare notes with the other kids
3081 to see how many region codes we had seen and if we had seen some
3082 exotic or special region codes and numbers. It was a fun game to pass
3083 time, as we kids have plenty of it.
</p
>
3085 <p
>A few days I came across
3086 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
3087 project
</a
>, a free software project to automatically discover and
3088 report license plates in images and video streams, and provide the
3089 "car numbers
" in a machine readable format. I
've been looking for
3090 such system for a while now, because I believe it is a bad idea that the
3091 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
3092 number plate recognition
</a
> tool only is available in the hands of
3093 the powerful, and want it to be available also for the powerless to
3094 even the score when it comes to surveillance and sousveillance. I
3095 discovered the developer
3096 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
3097 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
3098 help him get it into shape to get the package uploaded into the Debian
3101 <p
>Today we finally managed to get the package into shape and uploaded
3102 it into Debian, where it currently
3103 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
3104 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
3106 <p
>I guess you are wondering why on earth such tool would be useful
3107 for the common folks, ie those not running a large government
3108 surveillance system? Well, I plan to put it in a computer on my bike
3109 and in my car, tracking the cars nearby and allowing me to be notified
3110 when number plates on my watch list are discovered. Another use case
3111 was suggested by a friend of mine, who wanted to set it up at his home
3112 to open the car port automatically when it discovered the plate on his
3113 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3114 capable of placing his license plate number of a piece of cardboard to
3115 open his car port, men replied that it was always unlocked anyway. I
3116 guess for such use case it make sense. I am sure there are other use
3117 cases too, for those with imagination and a vision.
</p
>
3119 <p
>If you want to build your own version of the Debian package, check
3120 out the upstream git source and symlink ./distros/debian to ./debian/
3121 before running
"debuild
" to build the source. Or wait a bit until the
3122 package show up in unstable.
</p
>
3127 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
3128 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
3129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
3130 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
3131 <description><p
>Around three years ago, I created
3132 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
3133 system
</a
> to get a more practical solution in Debian for handing
3134 hardware related packages. A GUI system in the isenkram package will
3135 present a pop-up dialog when some hardware dongle supported by
3136 relevant packages in Debian is inserted into the machine. The same
3137 lookup mechanism to detect packages is available as command line
3138 tools in the isenkram-cli package. In addition to mapping hardware,
3139 it will also map kernel firmware files to packages and make it easy to
3140 install needed firmware packages automatically. The key for this
3141 system to work is a good way to map hardware to packages, in other
3142 words, allow packages to announce what hardware they will work
3145 <p
>I started by providing data files in the isenkram source, and
3146 adding code to download the latest version of these data files at run
3147 time, to ensure every user had the most up to date mapping available.
3148 I also added support for storing the mapping in the Packages file in
3149 the apt repositories, but did not push this approach because while I
3150 was trying to figure out how to best store hardware/package mappings,
3151 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
3152 appstream system
</a
> was announced. I got in touch and suggested to
3153 add the hardware mapping into that data set to be able to use
3154 appstream as a data source, and this was accepted at least for the
3155 Debian version of appstream.
</p
>
3157 <p
>A few days ago using appstream in Debian for this became possible,
3158 and today I uploaded a new version
0.20 of isenkram adding support for
3159 appstream as a data source for mapping hardware to packages. The only
3160 package so far using appstream to announce its hardware support is my
3161 pymissile package. I got help from Matthias Klumpp with figuring out
3162 how do add the required
3163 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
3164 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
3165 this content:
</p
>
3167 <blockquote
><pre
>
3168 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3169 &lt;component
&gt;
3170 &lt;id
&gt;pymissile
&lt;/id
&gt;
3171 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
3172 &lt;name
&gt;pymissile
&lt;/name
&gt;
3173 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
3174 &lt;description
&gt;
3176 Pymissile provides a curses interface to control an original
3177 Marks and Spencer / Striker USB Missile Launcher, as well as a
3178 motion control script to allow a webcamera to control the
3181 &lt;/description
&gt;
3182 &lt;provides
&gt;
3183 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
3184 &lt;/provides
&gt;
3185 &lt;/component
&gt;
3186 </pre
></blockquote
>
3188 <p
>The key for isenkram is the component/provides/modalias value,
3189 which is a glob style match rule for hardware specific strings
3190 (modalias strings) provided by the Linux kernel. In this case, it
3191 will map to all USB devices with vendor code
1130 and product code
3194 <p
>Note, it is important that the license of all the metadata files
3195 are compatible to have permissions to aggregate them into archive wide
3196 appstream files. Matthias suggested to use MIT or BSD licenses for
3197 these files. A challenge is figuring out a good id for the data, as
3198 it is supposed to be globally unique and shared across distributions
3199 (in other words, best to coordinate with upstream what to use). But
3200 it can be changed later or, so we went with the package name as
3201 upstream for this project is dormant.
</p
>
3203 <p
>To get the metadata file installed in the correct location for the
3204 mirror update scripts to pick it up and include its content the
3205 appstream data source, the file must be installed in the binary
3206 package under /usr/share/appdata/. I did this by adding the following
3207 line to debian/pymissile.install:
</p
>
3209 <blockquote
><pre
>
3210 debian/pymissile.metainfo.xml usr/share/appdata
3211 </pre
></blockquote
>
3213 <p
>With that in place, the command line tool isenkram-lookup will list
3214 all packages useful on the current computer automatically, and the GUI
3215 pop-up handler will propose to install the package not already
3216 installed if a hardware dongle is inserted into the machine in
3219 <p
>Details of the modalias field in appstream is available from the
3220 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
3222 <p
>To locate the modalias values of all hardware present in a machine,
3223 try running this command on the command line:
</p
>
3225 <blockquote
><pre
>
3226 cat $(find /sys/devices/|grep modalias)
3227 </pre
></blockquote
>
3229 <p
>To learn more about the isenkram system, please check out
3230 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3231 blog posts tagged isenkram
</a
>.
</p
>
3236 <title>The GNU General Public License is not magic pixie dust
</title>
3237 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
3238 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
3239 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
3240 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
3241 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
3242 GPL is not magic pixie dust
</a
>" explain the importance of making sure
3243 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
3244 I quote the blog post from Paul in full here with his permission:
<p
>
3248 <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
>
3251 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
3253 The first step is to choose a
3254 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
3257 The next step is, when someone fails to follow that copyleft license,
3258 <b
>it must be enforced
</b
><br/
>
3260 and its a simple fact of our modern society that such type of
3263 is incredibly expensive to do and incredibly difficult to do.
3266 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
3267 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
3268 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
3269 0x57</a
></small
></p
>
3271 <p
>As the Debian Website
3272 <a href=
"https://bugs.debian.org/
794116">used
</a
>
3273 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
3274 imply, public domain and permissively licensed software can lead to
3275 the production of more proprietary software as people discover useful
3276 software, extend it and or incorporate it into their hardware or
3277 software products. Copyleft licenses such as the GNU GPL were created
3278 to close off this avenue to the production of proprietary software but
3279 such licenses are not enough. With the ongoing adoption of Free
3280 Software by individuals and groups, inevitably the community
's
3281 expectations of license compliance are violated, usually out of
3282 ignorance of the way Free Software works, but not always. As Karen
3283 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
3284 Freedom
">FaiF
</a
>
3285 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
3286 copyleft is nothing if no-one is willing and able to stand up in court
3287 to protect it. The reality of today
's world is that legal
3288 representation is expensive, difficult and time consuming. With
3289 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
3290 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
3291 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
3292 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
3293 of the Linux project, Debian and other groups against GPL violations.
3294 In March the SFC supported a
3295 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
3296 by Christoph Hellwig
</a
> against VMware for refusing to
3297 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
3298 with the GPL
</a
> in relation to their use of parts of the Linux
3299 kernel. Since then two of their sponsors pulled corporate funding and
3301 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
3302 or cancelled their talks
</a
>. As a result they have decided to rely
3303 less on corporate funding and more on the broad community of
3304 individuals who support Free Software and copyleft. So the SFC has
3305 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
3306 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
3307 a community of folks who stand up for copyleft and the GPL by
3308 supporting their work on promoting and supporting copyleft and Free
3311 <p
>If you support Free Software,
3312 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
3313 what the SFC do, agree with their
3314 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
3315 principles
</a
>, are happy about their
3316 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
3317 work on a project that is an SFC
3318 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
3319 just want to stand up for copyleft, please join
3320 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
3321 Allan Webber
</a
>,
3322 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
3324 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
3325 Bacon
</a
>, myself and
3326 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
3328 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
3329 next week your donation will be
3330 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
3331 by an anonymous donor. Please also consider asking your employer to
3332 match your donation or become a sponsor of SFC. Don
't forget to
3333 spread the word about your support for SFC via email, your blog and or
3334 social media accounts.
</p
>
3338 <p
>I agree with Paul on this topic and just signed up as a Supporter
3339 of Software Freedom Conservancy myself. Perhaps you should be a
3340 supporter too?
</p
>
3345 <title>PGP key transition statement for key EE4E02F9
</title>
3346 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
3347 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
3348 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
3349 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
3350 set it up properly. I wanted to generate it offline and have it
3351 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
3352 smart card
</a
> for daily use, and learning how to do it and finding
3353 time to sit down with an offline machine almost took forever. But
3354 finally I
've been able to complete the process, and have now moved
3355 from my old GPG key to a new GPG key. See
3356 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
3357 full transition statement, signed with both my old and new key
</a
> for
3358 the details. This is my new key:
</p
>
3361 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
3362 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
3363 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
3364 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
3365 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
3366 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
3367 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
3370 <p
>The key can be downloaded from the OpenPGP key servers, signed by
3371 my old key.
</p
>
3373 <p
>If you signed my old key
3374 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
3375 I
'd very much appreciate a signature on my new key, details and
3376 instructions in the transition statement. I m happy to reciprocate if
3377 you have a similarly signed transition statement to present.
</p
>
3382 <title>The life and death of a laptop battery
</title>
3383 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
3384 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
3385 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
3386 <description><p
>When I get a new laptop, the battery life time at the start is OK.
3387 But this do not last. The last few laptops gave me a feeling that
3388 within a year, the life time is just a fraction of what it used to be,
3389 and it slowly become painful to use the laptop without power connected
3390 all the time. Because of this, when I got a new Thinkpad X230 laptop
3391 about two years ago, I decided to monitor its battery state to have
3392 more hard facts when the battery started to fail.
</p
>
3394 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
3396 <p
>First I tried to find a sensible Debian package to record the
3397 battery status, assuming that this must be a problem already handled
3398 by someone else. I found
3399 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
3400 which collects statistics from the battery, but it was completely
3401 broken. I sent a few suggestions to the maintainer, but decided to
3402 write my own collector as a shell script while I waited for feedback
3404 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3405 blog post about the battery development on a MacBook Air
</a
> I also
3407 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3408 available in Debian.
</p
>
3410 <p
>I started my collector
2013-
07-
15, and it has been collecting
3411 battery stats ever since. Now my
3412 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3413 measurements, from the time the battery was working great until now,
3414 when it is unable to charge above
7% of original capacity. My
3415 collector shell script is quite simple and look like this:
</p
>
3420 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3422 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3423 logfile=/var/log/hjemmenett-battery-status.log
3425 files=
"manufacturer model_name technology serial_number \
3426 energy_full energy_full_design energy_now cycle_count status
"
3428 if [ ! -e
"$logfile
" ] ; then
3430 printf
"timestamp,
"
3432 printf
"%s,
" $f
3435 )
> "$logfile
"
3439 # Print complete message in one echo call, to avoid race condition
3440 # when several log processes run in parallel.
3441 msg=$(printf
"%s,
" $(date +%s); \
3442 for f in $files; do \
3443 printf
"%s,
" $(cat $f); \
3445 echo
"$msg
"
3448 cd /sys/class/power_supply
3451 (cd $bat
&& log_battery
>> "$logfile
")
3455 <p
>The script is called when the power management system detect a
3456 change in the power status (power plug in or out), and when going into
3457 and out of hibernation and suspend. In addition, it collect a value
3458 every
10 minutes. This make it possible for me know when the battery
3459 is discharging, charging and how the maximum charge change over time.
3460 The code for the Debian package
3461 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3462 available on github
</a
>.
</p
>
3464 <p
>The collected log file look like this:
</p
>
3467 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3468 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3470 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3471 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3474 <p
>I wrote a small script to create a graph of the charge development
3475 over time. This graph depicted above show the slow death of my laptop
3478 <p
>But why is this happening? Why are my laptop batteries always
3479 dying in a year or two, while the batteries of space probes and
3480 satellites keep working year after year. If we are to believe
3481 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3482 University
</a
>, the cause is me charging the battery whenever I have a
3483 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3484 all the time, but to stay below
90% of full charge most of the time.
3485 I
've been told that the Tesla electric cars
3486 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3487 the charge of their batteries to
80%
</a
>, with the option to charge to
3488 100% when preparing for a longer trip (not that I would want a car
3489 like Tesla where rights to privacy is abandoned, but that is another
3490 story), which I guess is the option we should have for laptops on
3491 Linux too.
</p
>
3493 <p
>Is there a good and generic way with Linux to tell the battery to
3494 stop charging at
80%, unless requested to charge to
100% once in
3495 preparation for a longer trip? I found
3496 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3497 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3498 80%
</a
>, but could not get it to work (kernel module refused to
3501 <p
>I wonder why the battery capacity was reported to be more than
100%
3502 at the start. I also wonder why the
"full capacity
" increases some
3503 times, and if it is possible to repeat the process to get the battery
3504 back to design capacity. And I wonder if the discharge and charge
3505 speed change over time, or if this stay the same. I did not yet try
3506 to write a tool to calculate the derivative values of the battery
3507 level, but suspect some interesting insights might be learned from
3510 <p
>Update
2015-
09-
24: I got a tip to install the packages
3511 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3512 packages instead of the tp-smapi-dkms package I had tried to use
3513 initially, and use
'tlp setcharge
40 80' to change when charging start
3514 and stop. I
've done so now, but expect my existing battery is toast
3515 and need to be replaced. The proposal is unfortunately Thinkpad
3521 <title>New laptop - some more clues and ideas based on feedback
</title>
3522 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3523 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3524 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3525 <description><p
>Several people contacted me after my previous blog post about my
3526 need for a new laptop, and provided very useful feedback. I wish to
3527 thank every one of these. Several pointed me to the possibility of
3528 fixing my X230, and I am already in the process of getting Lenovo to
3529 do so thanks to the on site, next day support contract covering the
3530 machine. But the battery is almost useless (I expect to replace it
3531 with a non-official battery) and I do not expect the machine to live
3532 for many more years, so it is time to plan its replacement. If I did
3533 not have a support contract, it was suggested to find replacement parts
3534 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3535 might present a language barrier as I do not understand French.
</p
>
3537 <p
>One tip I got was to use the
3538 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3539 compare laptop models. It seem to have more models available than
3540 prisjakt.no. Another tip I got from someone I know have similar
3541 keyboard preferences was that the HP EliteBook
840 keyboard is not
3542 very good, and this matches my experience with earlier EliteBook
3543 keyboards I tested. Because of this, I will not consider it any further.
3545 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3546 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3547 (which is missing from the X240), and is working fairly well with
3548 Debian Sid/Unstable according to
3549 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3550 got on the keyboard quality are not consistent. Some say the keyboard
3551 is good, others say it is ok, while others say it is not very good.
3552 Those with experience from X41 and and X60 agree that the X250
3553 keyboard is not as good as those trusty old laptops, and suggest I
3554 keep and fix my X230 instead of upgrading, or get a used X230 to
3555 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3556 activity and battery status, which is very convenient on my X230. I
'm
3557 also told that the CPU fan is running very often, making it a bit
3558 noisy. In any case, the X250 do not work out of the box with Debian
3559 Stable/Jessie, one of my requirements.
</p
>
3561 <p
>I have also gotten a few vendor proposals, one was
3562 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3563 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3564 The latter look very attractive to me.
</p
>
3566 <p
>Again, thank you all for the very useful feedback. It help a lot
3567 as I keep looking for a replacement.
</p
>
3569 <p
>Update
2015-
07-
06: I was recommended to check out the
3570 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3572 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3573 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3578 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3579 <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>
3580 <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>
3581 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3582 <description><p
>My primary work horse laptop is failing, and will need a
3583 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3584 started flickering yesterday, and I suspect the cause is a broken
3585 cable, as changing the angle of the screen some times get rid of the
3586 flickering.
</p
>
3588 <p
>My requirements have not really changed since I bought it, and is
3590 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3591 described them in
2013</a
>. The last time I bought a laptop, I had
3593 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3594 where I could select at least a few of the requirements (mouse pin,
3595 wifi, weight) and go through the rest manually. Three button mouse
3596 and a good keyboard is not available as an option, and all the three
3597 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3598 G2) lack three mouse buttons). It is also unclear to me how good the
3599 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3600 the keyboard, even if the quality and robustness in the X series have
3601 deteriorated since X41.
</p
>
3603 <p
>I wonder how I can find a sensible laptop when none of the options
3604 seem sensible to me? Are there better services around to search the
3605 set of available laptops for features? Please send me an email if you
3606 have suggestions.
</p
>
3608 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3609 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3610 of endorsed hardware
</a
>, which is useful background information.
</p
>
3615 <title>How to stay with sysvinit in Debian Jessie
</title>
3616 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3618 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3619 <description><p
>By now, it is well known that Debian Jessie will not be using
3620 sysvinit as its boot system by default. But how can one keep using
3621 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3623 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3624 Schubert
</a
> and
3625 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3628 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3629 keep sysvinit as your boot system, create a file
3630 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3631 you upgrade:
</p
>
3633 <p
><blockquote
><pre
>
3634 Package: systemd-sysv
3635 Pin: release o=Debian
3637 </pre
></blockquote
><p
>
3639 <p
>This file content will tell apt and aptitude to not consider
3640 installing systemd-sysv as part of any installation and upgrade
3641 solution when resolving dependencies, and thus tell it to avoid
3642 systemd as a default boot system. The end result should be that the
3643 upgraded system keep using sysvinit.
</p
>
3645 <p
>If you are installing Jessie for the first time, there is no way to
3646 get sysvinit installed by default (debootstrap used by
3647 debian-installer have no option for this), but one can tell the
3648 installer to switch to sysvinit before the first boot. Either by
3649 using a kernel argument to the installer, or by adding a line to the
3650 preseed file used. First, the kernel command line argument:
3652 <p
><blockquote
><pre
>
3653 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3654 </pre
></blockquote
><p
>
3656 <p
>Next, the line to use in a preseed file:
</p
>
3658 <p
><blockquote
><pre
>
3659 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3660 </pre
></blockquote
><p
>
3662 <p
>One can of course also do this after the first boot by installing
3663 the sysvinit-core package.
</p
>
3665 <p
>I recommend only using sysvinit if you really need it, as the
3666 sysvinit boot sequence in Debian have several hardware specific bugs
3667 on Linux caused by the fact that it is unpredictable when hardware
3668 devices show up during boot. But on the other hand, the new default
3669 boot system still have a few rough edges I hope will be fixed before
3670 Jessie is released.
</p
>
3672 <p
>Update
2014-
11-
26: Inspired by
3673 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3674 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3680 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3681 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3682 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3683 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3684 <description><p
>The right to communicate with your friends and family in private,
3685 without anyone snooping, is a right every citicen have in a liberal
3686 democracy. But this right is under serious attack these days.
</p
>
3688 <p
>A while back it occurred to me that one way to make the dragnet
3689 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3690 the whisleblower Snowden) more expensive for Internet email,
3691 is to deliver all email using SMTP via Tor. Such SMTP option would be
3692 a nice addition to the FreedomBox project if we could send email
3693 between FreedomBox machines without leaking metadata about the emails
3694 to the people peeking on the wire. I
3695 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3696 this on the FreedomBox project mailing list in October
</a
> and got a
3697 lot of useful feedback and suggestions. It also became obvious to me
3698 that this was not a novel idea, as the same idea was tested and
3699 documented by Johannes Berg as early as
2006, and both
3700 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3701 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3702 propose a similar method / protocol to pass emails between users.
</p
>
3704 <p
>To implement such system one need to set up a Tor hidden service
3705 providing the SMTP protocol on port
25, and use email addresses
3706 looking like username@hidden-service-name.onion. With such addresses
3707 the connections to port
25 on hidden-service-name.onion using Tor will
3708 go to the correct SMTP server. To do this, one need to configure the
3709 Tor daemon to provide the hidden service and the mail server to accept
3710 emails for this .onion domain. To learn more about Exim configuration
3711 in Debian and test the design provided by Johannes Berg in his FAQ, I
3712 set out yesterday to create a Debian package for making it trivial to
3713 set up such SMTP over Tor service based on Debian. Getting it to work
3714 were fairly easy, and
3715 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3716 source code for the Debian package
</a
> is available from github. I
3717 plan to move it into Debian if further testing prove this to be a
3718 useful approach.
</p
>
3720 <p
>If you want to test this, set up a blank Debian machine without any
3721 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3722 get rid of exim4). Install tor, clone the git repository mentioned
3723 above, build the deb and install it on the machine. Next, run
3724 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3725 the instructions to get the service up and running. Restart tor and
3726 exim when it is done, and test mail delivery using swaks like
3729 <p
><blockquote
><pre
>
3730 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3731 --to fbx@dutlqrrmjhtfa3vp.onion
3732 </pre
></blockquote
></p
>
3734 <p
>This will test the SMTP delivery using tor. Replace the email
3735 address with your own address to test your server. :)
</p
>
3737 <p
>The setup procedure is still to complex, and I hope it can be made
3738 easier and more automatic. Especially the tor setup need more work.
3739 Also, the package include a tor-smtp tool written in C, but its task
3740 should probably be rewritten in some script language to make the deb
3741 architecture independent. It would probably also make the code easier
3742 to review. The tor-smtp tool currently need to listen on a socket for
3743 exim to talk to it and is started using xinetd. It would be better if
3744 no daemon and no socket is needed. I suspect it is possible to get
3745 exim to run a command line tool for delivery instead of talking to a
3746 socket, and hope to figure out how in a future version of this
3749 <p
>Until I wipe my test machine, I can be reached using the
3750 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3751 SMTorP. :)
</p
>
3756 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3757 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3758 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3759 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3760 <description><p
>If you ever had to moderate a mailman list, like the ones on
3761 alioth.debian.org, you know the web interface is fairly slow to
3762 operate. First you visit one web page, enter the moderation password
3763 and get a new page shown with a list of all the messages to moderate
3764 and various options for each email address. This take a while for
3765 every list you moderate, and you need to do it regularly to do a good
3766 job as a list moderator. But there is a quick alternative,
3767 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3768 listadmin program
</a
>. It allow you to check lists for new messages
3769 to moderate in a fraction of a second. Here is a test run on two
3770 lists I recently took over:
</p
>
3772 <p
><blockquote
><pre
>
3773 % time listadmin xiph
3774 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3775 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3781 </pre
></blockquote
></p
>
3783 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3784 there are no message in the moderation queue. Every morning I
3785 currently moderate
68 mailman lists, and it normally take around two
3786 minutes. When I took over the two pkg-xiph lists above a few days
3787 ago, there were
400 emails waiting in the moderator queue. It took me
3788 less than
15 minutes to process them all using the listadmin
3791 <p
>If you install
3792 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3793 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3794 with content like this, the moderation task is a breeze:
</p
>
3796 <p
><blockquote
><pre
>
3797 username username@example.org
3800 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3803 adminurl https://{domain}/mailman/admindb/{list}
3804 mailman-list@lists.example.com
3807 other-list@otherserver.example.org
3808 </pre
></blockquote
></p
>
3810 <p
>There are other options to set as well. Check the manual page to
3811 learn the details.
</p
>
3813 <p
>If you are forced to moderate lists on a mailman installation where
3814 the SSL certificate is self signed or not properly signed by a
3815 generally accepted signing authority, you can set a environment
3816 variable when calling listadmin to disable SSL verification:
</p
>
3818 <p
><blockquote
><pre
>
3819 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3820 </pre
></blockquote
></p
>
3822 <p
>If you want to moderate a subset of the lists you take care of, you
3823 can provide an argument to the listadmin script like I do in the
3824 initial screen dump (the xiph argument). Using an argument, only
3825 lists matching the argument string will be processed. This make it
3826 quick to accept messages if you notice the moderation request in your
3829 <p
>Without the listadmin program, I would never be the moderator of
68
3830 mailing lists, as I simply do not have time to spend on that if the
3831 process was any slower. The listadmin program have saved me hours of
3832 time I could spend elsewhere over the years. It truly is nice free
3835 <p
>As usual, if you use Bitcoin and want to show your support of my
3836 activities, please send Bitcoin donations to my address
3837 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3839 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
3840 configuration example. Also, I
've been told that the
3841 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
3847 <title>Debian Jessie, PXE and automatic firmware installation
</title>
3848 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
3849 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
3850 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
3851 <description><p
>When PXE installing laptops with Debian, I often run into the
3852 problem that the WiFi card require some firmware to work properly.
3853 And it has been a pain to fix this using preseeding in Debian.
3854 Normally something more is needed. But thanks to
3855 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
3856 package
</a
> and its recent tasksel extension, it has now become easy
3857 to do this using simple preseeding.
</p
>
3859 <p
>The isenkram-cli package provide tasksel tasks which will install
3860 firmware for the hardware found in the machine (actually, requested by
3861 the kernel modules for the hardware). (It can also install user space
3862 programs supporting the hardware detected, but that is not the focus
3863 of this story.)
</p
>
3865 <p
>To get this working in the default installation, two preeseding
3866 values are needed. First, the isenkram-cli package must be installed
3867 into the target chroot (aka the hard drive) before tasksel is executed
3868 in the pkgsel step of the debian-installer system. This is done by
3869 preseeding the base-installer/includes debconf value to include the
3870 isenkram-cli package. The package name is next passed to debootstrap
3871 for installation. With the isenkram-cli package in place, tasksel
3872 will automatically use the isenkram tasks to detect hardware specific
3873 packages for the machine being installed and install them, because
3874 isenkram-cli contain tasksel tasks.
</p
>
3876 <p
>Second, one need to enable the non-free APT repository, because
3877 most firmware unfortunately is non-free. This is done by preseeding
3878 the apt-mirror-setup step. This is unfortunate, but for a lot of
3879 hardware it is the only option in Debian.
</p
>
3881 <p
>The end result is two lines needed in your preseeding file to get
3882 firmware installed automatically by the installer:
</p
>
3884 <p
><blockquote
><pre
>
3885 base-installer base-installer/includes string isenkram-cli
3886 apt-mirror-setup apt-setup/non-free boolean true
3887 </pre
></blockquote
></p
>
3889 <p
>The current version of isenkram-cli in testing/jessie will install
3890 both firmware and user space packages when using this method. It also
3891 do not work well, so use version
0.15 or later. Installing both
3892 firmware and user space packages might give you a bit more than you
3893 want, so I decided to split the tasksel task in two, one for firmware
3894 and one for user space programs. The firmware task is enabled by
3895 default, while the one for user space programs is not. This split is
3896 implemented in the package currently in unstable.
</p
>
3898 <p
>If you decide to give this a go, please let me know (via email) how
3899 this recipe work for you. :)
</p
>
3901 <p
>So, I bet you are wondering, how can this work. First and
3902 foremost, it work because tasksel is modular, and driven by whatever
3903 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3904 isenkram-cli package place two files for tasksel to find. First there
3905 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3907 <p
><blockquote
><pre
>
3908 Task: isenkram-packages
3910 Description: Hardware specific packages (autodetected by isenkram)
3911 Based on the detected hardware various hardware specific packages are
3913 Test-new-install: show show
3915 Packages: for-current-hardware
3917 Task: isenkram-firmware
3919 Description: Hardware specific firmware packages (autodetected by isenkram)
3920 Based on the detected hardware various hardware specific firmware
3921 packages are proposed.
3922 Test-new-install: mark show
3924 Packages: for-current-hardware-firmware
3925 </pre
></blockquote
></p
>
3927 <p
>The key parts are Test-new-install which indicate how the task
3928 should be handled and the Packages line referencing to a script in
3929 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3930 list of packages to install. The for-current-hardware-firmware script
3931 look like this to list relevant firmware for the machine:
3933 <p
><blockquote
><pre
>
3936 PATH=/usr/sbin:$PATH
3938 isenkram-autoinstall-firmware -l
3939 </pre
></blockquote
></p
>
3941 <p
>With those two pieces in place, the firmware is installed by
3942 tasksel during the normal d-i run. :)
</p
>
3944 <p
>If you want to test what tasksel will install when isenkram-cli is
3945 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3946 --new-install
</tt
> to get the list of packages that tasksel would
3949 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3950 pilots in testing this feature, as isenkram is used there now to
3951 install firmware, replacing the earlier scripts.
</p
>
3956 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3957 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3958 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3959 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3960 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3961 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3962 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3963 on a screen normally showing the bread types and prizes:
</p
>
3965 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3967 <p
>If it had booted as it was supposed to, I would never had known
3968 about this hidden Linux installation. It is interesting what
3969 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3974 <title>New lsdvd release version
0.17 is ready
</title>
3975 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3976 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3977 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3978 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3979 got a new set of developers a few weeks ago, after the original
3980 developer decided to step down and pass the project to fresh blood.
3981 This project is now maintained by Petter Reinholdtsen and Steve
3984 <p
>I just wrapped up
3985 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3986 new lsdvd release
</a
>, available in git or from
3987 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3988 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3993 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3994 <li
>Check for garbage in the program chains, which indicate that a track is
3995 non-existant, to work around additional copy protection
</li
>
3996 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3997 <li
>Fix pallete display of first entry
</li
>
3998 <li
>Fix include orders
</li
>
3999 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
4000 <li
>Fix the chapter count
</li
>
4001 <li
>Make sure the array size and the array limit used when initialising
4002 the palette size is the same.
</li
>
4003 <li
>Fix array printing.
</li
>
4004 <li
>Correct subsecond calculations.
</li
>
4005 <li
>Add sector information to the output format.
</li
>
4006 <li
>Clean up code to be closer to ANSI C and compile without warnings
4007 with more GCC compiler warnings.
</li
>
4011 <p
>This change bring together patches for lsdvd in use in various
4012 Linux and Unix distributions, as well as patches submitted to the
4013 project the last nine years. Please check it out. :)
</p
>
4018 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
4019 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
4020 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
4021 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
4022 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4023 project
</a
> provide a Linux solution for schools, including a
4024 powerful desktop with education software, a central server providing
4025 web pages, user database, user home directories, central login and PXE
4026 boot of both clients without disk and the installation to install Debian
4027 Edu on machines with disk (and a few other services perhaps to small
4028 to mention here). We in the Debian Edu team are currently working on
4029 the Jessie based version, trying to get everything in shape before the
4030 freeze, to avoid having to maintain our own package repository in the
4032 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
4033 status
</a
> can be seen on the Debian wiki, and there is still heaps of
4034 work left. Some fatal problems block testing, breaking the installer,
4035 but it is possible to work around these to get anyway. Here is a
4036 recipe on how to get the installation limping along.
</p
>
4038 <p
>First, download the test ISO via
4039 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
4040 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
4042 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
4043 The ISO build was broken on Tuesday, so we do not get a new ISO every
4044 12 hours or so, but thankfully the ISO we already got we are able to
4045 install with some tweaking.
</p
>
4047 <p
>When you get to the Debian Edu profile question, go to tty2
4048 (use Alt-Ctrl-F2), run
</p
>
4050 <p
><blockquote
><pre
>
4051 nano /usr/bin/edu-eatmydata-install
4052 </pre
></blockquote
></p
>
4054 <p
>and add
'exit
0' as the second line, disabling the eatmydata
4055 optimization. Return to the installation, select the profile you want
4056 and continue. Without this change, exim4-config will fail to install
4057 due to a known bug in eatmydata.
</p
>
4059 <p
>When you get the grub question at the end, answer /dev/sda (or if
4060 this do not work, figure out what your correct value would be. All my
4061 test machines need /dev/sda, so I have no advice if it do not fit
4062 your need.
</p
>
4064 <p
>If you installed a profile including a graphical desktop, log in as
4065 root after the initial boot from hard drive, and install the
4066 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4067 or mate. If you want several desktop options, install more than one
4068 metapackage. Once this is done, reboot and you should have a working
4069 graphical login screen. This workaround should no longer be needed
4070 once the education-tasks package version
1.801 enter testing in two
4073 <p
>I believe the ISO build will start working on two days when the new
4074 tasksel package enter testing and Steve McIntyre get a chance to
4075 update the debian-cd git repository. The eatmydata, grub and desktop
4076 issues are already fixed in unstable and testing, and should show up
4077 on the ISO as soon as the ISO build start working again. Well the
4078 eatmydata optimization is really just disabled. The proper fix
4079 require an upload by the eatmydata maintainer applying the patch
4080 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
4081 The rest have proper fixes in unstable.
</p
>
4083 <p
>I hope this get you going with the installation testing, as we are
4084 quickly running out of time trying to get our Jessie based
4085 installation ready before the distribution freeze in a month.
</p
>
4090 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
4091 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
4092 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
4093 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
4094 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
4095 to handle my fairly large DVD collection. It is a nice command line
4096 tool to get details about a DVD, like title, tracks, track length,
4097 etc, in XML, Perl or human readable format. But lsdvd have not seen
4098 any new development since
2006 and had a few irritating bugs affecting
4099 its use with some DVDs. Upstream seemed to be dead, and in January I
4100 sent a small probe asking for a version control repository for the
4101 project, without any reply. But I use it regularly and would like to
4102 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
4103 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
4104 the project admin, and after getting a reply from him explaining that
4105 he was no longer interested in the project, I asked if I could take
4106 over. And yesterday, I became project admin.
</p
>
4108 <p
>I
've been in touch with a Gentoo developer and the Debian
4109 maintainer interested in joining forces to maintain the upstream
4110 project, and I hope we can get a new release out fairly quickly,
4111 collecting the patches spread around on the internet into on place.
4112 I
've added the relevant Debian patches to the freshly created git
4113 repository, and expect the Gentoo patches to make it too. If you got
4114 a DVD collection and care about command line tools, check out
4115 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
4116 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
4117 list
</a
>. :)
</p
>
4122 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
4123 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
4124 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
4125 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
4126 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
4127 a lot quicker. When we install more than
2000 packages in
4128 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
4129 tasksel in the installer, unpacking the binary packages take forever.
4130 A part of the slow I/O issue was discussed in
4131 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
4132 much file system sync-ing done by dpkg, which is the package
4133 responsible for unpacking the binary packages. Other parts (like code
4134 executed by postinst scripts) might also sync to disk during
4135 installation. All this sync-ing to disk do not really make sense to
4136 me. If the machine crash half-way through, I start over, I do not try
4137 to salvage the half installed system. So the failure sync-ing is
4138 supposed to protect against, hardware or system crash, is not really
4139 relevant while the installer is running.
</p
>
4141 <p
>A few days ago, I thought of a way to get rid of all the file
4142 system sync()-ing in a fairly non-intrusive way, without the need to
4143 change the code in several packages. The idea is not new, but I have
4144 not heard anyone propose the approach using dpkg-divert before. It
4145 depend on the small and clever package
4146 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
4147 uses LD_PRELOAD to replace the system functions for syncing data to
4148 disk with functions doing nothing, thus allowing programs to live
4149 dangerous while speeding up disk I/O significantly. Instead of
4150 modifying the implementation of dpkg, apt and tasksel (which are the
4151 packages responsible for selecting, fetching and installing packages),
4152 it occurred to me that we could just divert the programs away, replace
4153 them with a simple shell wrapper calling
4154 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
4155 Two days ago I decided to test the idea, and wrapped up a simple
4156 implementation for the Debian Edu udeb.
</p
>
4158 <p
>The effect was stunning. In my first test it reduced the running
4159 time of the pkgsel step (installing tasks) from
64 to less than
44
4160 minutes (
20 minutes shaved off the installation) on an old Dell
4161 Latitude D505 machine. I am not quite sure what the optimised time
4162 would have been, as I messed up the testing a bit, causing the debconf
4163 priority to get low enough for two questions to pop up during
4164 installation. As soon as I saw the questions I moved the installation
4165 along, but do not know how long the question were holding up the
4166 installation. I did some more measurements using Debian Edu Jessie,
4167 and got these results. The time measured is the time stamp in
4168 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
4169 "pkgsel: finishing up
" lines, if you want to do the same measurement
4170 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4171 timing thus do not depend on how quickly the user handle the tasksel
4174 <p
><table
>
4177 <th
>Machine/setup
</th
>
4178 <th
>Original tasksel
</th
>
4179 <th
>Optimised tasksel
</th
>
4180 <th
>Reduction
</th
>
4184 <td
>Latitude D505 Main+LTSP LXDE
</td
>
4185 <td
>64 min (
07:
46-
08:
50)
</td
>
4186 <td
><44 min (
11:
27-
12:
11)
</td
>
4187 <td
>>20 min
18%
</td
>
4191 <td
>Latitude D505 Roaming LXDE
</td
>
4192 <td
>57 min (
08:
48-
09:
45)
</td
>
4193 <td
>34 min (
07:
43-
08:
17)
</td
>
4194 <td
>23 min
40%
</td
>
4198 <td
>Latitude D505 Minimal
</td
>
4199 <td
>22 min (
10:
37-
10:
59)
</td
>
4200 <td
>11 min (
11:
16-
11:
27)
</td
>
4201 <td
>11 min
50%
</td
>
4205 <td
>Thinkpad X200 Minimal
</td
>
4206 <td
>6 min (
08:
19-
08:
25)
</td
>
4207 <td
>4 min (
08:
04-
08:
08)
</td
>
4208 <td
>2 min
33%
</td
>
4212 <td
>Thinkpad X200 Roaming KDE
</td
>
4213 <td
>19 min (
09:
21-
09:
40)
</td
>
4214 <td
>15 min (
10:
25-
10:
40)
</td
>
4215 <td
>4 min
21%
</td
>
4218 </table
></p
>
4220 <p
>The test is done using a netinst ISO on a USB stick, so some of the
4221 time is spent downloading packages. The connection to the Internet
4222 was
100Mbit/s during testing, so downloading should not be a
4223 significant factor in the measurement. Download typically took a few
4224 seconds to a few minutes, depending on the amount of packages being
4225 installed.
</p
>
4227 <p
>The speedup is implemented by using two hooks in
4228 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
4229 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
4230 finish-install.d hook to remove the divert at the end of the
4231 installation. I picked the pre-pkgsel.d hook instead of the
4232 post-base-installer.d hook because I test using an ISO without the
4233 eatmydata package included, and the post-base-installer.d hook in
4234 Debian Edu can only operate on packages included in the ISO. The
4235 negative effect of this is that I am unable to activate this
4236 optimization for the kernel installation step in d-i. If the code is
4237 moved to the post-base-installer.d hook, the speedup would be larger
4238 for the entire installation.
</p
>
4240 <p
>I
've implemented this in the
4241 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
4242 git repository, and plan to provide the optimization as part of the
4243 Debian Edu installation. If you want to test this yourself, you can
4244 create two files in the installer (or in an udeb). One shell script
4245 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
4247 <p
><blockquote
><pre
>
4250 . /usr/share/debconf/confmodule
4252 logger -t my-pkgsel
"info: $*
"
4255 logger -t my-pkgsel
"error: $*
"
4257 override_install() {
4258 apt-install eatmydata || true
4259 if [ -x /target/usr/bin/eatmydata ] ; then
4260 for bin in dpkg apt-get aptitude tasksel ; do
4262 # Test that the file exist and have not been diverted already.
4263 if [ -f /target$file ] ; then
4264 info
"diverting $file using eatmydata
"
4265 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
4266 > /target$file.edu
4267 chmod
755 /target$file.edu
4268 in-target dpkg-divert --package debian-edu-config \
4269 --rename --quiet --add $file
4270 ln -sf ./$bin.edu /target$file
4272 error
"unable to divert $file, as it is missing.
"
4276 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
4281 </pre
></blockquote
></p
>
4283 <p
>To clean up, another shell script should go into
4284 /usr/lib/finish-install.d/ with code like this:
4286 <p
><blockquote
><pre
>
4288 . /usr/share/debconf/confmodule
4290 logger -t my-finish-install
"error: $@
"
4292 remove_install_override() {
4293 for bin in dpkg apt-get aptitude tasksel ; do
4295 if [ -x /target$file.edu ] ; then
4297 in-target dpkg-divert --package debian-edu-config \
4298 --rename --quiet --remove $file
4301 error
"Missing divert for $file.
"
4304 sync # Flush file buffers before continuing
4307 remove_install_override
4308 </pre
></blockquote
></p
>
4310 <p
>In Debian Edu, I placed both code fragments in a separate script
4311 edu-eatmydata-install and call it from the pre-pkgsel.d and
4312 finish-install.d scripts.
</p
>
4314 <p
>By now you might ask if this change should get into the normal
4315 Debian installer too? I suspect it should, but am not sure the
4316 current debian-installer coordinators find it useful enough. It also
4317 depend on the side effects of the change. I
'm not aware of any, but I
4318 guess we will see if the change is safe after some more testing.
4319 Perhaps there is some package in Debian depending on sync() and
4320 fsync() having effect? Perhaps it should go into its own udeb, to
4321 allow those of us wanting to enable it to do so without affecting
4324 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
4325 will break installation of all programs using gnutls because of
4326 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
4327 eatmydata package in Debian will solve it.
</p
>
4329 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
4330 the optimization work again. And I have discovered that the
4331 dpkg-divert trick is not really needed and implemented a slightly
4332 simpler approach as part of the debian-edu-install package. See
4333 tools/edu-eatmydata-install in the source package.
</p
>
4335 <p
>Update
2014-
11-
11: Unfortunately, a new
4336 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
4337 triggering on i386 made it into testing, and broke this installation
4338 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
4339 request
768893</a
> is accepted, it should be working again.
</p
>
4344 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
4345 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
4346 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
4347 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
4348 <description><p
>Yesterday, I had the pleasure of attending a talk with the
4349 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
4350 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
4351 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
4352 learn that there is a large set of publicly available key servers to
4353 use when looking for peoples public key. So far I have used
4354 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4355 were misbehaving, but those days are ended. The servers I have used
4356 up until yesterday have been slow and some times unavailable. I hope
4357 those problems are gone now.
</p
>
4359 <p
>Behind the round robin DNS entry of the
4360 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
4361 there is a pool of more than
100 keyservers which are checked every
4362 day to ensure they are well connected and up to date. It must be
4363 better than what I have used so far. :)
</p
>
4365 <p
>Yesterdays speaker told me that the service is the default
4366 keyserver provided by the default configuration in GnuPG, but this do
4367 not seem to be used in Debian. Perhaps it should?
</p
>
4369 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
4372 <p
><blockquote
><pre
>
4373 keyserver pool.sks-keyservers.net
4374 </pre
></blockquote
></p
>
4376 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
4377 entries in DNS. Just for fun, I did just that at work, so now every
4378 user of GnuPG at the University of Oslo should find a OpenGPG
4379 keyserver automatically should their need it:
</p
>
4381 <p
><blockquote
><pre
>
4382 % host -t srv _pgpkey-http._tcp.uio.no
4383 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
4385 </pre
></blockquote
></p
>
4387 <p
>Now if only
4388 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
4389 HKP lookup protocol
</a
> supported finding signature paths, I would be
4390 very happy. It can look up a given key or search for a user ID, but I
4391 normally do not want that, but to find a trust path from my key to
4392 another key. Given a user ID or key ID, I would like to find (and
4393 download) the keys representing a signature path from my key to the
4394 key in question, to be able to get a trust path between the two keys.
4395 This is as far as I can tell not possible today. Perhaps something
4396 for a future version of the protocol?
</p
>
4401 <title>From English wiki to translated PDF and epub via Docbook
</title>
4402 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
4403 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
4404 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4405 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4406 project
</a
> provide an instruction manual for teachers, system
4407 administrators and other users that contain useful tips for setting up
4408 and maintaining a Debian Edu installation. This text is about how the
4409 text processing of this manual is handled in the project.
</p
>
4411 <p
>One goal of the project is to provide information in the native
4412 language of its users, and for this we need to handle translations.
4413 But we also want to make sure each language contain the same
4414 information, so for this we need a good way to keep the translations
4415 in sync. And we want it to be easy for our users to improve the
4416 documentation, avoiding the need to learn special formats or tools to
4417 contribute, and the obvious way to do this is to make it possible to
4418 edit the documentation using a web browser. We also want it to be
4419 easy for translators to keep the translation up to date, and give them
4420 help in figuring out what need to be translated. Here is the list of
4421 tools and the process we have found trying to reach all these
4424 <p
>We maintain the authoritative source of our manual in the
4425 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4426 wiki
</a
>, as several wiki pages written in English. It consist of one
4427 front page with references to the different chapters, several pages
4428 for each chapter, and finally one
"collection page
" gluing all the
4429 chapters together into one large web page (aka
4430 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4431 AllInOne page
</a
>). The AllInOne page is the one used for further
4432 processing and translations. Thanks to the fact that the
4433 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4434 wiki.debian.org support exporting pages in
4435 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4436 the list of pages to export using the raw version of the AllInOne
4437 page, loop over each of them to generate a Docbook XML version of the
4438 manual. This process also download images and transform image
4439 references to use the locally downloaded images. The generated
4440 Docbook XML files are slightly broken, so some post-processing is done
4441 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4442 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4443 a handfull of images. The XML file can now be used to generate PDF, HTML
4444 and epub versions of the English manual. This is the basic step of
4445 our process, making PDF (using dblatex), HTML (using xsltproc) and
4446 epub (using dbtoepub) version from Docbook XML, and the resulting files
4447 are placed in the debian-edu-doc-en binary package.
</p
>
4449 <p
>But English documentation is not enough for us. We want translated
4450 documentation too, and we want to make it easy for translators to
4451 track the English original. For this we use the
4452 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4453 which allow us to transform the English Docbook XML file into a
4454 translation file (a .pot file), usable with the normal gettext based
4455 translation tools used by those translating free software. The pot
4456 file is used to create and maintain translation files (several .po
4457 files), which the translations update with the native language
4458 translations of all titles, paragraphs and blocks of text in the
4459 original. The next step is combining the original English Docbook XML
4460 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4461 create a translated Docbook XML file (in this case
4462 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4463 translated, if the translation is not complete) Docbook XML file can
4464 then be used like the original to create a PDF, HTML and epub version
4465 of the documentation.
</p
>
4467 <p
>The translators use different tools to edit the .po files. We
4469 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4470 while some use emacs and vi, others can use web based editors like
4471 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4472 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4473 is where the .po file end up, in our git repository. Updated
4474 translations can either be committed directly to git, or submitted as
4475 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4476 against the debian-edu-doc package
</a
>.
</p
>
4478 <p
>One challenge is images, which both might need to be translated (if
4479 they show translated user applications), and are needed in different
4480 formats when creating PDF and HTML versions (epub is a HTML version in
4481 this regard). For this we transform the original PNG images to the
4482 needed density and format during build, and have a way to provide
4483 translated images by storing translated versions in
4484 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4485 package maintainers know more.
</p
>
4487 <p
>If you wonder what the result look like, we provide
4488 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4489 of the documentation packages on the web
</a
>. See for example the
4490 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4491 PDF version
</a
> or the
4492 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4493 HTML version
</a
>. We do not yet build the epub version by default,
4494 but perhaps it will be done in the future.
</p
>
4496 <p
>To learn more, check out
4497 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4498 debian-edu-doc package
</a
>,
4499 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4500 manual on the wiki
</a
> and
4501 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4502 translation instructions
</a
> in the manual.
</p
>
4507 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4508 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4509 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4510 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4511 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4512 related packages relevant for the computer installed automatically.
4513 So I implemented one, using
4514 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4515 package
</a
>. To use it, install the tasksel and isenkram packages and
4516 run tasksel as user root. You should be presented with a new option,
4517 "Hardware specific packages (autodetected by isenkram)
". When you
4518 select it, tasksel will install the packages isenkram claim is fit for
4519 the current hardware, hot pluggable or not.
<p
>
4521 <p
>The implementation is in two files, one is the tasksel menu entry
4522 description, and the other is the script used to extract the list of
4523 packages to install. The first part is in
4524 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4527 <p
><blockquote
><pre
>
4530 Description: Hardware specific packages (autodetected by isenkram)
4531 Based on the detected hardware various hardware specific packages are
4533 Test-new-install: mark show
4535 Packages: for-current-hardware
4536 </pre
></blockquote
></p
>
4538 <p
>The second part is in
4539 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4542 <p
><blockquote
><pre
>
4547 isenkram-autoinstall-firmware -l
4549 </pre
></blockquote
></p
>
4551 <p
>All in all, a very short and simple implementation making it
4552 trivial to install the hardware dependent package we all may want to
4553 have installed on our machines. I
've not been able to find a way to
4554 get tasksel to tell you exactly which packages it plan to install
4555 before doing the installation. So if you are curious or careful,
4556 check the output from the isenkram-* command line tools first.
</p
>
4558 <p
>The information about which packages are handling which hardware is
4559 fetched either from the isenkram package itself in
4560 /usr/share/isenkram/, from git.debian.org or from the APT package
4561 database (using the Modaliases header). The APT package database
4562 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4563 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4564 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4565 the python-apt code (bug
4566 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4567 workaround I was able to get rid of the file descriptor leak and
4568 reduce the memory leak from ~
30 MiB per hardware detection down to
4569 around
2 MiB per hardware detection. It should make the desktop
4570 daemon a lot more useful. The fix is in version
0.7 uploaded to
4571 unstable today.
</p
>
4573 <p
>I believe the current way of mapping hardware to packages in
4574 Isenkram is is a good draft, but in the future I expect isenkram to
4575 use the AppStream data source for this. A proposal for getting proper
4576 AppStream support into Debian is floating around as
4577 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4578 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4579 project
</a
> will take place this summer to improve the situation. I
4580 look forward to seeing the result, and welcome patches for isenkram to
4581 start using the information when it is ready.
</p
>
4583 <p
>If you want your package to map to some specific hardware, either
4584 add a
"Xb-Modaliases
" header to your control file like I did in
4585 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4586 package
</a
> or submit a bug report with the details to the isenkram
4588 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4589 blog posts tagged isenkram
</a
> for details on the notation. I expect
4590 the information will be migrated to AppStream eventually, but for the
4591 moment I got no better place to store it.
</p
>
4596 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4597 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4599 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4600 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4601 project
</a
> is working on providing the software and hardware to make
4602 it easy for non-technical people to host their data and communication
4603 at home, and being able to communicate with their friends and family
4604 encrypted and away from prying eyes. It is still going strong, and
4605 today a major mile stone was reached.
</p
>
4607 <p
>Today, the last of the packages currently used by the project to
4608 created the system images were accepted into Debian Unstable. It was
4609 the freedombox-setup package, which is used to configure the images
4610 during build and on the first boot. Now all one need to get going is
4611 the build code from the freedom-maker git repository and packages from
4612 Debian. And once the freedombox-setup package enter testing, we can
4613 build everything directly from Debian. :)
</p
>
4615 <p
>Some key packages used by Freedombox are
4616 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4617 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4618 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4619 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4620 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4621 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4622 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4623 are plans to integrate more packages into the setup. User
4624 documentation is maintained on the Debian wiki. Please
4625 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4626 the manual
</a
> and help us improve it.
</p
>
4628 <p
>To test for yourself and create boot images with the FreedomBox
4629 setup, run this on a Debian machine using a user with sudo rights to
4630 become root:
</p
>
4632 <p
><pre
>
4633 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4634 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4636 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4638 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4639 </pre
></p
>
4641 <p
>Root access is needed to run debootstrap and mount loopback
4642 devices. See the README in the freedom-maker git repo for more
4643 details on the build. If you do not want all three images, trim the
4644 make line. Note that the virtualbox-image target is not really
4645 virtualbox specific. It create a x86 image usable in kvm, qemu,
4646 vmware and any other x86 virtual machine environment. You might need
4647 the version of vmdebootstrap in Jessie to get the build working, as it
4648 include fixes for a race condition with kpartx.
</p
>
4650 <p
>If you instead want to install using a Debian CD and the preseed
4651 method, boot a Debian Wheezy ISO and use this boot argument to load
4652 the preseed values:
</p
>
4654 <p
><pre
>
4655 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4656 </pre
></p
>
4658 <p
>I have not tested it myself the last few weeks, so I do not know if
4659 it still work.
</p
>
4661 <p
>If you wonder how to help, one task you could look at is using
4662 systemd as the boot system. It will become the default for Linux in
4663 Jessie, so we need to make sure it is usable on the Freedombox. I did
4664 a simple test a few weeks ago, and noticed dnsmasq failed to start
4665 during boot when using systemd. I suspect there are other problems
4666 too. :) To detect problems, there is a test suite included, which can
4667 be run from the plinth web interface.
</p
>
4669 <p
>Give it a go and let us know how it goes on the mailing list, and help
4670 us get the new release published. :) Please join us on
4671 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4672 irc.debian.org)
</a
> and
4673 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4674 mailing list
</a
> if you want to help make this vision come true.
</p
>
4679 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4680 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4681 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4682 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4683 <description><p
>For a while now, I have been looking for a sensible offsite backup
4684 solution for use at home. My requirements are simple, it must be
4685 cheap and locally encrypted (in other words, I keep the encryption
4686 keys, the storage provider do not have access to my private files).
4687 One idea me and my friends had many years ago, before the cloud
4688 storage providers showed up, was to use Google mail as storage,
4689 writing a Linux block device storing blocks as emails in the mail
4690 service provided by Google, and thus get heaps of free space. On top
4691 of this one can add encryption, RAID and volume management to have
4692 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4693 I never found time to implement such system. But the last few weeks I
4694 have looked at a system called
4695 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4696 mounted network backed file system with the features I need.
</p
>
4698 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4699 handling several different storage providers, any with Amazon S3,
4700 Google Drive or OpenStack API. There are heaps of such storage
4701 providers. S3QL can also use a local directory as storage, which
4702 combined with sshfs allow for file storage on any ssh server. S3QL
4703 include support for encryption, compression, de-duplication, snapshots
4704 and immutable file systems, allowing me to mount the remote storage as
4705 a local mount point, look at and use the files as if they were local,
4706 while the content is stored in the cloud as well. This allow me to
4707 have a backup that should survive fire. The file system can not be
4708 shared between several machines at the same time, as only one can
4709 mount it at the time, but any machine with the encryption key and
4710 access to the storage service can mount it if it is unmounted.
</p
>
4712 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4713 package is included already. So to get started, run
<tt
>apt-get
4714 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4715 Greenqloud, after reading their nice recipe on
4716 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4717 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4718 in Iceland more than those in USA when it come to keeping my personal
4719 data safe and private, and thus would rather spend money on a company
4720 in Iceland. Another nice recipe is available from the article
4721 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4722 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4723 Admin magazine. When the provider is picked, figure out how to get
4724 the API key needed to connect to the storage API. With Greencloud,
4725 the key did not show up until I had added payment details to my
4728 <p
>Armed with the API access details, it is time to create the file
4729 system. First, create a new bucket in the cloud. This bucket is the
4730 file system storage area. I picked a bucket name reflecting the
4731 machine that was going to store data there, but any name will do.
4732 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4733 the API login and password, and a locally created password. Store it
4734 all in ~root/.s3ql/authinfo2 like this:
4736 <p
><blockquote
><pre
>
4738 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4739 backend-login: API-login
4740 backend-password: API-password
4741 fs-passphrase: local-password
4742 </pre
></blockquote
></p
>
4744 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4745 but any sensible way to create a fairly random password should do it.
4746 Armed with these details, it is now time to run mkfs, entering the API
4747 details and password to create it:
</p
>
4749 <p
><blockquote
><pre
>
4750 # mkdir -m
700 /var/lib/s3ql-cache
4751 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4752 --ssl s3c://s.greenqloud.com:
443/bucket-name
4753 Enter backend login:
4754 Enter backend password:
4755 Before using S3QL, make sure to read the user
's guide, especially
4756 the
'Important Rules to Avoid Loosing Data
' section.
4757 Enter encryption password:
4758 Confirm encryption password:
4759 Generating random encryption key...
4760 Creating metadata tables...
4770 Compressing and uploading metadata...
4771 Wrote
0.00 MB of compressed metadata.
4772 #
</pre
></blockquote
></p
>
4774 <p
>The next step is mounting the file system to make the storage available.
4776 <p
><blockquote
><pre
>
4777 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4778 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4779 Using
4 upload threads.
4780 Downloading and decompressing metadata...
4790 Mounting filesystem...
4792 Filesystem Size Used Avail Use% Mounted on
4793 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4795 </pre
></blockquote
></p
>
4797 <p
>The file system is now ready for use. I use rsync to store my
4798 backups in it, and as the metadata used by rsync is downloaded at
4799 mount time, no network traffic (and storage cost) is triggered by
4800 running rsync. To unmount, one should not use the normal umount
4801 command, as this will not flush the cache to the cloud storage, but
4802 instead running the umount.s3ql command like this:
4804 <p
><blockquote
><pre
>
4807 </pre
></blockquote
></p
>
4809 <p
>There is a fsck command available to check the file system and
4810 correct any problems detected. This can be used if the local server
4811 crashes while the file system is mounted, to reset the
"already
4812 mounted
" flag. This is what it look like when processing a working
4813 file system:
</p
>
4815 <p
><blockquote
><pre
>
4816 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4817 Using cached metadata.
4818 File system seems clean, checking anyway.
4819 Checking DB integrity...
4820 Creating temporary extra indices...
4821 Checking lost+found...
4822 Checking cached objects...
4823 Checking names (refcounts)...
4824 Checking contents (names)...
4825 Checking contents (inodes)...
4826 Checking contents (parent inodes)...
4827 Checking objects (reference counts)...
4828 Checking objects (backend)...
4829 ..processed
5000 objects so far..
4830 ..processed
10000 objects so far..
4831 ..processed
15000 objects so far..
4832 Checking objects (sizes)...
4833 Checking blocks (referenced objects)...
4834 Checking blocks (refcounts)...
4835 Checking inode-block mapping (blocks)...
4836 Checking inode-block mapping (inodes)...
4837 Checking inodes (refcounts)...
4838 Checking inodes (sizes)...
4839 Checking extended attributes (names)...
4840 Checking extended attributes (inodes)...
4841 Checking symlinks (inodes)...
4842 Checking directory reachability...
4843 Checking unix conventions...
4844 Checking referential integrity...
4845 Dropping temporary indices...
4846 Backing up old metadata...
4856 Compressing and uploading metadata...
4857 Wrote
0.89 MB of compressed metadata.
4859 </pre
></blockquote
></p
>
4861 <p
>Thanks to the cache, working on files that fit in the cache is very
4862 quick, about the same speed as local file access. Uploading large
4863 amount of data is to me limited by the bandwidth out of and into my
4864 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
4865 which is very close to my upload speed, and downloading the same
4866 Debian installation ISO gave me
610 kiB/s, close to my download speed.
4867 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
4868 network, not the file system code. I do not know what a good cache
4869 size would be, but suspect that the cache should e larger than your
4870 working set.
</p
>
4872 <p
>I mentioned that only one machine can mount the file system at the
4873 time. If another machine try, it is told that the file system is
4876 <p
><blockquote
><pre
>
4877 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4878 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4879 Using
8 upload threads.
4880 Backend reports that fs is still mounted elsewhere, aborting.
4882 </pre
></blockquote
></p
>
4884 <p
>The file content is uploaded when the cache is full, while the
4885 metadata is uploaded once every
24 hour by default. To ensure the
4886 file system content is flushed to the cloud, one can either umount the
4887 file system, or ask S3QL to flush the cache and metadata using
4890 <p
><blockquote
><pre
>
4891 # s3qlctrl upload-meta /s3ql
4892 # s3qlctrl flushcache /s3ql
4894 </pre
></blockquote
></p
>
4896 <p
>If you are curious about how much space your data uses in the
4897 cloud, and how much compression and deduplication cut down on the
4898 storage usage, you can use s3qlstat on the mounted file system to get
4901 <p
><blockquote
><pre
>
4903 Directory entries:
9141
4906 Total data size:
22049.38 MB
4907 After de-duplication:
21955.46 MB (
99.57% of total)
4908 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4909 Database size:
2.39 MB (uncompressed)
4910 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4912 </pre
></blockquote
></p
>
4914 <p
>I mentioned earlier that there are several possible suppliers of
4915 storage. I did not try to locate them all, but am aware of at least
4916 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4917 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4918 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4919 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4920 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4921 accept payment in Bitcoin. Pick one that suit your need. Some of
4922 them provide several GiB of free storage, but the prize models are
4923 quite different and you will have to figure out what suits you
4926 <p
>While researching this blog post, I had a look at research papers
4927 and posters discussing the S3QL file system. There are several, which
4928 told me that the file system is getting a critical check by the
4929 science community and increased my confidence in using it. One nice
4931 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4932 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4933 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4934 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4935 and Pamela Smith. Please have a look.
</p
>
4937 <p
>Given my problems with different file systems earlier, I decided to
4938 check out the mounted S3QL file system to see if it would be usable as
4939 a home directory (in other word, that it provided POSIX semantics when
4940 it come to locking and umask handling etc). Running
4941 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4942 test code to check file system semantics
</a
>, I was happy to discover that
4943 no error was found. So the file system can be used for home
4944 directories, if one chooses to do so.
</p
>
4946 <p
>If you do not want a locally file system, and want something that
4947 work without the Linux fuse file system, I would like to mention the
4948 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4949 provide locally encrypted backup using a command line client. It have
4950 a nicer access control system, where one can split out read and write
4951 access, allowing some systems to write to the backup and others to
4952 only read from it.
</p
>
4954 <p
>As usual, if you use Bitcoin and want to show your support of my
4955 activities, please send Bitcoin donations to my address
4956 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4961 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4962 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4963 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4964 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4965 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4966 project
</a
> is working on providing the software and hardware for
4967 making it easy for non-technical people to host their data and
4968 communication at home, and being able to communicate with their
4969 friends and family encrypted and away from prying eyes. It has been
4970 going on for a while, and is slowly progressing towards a new test
4971 release (
0.2).
</p
>
4973 <p
>And what day could be better than the Pi day to announce that the
4974 new version will provide
"hard drive
" / SD card / USB stick images for
4975 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4976 system), and can also be installed using a Debian installer preseed
4977 file. The Debian based Freedombox is now based on Debian Jessie,
4978 where most of the needed packages used are already present. Only one,
4979 the freedombox-setup package, is missing. To try to build your own
4980 boot image to test the current status, fetch the freedom-maker scripts
4982 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4983 with a user with sudo access to become root:
4986 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4988 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4989 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4991 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4994 <p
>Root access is needed to run debootstrap and mount loopback
4995 devices. See the README for more details on the build. If you do not
4996 want all three images, trim the make line. But note that thanks to
<a
4997 href=
"https://bugs.debian.org/
741407">a race condition in
4998 vmdebootstrap
</a
>, the build might fail without the patch to the
4999 kpartx call.
</p
>
5001 <p
>If you instead want to install using a Debian CD and the preseed
5002 method, boot a Debian Wheezy ISO and use this boot argument to load
5003 the preseed values:
</p
>
5006 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
5009 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
5010 recently introduced bug in apt in Jessie
</a
>, the installer will
5011 currently hang while setting up APT sources. Killing the
5012 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
5013 installation will get the installation going. This affect all
5014 installations in Jessie, and I expect it will be fixed soon.
</p
>
5016 <p
>Give it a go and let us know how it goes on the mailing list, and help
5017 us get the new release published. :) Please join us on
5018 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
5019 irc.debian.org)
</a
> and
5020 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5021 mailing list
</a
> if you want to help make this vision come true.
</p
>
5026 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
5027 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
5028 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
5029 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
5030 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
5031 innetgr tools, because I needed them in
5032 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
5033 ng-utils, and it has served me well. I placed the project under the
5034 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
5035 repository. But many years ago, the CVS repository was dropped (lost,
5036 not migrated to new hardware, not sure), and the project have lacked a
5037 proper home since then.
</p
>
5039 <p
>Last summer, I had a look at the package and made a new release
5040 fixing a irritating crash bug, but was unable to store the changes in
5041 a proper source control system. I applied for a project on
5042 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
5043 to follow up on it. Until today. :)
</p
>
5045 <p
>After many hours of cleaning and migration, the ng-utils project
5046 now have a new home, and a git repository with the highlight of the
5047 history of the project. I published all release tarballs and imported
5048 them into the git repository. As the project is really stable and not
5049 expected to gain new features any time soon, I decided to make a new
5050 release and call it
1.0. Visit the new project home on
5051 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
5052 if you want to check it out. The new version is also uploaded into
5053 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
5058 <title>Testing sysvinit from experimental in Debian Hurd
</title>
5059 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
5060 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
5061 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
5062 <description><p
>A few days ago I decided to try to help the Hurd people to get
5063 their changes into sysvinit, to allow them to use the normal sysvinit
5064 boot system instead of their old one. This follow up on the
5065 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
5066 Google Summer of Code work
</a
> done last summer by Justus Winter to
5067 get Debian on Hurd working more like Debian on Linux. To get started,
5068 I downloaded a prebuilt hard disk image from
5069 <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
>,
5070 and started it using virt-manager.
</p
>
5072 <p
>The first think I had to do after logging in (root without any
5073 password) was to get the network operational. I followed
5074 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
5075 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
5076 commands as root to get the machine to accept a IP address from the
5077 kvm internal DHCP server:
</p
>
5079 <p
><blockquote
><pre
>
5080 settrans -fgap /dev/netdde /hurd/netdde
5081 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
5082 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
5084 </pre
></blockquote
></p
>
5086 <p
>After this, the machine had internet connectivity, and I could
5087 upgrade it and install the sysvinit packages from experimental and
5088 enable it as the default boot system in Hurd.
</p
>
5090 <p
>But before I did that, I set a password on the root user, as ssh is
5091 running on the machine it for ssh login to work a password need to be
5092 set. Also, note that a bug somewhere in openssh on Hurd block
5093 compression from working. Remember to turn that off on the client
5096 <p
>Run these commands as root to upgrade and test the new sysvinit
5099 <p
><blockquote
><pre
>
5100 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
5101 deb http://http.debian.net/debian/ experimental main
5104 apt-get dist-upgrade
5105 apt-get install -t experimental initscripts sysv-rc sysvinit \
5106 sysvinit-core sysvinit-utils
5107 update-alternatives --config runsystem
5108 </pre
></blockquote
></p
>
5110 <p
>To reboot after switching boot system, you have to use
5111 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
5112 yet a sysvinit process able to receive the signals from the normal
5113 'reboot
' command. After switching to sysvinit as the boot system,
5114 upgrading every package and rebooting, the network come up with DHCP
5115 after boot as it should, and the settrans/pkill hack mentioned at the
5116 start is no longer needed. But for some strange reason, there are no
5117 longer any login prompt in the virtual console, so I logged in using
5120 <p
>Note that there are some race conditions in Hurd making the boot
5121 fail some times. No idea what the cause is, but hope the Hurd porters
5122 figure it out. At least Justus said on IRC (#debian-hurd on
5123 irc.debian.org) that they are aware of the problem. A way to reduce
5124 the impact is to upgrade to the Hurd packages built by Justus by
5125 adding this repository to the machine:
</p
>
5127 <p
><blockquote
><pre
>
5128 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
5129 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5131 </pre
></blockquote
></p
>
5133 <p
>At the moment the prebuilt virtual machine get some packages from
5134 http://ftp.debian-ports.org/debian, because some of the packages in
5135 unstable do not yet include the required patches that are lingering in
5136 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
5138 <p
><blockquote
><pre
>
5139 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
5140 i emacs - GNU Emacs editor (metapackage)
5141 i gdb - GNU Debugger
5142 i hurd-recommended - Miscellaneous translators
5143 i isc-dhcp-client - ISC DHCP client
5144 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5145 i libc-bin - Embedded GNU C Library: Binaries
5146 i libc-dev-bin - Embedded GNU C Library: Development binaries
5147 i libc0.3 - Embedded GNU C Library: Shared libraries
5148 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5149 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5150 i multiarch-support - Transitional package to ensure multiarch compatibilit
5151 i A x11-common - X Window System (X.Org) infrastructure
5152 i xorg - X.Org X Window System
5153 i A xserver-xorg - X.Org X server
5154 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5156 </pre
></blockquote
></p
>
5158 <p
>All in all, testing hurd has been an interesting experience. :)
5159 X.org did not work out of the box and I never took the time to follow
5160 the porters instructions to fix it. This time I was interested in the
5161 command line stuff.
<p
>
5166 <title>New chrpath release
0.16</title>
5167 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
5168 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
5169 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
5170 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
5171 find problems in C, C++ and Java code using static source code
5172 analysis. It can detect a lot of different problems, and is very
5173 useful to find memory and locking bugs in the error handling part of
5174 the source. The company behind it provide
5175 <a href=
"https://scan.coverity.com/
">check of free software projects as
5176 a community service
</a
>, and many hundred free software projects are
5177 already checked. A few days ago I decided to have a closer look at
5178 the Coverity system, and discovered that the
5179 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
5180 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
5181 projects I am involved with was already registered. But these are
5182 fairly big, and I would also like to have a small and easy project to
5183 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
5184 checking of the chrpath project
</a
>. It was
5185 added to the checker and discovered seven potential defects. Six of
5186 these were real, mostly resource
"leak
" when the program detected an
5187 error. Nothing serious, as the resources would be released a fraction
5188 of a second later when the program exited because of the error, but it
5189 is nice to do it right in case the source of the program some time in
5190 the future end up in a library. Having fixed all defects and added
5191 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
5192 mailing list for the chrpath developers
</a
>, I decided it was time to
5193 publish a new release. These are the release notes:
</p
>
5195 <p
>New in
0.16 released
2014-
01-
14:
</p
>
5199 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
5200 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
5201 <li
>Mention new project mailing list in the documentation.
</li
>
5206 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5207 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
5208 project if something is wrong with the new release. The test suite
5209 did not discover any old errors, so if you find a new one, please also
5210 include a test suite check.
</p
>
5215 <title>New chrpath release
0.15</title>
5216 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
5217 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
5218 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
5219 <description><p
>After many years break from the package and a vain hope that
5220 development would be continued by someone else, I finally pulled my
5221 acts together this morning and wrapped up a new release of chrpath,
5222 the command line tool to modify the rpath and runpath of already
5223 compiled ELF programs. The update was triggered by the persistence of
5224 Isha Vishnoi at IBM, which needed a new config.guess file to get
5225 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
5226 is working on. I checked the
5227 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
5228 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
5229 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
5230 packages for interesting patches (failed to find the source from
5231 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5232 These are the release notes:
</p
>
5234 <p
>New in
0.15 released
2013-
11-
24:
</p
>
5238 <li
>Updated config.sub and config.guess from the GNU project to work
5239 with newer architectures. Thanks to isha vishnoi for the heads
5242 <li
>Updated README with current URLs.
</li
>
5244 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5245 Matthias Klose.
</li
>
5247 <li
>Added missing help for -k|--keepgoing option, using patch by
5248 Petr Machata found in Fedora.
</li
>
5250 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
5251 .dynamic is a NULL terminated string. Based on patch found in
5252 Fedora credited Axel Thimm and Christian Krause.
</li
>
5257 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5258 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
5259 project if something is wrong with the new release. The test suite
5260 did not discover any old errors, so if you find a new one, please also
5261 include a testsuite check.
</p
>
5266 <title>Debian init.d boot script example for rsyslog
</title>
5267 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
5268 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
5269 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
5270 <description><p
>If one of the points of switching to a new init system in Debian is
5271 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
5272 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
5273 init.d scripts at all. Here is an example init.d script, ie a rewrite
5274 of /etc/init.d/rsyslog:
</p
>
5276 <p
><pre
>
5277 #!/lib/init/init-d-script
5280 # Required-Start: $remote_fs $time
5281 # Required-Stop: umountnfs $time
5282 # X-Stop-After: sendsigs
5283 # Default-Start:
2 3 4 5
5284 # Default-Stop:
0 1 6
5285 # Short-Description: enhanced syslogd
5286 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5287 # It is quite compatible to stock sysklogd and can be
5288 # used as a drop-in replacement.
5290 DESC=
"enhanced syslogd
"
5291 DAEMON=/usr/sbin/rsyslogd
5292 </pre
></p
>
5294 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
5295 script was
137 lines, and the above is just
15 lines, most of it meta
5296 info/comments.
</p
>
5298 <p
>How to do this, you ask? Well, one create a new script
5299 /lib/init/init-d-script looking something like this:
5301 <p
><pre
>
5304 # Define LSB log_* functions.
5305 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
5306 # and status_of_proc is working.
5307 . /lib/lsb/init-functions
5310 # Function that starts the daemon/service
5316 #
0 if daemon has been started
5317 #
1 if daemon was already running
5318 #
2 if daemon could not be started
5319 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
5321 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5324 # Add code here, if necessary, that waits for the process to be ready
5325 # to handle requests from services started subsequently which depend
5326 # on this one. As a last resort, sleep for some time.
5330 # Function that stops the daemon/service
5335 #
0 if daemon has been stopped
5336 #
1 if daemon was already stopped
5337 #
2 if daemon could not be stopped
5338 # other if a failure occurred
5339 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
5340 RETVAL=
"$?
"
5341 [
"$RETVAL
" =
2 ]
&& return
2
5342 # Wait for children to finish too if this is a daemon that forks
5343 # and if the daemon is only ever run from this initscript.
5344 # If the above conditions are not satisfied then add some other code
5345 # that waits for the process to drop all resources that could be
5346 # needed by services started subsequently. A last resort is to
5347 # sleep for some time.
5348 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
5349 [
"$?
" =
2 ]
&& return
2
5350 # Many daemons don
't delete their pidfiles when they exit.
5352 return
"$RETVAL
"
5356 # Function that sends a SIGHUP to the daemon/service
5360 # If the daemon can reload its configuration without
5361 # restarting (for example, when it is sent a SIGHUP),
5362 # then implement that here.
5364 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
5369 scriptbasename=
"$(basename $
1)
"
5370 echo
"SN: $scriptbasename
"
5371 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
5372 script=
"$
1"
5379 NAME=$(basename $DAEMON)
5380 PIDFILE=/var/run/$NAME.pid
5382 # Exit if the package is not installed
5383 #[ -x
"$DAEMON
" ] || exit
0
5385 # Read configuration variable file if it is present
5386 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
5388 # Load the VERBOSE setting and other rcS variables
5391 case
"$
1" in
5393 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
5395 case
"$?
" in
5396 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5397 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5401 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
5403 case
"$?
" in
5404 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5405 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5409 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5411 #reload|force-reload)
5413 # If do_reload() is not implemented then leave this commented out
5414 # and leave
'force-reload
' as an alias for
'restart
'.
5416 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5420 restart|force-reload)
5422 # If the
"reload
" option is implemented then remove the
5423 #
'force-reload
' alias
5425 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5427 case
"$?
" in
5430 case
"$?
" in
5432 1) log_end_msg
1 ;; # Old process is still running
5433 *) log_end_msg
1 ;; # Failed to start
5443 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5449 </pre
></p
>
5451 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5452 lot. I did not really polish the approach, so it might not always
5453 work out of the box, but you get the idea. I did not try very hard to
5454 optimize it nor make it more robust either.
</p
>
5456 <p
>A better argument for switching init system in Debian than reducing
5457 the size of init scripts (which is a good thing to do anyway), is to
5458 get boot system that is able to handle the kernel events sensibly and
5459 robustly, and do not depend on the boot to run sequentially. The boot
5460 and the kernel have not behaved sequentially in years.
</p
>
5465 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5466 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5467 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5468 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5469 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5470 remote display access is the preferred solution with oVirt and RedHat
5471 Enterprise Virtualization, and I was sad to discover the other day
5472 that the browser plugin needed to use these systems seamlessly was
5473 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5474 for a package
</a
> was from
2012-
04-
10 with no progress since
5475 2013-
04-
01, so I decided to wrap up a package based on the great work
5476 from Cajus Pollmeier and put it in a collab-maint maintained git
5477 repository to get a package I could use. I would very much like
5478 others to help me maintain the package (or just take over, I do not
5479 mind), but as no-one had volunteered so far, I just uploaded it to
5480 NEW. I hope it will be available in Debian in a few days.
</p
>
5482 <p
>The source is now available from
5483 <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
>
5488 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5489 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5490 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5491 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5492 <description><p
>The
5493 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5494 program is a a very nice system to create virtual machine images. It
5495 create a image file, add a partition table, mount it and run
5496 debootstrap in the mounted directory to create a Debian system on a
5497 stick. Yesterday, I decided to try to teach it how to make images for
5498 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5499 of a plan to simplify the build system for
5500 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5501 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5502 the virtualbox images, but its current build system made multistrap
5503 based system for Dreamplug images, and it is lacking support for
5504 Raspberry Pi.
</p
>
5506 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5507 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5508 code and adjusted it to be able to build armel images on my amd64
5509 Debian laptop. I ended up giving vmdebootstrap five new options,
5510 allowing me to replicate the image creation process I use to make
5511 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5512 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5513 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5514 call debootstrap with --foreign and to copy the handler into the
5515 generated chroot before running the second stage. This allow
5516 vmdebootstrap to create armel images on an amd64 host. Next I added
5517 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5518 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5519 given file system type, allowing me to create an image with a vfat
5520 partition for the /boot/ stuff. I also added a
<tt
>--variant
5521 variant
</tt
> option to allow me to create smaller images without the
5522 Debian base system packages installed. Finally, I added an option
5523 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5524 as a boot loader. It is not needed on the Raspberry Pi and probably
5525 most other non-x86 architectures. The changes were accepted by the
5526 upstream author of vmdebootstrap yesterday and today, and is now
5528 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5529 upstream project page
</a
>.
</p
>
5531 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5532 create a small script (the customize script) to add the non-free
5533 binary blob needed to boot the Raspberry Pi and the APT source
5536 <p
><pre
>
5538 set -e # Exit on first error
5539 rootdir=
"$
1"
5540 cd
"$rootdir
"
5541 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5542 deb http://http.debian.net/debian/ jessie main contrib non-free
5544 # Install non-free binary blob needed to boot Raspberry Pi. This
5545 # install a kernel somewhere too.
5546 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5547 -O $rootdir/usr/bin/rpi-update
5548 chmod a+x $rootdir/usr/bin/rpi-update
5549 mkdir -p $rootdir/lib/modules
5550 touch $rootdir/boot/start.elf
5551 chroot $rootdir rpi-update
5552 </pre
></p
>
5554 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5555 to build the image:
</p
>
5558 sudo ./vmdebootstrap \
5561 --distribution jessie \
5562 --mirror http://http.debian.net/debian \
5571 --root-password raspberry \
5572 --hostname raspberrypi \
5573 --foreign /usr/bin/qemu-arm-static \
5574 --customize `pwd`/customize \
5576 --package git-core \
5577 --package binutils \
5578 --package ca-certificates \
5581 </pre
></p
>
5583 <p
>The list of packages being installed are the ones needed by
5584 rpi-update to make the image bootable on the Raspberry Pi, with the
5585 exception of netbase, which is needed by debootstrap to find
5586 /etc/hosts with the minbase variant. I really wish there was a way to
5587 set up an Raspberry Pi using only packages in the Debian archive, but
5588 that is not possible as far as I know, because it boots from the GPU
5589 using a non-free binary blob.
</p
>
5591 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5592 probably a few others installed. I have not checked the complete
5593 build dependency list.
</p
>
5595 <p
>The resulting image will not use the hardware floating point unit
5596 on the Raspberry PI, because the armel architecture in Debian is not
5597 optimized for that use. So the images created will be a bit slower
5598 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5603 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5604 <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>
5605 <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>
5606 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5607 <description><p
>The last few days I came across a few good causes that should get
5608 wider attention. I recommend signing and donating to each one of
5611 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5612 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5613 Women program which is a Google Summer of Code like initiative to get
5614 more women involved in free software. One debian sponsor has offered
5615 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5616 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5617 hope you will to. :)
</p
>
5619 <p
>And the Electronic Frontier Foundation just announced plans to
5620 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5621 documentaries about the excessive spying
</a
> on every Internet user that
5622 take place these days, and their need to fund the work. I
've already
5623 donated. Are you next?
</p
>
5625 <p
>For my Norwegian audience, the organisation Studentenes og
5626 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5627 statement under the heading
5628 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5629 Access
</a
> for those of us asking for more focus on open access in the
5630 Norwegian government. So far
499 signatures. I hope you will sign it
5636 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5637 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5638 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5639 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5640 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5641 project
</a
> have been going on for a while, and have presented the
5642 vision, ideas and solution several places. Here is a little
5643 collection of videos of talks and presentation of the project.
</p
>
5647 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5648 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5650 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5651 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5653 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5654 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5655 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5656 (Youtube)
</li
>
5658 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5659 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5661 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5662 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5664 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5665 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5666 York City in
2012</a
> (Youtube)
</li
>
5668 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5669 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5670 (Youtube)
</li
>
5672 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5673 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5675 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5676 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5678 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5679 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5680 2013</a
> (Youtube)
</li
>
5684 <p
>A larger list is available from
5685 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5686 Freedombox Wiki
</a
>.
</p
>
5688 <p
>On other news, I am happy to report that Freedombox based on Debian
5689 Jessie is coming along quite well, and soon both Owncloud and using
5690 Tor should be available for testers of the Freedombox solution. :) In
5691 a few weeks I hope everything needed to test it is included in Debian.
5692 The withsqlite package is already in Debian, and the plinth package is
5693 pending in NEW. The third and vital part of that puzzle is the
5694 metapackage/setup framework, which is still pending an upload. Join
5695 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5696 (#freedombox on irc.debian.org)
</a
> and
5697 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5698 mailing list
</a
> if you want to help make this vision come true.
</p
>
5703 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5704 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5706 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5707 <description><p
>I was introduced to the
5708 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5709 in
2010, when Eben Moglen presented his vision about serving the need
5710 of non-technical people to keep their personal information private and
5711 within the legal protection of their own homes. The idea is to give
5712 people back the power over their network and machines, and return
5713 Internet back to its intended peer-to-peer architecture. Instead of
5714 depending on a central service, the Freedombox will give everyone
5715 control over their own basic infrastructure.
</p
>
5717 <p
>I
've intended to join the effort since then, but other tasks have
5718 taken priority. But this summers nasty news about the misuse of trust
5719 and privilege exercised by the
"western
" intelligence gathering
5720 communities increased my eagerness to contribute to a point where I
5721 actually started working on the project a while back.
</p
>
5723 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5724 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5725 create a simple and cheap Debian based appliance that anyone can hook
5726 up in their home and get access to secure and private services and
5727 communication. The initial deployment platform have been the
5728 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5729 which is a piece of hardware I do not own. So to be able to test what
5730 the current Freedombox setup look like, I had to come up with a way to install
5731 it on some hardware I do have access to. I have rewritten the
5732 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5733 image build framework to use .deb packages instead of only copying
5734 setup into the boot images, and thanks to this rewrite I am able to
5735 set up any machine supported by Debian Wheezy as a Freedombox, using
5736 the previously mentioned deb (and a few support debs for packages
5737 missing in Debian).
</p
>
5739 <p
>The current Freedombox setup consist of a set of bootstrapping
5741 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5742 and a administrative web interface
5743 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5744 withsqlite), as well as a privacy enhancing proxy based on
5745 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5746 (freedombox-privoxy). There is also a web/javascript based XMPP
5747 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5748 trying (unsuccessfully so far) to talk to the XMPP server
5749 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5750 web interface is pluggable, and the goal is to use it to enable OpenID
5751 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5752 this is really working yet, see
5753 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5754 project TODO
</a
> for links to GIT repositories. Most of the code is
5755 on github at the moment. The HTTP proxy is operational out of the
5756 box, and the admin web interface can be used to add/remove plinth
5757 users. I
've not been able to do anything else with it so far, but
5758 know there are several branches spread around github and other places
5759 with lots of half baked features.
</p
>
5761 <p
>Anyway, if you want to have a look at the current state, the
5762 following recipes should work to give you a test machine to poke
5765 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5769 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5770 <li
>Boot from it, either as CD or USB stick.
</li
>
5771 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5772 to the Debian installer:
<p
>
5773 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5775 <li
>Answer the few language/region/password questions and pick disk to
5776 install on.
</li
>
5778 <li
>When the installation is finished and the machine have rebooted a
5779 few times, your Freedombox is ready for testing.
</li
>
5783 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5787 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5788 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5789 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5791 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5792 </pre
></li
>
5793 <li
><p
>Run this as root:
</p
>
5795 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5798 apt-get install freedombox-setup
5799 /usr/lib/freedombox/setup
5800 </pre
></li
>
5801 <li
>Reboot into your freshly created Freedombox.
</li
>
5805 <p
>You can test it on other architectures too, but because the
5806 freedombox-privoxy package is binary, it will only work as intended on
5807 the architectures where I have had time to build the binary and put it
5808 in my APT repository. But do not let this stop you. It is only a
5809 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5811 <p
>Note that by default Freedombox is a DHCP server on the
5812 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5813 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5814 disable
</tt
>" as root.
</p
>
5816 <p
>Please let me know if this works for you, or if you have any
5817 problems. We gather on the IRC channel
5818 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5819 irc.debian.org and the
5820 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5821 mailing list
</a
>.
</p
>
5823 <p
>Once you get your freedombox operational, you can visit
5824 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
5825 welcome screen (dead end - do not be surprised if you are unable to
5826 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
5827 to look at the rest of plinth. The default user is
'admin
' and the
5828 default password is
'secret
'.
</p
>
5833 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
5834 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
5835 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
5836 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
5837 <description><p
>Earlier, I reported about
5838 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
5839 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
5840 told by IBM that the original disk should be thrown away. And as
5841 there no longer was a problem if I bricked the firmware, I decided
5842 today to try to install Intel firmware to replace the Lenovo firmware
5843 currently on the disk.
</p
>
5845 <p
>I searched the Intel site for firmware, and found
5846 <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
>
5847 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
5848 according to the site should contain the latest firmware for SSD
5849 disks. I inserted the broken disk in one of my spare laptops and
5850 booted the ISO from a USB stick. The disk was recognized, but the
5851 program claimed the newest firmware already were installed and refused
5852 to insert any Intel firmware. So no change, and the disk is still
5853 unable to handle write load. :( I guess the only way to get them
5854 working would be if Lenovo releases new firmware. No idea how likely
5855 that is. Anyway, just blogging about this test for completeness. I
5856 got a working Samsung disk, and see no point in spending more time on
5857 the broken disks.
</p
>
5862 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
5863 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
5864 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
5865 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
5866 <description><p
>Today I switched to
5867 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
5868 new laptop
</a
>. I
've previously written about the problems I had with
5869 my new Thinkpad X230, which was delivered with an
5870 <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
5871 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
5872 sustained writes. My hardware supplier have been very forthcoming in
5873 trying to find a solution, and after first trying with another
5874 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5875 disk instead to fix it once and for all. The Samsung disk survived
5876 the installation of Debian with encrypted disks (filling the disk with
5877 random data during installation killed the first two), and I thus
5878 decided to trust it with my data. I have installed it as a Debian Edu
5879 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5880 server at home using Kerberos and LDAP, and will use it as my work
5881 station from now on.
</p
>
5883 <p
>As this is a solid state disk with no moving parts, I believe the
5884 Debian Wheezy default installation need to be tuned a bit to increase
5885 performance and increase life time of the disk. The Linux kernel and
5886 user space applications do not yet adjust automatically to such
5887 environment. To make it easier for my self, I created a draft Debian
5888 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5889 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5890 for the ssd-setup package
</a
> is available from collab-maint, and it
5891 is set up to adjust the setup of the machine by just installing the
5892 package. If there is any non-SSD disk in the machine, the package
5893 will refuse to install, as I did not try to write any logic to sort
5894 file systems in SSD and non-SSD file systems.
</p
>
5896 <p
>I consider the package a draft, as I am a bit unsure how to best
5897 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5898 where I set up the machine with one large encrypted partition (in
5899 addition to /boot), put LVM on top of this and set up partitions on
5900 top of this again. See the README file in the package source for the
5901 references I used to pick the settings. At the moment these
5902 parameters are tuned:
</p
>
5906 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5907 (adding discard to /etc/crypttab)
</li
>
5909 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5910 this case a cryptsetup partition) by changing issue_discards from
5911 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5913 <li
>Set relatime as a file system option for ext3 and ext4 file
5916 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5917 /etc/fstab.
</li
>
5919 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5921 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5922 cron.daily).
</li
>
5924 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5925 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5929 <p
>During installation, I cancelled the part where the installer fill
5930 the disk with random data, as this would kill the SSD performance for
5931 little gain. My goal with the encrypted file system is to ensure
5932 those stealing my laptop end up with a brick and not a working
5933 computer. I have no hope in keeping the really resourceful people
5934 from getting the data on the disk (see
5935 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5936 Thus I concluded that adding the discard option to crypttab is the
5937 right thing to do.
</p
>
5939 <p
>I considered using the noop I/O scheduler, as several recommended
5940 it for SSD, but others recommended deadline and a benchmark I found
5941 indicated that deadline might be better for interactive use.
</p
>
5943 <p
>I also considered using the
'discard
' file system option for ext3
5944 and ext4, but read that it would give a performance hit ever time a
5945 file is removed, and thought it best to that that slowdown once a day
5946 instead of during my work.
</p
>
5948 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5949 this is already done by Debian Edu.
</p
>
5951 <p
>I have not yet started on the user space tuning. I expect
5952 iceweasel need some tuning, and perhaps other applications too, but
5953 have not yet had time to investigate those parts.
</p
>
5955 <p
>The package should work on Ubuntu too, but I have not yet tested it
5958 <p
>As for the answer to the question in the title of this blog post,
5959 as far as I know, the only solution I know about is to replace the
5960 disk. It might be possible to flash it with Intel firmware instead of
5961 the Lenovo firmware. But I have not tried and did not want to do so
5962 without approval from Lenovo as I wanted to keep the warranty on the
5963 disk until a solution was found and they wanted the broken disks
5969 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5970 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5971 <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>
5972 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5973 <description><p
>A few days ago, I wrote about
5974 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5975 problems I experienced with my new X230 and its SSD disk
</a
>, which
5976 was dying during installation because it is unable to cope with
5977 sustained write. My supplier is in contact with
5978 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5979 replacement disk to try to fix the problem. They decided to send an
5980 identical model, so my hopes for a permanent fix was slim.
</p
>
5982 <p
>Anyway, today I got the replacement disk and tried to install
5983 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5984 same firmware version as the original. This time my hope raised
5985 slightly as the installation progressed, as the original disk used to
5986 die after
4-
7% of the disk was written to, while this time it kept
5987 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5988 died again and I was back on square one. I still do not have a new
5989 laptop with a disk I can trust. I can not live with a disk that might
5990 lock up when I download a new
5991 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5992 other large files. I look forward to hearing from my supplier with
5993 the next proposal from Lenovo.
</p
>
5995 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5996 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5997 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5998 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5999 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6000 P/N
45N8295, P0C38732.
</p
>
6002 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
6003 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
6004 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
6005 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
6006 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6007 P/N
45N8295, P0C38732.
</p
>
6009 <p
>The only difference is in the first number (serial number?), ISN,
6010 SA, date and WNPP values. Mentioning all the details here in case
6011 someone is able to use the information to find a way to identify the
6012 failing disk among working ones (if any such working disk actually
6018 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
6019 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
6020 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
6021 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
6022 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
6023 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6024 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
6025 member assosiation NUUG
</a
> and
6026 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
6027 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
6028 Bitraf
</a
>.
</p
>
6030 <p
>It starts
10:
00 and continue until late evening. Everyone is
6031 welcome, and there is no fee to participate. There is on the other
6032 hand limited space, and only room for
30 people. Please put your name
6033 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
6034 wiki page
</a
> if you plan to join us.
</p
>
6039 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
6040 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
6041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
6042 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
6043 <description><p
>Half a year ago, I reported that I had to find a
6044 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
6045 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
6046 time to spend on it, and it took a while to find a model I believe
6047 will do the job, but two days ago the replacement finally arrived. I
6049 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
6050 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6051 a roaming workstation, and it seemed to work flawlessly. But my
6052 second installation with encrypted disk was not as successful. More
6053 on that below.
</p
>
6055 <p
>I had a hard time trying to track down a good laptop, as my most
6056 important requirements (robust and with a good keyboard) are never
6057 listed in the feature list. But I did get good help from the search
6058 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6059 allowed me to limit the list of interesting laptops based on my other
6060 requirements. A bit surprising that SSD disk are not disks according
6061 to that search interface, so I had to drop specifying the number of
6062 disks from my search parameters. I also asked around among friends to
6063 get their impression on keyboards and robustness.
</p
>
6065 <p
>So the new laptop arrived, and it is quite a lot wider than the
6066 X41. I am not quite convinced about the keyboard, as it is
6067 significantly wider than my old keyboard, and I have to stretch my
6068 hand a lot more to reach the edges. But the key response is fairly
6069 good and the individual key shape is fairly easy to handle, so I hope
6070 I will get used to it. My old X40 was starting to fail, and I really
6071 needed a new laptop now. :)
</p
>
6073 <p
>Turning off the touch pad was simple. All it took was a quick
6074 visit to the BIOS during boot it disable it.
</p
>
6076 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
6077 lock up during load. And this happen when installing Debian Wheezy
6078 with encrypted disk, while the disk is being filled with random data.
6079 I also tested to install Ubuntu Raring, and it happen there too if I
6080 reenable the code to fill the disk with random data (it is disabled by
6081 default in Ubuntu). And the bug with is already known. It was
6082 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
6083 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
6084 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6085 kernel developers as
6086 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
6087 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
6088 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6089 Lenovo forums, both for
6090 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
6091 2012-
11-
10</a
> and for
6092 <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
6093 03-
20-
2013</a
>. The problem do not only affect installation. The
6094 reports state that the disk lock up during use if many writes are done
6095 on the disk, so it is much no use to work around the installation
6096 problem and end up with a computer that can lock up at any moment.
6098 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
6099 available
</a
> that will lock up the hard drive after running a few
6100 minutes by writing to a file.
</p
>
6102 <p
>I
've contacted my supplier and asked how to handle this, and after
6103 contacting PCHELP Norway (request
01D1FDP) which handle support
6104 requests for Lenovo, his first suggestion was to upgrade the disk
6105 firmware. Unfortunately there is no newer firmware available from
6106 Lenovo, as my disk already have the most recent one (version LF1i). I
6107 hope to hear more from him today and hope the problem can be
6113 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
6114 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
6115 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
6116 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
6117 <description><p
>Half a year ago, I reported that I had to find a replacement for my
6118 trusty old Thinkpad X41. Unfortunately I did not have much time to
6119 spend on it, but today the replacement finally arrived. I ended up
6120 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
6121 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
6122 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6123 this, it is installing what I hope will be a more final installation,
6124 with a encrypted hard drive to ensure any dope head stealing it end up
6125 with an expencive door stop.
</p
>
6127 <p
>I had a hard time trying to track down a good laptop, as my most
6128 important requirements (robust and with a good keyboard) are never
6129 listed in the feature list. But I did get good help from the search
6130 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6131 allowed me to limit the list of interesting laptops based on my other
6132 requirements. A bit surprising that SSD disk are not disks, so I had
6133 to drop number of disks from my search parameters.
</p
>
6135 <p
>I am not quite convinced about the keyboard, as it is significantly
6136 wider than my old keyboard, and I have to stretch my hand a lot more
6137 to reach the edges. But the key response is fairly good and the
6138 individual key shape is fairly easy to handle, so I hope I will get
6139 used to it. My old X40 was starting to fail, and I really needed a
6140 new laptop now. :)
</p
>
6142 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
6147 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
6148 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
6149 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
6150 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
6151 <description><p
>It annoys me when the computer fail to do automatically what it is
6152 perfectly capable of, and I have to do it manually to get things
6153 working. One such task is to find out what firmware packages are
6154 needed to get the hardware on my computer working. Most often this
6155 affect the wifi card, but some times it even affect the RAID
6156 controller or the ethernet card. Today I pushed version
0.4 of the
6157 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
6158 including a new script isenkram-autoinstall-firmware handling the
6159 process of asking all the loaded kernel modules what firmware files
6160 they want, find debian packages providing these files and install the
6161 debian packages. Here is a test run on my laptop:
</p
>
6163 <p
><pre
>
6164 # isenkram-autoinstall-firmware
6165 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6166 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6167 info: locating packages with the requested firmware files
6168 info: Updating APT sources after adding non-free APT source
6169 info: trying to install firmware-ipw2x00
6172 Preconfiguring packages ...
6173 Selecting previously deselected package firmware-ipw2x00.
6174 (Reading database ...
259727 files and directories currently installed.)
6175 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6176 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
6178 </pre
></p
>
6180 <p
>When all the requested firmware is present, a simple message is
6181 printed instead:
</p
>
6183 <p
><pre
>
6184 # isenkram-autoinstall-firmware
6185 info: did not find any firmware files requested by loaded kernel modules. exiting
6187 </pre
></p
>
6189 <p
>It could use some polish, but it is already working well and saving
6190 me some time when setting up new machines. :)
</p
>
6192 <p
>So, how does it work? It look at the set of currently loaded
6193 kernel modules, and look up each one of them using modinfo, to find
6194 the firmware files listed in the module meta-information. Next, it
6195 download the Contents file from a nearby APT mirror, and search for
6196 the firmware files in this file to locate the package with the
6197 requested firmware file. If the package is in the non-free section, a
6198 non-free APT source is added and the package is installed using
6199 <tt
>apt-get install
</tt
>. The end result is a slightly better working
6202 <p
>I hope someone find time to implement a more polished version of
6203 this script as part of the hw-detect debian-installer module, to
6204 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
6205 #
655507</a
>. There really is no need to insert USB sticks with
6206 firmware during a PXE install when the packages already are available
6207 from the nearby Debian mirror.
</p
>
6212 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
6213 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
6214 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
6215 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
6216 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6217 the screen just turn black when Linux boot, either during installation
6218 or on first boot from the hard disk. I
've seen it once in a while the
6219 last few years, but only recently understood the cause. I
've seen it
6220 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6221 The reason seem to be in the wiring of some laptops. The system to
6222 control the screen background light is inverted, so when Linux try to
6223 turn the brightness fully on, it end up turning it off instead. I do
6224 not know which Linux drivers are affected, but this post is about the
6225 i915 driver used by the
6226 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6227 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
6229 <p
>The problem can be worked around two ways. Either by adding
6230 i915.invert_brightness=
1 as a kernel option, or by adding a file in
6231 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
6232 option when it load the i915 kernel module. On Debian and Ubuntu, it
6233 can be done by running these commands as root:
</p
>
6236 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
6237 update-initramfs -u -k all
6240 <p
>Since March
2012 there is
6241 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
6242 mechanism in the Linux kernel
</a
> to tell the i915 driver which
6243 hardware have this problem, and get the driver to invert the
6244 brightness setting automatically. To use it, one need to add a row in
6245 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
6246 intel_quirks array
</a
> in the driver source
6247 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
6248 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
6249 number (vendor number
8086 is assumed) and subdevice vendor and device
6252 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
6253 -vvnn
</tt
> for the video card in question:
</p
>
6255 <p
><pre
>
6256 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
6257 3rd Gen Core processor Graphics Controller [
8086:
0156] \
6258 (rev
09) (prog-if
00 [VGA controller])
6259 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
6260 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6261 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6262 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
6263 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
6265 Interrupt: pin A routed to IRQ
42
6266 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
6267 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
6268 Region
4: I/O ports at
4000 [size=
64]
6269 Expansion ROM at
<unassigned
> [disabled]
6270 Capabilities:
<access denied
>
6271 Kernel driver in use: i915
6272 </pre
></p
>
6274 <p
>The resulting intel_quirks entry would then look like this:
</p
>
6276 <p
><pre
>
6277 struct intel_quirk intel_quirks[] = {
6279 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6280 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
6283 </pre
></p
>
6285 <p
>According to the kernel module instructions (as seen using
6286 <tt
>modinfo i915
</tt
>), information about hardware needing the
6287 invert_brightness flag should be sent to the
6288 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
6289 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
6290 developers. But my email about the laptop sent
2013-
06-
03 have not
6292 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
6293 web archive for the mailing list
</a
>, so I suspect they do not accept
6294 emails from non-subscribers. Because of this, I sent my patch also to
6295 the Debian bug tracking system instead as
6296 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
6297 sure the patch is not lost.
</p
>
6299 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
6300 with this problem working properly with Linux. If you use Gnome, your
6301 worries should be over at this point. But if you use KDE, there is
6302 something in KDE ignoring the invert_brightness setting and turning on
6303 the screen during login. I
've reported it to Debian as
6304 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
6305 have no idea yet how to figure out exactly what subsystem is doing
6306 this. Perhaps you can help? Perhaps you know what the Gnome
6307 developers did to handle this, and this can give a clue to the KDE
6308 developers? Or you know where in KDE the screen brightness is changed
6309 during login? If so, please update the BTS report (or get in touch if
6310 you do not know how to update BTS).
</p
>
6312 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
6313 acpi_backlight=vendor, to disable ACPI backlight support completely,
6314 as the ACPI information on the machine is trash and it is better to
6315 leave it to the intel video driver to control the screen
6316 backlight.
</p
>
6321 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
6322 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
6323 <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>
6324 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
6325 <description><p
>Two days ago, I asked
6326 <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
6327 I could install Linux on a Packard Bell EasyNote LV computer
6328 preinstalled with Windows
8</a
>. I found a solution, but am horrified
6329 with the obstacles put in the way of Linux users on a laptop with UEFI
6330 and Windows
8.
</p
>
6332 <p
>I never found out if the cause of my problems were the use of UEFI
6333 secure booting or fast boot. I suspect fast boot was the problem,
6334 causing the firmware to boot directly from HD without considering any
6335 key presses and alternative devices, but do not know UEFI settings
6336 enough to tell.
</p
>
6338 <p
>There is no way to install Linux on the machine in question without
6339 opening the box and disconnecting the hard drive! This is as far as I
6340 can tell, the only way to get access to the firmware setup menu
6341 without accepting the Windows
8 license agreement. I am told (and
6342 found description on how to) that it is possible to configure the
6343 firmware setup once booted into Windows
8. But as I believe the terms
6344 of that agreement are completely unacceptable, accepting the license
6345 was never an alternative. I do not enter agreements I do not intend
6346 to follow.
</p
>
6348 <p
>I feared I had to return the laptops and ask for a refund, and
6349 waste many hours on this, but luckily there was a way to get it to
6350 work. But I would not recommend it to anyone planning to run Linux on
6351 it, and I have become sceptical to Windows
8 certified laptops. Is
6352 this the way Linux will be forced out of the market place, by making
6353 it close to impossible for
"normal
" users to install Linux without
6354 accepting the Microsoft Windows license terms? Or at least not
6355 without risking to loose the warranty?
</p
>
6357 <p
>I
've updated the
6358 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
6359 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
6360 do not have to struggle as much as I did to get Linux into the
6363 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6364 Michael Tokarev and others for feedback and ideas.
</p
>
6369 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
6370 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
6371 <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>
6372 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
6373 <description><p
>I
've run into quite a problem the last few days. I bought three
6374 new laptops for my parents and a few others. I bought Packard Bell
6375 Easynote LV to run Kubuntu on and use as their home computer. But I
6376 am completely unable to figure out how to install Linux on it. The
6377 computer is preinstalled with Windows
8, and I suspect it uses UEFI
6378 instead of a BIOS to boot.
</p
>
6380 <p
>The problem is that I am unable to get it to PXE boot, and unable
6381 to get it to boot the Linux installer from my USB stick. I have yet
6382 to try the DVD install, and still hope it will work. when I turn on
6383 the computer, there is no information on what buttons to press to get
6384 the normal boot menu. I expect to get some boot menu to select PXE or
6385 USB stick booting. When booting, it first ask for the language to
6386 use, then for some regional settings, and finally if I will accept the
6387 Windows
8 terms of use. As these terms are completely unacceptable to
6388 me, I have no other choice but to turn off the computer and try again
6389 to get it to boot the Linux installer.
</p
>
6391 <p
>I have gathered my findings so far on a Linlap page about the
6392 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6393 EasyNote LV
</a
> model. If you have any idea how to get Linux
6394 installed on this machine, please get in touch or update that wiki
6395 page. If I can
't find a way to install Linux, I will have to return
6396 the laptop to the seller and find another machine for my parents.
</p
>
6398 <p
>I wonder, is this the way Linux will be forced out of the market
6399 using UEFI and
"secure boot
" by making it impossible to install Linux
6400 on new Laptops?
</p
>
6405 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6406 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6407 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6408 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6409 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6410 an operating system based on Debian intended for use in schools. It
6411 contain a turn-key solution for the computer network provided to
6412 pupils in the primary schools. It provide both the central server,
6413 network boot servers and desktop environments with heaps of
6414 educational software. The project was founded almost
12 years ago,
6415 2001-
07-
02. If you want to support the project, which is in need for
6416 cash to fund developer gatherings and other project related activity,
6417 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6418 donate some money
</a
>.
6420 <p
>A topic that come up again and again on the Debian Edu mailing
6421 lists and elsewhere, is the question on how to transform a Debian or
6422 Ubuntu installation into a Debian Edu installation. It isn
't very
6423 hard, and last week I wrote a script to replicate the steps done by
6424 the Debian Edu installer.
</p
>
6426 <p
>The script,
6427 <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/
>
6428 in the debian-edu-config package, will go through these six steps and
6429 transform an existing Debian Wheezy or Ubuntu (untested) installation
6430 into a Debian Edu Workstation:
</p
>
6434 <li
>Add skolelinux related APT sources.
</li
>
6435 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6436 <li
>Install debian-edu-install to load preseeding values and pull in
6437 our configuration.
</li
>
6438 <li
>Preseed debconf database with profile setup in
6439 /etc/debian-edu/config, and run tasksel to install packages
6440 according to the profile specified in the config above,
6441 overriding some of the Debian automation machinery.
</li
>
6442 <li
>Run debian-edu-cfengine-D installation to configure everything
6443 that could not be done using preseeding.
</li
>
6444 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6448 <p
>There are some steps in the Debian Edu installation that can not be
6449 replicated like this. Disk partitioning and LVM setup, for example.
6450 So this script just assume there is enough disk space to install all
6451 the needed packages.
</p
>
6453 <p
>The script was created to help a Debian Edu student working on
6454 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6455 Debian Edu client, and using it he can take the existing
6456 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6457 transform it into a fully functioning Debian Edu Workstation (or
6458 Roaming Workstation, or whatever :).
</p
>
6460 <p
>The default setting in the script is to create a KDE Workstation.
6461 If a LXDE based Roaming workstation is wanted instead, modify the
6462 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6464 <p
><pre
>
6465 PROFILE=
"Roaming-Workstation
"
6466 DESKTOP=
"lxde
"
6467 </pre
></p
>
6469 <p
>The script could even become useful to set up Debian Edu servers in
6470 the cloud, by starting with a virtual Debian installation at some
6471 virtual hosting service and setting up all the services on first
6477 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6478 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6479 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6480 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6481 <description><P
>In January,
6482 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6483 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6484 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6485 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6486 marvellous construction system from Denmark. We also created
6487 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6488 a place to take notes and write down our plans and hopes. And several
6489 people showed up to help. I was very happy to see the effect of my
6490 call. Since the small start, we have a debtags tag
6491 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6492 tag for LEGO related packages, and now count
10 packages related to
6493 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6495 <p
><table
>
6496 <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
>
6497 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6498 <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
>
6499 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6500 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6501 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6502 <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
>
6503 <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
>
6504 <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
>
6505 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6506 </table
></p
>
6508 <p
>Some of these are available in Wheezy, and all but one are
6509 currently available in Jessie/testing. leocad is so far only
6510 available in experimental.
</p
>
6512 <p
>If you care about LEGO in Debian, please join us on IRC and help
6513 adding the rest of the great free software tools available on Linux
6514 for LEGO designers.
</p
>
6519 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6520 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6522 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6523 <description><p
>When I woke up this morning, I was very happy to see that the
6524 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6525 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6526 Debian release, and I expect to move my machines at home over to it fairly
6529 <p
>The new debian release contain heaps of new stuff, and one program
6530 in particular make me very happy to see included. The
6531 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6532 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6533 included for the first time. Alongside similar programs like
6534 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6535 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6536 it allow for visual programming where syntax errors can not happen,
6537 and a friendly programming environment for learning to control the
6538 computer. Scratch will also be included in the next release of Debian
6541 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6542 Edu/Skolelinux release too. The
6543 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6544 alpha release
</a
> went out last week, and the next should soon
6550 <title>Isenkram
0.2 finally in the Debian archive
</title>
6551 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6552 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6553 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6554 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6555 package
</a
> finally made it into the archive, after lingering in NEW
6556 for many months. I uploaded it to the Debian experimental suite
6557 2013-
01-
27, and today it was accepted into the archive.
</p
>
6559 <p
>Isenkram is a system for suggesting to users what packages to
6560 install to work with a pluggable hardware device. The suggestion pop
6561 up when the device is plugged in. For example if a Lego Mindstorm NXT
6562 is inserted, it will suggest to install the program needed to program
6563 the NXT controller. Give it a go, and report bugs and suggestions to
6569 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6570 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6571 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6572 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6573 <description><p
>My
6574 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6575 bitcoin related blog post
</a
> mentioned that the new
6576 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6577 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6578 2013-
01-
19, and have been available in unstable since then. It was
6579 automatically copied to Ubuntu, and is available in their Raring
6580 version too.
</p
>
6582 <p
>But there is a strange problem with the build that block this new
6583 version from being available on the i386 and kfreebsd-i386
6584 architectures. For some strange reason, the autobuilders in Debian
6585 for these architectures fail to run the test suite on these
6586 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6587 We are so far unable to reproduce it when building it manually, and
6588 no-one have been able to propose a fix. If you got an idea what is
6589 failing, please let us know via the BTS.
</p
>
6591 <p
>One feature that is annoying me with of the bitcoin client, because
6592 I often run low on disk space, is the fact that the client will exit
6593 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6594 #
696715</a
>). So make sure you have enough disk space when you run
6597 <p
>As usual, if you use bitcoin and want to show your support of my
6598 activities, please send Bitcoin donations to my address
6599 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6604 <title>Welcome to the world, Isenkram!
</title>
6605 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6606 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6607 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6608 <description><p
>Yesterday, I
6609 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6610 for testers
</a
> for my prototype for making Debian better at handling
6611 pluggable hardware devices, which I
6612 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6613 out to create
</a
> earlier this month. Several valuable testers showed
6614 up, and caused me to really want to to open up the development to more
6615 people. But before I did this, I want to come up with a sensible name
6616 for this project. Today I finally decided on a new name, and I have
6617 renamed the project from hw-support-handler to this new name. In the
6618 process, I moved the source to git and made it available as a
6619 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6620 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6621 To fetch and build the latest version of the source, use
</p
>
6624 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6625 cd isenkram
&& git-buildpackage -us -uc
6628 <p
>I have not yet adjusted all files to use the new name yet. If you
6629 want to hack on the source or improve the package, please go ahead.
6630 But please talk to me first on IRC or via email before you do major
6631 changes, to make sure we do not step on each others toes. :)
</p
>
6633 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6634 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6635 stuff, in other words. I
've been told it is the Norwegian variant of
6636 the German word eisenkram, for those that are familiar with that
6639 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6640 instructions, to avoid confusing people with an error from the signing
6643 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6644 clone argument to avoid the need for authentication.
</p
>
6649 <title>First prototype ready making hardware easier to use in Debian
</title>
6650 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6651 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6652 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6653 <description><p
>Early this month I set out to try to
6654 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6655 the Debian support for pluggable hardware devices
</a
>. Now my
6656 prototype is working, and it is ready for a larger audience. To test
6658 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6659 from the Debian Edu subversion repository
</a
>, build and install the
6660 package. You might have to log out and in again activate the
6661 autostart script.
</p
>
6663 <p
>The design is simple:
</p
>
6667 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6668 hw-support-handlerd to start when the user log in.
</li
>
6670 <li
>This program listen for kernel events about new hardware (directly
6671 from the kernel like udev does), not using HAL dbus events as I
6672 initially did.
</li
>
6674 <li
>When new hardware is inserted, look up the hardware modalias in
6675 the APT database, a database
6676 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6677 via HTTP
</a
> and a database available as part of the package.
</li
>
6679 <li
>If a package is mapped to the hardware in question, the package
6680 isn
't installed yet and this is the first time the hardware was
6681 plugged in, show a desktop notification suggesting to install the
6682 package or packages.
</li
>
6684 <li
>If the user click on the
'install package now
' button, ask
6685 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6687 <li
>aptdaemon ask for root password or sudo password, and install the
6688 package while showing progress information in a window.
</li
>
6692 <p
>I still need to come up with a better name for the system. Here
6693 are some screen shots showing the prototype in action. First the
6694 notification, then the password request, and finally the request to
6695 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6697 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6698 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6699 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6700 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6701 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6703 <p
>The prototype still need to be improved with longer timeouts, but
6704 is already useful. The database of hardware to package mappings also
6705 need more work. It is currently compatible with the Ubuntu way of
6706 storing such information in the package control file, but could be
6707 changed to use other formats instead or in addition to the current
6708 method. I
've dropped the use of discover for this mapping, as the
6709 modalias approach is more flexible and easier to use on Linux as long
6710 as the Linux kernel expose its modalias strings directly.
</p
>
6712 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6713 here is the command required to check out and build the source: Use
6714 '<tt
>svn checkout
6715 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6716 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6717 devscripts package.
</p
>
6719 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6720 renamed to Isenkram and the source moved from the Debian Edu
6721 subversion repository to a Debian collab-maint git repository. See
6722 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6723 instructions
</a
> for details.
</p
>
6728 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6729 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6730 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6731 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6732 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6733 suddenly in bed. With a quiet whimper, it went completely quiet and
6734 black. The power button was no longer able to turn it on. It was a
6735 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6736 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6737 Compaq I had before that. Now I need to find a replacement. To keep
6738 going during Christmas, I moved the one year old SSD disk to my old
6739 X40 where it fitted (only one I had left that could use it), but it is
6740 not a durable solution.
6742 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6743 got a new one more than
10 years ago. It still holds true.:)
</p
>
6747 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6748 than A4).
</li
>
6749 <li
>Robust, it will be in my backpack every day.
</li
>
6750 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6751 <li
>Long battery life time. Preferable a week.
</li
>
6752 <li
>Internal WIFI network card.
</li
>
6753 <li
>Internal Twisted Pair network card.
</li
>
6754 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6755 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6756 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6758 <li
>Hardware supported by Debian Stable, ie the default kernel and
6759 X.org packages.
</li
>
6760 <li
>Quiet, preferably fan free (or at least not using the fan most of
6765 <p
>You will notice that there are no RAM and CPU requirements in the
6766 list. The reason is simply that the specifications on laptops the
6767 last
10-
15 years have been sufficient for my needs, and I have to look
6768 at other features to choose my laptop. But are there still made as
6769 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6770 robust, and Thinkpads seem to be heading in the wrong direction since
6771 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6772 still be useful.
</p
>
6774 <p
>Perhaps I should rethink my needs, and look for a pad with an
6775 external keyboard? I
'll have to check the
6776 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6777 well-supported laptops, or perhaps just buy one preinstalled from one
6778 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6779 Pre-loaded site
</a
>.
</p
>
6784 <title>How to find a browser plugin supporting a given MIME type
</title>
6785 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6786 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6787 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6788 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6789 install to get support for a given MIME type. Thanks to
6790 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6791 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6792 Unfortunately, not very many packages provide the needed meta
6793 information, Anyway, here is a small script to look up all browser
6794 plugin packages announcing ther MIME support using this specification:
</p
>
6800 def pkgs_handling_mimetype(mimetype):
6805 version = pkg.candidate
6807 version = pkg.installed
6810 record = version.record
6811 if not record.has_key(
'Npp-MimeType
'):
6813 mime_types = record[
'Npp-MimeType
'].split(
',
')
6814 for t in mime_types:
6815 t = t.rstrip().strip()
6817 thepkgs.append(pkg.name)
6819 mimetype =
"audio/ogg
"
6820 if
1 < len(sys.argv):
6821 mimetype = sys.argv[
1]
6822 print
"Browser plugin packages supporting %s:
" % mimetype
6823 for pkg in pkgs_handling_mimetype(mimetype):
6824 print
" %s
" %pkg
6827 <p
>It can be used like this to look up a given MIME type:
</p
>
6830 % ./apt-find-browserplug-for-mimetype
6831 Browser plugin packages supporting audio/ogg:
6833 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
6834 Browser plugin packages supporting application/x-shockwave-flash:
6835 browser-plugin-gnash
6839 <p
>In Ubuntu this mechanism is combined with support in the browser
6840 itself to query for plugins and propose to install the needed
6841 packages. It would be great if Debian supported such feature too. Is
6842 anyone working on adding it?
</p
>
6844 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
6845 request for icweasel support for this feature is
6846 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
6847 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
6848 of manpower and wish for a different design is the reason thus feature
6849 is not yet in iceweasel from Debian.
</p
>
6854 <title>What is the most supported MIME type in Debian?
</title>
6855 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
6856 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
6857 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
6858 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
6859 proposal to add AppStream information to the Debian archive
</a
>, is a
6860 proposal to make it possible for a Desktop application to propose to
6861 the user some package to install to gain support for a given MIME
6862 type, font, library etc. that is currently missing. With such
6863 mechanism in place, it would be possible for the desktop to
6864 automatically propose and install leocad if some LDraw file is
6865 downloaded by the browser.
</p
>
6867 <p
>To get some idea about the current content of the archive, I decided
6868 to write a simple program to extract all .desktop files from the
6869 Debian archive and look up the claimed MIME support there. The result
6871 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
6872 site
</a
>. Using the collected information, it become possible to
6873 answer the question in the title. Here are the
20 most supported MIME
6874 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6875 The complete list is available from the link above.
</p
>
6877 <p
><strong
>Debian Stable:
</strong
></p
>
6881 ----- -----------------------
6897 18 application/x-ogg
6904 <p
><strong
>Debian Testing:
</strong
></p
>
6908 ----- -----------------------
6924 18 application/x-ogg
6931 <p
><strong
>Debian Unstable:
</strong
></p
>
6935 ----- -----------------------
6952 18 application/x-ogg
6958 <p
>I am told that PackageKit can provide an API to access the kind of
6959 information mentioned in DEP-
11. I have not yet had time to look at
6960 it, but hope the PackageKit people in Debian are on top of these
6963 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6964 discovering a typo in my script.
</p
>
6969 <title>Using modalias info to find packages handling my hardware
</title>
6970 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6971 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6972 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6973 <description><p
>Yesterday, I wrote about the
6974 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6975 values provided by the Linux kernel
</a
> following my hope for
6976 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6977 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6978 modalias values attached to package names can be used to map packages
6979 to hardware. This allow the system to look up and suggest relevant
6980 packages when I plug in some new hardware into my machine, and replace
6981 discover and discover-data as the database used to map hardware to
6984 <p
>I create a modaliases file with entries like the following,
6985 containing package name, kernel module name (if relevant, otherwise
6986 the package name) and globs matching the relevant hardware
6989 <p
><blockquote
>
6990 Package: package-name
6991 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6992 </blockquote
></p
>
6994 <p
>It is fairly trivial to write code to find the relevant packages
6995 for a given modalias value using this file.
</p
>
6997 <p
>An entry like this would suggest the video and picture application
6998 cheese for many USB web cameras (interface bus class
0E01):
</p
>
7000 <p
><blockquote
>
7002 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
7003 </blockquote
></p
>
7005 <p
>An entry like this would suggest the pcmciautils package when a
7006 CardBus bridge (bus class
0607) PCI device is present:
</p
>
7008 <p
><blockquote
>
7009 Package: pcmciautils
7010 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7011 </blockquote
></p
>
7013 <p
>An entry like this would suggest the package colorhug-client when
7014 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
7016 <p
><blockquote
>
7017 Package: colorhug-client
7018 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
7019 </blockquote
></p
>
7021 <p
>I believe the format is compatible with the format of the Packages
7022 file in the Debian archive. Ubuntu already uses their Packages file
7023 to store their mappings from packages to hardware.
</p
>
7025 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
7026 announce the hardware it support in a way my prototype understand.
7027 This allow those publishing packages in an APT source outside the
7028 Debian archive as well as those backporting packages to make sure the
7029 hardware mapping are included in the package meta information. I
've
7030 tested such header in the pymissile package, and its modalias mapping
7031 is working as it should with my prototype. It even made it to Ubuntu
7034 <p
>To test if it was possible to look up supported hardware using only
7035 the shell tools available in the Debian installer, I wrote a shell
7036 implementation of the lookup code. The idea is to create files for
7037 each modalias and let the shell do the matching. Please check out and
7039 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
7040 shell script. It run without any extra dependencies and fetch the
7041 hardware mappings from the Debian archive and the subversion
7042 repository where I currently work on my prototype.
</p
>
7044 <p
>When I use it on a machine with a yubikey inserted, it suggest to
7045 install yubikey-personalization:
</p
>
7047 <p
><blockquote
>
7048 % ./hw-support-lookup
7049 <br
>yubikey-personalization
7051 </blockquote
></p
>
7053 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7054 propose to install the pcmciautils package:
</p
>
7056 <p
><blockquote
>
7057 % ./hw-support-lookup
7058 <br
>pcmciautils
7060 </blockquote
></p
>
7062 <p
>If you know of any hardware-package mapping that should be added to
7063 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
7064 database
</a
>, please tell me about it.
</p
>
7066 <p
>It could be possible to generate several of the mappings between
7067 packages and hardware. One source would be to look at packages with
7068 kernel modules, ie packages with *.ko files in /lib/modules/, and
7069 extract their modalias information. Another would be to look at
7070 packages with udev rules, ie packages with files in
7071 /lib/udev/rules.d/, and extract their vendor/model information to
7072 generate a modalias matching rule. I have not tested any of these to
7073 see if it work.
</p
>
7075 <p
>If you want to help implementing a system to let us propose what
7076 packages to install when new hardware is plugged into a Debian
7077 machine, please send me an email or talk to me on
7078 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7083 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
7084 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
7085 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
7086 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
7087 <description><p
>While looking into how to look up Debian packages based on hardware
7088 information, to find the packages that support a given piece of
7089 hardware, I refreshed my memory regarding modalias values, and decided
7090 to document the details. Here are my findings so far, also available
7092 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7093 Debian Edu subversion repository
</a
>:
7095 <p
><strong
>Modalias decoded
</strong
></p
>
7097 <p
>This document try to explain what the different types of modalias
7098 values stands for. It is in part based on information from
7099 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
7100 &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;,
7101 &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
7102 &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;.
7104 <p
>The modalias entries for a given Linux machine can be found using
7105 this shell script:
</p
>
7108 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
7111 <p
>The supported modalias globs for a given kernel module can be found
7112 using modinfo:
</p
>
7115 % /sbin/modinfo psmouse | grep alias:
7116 alias: serio:ty05pr*id*ex*
7117 alias: serio:ty01pr*id*ex*
7121 <p
><strong
>PCI subtype
</strong
></p
>
7123 <p
>A typical PCI entry can look like this. This is an Intel Host
7124 Bridge memory controller:
</p
>
7126 <p
><blockquote
>
7127 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7128 </blockquote
></p
>
7130 <p
>This represent these values:
</p
>
7135 sv
00001028 (subvendor)
7136 sd
000001AD (subdevice)
7138 sc
00 (bus subclass)
7142 <p
>The vendor/device values are the same values outputted from
'lspci
7143 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
7144 0600. The
0600 class is a host bridge. Other useful bus values are
7145 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
7147 <p
>Not sure how to figure out the interface value, nor what it
7150 <p
><strong
>USB subtype
</strong
></p
>
7152 <p
>Some typical USB entries can look like this. This is an internal
7153 USB hub in a laptop:
</p
>
7155 <p
><blockquote
>
7156 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7157 </blockquote
></p
>
7159 <p
>Here is the values included in this alias:
</p
>
7162 v
1D6B (device vendor)
7163 p
0001 (device product)
7165 dc
09 (device class)
7166 dsc
00 (device subclass)
7167 dp
00 (device protocol)
7168 ic
09 (interface class)
7169 isc
00 (interface subclass)
7170 ip
00 (interface protocol)
7173 <p
>The
0900 device class/subclass means hub. Some times the relevant
7174 class is in the interface class section. For a simple USB web camera,
7175 these alias entries show up:
</p
>
7177 <p
><blockquote
>
7178 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7179 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7180 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7181 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7182 </blockquote
></p
>
7184 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
7185 camera),
0101 is audio control device and
0102 is audio streaming (aka
7186 microphone). Thus this is a camera with microphone included.
</p
>
7188 <p
><strong
>ACPI subtype
</strong
></p
>
7190 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
7191 receiver in a Thinkpad X40:
</p
>
7193 <p
><blockquote
>
7194 acpi:IBM0071:PNP0511:
7195 </blockquote
></p
>
7197 <p
>The values between the colons are IDs.
</p
>
7199 <p
><strong
>DMI subtype
</strong
></p
>
7201 <p
>The DMI table contain lots of information about the computer case
7202 and model. This is an entry for a IBM Thinkpad X40, fetched from
7203 /sys/devices/virtual/dmi/id/modalias:
</p
>
7205 <p
><blockquote
>
7206 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7207 </blockquote
></p
>
7209 <p
>The values present are
</p
>
7212 bvn IBM (BIOS vendor)
7213 bvr
1UETB
6WW(
1.66) (BIOS version)
7214 bd
06/
15/
2005 (BIOS date)
7215 svn IBM (system vendor)
7216 pn
2371H4G (product name)
7217 pvr ThinkPadX40 (product version)
7218 rvn IBM (board vendor)
7219 rn
2371H4G (board name)
7220 rvr NotAvailable (board version)
7221 cvn IBM (chassis vendor)
7222 ct
10 (chassis type)
7223 cvr NotAvailable (chassis version)
7226 <p
>The chassis type
10 is Notebook. Other interesting values can be
7227 found in the dmidecode source:
</p
>
7231 4 Low Profile Desktop
7244 17 Main Server Chassis
7245 18 Expansion Chassis
7247 20 Bus Expansion Chassis
7248 21 Peripheral Chassis
7250 23 Rack Mount Chassis
7259 <p
>The chassis type values are not always accurately set in the DMI
7260 table. For example my home server is a tower, but the DMI modalias
7261 claim it is a desktop.
</p
>
7263 <p
><strong
>SerIO subtype
</strong
></p
>
7265 <p
>This type is used for PS/
2 mouse plugs. One example is from my
7266 test machine:
</p
>
7268 <p
><blockquote
>
7269 serio:ty01pr00id00ex00
7270 </blockquote
></p
>
7272 <p
>The values present are
</p
>
7281 <p
>This type is supported by the psmouse driver. I am not sure what
7282 the valid values are.
</p
>
7284 <p
><strong
>Other subtypes
</strong
></p
>
7286 <p
>There are heaps of other modalias subtypes according to
7287 file2alias.c. There is the rest of the list from that source: amba,
7288 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7289 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7290 vmbus, x86cpu and zorro. I did not spend time documenting all of
7291 these, as they do not seem relevant for my intended use with mapping
7292 hardware to packages when new stuff is inserted during run time.
</p
>
7294 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
7296 <p
>To check which kernel modules provide support for a given modalias,
7297 one can use the following shell script:
</p
>
7300 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
7301 echo
"$id
" ; \
7302 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
7306 <p
>The output can look like this (only the first few entries as the
7307 list is very long on my test machine):
</p
>
7311 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
7313 FATAL: Module acpi:device: not found.
7315 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
7316 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
7317 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
7318 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7319 acpi:IBM0071:PNP0511:
7320 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
7321 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
7322 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
7326 <p
>If you want to help implementing a system to let us propose what
7327 packages to install when new hardware is plugged into a Debian
7328 machine, please send me an email or talk to me on
7329 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7331 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
7332 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
7333 in /sys/ with space in them.
</p
>
7338 <title>Moved the pymissile Debian packaging to collab-maint
</title>
7339 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
7340 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
7341 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
7342 <description><p
>As part of my investigation on how to improve the support in Debian
7343 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7344 Launcher and updated the Debian package
7345 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
7346 sure udev will fix the device permissions when it is plugged in. I
7347 also added a
"Modaliases
" header to test it in the Debian archive and
7348 hopefully make the package be proposed by jockey in Ubuntu when a user
7349 plug in his rocket launcher. In the process I moved the source to a
7350 git repository under collab-maint, to make it easier for any DD to
7351 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
7352 is not very active, but the software still work for me even after five
7353 years of relative silence. The new git repository is not listed in
7354 the uploaded package yet, because I want to test the other changes a
7355 bit more before I upload the new version. If you want to check out
7356 the new version with a .desktop file included, visit the
7357 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
7358 view
</a
> or use
"<tt
>git clone
7359 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
7364 <title>Lets make hardware dongles easier to use in Debian
</title>
7365 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
7366 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
7367 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
7368 <description><p
>One thing that annoys me with Debian and Linux distributions in
7369 general, is that there is a great package management system with the
7370 ability to automatically install software packages by downloading them
7371 from the distribution mirrors, but no way to get it to automatically
7372 install the packages I need to use the hardware I plug into my
7373 machine. Even if the package to use it is easily available from the
7374 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7375 suggest to automatically install the python-nxt, nbc and t2n packages
7376 I need to talk to it. When I plug in a Yubikey, it could propose the
7377 yubikey-personalization package. The information required to do this
7378 is available, but no-one have pulled all the pieces together.
</p
>
7380 <p
>Some years ago, I proposed to
7381 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
7382 the discover subsystem to implement this
</a
>. The idea is fairly
7387 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
7388 starting when a user log in.
</li
>
7390 <li
>Set this program up to listen for kernel events emitted when new
7391 hardware is inserted into the computer.
</li
>
7393 <li
>When new hardware is inserted, look up the hardware ID in a
7394 database mapping to packages, and take note of any non-installed
7395 packages.
</li
>
7397 <li
>Show a message to the user proposing to install the discovered
7398 package, and make it easy to install it.
</li
>
7402 <p
>I am not sure what the best way to implement this is, but my
7403 initial idea was to use dbus events to discover new hardware, the
7404 discover database to find packages and
7405 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7408 <p
>Yesterday, I found time to try to implement this idea, and the
7409 draft package is now checked into
7410 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7411 Debian Edu subversion repository
</a
>. In the process, I updated the
7412 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7413 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7414 the relevant packages in Debian, and uploaded a new version
7415 2.2013.01.09 to unstable. I also discovered that the current
7416 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7417 package in Debian no longer discovered any USB devices, because
7418 /proc/bus/usb/devices is no longer present. I ported it to use
7419 libusb as a fall back option to get it working. The fixed package
7420 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7421 because of the freeze).
</p
>
7423 <p
>With this prototype in place, I can insert my Yubikey, and get this
7424 desktop notification to show up (only once, the first time it is
7425 inserted):
</p
>
7427 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7429 <p
>For this prototype to be really useful, some way to automatically
7430 install the proposed packages by pressing the
"Please install
7431 program(s)
" button should to be implemented.
</p
>
7433 <p
>If this idea seem useful to you, and you want to help make it
7434 happen, please help me update the discover-data database with mappings
7435 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7436 list the package you would like to have installed when a given
7437 hardware device is inserted into your computer, and report bugs using
7438 reportbug if it isn
't. Or, if you know of a better way to provide
7439 such mapping, please let me know.
</p
>
7441 <p
>This prototype need more work, and there are several questions that
7442 should be considered before it is ready for production use. Is dbus
7443 the correct way to detect new hardware? At the moment I look for HAL
7444 dbus events on the system bus, because that is the events I could see
7445 on my Debian Squeeze KDE desktop. Are there better events to use?
7446 How should the user be notified? Is the desktop notification
7447 mechanism the best option, or should the background daemon raise a
7448 popup instead? How should packages be installed? When should they
7449 not be installed?
</p
>
7451 <p
>If you want to help getting such feature implemented in Debian,
7452 please send me an email. :)
</p
>
7457 <title>New IRC channel for LEGO designers using Debian
</title>
7458 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7459 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7460 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7461 <description><p
>During Christmas, I have worked a bit on the Debian support for
7462 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7463 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7464 discovered I had to build all the tools myself because none were
7465 already in Debian Squeeze. If Debian support for LEGO is something
7466 you care about, please join me on the IRC channel
7467 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7468 irc.debian.org). There is a lot that could be done to improve the
7469 Debian support for LEGO designers. For example both CAD software
7470 and Mindstorm compilers are missing. :)
</p
>
7472 <p
>Update
2012-
01-
03: A
7473 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7474 including links to Lego related packages is now available.
</p
>
7479 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7480 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7481 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7482 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7483 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7484 year! I hope next year will prove to be a good year.
</p
>
7486 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7487 decentralised
"currency
" that allow people to transfer bitcoins
7488 between each other with minimal overhead, is a very interesting
7489 experiment. And as I wrote a few days ago, the bitcoin situation in
7490 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7491 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7492 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7493 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7494 for one of the ftpmasters to approve the new bitcoin-qt package
7497 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7498 team in Debian, you can easily test the package in Debian Squeeze
7499 using the following steps to get a set of working packages:
</p
>
7501 <blockquote
><pre
>
7502 git clone git://git.debian.org/git/collab-maint/bitcoin
7504 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7505 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7506 </pre
></blockquote
>
7508 <p
>You might have to install some build dependencies as well. The
7509 list of commands should give you two packages, bitcoind and
7510 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7511 client will download the complete set of bitcoin
"blocks
", which need
7512 around
5.6 GiB of data on my machine at the moment. Make sure your
7513 ~/.bitcoin/ directory have lots of spare room if you want to download
7514 all the blocks. The client will warn if the disk is getting full, so
7515 there is not really a problem if you got too little room, but you will
7516 not be able to get all the features out of the client.
</p
>
7518 <p
>As usual, if you use bitcoin and want to show your support of my
7519 activities, please send Bitcoin donations to my address
7520 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7525 <title>A word on bitcoin support in Debian
</title>
7526 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7527 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7528 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7529 <description><p
>It has been a while since I wrote about
7530 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7531 peer-to-peer based crypto-currency, and the reason is simply that I
7532 have been busy elsewhere. But two days ago, I started looking at the
7533 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7534 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7535 is now maintained by a
7536 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7537 people
</a
>, and the grunt work had already been done by this team. We
7538 owe a huge thank you to all these team members. :)
7539 But I was sad to discover that the bitcoin client is missing in
7540 Wheezy. It is only available in Sid (and an outdated client from
7541 backports). The client had several RC bugs registered in BTS blocking
7542 it from entering testing. To try to help the team and improve the
7543 situation, I spent some time providing patches and triaging the bug
7544 reports. I also had a look at the bitcoin package available from Matt
7546 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7547 Ubuntu
</a
>, and moved the useful pieces from that version into the
7548 Debian package.
</p
>
7550 <p
>After checking with the main package maintainer Jonas Smedegaard on
7551 IRC, I pushed several patches into the collab-maint git repository to
7552 improve the package. It now contains fixes for the RC issues (not from
7553 me, but fixed by Scott Howard), build rules for a Qt GUI client
7554 package, konqueror support for the bitcoin: URI and bash completion
7555 setup. As I work on Debian Squeeze, I also created
7556 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7557 patch to backport
</a
> the latest version. Jonas is going to look at
7558 it and try to integrate it into the git repository before uploading a
7559 new version to unstable.
7561 <p
>I would very much like bitcoin to succeed, to get rid of the
7562 centralized control currently exercised in the monetary system. I
7563 find it completely unacceptable that the USA government is collecting
7564 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7565 that the major credit card companies can block legal money
7566 transactions to Wikileaks. But for bitcoin to succeed, more people
7567 need to use bitcoins, and more people need to accept bitcoins when
7568 they sell products and services. Improving the bitcoin support in
7569 Debian is a small step in the right direction, but not enough.
7570 Unfortunately the user experience when browsing the web and wanting to
7571 pay with bitcoin is still not very good. The bitcoin: URI is a step
7572 in the right direction, but need to work in most or every browser in
7573 use. Also the bitcoin-qt client is too heavy to fire up to do a
7574 quick transaction. I believe there are other clients available, but
7575 have not tested them.
</p
>
7578 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7579 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7580 I received
20.15 BTC so far on the address I provided in my blog two
7581 years ago, as can be
7582 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7583 on the blockexplorer service
</a
>. Thank you everyone for your
7584 donation. The blockexplorer service demonstrates quite well that
7585 bitcoin is not quite anonymous and untracked. :) I wonder if the
7586 number of users have gone up since then. If you use bitcoin and want
7587 to show your support of my activity, please send Bitcoin donations to
7588 the same address as last time,
7589 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7594 <title>Git repository for song book for Computer Scientists
</title>
7595 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7596 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7597 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7598 <description><p
>As I
7599 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7600 this summer
</a
>, I have created a Computer Science song book a few
7601 years ago, and today I finally found time to create a public
7602 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7603 repository for the project
</a
>.
</p
>
7605 <p
>If you want to help out, please clone the source and submit patches
7606 to the HTML version. To generate the PDF and PostScript version,
7607 please use prince XML, or let me know about a useful free software
7608 processor capable of creating a good looking PDF from the HTML.
</p
>
7610 <p
>Want to sing? You can still find the song book in HTML, PDF and
7611 PostScript formats at
7612 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7613 Science Songbook
</a
>.
</p
>
7618 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7619 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7620 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7621 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7622 <description><p
>I dag fyller
7623 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7624 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7625 si gratulerer med dagen, Debian!
</p
>
7630 <title>Song book for Computer Scientists
</title>
7631 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7633 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7634 <description><p
>Many years ago, while studying Computer Science at the
7635 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7636 collecting computer related songs for use at parties. The original
7637 version was written in LaTeX, but a few years ago I got help from
7638 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7639 while keeping the ability to create a nice book in PDF format. I have
7640 not had time to maintain the book for a while now, and guess I should
7641 put it up on some public version control repository where others can
7642 help me extend and update the book. If anyone is volunteering to help
7643 me with this, send me an email. Also let me know if there are songs
7644 missing in my book.
</p
>
7646 <p
>I have not mentioned the book on my blog so far, and it occured to
7647 me today that I really should let all my readers share the joys of
7648 singing out load about programming, computers and computer networks.
7649 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7650 12</a
> is about to start (and I am not going). Want to sing? Check
7651 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7652 Computer Science Songbook
</a
>.
7657 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7658 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7660 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7661 <description><p
>At work we have heaps of servers. I believe the total count is
7662 around
1000 at the moment. To be able to get help from the vendors
7663 when something go wrong, we want to keep the firmware on the servers
7664 up to date. If the firmware isn
't the latest and greatest, the
7665 vendors typically refuse to start debugging any problems until the
7666 firmware is upgraded. So before every reboot, we want to upgrade the
7667 firmware, and we would really like everyone handling servers at the
7668 university to do this themselves when they plan to reboot a machine.
7669 For that to happen we at the unix server admin group need to provide
7670 the tools to do so.
</p
>
7672 <p
>To make firmware upgrading easier, I am working on a script to
7673 fetch and install the latest firmware for the servers we got. Most of
7674 our hardware are from Dell and HP, so I have focused on these servers
7675 so far. This blog post is about the Dell part.
</P
>
7677 <p
>On the Dell FTP site I was lucky enough to find
7678 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7679 with firmware information for all
11th generation servers, listing
7680 which firmware should be used on a given model and where on the FTP
7681 site I can find it. Using a simple perl XML parser I can then
7682 download the shell scripts Dell provides to do firmware upgrades from
7683 within Linux and reboot when all the firmware is primed and ready to
7684 be activated on the first reboot.
</p
>
7686 <p
>This is the Dell related fragment of the perl code I am working on.
7687 Are there anyone working on similar tools for firmware upgrading all
7688 servers at a site? Please get in touch and lets share resources.
</p
>
7690 <p
><pre
>
7694 use File::Temp qw(tempdir);
7696 # Install needed RHEL packages if missing
7698 'XML::Simple
' =
> 'perl-XML-Simple
',
7700 for my $module (keys %rhelmodules) {
7701 eval
"use $module;
";
7703 my $pkg = $rhelmodules{$module};
7704 system(
"yum install -y $pkg
");
7705 eval
"use $module;
";
7709 my $errorsto =
'pere@hungry.com
';
7715 sub run_firmware_script {
7716 my ($opts, $script) = @_;
7718 print STDERR
"fail: missing script name\n
";
7721 print STDERR
"Running $script\n\n
";
7723 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7724 print STDERR
"success: firmware script ran succcessfully\n
";
7726 print STDERR
"fail: firmware script returned error\n
";
7730 sub run_firmware_scripts {
7731 my ($opts, @dirs) = @_;
7732 # Run firmware packages
7733 for my $dir (@dirs) {
7734 print STDERR
"info: Running scripts in $dir\n
";
7735 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7736 while (my $s = readdir $dh) {
7737 next if $s =~ m/^\.\.?/;
7738 run_firmware_script($opts,
"$dir/$s
");
7746 print STDERR
"info: Downloading $url\n
";
7747 system(
"wget --quiet \
"$url\
"");
7752 my $product = `dmidecode -s system-product-name`;
7755 if ($product =~ m/PowerEdge/) {
7757 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7758 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7760 my $tmpdir = tempdir(
7764 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7765 system(
'gunzip Catalog.xml.gz
');
7766 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7767 # -q is quiet, disabling interactivity and reducing console output
7768 my $fwopts =
"-q
";
7770 for my $url (@paths) {
7771 fetch_dell_fw($url);
7773 run_firmware_scripts($fwopts, $tmpdir);
7775 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7776 print STDERR
"error: Please report to $errorsto.\n
";
7780 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7781 print STDERR
"error: Please report to $errorsto.\n
";
7787 my $url =
"ftp://ftp.us.dell.com/$path
";
7791 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7792 # firmware packages to download from Dell. Only work for Linux
7793 # machines and
11th generation Dell servers.
7794 sub fetch_dell_fw_list {
7795 my $filename = shift;
7797 my $product = `dmidecode -s system-product-name`;
7799 my ($mybrand, $mymodel) = split(/\s+/, $product);
7801 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7803 my $xml = XMLin($filename);
7805 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7806 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7807 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7809 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7810 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7812 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7814 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7816 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7819 for my $component (@{$xml-
>{SoftwareComponent}}) {
7820 my $componenttype = $component-
>{ComponentType}-
>{value};
7822 # Drop application packages, only firmware and BIOS
7823 next if
'APAC
' eq $componenttype;
7825 my $cpath = $component-
>{path};
7826 for my $path (@paths) {
7827 if ($cpath =~ m%/$path$%) {
7828 push(@paths, $cpath);
7836 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
7837 it could work on other platforms with some tweaking. Anyone know a
7838 index like Catalog.xml is available from HP for HP servers? At the
7839 moment I maintain a similar list manually and it is quickly getting
7845 <title>How is booting into runlevel
1 different from single user boots?
</title>
7846 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
7847 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
7848 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
7849 <description><p
>Wouter Verhelst have some
7850 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
7851 comments and opinions
</a
> on my blog post on
7852 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
7853 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
7854 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
7855 default KDE desktop in Debian
</a
>. I only have time to address one
7856 small piece of his comment now, and though it best to address the
7857 misunderstanding he bring forward:
</p
>
7859 <p
><blockquote
>
7860 Currently, a system admin has four options: [...] boot to a
7861 single-user system (by adding
'single
' to the kernel command line;
7862 this runs rcS and rc1 scripts)
7863 </blockquote
></p
>
7865 <p
>This make me believe Wouter believe booting into single user mode
7866 and booting into runlevel
1 is the same. I am not surprised he
7867 believe this, because it would make sense and is a quite sensible
7868 thing to believe. But because the boot in Debian is slightly broken,
7869 runlevel
1 do not work properly and it isn
't the same as single user
7870 mode. I
'll try to explain what is actually happing, but it is a bit
7871 hard to explain.
</p
>
7873 <p
>Single user mode is defined like this in /etc/inittab:
7874 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7875 executed in single user mode is sulogin. Single user mode is a boot
7876 state
"between
" the runlevels, and when booting into single user mode,
7877 only the scripts in /etc/rcS.d/ are executed before the init process
7878 enters the single user state. When switching to runlevel
1, the state
7879 is in fact not ending in runlevel
1, but it passes through runlevel
1
7880 and end up in the single user mode (see /etc/rc1.d/S03single, which
7881 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7882 1. It is confusing that the
'S
' (single user) init mode is not the
7883 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7886 <p
>This summary might make it clearer. When booting for the first
7887 time into single user mode, the following commands are executed:
7888 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7889 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7890 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7891 trying to continue after visiting single user mode. Not all services
7892 are started again as they should, causing the machine to end up in an
7893 unpredicatble state. This is why Debian admins recommend rebooting
7894 after visiting single user mode.
</p
>
7896 <p
>A similar problem with runlevel
1 is caused by the amount of
7897 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7898 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7899 stopped when passing through the scripts in /etc/rc1.d/, and not
7900 started again when switching away from runlevel
1 to the runlevels
7901 2-
5. I believe the problem is best fixed by moving all the scripts
7902 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7903 functioning single user mode during boot.
</p
>
7905 <p
>I have spent several years investigating the Debian boot system,
7906 and discovered this problem a few years ago. I suspect it originates
7907 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7912 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7913 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7914 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7915 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7916 <description><p
>In the Debian boot system, several packages include scripts that
7917 are started from /etc/rcS.d/. In fact, there is a bite more of them
7918 than make sense, and this causes a few problems. What kind of
7919 problems, you might ask. There are at least two problems. The first
7920 is that it is not possible to recover a machine after switching to
7921 runlevel
1. One need to actually reboot to get the machine back to
7922 the expected state. The other is that single user boot will sometimes
7923 run into problems because some of the subsystems are activated before
7924 the root login is presented, causing problems when trying to recover a
7925 machine from a problem in that subsystem. A minor additional point is
7926 that moving more scripts out of rcS.d/ and into the other rc#.d/
7927 directories will increase the amount of scripts that can run in
7928 parallel during boot, and thus decrease the boot time.
</p
>
7930 <p
>So, which scripts should start from rcS.d/. In short, only the
7931 scripts that _have_ to execute before the root login prompt is
7932 presented during a single user boot should go there. Everything else
7933 should go into the numeric runlevels. This means things like
7934 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7935 the numeric runlevels. Today in Debian, there are around
115 init.d
7936 scripts that are started from rcS.d/, and most of them should be moved
7937 out. Do your package have one of them? Please help us make single
7938 user and runlevel
1 better by moving it.
</p
>
7940 <p
>Scripts setting up the screen, keyboard, system partitions
7941 etc. should still be started from rcS.d/, but there is for example no
7942 need to have the network enabled before the single user login prompt
7943 is presented.
</p
>
7945 <p
>As always, things are not so easy to fix as they sound. To keep
7946 Debian systems working while scripts migrate and during upgrades, the
7947 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7948 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7949 and the next ones can only be moved when their dependencies have been
7950 moved first. This migration must be done sequentially while we ensure
7951 that the package system upgrade packages in the right order to keep
7952 the system state correct. This will require some coordination when it
7953 comes to network related packages, but most of the packages with
7954 scripts that should migrate do not have anything in rcS.d/ depending
7955 on them. Some packages have already been updated, like the sudo
7956 package, while others are still left to do. I wish I had time to work
7957 on this myself, but real live constrains make it unlikely that I will
7958 find time to push this forward.
</p
>
7963 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7964 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7965 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7966 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7967 <description><p
>While at Debconf11, I have several times during discussions
7968 mentioned the issues I believe should be improved in Debian for its
7969 desktop to be useful for more people. The use case for this is my
7970 parents, which are currently running Kubuntu which solve the
7973 <p
>I suspect these four missing features are not very hard to
7974 implement. After all, they are present in Ubuntu, so if we wanted to
7975 do this in Debian we would have a source.
</p
>
7979 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7980 are new packages available for upgrades, a icon in the KDE status bar
7981 indicate this, and clicking on it will activate the simple upgrade
7982 tool to handle it. I have no problem guiding both of my parents
7983 through the process over the phone. If a kernel reboot is required,
7984 this too is indicated by the status bars and the upgrade tool. Last
7985 time I checked, nothing with the same features was working in KDE in
7988 <li
><strong
>Simple handling of missing Firefox browser
7989 plugins.
</strong
> When the browser encounter a MIME type it do not
7990 currently have a handler for, it will ask the user if the system
7991 should search for a package that would add support for this MIME type,
7992 and if the user say yes, the APT sources will be searched for packages
7993 advertising the MIME type in their control file (visible in the
7994 Packages file in the APT archive). If one or more packages are found,
7995 it is a simple click of the mouse to add support for the missing mime
7996 type. If the package require the user to accept some non-free
7997 license, this is explained to the user. The entire process make it
7998 more clear to the user why something do not work in the browser, and
7999 make the chances higher for the user to blame the web page authors and
8000 not the browser for any missing features.
</li
>
8002 <li
><strong
>Simple handling of missing multimedia codec/format
8003 handlers.
</strong
> When the media players encounter a format or codec
8004 it is not supporting, a dialog pop up asking the user if the system
8005 should search for a package that would add support for it. This
8006 happen with things like MP3, Windows Media or H
.264. The selection
8007 and installation procedure is very similar to the Firefox browser
8008 plugin handling. This is as far as I know implemented using a
8009 gstreamer hook. The end result is that the user easily get access to
8010 the codecs that are present from the APT archives available, while
8011 explaining more on why a given format is unsupported by Ubuntu.
</li
>
8013 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
8014 displaying a text/plain file in my Debian browser, it will propose to
8015 start emacs to show it. If I remember correctly, when doing the same
8016 in Kunbutu it show the file as a text file in the browser. At least I
8017 know Opera will show text files within the browser. I much prefer the
8018 latter behaviour.
</li
>
8022 <p
>There are other nice features as well, like the simplified suite
8023 upgrader, but given that I am the one mostly doing the dist-upgrade,
8024 it do not matter much.
</p
>
8026 <p
>I really hope we could get these features in place for the next
8027 Debian release. It would require the coordinated effort of several
8028 maintainers, but would make the end user experience a lot better.
</p
>
8033 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
8034 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
8035 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
8036 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
8037 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
8038 site is build on Debian/Squeeze, and this platform was chosen because
8039 I am most familiar with Debian (being a Debian Developer for around
10
8040 years) because it is the latest stable Debian release which should get
8041 security support for a few years.
</p
>
8043 <p
>The web service is written in Perl, and depend on some perl modules
8044 that are missing in Debian at the moment. It would be great if these
8045 modules were added to the Debian archive, allowing anyone to set up
8046 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
8047 in their own country using only Debian packages. The list of modules
8048 missing in Debian/Squeeze isn
't very long, and I hope the perl group
8049 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
8050 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8051 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8052 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8053 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8054 easier in the future.
</p
>
8056 <p
>Thanks to the great tools in Debian, getting the missing modules
8057 installed on my server was a simple call to
'cpan2deb Module::Name
'
8058 and
'dpkg -i
' to install the resulting package. But this leave me
8059 with the responsibility of tracking security problems, which I really
8060 do not have time for.
</p
>
8065 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
8066 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
8067 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
8068 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
8069 <description><p
>Here is a small update for my English readers. Most of my blog
8070 posts have been in Norwegian the last few weeks, so here is a short
8071 update in English.
</p
>
8073 <p
>The kids still keep me too busy to get much free software work
8074 done, but I did manage to organise a project to get a Norwegian port
8075 of the British service
8076 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
8077 and it has been running for a month now. The entire project has been
8078 organised by me and two others. Around Christmas we gathered sponsors
8079 to fund the development work. In January I drafted a contract with
8080 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
8081 and in February the development took place. Most of it involved
8082 converting the source to use GPS coordinates instead of British
8083 easting/northing, and the resulting code should be a lot easier to get
8084 running in any country by now. The Norwegian
8085 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
8086 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
8087 source and the source for administrative borders in Norway, and
8088 support for this had to be added/fixed.
</p
>
8090 <p
>The Norwegian version went live March
3th, and we spent the weekend
8091 polishing the system before we announced it March
7th. The system is
8092 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
8093 problem reports in a few weeks. Soon we hope to announce the Android
8094 and iPhone versions making it even easier to report problems with the
8095 public infrastructure.
</p
>
8097 <p
>Perhaps something to consider for those of you in countries without
8098 such service?
</p
>
8103 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
8104 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
8105 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
8106 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
8107 <description><p
>The last few days I have looked at ways to track open security
8108 issues here at my work with the University of Oslo. My idea is that
8109 it should be possible to use the information about security issues
8110 available on the Internet, and check our locally
8111 maintained/distributed software against this information. It should
8112 allow us to verify that no known security issues are forgotten. The
8113 CVE database listing vulnerabilities seem like a great central point,
8114 and by using the package lists from Debian mapped to CVEs provided by
8115 the testing security team, I believed it should be possible to figure
8116 out which security holes were present in our free software
8117 collection.
</p
>
8119 <p
>After reading up on the topic, it became obvious that the first
8120 building block is to be able to name software packages in a unique and
8121 consistent way across data sources. I considered several ways to do
8122 this, for example coming up with my own naming scheme like using URLs
8123 to project home pages or URLs to the Freshmeat entries, or using some
8124 existing naming scheme. And it seem like I am not the first one to
8125 come across this problem, as MITRE already proposed and implemented a
8126 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
8127 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
8128 software, hardware and other platform components. The CPE ids are
8129 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
8130 Vulnerability Database
</a
>, allowing me to look up know security
8131 issues for any CPE name. With this in place, all I need to do is to
8132 locate the CPE id for the software packages we use at the university.
8133 This is fairly trivial (I google for
'cve cpe $package
' and check the
8134 NVD entry if a CVE for the package exist).
</p
>
8136 <p
>To give you an example. The GNU gzip source package have the CPE
8137 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
8138 check out, one could look up
8139 <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
8140 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
8141 The most recent one is
8142 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
8143 and at the bottom of the NVD page for this vulnerability the complete
8144 list of affected versions is provided.
</p
>
8146 <p
>The NVD database of CVEs is also available as a XML dump, allowing
8147 for offline processing of issues. Using this dump, I
've written a
8148 small script taking a list of CPEs as input and list all CVEs
8149 affecting the packages represented by these CPEs. One give it CPEs
8150 with version numbers as specified above and get a list of open
8151 security issues out.
</p
>
8153 <p
>Of course for this approach to be useful, the quality of the NVD
8154 information need to be high. For that to happen, I believe as many as
8155 possible need to use and contribute to the NVD database. I notice
8157 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
8158 map from CVE to CPE
</a
>, indicating that they are using the CPE
8159 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
8161 <p
>To get an idea about the quality for free software, I spent some
8162 time making it possible to compare the CVE database from Debian with
8163 the CVE database in NVD. The result look fairly good, but there are
8164 some inconsistencies in NVD (same software package having several
8165 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8166 Debian believe are affected by a CVE). Hope to find time to improve
8167 the quality of NVD, but that require being able to get in touch with
8168 someone maintaining it. So far my three emails with questions and
8169 corrections have not seen any reply, but I hope contact can be
8170 established soon.
</p
>
8172 <p
>An interesting application for CPEs is cross platform package
8173 mapping. It would be useful to know which packages in for example
8174 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8175 this would be trivial if all linux distributions provided CPE entries
8176 for their packages.
</p
>
8181 <title>Which module is loaded for a given PCI and USB device?
</title>
8182 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
8183 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
8184 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
8185 <description><p
>In the
8186 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
8187 package in Debian, there is a script to report useful information
8188 about the running hardware for use when people report missing
8189 information. One part of this script that I find very useful when
8190 debugging hardware problems, is the part mapping loaded kernel module
8191 to the PCI device it claims. It allow me to quickly see if the kernel
8192 module I expect is driving the hardware I am struggling with. To see
8193 the output, make sure discover-data is installed and run
8194 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
8195 one of my machines like this:
</p
>
8199 10de:
03eb i2c_nforce2
8202 10de:
03f0 snd_hda_intel
8211 <p
>The code in question look like this, slightly modified for
8212 readability and to drop the output to file descriptor
3:
</p
>
8215 if [ -d /sys/bus/pci/devices/ ] ; then
8216 echo loaded pci modules:
8218 cd /sys/bus/pci/devices/
8219 for address in * ; do
8220 if [ -d
"$address/driver/module
" ] ; then
8221 module=`cd $address/driver/module ; pwd -P | xargs basename`
8222 if grep -q
"^$module
" /proc/modules ; then
8223 address=$(echo $address |sed s/
0000://)
8224 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
8225 echo
"$id $module
"
8234 <p
>Similar code could be used to extract USB device module
8238 if [ -d /sys/bus/usb/devices/ ] ; then
8239 echo loaded usb modules:
8241 cd /sys/bus/usb/devices/
8242 for address in * ; do
8243 if [ -d
"$address/driver/module
" ] ; then
8244 module=`cd $address/driver/module ; pwd -P | xargs basename`
8245 if grep -q
"^$module
" /proc/modules ; then
8246 address=$(echo $address |sed s/
0000://)
8247 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
8248 if [
"$id
" ] ; then
8249 echo
"$id $module
"
8259 <p
>This might perhaps be something to include in other tools as
8265 <title>How to test if a laptop is working with Linux
</title>
8266 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
8267 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
8268 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
8269 <description><p
>The last few days I have spent at work here at the
<a
8270 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
8271 batch of computers will work with Linux. Every year for the last few
8272 years the university have organised shared bid of a few thousand
8273 computers, and this year HP won the bid. Two different desktops and
8274 five different laptops are on the list this year. We in the UNIX
8275 group want to know which one of these computers work well with RHEL
8276 and Ubuntu, the two Linux distributions we currently handle at the
8277 university.
</p
>
8279 <p
>My test method is simple, and I share it here to get feedback and
8280 perhaps inspire others to test hardware as well. To test, I PXE
8281 install the OS version of choice, and log in as my normal user and run
8282 a few applications and plug in selected pieces of hardware. When
8283 something fail, I make a note about this in the test matrix and move
8284 on. If I have some spare time I try to report the bug to the OS
8285 vendor, but as I only have the machines for a short time, I rarely
8286 have the time to do this for all the problems I find.
</p
>
8288 <p
>Anyway, to get to the point of this post. Here is the simple tests
8289 I perform on a new model.
</p
>
8293 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
8294 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8295 RHEL5 and Debian Edu/Squeeze.
</li
>
8297 <li
>Is X.org working? If the graphical login screen show up after
8298 installation, X.org is working.
</li
>
8300 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
8301 package mesa-utils on Ubuntu) and writing down the frames per second
8302 reported by the program.
</li
>
8304 <li
>Is sound working? With Gnome and KDE, a sound is played when
8305 logging in, and if I can hear this the test is successful. If there
8306 are several audio exits on the machine, I try them all and check if
8307 the Gnome/KDE audio mixer can control where to send the sound. I
8308 normally test this by playing
8309 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
8310 video
</a
> in Firefox/Iceweasel.
</li
>
8312 <li
>Is the USB subsystem working? I test this by plugging in a USB
8313 memory stick and see if Gnome/KDE notices this.
</li
>
8315 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
8316 I have lying around, and see if Gnome/KDE notices this.
</li
>
8318 <li
>Is any built in camera working? Test using cheese, and see if a
8319 picture from the v4l device show up.
</li
>
8321 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8322 any bluetooth devices are discovered. In my office, I normally see a
8325 <li
>For laptops, is the SD or Compaq Flash reader working. I have
8326 memory modules lying around, and stick them in and see if Gnome/KDE
8327 notice this.
</li
>
8329 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
8330 special button work, and if the laptop continue to work after
8333 <li
>For laptops, is the extra buttons working, like audio level,
8334 adjusting background light, switching on/off external video output,
8335 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8336 laptop to laptop, so I just write down which are working and which are
8339 <li
>Some laptops have smart card readers, finger print readers,
8340 acceleration sensors etc. I rarely test these, as I do not know how
8341 to quickly test if they are working or not, so I only document their
8342 existence.
</li
>
8346 <p
>By now I suspect you are really curious what the test results are
8347 for the HP machines I am testing. I
'm not done yet, so I will report
8348 the test results later. For now I can report that HP
8100 Elite work
8349 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
8350 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
8351 can see, I have most machines left to test. One interesting
8352 observation is that Ubuntu Lucid has almost twice the frame rate than
8353 RHEL6 with glxgears. No idea why.
</p
>
8358 <title>Some thoughts on BitCoins
</title>
8359 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
8360 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
8361 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
8362 <description><p
>As I continue to explore
8363 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
8364 what properties the system have, and how it will be affected by laws
8365 and regulations here in Norway. Here are some random notes.
</p
>
8367 <p
>One interesting thing to note is that since the transactions are
8368 verified using a peer to peer network, all details about a transaction
8369 is known to everyone. This means that if a BitCoin address has been
8370 published like I did with mine in my initial post about BitCoin, it is
8371 possible for everyone to see how many BitCoins have been transfered to
8372 that address. There is even a web service to look at the details for
8373 all transactions. There I can see that my address
8374 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
8375 have received
16.06 Bitcoin, the
8376 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
8377 address of Simon Phipps have received
181.97 BitCoin and the address
8378 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
8379 of EFF have received
2447.38 BitCoins so far. Thank you to each and
8380 every one of you that donated bitcoins to support my activity. The
8381 fact that anyone can see how much money was transfered to a given
8382 address make it more obvious why the BitCoin community recommend to
8383 generate and hand out a new address for each transaction. I
'm told
8384 there is no way to track which addresses belong to a given person or
8385 organisation without the person or organisation revealing it
8386 themselves, as Simon, EFF and I have done.
</p
>
8388 <p
>In Norway, and in most other countries, there are laws and
8389 regulations limiting how much money one can transfer across the border
8390 without declaring it. There are money laundering, tax and accounting
8391 laws and regulations I would expect to apply to the use of BitCoin.
8392 If the Skolelinux foundation
8393 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
8394 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
8395 normal bank transfers like EFF is doing, how should this be accounted?
8396 Given that it is impossible to know if money can cross the border or
8397 not, should everything or nothing be declared? What exchange rate
8398 should be used when calculating taxes? Would receivers have to pay
8399 income tax if the foundation were to pay Skolelinux contributors in
8400 BitCoin? I have no idea, but it would be interesting to know.
</p
>
8402 <p
>For a currency to be useful and successful, it must be trusted and
8403 accepted by a lot of users. It must be possible to get easy access to
8404 the currency (as a wage or using currency exchanges), and it must be
8405 easy to spend it. At the moment BitCoin seem fairly easy to get
8406 access to, but there are very few places to spend it. I am not really
8407 a regular user of any of the vendor types currently accepting BitCoin,
8408 so I wonder when my kind of shop would start accepting BitCoins. I
8409 would like to buy electronics, travels and subway tickets, not herbs
8410 and books. :) The currency is young, and this will improve over time
8411 if it become popular, but I suspect regular banks will start to lobby
8412 to get BitCoin declared illegal if it become popular. I
'm sure they
8413 will claim it is helping fund terrorism and money laundering (which
8414 probably would be true, as is any currency in existence), but I
8415 believe the problems should be solved elsewhere and not by blaming
8416 currencies.
</p
>
8418 <p
>The process of creating new BitCoins is called mining, and it is
8419 CPU intensive process that depend on a bit of luck as well (as one is
8420 competing against all the other miners currently spending CPU cycles
8421 to see which one get the next lump of cash). The
"winner
" get
50
8422 BitCoin when this happen. Yesterday I came across the obvious way to
8423 join forces to increase ones changes of getting at least some coins,
8424 by coordinating the work on mining BitCoins across several machines
8425 and people, and sharing the result if one is lucky and get the
50
8427 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8428 if this sounds interesting. I have not had time to try to set up a
8429 machine to participate there yet, but have seen that running on ones
8430 own for a few days have not yield any BitCoins througth mining
8433 <p
>Update
2010-
12-
15: Found an
<a
8434 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8435 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8436 it was interesting to read. The arguments presented seem to be
8437 equally valid for gold, which was used as a currency for many years.
</p
>
8442 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8443 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8444 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8445 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8446 <description><p
>With this weeks lawless
8447 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8448 attacks
</a
> on Wikileak and
8449 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8450 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8451 not be trusted to handle money transactions.
8453 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8454 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8455 mine mentioned earlier. I decided to follow Simon
's example, and get
8456 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8457 some help from my friend to get it all running, and he even handed me
8458 some bitcoins to get started. I even donated a few bitcoins to Simon
8459 for helping me remember BitCoin.
</p
>
8461 <p
>So, what is bitcoins, you probably wonder? It is a digital
8462 crypto-currency, decentralised and handled using peer-to-peer
8463 networks. It allows anonymous transactions and prohibits central
8464 control over the transactions, making it impossible for governments
8465 and companies alike to block donations and other transactions. The
8466 source is free software, and while the key dependency wxWidgets
2.9
8467 for the graphical user interface is missing in Debian, the command
8468 line client builds just fine. Hopefully Jonas
8469 <a href=
"http://bugs.debian.org/
578157">will get the package into
8470 Debian
</a
> soon.
</p
>
8472 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8473 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8474 bitcoins
</a
> when selling services and goods, and there are even
8475 currency
"stock
" markets where the exchange rate is decided. There
8476 are not many users so far, but the concept seems promising. If you
8477 want to get started and lack a friend with any bitcoins to spare,
8479 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8480 bitcoin at the time of writing). Use
8481 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8482 on the current exchange rates.
</p
>
8484 <p
>As an experiment, I have decided to set up bitcoind on one of my
8485 machines. If you want to support my activity, please send Bitcoin
8486 donations to the address
8487 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8492 <title>Why isn
't Debian Edu using VLC?
</title>
8493 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8494 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8495 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8496 <description><p
>In the latest issue of Linux Journal, the readers choices were
8497 presented, and the winner among the multimedia player were VLC.
8498 Personally, I like VLC, and it is my player of choice when I first try
8499 to play a video file or stream. Only if VLC fail will I drag out
8500 gmplayer to see if it can do better. The reason is mostly the failure
8501 model and trust. When VLC fail, it normally pop up a error message
8502 reporting the problem. When mplayer fail, it normally segfault or
8503 just hangs. The latter failure mode drain my trust in the program.
<p
>
8505 <p
>But even if VLC is my player of choice, we have choosen to use
8506 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8507 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8508 plugin to play web videos seamlessly, and the VLC browser plugin is
8509 not very good. For example, it lack in-line control buttons, so there
8510 is no way for the user to pause the video. Also, when I
8511 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8512 tested the browser plugins
</a
> available in Debian, the VLC plugin
8513 failed on several video pages where mplayer based plugins worked. If
8514 the browser plugin for VLC was as good as the gecko-mediaplayer
8515 package (which uses mplayer), we would switch.
</P
>
8517 <p
>While VLC is a good player, its user interface is slightly
8518 annoying. The most annoying feature is its inconsistent use of
8519 keyboard shortcuts. When the player is in full screen mode, its
8520 shortcuts are different from when it is playing the video in a window.
8521 For example, space only work as pause when in full screen mode. I
8522 wish it had consisten shortcuts and that space also would work when in
8523 window mode. Another nice shortcut in gmplayer is [enter] to restart
8524 the current video. It is very nice when playing short videos from the
8525 web and want to restart it when new people arrive to have a look at
8526 what is going on.
</p
>
8531 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8532 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8533 <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>
8534 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8535 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8536 upgrade testing of the
8537 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8538 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8539 This seem like a very good idea, so I adjusted by test scripts and
8540 can now present the updated result from today:
</p
>
8542 <p
>This is for Gnome:
</p
>
8544 <p
>Installed using apt-get, missing with aptitude
</p
>
8546 <blockquote
><p
>
8551 browser-plugin-gnash
8558 freedesktop-sound-theme
8560 gconf-defaults-service
8575 gnome-desktop-environment
8579 gnome-session-canberra
8584 gstreamer0.10-fluendo-mp3
8590 libapache2-mod-dnssd
8593 libaprutil1-dbd-sqlite3
8596 libboost-date-time1.42
.0
8597 libboost-python1.42
.0
8598 libboost-thread1.42
.0
8600 libchamplain-gtk-
0.4-
0
8602 libclutter-gtk-
0.10-
0
8609 libfreerdp-plugins-standard
8624 libgnomepanel2.24-cil
8629 libgtksourceview2.0-common
8630 libmono-addins-gui0.2-cil
8631 libmono-addins0.2-cil
8632 libmono-cairo2.0-cil
8633 libmono-corlib2.0-cil
8634 libmono-i18n-west2.0-cil
8635 libmono-posix2.0-cil
8636 libmono-security2.0-cil
8637 libmono-sharpzip2.84-cil
8638 libmono-system2.0-cil
8641 libndesk-dbus-glib1.0-cil
8642 libndesk-dbus1.0-cil
8652 libtelepathy-farsight0
8661 nautilus-sendto-empathy
8665 python-aptdaemon-gtk
8667 python-beautifulsoup
8682 python-gtksourceview2
8693 python-pkg-resources
8700 python-twisted-conch
8706 python-zope.interface
8711 rhythmbox-plugin-cdrecorder
8718 system-config-printer-udev
8720 telepathy-mission-control-
5
8731 </p
></blockquote
>
8733 <p
>Installed using apt-get, removed with aptitude
</p
>
8735 <blockquote
><p
>
8741 fast-user-switch-applet
8760 libgtksourceview2.0-
0
8762 libsdl1.2debian-alsa
8768 system-config-printer
8773 </p
></blockquote
>
8775 <p
>Installed using aptitude, missing with apt-get
</p
>
8777 <blockquote
><p
>
8778 gstreamer0.10-gnomevfs
8779 </p
></blockquote
>
8781 <p
>Installed using aptitude, removed with apt-get
</p
>
8783 <blockquote
><p
>
8785 </p
></blockquote
>
8787 <p
>This is for KDE:
</p
>
8789 <p
>Installed using apt-get, missing with aptitude
</p
>
8791 <blockquote
><p
>
8793 </p
></blockquote
>
8795 <p
>Installed using apt-get, removed with aptitude
</p
>
8797 <blockquote
><p
>
8800 </p
></blockquote
>
8802 <p
>Installed using aptitude, missing with apt-get
</p
>
8804 <blockquote
><p
>
8818 kdeartwork-emoticons
8820 kdeartwork-theme-icon
8824 kdebase-workspace-bin
8825 kdebase-workspace-data
8839 kscreensaver-xsavers
8854 plasma-dataengines-workspace
8856 plasma-desktopthemes-artwork
8857 plasma-runners-addons
8858 plasma-scriptengine-googlegadgets
8859 plasma-scriptengine-python
8860 plasma-scriptengine-qedje
8861 plasma-scriptengine-ruby
8862 plasma-scriptengine-webkit
8863 plasma-scriptengines
8864 plasma-wallpapers-addons
8865 plasma-widget-folderview
8866 plasma-widget-networkmanagement
8870 xscreensaver-data-extra
8872 xscreensaver-gl-extra
8873 xscreensaver-screensaver-bsod
8874 </p
></blockquote
>
8876 <p
>Installed using aptitude, removed with apt-get
</p
>
8878 <blockquote
><p
>
8880 google-gadgets-common
8898 libggadget-qt-
1.0-
0b
8903 libkonqsidebarplugin4a
8912 libplasma-geolocation-interface4
8914 libplasmagenericshell4
8928 libsmokeknewstuff2-
3
8929 libsmokeknewstuff3-
3
8931 libsmokektexteditor3
8939 libsmokeqtnetwork4-
3
8945 libsmokeqtuitools4-
3
8957 plasma-dataengines-addons
8958 plasma-scriptengine-superkaramba
8959 plasma-widget-lancelot
8960 plasma-widgets-addons
8961 plasma-widgets-workspace
8965 update-notifier-common
8966 </p
></blockquote
>
8968 <p
>Running apt-get autoremove made the results using apt-get and
8969 aptitude a bit more similar, but there are still quite a lott of
8970 differences. I have no idea what packages should be installed after
8971 the upgrade, but hope those that do can have a look.
</p
>
8976 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8977 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8978 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8979 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8980 <description><p
>Most of the computers in use by the
8981 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8982 are virtual machines. And they have been Xen machines running on a
8983 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8984 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8985 bit harder that it could have been, because we set up the Xen virtual
8986 machines to get the virtual partitions from LVM, which as far as I
8987 know is not supported by KVM. So to migrate, we had to convert
8988 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8991 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8992 nice recipe
</a
> to do this, and wrote the following script to do the
8993 migration. It uses qemu-img from the qemu package to make the disk
8994 image, parted to partition it, losetup and kpartx to present the disk
8995 image partions as devices, and dd to copy the data. I NFS mounted the
8996 new servers storage area on the old server to do the migration.
</p
>
9002 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9007 if [ -z
"$
1" ] ; then
9008 echo
"Usage: $
0 &lt;hostname
&gt;
"
9014 if [ ! -e /dev/vg_data/$host-disk ] ; then
9015 echo
"error: unable to find LVM volume for $host
"
9019 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9020 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9021 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9022 totalsize=$(( ( $disksize + $swapsize ) ))
9025 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
9026 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9028 parted $img mklabel msdos
9029 parted $img mkpart primary linux-swap
0 $disksize
9030 parted $img mkpart primary ext2 $disksize $totalsize
9031 parted $img set
1 boot on
9034 losetup /dev/loop0 $img
9035 kpartx -a /dev/loop0
9037 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
9038 fsck.ext3 -f /dev/mapper/loop0p1 || true
9039 mkswap /dev/mapper/loop0p2
9041 kpartx -d /dev/loop0
9042 losetup -d /dev/loop0
9045 <p
>The script is perhaps so simple that it is not copyrightable, but
9046 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
9048 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
9049 the new disk image attached, installed grub-pc and linux-image-
686 and
9050 set up grub to boot from the disk image. After this, the KVM machines
9051 seem to work just fine.
</p
>
9056 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
9057 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
9058 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
9059 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
9060 <description><p
>I
'm still running upgrade testing of the
9061 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
9062 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
9063 status. Here is a short update based on a test I ran
20101118.
</p
>
9065 <p
>I still do not know what a correct migration should look like, so I
9066 report any differences between apt and aptitude and hope someone else
9067 can see if anything should be changed.
</p
>
9069 <p
>This is for Gnome:
</p
>
9071 <p
>Installed using apt-get, missing with aptitude
</p
>
9073 <blockquote
><p
>
9074 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9075 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
9076 dmz-cursor-theme empathy empathy-common finger
9077 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9078 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9079 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9080 gnome-cards-data gnome-codec-install gnome-core
9081 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9082 gnome-search-tool gnome-session-canberra gnome-spell
9083 gnome-system-log gnome-themes-extras gnome-themes-more
9084 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9085 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9086 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9087 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9088 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
9089 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
9090 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
9091 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
9092 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
9093 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9094 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
9095 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9096 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9097 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9098 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9099 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9100 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9101 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9102 libmono-security2.0-cil libmono-sharpzip2.84-cil
9103 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
9104 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
9105 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
9106 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
9107 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
9108 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
9109 libxalan2-java libxerces2-java media-player-info mesa-utils
9110 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
9111 nautilus-sendto-empathy openoffice.org-writer2latex
9112 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
9113 python-aptdaemon python-aptdaemon-gtk python-axiom
9114 python-beautifulsoup python-bugbuddy python-clientform
9115 python-coherence python-configobj python-crypto python-cupshelpers
9116 python-cupsutils python-eggtrayicon python-elementtree
9117 python-epsilon python-evolution python-feedparser python-gdata
9118 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9119 python-gtksourceview2 python-httplib2 python-louie python-mako
9120 python-markupsafe python-mechanize python-nevow python-notify
9121 python-opengl python-openssl python-pam python-pkg-resources
9122 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9123 python-tagpy python-twisted-bin python-twisted-conch
9124 python-twisted-core python-twisted-web python-utidylib python-webkit
9125 python-xdg python-zope.interface remmina remmina-plugin-data
9126 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9127 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9128 software-center svgalibg1 system-config-printer-udev
9129 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
9130 totem totem-coherence totem-mozilla totem-plugins
9131 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9133 </p
></blockquote
>
9135 Installed using apt-get, removed with aptitude
9137 <blockquote
><p
>
9138 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9139 epiphany-extensions epiphany-gecko evolution-exchange
9140 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9141 gedit-common gnome-app-install gnome-games gnome-games-data
9142 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9143 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9144 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9145 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
9146 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
9147 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
9148 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
9149 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9150 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9151 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9152 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
9153 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
9154 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9155 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9156 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9157 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9158 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
9159 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
9160 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
9161 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
9162 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
9163 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9164 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9165 sound-juicer swfdec-gnome system-config-printer totem-common
9166 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9167 </p
></blockquote
>
9169 <p
>Installed using aptitude, missing with apt-get
</p
>
9171 <blockquote
><p
>
9172 gstreamer0.10-gnomevfs
9173 </p
></blockquote
>
9175 <p
>Installed using aptitude, removed with apt-get
</p
>
9177 <blockquote
><p
>
9179 </p
></blockquote
>
9181 <p
>This is for KDE:
</p
>
9183 <p
>Installed using apt-get, missing with aptitude
</p
>
9185 <blockquote
><p
>
9186 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
9187 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9188 ghostscript-x git gnome-audio gnugo granatier gs-common
9189 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9190 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9191 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9192 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9193 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9194 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9195 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9196 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9197 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9198 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9199 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9200 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
9201 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9202 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9203 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9204 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9205 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9206 libkrossui4 libmailtools-perl libmime-tools-perl
9207 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9208 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9209 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9210 lirc luatex marble networkstatus noatun-plugins
9211 openoffice.org-writer2latex palapeli palapeli-data parley
9212 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9213 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9214 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9216 </p
></blockquote
>
9218 <p
>Installed using apt-get, removed with aptitude
</p
>
9220 <blockquote
><p
>
9221 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9222 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9223 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9224 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9225 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9226 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9227 kitchensync kiten kjumpingcube klatin klettres klickety klines
9228 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9229 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9230 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9231 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9232 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9233 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9234 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9235 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9236 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9237 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
9238 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
9239 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9240 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
9241 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
9242 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9243 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9244 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9245 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9246 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9247 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9248 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
9249 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
9250 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9251 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9252 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9253 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9254 </p
></blockquote
>
9256 <p
>Installed using aptitude, missing with apt-get
</p
>
9258 <blockquote
><p
>
9259 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9260 kdeartwork kdebase kdebase-apps kdebase-workspace
9261 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9262 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9263 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9264 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9265 xscreensaver-screensaver-bsod
9266 </p
></blockquote
>
9268 <p
>Installed using aptitude, removed with apt-get
</p
>
9270 <blockquote
><p
>
9271 kdebase-bin konq-plugins konqueror
9272 </p
></blockquote
>
9277 <title>Gnash buildbot slave and Debian kfreebsd
</title>
9278 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
9279 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
9280 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
9281 <description><p
>Answering
9282 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
9283 call from the Gnash project
</a
> for
9284 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
9285 current source, I have set up a virtual KVM machine on the Debian
9286 Edu/Skolelinux virtualization host to test the git source on
9287 Debian/Squeeze. I hope this can help the developers in getting new
9288 releases out more often.
</p
>
9290 <p
>As the developers want less main-stream build platforms tested to,
9291 I have considered setting up a
<a
9292 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
9293 machine as well. I have also considered using the kfreebsd
9294 architecture in Debian as a file server in NUUG to get access to the
5
9295 TB zfs volume we currently use to store DV video. Because of this, I
9296 finally got around to do a test installation of Debian/Squeeze with
9297 kfreebsd. Installation went fairly smooth, thought I noticed some
9298 visual glitches in the cdebconf dialogs (black cursor left on the
9299 screen at random locations). Have not gotten very far with the
9300 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9301 fatal problem. Have to spend some more time on it to see if it is
9302 useful as a file server for NUUG. Will try to find time to set up a
9303 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
9308 <title>Debian in
3D
</title>
9309 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
9310 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
9311 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
9312 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
9314 <p
>3D printing is just great. I just came across this Debian logo in
9316 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
9317 thingiverse blog
</a
>.
</p
>
9322 <title>Software updates
2010-
10-
24</title>
9323 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
9324 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
9325 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
9326 <description><p
>Some updates.
</p
>
9328 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
9329 raise money for the project is going well. The lower limit of
10
9330 signers was reached in
24 hours, and so far
13 people have signed it.
9331 More signers and more funding is most welcome, and I am really curious
9332 how far we can get before the time limit of December
24 is reached.
9335 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
9336 about what appear to be a great code coverage tool capable of
9337 generating code coverage stats without any changes to the source code.
9339 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
9340 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
9341 It is missing in Debian, but the git source built just fine in Squeeze
9342 after I installed libelf-dev, libdwarf-dev, pkg-config and
9343 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9344 solvable. I hope kcov make it into Debian soon.
</p
>
9346 <p
>Finally found time to wrap up the release notes for
<a
9347 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
9348 new alpha release of Debian Edu
</a
>, and just published the second
9349 alpha test release of the Squeeze based Debian Edu /
9350 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
9351 release. Give it a try if you need a complete linux solution for your
9352 school, including central infrastructure server, workstations, thin
9353 client servers and diskless workstations. A nice touch added
9354 yesterday is RDP support on the thin client servers, for windows
9355 clients to get a Linux desktop on request.
</p
>
9360 <title>Some notes on Flash in Debian and Debian Edu
</title>
9361 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
9362 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
9363 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
9364 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
9365 popularity-contest numbers
</a
>, the adobe-flashplugin package the
9366 second most popular used package that is missing in Debian. The sixth
9367 most popular is flashplayer-mozilla. This is a clear indication that
9368 working flash is important for Debian users. Around
10 percent of the
9369 users submitting data to popcon.debian.org have this package
9370 installed.
</p
>
9372 <p
>In the report written by Lars Risan in August
2008
9373 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
9374 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9375 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
9376 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
9377 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
9378 web sites require Flash to work, and lacking working Flash support in
9379 the web browser and the problems with installing it was perceived as a
9380 good reason to stay with Windows.
</p
>
9382 <p
>I once saw a funny and sad comment in a web forum, where Linux was
9383 said to be the retarded cousin that did not really understand
9384 everything you told him but could work fairly well. This was a
9385 comment regarding the problems Linux have with proprietary formats and
9386 non-standard web pages, and is sad because it exposes a fairly common
9387 understanding of whose fault it is if web pages that only work in for
9388 example Internet Explorer
6 fail to work on Firefox, and funny because
9389 it explain very well how annoying it is for users when Linux
9390 distributions do not work with the documents they receive or the web
9391 pages they want to visit.
</p
>
9393 <p
>This is part of the reason why I believe it is important for Debian
9394 and Debian Edu to have a well working Flash implementation in the
9395 distribution, to get at least popular sites as Youtube and Google
9396 Video to working out of the box. For Squeeze, Debian have the chance
9397 to include the latest version of Gnash that will make this happen, as
9398 the new release
0.8.8 was published a few weeks ago and is resting in
9399 unstable. The new version work with more sites that version
0.8.7.
9400 The Gnash maintainers have asked for a freeze exception, but the
9401 release team have not had time to reply to it yet. I hope they agree
9402 with me that Flash is important for the Debian desktop users, and thus
9403 accept the new package into Squeeze.
</p
>
9408 <title>Circular package dependencies harms apt recovery
</title>
9409 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9410 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9411 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9412 <description><p
>I discovered this while doing
9413 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9414 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9415 in Debian still got circular dependencies, and it is often claimed
9416 that apt and aptitude should be able to handle this just fine, but
9417 some times these dependency loops causes apt to fail.
</p
>
9419 <p
>An example is from todays
9420 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9421 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9422 causes perl-modules to fail to upgrade. The cause is simple. If a
9423 package fail to unpack, then only part of packages with the circular
9424 dependency might end up being unpacked when unpacking aborts, and the
9425 ones already unpacked will fail to configure in the recovery phase
9426 because its dependencies are unavailable.
</p
>
9428 <p
>In this log, the problem manifest itself with this error:
</p
>
9430 <blockquote
><pre
>
9431 dpkg: dependency problems prevent configuration of perl-modules:
9432 perl-modules depends on perl (
>=
5.10.1-
1); however:
9433 Version of perl on system is
5.10.0-
19lenny
2.
9434 dpkg: error processing perl-modules (--configure):
9435 dependency problems - leaving unconfigured
9436 </pre
></blockquote
>
9438 <p
>The perl/perl-modules circular dependency is already
9439 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9440 hopefully be solved as soon as possible, but it is not the only one,
9441 and each one of these loops in the dependency tree can cause similar
9442 failures. Of course, they only occur when there are bugs in other
9443 packages causing the unpacking to fail, but it is rather nasty when
9444 the failure of one package causes the problem to become worse because
9445 of dependency loops.
</p
>
9448 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9449 tireless effort by Bill Allombert
</a
>, the number of circular
9451 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9452 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9454 <p
>Todays testing also exposed a bug in
9455 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9456 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9457 apt-get and aptitude, the latter possibly caused by some circular
9458 dependency. Reported both to BTS to try to get someone to look at
9464 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9465 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9466 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9467 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9468 <description><p
>This is a
9469 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9471 <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
9473 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9474 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9476 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9477 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9478 and dhcp3-server-ldap in Debian use the LDAP server. The two
9479 implementations are quite different in how they use LDAP.
</p
>
9481 To get this information, I started slapd with debugging enabled and
9482 dumped the debug output to a file to get the LDAP searches performed
9483 on a Debian Edu main-server. Here is a summary.
9485 <p
><strong
>powerdns
</strong
></p
>
9487 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9488 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9491 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9492 One
"strict
" mode where the forward and reverse DNS lookups are done
9493 using the same LDAP objects, and a
"tree
" mode where the forward and
9494 reverse entries are in two different subtrees in LDAP with a structure
9495 based on the DNS names, as in tjener.intern and
9496 2.2.0.10.in-addr.arpa.
</p
>
9498 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9499 base, and uses a
"base
" scoped search for the DNS name by adding
9500 "dc=tjener,dc=intern,
" to the base with a filter for
9501 "(associateddomain=tjener.intern)
" for the forward entry and
9502 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9503 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9504 forward entries, it is looking for attributes named dnsttl, arecord,
9505 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9506 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9507 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9508 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9509 spfrecord and modifytimestamp. For reverse entries it is looking for
9510 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9511 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9512 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9513 ldapsearch commands could look like this:
</p
>
9515 <blockquote
><pre
>
9516 ldapsearch -h ldap \
9517 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9518 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9519 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9520 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9521 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9522 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9524 ldapsearch -h ldap \
9525 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9526 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9527 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9528 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9529 srvrecord naptrrecord modifytimestamp
9530 </pre
></blockquote
>
9532 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9533 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9534 example LDAP objects used there. In addition to these objects, the
9535 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9536 also exist.
</p
>
9538 <blockquote
><pre
>
9539 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9541 objectclass: dnsdomain
9542 objectclass: domainrelatedobject
9545 associateddomain: tjener.intern
9547 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9549 objectclass: dnsdomain2
9550 objectclass: domainrelatedobject
9552 ptrrecord: tjener.intern
9553 associateddomain:
2.2.0.10.in-addr.arpa
9554 </pre
></blockquote
>
9556 <p
>In strict mode, the server behaves differently. When looking for
9557 forward DNS entries, it is doing a
"subtree
" scoped search with the
9558 same base as in the tree mode for a object with filter
9559 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9560 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9561 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9562 naptrrecord and modifytimestamp. For reverse entires it also do a
9563 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9564 and the requested attributes are associateddomain, dnsttl and
9565 modifytimestamp. In short, in strict mode the objects with ptrrecord
9566 go away, and the arecord attribute in the forward object is used
9569 <p
>The forward and reverse searches can be simulated using ldapsearch
9570 like this:
</p
>
9572 <blockquote
><pre
>
9573 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9574 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9575 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9576 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9577 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9578 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9580 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9581 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9582 </pre
></blockquote
>
9584 <p
>In addition to the forward and reverse searches , there is also a
9585 search for SOA records, which behave similar to the forward and
9586 reverse lookups.
</p
>
9588 <p
>A thing to note with the PowerDNS behaviour is that it do not
9589 specify any objectclass names, and instead look for the attributes it
9590 need to generate a DNS reply. This make it able to work with any
9591 objectclass that provide the needed attributes.
</p
>
9593 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9594 dnsdomain2 schemas. The latter is used for reverse entries like
9595 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9597 <p
>In Debian Edu, we have created DNS objects using the object classes
9598 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9599 attributes) and domainrelatedobject (for associatedDomain). The use
9600 of structural object classes make it impossible to combine these
9601 classes with the object classes used by DHCP.
</p
>
9603 <p
>There are other schemas that could be used too, for example the
9604 dnszone structural object class used by Gosa and bind-sdb for the DNS
9605 attributes combined with the domainrelatedobject object class, but in
9606 this case some unused attributes would have to be included as well
9607 (zonename and relativedomainname).
</p
>
9609 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9610 mode and not use any of the existing objectclasses (dnsdomain,
9611 dnsdomain2 and dnszone) when one want to combine the DNS information
9612 with DHCP information, and instead create a auxiliary object class
9613 defined something like this (using the attributes defined for
9614 dnsdomain and dnsdomain2 or dnszone):
</p
>
9616 <blockquote
><pre
>
9617 objectclass ( some-oid NAME
'dnsDomainAux
'
9620 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9621 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9622 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9623 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9624 A6Record $ DNAMERecord
9626 </pre
></blockquote
>
9628 <p
>This will allow any object to become a DNS entry when combined with
9629 the domainrelatedobject object class, and allow any entity to include
9630 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9631 developers asking for their view on this schema and if they are
9632 interested in providing such schema with PowerDNS, and I hope my
9633 message will be accepted into their mailing list soon.
</p
>
9635 <p
><strong
>ISC dhcp
</strong
></p
>
9637 <p
>The DHCP server searches for specific objectclass and requests all
9638 the object attributes, and then uses the attributes it want. This
9639 make it harder to figure out exactly what attributes are used, but
9640 thanks to the working example in Debian Edu I can at least get an idea
9641 what is needed without having to read the source code.
</p
>
9643 <p
>In the DHCP server configuration, the LDAP base to use and the
9644 search filter to use to locate the correct dhcpServer entity is
9645 stored. These are the relevant entries from
9646 /etc/dhcp3/dhcpd.conf:
</p
>
9648 <blockquote
><pre
>
9649 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9650 ldap-dhcp-server-cn
"dhcp
";
9651 </pre
></blockquote
>
9653 <p
>The DHCP server uses this information to nest all the DHCP
9654 configuration it need. The cn
"dhcp
" is located using the given LDAP
9655 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9656 search result is this entry:
</p
>
9658 <blockquote
><pre
>
9659 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9662 objectClass: dhcpServer
9663 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9664 </pre
></blockquote
>
9666 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9667 subtree with DHCP configuration. The DHCP configuration subtree base
9668 is located using a base scope search with base
"cn=DHCP
9669 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9670 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9671 The search result is this entry:
</p
>
9673 <blockquote
><pre
>
9674 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9677 objectClass: dhcpService
9678 objectClass: dhcpOptions
9679 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9680 dhcpStatements: ddns-update-style none
9681 dhcpStatements: authoritative
9682 dhcpOption: smtp-server code
69 = array of ip-address
9683 dhcpOption: www-server code
72 = array of ip-address
9684 dhcpOption: wpad-url code
252 = text
9685 </pre
></blockquote
>
9687 <p
>Next, the entire subtree is processed, one level at the time. When
9688 all the DHCP configuration is loaded, it is ready to receive requests.
9689 The subtree in Debian Edu contain objects with object classes
9690 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9691 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9692 and information about netmasks, dynamic range etc. Leaving out the
9693 details here because it is not relevant for the focus of my
9694 investigation, which is to see if it is possible to merge dns and dhcp
9695 related computer objects.
</p
>
9697 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9698 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9699 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9700 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9701 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9704 <blockquote
><pre
>
9705 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9708 objectClass: dhcpHost
9709 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9710 dhcpStatements: fixed-address hostname
9711 </pre
></blockquote
>
9713 <p
>There is less flexiblity in the way LDAP searches are done here.
9714 The object classes need to have fixed names, and the configuration
9715 need to be stored in a fairly specific LDAP structure. On the
9716 positive side, the invidiual dhcpHost entires can be anywhere without
9717 the DN pointed to by the dhcpServer entries. The latter should make
9718 it possible to group all host entries in a subtree next to the
9719 configuration entries, and this subtree can also be shared with the
9720 DNS server if the schema proposed above is combined with the dhcpHost
9721 structural object class.
9723 <p
><strong
>Conclusion
</strong
></p
>
9725 <p
>The PowerDNS implementation seem to be very flexible when it come
9726 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9727 come to the the LDAP structure, the
"strict
" mode is very flexible,
9728 allowing DNS objects to be stored anywhere under the base cn specified
9729 in the configuration.
</p
>
9731 <p
>The DHCP implementation on the other hand is very inflexible, both
9732 regarding which LDAP schemas to use and which LDAP structure to use.
9733 I guess one could implement ones own schema, as long as the
9734 objectclasses and attributes have the names used, but this do not
9735 really help when the DHCP subtree need to have a fairly fixed
9736 structure.
</p
>
9738 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9739 this might work for Debian Edu:
</p
>
9741 <blockquote
><pre
>
9743 cn=machine-info (dhcpService) - dhcpServiceDN points here
9744 cn=dhcp (dhcpServer)
9745 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9746 cn=
10.0.2.0 (dhcpSubnet)
9747 cn=group1 (dhcpGroup/dhcpOptions)
9748 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9749 cn=
192.168.0.0 (dhcpSubnet)
9750 cn=group1 (dhcpGroup/dhcpOptions)
9751 ou=machines - PowerDNS base points here
9752 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9753 </pre
></blockquote
>
9755 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9756 entries to be in the dhcpGroup subtrees, the entries can be stored
9757 there instead of a common machines subtree, and the PowerDNS base
9758 would have to be moved one level up to the machine-info subtree.
</p
>
9760 <p
>The combined object under the machines subtree would look something
9761 like this:
</p
>
9763 <blockquote
><pre
>
9764 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9767 objectClass: dhcpHost
9768 objectclass: domainrelatedobject
9769 objectclass: dnsDomainAux
9770 associateddomain: hostname.intern
9771 arecord:
10.11.12.13
9772 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9773 dhcpStatements: fixed-address hostname.intern
9774 </pre
></blockquote
>
9776 </p
>One could even add the LTSP configuration associated with a given
9777 machine, as long as the required attributes are available in a
9778 auxiliary object class.
</p
>
9783 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9784 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9785 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9786 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9787 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9788 DHCP services in Debian Edu to use the same LDAP objects for a given
9789 computer, to avoid the possibility of having a inconsistent state for
9790 a computer in LDAP (as in DHCP but no DNS entry or the other way
9791 around) and make it easier to add computers to LDAP.
</p
>
9793 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9794 information finally found a solution that seem to work.
</p
>
9796 <p
>The old setup required three LDAP objects for a given computer.
9797 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9798 we switch powerdns to use its strict LDAP method (ldap-method=strict
9799 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9800 merged into one while making it impossible to transfer the reverse map
9801 to a slave DNS server.
</p
>
9803 <p
>If we also replace the object class used to get the DNS related
9804 attributes to one allowing these attributes to be combined with the
9805 dhcphost object class, we can merge the DNS and DHCP entries into one.
9806 I
've written such object class in the dnsdomainaux.schema file (need
9807 proper OIDs, but that is a minor issue), and tested the setup. It
9808 seem to work.
</p
>
9810 <p
>With this test setup in place, we can get away with one LDAP object
9811 for both DNS and DHCP, and even the LTSP configuration I suggested in
9812 an earlier email. The combined LDAP object will look something like
9815 <blockquote
><pre
>
9816 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9818 objectClass: dhcphost
9819 objectclass: domainrelatedobject
9820 objectclass: dnsdomainaux
9821 associateddomain: hostname.intern
9822 arecord:
10.11.12.13
9823 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9824 dhcpstatements: fixed-address hostname
9826 </pre
></blockquote
>
9828 <p
>The DNS server uses the associateddomain and arecord entries, while
9829 the DHCP server uses the dhcphwaddress and dhcpstatements entries
9830 before asking DNS to resolve the fixed-adddress. LTSP will use
9831 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
9833 <p
>I am not yet sure if I can get the DHCP server to look for its
9834 dhcphost in a different location, to allow us to put the objects
9835 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
9836 that. If I can
't figure out a way to do that, we can still get rid of
9837 the hosts subtree and move all its content into the DHCP Config tree
9838 (which probably should be renamed to be more related to the new
9839 content. I suspect cn=dnsdhcp,ou=services or something like that
9840 might be a good place to put it.
</p
>
9842 <p
>If you want to help out with implementing this for Debian Edu,
9843 please contact us on debian-edu@lists.debian.org.
</p
>
9848 <title>Idea for storing LTSP configuration in LDAP
</title>
9849 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
9850 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
9851 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
9852 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
9853 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
9854 clients, and that this can be used to fetch configuration from LDAP if
9855 Debian Edu choose to store configuration there.
</p
>
9857 <p
>Armed with this information, I got inspired and wrote a test module
9858 to get configuration from LDAP. The idea is to look up the MAC
9859 address of the client in LDAP, and look for attributes on the form
9860 ltspconfigsetting=value, and use this to export SETTING=value to the
9861 LTSP clients.
</p
>
9863 <p
>The goal is to be able to store the LTSP configuration attributes
9864 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
9865 allowing us to store all information about a computer in one place.
</p
>
9867 <p
>This is a untested draft implementation, and I welcome feedback on
9868 this approach. A real LDAP schema for the ltspClientAux objectclass
9869 need to be written. Comments, suggestions, etc?
</p
>
9871 <blockquote
><pre
>
9872 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9874 # Fetch LTSP client settings from LDAP based on MAC address
9876 # Uses ethernet address as stored in the dhcpHost objectclass using
9877 # the dhcpHWAddress attribute or ethernet address stored in the
9878 # ieee802Device objectclass with the macAddress attribute.
9880 # This module is written to be schema agnostic, and only depend on the
9881 # existence of attribute names.
9883 # The LTSP configuration variables are saved directly using a
9884 # ltspConfig prefix and uppercasing the rest of the attribute name.
9885 # To set the SERVER variable, set the ltspConfigServer attribute.
9887 # Some LDAP schema should be created with all the relevant
9888 # configuration settings. Something like this should work:
9890 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9893 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9895 LDAPSERVER=$(debian-edu-ldapserver)
9896 if [
"$LDAPSERVER
" ] ; then
9897 LDAPBASE=$(debian-edu-ldapserver -b)
9898 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9899 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9900 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9901 grep
'^ltspConfig
' | while read attr value ; do
9902 # Remove prefix and convert to upper case
9903 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9904 # bass value on to clients
9905 eval
"$attr=$value; export $attr
"
9909 </pre
></blockquote
>
9911 <p
>I
'm not sure this shell construction will work, because I suspect
9912 the while block might end up in a subshell causing the variables set
9913 there to not show up in ltsp-config, but if that is the case I am sure
9914 the code can be restructured to make sure the variables are passed on.
9915 I expect that can be solved with some testing. :)
</p
>
9917 <p
>If you want to help out with implementing this for Debian Edu,
9918 please contact us on debian-edu@lists.debian.org.
</p
>
9920 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9921 configuration in LDAP that was created around year
2000 by
9922 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9923 Xperience, Inc.,
2000</a
>. I found its
9924 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9925 personal home page over at redhat.com.
</p
>
9930 <title>jXplorer, a very nice LDAP GUI
</title>
9931 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9932 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9933 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9934 <description><p
>Since
9935 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9936 last post
</a
> about available LDAP tools in Debian, I was told about a
9937 LDAP GUI that is even better than luma. The java application
9938 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9939 moving LDAP objects and subtrees using drag-and-drop, and can
9940 authenticate using Kerberos. I have only tested the Kerberos
9941 authentication, but do not have a LDAP setup allowing me to rewrite
9942 LDAP with my test user yet. It is
9943 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9944 Debian
</a
> testing and unstable at the moment. The only problem I
9945 have with it is how it handle errors. If something go wrong, its
9946 non-intuitive behaviour require me to go through some query work list
9947 and remove the failing query. Nothing big, but very annoying.
</p
>
9952 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9953 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9954 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9955 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9956 <description><p
>Here is a short update on my
<a
9957 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9958 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9959 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9960 not reporting the status for KDE, because the upgrade crashes when
9961 aptitude try because of missing conflicts
9962 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9963 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9965 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9966 complete list of the installed packages. Based on this I see these
9967 differences when I did a test run today. As usual, I do not really
9968 know what the correct set of packages would be, but thought it best to
9969 publish the difference.
</p
>
9971 <p
>Installed using apt-get, missing with aptitude
</p
>
9973 <blockquote
><p
>
9974 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9975 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9976 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9977 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9978 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9979 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9980 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9981 python-gtkmozembed svgalibg1 xserver-xephyr zip
9982 </p
></blockquote
>
9984 <p
>Installed using apt-get, removed with aptitude
</p
>
9986 <blockquote
><p
>
9987 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9988 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9989 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9990 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9991 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9992 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9993 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9994 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9995 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9996 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9997 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9998 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9999 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10000 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
10001 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10002 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
10003 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
10004 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10005 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10006 mysql-common swfdec-gnome totem-gstreamer wodim
10007 </p
></blockquote
>
10009 <p
>Installed using aptitude, missing with apt-get
</p
>
10011 <blockquote
><p
>
10012 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10013 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10014 xserver-xorg-input-all xserver-xorg-input-evdev
10015 xserver-xorg-input-kbd xserver-xorg-input-mouse
10016 xserver-xorg-input-synaptics xserver-xorg-video-all
10017 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10018 xserver-xorg-video-chips xserver-xorg-video-cirrus
10019 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10020 xserver-xorg-video-glint xserver-xorg-video-i128
10021 xserver-xorg-video-i740 xserver-xorg-video-mach64
10022 xserver-xorg-video-mga xserver-xorg-video-neomagic
10023 xserver-xorg-video-nouveau xserver-xorg-video-nv
10024 xserver-xorg-video-r128 xserver-xorg-video-radeon
10025 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10026 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10027 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10028 xserver-xorg-video-sis xserver-xorg-video-sisusb
10029 xserver-xorg-video-tdfx xserver-xorg-video-tga
10030 xserver-xorg-video-trident xserver-xorg-video-tseng
10031 xserver-xorg-video-vesa xserver-xorg-video-vmware
10032 xserver-xorg-video-voodoo
10033 </p
></blockquote
>
10035 <p
>Installed using aptitude, removed with apt-get
</p
>
10037 <blockquote
><p
>
10038 deskbar-applet xserver-xorg xserver-xorg-core
10039 xserver-xorg-input-wacom xserver-xorg-video-intel
10040 xserver-xorg-video-openchrome
10041 </p
></blockquote
>
10043 <p
>I was told on IRC that the xorg-xserver package was
10044 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
10045 in git
</a
> today to try to get apt-get to not remove xorg completely.
10046 No idea when it hits Squeeze, but when it does I hope it will reduce
10047 the difference somewhat.
10052 <title>LUMA, a very nice LDAP GUI
</title>
10053 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
10054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
10055 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
10056 <description><p
>The last few days I have been looking into the status of the LDAP
10057 directory in Debian Edu, and in the process I started to miss a GUI
10058 tool to browse the LDAP tree. The only one I was able to find in
10059 Debian/Squeeze and Lenny is
10060 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
10061 be a great tool to get a overview of the current LDAP directory
10062 populated by default in Skolelinux. Thanks to it, I have been able to
10063 find empty and obsolete subtrees, misplaced objects and duplicate
10064 objects. It will be installed by default in Debian/Squeeze. If you
10065 are working with LDAP, give it a go. :)
</p
>
10067 <p
>I did notice one problem with it I have not had time to report to
10068 the BTS yet. There is no .desktop file in the package, so the tool do
10069 not show up in the Gnome and KDE menus, but only deep down in in the
10070 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10071 released.
</p
>
10073 <p
>I have not yet been able to get it to modify the tree yet. I would
10074 like to move objects and remove subtrees directly in the GUI, but have
10075 not found a way to do that with LUMA yet. So in the mean time, I use
10076 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
10078 <p
>If you have tips on other GUI tools for LDAP that might be useful
10079 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
10081 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
10082 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
10083 useful GUI alternative. It seem like a good tool, but is unmaintained
10084 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10085 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
10090 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
10091 <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>
10092 <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>
10093 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
10094 <description><p
>A while back, I
10095 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
10096 about the fact
</a
> that it is not possible with the provided schemas
10097 for storing DNS and DHCP information in LDAP to combine the two sets
10098 of information into one LDAP object representing a computer.
</p
>
10100 <p
>In the mean time, I discovered that a simple fix would be to make
10101 the dhcpHost object class auxiliary, to allow it to be combined with
10102 the dNSDomain object class, and thus forming one object for one
10103 computer when storing both DHCP and DNS information in LDAP.
</p
>
10105 <p
>If I understand this correctly, it is not safe to do this change
10106 without also changing the assigned number for the object class, and I
10107 do not know enough about LDAP schema design to do that properly for
10108 Debian Edu.
</p
>
10110 <p
>Anyway, for future reference, this is how I believe we could change
10112 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
10113 schema
</a
> to solve at least part of the problem with the LDAP schemas
10114 available today from IETF.
</p
>
10117 --- dhcp.schema (revision
65192)
10118 +++ dhcp.schema (working copy)
10119 @@ -
376,
7 +
376,
7 @@
10120 objectclass (
2.16.840.1.113719.1.203.6.6
10121 NAME
'dhcpHost
'
10122 DESC
'This represents information about a particular client
'
10124 + SUP top AUXILIARY
10126 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10127 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
10130 <p
>I very much welcome clues on how to do this properly for Debian
10131 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10132 package, and should thus be free to rewrite it as we see fit.
</p
>
10134 <p
>If you want to help out with implementing this for Debian Edu,
10135 please contact us on debian-edu@lists.debian.org.
</p
>
10140 <title>Calling tasksel like the installer, while still getting useful output
</title>
10141 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
10142 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
10143 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
10144 <description><p
>A few times I have had the need to simulate the way tasksel
10145 installs packages during the normal debian-installer run. Until now,
10146 I have ended up letting tasksel do the work, with the annoying problem
10147 of not getting any feedback at all when something fails (like a
10148 conffile question from dpkg or a download that fails), using code like
10151 <blockquote
><pre
>
10152 export DEBIAN_FRONTEND=noninteractive
10153 tasksel --new-install
10154 </pre
></blockquote
>
10156 This would invoke tasksel, let its automatic task selection pick the
10157 tasks to install, and continue to install the requested tasks without
10158 any output what so ever.
10160 Recently I revisited this problem while working on the automatic
10161 package upgrade testing, because tasksel would some times hang without
10162 any useful feedback, and I want to see what is going on when it
10163 happen. Then it occured to me, I can parse the output from tasksel
10164 when asked to run in test mode, and use that aptitude command line
10165 printed by tasksel then to simulate the tasksel run. I ended up using
10168 <blockquote
><pre
>
10169 export DEBIAN_FRONTEND=noninteractive
10170 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
10172 </pre
></blockquote
>
10174 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
10175 --without-recommends -o APT::Install-Recommends=no -y install
10176 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10177 ~pimportant
</tt
>", which will install the gnome desktop task, the
10178 laptop task and all packages with priority standard , required and
10179 important, just like tasksel would have done it during
10180 installation.
</p
>
10182 <p
>A better approach is probably to extend tasksel to be able to
10183 install packages without using debconf-apt-progress, for use cases
10184 like this.
</p
>
10189 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
10190 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
10191 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
10192 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
10193 <description><p
>My
10194 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
10195 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
10196 finally made the upgrade logs available from
10197 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
10198 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10199 apt and aptitude, and found their differences interesting. This time
10200 I will only focus on their removal plans.
</p
>
10202 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
10203 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
10204 surprising part is that it want to remove xorg and all
10205 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10206 sure why. When asking aptitude to do the same, it want to remove
129
10207 packages, but most of them are library packages I suspect are no
10208 longer needed. Both of them want to remove bluetooth packages, which
10209 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
10211 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
10212 which seem like a bad idea and xorg the same way as with Gnome. Asking
10213 aptitude for the same, it wants to remove
192 packages, none which are
10214 too surprising.
</p
>
10216 <p
>I guess the removal of xorg during upgrades should be investigated
10217 and avoided, and perhaps others as well. Here are the complete list
10218 of planned removals. The complete logs is available from the URL
10219 above. Note if you want to repeat these tests, that the upgrade test
10220 for kde+apt-get hung in the tasksel setup because of dpkg asking
10221 conffile questions. No idea why. I worked around it by using
10222 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
10223 continue.
</p
>
10225 <p
><b
>apt-get gnome
72</b
>
10226 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
10227 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10228 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
10229 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10230 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10231 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10232 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10233 xserver-xorg-input-kbd xserver-xorg-input-mouse
10234 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10235 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10236 xserver-xorg-video-ati xserver-xorg-video-chips
10237 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10238 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10239 xserver-xorg-video-glint xserver-xorg-video-i128
10240 xserver-xorg-video-i740 xserver-xorg-video-imstt
10241 xserver-xorg-video-intel xserver-xorg-video-mach64
10242 xserver-xorg-video-mga xserver-xorg-video-neomagic
10243 xserver-xorg-video-nsc xserver-xorg-video-nv
10244 xserver-xorg-video-openchrome xserver-xorg-video-r128
10245 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10246 xserver-xorg-video-rendition xserver-xorg-video-s3
10247 xserver-xorg-video-s3virge xserver-xorg-video-savage
10248 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10249 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10250 xserver-xorg-video-tga xserver-xorg-video-trident
10251 xserver-xorg-video-tseng xserver-xorg-video-v4l
10252 xserver-xorg-video-vesa xserver-xorg-video-vga
10253 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
10254 xulrunner-
1.9-gnome-support
</p
>
10256 <p
><b
>aptitude gnome
129</b
>
10258 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
10259 djvulibre-desktop finger gnome-app-install gnome-mount
10260 gnome-network-admin gnome-spell gnome-vfs-obexftp
10261 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10262 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10263 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10264 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
10265 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
10266 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
10267 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
10268 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
10269 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
10270 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
10271 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
10272 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
10273 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10274 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
10275 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
10276 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
10277 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
10278 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
10279 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10280 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10281 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10282 openoffice.org-writer2latex openssl-blacklist p7zip
10283 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
10284 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10285 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10286 swfdec-mozilla totem-gstreamer update-manager wodim
10287 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10288 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10291 <p
><b
>apt-get kde
82</b
>
10293 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10294 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10295 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10296 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10297 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10298 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10299 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10300 xserver-xorg-input-kbd xserver-xorg-input-mouse
10301 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10302 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10303 xserver-xorg-video-ati xserver-xorg-video-chips
10304 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10305 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10306 xserver-xorg-video-glint xserver-xorg-video-i128
10307 xserver-xorg-video-i740 xserver-xorg-video-imstt
10308 xserver-xorg-video-intel xserver-xorg-video-mach64
10309 xserver-xorg-video-mga xserver-xorg-video-neomagic
10310 xserver-xorg-video-nsc xserver-xorg-video-nv
10311 xserver-xorg-video-openchrome xserver-xorg-video-r128
10312 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10313 xserver-xorg-video-rendition xserver-xorg-video-s3
10314 xserver-xorg-video-s3virge xserver-xorg-video-savage
10315 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10316 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10317 xserver-xorg-video-tga xserver-xorg-video-trident
10318 xserver-xorg-video-tseng xserver-xorg-video-v4l
10319 xserver-xorg-video-vesa xserver-xorg-video-vga
10320 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
10322 <p
><b
>aptitude kde
192</b
>
10323 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
10324 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10325 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10326 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10327 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10328 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10329 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10330 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10331 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10332 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10333 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10334 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10335 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10336 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10337 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10338 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10339 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10340 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10341 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
10342 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10343 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10344 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
10345 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10346 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10347 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10348 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10349 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10350 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
10351 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
10352 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10353 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10354 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10355 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10356 texlive-common texlive-doc-base texlive-fonts-recommended
10357 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10358 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10359 xulrunner-
1.9</p
>
10365 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
10366 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
10367 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
10368 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
10369 <description><p
>The last few days I have done some upgrade testing in Debian, to
10370 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10371 have been discovered and reported in the process
10372 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
10373 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
10374 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
10375 kdebase-workspace-data), and to get a more regular testing going on, I
10376 am working on a script to automate the test.
</p
>
10378 <p
>The idea is to create a Lenny chroot and use tasksel to install a
10379 Gnome or KDE desktop installation inside the chroot before upgrading
10380 it. To ensure no services are started in the chroot, a policy-rc.d
10381 script is inserted. To make sure tasksel believe it is to install a
10382 desktop on a laptop, the tasksel tests are replaced in the chroot
10383 (only acceptable because this is a throw-away chroot).
</p
>
10385 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10386 currently always fail because udev refuses to upgrade with the kernel
10387 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10388 is created. The bug report
10389 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
10390 this problem do not trigger in a chroot, but I touch the file anyway
10391 to make sure the upgrade go well. Testing on virtual and real
10392 hardware have failed me because of udev so far, and creating this file
10393 do the trick in such settings anyway. This is a
10394 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
10395 issue
</a
> and the current udev behaviour is intended by the udev
10396 maintainer because he lack the resources to rewrite udev to keep
10397 working with old kernels or something like that. I really wish the
10398 udev upstream would keep udev backwards compatible, to avoid such
10399 upgrade problem, but given that they fail to do so, I guess
10400 documenting the way out of this mess is the best option we got for
10401 Debian Squeeze.
</p
>
10403 <p
>Anyway, back to the task at hand, testing upgrades. This test
10404 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10407 <blockquote
><pre
>
10411 if [
"$
1" ] ; then
10420 exec
&lt; /dev/null
10422 mirror=http://ftp.skolelinux.org/debian
10423 tmpdir=chroot-$from-upgrade-$to-$desktop
10425 debootstrap $from $tmpdir $mirror
10426 chroot $tmpdir aptitude update
10427 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10431 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10433 umount $tmpdir/proc
10435 mount -t proc proc $tmpdir/proc
10436 # Make sure proc is unmounted also on failure
10437 trap exit_cleanup EXIT INT
10439 chroot $tmpdir aptitude -y install debconf-utils
10441 # Make sure tasksel autoselection trigger. It need the test scripts
10442 # to return the correct answers.
10443 echo tasksel tasksel/desktop multiselect $desktop | \
10444 chroot $tmpdir debconf-set-selections
10446 # Include the desktop and laptop task
10447 for test in desktop laptop ; do
10448 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10452 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10455 DEBIAN_FRONTEND=noninteractive
10456 DEBIAN_PRIORITY=critical
10457 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10458 chroot $tmpdir tasksel --new-install
10460 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10461 chroot $tmpdir aptitude update
10462 touch $tmpdir/etc/udev/kernel-upgrade
10463 chroot $tmpdir aptitude -y dist-upgrade
10465 </pre
></blockquote
>
10467 <p
>I suspect it would be useful to test upgrades with both apt-get and
10468 with aptitude, but I have not had time to look at how they behave
10469 differently so far. I hope to get a cron job running to do the test
10470 regularly and post the result on the web. The Gnome upgrade currently
10471 work, while the KDE upgrade fail because of the bug in
10472 kdebase-workspace-data
</p
>
10474 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10475 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10476 post, so I will refrain from trying. I can report that for Gnome,
10477 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10478 remove and
1 not upgraded and
1024MB need to be downloaded while for
10479 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10480 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10482 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10483 is able to migrate to dependency based boot sequencing and parallel
10484 booting without a hitch. Was unsure if there were still bugs with
10485 packages failing to clean up their obsolete init.d script during
10486 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10487 packages.
</p
>
10492 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10493 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10494 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10495 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10496 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10497 scripts to migrate (some of) their operations to upstart job while
10498 keeping the init.d for hurd and kfreebsd. The packages with such
10499 needs will need a way to get their init.d scripts to behave
10500 differently when used with sysvinit and with upstart. Because of
10501 this, I had a look at the environment variables set when a init.d
10502 script is running under upstart, and when it is not.
</p
>
10504 <p
>With upstart, I notice these environment variables are set when a
10505 script is started from rcS.d/ (ignoring some irrelevant ones like
10506 COLUMNS):
</p
>
10508 <blockquote
><pre
>
10514 UPSTART_EVENTS=startup
10516 UPSTART_JOB=rc-sysinit
10517 </pre
></blockquote
>
10519 <p
>With sysvinit, these environment variables are set for the same
10522 <blockquote
><pre
>
10523 INIT_VERSION=sysvinit-
2.88
10528 </pre
></blockquote
>
10530 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10531 sysvinit are not set by upstart. Not sure if it is intentional or not
10532 to not be compatible with sysvinit in this regard.
</p
>
10534 <p
>For scripts needing to behave differently when upstart is used,
10535 looking for the UPSTART_JOB environment variable seem to be a good
10541 <title>A manual for standards wars...
</title>
10542 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10543 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10544 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10545 <description><p
>Via the
10546 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10547 of Rob Weir
</a
> I came across the very interesting essay named
10548 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10549 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10550 following the standards wars of today.
</p
>
10555 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10556 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10557 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10558 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10559 <description><p
>When using sitesummary at a site to track machines, it is possible
10560 to get a list of the machine types in use thanks to the DMI
10561 information extracted from each machine. The script to do so is
10562 included in the sitesummary package, and here is example output from
10563 the Skolelinux build servers:
</p
>
10565 <blockquote
><pre
>
10566 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10568 Dell Computer Corporation
1
10571 eserver xSeries
345 -[
8670M1X]-
1
10575 </pre
></blockquote
>
10577 <p
>The quality of the report depend on the quality of the DMI tables
10578 provided in each machine. Here there are Intel machines without model
10579 information listed with Intel as vendor and no model, and virtual Xen
10580 machines listed as [no-dmi-info]. One can add -l as a command line
10581 option to list the individual machines.
</p
>
10583 <p
>A larger list is
10584 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10585 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10586 provide the basic sitesummary report publicly. In their report there
10587 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10588 their machines, and as sitesummary is available in both distributions,
10589 it is trivial to get all of them to report to the same central
10590 collector.
</p
>
10595 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10596 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10597 <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>
10598 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10599 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10600 start at boot when an NVidia video card is used is handled. The
10601 problem seem to be that the nvidia X.org driver uses a long time to
10602 initialize, and this duration is longer than kdm is configured to
10605 <p
>I came across two bugs related to this issue,
10606 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10607 against initscripts and passed on to nvidia-glx when it became obvious
10608 that the nvidia drivers were involved, and
10609 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10610 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10612 <p
>To me, it seem that no-one is interested in actually solving the
10613 problem nvidia video card owners experience and make sure the Debian
10614 distribution work out of the box for these users. The nvidia driver
10615 maintainers expect kdm to be set up to wait longer, while kdm expect
10616 the nvidia driver maintainers to fix the driver to start faster, and
10617 while they wait for each other I guess the users end up switching to a
10618 distribution that work for them. I have no idea what the solution is,
10619 but I am pretty sure that waiting for each other is not it.
</p
>
10621 <p
>I wonder why we end up handling bugs this way.
</p
>
10626 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10627 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10628 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10629 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10630 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10631 The feature seem to hold up pretty well, but three fairly serious
10632 issues are known and should be solved:
10634 <p
><ul
>
10636 <li
>The wicd package seen to
10637 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10638 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10639 parallel booting is enabled. No idea why, but the wicd maintainer
10640 seem to be on the case.
</li
>
10642 <li
>The nvidia X driver seem to
10643 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10644 triggered more easily when parallel booting is in effect. The
10645 maintainer is on the case.
</li
>
10647 <li
>The sysv-rc package fail to properly enable dependency based boot
10648 sequencing (the shutdown is broken) when old file-rc users
10649 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10650 sysv-rc. One way to solve it would be for file-rc to create
10651 /etc/init.d/.legacy-bootordering, and another is to try to make
10652 sysv-rc more robust. Will investigate some more and probably upload a
10653 workaround in sysv-rc to help those trying to move from file-rc to
10654 sysv-rc get a working shutdown.
</li
>
10656 </ul
></p
>
10658 <p
>All in all not many surprising issues, and all of them seem
10659 solvable before Squeeze is released. In addition to these there are
10660 some packages with bugs in their dependencies and run level settings,
10661 which I expect will be fixed in a reasonable time span.
</p
>
10663 <p
>If you report any problems with dependencies in init.d scripts to
10664 the BTS, please usertag the report to get it to show up at
10665 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10666 list of usertagged bugs related to this
</a
>.
</p
>
10668 <p
>Update: Correct bug number to file-rc issue.
</p
>
10673 <title>More flexible firmware handling in debian-installer
</title>
10674 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10675 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10676 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10677 <description><p
>After a long break from debian-installer development, I finally
10678 found time today to return to the project. Having to spend less time
10679 working dependency based boot in debian, as it is almost complete now,
10680 definitely helped freeing some time.
</p
>
10682 <p
>A while back, I ran into a problem while working on Debian Edu. We
10683 include some firmware packages on the Debian Edu CDs, those needed to
10684 get disk and network controllers working. Without having these
10685 firmware packages available during installation, it is impossible to
10686 install Debian Edu on the given machine, and because our target group
10687 are non-technical people, asking them to provide firmware packages on
10688 an external medium is a support pain. Initially, I expected it to be
10689 enough to include the firmware packages on the CD to get
10690 debian-installer to find and use them. This proved to be wrong.
10691 Next, I hoped it was enough to symlink the relevant firmware packages
10692 to some useful location on the CD (tried /cdrom/ and
10693 /cdrom/firmware/). This also proved to not work, and at this point I
10694 found time to look at the debian-installer code to figure out what was
10695 going to work.
</p
>
10697 <p
>The firmware loading code is in the hw-detect package, and a closer
10698 look revealed that it would only look for firmware packages outside
10699 the installation media, so the CD was never checked for firmware
10700 packages. It would only check USB sticks, floppies and other
10701 "external
" media devices. Today I changed it to also look in the
10702 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10703 solve the problem I ran into with Debian edu. I also changed it to
10704 look in /firmware/, to make sure the installer also find firmware
10705 provided in the initrd when booting the installer via PXE, to allow us
10706 to provide the same feature in the PXE setup included in Debian
10709 <p
>To make sure firmware deb packages with a license questions are not
10710 activated without asking if the license is accepted, I extended
10711 hw-detect to look for preinst scripts in the firmware packages, and
10712 run these before activating the firmware during installation. The
10713 license question is asked using debconf in the preinst, so this should
10714 solve the issue for the firmware packages I have looked at so far.
</p
>
10716 <p
>If you want to discuss the details of these features, please
10717 contact us on debian-boot@lists.debian.org.
</p
>
10722 <title>Parallellized boot is now the default in Debian/unstable
</title>
10723 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10725 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10726 <description><p
>Since this evening, parallel booting is the default in
10727 Debian/unstable for machines using dependency based boot sequencing.
10728 Apparently the testing of concurrent booting has been wider than
10729 expected, if I am to believe the
10730 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10731 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10732 with the feature this weekend, to give us some time to detect any
10733 remaining problems before Squeeze is frozen. If serious problems are
10734 detected, it is simple to change the default back to sequential boot.
10735 The upload of the new sysvinit package also activate a new upstream
10738 More information about
10739 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10740 based boot sequencing
</a
> is available from the Debian wiki. It is
10741 currently possible to disable parallel booting when one run into
10742 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10744 <blockquote
><pre
>
10746 </pre
></blockquote
>
10748 <p
>If you report any problems with dependencies in init.d scripts to
10749 the BTS, please usertag the report to get it to show up at
10750 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10751 list of usertagged bugs related to this
</a
>.
</p
>
10756 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10757 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10758 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10759 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10760 <description><p
>In the recent Debian Edu versions, the
10761 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10762 system
</a
> is used to keep track of the machines in the school
10763 network. Each machine will automatically report its status to the
10764 central server after boot and once per night. The network setup is
10765 also reported, and using this information it is possible to get the
10766 MAC address of all network interfaces in the machines. This is useful
10767 to update the DHCP configuration.
</p
>
10769 <p
>To give some idea how to use sitesummary, here is a one-liner to
10770 ist all MAC addresses of all machines reporting to sitesummary. Run
10771 this on the collector host:
</p
>
10773 <blockquote
><pre
>
10774 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10775 </pre
></blockquote
>
10777 <p
>This will list all MAC addresses assosiated with all machine, one
10778 line per machine and with space between the MAC addresses.
</p
>
10780 <p
>To allow system administrators easier job at adding static DHCP
10781 addresses for hosts, it would be possible to extend this to fetch
10782 machine information from sitesummary and update the DHCP and DNS
10783 tables in LDAP using this information. Such tool is unfortunately not
10784 written yet.
</p
>
10789 <title>systemd, an interesting alternative to upstart
</title>
10790 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10791 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10792 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10793 <description><p
>The last few days a new boot system called
10794 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10796 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10798 to the free software world. I have not yet had time to play around
10799 with it, but it seem to be a very interesting alternative to
10800 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10801 a good alternative for Debian when we are able to switch to an event
10802 based boot system. Tollef is
10803 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10804 systemd into Debian, and I look forward to seeing how well it work. I
10805 like the fact that systemd handles init.d scripts with dependency
10806 information natively, allowing them to run in parallel where upstart
10807 at the moment do not.
</p
>
10809 <p
>Unfortunately do systemd have the same problem as upstart regarding
10810 platform support. It only work on recent Linux kernels, and also need
10811 some new kernel features enabled to function properly. This means
10812 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10813 system. Not sure how that will be handled if systemd proves to be the
10814 way forward.
</p
>
10816 <p
>In the mean time, based on the
10817 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10818 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10819 decided to enable full parallel booting as the default in Debian as
10820 soon as possible (probably this weekend or early next week), to see if
10821 there are any remaining serious bugs in the init.d dependencies. A
10822 new version of the sysvinit package implementing this change is
10823 already in experimental. If all go well, Squeeze will be released
10824 with parallel booting enabled by default.
</p
>
10829 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
10830 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
10831 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
10832 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
10833 <description><p
>These days, the init.d script dependencies in Squeeze are quite
10834 complete, so complete that it is actually possible to run all the
10835 init.d scripts in parallell based on these dependencies. If you want
10836 to test your Squeeze system, make sure
10837 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10838 based boot sequencing
</a
> is enabled, and add this line to
10839 /etc/default/rcS:
</p
>
10841 <blockquote
><pre
>
10842 CONCURRENCY=makefile
10843 </pre
></blockquote
>
10845 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
10846 scripts in parallel using the dependency information stored in
10847 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
10848 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
10849 to try to start the kdm and gdm scripts as early as possible, and will
10850 start the facilities required by kdm or gdm as early as possible to
10851 make this happen.
</p
>
10853 <p
>Give it a try, and see if you like the result. If some services
10854 fail to start properly, it is most likely because they have incomplete
10855 init.d script dependencies in their startup script (or some of their
10856 dependent scripts have incomplete dependencies). Report bugs and get
10857 the package maintainers to fix it. :)
</p
>
10859 <p
>Running scripts in parallel could be the default in Debian when we
10860 manage to get the init.d script dependencies complete and correct. I
10861 expect we will get there in Squeeze+
1, if we get manage to test and
10862 fix the remaining issues.
</p
>
10864 <p
>If you report any problems with dependencies in init.d scripts to
10865 the BTS, please usertag the report to get it to show up at
10866 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10867 list of usertagged bugs related to this
</a
>.
</p
>
10872 <title>Debian has switched to dependency based boot sequencing
</title>
10873 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10875 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10876 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10877 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10878 have been migrated to using dependency based boot sequencing. This
10879 conclude work me and others have been doing for the last three days.
10880 It feels great to see this finally part of the default Debian
10881 installation. Now we just need to weed out the last few problems that
10882 are bound to show up, to get everything ready for Squeeze.
</p
>
10884 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10885 fixing the more fundamental problem of handing the event based
10886 non-predictable kernel in the early boot.
</p
>
10891 <title>Taking over sysvinit development
</title>
10892 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10893 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10894 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10895 <description><p
>After several years of frustration with the lack of activity from
10896 the existing sysvinit upstream developer, I decided a few weeks ago to
10897 take over the package and become the new upstream. The number of
10898 patches to track for the Debian package was becoming a burden, and the
10899 lack of synchronization between the distribution made it hard to keep
10900 the package up to date.
</p
>
10902 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10903 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10904 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10905 and Fedora), based on the patches currently in use in these
10906 distributions. We Debian maintainers plan to move to this tarball as
10907 the new upstream as soon as we find time to do the merge. Since the
10908 new tarball was created, we agreed with Werner at SuSe to make a new
10909 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10910 development there. The project is registered and currently waiting
10911 for approval by the Savannah administrators, and as soon as it is
10912 approved, we will import the old versions from svn and continue
10913 working on the future release.
</p
>
10915 <p
>It is a bit ironic that this is done now, when some of the involved
10916 distributions are moving to upstart as a syvinit replacement.
</p
>
10921 <title>Debian boots quicker and quicker
</title>
10922 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10924 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10925 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10926 people involved in the boot system on Debian and Ubuntu, to see if we
10927 could find more ways to speed up the boot system. This was an Ubuntu
10929 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10930 gathering
</a
>. It was quite productive. We also discussed the future
10931 of boot systems, and ways to handle the increasing number of boot
10932 issues introduced by the Linux kernel becoming more and more
10933 asynchronous and event base. The Ubuntu approach using udev and
10934 upstart might be a good way forward. Time will show.
</p
>
10936 <p
>Anyway, there are a few ways at the moment to speed up the boot
10937 process in Debian. All of these should be applied to get a quick
10942 <li
>Use dash as /bin/sh.
</li
>
10944 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10945 clock is in UTC.
</li
>
10947 <li
>Install and activate the insserv package to enable
10948 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10949 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10953 These points are based on the Google summer of code work done by
10954 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10955 Villegas
</a
>.
10957 <p
>Support for makefile-style concurrency during boot was uploaded to
10958 unstable yesterday. When we tested it, we were able to cut
6 seconds
10959 from the boot sequence. It depend on very correct dependency
10960 declaration in all init.d scripts, so I expect us to find edge cases
10961 where the dependences in some scripts are slightly wrong when we start
10962 using this.
</p
>
10964 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10965 introduced by Raphael Geissert today, one that could affect the
10966 startup speed as well. Instead of starting some scripts concurrently
10967 from rcS.d/ and another set of scripts from rc2.d/, it would be
10968 possible to run a of them in the same process. A quick way to test
10969 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10970 insserv
'. Will need to test if that work. :)
</p
>
10975 <title>BSAs påstander om piratkopiering møter motstand
</title>
10976 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10977 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10978 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10979 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10980 programvareselskapene som Microsoft og Apple, publisert en rapport der
10981 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10982 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10984 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10985 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10986 dagene. Et spesielt interessant kommentar fra Sverige,
10987 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10988 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10991 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10992 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10993 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10994 exakta
", säger BSAs Sverigechef John Hugosson.
10995 </blockquote
>
10997 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10998 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10999 piracy figures need a shot of reality
</a
> og
<a
11000 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
11001 Copyright Treaty Work?
</a
></p
>
11003 <p
>Fant lenkene via
<a
11004 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
11005 på Slashdot
</a
>.
</p
>
11010 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
11011 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
11012 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
11013 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
11014 <description><p
>Kom over
11015 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
11016 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11017 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11018 jobber til daglig. En rask opptelling forteller meg at vi har
490
11019 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
11020 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
11021 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
11026 <title>Kryptert harddisk - naturligvis
</title>
11027 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
11028 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
11029 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
11030 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
11031 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
11032 når en tar tap av arbeidstid, fortrolige dokumenter,
11033 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11034 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11035 til at jeg har kryptert harddisken på både kontormaskinen og min
11036 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11037 komme på avveie, den første informasjon relatert til jobben min ved
11038 Universitetet i Oslo, og den andre relatert til blant annet
11039 foreningsarbeide. Kryptering av diskene gjør at det er lite
11040 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11041 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11042 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11043 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11044 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11045 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11046 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11047 det er gjort slik jeg gjør det er minimale, og gevinstene er
11048 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11049 maskinen reinstalleres og alt er tapt.
</p
>
11051 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11052 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11053 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11054 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11055 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11056 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11057 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11058 betydelige.
</p
>
11063 <title>Two projects that have improved the quality of free software a lot
</title>
11064 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
11065 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
11066 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
11067 <description><p
>There are two software projects that have had huge influence on the
11068 quality of free software, and I wanted to mention both in case someone
11069 do not yet know them.
</p
>
11071 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
11072 tool to detect and expose errors in the memory handling of programs.
11073 It is easy to use, all one need to do is to run
'valgrind program
',
11074 and it will report any problems on stdout. It is even better if the
11075 program include debug information. With debug information, it is able
11076 to report the source file name and line number where the problem
11077 occurs. It can report things like
'reading past memory block in file
11078 X line N, the memory block was allocated in file Y, line M
', and
11079 'using uninitialised value in control logic
'. This tool has made it
11080 trivial to investigate reproducible crash bugs in programs, and have
11081 reduced the number of this kind of bugs in free software a lot.
11083 <p
>The second one is
11084 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
11085 a source code checker. It is able to process the source of a program
11086 and find problems in the logic without running the program. It
11087 started out as the Stanford Checker and became well known when it was
11088 used to find bugs in the Linux kernel. It is now a commercial tool
11089 and the company behind it is running
11090 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
11091 free software community, where a lot of free software projects get
11092 their source checked for free. Several thousand defects have been
11093 found and fixed so far. It can find errors like
'lock L taken in file
11094 X line N is never released if exiting in line M
', or
'the code in file
11095 Y lines O to P can never be executed
'. The projects included in the
11096 community service project have managed to get rid of a lot of
11097 reliability problems thanks to Coverity.
</p
>
11099 <p
>I believe tools like this, that are able to automatically find
11100 errors in the source, are vital to improve the quality of software and
11101 make sure we can get rid of the crashing and failing software we are
11102 surrounded by today.
</p
>
11107 <title>No patch is not better than a useless patch
</title>
11108 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
11109 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
11110 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
11111 <description><p
>Julien Blache
11112 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
11113 patch is better than a useless patch
</a
>. I completely disagree, as a
11114 patch allow one to discuss a concrete and proposed solution, and also
11115 prove that the issue at hand is important enough for someone to spent
11116 time on fixing it. No patch do not provide any of these positive
11117 properties.
</p
>
11122 <title>Standardize on protocols and formats, not vendors and applications
</title>
11123 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
11124 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
11125 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
11126 <description><p
>Where I work at the University of Oslo, one decision stand out as a
11127 very good one to form a long lived computer infrastructure. It is the
11128 simple one, lost by many in todays computer industry: Standardize on
11129 open network protocols and open exchange/storage formats, not applications.
11130 Applications come and go, while protocols and files tend to stay, and
11131 thus one want to make it easy to change application and vendor, while
11132 avoiding conversion costs and locking users to a specific platform or
11133 application.
</p
>
11135 <p
>This approach make it possible to replace the client applications
11136 independently of the server applications. One can even allow users to
11137 use several different applications as long as they handle the selected
11138 protocol and format. In the normal case, only one client application
11139 is recommended and users only get help if they choose to use this
11140 application, but those that want to deviate from the easy path are not
11141 blocked from doing so.
</p
>
11143 <p
>It also allow us to replace the server side without forcing the
11144 users to replace their applications, and thus allow us to select the
11145 best server implementation at any moment, when scale and resouce
11146 requirements change.
</p
>
11148 <p
>I strongly recommend standardizing - on open network protocols and
11149 open formats, but I would never recommend standardizing on a single
11150 application that do not use open network protocol or open formats.
</p
>
11155 <title>Returning from Skolelinux developer gathering
</title>
11156 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
11157 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
11158 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
11159 <description><p
>I
'm sitting on the train going home from this weekends Debian
11160 Edu/Skolelinux development gathering. I got a bit done tuning the
11161 desktop, and looked into the dynamic service location protocol
11162 implementation avahi. It look like it could be useful for us. Almost
11163 30 people participated, and I believe it was a great environment to
11164 get to know the Skolelinux system. Walter Bender, involved in the
11165 development of the Sugar educational platform, presented his stuff and
11166 also helped me improve my OLPC installation. He also showed me that
11167 his Turtle Art application can be used in standalone mode, and we
11168 agreed that I would help getting it packaged for Debian. As a
11169 standalone application it would be great for Debian Edu. We also
11170 tried to get the video conferencing working with two OLPCs, but that
11171 proved to be too hard for us. The application seem to need more work
11172 before it is ready for me. I look forward to getting home and relax
11178 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
11179 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
11180 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
11181 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
11182 <description><p
>The state of standardized LDAP schemas on Linux is far from
11183 optimal. There is RFC
2307 documenting one way to store NIS maps in
11184 LDAP, and a modified version of this normally called RFC
2307bis, with
11185 some modifications to be compatible with Active Directory. The RFC
11186 specification handle the content of a lot of system databases, but do
11187 not handle DNS zones and DHCP configuration.
</p
>
11189 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
11190 we would like to store information about users, SMB clients/hosts,
11191 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11192 and LTSP configuration in LDAP. These objects have a lot in common,
11193 but with the current LDAP schemas it is not possible to have one
11194 object per entity. For example, one need to have at least three LDAP
11195 objects for a given computer, one with the SMB related stuff, one with
11196 DNS information and another with DHCP information. The schemas
11197 provided for DNS and DHCP are impossible to combine into one LDAP
11198 object. In addition, it is impossible to implement quick queries for
11199 netgroup membership, because of the way NIS triples are implemented.
11200 It just do not scale. I believe it is time for a few RFC
11201 specifications to cleam up this mess.
</p
>
11203 <p
>I would like to have one LDAP object representing each computer in
11204 the network, and this object can then keep the SMB (ie host key), DHCP
11205 (mac address/name) and DNS (name/IP address) settings in one place.
11206 It need to be efficently stored to make sure it scale well.
</p
>
11208 <p
>I would also like to have a quick way to map from a user or
11209 computer and to the net group this user or computer is a member.
</p
>
11211 <p
>Active Directory have done a better job than unix heads like myself
11212 in this regard, and the unix side need to catch up. Time to start a
11213 new IETF work group?
</p
>
11218 <title>Endelig er Debian Lenny gitt ut
</title>
11219 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
11220 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
11221 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
11222 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
11223 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
11224 Et langt steg videre for Debian-prosjektet, og en rekke nye
11225 programpakker blir nå tilgjengelig for de av oss som bruker den
11226 stabile utgaven av Debian. Neste steg er nå å få
11227 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
11228 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
11229 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11230 slippes løs på skolene. Takk til alle debian-utviklerne som har
11231 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11232 bootsekvens tilgjengelig i stabil utgave, vha pakken
11233 <tt
>insserv
</tt
>.
</p
>
11238 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
11239 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
11240 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
11241 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
11242 <description><p
>This weekend we had a small developer gathering for Debian Edu in
11243 Oslo. Most of Saturday was used for the general assemly for the
11244 member organization, but the rest of the weekend I used to tune the
11245 LTSP installation. LTSP now work out of the box on the
10-network.
11246 Acer Aspire One proved to be a very nice thin client, with both
11247 screen, mouse and keybard in a small box. Was working on getting the
11248 diskless workstation setup configured out of the box, but did not
11249 finish it before the weekend was up.
</p
>
11251 <p
>Did not find time to look at the
4 VGA cards in one box we got from
11252 the Brazilian group, so that will have to wait for the next
11253 development gathering. Would love to have the Debian Edu installer
11254 automatically detect and configure a multiseat setup when it find one
11255 of these cards.
</p
>
11260 <title>The sorry state of multimedia browser plugins in Debian
</title>
11261 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
11262 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
11263 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
11264 <description><p
>Recently I have spent some time evaluating the multimedia browser
11265 plugins available in Debian Lenny, to see which one we should use by
11266 default in Debian Edu. We need an embedded video playing plugin with
11267 control buttons to pause or stop the video, and capable of streaming
11268 all the multimedia content available on the web. The test results and
11269 notes are available on
11270 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
11271 Debian wiki
</a
>. I was surprised how few of the plugins are able to
11272 fill this need. My personal video player favorite, VLC, has a really
11273 bad plugin which fail on a lot of the test pages. A lot of the MIME
11274 types I would expect to work with any free software player (like
11275 video/ogg), just do not work. And simple formats like the
11276 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
11277 totem and vlc plugins. I hope the situation will improve soon. No
11278 wonder sites use the proprietary Adobe flash to play video.
</p
>
11280 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
11281 be the only one fitting our needs. :/
</p
>