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>Learn to program with Minetest on Debian
</title>
11 <link>http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
13 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
14 <description><p
>A fun way to learn how to program
15 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
16 instructions in the book
17 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
18 with Minecraft
</a
>", which introduces programming in Python to people
19 who like to play with Minecraft. The book uses a Python library to
20 talk to a TCP/IP socket with an API accepting build instructions and
21 providing information about the current players in a Minecraft world.
22 The TCP/IP API was first created for the Minecraft implementation for
23 Raspberry Pi, and has since been ported to some server versions of
24 Minecraft. The book contain recipes for those using Windows, MacOSX
25 and Raspian. But a little known fact is that you can follow the same
26 recipes using the free software construction game
27 <a href=
"https://minetest.org/
">Minetest
</a
>.
</p
>
29 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
30 Minetest module implementing the same API
</a
>, making it possible to
31 use the Python programs coded to talk to Minecraft with Minetest too.
33 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
34 this module
</a
> to Debian two weeks ago, and as soon as it clears the
35 FTP masters NEW queue, learning to program Python with Minetest on
36 Debian will be a simple
'apt install
' away. The Debian package is
37 maintained as part of the Debian Games team, and
38 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
39 packaging rules
</a
> are currently located under
'unfinished
' on
42 <p
>You will most likely need to install several of the Minetest
43 modules in Debian for the examples included with the library to work
44 well, as there are several blocks used by the example scripts that are
45 provided via modules in Minetest. Without the required blocks, a
46 simple stone block is used instead. My initial testing with a analog
47 clock did not get gold arms as instructed in the python library, but
48 instead used stone arms.
</p
>
50 <p
>I tried to find a way to add the API to the desktop version of
51 Minecraft, but were unable to find any working recipes. The
52 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
53 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
54 working with a standalone Minecraft server setup. Are there any
55 options to use with the normal desktop version?
</p
>
57 <p
>As usual, if you use Bitcoin and want to show your support of my
58 activities, please send Bitcoin donations to my address
59 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
64 <title>Time for an official MIME type for patches?
</title>
65 <link>http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
66 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
67 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
68 <description><p
>As part of my involvement in
69 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
70 archive API project
</a
>, I
've been importing a fairly large lump of
71 emails into a test instance of the archive to see how well this would
72 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
73 notmuch email database
</a
>, all public emails sent to me via
74 @lists.debian.org, giving me a set of around
216 000 emails to import.
75 In the process, I had a look at the various attachments included in
76 these emails, to figure out what to do with attachments, and noticed
77 that one of the most common attachment formats do not have
78 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
79 official MIME type
</a
> registered with IANA/IETF. The output from
80 diff, ie the input for patch, is on the top
10 list of formats
81 included in these emails. At the moment people seem to use either
82 text/x-patch or text/x-diff, but neither is officially registered. It
83 would be better if one official MIME type were registered and used
86 <p
>To try to get one official MIME type for these files, I
've brought
88 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
89 media-types mailing list
</a
>. If you are interested in discussion
90 which MIME type to use as the official for patch files, or involved in
91 making software using a MIME type for patches, perhaps you would like
92 to join the discussion?
</p
>
94 <p
>As usual, if you use Bitcoin and want to show your support of my
95 activities, please send Bitcoin donations to my address
96 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
101 <title>Automatic Google Drive sync using grive in Debian
</title>
102 <link>http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
104 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
105 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
106 rescue the remains, I helped set up automatic sync with Google Drive.
107 I did not find any sensible Debian package handling this
108 automatically, so I rebuild the grive2 source from
109 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
110 task and added a autostart desktop entry and a small shell script to
111 run in the background while the user is logged in to do the sync.
112 Here is a sketch of the setup for future reference.
</p
>
114 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
115 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
116 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
117 to start the sync when the user log in:
</p
>
119 <p
><blockquote
><pre
>
121 Name=Google drive autosync
123 Exec=/home/user/bin/grive-sync
124 </pre
></blockquote
></p
>
126 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
127 ~/googledrive/ with the files in Google Drive.
</p
>
129 <p
><blockquote
><pre
>
134 if [
"$syncpid
" ] ; then
138 trap cleanup EXIT INT QUIT
139 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
142 if ! xhost
>/dev/null
2>&1 ; then
143 echo
"no DISPLAY, exiting as the user probably logged out
"
146 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
147 /usr/lib/grive/grive-sync.sh sync googledrive
150 done
2>&1 | sed
"s%^%$
0:%
"
151 </pre
></blockquote
></p
>
153 <p
>Feel free to use the setup if you want. It can be assumed to be
154 GNU GPL v2 licensed (or any later version, at your leisure), but I
155 doubt this code is possible to claim copyright on.
</p
>
157 <p
>As usual, if you use Bitcoin and want to show your support of my
158 activities, please send Bitcoin donations to my address
159 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
164 <title>Using the Kodi API to play Youtube videos
</title>
165 <link>http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
166 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
167 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
168 <description><p
>I continue to explore my Kodi installation, and today I wanted to
169 tell it to play a youtube URL I received in a chat, without having to
170 insert search terms using the on-screen keyboard. After searching the
171 web for API access to the Youtube plugin and testing a bit, I managed
172 to find a recipe that worked. If you got a kodi instance with its API
173 available from http://kodihost/jsonrpc, you can try the following to
174 have check out a nice cover band.
</p
>
176 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
177 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
178 "params
": {
"item
": {
"file
":
179 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
180 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
182 <p
>I
've extended kodi-stream program to take a video source as its
183 first argument. It can now handle direct video links, youtube links
184 and
'desktop
' to stream my desktop to Kodi. It is almost like a
185 Chromecast. :)
</p
>
187 <p
>As usual, if you use Bitcoin and want to show your support of my
188 activities, please send Bitcoin donations to my address
189 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
194 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
195 <link>http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
196 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
197 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
198 <description><p
>For a while now, I have looked for a sensible way to share images
199 with my family using a self hosted solution, as it is unacceptable to
200 place images from my personal life under the control of strangers
201 working for data hoarders like Google or Dropbox. The last few days I
202 have drafted an approach that might work out, and I would like to
203 share it with you. I would like to publish images on a server under
204 my control, and point some Internet connected display units using some
205 free and open standard to the images I published. As my primary
206 language is not limited to ASCII, I need to store metadata using
207 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
208 of reading a RSS feed with image references (aka using the
209 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
210 of such frames. In the end I gave up that approach.
</p
>
212 <p
>Some months ago, I discovered that
213 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
214 read images from a RSS feed, and used it to set up a screen saver on
215 my home info screen, showing images from the Daily images feed from
216 NASA. This proved to work well. More recently I discovered that
217 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
218 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
219 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
220 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
221 screen saver capable of reading a RSS feed with images and news. For
222 fun, I used it this summer to test Kodi on my parents TV by hooking up
223 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
224 screen saver showing selected pictures from my selection.
</p
>
226 <p
>Armed with motivation and a test photo frame, I set out to generate
227 a RSS feed for the Kodi instance. I adjusted my
<a
228 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
229 /var/www/html/privatepictures/, wrote a small Perl script to extract
230 title and description metadata from the photo files and generate the
231 RSS file. I ended up using Perl instead of python, as the
232 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
233 tags I ended up using, while python3-exif did not. The relevant EXIF
234 tags only support ASCII, so I had to find better alternatives. XMP
235 seem to have the support I need.
</p
>
237 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
238 use tags that can be easily added/updated using normal free software
239 photo managing software. I ended up using the tags set using this
240 exiftool command, as these tags can also be set using digiKam:
</p
>
242 <blockquote
><pre
>
243 exiftool -headline=
'The RSS image title
' \
244 -description=
'The RSS image description.
' \
245 -subject+=for-family photo.jpeg
246 </pre
></blockquote
>
248 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
249 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
250 use the keyword/subject
'for-family
' to flag that the photo should be
251 shared with my family. Images with this keyword set are located and
252 copied into my Freedombox for the RSS generating script to find.
</p
>
254 <p
>Are there better ways to do this? Get in touch if you have better
255 suggestions.
</p
>
257 <p
>As usual, if you use Bitcoin and want to show your support of my
258 activities, please send Bitcoin donations to my address
259 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
264 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
265 <link>http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
266 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
267 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
268 <description><p
>Last night, I wrote
269 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
270 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
271 During the day I received valuable feedback, and thanks to the
272 suggestions I have been able to rewrite the recipe into a much simpler
273 approach requiring no setup at all. It is a single script that take
274 care of it all.
</p
>
276 <p
>This new script uses GStreamer instead of VLC to capture the
277 desktop and stream it to Kodi. This fixed the video quality issue I
278 saw initially. It further removes the need to add a m3u file on the
279 Kodi machine, as it instead connects to
280 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
281 Kodi
</a
> and simply ask Kodi to play from the stream created using
282 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
283 the script below, run it with the DNS name or IP address of the kodi
284 server to stream to as the only argument, and watch your screen show
285 up on the Kodi screen. Note, it depend on multicast on the local
286 network, so if you need to stream outside the local network, the
287 script must be modified. Also note, I have no idea if audio work, as
288 I only care about the picture part.
</p
>
290 <blockquote
><pre
>
293 # Stream the Linux desktop view to Kodi. See
294 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
295 # for backgorund information.
297 # Make sure the stream is stopped in Kodi and the gstreamer process is
298 # killed if something go wrong (for example if curl is unable to find the
299 # kodi server). Do the same when interrupting this script.
303 params=
"$
3"
304 curl --silent --header
'Content-Type: application/json
' \
305 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
306 "http://$host/jsonrpc
"
309 if [ -n
"$kodihost
" ] ; then
310 # Stop the playing when we end
311 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
312 jq .result[].playerid)
313 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
315 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
316 kill
"$gstpid
"
319 trap cleanup EXIT INT
321 if [ -n
"$
1" ]; then
332 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
333 cut -d
" " -f2|head -
1)
334 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
335 videoconvert ! queue2 ! \
336 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
337 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
338 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
339 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
340 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
341 > /dev/null
2>&1 &
344 # Give stream a second to get going
347 # Ask kodi to start streaming using its JSON-RPC API
348 kodicmd
"$kodihost
" Player.Open \
349 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
351 # wait for gst to end
352 wait
"$gstpid
"
353 </pre
></blockquote
>
355 <p
>I hope you find the approach useful. I know I do.
</p
>
357 <p
>As usual, if you use Bitcoin and want to show your support of my
358 activities, please send Bitcoin donations to my address
359 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
364 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
365 <link>http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
366 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
367 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
368 <description><p
>PS: See
369 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
370 followup post
</a
> for a even better approach.
</p
>
372 <p
>A while back, I was asked by a friend how to stream the desktop to
373 my projector connected to Kodi. I sadly had to admit that I had no
374 idea, as it was a task I never had tried. Since then, I have been
375 looking for a way to do so, preferable without much extra software to
376 install on either side. Today I found a way that seem to kind of
377 work. Not great, but it is a start.
</p
>
379 <p
>I had a look at several approaches, for example
380 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
381 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
382 local storage enough to store the stream locally. This is not going
383 to work well for me, lacking enough free space, and it would
384 impossible for my friend to get working.
</p
>
386 <p
>Next, it occurred to me that perhaps I could use VLC to create a
387 video stream that Kodi could play. Preferably using
388 broadcast/multicast, to avoid having to change any setup on the Kodi
389 side when starting such stream. Unfortunately, the only recipe I
390 could find using multicast used the rtp protocol, and this protocol
391 seem to not be supported by Kodi.
</p
>
393 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
394 have to specify the IP address of the streaming machine in both the
395 sending command and the file on the Kodi server. But it is showing my
396 desktop, and thus allow us to have a shared look on the big screen at
397 the programs I work on.
</p
>
399 <p
>I did not spend much time investigating codeces. I combined the
400 rtp and rtsp recipes from
401 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
402 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
403 this working on the desktop/streaming end.
</p
>
405 <blockquote
><pre
>
406 vlc screen:// --sout \
407 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
408 </pre
></blockquote
>
410 <p
>I ssh-ed into my Kodi box and created a file like this with the
411 same IP address:
</p
>
413 <blockquote
><pre
>
414 echo rtsp://
192.168.11.4:
8080/test.sdp \
415 > /storage/videos/screenstream.m3u
416 </pre
></blockquote
>
418 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
419 as I can tell the IP must be hardcoded for this to work. In other
420 words, if someone elses machine is going to do the steaming, you have
421 to update screenstream.m3u on the Kodi machine and adjust the vlc
422 recipe. To get started, locate the file in Kodi and select the m3u
423 file while the VLC stream is running. The desktop then show up in my
424 big screen. :)
</p
>
426 <p
>When using the same technique to stream a video file with audio,
427 the audio quality is really bad. No idea if the problem is package
428 loss or bad parameters for the transcode. I do not know VLC nor Kodi
429 enough to tell.
</p
>
431 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
432 succestions and reminded me about an important step. The
"screen:
"
433 input source is only available once the vlc-plugin-access-extra
434 package is installed on Debian. Without it, you will see this error
435 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
436 for details.
" He further found that it is possible to drop some parts
437 of the VLC command line to reduce the amount of hardcoded information.
438 It is also useful to consider using cvlc to avoid having the VLC
439 window in the desktop view. In sum, this give us this command line on
442 <blockquote
><pre
>
443 cvlc screen:// --sout \
444 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
445 </pre
></blockquote
>
447 <p
>and this on the Kodi end
<p
>
449 <blockquote
><pre
>
450 echo rtsp://
192.168.11.4:
8080/ \
451 > /storage/videos/screenstream.m3u
452 </pre
></blockquote
>
454 <p
>Still bad image quality, though. But I did discover that streaming
455 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
456 audio quality, so I guess the issue is in the input or transcoding
457 parts, not the rtsp part. I
've tried to change the vb and ab
458 parameters to use more bandwidth, but it did not make a
459 difference.
</p
>
461 <p
>I further received a suggestion from Einar Haraldseid to try using
462 gstreamer instead of VLC, and this proved to work great! He also
463 provided me with the trick to get Kodi to use a multicast stream as
464 its source. By using this monstrous oneliner, I can stream my desktop
465 with good video quality in reasonable framerate to the
239.255.0.1
466 multicast address on port
1234:
468 <blockquote
><pre
>
469 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
470 videoconvert ! queue2 ! \
471 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
472 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
473 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
474 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
475 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
476 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
477 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
478 </pre
></blockquote
>
480 <p
>and this on the Kodi end
<p
>
482 <blockquote
><pre
>
483 echo udp://@
239.255.0.1:
1234 \
484 > /storage/videos/screenstream.m3u
485 </pre
></blockquote
>
487 <p
>Note the trick to pick a valid pulseaudio source. It might not
488 pick the one you need. This approach will of course lead to trouble
489 if more than one source uses the same multicast port and address.
490 Note the ttl-mc=
1 setting, which limit the multicast packages to the
491 local network. If the value is increased, your screen will be
492 broadcasted further, one network
"hop
" for each increase (read up on
493 multicast to learn more. :)!
</p
>
495 <p
>Having cracked how to get Kodi to receive multicast streams, I
496 could use this VLC command to stream to the same multicast address.
497 The image quality is way better than the rtsp approach, but gstreamer
498 seem to be doing a better job.
</p
>
500 <blockquote
><pre
>
501 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
502 </pre
></blockquote
>
504 <p
>As usual, if you use Bitcoin and want to show your support of my
505 activities, please send Bitcoin donations to my address
506 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
511 <title>What is the most supported MIME type in Debian in
2018?
</title>
512 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
514 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
515 <description><p
>Five years ago,
516 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
517 measured what the most supported MIME type in Debian was
</a
>, by
518 analysing the desktop files in all packages in the archive. Since
519 then, the DEP-
11 AppStream system has been put into production, making
520 the task a lot easier. This made me want to repeat the measurement,
521 to see how much things changed. Here are the new numbers, for
522 unstable only this time:
524 <p
><strong
>Debian Unstable:
</strong
></p
>
528 ----- -----------------------
540 30 audio/x-vorbis+ogg
541 29 image/x-portable-pixmap
543 27 image/x-portable-bitmap
551 <p
>The list was created like this using a sid chroot:
"cat
552 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
553 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
555 <p
>It is interesting to see how image formats have passed text/plain
556 as the most announced supported MIME type. These days, thanks to the
557 AppStream system, if you run into a file format you do not know, and
558 want to figure out which packages support the format, you can find the
559 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
560 look up all packages announcing support for this format in their
561 AppStream metadata (XML or .desktop file) using
"appstreamcli
562 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
563 me, want to know which packages support inode/directory, you can get a
564 list like this:
</p
>
566 <p
><blockquote
><pre
>
567 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
574 Package: doublecmd-common
576 Package: enlightenment
596 </pre
></blockquote
></p
>
598 <p
>Using the same method, I can quickly discover that the Sketchup file
599 format is not yet supported by any package in Debian:
</p
>
601 <p
><blockquote
><pre
>
602 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
603 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
605 </pre
></blockquote
></p
>
607 <p
>Yesterday I used it to figure out which packages support the STL
3D
610 <p
><blockquote
><pre
>
611 % appstreamcli what-provides mimetype application/sla|grep Package
616 </pre
></blockquote
></p
>
618 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
620 <p
>As usual, if you use Bitcoin and want to show your support of my
621 activities, please send Bitcoin donations to my address
622 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
627 <title>Debian APT upgrade without enough free space on the disk...
</title>
628 <link>http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
629 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
630 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
631 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
632 for a while, and when I need to update it there is not enough free
633 space on the disk for apt to do a normal
'apt upgrade
'. I normally
634 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
635 upgrade only some of the packages in one batch, until the amount of
636 packages to download fall below the amount of free space available.
637 Today, I had about
500 packages to upgrade, and after a while I got
638 tired of trying to install chunks of packages manually. I concluded
639 that I did not have the spare hours required to complete the task, and
640 decided to see if I could automate it. I came up with this small
641 script which I call
'apt-in-chunks
':
</p
>
643 <p
><blockquote
><pre
>
646 # Upgrade packages when the disk is too full to upgrade every
647 # upgradable package in one lump. Fetching packages to upgrade using
648 # apt, and then installing using dpkg, to avoid changing the package
649 # flag for manual/automatic.
654 if [
"$
1" ]; then
655 grep -v
"$
1"
661 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
662 echo
"Upgrading $p
"
664 apt install --download-only -y $p
665 for f in /var/cache/apt/archives/*.deb; do
666 if [ -e
"$f
" ]; then
667 dpkg -i /var/cache/apt/archives/*.deb
672 </pre
></blockquote
></p
>
674 <p
>The script will extract the list of packages to upgrade, try to
675 download the packages needed to upgrade one package, install the
676 downloaded packages using dpkg. The idea is to upgrade packages
677 without changing the APT mark for the package (ie the one recording of
678 the package was manually requested or pulled in as a dependency). To
679 use it, simply run it as root from the command line. If it fail, try
680 'apt install -f
' to clean up the mess and run the script again. This
681 might happen if the new packages conflict with one of the old
682 packages. dpkg is unable to remove, while apt can do this.
</p
>
684 <p
>It take one option, a package to ignore in the list of packages to
685 upgrade. The option to ignore a package is there to be able to skip
686 the packages that are simply too large to unpack. Today this was
687 'ghc
', but I have run into other large packages causing similar
688 problems earlier (like TeX).
</p
>
690 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
691 alternative ways to handle this. The
"unattended-upgrades
692 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
693 each package to upgrade, and then upgrade them in order, smallest set
694 first. It might be a better option than my above mentioned script.
695 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
696 the need for using
"dpkg -i
" in the script above.
</p
>
698 <p
>As usual, if you use Bitcoin and want to show your support of my
699 activities, please send Bitcoin donations to my address
700 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
705 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
706 <link>http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
707 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
708 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
709 <description><p
>A new version of the
710 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
711 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
712 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
713 useful. It was uploaded the last few days, and the last update will
714 enter testing tomorrow. See the
715 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
716 notes
</a
> for the list of bug fixes and new features. Version
3.2
717 was announced
6 days ago. We will try to get it into Debian as
720 <p
>More information related to
3D printing is available on the
721 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
722 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
725 <p
>As usual, if you use Bitcoin and want to show your support of my
726 activities, please send Bitcoin donations to my address
727 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
732 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
733 <link>http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
734 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
735 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
736 <description><p
>After several months of working and waiting, I am happy to report
737 that the nice and user friendly
3D printer slicer software Cura just
738 entered Debian Unstable. It consist of five packages,
739 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
740 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
741 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
742 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
743 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
744 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
745 two, uranium and cura, entered Unstable yesterday. This should make
746 it easier for Debian users to print on at least the Ultimaker class of
747 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
748 make life easier for at least me. :)
</p
>
750 <p
>The work to make this happen was done by Gregor Riepl, and I was
751 happy to assist him in sponsoring the packages. With the introduction
752 of Cura, Debian is up to three
3D printer slicers at your service,
753 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
754 printer, give it a go. :)
</p
>
756 <p
>The
3D printer software is maintained by the
3D printer Debian
757 team, flocking together on the
758 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
760 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
761 IRC channel.
</p
>
763 <p
>The next step for Cura in Debian is to update the cura package to
764 version
3.0.3 and then update the entire set of packages to version
765 3.1.0 which showed up the last few days.
</p
>
770 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
771 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
772 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
773 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
774 <description><p
>At my nearby maker space,
775 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
776 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
777 on Windows and MacOS X than Linux, because the software involved had
778 to be manually compiled and set up on Linux while premade packages
779 worked out of the box on Windows and MacOS X. I found this annoying,
780 as the software involved,
781 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
782 and should be trivial to get up and running on Linux if someone took
783 the time to package it for the relevant distributions. I even found
784 <a href=
"https://bugs.debian.org/
706656">a request for adding into
785 Debian
</a
> from
2013, which had seem some activity over the years but
786 never resulted in the software showing up in Debian. So a few days
787 ago I offered my help to try to improve the situation.
</p
>
789 <p
>Now I am very happy to see that all the packages required by a
790 working Cura in Debian are uploaded into Debian and waiting in the NEW
791 queue for the ftpmasters to have a look. You can track the progress
793 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
794 status page for the
3D printer team
</a
>.
</p
>
796 <p
>The uploaded packages are a bit behind upstream, and was uploaded
797 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
798 queue
</a
> while we work up updating the packages to the latest
799 upstream version.
</p
>
801 <p
>On a related note, two competitors for Cura, which I found harder
802 to use and was unable to configure correctly for Ultimaker
2+ in the
803 short time I spent on it, are already in Debian. If you are looking
804 for
3D printer
"slicers
" and want something already available in
806 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
807 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
808 The latter is a fork of the former.
</p
>
810 <p
>As usual, if you use Bitcoin and want to show your support of my
811 activities, please send Bitcoin donations to my address
812 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
817 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
818 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
819 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
820 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
821 <description><p
>Every mobile phone announce its existence over radio to the nearby
822 mobile cell towers. And this radio chatter is available for anyone
823 with a radio receiver capable of receiving them. Details about the
824 mobile phones with very good accuracy is of course collected by the
825 phone companies, but this is not the topic of this blog post. The
826 mobile phone radio chatter make it possible to figure out when a cell
827 phone is nearby, as it include the SIM card ID (IMSI). By paying
828 attention over time, one can see when a phone arrive and when it leave
829 an area. I believe it would be nice to make this information more
830 available to the general public, to make more people aware of how
831 their phones are announcing their whereabouts to anyone that care to
834 <p
>I am very happy to report that we managed to get something
835 visualizing this information up and running for
836 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
837 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
838 library. The solution is based on the
839 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
840 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
841 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
842 Sone from the Computer Science department of the University of
843 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
844 IMSIs) as dots in a web browser graph, with lines to the dot
845 representing mobile base station it is talking to. It was working in
846 the lab yesterday, and was moved into place this morning.
</p
>
848 <p
>We set up a fairly powerful desktop machine using Debian
849 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
850 connected and visualize the visible cell phone towers using an
851 <a href=
"https://github.com/marlow925/hopglass
">English version of
852 Hopglass
</a
>. A fairly powerfull machine is needed as the
853 grgsm_livemon_headless processes from
854 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
855 the radio signal to data packages is quite CPU intensive.
</p
>
857 <p
>The frequencies to listen to, are identified using a slightly
858 patched scan-and-livemon (to set the --args values for each receiver),
859 and the Hopglass data is generated using the
860 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
861 in my meshviewer-output branch
</a
>. For some reason we could not get
862 more than four SDRs working. There is also a geographical map trying
863 to show the location of the base stations, but I believe their
864 coordinates are hardcoded to some random location in Germany, I
865 believe. The code should be replaced with code to look up location in
866 a text file, a sqlite database or one of the online databases
868 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
869 issue for the topic
</a
>.
871 <p
>If this sound interesting, visit the stand at the festival!
</p
>
876 <title>Easier recipe to observe the cell phones around you
</title>
877 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
879 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
880 <description><p
>A little more than a month ago I wrote
881 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
882 to observe the SIM card ID (aka IMSI number) of mobile phones talking
883 to nearby mobile phone base stations using Debian GNU/Linux and a
884 cheap USB software defined radio
</a
>, and thus being able to pinpoint
885 the location of people and equipment (like cars and trains) with an
886 accuracy of a few kilometer. Since then we have worked to make the
887 procedure even simpler, and it is now possible to do this without any
888 manual frequency tuning and without building your own packages.
</p
>
890 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
891 package is now included in Debian testing and unstable, and the
892 IMSI-catcher code no longer require root access to fetch and decode
893 the GSM data collected using gr-gsm.
</p
>
895 <p
>Here is an updated recipe, using packages built by Debian and a git
896 clone of two python scripts:
</p
>
900 <li
>Start with a Debian machine running the Buster version (aka
903 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
904 python-scapy
</tt
>' as root to install required packages.
</li
>
906 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
907 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
909 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
911 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
912 scan-and-livemon
</tt
>' to locate the frequency of nearby base
913 stations and start listening for GSM packages on one of them.
</li
>
915 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
916 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
920 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
921 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
922 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
923 work with RTL
8232 and other similar USB radio receivers you can get
925 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
926 from ebay
</a
>), so for now the solution is to scan using the RTL radio
927 and only use HackRF for fetching GSM data.
</p
>
929 <p
>As far as I can tell, a cell phone only show up on one of the
930 frequencies at the time, so if you are going to track and count every
931 cell phone around you, you need to listen to all the frequencies used.
932 To listen to several frequencies, use the --numrecv argument to
933 scan-and-livemon to use several receivers. Further, I am not sure if
934 phones using
3G or
4G will show as talking GSM to base stations, so
935 this approach might not see all phones around you. I typically see
936 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
938 <p
>I
've tried to run the scanner on a
939 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
940 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
941 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
942 stdout, I am told there it is caused by a buffer overflow between the
943 radio and GNU Radio, caused by the program being unable to read the
944 GSM data fast enough. If you see a stream of
'O
's from the terminal
945 where you started scan-and-livemon, you need a give the process more
946 CPU power. Perhaps someone are able to optimize the code to a point
947 where it become possible to set up RPi3 based GSM sniffers? I tried
948 using Raspbian instead of Debian, but there seem to be something wrong
949 with GNU Radio on raspbian, causing glibc to abort().
</p
>
954 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
955 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
957 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
958 <description><p
>On friday, I came across an interesting article in the Norwegian
959 web based ICT news magazine digi.no on
960 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
961 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
962 DVB-T software defined radios. The article refered to instructions
963 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
964 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
966 <p
>The instructions said to use Ubuntu, install pip using apt (to
967 bypass apt), use pip to install pybombs (to bypass both apt and pip),
968 and the ask pybombs to fetch and build everything you need from
969 scratch. I wanted to see if I could do the same on the most recent
970 Debian packages, but this did not work because pybombs tried to build
971 stuff that no longer build with the most recent openssl library or
972 some other version skew problem. While trying to get this recipe
973 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
974 and the only piece of software dependency missing in Debian was the
975 gr-gsm package. I also found out that the lead upstream developer of
976 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
977 Debian packages provided in an Ubuntu PPA repository. All I needed to
978 do was to dget the Debian source package and built it.
</p
>
980 <p
>The IMSI collector is a python script listening for packages on the
981 loopback network device and printing to the terminal some specific GSM
982 packages with IMSI numbers in them. The code is fairly short and easy
983 to understand. The reason this work is because gr-gsm include a tool
984 to read GSM data from a software defined radio like a DVB-T USB stick
985 and other software defined radios, decode them and inject them into a
986 network device on your Linux machine (using the loopback device by
987 default). This proved to work just fine, and I
've been testing the
988 collector for a few days now.
</p
>
990 <p
>The updated and simpler recipe is thus to
</p
>
994 <li
>start with a Debian machine running Stretch or newer,
</li
>
996 <li
>build and install the gr-gsm package available from
997 <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
>
999 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
1001 <li
>run grgsm_livemon and adjust the frequency until the terminal
1002 where it was started is filled with a stream of text (meaning you
1003 found a GSM station).
</li
>
1005 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
1009 <p
>To make it even easier in the future to get this sniffer up and
1010 running, I decided to package
1011 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
1012 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
1013 #
871055</a
>), and the package was uploaded into the NEW queue today.
1014 Luckily the gnuradio maintainer has promised to help me, as I do not
1015 know much about gnuradio stuff yet.
</p
>
1017 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
1018 commercial tools like
1019 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
1020 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
1021 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
1022 Stingray
</a
>, but I hope the existance of cheap alternatives can make
1023 more people realise how their whereabouts when carrying a cell phone
1024 is easily tracked. Seeing the data flow on the screen, realizing that
1025 I live close to a police station and knowing that the police is also
1026 wearing cell phones, I wonder how hard it would be for criminals to
1027 track the position of the police officers to discover when there are
1028 police near by, or for foreign military forces to track the location
1029 of the Norwegian military forces, or for anyone to track the location
1030 of government officials...
</p
>
1032 <p
>It is worth noting that the data reported by the IMSI-catcher
1033 script mentioned above is only a fraction of the data broadcasted on
1034 the GSM network. It will only collect one frequency at the time,
1035 while a typical phone will be using several frequencies, and not all
1036 phones will be using the frequencies tracked by the grgsm_livemod
1037 program. Also, there is a lot of radio chatter being ignored by the
1038 simple_IMSI-catcher script, which would be collected by extending the
1039 parser code. I wonder if gr-gsm can be set up to listen to more than
1040 one frequency?
</p
>
1045 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
1046 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
1047 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
1048 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
1049 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
1051 <p
>I finally received a copy of the Norwegian Bokmål edition of
1052 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1053 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
1054 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
1055 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
1056 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
1057 price. The book is also available for download in electronic form as
1058 PDF, EPUB and Mobipocket, as can be
1059 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
1060 as a web page
</a
>.
</p
>
1062 <p
>This is the second book I publish (the first was the book
1063 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
1065 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
1066 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
1068 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
1069 Bokmål
</a
>), and I am very excited to finally wrap up this
1071 "<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
1072 for Debian-administratoren
</a
>" will be well received.
</p
>
1077 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
1078 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
1079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
1080 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
1081 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
1082 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
1083 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
1084 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
1085 på om den fri oversetterløsningen
1086 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
1087 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
1089 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
1092 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
1093 rolle og muligheter til å håndtere internasjonale utfordringer, som
1094 for eksempel flykningekrisen.
</p
>
1096 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
1097 på temaet:
</p
>
1099 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
1100 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
1105 <p
>Dette oversetter Apertium slik:
</p
>
1108 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
1109 andre aktørar og høve til å handtera internasjonale utfordringar, som
1110 til dømes *flykningekrisen.
</p
>
1112 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
1116 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
1117 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
1122 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
1123 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
1124 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
1125 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
1126 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
1127 det er kanskje flisespikking. Det understreker vel bare at det alltid
1128 trengs korrekturlesning etter automatisk oversettelse.
</p
>
1133 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
1134 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
1135 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
1136 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
1137 <description><p
>Over the years, administrating thousand of NFS mounting linux
1138 computers at the time, I often needed a way to detect if the machine
1139 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
1140 file or directory affected by the hang, the process (and possibly the
1141 shell) will hang too. So you want to be able to detect this without
1142 risking the detection process getting stuck too. It has not been
1143 obvious how to do this. When the hang has lasted a while, it is
1144 possible to find messages like these in dmesg:
</p
>
1146 <p
><blockquote
>
1147 nfs: server nfsserver not responding, still trying
1148 <br
>nfs: server nfsserver OK
1149 </blockquote
></p
>
1151 <p
>It is hard to know if the hang is still going on, and it is hard to
1152 be sure looking in dmesg is going to work. If there are lots of other
1153 messages in dmesg the lines might have rotated out of site before they
1154 are noticed.
</p
>
1156 <p
>While reading through the nfs client implementation in linux kernel
1157 code, I came across some statistics that seem to give a way to detect
1158 it. The om_timeouts sunrpc value in the kernel will increase every
1159 time the above log entry is inserted into dmesg. And after digging a
1160 bit further, I discovered that this value show up in
1161 /proc/self/mountstats on Linux.
</p
>
1163 <p
>The mountstats content seem to be shared between files using the
1164 same file system context, so it is enough to check one of the
1165 mountstats files to get the state of the mount point for the machine.
1166 I assume this will not show lazy umounted NFS points, nor NFS mount
1167 points in a different process context (ie with a different filesystem
1168 view), but that does not worry me.
</p
>
1170 <p
>The content for a NFS mount point look similar to this:
</p
>
1172 <p
><blockquote
><pre
>
1174 device /dev/mapper/Debian-var mounted on /var with fstype ext3
1175 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
1176 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
1178 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
1179 sec: flavor=
1,pseudoflavor=
1
1180 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
1181 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
1182 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
1183 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
1185 NULL:
0 0 0 0 0 0 0 0
1186 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
1187 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
1188 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
1189 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
1190 READLINK:
125 125 0 20472 18620 0 1112 1118
1191 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
1192 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
1193 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
1194 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
1195 SYMLINK:
903 903 0 233428 245488 6 5865 5917
1196 MKNOD:
80 80 0 20148 21760 0 299 304
1197 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
1198 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
1199 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
1200 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
1201 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
1202 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
1203 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
1204 FSINFO:
2 2 0 232 328 0 1 1
1205 PATHCONF:
1 1 0 116 140 0 0 0
1206 COMMIT:
0 0 0 0 0 0 0 0
1208 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
1210 </pre
></blockquote
></p
>
1212 <p
>The key number to look at is the third number in the per-op list.
1213 It is the number of NFS timeouts experiences per file system
1214 operation. Here
22 write timeouts and
5 access timeouts. If these
1215 numbers are increasing, I believe the machine is experiencing NFS
1216 hang. Unfortunately the timeout value do not start to increase right
1217 away. The NFS operations need to time out first, and this can take a
1218 while. The exact timeout value depend on the setup. For example the
1219 defaults for TCP and UDP mount points are quite different, and the
1220 timeout value is affected by the soft, hard, timeo and retrans NFS
1221 mount options.
</p
>
1223 <p
>The only way I have been able to get working on Debian and RedHat
1224 Enterprise Linux for getting the timeout count is to peek in /proc/.
1226 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
1227 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
1228 command can be used to get these timeout values. But this do not work
1229 on Linux, as far as I can tell. I
1230 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
1231 but have not seen any replies yet.
</p
>
1233 <p
>Is there a better way to figure out if a Linux NFS client is
1234 experiencing NFS hangs? Is there a way to detect which processes are
1235 affected? Is there a way to get the NFS mount going quickly once the
1236 network problem causing the NFS hang has been cleared? I would very
1237 much welcome some clues, as we regularly run into NFS hangs.
</p
>
1242 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
1243 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
1244 <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>
1245 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
1246 <description><p
>For almost a year now, we have been working on making a Norwegian
1247 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
1248 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
1249 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
1250 we are working on the proof reading to ensure consistent language and
1251 use of correct computer science terms. The plan is to make the book
1252 available on paper, as well as in electronic form. For that to
1253 happen, the proof reading must be completed and all the figures need
1254 to be translated. If you want to help out, get in touch.
</p
>
1256 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
1258 fresh PDF edition
</a
> in A4 format (the final book will have smaller
1259 pages) of the book created every morning is available for
1260 proofreading. If you find any errors, please
1261 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
1262 Weblate and correct the error
</a
>. The
1263 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
1264 of the translation including figures
</a
> is a useful source for those
1265 provide Norwegian bokmål screen shots and figures.
</p
>
1270 <title>Unlimited randomness with the ChaosKey?
</title>
1271 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
1272 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
1273 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
1274 <description><p
>A few days ago I ordered a small batch of
1275 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
1276 USB dongle for generating entropy created by Bdale Garbee and Keith
1277 Packard. Yesterday it arrived, and I am very happy to report that it
1278 work great! According to its designers, to get it to work out of the
1279 box, you need the Linux kernel version
4.1 or later. I tested on a
1280 Debian Stretch machine (kernel version
4.9), and there it worked just
1281 fine, increasing the available entropy very quickly. I wrote a small
1282 test oneliner to test. It first print the current entropy level,
1283 drain /dev/random, and then print the entropy level for five seconds.
1284 Here is the situation without the ChaosKey inserted:
</p
>
1286 <blockquote
><pre
>
1287 % cat /proc/sys/kernel/random/entropy_avail; \
1288 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
1289 for n in $(seq
1 5); do \
1290 cat /proc/sys/kernel/random/entropy_avail; \
1296 28 byte kopiert,
0,
000264565 s,
106 kB/s
1303 </pre
></blockquote
>
1305 <p
>The entropy level increases by
3-
4 every second. In such case any
1306 application requiring random bits (like a HTTPS enabled web server)
1307 will halt and wait for more entrpy. And here is the situation with
1308 the ChaosKey inserted:
</p
>
1310 <blockquote
><pre
>
1311 % cat /proc/sys/kernel/random/entropy_avail; \
1312 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
1313 for n in $(seq
1 5); do \
1314 cat /proc/sys/kernel/random/entropy_avail; \
1320 104 byte kopiert,
0,
000487647 s,
213 kB/s
1327 </pre
></blockquote
>
1329 <p
>Quite the difference. :) I bought a few more than I need, in case
1330 someone want to buy one here in Norway. :)
</p
>
1332 <p
>Update: The dongle was presented at Debconf last year. You might
1333 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
1334 recording illuminating
</a
>. It explains exactly what the source of
1335 randomness is, if you are unable to spot it from the schema drawing
1336 available from the ChaosKey web site linked at the start of this blog
1342 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
1343 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
1344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
1345 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
1346 <description><p
>Did you ever wonder where the web trafic really flow to reach the
1347 web servers, and who own the network equipment it is flowing through?
1348 It is possible to get a glimpse of this from using traceroute, but it
1349 is hard to find all the details. Many years ago, I wrote a system to
1350 map the Norwegian Internet (trying to figure out if our plans for a
1351 network game service would get low enough latency, and who we needed
1352 to talk to about setting up game servers close to the users. Back
1353 then I used traceroute output from many locations (I asked my friends
1354 to run a script and send me their traceroute output) to create the
1355 graph and the map. The output from traceroute typically look like
1358 <p
><pre
>
1359 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
1360 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
1361 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
1362 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
1363 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
1364 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
1365 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
1366 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
1370 </pre
></p
>
1372 <p
>This show the DNS names and IP addresses of (at least some of the)
1373 network equipment involved in getting the data traffic from me to the
1374 www.stortinget.no server, and how long it took in milliseconds for a
1375 package to reach the equipment and return to me. Three packages are
1376 sent, and some times the packages do not follow the same path. This
1377 is shown for hop
5, where three different IP addresses replied to the
1378 traceroute request.
</p
>
1380 <p
>There are many ways to measure trace routes. Other good traceroute
1381 implementations I use are traceroute (using ICMP packages) mtr (can do
1382 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
1383 traceroute and a lot of other capabilities). All of them are easily
1384 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
1386 <p
>This time around, I wanted to know the geographic location of
1387 different route points, to visualize how visiting a web page spread
1388 information about the visit to a lot of servers around the globe. The
1389 background is that a web site today often will ask the browser to get
1390 from many servers the parts (for example HTML, JSON, fonts,
1391 JavaScript, CSS, video) required to display the content. This will
1392 leak information about the visit to those controlling these servers
1393 and anyone able to peek at the data traffic passing by (like your ISP,
1394 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
1396 <p
>Lets pick an example, the Norwegian parliament web site
1397 www.stortinget.no. It is read daily by all members of parliament and
1398 their staff, as well as political journalists, activits and many other
1399 citizens of Norway. A visit to the www.stortinget.no web site will
1400 ask your browser to contact
8 other servers: ajax.googleapis.com,
1401 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
1402 stats.g.doubleclick.net, www.google-analytics.com,
1403 www.googletagmanager.com and www.netigate.se. I extracted this by
1404 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
1405 Stortinget web page and tell me all the URLs PhantomJS downloaded to
1406 render the page (in HAR format using
1407 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
1408 netsniff example
</a
>. I am very grateful to Gorm for showing me how
1409 to do this). My goal is to visualize network traces to all IP
1410 addresses behind these DNS names, do show where visitors personal
1411 information is spread when visiting the page.
</p
>
1413 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
1414 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
>
1416 <p
>When I had a look around for options, I could not find any good
1417 free software tools to do this, and decided I needed my own traceroute
1418 wrapper outputting KML based on locations looked up using GeoIP. KML
1419 is easy to work with and easy to generate, and understood by several
1420 of the GIS tools I have available. I got good help from by NUUG
1421 colleague Anders Einar with this, and the result can be seen in
1422 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
1423 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
1424 free GeoIP databases I could find (and the for-pay databases my
1425 friends had access to) is not up to the task. The IP addresses of
1426 central Internet infrastructure would typically be placed near the
1427 controlling companies main office, and not where the router is really
1428 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
1429 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
1431 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
1432 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
>
1434 <p
>I also had a look at the visual traceroute graph created by
1435 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
1436 showing IP network ownership (aka AS owner) for the IP address in
1438 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
1439 graph display a lot of useful information about the traceroute in SVG
1440 format
</a
>, and give a good indication on who control the network
1441 equipment involved, but it do not include geolocation. This graph
1442 make it possible to see the information is made available at least for
1443 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
1444 3 Communications and NetDNA.
</p
>
1446 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
1447 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
>
1449 <p
>In the process, I came across the
1450 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
1451 Salim Gasmi. Its methology of combining guesses based on DNS names,
1452 various location databases and finally use latecy times to rule out
1453 candidate locations seemed to do a very good job of guessing correct
1454 geolocation. But it could only do one trace at the time, did not have
1455 a sensor in Norway and did not make the geolocations easily available
1456 for postprocessing. So I contacted the developer and asked if he
1457 would be willing to share the code (he refused until he had time to
1458 clean it up), but he was interested in providing the geolocations in a
1459 machine readable format, and willing to set up a sensor in Norway. So
1460 since yesterday, it is possible to run traces from Norway in this
1461 service thanks to a sensor node set up by
1462 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
1463 trace in KML format for further processing.
</p
>
1465 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
1466 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
>
1468 <p
>Here we can see a lot of trafic passes Sweden on its way to
1469 Denmark, Germany, Holland and Ireland. Plenty of places where the
1470 Snowden confirmations verified the traffic is read by various actors
1471 without your best interest as their top priority.
</p
>
1473 <p
>Combining KML files is trivial using a text editor, so I could loop
1474 over all the hosts behind the urls imported by www.stortinget.no and
1475 ask for the KML file from GeoTraceroute, and create a combined KML
1476 file with all the traces (unfortunately only one of the IP addresses
1477 behind the DNS name is traced this time. To get them all, one would
1478 have to request traces using IP number instead of DNS names from
1479 GeoTraceroute). That might be the next step in this project.
</p
>
1481 <p
>Armed with these tools, I find it a lot easier to figure out where
1482 the IP traffic moves and who control the boxes involved in moving it.
1483 And every time the link crosses for example the Swedish border, we can
1484 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
1485 Britain and NSA in USA and cables around the globe. (Hm, what should
1486 we tell them? :) Keep that in mind if you ever send anything
1487 unencrypted over the Internet.
</p
>
1489 <p
>PS: KML files are drawn using
1490 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
1491 Rublev
<a/
>, as it was less cluttered than the local Linux application
1492 Marble. There are heaps of other options too.
</p
>
1494 <p
>As usual, if you use Bitcoin and want to show your support of my
1495 activities, please send Bitcoin donations to my address
1496 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1501 <title>Appstream just learned how to map hardware to packages too!
</title>
1502 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
1503 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
1504 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
1505 <description><p
>I received a very nice Christmas present today. As my regular
1506 readers probably know, I have been working on the
1507 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
1508 system
</a
> for many years. The goal of the Isenkram system is to make
1509 it easier for users to figure out what to install to get a given piece
1510 of hardware to work in Debian, and a key part of this system is a way
1511 to map hardware to packages. Isenkram have its own mapping database,
1512 and also uses data provided by each package using the AppStream
1513 metadata format. And today,
1514 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
1515 Debian learned to look up hardware the same way Isenkram is doing it,
1516 ie using fnmatch():
</p
>
1518 <p
><pre
>
1519 % appstreamcli what-provides modalias \
1520 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1521 Identifier: pymissile [generic]
1523 Summary: Control original Striker USB Missile Launcher
1525 % appstreamcli what-provides modalias usb:v0694p0002d0000
1526 Identifier: libnxt [generic]
1528 Summary: utility library for talking to the LEGO Mindstorms NXT brick
1531 Identifier: t2n [generic]
1533 Summary: Simple command-line tool for Lego NXT
1536 Identifier: python-nxt [generic]
1538 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
1541 Identifier: nbc [generic]
1543 Summary: C compiler for LEGO Mindstorms NXT bricks
1546 </pre
></p
>
1548 <p
>A similar query can be done using the combined AppStream and
1549 Isenkram databases using the isenkram-lookup tool:
</p
>
1551 <p
><pre
>
1552 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
1554 % isenkram-lookup usb:v0694p0002d0000
1560 </pre
></p
>
1562 <p
>You can find modalias values relevant for your machine using
1563 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
1565 <p
>If you want to make this system a success and help Debian users
1566 make the most of the hardware they have, please
1567 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
1568 AppStream metadata for your package following the guidelines
</a
>
1569 documented in the wiki. So far only
11 packages provide such
1570 information, among the several hundred hardware specific packages in
1571 Debian. The Isenkram database on the other hand contain
101 packages,
1572 mostly related to USB dongles. Most of the packages with hardware
1573 mapping in AppStream are LEGO Mindstorms related, because I have, as
1574 part of my involvement in
1575 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
1576 team
</a
> given priority to making sure LEGO users get proposed the
1577 complete set of packages in Debian for that particular hardware. The
1578 team also got a nice Christmas present today. The
1579 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
1580 package
</a
> made it into Debian. With this package in place, it is
1581 now possible to use the LEGO Mindstorms NXT unit with only free
1582 software, as the nxt-firmware package contain the source and firmware
1583 binaries for the NXT brick.
</p
>
1585 <p
>As usual, if you use Bitcoin and want to show your support of my
1586 activities, please send Bitcoin donations to my address
1587 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1592 <title>Isenkram updated with a lot more hardware-package mappings
</title>
1593 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
1594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
1595 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
1596 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
1597 system
</a
> I wrote two years ago to make it easier in Debian to find
1598 and install packages to get your hardware dongles to work, is still
1599 going strong. It is a system to look up the hardware present on or
1600 connected to the current system, and map the hardware to Debian
1601 packages. It can either be done using the tools in isenkram-cli or
1602 using the user space daemon in the isenkram package. The latter will
1603 notify you, when inserting new hardware, about what packages to
1604 install to get the dongle working. It will even provide a button to
1605 click on to ask packagekit to install the packages.
</p
>
1607 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
1609 <p
><pre
>
1626 </pre
></p
>
1628 <p
>It can also list the firware package providing firmware requested
1629 by the load kernel modules, which in my case is an empty list because
1630 I have all the firmware my machine need:
1632 <p
><pre
>
1633 % /usr/sbin/isenkram-autoinstall-firmware -l
1634 info: did not find any firmware files requested by loaded kernel modules. exiting
1636 </pre
></p
>
1638 <p
>The last few days I had a look at several of the around
250
1639 packages in Debian with udev rules. These seem like good candidates
1640 to install when a given hardware dongle is inserted, and I found
1641 several that should be proposed by isenkram. I have not had time to
1642 check all of them, but am happy to report that now there are
97
1643 packages packages mapped to hardware by Isenkram.
11 of these
1644 packages provide hardware mapping using AppStream, while the rest are
1645 listed in the modaliases file provided in isenkram.
</p
>
1647 <p
>These are the packages with hardware mappings at the moment. The
1648 <strong
>marked packages
</strong
> are also announcing their hardware
1649 support using AppStream, for everyone to use:
</p
>
1651 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
1652 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
1653 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
1654 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
1655 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
1656 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
1657 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
1658 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
1659 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
1660 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
1661 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
1662 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
1663 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
1664 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
1665 pcscd, pidgin-blinklight, printer-driver-splix,
1666 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
1667 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
1668 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
1669 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
1670 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
1671 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
1672 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
1673 xserver-xorg-video-vmware, yubikey-personalization and
1674 zd1211-firmware
</p
>
1676 <p
>If you know of other packages, please let me know with a wishlist
1677 bug report against the isenkram-cli package, and ask the package
1679 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
1680 metadata according to the guidelines
</a
> to provide the information
1681 for everyone. In time, I hope to get rid of the isenkram specific
1682 hardware mapping and depend exclusively on AppStream.
</p
>
1684 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
1685 much hardware, and suggest that the package with with any ethernet
1686 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
1687 the details. I hope the maintainer find time to address it soon. In
1688 the mean time I provide an override in isenkram.
</p
>
1693 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
1694 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
1695 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
1696 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
1697 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
1699 <p
>In my early years, I played
1700 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
1701 Elite
</a
> on my PC. I spent many months trading and fighting in
1702 space, and reached the
'elite
' fighting status before I moved on. The
1703 original Elite game was available on Commodore
64 and the IBM PC
1704 edition I played had a
64 KB executable. I am still impressed today
1705 that the authors managed to squeeze both a
3D engine and details about
1706 more than
2000 planet systems across
7 galaxies into a binary so
1709 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
1710 software game Oolite inspired by Elite
</a
> for a while, but did not
1711 really have time to test it properly until a few days ago. It was
1712 great to discover that my old knowledge about trading routes were
1713 still valid. But my fighting and flying abilities were gone, so I had
1714 to retrain to be able to dock on a space station. And I am still not
1715 able to make much resistance when I am attacked by pirates, so I
1716 bougth and mounted the most powerful laser in the rear to be able to
1717 put up at least some resistance while fleeing for my life. :)
</p
>
1719 <p
>When playing Elite in the late eighties, I had to discover
1720 everything on my own, and I had long lists of prices seen on different
1721 planets to be able to decide where to trade what. This time I had the
1723 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
1724 where information about each planet is easily available with common
1725 price ranges and suggested trading routes. This improved my ability
1726 to earn money and I have been able to earn enough to buy a lot of
1727 useful equipent in a few days. I believe I originally played for
1728 months before I could get a docking computer, while now I could get it
1729 after less then a week.
</p
>
1731 <p
>If you like science fiction and dreamed of a life as a vagabond in
1732 space, you should try out Oolite. It is available for Linux, MacOSX
1733 and Windows, and is included in Debian and derivatives since
2011.
</p
>
1735 <p
>As usual, if you use Bitcoin and want to show your support of my
1736 activities, please send Bitcoin donations to my address
1737 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1742 <title>Quicker Debian installations using eatmydata
</title>
1743 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
1744 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
1745 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
1746 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
1747 installation system, observing how using
1748 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
1749 could speed up the installation
</a
> quite a bit. My testing measured
1750 speedup around
20-
40 percent for Debian Edu, where we install around
1751 1000 packages from within the installer. The eatmydata package
1752 provide a way to disable/delay file system flushing. This is a bit
1753 risky in the general case, as files that should be stored on disk will
1754 stay only in memory a bit longer than expected, causing problems if a
1755 machine crashes at an inconvenient time. But for an installation, if
1756 the machine crashes during installation the process is normally
1757 restarted, and avoiding disk operations as much as possible to speed
1758 up the process make perfect sense.
1760 <p
>I added code in the Debian Edu specific installation code to enable
1761 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
1762 but did not have time to push it any further. But a few months ago I
1763 picked it up again and worked with the libeatmydata package maintainer
1764 Mattia Rizzolo to make it easier for everyone to get this installation
1765 speedup in Debian. Thanks to our cooperation There is now an
1766 eatmydata-udeb package in Debian testing and unstable, and simply
1767 enabling/installing it in debian-installer (d-i) is enough to get the
1768 quicker installations. It can be enabled using preseeding. The
1769 following untested kernel argument should do the trick:
</p
>
1771 <blockquote
><pre
>
1772 preseed/early_command=
"anna-install eatmydata-udeb
"
1773 </pre
></blockquote
>
1775 <p
>This should ask d-i to install the package inside the d-i
1776 environment early in the installation sequence. Having it installed
1777 in d-i in turn will make sure the relevant scripts are called just
1778 after debootstrap filled /target/ with the freshly installed Debian
1779 system to configure apt to run dpkg with eatmydata. This is enough to
1780 speed up the installation process. There is a proposal to
1781 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
1782 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
1783 tested its impact.
</p
>
1789 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
1790 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
1791 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
1792 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
1793 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
1794 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
1795 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
1796 elever over det ganske land skal levere inn hvert år. Det mange ikke
1797 vet er at selv om de kommersielle alternativene
1798 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
1799 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
1800 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
1801 utmerket fri programvarealternativ som kan. Oversetterverktøyet
1802 Apertium har støtte for en rekke språkkombinasjoner, og takket være
1803 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
1804 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
1805 nynorsk, og få den automatoversatt til det andre skriftspråket.
1806 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
1807 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
1808 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
1809 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
1810 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
1811 teksten din i webskjemaet der.
1813 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
1814 teknologien kan du enten installere pakken
1815 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
1816 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
1817 api.apertium.org. Se
1818 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
1819 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
1820 denne teksten som ble skrevet på bokmål over maskinoversatt til
1825 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
1826 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
1827 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
1828 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
1829 veit er at sjølv om dei kommersielle alternativa
1830 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
1831 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
1832 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
1833 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
1834 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
1835 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
1836 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
1837 nynorsk, og få den *automatoversatt til det andre skriftspråket.
1838 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
1839 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
1840 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
1841 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
1842 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
1843 teksta di i *webskjemaet der.
1845 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
1846 teknologien kan du anten installera pakken
1847 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
1848 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
1849 *api.*apertium.org. Sjå
1850 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
1851 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
1852 for denne teksta som vart skreva på bokmål over *maskinoversatt til
1858 <title>Coz profiler for multi-threaded software is now in Debian
</title>
1859 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
1860 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
1861 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
1862 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
1863 profiler able to run benchmarking experiments on the instrumented
1864 multi-threaded program, finally
1865 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
1866 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
1868 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
1869 blogged about the coz tool
</a
> in August working with upstream to make
1870 it suitable for Debian. There are still issues with clang
1871 compatibility, inline assembly only working x86 and minimized
1872 JavaScript libraries.
</p
>
1874 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
1876 <p
><blockquote
>
1877 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
1878 </blockquote
></p
>
1880 <p
>This will produce a profile.coz file in the current working
1881 directory with the profiling information. This is then given to a
1882 JavaScript application provided in the package and available from
1883 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
1884 To start the local copy, invoke it in a browser like this:
</p
>
1886 <p
><blockquote
>
1887 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
1888 </blockquote
></p
>
1890 <p
>See the project home page and the
1891 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
1892 ;login: article on Coz
</a
> for more information on how it is
1898 <title>My own self balancing Lego Segway
</title>
1899 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
1900 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
1901 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
1902 <description><p
>A while back I received a Gyro sensor for the NXT
1903 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
1904 present. It had been on my wishlist for a while, because I wanted to
1905 build a Segway like balancing lego robot. I had already built
1906 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
1907 robot
</a
> with the kids, using the light/color sensor included in the
1908 NXT kit as the balance sensor, but it was not working very well. It
1909 could balance for a while, but was very sensitive to the light
1910 condition in the room and the reflective properties of the surface and
1911 would fall over after a short while. I wanted something more robust,
1913 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
1914 gyro sensor from HiTechnic
</a
> I believed would solve it on my
1915 wishlist for some years before it suddenly showed up as a gift from my
1916 loved ones. :)
</p
>
1918 <p
>Unfortunately I have not had time to sit down and play with it
1919 since then. But that changed some days ago, when I was searching for
1920 lego segway information and came across a recipe from HiTechnic for
1922 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
1923 HTWay
</a
>, a segway like balancing robot. Build instructions and
1924 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
1925 code
</a
> was included, so it was just a question of putting it all
1926 together. And thanks to the great work of many Debian developers, the
1927 compiler needed to build the source for the NXT is already included in
1928 Debian, so I was read to go in less than an hour. The resulting robot
1929 do not look very impressive in its simplicity:
</p
>
1931 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
1933 <p
>Because I lack the infrared sensor used to control the robot in the
1934 design from HiTechnic, I had to comment out the last task
1935 (taskControl). I simply placed /* and */ around it get the program
1936 working without that sensor present. Now it balances just fine until
1937 the battery status run low:
</p
>
1939 <p align=
"center
"><video width=
"70%
" controls=
"true
">
1940 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
1941 </video
></p
>
1943 <p
>Now we would like to teach it how to follow a line and take remote
1944 control instructions using the included Bluetooth receiver in the NXT.
</p
>
1946 <p
>If you, like me, love LEGO and want to make sure we find the tools
1947 they need to work with LEGO in Debian and all our derivative
1948 distributions like Ubuntu, check out
1949 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
1950 project page
</a
> and join the Debian LEGO team. Personally I own a
1951 RCX and NXT controller (no EV3), and would like to make sure the
1952 Debian tools needed to program the systems I own work as they
1958 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
1959 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
1960 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
1961 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
1962 <description><p
>In July
1963 <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
1964 wrote how to get the Signal Chrome/Chromium app working
</a
> without
1965 the ability to receive SMS messages (aka without a cell phone). It is
1966 time to share some experiences and provide an updated setup.
</p
>
1968 <p
>The Signal app have worked fine for several months now, and I use
1969 it regularly to chat with my loved ones. I had a major snag at the
1970 end of my summer vacation, when the the app completely forgot my
1971 setup, identity and keys. The reason behind this major mess was
1972 running out of disk space. To avoid that ever happening again I have
1973 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
1974 roll back to an earlier version if the files are wiped by mistake. I
1975 had to use it once after introducing the git backup. When rolling
1976 back to an earlier version, one need to use the
'reset session
' option
1977 in Signal to get going, and notify the people you talk with about the
1978 problem. I assume there is some sequence number tracking in the
1979 protocol to detect rollback attacks. The git repository is rather big
1980 (
674 MiB so far), but I have not tried to figure out if some of the
1981 content can be added to a .gitignore file due to lack of spare
1984 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
1985 make it impossible to send messages using Signal. I could still
1986 receive them, but had to patch the code with a new timestamp to send.
1987 I believe the timeout is added by the developers to force people to
1988 upgrade to the latest version of the app, even when there is no
1989 protocol changes, to reduce the version skew among the user base and
1990 thus try to keep the number of support requests down.
</p
>
1992 <p
>Since my original recipe, the Signal source code changed slightly,
1993 making the old patch fail to apply cleanly. Below is an updated
1994 patch, including the shell wrapper I use to start Signal. The
1995 original version required a new user to locate the JavaScript console
1996 and call a function from there. I got help from a friend with more
1997 JavaScript knowledge than me to modify the code to provide a GUI
1998 button instead. This mean that to get started you just need to run
1999 the wrapper and click the
'Register without mobile phone
' to get going
2000 now. I
've also modified the timeout code to always set it to
90 days
2001 in the future, to avoid having to patch the code regularly.
</p
>
2003 <p
>So, the updated recipe for Debian Jessie:
</p
>
2007 <li
>First, install required packages to get the source code and the
2008 browser you need. Signal only work with Chrome/Chromium, as far as I
2009 know, so you need to install it.
2012 apt install git tor chromium
2013 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2014 </pre
></li
>
2016 <li
>Modify the source code using command listed in the the patch
2017 block below.
</li
>
2019 <li
>Start Signal using the run-signal-app wrapper (for example using
2020 <tt
>`pwd`/run-signal-app
</tt
>).
2022 <li
>Click on the
'Register without mobile phone
', will in a phone
2023 number you can receive calls to the next minute, receive the
2024 verification code and enter it into the form field and press
2025 'Register
'. Note, the phone number you use will be user Signal
2026 username, ie the way others can find you on Signal.
</li
>
2028 <li
>You can now use Signal to contact others. Note, new contacts do
2029 not show up in the contact list until you restart Signal, and there is
2030 no way to assign names to Contacts. There is also no way to create or
2031 update chat groups. I suspect this is because the web app do not have
2032 a associated contact database.
</li
>
2036 <p
>I am still a bit uneasy about using Signal, because of the way its
2037 main author moxie0 reject federation and accept dependencies to major
2038 corporations like Google (part of the code is fetched from Google) and
2039 Amazon (the central coordination point is owned by Amazon). See for
2041 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
2042 LibreSignal issue tracker
</a
> for a thread documenting the authors
2043 view on these issues. But the network effect is strong in this case,
2044 and several of the people I want to communicate with already use
2045 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
2046 once it
<a href=
"https://bugs.debian.org/
830265">work on my
2047 laptop
</a
>? It already work on Windows and Android, and is included
2048 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
2049 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
2050 working on Debian Stable.
</p
>
2052 <p
>Anyway, this is the patch I apply to the Signal code to get it
2053 working. It switch to the production servers, disable to timeout,
2054 make registration easier and add the shell wrapper:
</p
>
2057 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
2058 diff --git a/js/background.js b/js/background.js
2059 index
24b4c1d.
.579345f
100644
2060 --- a/js/background.js
2061 +++ b/js/background.js
2066 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
2067 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
2068 var SERVER_PORTS = [
80,
4433,
8443];
2069 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
2070 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
2071 var messageReceiver;
2072 window.getSocketStatus = function() {
2073 if (messageReceiver) {
2074 diff --git a/js/expire.js b/js/expire.js
2075 index
639aeae..beb91c3
100644
2080 'use strict
';
2081 - var BUILD_EXPIRATION =
0;
2082 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
2084 window.extension = window.extension || {};
2086 diff --git a/js/views/install_view.js b/js/views/install_view.js
2087 index
7816f4f.
.1d6233b
100644
2088 --- a/js/views/install_view.js
2089 +++ b/js/views/install_view.js
2092 'click .step1
': this.selectStep.bind(this,
1),
2093 'click .step2
': this.selectStep.bind(this,
2),
2094 -
'click .step3
': this.selectStep.bind(this,
3)
2095 +
'click .step3
': this.selectStep.bind(this,
3),
2096 +
'click .callreg
': function() { extension.install(
'standalone
') },
2099 clearQR: function() {
2100 diff --git a/options.html b/options.html
2101 index dc0f28e.
.8d709f6
100644
2105 &lt;div class=
'nav
'>
2106 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
2107 &lt;p
>{{ installTagline }}
&lt;/p
>
2108 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
2109 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
2110 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
2113 &lt;span class=
'dot step1 selected
'>&lt;/span
>
2114 &lt;span class=
'dot step2
'>&lt;/span
>
2115 &lt;span class=
'dot step3
'>&lt;/span
>
2116 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
2117 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
2123 +userdata=
"`pwd`/userdata
"
2124 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
2125 + (cd $userdata
&& git init)
2127 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
2129 + --proxy-server=
"socks://localhost:
9050" \
2130 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
2132 chmod a+rx run-signal-app
2135 <p
>As usual, if you use Bitcoin and want to show your support of my
2136 activities, please send Bitcoin donations to my address
2137 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2142 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
2143 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
2144 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
2145 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
2146 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
2147 system
</a
> provide a practical and easy way to figure out which
2148 packages support the hardware in a given machine. The command line
2149 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
2150 convenient way to list and install packages relevant for the current
2151 hardware during system installation, both user space packages and
2152 firmware packages. The GUI background daemon on the other hand provide
2153 a pop-up proposing to install packages when a new dongle is inserted
2154 while using the computer. For example, if you plug in a smart card
2155 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
2156 that package isn
't already installed, and if you plug in a USB video
2157 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
2158 cheese is currently missing. This already work just fine.
</p
>
2160 <p
>But Isenkram depend on a database mapping from hardware IDs to
2161 package names. When I started no such database existed in Debian, so
2162 I made my own data set and included it with the isenkram package and
2163 made isenkram fetch the latest version of this database from git using
2164 http. This way the isenkram users would get updated package proposals
2165 as soon as I learned more about hardware related packages.
</p
>
2167 <p
>The hardware is identified using modalias strings. The modalias
2168 design is from the Linux kernel where most hardware descriptors are
2169 made available as a strings that can be matched using filename style
2170 globbing. It handle USB, PCI, DMI and a lot of other hardware related
2171 identifiers.
</p
>
2173 <p
>The downside to the Isenkram specific database is that there is no
2174 information about relevant distribution / Debian version, making
2175 isenkram propose obsolete packages too. But along came AppStream, a
2176 cross distribution mechanism to store and collect metadata about
2177 software packages. When I heard about the proposal, I contacted the
2178 people involved and suggested to add a hardware matching rule using
2179 modalias strings in the specification, to be able to use AppStream for
2180 mapping hardware to packages. This idea was accepted and AppStream is
2181 now a great way for a package to announce the hardware it support in a
2182 distribution neutral way. I wrote
2183 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
2184 recipe on how to add such meta-information
</a
> in a blog post last
2185 December. If you have a hardware related package in Debian, please
2186 announce the relevant hardware IDs using AppStream.
</p
>
2188 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
2189 RCX or NXT unit, announce this support using AppStream. The effect is
2190 that when you insert such LEGO robot controller into your Debian
2191 machine, Isenkram will propose to install the packages needed to get
2192 it working. The intention is that this should allow the local user to
2193 start programming his robot controller right away without having to
2194 guess what packages to use or which permissions to fix.
</p
>
2196 <p
>But when I sat down with my son the other day to program our NXT
2197 unit using his Debian Stretch computer, I discovered something
2198 annoying. The local console user (ie my son) did not get access to
2199 the USB device for programming the unit. This used to work, but no
2200 longer in Jessie and Stretch. After some investigation and asking
2201 around on #debian-devel, I discovered that this was because udev had
2202 changed the mechanism used to grant access to local devices. The
2203 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
2204 no longer applied, because LDAP users no longer was added to the
2205 plugdev group during login. Michael Biebl told me that this method
2206 was obsolete and the new method used ACLs instead. This was good
2207 news, as the plugdev mechanism is a mess when using a remote user
2208 directory like LDAP. Using ACLs would make sure a user lost device
2209 access when she logged out, even if the user left behind a background
2210 process which would retain the plugdev membership with the ConsoleKit
2211 setup. Armed with this knowledge I moved on to fix the access problem
2212 for the LEGO Mindstorms related packages.
</p
>
2214 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
2215 applied directly for a device, or is applied in
2216 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
2217 LEGO Mindstorms udev rules did not have a class, I decided to add the
2218 tag directly in the udev rules files included in the packages. Here
2219 is one example. For the nqc C compiler for the RCX, the
2220 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
2222 <p
><pre
>
2223 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
2224 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
2225 </pre
></p
>
2227 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
2228 packages using plugdev in their /lib/udev/rules.d/ files should be
2229 changed to use this tag (either directly or indirectly via
2230 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
2231 to detect this?
</p
>
2233 <p
>I
've been unable to find good documentation on the uaccess feature.
2234 It is unclear to me if the uaccess tag is an internal implementation
2235 detail like the udev-acl tag used by
2236 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
2237 indirect method is the preferred way. Michael
2238 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
2239 documentation from the systemd project
</a
> and I hope it will make
2240 this clearer. For now I use the generic classes when they exist and
2241 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
2242 directly if no such class exist.
</p
>
2244 <p
>To learn more about the isenkram system, please check out
2245 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2246 blog posts tagged isenkram
</a
>.
</p
>
2248 <p
>To help out making life for LEGO constructors in Debian easier,
2249 please join us on our IRC channel
2250 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
2251 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
2252 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
2253 list is not yet created, but we are working on it. :)
</p
>
2255 <p
>As usual, if you use Bitcoin and want to show your support of my
2256 activities, please send Bitcoin donations to my address
2257 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2262 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
2263 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
2264 <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>
2265 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
2266 <description><p
>In April we
2267 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
2268 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
2269 how to set up and administrate a Debian system. Today I am happy to
2270 report that the first draft is now publicly available. You can find
2271 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
2272 Administrator
's Handbook page
</a
> (under Other languages). The first
2273 eight chapters have a first draft translation, and we are working on
2274 proofreading the content. If you want to help out, please start
2276 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2277 hosted weblate project page
</a
>, and get in touch using
2278 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2279 translators mailing list
</a
>. Please also check out
2280 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2281 contributors
</a
>. A good way to contribute is to proofread the text
2282 and update weblate if you find errors.
</p
>
2284 <p
>Our goal is still to make the Norwegian book available on paper as well as
2285 electronic form.
</p
>
2290 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
2291 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
2292 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
2293 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
2294 <description><p
>This summer, I read a great article
2295 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
2296 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
2297 how to profile multi-threaded programs. It presented a system for
2298 profiling software by running experiences in the running program,
2299 testing how run time performance is affected by
"speeding up
" parts of
2300 the code to various degrees compared to a normal run. It does this by
2301 slowing down parallel threads while the
"faster up
" code is running
2302 and measure how this affect processing time. The processing time is
2303 measured using probes inserted into the code, either using progress
2304 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
2305 can also measure unmodified code by measuring complete the program
2306 runtime and running the program several times instead.
</p
>
2308 <p
>The project and presentation was so inspiring that I would like to
2309 get the system into Debian. I
2310 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
2311 a WNPP request for it
</a
> and contacted upstream to try to make the
2312 system ready for Debian by sending patches. The build process need to
2313 be changed a bit to avoid running
'git clone
' to get dependencies, and
2314 to include the JavaScript web page used to visualize the collected
2315 profiling information included in the source package.
2316 But I expect that should work out fairly soon.
</p
>
2318 <p
>The way the system work is fairly simple. To run an coz experiment
2319 on a binary with debug symbols available, start the program like this:
2321 <p
><blockquote
><pre
>
2322 coz run --- program-to-run
2323 </pre
></blockquote
></p
>
2325 <p
>This will create a text file profile.coz with the instrumentation
2326 information. To show what part of the code affect the performance
2327 most, use a web browser and either point it to
2328 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
2329 or use the copy from git (in the gh-pages branch). Check out this web
2330 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
2331 profiling more useful you include
&lt;coz.h
&gt; and insert the
2332 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
2333 code, rebuild and run the profiler. This allow coz to do more
2334 targeted experiments.
</p
>
2336 <p
>A video published by ACM
2337 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
2338 Coz profiler
</a
> is available from Youtube. There is also a paper
2339 from the
25th Symposium on Operating Systems Principles available
2341 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
2342 finding code that counts with causal profiling
</a
>.
</p
>
2344 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
2345 for Coz is available from github. It will only build with clang
2347 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
2348 feature missing in GCC
</a
>, but I
've submitted
2349 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
2350 it
</a
> and hope it will be included in the upstream source soon.
</p
>
2352 <p
>Please get in touch if you, like me, would like to see this piece
2353 of software in Debian. I would very much like some help with the
2354 packaging effort, as I lack the in depth knowledge on how to package
2355 C++ libraries.
</p
>
2360 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
2361 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
2362 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
2363 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
2364 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
2365 to be a slight challenge. Here is the recipe if I ever need to do it
2366 again. It all started by me wanting to try the recipe to set up
2367 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
2368 hardened Android installation
</a
> from the Tor project blog on a
2369 device I had access to. It is a old mobile phone with a broken
2370 microphone The initial idea had been to just
2371 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
2372 CyanogenMod on it
</a
>, but did not quite find time to start on it
2373 until a few days ago.
</p
>
2375 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
2376 loader (press volume down and power at the same time), (
2) select
2377 'fastboot
' before (
3) connecting the device via USB to a Linux
2378 machine, (
4) request the device identifier token by running
'fastboot
2379 oem get_identifier_token
', (
5) request the device unlocking key using
2380 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
2381 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
2383 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
2384 or newer, and the device I was working on had
2.00.0027. This
2385 apparently can be easily fixed by downloading a Windows program and
2386 running it on your Windows machine, if you accept the terms Microsoft
2387 require you to accept to use Windows - which I do not. So I had to
2388 come up with a different approach. I got a lot of help from AndyCap
2389 on #nuug, and would not have been able to get this working without
2392 <p
>First I needed to extract the hboot firmware from
2393 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
2394 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
2395 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
2396 project named unruu
</a
> using libunshield. The unshield tool did not
2397 recognise the file format, but unruu worked and extracted rom.zip,
2398 containing the new hboot firmware and a text file describing which
2399 devices it would work for.
</p
>
2401 <p
>Next, I needed to get the new firmware into the device. For this I
2402 followed some instructions
2403 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
2404 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
2405 machine with Debian testing:
</p
>
2407 <p
><pre
>
2408 adb reboot-bootloader
2409 fastboot oem rebootRUU
2410 fastboot flash zip rom.zip
2411 fastboot flash zip rom.zip
2413 </pre
></p
>
2415 <p
>The flash command apparently need to be done twice to take effect,
2416 as the first is just preparations and the second one do the flashing.
2417 The adb command is just to get to the boot loader menu, so turning the
2418 device on while holding volume down and the power button should work
2421 <p
>With the new hboot version in place I could start following the
2422 instructions on the HTC developer web site. I got the device token
2423 like this:
</p
>
2425 <p
><pre
>
2426 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
2429 <p
>And once I got the unlock code via email, I could use it like
2432 <p
><pre
>
2433 fastboot flash unlocktoken Unlock_code.bin
2434 </pre
></p
>
2436 <p
>And with that final step in place, the phone was unlocked and I
2437 could start stuffing the software of my own choosing into the device.
2438 So far I only inserted a replacement recovery image to wipe the phone
2439 before I start. We will see what happen next. Perhaps I should
2440 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
2445 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
2446 <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>
2447 <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>
2448 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
2449 <description><p
>For a while now, I have wanted to test
2450 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
2451 said to provide end to end encrypted communication and several of my
2452 friends and family are already using it. As I by choice do not own a
2453 mobile phone, this proved to be harder than expected. And I wanted to
2454 have the source of the client and know that it was the code used on my
2455 machine. But yesterday I managed to get it working. I used the
2456 Github source, compared it to the source in
2457 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
2458 Signal Chrome app
</a
> available from the Chrome web store, applied
2459 patches to use the production Signal servers, started the app and
2460 asked for the hidden
"register without a smart phone
" form. Here is
2461 the recipe how I did it.
</p
>
2463 <p
>First, I fetched the Signal desktop source from Github, using
2466 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2469 <p
>Next, I patched the source to use the production servers, to be
2470 able to talk to other Signal users:
</p
>
2473 cat
&lt;
&lt;EOF | patch -p0
2474 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2475 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2476 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
2481 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
2482 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
2483 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
2484 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
2485 var messageReceiver;
2486 window.getSocketStatus = function() {
2487 if (messageReceiver) {
2488 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
2489 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
2490 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
2493 'use strict
';
2494 - var BUILD_EXPIRATION =
0;
2495 + var BUILD_EXPIRATION =
1474492690000;
2497 window.extension = window.extension || {};
2502 <p
>The first part is changing the servers, and the second is updating
2503 an expiration timestamp. This timestamp need to be updated regularly.
2504 It is set
90 days in the future by the build process (Gruntfile.js).
2505 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
2507 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
2508 script to launch Signal in Chromium.
</p
>
2515 --proxy-server=
"socks://localhost:
9050" \
2516 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
2519 <p
> The script start the app and configure Chromium to use the Tor
2520 SOCKS5 proxy to make sure those controlling the Signal servers (today
2521 Amazon and Whisper Systems) as well as those listening on the lines
2522 will have a harder time location my laptop based on the Signal
2523 connections if they use source IP address.
</p
>
2525 <p
>When the script starts, one need to follow the instructions under
2526 "Standalone Registration
" in the CONTRIBUTING.md file in the git
2527 repository. I right clicked on the Signal window to get up the
2528 Chromium debugging tool, visited the
'Console
' tab and wrote
2529 'extension.install(
"standalone
")
' on the console prompt to get the
2530 registration form. Then I entered by land line phone number and
2531 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
2532 repeated the verification code three times. After entering the number
2533 into the verification code field in the form, I could start using
2534 Signal from my laptop.
2536 <p
>As far as I can tell, The Signal app will leak who is talking to
2537 whom and thus who know who to those controlling the central server,
2538 but such leakage is hard to avoid with a centrally controlled server
2539 setup. It is something to keep in mind when using Signal - the
2540 content of your chats are harder to intercept, but the meta data
2541 exposing your contact network is available to people you do not know.
2542 So better than many options, but not great. And sadly the usage is
2543 connected to my land line, thus allowing those controlling the server
2544 to associate it to my home and person. I would prefer it if only
2545 those I knew could tell who I was on Signal. There are options
2546 avoiding such information leakage, but most of my friends are not
2547 using them, so I am stuck with Signal for now.
</p
>
2549 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
2551 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
2552 and updated recipe for using the Signal app without a mobile
2553 phone
</a
>.
</p
>
2558 <title>The new
"best
" multimedia player in Debian?
</title>
2559 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
2560 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
2561 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
2562 <description><p
>When I set out a few weeks ago to figure out
2563 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
2564 multimedia player in Debian claimed to support most file formats /
2565 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
2566 the various players claimed support for. The range was from
55 to
130
2567 MIME types. I suspect most media formats are supported by all
2568 players, but this is not really reflected in the MimeTypes values in
2569 their desktop files. There are probably also some bogus MIME types
2570 listed, but it is hard to identify which one this is.
</p
>
2572 <p
>Anyway, in the mean time I got in touch with upstream for some of
2573 the players suggesting to add more MIME types to their desktop files,
2574 and decided to spend some time myself improving the situation for my
2575 favorite media player VLC. The fixes for VLC entered Debian unstable
2576 yesterday. The complete list of MIME types can be seen on the
2577 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
2578 player MIME type support status
</a
> Debian wiki page.
</p
>
2580 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
2581 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
2582 kmplayer. I am sure some of the other players desktop files support
2583 several of the formats currently listed as working only with vlc,
2584 toten and parole.
</p
>
2586 <p
>A sad observation is that only
14 MIME types are listed as
2587 supported by all the tested multimedia players in Debian in their
2588 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
2589 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
2590 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
2591 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
2592 it sad that video/ogg and video/webm is not supported by all the media
2593 players in Debian. As far as I can tell, all of them can handle both
2599 <title>A program should be able to open its own files on Linux
</title>
2600 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
2601 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
2602 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
2603 <description><p
>Many years ago, when koffice was fresh and with few users, I
2604 decided to test its presentation tool when making the slides for a
2605 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
2606 wrote the first draft of the slides, saved the result and went to bed
2607 the day before I would give the talk. The next day I took a plane to
2608 the location where the meeting should take place, and on the plane I
2609 started up koffice again to polish the talk a bit, only to discover
2610 that kpresenter refused to load its own data file. I cursed a bit and
2611 started making the slides again from memory, to have something to
2612 present when I arrived. I tested that the saved files could be
2613 loaded, and the day seemed to be rescued. I continued to polish the
2614 slides until I suddenly discovered that the saved file could no longer
2615 be loaded into kpresenter. In the end I had to rewrite the slides
2616 three times, condensing the content until the talk became shorter and
2617 shorter. After the talk I was able to pinpoint the problem
&ndash;
2618 kpresenter wrote inline images in a way itself could not understand.
2619 Eventually that bug was fixed and kpresenter ended up being a great
2620 program to make slides. The point I
'm trying to make is that we
2621 expect a program to be able to load its own data files, and it is
2622 embarrassing to its developers if it can
't.
</p
>
2624 <p
>Did you ever experience a program failing to load its own data
2625 files from the desktop file browser? It is not a uncommon problem. A
2626 while back I discovered that the screencast recorder
2627 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
2628 browser would refuse to open. No video player claimed to understand
2629 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
2630 returning the application/ogg MIME type, which no video player I had
2631 installed listed as a MIME type they would understand. I asked for
2632 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
2633 behavour
</a
> and use the MIME type video/ogg instead. I also asked
2634 several video players to add video/ogg to their desktop files, to give
2635 the file browser an idea what to do about Ogg Theora files. After a
2636 while, the desktop file browsers in Debian started to handle the
2637 output from gtk-recordmydesktop properly.
</p
>
2639 <p
>But history repeats itself. A few days ago I tested the music
2640 system Rosegarden again, and I discovered that the KDE and xfce file
2641 browsers did not know what to do with the Rosegarden project files
2642 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
2643 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
2644 included in the next upload. To increase the chance of me remembering
2645 how to fix the problem next time some program fail to load its files
2646 from the file browser, here are some notes on how to fix it.
</p
>
2648 <p
>The file browsers in Debian in general operates on MIME types.
2649 There are two sources for the MIME type of a given file. The output from
2650 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
2651 shared MIME type registry (under /usr/share/mime/). The file MIME
2652 type is mapped to programs supporting the MIME type, and this
2653 information is collected from
2654 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
2655 desktop files
</a
> available in /usr/share/applications/. If there is
2656 one desktop file claiming support for the MIME type of the file, it is
2657 activated when asking to open a given file. If there are more, one
2658 can normally select which one to use by right-clicking on the file and
2659 selecting the wanted one using
'Open with
' or similar. In general
2660 this work well. But it depend on each program picking a good MIME
2662 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
2663 MIME type registered with IANA
</a
>), file and/or the shared MIME
2664 registry recognizing the file and the desktop file to list the MIME
2665 type in its list of supported MIME types.
</p
>
2667 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
2668 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
2669 Shared MIME database
</a
> look like this:
</p
>
2671 <p
><blockquote
><pre
>
2672 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2673 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
2674 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
2675 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
2676 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
2677 &lt;glob pattern=
"*.rg
"/
&gt;
2678 &lt;/mime-type
&gt;
2679 &lt;/mime-info
&gt;
2680 </pre
></blockquote
></p
>
2682 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
2683 (it is a gzipped XML file). Note, it is much better to use an
2684 official MIME type registered with IANA than it is to make up ones own
2685 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
2687 <p
>The desktop file of the rosegarden program failed to list
2688 audio/x-rosegarden in its list of supported MIME types, causing the
2689 file browsers to have no idea what to do with *.rg files:
</p
>
2691 <p
><blockquote
><pre
>
2692 % grep Mime /usr/share/applications/rosegarden.desktop
2693 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
2694 X-KDE-NativeMimeType=audio/x-rosegarden-composition
2696 </pre
></blockquote
></p
>
2698 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
2699 MimeType= line.
</p
>
2701 <p
>If you run into a file which fail to open the correct program when
2702 selected from the file browser, please check out the output from
2703 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
2704 MIME type is registered somewhere under /usr/share/mime/ and check
2705 that some desktop file under /usr/share/applications/ is claiming
2706 support for this MIME type. If not, please report a bug to have it
2712 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
2713 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
2714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
2715 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
2716 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
2717 system
</a
> is a user-focused solution in Debian for handling hardware
2718 related packages. The idea is to have a database of mappings between
2719 hardware and packages, and pop up a dialog suggesting for the user to
2720 install the packages to use a given hardware dongle. Some use cases
2721 are when you insert a Yubikey, it proposes to install the software
2722 needed to control it; when you insert a braille reader list it
2723 proposes to install the packages needed to send text to the reader;
2724 and when you insert a ColorHug screen calibrator it suggests to
2725 install the driver for it. The system work well, and even have a few
2726 command line tools to install firmware packages and packages for the
2727 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
2729 <p
>The system was initially written using aptdaemon, because I found
2730 good documentation and example code on how to use it. But aptdaemon
2731 is going away and is generally being replaced by
2732 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
2733 so Isenkram needed a rewrite. And today, thanks to the great patch
2734 from my college Sunil Mohan Adapa in the FreedomBox project, the
2735 rewrite finally took place. I
've just uploaded a new version of
2736 Isenkram into Debian Unstable with the patch included, and the default
2737 for the background daemon is now to use PackageKit. To check it out,
2738 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
2739 and see if it is recognised.
</p
>
2741 <p
>If you want to know what kind of packages isenkram would propose for
2742 the machine it is running on, you can check out the isenkram-lookup
2743 program. This is what it look like on a Thinkpad X230:
</p
>
2745 <p
><blockquote
><pre
>
2761 </pre
></blockquote
></p
>
2763 <p
>The hardware mappings come from several places. The preferred way
2764 is for packages to announce their hardware support using
2765 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
2766 cross distribution appstream system
</a
>.
2768 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
2769 blog posts about isenkram
</a
> to learn how to do that.
</p
>
2774 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
2775 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
2776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
2777 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
2778 <description><p
>Yesterday I updated the
2779 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
2780 package in Debian
</a
> with a few patches sent to me by skilled and
2781 enterprising users. There were some nice user and visible changes.
2782 First of all, both desktop menu entries now work. A design flaw in
2783 one of the script made the history graph fail to show up (its PNG was
2784 dumped in ~/.xsession-errors) if no controlling TTY was available.
2785 The script worked when called from the command line, but not when
2786 called from the desktop menu. I changed this to look for a DISPLAY
2787 variable or a TTY before deciding where to draw the graph, and now the
2788 graph window pop up as expected.
</p
>
2790 <p
>The next new feature is a discharge rate estimator in one of the
2791 graphs (the one showing the last few hours). New is also the user of
2792 colours showing charging in blue and discharge in red. The percentages
2793 of this graph is relative to last full charge, not battery design
2796 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
2798 <p
>The other graph show the entire history of the collected battery
2799 statistics, comparing it to the design capacity of the battery to
2800 visualise how the battery life time get shorter over time. The red
2801 line in this graph is what the previous graph considers
100 percent:
2803 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
2805 <p
>In this graph you can see that I only charge the battery to
80
2806 percent of last full capacity, and how the capacity of the battery is
2807 shrinking. :(
</p
>
2809 <p
>The last new feature is in the collector, which now will handle
2810 more hardware models. On some hardware, Linux power supply
2811 information is stored in /sys/class/power_supply/ACAD/, while the
2812 collector previously only looked in /sys/class/power_supply/AC/. Now
2813 both are checked to figure if there is power connected to the
2816 <p
>If you are interested in how your laptop battery is doing, please
2818 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
2819 in Debian unstable, or rebuild it on Jessie to get it working on
2820 Debian stable. :) The upstream source is available from
<a
2821 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
2822 Patches are very welcome.
</p
>
2824 <p
>As usual, if you use Bitcoin and want to show your support of my
2825 activities, please send Bitcoin donations to my address
2826 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2831 <title>Debian now with ZFS on Linux included
</title>
2832 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
2833 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
2834 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
2835 <description><p
>Today, after many years of hard work from many people,
2836 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
2837 Debian. The package status can be seen on
2838 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
2839 for zfs-linux
</a
>. and
2840 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2841 team status page
</a
>. If you want to help out, please join us.
2842 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
2843 source code
</a
> is available via git on Alioth. It would also be
2844 great if you could help out with
2845 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
2846 it is an important piece of the puzzle to get ZFS working.
</p
>
2851 <title>What is the best multimedia player in Debian?
</title>
2852 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
2853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
2854 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
2855 <description><p
><strong
>Where I set out to figure out which multimedia player in
2856 Debian claim support for most file formats.
</strong
></p
>
2858 <p
>A few years ago, I had a look at the media support for Browser
2859 plugins in Debian, to get an idea which plugins to include in Debian
2860 Edu. I created a script to extract the set of supported MIME types
2861 for each plugin, and used this to find out which multimedia browser
2862 plugin supported most file formats / media types.
2863 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
2864 result
</a
> can still be seen on the Debian wiki, even though it have
2865 not been updated for a while. But browser plugins are less relevant
2866 these days, so I thought it was time to look at standalone
2869 <p
>A few days ago I was tired of VLC not being listed as a viable
2870 player when I wanted to play videos from the Norwegian National
2871 Broadcasting Company, and decided to investigate why. The cause is a
2872 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
2873 desktop file
</a
>. In the process I wrote a script to compare the set
2874 of MIME types announced in the desktop file and the browser plugin,
2875 only to discover that there is quite a large difference between the
2876 two for VLC. This discovery made me dig up the script I used to
2877 compare browser plugins, and adjust it to compare desktop files
2878 instead, to try to figure out which multimedia player in Debian
2879 support most file formats.
</p
>
2881 <p
>The result can be seen on the Debian Wiki, as
2882 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
2883 table listing all MIME types supported by one of the packages included
2884 in the table
</a
>, with the package supporting most MIME types being
2885 listed first in the table.
</p
>
2887 </p
>The best multimedia player in Debian? It is totem, followed by
2888 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
2889 kmplayer. Time for the other players to update their announced MIME
2895 <title>The Pyra - handheld computer with Debian preinstalled
</title>
2896 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
2897 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
2898 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
2899 <description>A friend of mine made me aware of
2900 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
2901 handheld computer which will be delivered with Debian preinstalled. I
2902 would love to get one of those for my birthday. :)
</p
>
2904 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
2905 plugs and many others connectors, and include a full keyboard and a
5"
2906 LCD touch screen. The
6000mAh battery is claimed to provide a whole
2907 day of battery life time, but I have not seen any independent tests
2908 confirming this. The vendor is still collecting preorders, and the
2909 last I heard last night was that
22 more orders were needed before
2910 production started.
</p
>
2912 <p
>As far as I know, this is the first handheld preinstalled with
2913 Debian. Please let me know if you know of any others. Is it the
2914 first computer being sold with Debian preinstalled?
</p
>
2919 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
2920 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
2921 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
2922 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
2923 <description><p
>During this weekends
2924 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
2925 squashing party and developer gathering
</a
>, we decided to do our part
2926 to make sure there are good books about Debian available in Norwegian
2927 Bokmål, and got in touch with the people behind the
2928 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
2929 project
</a
> to get started. If you want to help out, please start
2931 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
2932 hosted weblate project page
</a
>, and get in touch using
2933 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
2934 translators mailing list
</a
>. Please also check out
2935 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
2936 contributors
</a
>.
</p
>
2938 <p
>The book is already available on paper in English, French and
2939 Japanese, and our goal is to get it available on paper in Norwegian
2940 Bokmål too. In addition to the paper edition, there are also EPUB and
2941 Mobi versions available. And there are incomplete translations
2942 available for many more languages.
</p
>
2947 <title>One in two hundred Debian users using ZFS on Linux?
</title>
2948 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
2949 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
2950 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
2951 <description><p
>Just for fun I had a look at the popcon number of ZFS related
2952 packages in Debian, and was quite surprised with what I found. I use
2953 ZFS myself at home, but did not really expect many others to do so.
2954 But I might be wrong.
</p
>
2956 <p
>According to
2957 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
2958 results for spl-linux
</a
>, there are
1019 Debian installations, or
2959 0.53% of the population, with the package installed. As far as I know
2960 the only use of the spl-linux package is as a support library for ZFS
2961 on Linux, so I use it here as proxy for measuring the number of ZFS
2962 installation on Linux in Debian. In the kFreeBSD variant of Debian
2963 the ZFS feature is already available, and there
2964 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
2965 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
2966 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
2968 <p
>But even though the Debian project leader Lucas Nussbaum
2969 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
2970 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
2971 cleared, the package is still not in Debian. The package is again in
2972 the NEW queue. Several uploads have been rejected so far because the
2973 debian/copyright file was incomplete or wrong, but there is no reason
2974 to give up. The current status can be seen on
2975 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
2976 team status page
</a
>, and
2977 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
2978 source code
</a
> is available on Alioth.
</p
>
2980 <p
>As I want ZFS to be included in next version of Debian to make sure
2981 my home server can function in the future using only official Debian
2982 packages, and the current blocker is to get the debian/copyright file
2983 accepted by the FTP masters in Debian, I decided a while back to try
2984 to help out the team. This was the background for my blog post about
2985 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
2986 updating and checking debian/copyright semi-automatically
</a
>, and I
2987 used the techniques I explored there to try to find any errors in the
2988 copyright file. It is not very easy to check every one of the around
2989 2000 files in the source package, but I hope we this time got it
2990 right. If you want to help out, check out the git source and try to
2991 find missing entries in the debian/copyright file.
</p
>
2996 <title>Full battery stats collector is now available in Debian
</title>
2997 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
2998 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
2999 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
3000 <description><p
>Since this morning, the battery-stats package in Debian include an
3001 extended collector that will collect the complete battery history for
3002 later processing and graphing. The original collector store the
3003 battery level as percentage of last full level, while the new
3004 collector also record battery vendor, model, serial number, design
3005 full level, last full level and current battery level. This make it
3006 possible to predict the lifetime of the battery as well as visualise
3007 the energy flow when the battery is charging or discharging.
</p
>
3009 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
3010 in the version
0.5.1 package in unstable. Get the new battery level graph
3011 and lifetime prediction by running:
3013 <p
><pre
>
3014 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
3015 </pre
></p
>
3017 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
3019 <p
>The flow in/out of the battery can be seen by running (no menu
3020 entry yet):
</p
>
3022 <p
><pre
>
3023 /usr/share/battery-stats/battery-stats-graph-flow
3024 </pre
></p
>
3026 <p
>I
'm not quite happy with the way the data is visualised, at least
3027 when there are few data points. The graphs look a bit better with a
3028 few years of data.
</p
>
3030 <p
>A while back one important feature I use in the battery stats
3031 collector broke in Debian. The scripts in
3032 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
3033 suspect it happened when Jessie started using systemd, but I do not
3034 know. The issue is reported as
3035 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
3036 pm-utils. I managed to work around it by adding an udev rule to call
3037 the collector script every time the power connector is connected and
3038 disconnected. With this fix in place it was finally time to make a
3039 new release of the package, and get it into Debian.
</p
>
3041 <p
>If you are interested in how your laptop battery is doing, please
3043 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
3044 in Debian unstable, or rebuild it on Jessie to get it working on
3045 Debian stable. :) The upstream source is available from
3046 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
3047 As always, patches are very welcome.
</p
>
3052 <title>Making battery measurements a little easier in Debian
</title>
3053 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
3054 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
3055 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
3056 <description><p
>Back in September, I blogged about
3057 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
3058 system I wrote to collect statistics about my laptop battery
</a
>, and
3059 how it showed the decay and death of this battery (now replaced). I
3060 created a simple deb package to handle the collection and graphing,
3061 but did not want to upload it to Debian as there were already
3062 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
3063 package in Debian
</a
> that should do the same thing, and I did not see
3064 a point of uploading a competing package when battery-stats could be
3065 fixed instead. I reported a few bugs about its non-function, and
3066 hoped someone would step in and fix it. But no-one did.
</p
>
3068 <p
>I got tired of waiting a few days ago, and took matters in my own
3069 hands. The end result is that I am now the new upstream developer of
3070 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
3071 battery-stats in Debian, and the package in Debian unstable is finally
3072 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
3073 information provided by the Linux kernel. If you install the
3074 battery-stats package from unstable now, you will be able to get a
3075 graph of the current battery fill level, to get some idea about the
3076 status of the battery. The source package build and work just fine in
3077 Debian testing and stable (and probably oldstable too, but I have not
3078 tested). The default graph you get for that system look like this:
</p
>
3080 <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
>
3082 <p
>My plans for the future is to merge my old scripts into the
3083 battery-stats package, as my old scripts collected a lot more details
3084 about the battery. The scripts are merged into the upstream
3085 battery-stats git repository already, but I am not convinced they work
3086 yet, as I changed a lot of paths along the way. Will have to test a
3087 bit more before I make a new release.
</p
>
3089 <p
>I will also consider changing the file format slightly, as I
3090 suspect the way I combine several values into one field might make it
3091 impossible to know the type of the value when using it for processing
3092 and graphing.
</p
>
3094 <p
>If you would like I would like to keep an close eye on your laptop
3095 battery, check out the battery-stats package in
3096 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
3098 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
3099 I would love some help to improve the system further.
</p
>
3104 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
3105 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
3106 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
3107 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
3108 <description><p
>Making packages for Debian requires quite a lot of attention to
3109 details. And one of the details is the content of the
3110 debian/copyright file, which should list all relevant licenses used by
3111 the code in the package in question, preferably in
3112 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
3113 readable DEP5 format
</a
>.
</p
>
3115 <p
>For large packages with lots of contributors it is hard to write
3116 and update this file manually, and if you get some detail wrong, the
3117 package is normally rejected by the ftpmasters. So getting it right
3118 the first time around get the package into Debian faster, and save
3119 both you and the ftpmasters some work.. Today, while trying to figure
3120 out what was wrong with
3121 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
3122 zfsonlinux copyright file
</a
>, I decided to spend some time on
3123 figuring out the options for doing this job automatically, or at least
3124 semi-automatically.
</p
>
3126 <p
>Lucikly, there are at least two tools available for generating the
3127 file based on the code in the source package,
3128 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
3129 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
3130 not sure which one of them came first, but both seem to be able to
3131 create a sensible draft file. As far as I can tell, none of them can
3132 be trusted to get the result just right, so the content need to be
3133 polished a bit before the file is OK to upload. I found the debmake
3135 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
3136 blog posts from
2014</a
>.
3138 <p
>To generate using debmake, use the -cc option:
3140 <p
><pre
>
3141 debmake -cc
> debian/copyright
3142 </pre
></p
>
3144 <p
>Note there are some problems with python and non-ASCII names, so
3145 this might not be the best option.
</p
>
3147 <p
>The cme option is based on a config parsing library, and I found
3149 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
3150 blog post from
2015</a
>. To generate using cme, use the
'update
3151 dpkg-copyright
' option:
3153 <p
><pre
>
3154 cme update dpkg-copyright
3155 </pre
></p
>
3157 <p
>This will create or update debian/copyright. The cme tool seem to
3158 handle UTF-
8 names better than debmake.
</p
>
3160 <p
>When the copyright file is created, I would also like some help to
3161 check if the file is correct. For this I found two good options,
3162 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
3163 to focus on license types and file matching, and is able to detect
3164 ineffective blocks in the copyright file. The latter reports missing
3165 copyright holders and years, but was confused by inconsistent license
3166 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
3167 fix all issues reported by them before uploading. But I do not know
3168 if the tools and the ftpmasters agree on what is important to fix in a
3169 copyright file, so the package might still be rejected.
</p
>
3171 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
3172 will read through the source and try to find all copyright statements.
3173 It is not comparing the result to the content of debian/copyright, but
3174 can be useful when verifying the content of the copyright file.
</p
>
3176 <p
>Are you aware of better tools in Debian to create and update
3177 debian/copyright file. Please let me know, or blog about it on
3178 planet.debian.org.
</p
>
3180 <p
>As usual, if you use Bitcoin and want to show your support of my
3181 activities, please send Bitcoin donations to my address
3182 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3184 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
3185 on how to use licensecheck and cdbs to create a draft copyright file
3187 <p
><pre
>
3188 licensecheck --copyright -r `find * -type f` | \
3189 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
3190 </pre
></p
>
3192 <p
>He mentioned that he normally check the generated file into the
3193 version control system to make it easier to discover license and
3194 copyright changes in the upstream source. I will try to do the same
3195 with my packages in the future.
</p
>
3197 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
3198 against using -quiet for new users, so I removed it from the proposed
3199 command line.
</p
>
3204 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
3205 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
3206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
3207 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
3208 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
3209 is taking shape in Debian, and one provided feature is a very
3210 convenient way to tell you which package to install to make a given
3211 firmware file available when the kernel is looking for it. This can
3212 be done using apt-file too, but that is for someone else to blog
3215 <p
>Here is a small recipe to find the package with a given firmware
3216 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
3217 picked from the set of firmware announced using appstream in Debian
3218 unstable. In general you would be looking for the firmware requested
3219 by the kernel during kernel module loading. To find the package
3220 providing the example file, do like this:
</p
>
3222 <blockquote
><pre
>
3223 % apt install appstream
3227 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
3228 awk
'/Package:/ {print $
2}
'
3231 </pre
></blockquote
>
3233 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
3234 appstream wiki
</a
> page to learn how to embed the package metadata in
3235 a way appstream can use.
</p
>
3237 <p
>This same approach can be used to find any package supporting a
3238 given MIME type. This is very useful when you get a file you do not
3239 know how to handle. First find the mime type using
<tt
>file
3240 --mime-type
</tt
>, and next look up the package providing support for
3241 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
3242 and you can find all packages handling this type like this:
</p
>
3244 <blockquote
><pre
>
3245 % apt install appstream
3249 % appstreamcli what-provides mimetype image/svg+xml | \
3250 awk
'/Package:/ {print $
2}
'
3272 </pre
></blockquote
>
3274 <p
>I believe the MIME types are fetched from the desktop file for
3275 packages providing appstream metadata.
</p
>
3280 <title>Creepy, visualise geotagged social media information - nice free software
</title>
3281 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
3282 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
3283 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
3284 <description><p
>Most people seem not to realise that every time they walk around
3285 with the computerised radio beacon known as a mobile phone their
3286 position is tracked by the phone company and often stored for a long
3287 time (like every time a SMS is received or sent). And if their
3288 computerised radio beacon is capable of running programs (often called
3289 mobile apps) downloaded from the Internet, these programs are often
3290 also capable of tracking their location (if the app requested access
3291 during installation). And when these programs send out information to
3292 central collection points, the location is often included, unless
3293 extra care is taken to not send the location. The provided
3294 information is used by several entities, for good and bad (what is
3295 good and bad, depend on your point of view). What is certain, is that
3296 the private sphere and the right to free movement is challenged and
3297 perhaps even eradicated for those announcing their location this way,
3298 when they share their whereabouts with private and public
3301 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
3303 <p
>The phone company logs provide a register of locations to check out
3304 when one want to figure out what the tracked person was doing. It is
3305 unavailable for most of us, but provided to selected government
3306 officials, company staff, those illegally buying information from
3307 unfaithful servants and crackers stealing the information. But the
3308 public information can be collected and analysed, and a free software
3309 tool to do so is called
3310 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
3311 discovered it when I read
3312 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
3313 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
3314 November
2014, and decided to check if it was available in Debian.
3315 The python program was in Debian, but
3316 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
3317 Debian
</a
> was completely broken and practically unmaintained. I
3318 uploaded a new version which did not work quite right, but did not
3319 have time to fix it then. This Christmas I decided to finally try to
3320 get Creepy operational in Debian. Now a fixed version is available in
3321 Debian unstable and testing, and almost all Debian specific patches
3323 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
3325 <p
>The Creepy program visualises geolocation information fetched from
3326 Twitter, Instagram, Flickr and Google+, and allow one to get a
3327 complete picture of every social media message posted recently in a
3328 given area, or track the movement of a given individual across all
3329 these services. Earlier it was possible to use the search API of at
3330 least some of these services without identifying oneself, but these
3331 days it is impossible. This mean that to use Creepy, you need to
3332 configure it to log in as yourself on these services, and provide
3333 information to them about your search interests. This should be taken
3334 into account when using Creepy, as it will also share information
3335 about yourself with the services.
</p
>
3337 <p
>The picture above show the twitter messages sent from (or at least
3338 geotagged with a position from) the city centre of Oslo, the capital
3339 of Norway. One useful way to use Creepy is to first look at
3340 information tagged with an area of interest, and next look at all the
3341 information provided by one or more individuals who was in the area.
3342 I tested it by checking out which celebrity provide their location in
3343 twitter messages by checkout out who sent twitter messages near a
3344 Norwegian TV station, and next could track their position over time,
3345 making it possible to locate their home and work place, among other
3346 things. A similar technique have been
3347 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
3348 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
3349 tool to discover lying governments, and a useful tool to help people
3350 understand the value of the private information they provide to the
3353 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
3354 it depend on several python modules currently missing in Jessie (at
3355 least python-instagram, python-flickrapi and
3356 python-requests-toolbelt).
</p
>
3358 <p
>(I have uploaded
3359 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
3360 screenshots.debian.net
</a
> and licensed it under the same terms as the
3361 Creepy program in Debian.)
</p
>
3366 <title>Always download Debian packages using Tor - the simple recipe
</title>
3367 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
3368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
3369 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
3370 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
3371 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
3372 that those listening on the Internet lines would have good reason to
3373 believe a computer have a given security hole
</a
> if it download a
3374 security fix from a Debian mirror. This is a good reason to always
3375 use encrypted connections to the Debian mirror, to make sure those
3376 listening do not know which IP address to attack. In August, Richard
3377 Hartmann observed that encryption was not enough, when it was possible
3378 to interfere download size to security patches or the fact that
3379 download took place shortly after a security fix was released, and
3380 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
3381 to always use Tor to download packages from the Debian mirror
</a
>. He
3382 was not the first to propose this, as the
3383 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
3384 package by Tim Retout already existed to make it easy to convince apt
3385 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
3386 aware of that package when I read the blog post from Richard.
</p
>
3388 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
3389 sysadmins, and he set up a Tor hidden service on one of the central
3390 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
3391 it possible to download packages directly between two tor nodes,
3392 making sure the network traffic always were encrypted.
</p
>
3394 <p
>Here is a short recipe for enabling this on your machine, by
3395 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
3396 urls with tor+http and tor+https, and using the hidden service instead
3397 of the official Debian mirror site. I recommend installing
3398 <tt
>etckeeper
</tt
> before you start to have a history of the changes
3399 done in /etc/.
</p
>
3401 <blockquote
><pre
>
3402 apt install apt-transport-tor
3403 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
3404 sed -i
's% http% tor+http%
' /etc/apt/sources.list
3405 </pre
></blockquote
>
3407 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
3408 the sed commands for these too. The sed command is assuming your are
3409 using the ftp.debian.org Debian mirror. Adjust the command (or just
3410 edit the file manually) to match your mirror.
</p
>
3412 <p
>This work in Debian Jessie and later. Note that tools like
3413 <tt
>apt-file
</tt
> only recently started using the apt transport
3414 system, and do not work with these tor+http URLs. For
3415 <tt
>apt-file
</tt
> you need the version currently in experimental,
3416 which need a recent apt version currently only in unstable. So if you
3417 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
3419 <p
>Another advantage from this change is that your machine will start
3420 using Tor regularly and at fairly random intervals (every time you
3421 update the package lists or upgrade or install a new package), thus
3422 masking other Tor traffic done from the same machine. Using Tor will
3423 become normal for the machine in question.
</p
>
3425 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
3426 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
3427 enabled. It would be great if it was the default on any Debian
3433 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
3434 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
3435 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
3436 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
3437 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
3438 call the car license plate numbers in those days. I would write the
3439 numbers down in my little book and compare notes with the other kids
3440 to see how many region codes we had seen and if we had seen some
3441 exotic or special region codes and numbers. It was a fun game to pass
3442 time, as we kids have plenty of it.
</p
>
3444 <p
>A few days I came across
3445 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
3446 project
</a
>, a free software project to automatically discover and
3447 report license plates in images and video streams, and provide the
3448 "car numbers
" in a machine readable format. I
've been looking for
3449 such system for a while now, because I believe it is a bad idea that the
3450 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
3451 number plate recognition
</a
> tool only is available in the hands of
3452 the powerful, and want it to be available also for the powerless to
3453 even the score when it comes to surveillance and sousveillance. I
3454 discovered the developer
3455 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
3456 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
3457 help him get it into shape to get the package uploaded into the Debian
3460 <p
>Today we finally managed to get the package into shape and uploaded
3461 it into Debian, where it currently
3462 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
3463 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
3465 <p
>I guess you are wondering why on earth such tool would be useful
3466 for the common folks, ie those not running a large government
3467 surveillance system? Well, I plan to put it in a computer on my bike
3468 and in my car, tracking the cars nearby and allowing me to be notified
3469 when number plates on my watch list are discovered. Another use case
3470 was suggested by a friend of mine, who wanted to set it up at his home
3471 to open the car port automatically when it discovered the plate on his
3472 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
3473 capable of placing his license plate number of a piece of cardboard to
3474 open his car port, men replied that it was always unlocked anyway. I
3475 guess for such use case it make sense. I am sure there are other use
3476 cases too, for those with imagination and a vision.
</p
>
3478 <p
>If you want to build your own version of the Debian package, check
3479 out the upstream git source and symlink ./distros/debian to ./debian/
3480 before running
"debuild
" to build the source. Or wait a bit until the
3481 package show up in unstable.
</p
>
3486 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
3487 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
3488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
3489 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
3490 <description><p
>Around three years ago, I created
3491 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
3492 system
</a
> to get a more practical solution in Debian for handing
3493 hardware related packages. A GUI system in the isenkram package will
3494 present a pop-up dialog when some hardware dongle supported by
3495 relevant packages in Debian is inserted into the machine. The same
3496 lookup mechanism to detect packages is available as command line
3497 tools in the isenkram-cli package. In addition to mapping hardware,
3498 it will also map kernel firmware files to packages and make it easy to
3499 install needed firmware packages automatically. The key for this
3500 system to work is a good way to map hardware to packages, in other
3501 words, allow packages to announce what hardware they will work
3504 <p
>I started by providing data files in the isenkram source, and
3505 adding code to download the latest version of these data files at run
3506 time, to ensure every user had the most up to date mapping available.
3507 I also added support for storing the mapping in the Packages file in
3508 the apt repositories, but did not push this approach because while I
3509 was trying to figure out how to best store hardware/package mappings,
3510 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
3511 appstream system
</a
> was announced. I got in touch and suggested to
3512 add the hardware mapping into that data set to be able to use
3513 appstream as a data source, and this was accepted at least for the
3514 Debian version of appstream.
</p
>
3516 <p
>A few days ago using appstream in Debian for this became possible,
3517 and today I uploaded a new version
0.20 of isenkram adding support for
3518 appstream as a data source for mapping hardware to packages. The only
3519 package so far using appstream to announce its hardware support is my
3520 pymissile package. I got help from Matthias Klumpp with figuring out
3521 how do add the required
3522 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
3523 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
3524 this content:
</p
>
3526 <blockquote
><pre
>
3527 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3528 &lt;component
&gt;
3529 &lt;id
&gt;pymissile
&lt;/id
&gt;
3530 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
3531 &lt;name
&gt;pymissile
&lt;/name
&gt;
3532 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
3533 &lt;description
&gt;
3535 Pymissile provides a curses interface to control an original
3536 Marks and Spencer / Striker USB Missile Launcher, as well as a
3537 motion control script to allow a webcamera to control the
3540 &lt;/description
&gt;
3541 &lt;provides
&gt;
3542 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
3543 &lt;/provides
&gt;
3544 &lt;/component
&gt;
3545 </pre
></blockquote
>
3547 <p
>The key for isenkram is the component/provides/modalias value,
3548 which is a glob style match rule for hardware specific strings
3549 (modalias strings) provided by the Linux kernel. In this case, it
3550 will map to all USB devices with vendor code
1130 and product code
3553 <p
>Note, it is important that the license of all the metadata files
3554 are compatible to have permissions to aggregate them into archive wide
3555 appstream files. Matthias suggested to use MIT or BSD licenses for
3556 these files. A challenge is figuring out a good id for the data, as
3557 it is supposed to be globally unique and shared across distributions
3558 (in other words, best to coordinate with upstream what to use). But
3559 it can be changed later or, so we went with the package name as
3560 upstream for this project is dormant.
</p
>
3562 <p
>To get the metadata file installed in the correct location for the
3563 mirror update scripts to pick it up and include its content the
3564 appstream data source, the file must be installed in the binary
3565 package under /usr/share/appdata/. I did this by adding the following
3566 line to debian/pymissile.install:
</p
>
3568 <blockquote
><pre
>
3569 debian/pymissile.metainfo.xml usr/share/appdata
3570 </pre
></blockquote
>
3572 <p
>With that in place, the command line tool isenkram-lookup will list
3573 all packages useful on the current computer automatically, and the GUI
3574 pop-up handler will propose to install the package not already
3575 installed if a hardware dongle is inserted into the machine in
3578 <p
>Details of the modalias field in appstream is available from the
3579 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
3581 <p
>To locate the modalias values of all hardware present in a machine,
3582 try running this command on the command line:
</p
>
3584 <blockquote
><pre
>
3585 cat $(find /sys/devices/|grep modalias)
3586 </pre
></blockquote
>
3588 <p
>To learn more about the isenkram system, please check out
3589 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3590 blog posts tagged isenkram
</a
>.
</p
>
3595 <title>The GNU General Public License is not magic pixie dust
</title>
3596 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
3597 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
3598 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
3599 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
3600 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
3601 GPL is not magic pixie dust
</a
>" explain the importance of making sure
3602 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
3603 I quote the blog post from Paul in full here with his permission:
<p
>
3607 <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
>
3610 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
3612 The first step is to choose a
3613 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
3616 The next step is, when someone fails to follow that copyleft license,
3617 <b
>it must be enforced
</b
><br/
>
3619 and its a simple fact of our modern society that such type of
3622 is incredibly expensive to do and incredibly difficult to do.
3625 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
3626 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
3627 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
3628 0x57</a
></small
></p
>
3630 <p
>As the Debian Website
3631 <a href=
"https://bugs.debian.org/
794116">used
</a
>
3632 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
3633 imply, public domain and permissively licensed software can lead to
3634 the production of more proprietary software as people discover useful
3635 software, extend it and or incorporate it into their hardware or
3636 software products. Copyleft licenses such as the GNU GPL were created
3637 to close off this avenue to the production of proprietary software but
3638 such licenses are not enough. With the ongoing adoption of Free
3639 Software by individuals and groups, inevitably the community
's
3640 expectations of license compliance are violated, usually out of
3641 ignorance of the way Free Software works, but not always. As Karen
3642 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
3643 Freedom
">FaiF
</a
>
3644 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
3645 copyleft is nothing if no-one is willing and able to stand up in court
3646 to protect it. The reality of today
's world is that legal
3647 representation is expensive, difficult and time consuming. With
3648 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
3649 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
3650 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
3651 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
3652 of the Linux project, Debian and other groups against GPL violations.
3653 In March the SFC supported a
3654 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
3655 by Christoph Hellwig
</a
> against VMware for refusing to
3656 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
3657 with the GPL
</a
> in relation to their use of parts of the Linux
3658 kernel. Since then two of their sponsors pulled corporate funding and
3660 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
3661 or cancelled their talks
</a
>. As a result they have decided to rely
3662 less on corporate funding and more on the broad community of
3663 individuals who support Free Software and copyleft. So the SFC has
3664 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
3665 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
3666 a community of folks who stand up for copyleft and the GPL by
3667 supporting their work on promoting and supporting copyleft and Free
3670 <p
>If you support Free Software,
3671 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
3672 what the SFC do, agree with their
3673 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
3674 principles
</a
>, are happy about their
3675 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
3676 work on a project that is an SFC
3677 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
3678 just want to stand up for copyleft, please join
3679 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
3680 Allan Webber
</a
>,
3681 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
3683 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
3684 Bacon
</a
>, myself and
3685 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
3687 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
3688 next week your donation will be
3689 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
3690 by an anonymous donor. Please also consider asking your employer to
3691 match your donation or become a sponsor of SFC. Don
't forget to
3692 spread the word about your support for SFC via email, your blog and or
3693 social media accounts.
</p
>
3697 <p
>I agree with Paul on this topic and just signed up as a Supporter
3698 of Software Freedom Conservancy myself. Perhaps you should be a
3699 supporter too?
</p
>
3704 <title>PGP key transition statement for key EE4E02F9
</title>
3705 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
3706 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
3707 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
3708 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
3709 set it up properly. I wanted to generate it offline and have it
3710 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
3711 smart card
</a
> for daily use, and learning how to do it and finding
3712 time to sit down with an offline machine almost took forever. But
3713 finally I
've been able to complete the process, and have now moved
3714 from my old GPG key to a new GPG key. See
3715 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
3716 full transition statement, signed with both my old and new key
</a
> for
3717 the details. This is my new key:
</p
>
3720 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
3721 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
3722 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
3723 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
3724 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
3725 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
3726 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
3729 <p
>The key can be downloaded from the OpenPGP key servers, signed by
3730 my old key.
</p
>
3732 <p
>If you signed my old key
3733 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
3734 I
'd very much appreciate a signature on my new key, details and
3735 instructions in the transition statement. I m happy to reciprocate if
3736 you have a similarly signed transition statement to present.
</p
>
3741 <title>The life and death of a laptop battery
</title>
3742 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
3743 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
3744 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
3745 <description><p
>When I get a new laptop, the battery life time at the start is OK.
3746 But this do not last. The last few laptops gave me a feeling that
3747 within a year, the life time is just a fraction of what it used to be,
3748 and it slowly become painful to use the laptop without power connected
3749 all the time. Because of this, when I got a new Thinkpad X230 laptop
3750 about two years ago, I decided to monitor its battery state to have
3751 more hard facts when the battery started to fail.
</p
>
3753 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
3755 <p
>First I tried to find a sensible Debian package to record the
3756 battery status, assuming that this must be a problem already handled
3757 by someone else. I found
3758 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
3759 which collects statistics from the battery, but it was completely
3760 broken. I sent a few suggestions to the maintainer, but decided to
3761 write my own collector as a shell script while I waited for feedback
3763 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
3764 blog post about the battery development on a MacBook Air
</a
> I also
3766 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
3767 available in Debian.
</p
>
3769 <p
>I started my collector
2013-
07-
15, and it has been collecting
3770 battery stats ever since. Now my
3771 /var/log/hjemmenett-battery-status.log file contain around
115,
000
3772 measurements, from the time the battery was working great until now,
3773 when it is unable to charge above
7% of original capacity. My
3774 collector shell script is quite simple and look like this:
</p
>
3779 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
3781 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
3782 logfile=/var/log/hjemmenett-battery-status.log
3784 files=
"manufacturer model_name technology serial_number \
3785 energy_full energy_full_design energy_now cycle_count status
"
3787 if [ ! -e
"$logfile
" ] ; then
3789 printf
"timestamp,
"
3791 printf
"%s,
" $f
3794 )
> "$logfile
"
3798 # Print complete message in one echo call, to avoid race condition
3799 # when several log processes run in parallel.
3800 msg=$(printf
"%s,
" $(date +%s); \
3801 for f in $files; do \
3802 printf
"%s,
" $(cat $f); \
3804 echo
"$msg
"
3807 cd /sys/class/power_supply
3810 (cd $bat
&& log_battery
>> "$logfile
")
3814 <p
>The script is called when the power management system detect a
3815 change in the power status (power plug in or out), and when going into
3816 and out of hibernation and suspend. In addition, it collect a value
3817 every
10 minutes. This make it possible for me know when the battery
3818 is discharging, charging and how the maximum charge change over time.
3819 The code for the Debian package
3820 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
3821 available on github
</a
>.
</p
>
3823 <p
>The collected log file look like this:
</p
>
3826 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
3827 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
3829 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3830 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
3833 <p
>I wrote a small script to create a graph of the charge development
3834 over time. This graph depicted above show the slow death of my laptop
3837 <p
>But why is this happening? Why are my laptop batteries always
3838 dying in a year or two, while the batteries of space probes and
3839 satellites keep working year after year. If we are to believe
3840 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
3841 University
</a
>, the cause is me charging the battery whenever I have a
3842 chance, and the fix is to not charge the Lithium-ion batteries to
100%
3843 all the time, but to stay below
90% of full charge most of the time.
3844 I
've been told that the Tesla electric cars
3845 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
3846 the charge of their batteries to
80%
</a
>, with the option to charge to
3847 100% when preparing for a longer trip (not that I would want a car
3848 like Tesla where rights to privacy is abandoned, but that is another
3849 story), which I guess is the option we should have for laptops on
3850 Linux too.
</p
>
3852 <p
>Is there a good and generic way with Linux to tell the battery to
3853 stop charging at
80%, unless requested to charge to
100% once in
3854 preparation for a longer trip? I found
3855 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
3856 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
3857 80%
</a
>, but could not get it to work (kernel module refused to
3860 <p
>I wonder why the battery capacity was reported to be more than
100%
3861 at the start. I also wonder why the
"full capacity
" increases some
3862 times, and if it is possible to repeat the process to get the battery
3863 back to design capacity. And I wonder if the discharge and charge
3864 speed change over time, or if this stay the same. I did not yet try
3865 to write a tool to calculate the derivative values of the battery
3866 level, but suspect some interesting insights might be learned from
3869 <p
>Update
2015-
09-
24: I got a tip to install the packages
3870 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
3871 packages instead of the tp-smapi-dkms package I had tried to use
3872 initially, and use
'tlp setcharge
40 80' to change when charging start
3873 and stop. I
've done so now, but expect my existing battery is toast
3874 and need to be replaced. The proposal is unfortunately Thinkpad
3880 <title>New laptop - some more clues and ideas based on feedback
</title>
3881 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
3882 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
3883 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
3884 <description><p
>Several people contacted me after my previous blog post about my
3885 need for a new laptop, and provided very useful feedback. I wish to
3886 thank every one of these. Several pointed me to the possibility of
3887 fixing my X230, and I am already in the process of getting Lenovo to
3888 do so thanks to the on site, next day support contract covering the
3889 machine. But the battery is almost useless (I expect to replace it
3890 with a non-official battery) and I do not expect the machine to live
3891 for many more years, so it is time to plan its replacement. If I did
3892 not have a support contract, it was suggested to find replacement parts
3893 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
3894 might present a language barrier as I do not understand French.
</p
>
3896 <p
>One tip I got was to use the
3897 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
3898 compare laptop models. It seem to have more models available than
3899 prisjakt.no. Another tip I got from someone I know have similar
3900 keyboard preferences was that the HP EliteBook
840 keyboard is not
3901 very good, and this matches my experience with earlier EliteBook
3902 keyboards I tested. Because of this, I will not consider it any further.
3904 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
3905 newest Thinkpad X model. The keyboard reintroduces mouse buttons
3906 (which is missing from the X240), and is working fairly well with
3907 Debian Sid/Unstable according to
3908 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
3909 got on the keyboard quality are not consistent. Some say the keyboard
3910 is good, others say it is ok, while others say it is not very good.
3911 Those with experience from X41 and and X60 agree that the X250
3912 keyboard is not as good as those trusty old laptops, and suggest I
3913 keep and fix my X230 instead of upgrading, or get a used X230 to
3914 replace it. I
'm also told that the X250 lack leds for caps lock, disk
3915 activity and battery status, which is very convenient on my X230. I
'm
3916 also told that the CPU fan is running very often, making it a bit
3917 noisy. In any case, the X250 do not work out of the box with Debian
3918 Stable/Jessie, one of my requirements.
</p
>
3920 <p
>I have also gotten a few vendor proposals, one was
3921 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
3922 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
3923 The latter look very attractive to me.
</p
>
3925 <p
>Again, thank you all for the very useful feedback. It help a lot
3926 as I keep looking for a replacement.
</p
>
3928 <p
>Update
2015-
07-
06: I was recommended to check out the
3929 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
3931 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
3932 thinkpad X models
</a
>, and provide one year warranty.
</p
>
3937 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
3938 <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>
3939 <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>
3940 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
3941 <description><p
>My primary work horse laptop is failing, and will need a
3942 replacement soon. The left
5 cm of the screen on my Thinkpad X230
3943 started flickering yesterday, and I suspect the cause is a broken
3944 cable, as changing the angle of the screen some times get rid of the
3945 flickering.
</p
>
3947 <p
>My requirements have not really changed since I bought it, and is
3949 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
3950 described them in
2013</a
>. The last time I bought a laptop, I had
3952 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
3953 where I could select at least a few of the requirements (mouse pin,
3954 wifi, weight) and go through the rest manually. Three button mouse
3955 and a good keyboard is not available as an option, and all the three
3956 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
3957 G2) lack three mouse buttons). It is also unclear to me how good the
3958 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
3959 the keyboard, even if the quality and robustness in the X series have
3960 deteriorated since X41.
</p
>
3962 <p
>I wonder how I can find a sensible laptop when none of the options
3963 seem sensible to me? Are there better services around to search the
3964 set of available laptops for features? Please send me an email if you
3965 have suggestions.
</p
>
3967 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
3968 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
3969 of endorsed hardware
</a
>, which is useful background information.
</p
>
3974 <title>How to stay with sysvinit in Debian Jessie
</title>
3975 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
3976 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
3977 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
3978 <description><p
>By now, it is well known that Debian Jessie will not be using
3979 sysvinit as its boot system by default. But how can one keep using
3980 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
3982 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
3983 Schubert
</a
> and
3984 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
3987 <p
>If you already are using Wheezy and want to upgrade to Jessie and
3988 keep sysvinit as your boot system, create a file
3989 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
3990 you upgrade:
</p
>
3992 <p
><blockquote
><pre
>
3993 Package: systemd-sysv
3994 Pin: release o=Debian
3996 </pre
></blockquote
><p
>
3998 <p
>This file content will tell apt and aptitude to not consider
3999 installing systemd-sysv as part of any installation and upgrade
4000 solution when resolving dependencies, and thus tell it to avoid
4001 systemd as a default boot system. The end result should be that the
4002 upgraded system keep using sysvinit.
</p
>
4004 <p
>If you are installing Jessie for the first time, there is no way to
4005 get sysvinit installed by default (debootstrap used by
4006 debian-installer have no option for this), but one can tell the
4007 installer to switch to sysvinit before the first boot. Either by
4008 using a kernel argument to the installer, or by adding a line to the
4009 preseed file used. First, the kernel command line argument:
4011 <p
><blockquote
><pre
>
4012 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
4013 </pre
></blockquote
><p
>
4015 <p
>Next, the line to use in a preseed file:
</p
>
4017 <p
><blockquote
><pre
>
4018 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
4019 </pre
></blockquote
><p
>
4021 <p
>One can of course also do this after the first boot by installing
4022 the sysvinit-core package.
</p
>
4024 <p
>I recommend only using sysvinit if you really need it, as the
4025 sysvinit boot sequence in Debian have several hardware specific bugs
4026 on Linux caused by the fact that it is unpredictable when hardware
4027 devices show up during boot. But on the other hand, the new default
4028 boot system still have a few rough edges I hope will be fixed before
4029 Jessie is released.
</p
>
4031 <p
>Update
2014-
11-
26: Inspired by
4032 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
4033 blog post by Torsten Glaser
</a
>, added --purge to the preseed
4039 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
4040 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
4041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
4042 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
4043 <description><p
>The right to communicate with your friends and family in private,
4044 without anyone snooping, is a right every citicen have in a liberal
4045 democracy. But this right is under serious attack these days.
</p
>
4047 <p
>A while back it occurred to me that one way to make the dragnet
4048 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
4049 the whisleblower Snowden) more expensive for Internet email,
4050 is to deliver all email using SMTP via Tor. Such SMTP option would be
4051 a nice addition to the FreedomBox project if we could send email
4052 between FreedomBox machines without leaking metadata about the emails
4053 to the people peeking on the wire. I
4054 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
4055 this on the FreedomBox project mailing list in October
</a
> and got a
4056 lot of useful feedback and suggestions. It also became obvious to me
4057 that this was not a novel idea, as the same idea was tested and
4058 documented by Johannes Berg as early as
2006, and both
4059 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
4060 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
4061 propose a similar method / protocol to pass emails between users.
</p
>
4063 <p
>To implement such system one need to set up a Tor hidden service
4064 providing the SMTP protocol on port
25, and use email addresses
4065 looking like username@hidden-service-name.onion. With such addresses
4066 the connections to port
25 on hidden-service-name.onion using Tor will
4067 go to the correct SMTP server. To do this, one need to configure the
4068 Tor daemon to provide the hidden service and the mail server to accept
4069 emails for this .onion domain. To learn more about Exim configuration
4070 in Debian and test the design provided by Johannes Berg in his FAQ, I
4071 set out yesterday to create a Debian package for making it trivial to
4072 set up such SMTP over Tor service based on Debian. Getting it to work
4073 were fairly easy, and
4074 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
4075 source code for the Debian package
</a
> is available from github. I
4076 plan to move it into Debian if further testing prove this to be a
4077 useful approach.
</p
>
4079 <p
>If you want to test this, set up a blank Debian machine without any
4080 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
4081 get rid of exim4). Install tor, clone the git repository mentioned
4082 above, build the deb and install it on the machine. Next, run
4083 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
4084 the instructions to get the service up and running. Restart tor and
4085 exim when it is done, and test mail delivery using swaks like
4088 <p
><blockquote
><pre
>
4089 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
4090 --to fbx@dutlqrrmjhtfa3vp.onion
4091 </pre
></blockquote
></p
>
4093 <p
>This will test the SMTP delivery using tor. Replace the email
4094 address with your own address to test your server. :)
</p
>
4096 <p
>The setup procedure is still to complex, and I hope it can be made
4097 easier and more automatic. Especially the tor setup need more work.
4098 Also, the package include a tor-smtp tool written in C, but its task
4099 should probably be rewritten in some script language to make the deb
4100 architecture independent. It would probably also make the code easier
4101 to review. The tor-smtp tool currently need to listen on a socket for
4102 exim to talk to it and is started using xinetd. It would be better if
4103 no daemon and no socket is needed. I suspect it is possible to get
4104 exim to run a command line tool for delivery instead of talking to a
4105 socket, and hope to figure out how in a future version of this
4108 <p
>Until I wipe my test machine, I can be reached using the
4109 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
4110 SMTorP. :)
</p
>
4115 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
4116 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
4117 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
4118 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
4119 <description><p
>If you ever had to moderate a mailman list, like the ones on
4120 alioth.debian.org, you know the web interface is fairly slow to
4121 operate. First you visit one web page, enter the moderation password
4122 and get a new page shown with a list of all the messages to moderate
4123 and various options for each email address. This take a while for
4124 every list you moderate, and you need to do it regularly to do a good
4125 job as a list moderator. But there is a quick alternative,
4126 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
4127 listadmin program
</a
>. It allow you to check lists for new messages
4128 to moderate in a fraction of a second. Here is a test run on two
4129 lists I recently took over:
</p
>
4131 <p
><blockquote
><pre
>
4132 % time listadmin xiph
4133 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
4134 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
4140 </pre
></blockquote
></p
>
4142 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
4143 there are no message in the moderation queue. Every morning I
4144 currently moderate
68 mailman lists, and it normally take around two
4145 minutes. When I took over the two pkg-xiph lists above a few days
4146 ago, there were
400 emails waiting in the moderator queue. It took me
4147 less than
15 minutes to process them all using the listadmin
4150 <p
>If you install
4151 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
4152 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
4153 with content like this, the moderation task is a breeze:
</p
>
4155 <p
><blockquote
><pre
>
4156 username username@example.org
4159 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
4162 adminurl https://{domain}/mailman/admindb/{list}
4163 mailman-list@lists.example.com
4166 other-list@otherserver.example.org
4167 </pre
></blockquote
></p
>
4169 <p
>There are other options to set as well. Check the manual page to
4170 learn the details.
</p
>
4172 <p
>If you are forced to moderate lists on a mailman installation where
4173 the SSL certificate is self signed or not properly signed by a
4174 generally accepted signing authority, you can set a environment
4175 variable when calling listadmin to disable SSL verification:
</p
>
4177 <p
><blockquote
><pre
>
4178 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
4179 </pre
></blockquote
></p
>
4181 <p
>If you want to moderate a subset of the lists you take care of, you
4182 can provide an argument to the listadmin script like I do in the
4183 initial screen dump (the xiph argument). Using an argument, only
4184 lists matching the argument string will be processed. This make it
4185 quick to accept messages if you notice the moderation request in your
4188 <p
>Without the listadmin program, I would never be the moderator of
68
4189 mailing lists, as I simply do not have time to spend on that if the
4190 process was any slower. The listadmin program have saved me hours of
4191 time I could spend elsewhere over the years. It truly is nice free
4194 <p
>As usual, if you use Bitcoin and want to show your support of my
4195 activities, please send Bitcoin donations to my address
4196 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4198 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
4199 configuration example. Also, I
've been told that the
4200 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
4206 <title>Debian Jessie, PXE and automatic firmware installation
</title>
4207 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
4208 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
4209 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
4210 <description><p
>When PXE installing laptops with Debian, I often run into the
4211 problem that the WiFi card require some firmware to work properly.
4212 And it has been a pain to fix this using preseeding in Debian.
4213 Normally something more is needed. But thanks to
4214 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
4215 package
</a
> and its recent tasksel extension, it has now become easy
4216 to do this using simple preseeding.
</p
>
4218 <p
>The isenkram-cli package provide tasksel tasks which will install
4219 firmware for the hardware found in the machine (actually, requested by
4220 the kernel modules for the hardware). (It can also install user space
4221 programs supporting the hardware detected, but that is not the focus
4222 of this story.)
</p
>
4224 <p
>To get this working in the default installation, two preeseding
4225 values are needed. First, the isenkram-cli package must be installed
4226 into the target chroot (aka the hard drive) before tasksel is executed
4227 in the pkgsel step of the debian-installer system. This is done by
4228 preseeding the base-installer/includes debconf value to include the
4229 isenkram-cli package. The package name is next passed to debootstrap
4230 for installation. With the isenkram-cli package in place, tasksel
4231 will automatically use the isenkram tasks to detect hardware specific
4232 packages for the machine being installed and install them, because
4233 isenkram-cli contain tasksel tasks.
</p
>
4235 <p
>Second, one need to enable the non-free APT repository, because
4236 most firmware unfortunately is non-free. This is done by preseeding
4237 the apt-mirror-setup step. This is unfortunate, but for a lot of
4238 hardware it is the only option in Debian.
</p
>
4240 <p
>The end result is two lines needed in your preseeding file to get
4241 firmware installed automatically by the installer:
</p
>
4243 <p
><blockquote
><pre
>
4244 base-installer base-installer/includes string isenkram-cli
4245 apt-mirror-setup apt-setup/non-free boolean true
4246 </pre
></blockquote
></p
>
4248 <p
>The current version of isenkram-cli in testing/jessie will install
4249 both firmware and user space packages when using this method. It also
4250 do not work well, so use version
0.15 or later. Installing both
4251 firmware and user space packages might give you a bit more than you
4252 want, so I decided to split the tasksel task in two, one for firmware
4253 and one for user space programs. The firmware task is enabled by
4254 default, while the one for user space programs is not. This split is
4255 implemented in the package currently in unstable.
</p
>
4257 <p
>If you decide to give this a go, please let me know (via email) how
4258 this recipe work for you. :)
</p
>
4260 <p
>So, I bet you are wondering, how can this work. First and
4261 foremost, it work because tasksel is modular, and driven by whatever
4262 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
4263 isenkram-cli package place two files for tasksel to find. First there
4264 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
4266 <p
><blockquote
><pre
>
4267 Task: isenkram-packages
4269 Description: Hardware specific packages (autodetected by isenkram)
4270 Based on the detected hardware various hardware specific packages are
4272 Test-new-install: show show
4274 Packages: for-current-hardware
4276 Task: isenkram-firmware
4278 Description: Hardware specific firmware packages (autodetected by isenkram)
4279 Based on the detected hardware various hardware specific firmware
4280 packages are proposed.
4281 Test-new-install: mark show
4283 Packages: for-current-hardware-firmware
4284 </pre
></blockquote
></p
>
4286 <p
>The key parts are Test-new-install which indicate how the task
4287 should be handled and the Packages line referencing to a script in
4288 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
4289 list of packages to install. The for-current-hardware-firmware script
4290 look like this to list relevant firmware for the machine:
4292 <p
><blockquote
><pre
>
4295 PATH=/usr/sbin:$PATH
4297 isenkram-autoinstall-firmware -l
4298 </pre
></blockquote
></p
>
4300 <p
>With those two pieces in place, the firmware is installed by
4301 tasksel during the normal d-i run. :)
</p
>
4303 <p
>If you want to test what tasksel will install when isenkram-cli is
4304 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
4305 --new-install
</tt
> to get the list of packages that tasksel would
4308 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
4309 pilots in testing this feature, as isenkram is used there now to
4310 install firmware, replacing the earlier scripts.
</p
>
4315 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
4316 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
4317 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
4318 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
4319 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
4320 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
4321 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
4322 on a screen normally showing the bread types and prizes:
</p
>
4324 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
4326 <p
>If it had booted as it was supposed to, I would never had known
4327 about this hidden Linux installation. It is interesting what
4328 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
4333 <title>New lsdvd release version
0.17 is ready
</title>
4334 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
4335 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
4336 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
4337 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
4338 got a new set of developers a few weeks ago, after the original
4339 developer decided to step down and pass the project to fresh blood.
4340 This project is now maintained by Petter Reinholdtsen and Steve
4343 <p
>I just wrapped up
4344 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
4345 new lsdvd release
</a
>, available in git or from
4346 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
4347 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
4352 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
4353 <li
>Check for garbage in the program chains, which indicate that a track is
4354 non-existant, to work around additional copy protection
</li
>
4355 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
4356 <li
>Fix pallete display of first entry
</li
>
4357 <li
>Fix include orders
</li
>
4358 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
4359 <li
>Fix the chapter count
</li
>
4360 <li
>Make sure the array size and the array limit used when initialising
4361 the palette size is the same.
</li
>
4362 <li
>Fix array printing.
</li
>
4363 <li
>Correct subsecond calculations.
</li
>
4364 <li
>Add sector information to the output format.
</li
>
4365 <li
>Clean up code to be closer to ANSI C and compile without warnings
4366 with more GCC compiler warnings.
</li
>
4370 <p
>This change bring together patches for lsdvd in use in various
4371 Linux and Unix distributions, as well as patches submitted to the
4372 project the last nine years. Please check it out. :)
</p
>
4377 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
4378 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
4379 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
4380 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
4381 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4382 project
</a
> provide a Linux solution for schools, including a
4383 powerful desktop with education software, a central server providing
4384 web pages, user database, user home directories, central login and PXE
4385 boot of both clients without disk and the installation to install Debian
4386 Edu on machines with disk (and a few other services perhaps to small
4387 to mention here). We in the Debian Edu team are currently working on
4388 the Jessie based version, trying to get everything in shape before the
4389 freeze, to avoid having to maintain our own package repository in the
4391 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
4392 status
</a
> can be seen on the Debian wiki, and there is still heaps of
4393 work left. Some fatal problems block testing, breaking the installer,
4394 but it is possible to work around these to get anyway. Here is a
4395 recipe on how to get the installation limping along.
</p
>
4397 <p
>First, download the test ISO via
4398 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
4399 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
4401 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
4402 The ISO build was broken on Tuesday, so we do not get a new ISO every
4403 12 hours or so, but thankfully the ISO we already got we are able to
4404 install with some tweaking.
</p
>
4406 <p
>When you get to the Debian Edu profile question, go to tty2
4407 (use Alt-Ctrl-F2), run
</p
>
4409 <p
><blockquote
><pre
>
4410 nano /usr/bin/edu-eatmydata-install
4411 </pre
></blockquote
></p
>
4413 <p
>and add
'exit
0' as the second line, disabling the eatmydata
4414 optimization. Return to the installation, select the profile you want
4415 and continue. Without this change, exim4-config will fail to install
4416 due to a known bug in eatmydata.
</p
>
4418 <p
>When you get the grub question at the end, answer /dev/sda (or if
4419 this do not work, figure out what your correct value would be. All my
4420 test machines need /dev/sda, so I have no advice if it do not fit
4421 your need.
</p
>
4423 <p
>If you installed a profile including a graphical desktop, log in as
4424 root after the initial boot from hard drive, and install the
4425 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
4426 or mate. If you want several desktop options, install more than one
4427 metapackage. Once this is done, reboot and you should have a working
4428 graphical login screen. This workaround should no longer be needed
4429 once the education-tasks package version
1.801 enter testing in two
4432 <p
>I believe the ISO build will start working on two days when the new
4433 tasksel package enter testing and Steve McIntyre get a chance to
4434 update the debian-cd git repository. The eatmydata, grub and desktop
4435 issues are already fixed in unstable and testing, and should show up
4436 on the ISO as soon as the ISO build start working again. Well the
4437 eatmydata optimization is really just disabled. The proper fix
4438 require an upload by the eatmydata maintainer applying the patch
4439 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
4440 The rest have proper fixes in unstable.
</p
>
4442 <p
>I hope this get you going with the installation testing, as we are
4443 quickly running out of time trying to get our Jessie based
4444 installation ready before the distribution freeze in a month.
</p
>
4449 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
4450 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
4451 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
4452 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
4453 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
4454 to handle my fairly large DVD collection. It is a nice command line
4455 tool to get details about a DVD, like title, tracks, track length,
4456 etc, in XML, Perl or human readable format. But lsdvd have not seen
4457 any new development since
2006 and had a few irritating bugs affecting
4458 its use with some DVDs. Upstream seemed to be dead, and in January I
4459 sent a small probe asking for a version control repository for the
4460 project, without any reply. But I use it regularly and would like to
4461 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
4462 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
4463 the project admin, and after getting a reply from him explaining that
4464 he was no longer interested in the project, I asked if I could take
4465 over. And yesterday, I became project admin.
</p
>
4467 <p
>I
've been in touch with a Gentoo developer and the Debian
4468 maintainer interested in joining forces to maintain the upstream
4469 project, and I hope we can get a new release out fairly quickly,
4470 collecting the patches spread around on the internet into on place.
4471 I
've added the relevant Debian patches to the freshly created git
4472 repository, and expect the Gentoo patches to make it too. If you got
4473 a DVD collection and care about command line tools, check out
4474 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
4475 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
4476 list
</a
>. :)
</p
>
4481 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
4482 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
4483 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
4484 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
4485 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
4486 a lot quicker. When we install more than
2000 packages in
4487 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
4488 tasksel in the installer, unpacking the binary packages take forever.
4489 A part of the slow I/O issue was discussed in
4490 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
4491 much file system sync-ing done by dpkg, which is the package
4492 responsible for unpacking the binary packages. Other parts (like code
4493 executed by postinst scripts) might also sync to disk during
4494 installation. All this sync-ing to disk do not really make sense to
4495 me. If the machine crash half-way through, I start over, I do not try
4496 to salvage the half installed system. So the failure sync-ing is
4497 supposed to protect against, hardware or system crash, is not really
4498 relevant while the installer is running.
</p
>
4500 <p
>A few days ago, I thought of a way to get rid of all the file
4501 system sync()-ing in a fairly non-intrusive way, without the need to
4502 change the code in several packages. The idea is not new, but I have
4503 not heard anyone propose the approach using dpkg-divert before. It
4504 depend on the small and clever package
4505 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
4506 uses LD_PRELOAD to replace the system functions for syncing data to
4507 disk with functions doing nothing, thus allowing programs to live
4508 dangerous while speeding up disk I/O significantly. Instead of
4509 modifying the implementation of dpkg, apt and tasksel (which are the
4510 packages responsible for selecting, fetching and installing packages),
4511 it occurred to me that we could just divert the programs away, replace
4512 them with a simple shell wrapper calling
4513 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
4514 Two days ago I decided to test the idea, and wrapped up a simple
4515 implementation for the Debian Edu udeb.
</p
>
4517 <p
>The effect was stunning. In my first test it reduced the running
4518 time of the pkgsel step (installing tasks) from
64 to less than
44
4519 minutes (
20 minutes shaved off the installation) on an old Dell
4520 Latitude D505 machine. I am not quite sure what the optimised time
4521 would have been, as I messed up the testing a bit, causing the debconf
4522 priority to get low enough for two questions to pop up during
4523 installation. As soon as I saw the questions I moved the installation
4524 along, but do not know how long the question were holding up the
4525 installation. I did some more measurements using Debian Edu Jessie,
4526 and got these results. The time measured is the time stamp in
4527 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
4528 "pkgsel: finishing up
" lines, if you want to do the same measurement
4529 yourself. In Debian Edu, the tasksel dialog do not show up, and the
4530 timing thus do not depend on how quickly the user handle the tasksel
4533 <p
><table
>
4536 <th
>Machine/setup
</th
>
4537 <th
>Original tasksel
</th
>
4538 <th
>Optimised tasksel
</th
>
4539 <th
>Reduction
</th
>
4543 <td
>Latitude D505 Main+LTSP LXDE
</td
>
4544 <td
>64 min (
07:
46-
08:
50)
</td
>
4545 <td
><44 min (
11:
27-
12:
11)
</td
>
4546 <td
>>20 min
18%
</td
>
4550 <td
>Latitude D505 Roaming LXDE
</td
>
4551 <td
>57 min (
08:
48-
09:
45)
</td
>
4552 <td
>34 min (
07:
43-
08:
17)
</td
>
4553 <td
>23 min
40%
</td
>
4557 <td
>Latitude D505 Minimal
</td
>
4558 <td
>22 min (
10:
37-
10:
59)
</td
>
4559 <td
>11 min (
11:
16-
11:
27)
</td
>
4560 <td
>11 min
50%
</td
>
4564 <td
>Thinkpad X200 Minimal
</td
>
4565 <td
>6 min (
08:
19-
08:
25)
</td
>
4566 <td
>4 min (
08:
04-
08:
08)
</td
>
4567 <td
>2 min
33%
</td
>
4571 <td
>Thinkpad X200 Roaming KDE
</td
>
4572 <td
>19 min (
09:
21-
09:
40)
</td
>
4573 <td
>15 min (
10:
25-
10:
40)
</td
>
4574 <td
>4 min
21%
</td
>
4577 </table
></p
>
4579 <p
>The test is done using a netinst ISO on a USB stick, so some of the
4580 time is spent downloading packages. The connection to the Internet
4581 was
100Mbit/s during testing, so downloading should not be a
4582 significant factor in the measurement. Download typically took a few
4583 seconds to a few minutes, depending on the amount of packages being
4584 installed.
</p
>
4586 <p
>The speedup is implemented by using two hooks in
4587 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
4588 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
4589 finish-install.d hook to remove the divert at the end of the
4590 installation. I picked the pre-pkgsel.d hook instead of the
4591 post-base-installer.d hook because I test using an ISO without the
4592 eatmydata package included, and the post-base-installer.d hook in
4593 Debian Edu can only operate on packages included in the ISO. The
4594 negative effect of this is that I am unable to activate this
4595 optimization for the kernel installation step in d-i. If the code is
4596 moved to the post-base-installer.d hook, the speedup would be larger
4597 for the entire installation.
</p
>
4599 <p
>I
've implemented this in the
4600 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
4601 git repository, and plan to provide the optimization as part of the
4602 Debian Edu installation. If you want to test this yourself, you can
4603 create two files in the installer (or in an udeb). One shell script
4604 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
4606 <p
><blockquote
><pre
>
4609 . /usr/share/debconf/confmodule
4611 logger -t my-pkgsel
"info: $*
"
4614 logger -t my-pkgsel
"error: $*
"
4616 override_install() {
4617 apt-install eatmydata || true
4618 if [ -x /target/usr/bin/eatmydata ] ; then
4619 for bin in dpkg apt-get aptitude tasksel ; do
4621 # Test that the file exist and have not been diverted already.
4622 if [ -f /target$file ] ; then
4623 info
"diverting $file using eatmydata
"
4624 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
4625 > /target$file.edu
4626 chmod
755 /target$file.edu
4627 in-target dpkg-divert --package debian-edu-config \
4628 --rename --quiet --add $file
4629 ln -sf ./$bin.edu /target$file
4631 error
"unable to divert $file, as it is missing.
"
4635 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
4640 </pre
></blockquote
></p
>
4642 <p
>To clean up, another shell script should go into
4643 /usr/lib/finish-install.d/ with code like this:
4645 <p
><blockquote
><pre
>
4647 . /usr/share/debconf/confmodule
4649 logger -t my-finish-install
"error: $@
"
4651 remove_install_override() {
4652 for bin in dpkg apt-get aptitude tasksel ; do
4654 if [ -x /target$file.edu ] ; then
4656 in-target dpkg-divert --package debian-edu-config \
4657 --rename --quiet --remove $file
4660 error
"Missing divert for $file.
"
4663 sync # Flush file buffers before continuing
4666 remove_install_override
4667 </pre
></blockquote
></p
>
4669 <p
>In Debian Edu, I placed both code fragments in a separate script
4670 edu-eatmydata-install and call it from the pre-pkgsel.d and
4671 finish-install.d scripts.
</p
>
4673 <p
>By now you might ask if this change should get into the normal
4674 Debian installer too? I suspect it should, but am not sure the
4675 current debian-installer coordinators find it useful enough. It also
4676 depend on the side effects of the change. I
'm not aware of any, but I
4677 guess we will see if the change is safe after some more testing.
4678 Perhaps there is some package in Debian depending on sync() and
4679 fsync() having effect? Perhaps it should go into its own udeb, to
4680 allow those of us wanting to enable it to do so without affecting
4683 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
4684 will break installation of all programs using gnutls because of
4685 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
4686 eatmydata package in Debian will solve it.
</p
>
4688 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
4689 the optimization work again. And I have discovered that the
4690 dpkg-divert trick is not really needed and implemented a slightly
4691 simpler approach as part of the debian-edu-install package. See
4692 tools/edu-eatmydata-install in the source package.
</p
>
4694 <p
>Update
2014-
11-
11: Unfortunately, a new
4695 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
4696 triggering on i386 made it into testing, and broke this installation
4697 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
4698 request
768893</a
> is accepted, it should be working again.
</p
>
4703 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
4704 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
4705 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
4706 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
4707 <description><p
>Yesterday, I had the pleasure of attending a talk with the
4708 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
4709 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
4710 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
4711 learn that there is a large set of publicly available key servers to
4712 use when looking for peoples public key. So far I have used
4713 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
4714 were misbehaving, but those days are ended. The servers I have used
4715 up until yesterday have been slow and some times unavailable. I hope
4716 those problems are gone now.
</p
>
4718 <p
>Behind the round robin DNS entry of the
4719 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
4720 there is a pool of more than
100 keyservers which are checked every
4721 day to ensure they are well connected and up to date. It must be
4722 better than what I have used so far. :)
</p
>
4724 <p
>Yesterdays speaker told me that the service is the default
4725 keyserver provided by the default configuration in GnuPG, but this do
4726 not seem to be used in Debian. Perhaps it should?
</p
>
4728 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
4731 <p
><blockquote
><pre
>
4732 keyserver pool.sks-keyservers.net
4733 </pre
></blockquote
></p
>
4735 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
4736 entries in DNS. Just for fun, I did just that at work, so now every
4737 user of GnuPG at the University of Oslo should find a OpenGPG
4738 keyserver automatically should their need it:
</p
>
4740 <p
><blockquote
><pre
>
4741 % host -t srv _pgpkey-http._tcp.uio.no
4742 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
4744 </pre
></blockquote
></p
>
4746 <p
>Now if only
4747 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
4748 HKP lookup protocol
</a
> supported finding signature paths, I would be
4749 very happy. It can look up a given key or search for a user ID, but I
4750 normally do not want that, but to find a trust path from my key to
4751 another key. Given a user ID or key ID, I would like to find (and
4752 download) the keys representing a signature path from my key to the
4753 key in question, to be able to get a trust path between the two keys.
4754 This is as far as I can tell not possible today. Perhaps something
4755 for a future version of the protocol?
</p
>
4760 <title>From English wiki to translated PDF and epub via Docbook
</title>
4761 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
4762 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
4763 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
4764 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
4765 project
</a
> provide an instruction manual for teachers, system
4766 administrators and other users that contain useful tips for setting up
4767 and maintaining a Debian Edu installation. This text is about how the
4768 text processing of this manual is handled in the project.
</p
>
4770 <p
>One goal of the project is to provide information in the native
4771 language of its users, and for this we need to handle translations.
4772 But we also want to make sure each language contain the same
4773 information, so for this we need a good way to keep the translations
4774 in sync. And we want it to be easy for our users to improve the
4775 documentation, avoiding the need to learn special formats or tools to
4776 contribute, and the obvious way to do this is to make it possible to
4777 edit the documentation using a web browser. We also want it to be
4778 easy for translators to keep the translation up to date, and give them
4779 help in figuring out what need to be translated. Here is the list of
4780 tools and the process we have found trying to reach all these
4783 <p
>We maintain the authoritative source of our manual in the
4784 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
4785 wiki
</a
>, as several wiki pages written in English. It consist of one
4786 front page with references to the different chapters, several pages
4787 for each chapter, and finally one
"collection page
" gluing all the
4788 chapters together into one large web page (aka
4789 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
4790 AllInOne page
</a
>). The AllInOne page is the one used for further
4791 processing and translations. Thanks to the fact that the
4792 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
4793 wiki.debian.org support exporting pages in
4794 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
4795 the list of pages to export using the raw version of the AllInOne
4796 page, loop over each of them to generate a Docbook XML version of the
4797 manual. This process also download images and transform image
4798 references to use the locally downloaded images. The generated
4799 Docbook XML files are slightly broken, so some post-processing is done
4800 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
4801 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
4802 a handfull of images. The XML file can now be used to generate PDF, HTML
4803 and epub versions of the English manual. This is the basic step of
4804 our process, making PDF (using dblatex), HTML (using xsltproc) and
4805 epub (using dbtoepub) version from Docbook XML, and the resulting files
4806 are placed in the debian-edu-doc-en binary package.
</p
>
4808 <p
>But English documentation is not enough for us. We want translated
4809 documentation too, and we want to make it easy for translators to
4810 track the English original. For this we use the
4811 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
4812 which allow us to transform the English Docbook XML file into a
4813 translation file (a .pot file), usable with the normal gettext based
4814 translation tools used by those translating free software. The pot
4815 file is used to create and maintain translation files (several .po
4816 files), which the translations update with the native language
4817 translations of all titles, paragraphs and blocks of text in the
4818 original. The next step is combining the original English Docbook XML
4819 and the translation file (say debian-edu-wheezy-manual.nb.po), to
4820 create a translated Docbook XML file (in this case
4821 debian-edu-wheezy-manual.nb.xml). This translated (or partly
4822 translated, if the translation is not complete) Docbook XML file can
4823 then be used like the original to create a PDF, HTML and epub version
4824 of the documentation.
</p
>
4826 <p
>The translators use different tools to edit the .po files. We
4828 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
4829 while some use emacs and vi, others can use web based editors like
4830 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
4831 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
4832 is where the .po file end up, in our git repository. Updated
4833 translations can either be committed directly to git, or submitted as
4834 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
4835 against the debian-edu-doc package
</a
>.
</p
>
4837 <p
>One challenge is images, which both might need to be translated (if
4838 they show translated user applications), and are needed in different
4839 formats when creating PDF and HTML versions (epub is a HTML version in
4840 this regard). For this we transform the original PNG images to the
4841 needed density and format during build, and have a way to provide
4842 translated images by storing translated versions in
4843 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
4844 package maintainers know more.
</p
>
4846 <p
>If you wonder what the result look like, we provide
4847 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
4848 of the documentation packages on the web
</a
>. See for example the
4849 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
4850 PDF version
</a
> or the
4851 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
4852 HTML version
</a
>. We do not yet build the epub version by default,
4853 but perhaps it will be done in the future.
</p
>
4855 <p
>To learn more, check out
4856 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
4857 debian-edu-doc package
</a
>,
4858 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
4859 manual on the wiki
</a
> and
4860 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
4861 translation instructions
</a
> in the manual.
</p
>
4866 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
4867 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
4868 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
4869 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
4870 <description><p
>It would be nice if it was easier in Debian to get all the hardware
4871 related packages relevant for the computer installed automatically.
4872 So I implemented one, using
4873 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
4874 package
</a
>. To use it, install the tasksel and isenkram packages and
4875 run tasksel as user root. You should be presented with a new option,
4876 "Hardware specific packages (autodetected by isenkram)
". When you
4877 select it, tasksel will install the packages isenkram claim is fit for
4878 the current hardware, hot pluggable or not.
<p
>
4880 <p
>The implementation is in two files, one is the tasksel menu entry
4881 description, and the other is the script used to extract the list of
4882 packages to install. The first part is in
4883 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
4886 <p
><blockquote
><pre
>
4889 Description: Hardware specific packages (autodetected by isenkram)
4890 Based on the detected hardware various hardware specific packages are
4892 Test-new-install: mark show
4894 Packages: for-current-hardware
4895 </pre
></blockquote
></p
>
4897 <p
>The second part is in
4898 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
4901 <p
><blockquote
><pre
>
4906 isenkram-autoinstall-firmware -l
4908 </pre
></blockquote
></p
>
4910 <p
>All in all, a very short and simple implementation making it
4911 trivial to install the hardware dependent package we all may want to
4912 have installed on our machines. I
've not been able to find a way to
4913 get tasksel to tell you exactly which packages it plan to install
4914 before doing the installation. So if you are curious or careful,
4915 check the output from the isenkram-* command line tools first.
</p
>
4917 <p
>The information about which packages are handling which hardware is
4918 fetched either from the isenkram package itself in
4919 /usr/share/isenkram/, from git.debian.org or from the APT package
4920 database (using the Modaliases header). The APT package database
4921 parsing have caused a nasty resource leak in the isenkram daemon (bugs
4922 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
4923 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
4924 the python-apt code (bug
4925 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
4926 workaround I was able to get rid of the file descriptor leak and
4927 reduce the memory leak from ~
30 MiB per hardware detection down to
4928 around
2 MiB per hardware detection. It should make the desktop
4929 daemon a lot more useful. The fix is in version
0.7 uploaded to
4930 unstable today.
</p
>
4932 <p
>I believe the current way of mapping hardware to packages in
4933 Isenkram is is a good draft, but in the future I expect isenkram to
4934 use the AppStream data source for this. A proposal for getting proper
4935 AppStream support into Debian is floating around as
4936 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
4937 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
4938 project
</a
> will take place this summer to improve the situation. I
4939 look forward to seeing the result, and welcome patches for isenkram to
4940 start using the information when it is ready.
</p
>
4942 <p
>If you want your package to map to some specific hardware, either
4943 add a
"Xb-Modaliases
" header to your control file like I did in
4944 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
4945 package
</a
> or submit a bug report with the details to the isenkram
4947 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
4948 blog posts tagged isenkram
</a
> for details on the notation. I expect
4949 the information will be migrated to AppStream eventually, but for the
4950 moment I got no better place to store it.
</p
>
4955 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
4956 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
4957 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
4958 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
4959 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4960 project
</a
> is working on providing the software and hardware to make
4961 it easy for non-technical people to host their data and communication
4962 at home, and being able to communicate with their friends and family
4963 encrypted and away from prying eyes. It is still going strong, and
4964 today a major mile stone was reached.
</p
>
4966 <p
>Today, the last of the packages currently used by the project to
4967 created the system images were accepted into Debian Unstable. It was
4968 the freedombox-setup package, which is used to configure the images
4969 during build and on the first boot. Now all one need to get going is
4970 the build code from the freedom-maker git repository and packages from
4971 Debian. And once the freedombox-setup package enter testing, we can
4972 build everything directly from Debian. :)
</p
>
4974 <p
>Some key packages used by Freedombox are
4975 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
4976 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
4977 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
4978 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
4979 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
4980 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
4981 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
4982 are plans to integrate more packages into the setup. User
4983 documentation is maintained on the Debian wiki. Please
4984 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
4985 the manual
</a
> and help us improve it.
</p
>
4987 <p
>To test for yourself and create boot images with the FreedomBox
4988 setup, run this on a Debian machine using a user with sudo rights to
4989 become root:
</p
>
4991 <p
><pre
>
4992 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4993 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4995 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4997 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4998 </pre
></p
>
5000 <p
>Root access is needed to run debootstrap and mount loopback
5001 devices. See the README in the freedom-maker git repo for more
5002 details on the build. If you do not want all three images, trim the
5003 make line. Note that the virtualbox-image target is not really
5004 virtualbox specific. It create a x86 image usable in kvm, qemu,
5005 vmware and any other x86 virtual machine environment. You might need
5006 the version of vmdebootstrap in Jessie to get the build working, as it
5007 include fixes for a race condition with kpartx.
</p
>
5009 <p
>If you instead want to install using a Debian CD and the preseed
5010 method, boot a Debian Wheezy ISO and use this boot argument to load
5011 the preseed values:
</p
>
5013 <p
><pre
>
5014 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
5015 </pre
></p
>
5017 <p
>I have not tested it myself the last few weeks, so I do not know if
5018 it still work.
</p
>
5020 <p
>If you wonder how to help, one task you could look at is using
5021 systemd as the boot system. It will become the default for Linux in
5022 Jessie, so we need to make sure it is usable on the Freedombox. I did
5023 a simple test a few weeks ago, and noticed dnsmasq failed to start
5024 during boot when using systemd. I suspect there are other problems
5025 too. :) To detect problems, there is a test suite included, which can
5026 be run from the plinth web interface.
</p
>
5028 <p
>Give it a go and let us know how it goes on the mailing list, and help
5029 us get the new release published. :) Please join us on
5030 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
5031 irc.debian.org)
</a
> and
5032 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5033 mailing list
</a
> if you want to help make this vision come true.
</p
>
5038 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
5039 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
5040 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
5041 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
5042 <description><p
>For a while now, I have been looking for a sensible offsite backup
5043 solution for use at home. My requirements are simple, it must be
5044 cheap and locally encrypted (in other words, I keep the encryption
5045 keys, the storage provider do not have access to my private files).
5046 One idea me and my friends had many years ago, before the cloud
5047 storage providers showed up, was to use Google mail as storage,
5048 writing a Linux block device storing blocks as emails in the mail
5049 service provided by Google, and thus get heaps of free space. On top
5050 of this one can add encryption, RAID and volume management to have
5051 lots of (fairly slow, I admit that) cheap and encrypted storage. But
5052 I never found time to implement such system. But the last few weeks I
5053 have looked at a system called
5054 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
5055 mounted network backed file system with the features I need.
</p
>
5057 <p
>S3QL is a fuse file system with a local cache and cloud storage,
5058 handling several different storage providers, any with Amazon S3,
5059 Google Drive or OpenStack API. There are heaps of such storage
5060 providers. S3QL can also use a local directory as storage, which
5061 combined with sshfs allow for file storage on any ssh server. S3QL
5062 include support for encryption, compression, de-duplication, snapshots
5063 and immutable file systems, allowing me to mount the remote storage as
5064 a local mount point, look at and use the files as if they were local,
5065 while the content is stored in the cloud as well. This allow me to
5066 have a backup that should survive fire. The file system can not be
5067 shared between several machines at the same time, as only one can
5068 mount it at the time, but any machine with the encryption key and
5069 access to the storage service can mount it if it is unmounted.
</p
>
5071 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
5072 package is included already. So to get started, run
<tt
>apt-get
5073 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
5074 Greenqloud, after reading their nice recipe on
5075 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
5076 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
5077 in Iceland more than those in USA when it come to keeping my personal
5078 data safe and private, and thus would rather spend money on a company
5079 in Iceland. Another nice recipe is available from the article
5080 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
5081 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
5082 Admin magazine. When the provider is picked, figure out how to get
5083 the API key needed to connect to the storage API. With Greencloud,
5084 the key did not show up until I had added payment details to my
5087 <p
>Armed with the API access details, it is time to create the file
5088 system. First, create a new bucket in the cloud. This bucket is the
5089 file system storage area. I picked a bucket name reflecting the
5090 machine that was going to store data there, but any name will do.
5091 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
5092 the API login and password, and a locally created password. Store it
5093 all in ~root/.s3ql/authinfo2 like this:
5095 <p
><blockquote
><pre
>
5097 storage-url: s3c://s.greenqloud.com:
443/bucket-name
5098 backend-login: API-login
5099 backend-password: API-password
5100 fs-passphrase: local-password
5101 </pre
></blockquote
></p
>
5103 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
5104 but any sensible way to create a fairly random password should do it.
5105 Armed with these details, it is now time to run mkfs, entering the API
5106 details and password to create it:
</p
>
5108 <p
><blockquote
><pre
>
5109 # mkdir -m
700 /var/lib/s3ql-cache
5110 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5111 --ssl s3c://s.greenqloud.com:
443/bucket-name
5112 Enter backend login:
5113 Enter backend password:
5114 Before using S3QL, make sure to read the user
's guide, especially
5115 the
'Important Rules to Avoid Loosing Data
' section.
5116 Enter encryption password:
5117 Confirm encryption password:
5118 Generating random encryption key...
5119 Creating metadata tables...
5129 Compressing and uploading metadata...
5130 Wrote
0.00 MB of compressed metadata.
5131 #
</pre
></blockquote
></p
>
5133 <p
>The next step is mounting the file system to make the storage available.
5135 <p
><blockquote
><pre
>
5136 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5137 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
5138 Using
4 upload threads.
5139 Downloading and decompressing metadata...
5149 Mounting filesystem...
5151 Filesystem Size Used Avail Use% Mounted on
5152 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
5154 </pre
></blockquote
></p
>
5156 <p
>The file system is now ready for use. I use rsync to store my
5157 backups in it, and as the metadata used by rsync is downloaded at
5158 mount time, no network traffic (and storage cost) is triggered by
5159 running rsync. To unmount, one should not use the normal umount
5160 command, as this will not flush the cache to the cloud storage, but
5161 instead running the umount.s3ql command like this:
5163 <p
><blockquote
><pre
>
5166 </pre
></blockquote
></p
>
5168 <p
>There is a fsck command available to check the file system and
5169 correct any problems detected. This can be used if the local server
5170 crashes while the file system is mounted, to reset the
"already
5171 mounted
" flag. This is what it look like when processing a working
5172 file system:
</p
>
5174 <p
><blockquote
><pre
>
5175 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
5176 Using cached metadata.
5177 File system seems clean, checking anyway.
5178 Checking DB integrity...
5179 Creating temporary extra indices...
5180 Checking lost+found...
5181 Checking cached objects...
5182 Checking names (refcounts)...
5183 Checking contents (names)...
5184 Checking contents (inodes)...
5185 Checking contents (parent inodes)...
5186 Checking objects (reference counts)...
5187 Checking objects (backend)...
5188 ..processed
5000 objects so far..
5189 ..processed
10000 objects so far..
5190 ..processed
15000 objects so far..
5191 Checking objects (sizes)...
5192 Checking blocks (referenced objects)...
5193 Checking blocks (refcounts)...
5194 Checking inode-block mapping (blocks)...
5195 Checking inode-block mapping (inodes)...
5196 Checking inodes (refcounts)...
5197 Checking inodes (sizes)...
5198 Checking extended attributes (names)...
5199 Checking extended attributes (inodes)...
5200 Checking symlinks (inodes)...
5201 Checking directory reachability...
5202 Checking unix conventions...
5203 Checking referential integrity...
5204 Dropping temporary indices...
5205 Backing up old metadata...
5215 Compressing and uploading metadata...
5216 Wrote
0.89 MB of compressed metadata.
5218 </pre
></blockquote
></p
>
5220 <p
>Thanks to the cache, working on files that fit in the cache is very
5221 quick, about the same speed as local file access. Uploading large
5222 amount of data is to me limited by the bandwidth out of and into my
5223 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
5224 which is very close to my upload speed, and downloading the same
5225 Debian installation ISO gave me
610 kiB/s, close to my download speed.
5226 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
5227 network, not the file system code. I do not know what a good cache
5228 size would be, but suspect that the cache should e larger than your
5229 working set.
</p
>
5231 <p
>I mentioned that only one machine can mount the file system at the
5232 time. If another machine try, it is told that the file system is
5235 <p
><blockquote
><pre
>
5236 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
5237 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
5238 Using
8 upload threads.
5239 Backend reports that fs is still mounted elsewhere, aborting.
5241 </pre
></blockquote
></p
>
5243 <p
>The file content is uploaded when the cache is full, while the
5244 metadata is uploaded once every
24 hour by default. To ensure the
5245 file system content is flushed to the cloud, one can either umount the
5246 file system, or ask S3QL to flush the cache and metadata using
5249 <p
><blockquote
><pre
>
5250 # s3qlctrl upload-meta /s3ql
5251 # s3qlctrl flushcache /s3ql
5253 </pre
></blockquote
></p
>
5255 <p
>If you are curious about how much space your data uses in the
5256 cloud, and how much compression and deduplication cut down on the
5257 storage usage, you can use s3qlstat on the mounted file system to get
5260 <p
><blockquote
><pre
>
5262 Directory entries:
9141
5265 Total data size:
22049.38 MB
5266 After de-duplication:
21955.46 MB (
99.57% of total)
5267 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
5268 Database size:
2.39 MB (uncompressed)
5269 (some values do not take into account not-yet-uploaded dirty blocks in cache)
5271 </pre
></blockquote
></p
>
5273 <p
>I mentioned earlier that there are several possible suppliers of
5274 storage. I did not try to locate them all, but am aware of at least
5275 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
5276 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
5277 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
5278 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
5279 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
5280 accept payment in Bitcoin. Pick one that suit your need. Some of
5281 them provide several GiB of free storage, but the prize models are
5282 quite different and you will have to figure out what suits you
5285 <p
>While researching this blog post, I had a look at research papers
5286 and posters discussing the S3QL file system. There are several, which
5287 told me that the file system is getting a critical check by the
5288 science community and increased my confidence in using it. One nice
5290 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
5291 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
5292 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
5293 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
5294 and Pamela Smith. Please have a look.
</p
>
5296 <p
>Given my problems with different file systems earlier, I decided to
5297 check out the mounted S3QL file system to see if it would be usable as
5298 a home directory (in other word, that it provided POSIX semantics when
5299 it come to locking and umask handling etc). Running
5300 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
5301 test code to check file system semantics
</a
>, I was happy to discover that
5302 no error was found. So the file system can be used for home
5303 directories, if one chooses to do so.
</p
>
5305 <p
>If you do not want a locally file system, and want something that
5306 work without the Linux fuse file system, I would like to mention the
5307 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
5308 provide locally encrypted backup using a command line client. It have
5309 a nicer access control system, where one can split out read and write
5310 access, allowing some systems to write to the backup and others to
5311 only read from it.
</p
>
5313 <p
>As usual, if you use Bitcoin and want to show your support of my
5314 activities, please send Bitcoin donations to my address
5315 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5320 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
5321 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
5322 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
5323 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
5324 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
5325 project
</a
> is working on providing the software and hardware for
5326 making it easy for non-technical people to host their data and
5327 communication at home, and being able to communicate with their
5328 friends and family encrypted and away from prying eyes. It has been
5329 going on for a while, and is slowly progressing towards a new test
5330 release (
0.2).
</p
>
5332 <p
>And what day could be better than the Pi day to announce that the
5333 new version will provide
"hard drive
" / SD card / USB stick images for
5334 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
5335 system), and can also be installed using a Debian installer preseed
5336 file. The Debian based Freedombox is now based on Debian Jessie,
5337 where most of the needed packages used are already present. Only one,
5338 the freedombox-setup package, is missing. To try to build your own
5339 boot image to test the current status, fetch the freedom-maker scripts
5341 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
5342 with a user with sudo access to become root:
5345 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5347 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5348 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5350 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5353 <p
>Root access is needed to run debootstrap and mount loopback
5354 devices. See the README for more details on the build. If you do not
5355 want all three images, trim the make line. But note that thanks to
<a
5356 href=
"https://bugs.debian.org/
741407">a race condition in
5357 vmdebootstrap
</a
>, the build might fail without the patch to the
5358 kpartx call.
</p
>
5360 <p
>If you instead want to install using a Debian CD and the preseed
5361 method, boot a Debian Wheezy ISO and use this boot argument to load
5362 the preseed values:
</p
>
5365 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
5368 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
5369 recently introduced bug in apt in Jessie
</a
>, the installer will
5370 currently hang while setting up APT sources. Killing the
5371 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
5372 installation will get the installation going. This affect all
5373 installations in Jessie, and I expect it will be fixed soon.
</p
>
5375 <p
>Give it a go and let us know how it goes on the mailing list, and help
5376 us get the new release published. :) Please join us on
5377 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
5378 irc.debian.org)
</a
> and
5379 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
5380 mailing list
</a
> if you want to help make this vision come true.
</p
>
5385 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
5386 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
5387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
5388 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
5389 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
5390 innetgr tools, because I needed them in
5391 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
5392 ng-utils, and it has served me well. I placed the project under the
5393 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
5394 repository. But many years ago, the CVS repository was dropped (lost,
5395 not migrated to new hardware, not sure), and the project have lacked a
5396 proper home since then.
</p
>
5398 <p
>Last summer, I had a look at the package and made a new release
5399 fixing a irritating crash bug, but was unable to store the changes in
5400 a proper source control system. I applied for a project on
5401 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
5402 to follow up on it. Until today. :)
</p
>
5404 <p
>After many hours of cleaning and migration, the ng-utils project
5405 now have a new home, and a git repository with the highlight of the
5406 history of the project. I published all release tarballs and imported
5407 them into the git repository. As the project is really stable and not
5408 expected to gain new features any time soon, I decided to make a new
5409 release and call it
1.0. Visit the new project home on
5410 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
5411 if you want to check it out. The new version is also uploaded into
5412 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
5417 <title>Testing sysvinit from experimental in Debian Hurd
</title>
5418 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
5419 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
5420 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
5421 <description><p
>A few days ago I decided to try to help the Hurd people to get
5422 their changes into sysvinit, to allow them to use the normal sysvinit
5423 boot system instead of their old one. This follow up on the
5424 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
5425 Google Summer of Code work
</a
> done last summer by Justus Winter to
5426 get Debian on Hurd working more like Debian on Linux. To get started,
5427 I downloaded a prebuilt hard disk image from
5428 <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
>,
5429 and started it using virt-manager.
</p
>
5431 <p
>The first think I had to do after logging in (root without any
5432 password) was to get the network operational. I followed
5433 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
5434 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
5435 commands as root to get the machine to accept a IP address from the
5436 kvm internal DHCP server:
</p
>
5438 <p
><blockquote
><pre
>
5439 settrans -fgap /dev/netdde /hurd/netdde
5440 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
5441 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
5443 </pre
></blockquote
></p
>
5445 <p
>After this, the machine had internet connectivity, and I could
5446 upgrade it and install the sysvinit packages from experimental and
5447 enable it as the default boot system in Hurd.
</p
>
5449 <p
>But before I did that, I set a password on the root user, as ssh is
5450 running on the machine it for ssh login to work a password need to be
5451 set. Also, note that a bug somewhere in openssh on Hurd block
5452 compression from working. Remember to turn that off on the client
5455 <p
>Run these commands as root to upgrade and test the new sysvinit
5458 <p
><blockquote
><pre
>
5459 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
5460 deb http://http.debian.net/debian/ experimental main
5463 apt-get dist-upgrade
5464 apt-get install -t experimental initscripts sysv-rc sysvinit \
5465 sysvinit-core sysvinit-utils
5466 update-alternatives --config runsystem
5467 </pre
></blockquote
></p
>
5469 <p
>To reboot after switching boot system, you have to use
5470 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
5471 yet a sysvinit process able to receive the signals from the normal
5472 'reboot
' command. After switching to sysvinit as the boot system,
5473 upgrading every package and rebooting, the network come up with DHCP
5474 after boot as it should, and the settrans/pkill hack mentioned at the
5475 start is no longer needed. But for some strange reason, there are no
5476 longer any login prompt in the virtual console, so I logged in using
5479 <p
>Note that there are some race conditions in Hurd making the boot
5480 fail some times. No idea what the cause is, but hope the Hurd porters
5481 figure it out. At least Justus said on IRC (#debian-hurd on
5482 irc.debian.org) that they are aware of the problem. A way to reduce
5483 the impact is to upgrade to the Hurd packages built by Justus by
5484 adding this repository to the machine:
</p
>
5486 <p
><blockquote
><pre
>
5487 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
5488 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
5490 </pre
></blockquote
></p
>
5492 <p
>At the moment the prebuilt virtual machine get some packages from
5493 http://ftp.debian-ports.org/debian, because some of the packages in
5494 unstable do not yet include the required patches that are lingering in
5495 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
5497 <p
><blockquote
><pre
>
5498 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
5499 i emacs - GNU Emacs editor (metapackage)
5500 i gdb - GNU Debugger
5501 i hurd-recommended - Miscellaneous translators
5502 i isc-dhcp-client - ISC DHCP client
5503 i isc-dhcp-common - common files used by all the isc-dhcp* packages
5504 i libc-bin - Embedded GNU C Library: Binaries
5505 i libc-dev-bin - Embedded GNU C Library: Development binaries
5506 i libc0.3 - Embedded GNU C Library: Shared libraries
5507 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
5508 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
5509 i multiarch-support - Transitional package to ensure multiarch compatibilit
5510 i A x11-common - X Window System (X.Org) infrastructure
5511 i xorg - X.Org X Window System
5512 i A xserver-xorg - X.Org X server
5513 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
5515 </pre
></blockquote
></p
>
5517 <p
>All in all, testing hurd has been an interesting experience. :)
5518 X.org did not work out of the box and I never took the time to follow
5519 the porters instructions to fix it. This time I was interested in the
5520 command line stuff.
<p
>
5525 <title>New chrpath release
0.16</title>
5526 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
5527 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
5528 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
5529 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
5530 find problems in C, C++ and Java code using static source code
5531 analysis. It can detect a lot of different problems, and is very
5532 useful to find memory and locking bugs in the error handling part of
5533 the source. The company behind it provide
5534 <a href=
"https://scan.coverity.com/
">check of free software projects as
5535 a community service
</a
>, and many hundred free software projects are
5536 already checked. A few days ago I decided to have a closer look at
5537 the Coverity system, and discovered that the
5538 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
5539 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
5540 projects I am involved with was already registered. But these are
5541 fairly big, and I would also like to have a small and easy project to
5542 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
5543 checking of the chrpath project
</a
>. It was
5544 added to the checker and discovered seven potential defects. Six of
5545 these were real, mostly resource
"leak
" when the program detected an
5546 error. Nothing serious, as the resources would be released a fraction
5547 of a second later when the program exited because of the error, but it
5548 is nice to do it right in case the source of the program some time in
5549 the future end up in a library. Having fixed all defects and added
5550 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
5551 mailing list for the chrpath developers
</a
>, I decided it was time to
5552 publish a new release. These are the release notes:
</p
>
5554 <p
>New in
0.16 released
2014-
01-
14:
</p
>
5558 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
5559 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
5560 <li
>Mention new project mailing list in the documentation.
</li
>
5565 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5566 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
5567 project if something is wrong with the new release. The test suite
5568 did not discover any old errors, so if you find a new one, please also
5569 include a test suite check.
</p
>
5574 <title>New chrpath release
0.15</title>
5575 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
5576 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
5577 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
5578 <description><p
>After many years break from the package and a vain hope that
5579 development would be continued by someone else, I finally pulled my
5580 acts together this morning and wrapped up a new release of chrpath,
5581 the command line tool to modify the rpath and runpath of already
5582 compiled ELF programs. The update was triggered by the persistence of
5583 Isha Vishnoi at IBM, which needed a new config.guess file to get
5584 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
5585 is working on. I checked the
5586 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
5587 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
5588 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
5589 packages for interesting patches (failed to find the source from
5590 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
5591 These are the release notes:
</p
>
5593 <p
>New in
0.15 released
2013-
11-
24:
</p
>
5597 <li
>Updated config.sub and config.guess from the GNU project to work
5598 with newer architectures. Thanks to isha vishnoi for the heads
5601 <li
>Updated README with current URLs.
</li
>
5603 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
5604 Matthias Klose.
</li
>
5606 <li
>Added missing help for -k|--keepgoing option, using patch by
5607 Petr Machata found in Fedora.
</li
>
5609 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
5610 .dynamic is a NULL terminated string. Based on patch found in
5611 Fedora credited Axel Thimm and Christian Krause.
</li
>
5616 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
5617 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
5618 project if something is wrong with the new release. The test suite
5619 did not discover any old errors, so if you find a new one, please also
5620 include a testsuite check.
</p
>
5625 <title>Debian init.d boot script example for rsyslog
</title>
5626 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
5627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
5628 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
5629 <description><p
>If one of the points of switching to a new init system in Debian is
5630 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
5631 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
5632 init.d scripts at all. Here is an example init.d script, ie a rewrite
5633 of /etc/init.d/rsyslog:
</p
>
5635 <p
><pre
>
5636 #!/lib/init/init-d-script
5639 # Required-Start: $remote_fs $time
5640 # Required-Stop: umountnfs $time
5641 # X-Stop-After: sendsigs
5642 # Default-Start:
2 3 4 5
5643 # Default-Stop:
0 1 6
5644 # Short-Description: enhanced syslogd
5645 # Description: Rsyslog is an enhanced multi-threaded syslogd.
5646 # It is quite compatible to stock sysklogd and can be
5647 # used as a drop-in replacement.
5649 DESC=
"enhanced syslogd
"
5650 DAEMON=/usr/sbin/rsyslogd
5651 </pre
></p
>
5653 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
5654 script was
137 lines, and the above is just
15 lines, most of it meta
5655 info/comments.
</p
>
5657 <p
>How to do this, you ask? Well, one create a new script
5658 /lib/init/init-d-script looking something like this:
5660 <p
><pre
>
5663 # Define LSB log_* functions.
5664 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
5665 # and status_of_proc is working.
5666 . /lib/lsb/init-functions
5669 # Function that starts the daemon/service
5675 #
0 if daemon has been started
5676 #
1 if daemon was already running
5677 #
2 if daemon could not be started
5678 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
5680 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
5683 # Add code here, if necessary, that waits for the process to be ready
5684 # to handle requests from services started subsequently which depend
5685 # on this one. As a last resort, sleep for some time.
5689 # Function that stops the daemon/service
5694 #
0 if daemon has been stopped
5695 #
1 if daemon was already stopped
5696 #
2 if daemon could not be stopped
5697 # other if a failure occurred
5698 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
5699 RETVAL=
"$?
"
5700 [
"$RETVAL
" =
2 ]
&& return
2
5701 # Wait for children to finish too if this is a daemon that forks
5702 # and if the daemon is only ever run from this initscript.
5703 # If the above conditions are not satisfied then add some other code
5704 # that waits for the process to drop all resources that could be
5705 # needed by services started subsequently. A last resort is to
5706 # sleep for some time.
5707 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
5708 [
"$?
" =
2 ]
&& return
2
5709 # Many daemons don
't delete their pidfiles when they exit.
5711 return
"$RETVAL
"
5715 # Function that sends a SIGHUP to the daemon/service
5719 # If the daemon can reload its configuration without
5720 # restarting (for example, when it is sent a SIGHUP),
5721 # then implement that here.
5723 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
5728 scriptbasename=
"$(basename $
1)
"
5729 echo
"SN: $scriptbasename
"
5730 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
5731 script=
"$
1"
5738 NAME=$(basename $DAEMON)
5739 PIDFILE=/var/run/$NAME.pid
5741 # Exit if the package is not installed
5742 #[ -x
"$DAEMON
" ] || exit
0
5744 # Read configuration variable file if it is present
5745 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
5747 # Load the VERBOSE setting and other rcS variables
5750 case
"$
1" in
5752 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
5754 case
"$?
" in
5755 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5756 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5760 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
5762 case
"$?
" in
5763 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
5764 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
5768 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
5770 #reload|force-reload)
5772 # If do_reload() is not implemented then leave this commented out
5773 # and leave
'force-reload
' as an alias for
'restart
'.
5775 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
5779 restart|force-reload)
5781 # If the
"reload
" option is implemented then remove the
5782 #
'force-reload
' alias
5784 log_daemon_msg
"Restarting $DESC
" "$NAME
"
5786 case
"$?
" in
5789 case
"$?
" in
5791 1) log_end_msg
1 ;; # Old process is still running
5792 *) log_end_msg
1 ;; # Failed to start
5802 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
5808 </pre
></p
>
5810 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
5811 lot. I did not really polish the approach, so it might not always
5812 work out of the box, but you get the idea. I did not try very hard to
5813 optimize it nor make it more robust either.
</p
>
5815 <p
>A better argument for switching init system in Debian than reducing
5816 the size of init scripts (which is a good thing to do anyway), is to
5817 get boot system that is able to handle the kernel events sensibly and
5818 robustly, and do not depend on the boot to run sequentially. The boot
5819 and the kernel have not behaved sequentially in years.
</p
>
5824 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
5825 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
5826 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
5827 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
5828 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
5829 remote display access is the preferred solution with oVirt and RedHat
5830 Enterprise Virtualization, and I was sad to discover the other day
5831 that the browser plugin needed to use these systems seamlessly was
5832 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
5833 for a package
</a
> was from
2012-
04-
10 with no progress since
5834 2013-
04-
01, so I decided to wrap up a package based on the great work
5835 from Cajus Pollmeier and put it in a collab-maint maintained git
5836 repository to get a package I could use. I would very much like
5837 others to help me maintain the package (or just take over, I do not
5838 mind), but as no-one had volunteered so far, I just uploaded it to
5839 NEW. I hope it will be available in Debian in a few days.
</p
>
5841 <p
>The source is now available from
5842 <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
>
5847 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
5848 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
5849 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
5850 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
5851 <description><p
>The
5852 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
5853 program is a a very nice system to create virtual machine images. It
5854 create a image file, add a partition table, mount it and run
5855 debootstrap in the mounted directory to create a Debian system on a
5856 stick. Yesterday, I decided to try to teach it how to make images for
5857 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
5858 of a plan to simplify the build system for
5859 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
5860 project
</a
>. The FreedomBox project already uses vmdebootstrap for
5861 the virtualbox images, but its current build system made multistrap
5862 based system for Dreamplug images, and it is lacking support for
5863 Raspberry Pi.
</p
>
5865 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
5866 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
5867 code and adjusted it to be able to build armel images on my amd64
5868 Debian laptop. I ended up giving vmdebootstrap five new options,
5869 allowing me to replicate the image creation process I use to make
5870 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
5871 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
5872 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
5873 call debootstrap with --foreign and to copy the handler into the
5874 generated chroot before running the second stage. This allow
5875 vmdebootstrap to create armel images on an amd64 host. Next I added
5876 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
5877 fstype
</tt
> to teach it to create a separate /boot/ partition with the
5878 given file system type, allowing me to create an image with a vfat
5879 partition for the /boot/ stuff. I also added a
<tt
>--variant
5880 variant
</tt
> option to allow me to create smaller images without the
5881 Debian base system packages installed. Finally, I added an option
5882 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
5883 as a boot loader. It is not needed on the Raspberry Pi and probably
5884 most other non-x86 architectures. The changes were accepted by the
5885 upstream author of vmdebootstrap yesterday and today, and is now
5887 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
5888 upstream project page
</a
>.
</p
>
5890 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
5891 create a small script (the customize script) to add the non-free
5892 binary blob needed to boot the Raspberry Pi and the APT source
5895 <p
><pre
>
5897 set -e # Exit on first error
5898 rootdir=
"$
1"
5899 cd
"$rootdir
"
5900 cat
&lt;
&lt;EOF
> etc/apt/sources.list
5901 deb http://http.debian.net/debian/ jessie main contrib non-free
5903 # Install non-free binary blob needed to boot Raspberry Pi. This
5904 # install a kernel somewhere too.
5905 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
5906 -O $rootdir/usr/bin/rpi-update
5907 chmod a+x $rootdir/usr/bin/rpi-update
5908 mkdir -p $rootdir/lib/modules
5909 touch $rootdir/boot/start.elf
5910 chroot $rootdir rpi-update
5911 </pre
></p
>
5913 <p
>Next, fetch the latest vmdebootstrap script and call it like this
5914 to build the image:
</p
>
5917 sudo ./vmdebootstrap \
5920 --distribution jessie \
5921 --mirror http://http.debian.net/debian \
5930 --root-password raspberry \
5931 --hostname raspberrypi \
5932 --foreign /usr/bin/qemu-arm-static \
5933 --customize `pwd`/customize \
5935 --package git-core \
5936 --package binutils \
5937 --package ca-certificates \
5940 </pre
></p
>
5942 <p
>The list of packages being installed are the ones needed by
5943 rpi-update to make the image bootable on the Raspberry Pi, with the
5944 exception of netbase, which is needed by debootstrap to find
5945 /etc/hosts with the minbase variant. I really wish there was a way to
5946 set up an Raspberry Pi using only packages in the Debian archive, but
5947 that is not possible as far as I know, because it boots from the GPU
5948 using a non-free binary blob.
</p
>
5950 <p
>The build host need debootstrap, kpartx and qemu-user-static and
5951 probably a few others installed. I have not checked the complete
5952 build dependency list.
</p
>
5954 <p
>The resulting image will not use the hardware floating point unit
5955 on the Raspberry PI, because the armel architecture in Debian is not
5956 optimized for that use. So the images created will be a bit slower
5957 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
5962 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
5963 <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>
5964 <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>
5965 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
5966 <description><p
>The last few days I came across a few good causes that should get
5967 wider attention. I recommend signing and donating to each one of
5970 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
5971 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
5972 Women program which is a Google Summer of Code like initiative to get
5973 more women involved in free software. One debian sponsor has offered
5974 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
5975 earmarked
</a
> for this initiative. I donated a few minutes ago, and
5976 hope you will to. :)
</p
>
5978 <p
>And the Electronic Frontier Foundation just announced plans to
5979 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
5980 documentaries about the excessive spying
</a
> on every Internet user that
5981 take place these days, and their need to fund the work. I
've already
5982 donated. Are you next?
</p
>
5984 <p
>For my Norwegian audience, the organisation Studentenes og
5985 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
5986 statement under the heading
5987 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
5988 Access
</a
> for those of us asking for more focus on open access in the
5989 Norwegian government. So far
499 signatures. I hope you will sign it
5995 <title>Videos about the Freedombox project - for inspiration and learning
</title>
5996 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
5997 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
5998 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
5999 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
6000 project
</a
> have been going on for a while, and have presented the
6001 vision, ideas and solution several places. Here is a little
6002 collection of videos of talks and presentation of the project.
</p
>
6006 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
6007 2,
5 minute marketing film
</a
> (Youtube)
</li
>
6009 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
6010 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
6012 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
6013 Freedom in the Cloud - Software Freedom, Privacy and and Security for
6014 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
6015 (Youtube)
</li
>
6017 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
6018 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
6020 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
6021 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
6023 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
6024 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
6025 York City in
2012</a
> (Youtube)
</li
>
6027 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
6028 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
6029 (Youtube)
</li
>
6031 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
6032 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
6034 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
6035 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
6037 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
6038 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
6039 2013</a
> (Youtube)
</li
>
6043 <p
>A larger list is available from
6044 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
6045 Freedombox Wiki
</a
>.
</p
>
6047 <p
>On other news, I am happy to report that Freedombox based on Debian
6048 Jessie is coming along quite well, and soon both Owncloud and using
6049 Tor should be available for testers of the Freedombox solution. :) In
6050 a few weeks I hope everything needed to test it is included in Debian.
6051 The withsqlite package is already in Debian, and the plinth package is
6052 pending in NEW. The third and vital part of that puzzle is the
6053 metapackage/setup framework, which is still pending an upload. Join
6054 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
6055 (#freedombox on irc.debian.org)
</a
> and
6056 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6057 mailing list
</a
> if you want to help make this vision come true.
</p
>
6062 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
6063 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
6064 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
6065 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
6066 <description><p
>I was introduced to the
6067 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
6068 in
2010, when Eben Moglen presented his vision about serving the need
6069 of non-technical people to keep their personal information private and
6070 within the legal protection of their own homes. The idea is to give
6071 people back the power over their network and machines, and return
6072 Internet back to its intended peer-to-peer architecture. Instead of
6073 depending on a central service, the Freedombox will give everyone
6074 control over their own basic infrastructure.
</p
>
6076 <p
>I
've intended to join the effort since then, but other tasks have
6077 taken priority. But this summers nasty news about the misuse of trust
6078 and privilege exercised by the
"western
" intelligence gathering
6079 communities increased my eagerness to contribute to a point where I
6080 actually started working on the project a while back.
</p
>
6082 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
6083 Debian initiative
</a
> based on the vision from Eben Moglen, is to
6084 create a simple and cheap Debian based appliance that anyone can hook
6085 up in their home and get access to secure and private services and
6086 communication. The initial deployment platform have been the
6087 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
6088 which is a piece of hardware I do not own. So to be able to test what
6089 the current Freedombox setup look like, I had to come up with a way to install
6090 it on some hardware I do have access to. I have rewritten the
6091 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
6092 image build framework to use .deb packages instead of only copying
6093 setup into the boot images, and thanks to this rewrite I am able to
6094 set up any machine supported by Debian Wheezy as a Freedombox, using
6095 the previously mentioned deb (and a few support debs for packages
6096 missing in Debian).
</p
>
6098 <p
>The current Freedombox setup consist of a set of bootstrapping
6100 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
6101 and a administrative web interface
6102 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
6103 withsqlite), as well as a privacy enhancing proxy based on
6104 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
6105 (freedombox-privoxy). There is also a web/javascript based XMPP
6106 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
6107 trying (unsuccessfully so far) to talk to the XMPP server
6108 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
6109 web interface is pluggable, and the goal is to use it to enable OpenID
6110 services, mesh network connectivity, use of TOR, etc, etc. Not much of
6111 this is really working yet, see
6112 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
6113 project TODO
</a
> for links to GIT repositories. Most of the code is
6114 on github at the moment. The HTTP proxy is operational out of the
6115 box, and the admin web interface can be used to add/remove plinth
6116 users. I
've not been able to do anything else with it so far, but
6117 know there are several branches spread around github and other places
6118 with lots of half baked features.
</p
>
6120 <p
>Anyway, if you want to have a look at the current state, the
6121 following recipes should work to give you a test machine to poke
6124 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
6128 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
6129 <li
>Boot from it, either as CD or USB stick.
</li
>
6130 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
6131 to the Debian installer:
<p
>
6132 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
6134 <li
>Answer the few language/region/password questions and pick disk to
6135 install on.
</li
>
6137 <li
>When the installation is finished and the machine have rebooted a
6138 few times, your Freedombox is ready for testing.
</li
>
6142 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
6146 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
6147 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
6148 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
6150 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
6151 </pre
></li
>
6152 <li
><p
>Run this as root:
</p
>
6154 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
6157 apt-get install freedombox-setup
6158 /usr/lib/freedombox/setup
6159 </pre
></li
>
6160 <li
>Reboot into your freshly created Freedombox.
</li
>
6164 <p
>You can test it on other architectures too, but because the
6165 freedombox-privoxy package is binary, it will only work as intended on
6166 the architectures where I have had time to build the binary and put it
6167 in my APT repository. But do not let this stop you. It is only a
6168 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
6170 <p
>Note that by default Freedombox is a DHCP server on the
6171 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
6172 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
6173 disable
</tt
>" as root.
</p
>
6175 <p
>Please let me know if this works for you, or if you have any
6176 problems. We gather on the IRC channel
6177 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
6178 irc.debian.org and the
6179 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
6180 mailing list
</a
>.
</p
>
6182 <p
>Once you get your freedombox operational, you can visit
6183 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
6184 welcome screen (dead end - do not be surprised if you are unable to
6185 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
6186 to look at the rest of plinth. The default user is
'admin
' and the
6187 default password is
'secret
'.
</p
>
6192 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
6193 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
6194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
6195 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
6196 <description><p
>Earlier, I reported about
6197 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
6198 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
6199 told by IBM that the original disk should be thrown away. And as
6200 there no longer was a problem if I bricked the firmware, I decided
6201 today to try to install Intel firmware to replace the Lenovo firmware
6202 currently on the disk.
</p
>
6204 <p
>I searched the Intel site for firmware, and found
6205 <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
>
6206 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
6207 according to the site should contain the latest firmware for SSD
6208 disks. I inserted the broken disk in one of my spare laptops and
6209 booted the ISO from a USB stick. The disk was recognized, but the
6210 program claimed the newest firmware already were installed and refused
6211 to insert any Intel firmware. So no change, and the disk is still
6212 unable to handle write load. :( I guess the only way to get them
6213 working would be if Lenovo releases new firmware. No idea how likely
6214 that is. Anyway, just blogging about this test for completeness. I
6215 got a working Samsung disk, and see no point in spending more time on
6216 the broken disks.
</p
>
6221 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
6222 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
6223 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
6224 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
6225 <description><p
>Today I switched to
6226 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
6227 new laptop
</a
>. I
've previously written about the problems I had with
6228 my new Thinkpad X230, which was delivered with an
6229 <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
6230 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
6231 sustained writes. My hardware supplier have been very forthcoming in
6232 trying to find a solution, and after first trying with another
6233 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
6234 disk instead to fix it once and for all. The Samsung disk survived
6235 the installation of Debian with encrypted disks (filling the disk with
6236 random data during installation killed the first two), and I thus
6237 decided to trust it with my data. I have installed it as a Debian Edu
6238 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
6239 server at home using Kerberos and LDAP, and will use it as my work
6240 station from now on.
</p
>
6242 <p
>As this is a solid state disk with no moving parts, I believe the
6243 Debian Wheezy default installation need to be tuned a bit to increase
6244 performance and increase life time of the disk. The Linux kernel and
6245 user space applications do not yet adjust automatically to such
6246 environment. To make it easier for my self, I created a draft Debian
6247 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
6248 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
6249 for the ssd-setup package
</a
> is available from collab-maint, and it
6250 is set up to adjust the setup of the machine by just installing the
6251 package. If there is any non-SSD disk in the machine, the package
6252 will refuse to install, as I did not try to write any logic to sort
6253 file systems in SSD and non-SSD file systems.
</p
>
6255 <p
>I consider the package a draft, as I am a bit unsure how to best
6256 set up Debian Wheezy with an SSD. It is adjusted to my use case,
6257 where I set up the machine with one large encrypted partition (in
6258 addition to /boot), put LVM on top of this and set up partitions on
6259 top of this again. See the README file in the package source for the
6260 references I used to pick the settings. At the moment these
6261 parameters are tuned:
</p
>
6265 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
6266 (adding discard to /etc/crypttab)
</li
>
6268 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
6269 this case a cryptsetup partition) by changing issue_discards from
6270 0 to
1 in /etc/lvm/lvm.conf.
</li
>
6272 <li
>Set relatime as a file system option for ext3 and ext4 file
6275 <li
>Tell swap to use TRIM commands by adding
'discard
' to
6276 /etc/fstab.
</li
>
6278 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
6280 <li
>Run fstrim on every ext3 and ext4 file system every night (from
6281 cron.daily).
</li
>
6283 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
6284 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
6288 <p
>During installation, I cancelled the part where the installer fill
6289 the disk with random data, as this would kill the SSD performance for
6290 little gain. My goal with the encrypted file system is to ensure
6291 those stealing my laptop end up with a brick and not a working
6292 computer. I have no hope in keeping the really resourceful people
6293 from getting the data on the disk (see
6294 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
6295 Thus I concluded that adding the discard option to crypttab is the
6296 right thing to do.
</p
>
6298 <p
>I considered using the noop I/O scheduler, as several recommended
6299 it for SSD, but others recommended deadline and a benchmark I found
6300 indicated that deadline might be better for interactive use.
</p
>
6302 <p
>I also considered using the
'discard
' file system option for ext3
6303 and ext4, but read that it would give a performance hit ever time a
6304 file is removed, and thought it best to that that slowdown once a day
6305 instead of during my work.
</p
>
6307 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
6308 this is already done by Debian Edu.
</p
>
6310 <p
>I have not yet started on the user space tuning. I expect
6311 iceweasel need some tuning, and perhaps other applications too, but
6312 have not yet had time to investigate those parts.
</p
>
6314 <p
>The package should work on Ubuntu too, but I have not yet tested it
6317 <p
>As for the answer to the question in the title of this blog post,
6318 as far as I know, the only solution I know about is to replace the
6319 disk. It might be possible to flash it with Intel firmware instead of
6320 the Lenovo firmware. But I have not tried and did not want to do so
6321 without approval from Lenovo as I wanted to keep the warranty on the
6322 disk until a solution was found and they wanted the broken disks
6328 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
6329 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
6330 <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>
6331 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
6332 <description><p
>A few days ago, I wrote about
6333 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
6334 problems I experienced with my new X230 and its SSD disk
</a
>, which
6335 was dying during installation because it is unable to cope with
6336 sustained write. My supplier is in contact with
6337 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
6338 replacement disk to try to fix the problem. They decided to send an
6339 identical model, so my hopes for a permanent fix was slim.
</p
>
6341 <p
>Anyway, today I got the replacement disk and tried to install
6342 Debian Edu Wheezy with encrypted disk on it. The new disk have the
6343 same firmware version as the original. This time my hope raised
6344 slightly as the installation progressed, as the original disk used to
6345 die after
4-
7% of the disk was written to, while this time it kept
6346 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
6347 died again and I was back on square one. I still do not have a new
6348 laptop with a disk I can trust. I can not live with a disk that might
6349 lock up when I download a new
6350 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
6351 other large files. I look forward to hearing from my supplier with
6352 the next proposal from Lenovo.
</p
>
6354 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
6355 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
6356 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
6357 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
6358 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6359 P/N
45N8295, P0C38732.
</p
>
6361 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
6362 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
6363 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
6364 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
6365 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
6366 P/N
45N8295, P0C38732.
</p
>
6368 <p
>The only difference is in the first number (serial number?), ISN,
6369 SA, date and WNPP values. Mentioning all the details here in case
6370 someone is able to use the information to find a way to identify the
6371 failing disk among working ones (if any such working disk actually
6377 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
6378 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
6379 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
6380 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
6381 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
6382 Debian Edu developer gathering and Debian and Ubuntu bug squashing
6383 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
6384 member assosiation NUUG
</a
> and
6385 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
6386 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
6387 Bitraf
</a
>.
</p
>
6389 <p
>It starts
10:
00 and continue until late evening. Everyone is
6390 welcome, and there is no fee to participate. There is on the other
6391 hand limited space, and only room for
30 people. Please put your name
6392 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
6393 wiki page
</a
> if you plan to join us.
</p
>
6398 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
6399 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
6400 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
6401 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
6402 <description><p
>Half a year ago, I reported that I had to find a
6403 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
6404 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
6405 time to spend on it, and it took a while to find a model I believe
6406 will do the job, but two days ago the replacement finally arrived. I
6408 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
6409 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
6410 a roaming workstation, and it seemed to work flawlessly. But my
6411 second installation with encrypted disk was not as successful. More
6412 on that below.
</p
>
6414 <p
>I had a hard time trying to track down a good laptop, as my most
6415 important requirements (robust and with a good keyboard) are never
6416 listed in the feature list. But I did get good help from the search
6417 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6418 allowed me to limit the list of interesting laptops based on my other
6419 requirements. A bit surprising that SSD disk are not disks according
6420 to that search interface, so I had to drop specifying the number of
6421 disks from my search parameters. I also asked around among friends to
6422 get their impression on keyboards and robustness.
</p
>
6424 <p
>So the new laptop arrived, and it is quite a lot wider than the
6425 X41. I am not quite convinced about the keyboard, as it is
6426 significantly wider than my old keyboard, and I have to stretch my
6427 hand a lot more to reach the edges. But the key response is fairly
6428 good and the individual key shape is fairly easy to handle, so I hope
6429 I will get used to it. My old X40 was starting to fail, and I really
6430 needed a new laptop now. :)
</p
>
6432 <p
>Turning off the touch pad was simple. All it took was a quick
6433 visit to the BIOS during boot it disable it.
</p
>
6435 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
6436 lock up during load. And this happen when installing Debian Wheezy
6437 with encrypted disk, while the disk is being filled with random data.
6438 I also tested to install Ubuntu Raring, and it happen there too if I
6439 reenable the code to fill the disk with random data (it is disabled by
6440 default in Ubuntu). And the bug with is already known. It was
6441 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
6442 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
6443 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
6444 kernel developers as
6445 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
6446 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
6447 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
6448 Lenovo forums, both for
6449 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
6450 2012-
11-
10</a
> and for
6451 <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
6452 03-
20-
2013</a
>. The problem do not only affect installation. The
6453 reports state that the disk lock up during use if many writes are done
6454 on the disk, so it is much no use to work around the installation
6455 problem and end up with a computer that can lock up at any moment.
6457 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
6458 available
</a
> that will lock up the hard drive after running a few
6459 minutes by writing to a file.
</p
>
6461 <p
>I
've contacted my supplier and asked how to handle this, and after
6462 contacting PCHELP Norway (request
01D1FDP) which handle support
6463 requests for Lenovo, his first suggestion was to upgrade the disk
6464 firmware. Unfortunately there is no newer firmware available from
6465 Lenovo, as my disk already have the most recent one (version LF1i). I
6466 hope to hear more from him today and hope the problem can be
6472 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
6473 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
6474 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
6475 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
6476 <description><p
>Half a year ago, I reported that I had to find a replacement for my
6477 trusty old Thinkpad X41. Unfortunately I did not have much time to
6478 spend on it, but today the replacement finally arrived. I ended up
6479 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
6480 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
6481 Wheezy as a roaming workstation, and it worked flawlessly. As I write
6482 this, it is installing what I hope will be a more final installation,
6483 with a encrypted hard drive to ensure any dope head stealing it end up
6484 with an expencive door stop.
</p
>
6486 <p
>I had a hard time trying to track down a good laptop, as my most
6487 important requirements (robust and with a good keyboard) are never
6488 listed in the feature list. But I did get good help from the search
6489 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
6490 allowed me to limit the list of interesting laptops based on my other
6491 requirements. A bit surprising that SSD disk are not disks, so I had
6492 to drop number of disks from my search parameters.
</p
>
6494 <p
>I am not quite convinced about the keyboard, as it is significantly
6495 wider than my old keyboard, and I have to stretch my hand a lot more
6496 to reach the edges. But the key response is fairly good and the
6497 individual key shape is fairly easy to handle, so I hope I will get
6498 used to it. My old X40 was starting to fail, and I really needed a
6499 new laptop now. :)
</p
>
6501 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
6506 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
6507 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
6508 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
6509 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
6510 <description><p
>It annoys me when the computer fail to do automatically what it is
6511 perfectly capable of, and I have to do it manually to get things
6512 working. One such task is to find out what firmware packages are
6513 needed to get the hardware on my computer working. Most often this
6514 affect the wifi card, but some times it even affect the RAID
6515 controller or the ethernet card. Today I pushed version
0.4 of the
6516 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
6517 including a new script isenkram-autoinstall-firmware handling the
6518 process of asking all the loaded kernel modules what firmware files
6519 they want, find debian packages providing these files and install the
6520 debian packages. Here is a test run on my laptop:
</p
>
6522 <p
><pre
>
6523 # isenkram-autoinstall-firmware
6524 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
6525 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
6526 info: locating packages with the requested firmware files
6527 info: Updating APT sources after adding non-free APT source
6528 info: trying to install firmware-ipw2x00
6531 Preconfiguring packages ...
6532 Selecting previously deselected package firmware-ipw2x00.
6533 (Reading database ...
259727 files and directories currently installed.)
6534 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
6535 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
6537 </pre
></p
>
6539 <p
>When all the requested firmware is present, a simple message is
6540 printed instead:
</p
>
6542 <p
><pre
>
6543 # isenkram-autoinstall-firmware
6544 info: did not find any firmware files requested by loaded kernel modules. exiting
6546 </pre
></p
>
6548 <p
>It could use some polish, but it is already working well and saving
6549 me some time when setting up new machines. :)
</p
>
6551 <p
>So, how does it work? It look at the set of currently loaded
6552 kernel modules, and look up each one of them using modinfo, to find
6553 the firmware files listed in the module meta-information. Next, it
6554 download the Contents file from a nearby APT mirror, and search for
6555 the firmware files in this file to locate the package with the
6556 requested firmware file. If the package is in the non-free section, a
6557 non-free APT source is added and the package is installed using
6558 <tt
>apt-get install
</tt
>. The end result is a slightly better working
6561 <p
>I hope someone find time to implement a more polished version of
6562 this script as part of the hw-detect debian-installer module, to
6563 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
6564 #
655507</a
>. There really is no need to insert USB sticks with
6565 firmware during a PXE install when the packages already are available
6566 from the nearby Debian mirror.
</p
>
6571 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
6572 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
6573 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
6574 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
6575 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
6576 the screen just turn black when Linux boot, either during installation
6577 or on first boot from the hard disk. I
've seen it once in a while the
6578 last few years, but only recently understood the cause. I
've seen it
6579 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
6580 The reason seem to be in the wiring of some laptops. The system to
6581 control the screen background light is inverted, so when Linux try to
6582 turn the brightness fully on, it end up turning it off instead. I do
6583 not know which Linux drivers are affected, but this post is about the
6584 i915 driver used by the
6585 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6586 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
6588 <p
>The problem can be worked around two ways. Either by adding
6589 i915.invert_brightness=
1 as a kernel option, or by adding a file in
6590 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
6591 option when it load the i915 kernel module. On Debian and Ubuntu, it
6592 can be done by running these commands as root:
</p
>
6595 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
6596 update-initramfs -u -k all
6599 <p
>Since March
2012 there is
6600 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
6601 mechanism in the Linux kernel
</a
> to tell the i915 driver which
6602 hardware have this problem, and get the driver to invert the
6603 brightness setting automatically. To use it, one need to add a row in
6604 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
6605 intel_quirks array
</a
> in the driver source
6606 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
6607 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
6608 number (vendor number
8086 is assumed) and subdevice vendor and device
6611 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
6612 -vvnn
</tt
> for the video card in question:
</p
>
6614 <p
><pre
>
6615 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
6616 3rd Gen Core processor Graphics Controller [
8086:
0156] \
6617 (rev
09) (prog-if
00 [VGA controller])
6618 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
6619 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
6620 ParErr- Stepping- SE RR- FastB2B- DisINTx+
6621 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
6622 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
6624 Interrupt: pin A routed to IRQ
42
6625 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
6626 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
6627 Region
4: I/O ports at
4000 [size=
64]
6628 Expansion ROM at
<unassigned
> [disabled]
6629 Capabilities:
<access denied
>
6630 Kernel driver in use: i915
6631 </pre
></p
>
6633 <p
>The resulting intel_quirks entry would then look like this:
</p
>
6635 <p
><pre
>
6636 struct intel_quirk intel_quirks[] = {
6638 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
6639 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
6642 </pre
></p
>
6644 <p
>According to the kernel module instructions (as seen using
6645 <tt
>modinfo i915
</tt
>), information about hardware needing the
6646 invert_brightness flag should be sent to the
6647 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
6648 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
6649 developers. But my email about the laptop sent
2013-
06-
03 have not
6651 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
6652 web archive for the mailing list
</a
>, so I suspect they do not accept
6653 emails from non-subscribers. Because of this, I sent my patch also to
6654 the Debian bug tracking system instead as
6655 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
6656 sure the patch is not lost.
</p
>
6658 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
6659 with this problem working properly with Linux. If you use Gnome, your
6660 worries should be over at this point. But if you use KDE, there is
6661 something in KDE ignoring the invert_brightness setting and turning on
6662 the screen during login. I
've reported it to Debian as
6663 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
6664 have no idea yet how to figure out exactly what subsystem is doing
6665 this. Perhaps you can help? Perhaps you know what the Gnome
6666 developers did to handle this, and this can give a clue to the KDE
6667 developers? Or you know where in KDE the screen brightness is changed
6668 during login? If so, please update the BTS report (or get in touch if
6669 you do not know how to update BTS).
</p
>
6671 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
6672 acpi_backlight=vendor, to disable ACPI backlight support completely,
6673 as the ACPI information on the machine is trash and it is better to
6674 leave it to the intel video driver to control the screen
6675 backlight.
</p
>
6680 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
6681 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
6682 <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>
6683 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
6684 <description><p
>Two days ago, I asked
6685 <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
6686 I could install Linux on a Packard Bell EasyNote LV computer
6687 preinstalled with Windows
8</a
>. I found a solution, but am horrified
6688 with the obstacles put in the way of Linux users on a laptop with UEFI
6689 and Windows
8.
</p
>
6691 <p
>I never found out if the cause of my problems were the use of UEFI
6692 secure booting or fast boot. I suspect fast boot was the problem,
6693 causing the firmware to boot directly from HD without considering any
6694 key presses and alternative devices, but do not know UEFI settings
6695 enough to tell.
</p
>
6697 <p
>There is no way to install Linux on the machine in question without
6698 opening the box and disconnecting the hard drive! This is as far as I
6699 can tell, the only way to get access to the firmware setup menu
6700 without accepting the Windows
8 license agreement. I am told (and
6701 found description on how to) that it is possible to configure the
6702 firmware setup once booted into Windows
8. But as I believe the terms
6703 of that agreement are completely unacceptable, accepting the license
6704 was never an alternative. I do not enter agreements I do not intend
6705 to follow.
</p
>
6707 <p
>I feared I had to return the laptops and ask for a refund, and
6708 waste many hours on this, but luckily there was a way to get it to
6709 work. But I would not recommend it to anyone planning to run Linux on
6710 it, and I have become sceptical to Windows
8 certified laptops. Is
6711 this the way Linux will be forced out of the market place, by making
6712 it close to impossible for
"normal
" users to install Linux without
6713 accepting the Microsoft Windows license terms? Or at least not
6714 without risking to loose the warranty?
</p
>
6716 <p
>I
've updated the
6717 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
6718 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
6719 do not have to struggle as much as I did to get Linux into the
6722 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
6723 Michael Tokarev and others for feedback and ideas.
</p
>
6728 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
6729 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
6730 <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>
6731 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
6732 <description><p
>I
've run into quite a problem the last few days. I bought three
6733 new laptops for my parents and a few others. I bought Packard Bell
6734 Easynote LV to run Kubuntu on and use as their home computer. But I
6735 am completely unable to figure out how to install Linux on it. The
6736 computer is preinstalled with Windows
8, and I suspect it uses UEFI
6737 instead of a BIOS to boot.
</p
>
6739 <p
>The problem is that I am unable to get it to PXE boot, and unable
6740 to get it to boot the Linux installer from my USB stick. I have yet
6741 to try the DVD install, and still hope it will work. when I turn on
6742 the computer, there is no information on what buttons to press to get
6743 the normal boot menu. I expect to get some boot menu to select PXE or
6744 USB stick booting. When booting, it first ask for the language to
6745 use, then for some regional settings, and finally if I will accept the
6746 Windows
8 terms of use. As these terms are completely unacceptable to
6747 me, I have no other choice but to turn off the computer and try again
6748 to get it to boot the Linux installer.
</p
>
6750 <p
>I have gathered my findings so far on a Linlap page about the
6751 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
6752 EasyNote LV
</a
> model. If you have any idea how to get Linux
6753 installed on this machine, please get in touch or update that wiki
6754 page. If I can
't find a way to install Linux, I will have to return
6755 the laptop to the seller and find another machine for my parents.
</p
>
6757 <p
>I wonder, is this the way Linux will be forced out of the market
6758 using UEFI and
"secure boot
" by making it impossible to install Linux
6759 on new Laptops?
</p
>
6764 <title>How to transform a Debian based system to a Debian Edu installation
</title>
6765 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
6766 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
6767 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
6768 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
6769 an operating system based on Debian intended for use in schools. It
6770 contain a turn-key solution for the computer network provided to
6771 pupils in the primary schools. It provide both the central server,
6772 network boot servers and desktop environments with heaps of
6773 educational software. The project was founded almost
12 years ago,
6774 2001-
07-
02. If you want to support the project, which is in need for
6775 cash to fund developer gatherings and other project related activity,
6776 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
6777 donate some money
</a
>.
6779 <p
>A topic that come up again and again on the Debian Edu mailing
6780 lists and elsewhere, is the question on how to transform a Debian or
6781 Ubuntu installation into a Debian Edu installation. It isn
't very
6782 hard, and last week I wrote a script to replicate the steps done by
6783 the Debian Edu installer.
</p
>
6785 <p
>The script,
6786 <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/
>
6787 in the debian-edu-config package, will go through these six steps and
6788 transform an existing Debian Wheezy or Ubuntu (untested) installation
6789 into a Debian Edu Workstation:
</p
>
6793 <li
>Add skolelinux related APT sources.
</li
>
6794 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
6795 <li
>Install debian-edu-install to load preseeding values and pull in
6796 our configuration.
</li
>
6797 <li
>Preseed debconf database with profile setup in
6798 /etc/debian-edu/config, and run tasksel to install packages
6799 according to the profile specified in the config above,
6800 overriding some of the Debian automation machinery.
</li
>
6801 <li
>Run debian-edu-cfengine-D installation to configure everything
6802 that could not be done using preseeding.
</li
>
6803 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
6807 <p
>There are some steps in the Debian Edu installation that can not be
6808 replicated like this. Disk partitioning and LVM setup, for example.
6809 So this script just assume there is enough disk space to install all
6810 the needed packages.
</p
>
6812 <p
>The script was created to help a Debian Edu student working on
6813 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
6814 Debian Edu client, and using it he can take the existing
6815 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
6816 transform it into a fully functioning Debian Edu Workstation (or
6817 Roaming Workstation, or whatever :).
</p
>
6819 <p
>The default setting in the script is to create a KDE Workstation.
6820 If a LXDE based Roaming workstation is wanted instead, modify the
6821 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
6823 <p
><pre
>
6824 PROFILE=
"Roaming-Workstation
"
6825 DESKTOP=
"lxde
"
6826 </pre
></p
>
6828 <p
>The script could even become useful to set up Debian Edu servers in
6829 the cloud, by starting with a virtual Debian installation at some
6830 virtual hosting service and setting up all the services on first
6836 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
6837 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
6838 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
6839 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
6840 <description><P
>In January,
6841 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
6842 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
6843 channel #debian-lego
</a
>, for those of us in the Debian and Linux
6844 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
6845 marvellous construction system from Denmark. We also created
6846 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
6847 a place to take notes and write down our plans and hopes. And several
6848 people showed up to help. I was very happy to see the effect of my
6849 call. Since the small start, we have a debtags tag
6850 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
6851 tag for LEGO related packages, and now count
10 packages related to
6852 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
6854 <p
><table
>
6855 <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
>
6856 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
6857 <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
>
6858 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
6859 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
6860 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
6861 <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
>
6862 <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
>
6863 <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
>
6864 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
6865 </table
></p
>
6867 <p
>Some of these are available in Wheezy, and all but one are
6868 currently available in Jessie/testing. leocad is so far only
6869 available in experimental.
</p
>
6871 <p
>If you care about LEGO in Debian, please join us on IRC and help
6872 adding the rest of the great free software tools available on Linux
6873 for LEGO designers.
</p
>
6878 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
6879 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
6880 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
6881 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
6882 <description><p
>When I woke up this morning, I was very happy to see that the
6883 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
6884 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
6885 Debian release, and I expect to move my machines at home over to it fairly
6888 <p
>The new debian release contain heaps of new stuff, and one program
6889 in particular make me very happy to see included. The
6890 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
6891 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
6892 included for the first time. Alongside similar programs like
6893 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
6894 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
6895 it allow for visual programming where syntax errors can not happen,
6896 and a friendly programming environment for learning to control the
6897 computer. Scratch will also be included in the next release of Debian
6900 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
6901 Edu/Skolelinux release too. The
6902 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
6903 alpha release
</a
> went out last week, and the next should soon
6909 <title>Isenkram
0.2 finally in the Debian archive
</title>
6910 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
6911 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
6912 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
6913 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
6914 package
</a
> finally made it into the archive, after lingering in NEW
6915 for many months. I uploaded it to the Debian experimental suite
6916 2013-
01-
27, and today it was accepted into the archive.
</p
>
6918 <p
>Isenkram is a system for suggesting to users what packages to
6919 install to work with a pluggable hardware device. The suggestion pop
6920 up when the device is plugged in. For example if a Lego Mindstorm NXT
6921 is inserted, it will suggest to install the program needed to program
6922 the NXT controller. Give it a go, and report bugs and suggestions to
6928 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
6929 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
6930 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
6931 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
6932 <description><p
>My
6933 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
6934 bitcoin related blog post
</a
> mentioned that the new
6935 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
6936 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
6937 2013-
01-
19, and have been available in unstable since then. It was
6938 automatically copied to Ubuntu, and is available in their Raring
6939 version too.
</p
>
6941 <p
>But there is a strange problem with the build that block this new
6942 version from being available on the i386 and kfreebsd-i386
6943 architectures. For some strange reason, the autobuilders in Debian
6944 for these architectures fail to run the test suite on these
6945 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
6946 We are so far unable to reproduce it when building it manually, and
6947 no-one have been able to propose a fix. If you got an idea what is
6948 failing, please let us know via the BTS.
</p
>
6950 <p
>One feature that is annoying me with of the bitcoin client, because
6951 I often run low on disk space, is the fact that the client will exit
6952 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
6953 #
696715</a
>). So make sure you have enough disk space when you run
6956 <p
>As usual, if you use bitcoin and want to show your support of my
6957 activities, please send Bitcoin donations to my address
6958 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6963 <title>Welcome to the world, Isenkram!
</title>
6964 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
6965 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
6966 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
6967 <description><p
>Yesterday, I
6968 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
6969 for testers
</a
> for my prototype for making Debian better at handling
6970 pluggable hardware devices, which I
6971 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
6972 out to create
</a
> earlier this month. Several valuable testers showed
6973 up, and caused me to really want to to open up the development to more
6974 people. But before I did this, I want to come up with a sensible name
6975 for this project. Today I finally decided on a new name, and I have
6976 renamed the project from hw-support-handler to this new name. In the
6977 process, I moved the source to git and made it available as a
6978 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
6979 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
6980 To fetch and build the latest version of the source, use
</p
>
6983 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
6984 cd isenkram
&& git-buildpackage -us -uc
6987 <p
>I have not yet adjusted all files to use the new name yet. If you
6988 want to hack on the source or improve the package, please go ahead.
6989 But please talk to me first on IRC or via email before you do major
6990 changes, to make sure we do not step on each others toes. :)
</p
>
6992 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
6993 stuff, typically meaning tools, nails, screws, etc. Typical hardware
6994 stuff, in other words. I
've been told it is the Norwegian variant of
6995 the German word eisenkram, for those that are familiar with that
6998 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
6999 instructions, to avoid confusing people with an error from the signing
7002 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
7003 clone argument to avoid the need for authentication.
</p
>
7008 <title>First prototype ready making hardware easier to use in Debian
</title>
7009 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
7010 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
7011 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
7012 <description><p
>Early this month I set out to try to
7013 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
7014 the Debian support for pluggable hardware devices
</a
>. Now my
7015 prototype is working, and it is ready for a larger audience. To test
7017 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
7018 from the Debian Edu subversion repository
</a
>, build and install the
7019 package. You might have to log out and in again activate the
7020 autostart script.
</p
>
7022 <p
>The design is simple:
</p
>
7026 <li
>Add desktop entry in /usr/share/autostart/ causing a program
7027 hw-support-handlerd to start when the user log in.
</li
>
7029 <li
>This program listen for kernel events about new hardware (directly
7030 from the kernel like udev does), not using HAL dbus events as I
7031 initially did.
</li
>
7033 <li
>When new hardware is inserted, look up the hardware modalias in
7034 the APT database, a database
7035 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
7036 via HTTP
</a
> and a database available as part of the package.
</li
>
7038 <li
>If a package is mapped to the hardware in question, the package
7039 isn
't installed yet and this is the first time the hardware was
7040 plugged in, show a desktop notification suggesting to install the
7041 package or packages.
</li
>
7043 <li
>If the user click on the
'install package now
' button, ask
7044 aptdaemon via the PackageKit API to install the requrired package.
</li
>
7046 <li
>aptdaemon ask for root password or sudo password, and install the
7047 package while showing progress information in a window.
</li
>
7051 <p
>I still need to come up with a better name for the system. Here
7052 are some screen shots showing the prototype in action. First the
7053 notification, then the password request, and finally the request to
7054 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
7056 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
7057 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
7058 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
7059 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
7060 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
7062 <p
>The prototype still need to be improved with longer timeouts, but
7063 is already useful. The database of hardware to package mappings also
7064 need more work. It is currently compatible with the Ubuntu way of
7065 storing such information in the package control file, but could be
7066 changed to use other formats instead or in addition to the current
7067 method. I
've dropped the use of discover for this mapping, as the
7068 modalias approach is more flexible and easier to use on Linux as long
7069 as the Linux kernel expose its modalias strings directly.
</p
>
7071 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
7072 here is the command required to check out and build the source: Use
7073 '<tt
>svn checkout
7074 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
7075 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
7076 devscripts package.
</p
>
7078 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
7079 renamed to Isenkram and the source moved from the Debian Edu
7080 subversion repository to a Debian collab-maint git repository. See
7081 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
7082 instructions
</a
> for details.
</p
>
7087 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
7088 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
7089 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
7090 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
7091 <description><p
>This Christmas my trusty old laptop died. It died quietly and
7092 suddenly in bed. With a quiet whimper, it went completely quiet and
7093 black. The power button was no longer able to turn it on. It was a
7094 IBM Thinkpad X41, and the best laptop I ever had. Better than both
7095 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
7096 Compaq I had before that. Now I need to find a replacement. To keep
7097 going during Christmas, I moved the one year old SSD disk to my old
7098 X40 where it fitted (only one I had left that could use it), but it is
7099 not a durable solution.
7101 <p
>My laptop needs are fairly modest. This is my wishlist from when I
7102 got a new one more than
10 years ago. It still holds true.:)
</p
>
7106 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
7107 than A4).
</li
>
7108 <li
>Robust, it will be in my backpack every day.
</li
>
7109 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
7110 <li
>Long battery life time. Preferable a week.
</li
>
7111 <li
>Internal WIFI network card.
</li
>
7112 <li
>Internal Twisted Pair network card.
</li
>
7113 <li
>Some USB slots (
2-
3 is plenty)
</li
>
7114 <li
>Good keyboard - similar to the Thinkpad.
</li
>
7115 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
7117 <li
>Hardware supported by Debian Stable, ie the default kernel and
7118 X.org packages.
</li
>
7119 <li
>Quiet, preferably fan free (or at least not using the fan most of
7124 <p
>You will notice that there are no RAM and CPU requirements in the
7125 list. The reason is simply that the specifications on laptops the
7126 last
10-
15 years have been sufficient for my needs, and I have to look
7127 at other features to choose my laptop. But are there still made as
7128 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
7129 robust, and Thinkpads seem to be heading in the wrong direction since
7130 Lenovo took over. But I
've been told that X220 and X1 Carbon might
7131 still be useful.
</p
>
7133 <p
>Perhaps I should rethink my needs, and look for a pad with an
7134 external keyboard? I
'll have to check the
7135 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
7136 well-supported laptops, or perhaps just buy one preinstalled from one
7137 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
7138 Pre-loaded site
</a
>.
</p
>
7143 <title>How to find a browser plugin supporting a given MIME type
</title>
7144 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
7145 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
7146 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
7147 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
7148 install to get support for a given MIME type. Thanks to
7149 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
7150 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
7151 Unfortunately, not very many packages provide the needed meta
7152 information, Anyway, here is a small script to look up all browser
7153 plugin packages announcing ther MIME support using this specification:
</p
>
7159 def pkgs_handling_mimetype(mimetype):
7164 version = pkg.candidate
7166 version = pkg.installed
7169 record = version.record
7170 if not record.has_key(
'Npp-MimeType
'):
7172 mime_types = record[
'Npp-MimeType
'].split(
',
')
7173 for t in mime_types:
7174 t = t.rstrip().strip()
7176 thepkgs.append(pkg.name)
7178 mimetype =
"audio/ogg
"
7179 if
1 < len(sys.argv):
7180 mimetype = sys.argv[
1]
7181 print
"Browser plugin packages supporting %s:
" % mimetype
7182 for pkg in pkgs_handling_mimetype(mimetype):
7183 print
" %s
" %pkg
7186 <p
>It can be used like this to look up a given MIME type:
</p
>
7189 % ./apt-find-browserplug-for-mimetype
7190 Browser plugin packages supporting audio/ogg:
7192 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
7193 Browser plugin packages supporting application/x-shockwave-flash:
7194 browser-plugin-gnash
7198 <p
>In Ubuntu this mechanism is combined with support in the browser
7199 itself to query for plugins and propose to install the needed
7200 packages. It would be great if Debian supported such feature too. Is
7201 anyone working on adding it?
</p
>
7203 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
7204 request for icweasel support for this feature is
7205 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
7206 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
7207 of manpower and wish for a different design is the reason thus feature
7208 is not yet in iceweasel from Debian.
</p
>
7213 <title>What is the most supported MIME type in Debian?
</title>
7214 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
7215 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
7216 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
7217 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
7218 proposal to add AppStream information to the Debian archive
</a
>, is a
7219 proposal to make it possible for a Desktop application to propose to
7220 the user some package to install to gain support for a given MIME
7221 type, font, library etc. that is currently missing. With such
7222 mechanism in place, it would be possible for the desktop to
7223 automatically propose and install leocad if some LDraw file is
7224 downloaded by the browser.
</p
>
7226 <p
>To get some idea about the current content of the archive, I decided
7227 to write a simple program to extract all .desktop files from the
7228 Debian archive and look up the claimed MIME support there. The result
7230 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
7231 site
</a
>. Using the collected information, it become possible to
7232 answer the question in the title. Here are the
20 most supported MIME
7233 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
7234 The complete list is available from the link above.
</p
>
7236 <p
><strong
>Debian Stable:
</strong
></p
>
7240 ----- -----------------------
7256 18 application/x-ogg
7263 <p
><strong
>Debian Testing:
</strong
></p
>
7267 ----- -----------------------
7283 18 application/x-ogg
7290 <p
><strong
>Debian Unstable:
</strong
></p
>
7294 ----- -----------------------
7311 18 application/x-ogg
7317 <p
>I am told that PackageKit can provide an API to access the kind of
7318 information mentioned in DEP-
11. I have not yet had time to look at
7319 it, but hope the PackageKit people in Debian are on top of these
7322 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
7323 discovering a typo in my script.
</p
>
7328 <title>Using modalias info to find packages handling my hardware
</title>
7329 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
7330 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
7331 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
7332 <description><p
>Yesterday, I wrote about the
7333 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
7334 values provided by the Linux kernel
</a
> following my hope for
7335 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
7336 dongle support in Debian
</a
>. Using this knowledge, I have tested how
7337 modalias values attached to package names can be used to map packages
7338 to hardware. This allow the system to look up and suggest relevant
7339 packages when I plug in some new hardware into my machine, and replace
7340 discover and discover-data as the database used to map hardware to
7343 <p
>I create a modaliases file with entries like the following,
7344 containing package name, kernel module name (if relevant, otherwise
7345 the package name) and globs matching the relevant hardware
7348 <p
><blockquote
>
7349 Package: package-name
7350 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
7351 </blockquote
></p
>
7353 <p
>It is fairly trivial to write code to find the relevant packages
7354 for a given modalias value using this file.
</p
>
7356 <p
>An entry like this would suggest the video and picture application
7357 cheese for many USB web cameras (interface bus class
0E01):
</p
>
7359 <p
><blockquote
>
7361 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
7362 </blockquote
></p
>
7364 <p
>An entry like this would suggest the pcmciautils package when a
7365 CardBus bridge (bus class
0607) PCI device is present:
</p
>
7367 <p
><blockquote
>
7368 Package: pcmciautils
7369 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
7370 </blockquote
></p
>
7372 <p
>An entry like this would suggest the package colorhug-client when
7373 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
7375 <p
><blockquote
>
7376 Package: colorhug-client
7377 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
7378 </blockquote
></p
>
7380 <p
>I believe the format is compatible with the format of the Packages
7381 file in the Debian archive. Ubuntu already uses their Packages file
7382 to store their mappings from packages to hardware.
</p
>
7384 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
7385 announce the hardware it support in a way my prototype understand.
7386 This allow those publishing packages in an APT source outside the
7387 Debian archive as well as those backporting packages to make sure the
7388 hardware mapping are included in the package meta information. I
've
7389 tested such header in the pymissile package, and its modalias mapping
7390 is working as it should with my prototype. It even made it to Ubuntu
7393 <p
>To test if it was possible to look up supported hardware using only
7394 the shell tools available in the Debian installer, I wrote a shell
7395 implementation of the lookup code. The idea is to create files for
7396 each modalias and let the shell do the matching. Please check out and
7398 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
7399 shell script. It run without any extra dependencies and fetch the
7400 hardware mappings from the Debian archive and the subversion
7401 repository where I currently work on my prototype.
</p
>
7403 <p
>When I use it on a machine with a yubikey inserted, it suggest to
7404 install yubikey-personalization:
</p
>
7406 <p
><blockquote
>
7407 % ./hw-support-lookup
7408 <br
>yubikey-personalization
7410 </blockquote
></p
>
7412 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
7413 propose to install the pcmciautils package:
</p
>
7415 <p
><blockquote
>
7416 % ./hw-support-lookup
7417 <br
>pcmciautils
7419 </blockquote
></p
>
7421 <p
>If you know of any hardware-package mapping that should be added to
7422 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
7423 database
</a
>, please tell me about it.
</p
>
7425 <p
>It could be possible to generate several of the mappings between
7426 packages and hardware. One source would be to look at packages with
7427 kernel modules, ie packages with *.ko files in /lib/modules/, and
7428 extract their modalias information. Another would be to look at
7429 packages with udev rules, ie packages with files in
7430 /lib/udev/rules.d/, and extract their vendor/model information to
7431 generate a modalias matching rule. I have not tested any of these to
7432 see if it work.
</p
>
7434 <p
>If you want to help implementing a system to let us propose what
7435 packages to install when new hardware is plugged into a Debian
7436 machine, please send me an email or talk to me on
7437 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7442 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
7443 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
7444 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
7445 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
7446 <description><p
>While looking into how to look up Debian packages based on hardware
7447 information, to find the packages that support a given piece of
7448 hardware, I refreshed my memory regarding modalias values, and decided
7449 to document the details. Here are my findings so far, also available
7451 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7452 Debian Edu subversion repository
</a
>:
7454 <p
><strong
>Modalias decoded
</strong
></p
>
7456 <p
>This document try to explain what the different types of modalias
7457 values stands for. It is in part based on information from
7458 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
7459 &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;,
7460 &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
7461 &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;.
7463 <p
>The modalias entries for a given Linux machine can be found using
7464 this shell script:
</p
>
7467 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
7470 <p
>The supported modalias globs for a given kernel module can be found
7471 using modinfo:
</p
>
7474 % /sbin/modinfo psmouse | grep alias:
7475 alias: serio:ty05pr*id*ex*
7476 alias: serio:ty01pr*id*ex*
7480 <p
><strong
>PCI subtype
</strong
></p
>
7482 <p
>A typical PCI entry can look like this. This is an Intel Host
7483 Bridge memory controller:
</p
>
7485 <p
><blockquote
>
7486 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
7487 </blockquote
></p
>
7489 <p
>This represent these values:
</p
>
7494 sv
00001028 (subvendor)
7495 sd
000001AD (subdevice)
7497 sc
00 (bus subclass)
7501 <p
>The vendor/device values are the same values outputted from
'lspci
7502 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
7503 0600. The
0600 class is a host bridge. Other useful bus values are
7504 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
7506 <p
>Not sure how to figure out the interface value, nor what it
7509 <p
><strong
>USB subtype
</strong
></p
>
7511 <p
>Some typical USB entries can look like this. This is an internal
7512 USB hub in a laptop:
</p
>
7514 <p
><blockquote
>
7515 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
7516 </blockquote
></p
>
7518 <p
>Here is the values included in this alias:
</p
>
7521 v
1D6B (device vendor)
7522 p
0001 (device product)
7524 dc
09 (device class)
7525 dsc
00 (device subclass)
7526 dp
00 (device protocol)
7527 ic
09 (interface class)
7528 isc
00 (interface subclass)
7529 ip
00 (interface protocol)
7532 <p
>The
0900 device class/subclass means hub. Some times the relevant
7533 class is in the interface class section. For a simple USB web camera,
7534 these alias entries show up:
</p
>
7536 <p
><blockquote
>
7537 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
7538 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
7539 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
7540 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
7541 </blockquote
></p
>
7543 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
7544 camera),
0101 is audio control device and
0102 is audio streaming (aka
7545 microphone). Thus this is a camera with microphone included.
</p
>
7547 <p
><strong
>ACPI subtype
</strong
></p
>
7549 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
7550 receiver in a Thinkpad X40:
</p
>
7552 <p
><blockquote
>
7553 acpi:IBM0071:PNP0511:
7554 </blockquote
></p
>
7556 <p
>The values between the colons are IDs.
</p
>
7558 <p
><strong
>DMI subtype
</strong
></p
>
7560 <p
>The DMI table contain lots of information about the computer case
7561 and model. This is an entry for a IBM Thinkpad X40, fetched from
7562 /sys/devices/virtual/dmi/id/modalias:
</p
>
7564 <p
><blockquote
>
7565 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
7566 </blockquote
></p
>
7568 <p
>The values present are
</p
>
7571 bvn IBM (BIOS vendor)
7572 bvr
1UETB
6WW(
1.66) (BIOS version)
7573 bd
06/
15/
2005 (BIOS date)
7574 svn IBM (system vendor)
7575 pn
2371H4G (product name)
7576 pvr ThinkPadX40 (product version)
7577 rvn IBM (board vendor)
7578 rn
2371H4G (board name)
7579 rvr NotAvailable (board version)
7580 cvn IBM (chassis vendor)
7581 ct
10 (chassis type)
7582 cvr NotAvailable (chassis version)
7585 <p
>The chassis type
10 is Notebook. Other interesting values can be
7586 found in the dmidecode source:
</p
>
7590 4 Low Profile Desktop
7603 17 Main Server Chassis
7604 18 Expansion Chassis
7606 20 Bus Expansion Chassis
7607 21 Peripheral Chassis
7609 23 Rack Mount Chassis
7618 <p
>The chassis type values are not always accurately set in the DMI
7619 table. For example my home server is a tower, but the DMI modalias
7620 claim it is a desktop.
</p
>
7622 <p
><strong
>SerIO subtype
</strong
></p
>
7624 <p
>This type is used for PS/
2 mouse plugs. One example is from my
7625 test machine:
</p
>
7627 <p
><blockquote
>
7628 serio:ty01pr00id00ex00
7629 </blockquote
></p
>
7631 <p
>The values present are
</p
>
7640 <p
>This type is supported by the psmouse driver. I am not sure what
7641 the valid values are.
</p
>
7643 <p
><strong
>Other subtypes
</strong
></p
>
7645 <p
>There are heaps of other modalias subtypes according to
7646 file2alias.c. There is the rest of the list from that source: amba,
7647 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
7648 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
7649 vmbus, x86cpu and zorro. I did not spend time documenting all of
7650 these, as they do not seem relevant for my intended use with mapping
7651 hardware to packages when new stuff is inserted during run time.
</p
>
7653 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
7655 <p
>To check which kernel modules provide support for a given modalias,
7656 one can use the following shell script:
</p
>
7659 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
7660 echo
"$id
" ; \
7661 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
7665 <p
>The output can look like this (only the first few entries as the
7666 list is very long on my test machine):
</p
>
7670 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
7672 FATAL: Module acpi:device: not found.
7674 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
7675 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
7676 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
7677 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
7678 acpi:IBM0071:PNP0511:
7679 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
7680 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
7681 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
7685 <p
>If you want to help implementing a system to let us propose what
7686 packages to install when new hardware is plugged into a Debian
7687 machine, please send me an email or talk to me on
7688 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
7690 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
7691 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
7692 in /sys/ with space in them.
</p
>
7697 <title>Moved the pymissile Debian packaging to collab-maint
</title>
7698 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
7699 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
7700 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
7701 <description><p
>As part of my investigation on how to improve the support in Debian
7702 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
7703 Launcher and updated the Debian package
7704 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
7705 sure udev will fix the device permissions when it is plugged in. I
7706 also added a
"Modaliases
" header to test it in the Debian archive and
7707 hopefully make the package be proposed by jockey in Ubuntu when a user
7708 plug in his rocket launcher. In the process I moved the source to a
7709 git repository under collab-maint, to make it easier for any DD to
7710 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
7711 is not very active, but the software still work for me even after five
7712 years of relative silence. The new git repository is not listed in
7713 the uploaded package yet, because I want to test the other changes a
7714 bit more before I upload the new version. If you want to check out
7715 the new version with a .desktop file included, visit the
7716 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
7717 view
</a
> or use
"<tt
>git clone
7718 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
7723 <title>Lets make hardware dongles easier to use in Debian
</title>
7724 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
7725 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
7726 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
7727 <description><p
>One thing that annoys me with Debian and Linux distributions in
7728 general, is that there is a great package management system with the
7729 ability to automatically install software packages by downloading them
7730 from the distribution mirrors, but no way to get it to automatically
7731 install the packages I need to use the hardware I plug into my
7732 machine. Even if the package to use it is easily available from the
7733 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
7734 suggest to automatically install the python-nxt, nbc and t2n packages
7735 I need to talk to it. When I plug in a Yubikey, it could propose the
7736 yubikey-personalization package. The information required to do this
7737 is available, but no-one have pulled all the pieces together.
</p
>
7739 <p
>Some years ago, I proposed to
7740 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
7741 the discover subsystem to implement this
</a
>. The idea is fairly
7746 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
7747 starting when a user log in.
</li
>
7749 <li
>Set this program up to listen for kernel events emitted when new
7750 hardware is inserted into the computer.
</li
>
7752 <li
>When new hardware is inserted, look up the hardware ID in a
7753 database mapping to packages, and take note of any non-installed
7754 packages.
</li
>
7756 <li
>Show a message to the user proposing to install the discovered
7757 package, and make it easy to install it.
</li
>
7761 <p
>I am not sure what the best way to implement this is, but my
7762 initial idea was to use dbus events to discover new hardware, the
7763 discover database to find packages and
7764 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
7767 <p
>Yesterday, I found time to try to implement this idea, and the
7768 draft package is now checked into
7769 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
7770 Debian Edu subversion repository
</a
>. In the process, I updated the
7771 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
7772 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
7773 the relevant packages in Debian, and uploaded a new version
7774 2.2013.01.09 to unstable. I also discovered that the current
7775 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
7776 package in Debian no longer discovered any USB devices, because
7777 /proc/bus/usb/devices is no longer present. I ported it to use
7778 libusb as a fall back option to get it working. The fixed package
7779 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
7780 because of the freeze).
</p
>
7782 <p
>With this prototype in place, I can insert my Yubikey, and get this
7783 desktop notification to show up (only once, the first time it is
7784 inserted):
</p
>
7786 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
7788 <p
>For this prototype to be really useful, some way to automatically
7789 install the proposed packages by pressing the
"Please install
7790 program(s)
" button should to be implemented.
</p
>
7792 <p
>If this idea seem useful to you, and you want to help make it
7793 happen, please help me update the discover-data database with mappings
7794 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
7795 list the package you would like to have installed when a given
7796 hardware device is inserted into your computer, and report bugs using
7797 reportbug if it isn
't. Or, if you know of a better way to provide
7798 such mapping, please let me know.
</p
>
7800 <p
>This prototype need more work, and there are several questions that
7801 should be considered before it is ready for production use. Is dbus
7802 the correct way to detect new hardware? At the moment I look for HAL
7803 dbus events on the system bus, because that is the events I could see
7804 on my Debian Squeeze KDE desktop. Are there better events to use?
7805 How should the user be notified? Is the desktop notification
7806 mechanism the best option, or should the background daemon raise a
7807 popup instead? How should packages be installed? When should they
7808 not be installed?
</p
>
7810 <p
>If you want to help getting such feature implemented in Debian,
7811 please send me an email. :)
</p
>
7816 <title>New IRC channel for LEGO designers using Debian
</title>
7817 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
7818 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
7819 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
7820 <description><p
>During Christmas, I have worked a bit on the Debian support for
7821 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
7822 NXT
</a
>. My son and I have played a bit with my NXT set, and I
7823 discovered I had to build all the tools myself because none were
7824 already in Debian Squeeze. If Debian support for LEGO is something
7825 you care about, please join me on the IRC channel
7826 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
7827 irc.debian.org). There is a lot that could be done to improve the
7828 Debian support for LEGO designers. For example both CAD software
7829 and Mindstorm compilers are missing. :)
</p
>
7831 <p
>Update
2012-
01-
03: A
7832 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
7833 including links to Lego related packages is now available.
</p
>
7838 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
7839 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
7840 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
7841 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
7842 <description><p
>Let me start by wishing you all marry Christmas and a happy new
7843 year! I hope next year will prove to be a good year.
</p
>
7845 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
7846 decentralised
"currency
" that allow people to transfer bitcoins
7847 between each other with minimal overhead, is a very interesting
7848 experiment. And as I wrote a few days ago, the bitcoin situation in
7849 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
7850 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
7851 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
7852 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
7853 for one of the ftpmasters to approve the new bitcoin-qt package
7856 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
7857 team in Debian, you can easily test the package in Debian Squeeze
7858 using the following steps to get a set of working packages:
</p
>
7860 <blockquote
><pre
>
7861 git clone git://git.debian.org/git/collab-maint/bitcoin
7863 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
7864 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
7865 </pre
></blockquote
>
7867 <p
>You might have to install some build dependencies as well. The
7868 list of commands should give you two packages, bitcoind and
7869 bitcoin-qt, ready for use in a Squeeze environment. Note that the
7870 client will download the complete set of bitcoin
"blocks
", which need
7871 around
5.6 GiB of data on my machine at the moment. Make sure your
7872 ~/.bitcoin/ directory have lots of spare room if you want to download
7873 all the blocks. The client will warn if the disk is getting full, so
7874 there is not really a problem if you got too little room, but you will
7875 not be able to get all the features out of the client.
</p
>
7877 <p
>As usual, if you use bitcoin and want to show your support of my
7878 activities, please send Bitcoin donations to my address
7879 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7884 <title>A word on bitcoin support in Debian
</title>
7885 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
7886 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
7887 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
7888 <description><p
>It has been a while since I wrote about
7889 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
7890 peer-to-peer based crypto-currency, and the reason is simply that I
7891 have been busy elsewhere. But two days ago, I started looking at the
7892 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
7893 Debian
</a
> again to try to recover my old bitcoin wallet. The package
7894 is now maintained by a
7895 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
7896 people
</a
>, and the grunt work had already been done by this team. We
7897 owe a huge thank you to all these team members. :)
7898 But I was sad to discover that the bitcoin client is missing in
7899 Wheezy. It is only available in Sid (and an outdated client from
7900 backports). The client had several RC bugs registered in BTS blocking
7901 it from entering testing. To try to help the team and improve the
7902 situation, I spent some time providing patches and triaging the bug
7903 reports. I also had a look at the bitcoin package available from Matt
7905 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
7906 Ubuntu
</a
>, and moved the useful pieces from that version into the
7907 Debian package.
</p
>
7909 <p
>After checking with the main package maintainer Jonas Smedegaard on
7910 IRC, I pushed several patches into the collab-maint git repository to
7911 improve the package. It now contains fixes for the RC issues (not from
7912 me, but fixed by Scott Howard), build rules for a Qt GUI client
7913 package, konqueror support for the bitcoin: URI and bash completion
7914 setup. As I work on Debian Squeeze, I also created
7915 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
7916 patch to backport
</a
> the latest version. Jonas is going to look at
7917 it and try to integrate it into the git repository before uploading a
7918 new version to unstable.
7920 <p
>I would very much like bitcoin to succeed, to get rid of the
7921 centralized control currently exercised in the monetary system. I
7922 find it completely unacceptable that the USA government is collecting
7923 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
7924 that the major credit card companies can block legal money
7925 transactions to Wikileaks. But for bitcoin to succeed, more people
7926 need to use bitcoins, and more people need to accept bitcoins when
7927 they sell products and services. Improving the bitcoin support in
7928 Debian is a small step in the right direction, but not enough.
7929 Unfortunately the user experience when browsing the web and wanting to
7930 pay with bitcoin is still not very good. The bitcoin: URI is a step
7931 in the right direction, but need to work in most or every browser in
7932 use. Also the bitcoin-qt client is too heavy to fire up to do a
7933 quick transaction. I believe there are other clients available, but
7934 have not tested them.
</p
>
7937 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
7938 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
7939 I received
20.15 BTC so far on the address I provided in my blog two
7940 years ago, as can be
7941 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
7942 on the blockexplorer service
</a
>. Thank you everyone for your
7943 donation. The blockexplorer service demonstrates quite well that
7944 bitcoin is not quite anonymous and untracked. :) I wonder if the
7945 number of users have gone up since then. If you use bitcoin and want
7946 to show your support of my activity, please send Bitcoin donations to
7947 the same address as last time,
7948 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
7953 <title>Git repository for song book for Computer Scientists
</title>
7954 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
7955 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
7956 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
7957 <description><p
>As I
7958 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
7959 this summer
</a
>, I have created a Computer Science song book a few
7960 years ago, and today I finally found time to create a public
7961 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
7962 repository for the project
</a
>.
</p
>
7964 <p
>If you want to help out, please clone the source and submit patches
7965 to the HTML version. To generate the PDF and PostScript version,
7966 please use prince XML, or let me know about a useful free software
7967 processor capable of creating a good looking PDF from the HTML.
</p
>
7969 <p
>Want to sing? You can still find the song book in HTML, PDF and
7970 PostScript formats at
7971 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
7972 Science Songbook
</a
>.
</p
>
7977 <title>Gratulerer med
19-årsdagen, Debian!
</title>
7978 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
7979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
7980 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
7981 <description><p
>I dag fyller
7982 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
7983 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
7984 si gratulerer med dagen, Debian!
</p
>
7989 <title>Song book for Computer Scientists
</title>
7990 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
7991 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
7992 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
7993 <description><p
>Many years ago, while studying Computer Science at the
7994 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
7995 collecting computer related songs for use at parties. The original
7996 version was written in LaTeX, but a few years ago I got help from
7997 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
7998 while keeping the ability to create a nice book in PDF format. I have
7999 not had time to maintain the book for a while now, and guess I should
8000 put it up on some public version control repository where others can
8001 help me extend and update the book. If anyone is volunteering to help
8002 me with this, send me an email. Also let me know if there are songs
8003 missing in my book.
</p
>
8005 <p
>I have not mentioned the book on my blog so far, and it occured to
8006 me today that I really should let all my readers share the joys of
8007 singing out load about programming, computers and computer networks.
8008 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
8009 12</a
> is about to start (and I am not going). Want to sing? Check
8010 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
8011 Computer Science Songbook
</a
>.
8016 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
8017 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
8018 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
8019 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
8020 <description><p
>At work we have heaps of servers. I believe the total count is
8021 around
1000 at the moment. To be able to get help from the vendors
8022 when something go wrong, we want to keep the firmware on the servers
8023 up to date. If the firmware isn
't the latest and greatest, the
8024 vendors typically refuse to start debugging any problems until the
8025 firmware is upgraded. So before every reboot, we want to upgrade the
8026 firmware, and we would really like everyone handling servers at the
8027 university to do this themselves when they plan to reboot a machine.
8028 For that to happen we at the unix server admin group need to provide
8029 the tools to do so.
</p
>
8031 <p
>To make firmware upgrading easier, I am working on a script to
8032 fetch and install the latest firmware for the servers we got. Most of
8033 our hardware are from Dell and HP, so I have focused on these servers
8034 so far. This blog post is about the Dell part.
</P
>
8036 <p
>On the Dell FTP site I was lucky enough to find
8037 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
8038 with firmware information for all
11th generation servers, listing
8039 which firmware should be used on a given model and where on the FTP
8040 site I can find it. Using a simple perl XML parser I can then
8041 download the shell scripts Dell provides to do firmware upgrades from
8042 within Linux and reboot when all the firmware is primed and ready to
8043 be activated on the first reboot.
</p
>
8045 <p
>This is the Dell related fragment of the perl code I am working on.
8046 Are there anyone working on similar tools for firmware upgrading all
8047 servers at a site? Please get in touch and lets share resources.
</p
>
8049 <p
><pre
>
8053 use File::Temp qw(tempdir);
8055 # Install needed RHEL packages if missing
8057 'XML::Simple
' =
> 'perl-XML-Simple
',
8059 for my $module (keys %rhelmodules) {
8060 eval
"use $module;
";
8062 my $pkg = $rhelmodules{$module};
8063 system(
"yum install -y $pkg
");
8064 eval
"use $module;
";
8068 my $errorsto =
'pere@hungry.com
';
8074 sub run_firmware_script {
8075 my ($opts, $script) = @_;
8077 print STDERR
"fail: missing script name\n
";
8080 print STDERR
"Running $script\n\n
";
8082 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
8083 print STDERR
"success: firmware script ran succcessfully\n
";
8085 print STDERR
"fail: firmware script returned error\n
";
8089 sub run_firmware_scripts {
8090 my ($opts, @dirs) = @_;
8091 # Run firmware packages
8092 for my $dir (@dirs) {
8093 print STDERR
"info: Running scripts in $dir\n
";
8094 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
8095 while (my $s = readdir $dh) {
8096 next if $s =~ m/^\.\.?/;
8097 run_firmware_script($opts,
"$dir/$s
");
8105 print STDERR
"info: Downloading $url\n
";
8106 system(
"wget --quiet \
"$url\
"");
8111 my $product = `dmidecode -s system-product-name`;
8114 if ($product =~ m/PowerEdge/) {
8116 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
8117 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
8119 my $tmpdir = tempdir(
8123 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
8124 system(
'gunzip Catalog.xml.gz
');
8125 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
8126 # -q is quiet, disabling interactivity and reducing console output
8127 my $fwopts =
"-q
";
8129 for my $url (@paths) {
8130 fetch_dell_fw($url);
8132 run_firmware_scripts($fwopts, $tmpdir);
8134 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
8135 print STDERR
"error: Please report to $errorsto.\n
";
8139 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
8140 print STDERR
"error: Please report to $errorsto.\n
";
8146 my $url =
"ftp://ftp.us.dell.com/$path
";
8150 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
8151 # firmware packages to download from Dell. Only work for Linux
8152 # machines and
11th generation Dell servers.
8153 sub fetch_dell_fw_list {
8154 my $filename = shift;
8156 my $product = `dmidecode -s system-product-name`;
8158 my ($mybrand, $mymodel) = split(/\s+/, $product);
8160 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
8162 my $xml = XMLin($filename);
8164 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
8165 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
8166 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
8168 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
8169 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
8171 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
8173 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
8175 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
8178 for my $component (@{$xml-
>{SoftwareComponent}}) {
8179 my $componenttype = $component-
>{ComponentType}-
>{value};
8181 # Drop application packages, only firmware and BIOS
8182 next if
'APAC
' eq $componenttype;
8184 my $cpath = $component-
>{path};
8185 for my $path (@paths) {
8186 if ($cpath =~ m%/$path$%) {
8187 push(@paths, $cpath);
8195 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
8196 it could work on other platforms with some tweaking. Anyone know a
8197 index like Catalog.xml is available from HP for HP servers? At the
8198 moment I maintain a similar list manually and it is quickly getting
8204 <title>How is booting into runlevel
1 different from single user boots?
</title>
8205 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
8206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
8207 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
8208 <description><p
>Wouter Verhelst have some
8209 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
8210 comments and opinions
</a
> on my blog post on
8211 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
8212 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
8213 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
8214 default KDE desktop in Debian
</a
>. I only have time to address one
8215 small piece of his comment now, and though it best to address the
8216 misunderstanding he bring forward:
</p
>
8218 <p
><blockquote
>
8219 Currently, a system admin has four options: [...] boot to a
8220 single-user system (by adding
'single
' to the kernel command line;
8221 this runs rcS and rc1 scripts)
8222 </blockquote
></p
>
8224 <p
>This make me believe Wouter believe booting into single user mode
8225 and booting into runlevel
1 is the same. I am not surprised he
8226 believe this, because it would make sense and is a quite sensible
8227 thing to believe. But because the boot in Debian is slightly broken,
8228 runlevel
1 do not work properly and it isn
't the same as single user
8229 mode. I
'll try to explain what is actually happing, but it is a bit
8230 hard to explain.
</p
>
8232 <p
>Single user mode is defined like this in /etc/inittab:
8233 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
8234 executed in single user mode is sulogin. Single user mode is a boot
8235 state
"between
" the runlevels, and when booting into single user mode,
8236 only the scripts in /etc/rcS.d/ are executed before the init process
8237 enters the single user state. When switching to runlevel
1, the state
8238 is in fact not ending in runlevel
1, but it passes through runlevel
1
8239 and end up in the single user mode (see /etc/rc1.d/S03single, which
8240 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
8241 1. It is confusing that the
'S
' (single user) init mode is not the
8242 mode enabled by /etc/rcS.d/ (which is more like the initial boot
8245 <p
>This summary might make it clearer. When booting for the first
8246 time into single user mode, the following commands are executed:
8247 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
8248 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
8249 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
8250 trying to continue after visiting single user mode. Not all services
8251 are started again as they should, causing the machine to end up in an
8252 unpredicatble state. This is why Debian admins recommend rebooting
8253 after visiting single user mode.
</p
>
8255 <p
>A similar problem with runlevel
1 is caused by the amount of
8256 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
8257 to runlevel
1, the services started from /etc/rcS.d/ are not properly
8258 stopped when passing through the scripts in /etc/rc1.d/, and not
8259 started again when switching away from runlevel
1 to the runlevels
8260 2-
5. I believe the problem is best fixed by moving all the scripts
8261 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
8262 functioning single user mode during boot.
</p
>
8264 <p
>I have spent several years investigating the Debian boot system,
8265 and discovered this problem a few years ago. I suspect it originates
8266 from when sysvinit was introduced into Debian, a long time ago.
</p
>
8271 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
8272 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
8273 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
8274 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
8275 <description><p
>In the Debian boot system, several packages include scripts that
8276 are started from /etc/rcS.d/. In fact, there is a bite more of them
8277 than make sense, and this causes a few problems. What kind of
8278 problems, you might ask. There are at least two problems. The first
8279 is that it is not possible to recover a machine after switching to
8280 runlevel
1. One need to actually reboot to get the machine back to
8281 the expected state. The other is that single user boot will sometimes
8282 run into problems because some of the subsystems are activated before
8283 the root login is presented, causing problems when trying to recover a
8284 machine from a problem in that subsystem. A minor additional point is
8285 that moving more scripts out of rcS.d/ and into the other rc#.d/
8286 directories will increase the amount of scripts that can run in
8287 parallel during boot, and thus decrease the boot time.
</p
>
8289 <p
>So, which scripts should start from rcS.d/. In short, only the
8290 scripts that _have_ to execute before the root login prompt is
8291 presented during a single user boot should go there. Everything else
8292 should go into the numeric runlevels. This means things like
8293 lm-sensors, fuse and x11-common should not run from rcS.d, but from
8294 the numeric runlevels. Today in Debian, there are around
115 init.d
8295 scripts that are started from rcS.d/, and most of them should be moved
8296 out. Do your package have one of them? Please help us make single
8297 user and runlevel
1 better by moving it.
</p
>
8299 <p
>Scripts setting up the screen, keyboard, system partitions
8300 etc. should still be started from rcS.d/, but there is for example no
8301 need to have the network enabled before the single user login prompt
8302 is presented.
</p
>
8304 <p
>As always, things are not so easy to fix as they sound. To keep
8305 Debian systems working while scripts migrate and during upgrades, the
8306 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
8307 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
8308 and the next ones can only be moved when their dependencies have been
8309 moved first. This migration must be done sequentially while we ensure
8310 that the package system upgrade packages in the right order to keep
8311 the system state correct. This will require some coordination when it
8312 comes to network related packages, but most of the packages with
8313 scripts that should migrate do not have anything in rcS.d/ depending
8314 on them. Some packages have already been updated, like the sudo
8315 package, while others are still left to do. I wish I had time to work
8316 on this myself, but real live constrains make it unlikely that I will
8317 find time to push this forward.
</p
>
8322 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
8323 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
8324 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
8325 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
8326 <description><p
>While at Debconf11, I have several times during discussions
8327 mentioned the issues I believe should be improved in Debian for its
8328 desktop to be useful for more people. The use case for this is my
8329 parents, which are currently running Kubuntu which solve the
8332 <p
>I suspect these four missing features are not very hard to
8333 implement. After all, they are present in Ubuntu, so if we wanted to
8334 do this in Debian we would have a source.
</p
>
8338 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
8339 are new packages available for upgrades, a icon in the KDE status bar
8340 indicate this, and clicking on it will activate the simple upgrade
8341 tool to handle it. I have no problem guiding both of my parents
8342 through the process over the phone. If a kernel reboot is required,
8343 this too is indicated by the status bars and the upgrade tool. Last
8344 time I checked, nothing with the same features was working in KDE in
8347 <li
><strong
>Simple handling of missing Firefox browser
8348 plugins.
</strong
> When the browser encounter a MIME type it do not
8349 currently have a handler for, it will ask the user if the system
8350 should search for a package that would add support for this MIME type,
8351 and if the user say yes, the APT sources will be searched for packages
8352 advertising the MIME type in their control file (visible in the
8353 Packages file in the APT archive). If one or more packages are found,
8354 it is a simple click of the mouse to add support for the missing mime
8355 type. If the package require the user to accept some non-free
8356 license, this is explained to the user. The entire process make it
8357 more clear to the user why something do not work in the browser, and
8358 make the chances higher for the user to blame the web page authors and
8359 not the browser for any missing features.
</li
>
8361 <li
><strong
>Simple handling of missing multimedia codec/format
8362 handlers.
</strong
> When the media players encounter a format or codec
8363 it is not supporting, a dialog pop up asking the user if the system
8364 should search for a package that would add support for it. This
8365 happen with things like MP3, Windows Media or H
.264. The selection
8366 and installation procedure is very similar to the Firefox browser
8367 plugin handling. This is as far as I know implemented using a
8368 gstreamer hook. The end result is that the user easily get access to
8369 the codecs that are present from the APT archives available, while
8370 explaining more on why a given format is unsupported by Ubuntu.
</li
>
8372 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
8373 displaying a text/plain file in my Debian browser, it will propose to
8374 start emacs to show it. If I remember correctly, when doing the same
8375 in Kunbutu it show the file as a text file in the browser. At least I
8376 know Opera will show text files within the browser. I much prefer the
8377 latter behaviour.
</li
>
8381 <p
>There are other nice features as well, like the simplified suite
8382 upgrader, but given that I am the one mostly doing the dist-upgrade,
8383 it do not matter much.
</p
>
8385 <p
>I really hope we could get these features in place for the next
8386 Debian release. It would require the coordinated effort of several
8387 maintainers, but would make the end user experience a lot better.
</p
>
8392 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
8393 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
8394 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
8395 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
8396 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
8397 site is build on Debian/Squeeze, and this platform was chosen because
8398 I am most familiar with Debian (being a Debian Developer for around
10
8399 years) because it is the latest stable Debian release which should get
8400 security support for a few years.
</p
>
8402 <p
>The web service is written in Perl, and depend on some perl modules
8403 that are missing in Debian at the moment. It would be great if these
8404 modules were added to the Debian archive, allowing anyone to set up
8405 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
8406 in their own country using only Debian packages. The list of modules
8407 missing in Debian/Squeeze isn
't very long, and I hope the perl group
8408 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
8409 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
8410 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
8411 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
8412 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
8413 easier in the future.
</p
>
8415 <p
>Thanks to the great tools in Debian, getting the missing modules
8416 installed on my server was a simple call to
'cpan2deb Module::Name
'
8417 and
'dpkg -i
' to install the resulting package. But this leave me
8418 with the responsibility of tracking security problems, which I really
8419 do not have time for.
</p
>
8424 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
8425 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
8426 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
8427 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
8428 <description><p
>Here is a small update for my English readers. Most of my blog
8429 posts have been in Norwegian the last few weeks, so here is a short
8430 update in English.
</p
>
8432 <p
>The kids still keep me too busy to get much free software work
8433 done, but I did manage to organise a project to get a Norwegian port
8434 of the British service
8435 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
8436 and it has been running for a month now. The entire project has been
8437 organised by me and two others. Around Christmas we gathered sponsors
8438 to fund the development work. In January I drafted a contract with
8439 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
8440 and in February the development took place. Most of it involved
8441 converting the source to use GPS coordinates instead of British
8442 easting/northing, and the resulting code should be a lot easier to get
8443 running in any country by now. The Norwegian
8444 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
8445 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
8446 source and the source for administrative borders in Norway, and
8447 support for this had to be added/fixed.
</p
>
8449 <p
>The Norwegian version went live March
3th, and we spent the weekend
8450 polishing the system before we announced it March
7th. The system is
8451 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
8452 problem reports in a few weeks. Soon we hope to announce the Android
8453 and iPhone versions making it even easier to report problems with the
8454 public infrastructure.
</p
>
8456 <p
>Perhaps something to consider for those of you in countries without
8457 such service?
</p
>
8462 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
8463 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
8464 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
8465 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
8466 <description><p
>The last few days I have looked at ways to track open security
8467 issues here at my work with the University of Oslo. My idea is that
8468 it should be possible to use the information about security issues
8469 available on the Internet, and check our locally
8470 maintained/distributed software against this information. It should
8471 allow us to verify that no known security issues are forgotten. The
8472 CVE database listing vulnerabilities seem like a great central point,
8473 and by using the package lists from Debian mapped to CVEs provided by
8474 the testing security team, I believed it should be possible to figure
8475 out which security holes were present in our free software
8476 collection.
</p
>
8478 <p
>After reading up on the topic, it became obvious that the first
8479 building block is to be able to name software packages in a unique and
8480 consistent way across data sources. I considered several ways to do
8481 this, for example coming up with my own naming scheme like using URLs
8482 to project home pages or URLs to the Freshmeat entries, or using some
8483 existing naming scheme. And it seem like I am not the first one to
8484 come across this problem, as MITRE already proposed and implemented a
8485 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
8486 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
8487 software, hardware and other platform components. The CPE ids are
8488 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
8489 Vulnerability Database
</a
>, allowing me to look up know security
8490 issues for any CPE name. With this in place, all I need to do is to
8491 locate the CPE id for the software packages we use at the university.
8492 This is fairly trivial (I google for
'cve cpe $package
' and check the
8493 NVD entry if a CVE for the package exist).
</p
>
8495 <p
>To give you an example. The GNU gzip source package have the CPE
8496 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
8497 check out, one could look up
8498 <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
8499 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
8500 The most recent one is
8501 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
8502 and at the bottom of the NVD page for this vulnerability the complete
8503 list of affected versions is provided.
</p
>
8505 <p
>The NVD database of CVEs is also available as a XML dump, allowing
8506 for offline processing of issues. Using this dump, I
've written a
8507 small script taking a list of CPEs as input and list all CVEs
8508 affecting the packages represented by these CPEs. One give it CPEs
8509 with version numbers as specified above and get a list of open
8510 security issues out.
</p
>
8512 <p
>Of course for this approach to be useful, the quality of the NVD
8513 information need to be high. For that to happen, I believe as many as
8514 possible need to use and contribute to the NVD database. I notice
8516 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
8517 map from CVE to CPE
</a
>, indicating that they are using the CPE
8518 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
8520 <p
>To get an idea about the quality for free software, I spent some
8521 time making it possible to compare the CVE database from Debian with
8522 the CVE database in NVD. The result look fairly good, but there are
8523 some inconsistencies in NVD (same software package having several
8524 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
8525 Debian believe are affected by a CVE). Hope to find time to improve
8526 the quality of NVD, but that require being able to get in touch with
8527 someone maintaining it. So far my three emails with questions and
8528 corrections have not seen any reply, but I hope contact can be
8529 established soon.
</p
>
8531 <p
>An interesting application for CPEs is cross platform package
8532 mapping. It would be useful to know which packages in for example
8533 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
8534 this would be trivial if all linux distributions provided CPE entries
8535 for their packages.
</p
>
8540 <title>Which module is loaded for a given PCI and USB device?
</title>
8541 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
8542 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
8543 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
8544 <description><p
>In the
8545 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
8546 package in Debian, there is a script to report useful information
8547 about the running hardware for use when people report missing
8548 information. One part of this script that I find very useful when
8549 debugging hardware problems, is the part mapping loaded kernel module
8550 to the PCI device it claims. It allow me to quickly see if the kernel
8551 module I expect is driving the hardware I am struggling with. To see
8552 the output, make sure discover-data is installed and run
8553 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
8554 one of my machines like this:
</p
>
8558 10de:
03eb i2c_nforce2
8561 10de:
03f0 snd_hda_intel
8570 <p
>The code in question look like this, slightly modified for
8571 readability and to drop the output to file descriptor
3:
</p
>
8574 if [ -d /sys/bus/pci/devices/ ] ; then
8575 echo loaded pci modules:
8577 cd /sys/bus/pci/devices/
8578 for address in * ; do
8579 if [ -d
"$address/driver/module
" ] ; then
8580 module=`cd $address/driver/module ; pwd -P | xargs basename`
8581 if grep -q
"^$module
" /proc/modules ; then
8582 address=$(echo $address |sed s/
0000://)
8583 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
8584 echo
"$id $module
"
8593 <p
>Similar code could be used to extract USB device module
8597 if [ -d /sys/bus/usb/devices/ ] ; then
8598 echo loaded usb modules:
8600 cd /sys/bus/usb/devices/
8601 for address in * ; do
8602 if [ -d
"$address/driver/module
" ] ; then
8603 module=`cd $address/driver/module ; pwd -P | xargs basename`
8604 if grep -q
"^$module
" /proc/modules ; then
8605 address=$(echo $address |sed s/
0000://)
8606 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
8607 if [
"$id
" ] ; then
8608 echo
"$id $module
"
8618 <p
>This might perhaps be something to include in other tools as
8624 <title>How to test if a laptop is working with Linux
</title>
8625 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
8626 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
8627 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
8628 <description><p
>The last few days I have spent at work here at the
<a
8629 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
8630 batch of computers will work with Linux. Every year for the last few
8631 years the university have organised shared bid of a few thousand
8632 computers, and this year HP won the bid. Two different desktops and
8633 five different laptops are on the list this year. We in the UNIX
8634 group want to know which one of these computers work well with RHEL
8635 and Ubuntu, the two Linux distributions we currently handle at the
8636 university.
</p
>
8638 <p
>My test method is simple, and I share it here to get feedback and
8639 perhaps inspire others to test hardware as well. To test, I PXE
8640 install the OS version of choice, and log in as my normal user and run
8641 a few applications and plug in selected pieces of hardware. When
8642 something fail, I make a note about this in the test matrix and move
8643 on. If I have some spare time I try to report the bug to the OS
8644 vendor, but as I only have the machines for a short time, I rarely
8645 have the time to do this for all the problems I find.
</p
>
8647 <p
>Anyway, to get to the point of this post. Here is the simple tests
8648 I perform on a new model.
</p
>
8652 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
8653 and Ubuntu Maverik at the moment. If I feel like it, I also test with
8654 RHEL5 and Debian Edu/Squeeze.
</li
>
8656 <li
>Is X.org working? If the graphical login screen show up after
8657 installation, X.org is working.
</li
>
8659 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
8660 package mesa-utils on Ubuntu) and writing down the frames per second
8661 reported by the program.
</li
>
8663 <li
>Is sound working? With Gnome and KDE, a sound is played when
8664 logging in, and if I can hear this the test is successful. If there
8665 are several audio exits on the machine, I try them all and check if
8666 the Gnome/KDE audio mixer can control where to send the sound. I
8667 normally test this by playing
8668 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
8669 video
</a
> in Firefox/Iceweasel.
</li
>
8671 <li
>Is the USB subsystem working? I test this by plugging in a USB
8672 memory stick and see if Gnome/KDE notices this.
</li
>
8674 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
8675 I have lying around, and see if Gnome/KDE notices this.
</li
>
8677 <li
>Is any built in camera working? Test using cheese, and see if a
8678 picture from the v4l device show up.
</li
>
8680 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
8681 any bluetooth devices are discovered. In my office, I normally see a
8684 <li
>For laptops, is the SD or Compaq Flash reader working. I have
8685 memory modules lying around, and stick them in and see if Gnome/KDE
8686 notice this.
</li
>
8688 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
8689 special button work, and if the laptop continue to work after
8692 <li
>For laptops, is the extra buttons working, like audio level,
8693 adjusting background light, switching on/off external video output,
8694 switching on/off wifi, bluetooth, etc? The set of buttons differ from
8695 laptop to laptop, so I just write down which are working and which are
8698 <li
>Some laptops have smart card readers, finger print readers,
8699 acceleration sensors etc. I rarely test these, as I do not know how
8700 to quickly test if they are working or not, so I only document their
8701 existence.
</li
>
8705 <p
>By now I suspect you are really curious what the test results are
8706 for the HP machines I am testing. I
'm not done yet, so I will report
8707 the test results later. For now I can report that HP
8100 Elite work
8708 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
8709 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
8710 can see, I have most machines left to test. One interesting
8711 observation is that Ubuntu Lucid has almost twice the frame rate than
8712 RHEL6 with glxgears. No idea why.
</p
>
8717 <title>Some thoughts on BitCoins
</title>
8718 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
8719 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
8720 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
8721 <description><p
>As I continue to explore
8722 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
8723 what properties the system have, and how it will be affected by laws
8724 and regulations here in Norway. Here are some random notes.
</p
>
8726 <p
>One interesting thing to note is that since the transactions are
8727 verified using a peer to peer network, all details about a transaction
8728 is known to everyone. This means that if a BitCoin address has been
8729 published like I did with mine in my initial post about BitCoin, it is
8730 possible for everyone to see how many BitCoins have been transfered to
8731 that address. There is even a web service to look at the details for
8732 all transactions. There I can see that my address
8733 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
8734 have received
16.06 Bitcoin, the
8735 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
8736 address of Simon Phipps have received
181.97 BitCoin and the address
8737 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
8738 of EFF have received
2447.38 BitCoins so far. Thank you to each and
8739 every one of you that donated bitcoins to support my activity. The
8740 fact that anyone can see how much money was transfered to a given
8741 address make it more obvious why the BitCoin community recommend to
8742 generate and hand out a new address for each transaction. I
'm told
8743 there is no way to track which addresses belong to a given person or
8744 organisation without the person or organisation revealing it
8745 themselves, as Simon, EFF and I have done.
</p
>
8747 <p
>In Norway, and in most other countries, there are laws and
8748 regulations limiting how much money one can transfer across the border
8749 without declaring it. There are money laundering, tax and accounting
8750 laws and regulations I would expect to apply to the use of BitCoin.
8751 If the Skolelinux foundation
8752 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
8753 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
8754 normal bank transfers like EFF is doing, how should this be accounted?
8755 Given that it is impossible to know if money can cross the border or
8756 not, should everything or nothing be declared? What exchange rate
8757 should be used when calculating taxes? Would receivers have to pay
8758 income tax if the foundation were to pay Skolelinux contributors in
8759 BitCoin? I have no idea, but it would be interesting to know.
</p
>
8761 <p
>For a currency to be useful and successful, it must be trusted and
8762 accepted by a lot of users. It must be possible to get easy access to
8763 the currency (as a wage or using currency exchanges), and it must be
8764 easy to spend it. At the moment BitCoin seem fairly easy to get
8765 access to, but there are very few places to spend it. I am not really
8766 a regular user of any of the vendor types currently accepting BitCoin,
8767 so I wonder when my kind of shop would start accepting BitCoins. I
8768 would like to buy electronics, travels and subway tickets, not herbs
8769 and books. :) The currency is young, and this will improve over time
8770 if it become popular, but I suspect regular banks will start to lobby
8771 to get BitCoin declared illegal if it become popular. I
'm sure they
8772 will claim it is helping fund terrorism and money laundering (which
8773 probably would be true, as is any currency in existence), but I
8774 believe the problems should be solved elsewhere and not by blaming
8775 currencies.
</p
>
8777 <p
>The process of creating new BitCoins is called mining, and it is
8778 CPU intensive process that depend on a bit of luck as well (as one is
8779 competing against all the other miners currently spending CPU cycles
8780 to see which one get the next lump of cash). The
"winner
" get
50
8781 BitCoin when this happen. Yesterday I came across the obvious way to
8782 join forces to increase ones changes of getting at least some coins,
8783 by coordinating the work on mining BitCoins across several machines
8784 and people, and sharing the result if one is lucky and get the
50
8786 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
8787 if this sounds interesting. I have not had time to try to set up a
8788 machine to participate there yet, but have seen that running on ones
8789 own for a few days have not yield any BitCoins througth mining
8792 <p
>Update
2010-
12-
15: Found an
<a
8793 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
8794 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
8795 it was interesting to read. The arguments presented seem to be
8796 equally valid for gold, which was used as a currency for many years.
</p
>
8801 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
8802 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
8803 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
8804 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
8805 <description><p
>With this weeks lawless
8806 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
8807 attacks
</a
> on Wikileak and
8808 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
8809 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
8810 not be trusted to handle money transactions.
8812 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
8813 Phipps on bitcoin
</a
> reminded me about a project that a friend of
8814 mine mentioned earlier. I decided to follow Simon
's example, and get
8815 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
8816 some help from my friend to get it all running, and he even handed me
8817 some bitcoins to get started. I even donated a few bitcoins to Simon
8818 for helping me remember BitCoin.
</p
>
8820 <p
>So, what is bitcoins, you probably wonder? It is a digital
8821 crypto-currency, decentralised and handled using peer-to-peer
8822 networks. It allows anonymous transactions and prohibits central
8823 control over the transactions, making it impossible for governments
8824 and companies alike to block donations and other transactions. The
8825 source is free software, and while the key dependency wxWidgets
2.9
8826 for the graphical user interface is missing in Debian, the command
8827 line client builds just fine. Hopefully Jonas
8828 <a href=
"http://bugs.debian.org/
578157">will get the package into
8829 Debian
</a
> soon.
</p
>
8831 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
8832 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
8833 bitcoins
</a
> when selling services and goods, and there are even
8834 currency
"stock
" markets where the exchange rate is decided. There
8835 are not many users so far, but the concept seems promising. If you
8836 want to get started and lack a friend with any bitcoins to spare,
8838 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
8839 bitcoin at the time of writing). Use
8840 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
8841 on the current exchange rates.
</p
>
8843 <p
>As an experiment, I have decided to set up bitcoind on one of my
8844 machines. If you want to support my activity, please send Bitcoin
8845 donations to the address
8846 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
8851 <title>Why isn
't Debian Edu using VLC?
</title>
8852 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
8853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
8854 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
8855 <description><p
>In the latest issue of Linux Journal, the readers choices were
8856 presented, and the winner among the multimedia player were VLC.
8857 Personally, I like VLC, and it is my player of choice when I first try
8858 to play a video file or stream. Only if VLC fail will I drag out
8859 gmplayer to see if it can do better. The reason is mostly the failure
8860 model and trust. When VLC fail, it normally pop up a error message
8861 reporting the problem. When mplayer fail, it normally segfault or
8862 just hangs. The latter failure mode drain my trust in the program.
<p
>
8864 <p
>But even if VLC is my player of choice, we have choosen to use
8865 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
8866 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
8867 plugin to play web videos seamlessly, and the VLC browser plugin is
8868 not very good. For example, it lack in-line control buttons, so there
8869 is no way for the user to pause the video. Also, when I
8870 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
8871 tested the browser plugins
</a
> available in Debian, the VLC plugin
8872 failed on several video pages where mplayer based plugins worked. If
8873 the browser plugin for VLC was as good as the gecko-mediaplayer
8874 package (which uses mplayer), we would switch.
</P
>
8876 <p
>While VLC is a good player, its user interface is slightly
8877 annoying. The most annoying feature is its inconsistent use of
8878 keyboard shortcuts. When the player is in full screen mode, its
8879 shortcuts are different from when it is playing the video in a window.
8880 For example, space only work as pause when in full screen mode. I
8881 wish it had consisten shortcuts and that space also would work when in
8882 window mode. Another nice shortcut in gmplayer is [enter] to restart
8883 the current video. It is very nice when playing short videos from the
8884 web and want to restart it when new people arrive to have a look at
8885 what is going on.
</p
>
8890 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
8891 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
8892 <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>
8893 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
8894 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
8895 upgrade testing of the
8896 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8897 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
8898 This seem like a very good idea, so I adjusted by test scripts and
8899 can now present the updated result from today:
</p
>
8901 <p
>This is for Gnome:
</p
>
8903 <p
>Installed using apt-get, missing with aptitude
</p
>
8905 <blockquote
><p
>
8910 browser-plugin-gnash
8917 freedesktop-sound-theme
8919 gconf-defaults-service
8934 gnome-desktop-environment
8938 gnome-session-canberra
8943 gstreamer0.10-fluendo-mp3
8949 libapache2-mod-dnssd
8952 libaprutil1-dbd-sqlite3
8955 libboost-date-time1.42
.0
8956 libboost-python1.42
.0
8957 libboost-thread1.42
.0
8959 libchamplain-gtk-
0.4-
0
8961 libclutter-gtk-
0.10-
0
8968 libfreerdp-plugins-standard
8983 libgnomepanel2.24-cil
8988 libgtksourceview2.0-common
8989 libmono-addins-gui0.2-cil
8990 libmono-addins0.2-cil
8991 libmono-cairo2.0-cil
8992 libmono-corlib2.0-cil
8993 libmono-i18n-west2.0-cil
8994 libmono-posix2.0-cil
8995 libmono-security2.0-cil
8996 libmono-sharpzip2.84-cil
8997 libmono-system2.0-cil
9000 libndesk-dbus-glib1.0-cil
9001 libndesk-dbus1.0-cil
9011 libtelepathy-farsight0
9020 nautilus-sendto-empathy
9024 python-aptdaemon-gtk
9026 python-beautifulsoup
9041 python-gtksourceview2
9052 python-pkg-resources
9059 python-twisted-conch
9065 python-zope.interface
9070 rhythmbox-plugin-cdrecorder
9077 system-config-printer-udev
9079 telepathy-mission-control-
5
9090 </p
></blockquote
>
9092 <p
>Installed using apt-get, removed with aptitude
</p
>
9094 <blockquote
><p
>
9100 fast-user-switch-applet
9119 libgtksourceview2.0-
0
9121 libsdl1.2debian-alsa
9127 system-config-printer
9132 </p
></blockquote
>
9134 <p
>Installed using aptitude, missing with apt-get
</p
>
9136 <blockquote
><p
>
9137 gstreamer0.10-gnomevfs
9138 </p
></blockquote
>
9140 <p
>Installed using aptitude, removed with apt-get
</p
>
9142 <blockquote
><p
>
9144 </p
></blockquote
>
9146 <p
>This is for KDE:
</p
>
9148 <p
>Installed using apt-get, missing with aptitude
</p
>
9150 <blockquote
><p
>
9152 </p
></blockquote
>
9154 <p
>Installed using apt-get, removed with aptitude
</p
>
9156 <blockquote
><p
>
9159 </p
></blockquote
>
9161 <p
>Installed using aptitude, missing with apt-get
</p
>
9163 <blockquote
><p
>
9177 kdeartwork-emoticons
9179 kdeartwork-theme-icon
9183 kdebase-workspace-bin
9184 kdebase-workspace-data
9198 kscreensaver-xsavers
9213 plasma-dataengines-workspace
9215 plasma-desktopthemes-artwork
9216 plasma-runners-addons
9217 plasma-scriptengine-googlegadgets
9218 plasma-scriptengine-python
9219 plasma-scriptengine-qedje
9220 plasma-scriptengine-ruby
9221 plasma-scriptengine-webkit
9222 plasma-scriptengines
9223 plasma-wallpapers-addons
9224 plasma-widget-folderview
9225 plasma-widget-networkmanagement
9229 xscreensaver-data-extra
9231 xscreensaver-gl-extra
9232 xscreensaver-screensaver-bsod
9233 </p
></blockquote
>
9235 <p
>Installed using aptitude, removed with apt-get
</p
>
9237 <blockquote
><p
>
9239 google-gadgets-common
9257 libggadget-qt-
1.0-
0b
9262 libkonqsidebarplugin4a
9271 libplasma-geolocation-interface4
9273 libplasmagenericshell4
9287 libsmokeknewstuff2-
3
9288 libsmokeknewstuff3-
3
9290 libsmokektexteditor3
9298 libsmokeqtnetwork4-
3
9304 libsmokeqtuitools4-
3
9316 plasma-dataengines-addons
9317 plasma-scriptengine-superkaramba
9318 plasma-widget-lancelot
9319 plasma-widgets-addons
9320 plasma-widgets-workspace
9324 update-notifier-common
9325 </p
></blockquote
>
9327 <p
>Running apt-get autoremove made the results using apt-get and
9328 aptitude a bit more similar, but there are still quite a lott of
9329 differences. I have no idea what packages should be installed after
9330 the upgrade, but hope those that do can have a look.
</p
>
9335 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
9336 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
9337 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
9338 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
9339 <description><p
>Most of the computers in use by the
9340 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
9341 are virtual machines. And they have been Xen machines running on a
9342 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
9343 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
9344 bit harder that it could have been, because we set up the Xen virtual
9345 machines to get the virtual partitions from LVM, which as far as I
9346 know is not supported by KVM. So to migrate, we had to convert
9347 several LVM logical volumes to partitions on a virtual disk file.
</p
>
9350 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
9351 nice recipe
</a
> to do this, and wrote the following script to do the
9352 migration. It uses qemu-img from the qemu package to make the disk
9353 image, parted to partition it, losetup and kpartx to present the disk
9354 image partions as devices, and dd to copy the data. I NFS mounted the
9355 new servers storage area on the old server to do the migration.
</p
>
9361 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
9366 if [ -z
"$
1" ] ; then
9367 echo
"Usage: $
0 &lt;hostname
&gt;
"
9373 if [ ! -e /dev/vg_data/$host-disk ] ; then
9374 echo
"error: unable to find LVM volume for $host
"
9378 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
9379 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9380 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
9381 totalsize=$(( ( $disksize + $swapsize ) ))
9384 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
9385 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
9387 parted $img mklabel msdos
9388 parted $img mkpart primary linux-swap
0 $disksize
9389 parted $img mkpart primary ext2 $disksize $totalsize
9390 parted $img set
1 boot on
9393 losetup /dev/loop0 $img
9394 kpartx -a /dev/loop0
9396 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
9397 fsck.ext3 -f /dev/mapper/loop0p1 || true
9398 mkswap /dev/mapper/loop0p2
9400 kpartx -d /dev/loop0
9401 losetup -d /dev/loop0
9404 <p
>The script is perhaps so simple that it is not copyrightable, but
9405 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
9407 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
9408 the new disk image attached, installed grub-pc and linux-image-
686 and
9409 set up grub to boot from the disk image. After this, the KVM machines
9410 seem to work just fine.
</p
>
9415 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
9416 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
9417 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
9418 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
9419 <description><p
>I
'm still running upgrade testing of the
9420 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
9421 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
9422 status. Here is a short update based on a test I ran
20101118.
</p
>
9424 <p
>I still do not know what a correct migration should look like, so I
9425 report any differences between apt and aptitude and hope someone else
9426 can see if anything should be changed.
</p
>
9428 <p
>This is for Gnome:
</p
>
9430 <p
>Installed using apt-get, missing with aptitude
</p
>
9432 <blockquote
><p
>
9433 apache2.2-bin aptdaemon at-spi baobab binfmt-support
9434 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
9435 dmz-cursor-theme empathy empathy-common finger
9436 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
9437 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
9438 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
9439 gnome-cards-data gnome-codec-install gnome-core
9440 gnome-desktop-environment gnome-disk-utility gnome-screenshot
9441 gnome-search-tool gnome-session-canberra gnome-spell
9442 gnome-system-log gnome-themes-extras gnome-themes-more
9443 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
9444 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
9445 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
9446 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
9447 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
9448 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
9449 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
9450 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
9451 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
9452 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
9453 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
9454 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
9455 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
9456 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
9457 libgtk2.0-cil libgtkglext1 libgtksourceview-common
9458 libgtksourceview2.0-common libmono-addins-gui0.2-cil
9459 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
9460 libmono-i18n-west2.0-cil libmono-posix2.0-cil
9461 libmono-security2.0-cil libmono-sharpzip2.84-cil
9462 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
9463 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
9464 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
9465 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
9466 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
9467 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
9468 libxalan2-java libxerces2-java media-player-info mesa-utils
9469 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
9470 nautilus-sendto-empathy openoffice.org-writer2latex
9471 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
9472 python-aptdaemon python-aptdaemon-gtk python-axiom
9473 python-beautifulsoup python-bugbuddy python-clientform
9474 python-coherence python-configobj python-crypto python-cupshelpers
9475 python-cupsutils python-eggtrayicon python-elementtree
9476 python-epsilon python-evolution python-feedparser python-gdata
9477 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
9478 python-gtksourceview2 python-httplib2 python-louie python-mako
9479 python-markupsafe python-mechanize python-nevow python-notify
9480 python-opengl python-openssl python-pam python-pkg-resources
9481 python-pyasn1 python-pysqlite2 python-rdflib python-serial
9482 python-tagpy python-twisted-bin python-twisted-conch
9483 python-twisted-core python-twisted-web python-utidylib python-webkit
9484 python-xdg python-zope.interface remmina remmina-plugin-data
9485 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
9486 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
9487 software-center svgalibg1 system-config-printer-udev
9488 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
9489 totem totem-coherence totem-mozilla totem-plugins
9490 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
9492 </p
></blockquote
>
9494 Installed using apt-get, removed with aptitude
9496 <blockquote
><p
>
9497 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
9498 epiphany-extensions epiphany-gecko evolution-exchange
9499 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
9500 gedit-common gnome-app-install gnome-games gnome-games-data
9501 gnome-nettool gnome-system-tools gnome-themes gnome-utils
9502 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
9503 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
9504 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
9505 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
9506 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
9507 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
9508 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9509 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9510 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9511 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
9512 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
9513 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
9514 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
9515 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
9516 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
9517 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
9518 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
9519 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
9520 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
9521 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
9522 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
9523 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
9524 sound-juicer swfdec-gnome system-config-printer totem-common
9525 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
9526 </p
></blockquote
>
9528 <p
>Installed using aptitude, missing with apt-get
</p
>
9530 <blockquote
><p
>
9531 gstreamer0.10-gnomevfs
9532 </p
></blockquote
>
9534 <p
>Installed using aptitude, removed with apt-get
</p
>
9536 <blockquote
><p
>
9538 </p
></blockquote
>
9540 <p
>This is for KDE:
</p
>
9542 <p
>Installed using apt-get, missing with aptitude
</p
>
9544 <blockquote
><p
>
9545 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
9546 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
9547 ghostscript-x git gnome-audio gnugo granatier gs-common
9548 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
9549 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
9550 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
9551 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9552 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
9553 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
9554 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9555 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
9556 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
9557 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
9558 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
9559 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
9560 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
9561 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
9562 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
9563 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
9564 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
9565 libkrossui4 libmailtools-perl libmime-tools-perl
9566 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
9567 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
9568 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
9569 lirc luatex marble networkstatus noatun-plugins
9570 openoffice.org-writer2latex palapeli palapeli-data parley
9571 parley-data poster psutils pulseaudio pulseaudio-esound-compat
9572 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
9573 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
9575 </p
></blockquote
>
9577 <p
>Installed using apt-get, removed with aptitude
</p
>
9579 <blockquote
><p
>
9580 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
9581 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
9582 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
9583 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
9584 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
9585 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
9586 kitchensync kiten kjumpingcube klatin klettres klickety klines
9587 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
9588 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
9589 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
9590 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
9591 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
9592 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
9593 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
9594 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
9595 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9596 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
9597 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
9598 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9599 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
9600 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
9601 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
9602 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
9603 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9604 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
9605 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
9606 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
9607 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
9608 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
9609 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
9610 mpeglib network-manager-kde noatun pmount tex-common texlive-base
9611 texlive-common texlive-doc-base texlive-fonts-recommended tidy
9612 ttf-dustin ttf-kochi-gothic ttf-sjfonts
9613 </p
></blockquote
>
9615 <p
>Installed using aptitude, missing with apt-get
</p
>
9617 <blockquote
><p
>
9618 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
9619 kdeartwork kdebase kdebase-apps kdebase-workspace
9620 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
9621 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
9622 netpbm plasma-widget-folderview plasma-widget-networkmanagement
9623 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
9624 xscreensaver-screensaver-bsod
9625 </p
></blockquote
>
9627 <p
>Installed using aptitude, removed with apt-get
</p
>
9629 <blockquote
><p
>
9630 kdebase-bin konq-plugins konqueror
9631 </p
></blockquote
>
9636 <title>Gnash buildbot slave and Debian kfreebsd
</title>
9637 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
9638 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
9639 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
9640 <description><p
>Answering
9641 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
9642 call from the Gnash project
</a
> for
9643 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
9644 current source, I have set up a virtual KVM machine on the Debian
9645 Edu/Skolelinux virtualization host to test the git source on
9646 Debian/Squeeze. I hope this can help the developers in getting new
9647 releases out more often.
</p
>
9649 <p
>As the developers want less main-stream build platforms tested to,
9650 I have considered setting up a
<a
9651 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
9652 machine as well. I have also considered using the kfreebsd
9653 architecture in Debian as a file server in NUUG to get access to the
5
9654 TB zfs volume we currently use to store DV video. Because of this, I
9655 finally got around to do a test installation of Debian/Squeeze with
9656 kfreebsd. Installation went fairly smooth, thought I noticed some
9657 visual glitches in the cdebconf dialogs (black cursor left on the
9658 screen at random locations). Have not gotten very far with the
9659 testing. Noticed cfdisk did not work, but fdisk did so it was not a
9660 fatal problem. Have to spend some more time on it to see if it is
9661 useful as a file server for NUUG. Will try to find time to set up a
9662 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
9667 <title>Debian in
3D
</title>
9668 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
9669 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
9670 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
9671 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
9673 <p
>3D printing is just great. I just came across this Debian logo in
9675 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
9676 thingiverse blog
</a
>.
</p
>
9681 <title>Software updates
2010-
10-
24</title>
9682 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
9683 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
9684 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
9685 <description><p
>Some updates.
</p
>
9687 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
9688 raise money for the project is going well. The lower limit of
10
9689 signers was reached in
24 hours, and so far
13 people have signed it.
9690 More signers and more funding is most welcome, and I am really curious
9691 how far we can get before the time limit of December
24 is reached.
9694 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
9695 about what appear to be a great code coverage tool capable of
9696 generating code coverage stats without any changes to the source code.
9698 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
9699 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
9700 It is missing in Debian, but the git source built just fine in Squeeze
9701 after I installed libelf-dev, libdwarf-dev, pkg-config and
9702 libglib2.0-dev. Failed to build in Lenny, but suspect that is
9703 solvable. I hope kcov make it into Debian soon.
</p
>
9705 <p
>Finally found time to wrap up the release notes for
<a
9706 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
9707 new alpha release of Debian Edu
</a
>, and just published the second
9708 alpha test release of the Squeeze based Debian Edu /
9709 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
9710 release. Give it a try if you need a complete linux solution for your
9711 school, including central infrastructure server, workstations, thin
9712 client servers and diskless workstations. A nice touch added
9713 yesterday is RDP support on the thin client servers, for windows
9714 clients to get a Linux desktop on request.
</p
>
9719 <title>Some notes on Flash in Debian and Debian Edu
</title>
9720 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
9721 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
9722 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
9723 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
9724 popularity-contest numbers
</a
>, the adobe-flashplugin package the
9725 second most popular used package that is missing in Debian. The sixth
9726 most popular is flashplayer-mozilla. This is a clear indication that
9727 working flash is important for Debian users. Around
10 percent of the
9728 users submitting data to popcon.debian.org have this package
9729 installed.
</p
>
9731 <p
>In the report written by Lars Risan in August
2008
9732 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
9733 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
9734 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
9735 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
9736 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
9737 web sites require Flash to work, and lacking working Flash support in
9738 the web browser and the problems with installing it was perceived as a
9739 good reason to stay with Windows.
</p
>
9741 <p
>I once saw a funny and sad comment in a web forum, where Linux was
9742 said to be the retarded cousin that did not really understand
9743 everything you told him but could work fairly well. This was a
9744 comment regarding the problems Linux have with proprietary formats and
9745 non-standard web pages, and is sad because it exposes a fairly common
9746 understanding of whose fault it is if web pages that only work in for
9747 example Internet Explorer
6 fail to work on Firefox, and funny because
9748 it explain very well how annoying it is for users when Linux
9749 distributions do not work with the documents they receive or the web
9750 pages they want to visit.
</p
>
9752 <p
>This is part of the reason why I believe it is important for Debian
9753 and Debian Edu to have a well working Flash implementation in the
9754 distribution, to get at least popular sites as Youtube and Google
9755 Video to working out of the box. For Squeeze, Debian have the chance
9756 to include the latest version of Gnash that will make this happen, as
9757 the new release
0.8.8 was published a few weeks ago and is resting in
9758 unstable. The new version work with more sites that version
0.8.7.
9759 The Gnash maintainers have asked for a freeze exception, but the
9760 release team have not had time to reply to it yet. I hope they agree
9761 with me that Flash is important for the Debian desktop users, and thus
9762 accept the new package into Squeeze.
</p
>
9767 <title>Circular package dependencies harms apt recovery
</title>
9768 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
9769 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
9770 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
9771 <description><p
>I discovered this while doing
9772 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
9773 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
9774 in Debian still got circular dependencies, and it is often claimed
9775 that apt and aptitude should be able to handle this just fine, but
9776 some times these dependency loops causes apt to fail.
</p
>
9778 <p
>An example is from todays
9779 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
9780 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
9781 causes perl-modules to fail to upgrade. The cause is simple. If a
9782 package fail to unpack, then only part of packages with the circular
9783 dependency might end up being unpacked when unpacking aborts, and the
9784 ones already unpacked will fail to configure in the recovery phase
9785 because its dependencies are unavailable.
</p
>
9787 <p
>In this log, the problem manifest itself with this error:
</p
>
9789 <blockquote
><pre
>
9790 dpkg: dependency problems prevent configuration of perl-modules:
9791 perl-modules depends on perl (
>=
5.10.1-
1); however:
9792 Version of perl on system is
5.10.0-
19lenny
2.
9793 dpkg: error processing perl-modules (--configure):
9794 dependency problems - leaving unconfigured
9795 </pre
></blockquote
>
9797 <p
>The perl/perl-modules circular dependency is already
9798 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
9799 hopefully be solved as soon as possible, but it is not the only one,
9800 and each one of these loops in the dependency tree can cause similar
9801 failures. Of course, they only occur when there are bugs in other
9802 packages causing the unpacking to fail, but it is rather nasty when
9803 the failure of one package causes the problem to become worse because
9804 of dependency loops.
</p
>
9807 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
9808 tireless effort by Bill Allombert
</a
>, the number of circular
9810 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
9811 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
9813 <p
>Todays testing also exposed a bug in
9814 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
9815 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
9816 apt-get and aptitude, the latter possibly caused by some circular
9817 dependency. Reported both to BTS to try to get someone to look at
9823 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
9824 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
9825 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
9826 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
9827 <description><p
>This is a
9828 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
9830 <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
9832 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
9833 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
9835 <p
>As a step to try to see if it possible to merge the DNS and DHCP
9836 LDAP objects, I have had a look at how the packages pdns-backend-ldap
9837 and dhcp3-server-ldap in Debian use the LDAP server. The two
9838 implementations are quite different in how they use LDAP.
</p
>
9840 To get this information, I started slapd with debugging enabled and
9841 dumped the debug output to a file to get the LDAP searches performed
9842 on a Debian Edu main-server. Here is a summary.
9844 <p
><strong
>powerdns
</strong
></p
>
9846 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
9847 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
9850 <p
>PowerDNS have two modes of operation using LDAP as its backend.
9851 One
"strict
" mode where the forward and reverse DNS lookups are done
9852 using the same LDAP objects, and a
"tree
" mode where the forward and
9853 reverse entries are in two different subtrees in LDAP with a structure
9854 based on the DNS names, as in tjener.intern and
9855 2.2.0.10.in-addr.arpa.
</p
>
9857 <p
>In tree mode, the server is set up to use a LDAP subtree as its
9858 base, and uses a
"base
" scoped search for the DNS name by adding
9859 "dc=tjener,dc=intern,
" to the base with a filter for
9860 "(associateddomain=tjener.intern)
" for the forward entry and
9861 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
9862 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
9863 forward entries, it is looking for attributes named dnsttl, arecord,
9864 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
9865 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
9866 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
9867 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
9868 spfrecord and modifytimestamp. For reverse entries it is looking for
9869 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
9870 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
9871 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
9872 ldapsearch commands could look like this:
</p
>
9874 <blockquote
><pre
>
9875 ldapsearch -h ldap \
9876 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9877 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9878 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9879 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9880 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9881 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9883 ldapsearch -h ldap \
9884 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
9885 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
9886 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
9887 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
9888 srvrecord naptrrecord modifytimestamp
9889 </pre
></blockquote
>
9891 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
9892 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
9893 example LDAP objects used there. In addition to these objects, the
9894 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
9895 also exist.
</p
>
9897 <blockquote
><pre
>
9898 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
9900 objectclass: dnsdomain
9901 objectclass: domainrelatedobject
9904 associateddomain: tjener.intern
9906 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
9908 objectclass: dnsdomain2
9909 objectclass: domainrelatedobject
9911 ptrrecord: tjener.intern
9912 associateddomain:
2.2.0.10.in-addr.arpa
9913 </pre
></blockquote
>
9915 <p
>In strict mode, the server behaves differently. When looking for
9916 forward DNS entries, it is doing a
"subtree
" scoped search with the
9917 same base as in the tree mode for a object with filter
9918 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
9919 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
9920 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
9921 naptrrecord and modifytimestamp. For reverse entires it also do a
9922 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
9923 and the requested attributes are associateddomain, dnsttl and
9924 modifytimestamp. In short, in strict mode the objects with ptrrecord
9925 go away, and the arecord attribute in the forward object is used
9928 <p
>The forward and reverse searches can be simulated using ldapsearch
9929 like this:
</p
>
9931 <blockquote
><pre
>
9932 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9933 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
9934 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
9935 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
9936 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
9937 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
9939 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
9940 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
9941 </pre
></blockquote
>
9943 <p
>In addition to the forward and reverse searches , there is also a
9944 search for SOA records, which behave similar to the forward and
9945 reverse lookups.
</p
>
9947 <p
>A thing to note with the PowerDNS behaviour is that it do not
9948 specify any objectclass names, and instead look for the attributes it
9949 need to generate a DNS reply. This make it able to work with any
9950 objectclass that provide the needed attributes.
</p
>
9952 <p
>The attributes are normally provided in the cosine (RFC
1274) and
9953 dnsdomain2 schemas. The latter is used for reverse entries like
9954 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
9956 <p
>In Debian Edu, we have created DNS objects using the object classes
9957 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
9958 attributes) and domainrelatedobject (for associatedDomain). The use
9959 of structural object classes make it impossible to combine these
9960 classes with the object classes used by DHCP.
</p
>
9962 <p
>There are other schemas that could be used too, for example the
9963 dnszone structural object class used by Gosa and bind-sdb for the DNS
9964 attributes combined with the domainrelatedobject object class, but in
9965 this case some unused attributes would have to be included as well
9966 (zonename and relativedomainname).
</p
>
9968 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
9969 mode and not use any of the existing objectclasses (dnsdomain,
9970 dnsdomain2 and dnszone) when one want to combine the DNS information
9971 with DHCP information, and instead create a auxiliary object class
9972 defined something like this (using the attributes defined for
9973 dnsdomain and dnsdomain2 or dnszone):
</p
>
9975 <blockquote
><pre
>
9976 objectclass ( some-oid NAME
'dnsDomainAux
'
9979 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
9980 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
9981 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
9982 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
9983 A6Record $ DNAMERecord
9985 </pre
></blockquote
>
9987 <p
>This will allow any object to become a DNS entry when combined with
9988 the domainrelatedobject object class, and allow any entity to include
9989 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
9990 developers asking for their view on this schema and if they are
9991 interested in providing such schema with PowerDNS, and I hope my
9992 message will be accepted into their mailing list soon.
</p
>
9994 <p
><strong
>ISC dhcp
</strong
></p
>
9996 <p
>The DHCP server searches for specific objectclass and requests all
9997 the object attributes, and then uses the attributes it want. This
9998 make it harder to figure out exactly what attributes are used, but
9999 thanks to the working example in Debian Edu I can at least get an idea
10000 what is needed without having to read the source code.
</p
>
10002 <p
>In the DHCP server configuration, the LDAP base to use and the
10003 search filter to use to locate the correct dhcpServer entity is
10004 stored. These are the relevant entries from
10005 /etc/dhcp3/dhcpd.conf:
</p
>
10007 <blockquote
><pre
>
10008 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
10009 ldap-dhcp-server-cn
"dhcp
";
10010 </pre
></blockquote
>
10012 <p
>The DHCP server uses this information to nest all the DHCP
10013 configuration it need. The cn
"dhcp
" is located using the given LDAP
10014 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
10015 search result is this entry:
</p
>
10017 <blockquote
><pre
>
10018 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
10021 objectClass: dhcpServer
10022 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10023 </pre
></blockquote
>
10025 <p
>The content of the dhcpServiceDN attribute is next used to locate the
10026 subtree with DHCP configuration. The DHCP configuration subtree base
10027 is located using a base scope search with base
"cn=DHCP
10028 Config,dc=skole,dc=skolelinux,dc=no
" and filter
10029 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
10030 The search result is this entry:
</p
>
10032 <blockquote
><pre
>
10033 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10036 objectClass: dhcpService
10037 objectClass: dhcpOptions
10038 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
10039 dhcpStatements: ddns-update-style none
10040 dhcpStatements: authoritative
10041 dhcpOption: smtp-server code
69 = array of ip-address
10042 dhcpOption: www-server code
72 = array of ip-address
10043 dhcpOption: wpad-url code
252 = text
10044 </pre
></blockquote
>
10046 <p
>Next, the entire subtree is processed, one level at the time. When
10047 all the DHCP configuration is loaded, it is ready to receive requests.
10048 The subtree in Debian Edu contain objects with object classes
10049 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
10050 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
10051 and information about netmasks, dynamic range etc. Leaving out the
10052 details here because it is not relevant for the focus of my
10053 investigation, which is to see if it is possible to merge dns and dhcp
10054 related computer objects.
</p
>
10056 <p
>When a DHCP request come in, LDAP is searched for the MAC address
10057 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
10058 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
10059 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
10060 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
10063 <blockquote
><pre
>
10064 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10067 objectClass: dhcpHost
10068 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
10069 dhcpStatements: fixed-address hostname
10070 </pre
></blockquote
>
10072 <p
>There is less flexiblity in the way LDAP searches are done here.
10073 The object classes need to have fixed names, and the configuration
10074 need to be stored in a fairly specific LDAP structure. On the
10075 positive side, the invidiual dhcpHost entires can be anywhere without
10076 the DN pointed to by the dhcpServer entries. The latter should make
10077 it possible to group all host entries in a subtree next to the
10078 configuration entries, and this subtree can also be shared with the
10079 DNS server if the schema proposed above is combined with the dhcpHost
10080 structural object class.
10082 <p
><strong
>Conclusion
</strong
></p
>
10084 <p
>The PowerDNS implementation seem to be very flexible when it come
10085 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
10086 come to the the LDAP structure, the
"strict
" mode is very flexible,
10087 allowing DNS objects to be stored anywhere under the base cn specified
10088 in the configuration.
</p
>
10090 <p
>The DHCP implementation on the other hand is very inflexible, both
10091 regarding which LDAP schemas to use and which LDAP structure to use.
10092 I guess one could implement ones own schema, as long as the
10093 objectclasses and attributes have the names used, but this do not
10094 really help when the DHCP subtree need to have a fairly fixed
10095 structure.
</p
>
10097 <p
>Based on the observed behaviour, I suspect a LDAP structure like
10098 this might work for Debian Edu:
</p
>
10100 <blockquote
><pre
>
10102 cn=machine-info (dhcpService) - dhcpServiceDN points here
10103 cn=dhcp (dhcpServer)
10104 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
10105 cn=
10.0.2.0 (dhcpSubnet)
10106 cn=group1 (dhcpGroup/dhcpOptions)
10107 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
10108 cn=
192.168.0.0 (dhcpSubnet)
10109 cn=group1 (dhcpGroup/dhcpOptions)
10110 ou=machines - PowerDNS base points here
10111 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
10112 </pre
></blockquote
>
10114 <P
>This is not tested yet. If the DHCP server require the dhcpHost
10115 entries to be in the dhcpGroup subtrees, the entries can be stored
10116 there instead of a common machines subtree, and the PowerDNS base
10117 would have to be moved one level up to the machine-info subtree.
</p
>
10119 <p
>The combined object under the machines subtree would look something
10120 like this:
</p
>
10122 <blockquote
><pre
>
10123 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
10126 objectClass: dhcpHost
10127 objectclass: domainrelatedobject
10128 objectclass: dnsDomainAux
10129 associateddomain: hostname.intern
10130 arecord:
10.11.12.13
10131 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
10132 dhcpStatements: fixed-address hostname.intern
10133 </pre
></blockquote
>
10135 </p
>One could even add the LTSP configuration associated with a given
10136 machine, as long as the required attributes are available in a
10137 auxiliary object class.
</p
>
10142 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
10143 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
10144 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
10145 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
10146 <description><p
>For a while now, I have wanted to find a way to change the DNS and
10147 DHCP services in Debian Edu to use the same LDAP objects for a given
10148 computer, to avoid the possibility of having a inconsistent state for
10149 a computer in LDAP (as in DHCP but no DNS entry or the other way
10150 around) and make it easier to add computers to LDAP.
</p
>
10152 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
10153 information finally found a solution that seem to work.
</p
>
10155 <p
>The old setup required three LDAP objects for a given computer.
10156 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
10157 we switch powerdns to use its strict LDAP method (ldap-method=strict
10158 in pdns-debian-edu.conf), the forward and reverse DNS entries are
10159 merged into one while making it impossible to transfer the reverse map
10160 to a slave DNS server.
</p
>
10162 <p
>If we also replace the object class used to get the DNS related
10163 attributes to one allowing these attributes to be combined with the
10164 dhcphost object class, we can merge the DNS and DHCP entries into one.
10165 I
've written such object class in the dnsdomainaux.schema file (need
10166 proper OIDs, but that is a minor issue), and tested the setup. It
10167 seem to work.
</p
>
10169 <p
>With this test setup in place, we can get away with one LDAP object
10170 for both DNS and DHCP, and even the LTSP configuration I suggested in
10171 an earlier email. The combined LDAP object will look something like
10174 <blockquote
><pre
>
10175 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10177 objectClass: dhcphost
10178 objectclass: domainrelatedobject
10179 objectclass: dnsdomainaux
10180 associateddomain: hostname.intern
10181 arecord:
10.11.12.13
10182 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
10183 dhcpstatements: fixed-address hostname
10185 </pre
></blockquote
>
10187 <p
>The DNS server uses the associateddomain and arecord entries, while
10188 the DHCP server uses the dhcphwaddress and dhcpstatements entries
10189 before asking DNS to resolve the fixed-adddress. LTSP will use
10190 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
10192 <p
>I am not yet sure if I can get the DHCP server to look for its
10193 dhcphost in a different location, to allow us to put the objects
10194 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
10195 that. If I can
't figure out a way to do that, we can still get rid of
10196 the hosts subtree and move all its content into the DHCP Config tree
10197 (which probably should be renamed to be more related to the new
10198 content. I suspect cn=dnsdhcp,ou=services or something like that
10199 might be a good place to put it.
</p
>
10201 <p
>If you want to help out with implementing this for Debian Edu,
10202 please contact us on debian-edu@lists.debian.org.
</p
>
10207 <title>Idea for storing LTSP configuration in LDAP
</title>
10208 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
10209 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
10210 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
10211 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
10212 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
10213 clients, and that this can be used to fetch configuration from LDAP if
10214 Debian Edu choose to store configuration there.
</p
>
10216 <p
>Armed with this information, I got inspired and wrote a test module
10217 to get configuration from LDAP. The idea is to look up the MAC
10218 address of the client in LDAP, and look for attributes on the form
10219 ltspconfigsetting=value, and use this to export SETTING=value to the
10220 LTSP clients.
</p
>
10222 <p
>The goal is to be able to store the LTSP configuration attributes
10223 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
10224 allowing us to store all information about a computer in one place.
</p
>
10226 <p
>This is a untested draft implementation, and I welcome feedback on
10227 this approach. A real LDAP schema for the ltspClientAux objectclass
10228 need to be written. Comments, suggestions, etc?
</p
>
10230 <blockquote
><pre
>
10231 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
10233 # Fetch LTSP client settings from LDAP based on MAC address
10235 # Uses ethernet address as stored in the dhcpHost objectclass using
10236 # the dhcpHWAddress attribute or ethernet address stored in the
10237 # ieee802Device objectclass with the macAddress attribute.
10239 # This module is written to be schema agnostic, and only depend on the
10240 # existence of attribute names.
10242 # The LTSP configuration variables are saved directly using a
10243 # ltspConfig prefix and uppercasing the rest of the attribute name.
10244 # To set the SERVER variable, set the ltspConfigServer attribute.
10246 # Some LDAP schema should be created with all the relevant
10247 # configuration settings. Something like this should work:
10249 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
10252 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
10254 LDAPSERVER=$(debian-edu-ldapserver)
10255 if [
"$LDAPSERVER
" ] ; then
10256 LDAPBASE=$(debian-edu-ldapserver -b)
10257 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
10258 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
10259 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
10260 grep
'^ltspConfig
' | while read attr value ; do
10261 # Remove prefix and convert to upper case
10262 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
10263 # bass value on to clients
10264 eval
"$attr=$value; export $attr
"
10268 </pre
></blockquote
>
10270 <p
>I
'm not sure this shell construction will work, because I suspect
10271 the while block might end up in a subshell causing the variables set
10272 there to not show up in ltsp-config, but if that is the case I am sure
10273 the code can be restructured to make sure the variables are passed on.
10274 I expect that can be solved with some testing. :)
</p
>
10276 <p
>If you want to help out with implementing this for Debian Edu,
10277 please contact us on debian-edu@lists.debian.org.
</p
>
10279 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
10280 configuration in LDAP that was created around year
2000 by
10281 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
10282 Xperience, Inc.,
2000</a
>. I found its
10283 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
10284 personal home page over at redhat.com.
</p
>
10289 <title>jXplorer, a very nice LDAP GUI
</title>
10290 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
10291 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
10292 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
10293 <description><p
>Since
10294 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
10295 last post
</a
> about available LDAP tools in Debian, I was told about a
10296 LDAP GUI that is even better than luma. The java application
10297 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
10298 moving LDAP objects and subtrees using drag-and-drop, and can
10299 authenticate using Kerberos. I have only tested the Kerberos
10300 authentication, but do not have a LDAP setup allowing me to rewrite
10301 LDAP with my test user yet. It is
10302 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
10303 Debian
</a
> testing and unstable at the moment. The only problem I
10304 have with it is how it handle errors. If something go wrong, its
10305 non-intuitive behaviour require me to go through some query work list
10306 and remove the failing query. Nothing big, but very annoying.
</p
>
10311 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
10312 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
10313 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
10314 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
10315 <description><p
>Here is a short update on my
<a
10316 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
10317 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
10318 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
10319 not reporting the status for KDE, because the upgrade crashes when
10320 aptitude try because of missing conflicts
10321 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
10322 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
10324 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
10325 complete list of the installed packages. Based on this I see these
10326 differences when I did a test run today. As usual, I do not really
10327 know what the correct set of packages would be, but thought it best to
10328 publish the difference.
</p
>
10330 <p
>Installed using apt-get, missing with aptitude
</p
>
10332 <blockquote
><p
>
10333 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
10334 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
10335 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
10336 libgtksourceview-common libpt-
1.10.10-plugins-alsa
10337 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
10338 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
10339 python-
4suite-xml python-eggtrayicon python-gtkhtml2
10340 python-gtkmozembed svgalibg1 xserver-xephyr zip
10341 </p
></blockquote
>
10343 <p
>Installed using apt-get, removed with aptitude
</p
>
10345 <blockquote
><p
>
10346 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
10347 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
10348 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
10349 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
10350 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
10351 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
10352 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
10353 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
10354 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
10355 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
10356 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
10357 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
10358 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
10359 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
10360 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
10361 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
10362 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
10363 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
10364 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
10365 mysql-common swfdec-gnome totem-gstreamer wodim
10366 </p
></blockquote
>
10368 <p
>Installed using aptitude, missing with apt-get
</p
>
10370 <blockquote
><p
>
10371 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
10372 python-gnomekeyring python-wnck rhythmbox-plugins xorg
10373 xserver-xorg-input-all xserver-xorg-input-evdev
10374 xserver-xorg-input-kbd xserver-xorg-input-mouse
10375 xserver-xorg-input-synaptics xserver-xorg-video-all
10376 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
10377 xserver-xorg-video-chips xserver-xorg-video-cirrus
10378 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10379 xserver-xorg-video-glint xserver-xorg-video-i128
10380 xserver-xorg-video-i740 xserver-xorg-video-mach64
10381 xserver-xorg-video-mga xserver-xorg-video-neomagic
10382 xserver-xorg-video-nouveau xserver-xorg-video-nv
10383 xserver-xorg-video-r128 xserver-xorg-video-radeon
10384 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
10385 xserver-xorg-video-s3 xserver-xorg-video-s3virge
10386 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
10387 xserver-xorg-video-sis xserver-xorg-video-sisusb
10388 xserver-xorg-video-tdfx xserver-xorg-video-tga
10389 xserver-xorg-video-trident xserver-xorg-video-tseng
10390 xserver-xorg-video-vesa xserver-xorg-video-vmware
10391 xserver-xorg-video-voodoo
10392 </p
></blockquote
>
10394 <p
>Installed using aptitude, removed with apt-get
</p
>
10396 <blockquote
><p
>
10397 deskbar-applet xserver-xorg xserver-xorg-core
10398 xserver-xorg-input-wacom xserver-xorg-video-intel
10399 xserver-xorg-video-openchrome
10400 </p
></blockquote
>
10402 <p
>I was told on IRC that the xorg-xserver package was
10403 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
10404 in git
</a
> today to try to get apt-get to not remove xorg completely.
10405 No idea when it hits Squeeze, but when it does I hope it will reduce
10406 the difference somewhat.
10411 <title>LUMA, a very nice LDAP GUI
</title>
10412 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
10413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
10414 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
10415 <description><p
>The last few days I have been looking into the status of the LDAP
10416 directory in Debian Edu, and in the process I started to miss a GUI
10417 tool to browse the LDAP tree. The only one I was able to find in
10418 Debian/Squeeze and Lenny is
10419 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
10420 be a great tool to get a overview of the current LDAP directory
10421 populated by default in Skolelinux. Thanks to it, I have been able to
10422 find empty and obsolete subtrees, misplaced objects and duplicate
10423 objects. It will be installed by default in Debian/Squeeze. If you
10424 are working with LDAP, give it a go. :)
</p
>
10426 <p
>I did notice one problem with it I have not had time to report to
10427 the BTS yet. There is no .desktop file in the package, so the tool do
10428 not show up in the Gnome and KDE menus, but only deep down in in the
10429 Debian submenu in KDE. I hope that can be fixed before Squeeze is
10430 released.
</p
>
10432 <p
>I have not yet been able to get it to modify the tree yet. I would
10433 like to move objects and remove subtrees directly in the GUI, but have
10434 not found a way to do that with LUMA yet. So in the mean time, I use
10435 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
10437 <p
>If you have tips on other GUI tools for LDAP that might be useful
10438 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
10440 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
10441 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
10442 useful GUI alternative. It seem like a good tool, but is unmaintained
10443 in Debian and got a RC bug keeping it out of Squeeze. Unless that
10444 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
10449 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
10450 <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>
10451 <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>
10452 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
10453 <description><p
>A while back, I
10454 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
10455 about the fact
</a
> that it is not possible with the provided schemas
10456 for storing DNS and DHCP information in LDAP to combine the two sets
10457 of information into one LDAP object representing a computer.
</p
>
10459 <p
>In the mean time, I discovered that a simple fix would be to make
10460 the dhcpHost object class auxiliary, to allow it to be combined with
10461 the dNSDomain object class, and thus forming one object for one
10462 computer when storing both DHCP and DNS information in LDAP.
</p
>
10464 <p
>If I understand this correctly, it is not safe to do this change
10465 without also changing the assigned number for the object class, and I
10466 do not know enough about LDAP schema design to do that properly for
10467 Debian Edu.
</p
>
10469 <p
>Anyway, for future reference, this is how I believe we could change
10471 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
10472 schema
</a
> to solve at least part of the problem with the LDAP schemas
10473 available today from IETF.
</p
>
10476 --- dhcp.schema (revision
65192)
10477 +++ dhcp.schema (working copy)
10478 @@ -
376,
7 +
376,
7 @@
10479 objectclass (
2.16.840.1.113719.1.203.6.6
10480 NAME
'dhcpHost
'
10481 DESC
'This represents information about a particular client
'
10483 + SUP top AUXILIARY
10485 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
10486 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
10489 <p
>I very much welcome clues on how to do this properly for Debian
10490 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
10491 package, and should thus be free to rewrite it as we see fit.
</p
>
10493 <p
>If you want to help out with implementing this for Debian Edu,
10494 please contact us on debian-edu@lists.debian.org.
</p
>
10499 <title>Calling tasksel like the installer, while still getting useful output
</title>
10500 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
10501 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
10502 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
10503 <description><p
>A few times I have had the need to simulate the way tasksel
10504 installs packages during the normal debian-installer run. Until now,
10505 I have ended up letting tasksel do the work, with the annoying problem
10506 of not getting any feedback at all when something fails (like a
10507 conffile question from dpkg or a download that fails), using code like
10510 <blockquote
><pre
>
10511 export DEBIAN_FRONTEND=noninteractive
10512 tasksel --new-install
10513 </pre
></blockquote
>
10515 This would invoke tasksel, let its automatic task selection pick the
10516 tasks to install, and continue to install the requested tasks without
10517 any output what so ever.
10519 Recently I revisited this problem while working on the automatic
10520 package upgrade testing, because tasksel would some times hang without
10521 any useful feedback, and I want to see what is going on when it
10522 happen. Then it occured to me, I can parse the output from tasksel
10523 when asked to run in test mode, and use that aptitude command line
10524 printed by tasksel then to simulate the tasksel run. I ended up using
10527 <blockquote
><pre
>
10528 export DEBIAN_FRONTEND=noninteractive
10529 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
10531 </pre
></blockquote
>
10533 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
10534 --without-recommends -o APT::Install-Recommends=no -y install
10535 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
10536 ~pimportant
</tt
>", which will install the gnome desktop task, the
10537 laptop task and all packages with priority standard , required and
10538 important, just like tasksel would have done it during
10539 installation.
</p
>
10541 <p
>A better approach is probably to extend tasksel to be able to
10542 install packages without using debconf-apt-progress, for use cases
10543 like this.
</p
>
10548 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
10549 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
10550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
10551 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
10552 <description><p
>My
10553 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
10554 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
10555 finally made the upgrade logs available from
10556 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
10557 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
10558 apt and aptitude, and found their differences interesting. This time
10559 I will only focus on their removal plans.
</p
>
10561 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
10562 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
10563 surprising part is that it want to remove xorg and all
10564 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
10565 sure why. When asking aptitude to do the same, it want to remove
129
10566 packages, but most of them are library packages I suspect are no
10567 longer needed. Both of them want to remove bluetooth packages, which
10568 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
10570 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
10571 which seem like a bad idea and xorg the same way as with Gnome. Asking
10572 aptitude for the same, it wants to remove
192 packages, none which are
10573 too surprising.
</p
>
10575 <p
>I guess the removal of xorg during upgrades should be investigated
10576 and avoided, and perhaps others as well. Here are the complete list
10577 of planned removals. The complete logs is available from the URL
10578 above. Note if you want to repeat these tests, that the upgrade test
10579 for kde+apt-get hung in the tasksel setup because of dpkg asking
10580 conffile questions. No idea why. I worked around it by using
10581 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
10582 continue.
</p
>
10584 <p
><b
>apt-get gnome
72</b
>
10585 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
10586 gnome-desktop-environment gnome-network-admin gtkhtml3.14
10587 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
10588 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
10589 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
10590 serpentine swfdec-mozilla update-manager xorg xserver-xorg
10591 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10592 xserver-xorg-input-kbd xserver-xorg-input-mouse
10593 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10594 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10595 xserver-xorg-video-ati xserver-xorg-video-chips
10596 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10597 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10598 xserver-xorg-video-glint xserver-xorg-video-i128
10599 xserver-xorg-video-i740 xserver-xorg-video-imstt
10600 xserver-xorg-video-intel xserver-xorg-video-mach64
10601 xserver-xorg-video-mga xserver-xorg-video-neomagic
10602 xserver-xorg-video-nsc xserver-xorg-video-nv
10603 xserver-xorg-video-openchrome xserver-xorg-video-r128
10604 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10605 xserver-xorg-video-rendition xserver-xorg-video-s3
10606 xserver-xorg-video-s3virge xserver-xorg-video-savage
10607 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10608 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10609 xserver-xorg-video-tga xserver-xorg-video-trident
10610 xserver-xorg-video-tseng xserver-xorg-video-v4l
10611 xserver-xorg-video-vesa xserver-xorg-video-vga
10612 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
10613 xulrunner-
1.9-gnome-support
</p
>
10615 <p
><b
>aptitude gnome
129</b
>
10617 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
10618 djvulibre-desktop finger gnome-app-install gnome-mount
10619 gnome-network-admin gnome-spell gnome-vfs-obexftp
10620 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
10621 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
10622 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
10623 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
10624 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
10625 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
10626 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
10627 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
10628 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
10629 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
10630 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
10631 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
10632 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
10633 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
10634 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
10635 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
10636 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
10637 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
10638 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
10639 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
10640 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
10641 openoffice.org-writer2latex openssl-blacklist p7zip
10642 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
10643 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
10644 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
10645 swfdec-mozilla totem-gstreamer update-manager wodim
10646 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10647 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10650 <p
><b
>apt-get kde
82</b
>
10652 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
10653 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
10654 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
10655 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
10656 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
10657 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
10658 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
10659 xserver-xorg-input-kbd xserver-xorg-input-mouse
10660 xserver-xorg-input-synaptics xserver-xorg-input-wacom
10661 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
10662 xserver-xorg-video-ati xserver-xorg-video-chips
10663 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
10664 xserver-xorg-video-dummy xserver-xorg-video-fbdev
10665 xserver-xorg-video-glint xserver-xorg-video-i128
10666 xserver-xorg-video-i740 xserver-xorg-video-imstt
10667 xserver-xorg-video-intel xserver-xorg-video-mach64
10668 xserver-xorg-video-mga xserver-xorg-video-neomagic
10669 xserver-xorg-video-nsc xserver-xorg-video-nv
10670 xserver-xorg-video-openchrome xserver-xorg-video-r128
10671 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
10672 xserver-xorg-video-rendition xserver-xorg-video-s3
10673 xserver-xorg-video-s3virge xserver-xorg-video-savage
10674 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
10675 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
10676 xserver-xorg-video-tga xserver-xorg-video-trident
10677 xserver-xorg-video-tseng xserver-xorg-video-v4l
10678 xserver-xorg-video-vesa xserver-xorg-video-vga
10679 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
10681 <p
><b
>aptitude kde
192</b
>
10682 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
10683 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
10684 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
10685 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
10686 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10687 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
10688 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
10689 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10690 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
10691 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
10692 kghostview khelpcenter khexedit kiconedit kitchensync klatin
10693 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
10694 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
10695 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
10696 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
10697 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
10698 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
10699 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10700 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
10701 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
10702 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10703 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
10704 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
10705 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
10706 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10707 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
10708 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
10709 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
10710 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
10711 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
10712 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
10713 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
10714 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
10715 texlive-common texlive-doc-base texlive-fonts-recommended
10716 xserver-xorg-video-cyrix xserver-xorg-video-imstt
10717 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
10718 xulrunner-
1.9</p
>
10724 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
10725 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
10726 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
10727 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
10728 <description><p
>The last few days I have done some upgrade testing in Debian, to
10729 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
10730 have been discovered and reported in the process
10731 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
10732 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
10733 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
10734 kdebase-workspace-data), and to get a more regular testing going on, I
10735 am working on a script to automate the test.
</p
>
10737 <p
>The idea is to create a Lenny chroot and use tasksel to install a
10738 Gnome or KDE desktop installation inside the chroot before upgrading
10739 it. To ensure no services are started in the chroot, a policy-rc.d
10740 script is inserted. To make sure tasksel believe it is to install a
10741 desktop on a laptop, the tasksel tests are replaced in the chroot
10742 (only acceptable because this is a throw-away chroot).
</p
>
10744 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
10745 currently always fail because udev refuses to upgrade with the kernel
10746 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
10747 is created. The bug report
10748 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
10749 this problem do not trigger in a chroot, but I touch the file anyway
10750 to make sure the upgrade go well. Testing on virtual and real
10751 hardware have failed me because of udev so far, and creating this file
10752 do the trick in such settings anyway. This is a
10753 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
10754 issue
</a
> and the current udev behaviour is intended by the udev
10755 maintainer because he lack the resources to rewrite udev to keep
10756 working with old kernels or something like that. I really wish the
10757 udev upstream would keep udev backwards compatible, to avoid such
10758 upgrade problem, but given that they fail to do so, I guess
10759 documenting the way out of this mess is the best option we got for
10760 Debian Squeeze.
</p
>
10762 <p
>Anyway, back to the task at hand, testing upgrades. This test
10763 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
10766 <blockquote
><pre
>
10770 if [
"$
1" ] ; then
10779 exec
&lt; /dev/null
10781 mirror=http://ftp.skolelinux.org/debian
10782 tmpdir=chroot-$from-upgrade-$to-$desktop
10784 debootstrap $from $tmpdir $mirror
10785 chroot $tmpdir aptitude update
10786 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
10790 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
10792 umount $tmpdir/proc
10794 mount -t proc proc $tmpdir/proc
10795 # Make sure proc is unmounted also on failure
10796 trap exit_cleanup EXIT INT
10798 chroot $tmpdir aptitude -y install debconf-utils
10800 # Make sure tasksel autoselection trigger. It need the test scripts
10801 # to return the correct answers.
10802 echo tasksel tasksel/desktop multiselect $desktop | \
10803 chroot $tmpdir debconf-set-selections
10805 # Include the desktop and laptop task
10806 for test in desktop laptop ; do
10807 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
10811 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
10814 DEBIAN_FRONTEND=noninteractive
10815 DEBIAN_PRIORITY=critical
10816 export DEBIAN_FRONTEND DEBIAN_PRIORITY
10817 chroot $tmpdir tasksel --new-install
10819 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
10820 chroot $tmpdir aptitude update
10821 touch $tmpdir/etc/udev/kernel-upgrade
10822 chroot $tmpdir aptitude -y dist-upgrade
10824 </pre
></blockquote
>
10826 <p
>I suspect it would be useful to test upgrades with both apt-get and
10827 with aptitude, but I have not had time to look at how they behave
10828 differently so far. I hope to get a cron job running to do the test
10829 regularly and post the result on the web. The Gnome upgrade currently
10830 work, while the KDE upgrade fail because of the bug in
10831 kdebase-workspace-data
</p
>
10833 <p
>I am not quite sure what kind of extract from the huge upgrade logs
10834 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
10835 post, so I will refrain from trying. I can report that for Gnome,
10836 aptitude report
760 packages upgraded,
448 newly installed,
129 to
10837 remove and
1 not upgraded and
1024MB need to be downloaded while for
10838 KDE the same numbers are
702 packages upgraded,
507 newly installed,
10839 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
10841 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
10842 is able to migrate to dependency based boot sequencing and parallel
10843 booting without a hitch. Was unsure if there were still bugs with
10844 packages failing to clean up their obsolete init.d script during
10845 upgrades, and no such problem seem to affect the Gnome desktop+laptop
10846 packages.
</p
>
10851 <title>Upstart or sysvinit - as init.d scripts see it
</title>
10852 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
10853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
10854 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
10855 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
10856 scripts to migrate (some of) their operations to upstart job while
10857 keeping the init.d for hurd and kfreebsd. The packages with such
10858 needs will need a way to get their init.d scripts to behave
10859 differently when used with sysvinit and with upstart. Because of
10860 this, I had a look at the environment variables set when a init.d
10861 script is running under upstart, and when it is not.
</p
>
10863 <p
>With upstart, I notice these environment variables are set when a
10864 script is started from rcS.d/ (ignoring some irrelevant ones like
10865 COLUMNS):
</p
>
10867 <blockquote
><pre
>
10873 UPSTART_EVENTS=startup
10875 UPSTART_JOB=rc-sysinit
10876 </pre
></blockquote
>
10878 <p
>With sysvinit, these environment variables are set for the same
10881 <blockquote
><pre
>
10882 INIT_VERSION=sysvinit-
2.88
10887 </pre
></blockquote
>
10889 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
10890 sysvinit are not set by upstart. Not sure if it is intentional or not
10891 to not be compatible with sysvinit in this regard.
</p
>
10893 <p
>For scripts needing to behave differently when upstart is used,
10894 looking for the UPSTART_JOB environment variable seem to be a good
10900 <title>A manual for standards wars...
</title>
10901 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
10902 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
10903 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
10904 <description><p
>Via the
10905 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
10906 of Rob Weir
</a
> I came across the very interesting essay named
10907 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
10908 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
10909 following the standards wars of today.
</p
>
10914 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
10915 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
10916 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
10917 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
10918 <description><p
>When using sitesummary at a site to track machines, it is possible
10919 to get a list of the machine types in use thanks to the DMI
10920 information extracted from each machine. The script to do so is
10921 included in the sitesummary package, and here is example output from
10922 the Skolelinux build servers:
</p
>
10924 <blockquote
><pre
>
10925 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
10927 Dell Computer Corporation
1
10930 eserver xSeries
345 -[
8670M1X]-
1
10934 </pre
></blockquote
>
10936 <p
>The quality of the report depend on the quality of the DMI tables
10937 provided in each machine. Here there are Intel machines without model
10938 information listed with Intel as vendor and no model, and virtual Xen
10939 machines listed as [no-dmi-info]. One can add -l as a command line
10940 option to list the individual machines.
</p
>
10942 <p
>A larger list is
10943 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
10944 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
10945 provide the basic sitesummary report publicly. In their report there
10946 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
10947 their machines, and as sitesummary is available in both distributions,
10948 it is trivial to get all of them to report to the same central
10949 collector.
</p
>
10954 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
10955 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
10956 <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>
10957 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
10958 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
10959 start at boot when an NVidia video card is used is handled. The
10960 problem seem to be that the nvidia X.org driver uses a long time to
10961 initialize, and this duration is longer than kdm is configured to
10964 <p
>I came across two bugs related to this issue,
10965 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
10966 against initscripts and passed on to nvidia-glx when it became obvious
10967 that the nvidia drivers were involved, and
10968 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
10969 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
10971 <p
>To me, it seem that no-one is interested in actually solving the
10972 problem nvidia video card owners experience and make sure the Debian
10973 distribution work out of the box for these users. The nvidia driver
10974 maintainers expect kdm to be set up to wait longer, while kdm expect
10975 the nvidia driver maintainers to fix the driver to start faster, and
10976 while they wait for each other I guess the users end up switching to a
10977 distribution that work for them. I have no idea what the solution is,
10978 but I am pretty sure that waiting for each other is not it.
</p
>
10980 <p
>I wonder why we end up handling bugs this way.
</p
>
10985 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
10986 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
10987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
10988 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
10989 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
10990 The feature seem to hold up pretty well, but three fairly serious
10991 issues are known and should be solved:
10993 <p
><ul
>
10995 <li
>The wicd package seen to
10996 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
10997 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
10998 parallel booting is enabled. No idea why, but the wicd maintainer
10999 seem to be on the case.
</li
>
11001 <li
>The nvidia X driver seem to
11002 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
11003 triggered more easily when parallel booting is in effect. The
11004 maintainer is on the case.
</li
>
11006 <li
>The sysv-rc package fail to properly enable dependency based boot
11007 sequencing (the shutdown is broken) when old file-rc users
11008 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
11009 sysv-rc. One way to solve it would be for file-rc to create
11010 /etc/init.d/.legacy-bootordering, and another is to try to make
11011 sysv-rc more robust. Will investigate some more and probably upload a
11012 workaround in sysv-rc to help those trying to move from file-rc to
11013 sysv-rc get a working shutdown.
</li
>
11015 </ul
></p
>
11017 <p
>All in all not many surprising issues, and all of them seem
11018 solvable before Squeeze is released. In addition to these there are
11019 some packages with bugs in their dependencies and run level settings,
11020 which I expect will be fixed in a reasonable time span.
</p
>
11022 <p
>If you report any problems with dependencies in init.d scripts to
11023 the BTS, please usertag the report to get it to show up at
11024 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
11025 list of usertagged bugs related to this
</a
>.
</p
>
11027 <p
>Update: Correct bug number to file-rc issue.
</p
>
11032 <title>More flexible firmware handling in debian-installer
</title>
11033 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
11034 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
11035 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
11036 <description><p
>After a long break from debian-installer development, I finally
11037 found time today to return to the project. Having to spend less time
11038 working dependency based boot in debian, as it is almost complete now,
11039 definitely helped freeing some time.
</p
>
11041 <p
>A while back, I ran into a problem while working on Debian Edu. We
11042 include some firmware packages on the Debian Edu CDs, those needed to
11043 get disk and network controllers working. Without having these
11044 firmware packages available during installation, it is impossible to
11045 install Debian Edu on the given machine, and because our target group
11046 are non-technical people, asking them to provide firmware packages on
11047 an external medium is a support pain. Initially, I expected it to be
11048 enough to include the firmware packages on the CD to get
11049 debian-installer to find and use them. This proved to be wrong.
11050 Next, I hoped it was enough to symlink the relevant firmware packages
11051 to some useful location on the CD (tried /cdrom/ and
11052 /cdrom/firmware/). This also proved to not work, and at this point I
11053 found time to look at the debian-installer code to figure out what was
11054 going to work.
</p
>
11056 <p
>The firmware loading code is in the hw-detect package, and a closer
11057 look revealed that it would only look for firmware packages outside
11058 the installation media, so the CD was never checked for firmware
11059 packages. It would only check USB sticks, floppies and other
11060 "external
" media devices. Today I changed it to also look in the
11061 /cdrom/firmware/ directory on the mounted CD or DVD, which should
11062 solve the problem I ran into with Debian edu. I also changed it to
11063 look in /firmware/, to make sure the installer also find firmware
11064 provided in the initrd when booting the installer via PXE, to allow us
11065 to provide the same feature in the PXE setup included in Debian
11068 <p
>To make sure firmware deb packages with a license questions are not
11069 activated without asking if the license is accepted, I extended
11070 hw-detect to look for preinst scripts in the firmware packages, and
11071 run these before activating the firmware during installation. The
11072 license question is asked using debconf in the preinst, so this should
11073 solve the issue for the firmware packages I have looked at so far.
</p
>
11075 <p
>If you want to discuss the details of these features, please
11076 contact us on debian-boot@lists.debian.org.
</p
>
11081 <title>Parallellized boot is now the default in Debian/unstable
</title>
11082 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
11083 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
11084 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
11085 <description><p
>Since this evening, parallel booting is the default in
11086 Debian/unstable for machines using dependency based boot sequencing.
11087 Apparently the testing of concurrent booting has been wider than
11088 expected, if I am to believe the
11089 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
11090 on debian-devel@
</a
>, and I concluded a few days ago to move forward
11091 with the feature this weekend, to give us some time to detect any
11092 remaining problems before Squeeze is frozen. If serious problems are
11093 detected, it is simple to change the default back to sequential boot.
11094 The upload of the new sysvinit package also activate a new upstream
11097 More information about
11098 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11099 based boot sequencing
</a
> is available from the Debian wiki. It is
11100 currently possible to disable parallel booting when one run into
11101 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
11103 <blockquote
><pre
>
11105 </pre
></blockquote
>
11107 <p
>If you report any problems with dependencies in init.d scripts to
11108 the BTS, please usertag the report to get it to show up at
11109 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
11110 list of usertagged bugs related to this
</a
>.
</p
>
11115 <title>Sitesummary tip: Listing MAC address of all clients
</title>
11116 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
11117 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
11118 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
11119 <description><p
>In the recent Debian Edu versions, the
11120 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
11121 system
</a
> is used to keep track of the machines in the school
11122 network. Each machine will automatically report its status to the
11123 central server after boot and once per night. The network setup is
11124 also reported, and using this information it is possible to get the
11125 MAC address of all network interfaces in the machines. This is useful
11126 to update the DHCP configuration.
</p
>
11128 <p
>To give some idea how to use sitesummary, here is a one-liner to
11129 ist all MAC addresses of all machines reporting to sitesummary. Run
11130 this on the collector host:
</p
>
11132 <blockquote
><pre
>
11133 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
11134 </pre
></blockquote
>
11136 <p
>This will list all MAC addresses assosiated with all machine, one
11137 line per machine and with space between the MAC addresses.
</p
>
11139 <p
>To allow system administrators easier job at adding static DHCP
11140 addresses for hosts, it would be possible to extend this to fetch
11141 machine information from sitesummary and update the DHCP and DNS
11142 tables in LDAP using this information. Such tool is unfortunately not
11143 written yet.
</p
>
11148 <title>systemd, an interesting alternative to upstart
</title>
11149 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
11150 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
11151 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
11152 <description><p
>The last few days a new boot system called
11153 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
11155 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
11157 to the free software world. I have not yet had time to play around
11158 with it, but it seem to be a very interesting alternative to
11159 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
11160 a good alternative for Debian when we are able to switch to an event
11161 based boot system. Tollef is
11162 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
11163 systemd into Debian, and I look forward to seeing how well it work. I
11164 like the fact that systemd handles init.d scripts with dependency
11165 information natively, allowing them to run in parallel where upstart
11166 at the moment do not.
</p
>
11168 <p
>Unfortunately do systemd have the same problem as upstart regarding
11169 platform support. It only work on recent Linux kernels, and also need
11170 some new kernel features enabled to function properly. This means
11171 kFreeBSD and Hurd ports of Debian will need a port or a different boot
11172 system. Not sure how that will be handled if systemd proves to be the
11173 way forward.
</p
>
11175 <p
>In the mean time, based on the
11176 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
11177 on debian-devel@
</a
> regarding parallel booting in Debian, I have
11178 decided to enable full parallel booting as the default in Debian as
11179 soon as possible (probably this weekend or early next week), to see if
11180 there are any remaining serious bugs in the init.d dependencies. A
11181 new version of the sysvinit package implementing this change is
11182 already in experimental. If all go well, Squeeze will be released
11183 with parallel booting enabled by default.
</p
>
11188 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
11189 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
11190 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
11191 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
11192 <description><p
>These days, the init.d script dependencies in Squeeze are quite
11193 complete, so complete that it is actually possible to run all the
11194 init.d scripts in parallell based on these dependencies. If you want
11195 to test your Squeeze system, make sure
11196 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11197 based boot sequencing
</a
> is enabled, and add this line to
11198 /etc/default/rcS:
</p
>
11200 <blockquote
><pre
>
11201 CONCURRENCY=makefile
11202 </pre
></blockquote
>
11204 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
11205 scripts in parallel using the dependency information stored in
11206 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
11207 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
11208 to try to start the kdm and gdm scripts as early as possible, and will
11209 start the facilities required by kdm or gdm as early as possible to
11210 make this happen.
</p
>
11212 <p
>Give it a try, and see if you like the result. If some services
11213 fail to start properly, it is most likely because they have incomplete
11214 init.d script dependencies in their startup script (or some of their
11215 dependent scripts have incomplete dependencies). Report bugs and get
11216 the package maintainers to fix it. :)
</p
>
11218 <p
>Running scripts in parallel could be the default in Debian when we
11219 manage to get the init.d script dependencies complete and correct. I
11220 expect we will get there in Squeeze+
1, if we get manage to test and
11221 fix the remaining issues.
</p
>
11223 <p
>If you report any problems with dependencies in init.d scripts to
11224 the BTS, please usertag the report to get it to show up at
11225 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
11226 list of usertagged bugs related to this
</a
>.
</p
>
11231 <title>Debian has switched to dependency based boot sequencing
</title>
11232 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
11233 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
11234 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
11235 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
11236 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
11237 have been migrated to using dependency based boot sequencing. This
11238 conclude work me and others have been doing for the last three days.
11239 It feels great to see this finally part of the default Debian
11240 installation. Now we just need to weed out the last few problems that
11241 are bound to show up, to get everything ready for Squeeze.
</p
>
11243 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
11244 fixing the more fundamental problem of handing the event based
11245 non-predictable kernel in the early boot.
</p
>
11250 <title>Taking over sysvinit development
</title>
11251 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
11252 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
11253 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
11254 <description><p
>After several years of frustration with the lack of activity from
11255 the existing sysvinit upstream developer, I decided a few weeks ago to
11256 take over the package and become the new upstream. The number of
11257 patches to track for the Debian package was becoming a burden, and the
11258 lack of synchronization between the distribution made it hard to keep
11259 the package up to date.
</p
>
11261 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
11262 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
11263 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
11264 and Fedora), based on the patches currently in use in these
11265 distributions. We Debian maintainers plan to move to this tarball as
11266 the new upstream as soon as we find time to do the merge. Since the
11267 new tarball was created, we agreed with Werner at SuSe to make a new
11268 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
11269 development there. The project is registered and currently waiting
11270 for approval by the Savannah administrators, and as soon as it is
11271 approved, we will import the old versions from svn and continue
11272 working on the future release.
</p
>
11274 <p
>It is a bit ironic that this is done now, when some of the involved
11275 distributions are moving to upstart as a syvinit replacement.
</p
>
11280 <title>Debian boots quicker and quicker
</title>
11281 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
11282 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
11283 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
11284 <description><p
>I spent Monday and tuesday this week in London with a lot of the
11285 people involved in the boot system on Debian and Ubuntu, to see if we
11286 could find more ways to speed up the boot system. This was an Ubuntu
11288 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
11289 gathering
</a
>. It was quite productive. We also discussed the future
11290 of boot systems, and ways to handle the increasing number of boot
11291 issues introduced by the Linux kernel becoming more and more
11292 asynchronous and event base. The Ubuntu approach using udev and
11293 upstart might be a good way forward. Time will show.
</p
>
11295 <p
>Anyway, there are a few ways at the moment to speed up the boot
11296 process in Debian. All of these should be applied to get a quick
11301 <li
>Use dash as /bin/sh.
</li
>
11303 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
11304 clock is in UTC.
</li
>
11306 <li
>Install and activate the insserv package to enable
11307 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
11308 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
11312 These points are based on the Google summer of code work done by
11313 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
11314 Villegas
</a
>.
11316 <p
>Support for makefile-style concurrency during boot was uploaded to
11317 unstable yesterday. When we tested it, we were able to cut
6 seconds
11318 from the boot sequence. It depend on very correct dependency
11319 declaration in all init.d scripts, so I expect us to find edge cases
11320 where the dependences in some scripts are slightly wrong when we start
11321 using this.
</p
>
11323 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
11324 introduced by Raphael Geissert today, one that could affect the
11325 startup speed as well. Instead of starting some scripts concurrently
11326 from rcS.d/ and another set of scripts from rc2.d/, it would be
11327 possible to run a of them in the same process. A quick way to test
11328 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
11329 insserv
'. Will need to test if that work. :)
</p
>
11334 <title>BSAs påstander om piratkopiering møter motstand
</title>
11335 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
11336 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
11337 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
11338 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
11339 programvareselskapene som Microsoft og Apple, publisert en rapport der
11340 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
11341 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
11343 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
11344 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
11345 dagene. Et spesielt interessant kommentar fra Sverige,
11346 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
11347 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
11350 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
11351 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
11352 företag.
"Man bör nog kanske inte se de här siffrorna som helt
11353 exakta
", säger BSAs Sverigechef John Hugosson.
11354 </blockquote
>
11356 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
11357 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
11358 piracy figures need a shot of reality
</a
> og
<a
11359 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
11360 Copyright Treaty Work?
</a
></p
>
11362 <p
>Fant lenkene via
<a
11363 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
11364 på Slashdot
</a
>.
</p
>
11369 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
11370 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
11371 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
11372 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
11373 <description><p
>Kom over
11374 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
11375 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
11376 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
11377 jobber til daglig. En rask opptelling forteller meg at vi har
490
11378 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
11379 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
11380 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
11385 <title>Kryptert harddisk - naturligvis
</title>
11386 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
11387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
11388 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
11389 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
11390 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
11391 når en tar tap av arbeidstid, fortrolige dokumenter,
11392 personopplysninger og alt annet det innebærer. Det er ingen tvil om
11393 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
11394 til at jeg har kryptert harddisken på både kontormaskinen og min
11395 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
11396 komme på avveie, den første informasjon relatert til jobben min ved
11397 Universitetet i Oslo, og den andre relatert til blant annet
11398 foreningsarbeide. Kryptering av diskene gjør at det er lite
11399 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
11400 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
11401 og en reboot vil gjøre at de ber om passord før de vil starte opp.
11402 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
11403 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
11404 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
11405 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
11406 det er gjort slik jeg gjør det er minimale, og gevinstene er
11407 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
11408 maskinen reinstalleres og alt er tapt.
</p
>
11410 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
11411 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
11412 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
11413 er for min del høyere enn gevinsten. Jeg tror oddsene for at
11414 f.eks. etteretningsorganisasjoner har glede av å titte på mine
11415 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
11416 gjøre det vanskeligere for angripere med kompetanse og ressurser er
11417 betydelige.
</p
>
11422 <title>Two projects that have improved the quality of free software a lot
</title>
11423 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
11424 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
11425 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
11426 <description><p
>There are two software projects that have had huge influence on the
11427 quality of free software, and I wanted to mention both in case someone
11428 do not yet know them.
</p
>
11430 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
11431 tool to detect and expose errors in the memory handling of programs.
11432 It is easy to use, all one need to do is to run
'valgrind program
',
11433 and it will report any problems on stdout. It is even better if the
11434 program include debug information. With debug information, it is able
11435 to report the source file name and line number where the problem
11436 occurs. It can report things like
'reading past memory block in file
11437 X line N, the memory block was allocated in file Y, line M
', and
11438 'using uninitialised value in control logic
'. This tool has made it
11439 trivial to investigate reproducible crash bugs in programs, and have
11440 reduced the number of this kind of bugs in free software a lot.
11442 <p
>The second one is
11443 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
11444 a source code checker. It is able to process the source of a program
11445 and find problems in the logic without running the program. It
11446 started out as the Stanford Checker and became well known when it was
11447 used to find bugs in the Linux kernel. It is now a commercial tool
11448 and the company behind it is running
11449 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
11450 free software community, where a lot of free software projects get
11451 their source checked for free. Several thousand defects have been
11452 found and fixed so far. It can find errors like
'lock L taken in file
11453 X line N is never released if exiting in line M
', or
'the code in file
11454 Y lines O to P can never be executed
'. The projects included in the
11455 community service project have managed to get rid of a lot of
11456 reliability problems thanks to Coverity.
</p
>
11458 <p
>I believe tools like this, that are able to automatically find
11459 errors in the source, are vital to improve the quality of software and
11460 make sure we can get rid of the crashing and failing software we are
11461 surrounded by today.
</p
>
11466 <title>No patch is not better than a useless patch
</title>
11467 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
11468 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
11469 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
11470 <description><p
>Julien Blache
11471 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
11472 patch is better than a useless patch
</a
>. I completely disagree, as a
11473 patch allow one to discuss a concrete and proposed solution, and also
11474 prove that the issue at hand is important enough for someone to spent
11475 time on fixing it. No patch do not provide any of these positive
11476 properties.
</p
>
11481 <title>Standardize on protocols and formats, not vendors and applications
</title>
11482 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
11483 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
11484 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
11485 <description><p
>Where I work at the University of Oslo, one decision stand out as a
11486 very good one to form a long lived computer infrastructure. It is the
11487 simple one, lost by many in todays computer industry: Standardize on
11488 open network protocols and open exchange/storage formats, not applications.
11489 Applications come and go, while protocols and files tend to stay, and
11490 thus one want to make it easy to change application and vendor, while
11491 avoiding conversion costs and locking users to a specific platform or
11492 application.
</p
>
11494 <p
>This approach make it possible to replace the client applications
11495 independently of the server applications. One can even allow users to
11496 use several different applications as long as they handle the selected
11497 protocol and format. In the normal case, only one client application
11498 is recommended and users only get help if they choose to use this
11499 application, but those that want to deviate from the easy path are not
11500 blocked from doing so.
</p
>
11502 <p
>It also allow us to replace the server side without forcing the
11503 users to replace their applications, and thus allow us to select the
11504 best server implementation at any moment, when scale and resouce
11505 requirements change.
</p
>
11507 <p
>I strongly recommend standardizing - on open network protocols and
11508 open formats, but I would never recommend standardizing on a single
11509 application that do not use open network protocol or open formats.
</p
>
11514 <title>Returning from Skolelinux developer gathering
</title>
11515 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
11516 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
11517 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
11518 <description><p
>I
'm sitting on the train going home from this weekends Debian
11519 Edu/Skolelinux development gathering. I got a bit done tuning the
11520 desktop, and looked into the dynamic service location protocol
11521 implementation avahi. It look like it could be useful for us. Almost
11522 30 people participated, and I believe it was a great environment to
11523 get to know the Skolelinux system. Walter Bender, involved in the
11524 development of the Sugar educational platform, presented his stuff and
11525 also helped me improve my OLPC installation. He also showed me that
11526 his Turtle Art application can be used in standalone mode, and we
11527 agreed that I would help getting it packaged for Debian. As a
11528 standalone application it would be great for Debian Edu. We also
11529 tried to get the video conferencing working with two OLPCs, but that
11530 proved to be too hard for us. The application seem to need more work
11531 before it is ready for me. I look forward to getting home and relax
11537 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
11538 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
11539 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
11540 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
11541 <description><p
>The state of standardized LDAP schemas on Linux is far from
11542 optimal. There is RFC
2307 documenting one way to store NIS maps in
11543 LDAP, and a modified version of this normally called RFC
2307bis, with
11544 some modifications to be compatible with Active Directory. The RFC
11545 specification handle the content of a lot of system databases, but do
11546 not handle DNS zones and DHCP configuration.
</p
>
11548 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
11549 we would like to store information about users, SMB clients/hosts,
11550 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
11551 and LTSP configuration in LDAP. These objects have a lot in common,
11552 but with the current LDAP schemas it is not possible to have one
11553 object per entity. For example, one need to have at least three LDAP
11554 objects for a given computer, one with the SMB related stuff, one with
11555 DNS information and another with DHCP information. The schemas
11556 provided for DNS and DHCP are impossible to combine into one LDAP
11557 object. In addition, it is impossible to implement quick queries for
11558 netgroup membership, because of the way NIS triples are implemented.
11559 It just do not scale. I believe it is time for a few RFC
11560 specifications to cleam up this mess.
</p
>
11562 <p
>I would like to have one LDAP object representing each computer in
11563 the network, and this object can then keep the SMB (ie host key), DHCP
11564 (mac address/name) and DNS (name/IP address) settings in one place.
11565 It need to be efficently stored to make sure it scale well.
</p
>
11567 <p
>I would also like to have a quick way to map from a user or
11568 computer and to the net group this user or computer is a member.
</p
>
11570 <p
>Active Directory have done a better job than unix heads like myself
11571 in this regard, and the unix side need to catch up. Time to start a
11572 new IETF work group?
</p
>
11577 <title>Endelig er Debian Lenny gitt ut
</title>
11578 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
11579 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
11580 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
11581 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
11582 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
11583 Et langt steg videre for Debian-prosjektet, og en rekke nye
11584 programpakker blir nå tilgjengelig for de av oss som bruker den
11585 stabile utgaven av Debian. Neste steg er nå å få
11586 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
11587 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
11588 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
11589 slippes løs på skolene. Takk til alle debian-utviklerne som har
11590 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
11591 bootsekvens tilgjengelig i stabil utgave, vha pakken
11592 <tt
>insserv
</tt
>.
</p
>
11597 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
11598 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
11599 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
11600 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
11601 <description><p
>This weekend we had a small developer gathering for Debian Edu in
11602 Oslo. Most of Saturday was used for the general assemly for the
11603 member organization, but the rest of the weekend I used to tune the
11604 LTSP installation. LTSP now work out of the box on the
10-network.
11605 Acer Aspire One proved to be a very nice thin client, with both
11606 screen, mouse and keybard in a small box. Was working on getting the
11607 diskless workstation setup configured out of the box, but did not
11608 finish it before the weekend was up.
</p
>
11610 <p
>Did not find time to look at the
4 VGA cards in one box we got from
11611 the Brazilian group, so that will have to wait for the next
11612 development gathering. Would love to have the Debian Edu installer
11613 automatically detect and configure a multiseat setup when it find one
11614 of these cards.
</p
>
11619 <title>The sorry state of multimedia browser plugins in Debian
</title>
11620 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
11621 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
11622 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
11623 <description><p
>Recently I have spent some time evaluating the multimedia browser
11624 plugins available in Debian Lenny, to see which one we should use by
11625 default in Debian Edu. We need an embedded video playing plugin with
11626 control buttons to pause or stop the video, and capable of streaming
11627 all the multimedia content available on the web. The test results and
11628 notes are available on
11629 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
11630 Debian wiki
</a
>. I was surprised how few of the plugins are able to
11631 fill this need. My personal video player favorite, VLC, has a really
11632 bad plugin which fail on a lot of the test pages. A lot of the MIME
11633 types I would expect to work with any free software player (like
11634 video/ogg), just do not work. And simple formats like the
11635 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
11636 totem and vlc plugins. I hope the situation will improve soon. No
11637 wonder sites use the proprietary Adobe flash to play video.
</p
>
11639 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
11640 be the only one fitting our needs. :/
</p
>