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>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
11 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
13 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
14 <description><p
>For a while now, I have looked for a sensible way to share images
15 with my family using a self hosted solution, as it is unacceptable to
16 place images from my personal life under the control of strangers
17 working for data hoarders like Google or Dropbox. The last few days I
18 have drafted an approach that might work out, and I would like to
19 share it with you. I would like to publish images on a server under
20 my control, and point some Internet connected display units using some
21 free and open standard to the images I published. As my primary
22 language is not limited to ASCII, I need to store metadata using
23 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
24 of reading a RSS feed with image references (aka using the
25 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
26 of such frames. In the end I gave up that approach.
</p
>
28 <p
>Some months ago, I discovered that
29 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
30 read images from a RSS feed, and used it to set up a screen saver on
31 my home info screen, showing images from the Daily images feed from
32 NASA. This proved to work well. More recently I discovered that
33 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
34 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
35 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
36 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
37 screen saver capable of reading a RSS feed with images and news. For
38 fun, I used it this summer to test Kodi on my parents TV by hooking up
39 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
40 screen saver showing selected pictures from my selection.
</p
>
42 <p
>Armed with motivation and a test photo frame, I set out to generate
43 a RSS feed for the Kodi instance. I adjusted my
<a
44 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
45 /var/www/html/privatepictures/, wrote a small Perl script to extract
46 title and description metadata from the photo files and generate the
47 RSS file. I ended up using Perl instead of python, as the
48 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
49 tags I ended up using, while python3-exif did not. The relevant EXIF
50 tags only support ASCII, so I had to find better alternatives. XMP
51 seem to have the support I need.
</p
>
53 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
54 use tags that can be easily added/updated using normal free software
55 photo managing software. I ended up using the tags set using this
56 exiftool command, as these tags can also be set using digiKam:
</p
>
58 <blockquote
><pre
>
59 exiftool -headline=
'The RSS image title
' \
60 -description=
'The RSS image description.
' \
61 -subject+=for-family photo.jpeg
62 </pre
></blockquote
>
64 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
65 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
66 use the keyword/subject
'for-family
' to flag that the photo should be
67 shared with my family. Images with this keyword set are located and
68 copied into my Freedombox for the RSS generating script to find.
</p
>
70 <p
>Are there better ways to do this? Get in touch if you have better
71 suggestions.
</p
>
73 <p
>As usual, if you use Bitcoin and want to show your support of my
74 activities, please send Bitcoin donations to my address
75 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
80 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
81 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
82 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
83 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
84 <description><p
>Last night, I wrote
85 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
86 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
87 During the day I received valuable feedback, and thanks to the
88 suggestions I have been able to rewrite the recipe into a much simpler
89 approach requiring no setup at all. It is a single script that take
90 care of it all.
</p
>
92 <p
>This new script uses GStreamer instead of VLC to capture the
93 desktop and stream it to Kodi. This fixed the video quality issue I
94 saw initially. It further removes the need to add a m3u file on the
95 Kodi machine, as it instead connects to
96 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
97 Kodi
</a
> and simply ask Kodi to play from the stream created using
98 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
99 the script below, run it with the DNS name or IP address of the kodi
100 server to stream to as the only argument, and watch your screen show
101 up on the Kodi screen. Note, it depend on multicast on the local
102 network, so if you need to stream outside the local network, the
103 script must be modified. Also note, I have no idea if audio work, as
104 I only care about the picture part.
</p
>
106 <blockquote
><pre
>
109 # Stream the Linux desktop view to Kodi. See
110 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
111 # for backgorund information.
113 # Make sure the stream is stopped in Kodi and the gstreamer process is
114 # killed if something go wrong (for example if curl is unable to find the
115 # kodi server). Do the same when interrupting this script.
119 params=
"$
3"
120 curl --silent --header
'Content-Type: application/json
' \
121 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
122 "http://$host/jsonrpc
"
125 if [ -n
"$kodihost
" ] ; then
126 # Stop the playing when we end
127 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
128 jq .result[].playerid)
129 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
131 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
132 kill
"$gstpid
"
135 trap cleanup EXIT INT
137 if [ -n
"$
1" ]; then
148 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
149 cut -d
" " -f2|head -
1)
150 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
151 videoconvert ! queue2 ! \
152 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
153 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
154 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
155 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
156 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
157 > /dev/null
2>&1 &
160 # Give stream a second to get going
163 # Ask kodi to start streaming using its JSON-RPC API
164 kodicmd
"$kodihost
" Player.Open \
165 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
167 # wait for gst to end
168 wait
"$gstpid
"
169 </pre
></blockquote
>
171 <p
>I hope you find the approach useful. I know I do.
</p
>
173 <p
>As usual, if you use Bitcoin and want to show your support of my
174 activities, please send Bitcoin donations to my address
175 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
180 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
181 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
182 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
183 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
184 <description><p
>PS: See
185 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
186 followup post
</a
> for a even better approach.
</p
>
188 <p
>A while back, I was asked by a friend how to stream the desktop to
189 my projector connected to Kodi. I sadly had to admit that I had no
190 idea, as it was a task I never had tried. Since then, I have been
191 looking for a way to do so, preferable without much extra software to
192 install on either side. Today I found a way that seem to kind of
193 work. Not great, but it is a start.
</p
>
195 <p
>I had a look at several approaches, for example
196 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
197 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
198 local storage enough to store the stream locally. This is not going
199 to work well for me, lacking enough free space, and it would
200 impossible for my friend to get working.
</p
>
202 <p
>Next, it occurred to me that perhaps I could use VLC to create a
203 video stream that Kodi could play. Preferably using
204 broadcast/multicast, to avoid having to change any setup on the Kodi
205 side when starting such stream. Unfortunately, the only recipe I
206 could find using multicast used the rtp protocol, and this protocol
207 seem to not be supported by Kodi.
</p
>
209 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
210 have to specify the IP address of the streaming machine in both the
211 sending command and the file on the Kodi server. But it is showing my
212 desktop, and thus allow us to have a shared look on the big screen at
213 the programs I work on.
</p
>
215 <p
>I did not spend much time investigating codeces. I combined the
216 rtp and rtsp recipes from
217 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
218 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
219 this working on the desktop/streaming end.
</p
>
221 <blockquote
><pre
>
222 vlc screen:// --sout \
223 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
224 </pre
></blockquote
>
226 <p
>I ssh-ed into my Kodi box and created a file like this with the
227 same IP address:
</p
>
229 <blockquote
><pre
>
230 echo rtsp://
192.168.11.4:
8080/test.sdp \
231 > /storage/videos/screenstream.m3u
232 </pre
></blockquote
>
234 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
235 as I can tell the IP must be hardcoded for this to work. In other
236 words, if someone elses machine is going to do the steaming, you have
237 to update screenstream.m3u on the Kodi machine and adjust the vlc
238 recipe. To get started, locate the file in Kodi and select the m3u
239 file while the VLC stream is running. The desktop then show up in my
240 big screen. :)
</p
>
242 <p
>When using the same technique to stream a video file with audio,
243 the audio quality is really bad. No idea if the problem is package
244 loss or bad parameters for the transcode. I do not know VLC nor Kodi
245 enough to tell.
</p
>
247 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
248 succestions and reminded me about an important step. The
"screen:
"
249 input source is only available once the vlc-plugin-access-extra
250 package is installed on Debian. Without it, you will see this error
251 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
252 for details.
" He further found that it is possible to drop some parts
253 of the VLC command line to reduce the amount of hardcoded information.
254 It is also useful to consider using cvlc to avoid having the VLC
255 window in the desktop view. In sum, this give us this command line on
258 <blockquote
><pre
>
259 cvlc screen:// --sout \
260 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
261 </pre
></blockquote
>
263 <p
>and this on the Kodi end
<p
>
265 <blockquote
><pre
>
266 echo rtsp://
192.168.11.4:
8080/ \
267 > /storage/videos/screenstream.m3u
268 </pre
></blockquote
>
270 <p
>Still bad image quality, though. But I did discover that streaming
271 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
272 audio quality, so I guess the issue is in the input or transcoding
273 parts, not the rtsp part. I
've tried to change the vb and ab
274 parameters to use more bandwidth, but it did not make a
275 difference.
</p
>
277 <p
>I further received a suggestion from Einar Haraldseid to try using
278 gstreamer instead of VLC, and this proved to work great! He also
279 provided me with the trick to get Kodi to use a multicast stream as
280 its source. By using this monstrous oneliner, I can stream my desktop
281 with good video quality in reasonable framerate to the
239.255.0.1
282 multicast address on port
1234:
284 <blockquote
><pre
>
285 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
286 videoconvert ! queue2 ! \
287 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
288 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
289 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
290 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
291 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
292 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
293 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
294 </pre
></blockquote
>
296 <p
>and this on the Kodi end
<p
>
298 <blockquote
><pre
>
299 echo udp://@
239.255.0.1:
1234 \
300 > /storage/videos/screenstream.m3u
301 </pre
></blockquote
>
303 <p
>Note the trick to pick a valid pulseaudio source. It might not
304 pick the one you need. This approach will of course lead to trouble
305 if more than one source uses the same multicast port and address.
306 Note the ttl-mc=
1 setting, which limit the multicast packages to the
307 local network. If the value is increased, your screen will be
308 broadcasted further, one network
"hop
" for each increase (read up on
309 multicast to learn more. :)!
</p
>
311 <p
>Having cracked how to get Kodi to receive multicast streams, I
312 could use this VLC command to stream to the same multicast address.
313 The image quality is way better than the rtsp approach, but gstreamer
314 seem to be doing a better job.
</p
>
316 <blockquote
><pre
>
317 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
318 </pre
></blockquote
>
320 <p
>As usual, if you use Bitcoin and want to show your support of my
321 activities, please send Bitcoin donations to my address
322 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
327 <title>What is the most supported MIME type in Debian in
2018?
</title>
328 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
329 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
330 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
331 <description><p
>Five years ago,
332 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
333 measured what the most supported MIME type in Debian was
</a
>, by
334 analysing the desktop files in all packages in the archive. Since
335 then, the DEP-
11 AppStream system has been put into production, making
336 the task a lot easier. This made me want to repeat the measurement,
337 to see how much things changed. Here are the new numbers, for
338 unstable only this time:
340 <p
><strong
>Debian Unstable:
</strong
></p
>
344 ----- -----------------------
356 30 audio/x-vorbis+ogg
357 29 image/x-portable-pixmap
359 27 image/x-portable-bitmap
367 <p
>The list was created like this using a sid chroot:
"cat
368 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
369 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
371 <p
>It is interesting to see how image formats have passed text/plain
372 as the most announced supported MIME type. These days, thanks to the
373 AppStream system, if you run into a file format you do not know, and
374 want to figure out which packages support the format, you can find the
375 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
376 look up all packages announcing support for this format in their
377 AppStream metadata (XML or .desktop file) using
"appstreamcli
378 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
379 me, want to know which packages support inode/directory, you can get a
380 list like this:
</p
>
382 <p
><blockquote
><pre
>
383 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
390 Package: doublecmd-common
392 Package: enlightenment
412 </pre
></blockquote
></p
>
414 <p
>Using the same method, I can quickly discover that the Sketchup file
415 format is not yet supported by any package in Debian:
</p
>
417 <p
><blockquote
><pre
>
418 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
419 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
421 </pre
></blockquote
></p
>
423 <p
>Yesterday I used it to figure out which packages support the STL
3D
426 <p
><blockquote
><pre
>
427 % appstreamcli what-provides mimetype application/sla|grep Package
432 </pre
></blockquote
></p
>
434 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
436 <p
>As usual, if you use Bitcoin and want to show your support of my
437 activities, please send Bitcoin donations to my address
438 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
443 <title>Debian APT upgrade without enough free space on the disk...
</title>
444 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
445 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
446 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
447 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
448 for a while, and when I need to update it there is not enough free
449 space on the disk for apt to do a normal
'apt upgrade
'. I normally
450 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
451 upgrade only some of the packages in one batch, until the amount of
452 packages to download fall below the amount of free space available.
453 Today, I had about
500 packages to upgrade, and after a while I got
454 tired of trying to install chunks of packages manually. I concluded
455 that I did not have the spare hours required to complete the task, and
456 decided to see if I could automate it. I came up with this small
457 script which I call
'apt-in-chunks
':
</p
>
459 <p
><blockquote
><pre
>
462 # Upgrade packages when the disk is too full to upgrade every
463 # upgradable package in one lump. Fetching packages to upgrade using
464 # apt, and then installing using dpkg, to avoid changing the package
465 # flag for manual/automatic.
470 if [
"$
1" ]; then
471 grep -v
"$
1"
477 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
478 echo
"Upgrading $p
"
480 apt install --download-only -y $p
481 for f in /var/cache/apt/archives/*.deb; do
482 if [ -e
"$f
" ]; then
483 dpkg -i /var/cache/apt/archives/*.deb
488 </pre
></blockquote
></p
>
490 <p
>The script will extract the list of packages to upgrade, try to
491 download the packages needed to upgrade one package, install the
492 downloaded packages using dpkg. The idea is to upgrade packages
493 without changing the APT mark for the package (ie the one recording of
494 the package was manually requested or pulled in as a dependency). To
495 use it, simply run it as root from the command line. If it fail, try
496 'apt install -f
' to clean up the mess and run the script again. This
497 might happen if the new packages conflict with one of the old
498 packages. dpkg is unable to remove, while apt can do this.
</p
>
500 <p
>It take one option, a package to ignore in the list of packages to
501 upgrade. The option to ignore a package is there to be able to skip
502 the packages that are simply too large to unpack. Today this was
503 'ghc
', but I have run into other large packages causing similar
504 problems earlier (like TeX).
</p
>
506 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
507 alternative ways to handle this. The
"unattended-upgrades
508 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
509 each package to upgrade, and then upgrade them in order, smallest set
510 first. It might be a better option than my above mentioned script.
511 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
512 the need for using
"dpkg -i
" in the script above.
</p
>
514 <p
>As usual, if you use Bitcoin and want to show your support of my
515 activities, please send Bitcoin donations to my address
516 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
521 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
522 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
523 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
524 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
525 <description><p
>A new version of the
526 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
527 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
528 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
529 useful. It was uploaded the last few days, and the last update will
530 enter testing tomorrow. See the
531 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
532 notes
</a
> for the list of bug fixes and new features. Version
3.2
533 was announced
6 days ago. We will try to get it into Debian as
536 <p
>More information related to
3D printing is available on the
537 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
538 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
541 <p
>As usual, if you use Bitcoin and want to show your support of my
542 activities, please send Bitcoin donations to my address
543 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
548 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
549 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
551 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
552 <description><p
>After several months of working and waiting, I am happy to report
553 that the nice and user friendly
3D printer slicer software Cura just
554 entered Debian Unstable. It consist of five packages,
555 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
556 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
557 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
558 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
559 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
560 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
561 two, uranium and cura, entered Unstable yesterday. This should make
562 it easier for Debian users to print on at least the Ultimaker class of
563 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
564 make life easier for at least me. :)
</p
>
566 <p
>The work to make this happen was done by Gregor Riepl, and I was
567 happy to assist him in sponsoring the packages. With the introduction
568 of Cura, Debian is up to three
3D printer slicers at your service,
569 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
570 printer, give it a go. :)
</p
>
572 <p
>The
3D printer software is maintained by the
3D printer Debian
573 team, flocking together on the
574 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
576 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
577 IRC channel.
</p
>
579 <p
>The next step for Cura in Debian is to update the cura package to
580 version
3.0.3 and then update the entire set of packages to version
581 3.1.0 which showed up the last few days.
</p
>
586 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
587 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
588 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
589 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
590 <description><p
>At my nearby maker space,
591 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
592 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
593 on Windows and MacOS X than Linux, because the software involved had
594 to be manually compiled and set up on Linux while premade packages
595 worked out of the box on Windows and MacOS X. I found this annoying,
596 as the software involved,
597 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
598 and should be trivial to get up and running on Linux if someone took
599 the time to package it for the relevant distributions. I even found
600 <a href=
"https://bugs.debian.org/
706656">a request for adding into
601 Debian
</a
> from
2013, which had seem some activity over the years but
602 never resulted in the software showing up in Debian. So a few days
603 ago I offered my help to try to improve the situation.
</p
>
605 <p
>Now I am very happy to see that all the packages required by a
606 working Cura in Debian are uploaded into Debian and waiting in the NEW
607 queue for the ftpmasters to have a look. You can track the progress
609 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
610 status page for the
3D printer team
</a
>.
</p
>
612 <p
>The uploaded packages are a bit behind upstream, and was uploaded
613 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
614 queue
</a
> while we work up updating the packages to the latest
615 upstream version.
</p
>
617 <p
>On a related note, two competitors for Cura, which I found harder
618 to use and was unable to configure correctly for Ultimaker
2+ in the
619 short time I spent on it, are already in Debian. If you are looking
620 for
3D printer
"slicers
" and want something already available in
622 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
623 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
624 The latter is a fork of the former.
</p
>
626 <p
>As usual, if you use Bitcoin and want to show your support of my
627 activities, please send Bitcoin donations to my address
628 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
633 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
634 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
636 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
637 <description><p
>Every mobile phone announce its existence over radio to the nearby
638 mobile cell towers. And this radio chatter is available for anyone
639 with a radio receiver capable of receiving them. Details about the
640 mobile phones with very good accuracy is of course collected by the
641 phone companies, but this is not the topic of this blog post. The
642 mobile phone radio chatter make it possible to figure out when a cell
643 phone is nearby, as it include the SIM card ID (IMSI). By paying
644 attention over time, one can see when a phone arrive and when it leave
645 an area. I believe it would be nice to make this information more
646 available to the general public, to make more people aware of how
647 their phones are announcing their whereabouts to anyone that care to
650 <p
>I am very happy to report that we managed to get something
651 visualizing this information up and running for
652 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
653 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
654 library. The solution is based on the
655 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
656 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
657 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
658 Sone from the Computer Science department of the University of
659 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
660 IMSIs) as dots in a web browser graph, with lines to the dot
661 representing mobile base station it is talking to. It was working in
662 the lab yesterday, and was moved into place this morning.
</p
>
664 <p
>We set up a fairly powerful desktop machine using Debian
665 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
666 connected and visualize the visible cell phone towers using an
667 <a href=
"https://github.com/marlow925/hopglass
">English version of
668 Hopglass
</a
>. A fairly powerfull machine is needed as the
669 grgsm_livemon_headless processes from
670 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
671 the radio signal to data packages is quite CPU intensive.
</p
>
673 <p
>The frequencies to listen to, are identified using a slightly
674 patched scan-and-livemon (to set the --args values for each receiver),
675 and the Hopglass data is generated using the
676 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
677 in my meshviewer-output branch
</a
>. For some reason we could not get
678 more than four SDRs working. There is also a geographical map trying
679 to show the location of the base stations, but I believe their
680 coordinates are hardcoded to some random location in Germany, I
681 believe. The code should be replaced with code to look up location in
682 a text file, a sqlite database or one of the online databases
684 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
685 issue for the topic
</a
>.
687 <p
>If this sound interesting, visit the stand at the festival!
</p
>
692 <title>Easier recipe to observe the cell phones around you
</title>
693 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
694 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
695 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
696 <description><p
>A little more than a month ago I wrote
697 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
698 to observe the SIM card ID (aka IMSI number) of mobile phones talking
699 to nearby mobile phone base stations using Debian GNU/Linux and a
700 cheap USB software defined radio
</a
>, and thus being able to pinpoint
701 the location of people and equipment (like cars and trains) with an
702 accuracy of a few kilometer. Since then we have worked to make the
703 procedure even simpler, and it is now possible to do this without any
704 manual frequency tuning and without building your own packages.
</p
>
706 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
707 package is now included in Debian testing and unstable, and the
708 IMSI-catcher code no longer require root access to fetch and decode
709 the GSM data collected using gr-gsm.
</p
>
711 <p
>Here is an updated recipe, using packages built by Debian and a git
712 clone of two python scripts:
</p
>
716 <li
>Start with a Debian machine running the Buster version (aka
719 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
720 python-scapy
</tt
>' as root to install required packages.
</li
>
722 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
723 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
725 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
727 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
728 scan-and-livemon
</tt
>' to locate the frequency of nearby base
729 stations and start listening for GSM packages on one of them.
</li
>
731 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
732 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
736 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
737 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
738 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
739 work with RTL
8232 and other similar USB radio receivers you can get
741 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
742 from ebay
</a
>), so for now the solution is to scan using the RTL radio
743 and only use HackRF for fetching GSM data.
</p
>
745 <p
>As far as I can tell, a cell phone only show up on one of the
746 frequencies at the time, so if you are going to track and count every
747 cell phone around you, you need to listen to all the frequencies used.
748 To listen to several frequencies, use the --numrecv argument to
749 scan-and-livemon to use several receivers. Further, I am not sure if
750 phones using
3G or
4G will show as talking GSM to base stations, so
751 this approach might not see all phones around you. I typically see
752 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
754 <p
>I
've tried to run the scanner on a
755 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
756 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
757 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
758 stdout, I am told there it is caused by a buffer overflow between the
759 radio and GNU Radio, caused by the program being unable to read the
760 GSM data fast enough. If you see a stream of
'O
's from the terminal
761 where you started scan-and-livemon, you need a give the process more
762 CPU power. Perhaps someone are able to optimize the code to a point
763 where it become possible to set up RPi3 based GSM sniffers? I tried
764 using Raspbian instead of Debian, but there seem to be something wrong
765 with GNU Radio on raspbian, causing glibc to abort().
</p
>
770 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
771 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
773 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
774 <description><p
>On friday, I came across an interesting article in the Norwegian
775 web based ICT news magazine digi.no on
776 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
777 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
778 DVB-T software defined radios. The article refered to instructions
779 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
780 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
782 <p
>The instructions said to use Ubuntu, install pip using apt (to
783 bypass apt), use pip to install pybombs (to bypass both apt and pip),
784 and the ask pybombs to fetch and build everything you need from
785 scratch. I wanted to see if I could do the same on the most recent
786 Debian packages, but this did not work because pybombs tried to build
787 stuff that no longer build with the most recent openssl library or
788 some other version skew problem. While trying to get this recipe
789 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
790 and the only piece of software dependency missing in Debian was the
791 gr-gsm package. I also found out that the lead upstream developer of
792 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
793 Debian packages provided in an Ubuntu PPA repository. All I needed to
794 do was to dget the Debian source package and built it.
</p
>
796 <p
>The IMSI collector is a python script listening for packages on the
797 loopback network device and printing to the terminal some specific GSM
798 packages with IMSI numbers in them. The code is fairly short and easy
799 to understand. The reason this work is because gr-gsm include a tool
800 to read GSM data from a software defined radio like a DVB-T USB stick
801 and other software defined radios, decode them and inject them into a
802 network device on your Linux machine (using the loopback device by
803 default). This proved to work just fine, and I
've been testing the
804 collector for a few days now.
</p
>
806 <p
>The updated and simpler recipe is thus to
</p
>
810 <li
>start with a Debian machine running Stretch or newer,
</li
>
812 <li
>build and install the gr-gsm package available from
813 <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
>
815 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
817 <li
>run grgsm_livemon and adjust the frequency until the terminal
818 where it was started is filled with a stream of text (meaning you
819 found a GSM station).
</li
>
821 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
825 <p
>To make it even easier in the future to get this sniffer up and
826 running, I decided to package
827 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
828 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
829 #
871055</a
>), and the package was uploaded into the NEW queue today.
830 Luckily the gnuradio maintainer has promised to help me, as I do not
831 know much about gnuradio stuff yet.
</p
>
833 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
834 commercial tools like
835 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
836 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
837 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
838 Stingray
</a
>, but I hope the existance of cheap alternatives can make
839 more people realise how their whereabouts when carrying a cell phone
840 is easily tracked. Seeing the data flow on the screen, realizing that
841 I live close to a police station and knowing that the police is also
842 wearing cell phones, I wonder how hard it would be for criminals to
843 track the position of the police officers to discover when there are
844 police near by, or for foreign military forces to track the location
845 of the Norwegian military forces, or for anyone to track the location
846 of government officials...
</p
>
848 <p
>It is worth noting that the data reported by the IMSI-catcher
849 script mentioned above is only a fraction of the data broadcasted on
850 the GSM network. It will only collect one frequency at the time,
851 while a typical phone will be using several frequencies, and not all
852 phones will be using the frequencies tracked by the grgsm_livemod
853 program. Also, there is a lot of radio chatter being ignored by the
854 simple_IMSI-catcher script, which would be collected by extending the
855 parser code. I wonder if gr-gsm can be set up to listen to more than
856 one frequency?
</p
>
861 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
862 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
863 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
864 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
865 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
867 <p
>I finally received a copy of the Norwegian Bokmål edition of
868 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
869 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
870 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
871 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
872 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
873 price. The book is also available for download in electronic form as
874 PDF, EPUB and Mobipocket, as can be
875 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
876 as a web page
</a
>.
</p
>
878 <p
>This is the second book I publish (the first was the book
879 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
881 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
882 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
884 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
885 Bokmål
</a
>), and I am very excited to finally wrap up this
887 "<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
888 for Debian-administratoren
</a
>" will be well received.
</p
>
893 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
894 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
896 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
897 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
898 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
899 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
900 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
901 på om den fri oversetterløsningen
902 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
903 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
905 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
908 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
909 rolle og muligheter til å håndtere internasjonale utfordringer, som
910 for eksempel flykningekrisen.
</p
>
912 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
915 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
916 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
921 <p
>Dette oversetter Apertium slik:
</p
>
924 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
925 andre aktørar og høve til å handtera internasjonale utfordringar, som
926 til dømes *flykningekrisen.
</p
>
928 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
932 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
933 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
938 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
939 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
940 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
941 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
942 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
943 det er kanskje flisespikking. Det understreker vel bare at det alltid
944 trengs korrekturlesning etter automatisk oversettelse.
</p
>
949 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
950 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
951 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
952 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
953 <description><p
>Over the years, administrating thousand of NFS mounting linux
954 computers at the time, I often needed a way to detect if the machine
955 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
956 file or directory affected by the hang, the process (and possibly the
957 shell) will hang too. So you want to be able to detect this without
958 risking the detection process getting stuck too. It has not been
959 obvious how to do this. When the hang has lasted a while, it is
960 possible to find messages like these in dmesg:
</p
>
962 <p
><blockquote
>
963 nfs: server nfsserver not responding, still trying
964 <br
>nfs: server nfsserver OK
965 </blockquote
></p
>
967 <p
>It is hard to know if the hang is still going on, and it is hard to
968 be sure looking in dmesg is going to work. If there are lots of other
969 messages in dmesg the lines might have rotated out of site before they
970 are noticed.
</p
>
972 <p
>While reading through the nfs client implementation in linux kernel
973 code, I came across some statistics that seem to give a way to detect
974 it. The om_timeouts sunrpc value in the kernel will increase every
975 time the above log entry is inserted into dmesg. And after digging a
976 bit further, I discovered that this value show up in
977 /proc/self/mountstats on Linux.
</p
>
979 <p
>The mountstats content seem to be shared between files using the
980 same file system context, so it is enough to check one of the
981 mountstats files to get the state of the mount point for the machine.
982 I assume this will not show lazy umounted NFS points, nor NFS mount
983 points in a different process context (ie with a different filesystem
984 view), but that does not worry me.
</p
>
986 <p
>The content for a NFS mount point look similar to this:
</p
>
988 <p
><blockquote
><pre
>
990 device /dev/mapper/Debian-var mounted on /var with fstype ext3
991 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
992 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
994 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
995 sec: flavor=
1,pseudoflavor=
1
996 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
997 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
998 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
999 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1001 NULL:
0 0 0 0 0 0 0 0
1002 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1003 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
1004 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1005 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1006 READLINK:
125 125 0 20472 18620 0 1112 1118
1007 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1008 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1009 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
1010 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
1011 SYMLINK:
903 903 0 233428 245488 6 5865 5917
1012 MKNOD:
80 80 0 20148 21760 0 299 304
1013 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
1014 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
1015 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
1016 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
1017 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1018 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1019 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
1020 FSINFO:
2 2 0 232 328 0 1 1
1021 PATHCONF:
1 1 0 116 140 0 0 0
1022 COMMIT:
0 0 0 0 0 0 0 0
1024 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1026 </pre
></blockquote
></p
>
1028 <p
>The key number to look at is the third number in the per-op list.
1029 It is the number of NFS timeouts experiences per file system
1030 operation. Here
22 write timeouts and
5 access timeouts. If these
1031 numbers are increasing, I believe the machine is experiencing NFS
1032 hang. Unfortunately the timeout value do not start to increase right
1033 away. The NFS operations need to time out first, and this can take a
1034 while. The exact timeout value depend on the setup. For example the
1035 defaults for TCP and UDP mount points are quite different, and the
1036 timeout value is affected by the soft, hard, timeo and retrans NFS
1037 mount options.
</p
>
1039 <p
>The only way I have been able to get working on Debian and RedHat
1040 Enterprise Linux for getting the timeout count is to peek in /proc/.
1042 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
1043 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
1044 command can be used to get these timeout values. But this do not work
1045 on Linux, as far as I can tell. I
1046 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
1047 but have not seen any replies yet.
</p
>
1049 <p
>Is there a better way to figure out if a Linux NFS client is
1050 experiencing NFS hangs? Is there a way to detect which processes are
1051 affected? Is there a way to get the NFS mount going quickly once the
1052 network problem causing the NFS hang has been cleared? I would very
1053 much welcome some clues, as we regularly run into NFS hangs.
</p
>
1058 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
1059 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
1060 <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>
1061 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
1062 <description><p
>For almost a year now, we have been working on making a Norwegian
1063 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
1064 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
1065 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1066 we are working on the proof reading to ensure consistent language and
1067 use of correct computer science terms. The plan is to make the book
1068 available on paper, as well as in electronic form. For that to
1069 happen, the proof reading must be completed and all the figures need
1070 to be translated. If you want to help out, get in touch.
</p
>
1072 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
1074 fresh PDF edition
</a
> in A4 format (the final book will have smaller
1075 pages) of the book created every morning is available for
1076 proofreading. If you find any errors, please
1077 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
1078 Weblate and correct the error
</a
>. The
1079 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
1080 of the translation including figures
</a
> is a useful source for those
1081 provide Norwegian bokmål screen shots and figures.
</p
>
1086 <title>Unlimited randomness with the ChaosKey?
</title>
1087 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
1088 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
1089 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
1090 <description><p
>A few days ago I ordered a small batch of
1091 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
1092 USB dongle for generating entropy created by Bdale Garbee and Keith
1093 Packard. Yesterday it arrived, and I am very happy to report that it
1094 work great! According to its designers, to get it to work out of the
1095 box, you need the Linux kernel version
4.1 or later. I tested on a
1096 Debian Stretch machine (kernel version
4.9), and there it worked just
1097 fine, increasing the available entropy very quickly. I wrote a small
1098 test oneliner to test. It first print the current entropy level,
1099 drain /dev/random, and then print the entropy level for five seconds.
1100 Here is the situation without the ChaosKey inserted:
</p
>
1102 <blockquote
><pre
>
1103 % cat /proc/sys/kernel/random/entropy_avail; \
1104 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
1105 for n in $(seq
1 5); do \
1106 cat /proc/sys/kernel/random/entropy_avail; \
1112 28 byte kopiert,
0,
000264565 s,
106 kB/s
1119 </pre
></blockquote
>
1121 <p
>The entropy level increases by
3-
4 every second. In such case any
1122 application requiring random bits (like a HTTPS enabled web server)
1123 will halt and wait for more entrpy. And here is the situation with
1124 the ChaosKey inserted:
</p
>
1126 <blockquote
><pre
>
1127 % cat /proc/sys/kernel/random/entropy_avail; \
1128 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
1129 for n in $(seq
1 5); do \
1130 cat /proc/sys/kernel/random/entropy_avail; \
1136 104 byte kopiert,
0,
000487647 s,
213 kB/s
1143 </pre
></blockquote
>
1145 <p
>Quite the difference. :) I bought a few more than I need, in case
1146 someone want to buy one here in Norway. :)
</p
>
1148 <p
>Update: The dongle was presented at Debconf last year. You might
1149 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
1150 recording illuminating
</a
>. It explains exactly what the source of
1151 randomness is, if you are unable to spot it from the schema drawing
1152 available from the ChaosKey web site linked at the start of this blog
1158 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
1159 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
1160 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
1161 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
1162 <description><p
>Did you ever wonder where the web trafic really flow to reach the
1163 web servers, and who own the network equipment it is flowing through?
1164 It is possible to get a glimpse of this from using traceroute, but it
1165 is hard to find all the details. Many years ago, I wrote a system to
1166 map the Norwegian Internet (trying to figure out if our plans for a
1167 network game service would get low enough latency, and who we needed
1168 to talk to about setting up game servers close to the users. Back
1169 then I used traceroute output from many locations (I asked my friends
1170 to run a script and send me their traceroute output) to create the
1171 graph and the map. The output from traceroute typically look like
1174 <p
><pre
>
1175 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
1176 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
1177 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
1178 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
1179 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
1180 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
1181 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
1182 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
1186 </pre
></p
>
1188 <p
>This show the DNS names and IP addresses of (at least some of the)
1189 network equipment involved in getting the data traffic from me to the
1190 www.stortinget.no server, and how long it took in milliseconds for a
1191 package to reach the equipment and return to me. Three packages are
1192 sent, and some times the packages do not follow the same path. This
1193 is shown for hop
5, where three different IP addresses replied to the
1194 traceroute request.
</p
>
1196 <p
>There are many ways to measure trace routes. Other good traceroute
1197 implementations I use are traceroute (using ICMP packages) mtr (can do
1198 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1199 traceroute and a lot of other capabilities). All of them are easily
1200 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
1202 <p
>This time around, I wanted to know the geographic location of
1203 different route points, to visualize how visiting a web page spread
1204 information about the visit to a lot of servers around the globe. The
1205 background is that a web site today often will ask the browser to get
1206 from many servers the parts (for example HTML, JSON, fonts,
1207 JavaScript, CSS, video) required to display the content. This will
1208 leak information about the visit to those controlling these servers
1209 and anyone able to peek at the data traffic passing by (like your ISP,
1210 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
1212 <p
>Lets pick an example, the Norwegian parliament web site
1213 www.stortinget.no. It is read daily by all members of parliament and
1214 their staff, as well as political journalists, activits and many other
1215 citizens of Norway. A visit to the www.stortinget.no web site will
1216 ask your browser to contact
8 other servers: ajax.googleapis.com,
1217 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1218 stats.g.doubleclick.net, www.google-analytics.com,
1219 www.googletagmanager.com and www.netigate.se. I extracted this by
1220 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
1221 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1222 render the page (in HAR format using
1223 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
1224 netsniff example
</a
>. I am very grateful to Gorm for showing me how
1225 to do this). My goal is to visualize network traces to all IP
1226 addresses behind these DNS names, do show where visitors personal
1227 information is spread when visiting the page.
</p
>
1229 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
1230 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
>
1232 <p
>When I had a look around for options, I could not find any good
1233 free software tools to do this, and decided I needed my own traceroute
1234 wrapper outputting KML based on locations looked up using GeoIP. KML
1235 is easy to work with and easy to generate, and understood by several
1236 of the GIS tools I have available. I got good help from by NUUG
1237 colleague Anders Einar with this, and the result can be seen in
1238 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
1239 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
1240 free GeoIP databases I could find (and the for-pay databases my
1241 friends had access to) is not up to the task. The IP addresses of
1242 central Internet infrastructure would typically be placed near the
1243 controlling companies main office, and not where the router is really
1244 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
1245 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
1247 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
1248 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
>
1250 <p
>I also had a look at the visual traceroute graph created by
1251 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
1252 showing IP network ownership (aka AS owner) for the IP address in
1254 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
1255 graph display a lot of useful information about the traceroute in SVG
1256 format
</a
>, and give a good indication on who control the network
1257 equipment involved, but it do not include geolocation. This graph
1258 make it possible to see the information is made available at least for
1259 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1260 3 Communications and NetDNA.
</p
>
1262 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
1263 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
>
1265 <p
>In the process, I came across the
1266 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
1267 Salim Gasmi. Its methology of combining guesses based on DNS names,
1268 various location databases and finally use latecy times to rule out
1269 candidate locations seemed to do a very good job of guessing correct
1270 geolocation. But it could only do one trace at the time, did not have
1271 a sensor in Norway and did not make the geolocations easily available
1272 for postprocessing. So I contacted the developer and asked if he
1273 would be willing to share the code (he refused until he had time to
1274 clean it up), but he was interested in providing the geolocations in a
1275 machine readable format, and willing to set up a sensor in Norway. So
1276 since yesterday, it is possible to run traces from Norway in this
1277 service thanks to a sensor node set up by
1278 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
1279 trace in KML format for further processing.
</p
>
1281 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
1282 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
>
1284 <p
>Here we can see a lot of trafic passes Sweden on its way to
1285 Denmark, Germany, Holland and Ireland. Plenty of places where the
1286 Snowden confirmations verified the traffic is read by various actors
1287 without your best interest as their top priority.
</p
>
1289 <p
>Combining KML files is trivial using a text editor, so I could loop
1290 over all the hosts behind the urls imported by www.stortinget.no and
1291 ask for the KML file from GeoTraceroute, and create a combined KML
1292 file with all the traces (unfortunately only one of the IP addresses
1293 behind the DNS name is traced this time. To get them all, one would
1294 have to request traces using IP number instead of DNS names from
1295 GeoTraceroute). That might be the next step in this project.
</p
>
1297 <p
>Armed with these tools, I find it a lot easier to figure out where
1298 the IP traffic moves and who control the boxes involved in moving it.
1299 And every time the link crosses for example the Swedish border, we can
1300 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1301 Britain and NSA in USA and cables around the globe. (Hm, what should
1302 we tell them? :) Keep that in mind if you ever send anything
1303 unencrypted over the Internet.
</p
>
1305 <p
>PS: KML files are drawn using
1306 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
1307 Rublev
<a/
>, as it was less cluttered than the local Linux application
1308 Marble. There are heaps of other options too.
</p
>
1310 <p
>As usual, if you use Bitcoin and want to show your support of my
1311 activities, please send Bitcoin donations to my address
1312 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1317 <title>Appstream just learned how to map hardware to packages too!
</title>
1318 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
1319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
1320 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
1321 <description><p
>I received a very nice Christmas present today. As my regular
1322 readers probably know, I have been working on the
1323 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
1324 system
</a
> for many years. The goal of the Isenkram system is to make
1325 it easier for users to figure out what to install to get a given piece
1326 of hardware to work in Debian, and a key part of this system is a way
1327 to map hardware to packages. Isenkram have its own mapping database,
1328 and also uses data provided by each package using the AppStream
1329 metadata format. And today,
1330 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
1331 Debian learned to look up hardware the same way Isenkram is doing it,
1332 ie using fnmatch():
</p
>
1334 <p
><pre
>
1335 % appstreamcli what-provides modalias \
1336 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1337 Identifier: pymissile [generic]
1339 Summary: Control original Striker USB Missile Launcher
1341 % appstreamcli what-provides modalias usb:v0694p0002d0000
1342 Identifier: libnxt [generic]
1344 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1347 Identifier: t2n [generic]
1349 Summary: Simple command-line tool for Lego NXT
1352 Identifier: python-nxt [generic]
1354 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1357 Identifier: nbc [generic]
1359 Summary: C compiler for LEGO Mindstorms NXT bricks
1362 </pre
></p
>
1364 <p
>A similar query can be done using the combined AppStream and
1365 Isenkram databases using the isenkram-lookup tool:
</p
>
1367 <p
><pre
>
1368 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1370 % isenkram-lookup usb:v0694p0002d0000
1376 </pre
></p
>
1378 <p
>You can find modalias values relevant for your machine using
1379 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
1381 <p
>If you want to make this system a success and help Debian users
1382 make the most of the hardware they have, please
1383 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
1384 AppStream metadata for your package following the guidelines
</a
>
1385 documented in the wiki. So far only
11 packages provide such
1386 information, among the several hundred hardware specific packages in
1387 Debian. The Isenkram database on the other hand contain
101 packages,
1388 mostly related to USB dongles. Most of the packages with hardware
1389 mapping in AppStream are LEGO Mindstorms related, because I have, as
1390 part of my involvement in
1391 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
1392 team
</a
> given priority to making sure LEGO users get proposed the
1393 complete set of packages in Debian for that particular hardware. The
1394 team also got a nice Christmas present today. The
1395 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
1396 package
</a
> made it into Debian. With this package in place, it is
1397 now possible to use the LEGO Mindstorms NXT unit with only free
1398 software, as the nxt-firmware package contain the source and firmware
1399 binaries for the NXT brick.
</p
>
1401 <p
>As usual, if you use Bitcoin and want to show your support of my
1402 activities, please send Bitcoin donations to my address
1403 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1408 <title>Isenkram updated with a lot more hardware-package mappings
</title>
1409 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
1410 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
1411 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
1412 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1413 system
</a
> I wrote two years ago to make it easier in Debian to find
1414 and install packages to get your hardware dongles to work, is still
1415 going strong. It is a system to look up the hardware present on or
1416 connected to the current system, and map the hardware to Debian
1417 packages. It can either be done using the tools in isenkram-cli or
1418 using the user space daemon in the isenkram package. The latter will
1419 notify you, when inserting new hardware, about what packages to
1420 install to get the dongle working. It will even provide a button to
1421 click on to ask packagekit to install the packages.
</p
>
1423 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
1425 <p
><pre
>
1442 </pre
></p
>
1444 <p
>It can also list the firware package providing firmware requested
1445 by the load kernel modules, which in my case is an empty list because
1446 I have all the firmware my machine need:
1448 <p
><pre
>
1449 % /usr/sbin/isenkram-autoinstall-firmware -l
1450 info: did not find any firmware files requested by loaded kernel modules. exiting
1452 </pre
></p
>
1454 <p
>The last few days I had a look at several of the around
250
1455 packages in Debian with udev rules. These seem like good candidates
1456 to install when a given hardware dongle is inserted, and I found
1457 several that should be proposed by isenkram. I have not had time to
1458 check all of them, but am happy to report that now there are
97
1459 packages packages mapped to hardware by Isenkram.
11 of these
1460 packages provide hardware mapping using AppStream, while the rest are
1461 listed in the modaliases file provided in isenkram.
</p
>
1463 <p
>These are the packages with hardware mappings at the moment. The
1464 <strong
>marked packages
</strong
> are also announcing their hardware
1465 support using AppStream, for everyone to use:
</p
>
1467 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
1468 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
1469 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
1470 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
1471 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
1472 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1473 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
1474 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1475 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1476 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1477 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
1478 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1479 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
1480 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1481 pcscd, pidgin-blinklight, printer-driver-splix,
1482 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
1483 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1484 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1485 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1486 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1487 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1488 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1489 xserver-xorg-video-vmware, yubikey-personalization and
1490 zd1211-firmware
</p
>
1492 <p
>If you know of other packages, please let me know with a wishlist
1493 bug report against the isenkram-cli package, and ask the package
1495 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
1496 metadata according to the guidelines
</a
> to provide the information
1497 for everyone. In time, I hope to get rid of the isenkram specific
1498 hardware mapping and depend exclusively on AppStream.
</p
>
1500 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
1501 much hardware, and suggest that the package with with any ethernet
1502 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
1503 the details. I hope the maintainer find time to address it soon. In
1504 the mean time I provide an override in isenkram.
</p
>
1509 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
1510 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
1511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
1512 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
1513 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
1515 <p
>In my early years, I played
1516 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
1517 Elite
</a
> on my PC. I spent many months trading and fighting in
1518 space, and reached the
'elite
' fighting status before I moved on. The
1519 original Elite game was available on Commodore
64 and the IBM PC
1520 edition I played had a
64 KB executable. I am still impressed today
1521 that the authors managed to squeeze both a
3D engine and details about
1522 more than
2000 planet systems across
7 galaxies into a binary so
1525 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
1526 software game Oolite inspired by Elite
</a
> for a while, but did not
1527 really have time to test it properly until a few days ago. It was
1528 great to discover that my old knowledge about trading routes were
1529 still valid. But my fighting and flying abilities were gone, so I had
1530 to retrain to be able to dock on a space station. And I am still not
1531 able to make much resistance when I am attacked by pirates, so I
1532 bougth and mounted the most powerful laser in the rear to be able to
1533 put up at least some resistance while fleeing for my life. :)
</p
>
1535 <p
>When playing Elite in the late eighties, I had to discover
1536 everything on my own, and I had long lists of prices seen on different
1537 planets to be able to decide where to trade what. This time I had the
1539 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
1540 where information about each planet is easily available with common
1541 price ranges and suggested trading routes. This improved my ability
1542 to earn money and I have been able to earn enough to buy a lot of
1543 useful equipent in a few days. I believe I originally played for
1544 months before I could get a docking computer, while now I could get it
1545 after less then a week.
</p
>
1547 <p
>If you like science fiction and dreamed of a life as a vagabond in
1548 space, you should try out Oolite. It is available for Linux, MacOSX
1549 and Windows, and is included in Debian and derivatives since
2011.
</p
>
1551 <p
>As usual, if you use Bitcoin and want to show your support of my
1552 activities, please send Bitcoin donations to my address
1553 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1558 <title>Quicker Debian installations using eatmydata
</title>
1559 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
1560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
1561 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
1562 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
1563 installation system, observing how using
1564 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
1565 could speed up the installation
</a
> quite a bit. My testing measured
1566 speedup around
20-
40 percent for Debian Edu, where we install around
1567 1000 packages from within the installer. The eatmydata package
1568 provide a way to disable/delay file system flushing. This is a bit
1569 risky in the general case, as files that should be stored on disk will
1570 stay only in memory a bit longer than expected, causing problems if a
1571 machine crashes at an inconvenient time. But for an installation, if
1572 the machine crashes during installation the process is normally
1573 restarted, and avoiding disk operations as much as possible to speed
1574 up the process make perfect sense.
1576 <p
>I added code in the Debian Edu specific installation code to enable
1577 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
1578 but did not have time to push it any further. But a few months ago I
1579 picked it up again and worked with the libeatmydata package maintainer
1580 Mattia Rizzolo to make it easier for everyone to get this installation
1581 speedup in Debian. Thanks to our cooperation There is now an
1582 eatmydata-udeb package in Debian testing and unstable, and simply
1583 enabling/installing it in debian-installer (d-i) is enough to get the
1584 quicker installations. It can be enabled using preseeding. The
1585 following untested kernel argument should do the trick:
</p
>
1587 <blockquote
><pre
>
1588 preseed/early_command=
"anna-install eatmydata-udeb
"
1589 </pre
></blockquote
>
1591 <p
>This should ask d-i to install the package inside the d-i
1592 environment early in the installation sequence. Having it installed
1593 in d-i in turn will make sure the relevant scripts are called just
1594 after debootstrap filled /target/ with the freshly installed Debian
1595 system to configure apt to run dpkg with eatmydata. This is enough to
1596 speed up the installation process. There is a proposal to
1597 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1598 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1599 tested its impact.
</p
>
1605 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1606 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1607 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1608 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1609 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1610 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1611 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1612 elever over det ganske land skal levere inn hvert år. Det mange ikke
1613 vet er at selv om de kommersielle alternativene
1614 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1615 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1616 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1617 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1618 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1619 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1620 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1621 nynorsk, og få den automatoversatt til det andre skriftspråket.
1622 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1623 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1624 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1625 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1626 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1627 teksten din i webskjemaet der.
1629 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1630 teknologien kan du enten installere pakken
1631 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1632 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1633 api.apertium.org. Se
1634 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1635 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1636 denne teksten som ble skrevet på bokmål over maskinoversatt til
1641 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1642 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1643 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1644 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1645 veit er at sjølv om dei kommersielle alternativa
1646 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1647 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1648 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1649 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1650 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1651 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1652 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1653 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1654 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1655 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1656 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1657 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1658 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1659 teksta di i *webskjemaet der.
1661 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1662 teknologien kan du anten installera pakken
1663 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1664 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1665 *api.*apertium.org. Sjå
1666 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1667 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1668 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1674 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1675 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1676 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1677 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1678 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1679 profiler able to run benchmarking experiments on the instrumented
1680 multi-threaded program, finally
1681 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1682 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1684 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1685 blogged about the coz tool
</a
> in August working with upstream to make
1686 it suitable for Debian. There are still issues with clang
1687 compatibility, inline assembly only working x86 and minimized
1688 JavaScript libraries.
</p
>
1690 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1692 <p
><blockquote
>
1693 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1694 </blockquote
></p
>
1696 <p
>This will produce a profile.coz file in the current working
1697 directory with the profiling information. This is then given to a
1698 JavaScript application provided in the package and available from
1699 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1700 To start the local copy, invoke it in a browser like this:
</p
>
1702 <p
><blockquote
>
1703 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1704 </blockquote
></p
>
1706 <p
>See the project home page and the
1707 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1708 ;login: article on Coz
</a
> for more information on how it is
1714 <title>My own self balancing Lego Segway
</title>
1715 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1716 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1717 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1718 <description><p
>A while back I received a Gyro sensor for the NXT
1719 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1720 present. It had been on my wishlist for a while, because I wanted to
1721 build a Segway like balancing lego robot. I had already built
1722 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1723 robot
</a
> with the kids, using the light/color sensor included in the
1724 NXT kit as the balance sensor, but it was not working very well. It
1725 could balance for a while, but was very sensitive to the light
1726 condition in the room and the reflective properties of the surface and
1727 would fall over after a short while. I wanted something more robust,
1729 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1730 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1731 wishlist for some years before it suddenly showed up as a gift from my
1732 loved ones. :)
</p
>
1734 <p
>Unfortunately I have not had time to sit down and play with it
1735 since then. But that changed some days ago, when I was searching for
1736 lego segway information and came across a recipe from HiTechnic for
1738 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1739 HTWay
</a
>, a segway like balancing robot. Build instructions and
1740 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1741 code
</a
> was included, so it was just a question of putting it all
1742 together. And thanks to the great work of many Debian developers, the
1743 compiler needed to build the source for the NXT is already included in
1744 Debian, so I was read to go in less than an hour. The resulting robot
1745 do not look very impressive in its simplicity:
</p
>
1747 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1749 <p
>Because I lack the infrared sensor used to control the robot in the
1750 design from HiTechnic, I had to comment out the last task
1751 (taskControl). I simply placed /* and */ around it get the program
1752 working without that sensor present. Now it balances just fine until
1753 the battery status run low:
</p
>
1755 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1756 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1757 </video
></p
>
1759 <p
>Now we would like to teach it how to follow a line and take remote
1760 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1762 <p
>If you, like me, love LEGO and want to make sure we find the tools
1763 they need to work with LEGO in Debian and all our derivative
1764 distributions like Ubuntu, check out
1765 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1766 project page
</a
> and join the Debian LEGO team. Personally I own a
1767 RCX and NXT controller (no EV3), and would like to make sure the
1768 Debian tools needed to program the systems I own work as they
1774 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1775 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1777 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1778 <description><p
>In July
1779 <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
1780 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1781 the ability to receive SMS messages (aka without a cell phone). It is
1782 time to share some experiences and provide an updated setup.
</p
>
1784 <p
>The Signal app have worked fine for several months now, and I use
1785 it regularly to chat with my loved ones. I had a major snag at the
1786 end of my summer vacation, when the the app completely forgot my
1787 setup, identity and keys. The reason behind this major mess was
1788 running out of disk space. To avoid that ever happening again I have
1789 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1790 roll back to an earlier version if the files are wiped by mistake. I
1791 had to use it once after introducing the git backup. When rolling
1792 back to an earlier version, one need to use the
'reset session
' option
1793 in Signal to get going, and notify the people you talk with about the
1794 problem. I assume there is some sequence number tracking in the
1795 protocol to detect rollback attacks. The git repository is rather big
1796 (
674 MiB so far), but I have not tried to figure out if some of the
1797 content can be added to a .gitignore file due to lack of spare
1800 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1801 make it impossible to send messages using Signal. I could still
1802 receive them, but had to patch the code with a new timestamp to send.
1803 I believe the timeout is added by the developers to force people to
1804 upgrade to the latest version of the app, even when there is no
1805 protocol changes, to reduce the version skew among the user base and
1806 thus try to keep the number of support requests down.
</p
>
1808 <p
>Since my original recipe, the Signal source code changed slightly,
1809 making the old patch fail to apply cleanly. Below is an updated
1810 patch, including the shell wrapper I use to start Signal. The
1811 original version required a new user to locate the JavaScript console
1812 and call a function from there. I got help from a friend with more
1813 JavaScript knowledge than me to modify the code to provide a GUI
1814 button instead. This mean that to get started you just need to run
1815 the wrapper and click the
'Register without mobile phone
' to get going
1816 now. I
've also modified the timeout code to always set it to
90 days
1817 in the future, to avoid having to patch the code regularly.
</p
>
1819 <p
>So, the updated recipe for Debian Jessie:
</p
>
1823 <li
>First, install required packages to get the source code and the
1824 browser you need. Signal only work with Chrome/Chromium, as far as I
1825 know, so you need to install it.
1828 apt install git tor chromium
1829 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1830 </pre
></li
>
1832 <li
>Modify the source code using command listed in the the patch
1833 block below.
</li
>
1835 <li
>Start Signal using the run-signal-app wrapper (for example using
1836 <tt
>`pwd`/run-signal-app
</tt
>).
1838 <li
>Click on the
'Register without mobile phone
', will in a phone
1839 number you can receive calls to the next minute, receive the
1840 verification code and enter it into the form field and press
1841 'Register
'. Note, the phone number you use will be user Signal
1842 username, ie the way others can find you on Signal.
</li
>
1844 <li
>You can now use Signal to contact others. Note, new contacts do
1845 not show up in the contact list until you restart Signal, and there is
1846 no way to assign names to Contacts. There is also no way to create or
1847 update chat groups. I suspect this is because the web app do not have
1848 a associated contact database.
</li
>
1852 <p
>I am still a bit uneasy about using Signal, because of the way its
1853 main author moxie0 reject federation and accept dependencies to major
1854 corporations like Google (part of the code is fetched from Google) and
1855 Amazon (the central coordination point is owned by Amazon). See for
1857 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
1858 LibreSignal issue tracker
</a
> for a thread documenting the authors
1859 view on these issues. But the network effect is strong in this case,
1860 and several of the people I want to communicate with already use
1861 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
1862 once it
<a href=
"https://bugs.debian.org/
830265">work on my
1863 laptop
</a
>? It already work on Windows and Android, and is included
1864 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
1865 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
1866 working on Debian Stable.
</p
>
1868 <p
>Anyway, this is the patch I apply to the Signal code to get it
1869 working. It switch to the production servers, disable to timeout,
1870 make registration easier and add the shell wrapper:
</p
>
1873 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
1874 diff --git a/js/background.js b/js/background.js
1875 index
24b4c1d.
.579345f
100644
1876 --- a/js/background.js
1877 +++ b/js/background.js
1882 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1883 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
1884 var SERVER_PORTS = [
80,
4433,
8443];
1885 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1886 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1887 var messageReceiver;
1888 window.getSocketStatus = function() {
1889 if (messageReceiver) {
1890 diff --git a/js/expire.js b/js/expire.js
1891 index
639aeae..beb91c3
100644
1896 'use strict
';
1897 - var BUILD_EXPIRATION =
0;
1898 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
1900 window.extension = window.extension || {};
1902 diff --git a/js/views/install_view.js b/js/views/install_view.js
1903 index
7816f4f.
.1d6233b
100644
1904 --- a/js/views/install_view.js
1905 +++ b/js/views/install_view.js
1908 'click .step1
': this.selectStep.bind(this,
1),
1909 'click .step2
': this.selectStep.bind(this,
2),
1910 -
'click .step3
': this.selectStep.bind(this,
3)
1911 +
'click .step3
': this.selectStep.bind(this,
3),
1912 +
'click .callreg
': function() { extension.install(
'standalone
') },
1915 clearQR: function() {
1916 diff --git a/options.html b/options.html
1917 index dc0f28e.
.8d709f6
100644
1921 &lt;div class=
'nav
'>
1922 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
1923 &lt;p
>{{ installTagline }}
&lt;/p
>
1924 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
1925 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
1926 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
1929 &lt;span class=
'dot step1 selected
'>&lt;/span
>
1930 &lt;span class=
'dot step2
'>&lt;/span
>
1931 &lt;span class=
'dot step3
'>&lt;/span
>
1932 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
1933 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
1939 +userdata=
"`pwd`/userdata
"
1940 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
1941 + (cd $userdata
&& git init)
1943 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
1945 + --proxy-server=
"socks://localhost:
9050" \
1946 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
1948 chmod a+rx run-signal-app
1951 <p
>As usual, if you use Bitcoin and want to show your support of my
1952 activities, please send Bitcoin donations to my address
1953 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1958 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
1959 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
1960 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
1961 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
1962 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1963 system
</a
> provide a practical and easy way to figure out which
1964 packages support the hardware in a given machine. The command line
1965 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
1966 convenient way to list and install packages relevant for the current
1967 hardware during system installation, both user space packages and
1968 firmware packages. The GUI background daemon on the other hand provide
1969 a pop-up proposing to install packages when a new dongle is inserted
1970 while using the computer. For example, if you plug in a smart card
1971 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
1972 that package isn
't already installed, and if you plug in a USB video
1973 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
1974 cheese is currently missing. This already work just fine.
</p
>
1976 <p
>But Isenkram depend on a database mapping from hardware IDs to
1977 package names. When I started no such database existed in Debian, so
1978 I made my own data set and included it with the isenkram package and
1979 made isenkram fetch the latest version of this database from git using
1980 http. This way the isenkram users would get updated package proposals
1981 as soon as I learned more about hardware related packages.
</p
>
1983 <p
>The hardware is identified using modalias strings. The modalias
1984 design is from the Linux kernel where most hardware descriptors are
1985 made available as a strings that can be matched using filename style
1986 globbing. It handle USB, PCI, DMI and a lot of other hardware related
1987 identifiers.
</p
>
1989 <p
>The downside to the Isenkram specific database is that there is no
1990 information about relevant distribution / Debian version, making
1991 isenkram propose obsolete packages too. But along came AppStream, a
1992 cross distribution mechanism to store and collect metadata about
1993 software packages. When I heard about the proposal, I contacted the
1994 people involved and suggested to add a hardware matching rule using
1995 modalias strings in the specification, to be able to use AppStream for
1996 mapping hardware to packages. This idea was accepted and AppStream is
1997 now a great way for a package to announce the hardware it support in a
1998 distribution neutral way. I wrote
1999 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
2000 recipe on how to add such meta-information
</a
> in a blog post last
2001 December. If you have a hardware related package in Debian, please
2002 announce the relevant hardware IDs using AppStream.
</p
>
2004 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
2005 RCX or NXT unit, announce this support using AppStream. The effect is
2006 that when you insert such LEGO robot controller into your Debian
2007 machine, Isenkram will propose to install the packages needed to get
2008 it working. The intention is that this should allow the local user to
2009 start programming his robot controller right away without having to
2010 guess what packages to use or which permissions to fix.
</p
>
2012 <p
>But when I sat down with my son the other day to program our NXT
2013 unit using his Debian Stretch computer, I discovered something
2014 annoying. The local console user (ie my son) did not get access to
2015 the USB device for programming the unit. This used to work, but no
2016 longer in Jessie and Stretch. After some investigation and asking
2017 around on #debian-devel, I discovered that this was because udev had
2018 changed the mechanism used to grant access to local devices. The
2019 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
2020 no longer applied, because LDAP users no longer was added to the
2021 plugdev group during login. Michael Biebl told me that this method
2022 was obsolete and the new method used ACLs instead. This was good
2023 news, as the plugdev mechanism is a mess when using a remote user
2024 directory like LDAP. Using ACLs would make sure a user lost device
2025 access when she logged out, even if the user left behind a background
2026 process which would retain the plugdev membership with the ConsoleKit
2027 setup. Armed with this knowledge I moved on to fix the access problem
2028 for the LEGO Mindstorms related packages.
</p
>
2030 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
2031 applied directly for a device, or is applied in
2032 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
2033 LEGO Mindstorms udev rules did not have a class, I decided to add the
2034 tag directly in the udev rules files included in the packages. Here
2035 is one example. For the nqc C compiler for the RCX, the
2036 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
2038 <p
><pre
>
2039 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
2040 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
2041 </pre
></p
>
2043 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
2044 packages using plugdev in their /lib/udev/rules.d/ files should be
2045 changed to use this tag (either directly or indirectly via
2046 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
2047 to detect this?
</p
>
2049 <p
>I
've been unable to find good documentation on the uaccess feature.
2050 It is unclear to me if the uaccess tag is an internal implementation
2051 detail like the udev-acl tag used by
2052 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
2053 indirect method is the preferred way. Michael
2054 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
2055 documentation from the systemd project
</a
> and I hope it will make
2056 this clearer. For now I use the generic classes when they exist and
2057 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
2058 directly if no such class exist.
</p
>
2060 <p
>To learn more about the isenkram system, please check out
2061 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2062 blog posts tagged isenkram
</a
>.
</p
>
2064 <p
>To help out making life for LEGO constructors in Debian easier,
2065 please join us on our IRC channel
2066 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
2067 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
2068 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
2069 list is not yet created, but we are working on it. :)
</p
>
2071 <p
>As usual, if you use Bitcoin and want to show your support of my
2072 activities, please send Bitcoin donations to my address
2073 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2078 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
2079 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
2080 <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>
2081 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
2082 <description><p
>In April we
2083 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
2084 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
2085 how to set up and administrate a Debian system. Today I am happy to
2086 report that the first draft is now publicly available. You can find
2087 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
2088 Administrator
's Handbook page
</a
> (under Other languages). The first
2089 eight chapters have a first draft translation, and we are working on
2090 proofreading the content. If you want to help out, please start
2092 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2093 hosted weblate project page
</a
>, and get in touch using
2094 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2095 translators mailing list
</a
>. Please also check out
2096 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2097 contributors
</a
>. A good way to contribute is to proofread the text
2098 and update weblate if you find errors.
</p
>
2100 <p
>Our goal is still to make the Norwegian book available on paper as well as
2101 electronic form.
</p
>
2106 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
2107 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
2108 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
2109 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
2110 <description><p
>This summer, I read a great article
2111 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
2112 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
2113 how to profile multi-threaded programs. It presented a system for
2114 profiling software by running experiences in the running program,
2115 testing how run time performance is affected by
"speeding up
" parts of
2116 the code to various degrees compared to a normal run. It does this by
2117 slowing down parallel threads while the
"faster up
" code is running
2118 and measure how this affect processing time. The processing time is
2119 measured using probes inserted into the code, either using progress
2120 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2121 can also measure unmodified code by measuring complete the program
2122 runtime and running the program several times instead.
</p
>
2124 <p
>The project and presentation was so inspiring that I would like to
2125 get the system into Debian. I
2126 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
2127 a WNPP request for it
</a
> and contacted upstream to try to make the
2128 system ready for Debian by sending patches. The build process need to
2129 be changed a bit to avoid running
'git clone
' to get dependencies, and
2130 to include the JavaScript web page used to visualize the collected
2131 profiling information included in the source package.
2132 But I expect that should work out fairly soon.
</p
>
2134 <p
>The way the system work is fairly simple. To run an coz experiment
2135 on a binary with debug symbols available, start the program like this:
2137 <p
><blockquote
><pre
>
2138 coz run --- program-to-run
2139 </pre
></blockquote
></p
>
2141 <p
>This will create a text file profile.coz with the instrumentation
2142 information. To show what part of the code affect the performance
2143 most, use a web browser and either point it to
2144 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
2145 or use the copy from git (in the gh-pages branch). Check out this web
2146 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
2147 profiling more useful you include
&lt;coz.h
&gt; and insert the
2148 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2149 code, rebuild and run the profiler. This allow coz to do more
2150 targeted experiments.
</p
>
2152 <p
>A video published by ACM
2153 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
2154 Coz profiler
</a
> is available from Youtube. There is also a paper
2155 from the
25th Symposium on Operating Systems Principles available
2157 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
2158 finding code that counts with causal profiling
</a
>.
</p
>
2160 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
2161 for Coz is available from github. It will only build with clang
2163 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
2164 feature missing in GCC
</a
>, but I
've submitted
2165 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
2166 it
</a
> and hope it will be included in the upstream source soon.
</p
>
2168 <p
>Please get in touch if you, like me, would like to see this piece
2169 of software in Debian. I would very much like some help with the
2170 packaging effort, as I lack the in depth knowledge on how to package
2171 C++ libraries.
</p
>
2176 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
2177 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
2178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
2179 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
2180 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2181 to be a slight challenge. Here is the recipe if I ever need to do it
2182 again. It all started by me wanting to try the recipe to set up
2183 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
2184 hardened Android installation
</a
> from the Tor project blog on a
2185 device I had access to. It is a old mobile phone with a broken
2186 microphone The initial idea had been to just
2187 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
2188 CyanogenMod on it
</a
>, but did not quite find time to start on it
2189 until a few days ago.
</p
>
2191 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
2192 loader (press volume down and power at the same time), (
2) select
2193 'fastboot
' before (
3) connecting the device via USB to a Linux
2194 machine, (
4) request the device identifier token by running
'fastboot
2195 oem get_identifier_token
', (
5) request the device unlocking key using
2196 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
2197 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
2199 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
2200 or newer, and the device I was working on had
2.00.0027. This
2201 apparently can be easily fixed by downloading a Windows program and
2202 running it on your Windows machine, if you accept the terms Microsoft
2203 require you to accept to use Windows - which I do not. So I had to
2204 come up with a different approach. I got a lot of help from AndyCap
2205 on #nuug, and would not have been able to get this working without
2208 <p
>First I needed to extract the hboot firmware from
2209 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
2210 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
2211 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
2212 project named unruu
</a
> using libunshield. The unshield tool did not
2213 recognise the file format, but unruu worked and extracted rom.zip,
2214 containing the new hboot firmware and a text file describing which
2215 devices it would work for.
</p
>
2217 <p
>Next, I needed to get the new firmware into the device. For this I
2218 followed some instructions
2219 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
2220 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
2221 machine with Debian testing:
</p
>
2223 <p
><pre
>
2224 adb reboot-bootloader
2225 fastboot oem rebootRUU
2226 fastboot flash zip rom.zip
2227 fastboot flash zip rom.zip
2229 </pre
></p
>
2231 <p
>The flash command apparently need to be done twice to take effect,
2232 as the first is just preparations and the second one do the flashing.
2233 The adb command is just to get to the boot loader menu, so turning the
2234 device on while holding volume down and the power button should work
2237 <p
>With the new hboot version in place I could start following the
2238 instructions on the HTC developer web site. I got the device token
2239 like this:
</p
>
2241 <p
><pre
>
2242 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
2245 <p
>And once I got the unlock code via email, I could use it like
2248 <p
><pre
>
2249 fastboot flash unlocktoken Unlock_code.bin
2250 </pre
></p
>
2252 <p
>And with that final step in place, the phone was unlocked and I
2253 could start stuffing the software of my own choosing into the device.
2254 So far I only inserted a replacement recovery image to wipe the phone
2255 before I start. We will see what happen next. Perhaps I should
2256 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
2261 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
2262 <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>
2263 <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>
2264 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
2265 <description><p
>For a while now, I have wanted to test
2266 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
2267 said to provide end to end encrypted communication and several of my
2268 friends and family are already using it. As I by choice do not own a
2269 mobile phone, this proved to be harder than expected. And I wanted to
2270 have the source of the client and know that it was the code used on my
2271 machine. But yesterday I managed to get it working. I used the
2272 Github source, compared it to the source in
2273 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
2274 Signal Chrome app
</a
> available from the Chrome web store, applied
2275 patches to use the production Signal servers, started the app and
2276 asked for the hidden
"register without a smart phone
" form. Here is
2277 the recipe how I did it.
</p
>
2279 <p
>First, I fetched the Signal desktop source from Github, using
2282 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2285 <p
>Next, I patched the source to use the production servers, to be
2286 able to talk to other Signal users:
</p
>
2289 cat
&lt;
&lt;EOF | patch -p0
2290 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2291 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2292 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
2297 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
2298 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
2299 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
2300 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
2301 var messageReceiver;
2302 window.getSocketStatus = function() {
2303 if (messageReceiver) {
2304 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
2305 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2306 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
2309 'use strict
';
2310 - var BUILD_EXPIRATION =
0;
2311 + var BUILD_EXPIRATION =
1474492690000;
2313 window.extension = window.extension || {};
2318 <p
>The first part is changing the servers, and the second is updating
2319 an expiration timestamp. This timestamp need to be updated regularly.
2320 It is set
90 days in the future by the build process (Gruntfile.js).
2321 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
2323 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
2324 script to launch Signal in Chromium.
</p
>
2331 --proxy-server=
"socks://localhost:
9050" \
2332 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2335 <p
> The script start the app and configure Chromium to use the Tor
2336 SOCKS5 proxy to make sure those controlling the Signal servers (today
2337 Amazon and Whisper Systems) as well as those listening on the lines
2338 will have a harder time location my laptop based on the Signal
2339 connections if they use source IP address.
</p
>
2341 <p
>When the script starts, one need to follow the instructions under
2342 "Standalone Registration
" in the CONTRIBUTING.md file in the git
2343 repository. I right clicked on the Signal window to get up the
2344 Chromium debugging tool, visited the
'Console
' tab and wrote
2345 'extension.install(
"standalone
")
' on the console prompt to get the
2346 registration form. Then I entered by land line phone number and
2347 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
2348 repeated the verification code three times. After entering the number
2349 into the verification code field in the form, I could start using
2350 Signal from my laptop.
2352 <p
>As far as I can tell, The Signal app will leak who is talking to
2353 whom and thus who know who to those controlling the central server,
2354 but such leakage is hard to avoid with a centrally controlled server
2355 setup. It is something to keep in mind when using Signal - the
2356 content of your chats are harder to intercept, but the meta data
2357 exposing your contact network is available to people you do not know.
2358 So better than many options, but not great. And sadly the usage is
2359 connected to my land line, thus allowing those controlling the server
2360 to associate it to my home and person. I would prefer it if only
2361 those I knew could tell who I was on Signal. There are options
2362 avoiding such information leakage, but most of my friends are not
2363 using them, so I am stuck with Signal for now.
</p
>
2365 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
2367 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
2368 and updated recipe for using the Signal app without a mobile
2369 phone
</a
>.
</p
>
2374 <title>The new
"best
" multimedia player in Debian?
</title>
2375 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
2376 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
2377 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
2378 <description><p
>When I set out a few weeks ago to figure out
2379 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
2380 multimedia player in Debian claimed to support most file formats /
2381 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
2382 the various players claimed support for. The range was from
55 to
130
2383 MIME types. I suspect most media formats are supported by all
2384 players, but this is not really reflected in the MimeTypes values in
2385 their desktop files. There are probably also some bogus MIME types
2386 listed, but it is hard to identify which one this is.
</p
>
2388 <p
>Anyway, in the mean time I got in touch with upstream for some of
2389 the players suggesting to add more MIME types to their desktop files,
2390 and decided to spend some time myself improving the situation for my
2391 favorite media player VLC. The fixes for VLC entered Debian unstable
2392 yesterday. The complete list of MIME types can be seen on the
2393 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
2394 player MIME type support status
</a
> Debian wiki page.
</p
>
2396 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
2397 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2398 kmplayer. I am sure some of the other players desktop files support
2399 several of the formats currently listed as working only with vlc,
2400 toten and parole.
</p
>
2402 <p
>A sad observation is that only
14 MIME types are listed as
2403 supported by all the tested multimedia players in Debian in their
2404 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2405 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2406 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2407 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2408 it sad that video/ogg and video/webm is not supported by all the media
2409 players in Debian. As far as I can tell, all of them can handle both
2415 <title>A program should be able to open its own files on Linux
</title>
2416 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
2417 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
2418 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
2419 <description><p
>Many years ago, when koffice was fresh and with few users, I
2420 decided to test its presentation tool when making the slides for a
2421 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2422 wrote the first draft of the slides, saved the result and went to bed
2423 the day before I would give the talk. The next day I took a plane to
2424 the location where the meeting should take place, and on the plane I
2425 started up koffice again to polish the talk a bit, only to discover
2426 that kpresenter refused to load its own data file. I cursed a bit and
2427 started making the slides again from memory, to have something to
2428 present when I arrived. I tested that the saved files could be
2429 loaded, and the day seemed to be rescued. I continued to polish the
2430 slides until I suddenly discovered that the saved file could no longer
2431 be loaded into kpresenter. In the end I had to rewrite the slides
2432 three times, condensing the content until the talk became shorter and
2433 shorter. After the talk I was able to pinpoint the problem
&ndash;
2434 kpresenter wrote inline images in a way itself could not understand.
2435 Eventually that bug was fixed and kpresenter ended up being a great
2436 program to make slides. The point I
'm trying to make is that we
2437 expect a program to be able to load its own data files, and it is
2438 embarrassing to its developers if it can
't.
</p
>
2440 <p
>Did you ever experience a program failing to load its own data
2441 files from the desktop file browser? It is not a uncommon problem. A
2442 while back I discovered that the screencast recorder
2443 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2444 browser would refuse to open. No video player claimed to understand
2445 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
2446 returning the application/ogg MIME type, which no video player I had
2447 installed listed as a MIME type they would understand. I asked for
2448 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
2449 behavour
</a
> and use the MIME type video/ogg instead. I also asked
2450 several video players to add video/ogg to their desktop files, to give
2451 the file browser an idea what to do about Ogg Theora files. After a
2452 while, the desktop file browsers in Debian started to handle the
2453 output from gtk-recordmydesktop properly.
</p
>
2455 <p
>But history repeats itself. A few days ago I tested the music
2456 system Rosegarden again, and I discovered that the KDE and xfce file
2457 browsers did not know what to do with the Rosegarden project files
2458 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
2459 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
2460 included in the next upload. To increase the chance of me remembering
2461 how to fix the problem next time some program fail to load its files
2462 from the file browser, here are some notes on how to fix it.
</p
>
2464 <p
>The file browsers in Debian in general operates on MIME types.
2465 There are two sources for the MIME type of a given file. The output from
2466 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
2467 shared MIME type registry (under /usr/share/mime/). The file MIME
2468 type is mapped to programs supporting the MIME type, and this
2469 information is collected from
2470 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
2471 desktop files
</a
> available in /usr/share/applications/. If there is
2472 one desktop file claiming support for the MIME type of the file, it is
2473 activated when asking to open a given file. If there are more, one
2474 can normally select which one to use by right-clicking on the file and
2475 selecting the wanted one using
'Open with
' or similar. In general
2476 this work well. But it depend on each program picking a good MIME
2478 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
2479 MIME type registered with IANA
</a
>), file and/or the shared MIME
2480 registry recognizing the file and the desktop file to list the MIME
2481 type in its list of supported MIME types.
</p
>
2483 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
2484 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
2485 Shared MIME database
</a
> look like this:
</p
>
2487 <p
><blockquote
><pre
>
2488 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2489 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
2490 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
2491 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
2492 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
2493 &lt;glob pattern=
"*.rg
"/
&gt;
2494 &lt;/mime-type
&gt;
2495 &lt;/mime-info
&gt;
2496 </pre
></blockquote
></p
>
2498 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
2499 (it is a gzipped XML file). Note, it is much better to use an
2500 official MIME type registered with IANA than it is to make up ones own
2501 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
2503 <p
>The desktop file of the rosegarden program failed to list
2504 audio/x-rosegarden in its list of supported MIME types, causing the
2505 file browsers to have no idea what to do with *.rg files:
</p
>
2507 <p
><blockquote
><pre
>
2508 % grep Mime /usr/share/applications/rosegarden.desktop
2509 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2510 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2512 </pre
></blockquote
></p
>
2514 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
2515 MimeType= line.
</p
>
2517 <p
>If you run into a file which fail to open the correct program when
2518 selected from the file browser, please check out the output from
2519 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
2520 MIME type is registered somewhere under /usr/share/mime/ and check
2521 that some desktop file under /usr/share/applications/ is claiming
2522 support for this MIME type. If not, please report a bug to have it
2528 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
2529 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
2530 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
2531 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
2532 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
2533 system
</a
> is a user-focused solution in Debian for handling hardware
2534 related packages. The idea is to have a database of mappings between
2535 hardware and packages, and pop up a dialog suggesting for the user to
2536 install the packages to use a given hardware dongle. Some use cases
2537 are when you insert a Yubikey, it proposes to install the software
2538 needed to control it; when you insert a braille reader list it
2539 proposes to install the packages needed to send text to the reader;
2540 and when you insert a ColorHug screen calibrator it suggests to
2541 install the driver for it. The system work well, and even have a few
2542 command line tools to install firmware packages and packages for the
2543 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
2545 <p
>The system was initially written using aptdaemon, because I found
2546 good documentation and example code on how to use it. But aptdaemon
2547 is going away and is generally being replaced by
2548 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
2549 so Isenkram needed a rewrite. And today, thanks to the great patch
2550 from my college Sunil Mohan Adapa in the FreedomBox project, the
2551 rewrite finally took place. I
've just uploaded a new version of
2552 Isenkram into Debian Unstable with the patch included, and the default
2553 for the background daemon is now to use PackageKit. To check it out,
2554 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
2555 and see if it is recognised.
</p
>
2557 <p
>If you want to know what kind of packages isenkram would propose for
2558 the machine it is running on, you can check out the isenkram-lookup
2559 program. This is what it look like on a Thinkpad X230:
</p
>
2561 <p
><blockquote
><pre
>
2577 </pre
></blockquote
></p
>
2579 <p
>The hardware mappings come from several places. The preferred way
2580 is for packages to announce their hardware support using
2581 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2582 cross distribution appstream system
</a
>.
2584 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2585 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2590 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2591 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2592 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2593 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2594 <description><p
>Yesterday I updated the
2595 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2596 package in Debian
</a
> with a few patches sent to me by skilled and
2597 enterprising users. There were some nice user and visible changes.
2598 First of all, both desktop menu entries now work. A design flaw in
2599 one of the script made the history graph fail to show up (its PNG was
2600 dumped in ~/.xsession-errors) if no controlling TTY was available.
2601 The script worked when called from the command line, but not when
2602 called from the desktop menu. I changed this to look for a DISPLAY
2603 variable or a TTY before deciding where to draw the graph, and now the
2604 graph window pop up as expected.
</p
>
2606 <p
>The next new feature is a discharge rate estimator in one of the
2607 graphs (the one showing the last few hours). New is also the user of
2608 colours showing charging in blue and discharge in red. The percentages
2609 of this graph is relative to last full charge, not battery design
2612 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2614 <p
>The other graph show the entire history of the collected battery
2615 statistics, comparing it to the design capacity of the battery to
2616 visualise how the battery life time get shorter over time. The red
2617 line in this graph is what the previous graph considers
100 percent:
2619 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2621 <p
>In this graph you can see that I only charge the battery to
80
2622 percent of last full capacity, and how the capacity of the battery is
2623 shrinking. :(
</p
>
2625 <p
>The last new feature is in the collector, which now will handle
2626 more hardware models. On some hardware, Linux power supply
2627 information is stored in /sys/class/power_supply/ACAD/, while the
2628 collector previously only looked in /sys/class/power_supply/AC/. Now
2629 both are checked to figure if there is power connected to the
2632 <p
>If you are interested in how your laptop battery is doing, please
2634 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2635 in Debian unstable, or rebuild it on Jessie to get it working on
2636 Debian stable. :) The upstream source is available from
<a
2637 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2638 Patches are very welcome.
</p
>
2640 <p
>As usual, if you use Bitcoin and want to show your support of my
2641 activities, please send Bitcoin donations to my address
2642 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2647 <title>Debian now with ZFS on Linux included
</title>
2648 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2649 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2650 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2651 <description><p
>Today, after many years of hard work from many people,
2652 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2653 Debian. The package status can be seen on
2654 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2655 for zfs-linux
</a
>. and
2656 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2657 team status page
</a
>. If you want to help out, please join us.
2658 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2659 source code
</a
> is available via git on Alioth. It would also be
2660 great if you could help out with
2661 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2662 it is an important piece of the puzzle to get ZFS working.
</p
>
2667 <title>What is the best multimedia player in Debian?
</title>
2668 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2669 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2670 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2671 <description><p
><strong
>Where I set out to figure out which multimedia player in
2672 Debian claim support for most file formats.
</strong
></p
>
2674 <p
>A few years ago, I had a look at the media support for Browser
2675 plugins in Debian, to get an idea which plugins to include in Debian
2676 Edu. I created a script to extract the set of supported MIME types
2677 for each plugin, and used this to find out which multimedia browser
2678 plugin supported most file formats / media types.
2679 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2680 result
</a
> can still be seen on the Debian wiki, even though it have
2681 not been updated for a while. But browser plugins are less relevant
2682 these days, so I thought it was time to look at standalone
2685 <p
>A few days ago I was tired of VLC not being listed as a viable
2686 player when I wanted to play videos from the Norwegian National
2687 Broadcasting Company, and decided to investigate why. The cause is a
2688 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2689 desktop file
</a
>. In the process I wrote a script to compare the set
2690 of MIME types announced in the desktop file and the browser plugin,
2691 only to discover that there is quite a large difference between the
2692 two for VLC. This discovery made me dig up the script I used to
2693 compare browser plugins, and adjust it to compare desktop files
2694 instead, to try to figure out which multimedia player in Debian
2695 support most file formats.
</p
>
2697 <p
>The result can be seen on the Debian Wiki, as
2698 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2699 table listing all MIME types supported by one of the packages included
2700 in the table
</a
>, with the package supporting most MIME types being
2701 listed first in the table.
</p
>
2703 </p
>The best multimedia player in Debian? It is totem, followed by
2704 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2705 kmplayer. Time for the other players to update their announced MIME
2711 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2712 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2713 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2714 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2715 <description>A friend of mine made me aware of
2716 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2717 handheld computer which will be delivered with Debian preinstalled. I
2718 would love to get one of those for my birthday. :)
</p
>
2720 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2721 plugs and many others connectors, and include a full keyboard and a
5"
2722 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2723 day of battery life time, but I have not seen any independent tests
2724 confirming this. The vendor is still collecting preorders, and the
2725 last I heard last night was that
22 more orders were needed before
2726 production started.
</p
>
2728 <p
>As far as I know, this is the first handheld preinstalled with
2729 Debian. Please let me know if you know of any others. Is it the
2730 first computer being sold with Debian preinstalled?
</p
>
2735 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2736 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2737 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2738 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2739 <description><p
>During this weekends
2740 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2741 squashing party and developer gathering
</a
>, we decided to do our part
2742 to make sure there are good books about Debian available in Norwegian
2743 Bokmål, and got in touch with the people behind the
2744 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2745 project
</a
> to get started. If you want to help out, please start
2747 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2748 hosted weblate project page
</a
>, and get in touch using
2749 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2750 translators mailing list
</a
>. Please also check out
2751 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2752 contributors
</a
>.
</p
>
2754 <p
>The book is already available on paper in English, French and
2755 Japanese, and our goal is to get it available on paper in Norwegian
2756 Bokmål too. In addition to the paper edition, there are also EPUB and
2757 Mobi versions available. And there are incomplete translations
2758 available for many more languages.
</p
>
2763 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2764 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2765 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2766 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2767 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2768 packages in Debian, and was quite surprised with what I found. I use
2769 ZFS myself at home, but did not really expect many others to do so.
2770 But I might be wrong.
</p
>
2772 <p
>According to
2773 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2774 results for spl-linux
</a
>, there are
1019 Debian installations, or
2775 0.53% of the population, with the package installed. As far as I know
2776 the only use of the spl-linux package is as a support library for ZFS
2777 on Linux, so I use it here as proxy for measuring the number of ZFS
2778 installation on Linux in Debian. In the kFreeBSD variant of Debian
2779 the ZFS feature is already available, and there
2780 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2781 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2782 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2784 <p
>But even though the Debian project leader Lucas Nussbaum
2785 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2786 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2787 cleared, the package is still not in Debian. The package is again in
2788 the NEW queue. Several uploads have been rejected so far because the
2789 debian/copyright file was incomplete or wrong, but there is no reason
2790 to give up. The current status can be seen on
2791 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2792 team status page
</a
>, and
2793 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2794 source code
</a
> is available on Alioth.
</p
>
2796 <p
>As I want ZFS to be included in next version of Debian to make sure
2797 my home server can function in the future using only official Debian
2798 packages, and the current blocker is to get the debian/copyright file
2799 accepted by the FTP masters in Debian, I decided a while back to try
2800 to help out the team. This was the background for my blog post about
2801 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2802 updating and checking debian/copyright semi-automatically
</a
>, and I
2803 used the techniques I explored there to try to find any errors in the
2804 copyright file. It is not very easy to check every one of the around
2805 2000 files in the source package, but I hope we this time got it
2806 right. If you want to help out, check out the git source and try to
2807 find missing entries in the debian/copyright file.
</p
>
2812 <title>Full battery stats collector is now available in Debian
</title>
2813 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2814 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2815 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
2816 <description><p
>Since this morning, the battery-stats package in Debian include an
2817 extended collector that will collect the complete battery history for
2818 later processing and graphing. The original collector store the
2819 battery level as percentage of last full level, while the new
2820 collector also record battery vendor, model, serial number, design
2821 full level, last full level and current battery level. This make it
2822 possible to predict the lifetime of the battery as well as visualise
2823 the energy flow when the battery is charging or discharging.
</p
>
2825 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
2826 in the version
0.5.1 package in unstable. Get the new battery level graph
2827 and lifetime prediction by running:
2829 <p
><pre
>
2830 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
2831 </pre
></p
>
2833 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
2835 <p
>The flow in/out of the battery can be seen by running (no menu
2836 entry yet):
</p
>
2838 <p
><pre
>
2839 /usr/share/battery-stats/battery-stats-graph-flow
2840 </pre
></p
>
2842 <p
>I
'm not quite happy with the way the data is visualised, at least
2843 when there are few data points. The graphs look a bit better with a
2844 few years of data.
</p
>
2846 <p
>A while back one important feature I use in the battery stats
2847 collector broke in Debian. The scripts in
2848 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
2849 suspect it happened when Jessie started using systemd, but I do not
2850 know. The issue is reported as
2851 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
2852 pm-utils. I managed to work around it by adding an udev rule to call
2853 the collector script every time the power connector is connected and
2854 disconnected. With this fix in place it was finally time to make a
2855 new release of the package, and get it into Debian.
</p
>
2857 <p
>If you are interested in how your laptop battery is doing, please
2859 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2860 in Debian unstable, or rebuild it on Jessie to get it working on
2861 Debian stable. :) The upstream source is available from
2862 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2863 As always, patches are very welcome.
</p
>
2868 <title>Making battery measurements a little easier in Debian
</title>
2869 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
2870 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
2871 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
2872 <description><p
>Back in September, I blogged about
2873 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
2874 system I wrote to collect statistics about my laptop battery
</a
>, and
2875 how it showed the decay and death of this battery (now replaced). I
2876 created a simple deb package to handle the collection and graphing,
2877 but did not want to upload it to Debian as there were already
2878 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
2879 package in Debian
</a
> that should do the same thing, and I did not see
2880 a point of uploading a competing package when battery-stats could be
2881 fixed instead. I reported a few bugs about its non-function, and
2882 hoped someone would step in and fix it. But no-one did.
</p
>
2884 <p
>I got tired of waiting a few days ago, and took matters in my own
2885 hands. The end result is that I am now the new upstream developer of
2886 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
2887 battery-stats in Debian, and the package in Debian unstable is finally
2888 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
2889 information provided by the Linux kernel. If you install the
2890 battery-stats package from unstable now, you will be able to get a
2891 graph of the current battery fill level, to get some idea about the
2892 status of the battery. The source package build and work just fine in
2893 Debian testing and stable (and probably oldstable too, but I have not
2894 tested). The default graph you get for that system look like this:
</p
>
2896 <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
>
2898 <p
>My plans for the future is to merge my old scripts into the
2899 battery-stats package, as my old scripts collected a lot more details
2900 about the battery. The scripts are merged into the upstream
2901 battery-stats git repository already, but I am not convinced they work
2902 yet, as I changed a lot of paths along the way. Will have to test a
2903 bit more before I make a new release.
</p
>
2905 <p
>I will also consider changing the file format slightly, as I
2906 suspect the way I combine several values into one field might make it
2907 impossible to know the type of the value when using it for processing
2908 and graphing.
</p
>
2910 <p
>If you would like I would like to keep an close eye on your laptop
2911 battery, check out the battery-stats package in
2912 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
2914 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2915 I would love some help to improve the system further.
</p
>
2920 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
2921 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
2922 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
2923 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
2924 <description><p
>Making packages for Debian requires quite a lot of attention to
2925 details. And one of the details is the content of the
2926 debian/copyright file, which should list all relevant licenses used by
2927 the code in the package in question, preferably in
2928 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
2929 readable DEP5 format
</a
>.
</p
>
2931 <p
>For large packages with lots of contributors it is hard to write
2932 and update this file manually, and if you get some detail wrong, the
2933 package is normally rejected by the ftpmasters. So getting it right
2934 the first time around get the package into Debian faster, and save
2935 both you and the ftpmasters some work.. Today, while trying to figure
2936 out what was wrong with
2937 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
2938 zfsonlinux copyright file
</a
>, I decided to spend some time on
2939 figuring out the options for doing this job automatically, or at least
2940 semi-automatically.
</p
>
2942 <p
>Lucikly, there are at least two tools available for generating the
2943 file based on the code in the source package,
2944 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
2945 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
2946 not sure which one of them came first, but both seem to be able to
2947 create a sensible draft file. As far as I can tell, none of them can
2948 be trusted to get the result just right, so the content need to be
2949 polished a bit before the file is OK to upload. I found the debmake
2951 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
2952 blog posts from
2014</a
>.
2954 <p
>To generate using debmake, use the -cc option:
2956 <p
><pre
>
2957 debmake -cc
> debian/copyright
2958 </pre
></p
>
2960 <p
>Note there are some problems with python and non-ASCII names, so
2961 this might not be the best option.
</p
>
2963 <p
>The cme option is based on a config parsing library, and I found
2965 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
2966 blog post from
2015</a
>. To generate using cme, use the
'update
2967 dpkg-copyright
' option:
2969 <p
><pre
>
2970 cme update dpkg-copyright
2971 </pre
></p
>
2973 <p
>This will create or update debian/copyright. The cme tool seem to
2974 handle UTF-
8 names better than debmake.
</p
>
2976 <p
>When the copyright file is created, I would also like some help to
2977 check if the file is correct. For this I found two good options,
2978 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
2979 to focus on license types and file matching, and is able to detect
2980 ineffective blocks in the copyright file. The latter reports missing
2981 copyright holders and years, but was confused by inconsistent license
2982 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
2983 fix all issues reported by them before uploading. But I do not know
2984 if the tools and the ftpmasters agree on what is important to fix in a
2985 copyright file, so the package might still be rejected.
</p
>
2987 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
2988 will read through the source and try to find all copyright statements.
2989 It is not comparing the result to the content of debian/copyright, but
2990 can be useful when verifying the content of the copyright file.
</p
>
2992 <p
>Are you aware of better tools in Debian to create and update
2993 debian/copyright file. Please let me know, or blog about it on
2994 planet.debian.org.
</p
>
2996 <p
>As usual, if you use Bitcoin and want to show your support of my
2997 activities, please send Bitcoin donations to my address
2998 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3000 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
3001 on how to use licensecheck and cdbs to create a draft copyright file
3003 <p
><pre
>
3004 licensecheck --copyright -r `find * -type f` | \
3005 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
3006 </pre
></p
>
3008 <p
>He mentioned that he normally check the generated file into the
3009 version control system to make it easier to discover license and
3010 copyright changes in the upstream source. I will try to do the same
3011 with my packages in the future.
</p
>
3013 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
3014 against using -quiet for new users, so I removed it from the proposed
3015 command line.
</p
>
3020 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
3021 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
3022 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
3023 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
3024 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
3025 is taking shape in Debian, and one provided feature is a very
3026 convenient way to tell you which package to install to make a given
3027 firmware file available when the kernel is looking for it. This can
3028 be done using apt-file too, but that is for someone else to blog
3031 <p
>Here is a small recipe to find the package with a given firmware
3032 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
3033 picked from the set of firmware announced using appstream in Debian
3034 unstable. In general you would be looking for the firmware requested
3035 by the kernel during kernel module loading. To find the package
3036 providing the example file, do like this:
</p
>
3038 <blockquote
><pre
>
3039 % apt install appstream
3043 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
3044 awk
'/Package:/ {print $
2}
'
3047 </pre
></blockquote
>
3049 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
3050 appstream wiki
</a
> page to learn how to embed the package metadata in
3051 a way appstream can use.
</p
>
3053 <p
>This same approach can be used to find any package supporting a
3054 given MIME type. This is very useful when you get a file you do not
3055 know how to handle. First find the mime type using
<tt
>file
3056 --mime-type
</tt
>, and next look up the package providing support for
3057 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3058 and you can find all packages handling this type like this:
</p
>
3060 <blockquote
><pre
>
3061 % apt install appstream
3065 % appstreamcli what-provides mimetype image/svg+xml | \
3066 awk
'/Package:/ {print $
2}
'
3088 </pre
></blockquote
>
3090 <p
>I believe the MIME types are fetched from the desktop file for
3091 packages providing appstream metadata.
</p
>
3096 <title>Creepy, visualise geotagged social media information - nice free software
</title>
3097 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
3098 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
3099 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
3100 <description><p
>Most people seem not to realise that every time they walk around
3101 with the computerised radio beacon known as a mobile phone their
3102 position is tracked by the phone company and often stored for a long
3103 time (like every time a SMS is received or sent). And if their
3104 computerised radio beacon is capable of running programs (often called
3105 mobile apps) downloaded from the Internet, these programs are often
3106 also capable of tracking their location (if the app requested access
3107 during installation). And when these programs send out information to
3108 central collection points, the location is often included, unless
3109 extra care is taken to not send the location. The provided
3110 information is used by several entities, for good and bad (what is
3111 good and bad, depend on your point of view). What is certain, is that
3112 the private sphere and the right to free movement is challenged and
3113 perhaps even eradicated for those announcing their location this way,
3114 when they share their whereabouts with private and public
3117 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
3119 <p
>The phone company logs provide a register of locations to check out
3120 when one want to figure out what the tracked person was doing. It is
3121 unavailable for most of us, but provided to selected government
3122 officials, company staff, those illegally buying information from
3123 unfaithful servants and crackers stealing the information. But the
3124 public information can be collected and analysed, and a free software
3125 tool to do so is called
3126 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
3127 discovered it when I read
3128 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
3129 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
3130 November
2014, and decided to check if it was available in Debian.
3131 The python program was in Debian, but
3132 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
3133 Debian
</a
> was completely broken and practically unmaintained. I
3134 uploaded a new version which did not work quite right, but did not
3135 have time to fix it then. This Christmas I decided to finally try to
3136 get Creepy operational in Debian. Now a fixed version is available in
3137 Debian unstable and testing, and almost all Debian specific patches
3139 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
3141 <p
>The Creepy program visualises geolocation information fetched from
3142 Twitter, Instagram, Flickr and Google+, and allow one to get a
3143 complete picture of every social media message posted recently in a
3144 given area, or track the movement of a given individual across all
3145 these services. Earlier it was possible to use the search API of at
3146 least some of these services without identifying oneself, but these
3147 days it is impossible. This mean that to use Creepy, you need to
3148 configure it to log in as yourself on these services, and provide
3149 information to them about your search interests. This should be taken
3150 into account when using Creepy, as it will also share information
3151 about yourself with the services.
</p
>
3153 <p
>The picture above show the twitter messages sent from (or at least
3154 geotagged with a position from) the city centre of Oslo, the capital
3155 of Norway. One useful way to use Creepy is to first look at
3156 information tagged with an area of interest, and next look at all the
3157 information provided by one or more individuals who was in the area.
3158 I tested it by checking out which celebrity provide their location in
3159 twitter messages by checkout out who sent twitter messages near a
3160 Norwegian TV station, and next could track their position over time,
3161 making it possible to locate their home and work place, among other
3162 things. A similar technique have been
3163 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
3164 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
3165 tool to discover lying governments, and a useful tool to help people
3166 understand the value of the private information they provide to the
3169 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
3170 it depend on several python modules currently missing in Jessie (at
3171 least python-instagram, python-flickrapi and
3172 python-requests-toolbelt).
</p
>
3174 <p
>(I have uploaded
3175 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
3176 screenshots.debian.net
</a
> and licensed it under the same terms as the
3177 Creepy program in Debian.)
</p
>
3182 <title>Always download Debian packages using Tor - the simple recipe
</title>
3183 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
3184 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
3185 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
3186 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
3187 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
3188 that those listening on the Internet lines would have good reason to
3189 believe a computer have a given security hole
</a
> if it download a
3190 security fix from a Debian mirror. This is a good reason to always
3191 use encrypted connections to the Debian mirror, to make sure those
3192 listening do not know which IP address to attack. In August, Richard
3193 Hartmann observed that encryption was not enough, when it was possible
3194 to interfere download size to security patches or the fact that
3195 download took place shortly after a security fix was released, and
3196 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
3197 to always use Tor to download packages from the Debian mirror
</a
>. He
3198 was not the first to propose this, as the
3199 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
3200 package by Tim Retout already existed to make it easy to convince apt
3201 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
3202 aware of that package when I read the blog post from Richard.
</p
>
3204 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
3205 sysadmins, and he set up a Tor hidden service on one of the central
3206 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3207 it possible to download packages directly between two tor nodes,
3208 making sure the network traffic always were encrypted.
</p
>
3210 <p
>Here is a short recipe for enabling this on your machine, by
3211 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
3212 urls with tor+http and tor+https, and using the hidden service instead
3213 of the official Debian mirror site. I recommend installing
3214 <tt
>etckeeper
</tt
> before you start to have a history of the changes
3215 done in /etc/.
</p
>
3217 <blockquote
><pre
>
3218 apt install apt-transport-tor
3219 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
3220 sed -i
's% http% tor+http%
' /etc/apt/sources.list
3221 </pre
></blockquote
>
3223 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
3224 the sed commands for these too. The sed command is assuming your are
3225 using the ftp.debian.org Debian mirror. Adjust the command (or just
3226 edit the file manually) to match your mirror.
</p
>
3228 <p
>This work in Debian Jessie and later. Note that tools like
3229 <tt
>apt-file
</tt
> only recently started using the apt transport
3230 system, and do not work with these tor+http URLs. For
3231 <tt
>apt-file
</tt
> you need the version currently in experimental,
3232 which need a recent apt version currently only in unstable. So if you
3233 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
3235 <p
>Another advantage from this change is that your machine will start
3236 using Tor regularly and at fairly random intervals (every time you
3237 update the package lists or upgrade or install a new package), thus
3238 masking other Tor traffic done from the same machine. Using Tor will
3239 become normal for the machine in question.
</p
>
3241 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
3242 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
3243 enabled. It would be great if it was the default on any Debian
3249 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
3250 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
3251 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
3252 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
3253 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
3254 call the car license plate numbers in those days. I would write the
3255 numbers down in my little book and compare notes with the other kids
3256 to see how many region codes we had seen and if we had seen some
3257 exotic or special region codes and numbers. It was a fun game to pass
3258 time, as we kids have plenty of it.
</p
>
3260 <p
>A few days I came across
3261 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
3262 project
</a
>, a free software project to automatically discover and
3263 report license plates in images and video streams, and provide the
3264 "car numbers
" in a machine readable format. I
've been looking for
3265 such system for a while now, because I believe it is a bad idea that the
3266 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
3267 number plate recognition
</a
> tool only is available in the hands of
3268 the powerful, and want it to be available also for the powerless to
3269 even the score when it comes to surveillance and sousveillance. I
3270 discovered the developer
3271 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
3272 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
3273 help him get it into shape to get the package uploaded into the Debian
3276 <p
>Today we finally managed to get the package into shape and uploaded
3277 it into Debian, where it currently
3278 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
3279 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
3281 <p
>I guess you are wondering why on earth such tool would be useful
3282 for the common folks, ie those not running a large government
3283 surveillance system? Well, I plan to put it in a computer on my bike
3284 and in my car, tracking the cars nearby and allowing me to be notified
3285 when number plates on my watch list are discovered. Another use case
3286 was suggested by a friend of mine, who wanted to set it up at his home
3287 to open the car port automatically when it discovered the plate on his
3288 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3289 capable of placing his license plate number of a piece of cardboard to
3290 open his car port, men replied that it was always unlocked anyway. I
3291 guess for such use case it make sense. I am sure there are other use
3292 cases too, for those with imagination and a vision.
</p
>
3294 <p
>If you want to build your own version of the Debian package, check
3295 out the upstream git source and symlink ./distros/debian to ./debian/
3296 before running
"debuild
" to build the source. Or wait a bit until the
3297 package show up in unstable.
</p
>
3302 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
3303 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
3304 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
3305 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
3306 <description><p
>Around three years ago, I created
3307 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
3308 system
</a
> to get a more practical solution in Debian for handing
3309 hardware related packages. A GUI system in the isenkram package will
3310 present a pop-up dialog when some hardware dongle supported by
3311 relevant packages in Debian is inserted into the machine. The same
3312 lookup mechanism to detect packages is available as command line
3313 tools in the isenkram-cli package. In addition to mapping hardware,
3314 it will also map kernel firmware files to packages and make it easy to
3315 install needed firmware packages automatically. The key for this
3316 system to work is a good way to map hardware to packages, in other
3317 words, allow packages to announce what hardware they will work
3320 <p
>I started by providing data files in the isenkram source, and
3321 adding code to download the latest version of these data files at run
3322 time, to ensure every user had the most up to date mapping available.
3323 I also added support for storing the mapping in the Packages file in
3324 the apt repositories, but did not push this approach because while I
3325 was trying to figure out how to best store hardware/package mappings,
3326 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
3327 appstream system
</a
> was announced. I got in touch and suggested to
3328 add the hardware mapping into that data set to be able to use
3329 appstream as a data source, and this was accepted at least for the
3330 Debian version of appstream.
</p
>
3332 <p
>A few days ago using appstream in Debian for this became possible,
3333 and today I uploaded a new version
0.20 of isenkram adding support for
3334 appstream as a data source for mapping hardware to packages. The only
3335 package so far using appstream to announce its hardware support is my
3336 pymissile package. I got help from Matthias Klumpp with figuring out
3337 how do add the required
3338 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
3339 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
3340 this content:
</p
>
3342 <blockquote
><pre
>
3343 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3344 &lt;component
&gt;
3345 &lt;id
&gt;pymissile
&lt;/id
&gt;
3346 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
3347 &lt;name
&gt;pymissile
&lt;/name
&gt;
3348 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
3349 &lt;description
&gt;
3351 Pymissile provides a curses interface to control an original
3352 Marks and Spencer / Striker USB Missile Launcher, as well as a
3353 motion control script to allow a webcamera to control the
3356 &lt;/description
&gt;
3357 &lt;provides
&gt;
3358 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
3359 &lt;/provides
&gt;
3360 &lt;/component
&gt;
3361 </pre
></blockquote
>
3363 <p
>The key for isenkram is the component/provides/modalias value,
3364 which is a glob style match rule for hardware specific strings
3365 (modalias strings) provided by the Linux kernel. In this case, it
3366 will map to all USB devices with vendor code
1130 and product code
3369 <p
>Note, it is important that the license of all the metadata files
3370 are compatible to have permissions to aggregate them into archive wide
3371 appstream files. Matthias suggested to use MIT or BSD licenses for
3372 these files. A challenge is figuring out a good id for the data, as
3373 it is supposed to be globally unique and shared across distributions
3374 (in other words, best to coordinate with upstream what to use). But
3375 it can be changed later or, so we went with the package name as
3376 upstream for this project is dormant.
</p
>
3378 <p
>To get the metadata file installed in the correct location for the
3379 mirror update scripts to pick it up and include its content the
3380 appstream data source, the file must be installed in the binary
3381 package under /usr/share/appdata/. I did this by adding the following
3382 line to debian/pymissile.install:
</p
>
3384 <blockquote
><pre
>
3385 debian/pymissile.metainfo.xml usr/share/appdata
3386 </pre
></blockquote
>
3388 <p
>With that in place, the command line tool isenkram-lookup will list
3389 all packages useful on the current computer automatically, and the GUI
3390 pop-up handler will propose to install the package not already
3391 installed if a hardware dongle is inserted into the machine in
3394 <p
>Details of the modalias field in appstream is available from the
3395 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
3397 <p
>To locate the modalias values of all hardware present in a machine,
3398 try running this command on the command line:
</p
>
3400 <blockquote
><pre
>
3401 cat $(find /sys/devices/|grep modalias)
3402 </pre
></blockquote
>
3404 <p
>To learn more about the isenkram system, please check out
3405 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3406 blog posts tagged isenkram
</a
>.
</p
>
3411 <title>The GNU General Public License is not magic pixie dust
</title>
3412 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
3413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
3414 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
3415 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
3416 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
3417 GPL is not magic pixie dust
</a
>" explain the importance of making sure
3418 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
3419 I quote the blog post from Paul in full here with his permission:
<p
>
3423 <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
>
3426 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
3428 The first step is to choose a
3429 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
3432 The next step is, when someone fails to follow that copyleft license,
3433 <b
>it must be enforced
</b
><br/
>
3435 and its a simple fact of our modern society that such type of
3438 is incredibly expensive to do and incredibly difficult to do.
3441 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
3442 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
3443 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
3444 0x57</a
></small
></p
>
3446 <p
>As the Debian Website
3447 <a href=
"https://bugs.debian.org/
794116">used
</a
>
3448 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
3449 imply, public domain and permissively licensed software can lead to
3450 the production of more proprietary software as people discover useful
3451 software, extend it and or incorporate it into their hardware or
3452 software products. Copyleft licenses such as the GNU GPL were created
3453 to close off this avenue to the production of proprietary software but
3454 such licenses are not enough. With the ongoing adoption of Free
3455 Software by individuals and groups, inevitably the community
's
3456 expectations of license compliance are violated, usually out of
3457 ignorance of the way Free Software works, but not always. As Karen
3458 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
3459 Freedom
">FaiF
</a
>
3460 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
3461 copyleft is nothing if no-one is willing and able to stand up in court
3462 to protect it. The reality of today
's world is that legal
3463 representation is expensive, difficult and time consuming. With
3464 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
3465 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
3466 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
3467 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
3468 of the Linux project, Debian and other groups against GPL violations.
3469 In March the SFC supported a
3470 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
3471 by Christoph Hellwig
</a
> against VMware for refusing to
3472 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
3473 with the GPL
</a
> in relation to their use of parts of the Linux
3474 kernel. Since then two of their sponsors pulled corporate funding and
3476 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
3477 or cancelled their talks
</a
>. As a result they have decided to rely
3478 less on corporate funding and more on the broad community of
3479 individuals who support Free Software and copyleft. So the SFC has
3480 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
3481 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
3482 a community of folks who stand up for copyleft and the GPL by
3483 supporting their work on promoting and supporting copyleft and Free
3486 <p
>If you support Free Software,
3487 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
3488 what the SFC do, agree with their
3489 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
3490 principles
</a
>, are happy about their
3491 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
3492 work on a project that is an SFC
3493 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
3494 just want to stand up for copyleft, please join
3495 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
3496 Allan Webber
</a
>,
3497 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
3499 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
3500 Bacon
</a
>, myself and
3501 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
3503 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
3504 next week your donation will be
3505 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
3506 by an anonymous donor. Please also consider asking your employer to
3507 match your donation or become a sponsor of SFC. Don
't forget to
3508 spread the word about your support for SFC via email, your blog and or
3509 social media accounts.
</p
>
3513 <p
>I agree with Paul on this topic and just signed up as a Supporter
3514 of Software Freedom Conservancy myself. Perhaps you should be a
3515 supporter too?
</p
>
3520 <title>PGP key transition statement for key EE4E02F9
</title>
3521 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
3522 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
3523 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
3524 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
3525 set it up properly. I wanted to generate it offline and have it
3526 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
3527 smart card
</a
> for daily use, and learning how to do it and finding
3528 time to sit down with an offline machine almost took forever. But
3529 finally I
've been able to complete the process, and have now moved
3530 from my old GPG key to a new GPG key. See
3531 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
3532 full transition statement, signed with both my old and new key
</a
> for
3533 the details. This is my new key:
</p
>
3536 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
3537 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
3538 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
3539 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
3540 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
3541 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
3542 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
3545 <p
>The key can be downloaded from the OpenPGP key servers, signed by
3546 my old key.
</p
>
3548 <p
>If you signed my old key
3549 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
3550 I
'd very much appreciate a signature on my new key, details and
3551 instructions in the transition statement. I m happy to reciprocate if
3552 you have a similarly signed transition statement to present.
</p
>
3557 <title>The life and death of a laptop battery
</title>
3558 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
3559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
3560 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
3561 <description><p
>When I get a new laptop, the battery life time at the start is OK.
3562 But this do not last. The last few laptops gave me a feeling that
3563 within a year, the life time is just a fraction of what it used to be,
3564 and it slowly become painful to use the laptop without power connected
3565 all the time. Because of this, when I got a new Thinkpad X230 laptop
3566 about two years ago, I decided to monitor its battery state to have
3567 more hard facts when the battery started to fail.
</p
>
3569 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
3571 <p
>First I tried to find a sensible Debian package to record the
3572 battery status, assuming that this must be a problem already handled
3573 by someone else. I found
3574 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
3575 which collects statistics from the battery, but it was completely
3576 broken. I sent a few suggestions to the maintainer, but decided to
3577 write my own collector as a shell script while I waited for feedback
3579 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3580 blog post about the battery development on a MacBook Air
</a
> I also
3582 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3583 available in Debian.
</p
>
3585 <p
>I started my collector
2013-
07-
15, and it has been collecting
3586 battery stats ever since. Now my
3587 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3588 measurements, from the time the battery was working great until now,
3589 when it is unable to charge above
7% of original capacity. My
3590 collector shell script is quite simple and look like this:
</p
>
3595 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3597 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3598 logfile=/var/log/hjemmenett-battery-status.log
3600 files=
"manufacturer model_name technology serial_number \
3601 energy_full energy_full_design energy_now cycle_count status
"
3603 if [ ! -e
"$logfile
" ] ; then
3605 printf
"timestamp,
"
3607 printf
"%s,
" $f
3610 )
> "$logfile
"
3614 # Print complete message in one echo call, to avoid race condition
3615 # when several log processes run in parallel.
3616 msg=$(printf
"%s,
" $(date +%s); \
3617 for f in $files; do \
3618 printf
"%s,
" $(cat $f); \
3620 echo
"$msg
"
3623 cd /sys/class/power_supply
3626 (cd $bat
&& log_battery
>> "$logfile
")
3630 <p
>The script is called when the power management system detect a
3631 change in the power status (power plug in or out), and when going into
3632 and out of hibernation and suspend. In addition, it collect a value
3633 every
10 minutes. This make it possible for me know when the battery
3634 is discharging, charging and how the maximum charge change over time.
3635 The code for the Debian package
3636 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3637 available on github
</a
>.
</p
>
3639 <p
>The collected log file look like this:
</p
>
3642 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3643 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3645 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3646 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3649 <p
>I wrote a small script to create a graph of the charge development
3650 over time. This graph depicted above show the slow death of my laptop
3653 <p
>But why is this happening? Why are my laptop batteries always
3654 dying in a year or two, while the batteries of space probes and
3655 satellites keep working year after year. If we are to believe
3656 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3657 University
</a
>, the cause is me charging the battery whenever I have a
3658 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3659 all the time, but to stay below
90% of full charge most of the time.
3660 I
've been told that the Tesla electric cars
3661 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3662 the charge of their batteries to
80%
</a
>, with the option to charge to
3663 100% when preparing for a longer trip (not that I would want a car
3664 like Tesla where rights to privacy is abandoned, but that is another
3665 story), which I guess is the option we should have for laptops on
3666 Linux too.
</p
>
3668 <p
>Is there a good and generic way with Linux to tell the battery to
3669 stop charging at
80%, unless requested to charge to
100% once in
3670 preparation for a longer trip? I found
3671 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3672 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3673 80%
</a
>, but could not get it to work (kernel module refused to
3676 <p
>I wonder why the battery capacity was reported to be more than
100%
3677 at the start. I also wonder why the
"full capacity
" increases some
3678 times, and if it is possible to repeat the process to get the battery
3679 back to design capacity. And I wonder if the discharge and charge
3680 speed change over time, or if this stay the same. I did not yet try
3681 to write a tool to calculate the derivative values of the battery
3682 level, but suspect some interesting insights might be learned from
3685 <p
>Update
2015-
09-
24: I got a tip to install the packages
3686 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3687 packages instead of the tp-smapi-dkms package I had tried to use
3688 initially, and use
'tlp setcharge
40 80' to change when charging start
3689 and stop. I
've done so now, but expect my existing battery is toast
3690 and need to be replaced. The proposal is unfortunately Thinkpad
3696 <title>New laptop - some more clues and ideas based on feedback
</title>
3697 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3698 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3699 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3700 <description><p
>Several people contacted me after my previous blog post about my
3701 need for a new laptop, and provided very useful feedback. I wish to
3702 thank every one of these. Several pointed me to the possibility of
3703 fixing my X230, and I am already in the process of getting Lenovo to
3704 do so thanks to the on site, next day support contract covering the
3705 machine. But the battery is almost useless (I expect to replace it
3706 with a non-official battery) and I do not expect the machine to live
3707 for many more years, so it is time to plan its replacement. If I did
3708 not have a support contract, it was suggested to find replacement parts
3709 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3710 might present a language barrier as I do not understand French.
</p
>
3712 <p
>One tip I got was to use the
3713 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3714 compare laptop models. It seem to have more models available than
3715 prisjakt.no. Another tip I got from someone I know have similar
3716 keyboard preferences was that the HP EliteBook
840 keyboard is not
3717 very good, and this matches my experience with earlier EliteBook
3718 keyboards I tested. Because of this, I will not consider it any further.
3720 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3721 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3722 (which is missing from the X240), and is working fairly well with
3723 Debian Sid/Unstable according to
3724 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3725 got on the keyboard quality are not consistent. Some say the keyboard
3726 is good, others say it is ok, while others say it is not very good.
3727 Those with experience from X41 and and X60 agree that the X250
3728 keyboard is not as good as those trusty old laptops, and suggest I
3729 keep and fix my X230 instead of upgrading, or get a used X230 to
3730 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3731 activity and battery status, which is very convenient on my X230. I
'm
3732 also told that the CPU fan is running very often, making it a bit
3733 noisy. In any case, the X250 do not work out of the box with Debian
3734 Stable/Jessie, one of my requirements.
</p
>
3736 <p
>I have also gotten a few vendor proposals, one was
3737 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3738 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3739 The latter look very attractive to me.
</p
>
3741 <p
>Again, thank you all for the very useful feedback. It help a lot
3742 as I keep looking for a replacement.
</p
>
3744 <p
>Update
2015-
07-
06: I was recommended to check out the
3745 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3747 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3748 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3753 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3754 <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>
3755 <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>
3756 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3757 <description><p
>My primary work horse laptop is failing, and will need a
3758 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3759 started flickering yesterday, and I suspect the cause is a broken
3760 cable, as changing the angle of the screen some times get rid of the
3761 flickering.
</p
>
3763 <p
>My requirements have not really changed since I bought it, and is
3765 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3766 described them in
2013</a
>. The last time I bought a laptop, I had
3768 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3769 where I could select at least a few of the requirements (mouse pin,
3770 wifi, weight) and go through the rest manually. Three button mouse
3771 and a good keyboard is not available as an option, and all the three
3772 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3773 G2) lack three mouse buttons). It is also unclear to me how good the
3774 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3775 the keyboard, even if the quality and robustness in the X series have
3776 deteriorated since X41.
</p
>
3778 <p
>I wonder how I can find a sensible laptop when none of the options
3779 seem sensible to me? Are there better services around to search the
3780 set of available laptops for features? Please send me an email if you
3781 have suggestions.
</p
>
3783 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3784 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3785 of endorsed hardware
</a
>, which is useful background information.
</p
>
3790 <title>How to stay with sysvinit in Debian Jessie
</title>
3791 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3792 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3793 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3794 <description><p
>By now, it is well known that Debian Jessie will not be using
3795 sysvinit as its boot system by default. But how can one keep using
3796 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3798 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3799 Schubert
</a
> and
3800 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3803 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3804 keep sysvinit as your boot system, create a file
3805 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3806 you upgrade:
</p
>
3808 <p
><blockquote
><pre
>
3809 Package: systemd-sysv
3810 Pin: release o=Debian
3812 </pre
></blockquote
><p
>
3814 <p
>This file content will tell apt and aptitude to not consider
3815 installing systemd-sysv as part of any installation and upgrade
3816 solution when resolving dependencies, and thus tell it to avoid
3817 systemd as a default boot system. The end result should be that the
3818 upgraded system keep using sysvinit.
</p
>
3820 <p
>If you are installing Jessie for the first time, there is no way to
3821 get sysvinit installed by default (debootstrap used by
3822 debian-installer have no option for this), but one can tell the
3823 installer to switch to sysvinit before the first boot. Either by
3824 using a kernel argument to the installer, or by adding a line to the
3825 preseed file used. First, the kernel command line argument:
3827 <p
><blockquote
><pre
>
3828 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
3829 </pre
></blockquote
><p
>
3831 <p
>Next, the line to use in a preseed file:
</p
>
3833 <p
><blockquote
><pre
>
3834 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
3835 </pre
></blockquote
><p
>
3837 <p
>One can of course also do this after the first boot by installing
3838 the sysvinit-core package.
</p
>
3840 <p
>I recommend only using sysvinit if you really need it, as the
3841 sysvinit boot sequence in Debian have several hardware specific bugs
3842 on Linux caused by the fact that it is unpredictable when hardware
3843 devices show up during boot. But on the other hand, the new default
3844 boot system still have a few rough edges I hope will be fixed before
3845 Jessie is released.
</p
>
3847 <p
>Update
2014-
11-
26: Inspired by
3848 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
3849 blog post by Torsten Glaser
</a
>, added --purge to the preseed
3855 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
3856 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
3857 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
3858 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
3859 <description><p
>The right to communicate with your friends and family in private,
3860 without anyone snooping, is a right every citicen have in a liberal
3861 democracy. But this right is under serious attack these days.
</p
>
3863 <p
>A while back it occurred to me that one way to make the dragnet
3864 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
3865 the whisleblower Snowden) more expensive for Internet email,
3866 is to deliver all email using SMTP via Tor. Such SMTP option would be
3867 a nice addition to the FreedomBox project if we could send email
3868 between FreedomBox machines without leaking metadata about the emails
3869 to the people peeking on the wire. I
3870 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
3871 this on the FreedomBox project mailing list in October
</a
> and got a
3872 lot of useful feedback and suggestions. It also became obvious to me
3873 that this was not a novel idea, as the same idea was tested and
3874 documented by Johannes Berg as early as
2006, and both
3875 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
3876 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
3877 propose a similar method / protocol to pass emails between users.
</p
>
3879 <p
>To implement such system one need to set up a Tor hidden service
3880 providing the SMTP protocol on port
25, and use email addresses
3881 looking like username@hidden-service-name.onion. With such addresses
3882 the connections to port
25 on hidden-service-name.onion using Tor will
3883 go to the correct SMTP server. To do this, one need to configure the
3884 Tor daemon to provide the hidden service and the mail server to accept
3885 emails for this .onion domain. To learn more about Exim configuration
3886 in Debian and test the design provided by Johannes Berg in his FAQ, I
3887 set out yesterday to create a Debian package for making it trivial to
3888 set up such SMTP over Tor service based on Debian. Getting it to work
3889 were fairly easy, and
3890 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
3891 source code for the Debian package
</a
> is available from github. I
3892 plan to move it into Debian if further testing prove this to be a
3893 useful approach.
</p
>
3895 <p
>If you want to test this, set up a blank Debian machine without any
3896 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
3897 get rid of exim4). Install tor, clone the git repository mentioned
3898 above, build the deb and install it on the machine. Next, run
3899 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
3900 the instructions to get the service up and running. Restart tor and
3901 exim when it is done, and test mail delivery using swaks like
3904 <p
><blockquote
><pre
>
3905 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
3906 --to fbx@dutlqrrmjhtfa3vp.onion
3907 </pre
></blockquote
></p
>
3909 <p
>This will test the SMTP delivery using tor. Replace the email
3910 address with your own address to test your server. :)
</p
>
3912 <p
>The setup procedure is still to complex, and I hope it can be made
3913 easier and more automatic. Especially the tor setup need more work.
3914 Also, the package include a tor-smtp tool written in C, but its task
3915 should probably be rewritten in some script language to make the deb
3916 architecture independent. It would probably also make the code easier
3917 to review. The tor-smtp tool currently need to listen on a socket for
3918 exim to talk to it and is started using xinetd. It would be better if
3919 no daemon and no socket is needed. I suspect it is possible to get
3920 exim to run a command line tool for delivery instead of talking to a
3921 socket, and hope to figure out how in a future version of this
3924 <p
>Until I wipe my test machine, I can be reached using the
3925 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
3926 SMTorP. :)
</p
>
3931 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
3932 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
3933 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
3934 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
3935 <description><p
>If you ever had to moderate a mailman list, like the ones on
3936 alioth.debian.org, you know the web interface is fairly slow to
3937 operate. First you visit one web page, enter the moderation password
3938 and get a new page shown with a list of all the messages to moderate
3939 and various options for each email address. This take a while for
3940 every list you moderate, and you need to do it regularly to do a good
3941 job as a list moderator. But there is a quick alternative,
3942 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
3943 listadmin program
</a
>. It allow you to check lists for new messages
3944 to moderate in a fraction of a second. Here is a test run on two
3945 lists I recently took over:
</p
>
3947 <p
><blockquote
><pre
>
3948 % time listadmin xiph
3949 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
3950 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
3956 </pre
></blockquote
></p
>
3958 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
3959 there are no message in the moderation queue. Every morning I
3960 currently moderate
68 mailman lists, and it normally take around two
3961 minutes. When I took over the two pkg-xiph lists above a few days
3962 ago, there were
400 emails waiting in the moderator queue. It took me
3963 less than
15 minutes to process them all using the listadmin
3966 <p
>If you install
3967 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
3968 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
3969 with content like this, the moderation task is a breeze:
</p
>
3971 <p
><blockquote
><pre
>
3972 username username@example.org
3975 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
3978 adminurl https://{domain}/mailman/admindb/{list}
3979 mailman-list@lists.example.com
3982 other-list@otherserver.example.org
3983 </pre
></blockquote
></p
>
3985 <p
>There are other options to set as well. Check the manual page to
3986 learn the details.
</p
>
3988 <p
>If you are forced to moderate lists on a mailman installation where
3989 the SSL certificate is self signed or not properly signed by a
3990 generally accepted signing authority, you can set a environment
3991 variable when calling listadmin to disable SSL verification:
</p
>
3993 <p
><blockquote
><pre
>
3994 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
3995 </pre
></blockquote
></p
>
3997 <p
>If you want to moderate a subset of the lists you take care of, you
3998 can provide an argument to the listadmin script like I do in the
3999 initial screen dump (the xiph argument). Using an argument, only
4000 lists matching the argument string will be processed. This make it
4001 quick to accept messages if you notice the moderation request in your
4004 <p
>Without the listadmin program, I would never be the moderator of
68
4005 mailing lists, as I simply do not have time to spend on that if the
4006 process was any slower. The listadmin program have saved me hours of
4007 time I could spend elsewhere over the years. It truly is nice free
4010 <p
>As usual, if you use Bitcoin and want to show your support of my
4011 activities, please send Bitcoin donations to my address
4012 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4014 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
4015 configuration example. Also, I
've been told that the
4016 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
4022 <title>Debian Jessie, PXE and automatic firmware installation
</title>
4023 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
4024 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
4025 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
4026 <description><p
>When PXE installing laptops with Debian, I often run into the
4027 problem that the WiFi card require some firmware to work properly.
4028 And it has been a pain to fix this using preseeding in Debian.
4029 Normally something more is needed. But thanks to
4030 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
4031 package
</a
> and its recent tasksel extension, it has now become easy
4032 to do this using simple preseeding.
</p
>
4034 <p
>The isenkram-cli package provide tasksel tasks which will install
4035 firmware for the hardware found in the machine (actually, requested by
4036 the kernel modules for the hardware). (It can also install user space
4037 programs supporting the hardware detected, but that is not the focus
4038 of this story.)
</p
>
4040 <p
>To get this working in the default installation, two preeseding
4041 values are needed. First, the isenkram-cli package must be installed
4042 into the target chroot (aka the hard drive) before tasksel is executed
4043 in the pkgsel step of the debian-installer system. This is done by
4044 preseeding the base-installer/includes debconf value to include the
4045 isenkram-cli package. The package name is next passed to debootstrap
4046 for installation. With the isenkram-cli package in place, tasksel
4047 will automatically use the isenkram tasks to detect hardware specific
4048 packages for the machine being installed and install them, because
4049 isenkram-cli contain tasksel tasks.
</p
>
4051 <p
>Second, one need to enable the non-free APT repository, because
4052 most firmware unfortunately is non-free. This is done by preseeding
4053 the apt-mirror-setup step. This is unfortunate, but for a lot of
4054 hardware it is the only option in Debian.
</p
>
4056 <p
>The end result is two lines needed in your preseeding file to get
4057 firmware installed automatically by the installer:
</p
>
4059 <p
><blockquote
><pre
>
4060 base-installer base-installer/includes string isenkram-cli
4061 apt-mirror-setup apt-setup/non-free boolean true
4062 </pre
></blockquote
></p
>
4064 <p
>The current version of isenkram-cli in testing/jessie will install
4065 both firmware and user space packages when using this method. It also
4066 do not work well, so use version
0.15 or later. Installing both
4067 firmware and user space packages might give you a bit more than you
4068 want, so I decided to split the tasksel task in two, one for firmware
4069 and one for user space programs. The firmware task is enabled by
4070 default, while the one for user space programs is not. This split is
4071 implemented in the package currently in unstable.
</p
>
4073 <p
>If you decide to give this a go, please let me know (via email) how
4074 this recipe work for you. :)
</p
>
4076 <p
>So, I bet you are wondering, how can this work. First and
4077 foremost, it work because tasksel is modular, and driven by whatever
4078 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4079 isenkram-cli package place two files for tasksel to find. First there
4080 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
4082 <p
><blockquote
><pre
>
4083 Task: isenkram-packages
4085 Description: Hardware specific packages (autodetected by isenkram)
4086 Based on the detected hardware various hardware specific packages are
4088 Test-new-install: show show
4090 Packages: for-current-hardware
4092 Task: isenkram-firmware
4094 Description: Hardware specific firmware packages (autodetected by isenkram)
4095 Based on the detected hardware various hardware specific firmware
4096 packages are proposed.
4097 Test-new-install: mark show
4099 Packages: for-current-hardware-firmware
4100 </pre
></blockquote
></p
>
4102 <p
>The key parts are Test-new-install which indicate how the task
4103 should be handled and the Packages line referencing to a script in
4104 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4105 list of packages to install. The for-current-hardware-firmware script
4106 look like this to list relevant firmware for the machine:
4108 <p
><blockquote
><pre
>
4111 PATH=/usr/sbin:$PATH
4113 isenkram-autoinstall-firmware -l
4114 </pre
></blockquote
></p
>
4116 <p
>With those two pieces in place, the firmware is installed by
4117 tasksel during the normal d-i run. :)
</p
>
4119 <p
>If you want to test what tasksel will install when isenkram-cli is
4120 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
4121 --new-install
</tt
> to get the list of packages that tasksel would
4124 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
4125 pilots in testing this feature, as isenkram is used there now to
4126 install firmware, replacing the earlier scripts.
</p
>
4131 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
4132 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
4133 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
4134 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
4135 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
4136 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4137 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
4138 on a screen normally showing the bread types and prizes:
</p
>
4140 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
4142 <p
>If it had booted as it was supposed to, I would never had known
4143 about this hidden Linux installation. It is interesting what
4144 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
4149 <title>New lsdvd release version
0.17 is ready
</title>
4150 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
4151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
4152 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
4153 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
4154 got a new set of developers a few weeks ago, after the original
4155 developer decided to step down and pass the project to fresh blood.
4156 This project is now maintained by Petter Reinholdtsen and Steve
4159 <p
>I just wrapped up
4160 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
4161 new lsdvd release
</a
>, available in git or from
4162 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
4163 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
4168 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
4169 <li
>Check for garbage in the program chains, which indicate that a track is
4170 non-existant, to work around additional copy protection
</li
>
4171 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
4172 <li
>Fix pallete display of first entry
</li
>
4173 <li
>Fix include orders
</li
>
4174 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
4175 <li
>Fix the chapter count
</li
>
4176 <li
>Make sure the array size and the array limit used when initialising
4177 the palette size is the same.
</li
>
4178 <li
>Fix array printing.
</li
>
4179 <li
>Correct subsecond calculations.
</li
>
4180 <li
>Add sector information to the output format.
</li
>
4181 <li
>Clean up code to be closer to ANSI C and compile without warnings
4182 with more GCC compiler warnings.
</li
>
4186 <p
>This change bring together patches for lsdvd in use in various
4187 Linux and Unix distributions, as well as patches submitted to the
4188 project the last nine years. Please check it out. :)
</p
>
4193 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
4194 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
4195 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
4196 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
4197 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4198 project
</a
> provide a Linux solution for schools, including a
4199 powerful desktop with education software, a central server providing
4200 web pages, user database, user home directories, central login and PXE
4201 boot of both clients without disk and the installation to install Debian
4202 Edu on machines with disk (and a few other services perhaps to small
4203 to mention here). We in the Debian Edu team are currently working on
4204 the Jessie based version, trying to get everything in shape before the
4205 freeze, to avoid having to maintain our own package repository in the
4207 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
4208 status
</a
> can be seen on the Debian wiki, and there is still heaps of
4209 work left. Some fatal problems block testing, breaking the installer,
4210 but it is possible to work around these to get anyway. Here is a
4211 recipe on how to get the installation limping along.
</p
>
4213 <p
>First, download the test ISO via
4214 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
4215 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
4217 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
4218 The ISO build was broken on Tuesday, so we do not get a new ISO every
4219 12 hours or so, but thankfully the ISO we already got we are able to
4220 install with some tweaking.
</p
>
4222 <p
>When you get to the Debian Edu profile question, go to tty2
4223 (use Alt-Ctrl-F2), run
</p
>
4225 <p
><blockquote
><pre
>
4226 nano /usr/bin/edu-eatmydata-install
4227 </pre
></blockquote
></p
>
4229 <p
>and add
'exit
0' as the second line, disabling the eatmydata
4230 optimization. Return to the installation, select the profile you want
4231 and continue. Without this change, exim4-config will fail to install
4232 due to a known bug in eatmydata.
</p
>
4234 <p
>When you get the grub question at the end, answer /dev/sda (or if
4235 this do not work, figure out what your correct value would be. All my
4236 test machines need /dev/sda, so I have no advice if it do not fit
4237 your need.
</p
>
4239 <p
>If you installed a profile including a graphical desktop, log in as
4240 root after the initial boot from hard drive, and install the
4241 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4242 or mate. If you want several desktop options, install more than one
4243 metapackage. Once this is done, reboot and you should have a working
4244 graphical login screen. This workaround should no longer be needed
4245 once the education-tasks package version
1.801 enter testing in two
4248 <p
>I believe the ISO build will start working on two days when the new
4249 tasksel package enter testing and Steve McIntyre get a chance to
4250 update the debian-cd git repository. The eatmydata, grub and desktop
4251 issues are already fixed in unstable and testing, and should show up
4252 on the ISO as soon as the ISO build start working again. Well the
4253 eatmydata optimization is really just disabled. The proper fix
4254 require an upload by the eatmydata maintainer applying the patch
4255 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
4256 The rest have proper fixes in unstable.
</p
>
4258 <p
>I hope this get you going with the installation testing, as we are
4259 quickly running out of time trying to get our Jessie based
4260 installation ready before the distribution freeze in a month.
</p
>
4265 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
4266 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
4267 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
4268 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
4269 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
4270 to handle my fairly large DVD collection. It is a nice command line
4271 tool to get details about a DVD, like title, tracks, track length,
4272 etc, in XML, Perl or human readable format. But lsdvd have not seen
4273 any new development since
2006 and had a few irritating bugs affecting
4274 its use with some DVDs. Upstream seemed to be dead, and in January I
4275 sent a small probe asking for a version control repository for the
4276 project, without any reply. But I use it regularly and would like to
4277 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
4278 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
4279 the project admin, and after getting a reply from him explaining that
4280 he was no longer interested in the project, I asked if I could take
4281 over. And yesterday, I became project admin.
</p
>
4283 <p
>I
've been in touch with a Gentoo developer and the Debian
4284 maintainer interested in joining forces to maintain the upstream
4285 project, and I hope we can get a new release out fairly quickly,
4286 collecting the patches spread around on the internet into on place.
4287 I
've added the relevant Debian patches to the freshly created git
4288 repository, and expect the Gentoo patches to make it too. If you got
4289 a DVD collection and care about command line tools, check out
4290 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
4291 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
4292 list
</a
>. :)
</p
>
4297 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
4298 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
4299 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
4300 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
4301 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
4302 a lot quicker. When we install more than
2000 packages in
4303 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
4304 tasksel in the installer, unpacking the binary packages take forever.
4305 A part of the slow I/O issue was discussed in
4306 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
4307 much file system sync-ing done by dpkg, which is the package
4308 responsible for unpacking the binary packages. Other parts (like code
4309 executed by postinst scripts) might also sync to disk during
4310 installation. All this sync-ing to disk do not really make sense to
4311 me. If the machine crash half-way through, I start over, I do not try
4312 to salvage the half installed system. So the failure sync-ing is
4313 supposed to protect against, hardware or system crash, is not really
4314 relevant while the installer is running.
</p
>
4316 <p
>A few days ago, I thought of a way to get rid of all the file
4317 system sync()-ing in a fairly non-intrusive way, without the need to
4318 change the code in several packages. The idea is not new, but I have
4319 not heard anyone propose the approach using dpkg-divert before. It
4320 depend on the small and clever package
4321 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
4322 uses LD_PRELOAD to replace the system functions for syncing data to
4323 disk with functions doing nothing, thus allowing programs to live
4324 dangerous while speeding up disk I/O significantly. Instead of
4325 modifying the implementation of dpkg, apt and tasksel (which are the
4326 packages responsible for selecting, fetching and installing packages),
4327 it occurred to me that we could just divert the programs away, replace
4328 them with a simple shell wrapper calling
4329 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
4330 Two days ago I decided to test the idea, and wrapped up a simple
4331 implementation for the Debian Edu udeb.
</p
>
4333 <p
>The effect was stunning. In my first test it reduced the running
4334 time of the pkgsel step (installing tasks) from
64 to less than
44
4335 minutes (
20 minutes shaved off the installation) on an old Dell
4336 Latitude D505 machine. I am not quite sure what the optimised time
4337 would have been, as I messed up the testing a bit, causing the debconf
4338 priority to get low enough for two questions to pop up during
4339 installation. As soon as I saw the questions I moved the installation
4340 along, but do not know how long the question were holding up the
4341 installation. I did some more measurements using Debian Edu Jessie,
4342 and got these results. The time measured is the time stamp in
4343 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
4344 "pkgsel: finishing up
" lines, if you want to do the same measurement
4345 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4346 timing thus do not depend on how quickly the user handle the tasksel
4349 <p
><table
>
4352 <th
>Machine/setup
</th
>
4353 <th
>Original tasksel
</th
>
4354 <th
>Optimised tasksel
</th
>
4355 <th
>Reduction
</th
>
4359 <td
>Latitude D505 Main+LTSP LXDE
</td
>
4360 <td
>64 min (
07:
46-
08:
50)
</td
>
4361 <td
><44 min (
11:
27-
12:
11)
</td
>
4362 <td
>>20 min
18%
</td
>
4366 <td
>Latitude D505 Roaming LXDE
</td
>
4367 <td
>57 min (
08:
48-
09:
45)
</td
>
4368 <td
>34 min (
07:
43-
08:
17)
</td
>
4369 <td
>23 min
40%
</td
>
4373 <td
>Latitude D505 Minimal
</td
>
4374 <td
>22 min (
10:
37-
10:
59)
</td
>
4375 <td
>11 min (
11:
16-
11:
27)
</td
>
4376 <td
>11 min
50%
</td
>
4380 <td
>Thinkpad X200 Minimal
</td
>
4381 <td
>6 min (
08:
19-
08:
25)
</td
>
4382 <td
>4 min (
08:
04-
08:
08)
</td
>
4383 <td
>2 min
33%
</td
>
4387 <td
>Thinkpad X200 Roaming KDE
</td
>
4388 <td
>19 min (
09:
21-
09:
40)
</td
>
4389 <td
>15 min (
10:
25-
10:
40)
</td
>
4390 <td
>4 min
21%
</td
>
4393 </table
></p
>
4395 <p
>The test is done using a netinst ISO on a USB stick, so some of the
4396 time is spent downloading packages. The connection to the Internet
4397 was
100Mbit/s during testing, so downloading should not be a
4398 significant factor in the measurement. Download typically took a few
4399 seconds to a few minutes, depending on the amount of packages being
4400 installed.
</p
>
4402 <p
>The speedup is implemented by using two hooks in
4403 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
4404 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
4405 finish-install.d hook to remove the divert at the end of the
4406 installation. I picked the pre-pkgsel.d hook instead of the
4407 post-base-installer.d hook because I test using an ISO without the
4408 eatmydata package included, and the post-base-installer.d hook in
4409 Debian Edu can only operate on packages included in the ISO. The
4410 negative effect of this is that I am unable to activate this
4411 optimization for the kernel installation step in d-i. If the code is
4412 moved to the post-base-installer.d hook, the speedup would be larger
4413 for the entire installation.
</p
>
4415 <p
>I
've implemented this in the
4416 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
4417 git repository, and plan to provide the optimization as part of the
4418 Debian Edu installation. If you want to test this yourself, you can
4419 create two files in the installer (or in an udeb). One shell script
4420 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
4422 <p
><blockquote
><pre
>
4425 . /usr/share/debconf/confmodule
4427 logger -t my-pkgsel
"info: $*
"
4430 logger -t my-pkgsel
"error: $*
"
4432 override_install() {
4433 apt-install eatmydata || true
4434 if [ -x /target/usr/bin/eatmydata ] ; then
4435 for bin in dpkg apt-get aptitude tasksel ; do
4437 # Test that the file exist and have not been diverted already.
4438 if [ -f /target$file ] ; then
4439 info
"diverting $file using eatmydata
"
4440 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
4441 > /target$file.edu
4442 chmod
755 /target$file.edu
4443 in-target dpkg-divert --package debian-edu-config \
4444 --rename --quiet --add $file
4445 ln -sf ./$bin.edu /target$file
4447 error
"unable to divert $file, as it is missing.
"
4451 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
4456 </pre
></blockquote
></p
>
4458 <p
>To clean up, another shell script should go into
4459 /usr/lib/finish-install.d/ with code like this:
4461 <p
><blockquote
><pre
>
4463 . /usr/share/debconf/confmodule
4465 logger -t my-finish-install
"error: $@
"
4467 remove_install_override() {
4468 for bin in dpkg apt-get aptitude tasksel ; do
4470 if [ -x /target$file.edu ] ; then
4472 in-target dpkg-divert --package debian-edu-config \
4473 --rename --quiet --remove $file
4476 error
"Missing divert for $file.
"
4479 sync # Flush file buffers before continuing
4482 remove_install_override
4483 </pre
></blockquote
></p
>
4485 <p
>In Debian Edu, I placed both code fragments in a separate script
4486 edu-eatmydata-install and call it from the pre-pkgsel.d and
4487 finish-install.d scripts.
</p
>
4489 <p
>By now you might ask if this change should get into the normal
4490 Debian installer too? I suspect it should, but am not sure the
4491 current debian-installer coordinators find it useful enough. It also
4492 depend on the side effects of the change. I
'm not aware of any, but I
4493 guess we will see if the change is safe after some more testing.
4494 Perhaps there is some package in Debian depending on sync() and
4495 fsync() having effect? Perhaps it should go into its own udeb, to
4496 allow those of us wanting to enable it to do so without affecting
4499 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
4500 will break installation of all programs using gnutls because of
4501 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
4502 eatmydata package in Debian will solve it.
</p
>
4504 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
4505 the optimization work again. And I have discovered that the
4506 dpkg-divert trick is not really needed and implemented a slightly
4507 simpler approach as part of the debian-edu-install package. See
4508 tools/edu-eatmydata-install in the source package.
</p
>
4510 <p
>Update
2014-
11-
11: Unfortunately, a new
4511 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
4512 triggering on i386 made it into testing, and broke this installation
4513 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
4514 request
768893</a
> is accepted, it should be working again.
</p
>
4519 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
4520 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
4521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
4522 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
4523 <description><p
>Yesterday, I had the pleasure of attending a talk with the
4524 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
4525 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
4526 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
4527 learn that there is a large set of publicly available key servers to
4528 use when looking for peoples public key. So far I have used
4529 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4530 were misbehaving, but those days are ended. The servers I have used
4531 up until yesterday have been slow and some times unavailable. I hope
4532 those problems are gone now.
</p
>
4534 <p
>Behind the round robin DNS entry of the
4535 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
4536 there is a pool of more than
100 keyservers which are checked every
4537 day to ensure they are well connected and up to date. It must be
4538 better than what I have used so far. :)
</p
>
4540 <p
>Yesterdays speaker told me that the service is the default
4541 keyserver provided by the default configuration in GnuPG, but this do
4542 not seem to be used in Debian. Perhaps it should?
</p
>
4544 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
4547 <p
><blockquote
><pre
>
4548 keyserver pool.sks-keyservers.net
4549 </pre
></blockquote
></p
>
4551 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
4552 entries in DNS. Just for fun, I did just that at work, so now every
4553 user of GnuPG at the University of Oslo should find a OpenGPG
4554 keyserver automatically should their need it:
</p
>
4556 <p
><blockquote
><pre
>
4557 % host -t srv _pgpkey-http._tcp.uio.no
4558 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
4560 </pre
></blockquote
></p
>
4562 <p
>Now if only
4563 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
4564 HKP lookup protocol
</a
> supported finding signature paths, I would be
4565 very happy. It can look up a given key or search for a user ID, but I
4566 normally do not want that, but to find a trust path from my key to
4567 another key. Given a user ID or key ID, I would like to find (and
4568 download) the keys representing a signature path from my key to the
4569 key in question, to be able to get a trust path between the two keys.
4570 This is as far as I can tell not possible today. Perhaps something
4571 for a future version of the protocol?
</p
>
4576 <title>From English wiki to translated PDF and epub via Docbook
</title>
4577 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
4578 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
4579 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4580 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4581 project
</a
> provide an instruction manual for teachers, system
4582 administrators and other users that contain useful tips for setting up
4583 and maintaining a Debian Edu installation. This text is about how the
4584 text processing of this manual is handled in the project.
</p
>
4586 <p
>One goal of the project is to provide information in the native
4587 language of its users, and for this we need to handle translations.
4588 But we also want to make sure each language contain the same
4589 information, so for this we need a good way to keep the translations
4590 in sync. And we want it to be easy for our users to improve the
4591 documentation, avoiding the need to learn special formats or tools to
4592 contribute, and the obvious way to do this is to make it possible to
4593 edit the documentation using a web browser. We also want it to be
4594 easy for translators to keep the translation up to date, and give them
4595 help in figuring out what need to be translated. Here is the list of
4596 tools and the process we have found trying to reach all these
4599 <p
>We maintain the authoritative source of our manual in the
4600 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4601 wiki
</a
>, as several wiki pages written in English. It consist of one
4602 front page with references to the different chapters, several pages
4603 for each chapter, and finally one
"collection page
" gluing all the
4604 chapters together into one large web page (aka
4605 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4606 AllInOne page
</a
>). The AllInOne page is the one used for further
4607 processing and translations. Thanks to the fact that the
4608 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4609 wiki.debian.org support exporting pages in
4610 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4611 the list of pages to export using the raw version of the AllInOne
4612 page, loop over each of them to generate a Docbook XML version of the
4613 manual. This process also download images and transform image
4614 references to use the locally downloaded images. The generated
4615 Docbook XML files are slightly broken, so some post-processing is done
4616 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4617 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4618 a handfull of images. The XML file can now be used to generate PDF, HTML
4619 and epub versions of the English manual. This is the basic step of
4620 our process, making PDF (using dblatex), HTML (using xsltproc) and
4621 epub (using dbtoepub) version from Docbook XML, and the resulting files
4622 are placed in the debian-edu-doc-en binary package.
</p
>
4624 <p
>But English documentation is not enough for us. We want translated
4625 documentation too, and we want to make it easy for translators to
4626 track the English original. For this we use the
4627 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4628 which allow us to transform the English Docbook XML file into a
4629 translation file (a .pot file), usable with the normal gettext based
4630 translation tools used by those translating free software. The pot
4631 file is used to create and maintain translation files (several .po
4632 files), which the translations update with the native language
4633 translations of all titles, paragraphs and blocks of text in the
4634 original. The next step is combining the original English Docbook XML
4635 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4636 create a translated Docbook XML file (in this case
4637 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4638 translated, if the translation is not complete) Docbook XML file can
4639 then be used like the original to create a PDF, HTML and epub version
4640 of the documentation.
</p
>
4642 <p
>The translators use different tools to edit the .po files. We
4644 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4645 while some use emacs and vi, others can use web based editors like
4646 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4647 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4648 is where the .po file end up, in our git repository. Updated
4649 translations can either be committed directly to git, or submitted as
4650 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4651 against the debian-edu-doc package
</a
>.
</p
>
4653 <p
>One challenge is images, which both might need to be translated (if
4654 they show translated user applications), and are needed in different
4655 formats when creating PDF and HTML versions (epub is a HTML version in
4656 this regard). For this we transform the original PNG images to the
4657 needed density and format during build, and have a way to provide
4658 translated images by storing translated versions in
4659 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4660 package maintainers know more.
</p
>
4662 <p
>If you wonder what the result look like, we provide
4663 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4664 of the documentation packages on the web
</a
>. See for example the
4665 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4666 PDF version
</a
> or the
4667 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4668 HTML version
</a
>. We do not yet build the epub version by default,
4669 but perhaps it will be done in the future.
</p
>
4671 <p
>To learn more, check out
4672 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4673 debian-edu-doc package
</a
>,
4674 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4675 manual on the wiki
</a
> and
4676 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4677 translation instructions
</a
> in the manual.
</p
>
4682 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4683 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4685 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4686 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4687 related packages relevant for the computer installed automatically.
4688 So I implemented one, using
4689 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4690 package
</a
>. To use it, install the tasksel and isenkram packages and
4691 run tasksel as user root. You should be presented with a new option,
4692 "Hardware specific packages (autodetected by isenkram)
". When you
4693 select it, tasksel will install the packages isenkram claim is fit for
4694 the current hardware, hot pluggable or not.
<p
>
4696 <p
>The implementation is in two files, one is the tasksel menu entry
4697 description, and the other is the script used to extract the list of
4698 packages to install. The first part is in
4699 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4702 <p
><blockquote
><pre
>
4705 Description: Hardware specific packages (autodetected by isenkram)
4706 Based on the detected hardware various hardware specific packages are
4708 Test-new-install: mark show
4710 Packages: for-current-hardware
4711 </pre
></blockquote
></p
>
4713 <p
>The second part is in
4714 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4717 <p
><blockquote
><pre
>
4722 isenkram-autoinstall-firmware -l
4724 </pre
></blockquote
></p
>
4726 <p
>All in all, a very short and simple implementation making it
4727 trivial to install the hardware dependent package we all may want to
4728 have installed on our machines. I
've not been able to find a way to
4729 get tasksel to tell you exactly which packages it plan to install
4730 before doing the installation. So if you are curious or careful,
4731 check the output from the isenkram-* command line tools first.
</p
>
4733 <p
>The information about which packages are handling which hardware is
4734 fetched either from the isenkram package itself in
4735 /usr/share/isenkram/, from git.debian.org or from the APT package
4736 database (using the Modaliases header). The APT package database
4737 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4738 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4739 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4740 the python-apt code (bug
4741 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4742 workaround I was able to get rid of the file descriptor leak and
4743 reduce the memory leak from ~
30 MiB per hardware detection down to
4744 around
2 MiB per hardware detection. It should make the desktop
4745 daemon a lot more useful. The fix is in version
0.7 uploaded to
4746 unstable today.
</p
>
4748 <p
>I believe the current way of mapping hardware to packages in
4749 Isenkram is is a good draft, but in the future I expect isenkram to
4750 use the AppStream data source for this. A proposal for getting proper
4751 AppStream support into Debian is floating around as
4752 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4753 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4754 project
</a
> will take place this summer to improve the situation. I
4755 look forward to seeing the result, and welcome patches for isenkram to
4756 start using the information when it is ready.
</p
>
4758 <p
>If you want your package to map to some specific hardware, either
4759 add a
"Xb-Modaliases
" header to your control file like I did in
4760 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4761 package
</a
> or submit a bug report with the details to the isenkram
4763 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4764 blog posts tagged isenkram
</a
> for details on the notation. I expect
4765 the information will be migrated to AppStream eventually, but for the
4766 moment I got no better place to store it.
</p
>
4771 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4772 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4773 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4774 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4775 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4776 project
</a
> is working on providing the software and hardware to make
4777 it easy for non-technical people to host their data and communication
4778 at home, and being able to communicate with their friends and family
4779 encrypted and away from prying eyes. It is still going strong, and
4780 today a major mile stone was reached.
</p
>
4782 <p
>Today, the last of the packages currently used by the project to
4783 created the system images were accepted into Debian Unstable. It was
4784 the freedombox-setup package, which is used to configure the images
4785 during build and on the first boot. Now all one need to get going is
4786 the build code from the freedom-maker git repository and packages from
4787 Debian. And once the freedombox-setup package enter testing, we can
4788 build everything directly from Debian. :)
</p
>
4790 <p
>Some key packages used by Freedombox are
4791 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4792 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4793 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4794 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4795 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4796 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4797 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4798 are plans to integrate more packages into the setup. User
4799 documentation is maintained on the Debian wiki. Please
4800 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4801 the manual
</a
> and help us improve it.
</p
>
4803 <p
>To test for yourself and create boot images with the FreedomBox
4804 setup, run this on a Debian machine using a user with sudo rights to
4805 become root:
</p
>
4807 <p
><pre
>
4808 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4809 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4811 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4813 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4814 </pre
></p
>
4816 <p
>Root access is needed to run debootstrap and mount loopback
4817 devices. See the README in the freedom-maker git repo for more
4818 details on the build. If you do not want all three images, trim the
4819 make line. Note that the virtualbox-image target is not really
4820 virtualbox specific. It create a x86 image usable in kvm, qemu,
4821 vmware and any other x86 virtual machine environment. You might need
4822 the version of vmdebootstrap in Jessie to get the build working, as it
4823 include fixes for a race condition with kpartx.
</p
>
4825 <p
>If you instead want to install using a Debian CD and the preseed
4826 method, boot a Debian Wheezy ISO and use this boot argument to load
4827 the preseed values:
</p
>
4829 <p
><pre
>
4830 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4831 </pre
></p
>
4833 <p
>I have not tested it myself the last few weeks, so I do not know if
4834 it still work.
</p
>
4836 <p
>If you wonder how to help, one task you could look at is using
4837 systemd as the boot system. It will become the default for Linux in
4838 Jessie, so we need to make sure it is usable on the Freedombox. I did
4839 a simple test a few weeks ago, and noticed dnsmasq failed to start
4840 during boot when using systemd. I suspect there are other problems
4841 too. :) To detect problems, there is a test suite included, which can
4842 be run from the plinth web interface.
</p
>
4844 <p
>Give it a go and let us know how it goes on the mailing list, and help
4845 us get the new release published. :) Please join us on
4846 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4847 irc.debian.org)
</a
> and
4848 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4849 mailing list
</a
> if you want to help make this vision come true.
</p
>
4854 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
4855 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
4856 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
4857 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
4858 <description><p
>For a while now, I have been looking for a sensible offsite backup
4859 solution for use at home. My requirements are simple, it must be
4860 cheap and locally encrypted (in other words, I keep the encryption
4861 keys, the storage provider do not have access to my private files).
4862 One idea me and my friends had many years ago, before the cloud
4863 storage providers showed up, was to use Google mail as storage,
4864 writing a Linux block device storing blocks as emails in the mail
4865 service provided by Google, and thus get heaps of free space. On top
4866 of this one can add encryption, RAID and volume management to have
4867 lots of (fairly slow, I admit that) cheap and encrypted storage. But
4868 I never found time to implement such system. But the last few weeks I
4869 have looked at a system called
4870 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
4871 mounted network backed file system with the features I need.
</p
>
4873 <p
>S3QL is a fuse file system with a local cache and cloud storage,
4874 handling several different storage providers, any with Amazon S3,
4875 Google Drive or OpenStack API. There are heaps of such storage
4876 providers. S3QL can also use a local directory as storage, which
4877 combined with sshfs allow for file storage on any ssh server. S3QL
4878 include support for encryption, compression, de-duplication, snapshots
4879 and immutable file systems, allowing me to mount the remote storage as
4880 a local mount point, look at and use the files as if they were local,
4881 while the content is stored in the cloud as well. This allow me to
4882 have a backup that should survive fire. The file system can not be
4883 shared between several machines at the same time, as only one can
4884 mount it at the time, but any machine with the encryption key and
4885 access to the storage service can mount it if it is unmounted.
</p
>
4887 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
4888 package is included already. So to get started, run
<tt
>apt-get
4889 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
4890 Greenqloud, after reading their nice recipe on
4891 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
4892 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
4893 in Iceland more than those in USA when it come to keeping my personal
4894 data safe and private, and thus would rather spend money on a company
4895 in Iceland. Another nice recipe is available from the article
4896 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
4897 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
4898 Admin magazine. When the provider is picked, figure out how to get
4899 the API key needed to connect to the storage API. With Greencloud,
4900 the key did not show up until I had added payment details to my
4903 <p
>Armed with the API access details, it is time to create the file
4904 system. First, create a new bucket in the cloud. This bucket is the
4905 file system storage area. I picked a bucket name reflecting the
4906 machine that was going to store data there, but any name will do.
4907 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
4908 the API login and password, and a locally created password. Store it
4909 all in ~root/.s3ql/authinfo2 like this:
4911 <p
><blockquote
><pre
>
4913 storage-url: s3c://s.greenqloud.com:
443/bucket-name
4914 backend-login: API-login
4915 backend-password: API-password
4916 fs-passphrase: local-password
4917 </pre
></blockquote
></p
>
4919 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
4920 but any sensible way to create a fairly random password should do it.
4921 Armed with these details, it is now time to run mkfs, entering the API
4922 details and password to create it:
</p
>
4924 <p
><blockquote
><pre
>
4925 # mkdir -m
700 /var/lib/s3ql-cache
4926 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4927 --ssl s3c://s.greenqloud.com:
443/bucket-name
4928 Enter backend login:
4929 Enter backend password:
4930 Before using S3QL, make sure to read the user
's guide, especially
4931 the
'Important Rules to Avoid Loosing Data
' section.
4932 Enter encryption password:
4933 Confirm encryption password:
4934 Generating random encryption key...
4935 Creating metadata tables...
4945 Compressing and uploading metadata...
4946 Wrote
0.00 MB of compressed metadata.
4947 #
</pre
></blockquote
></p
>
4949 <p
>The next step is mounting the file system to make the storage available.
4951 <p
><blockquote
><pre
>
4952 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4953 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4954 Using
4 upload threads.
4955 Downloading and decompressing metadata...
4965 Mounting filesystem...
4967 Filesystem Size Used Avail Use% Mounted on
4968 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
4970 </pre
></blockquote
></p
>
4972 <p
>The file system is now ready for use. I use rsync to store my
4973 backups in it, and as the metadata used by rsync is downloaded at
4974 mount time, no network traffic (and storage cost) is triggered by
4975 running rsync. To unmount, one should not use the normal umount
4976 command, as this will not flush the cache to the cloud storage, but
4977 instead running the umount.s3ql command like this:
4979 <p
><blockquote
><pre
>
4982 </pre
></blockquote
></p
>
4984 <p
>There is a fsck command available to check the file system and
4985 correct any problems detected. This can be used if the local server
4986 crashes while the file system is mounted, to reset the
"already
4987 mounted
" flag. This is what it look like when processing a working
4988 file system:
</p
>
4990 <p
><blockquote
><pre
>
4991 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
4992 Using cached metadata.
4993 File system seems clean, checking anyway.
4994 Checking DB integrity...
4995 Creating temporary extra indices...
4996 Checking lost+found...
4997 Checking cached objects...
4998 Checking names (refcounts)...
4999 Checking contents (names)...
5000 Checking contents (inodes)...
5001 Checking contents (parent inodes)...
5002 Checking objects (reference counts)...
5003 Checking objects (backend)...
5004 ..processed
5000 objects so far..
5005 ..processed
10000 objects so far..
5006 ..processed
15000 objects so far..
5007 Checking objects (sizes)...
5008 Checking blocks (referenced objects)...
5009 Checking blocks (refcounts)...
5010 Checking inode-block mapping (blocks)...
5011 Checking inode-block mapping (inodes)...
5012 Checking inodes (refcounts)...
5013 Checking inodes (sizes)...
5014 Checking extended attributes (names)...
5015 Checking extended attributes (inodes)...
5016 Checking symlinks (inodes)...
5017 Checking directory reachability...
5018 Checking unix conventions...
5019 Checking referential integrity...
5020 Dropping temporary indices...
5021 Backing up old metadata...
5031 Compressing and uploading metadata...
5032 Wrote
0.89 MB of compressed metadata.
5034 </pre
></blockquote
></p
>
5036 <p
>Thanks to the cache, working on files that fit in the cache is very
5037 quick, about the same speed as local file access. Uploading large
5038 amount of data is to me limited by the bandwidth out of and into my
5039 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
5040 which is very close to my upload speed, and downloading the same
5041 Debian installation ISO gave me
610 kiB/s, close to my download speed.
5042 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
5043 network, not the file system code. I do not know what a good cache
5044 size would be, but suspect that the cache should e larger than your
5045 working set.
</p
>
5047 <p
>I mentioned that only one machine can mount the file system at the
5048 time. If another machine try, it is told that the file system is
5051 <p
><blockquote
><pre
>
5052 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5053 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
5054 Using
8 upload threads.
5055 Backend reports that fs is still mounted elsewhere, aborting.
5057 </pre
></blockquote
></p
>
5059 <p
>The file content is uploaded when the cache is full, while the
5060 metadata is uploaded once every
24 hour by default. To ensure the
5061 file system content is flushed to the cloud, one can either umount the
5062 file system, or ask S3QL to flush the cache and metadata using
5065 <p
><blockquote
><pre
>
5066 # s3qlctrl upload-meta /s3ql
5067 # s3qlctrl flushcache /s3ql
5069 </pre
></blockquote
></p
>
5071 <p
>If you are curious about how much space your data uses in the
5072 cloud, and how much compression and deduplication cut down on the
5073 storage usage, you can use s3qlstat on the mounted file system to get
5076 <p
><blockquote
><pre
>
5078 Directory entries:
9141
5081 Total data size:
22049.38 MB
5082 After de-duplication:
21955.46 MB (
99.57% of total)
5083 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
5084 Database size:
2.39 MB (uncompressed)
5085 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5087 </pre
></blockquote
></p
>
5089 <p
>I mentioned earlier that there are several possible suppliers of
5090 storage. I did not try to locate them all, but am aware of at least
5091 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
5092 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
5093 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
5094 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
5095 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
5096 accept payment in Bitcoin. Pick one that suit your need. Some of
5097 them provide several GiB of free storage, but the prize models are
5098 quite different and you will have to figure out what suits you
5101 <p
>While researching this blog post, I had a look at research papers
5102 and posters discussing the S3QL file system. There are several, which
5103 told me that the file system is getting a critical check by the
5104 science community and increased my confidence in using it. One nice
5106 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
5107 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5108 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
5109 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5110 and Pamela Smith. Please have a look.
</p
>
5112 <p
>Given my problems with different file systems earlier, I decided to
5113 check out the mounted S3QL file system to see if it would be usable as
5114 a home directory (in other word, that it provided POSIX semantics when
5115 it come to locking and umask handling etc). Running
5116 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
5117 test code to check file system semantics
</a
>, I was happy to discover that
5118 no error was found. So the file system can be used for home
5119 directories, if one chooses to do so.
</p
>
5121 <p
>If you do not want a locally file system, and want something that
5122 work without the Linux fuse file system, I would like to mention the
5123 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
5124 provide locally encrypted backup using a command line client. It have
5125 a nicer access control system, where one can split out read and write
5126 access, allowing some systems to write to the backup and others to
5127 only read from it.
</p
>
5129 <p
>As usual, if you use Bitcoin and want to show your support of my
5130 activities, please send Bitcoin donations to my address
5131 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5136 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
5137 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
5138 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
5139 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
5140 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
5141 project
</a
> is working on providing the software and hardware for
5142 making it easy for non-technical people to host their data and
5143 communication at home, and being able to communicate with their
5144 friends and family encrypted and away from prying eyes. It has been
5145 going on for a while, and is slowly progressing towards a new test
5146 release (
0.2).
</p
>
5148 <p
>And what day could be better than the Pi day to announce that the
5149 new version will provide
"hard drive
" / SD card / USB stick images for
5150 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5151 system), and can also be installed using a Debian installer preseed
5152 file. The Debian based Freedombox is now based on Debian Jessie,
5153 where most of the needed packages used are already present. Only one,
5154 the freedombox-setup package, is missing. To try to build your own
5155 boot image to test the current status, fetch the freedom-maker scripts
5157 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
5158 with a user with sudo access to become root:
5161 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5163 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5164 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5166 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5169 <p
>Root access is needed to run debootstrap and mount loopback
5170 devices. See the README for more details on the build. If you do not
5171 want all three images, trim the make line. But note that thanks to
<a
5172 href=
"https://bugs.debian.org/
741407">a race condition in
5173 vmdebootstrap
</a
>, the build might fail without the patch to the
5174 kpartx call.
</p
>
5176 <p
>If you instead want to install using a Debian CD and the preseed
5177 method, boot a Debian Wheezy ISO and use this boot argument to load
5178 the preseed values:
</p
>
5181 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
5184 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
5185 recently introduced bug in apt in Jessie
</a
>, the installer will
5186 currently hang while setting up APT sources. Killing the
5187 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
5188 installation will get the installation going. This affect all
5189 installations in Jessie, and I expect it will be fixed soon.
</p
>
5191 <p
>Give it a go and let us know how it goes on the mailing list, and help
5192 us get the new release published. :) Please join us on
5193 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
5194 irc.debian.org)
</a
> and
5195 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5196 mailing list
</a
> if you want to help make this vision come true.
</p
>
5201 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
5202 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
5203 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
5204 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
5205 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
5206 innetgr tools, because I needed them in
5207 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
5208 ng-utils, and it has served me well. I placed the project under the
5209 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
5210 repository. But many years ago, the CVS repository was dropped (lost,
5211 not migrated to new hardware, not sure), and the project have lacked a
5212 proper home since then.
</p
>
5214 <p
>Last summer, I had a look at the package and made a new release
5215 fixing a irritating crash bug, but was unable to store the changes in
5216 a proper source control system. I applied for a project on
5217 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
5218 to follow up on it. Until today. :)
</p
>
5220 <p
>After many hours of cleaning and migration, the ng-utils project
5221 now have a new home, and a git repository with the highlight of the
5222 history of the project. I published all release tarballs and imported
5223 them into the git repository. As the project is really stable and not
5224 expected to gain new features any time soon, I decided to make a new
5225 release and call it
1.0. Visit the new project home on
5226 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
5227 if you want to check it out. The new version is also uploaded into
5228 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
5233 <title>Testing sysvinit from experimental in Debian Hurd
</title>
5234 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
5235 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
5236 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
5237 <description><p
>A few days ago I decided to try to help the Hurd people to get
5238 their changes into sysvinit, to allow them to use the normal sysvinit
5239 boot system instead of their old one. This follow up on the
5240 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
5241 Google Summer of Code work
</a
> done last summer by Justus Winter to
5242 get Debian on Hurd working more like Debian on Linux. To get started,
5243 I downloaded a prebuilt hard disk image from
5244 <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
>,
5245 and started it using virt-manager.
</p
>
5247 <p
>The first think I had to do after logging in (root without any
5248 password) was to get the network operational. I followed
5249 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
5250 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
5251 commands as root to get the machine to accept a IP address from the
5252 kvm internal DHCP server:
</p
>
5254 <p
><blockquote
><pre
>
5255 settrans -fgap /dev/netdde /hurd/netdde
5256 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
5257 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
5259 </pre
></blockquote
></p
>
5261 <p
>After this, the machine had internet connectivity, and I could
5262 upgrade it and install the sysvinit packages from experimental and
5263 enable it as the default boot system in Hurd.
</p
>
5265 <p
>But before I did that, I set a password on the root user, as ssh is
5266 running on the machine it for ssh login to work a password need to be
5267 set. Also, note that a bug somewhere in openssh on Hurd block
5268 compression from working. Remember to turn that off on the client
5271 <p
>Run these commands as root to upgrade and test the new sysvinit
5274 <p
><blockquote
><pre
>
5275 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
5276 deb http://http.debian.net/debian/ experimental main
5279 apt-get dist-upgrade
5280 apt-get install -t experimental initscripts sysv-rc sysvinit \
5281 sysvinit-core sysvinit-utils
5282 update-alternatives --config runsystem
5283 </pre
></blockquote
></p
>
5285 <p
>To reboot after switching boot system, you have to use
5286 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
5287 yet a sysvinit process able to receive the signals from the normal
5288 'reboot
' command. After switching to sysvinit as the boot system,
5289 upgrading every package and rebooting, the network come up with DHCP
5290 after boot as it should, and the settrans/pkill hack mentioned at the
5291 start is no longer needed. But for some strange reason, there are no
5292 longer any login prompt in the virtual console, so I logged in using
5295 <p
>Note that there are some race conditions in Hurd making the boot
5296 fail some times. No idea what the cause is, but hope the Hurd porters
5297 figure it out. At least Justus said on IRC (#debian-hurd on
5298 irc.debian.org) that they are aware of the problem. A way to reduce
5299 the impact is to upgrade to the Hurd packages built by Justus by
5300 adding this repository to the machine:
</p
>
5302 <p
><blockquote
><pre
>
5303 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
5304 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5306 </pre
></blockquote
></p
>
5308 <p
>At the moment the prebuilt virtual machine get some packages from
5309 http://ftp.debian-ports.org/debian, because some of the packages in
5310 unstable do not yet include the required patches that are lingering in
5311 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
5313 <p
><blockquote
><pre
>
5314 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
5315 i emacs - GNU Emacs editor (metapackage)
5316 i gdb - GNU Debugger
5317 i hurd-recommended - Miscellaneous translators
5318 i isc-dhcp-client - ISC DHCP client
5319 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5320 i libc-bin - Embedded GNU C Library: Binaries
5321 i libc-dev-bin - Embedded GNU C Library: Development binaries
5322 i libc0.3 - Embedded GNU C Library: Shared libraries
5323 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5324 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5325 i multiarch-support - Transitional package to ensure multiarch compatibilit
5326 i A x11-common - X Window System (X.Org) infrastructure
5327 i xorg - X.Org X Window System
5328 i A xserver-xorg - X.Org X server
5329 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5331 </pre
></blockquote
></p
>
5333 <p
>All in all, testing hurd has been an interesting experience. :)
5334 X.org did not work out of the box and I never took the time to follow
5335 the porters instructions to fix it. This time I was interested in the
5336 command line stuff.
<p
>
5341 <title>New chrpath release
0.16</title>
5342 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
5343 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
5344 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
5345 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
5346 find problems in C, C++ and Java code using static source code
5347 analysis. It can detect a lot of different problems, and is very
5348 useful to find memory and locking bugs in the error handling part of
5349 the source. The company behind it provide
5350 <a href=
"https://scan.coverity.com/
">check of free software projects as
5351 a community service
</a
>, and many hundred free software projects are
5352 already checked. A few days ago I decided to have a closer look at
5353 the Coverity system, and discovered that the
5354 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
5355 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
5356 projects I am involved with was already registered. But these are
5357 fairly big, and I would also like to have a small and easy project to
5358 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
5359 checking of the chrpath project
</a
>. It was
5360 added to the checker and discovered seven potential defects. Six of
5361 these were real, mostly resource
"leak
" when the program detected an
5362 error. Nothing serious, as the resources would be released a fraction
5363 of a second later when the program exited because of the error, but it
5364 is nice to do it right in case the source of the program some time in
5365 the future end up in a library. Having fixed all defects and added
5366 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
5367 mailing list for the chrpath developers
</a
>, I decided it was time to
5368 publish a new release. These are the release notes:
</p
>
5370 <p
>New in
0.16 released
2014-
01-
14:
</p
>
5374 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
5375 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
5376 <li
>Mention new project mailing list in the documentation.
</li
>
5381 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5382 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
5383 project if something is wrong with the new release. The test suite
5384 did not discover any old errors, so if you find a new one, please also
5385 include a test suite check.
</p
>
5390 <title>New chrpath release
0.15</title>
5391 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
5392 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
5393 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
5394 <description><p
>After many years break from the package and a vain hope that
5395 development would be continued by someone else, I finally pulled my
5396 acts together this morning and wrapped up a new release of chrpath,
5397 the command line tool to modify the rpath and runpath of already
5398 compiled ELF programs. The update was triggered by the persistence of
5399 Isha Vishnoi at IBM, which needed a new config.guess file to get
5400 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
5401 is working on. I checked the
5402 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
5403 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
5404 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
5405 packages for interesting patches (failed to find the source from
5406 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5407 These are the release notes:
</p
>
5409 <p
>New in
0.15 released
2013-
11-
24:
</p
>
5413 <li
>Updated config.sub and config.guess from the GNU project to work
5414 with newer architectures. Thanks to isha vishnoi for the heads
5417 <li
>Updated README with current URLs.
</li
>
5419 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5420 Matthias Klose.
</li
>
5422 <li
>Added missing help for -k|--keepgoing option, using patch by
5423 Petr Machata found in Fedora.
</li
>
5425 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
5426 .dynamic is a NULL terminated string. Based on patch found in
5427 Fedora credited Axel Thimm and Christian Krause.
</li
>
5432 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5433 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
5434 project if something is wrong with the new release. The test suite
5435 did not discover any old errors, so if you find a new one, please also
5436 include a testsuite check.
</p
>
5441 <title>Debian init.d boot script example for rsyslog
</title>
5442 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
5443 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
5444 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
5445 <description><p
>If one of the points of switching to a new init system in Debian is
5446 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
5447 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
5448 init.d scripts at all. Here is an example init.d script, ie a rewrite
5449 of /etc/init.d/rsyslog:
</p
>
5451 <p
><pre
>
5452 #!/lib/init/init-d-script
5455 # Required-Start: $remote_fs $time
5456 # Required-Stop: umountnfs $time
5457 # X-Stop-After: sendsigs
5458 # Default-Start:
2 3 4 5
5459 # Default-Stop:
0 1 6
5460 # Short-Description: enhanced syslogd
5461 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5462 # It is quite compatible to stock sysklogd and can be
5463 # used as a drop-in replacement.
5465 DESC=
"enhanced syslogd
"
5466 DAEMON=/usr/sbin/rsyslogd
5467 </pre
></p
>
5469 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
5470 script was
137 lines, and the above is just
15 lines, most of it meta
5471 info/comments.
</p
>
5473 <p
>How to do this, you ask? Well, one create a new script
5474 /lib/init/init-d-script looking something like this:
5476 <p
><pre
>
5479 # Define LSB log_* functions.
5480 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
5481 # and status_of_proc is working.
5482 . /lib/lsb/init-functions
5485 # Function that starts the daemon/service
5491 #
0 if daemon has been started
5492 #
1 if daemon was already running
5493 #
2 if daemon could not be started
5494 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
5496 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5499 # Add code here, if necessary, that waits for the process to be ready
5500 # to handle requests from services started subsequently which depend
5501 # on this one. As a last resort, sleep for some time.
5505 # Function that stops the daemon/service
5510 #
0 if daemon has been stopped
5511 #
1 if daemon was already stopped
5512 #
2 if daemon could not be stopped
5513 # other if a failure occurred
5514 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
5515 RETVAL=
"$?
"
5516 [
"$RETVAL
" =
2 ]
&& return
2
5517 # Wait for children to finish too if this is a daemon that forks
5518 # and if the daemon is only ever run from this initscript.
5519 # If the above conditions are not satisfied then add some other code
5520 # that waits for the process to drop all resources that could be
5521 # needed by services started subsequently. A last resort is to
5522 # sleep for some time.
5523 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
5524 [
"$?
" =
2 ]
&& return
2
5525 # Many daemons don
't delete their pidfiles when they exit.
5527 return
"$RETVAL
"
5531 # Function that sends a SIGHUP to the daemon/service
5535 # If the daemon can reload its configuration without
5536 # restarting (for example, when it is sent a SIGHUP),
5537 # then implement that here.
5539 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
5544 scriptbasename=
"$(basename $
1)
"
5545 echo
"SN: $scriptbasename
"
5546 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
5547 script=
"$
1"
5554 NAME=$(basename $DAEMON)
5555 PIDFILE=/var/run/$NAME.pid
5557 # Exit if the package is not installed
5558 #[ -x
"$DAEMON
" ] || exit
0
5560 # Read configuration variable file if it is present
5561 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
5563 # Load the VERBOSE setting and other rcS variables
5566 case
"$
1" in
5568 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
5570 case
"$?
" in
5571 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5572 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5576 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
5578 case
"$?
" in
5579 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5580 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5584 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5586 #reload|force-reload)
5588 # If do_reload() is not implemented then leave this commented out
5589 # and leave
'force-reload
' as an alias for
'restart
'.
5591 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5595 restart|force-reload)
5597 # If the
"reload
" option is implemented then remove the
5598 #
'force-reload
' alias
5600 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5602 case
"$?
" in
5605 case
"$?
" in
5607 1) log_end_msg
1 ;; # Old process is still running
5608 *) log_end_msg
1 ;; # Failed to start
5618 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5624 </pre
></p
>
5626 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5627 lot. I did not really polish the approach, so it might not always
5628 work out of the box, but you get the idea. I did not try very hard to
5629 optimize it nor make it more robust either.
</p
>
5631 <p
>A better argument for switching init system in Debian than reducing
5632 the size of init scripts (which is a good thing to do anyway), is to
5633 get boot system that is able to handle the kernel events sensibly and
5634 robustly, and do not depend on the boot to run sequentially. The boot
5635 and the kernel have not behaved sequentially in years.
</p
>
5640 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5641 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5642 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5643 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5644 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5645 remote display access is the preferred solution with oVirt and RedHat
5646 Enterprise Virtualization, and I was sad to discover the other day
5647 that the browser plugin needed to use these systems seamlessly was
5648 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5649 for a package
</a
> was from
2012-
04-
10 with no progress since
5650 2013-
04-
01, so I decided to wrap up a package based on the great work
5651 from Cajus Pollmeier and put it in a collab-maint maintained git
5652 repository to get a package I could use. I would very much like
5653 others to help me maintain the package (or just take over, I do not
5654 mind), but as no-one had volunteered so far, I just uploaded it to
5655 NEW. I hope it will be available in Debian in a few days.
</p
>
5657 <p
>The source is now available from
5658 <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
>
5663 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5664 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5665 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5666 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5667 <description><p
>The
5668 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5669 program is a a very nice system to create virtual machine images. It
5670 create a image file, add a partition table, mount it and run
5671 debootstrap in the mounted directory to create a Debian system on a
5672 stick. Yesterday, I decided to try to teach it how to make images for
5673 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5674 of a plan to simplify the build system for
5675 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5676 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5677 the virtualbox images, but its current build system made multistrap
5678 based system for Dreamplug images, and it is lacking support for
5679 Raspberry Pi.
</p
>
5681 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5682 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5683 code and adjusted it to be able to build armel images on my amd64
5684 Debian laptop. I ended up giving vmdebootstrap five new options,
5685 allowing me to replicate the image creation process I use to make
5686 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5687 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5688 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5689 call debootstrap with --foreign and to copy the handler into the
5690 generated chroot before running the second stage. This allow
5691 vmdebootstrap to create armel images on an amd64 host. Next I added
5692 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5693 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5694 given file system type, allowing me to create an image with a vfat
5695 partition for the /boot/ stuff. I also added a
<tt
>--variant
5696 variant
</tt
> option to allow me to create smaller images without the
5697 Debian base system packages installed. Finally, I added an option
5698 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5699 as a boot loader. It is not needed on the Raspberry Pi and probably
5700 most other non-x86 architectures. The changes were accepted by the
5701 upstream author of vmdebootstrap yesterday and today, and is now
5703 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5704 upstream project page
</a
>.
</p
>
5706 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5707 create a small script (the customize script) to add the non-free
5708 binary blob needed to boot the Raspberry Pi and the APT source
5711 <p
><pre
>
5713 set -e # Exit on first error
5714 rootdir=
"$
1"
5715 cd
"$rootdir
"
5716 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5717 deb http://http.debian.net/debian/ jessie main contrib non-free
5719 # Install non-free binary blob needed to boot Raspberry Pi. This
5720 # install a kernel somewhere too.
5721 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5722 -O $rootdir/usr/bin/rpi-update
5723 chmod a+x $rootdir/usr/bin/rpi-update
5724 mkdir -p $rootdir/lib/modules
5725 touch $rootdir/boot/start.elf
5726 chroot $rootdir rpi-update
5727 </pre
></p
>
5729 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5730 to build the image:
</p
>
5733 sudo ./vmdebootstrap \
5736 --distribution jessie \
5737 --mirror http://http.debian.net/debian \
5746 --root-password raspberry \
5747 --hostname raspberrypi \
5748 --foreign /usr/bin/qemu-arm-static \
5749 --customize `pwd`/customize \
5751 --package git-core \
5752 --package binutils \
5753 --package ca-certificates \
5756 </pre
></p
>
5758 <p
>The list of packages being installed are the ones needed by
5759 rpi-update to make the image bootable on the Raspberry Pi, with the
5760 exception of netbase, which is needed by debootstrap to find
5761 /etc/hosts with the minbase variant. I really wish there was a way to
5762 set up an Raspberry Pi using only packages in the Debian archive, but
5763 that is not possible as far as I know, because it boots from the GPU
5764 using a non-free binary blob.
</p
>
5766 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5767 probably a few others installed. I have not checked the complete
5768 build dependency list.
</p
>
5770 <p
>The resulting image will not use the hardware floating point unit
5771 on the Raspberry PI, because the armel architecture in Debian is not
5772 optimized for that use. So the images created will be a bit slower
5773 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5778 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5779 <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>
5780 <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>
5781 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5782 <description><p
>The last few days I came across a few good causes that should get
5783 wider attention. I recommend signing and donating to each one of
5786 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5787 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5788 Women program which is a Google Summer of Code like initiative to get
5789 more women involved in free software. One debian sponsor has offered
5790 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5791 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5792 hope you will to. :)
</p
>
5794 <p
>And the Electronic Frontier Foundation just announced plans to
5795 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5796 documentaries about the excessive spying
</a
> on every Internet user that
5797 take place these days, and their need to fund the work. I
've already
5798 donated. Are you next?
</p
>
5800 <p
>For my Norwegian audience, the organisation Studentenes og
5801 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5802 statement under the heading
5803 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5804 Access
</a
> for those of us asking for more focus on open access in the
5805 Norwegian government. So far
499 signatures. I hope you will sign it
5811 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5812 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5813 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5814 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5815 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
5816 project
</a
> have been going on for a while, and have presented the
5817 vision, ideas and solution several places. Here is a little
5818 collection of videos of talks and presentation of the project.
</p
>
5822 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
5823 2,
5 minute marketing film
</a
> (Youtube)
</li
>
5825 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
5826 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
5828 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
5829 Freedom in the Cloud - Software Freedom, Privacy and and Security for
5830 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
5831 (Youtube)
</li
>
5833 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
5834 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
5836 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
5837 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
5839 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
5840 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
5841 York City in
2012</a
> (Youtube)
</li
>
5843 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
5844 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
5845 (Youtube)
</li
>
5847 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
5848 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
5850 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
5851 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
5853 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
5854 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
5855 2013</a
> (Youtube)
</li
>
5859 <p
>A larger list is available from
5860 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
5861 Freedombox Wiki
</a
>.
</p
>
5863 <p
>On other news, I am happy to report that Freedombox based on Debian
5864 Jessie is coming along quite well, and soon both Owncloud and using
5865 Tor should be available for testers of the Freedombox solution. :) In
5866 a few weeks I hope everything needed to test it is included in Debian.
5867 The withsqlite package is already in Debian, and the plinth package is
5868 pending in NEW. The third and vital part of that puzzle is the
5869 metapackage/setup framework, which is still pending an upload. Join
5870 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
5871 (#freedombox on irc.debian.org)
</a
> and
5872 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5873 mailing list
</a
> if you want to help make this vision come true.
</p
>
5878 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
5879 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
5880 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
5881 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
5882 <description><p
>I was introduced to the
5883 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
5884 in
2010, when Eben Moglen presented his vision about serving the need
5885 of non-technical people to keep their personal information private and
5886 within the legal protection of their own homes. The idea is to give
5887 people back the power over their network and machines, and return
5888 Internet back to its intended peer-to-peer architecture. Instead of
5889 depending on a central service, the Freedombox will give everyone
5890 control over their own basic infrastructure.
</p
>
5892 <p
>I
've intended to join the effort since then, but other tasks have
5893 taken priority. But this summers nasty news about the misuse of trust
5894 and privilege exercised by the
"western
" intelligence gathering
5895 communities increased my eagerness to contribute to a point where I
5896 actually started working on the project a while back.
</p
>
5898 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
5899 Debian initiative
</a
> based on the vision from Eben Moglen, is to
5900 create a simple and cheap Debian based appliance that anyone can hook
5901 up in their home and get access to secure and private services and
5902 communication. The initial deployment platform have been the
5903 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
5904 which is a piece of hardware I do not own. So to be able to test what
5905 the current Freedombox setup look like, I had to come up with a way to install
5906 it on some hardware I do have access to. I have rewritten the
5907 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
5908 image build framework to use .deb packages instead of only copying
5909 setup into the boot images, and thanks to this rewrite I am able to
5910 set up any machine supported by Debian Wheezy as a Freedombox, using
5911 the previously mentioned deb (and a few support debs for packages
5912 missing in Debian).
</p
>
5914 <p
>The current Freedombox setup consist of a set of bootstrapping
5916 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
5917 and a administrative web interface
5918 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
5919 withsqlite), as well as a privacy enhancing proxy based on
5920 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
5921 (freedombox-privoxy). There is also a web/javascript based XMPP
5922 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
5923 trying (unsuccessfully so far) to talk to the XMPP server
5924 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
5925 web interface is pluggable, and the goal is to use it to enable OpenID
5926 services, mesh network connectivity, use of TOR, etc, etc. Not much of
5927 this is really working yet, see
5928 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
5929 project TODO
</a
> for links to GIT repositories. Most of the code is
5930 on github at the moment. The HTTP proxy is operational out of the
5931 box, and the admin web interface can be used to add/remove plinth
5932 users. I
've not been able to do anything else with it so far, but
5933 know there are several branches spread around github and other places
5934 with lots of half baked features.
</p
>
5936 <p
>Anyway, if you want to have a look at the current state, the
5937 following recipes should work to give you a test machine to poke
5940 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
5944 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
5945 <li
>Boot from it, either as CD or USB stick.
</li
>
5946 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
5947 to the Debian installer:
<p
>
5948 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
5950 <li
>Answer the few language/region/password questions and pick disk to
5951 install on.
</li
>
5953 <li
>When the installation is finished and the machine have rebooted a
5954 few times, your Freedombox is ready for testing.
</li
>
5958 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
5962 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
5963 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
5964 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
5966 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
5967 </pre
></li
>
5968 <li
><p
>Run this as root:
</p
>
5970 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
5973 apt-get install freedombox-setup
5974 /usr/lib/freedombox/setup
5975 </pre
></li
>
5976 <li
>Reboot into your freshly created Freedombox.
</li
>
5980 <p
>You can test it on other architectures too, but because the
5981 freedombox-privoxy package is binary, it will only work as intended on
5982 the architectures where I have had time to build the binary and put it
5983 in my APT repository. But do not let this stop you. It is only a
5984 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
5986 <p
>Note that by default Freedombox is a DHCP server on the
5987 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
5988 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
5989 disable
</tt
>" as root.
</p
>
5991 <p
>Please let me know if this works for you, or if you have any
5992 problems. We gather on the IRC channel
5993 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
5994 irc.debian.org and the
5995 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
5996 mailing list
</a
>.
</p
>
5998 <p
>Once you get your freedombox operational, you can visit
5999 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
6000 welcome screen (dead end - do not be surprised if you are unable to
6001 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
6002 to look at the rest of plinth. The default user is
'admin
' and the
6003 default password is
'secret
'.
</p
>
6008 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
6009 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
6010 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
6011 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
6012 <description><p
>Earlier, I reported about
6013 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
6014 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
6015 told by IBM that the original disk should be thrown away. And as
6016 there no longer was a problem if I bricked the firmware, I decided
6017 today to try to install Intel firmware to replace the Lenovo firmware
6018 currently on the disk.
</p
>
6020 <p
>I searched the Intel site for firmware, and found
6021 <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
>
6022 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6023 according to the site should contain the latest firmware for SSD
6024 disks. I inserted the broken disk in one of my spare laptops and
6025 booted the ISO from a USB stick. The disk was recognized, but the
6026 program claimed the newest firmware already were installed and refused
6027 to insert any Intel firmware. So no change, and the disk is still
6028 unable to handle write load. :( I guess the only way to get them
6029 working would be if Lenovo releases new firmware. No idea how likely
6030 that is. Anyway, just blogging about this test for completeness. I
6031 got a working Samsung disk, and see no point in spending more time on
6032 the broken disks.
</p
>
6037 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
6038 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
6039 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
6040 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
6041 <description><p
>Today I switched to
6042 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
6043 new laptop
</a
>. I
've previously written about the problems I had with
6044 my new Thinkpad X230, which was delivered with an
6045 <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
6046 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
6047 sustained writes. My hardware supplier have been very forthcoming in
6048 trying to find a solution, and after first trying with another
6049 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
6050 disk instead to fix it once and for all. The Samsung disk survived
6051 the installation of Debian with encrypted disks (filling the disk with
6052 random data during installation killed the first two), and I thus
6053 decided to trust it with my data. I have installed it as a Debian Edu
6054 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6055 server at home using Kerberos and LDAP, and will use it as my work
6056 station from now on.
</p
>
6058 <p
>As this is a solid state disk with no moving parts, I believe the
6059 Debian Wheezy default installation need to be tuned a bit to increase
6060 performance and increase life time of the disk. The Linux kernel and
6061 user space applications do not yet adjust automatically to such
6062 environment. To make it easier for my self, I created a draft Debian
6063 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
6064 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
6065 for the ssd-setup package
</a
> is available from collab-maint, and it
6066 is set up to adjust the setup of the machine by just installing the
6067 package. If there is any non-SSD disk in the machine, the package
6068 will refuse to install, as I did not try to write any logic to sort
6069 file systems in SSD and non-SSD file systems.
</p
>
6071 <p
>I consider the package a draft, as I am a bit unsure how to best
6072 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6073 where I set up the machine with one large encrypted partition (in
6074 addition to /boot), put LVM on top of this and set up partitions on
6075 top of this again. See the README file in the package source for the
6076 references I used to pick the settings. At the moment these
6077 parameters are tuned:
</p
>
6081 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
6082 (adding discard to /etc/crypttab)
</li
>
6084 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
6085 this case a cryptsetup partition) by changing issue_discards from
6086 0 to
1 in /etc/lvm/lvm.conf.
</li
>
6088 <li
>Set relatime as a file system option for ext3 and ext4 file
6091 <li
>Tell swap to use TRIM commands by adding
'discard
' to
6092 /etc/fstab.
</li
>
6094 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
6096 <li
>Run fstrim on every ext3 and ext4 file system every night (from
6097 cron.daily).
</li
>
6099 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
6100 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
6104 <p
>During installation, I cancelled the part where the installer fill
6105 the disk with random data, as this would kill the SSD performance for
6106 little gain. My goal with the encrypted file system is to ensure
6107 those stealing my laptop end up with a brick and not a working
6108 computer. I have no hope in keeping the really resourceful people
6109 from getting the data on the disk (see
6110 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
6111 Thus I concluded that adding the discard option to crypttab is the
6112 right thing to do.
</p
>
6114 <p
>I considered using the noop I/O scheduler, as several recommended
6115 it for SSD, but others recommended deadline and a benchmark I found
6116 indicated that deadline might be better for interactive use.
</p
>
6118 <p
>I also considered using the
'discard
' file system option for ext3
6119 and ext4, but read that it would give a performance hit ever time a
6120 file is removed, and thought it best to that that slowdown once a day
6121 instead of during my work.
</p
>
6123 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6124 this is already done by Debian Edu.
</p
>
6126 <p
>I have not yet started on the user space tuning. I expect
6127 iceweasel need some tuning, and perhaps other applications too, but
6128 have not yet had time to investigate those parts.
</p
>
6130 <p
>The package should work on Ubuntu too, but I have not yet tested it
6133 <p
>As for the answer to the question in the title of this blog post,
6134 as far as I know, the only solution I know about is to replace the
6135 disk. It might be possible to flash it with Intel firmware instead of
6136 the Lenovo firmware. But I have not tried and did not want to do so
6137 without approval from Lenovo as I wanted to keep the warranty on the
6138 disk until a solution was found and they wanted the broken disks
6144 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
6145 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
6146 <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>
6147 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
6148 <description><p
>A few days ago, I wrote about
6149 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
6150 problems I experienced with my new X230 and its SSD disk
</a
>, which
6151 was dying during installation because it is unable to cope with
6152 sustained write. My supplier is in contact with
6153 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
6154 replacement disk to try to fix the problem. They decided to send an
6155 identical model, so my hopes for a permanent fix was slim.
</p
>
6157 <p
>Anyway, today I got the replacement disk and tried to install
6158 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6159 same firmware version as the original. This time my hope raised
6160 slightly as the installation progressed, as the original disk used to
6161 die after
4-
7% of the disk was written to, while this time it kept
6162 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
6163 died again and I was back on square one. I still do not have a new
6164 laptop with a disk I can trust. I can not live with a disk that might
6165 lock up when I download a new
6166 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
6167 other large files. I look forward to hearing from my supplier with
6168 the next proposal from Lenovo.
</p
>
6170 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
6171 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6172 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
6173 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
6174 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6175 P/N
45N8295, P0C38732.
</p
>
6177 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
6178 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
6179 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
6180 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
6181 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6182 P/N
45N8295, P0C38732.
</p
>
6184 <p
>The only difference is in the first number (serial number?), ISN,
6185 SA, date and WNPP values. Mentioning all the details here in case
6186 someone is able to use the information to find a way to identify the
6187 failing disk among working ones (if any such working disk actually
6193 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
6194 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
6195 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
6196 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
6197 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
6198 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6199 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
6200 member assosiation NUUG
</a
> and
6201 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
6202 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
6203 Bitraf
</a
>.
</p
>
6205 <p
>It starts
10:
00 and continue until late evening. Everyone is
6206 welcome, and there is no fee to participate. There is on the other
6207 hand limited space, and only room for
30 people. Please put your name
6208 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
6209 wiki page
</a
> if you plan to join us.
</p
>
6214 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
6215 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
6216 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
6217 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
6218 <description><p
>Half a year ago, I reported that I had to find a
6219 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
6220 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
6221 time to spend on it, and it took a while to find a model I believe
6222 will do the job, but two days ago the replacement finally arrived. I
6224 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
6225 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6226 a roaming workstation, and it seemed to work flawlessly. But my
6227 second installation with encrypted disk was not as successful. More
6228 on that below.
</p
>
6230 <p
>I had a hard time trying to track down a good laptop, as my most
6231 important requirements (robust and with a good keyboard) are never
6232 listed in the feature list. But I did get good help from the search
6233 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6234 allowed me to limit the list of interesting laptops based on my other
6235 requirements. A bit surprising that SSD disk are not disks according
6236 to that search interface, so I had to drop specifying the number of
6237 disks from my search parameters. I also asked around among friends to
6238 get their impression on keyboards and robustness.
</p
>
6240 <p
>So the new laptop arrived, and it is quite a lot wider than the
6241 X41. I am not quite convinced about the keyboard, as it is
6242 significantly wider than my old keyboard, and I have to stretch my
6243 hand a lot more to reach the edges. But the key response is fairly
6244 good and the individual key shape is fairly easy to handle, so I hope
6245 I will get used to it. My old X40 was starting to fail, and I really
6246 needed a new laptop now. :)
</p
>
6248 <p
>Turning off the touch pad was simple. All it took was a quick
6249 visit to the BIOS during boot it disable it.
</p
>
6251 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
6252 lock up during load. And this happen when installing Debian Wheezy
6253 with encrypted disk, while the disk is being filled with random data.
6254 I also tested to install Ubuntu Raring, and it happen there too if I
6255 reenable the code to fill the disk with random data (it is disabled by
6256 default in Ubuntu). And the bug with is already known. It was
6257 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
6258 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
6259 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6260 kernel developers as
6261 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
6262 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
6263 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6264 Lenovo forums, both for
6265 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
6266 2012-
11-
10</a
> and for
6267 <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
6268 03-
20-
2013</a
>. The problem do not only affect installation. The
6269 reports state that the disk lock up during use if many writes are done
6270 on the disk, so it is much no use to work around the installation
6271 problem and end up with a computer that can lock up at any moment.
6273 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
6274 available
</a
> that will lock up the hard drive after running a few
6275 minutes by writing to a file.
</p
>
6277 <p
>I
've contacted my supplier and asked how to handle this, and after
6278 contacting PCHELP Norway (request
01D1FDP) which handle support
6279 requests for Lenovo, his first suggestion was to upgrade the disk
6280 firmware. Unfortunately there is no newer firmware available from
6281 Lenovo, as my disk already have the most recent one (version LF1i). I
6282 hope to hear more from him today and hope the problem can be
6288 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
6289 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
6290 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
6291 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
6292 <description><p
>Half a year ago, I reported that I had to find a replacement for my
6293 trusty old Thinkpad X41. Unfortunately I did not have much time to
6294 spend on it, but today the replacement finally arrived. I ended up
6295 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
6296 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
6297 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6298 this, it is installing what I hope will be a more final installation,
6299 with a encrypted hard drive to ensure any dope head stealing it end up
6300 with an expencive door stop.
</p
>
6302 <p
>I had a hard time trying to track down a good laptop, as my most
6303 important requirements (robust and with a good keyboard) are never
6304 listed in the feature list. But I did get good help from the search
6305 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6306 allowed me to limit the list of interesting laptops based on my other
6307 requirements. A bit surprising that SSD disk are not disks, so I had
6308 to drop number of disks from my search parameters.
</p
>
6310 <p
>I am not quite convinced about the keyboard, as it is significantly
6311 wider than my old keyboard, and I have to stretch my hand a lot more
6312 to reach the edges. But the key response is fairly good and the
6313 individual key shape is fairly easy to handle, so I hope I will get
6314 used to it. My old X40 was starting to fail, and I really needed a
6315 new laptop now. :)
</p
>
6317 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
6322 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
6323 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
6324 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
6325 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
6326 <description><p
>It annoys me when the computer fail to do automatically what it is
6327 perfectly capable of, and I have to do it manually to get things
6328 working. One such task is to find out what firmware packages are
6329 needed to get the hardware on my computer working. Most often this
6330 affect the wifi card, but some times it even affect the RAID
6331 controller or the ethernet card. Today I pushed version
0.4 of the
6332 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
6333 including a new script isenkram-autoinstall-firmware handling the
6334 process of asking all the loaded kernel modules what firmware files
6335 they want, find debian packages providing these files and install the
6336 debian packages. Here is a test run on my laptop:
</p
>
6338 <p
><pre
>
6339 # isenkram-autoinstall-firmware
6340 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6341 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6342 info: locating packages with the requested firmware files
6343 info: Updating APT sources after adding non-free APT source
6344 info: trying to install firmware-ipw2x00
6347 Preconfiguring packages ...
6348 Selecting previously deselected package firmware-ipw2x00.
6349 (Reading database ...
259727 files and directories currently installed.)
6350 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6351 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
6353 </pre
></p
>
6355 <p
>When all the requested firmware is present, a simple message is
6356 printed instead:
</p
>
6358 <p
><pre
>
6359 # isenkram-autoinstall-firmware
6360 info: did not find any firmware files requested by loaded kernel modules. exiting
6362 </pre
></p
>
6364 <p
>It could use some polish, but it is already working well and saving
6365 me some time when setting up new machines. :)
</p
>
6367 <p
>So, how does it work? It look at the set of currently loaded
6368 kernel modules, and look up each one of them using modinfo, to find
6369 the firmware files listed in the module meta-information. Next, it
6370 download the Contents file from a nearby APT mirror, and search for
6371 the firmware files in this file to locate the package with the
6372 requested firmware file. If the package is in the non-free section, a
6373 non-free APT source is added and the package is installed using
6374 <tt
>apt-get install
</tt
>. The end result is a slightly better working
6377 <p
>I hope someone find time to implement a more polished version of
6378 this script as part of the hw-detect debian-installer module, to
6379 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
6380 #
655507</a
>. There really is no need to insert USB sticks with
6381 firmware during a PXE install when the packages already are available
6382 from the nearby Debian mirror.
</p
>
6387 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
6388 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
6389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
6390 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
6391 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6392 the screen just turn black when Linux boot, either during installation
6393 or on first boot from the hard disk. I
've seen it once in a while the
6394 last few years, but only recently understood the cause. I
've seen it
6395 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6396 The reason seem to be in the wiring of some laptops. The system to
6397 control the screen background light is inverted, so when Linux try to
6398 turn the brightness fully on, it end up turning it off instead. I do
6399 not know which Linux drivers are affected, but this post is about the
6400 i915 driver used by the
6401 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6402 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
6404 <p
>The problem can be worked around two ways. Either by adding
6405 i915.invert_brightness=
1 as a kernel option, or by adding a file in
6406 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
6407 option when it load the i915 kernel module. On Debian and Ubuntu, it
6408 can be done by running these commands as root:
</p
>
6411 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
6412 update-initramfs -u -k all
6415 <p
>Since March
2012 there is
6416 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
6417 mechanism in the Linux kernel
</a
> to tell the i915 driver which
6418 hardware have this problem, and get the driver to invert the
6419 brightness setting automatically. To use it, one need to add a row in
6420 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
6421 intel_quirks array
</a
> in the driver source
6422 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
6423 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
6424 number (vendor number
8086 is assumed) and subdevice vendor and device
6427 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
6428 -vvnn
</tt
> for the video card in question:
</p
>
6430 <p
><pre
>
6431 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
6432 3rd Gen Core processor Graphics Controller [
8086:
0156] \
6433 (rev
09) (prog-if
00 [VGA controller])
6434 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
6435 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6436 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6437 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
6438 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
6440 Interrupt: pin A routed to IRQ
42
6441 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
6442 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
6443 Region
4: I/O ports at
4000 [size=
64]
6444 Expansion ROM at
<unassigned
> [disabled]
6445 Capabilities:
<access denied
>
6446 Kernel driver in use: i915
6447 </pre
></p
>
6449 <p
>The resulting intel_quirks entry would then look like this:
</p
>
6451 <p
><pre
>
6452 struct intel_quirk intel_quirks[] = {
6454 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6455 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
6458 </pre
></p
>
6460 <p
>According to the kernel module instructions (as seen using
6461 <tt
>modinfo i915
</tt
>), information about hardware needing the
6462 invert_brightness flag should be sent to the
6463 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
6464 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
6465 developers. But my email about the laptop sent
2013-
06-
03 have not
6467 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
6468 web archive for the mailing list
</a
>, so I suspect they do not accept
6469 emails from non-subscribers. Because of this, I sent my patch also to
6470 the Debian bug tracking system instead as
6471 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
6472 sure the patch is not lost.
</p
>
6474 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
6475 with this problem working properly with Linux. If you use Gnome, your
6476 worries should be over at this point. But if you use KDE, there is
6477 something in KDE ignoring the invert_brightness setting and turning on
6478 the screen during login. I
've reported it to Debian as
6479 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
6480 have no idea yet how to figure out exactly what subsystem is doing
6481 this. Perhaps you can help? Perhaps you know what the Gnome
6482 developers did to handle this, and this can give a clue to the KDE
6483 developers? Or you know where in KDE the screen brightness is changed
6484 during login? If so, please update the BTS report (or get in touch if
6485 you do not know how to update BTS).
</p
>
6487 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
6488 acpi_backlight=vendor, to disable ACPI backlight support completely,
6489 as the ACPI information on the machine is trash and it is better to
6490 leave it to the intel video driver to control the screen
6491 backlight.
</p
>
6496 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
6497 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
6498 <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>
6499 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
6500 <description><p
>Two days ago, I asked
6501 <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
6502 I could install Linux on a Packard Bell EasyNote LV computer
6503 preinstalled with Windows
8</a
>. I found a solution, but am horrified
6504 with the obstacles put in the way of Linux users on a laptop with UEFI
6505 and Windows
8.
</p
>
6507 <p
>I never found out if the cause of my problems were the use of UEFI
6508 secure booting or fast boot. I suspect fast boot was the problem,
6509 causing the firmware to boot directly from HD without considering any
6510 key presses and alternative devices, but do not know UEFI settings
6511 enough to tell.
</p
>
6513 <p
>There is no way to install Linux on the machine in question without
6514 opening the box and disconnecting the hard drive! This is as far as I
6515 can tell, the only way to get access to the firmware setup menu
6516 without accepting the Windows
8 license agreement. I am told (and
6517 found description on how to) that it is possible to configure the
6518 firmware setup once booted into Windows
8. But as I believe the terms
6519 of that agreement are completely unacceptable, accepting the license
6520 was never an alternative. I do not enter agreements I do not intend
6521 to follow.
</p
>
6523 <p
>I feared I had to return the laptops and ask for a refund, and
6524 waste many hours on this, but luckily there was a way to get it to
6525 work. But I would not recommend it to anyone planning to run Linux on
6526 it, and I have become sceptical to Windows
8 certified laptops. Is
6527 this the way Linux will be forced out of the market place, by making
6528 it close to impossible for
"normal
" users to install Linux without
6529 accepting the Microsoft Windows license terms? Or at least not
6530 without risking to loose the warranty?
</p
>
6532 <p
>I
've updated the
6533 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
6534 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
6535 do not have to struggle as much as I did to get Linux into the
6538 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6539 Michael Tokarev and others for feedback and ideas.
</p
>
6544 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
6545 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
6546 <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>
6547 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
6548 <description><p
>I
've run into quite a problem the last few days. I bought three
6549 new laptops for my parents and a few others. I bought Packard Bell
6550 Easynote LV to run Kubuntu on and use as their home computer. But I
6551 am completely unable to figure out how to install Linux on it. The
6552 computer is preinstalled with Windows
8, and I suspect it uses UEFI
6553 instead of a BIOS to boot.
</p
>
6555 <p
>The problem is that I am unable to get it to PXE boot, and unable
6556 to get it to boot the Linux installer from my USB stick. I have yet
6557 to try the DVD install, and still hope it will work. when I turn on
6558 the computer, there is no information on what buttons to press to get
6559 the normal boot menu. I expect to get some boot menu to select PXE or
6560 USB stick booting. When booting, it first ask for the language to
6561 use, then for some regional settings, and finally if I will accept the
6562 Windows
8 terms of use. As these terms are completely unacceptable to
6563 me, I have no other choice but to turn off the computer and try again
6564 to get it to boot the Linux installer.
</p
>
6566 <p
>I have gathered my findings so far on a Linlap page about the
6567 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6568 EasyNote LV
</a
> model. If you have any idea how to get Linux
6569 installed on this machine, please get in touch or update that wiki
6570 page. If I can
't find a way to install Linux, I will have to return
6571 the laptop to the seller and find another machine for my parents.
</p
>
6573 <p
>I wonder, is this the way Linux will be forced out of the market
6574 using UEFI and
"secure boot
" by making it impossible to install Linux
6575 on new Laptops?
</p
>
6580 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6581 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6582 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6583 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6584 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6585 an operating system based on Debian intended for use in schools. It
6586 contain a turn-key solution for the computer network provided to
6587 pupils in the primary schools. It provide both the central server,
6588 network boot servers and desktop environments with heaps of
6589 educational software. The project was founded almost
12 years ago,
6590 2001-
07-
02. If you want to support the project, which is in need for
6591 cash to fund developer gatherings and other project related activity,
6592 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6593 donate some money
</a
>.
6595 <p
>A topic that come up again and again on the Debian Edu mailing
6596 lists and elsewhere, is the question on how to transform a Debian or
6597 Ubuntu installation into a Debian Edu installation. It isn
't very
6598 hard, and last week I wrote a script to replicate the steps done by
6599 the Debian Edu installer.
</p
>
6601 <p
>The script,
6602 <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/
>
6603 in the debian-edu-config package, will go through these six steps and
6604 transform an existing Debian Wheezy or Ubuntu (untested) installation
6605 into a Debian Edu Workstation:
</p
>
6609 <li
>Add skolelinux related APT sources.
</li
>
6610 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6611 <li
>Install debian-edu-install to load preseeding values and pull in
6612 our configuration.
</li
>
6613 <li
>Preseed debconf database with profile setup in
6614 /etc/debian-edu/config, and run tasksel to install packages
6615 according to the profile specified in the config above,
6616 overriding some of the Debian automation machinery.
</li
>
6617 <li
>Run debian-edu-cfengine-D installation to configure everything
6618 that could not be done using preseeding.
</li
>
6619 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6623 <p
>There are some steps in the Debian Edu installation that can not be
6624 replicated like this. Disk partitioning and LVM setup, for example.
6625 So this script just assume there is enough disk space to install all
6626 the needed packages.
</p
>
6628 <p
>The script was created to help a Debian Edu student working on
6629 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6630 Debian Edu client, and using it he can take the existing
6631 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6632 transform it into a fully functioning Debian Edu Workstation (or
6633 Roaming Workstation, or whatever :).
</p
>
6635 <p
>The default setting in the script is to create a KDE Workstation.
6636 If a LXDE based Roaming workstation is wanted instead, modify the
6637 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6639 <p
><pre
>
6640 PROFILE=
"Roaming-Workstation
"
6641 DESKTOP=
"lxde
"
6642 </pre
></p
>
6644 <p
>The script could even become useful to set up Debian Edu servers in
6645 the cloud, by starting with a virtual Debian installation at some
6646 virtual hosting service and setting up all the services on first
6652 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6653 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6654 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6655 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6656 <description><P
>In January,
6657 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6658 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6659 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6660 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6661 marvellous construction system from Denmark. We also created
6662 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6663 a place to take notes and write down our plans and hopes. And several
6664 people showed up to help. I was very happy to see the effect of my
6665 call. Since the small start, we have a debtags tag
6666 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6667 tag for LEGO related packages, and now count
10 packages related to
6668 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6670 <p
><table
>
6671 <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
>
6672 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6673 <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
>
6674 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6675 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6676 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6677 <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
>
6678 <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
>
6679 <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
>
6680 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6681 </table
></p
>
6683 <p
>Some of these are available in Wheezy, and all but one are
6684 currently available in Jessie/testing. leocad is so far only
6685 available in experimental.
</p
>
6687 <p
>If you care about LEGO in Debian, please join us on IRC and help
6688 adding the rest of the great free software tools available on Linux
6689 for LEGO designers.
</p
>
6694 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6695 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6696 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6697 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6698 <description><p
>When I woke up this morning, I was very happy to see that the
6699 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6700 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6701 Debian release, and I expect to move my machines at home over to it fairly
6704 <p
>The new debian release contain heaps of new stuff, and one program
6705 in particular make me very happy to see included. The
6706 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6707 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6708 included for the first time. Alongside similar programs like
6709 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6710 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6711 it allow for visual programming where syntax errors can not happen,
6712 and a friendly programming environment for learning to control the
6713 computer. Scratch will also be included in the next release of Debian
6716 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6717 Edu/Skolelinux release too. The
6718 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6719 alpha release
</a
> went out last week, and the next should soon
6725 <title>Isenkram
0.2 finally in the Debian archive
</title>
6726 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6727 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6728 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6729 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6730 package
</a
> finally made it into the archive, after lingering in NEW
6731 for many months. I uploaded it to the Debian experimental suite
6732 2013-
01-
27, and today it was accepted into the archive.
</p
>
6734 <p
>Isenkram is a system for suggesting to users what packages to
6735 install to work with a pluggable hardware device. The suggestion pop
6736 up when the device is plugged in. For example if a Lego Mindstorm NXT
6737 is inserted, it will suggest to install the program needed to program
6738 the NXT controller. Give it a go, and report bugs and suggestions to
6744 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6745 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6746 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6747 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6748 <description><p
>My
6749 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6750 bitcoin related blog post
</a
> mentioned that the new
6751 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6752 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6753 2013-
01-
19, and have been available in unstable since then. It was
6754 automatically copied to Ubuntu, and is available in their Raring
6755 version too.
</p
>
6757 <p
>But there is a strange problem with the build that block this new
6758 version from being available on the i386 and kfreebsd-i386
6759 architectures. For some strange reason, the autobuilders in Debian
6760 for these architectures fail to run the test suite on these
6761 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6762 We are so far unable to reproduce it when building it manually, and
6763 no-one have been able to propose a fix. If you got an idea what is
6764 failing, please let us know via the BTS.
</p
>
6766 <p
>One feature that is annoying me with of the bitcoin client, because
6767 I often run low on disk space, is the fact that the client will exit
6768 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6769 #
696715</a
>). So make sure you have enough disk space when you run
6772 <p
>As usual, if you use bitcoin and want to show your support of my
6773 activities, please send Bitcoin donations to my address
6774 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6779 <title>Welcome to the world, Isenkram!
</title>
6780 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6781 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6782 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6783 <description><p
>Yesterday, I
6784 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6785 for testers
</a
> for my prototype for making Debian better at handling
6786 pluggable hardware devices, which I
6787 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6788 out to create
</a
> earlier this month. Several valuable testers showed
6789 up, and caused me to really want to to open up the development to more
6790 people. But before I did this, I want to come up with a sensible name
6791 for this project. Today I finally decided on a new name, and I have
6792 renamed the project from hw-support-handler to this new name. In the
6793 process, I moved the source to git and made it available as a
6794 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6795 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6796 To fetch and build the latest version of the source, use
</p
>
6799 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6800 cd isenkram
&& git-buildpackage -us -uc
6803 <p
>I have not yet adjusted all files to use the new name yet. If you
6804 want to hack on the source or improve the package, please go ahead.
6805 But please talk to me first on IRC or via email before you do major
6806 changes, to make sure we do not step on each others toes. :)
</p
>
6808 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6809 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6810 stuff, in other words. I
've been told it is the Norwegian variant of
6811 the German word eisenkram, for those that are familiar with that
6814 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6815 instructions, to avoid confusing people with an error from the signing
6818 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
6819 clone argument to avoid the need for authentication.
</p
>
6824 <title>First prototype ready making hardware easier to use in Debian
</title>
6825 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
6826 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
6827 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
6828 <description><p
>Early this month I set out to try to
6829 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
6830 the Debian support for pluggable hardware devices
</a
>. Now my
6831 prototype is working, and it is ready for a larger audience. To test
6833 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
6834 from the Debian Edu subversion repository
</a
>, build and install the
6835 package. You might have to log out and in again activate the
6836 autostart script.
</p
>
6838 <p
>The design is simple:
</p
>
6842 <li
>Add desktop entry in /usr/share/autostart/ causing a program
6843 hw-support-handlerd to start when the user log in.
</li
>
6845 <li
>This program listen for kernel events about new hardware (directly
6846 from the kernel like udev does), not using HAL dbus events as I
6847 initially did.
</li
>
6849 <li
>When new hardware is inserted, look up the hardware modalias in
6850 the APT database, a database
6851 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
6852 via HTTP
</a
> and a database available as part of the package.
</li
>
6854 <li
>If a package is mapped to the hardware in question, the package
6855 isn
't installed yet and this is the first time the hardware was
6856 plugged in, show a desktop notification suggesting to install the
6857 package or packages.
</li
>
6859 <li
>If the user click on the
'install package now
' button, ask
6860 aptdaemon via the PackageKit API to install the requrired package.
</li
>
6862 <li
>aptdaemon ask for root password or sudo password, and install the
6863 package while showing progress information in a window.
</li
>
6867 <p
>I still need to come up with a better name for the system. Here
6868 are some screen shots showing the prototype in action. First the
6869 notification, then the password request, and finally the request to
6870 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
6872 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
6873 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
6874 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
6875 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
6876 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
6878 <p
>The prototype still need to be improved with longer timeouts, but
6879 is already useful. The database of hardware to package mappings also
6880 need more work. It is currently compatible with the Ubuntu way of
6881 storing such information in the package control file, but could be
6882 changed to use other formats instead or in addition to the current
6883 method. I
've dropped the use of discover for this mapping, as the
6884 modalias approach is more flexible and easier to use on Linux as long
6885 as the Linux kernel expose its modalias strings directly.
</p
>
6887 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
6888 here is the command required to check out and build the source: Use
6889 '<tt
>svn checkout
6890 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
6891 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
6892 devscripts package.
</p
>
6894 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
6895 renamed to Isenkram and the source moved from the Debian Edu
6896 subversion repository to a Debian collab-maint git repository. See
6897 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
6898 instructions
</a
> for details.
</p
>
6903 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
6904 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
6905 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
6906 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
6907 <description><p
>This Christmas my trusty old laptop died. It died quietly and
6908 suddenly in bed. With a quiet whimper, it went completely quiet and
6909 black. The power button was no longer able to turn it on. It was a
6910 IBM Thinkpad X41, and the best laptop I ever had. Better than both
6911 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
6912 Compaq I had before that. Now I need to find a replacement. To keep
6913 going during Christmas, I moved the one year old SSD disk to my old
6914 X40 where it fitted (only one I had left that could use it), but it is
6915 not a durable solution.
6917 <p
>My laptop needs are fairly modest. This is my wishlist from when I
6918 got a new one more than
10 years ago. It still holds true.:)
</p
>
6922 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
6923 than A4).
</li
>
6924 <li
>Robust, it will be in my backpack every day.
</li
>
6925 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
6926 <li
>Long battery life time. Preferable a week.
</li
>
6927 <li
>Internal WIFI network card.
</li
>
6928 <li
>Internal Twisted Pair network card.
</li
>
6929 <li
>Some USB slots (
2-
3 is plenty)
</li
>
6930 <li
>Good keyboard - similar to the Thinkpad.
</li
>
6931 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
6933 <li
>Hardware supported by Debian Stable, ie the default kernel and
6934 X.org packages.
</li
>
6935 <li
>Quiet, preferably fan free (or at least not using the fan most of
6940 <p
>You will notice that there are no RAM and CPU requirements in the
6941 list. The reason is simply that the specifications on laptops the
6942 last
10-
15 years have been sufficient for my needs, and I have to look
6943 at other features to choose my laptop. But are there still made as
6944 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
6945 robust, and Thinkpads seem to be heading in the wrong direction since
6946 Lenovo took over. But I
've been told that X220 and X1 Carbon might
6947 still be useful.
</p
>
6949 <p
>Perhaps I should rethink my needs, and look for a pad with an
6950 external keyboard? I
'll have to check the
6951 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
6952 well-supported laptops, or perhaps just buy one preinstalled from one
6953 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
6954 Pre-loaded site
</a
>.
</p
>
6959 <title>How to find a browser plugin supporting a given MIME type
</title>
6960 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
6961 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
6962 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
6963 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
6964 install to get support for a given MIME type. Thanks to
6965 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
6966 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
6967 Unfortunately, not very many packages provide the needed meta
6968 information, Anyway, here is a small script to look up all browser
6969 plugin packages announcing ther MIME support using this specification:
</p
>
6975 def pkgs_handling_mimetype(mimetype):
6980 version = pkg.candidate
6982 version = pkg.installed
6985 record = version.record
6986 if not record.has_key(
'Npp-MimeType
'):
6988 mime_types = record[
'Npp-MimeType
'].split(
',
')
6989 for t in mime_types:
6990 t = t.rstrip().strip()
6992 thepkgs.append(pkg.name)
6994 mimetype =
"audio/ogg
"
6995 if
1 < len(sys.argv):
6996 mimetype = sys.argv[
1]
6997 print
"Browser plugin packages supporting %s:
" % mimetype
6998 for pkg in pkgs_handling_mimetype(mimetype):
6999 print
" %s
" %pkg
7002 <p
>It can be used like this to look up a given MIME type:
</p
>
7005 % ./apt-find-browserplug-for-mimetype
7006 Browser plugin packages supporting audio/ogg:
7008 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7009 Browser plugin packages supporting application/x-shockwave-flash:
7010 browser-plugin-gnash
7014 <p
>In Ubuntu this mechanism is combined with support in the browser
7015 itself to query for plugins and propose to install the needed
7016 packages. It would be great if Debian supported such feature too. Is
7017 anyone working on adding it?
</p
>
7019 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
7020 request for icweasel support for this feature is
7021 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
7022 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
7023 of manpower and wish for a different design is the reason thus feature
7024 is not yet in iceweasel from Debian.
</p
>
7029 <title>What is the most supported MIME type in Debian?
</title>
7030 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
7031 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
7032 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
7033 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
7034 proposal to add AppStream information to the Debian archive
</a
>, is a
7035 proposal to make it possible for a Desktop application to propose to
7036 the user some package to install to gain support for a given MIME
7037 type, font, library etc. that is currently missing. With such
7038 mechanism in place, it would be possible for the desktop to
7039 automatically propose and install leocad if some LDraw file is
7040 downloaded by the browser.
</p
>
7042 <p
>To get some idea about the current content of the archive, I decided
7043 to write a simple program to extract all .desktop files from the
7044 Debian archive and look up the claimed MIME support there. The result
7046 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
7047 site
</a
>. Using the collected information, it become possible to
7048 answer the question in the title. Here are the
20 most supported MIME
7049 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7050 The complete list is available from the link above.
</p
>
7052 <p
><strong
>Debian Stable:
</strong
></p
>
7056 ----- -----------------------
7072 18 application/x-ogg
7079 <p
><strong
>Debian Testing:
</strong
></p
>
7083 ----- -----------------------
7099 18 application/x-ogg
7106 <p
><strong
>Debian Unstable:
</strong
></p
>
7110 ----- -----------------------
7127 18 application/x-ogg
7133 <p
>I am told that PackageKit can provide an API to access the kind of
7134 information mentioned in DEP-
11. I have not yet had time to look at
7135 it, but hope the PackageKit people in Debian are on top of these
7138 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
7139 discovering a typo in my script.
</p
>
7144 <title>Using modalias info to find packages handling my hardware
</title>
7145 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
7146 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
7147 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
7148 <description><p
>Yesterday, I wrote about the
7149 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
7150 values provided by the Linux kernel
</a
> following my hope for
7151 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
7152 dongle support in Debian
</a
>. Using this knowledge, I have tested how
7153 modalias values attached to package names can be used to map packages
7154 to hardware. This allow the system to look up and suggest relevant
7155 packages when I plug in some new hardware into my machine, and replace
7156 discover and discover-data as the database used to map hardware to
7159 <p
>I create a modaliases file with entries like the following,
7160 containing package name, kernel module name (if relevant, otherwise
7161 the package name) and globs matching the relevant hardware
7164 <p
><blockquote
>
7165 Package: package-name
7166 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
7167 </blockquote
></p
>
7169 <p
>It is fairly trivial to write code to find the relevant packages
7170 for a given modalias value using this file.
</p
>
7172 <p
>An entry like this would suggest the video and picture application
7173 cheese for many USB web cameras (interface bus class
0E01):
</p
>
7175 <p
><blockquote
>
7177 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
7178 </blockquote
></p
>
7180 <p
>An entry like this would suggest the pcmciautils package when a
7181 CardBus bridge (bus class
0607) PCI device is present:
</p
>
7183 <p
><blockquote
>
7184 Package: pcmciautils
7185 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7186 </blockquote
></p
>
7188 <p
>An entry like this would suggest the package colorhug-client when
7189 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
7191 <p
><blockquote
>
7192 Package: colorhug-client
7193 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
7194 </blockquote
></p
>
7196 <p
>I believe the format is compatible with the format of the Packages
7197 file in the Debian archive. Ubuntu already uses their Packages file
7198 to store their mappings from packages to hardware.
</p
>
7200 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
7201 announce the hardware it support in a way my prototype understand.
7202 This allow those publishing packages in an APT source outside the
7203 Debian archive as well as those backporting packages to make sure the
7204 hardware mapping are included in the package meta information. I
've
7205 tested such header in the pymissile package, and its modalias mapping
7206 is working as it should with my prototype. It even made it to Ubuntu
7209 <p
>To test if it was possible to look up supported hardware using only
7210 the shell tools available in the Debian installer, I wrote a shell
7211 implementation of the lookup code. The idea is to create files for
7212 each modalias and let the shell do the matching. Please check out and
7214 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
7215 shell script. It run without any extra dependencies and fetch the
7216 hardware mappings from the Debian archive and the subversion
7217 repository where I currently work on my prototype.
</p
>
7219 <p
>When I use it on a machine with a yubikey inserted, it suggest to
7220 install yubikey-personalization:
</p
>
7222 <p
><blockquote
>
7223 % ./hw-support-lookup
7224 <br
>yubikey-personalization
7226 </blockquote
></p
>
7228 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7229 propose to install the pcmciautils package:
</p
>
7231 <p
><blockquote
>
7232 % ./hw-support-lookup
7233 <br
>pcmciautils
7235 </blockquote
></p
>
7237 <p
>If you know of any hardware-package mapping that should be added to
7238 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
7239 database
</a
>, please tell me about it.
</p
>
7241 <p
>It could be possible to generate several of the mappings between
7242 packages and hardware. One source would be to look at packages with
7243 kernel modules, ie packages with *.ko files in /lib/modules/, and
7244 extract their modalias information. Another would be to look at
7245 packages with udev rules, ie packages with files in
7246 /lib/udev/rules.d/, and extract their vendor/model information to
7247 generate a modalias matching rule. I have not tested any of these to
7248 see if it work.
</p
>
7250 <p
>If you want to help implementing a system to let us propose what
7251 packages to install when new hardware is plugged into a Debian
7252 machine, please send me an email or talk to me on
7253 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7258 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
7259 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
7260 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
7261 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
7262 <description><p
>While looking into how to look up Debian packages based on hardware
7263 information, to find the packages that support a given piece of
7264 hardware, I refreshed my memory regarding modalias values, and decided
7265 to document the details. Here are my findings so far, also available
7267 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7268 Debian Edu subversion repository
</a
>:
7270 <p
><strong
>Modalias decoded
</strong
></p
>
7272 <p
>This document try to explain what the different types of modalias
7273 values stands for. It is in part based on information from
7274 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
7275 &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;,
7276 &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
7277 &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;.
7279 <p
>The modalias entries for a given Linux machine can be found using
7280 this shell script:
</p
>
7283 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
7286 <p
>The supported modalias globs for a given kernel module can be found
7287 using modinfo:
</p
>
7290 % /sbin/modinfo psmouse | grep alias:
7291 alias: serio:ty05pr*id*ex*
7292 alias: serio:ty01pr*id*ex*
7296 <p
><strong
>PCI subtype
</strong
></p
>
7298 <p
>A typical PCI entry can look like this. This is an Intel Host
7299 Bridge memory controller:
</p
>
7301 <p
><blockquote
>
7302 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7303 </blockquote
></p
>
7305 <p
>This represent these values:
</p
>
7310 sv
00001028 (subvendor)
7311 sd
000001AD (subdevice)
7313 sc
00 (bus subclass)
7317 <p
>The vendor/device values are the same values outputted from
'lspci
7318 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
7319 0600. The
0600 class is a host bridge. Other useful bus values are
7320 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
7322 <p
>Not sure how to figure out the interface value, nor what it
7325 <p
><strong
>USB subtype
</strong
></p
>
7327 <p
>Some typical USB entries can look like this. This is an internal
7328 USB hub in a laptop:
</p
>
7330 <p
><blockquote
>
7331 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7332 </blockquote
></p
>
7334 <p
>Here is the values included in this alias:
</p
>
7337 v
1D6B (device vendor)
7338 p
0001 (device product)
7340 dc
09 (device class)
7341 dsc
00 (device subclass)
7342 dp
00 (device protocol)
7343 ic
09 (interface class)
7344 isc
00 (interface subclass)
7345 ip
00 (interface protocol)
7348 <p
>The
0900 device class/subclass means hub. Some times the relevant
7349 class is in the interface class section. For a simple USB web camera,
7350 these alias entries show up:
</p
>
7352 <p
><blockquote
>
7353 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7354 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7355 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7356 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7357 </blockquote
></p
>
7359 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
7360 camera),
0101 is audio control device and
0102 is audio streaming (aka
7361 microphone). Thus this is a camera with microphone included.
</p
>
7363 <p
><strong
>ACPI subtype
</strong
></p
>
7365 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
7366 receiver in a Thinkpad X40:
</p
>
7368 <p
><blockquote
>
7369 acpi:IBM0071:PNP0511:
7370 </blockquote
></p
>
7372 <p
>The values between the colons are IDs.
</p
>
7374 <p
><strong
>DMI subtype
</strong
></p
>
7376 <p
>The DMI table contain lots of information about the computer case
7377 and model. This is an entry for a IBM Thinkpad X40, fetched from
7378 /sys/devices/virtual/dmi/id/modalias:
</p
>
7380 <p
><blockquote
>
7381 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7382 </blockquote
></p
>
7384 <p
>The values present are
</p
>
7387 bvn IBM (BIOS vendor)
7388 bvr
1UETB
6WW(
1.66) (BIOS version)
7389 bd
06/
15/
2005 (BIOS date)
7390 svn IBM (system vendor)
7391 pn
2371H4G (product name)
7392 pvr ThinkPadX40 (product version)
7393 rvn IBM (board vendor)
7394 rn
2371H4G (board name)
7395 rvr NotAvailable (board version)
7396 cvn IBM (chassis vendor)
7397 ct
10 (chassis type)
7398 cvr NotAvailable (chassis version)
7401 <p
>The chassis type
10 is Notebook. Other interesting values can be
7402 found in the dmidecode source:
</p
>
7406 4 Low Profile Desktop
7419 17 Main Server Chassis
7420 18 Expansion Chassis
7422 20 Bus Expansion Chassis
7423 21 Peripheral Chassis
7425 23 Rack Mount Chassis
7434 <p
>The chassis type values are not always accurately set in the DMI
7435 table. For example my home server is a tower, but the DMI modalias
7436 claim it is a desktop.
</p
>
7438 <p
><strong
>SerIO subtype
</strong
></p
>
7440 <p
>This type is used for PS/
2 mouse plugs. One example is from my
7441 test machine:
</p
>
7443 <p
><blockquote
>
7444 serio:ty01pr00id00ex00
7445 </blockquote
></p
>
7447 <p
>The values present are
</p
>
7456 <p
>This type is supported by the psmouse driver. I am not sure what
7457 the valid values are.
</p
>
7459 <p
><strong
>Other subtypes
</strong
></p
>
7461 <p
>There are heaps of other modalias subtypes according to
7462 file2alias.c. There is the rest of the list from that source: amba,
7463 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7464 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7465 vmbus, x86cpu and zorro. I did not spend time documenting all of
7466 these, as they do not seem relevant for my intended use with mapping
7467 hardware to packages when new stuff is inserted during run time.
</p
>
7469 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
7471 <p
>To check which kernel modules provide support for a given modalias,
7472 one can use the following shell script:
</p
>
7475 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
7476 echo
"$id
" ; \
7477 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
7481 <p
>The output can look like this (only the first few entries as the
7482 list is very long on my test machine):
</p
>
7486 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
7488 FATAL: Module acpi:device: not found.
7490 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
7491 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
7492 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
7493 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7494 acpi:IBM0071:PNP0511:
7495 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
7496 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
7497 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
7501 <p
>If you want to help implementing a system to let us propose what
7502 packages to install when new hardware is plugged into a Debian
7503 machine, please send me an email or talk to me on
7504 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7506 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
7507 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
7508 in /sys/ with space in them.
</p
>
7513 <title>Moved the pymissile Debian packaging to collab-maint
</title>
7514 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
7515 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
7516 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
7517 <description><p
>As part of my investigation on how to improve the support in Debian
7518 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7519 Launcher and updated the Debian package
7520 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
7521 sure udev will fix the device permissions when it is plugged in. I
7522 also added a
"Modaliases
" header to test it in the Debian archive and
7523 hopefully make the package be proposed by jockey in Ubuntu when a user
7524 plug in his rocket launcher. In the process I moved the source to a
7525 git repository under collab-maint, to make it easier for any DD to
7526 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
7527 is not very active, but the software still work for me even after five
7528 years of relative silence. The new git repository is not listed in
7529 the uploaded package yet, because I want to test the other changes a
7530 bit more before I upload the new version. If you want to check out
7531 the new version with a .desktop file included, visit the
7532 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
7533 view
</a
> or use
"<tt
>git clone
7534 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
7539 <title>Lets make hardware dongles easier to use in Debian
</title>
7540 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
7541 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
7542 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
7543 <description><p
>One thing that annoys me with Debian and Linux distributions in
7544 general, is that there is a great package management system with the
7545 ability to automatically install software packages by downloading them
7546 from the distribution mirrors, but no way to get it to automatically
7547 install the packages I need to use the hardware I plug into my
7548 machine. Even if the package to use it is easily available from the
7549 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7550 suggest to automatically install the python-nxt, nbc and t2n packages
7551 I need to talk to it. When I plug in a Yubikey, it could propose the
7552 yubikey-personalization package. The information required to do this
7553 is available, but no-one have pulled all the pieces together.
</p
>
7555 <p
>Some years ago, I proposed to
7556 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
7557 the discover subsystem to implement this
</a
>. The idea is fairly
7562 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
7563 starting when a user log in.
</li
>
7565 <li
>Set this program up to listen for kernel events emitted when new
7566 hardware is inserted into the computer.
</li
>
7568 <li
>When new hardware is inserted, look up the hardware ID in a
7569 database mapping to packages, and take note of any non-installed
7570 packages.
</li
>
7572 <li
>Show a message to the user proposing to install the discovered
7573 package, and make it easy to install it.
</li
>
7577 <p
>I am not sure what the best way to implement this is, but my
7578 initial idea was to use dbus events to discover new hardware, the
7579 discover database to find packages and
7580 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7583 <p
>Yesterday, I found time to try to implement this idea, and the
7584 draft package is now checked into
7585 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7586 Debian Edu subversion repository
</a
>. In the process, I updated the
7587 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7588 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7589 the relevant packages in Debian, and uploaded a new version
7590 2.2013.01.09 to unstable. I also discovered that the current
7591 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7592 package in Debian no longer discovered any USB devices, because
7593 /proc/bus/usb/devices is no longer present. I ported it to use
7594 libusb as a fall back option to get it working. The fixed package
7595 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7596 because of the freeze).
</p
>
7598 <p
>With this prototype in place, I can insert my Yubikey, and get this
7599 desktop notification to show up (only once, the first time it is
7600 inserted):
</p
>
7602 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7604 <p
>For this prototype to be really useful, some way to automatically
7605 install the proposed packages by pressing the
"Please install
7606 program(s)
" button should to be implemented.
</p
>
7608 <p
>If this idea seem useful to you, and you want to help make it
7609 happen, please help me update the discover-data database with mappings
7610 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7611 list the package you would like to have installed when a given
7612 hardware device is inserted into your computer, and report bugs using
7613 reportbug if it isn
't. Or, if you know of a better way to provide
7614 such mapping, please let me know.
</p
>
7616 <p
>This prototype need more work, and there are several questions that
7617 should be considered before it is ready for production use. Is dbus
7618 the correct way to detect new hardware? At the moment I look for HAL
7619 dbus events on the system bus, because that is the events I could see
7620 on my Debian Squeeze KDE desktop. Are there better events to use?
7621 How should the user be notified? Is the desktop notification
7622 mechanism the best option, or should the background daemon raise a
7623 popup instead? How should packages be installed? When should they
7624 not be installed?
</p
>
7626 <p
>If you want to help getting such feature implemented in Debian,
7627 please send me an email. :)
</p
>
7632 <title>New IRC channel for LEGO designers using Debian
</title>
7633 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7635 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7636 <description><p
>During Christmas, I have worked a bit on the Debian support for
7637 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7638 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7639 discovered I had to build all the tools myself because none were
7640 already in Debian Squeeze. If Debian support for LEGO is something
7641 you care about, please join me on the IRC channel
7642 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7643 irc.debian.org). There is a lot that could be done to improve the
7644 Debian support for LEGO designers. For example both CAD software
7645 and Mindstorm compilers are missing. :)
</p
>
7647 <p
>Update
2012-
01-
03: A
7648 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7649 including links to Lego related packages is now available.
</p
>
7654 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7655 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7656 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7657 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7658 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7659 year! I hope next year will prove to be a good year.
</p
>
7661 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7662 decentralised
"currency
" that allow people to transfer bitcoins
7663 between each other with minimal overhead, is a very interesting
7664 experiment. And as I wrote a few days ago, the bitcoin situation in
7665 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7666 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7667 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7668 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7669 for one of the ftpmasters to approve the new bitcoin-qt package
7672 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7673 team in Debian, you can easily test the package in Debian Squeeze
7674 using the following steps to get a set of working packages:
</p
>
7676 <blockquote
><pre
>
7677 git clone git://git.debian.org/git/collab-maint/bitcoin
7679 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7680 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7681 </pre
></blockquote
>
7683 <p
>You might have to install some build dependencies as well. The
7684 list of commands should give you two packages, bitcoind and
7685 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7686 client will download the complete set of bitcoin
"blocks
", which need
7687 around
5.6 GiB of data on my machine at the moment. Make sure your
7688 ~/.bitcoin/ directory have lots of spare room if you want to download
7689 all the blocks. The client will warn if the disk is getting full, so
7690 there is not really a problem if you got too little room, but you will
7691 not be able to get all the features out of the client.
</p
>
7693 <p
>As usual, if you use bitcoin and want to show your support of my
7694 activities, please send Bitcoin donations to my address
7695 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7700 <title>A word on bitcoin support in Debian
</title>
7701 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7702 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7703 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7704 <description><p
>It has been a while since I wrote about
7705 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7706 peer-to-peer based crypto-currency, and the reason is simply that I
7707 have been busy elsewhere. But two days ago, I started looking at the
7708 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7709 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7710 is now maintained by a
7711 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7712 people
</a
>, and the grunt work had already been done by this team. We
7713 owe a huge thank you to all these team members. :)
7714 But I was sad to discover that the bitcoin client is missing in
7715 Wheezy. It is only available in Sid (and an outdated client from
7716 backports). The client had several RC bugs registered in BTS blocking
7717 it from entering testing. To try to help the team and improve the
7718 situation, I spent some time providing patches and triaging the bug
7719 reports. I also had a look at the bitcoin package available from Matt
7721 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7722 Ubuntu
</a
>, and moved the useful pieces from that version into the
7723 Debian package.
</p
>
7725 <p
>After checking with the main package maintainer Jonas Smedegaard on
7726 IRC, I pushed several patches into the collab-maint git repository to
7727 improve the package. It now contains fixes for the RC issues (not from
7728 me, but fixed by Scott Howard), build rules for a Qt GUI client
7729 package, konqueror support for the bitcoin: URI and bash completion
7730 setup. As I work on Debian Squeeze, I also created
7731 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7732 patch to backport
</a
> the latest version. Jonas is going to look at
7733 it and try to integrate it into the git repository before uploading a
7734 new version to unstable.
7736 <p
>I would very much like bitcoin to succeed, to get rid of the
7737 centralized control currently exercised in the monetary system. I
7738 find it completely unacceptable that the USA government is collecting
7739 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7740 that the major credit card companies can block legal money
7741 transactions to Wikileaks. But for bitcoin to succeed, more people
7742 need to use bitcoins, and more people need to accept bitcoins when
7743 they sell products and services. Improving the bitcoin support in
7744 Debian is a small step in the right direction, but not enough.
7745 Unfortunately the user experience when browsing the web and wanting to
7746 pay with bitcoin is still not very good. The bitcoin: URI is a step
7747 in the right direction, but need to work in most or every browser in
7748 use. Also the bitcoin-qt client is too heavy to fire up to do a
7749 quick transaction. I believe there are other clients available, but
7750 have not tested them.
</p
>
7753 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7754 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7755 I received
20.15 BTC so far on the address I provided in my blog two
7756 years ago, as can be
7757 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7758 on the blockexplorer service
</a
>. Thank you everyone for your
7759 donation. The blockexplorer service demonstrates quite well that
7760 bitcoin is not quite anonymous and untracked. :) I wonder if the
7761 number of users have gone up since then. If you use bitcoin and want
7762 to show your support of my activity, please send Bitcoin donations to
7763 the same address as last time,
7764 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7769 <title>Git repository for song book for Computer Scientists
</title>
7770 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7771 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7772 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7773 <description><p
>As I
7774 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7775 this summer
</a
>, I have created a Computer Science song book a few
7776 years ago, and today I finally found time to create a public
7777 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7778 repository for the project
</a
>.
</p
>
7780 <p
>If you want to help out, please clone the source and submit patches
7781 to the HTML version. To generate the PDF and PostScript version,
7782 please use prince XML, or let me know about a useful free software
7783 processor capable of creating a good looking PDF from the HTML.
</p
>
7785 <p
>Want to sing? You can still find the song book in HTML, PDF and
7786 PostScript formats at
7787 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7788 Science Songbook
</a
>.
</p
>
7793 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7794 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7795 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7796 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7797 <description><p
>I dag fyller
7798 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7799 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7800 si gratulerer med dagen, Debian!
</p
>
7805 <title>Song book for Computer Scientists
</title>
7806 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7807 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7808 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7809 <description><p
>Many years ago, while studying Computer Science at the
7810 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7811 collecting computer related songs for use at parties. The original
7812 version was written in LaTeX, but a few years ago I got help from
7813 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7814 while keeping the ability to create a nice book in PDF format. I have
7815 not had time to maintain the book for a while now, and guess I should
7816 put it up on some public version control repository where others can
7817 help me extend and update the book. If anyone is volunteering to help
7818 me with this, send me an email. Also let me know if there are songs
7819 missing in my book.
</p
>
7821 <p
>I have not mentioned the book on my blog so far, and it occured to
7822 me today that I really should let all my readers share the joys of
7823 singing out load about programming, computers and computer networks.
7824 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
7825 12</a
> is about to start (and I am not going). Want to sing? Check
7826 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
7827 Computer Science Songbook
</a
>.
7832 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
7833 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
7834 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
7835 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
7836 <description><p
>At work we have heaps of servers. I believe the total count is
7837 around
1000 at the moment. To be able to get help from the vendors
7838 when something go wrong, we want to keep the firmware on the servers
7839 up to date. If the firmware isn
't the latest and greatest, the
7840 vendors typically refuse to start debugging any problems until the
7841 firmware is upgraded. So before every reboot, we want to upgrade the
7842 firmware, and we would really like everyone handling servers at the
7843 university to do this themselves when they plan to reboot a machine.
7844 For that to happen we at the unix server admin group need to provide
7845 the tools to do so.
</p
>
7847 <p
>To make firmware upgrading easier, I am working on a script to
7848 fetch and install the latest firmware for the servers we got. Most of
7849 our hardware are from Dell and HP, so I have focused on these servers
7850 so far. This blog post is about the Dell part.
</P
>
7852 <p
>On the Dell FTP site I was lucky enough to find
7853 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
7854 with firmware information for all
11th generation servers, listing
7855 which firmware should be used on a given model and where on the FTP
7856 site I can find it. Using a simple perl XML parser I can then
7857 download the shell scripts Dell provides to do firmware upgrades from
7858 within Linux and reboot when all the firmware is primed and ready to
7859 be activated on the first reboot.
</p
>
7861 <p
>This is the Dell related fragment of the perl code I am working on.
7862 Are there anyone working on similar tools for firmware upgrading all
7863 servers at a site? Please get in touch and lets share resources.
</p
>
7865 <p
><pre
>
7869 use File::Temp qw(tempdir);
7871 # Install needed RHEL packages if missing
7873 'XML::Simple
' =
> 'perl-XML-Simple
',
7875 for my $module (keys %rhelmodules) {
7876 eval
"use $module;
";
7878 my $pkg = $rhelmodules{$module};
7879 system(
"yum install -y $pkg
");
7880 eval
"use $module;
";
7884 my $errorsto =
'pere@hungry.com
';
7890 sub run_firmware_script {
7891 my ($opts, $script) = @_;
7893 print STDERR
"fail: missing script name\n
";
7896 print STDERR
"Running $script\n\n
";
7898 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
7899 print STDERR
"success: firmware script ran succcessfully\n
";
7901 print STDERR
"fail: firmware script returned error\n
";
7905 sub run_firmware_scripts {
7906 my ($opts, @dirs) = @_;
7907 # Run firmware packages
7908 for my $dir (@dirs) {
7909 print STDERR
"info: Running scripts in $dir\n
";
7910 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
7911 while (my $s = readdir $dh) {
7912 next if $s =~ m/^\.\.?/;
7913 run_firmware_script($opts,
"$dir/$s
");
7921 print STDERR
"info: Downloading $url\n
";
7922 system(
"wget --quiet \
"$url\
"");
7927 my $product = `dmidecode -s system-product-name`;
7930 if ($product =~ m/PowerEdge/) {
7932 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
7933 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
7935 my $tmpdir = tempdir(
7939 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
7940 system(
'gunzip Catalog.xml.gz
');
7941 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
7942 # -q is quiet, disabling interactivity and reducing console output
7943 my $fwopts =
"-q
";
7945 for my $url (@paths) {
7946 fetch_dell_fw($url);
7948 run_firmware_scripts($fwopts, $tmpdir);
7950 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7951 print STDERR
"error: Please report to $errorsto.\n
";
7955 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
7956 print STDERR
"error: Please report to $errorsto.\n
";
7962 my $url =
"ftp://ftp.us.dell.com/$path
";
7966 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
7967 # firmware packages to download from Dell. Only work for Linux
7968 # machines and
11th generation Dell servers.
7969 sub fetch_dell_fw_list {
7970 my $filename = shift;
7972 my $product = `dmidecode -s system-product-name`;
7974 my ($mybrand, $mymodel) = split(/\s+/, $product);
7976 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
7978 my $xml = XMLin($filename);
7980 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
7981 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
7982 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
7984 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
7985 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
7987 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
7989 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
7991 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
7994 for my $component (@{$xml-
>{SoftwareComponent}}) {
7995 my $componenttype = $component-
>{ComponentType}-
>{value};
7997 # Drop application packages, only firmware and BIOS
7998 next if
'APAC
' eq $componenttype;
8000 my $cpath = $component-
>{path};
8001 for my $path (@paths) {
8002 if ($cpath =~ m%/$path$%) {
8003 push(@paths, $cpath);
8011 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
8012 it could work on other platforms with some tweaking. Anyone know a
8013 index like Catalog.xml is available from HP for HP servers? At the
8014 moment I maintain a similar list manually and it is quickly getting
8020 <title>How is booting into runlevel
1 different from single user boots?
</title>
8021 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
8022 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
8023 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
8024 <description><p
>Wouter Verhelst have some
8025 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
8026 comments and opinions
</a
> on my blog post on
8027 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
8028 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
8029 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
8030 default KDE desktop in Debian
</a
>. I only have time to address one
8031 small piece of his comment now, and though it best to address the
8032 misunderstanding he bring forward:
</p
>
8034 <p
><blockquote
>
8035 Currently, a system admin has four options: [...] boot to a
8036 single-user system (by adding
'single
' to the kernel command line;
8037 this runs rcS and rc1 scripts)
8038 </blockquote
></p
>
8040 <p
>This make me believe Wouter believe booting into single user mode
8041 and booting into runlevel
1 is the same. I am not surprised he
8042 believe this, because it would make sense and is a quite sensible
8043 thing to believe. But because the boot in Debian is slightly broken,
8044 runlevel
1 do not work properly and it isn
't the same as single user
8045 mode. I
'll try to explain what is actually happing, but it is a bit
8046 hard to explain.
</p
>
8048 <p
>Single user mode is defined like this in /etc/inittab:
8049 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
8050 executed in single user mode is sulogin. Single user mode is a boot
8051 state
"between
" the runlevels, and when booting into single user mode,
8052 only the scripts in /etc/rcS.d/ are executed before the init process
8053 enters the single user state. When switching to runlevel
1, the state
8054 is in fact not ending in runlevel
1, but it passes through runlevel
1
8055 and end up in the single user mode (see /etc/rc1.d/S03single, which
8056 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
8057 1. It is confusing that the
'S
' (single user) init mode is not the
8058 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8061 <p
>This summary might make it clearer. When booting for the first
8062 time into single user mode, the following commands are executed:
8063 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
8064 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
8065 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
8066 trying to continue after visiting single user mode. Not all services
8067 are started again as they should, causing the machine to end up in an
8068 unpredicatble state. This is why Debian admins recommend rebooting
8069 after visiting single user mode.
</p
>
8071 <p
>A similar problem with runlevel
1 is caused by the amount of
8072 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
8073 to runlevel
1, the services started from /etc/rcS.d/ are not properly
8074 stopped when passing through the scripts in /etc/rc1.d/, and not
8075 started again when switching away from runlevel
1 to the runlevels
8076 2-
5. I believe the problem is best fixed by moving all the scripts
8077 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
8078 functioning single user mode during boot.
</p
>
8080 <p
>I have spent several years investigating the Debian boot system,
8081 and discovered this problem a few years ago. I suspect it originates
8082 from when sysvinit was introduced into Debian, a long time ago.
</p
>
8087 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
8088 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
8089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
8090 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
8091 <description><p
>In the Debian boot system, several packages include scripts that
8092 are started from /etc/rcS.d/. In fact, there is a bite more of them
8093 than make sense, and this causes a few problems. What kind of
8094 problems, you might ask. There are at least two problems. The first
8095 is that it is not possible to recover a machine after switching to
8096 runlevel
1. One need to actually reboot to get the machine back to
8097 the expected state. The other is that single user boot will sometimes
8098 run into problems because some of the subsystems are activated before
8099 the root login is presented, causing problems when trying to recover a
8100 machine from a problem in that subsystem. A minor additional point is
8101 that moving more scripts out of rcS.d/ and into the other rc#.d/
8102 directories will increase the amount of scripts that can run in
8103 parallel during boot, and thus decrease the boot time.
</p
>
8105 <p
>So, which scripts should start from rcS.d/. In short, only the
8106 scripts that _have_ to execute before the root login prompt is
8107 presented during a single user boot should go there. Everything else
8108 should go into the numeric runlevels. This means things like
8109 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8110 the numeric runlevels. Today in Debian, there are around
115 init.d
8111 scripts that are started from rcS.d/, and most of them should be moved
8112 out. Do your package have one of them? Please help us make single
8113 user and runlevel
1 better by moving it.
</p
>
8115 <p
>Scripts setting up the screen, keyboard, system partitions
8116 etc. should still be started from rcS.d/, but there is for example no
8117 need to have the network enabled before the single user login prompt
8118 is presented.
</p
>
8120 <p
>As always, things are not so easy to fix as they sound. To keep
8121 Debian systems working while scripts migrate and during upgrades, the
8122 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8123 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8124 and the next ones can only be moved when their dependencies have been
8125 moved first. This migration must be done sequentially while we ensure
8126 that the package system upgrade packages in the right order to keep
8127 the system state correct. This will require some coordination when it
8128 comes to network related packages, but most of the packages with
8129 scripts that should migrate do not have anything in rcS.d/ depending
8130 on them. Some packages have already been updated, like the sudo
8131 package, while others are still left to do. I wish I had time to work
8132 on this myself, but real live constrains make it unlikely that I will
8133 find time to push this forward.
</p
>
8138 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
8139 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
8140 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
8141 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
8142 <description><p
>While at Debconf11, I have several times during discussions
8143 mentioned the issues I believe should be improved in Debian for its
8144 desktop to be useful for more people. The use case for this is my
8145 parents, which are currently running Kubuntu which solve the
8148 <p
>I suspect these four missing features are not very hard to
8149 implement. After all, they are present in Ubuntu, so if we wanted to
8150 do this in Debian we would have a source.
</p
>
8154 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
8155 are new packages available for upgrades, a icon in the KDE status bar
8156 indicate this, and clicking on it will activate the simple upgrade
8157 tool to handle it. I have no problem guiding both of my parents
8158 through the process over the phone. If a kernel reboot is required,
8159 this too is indicated by the status bars and the upgrade tool. Last
8160 time I checked, nothing with the same features was working in KDE in
8163 <li
><strong
>Simple handling of missing Firefox browser
8164 plugins.
</strong
> When the browser encounter a MIME type it do not
8165 currently have a handler for, it will ask the user if the system
8166 should search for a package that would add support for this MIME type,
8167 and if the user say yes, the APT sources will be searched for packages
8168 advertising the MIME type in their control file (visible in the
8169 Packages file in the APT archive). If one or more packages are found,
8170 it is a simple click of the mouse to add support for the missing mime
8171 type. If the package require the user to accept some non-free
8172 license, this is explained to the user. The entire process make it
8173 more clear to the user why something do not work in the browser, and
8174 make the chances higher for the user to blame the web page authors and
8175 not the browser for any missing features.
</li
>
8177 <li
><strong
>Simple handling of missing multimedia codec/format
8178 handlers.
</strong
> When the media players encounter a format or codec
8179 it is not supporting, a dialog pop up asking the user if the system
8180 should search for a package that would add support for it. This
8181 happen with things like MP3, Windows Media or H
.264. The selection
8182 and installation procedure is very similar to the Firefox browser
8183 plugin handling. This is as far as I know implemented using a
8184 gstreamer hook. The end result is that the user easily get access to
8185 the codecs that are present from the APT archives available, while
8186 explaining more on why a given format is unsupported by Ubuntu.
</li
>
8188 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
8189 displaying a text/plain file in my Debian browser, it will propose to
8190 start emacs to show it. If I remember correctly, when doing the same
8191 in Kunbutu it show the file as a text file in the browser. At least I
8192 know Opera will show text files within the browser. I much prefer the
8193 latter behaviour.
</li
>
8197 <p
>There are other nice features as well, like the simplified suite
8198 upgrader, but given that I am the one mostly doing the dist-upgrade,
8199 it do not matter much.
</p
>
8201 <p
>I really hope we could get these features in place for the next
8202 Debian release. It would require the coordinated effort of several
8203 maintainers, but would make the end user experience a lot better.
</p
>
8208 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
8209 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
8210 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
8211 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
8212 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
8213 site is build on Debian/Squeeze, and this platform was chosen because
8214 I am most familiar with Debian (being a Debian Developer for around
10
8215 years) because it is the latest stable Debian release which should get
8216 security support for a few years.
</p
>
8218 <p
>The web service is written in Perl, and depend on some perl modules
8219 that are missing in Debian at the moment. It would be great if these
8220 modules were added to the Debian archive, allowing anyone to set up
8221 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
8222 in their own country using only Debian packages. The list of modules
8223 missing in Debian/Squeeze isn
't very long, and I hope the perl group
8224 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
8225 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8226 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8227 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8228 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8229 easier in the future.
</p
>
8231 <p
>Thanks to the great tools in Debian, getting the missing modules
8232 installed on my server was a simple call to
'cpan2deb Module::Name
'
8233 and
'dpkg -i
' to install the resulting package. But this leave me
8234 with the responsibility of tracking security problems, which I really
8235 do not have time for.
</p
>
8240 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
8241 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
8242 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
8243 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
8244 <description><p
>Here is a small update for my English readers. Most of my blog
8245 posts have been in Norwegian the last few weeks, so here is a short
8246 update in English.
</p
>
8248 <p
>The kids still keep me too busy to get much free software work
8249 done, but I did manage to organise a project to get a Norwegian port
8250 of the British service
8251 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
8252 and it has been running for a month now. The entire project has been
8253 organised by me and two others. Around Christmas we gathered sponsors
8254 to fund the development work. In January I drafted a contract with
8255 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
8256 and in February the development took place. Most of it involved
8257 converting the source to use GPS coordinates instead of British
8258 easting/northing, and the resulting code should be a lot easier to get
8259 running in any country by now. The Norwegian
8260 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
8261 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
8262 source and the source for administrative borders in Norway, and
8263 support for this had to be added/fixed.
</p
>
8265 <p
>The Norwegian version went live March
3th, and we spent the weekend
8266 polishing the system before we announced it March
7th. The system is
8267 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
8268 problem reports in a few weeks. Soon we hope to announce the Android
8269 and iPhone versions making it even easier to report problems with the
8270 public infrastructure.
</p
>
8272 <p
>Perhaps something to consider for those of you in countries without
8273 such service?
</p
>
8278 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
8279 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
8280 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
8281 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
8282 <description><p
>The last few days I have looked at ways to track open security
8283 issues here at my work with the University of Oslo. My idea is that
8284 it should be possible to use the information about security issues
8285 available on the Internet, and check our locally
8286 maintained/distributed software against this information. It should
8287 allow us to verify that no known security issues are forgotten. The
8288 CVE database listing vulnerabilities seem like a great central point,
8289 and by using the package lists from Debian mapped to CVEs provided by
8290 the testing security team, I believed it should be possible to figure
8291 out which security holes were present in our free software
8292 collection.
</p
>
8294 <p
>After reading up on the topic, it became obvious that the first
8295 building block is to be able to name software packages in a unique and
8296 consistent way across data sources. I considered several ways to do
8297 this, for example coming up with my own naming scheme like using URLs
8298 to project home pages or URLs to the Freshmeat entries, or using some
8299 existing naming scheme. And it seem like I am not the first one to
8300 come across this problem, as MITRE already proposed and implemented a
8301 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
8302 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
8303 software, hardware and other platform components. The CPE ids are
8304 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
8305 Vulnerability Database
</a
>, allowing me to look up know security
8306 issues for any CPE name. With this in place, all I need to do is to
8307 locate the CPE id for the software packages we use at the university.
8308 This is fairly trivial (I google for
'cve cpe $package
' and check the
8309 NVD entry if a CVE for the package exist).
</p
>
8311 <p
>To give you an example. The GNU gzip source package have the CPE
8312 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
8313 check out, one could look up
8314 <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
8315 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
8316 The most recent one is
8317 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
8318 and at the bottom of the NVD page for this vulnerability the complete
8319 list of affected versions is provided.
</p
>
8321 <p
>The NVD database of CVEs is also available as a XML dump, allowing
8322 for offline processing of issues. Using this dump, I
've written a
8323 small script taking a list of CPEs as input and list all CVEs
8324 affecting the packages represented by these CPEs. One give it CPEs
8325 with version numbers as specified above and get a list of open
8326 security issues out.
</p
>
8328 <p
>Of course for this approach to be useful, the quality of the NVD
8329 information need to be high. For that to happen, I believe as many as
8330 possible need to use and contribute to the NVD database. I notice
8332 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
8333 map from CVE to CPE
</a
>, indicating that they are using the CPE
8334 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
8336 <p
>To get an idea about the quality for free software, I spent some
8337 time making it possible to compare the CVE database from Debian with
8338 the CVE database in NVD. The result look fairly good, but there are
8339 some inconsistencies in NVD (same software package having several
8340 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8341 Debian believe are affected by a CVE). Hope to find time to improve
8342 the quality of NVD, but that require being able to get in touch with
8343 someone maintaining it. So far my three emails with questions and
8344 corrections have not seen any reply, but I hope contact can be
8345 established soon.
</p
>
8347 <p
>An interesting application for CPEs is cross platform package
8348 mapping. It would be useful to know which packages in for example
8349 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8350 this would be trivial if all linux distributions provided CPE entries
8351 for their packages.
</p
>
8356 <title>Which module is loaded for a given PCI and USB device?
</title>
8357 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
8358 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
8359 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
8360 <description><p
>In the
8361 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
8362 package in Debian, there is a script to report useful information
8363 about the running hardware for use when people report missing
8364 information. One part of this script that I find very useful when
8365 debugging hardware problems, is the part mapping loaded kernel module
8366 to the PCI device it claims. It allow me to quickly see if the kernel
8367 module I expect is driving the hardware I am struggling with. To see
8368 the output, make sure discover-data is installed and run
8369 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
8370 one of my machines like this:
</p
>
8374 10de:
03eb i2c_nforce2
8377 10de:
03f0 snd_hda_intel
8386 <p
>The code in question look like this, slightly modified for
8387 readability and to drop the output to file descriptor
3:
</p
>
8390 if [ -d /sys/bus/pci/devices/ ] ; then
8391 echo loaded pci modules:
8393 cd /sys/bus/pci/devices/
8394 for address in * ; do
8395 if [ -d
"$address/driver/module
" ] ; then
8396 module=`cd $address/driver/module ; pwd -P | xargs basename`
8397 if grep -q
"^$module
" /proc/modules ; then
8398 address=$(echo $address |sed s/
0000://)
8399 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
8400 echo
"$id $module
"
8409 <p
>Similar code could be used to extract USB device module
8413 if [ -d /sys/bus/usb/devices/ ] ; then
8414 echo loaded usb modules:
8416 cd /sys/bus/usb/devices/
8417 for address in * ; do
8418 if [ -d
"$address/driver/module
" ] ; then
8419 module=`cd $address/driver/module ; pwd -P | xargs basename`
8420 if grep -q
"^$module
" /proc/modules ; then
8421 address=$(echo $address |sed s/
0000://)
8422 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
8423 if [
"$id
" ] ; then
8424 echo
"$id $module
"
8434 <p
>This might perhaps be something to include in other tools as
8440 <title>How to test if a laptop is working with Linux
</title>
8441 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
8442 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
8443 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
8444 <description><p
>The last few days I have spent at work here at the
<a
8445 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
8446 batch of computers will work with Linux. Every year for the last few
8447 years the university have organised shared bid of a few thousand
8448 computers, and this year HP won the bid. Two different desktops and
8449 five different laptops are on the list this year. We in the UNIX
8450 group want to know which one of these computers work well with RHEL
8451 and Ubuntu, the two Linux distributions we currently handle at the
8452 university.
</p
>
8454 <p
>My test method is simple, and I share it here to get feedback and
8455 perhaps inspire others to test hardware as well. To test, I PXE
8456 install the OS version of choice, and log in as my normal user and run
8457 a few applications and plug in selected pieces of hardware. When
8458 something fail, I make a note about this in the test matrix and move
8459 on. If I have some spare time I try to report the bug to the OS
8460 vendor, but as I only have the machines for a short time, I rarely
8461 have the time to do this for all the problems I find.
</p
>
8463 <p
>Anyway, to get to the point of this post. Here is the simple tests
8464 I perform on a new model.
</p
>
8468 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
8469 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8470 RHEL5 and Debian Edu/Squeeze.
</li
>
8472 <li
>Is X.org working? If the graphical login screen show up after
8473 installation, X.org is working.
</li
>
8475 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
8476 package mesa-utils on Ubuntu) and writing down the frames per second
8477 reported by the program.
</li
>
8479 <li
>Is sound working? With Gnome and KDE, a sound is played when
8480 logging in, and if I can hear this the test is successful. If there
8481 are several audio exits on the machine, I try them all and check if
8482 the Gnome/KDE audio mixer can control where to send the sound. I
8483 normally test this by playing
8484 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
8485 video
</a
> in Firefox/Iceweasel.
</li
>
8487 <li
>Is the USB subsystem working? I test this by plugging in a USB
8488 memory stick and see if Gnome/KDE notices this.
</li
>
8490 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
8491 I have lying around, and see if Gnome/KDE notices this.
</li
>
8493 <li
>Is any built in camera working? Test using cheese, and see if a
8494 picture from the v4l device show up.
</li
>
8496 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8497 any bluetooth devices are discovered. In my office, I normally see a
8500 <li
>For laptops, is the SD or Compaq Flash reader working. I have
8501 memory modules lying around, and stick them in and see if Gnome/KDE
8502 notice this.
</li
>
8504 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
8505 special button work, and if the laptop continue to work after
8508 <li
>For laptops, is the extra buttons working, like audio level,
8509 adjusting background light, switching on/off external video output,
8510 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8511 laptop to laptop, so I just write down which are working and which are
8514 <li
>Some laptops have smart card readers, finger print readers,
8515 acceleration sensors etc. I rarely test these, as I do not know how
8516 to quickly test if they are working or not, so I only document their
8517 existence.
</li
>
8521 <p
>By now I suspect you are really curious what the test results are
8522 for the HP machines I am testing. I
'm not done yet, so I will report
8523 the test results later. For now I can report that HP
8100 Elite work
8524 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
8525 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
8526 can see, I have most machines left to test. One interesting
8527 observation is that Ubuntu Lucid has almost twice the frame rate than
8528 RHEL6 with glxgears. No idea why.
</p
>
8533 <title>Some thoughts on BitCoins
</title>
8534 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
8535 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
8536 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
8537 <description><p
>As I continue to explore
8538 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
8539 what properties the system have, and how it will be affected by laws
8540 and regulations here in Norway. Here are some random notes.
</p
>
8542 <p
>One interesting thing to note is that since the transactions are
8543 verified using a peer to peer network, all details about a transaction
8544 is known to everyone. This means that if a BitCoin address has been
8545 published like I did with mine in my initial post about BitCoin, it is
8546 possible for everyone to see how many BitCoins have been transfered to
8547 that address. There is even a web service to look at the details for
8548 all transactions. There I can see that my address
8549 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
8550 have received
16.06 Bitcoin, the
8551 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
8552 address of Simon Phipps have received
181.97 BitCoin and the address
8553 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
8554 of EFF have received
2447.38 BitCoins so far. Thank you to each and
8555 every one of you that donated bitcoins to support my activity. The
8556 fact that anyone can see how much money was transfered to a given
8557 address make it more obvious why the BitCoin community recommend to
8558 generate and hand out a new address for each transaction. I
'm told
8559 there is no way to track which addresses belong to a given person or
8560 organisation without the person or organisation revealing it
8561 themselves, as Simon, EFF and I have done.
</p
>
8563 <p
>In Norway, and in most other countries, there are laws and
8564 regulations limiting how much money one can transfer across the border
8565 without declaring it. There are money laundering, tax and accounting
8566 laws and regulations I would expect to apply to the use of BitCoin.
8567 If the Skolelinux foundation
8568 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
8569 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
8570 normal bank transfers like EFF is doing, how should this be accounted?
8571 Given that it is impossible to know if money can cross the border or
8572 not, should everything or nothing be declared? What exchange rate
8573 should be used when calculating taxes? Would receivers have to pay
8574 income tax if the foundation were to pay Skolelinux contributors in
8575 BitCoin? I have no idea, but it would be interesting to know.
</p
>
8577 <p
>For a currency to be useful and successful, it must be trusted and
8578 accepted by a lot of users. It must be possible to get easy access to
8579 the currency (as a wage or using currency exchanges), and it must be
8580 easy to spend it. At the moment BitCoin seem fairly easy to get
8581 access to, but there are very few places to spend it. I am not really
8582 a regular user of any of the vendor types currently accepting BitCoin,
8583 so I wonder when my kind of shop would start accepting BitCoins. I
8584 would like to buy electronics, travels and subway tickets, not herbs
8585 and books. :) The currency is young, and this will improve over time
8586 if it become popular, but I suspect regular banks will start to lobby
8587 to get BitCoin declared illegal if it become popular. I
'm sure they
8588 will claim it is helping fund terrorism and money laundering (which
8589 probably would be true, as is any currency in existence), but I
8590 believe the problems should be solved elsewhere and not by blaming
8591 currencies.
</p
>
8593 <p
>The process of creating new BitCoins is called mining, and it is
8594 CPU intensive process that depend on a bit of luck as well (as one is
8595 competing against all the other miners currently spending CPU cycles
8596 to see which one get the next lump of cash). The
"winner
" get
50
8597 BitCoin when this happen. Yesterday I came across the obvious way to
8598 join forces to increase ones changes of getting at least some coins,
8599 by coordinating the work on mining BitCoins across several machines
8600 and people, and sharing the result if one is lucky and get the
50
8602 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8603 if this sounds interesting. I have not had time to try to set up a
8604 machine to participate there yet, but have seen that running on ones
8605 own for a few days have not yield any BitCoins througth mining
8608 <p
>Update
2010-
12-
15: Found an
<a
8609 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8610 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8611 it was interesting to read. The arguments presented seem to be
8612 equally valid for gold, which was used as a currency for many years.
</p
>
8617 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8618 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8620 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8621 <description><p
>With this weeks lawless
8622 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8623 attacks
</a
> on Wikileak and
8624 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8625 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8626 not be trusted to handle money transactions.
8628 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8629 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8630 mine mentioned earlier. I decided to follow Simon
's example, and get
8631 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8632 some help from my friend to get it all running, and he even handed me
8633 some bitcoins to get started. I even donated a few bitcoins to Simon
8634 for helping me remember BitCoin.
</p
>
8636 <p
>So, what is bitcoins, you probably wonder? It is a digital
8637 crypto-currency, decentralised and handled using peer-to-peer
8638 networks. It allows anonymous transactions and prohibits central
8639 control over the transactions, making it impossible for governments
8640 and companies alike to block donations and other transactions. The
8641 source is free software, and while the key dependency wxWidgets
2.9
8642 for the graphical user interface is missing in Debian, the command
8643 line client builds just fine. Hopefully Jonas
8644 <a href=
"http://bugs.debian.org/
578157">will get the package into
8645 Debian
</a
> soon.
</p
>
8647 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8648 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8649 bitcoins
</a
> when selling services and goods, and there are even
8650 currency
"stock
" markets where the exchange rate is decided. There
8651 are not many users so far, but the concept seems promising. If you
8652 want to get started and lack a friend with any bitcoins to spare,
8654 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8655 bitcoin at the time of writing). Use
8656 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8657 on the current exchange rates.
</p
>
8659 <p
>As an experiment, I have decided to set up bitcoind on one of my
8660 machines. If you want to support my activity, please send Bitcoin
8661 donations to the address
8662 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8667 <title>Why isn
't Debian Edu using VLC?
</title>
8668 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8669 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8670 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8671 <description><p
>In the latest issue of Linux Journal, the readers choices were
8672 presented, and the winner among the multimedia player were VLC.
8673 Personally, I like VLC, and it is my player of choice when I first try
8674 to play a video file or stream. Only if VLC fail will I drag out
8675 gmplayer to see if it can do better. The reason is mostly the failure
8676 model and trust. When VLC fail, it normally pop up a error message
8677 reporting the problem. When mplayer fail, it normally segfault or
8678 just hangs. The latter failure mode drain my trust in the program.
<p
>
8680 <p
>But even if VLC is my player of choice, we have choosen to use
8681 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8682 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8683 plugin to play web videos seamlessly, and the VLC browser plugin is
8684 not very good. For example, it lack in-line control buttons, so there
8685 is no way for the user to pause the video. Also, when I
8686 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8687 tested the browser plugins
</a
> available in Debian, the VLC plugin
8688 failed on several video pages where mplayer based plugins worked. If
8689 the browser plugin for VLC was as good as the gecko-mediaplayer
8690 package (which uses mplayer), we would switch.
</P
>
8692 <p
>While VLC is a good player, its user interface is slightly
8693 annoying. The most annoying feature is its inconsistent use of
8694 keyboard shortcuts. When the player is in full screen mode, its
8695 shortcuts are different from when it is playing the video in a window.
8696 For example, space only work as pause when in full screen mode. I
8697 wish it had consisten shortcuts and that space also would work when in
8698 window mode. Another nice shortcut in gmplayer is [enter] to restart
8699 the current video. It is very nice when playing short videos from the
8700 web and want to restart it when new people arrive to have a look at
8701 what is going on.
</p
>
8706 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8707 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8708 <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>
8709 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8710 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8711 upgrade testing of the
8712 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8713 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8714 This seem like a very good idea, so I adjusted by test scripts and
8715 can now present the updated result from today:
</p
>
8717 <p
>This is for Gnome:
</p
>
8719 <p
>Installed using apt-get, missing with aptitude
</p
>
8721 <blockquote
><p
>
8726 browser-plugin-gnash
8733 freedesktop-sound-theme
8735 gconf-defaults-service
8750 gnome-desktop-environment
8754 gnome-session-canberra
8759 gstreamer0.10-fluendo-mp3
8765 libapache2-mod-dnssd
8768 libaprutil1-dbd-sqlite3
8771 libboost-date-time1.42
.0
8772 libboost-python1.42
.0
8773 libboost-thread1.42
.0
8775 libchamplain-gtk-
0.4-
0
8777 libclutter-gtk-
0.10-
0
8784 libfreerdp-plugins-standard
8799 libgnomepanel2.24-cil
8804 libgtksourceview2.0-common
8805 libmono-addins-gui0.2-cil
8806 libmono-addins0.2-cil
8807 libmono-cairo2.0-cil
8808 libmono-corlib2.0-cil
8809 libmono-i18n-west2.0-cil
8810 libmono-posix2.0-cil
8811 libmono-security2.0-cil
8812 libmono-sharpzip2.84-cil
8813 libmono-system2.0-cil
8816 libndesk-dbus-glib1.0-cil
8817 libndesk-dbus1.0-cil
8827 libtelepathy-farsight0
8836 nautilus-sendto-empathy
8840 python-aptdaemon-gtk
8842 python-beautifulsoup
8857 python-gtksourceview2
8868 python-pkg-resources
8875 python-twisted-conch
8881 python-zope.interface
8886 rhythmbox-plugin-cdrecorder
8893 system-config-printer-udev
8895 telepathy-mission-control-
5
8906 </p
></blockquote
>
8908 <p
>Installed using apt-get, removed with aptitude
</p
>
8910 <blockquote
><p
>
8916 fast-user-switch-applet
8935 libgtksourceview2.0-
0
8937 libsdl1.2debian-alsa
8943 system-config-printer
8948 </p
></blockquote
>
8950 <p
>Installed using aptitude, missing with apt-get
</p
>
8952 <blockquote
><p
>
8953 gstreamer0.10-gnomevfs
8954 </p
></blockquote
>
8956 <p
>Installed using aptitude, removed with apt-get
</p
>
8958 <blockquote
><p
>
8960 </p
></blockquote
>
8962 <p
>This is for KDE:
</p
>
8964 <p
>Installed using apt-get, missing with aptitude
</p
>
8966 <blockquote
><p
>
8968 </p
></blockquote
>
8970 <p
>Installed using apt-get, removed with aptitude
</p
>
8972 <blockquote
><p
>
8975 </p
></blockquote
>
8977 <p
>Installed using aptitude, missing with apt-get
</p
>
8979 <blockquote
><p
>
8993 kdeartwork-emoticons
8995 kdeartwork-theme-icon
8999 kdebase-workspace-bin
9000 kdebase-workspace-data
9014 kscreensaver-xsavers
9029 plasma-dataengines-workspace
9031 plasma-desktopthemes-artwork
9032 plasma-runners-addons
9033 plasma-scriptengine-googlegadgets
9034 plasma-scriptengine-python
9035 plasma-scriptengine-qedje
9036 plasma-scriptengine-ruby
9037 plasma-scriptengine-webkit
9038 plasma-scriptengines
9039 plasma-wallpapers-addons
9040 plasma-widget-folderview
9041 plasma-widget-networkmanagement
9045 xscreensaver-data-extra
9047 xscreensaver-gl-extra
9048 xscreensaver-screensaver-bsod
9049 </p
></blockquote
>
9051 <p
>Installed using aptitude, removed with apt-get
</p
>
9053 <blockquote
><p
>
9055 google-gadgets-common
9073 libggadget-qt-
1.0-
0b
9078 libkonqsidebarplugin4a
9087 libplasma-geolocation-interface4
9089 libplasmagenericshell4
9103 libsmokeknewstuff2-
3
9104 libsmokeknewstuff3-
3
9106 libsmokektexteditor3
9114 libsmokeqtnetwork4-
3
9120 libsmokeqtuitools4-
3
9132 plasma-dataengines-addons
9133 plasma-scriptengine-superkaramba
9134 plasma-widget-lancelot
9135 plasma-widgets-addons
9136 plasma-widgets-workspace
9140 update-notifier-common
9141 </p
></blockquote
>
9143 <p
>Running apt-get autoremove made the results using apt-get and
9144 aptitude a bit more similar, but there are still quite a lott of
9145 differences. I have no idea what packages should be installed after
9146 the upgrade, but hope those that do can have a look.
</p
>
9151 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
9152 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
9153 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
9154 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
9155 <description><p
>Most of the computers in use by the
9156 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
9157 are virtual machines. And they have been Xen machines running on a
9158 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
9159 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
9160 bit harder that it could have been, because we set up the Xen virtual
9161 machines to get the virtual partitions from LVM, which as far as I
9162 know is not supported by KVM. So to migrate, we had to convert
9163 several LVM logical volumes to partitions on a virtual disk file.
</p
>
9166 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
9167 nice recipe
</a
> to do this, and wrote the following script to do the
9168 migration. It uses qemu-img from the qemu package to make the disk
9169 image, parted to partition it, losetup and kpartx to present the disk
9170 image partions as devices, and dd to copy the data. I NFS mounted the
9171 new servers storage area on the old server to do the migration.
</p
>
9177 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9182 if [ -z
"$
1" ] ; then
9183 echo
"Usage: $
0 &lt;hostname
&gt;
"
9189 if [ ! -e /dev/vg_data/$host-disk ] ; then
9190 echo
"error: unable to find LVM volume for $host
"
9194 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9195 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9196 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9197 totalsize=$(( ( $disksize + $swapsize ) ))
9200 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
9201 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9203 parted $img mklabel msdos
9204 parted $img mkpart primary linux-swap
0 $disksize
9205 parted $img mkpart primary ext2 $disksize $totalsize
9206 parted $img set
1 boot on
9209 losetup /dev/loop0 $img
9210 kpartx -a /dev/loop0
9212 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
9213 fsck.ext3 -f /dev/mapper/loop0p1 || true
9214 mkswap /dev/mapper/loop0p2
9216 kpartx -d /dev/loop0
9217 losetup -d /dev/loop0
9220 <p
>The script is perhaps so simple that it is not copyrightable, but
9221 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
9223 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
9224 the new disk image attached, installed grub-pc and linux-image-
686 and
9225 set up grub to boot from the disk image. After this, the KVM machines
9226 seem to work just fine.
</p
>
9231 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
9232 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
9233 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
9234 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
9235 <description><p
>I
'm still running upgrade testing of the
9236 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
9237 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
9238 status. Here is a short update based on a test I ran
20101118.
</p
>
9240 <p
>I still do not know what a correct migration should look like, so I
9241 report any differences between apt and aptitude and hope someone else
9242 can see if anything should be changed.
</p
>
9244 <p
>This is for Gnome:
</p
>
9246 <p
>Installed using apt-get, missing with aptitude
</p
>
9248 <blockquote
><p
>
9249 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9250 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
9251 dmz-cursor-theme empathy empathy-common finger
9252 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9253 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9254 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9255 gnome-cards-data gnome-codec-install gnome-core
9256 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9257 gnome-search-tool gnome-session-canberra gnome-spell
9258 gnome-system-log gnome-themes-extras gnome-themes-more
9259 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9260 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9261 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9262 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9263 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
9264 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
9265 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
9266 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
9267 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
9268 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9269 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
9270 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9271 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9272 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9273 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9274 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9275 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9276 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9277 libmono-security2.0-cil libmono-sharpzip2.84-cil
9278 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
9279 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
9280 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
9281 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
9282 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
9283 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
9284 libxalan2-java libxerces2-java media-player-info mesa-utils
9285 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
9286 nautilus-sendto-empathy openoffice.org-writer2latex
9287 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
9288 python-aptdaemon python-aptdaemon-gtk python-axiom
9289 python-beautifulsoup python-bugbuddy python-clientform
9290 python-coherence python-configobj python-crypto python-cupshelpers
9291 python-cupsutils python-eggtrayicon python-elementtree
9292 python-epsilon python-evolution python-feedparser python-gdata
9293 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9294 python-gtksourceview2 python-httplib2 python-louie python-mako
9295 python-markupsafe python-mechanize python-nevow python-notify
9296 python-opengl python-openssl python-pam python-pkg-resources
9297 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9298 python-tagpy python-twisted-bin python-twisted-conch
9299 python-twisted-core python-twisted-web python-utidylib python-webkit
9300 python-xdg python-zope.interface remmina remmina-plugin-data
9301 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9302 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9303 software-center svgalibg1 system-config-printer-udev
9304 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
9305 totem totem-coherence totem-mozilla totem-plugins
9306 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9308 </p
></blockquote
>
9310 Installed using apt-get, removed with aptitude
9312 <blockquote
><p
>
9313 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9314 epiphany-extensions epiphany-gecko evolution-exchange
9315 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9316 gedit-common gnome-app-install gnome-games gnome-games-data
9317 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9318 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9319 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9320 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
9321 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
9322 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
9323 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
9324 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9325 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9326 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9327 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
9328 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
9329 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9330 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9331 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9332 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9333 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
9334 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
9335 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
9336 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
9337 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
9338 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9339 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9340 sound-juicer swfdec-gnome system-config-printer totem-common
9341 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9342 </p
></blockquote
>
9344 <p
>Installed using aptitude, missing with apt-get
</p
>
9346 <blockquote
><p
>
9347 gstreamer0.10-gnomevfs
9348 </p
></blockquote
>
9350 <p
>Installed using aptitude, removed with apt-get
</p
>
9352 <blockquote
><p
>
9354 </p
></blockquote
>
9356 <p
>This is for KDE:
</p
>
9358 <p
>Installed using apt-get, missing with aptitude
</p
>
9360 <blockquote
><p
>
9361 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
9362 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9363 ghostscript-x git gnome-audio gnugo granatier gs-common
9364 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9365 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9366 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9367 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9368 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9369 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9370 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9371 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9372 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9373 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9374 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9375 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
9376 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9377 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9378 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9379 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9380 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9381 libkrossui4 libmailtools-perl libmime-tools-perl
9382 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9383 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9384 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9385 lirc luatex marble networkstatus noatun-plugins
9386 openoffice.org-writer2latex palapeli palapeli-data parley
9387 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9388 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9389 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9391 </p
></blockquote
>
9393 <p
>Installed using apt-get, removed with aptitude
</p
>
9395 <blockquote
><p
>
9396 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9397 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9398 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9399 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9400 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9401 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9402 kitchensync kiten kjumpingcube klatin klettres klickety klines
9403 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9404 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9405 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9406 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9407 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9408 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9409 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9410 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9411 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9412 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
9413 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
9414 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9415 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
9416 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
9417 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9418 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9419 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9420 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9421 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9422 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9423 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
9424 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
9425 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9426 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9427 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9428 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9429 </p
></blockquote
>
9431 <p
>Installed using aptitude, missing with apt-get
</p
>
9433 <blockquote
><p
>
9434 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9435 kdeartwork kdebase kdebase-apps kdebase-workspace
9436 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9437 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9438 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9439 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9440 xscreensaver-screensaver-bsod
9441 </p
></blockquote
>
9443 <p
>Installed using aptitude, removed with apt-get
</p
>
9445 <blockquote
><p
>
9446 kdebase-bin konq-plugins konqueror
9447 </p
></blockquote
>
9452 <title>Gnash buildbot slave and Debian kfreebsd
</title>
9453 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
9454 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
9455 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
9456 <description><p
>Answering
9457 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
9458 call from the Gnash project
</a
> for
9459 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
9460 current source, I have set up a virtual KVM machine on the Debian
9461 Edu/Skolelinux virtualization host to test the git source on
9462 Debian/Squeeze. I hope this can help the developers in getting new
9463 releases out more often.
</p
>
9465 <p
>As the developers want less main-stream build platforms tested to,
9466 I have considered setting up a
<a
9467 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
9468 machine as well. I have also considered using the kfreebsd
9469 architecture in Debian as a file server in NUUG to get access to the
5
9470 TB zfs volume we currently use to store DV video. Because of this, I
9471 finally got around to do a test installation of Debian/Squeeze with
9472 kfreebsd. Installation went fairly smooth, thought I noticed some
9473 visual glitches in the cdebconf dialogs (black cursor left on the
9474 screen at random locations). Have not gotten very far with the
9475 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9476 fatal problem. Have to spend some more time on it to see if it is
9477 useful as a file server for NUUG. Will try to find time to set up a
9478 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
9483 <title>Debian in
3D
</title>
9484 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
9485 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
9486 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
9487 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
9489 <p
>3D printing is just great. I just came across this Debian logo in
9491 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
9492 thingiverse blog
</a
>.
</p
>
9497 <title>Software updates
2010-
10-
24</title>
9498 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
9499 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
9500 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
9501 <description><p
>Some updates.
</p
>
9503 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
9504 raise money for the project is going well. The lower limit of
10
9505 signers was reached in
24 hours, and so far
13 people have signed it.
9506 More signers and more funding is most welcome, and I am really curious
9507 how far we can get before the time limit of December
24 is reached.
9510 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
9511 about what appear to be a great code coverage tool capable of
9512 generating code coverage stats without any changes to the source code.
9514 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
9515 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
9516 It is missing in Debian, but the git source built just fine in Squeeze
9517 after I installed libelf-dev, libdwarf-dev, pkg-config and
9518 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9519 solvable. I hope kcov make it into Debian soon.
</p
>
9521 <p
>Finally found time to wrap up the release notes for
<a
9522 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
9523 new alpha release of Debian Edu
</a
>, and just published the second
9524 alpha test release of the Squeeze based Debian Edu /
9525 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
9526 release. Give it a try if you need a complete linux solution for your
9527 school, including central infrastructure server, workstations, thin
9528 client servers and diskless workstations. A nice touch added
9529 yesterday is RDP support on the thin client servers, for windows
9530 clients to get a Linux desktop on request.
</p
>
9535 <title>Some notes on Flash in Debian and Debian Edu
</title>
9536 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
9537 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
9538 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
9539 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
9540 popularity-contest numbers
</a
>, the adobe-flashplugin package the
9541 second most popular used package that is missing in Debian. The sixth
9542 most popular is flashplayer-mozilla. This is a clear indication that
9543 working flash is important for Debian users. Around
10 percent of the
9544 users submitting data to popcon.debian.org have this package
9545 installed.
</p
>
9547 <p
>In the report written by Lars Risan in August
2008
9548 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
9549 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9550 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
9551 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
9552 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
9553 web sites require Flash to work, and lacking working Flash support in
9554 the web browser and the problems with installing it was perceived as a
9555 good reason to stay with Windows.
</p
>
9557 <p
>I once saw a funny and sad comment in a web forum, where Linux was
9558 said to be the retarded cousin that did not really understand
9559 everything you told him but could work fairly well. This was a
9560 comment regarding the problems Linux have with proprietary formats and
9561 non-standard web pages, and is sad because it exposes a fairly common
9562 understanding of whose fault it is if web pages that only work in for
9563 example Internet Explorer
6 fail to work on Firefox, and funny because
9564 it explain very well how annoying it is for users when Linux
9565 distributions do not work with the documents they receive or the web
9566 pages they want to visit.
</p
>
9568 <p
>This is part of the reason why I believe it is important for Debian
9569 and Debian Edu to have a well working Flash implementation in the
9570 distribution, to get at least popular sites as Youtube and Google
9571 Video to working out of the box. For Squeeze, Debian have the chance
9572 to include the latest version of Gnash that will make this happen, as
9573 the new release
0.8.8 was published a few weeks ago and is resting in
9574 unstable. The new version work with more sites that version
0.8.7.
9575 The Gnash maintainers have asked for a freeze exception, but the
9576 release team have not had time to reply to it yet. I hope they agree
9577 with me that Flash is important for the Debian desktop users, and thus
9578 accept the new package into Squeeze.
</p
>
9583 <title>Circular package dependencies harms apt recovery
</title>
9584 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9585 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9586 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9587 <description><p
>I discovered this while doing
9588 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9589 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9590 in Debian still got circular dependencies, and it is often claimed
9591 that apt and aptitude should be able to handle this just fine, but
9592 some times these dependency loops causes apt to fail.
</p
>
9594 <p
>An example is from todays
9595 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9596 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9597 causes perl-modules to fail to upgrade. The cause is simple. If a
9598 package fail to unpack, then only part of packages with the circular
9599 dependency might end up being unpacked when unpacking aborts, and the
9600 ones already unpacked will fail to configure in the recovery phase
9601 because its dependencies are unavailable.
</p
>
9603 <p
>In this log, the problem manifest itself with this error:
</p
>
9605 <blockquote
><pre
>
9606 dpkg: dependency problems prevent configuration of perl-modules:
9607 perl-modules depends on perl (
>=
5.10.1-
1); however:
9608 Version of perl on system is
5.10.0-
19lenny
2.
9609 dpkg: error processing perl-modules (--configure):
9610 dependency problems - leaving unconfigured
9611 </pre
></blockquote
>
9613 <p
>The perl/perl-modules circular dependency is already
9614 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9615 hopefully be solved as soon as possible, but it is not the only one,
9616 and each one of these loops in the dependency tree can cause similar
9617 failures. Of course, they only occur when there are bugs in other
9618 packages causing the unpacking to fail, but it is rather nasty when
9619 the failure of one package causes the problem to become worse because
9620 of dependency loops.
</p
>
9623 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9624 tireless effort by Bill Allombert
</a
>, the number of circular
9626 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9627 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9629 <p
>Todays testing also exposed a bug in
9630 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9631 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9632 apt-get and aptitude, the latter possibly caused by some circular
9633 dependency. Reported both to BTS to try to get someone to look at
9639 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9640 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9642 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9643 <description><p
>This is a
9644 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9646 <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
9648 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9649 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9651 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9652 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9653 and dhcp3-server-ldap in Debian use the LDAP server. The two
9654 implementations are quite different in how they use LDAP.
</p
>
9656 To get this information, I started slapd with debugging enabled and
9657 dumped the debug output to a file to get the LDAP searches performed
9658 on a Debian Edu main-server. Here is a summary.
9660 <p
><strong
>powerdns
</strong
></p
>
9662 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9663 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9666 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9667 One
"strict
" mode where the forward and reverse DNS lookups are done
9668 using the same LDAP objects, and a
"tree
" mode where the forward and
9669 reverse entries are in two different subtrees in LDAP with a structure
9670 based on the DNS names, as in tjener.intern and
9671 2.2.0.10.in-addr.arpa.
</p
>
9673 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9674 base, and uses a
"base
" scoped search for the DNS name by adding
9675 "dc=tjener,dc=intern,
" to the base with a filter for
9676 "(associateddomain=tjener.intern)
" for the forward entry and
9677 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9678 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9679 forward entries, it is looking for attributes named dnsttl, arecord,
9680 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9681 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9682 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9683 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9684 spfrecord and modifytimestamp. For reverse entries it is looking for
9685 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9686 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9687 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9688 ldapsearch commands could look like this:
</p
>
9690 <blockquote
><pre
>
9691 ldapsearch -h ldap \
9692 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9693 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9694 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9695 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9696 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9697 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9699 ldapsearch -h ldap \
9700 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9701 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9702 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9703 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9704 srvrecord naptrrecord modifytimestamp
9705 </pre
></blockquote
>
9707 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9708 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9709 example LDAP objects used there. In addition to these objects, the
9710 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9711 also exist.
</p
>
9713 <blockquote
><pre
>
9714 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9716 objectclass: dnsdomain
9717 objectclass: domainrelatedobject
9720 associateddomain: tjener.intern
9722 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9724 objectclass: dnsdomain2
9725 objectclass: domainrelatedobject
9727 ptrrecord: tjener.intern
9728 associateddomain:
2.2.0.10.in-addr.arpa
9729 </pre
></blockquote
>
9731 <p
>In strict mode, the server behaves differently. When looking for
9732 forward DNS entries, it is doing a
"subtree
" scoped search with the
9733 same base as in the tree mode for a object with filter
9734 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9735 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9736 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9737 naptrrecord and modifytimestamp. For reverse entires it also do a
9738 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9739 and the requested attributes are associateddomain, dnsttl and
9740 modifytimestamp. In short, in strict mode the objects with ptrrecord
9741 go away, and the arecord attribute in the forward object is used
9744 <p
>The forward and reverse searches can be simulated using ldapsearch
9745 like this:
</p
>
9747 <blockquote
><pre
>
9748 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9749 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9750 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9751 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9752 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9753 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9755 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9756 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9757 </pre
></blockquote
>
9759 <p
>In addition to the forward and reverse searches , there is also a
9760 search for SOA records, which behave similar to the forward and
9761 reverse lookups.
</p
>
9763 <p
>A thing to note with the PowerDNS behaviour is that it do not
9764 specify any objectclass names, and instead look for the attributes it
9765 need to generate a DNS reply. This make it able to work with any
9766 objectclass that provide the needed attributes.
</p
>
9768 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9769 dnsdomain2 schemas. The latter is used for reverse entries like
9770 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9772 <p
>In Debian Edu, we have created DNS objects using the object classes
9773 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9774 attributes) and domainrelatedobject (for associatedDomain). The use
9775 of structural object classes make it impossible to combine these
9776 classes with the object classes used by DHCP.
</p
>
9778 <p
>There are other schemas that could be used too, for example the
9779 dnszone structural object class used by Gosa and bind-sdb for the DNS
9780 attributes combined with the domainrelatedobject object class, but in
9781 this case some unused attributes would have to be included as well
9782 (zonename and relativedomainname).
</p
>
9784 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9785 mode and not use any of the existing objectclasses (dnsdomain,
9786 dnsdomain2 and dnszone) when one want to combine the DNS information
9787 with DHCP information, and instead create a auxiliary object class
9788 defined something like this (using the attributes defined for
9789 dnsdomain and dnsdomain2 or dnszone):
</p
>
9791 <blockquote
><pre
>
9792 objectclass ( some-oid NAME
'dnsDomainAux
'
9795 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9796 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9797 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9798 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9799 A6Record $ DNAMERecord
9801 </pre
></blockquote
>
9803 <p
>This will allow any object to become a DNS entry when combined with
9804 the domainrelatedobject object class, and allow any entity to include
9805 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9806 developers asking for their view on this schema and if they are
9807 interested in providing such schema with PowerDNS, and I hope my
9808 message will be accepted into their mailing list soon.
</p
>
9810 <p
><strong
>ISC dhcp
</strong
></p
>
9812 <p
>The DHCP server searches for specific objectclass and requests all
9813 the object attributes, and then uses the attributes it want. This
9814 make it harder to figure out exactly what attributes are used, but
9815 thanks to the working example in Debian Edu I can at least get an idea
9816 what is needed without having to read the source code.
</p
>
9818 <p
>In the DHCP server configuration, the LDAP base to use and the
9819 search filter to use to locate the correct dhcpServer entity is
9820 stored. These are the relevant entries from
9821 /etc/dhcp3/dhcpd.conf:
</p
>
9823 <blockquote
><pre
>
9824 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
9825 ldap-dhcp-server-cn
"dhcp
";
9826 </pre
></blockquote
>
9828 <p
>The DHCP server uses this information to nest all the DHCP
9829 configuration it need. The cn
"dhcp
" is located using the given LDAP
9830 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
9831 search result is this entry:
</p
>
9833 <blockquote
><pre
>
9834 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
9837 objectClass: dhcpServer
9838 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9839 </pre
></blockquote
>
9841 <p
>The content of the dhcpServiceDN attribute is next used to locate the
9842 subtree with DHCP configuration. The DHCP configuration subtree base
9843 is located using a base scope search with base
"cn=DHCP
9844 Config,dc=skole,dc=skolelinux,dc=no
" and filter
9845 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
9846 The search result is this entry:
</p
>
9848 <blockquote
><pre
>
9849 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9852 objectClass: dhcpService
9853 objectClass: dhcpOptions
9854 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
9855 dhcpStatements: ddns-update-style none
9856 dhcpStatements: authoritative
9857 dhcpOption: smtp-server code
69 = array of ip-address
9858 dhcpOption: www-server code
72 = array of ip-address
9859 dhcpOption: wpad-url code
252 = text
9860 </pre
></blockquote
>
9862 <p
>Next, the entire subtree is processed, one level at the time. When
9863 all the DHCP configuration is loaded, it is ready to receive requests.
9864 The subtree in Debian Edu contain objects with object classes
9865 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
9866 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
9867 and information about netmasks, dynamic range etc. Leaving out the
9868 details here because it is not relevant for the focus of my
9869 investigation, which is to see if it is possible to merge dns and dhcp
9870 related computer objects.
</p
>
9872 <p
>When a DHCP request come in, LDAP is searched for the MAC address
9873 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
9874 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
9875 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
9876 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
9879 <blockquote
><pre
>
9880 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9883 objectClass: dhcpHost
9884 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9885 dhcpStatements: fixed-address hostname
9886 </pre
></blockquote
>
9888 <p
>There is less flexiblity in the way LDAP searches are done here.
9889 The object classes need to have fixed names, and the configuration
9890 need to be stored in a fairly specific LDAP structure. On the
9891 positive side, the invidiual dhcpHost entires can be anywhere without
9892 the DN pointed to by the dhcpServer entries. The latter should make
9893 it possible to group all host entries in a subtree next to the
9894 configuration entries, and this subtree can also be shared with the
9895 DNS server if the schema proposed above is combined with the dhcpHost
9896 structural object class.
9898 <p
><strong
>Conclusion
</strong
></p
>
9900 <p
>The PowerDNS implementation seem to be very flexible when it come
9901 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
9902 come to the the LDAP structure, the
"strict
" mode is very flexible,
9903 allowing DNS objects to be stored anywhere under the base cn specified
9904 in the configuration.
</p
>
9906 <p
>The DHCP implementation on the other hand is very inflexible, both
9907 regarding which LDAP schemas to use and which LDAP structure to use.
9908 I guess one could implement ones own schema, as long as the
9909 objectclasses and attributes have the names used, but this do not
9910 really help when the DHCP subtree need to have a fairly fixed
9911 structure.
</p
>
9913 <p
>Based on the observed behaviour, I suspect a LDAP structure like
9914 this might work for Debian Edu:
</p
>
9916 <blockquote
><pre
>
9918 cn=machine-info (dhcpService) - dhcpServiceDN points here
9919 cn=dhcp (dhcpServer)
9920 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
9921 cn=
10.0.2.0 (dhcpSubnet)
9922 cn=group1 (dhcpGroup/dhcpOptions)
9923 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
9924 cn=
192.168.0.0 (dhcpSubnet)
9925 cn=group1 (dhcpGroup/dhcpOptions)
9926 ou=machines - PowerDNS base points here
9927 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
9928 </pre
></blockquote
>
9930 <P
>This is not tested yet. If the DHCP server require the dhcpHost
9931 entries to be in the dhcpGroup subtrees, the entries can be stored
9932 there instead of a common machines subtree, and the PowerDNS base
9933 would have to be moved one level up to the machine-info subtree.
</p
>
9935 <p
>The combined object under the machines subtree would look something
9936 like this:
</p
>
9938 <blockquote
><pre
>
9939 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
9942 objectClass: dhcpHost
9943 objectclass: domainrelatedobject
9944 objectclass: dnsDomainAux
9945 associateddomain: hostname.intern
9946 arecord:
10.11.12.13
9947 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
9948 dhcpStatements: fixed-address hostname.intern
9949 </pre
></blockquote
>
9951 </p
>One could even add the LTSP configuration associated with a given
9952 machine, as long as the required attributes are available in a
9953 auxiliary object class.
</p
>
9958 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
9959 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
9960 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
9961 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
9962 <description><p
>For a while now, I have wanted to find a way to change the DNS and
9963 DHCP services in Debian Edu to use the same LDAP objects for a given
9964 computer, to avoid the possibility of having a inconsistent state for
9965 a computer in LDAP (as in DHCP but no DNS entry or the other way
9966 around) and make it easier to add computers to LDAP.
</p
>
9968 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
9969 information finally found a solution that seem to work.
</p
>
9971 <p
>The old setup required three LDAP objects for a given computer.
9972 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
9973 we switch powerdns to use its strict LDAP method (ldap-method=strict
9974 in pdns-debian-edu.conf), the forward and reverse DNS entries are
9975 merged into one while making it impossible to transfer the reverse map
9976 to a slave DNS server.
</p
>
9978 <p
>If we also replace the object class used to get the DNS related
9979 attributes to one allowing these attributes to be combined with the
9980 dhcphost object class, we can merge the DNS and DHCP entries into one.
9981 I
've written such object class in the dnsdomainaux.schema file (need
9982 proper OIDs, but that is a minor issue), and tested the setup. It
9983 seem to work.
</p
>
9985 <p
>With this test setup in place, we can get away with one LDAP object
9986 for both DNS and DHCP, and even the LTSP configuration I suggested in
9987 an earlier email. The combined LDAP object will look something like
9990 <blockquote
><pre
>
9991 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
9993 objectClass: dhcphost
9994 objectclass: domainrelatedobject
9995 objectclass: dnsdomainaux
9996 associateddomain: hostname.intern
9997 arecord:
10.11.12.13
9998 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
9999 dhcpstatements: fixed-address hostname
10001 </pre
></blockquote
>
10003 <p
>The DNS server uses the associateddomain and arecord entries, while
10004 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10005 before asking DNS to resolve the fixed-adddress. LTSP will use
10006 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
10008 <p
>I am not yet sure if I can get the DHCP server to look for its
10009 dhcphost in a different location, to allow us to put the objects
10010 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
10011 that. If I can
't figure out a way to do that, we can still get rid of
10012 the hosts subtree and move all its content into the DHCP Config tree
10013 (which probably should be renamed to be more related to the new
10014 content. I suspect cn=dnsdhcp,ou=services or something like that
10015 might be a good place to put it.
</p
>
10017 <p
>If you want to help out with implementing this for Debian Edu,
10018 please contact us on debian-edu@lists.debian.org.
</p
>
10023 <title>Idea for storing LTSP configuration in LDAP
</title>
10024 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
10025 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
10026 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
10027 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
10028 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10029 clients, and that this can be used to fetch configuration from LDAP if
10030 Debian Edu choose to store configuration there.
</p
>
10032 <p
>Armed with this information, I got inspired and wrote a test module
10033 to get configuration from LDAP. The idea is to look up the MAC
10034 address of the client in LDAP, and look for attributes on the form
10035 ltspconfigsetting=value, and use this to export SETTING=value to the
10036 LTSP clients.
</p
>
10038 <p
>The goal is to be able to store the LTSP configuration attributes
10039 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
10040 allowing us to store all information about a computer in one place.
</p
>
10042 <p
>This is a untested draft implementation, and I welcome feedback on
10043 this approach. A real LDAP schema for the ltspClientAux objectclass
10044 need to be written. Comments, suggestions, etc?
</p
>
10046 <blockquote
><pre
>
10047 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10049 # Fetch LTSP client settings from LDAP based on MAC address
10051 # Uses ethernet address as stored in the dhcpHost objectclass using
10052 # the dhcpHWAddress attribute or ethernet address stored in the
10053 # ieee802Device objectclass with the macAddress attribute.
10055 # This module is written to be schema agnostic, and only depend on the
10056 # existence of attribute names.
10058 # The LTSP configuration variables are saved directly using a
10059 # ltspConfig prefix and uppercasing the rest of the attribute name.
10060 # To set the SERVER variable, set the ltspConfigServer attribute.
10062 # Some LDAP schema should be created with all the relevant
10063 # configuration settings. Something like this should work:
10065 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
10068 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10070 LDAPSERVER=$(debian-edu-ldapserver)
10071 if [
"$LDAPSERVER
" ] ; then
10072 LDAPBASE=$(debian-edu-ldapserver -b)
10073 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
10074 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
10075 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
10076 grep
'^ltspConfig
' | while read attr value ; do
10077 # Remove prefix and convert to upper case
10078 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
10079 # bass value on to clients
10080 eval
"$attr=$value; export $attr
"
10084 </pre
></blockquote
>
10086 <p
>I
'm not sure this shell construction will work, because I suspect
10087 the while block might end up in a subshell causing the variables set
10088 there to not show up in ltsp-config, but if that is the case I am sure
10089 the code can be restructured to make sure the variables are passed on.
10090 I expect that can be solved with some testing. :)
</p
>
10092 <p
>If you want to help out with implementing this for Debian Edu,
10093 please contact us on debian-edu@lists.debian.org.
</p
>
10095 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
10096 configuration in LDAP that was created around year
2000 by
10097 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
10098 Xperience, Inc.,
2000</a
>. I found its
10099 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
10100 personal home page over at redhat.com.
</p
>
10105 <title>jXplorer, a very nice LDAP GUI
</title>
10106 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
10107 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
10108 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
10109 <description><p
>Since
10110 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
10111 last post
</a
> about available LDAP tools in Debian, I was told about a
10112 LDAP GUI that is even better than luma. The java application
10113 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
10114 moving LDAP objects and subtrees using drag-and-drop, and can
10115 authenticate using Kerberos. I have only tested the Kerberos
10116 authentication, but do not have a LDAP setup allowing me to rewrite
10117 LDAP with my test user yet. It is
10118 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
10119 Debian
</a
> testing and unstable at the moment. The only problem I
10120 have with it is how it handle errors. If something go wrong, its
10121 non-intuitive behaviour require me to go through some query work list
10122 and remove the failing query. Nothing big, but very annoying.
</p
>
10127 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
10128 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
10129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
10130 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
10131 <description><p
>Here is a short update on my
<a
10132 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
10133 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
10134 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
10135 not reporting the status for KDE, because the upgrade crashes when
10136 aptitude try because of missing conflicts
10137 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
10138 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
10140 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
10141 complete list of the installed packages. Based on this I see these
10142 differences when I did a test run today. As usual, I do not really
10143 know what the correct set of packages would be, but thought it best to
10144 publish the difference.
</p
>
10146 <p
>Installed using apt-get, missing with aptitude
</p
>
10148 <blockquote
><p
>
10149 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
10150 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
10151 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10152 libgtksourceview-common libpt-
1.10.10-plugins-alsa
10153 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10154 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10155 python-
4suite-xml python-eggtrayicon python-gtkhtml2
10156 python-gtkmozembed svgalibg1 xserver-xephyr zip
10157 </p
></blockquote
>
10159 <p
>Installed using apt-get, removed with aptitude
</p
>
10161 <blockquote
><p
>
10162 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10163 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10164 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
10165 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
10166 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
10167 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
10168 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
10169 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
10170 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
10171 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
10172 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
10173 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
10174 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10175 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
10176 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10177 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
10178 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
10179 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10180 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10181 mysql-common swfdec-gnome totem-gstreamer wodim
10182 </p
></blockquote
>
10184 <p
>Installed using aptitude, missing with apt-get
</p
>
10186 <blockquote
><p
>
10187 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10188 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10189 xserver-xorg-input-all xserver-xorg-input-evdev
10190 xserver-xorg-input-kbd xserver-xorg-input-mouse
10191 xserver-xorg-input-synaptics xserver-xorg-video-all
10192 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10193 xserver-xorg-video-chips xserver-xorg-video-cirrus
10194 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10195 xserver-xorg-video-glint xserver-xorg-video-i128
10196 xserver-xorg-video-i740 xserver-xorg-video-mach64
10197 xserver-xorg-video-mga xserver-xorg-video-neomagic
10198 xserver-xorg-video-nouveau xserver-xorg-video-nv
10199 xserver-xorg-video-r128 xserver-xorg-video-radeon
10200 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10201 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10202 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10203 xserver-xorg-video-sis xserver-xorg-video-sisusb
10204 xserver-xorg-video-tdfx xserver-xorg-video-tga
10205 xserver-xorg-video-trident xserver-xorg-video-tseng
10206 xserver-xorg-video-vesa xserver-xorg-video-vmware
10207 xserver-xorg-video-voodoo
10208 </p
></blockquote
>
10210 <p
>Installed using aptitude, removed with apt-get
</p
>
10212 <blockquote
><p
>
10213 deskbar-applet xserver-xorg xserver-xorg-core
10214 xserver-xorg-input-wacom xserver-xorg-video-intel
10215 xserver-xorg-video-openchrome
10216 </p
></blockquote
>
10218 <p
>I was told on IRC that the xorg-xserver package was
10219 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
10220 in git
</a
> today to try to get apt-get to not remove xorg completely.
10221 No idea when it hits Squeeze, but when it does I hope it will reduce
10222 the difference somewhat.
10227 <title>LUMA, a very nice LDAP GUI
</title>
10228 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
10229 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
10230 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
10231 <description><p
>The last few days I have been looking into the status of the LDAP
10232 directory in Debian Edu, and in the process I started to miss a GUI
10233 tool to browse the LDAP tree. The only one I was able to find in
10234 Debian/Squeeze and Lenny is
10235 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
10236 be a great tool to get a overview of the current LDAP directory
10237 populated by default in Skolelinux. Thanks to it, I have been able to
10238 find empty and obsolete subtrees, misplaced objects and duplicate
10239 objects. It will be installed by default in Debian/Squeeze. If you
10240 are working with LDAP, give it a go. :)
</p
>
10242 <p
>I did notice one problem with it I have not had time to report to
10243 the BTS yet. There is no .desktop file in the package, so the tool do
10244 not show up in the Gnome and KDE menus, but only deep down in in the
10245 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10246 released.
</p
>
10248 <p
>I have not yet been able to get it to modify the tree yet. I would
10249 like to move objects and remove subtrees directly in the GUI, but have
10250 not found a way to do that with LUMA yet. So in the mean time, I use
10251 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
10253 <p
>If you have tips on other GUI tools for LDAP that might be useful
10254 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
10256 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
10257 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
10258 useful GUI alternative. It seem like a good tool, but is unmaintained
10259 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10260 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
10265 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
10266 <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>
10267 <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>
10268 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
10269 <description><p
>A while back, I
10270 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
10271 about the fact
</a
> that it is not possible with the provided schemas
10272 for storing DNS and DHCP information in LDAP to combine the two sets
10273 of information into one LDAP object representing a computer.
</p
>
10275 <p
>In the mean time, I discovered that a simple fix would be to make
10276 the dhcpHost object class auxiliary, to allow it to be combined with
10277 the dNSDomain object class, and thus forming one object for one
10278 computer when storing both DHCP and DNS information in LDAP.
</p
>
10280 <p
>If I understand this correctly, it is not safe to do this change
10281 without also changing the assigned number for the object class, and I
10282 do not know enough about LDAP schema design to do that properly for
10283 Debian Edu.
</p
>
10285 <p
>Anyway, for future reference, this is how I believe we could change
10287 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
10288 schema
</a
> to solve at least part of the problem with the LDAP schemas
10289 available today from IETF.
</p
>
10292 --- dhcp.schema (revision
65192)
10293 +++ dhcp.schema (working copy)
10294 @@ -
376,
7 +
376,
7 @@
10295 objectclass (
2.16.840.1.113719.1.203.6.6
10296 NAME
'dhcpHost
'
10297 DESC
'This represents information about a particular client
'
10299 + SUP top AUXILIARY
10301 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10302 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
10305 <p
>I very much welcome clues on how to do this properly for Debian
10306 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10307 package, and should thus be free to rewrite it as we see fit.
</p
>
10309 <p
>If you want to help out with implementing this for Debian Edu,
10310 please contact us on debian-edu@lists.debian.org.
</p
>
10315 <title>Calling tasksel like the installer, while still getting useful output
</title>
10316 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
10317 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
10318 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
10319 <description><p
>A few times I have had the need to simulate the way tasksel
10320 installs packages during the normal debian-installer run. Until now,
10321 I have ended up letting tasksel do the work, with the annoying problem
10322 of not getting any feedback at all when something fails (like a
10323 conffile question from dpkg or a download that fails), using code like
10326 <blockquote
><pre
>
10327 export DEBIAN_FRONTEND=noninteractive
10328 tasksel --new-install
10329 </pre
></blockquote
>
10331 This would invoke tasksel, let its automatic task selection pick the
10332 tasks to install, and continue to install the requested tasks without
10333 any output what so ever.
10335 Recently I revisited this problem while working on the automatic
10336 package upgrade testing, because tasksel would some times hang without
10337 any useful feedback, and I want to see what is going on when it
10338 happen. Then it occured to me, I can parse the output from tasksel
10339 when asked to run in test mode, and use that aptitude command line
10340 printed by tasksel then to simulate the tasksel run. I ended up using
10343 <blockquote
><pre
>
10344 export DEBIAN_FRONTEND=noninteractive
10345 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
10347 </pre
></blockquote
>
10349 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
10350 --without-recommends -o APT::Install-Recommends=no -y install
10351 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10352 ~pimportant
</tt
>", which will install the gnome desktop task, the
10353 laptop task and all packages with priority standard , required and
10354 important, just like tasksel would have done it during
10355 installation.
</p
>
10357 <p
>A better approach is probably to extend tasksel to be able to
10358 install packages without using debconf-apt-progress, for use cases
10359 like this.
</p
>
10364 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
10365 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
10366 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
10367 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
10368 <description><p
>My
10369 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
10370 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
10371 finally made the upgrade logs available from
10372 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
10373 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10374 apt and aptitude, and found their differences interesting. This time
10375 I will only focus on their removal plans.
</p
>
10377 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
10378 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
10379 surprising part is that it want to remove xorg and all
10380 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10381 sure why. When asking aptitude to do the same, it want to remove
129
10382 packages, but most of them are library packages I suspect are no
10383 longer needed. Both of them want to remove bluetooth packages, which
10384 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
10386 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
10387 which seem like a bad idea and xorg the same way as with Gnome. Asking
10388 aptitude for the same, it wants to remove
192 packages, none which are
10389 too surprising.
</p
>
10391 <p
>I guess the removal of xorg during upgrades should be investigated
10392 and avoided, and perhaps others as well. Here are the complete list
10393 of planned removals. The complete logs is available from the URL
10394 above. Note if you want to repeat these tests, that the upgrade test
10395 for kde+apt-get hung in the tasksel setup because of dpkg asking
10396 conffile questions. No idea why. I worked around it by using
10397 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
10398 continue.
</p
>
10400 <p
><b
>apt-get gnome
72</b
>
10401 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
10402 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10403 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
10404 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10405 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10406 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10407 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10408 xserver-xorg-input-kbd xserver-xorg-input-mouse
10409 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10410 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10411 xserver-xorg-video-ati xserver-xorg-video-chips
10412 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10413 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10414 xserver-xorg-video-glint xserver-xorg-video-i128
10415 xserver-xorg-video-i740 xserver-xorg-video-imstt
10416 xserver-xorg-video-intel xserver-xorg-video-mach64
10417 xserver-xorg-video-mga xserver-xorg-video-neomagic
10418 xserver-xorg-video-nsc xserver-xorg-video-nv
10419 xserver-xorg-video-openchrome xserver-xorg-video-r128
10420 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10421 xserver-xorg-video-rendition xserver-xorg-video-s3
10422 xserver-xorg-video-s3virge xserver-xorg-video-savage
10423 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10424 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10425 xserver-xorg-video-tga xserver-xorg-video-trident
10426 xserver-xorg-video-tseng xserver-xorg-video-v4l
10427 xserver-xorg-video-vesa xserver-xorg-video-vga
10428 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
10429 xulrunner-
1.9-gnome-support
</p
>
10431 <p
><b
>aptitude gnome
129</b
>
10433 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
10434 djvulibre-desktop finger gnome-app-install gnome-mount
10435 gnome-network-admin gnome-spell gnome-vfs-obexftp
10436 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10437 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10438 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10439 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
10440 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
10441 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
10442 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
10443 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
10444 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
10445 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
10446 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
10447 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
10448 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10449 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
10450 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
10451 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
10452 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
10453 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
10454 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10455 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10456 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10457 openoffice.org-writer2latex openssl-blacklist p7zip
10458 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
10459 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10460 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10461 swfdec-mozilla totem-gstreamer update-manager wodim
10462 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10463 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10466 <p
><b
>apt-get kde
82</b
>
10468 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10469 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10470 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10471 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10472 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10473 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10474 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10475 xserver-xorg-input-kbd xserver-xorg-input-mouse
10476 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10477 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10478 xserver-xorg-video-ati xserver-xorg-video-chips
10479 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10480 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10481 xserver-xorg-video-glint xserver-xorg-video-i128
10482 xserver-xorg-video-i740 xserver-xorg-video-imstt
10483 xserver-xorg-video-intel xserver-xorg-video-mach64
10484 xserver-xorg-video-mga xserver-xorg-video-neomagic
10485 xserver-xorg-video-nsc xserver-xorg-video-nv
10486 xserver-xorg-video-openchrome xserver-xorg-video-r128
10487 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10488 xserver-xorg-video-rendition xserver-xorg-video-s3
10489 xserver-xorg-video-s3virge xserver-xorg-video-savage
10490 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10491 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10492 xserver-xorg-video-tga xserver-xorg-video-trident
10493 xserver-xorg-video-tseng xserver-xorg-video-v4l
10494 xserver-xorg-video-vesa xserver-xorg-video-vga
10495 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
10497 <p
><b
>aptitude kde
192</b
>
10498 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
10499 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10500 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10501 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10502 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10503 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10504 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10505 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10506 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10507 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10508 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10509 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10510 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10511 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10512 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10513 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10514 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10515 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10516 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
10517 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10518 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10519 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
10520 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10521 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10522 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10523 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10524 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10525 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
10526 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
10527 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10528 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10529 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10530 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10531 texlive-common texlive-doc-base texlive-fonts-recommended
10532 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10533 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10534 xulrunner-
1.9</p
>
10540 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
10541 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
10542 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
10543 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
10544 <description><p
>The last few days I have done some upgrade testing in Debian, to
10545 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10546 have been discovered and reported in the process
10547 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
10548 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
10549 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
10550 kdebase-workspace-data), and to get a more regular testing going on, I
10551 am working on a script to automate the test.
</p
>
10553 <p
>The idea is to create a Lenny chroot and use tasksel to install a
10554 Gnome or KDE desktop installation inside the chroot before upgrading
10555 it. To ensure no services are started in the chroot, a policy-rc.d
10556 script is inserted. To make sure tasksel believe it is to install a
10557 desktop on a laptop, the tasksel tests are replaced in the chroot
10558 (only acceptable because this is a throw-away chroot).
</p
>
10560 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10561 currently always fail because udev refuses to upgrade with the kernel
10562 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10563 is created. The bug report
10564 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
10565 this problem do not trigger in a chroot, but I touch the file anyway
10566 to make sure the upgrade go well. Testing on virtual and real
10567 hardware have failed me because of udev so far, and creating this file
10568 do the trick in such settings anyway. This is a
10569 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
10570 issue
</a
> and the current udev behaviour is intended by the udev
10571 maintainer because he lack the resources to rewrite udev to keep
10572 working with old kernels or something like that. I really wish the
10573 udev upstream would keep udev backwards compatible, to avoid such
10574 upgrade problem, but given that they fail to do so, I guess
10575 documenting the way out of this mess is the best option we got for
10576 Debian Squeeze.
</p
>
10578 <p
>Anyway, back to the task at hand, testing upgrades. This test
10579 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10582 <blockquote
><pre
>
10586 if [
"$
1" ] ; then
10595 exec
&lt; /dev/null
10597 mirror=http://ftp.skolelinux.org/debian
10598 tmpdir=chroot-$from-upgrade-$to-$desktop
10600 debootstrap $from $tmpdir $mirror
10601 chroot $tmpdir aptitude update
10602 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10606 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10608 umount $tmpdir/proc
10610 mount -t proc proc $tmpdir/proc
10611 # Make sure proc is unmounted also on failure
10612 trap exit_cleanup EXIT INT
10614 chroot $tmpdir aptitude -y install debconf-utils
10616 # Make sure tasksel autoselection trigger. It need the test scripts
10617 # to return the correct answers.
10618 echo tasksel tasksel/desktop multiselect $desktop | \
10619 chroot $tmpdir debconf-set-selections
10621 # Include the desktop and laptop task
10622 for test in desktop laptop ; do
10623 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10627 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10630 DEBIAN_FRONTEND=noninteractive
10631 DEBIAN_PRIORITY=critical
10632 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10633 chroot $tmpdir tasksel --new-install
10635 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10636 chroot $tmpdir aptitude update
10637 touch $tmpdir/etc/udev/kernel-upgrade
10638 chroot $tmpdir aptitude -y dist-upgrade
10640 </pre
></blockquote
>
10642 <p
>I suspect it would be useful to test upgrades with both apt-get and
10643 with aptitude, but I have not had time to look at how they behave
10644 differently so far. I hope to get a cron job running to do the test
10645 regularly and post the result on the web. The Gnome upgrade currently
10646 work, while the KDE upgrade fail because of the bug in
10647 kdebase-workspace-data
</p
>
10649 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10650 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10651 post, so I will refrain from trying. I can report that for Gnome,
10652 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10653 remove and
1 not upgraded and
1024MB need to be downloaded while for
10654 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10655 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10657 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10658 is able to migrate to dependency based boot sequencing and parallel
10659 booting without a hitch. Was unsure if there were still bugs with
10660 packages failing to clean up their obsolete init.d script during
10661 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10662 packages.
</p
>
10667 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10668 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10669 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10670 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10671 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10672 scripts to migrate (some of) their operations to upstart job while
10673 keeping the init.d for hurd and kfreebsd. The packages with such
10674 needs will need a way to get their init.d scripts to behave
10675 differently when used with sysvinit and with upstart. Because of
10676 this, I had a look at the environment variables set when a init.d
10677 script is running under upstart, and when it is not.
</p
>
10679 <p
>With upstart, I notice these environment variables are set when a
10680 script is started from rcS.d/ (ignoring some irrelevant ones like
10681 COLUMNS):
</p
>
10683 <blockquote
><pre
>
10689 UPSTART_EVENTS=startup
10691 UPSTART_JOB=rc-sysinit
10692 </pre
></blockquote
>
10694 <p
>With sysvinit, these environment variables are set for the same
10697 <blockquote
><pre
>
10698 INIT_VERSION=sysvinit-
2.88
10703 </pre
></blockquote
>
10705 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10706 sysvinit are not set by upstart. Not sure if it is intentional or not
10707 to not be compatible with sysvinit in this regard.
</p
>
10709 <p
>For scripts needing to behave differently when upstart is used,
10710 looking for the UPSTART_JOB environment variable seem to be a good
10716 <title>A manual for standards wars...
</title>
10717 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10718 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10719 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10720 <description><p
>Via the
10721 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10722 of Rob Weir
</a
> I came across the very interesting essay named
10723 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10724 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10725 following the standards wars of today.
</p
>
10730 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10731 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10733 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10734 <description><p
>When using sitesummary at a site to track machines, it is possible
10735 to get a list of the machine types in use thanks to the DMI
10736 information extracted from each machine. The script to do so is
10737 included in the sitesummary package, and here is example output from
10738 the Skolelinux build servers:
</p
>
10740 <blockquote
><pre
>
10741 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10743 Dell Computer Corporation
1
10746 eserver xSeries
345 -[
8670M1X]-
1
10750 </pre
></blockquote
>
10752 <p
>The quality of the report depend on the quality of the DMI tables
10753 provided in each machine. Here there are Intel machines without model
10754 information listed with Intel as vendor and no model, and virtual Xen
10755 machines listed as [no-dmi-info]. One can add -l as a command line
10756 option to list the individual machines.
</p
>
10758 <p
>A larger list is
10759 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10760 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10761 provide the basic sitesummary report publicly. In their report there
10762 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10763 their machines, and as sitesummary is available in both distributions,
10764 it is trivial to get all of them to report to the same central
10765 collector.
</p
>
10770 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10771 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10772 <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>
10773 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10774 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10775 start at boot when an NVidia video card is used is handled. The
10776 problem seem to be that the nvidia X.org driver uses a long time to
10777 initialize, and this duration is longer than kdm is configured to
10780 <p
>I came across two bugs related to this issue,
10781 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10782 against initscripts and passed on to nvidia-glx when it became obvious
10783 that the nvidia drivers were involved, and
10784 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10785 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10787 <p
>To me, it seem that no-one is interested in actually solving the
10788 problem nvidia video card owners experience and make sure the Debian
10789 distribution work out of the box for these users. The nvidia driver
10790 maintainers expect kdm to be set up to wait longer, while kdm expect
10791 the nvidia driver maintainers to fix the driver to start faster, and
10792 while they wait for each other I guess the users end up switching to a
10793 distribution that work for them. I have no idea what the solution is,
10794 but I am pretty sure that waiting for each other is not it.
</p
>
10796 <p
>I wonder why we end up handling bugs this way.
</p
>
10801 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10802 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10803 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10804 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10805 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10806 The feature seem to hold up pretty well, but three fairly serious
10807 issues are known and should be solved:
10809 <p
><ul
>
10811 <li
>The wicd package seen to
10812 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10813 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10814 parallel booting is enabled. No idea why, but the wicd maintainer
10815 seem to be on the case.
</li
>
10817 <li
>The nvidia X driver seem to
10818 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
10819 triggered more easily when parallel booting is in effect. The
10820 maintainer is on the case.
</li
>
10822 <li
>The sysv-rc package fail to properly enable dependency based boot
10823 sequencing (the shutdown is broken) when old file-rc users
10824 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
10825 sysv-rc. One way to solve it would be for file-rc to create
10826 /etc/init.d/.legacy-bootordering, and another is to try to make
10827 sysv-rc more robust. Will investigate some more and probably upload a
10828 workaround in sysv-rc to help those trying to move from file-rc to
10829 sysv-rc get a working shutdown.
</li
>
10831 </ul
></p
>
10833 <p
>All in all not many surprising issues, and all of them seem
10834 solvable before Squeeze is released. In addition to these there are
10835 some packages with bugs in their dependencies and run level settings,
10836 which I expect will be fixed in a reasonable time span.
</p
>
10838 <p
>If you report any problems with dependencies in init.d scripts to
10839 the BTS, please usertag the report to get it to show up at
10840 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10841 list of usertagged bugs related to this
</a
>.
</p
>
10843 <p
>Update: Correct bug number to file-rc issue.
</p
>
10848 <title>More flexible firmware handling in debian-installer
</title>
10849 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
10850 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
10851 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
10852 <description><p
>After a long break from debian-installer development, I finally
10853 found time today to return to the project. Having to spend less time
10854 working dependency based boot in debian, as it is almost complete now,
10855 definitely helped freeing some time.
</p
>
10857 <p
>A while back, I ran into a problem while working on Debian Edu. We
10858 include some firmware packages on the Debian Edu CDs, those needed to
10859 get disk and network controllers working. Without having these
10860 firmware packages available during installation, it is impossible to
10861 install Debian Edu on the given machine, and because our target group
10862 are non-technical people, asking them to provide firmware packages on
10863 an external medium is a support pain. Initially, I expected it to be
10864 enough to include the firmware packages on the CD to get
10865 debian-installer to find and use them. This proved to be wrong.
10866 Next, I hoped it was enough to symlink the relevant firmware packages
10867 to some useful location on the CD (tried /cdrom/ and
10868 /cdrom/firmware/). This also proved to not work, and at this point I
10869 found time to look at the debian-installer code to figure out what was
10870 going to work.
</p
>
10872 <p
>The firmware loading code is in the hw-detect package, and a closer
10873 look revealed that it would only look for firmware packages outside
10874 the installation media, so the CD was never checked for firmware
10875 packages. It would only check USB sticks, floppies and other
10876 "external
" media devices. Today I changed it to also look in the
10877 /cdrom/firmware/ directory on the mounted CD or DVD, which should
10878 solve the problem I ran into with Debian edu. I also changed it to
10879 look in /firmware/, to make sure the installer also find firmware
10880 provided in the initrd when booting the installer via PXE, to allow us
10881 to provide the same feature in the PXE setup included in Debian
10884 <p
>To make sure firmware deb packages with a license questions are not
10885 activated without asking if the license is accepted, I extended
10886 hw-detect to look for preinst scripts in the firmware packages, and
10887 run these before activating the firmware during installation. The
10888 license question is asked using debconf in the preinst, so this should
10889 solve the issue for the firmware packages I have looked at so far.
</p
>
10891 <p
>If you want to discuss the details of these features, please
10892 contact us on debian-boot@lists.debian.org.
</p
>
10897 <title>Parallellized boot is now the default in Debian/unstable
</title>
10898 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
10899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
10900 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
10901 <description><p
>Since this evening, parallel booting is the default in
10902 Debian/unstable for machines using dependency based boot sequencing.
10903 Apparently the testing of concurrent booting has been wider than
10904 expected, if I am to believe the
10905 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10906 on debian-devel@
</a
>, and I concluded a few days ago to move forward
10907 with the feature this weekend, to give us some time to detect any
10908 remaining problems before Squeeze is frozen. If serious problems are
10909 detected, it is simple to change the default back to sequential boot.
10910 The upload of the new sysvinit package also activate a new upstream
10913 More information about
10914 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10915 based boot sequencing
</a
> is available from the Debian wiki. It is
10916 currently possible to disable parallel booting when one run into
10917 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
10919 <blockquote
><pre
>
10921 </pre
></blockquote
>
10923 <p
>If you report any problems with dependencies in init.d scripts to
10924 the BTS, please usertag the report to get it to show up at
10925 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
10926 list of usertagged bugs related to this
</a
>.
</p
>
10931 <title>Sitesummary tip: Listing MAC address of all clients
</title>
10932 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
10933 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
10934 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
10935 <description><p
>In the recent Debian Edu versions, the
10936 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
10937 system
</a
> is used to keep track of the machines in the school
10938 network. Each machine will automatically report its status to the
10939 central server after boot and once per night. The network setup is
10940 also reported, and using this information it is possible to get the
10941 MAC address of all network interfaces in the machines. This is useful
10942 to update the DHCP configuration.
</p
>
10944 <p
>To give some idea how to use sitesummary, here is a one-liner to
10945 ist all MAC addresses of all machines reporting to sitesummary. Run
10946 this on the collector host:
</p
>
10948 <blockquote
><pre
>
10949 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
10950 </pre
></blockquote
>
10952 <p
>This will list all MAC addresses assosiated with all machine, one
10953 line per machine and with space between the MAC addresses.
</p
>
10955 <p
>To allow system administrators easier job at adding static DHCP
10956 addresses for hosts, it would be possible to extend this to fetch
10957 machine information from sitesummary and update the DHCP and DNS
10958 tables in LDAP using this information. Such tool is unfortunately not
10959 written yet.
</p
>
10964 <title>systemd, an interesting alternative to upstart
</title>
10965 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
10966 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
10967 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
10968 <description><p
>The last few days a new boot system called
10969 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
10971 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
10973 to the free software world. I have not yet had time to play around
10974 with it, but it seem to be a very interesting alternative to
10975 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
10976 a good alternative for Debian when we are able to switch to an event
10977 based boot system. Tollef is
10978 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
10979 systemd into Debian, and I look forward to seeing how well it work. I
10980 like the fact that systemd handles init.d scripts with dependency
10981 information natively, allowing them to run in parallel where upstart
10982 at the moment do not.
</p
>
10984 <p
>Unfortunately do systemd have the same problem as upstart regarding
10985 platform support. It only work on recent Linux kernels, and also need
10986 some new kernel features enabled to function properly. This means
10987 kFreeBSD and Hurd ports of Debian will need a port or a different boot
10988 system. Not sure how that will be handled if systemd proves to be the
10989 way forward.
</p
>
10991 <p
>In the mean time, based on the
10992 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
10993 on debian-devel@
</a
> regarding parallel booting in Debian, I have
10994 decided to enable full parallel booting as the default in Debian as
10995 soon as possible (probably this weekend or early next week), to see if
10996 there are any remaining serious bugs in the init.d dependencies. A
10997 new version of the sysvinit package implementing this change is
10998 already in experimental. If all go well, Squeeze will be released
10999 with parallel booting enabled by default.
</p
>
11004 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
11005 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
11006 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
11007 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
11008 <description><p
>These days, the init.d script dependencies in Squeeze are quite
11009 complete, so complete that it is actually possible to run all the
11010 init.d scripts in parallell based on these dependencies. If you want
11011 to test your Squeeze system, make sure
11012 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11013 based boot sequencing
</a
> is enabled, and add this line to
11014 /etc/default/rcS:
</p
>
11016 <blockquote
><pre
>
11017 CONCURRENCY=makefile
11018 </pre
></blockquote
>
11020 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
11021 scripts in parallel using the dependency information stored in
11022 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11023 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11024 to try to start the kdm and gdm scripts as early as possible, and will
11025 start the facilities required by kdm or gdm as early as possible to
11026 make this happen.
</p
>
11028 <p
>Give it a try, and see if you like the result. If some services
11029 fail to start properly, it is most likely because they have incomplete
11030 init.d script dependencies in their startup script (or some of their
11031 dependent scripts have incomplete dependencies). Report bugs and get
11032 the package maintainers to fix it. :)
</p
>
11034 <p
>Running scripts in parallel could be the default in Debian when we
11035 manage to get the init.d script dependencies complete and correct. I
11036 expect we will get there in Squeeze+
1, if we get manage to test and
11037 fix the remaining issues.
</p
>
11039 <p
>If you report any problems with dependencies in init.d scripts to
11040 the BTS, please usertag the report to get it to show up at
11041 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
11042 list of usertagged bugs related to this
</a
>.
</p
>
11047 <title>Debian has switched to dependency based boot sequencing
</title>
11048 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
11049 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
11050 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
11051 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
11052 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
11053 have been migrated to using dependency based boot sequencing. This
11054 conclude work me and others have been doing for the last three days.
11055 It feels great to see this finally part of the default Debian
11056 installation. Now we just need to weed out the last few problems that
11057 are bound to show up, to get everything ready for Squeeze.
</p
>
11059 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
11060 fixing the more fundamental problem of handing the event based
11061 non-predictable kernel in the early boot.
</p
>
11066 <title>Taking over sysvinit development
</title>
11067 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
11068 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
11069 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
11070 <description><p
>After several years of frustration with the lack of activity from
11071 the existing sysvinit upstream developer, I decided a few weeks ago to
11072 take over the package and become the new upstream. The number of
11073 patches to track for the Debian package was becoming a burden, and the
11074 lack of synchronization between the distribution made it hard to keep
11075 the package up to date.
</p
>
11077 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11078 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
11079 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
11080 and Fedora), based on the patches currently in use in these
11081 distributions. We Debian maintainers plan to move to this tarball as
11082 the new upstream as soon as we find time to do the merge. Since the
11083 new tarball was created, we agreed with Werner at SuSe to make a new
11084 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
11085 development there. The project is registered and currently waiting
11086 for approval by the Savannah administrators, and as soon as it is
11087 approved, we will import the old versions from svn and continue
11088 working on the future release.
</p
>
11090 <p
>It is a bit ironic that this is done now, when some of the involved
11091 distributions are moving to upstart as a syvinit replacement.
</p
>
11096 <title>Debian boots quicker and quicker
</title>
11097 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
11098 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
11099 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
11100 <description><p
>I spent Monday and tuesday this week in London with a lot of the
11101 people involved in the boot system on Debian and Ubuntu, to see if we
11102 could find more ways to speed up the boot system. This was an Ubuntu
11104 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
11105 gathering
</a
>. It was quite productive. We also discussed the future
11106 of boot systems, and ways to handle the increasing number of boot
11107 issues introduced by the Linux kernel becoming more and more
11108 asynchronous and event base. The Ubuntu approach using udev and
11109 upstart might be a good way forward. Time will show.
</p
>
11111 <p
>Anyway, there are a few ways at the moment to speed up the boot
11112 process in Debian. All of these should be applied to get a quick
11117 <li
>Use dash as /bin/sh.
</li
>
11119 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
11120 clock is in UTC.
</li
>
11122 <li
>Install and activate the insserv package to enable
11123 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11124 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
11128 These points are based on the Google summer of code work done by
11129 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
11130 Villegas
</a
>.
11132 <p
>Support for makefile-style concurrency during boot was uploaded to
11133 unstable yesterday. When we tested it, we were able to cut
6 seconds
11134 from the boot sequence. It depend on very correct dependency
11135 declaration in all init.d scripts, so I expect us to find edge cases
11136 where the dependences in some scripts are slightly wrong when we start
11137 using this.
</p
>
11139 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11140 introduced by Raphael Geissert today, one that could affect the
11141 startup speed as well. Instead of starting some scripts concurrently
11142 from rcS.d/ and another set of scripts from rc2.d/, it would be
11143 possible to run a of them in the same process. A quick way to test
11144 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
11145 insserv
'. Will need to test if that work. :)
</p
>
11150 <title>BSAs påstander om piratkopiering møter motstand
</title>
11151 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
11152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
11153 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
11154 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
11155 programvareselskapene som Microsoft og Apple, publisert en rapport der
11156 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11157 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11159 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
11160 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
11161 dagene. Et spesielt interessant kommentar fra Sverige,
11162 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
11163 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
11166 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
11167 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11168 företag.
"Man bör nog kanske inte se de här siffrorna som helt
11169 exakta
", säger BSAs Sverigechef John Hugosson.
11170 </blockquote
>
11172 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
11173 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
11174 piracy figures need a shot of reality
</a
> og
<a
11175 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
11176 Copyright Treaty Work?
</a
></p
>
11178 <p
>Fant lenkene via
<a
11179 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
11180 på Slashdot
</a
>.
</p
>
11185 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
11186 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
11187 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
11188 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
11189 <description><p
>Kom over
11190 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
11191 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11192 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11193 jobber til daglig. En rask opptelling forteller meg at vi har
490
11194 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
11195 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
11196 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
11201 <title>Kryptert harddisk - naturligvis
</title>
11202 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
11203 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
11204 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
11205 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
11206 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
11207 når en tar tap av arbeidstid, fortrolige dokumenter,
11208 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11209 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11210 til at jeg har kryptert harddisken på både kontormaskinen og min
11211 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11212 komme på avveie, den første informasjon relatert til jobben min ved
11213 Universitetet i Oslo, og den andre relatert til blant annet
11214 foreningsarbeide. Kryptering av diskene gjør at det er lite
11215 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11216 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11217 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11218 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11219 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11220 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11221 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11222 det er gjort slik jeg gjør det er minimale, og gevinstene er
11223 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11224 maskinen reinstalleres og alt er tapt.
</p
>
11226 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11227 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11228 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11229 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11230 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11231 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11232 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11233 betydelige.
</p
>
11238 <title>Two projects that have improved the quality of free software a lot
</title>
11239 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
11240 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
11241 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
11242 <description><p
>There are two software projects that have had huge influence on the
11243 quality of free software, and I wanted to mention both in case someone
11244 do not yet know them.
</p
>
11246 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
11247 tool to detect and expose errors in the memory handling of programs.
11248 It is easy to use, all one need to do is to run
'valgrind program
',
11249 and it will report any problems on stdout. It is even better if the
11250 program include debug information. With debug information, it is able
11251 to report the source file name and line number where the problem
11252 occurs. It can report things like
'reading past memory block in file
11253 X line N, the memory block was allocated in file Y, line M
', and
11254 'using uninitialised value in control logic
'. This tool has made it
11255 trivial to investigate reproducible crash bugs in programs, and have
11256 reduced the number of this kind of bugs in free software a lot.
11258 <p
>The second one is
11259 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
11260 a source code checker. It is able to process the source of a program
11261 and find problems in the logic without running the program. It
11262 started out as the Stanford Checker and became well known when it was
11263 used to find bugs in the Linux kernel. It is now a commercial tool
11264 and the company behind it is running
11265 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
11266 free software community, where a lot of free software projects get
11267 their source checked for free. Several thousand defects have been
11268 found and fixed so far. It can find errors like
'lock L taken in file
11269 X line N is never released if exiting in line M
', or
'the code in file
11270 Y lines O to P can never be executed
'. The projects included in the
11271 community service project have managed to get rid of a lot of
11272 reliability problems thanks to Coverity.
</p
>
11274 <p
>I believe tools like this, that are able to automatically find
11275 errors in the source, are vital to improve the quality of software and
11276 make sure we can get rid of the crashing and failing software we are
11277 surrounded by today.
</p
>
11282 <title>No patch is not better than a useless patch
</title>
11283 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
11284 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
11285 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
11286 <description><p
>Julien Blache
11287 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
11288 patch is better than a useless patch
</a
>. I completely disagree, as a
11289 patch allow one to discuss a concrete and proposed solution, and also
11290 prove that the issue at hand is important enough for someone to spent
11291 time on fixing it. No patch do not provide any of these positive
11292 properties.
</p
>
11297 <title>Standardize on protocols and formats, not vendors and applications
</title>
11298 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
11299 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
11300 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
11301 <description><p
>Where I work at the University of Oslo, one decision stand out as a
11302 very good one to form a long lived computer infrastructure. It is the
11303 simple one, lost by many in todays computer industry: Standardize on
11304 open network protocols and open exchange/storage formats, not applications.
11305 Applications come and go, while protocols and files tend to stay, and
11306 thus one want to make it easy to change application and vendor, while
11307 avoiding conversion costs and locking users to a specific platform or
11308 application.
</p
>
11310 <p
>This approach make it possible to replace the client applications
11311 independently of the server applications. One can even allow users to
11312 use several different applications as long as they handle the selected
11313 protocol and format. In the normal case, only one client application
11314 is recommended and users only get help if they choose to use this
11315 application, but those that want to deviate from the easy path are not
11316 blocked from doing so.
</p
>
11318 <p
>It also allow us to replace the server side without forcing the
11319 users to replace their applications, and thus allow us to select the
11320 best server implementation at any moment, when scale and resouce
11321 requirements change.
</p
>
11323 <p
>I strongly recommend standardizing - on open network protocols and
11324 open formats, but I would never recommend standardizing on a single
11325 application that do not use open network protocol or open formats.
</p
>
11330 <title>Returning from Skolelinux developer gathering
</title>
11331 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
11332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
11333 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
11334 <description><p
>I
'm sitting on the train going home from this weekends Debian
11335 Edu/Skolelinux development gathering. I got a bit done tuning the
11336 desktop, and looked into the dynamic service location protocol
11337 implementation avahi. It look like it could be useful for us. Almost
11338 30 people participated, and I believe it was a great environment to
11339 get to know the Skolelinux system. Walter Bender, involved in the
11340 development of the Sugar educational platform, presented his stuff and
11341 also helped me improve my OLPC installation. He also showed me that
11342 his Turtle Art application can be used in standalone mode, and we
11343 agreed that I would help getting it packaged for Debian. As a
11344 standalone application it would be great for Debian Edu. We also
11345 tried to get the video conferencing working with two OLPCs, but that
11346 proved to be too hard for us. The application seem to need more work
11347 before it is ready for me. I look forward to getting home and relax
11353 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
11354 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
11355 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
11356 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
11357 <description><p
>The state of standardized LDAP schemas on Linux is far from
11358 optimal. There is RFC
2307 documenting one way to store NIS maps in
11359 LDAP, and a modified version of this normally called RFC
2307bis, with
11360 some modifications to be compatible with Active Directory. The RFC
11361 specification handle the content of a lot of system databases, but do
11362 not handle DNS zones and DHCP configuration.
</p
>
11364 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
11365 we would like to store information about users, SMB clients/hosts,
11366 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11367 and LTSP configuration in LDAP. These objects have a lot in common,
11368 but with the current LDAP schemas it is not possible to have one
11369 object per entity. For example, one need to have at least three LDAP
11370 objects for a given computer, one with the SMB related stuff, one with
11371 DNS information and another with DHCP information. The schemas
11372 provided for DNS and DHCP are impossible to combine into one LDAP
11373 object. In addition, it is impossible to implement quick queries for
11374 netgroup membership, because of the way NIS triples are implemented.
11375 It just do not scale. I believe it is time for a few RFC
11376 specifications to cleam up this mess.
</p
>
11378 <p
>I would like to have one LDAP object representing each computer in
11379 the network, and this object can then keep the SMB (ie host key), DHCP
11380 (mac address/name) and DNS (name/IP address) settings in one place.
11381 It need to be efficently stored to make sure it scale well.
</p
>
11383 <p
>I would also like to have a quick way to map from a user or
11384 computer and to the net group this user or computer is a member.
</p
>
11386 <p
>Active Directory have done a better job than unix heads like myself
11387 in this regard, and the unix side need to catch up. Time to start a
11388 new IETF work group?
</p
>
11393 <title>Endelig er Debian Lenny gitt ut
</title>
11394 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
11395 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
11396 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
11397 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
11398 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
11399 Et langt steg videre for Debian-prosjektet, og en rekke nye
11400 programpakker blir nå tilgjengelig for de av oss som bruker den
11401 stabile utgaven av Debian. Neste steg er nå å få
11402 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
11403 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
11404 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11405 slippes løs på skolene. Takk til alle debian-utviklerne som har
11406 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11407 bootsekvens tilgjengelig i stabil utgave, vha pakken
11408 <tt
>insserv
</tt
>.
</p
>
11413 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
11414 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
11415 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
11416 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
11417 <description><p
>This weekend we had a small developer gathering for Debian Edu in
11418 Oslo. Most of Saturday was used for the general assemly for the
11419 member organization, but the rest of the weekend I used to tune the
11420 LTSP installation. LTSP now work out of the box on the
10-network.
11421 Acer Aspire One proved to be a very nice thin client, with both
11422 screen, mouse and keybard in a small box. Was working on getting the
11423 diskless workstation setup configured out of the box, but did not
11424 finish it before the weekend was up.
</p
>
11426 <p
>Did not find time to look at the
4 VGA cards in one box we got from
11427 the Brazilian group, so that will have to wait for the next
11428 development gathering. Would love to have the Debian Edu installer
11429 automatically detect and configure a multiseat setup when it find one
11430 of these cards.
</p
>
11435 <title>The sorry state of multimedia browser plugins in Debian
</title>
11436 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
11437 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
11438 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
11439 <description><p
>Recently I have spent some time evaluating the multimedia browser
11440 plugins available in Debian Lenny, to see which one we should use by
11441 default in Debian Edu. We need an embedded video playing plugin with
11442 control buttons to pause or stop the video, and capable of streaming
11443 all the multimedia content available on the web. The test results and
11444 notes are available on
11445 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
11446 Debian wiki
</a
>. I was surprised how few of the plugins are able to
11447 fill this need. My personal video player favorite, VLC, has a really
11448 bad plugin which fail on a lot of the test pages. A lot of the MIME
11449 types I would expect to work with any free software player (like
11450 video/ogg), just do not work. And simple formats like the
11451 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
11452 totem and vlc plugins. I hope the situation will improve soon. No
11453 wonder sites use the proprietary Adobe flash to play video.
</p
>
11455 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
11456 be the only one fitting our needs. :/
</p
>