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>Isenkram updated with a lot more hardware-package mappings
</title>
11 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
13 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
14 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
15 system
</a
> I wrote two years ago to make it easier in Debian to find
16 and install packages to get your hardware dongles to work, is still
17 going strong. It is a system to look up the hardware present on or
18 connected to the current system, and map the hardware to Debian
19 packages. It can either be done using the tools in isenkram-cli or
20 using the user space daemon in the isenkram package. The latter will
21 notify you when new hardware about the packages to install to get it
22 working, and even provide a button to click on to ask packagekit to
23 install the packages. Here is an command line example from my
24 Thinkpad laptop:
</p
>
43 </pre
></p
>
45 <p
>It can also list the firware package providing firmware requested
46 by the load kernel modules, which in my case is an empty list because
47 I have all the firmware my machine need:
50 % /usr/sbin/isenkram-autoinstall-firmware -l
51 info: did not find any firmware files requested by loaded kernel modules. exiting
53 </pre
></p
>
55 <p
>The last few days I had a look at several of the around
250
56 packages in Debian with udev rules. These seem like good candidates
57 to install when a given hardware dongle is inserted, and I found
58 several that should be proposed by isenkram. I have not had time to
59 check all of them, but am happy to report that now there are
97
60 packages packages mapped to hardware by Isenkram.
11 of these
61 packages provide hardware mapping using AppStream, while the rest are
62 listed in the modaliases file provided in isenkram.
</p
>
64 <p
>These are the packages with hardware mappings at the moment. The
65 <strong
>marked packages
</strong
> are also announcing their hardware
66 support using AppStream, for everyone to use:
</p
>
68 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
69 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
70 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
71 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
72 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
73 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
74 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
75 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
76 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
77 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
78 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
79 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
80 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
81 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
82 pcscd, pidgin-blinklight, printer-driver-splix,
83 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
84 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
85 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
86 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
87 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
88 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
89 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
90 xserver-xorg-video-vmware, yubikey-personalization and
91 zd1211-firmware
</p
>
93 <p
>If you know of other packages, please let me know with a wishlist
94 bug report against the isenkram-cli package, and ask the package
96 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
97 metadata according to the guidelines
</a
> to provide the information
98 for everyone. In time, I hope to get rid of the isenkram specific
99 hardware mapping and depend exclusively on AppStream.
</p
>
101 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
102 much hardware, and suggest that the package with with any ethernet
103 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
104 the details. I hope the maintainer find time to address it soon. In
105 the mean time I provide an override in isenkram.
</p
>
110 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
111 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
113 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
114 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
116 <p
>In my early years, I played
117 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
118 Elite
</a
> on my PC. I spent many months trading and fighting in
119 space, and reached the
'elite
' fighting status before I moved on. The
120 original Elite game was available on Commodore
64 and the IBM PC
121 edition I played had a
64 KB executable. I am still impressed today
122 that the authors managed to squeeze both a
3D engine and details about
123 more than
2000 planet systems across
7 galaxies into a binary so
126 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
127 software game Oolite inspired by Elite
</a
> for a while, but did not
128 really have time to test it properly until a few days ago. It was
129 great to discover that my old knowledge about trading routes were
130 still valid. But my fighting and flying abilities were gone, so I had
131 to retrain to be able to dock on a space station. And I am still not
132 able to make much resistance when I am attacked by pirates, so I
133 bougth and mounted the most powerful laser in the rear to be able to
134 put up at least some resistance while fleeing for my life. :)
</p
>
136 <p
>When playing Elite in the late eighties, I had to discover
137 everything on my own, and I had long lists of prices seen on different
138 planets to be able to decide where to trade what. This time I had the
140 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
141 where information about each planet is easily available with common
142 price ranges and suggested trading routes. This improved my ability
143 to earn money and I have been able to earn enough to buy a lot of
144 useful equipent in a few days. I believe I originally played for
145 months before I could get a docking computer, while now I could get it
146 after less then a week.
</p
>
148 <p
>If you like science fiction and dreamed of a life as a vagabond in
149 space, you should try out Oolite. It is available for Linux, MacOSX
150 and Windows, and is included in Debian and derivatives since
2011.
</p
>
152 <p
>As usual, if you use Bitcoin and want to show your support of my
153 activities, please send Bitcoin donations to my address
154 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
159 <title>Quicker Debian installations using eatmydata
</title>
160 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
161 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
162 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
163 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
164 installation system, observing how using
165 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
166 could speed up the installation
</a
> quite a bit. My testing measured
167 speedup around
20-
40 percent for Debian Edu, where we install around
168 1000 packages from within the installer. The eatmydata package
169 provide a way to disable/delay file system flushing. This is a bit
170 risky in the general case, as files that should be stored on disk will
171 stay only in memory a bit longer than expected, causing problems if a
172 machine crashes at an inconvenient time. But for an installation, if
173 the machine crashes during installation the process is normally
174 restarted, and avoiding disk operations as much as possible to speed
175 up the process make perfect sense.
177 <p
>I added code in the Debian Edu specific installation code to enable
178 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
179 but did not have time to push it any further. But a few months ago I
180 picked it up again and worked with the libeatmydata package maintainer
181 Mattia Rizzolo to make it easier for everyone to get this installation
182 speedup in Debian. Thanks to our cooperation There is now an
183 eatmydata-udeb package in Debian testing and unstable, and simply
184 enabling/installing it in debian-installer (d-i) is enough to get the
185 quicker installations. It can be enabled using preseeding. The
186 following untested kernel argument should do the trick:
</p
>
188 <blockquote
><pre
>
189 preseed/early_command=
"anna-install eatmydata-udeb
"
190 </pre
></blockquote
>
192 <p
>This should ask d-i to install the package inside the d-i
193 environment early in the installation sequence. Having it installed
194 in d-i in turn will make sure the relevant scripts are called just
195 after debootstrap filled /target/ with the freshly installed Debian
196 system to configure apt to run dpkg with eatmydata. This is enough to
197 speed up the installation process. There is a proposal to
198 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
199 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
200 tested its impact.
</p
>
206 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
207 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
208 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
209 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
210 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
211 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
212 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
213 elever over det ganske land skal levere inn hvert år. Det mange ikke
214 vet er at selv om de kommersielle alternativene
215 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
216 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
217 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
218 utmerket fri programvarealternativ som kan. Oversetterverktøyet
219 Apertium har støtte for en rekke språkkombinasjoner, og takket være
220 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
221 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
222 nynorsk, og få den automatoversatt til det andre skriftspråket.
223 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
224 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
225 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
226 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
227 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
228 teksten din i webskjemaet der.
230 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
231 teknologien kan du enten installere pakken
232 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
233 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
235 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
236 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
237 denne teksten som ble skrevet på bokmål over maskinoversatt til
242 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
243 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
244 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
245 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
246 veit er at sjølv om dei kommersielle alternativa
247 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
248 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
249 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
250 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
251 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
252 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
253 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
254 nynorsk, og få den *automatoversatt til det andre skriftspråket.
255 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
256 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
257 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
258 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
259 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
260 teksta di i *webskjemaet der.
262 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
263 teknologien kan du anten installera pakken
264 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
265 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
266 *api.*apertium.org. Sjå
267 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
268 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
269 for denne teksta som vart skreva på bokmål over *maskinoversatt til
275 <title>Coz profiler for multi-threaded software is now in Debian
</title>
276 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
277 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
278 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
279 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
280 profiler able to run benchmarking experiments on the instrumented
281 multi-threaded program, finally
282 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
283 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
285 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
286 blogged about the coz tool
</a
> in August working with upstream to make
287 it suitable for Debian. There are still issues with clang
288 compatibility, inline assembly only working x86 and minimized
289 JavaScript libraries.
</p
>
291 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
293 <p
><blockquote
>
294 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
295 </blockquote
></p
>
297 <p
>This will produce a profile.coz file in the current working
298 directory with the profiling information. This is then given to a
299 JavaScript application provided in the package and available from
300 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
301 To start the local copy, invoke it in a browser like this:
</p
>
303 <p
><blockquote
>
304 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
305 </blockquote
></p
>
307 <p
>See the project home page and the
308 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
309 ;login: article on Coz
</a
> for more information on how it is
315 <title>My own self balancing Lego Segway
</title>
316 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
317 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
318 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
319 <description><p
>A while back I received a Gyro sensor for the NXT
320 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
321 present. It had been on my wishlist for a while, because I wanted to
322 build a Segway like balancing lego robot. I had already built
323 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
324 robot
</a
> with the kids, using the light/color sensor included in the
325 NXT kit as the balance sensor, but it was not working very well. It
326 could balance for a while, but was very sensitive to the light
327 condition in the room and the reflective properties of the surface and
328 would fall over after a short while. I wanted something more robust,
330 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
331 gyro sensor from HiTechnic
</a
> I believed would solve it on my
332 wishlist for some years before it suddenly showed up as a gift from my
333 loved ones. :)
</p
>
335 <p
>Unfortunately I have not had time to sit down and play with it
336 since then. But that changed some days ago, when I was searching for
337 lego segway information and came across a recipe from HiTechnic for
339 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
340 HTWay
</a
>, a segway like balancing robot. Build instructions and
341 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
342 code
</a
> was included, so it was just a question of putting it all
343 together. And thanks to the great work of many Debian developers, the
344 compiler needed to build the source for the NXT is already included in
345 Debian, so I was read to go in less than an hour. The resulting robot
346 do not look very impressive in its simplicity:
</p
>
348 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
350 <p
>Because I lack the infrared sensor used to control the robot in the
351 design from HiTechnic, I had to comment out the last task
352 (taskControl). I simply placed /* and */ around it get the program
353 working without that sensor present. Now it balances just fine until
354 the battery status run low:
</p
>
356 <p align=
"center
"><video width=
"70%
" controls=
"true
">
357 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
358 </video
></p
>
360 <p
>Now we would like to teach it how to follow a line and take remote
361 control instructions using the included Bluetooth receiver in the NXT.
</p
>
363 <p
>If you, like me, love LEGO and want to make sure we find the tools
364 they need to work with LEGO in Debian and all our derivative
365 distributions like Ubuntu, check out
366 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
367 project page
</a
> and join the Debian LEGO team. Personally I own a
368 RCX and NXT controller (no EV3), and would like to make sure the
369 Debian tools needed to program the systems I own work as they
375 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
376 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
377 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
378 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
379 <description><p
>In July
380 <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
381 wrote how to get the Signal Chrome/Chromium app working
</a
> without
382 the ability to receive SMS messages (aka without a cell phone). It is
383 time to share some experiences and provide an updated setup.
</p
>
385 <p
>The Signal app have worked fine for several months now, and I use
386 it regularly to chat with my loved ones. I had a major snag at the
387 end of my summer vacation, when the the app completely forgot my
388 setup, identity and keys. The reason behind this major mess was
389 running out of disk space. To avoid that ever happening again I have
390 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
391 roll back to an earlier version if the files are wiped by mistake. I
392 had to use it once after introducing the git backup. When rolling
393 back to an earlier version, one need to use the
'reset session
' option
394 in Signal to get going, and notify the people you talk with about the
395 problem. I assume there is some sequence number tracking in the
396 protocol to detect rollback attacks. The git repository is rather big
397 (
674 MiB so far), but I have not tried to figure out if some of the
398 content can be added to a .gitignore file due to lack of spare
401 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
402 make it impossible to send messages using Signal. I could still
403 receive them, but had to patch the code with a new timestamp to send.
404 I believe the timeout is added by the developers to force people to
405 upgrade to the latest version of the app, even when there is no
406 protocol changes, to reduce the version skew among the user base and
407 thus try to keep the number of support requests down.
</p
>
409 <p
>Since my original recipe, the Signal source code changed slightly,
410 making the old patch fail to apply cleanly. Below is an updated
411 patch, including the shell wrapper I use to start Signal. The
412 original version required a new user to locate the JavaScript console
413 and call a function from there. I got help from a friend with more
414 JavaScript knowledge than me to modify the code to provide a GUI
415 button instead. This mean that to get started you just need to run
416 the wrapper and click the
'Register without mobile phone
' to get going
417 now. I
've also modified the timeout code to always set it to
90 days
418 in the future, to avoid having to patch the code regularly.
</p
>
420 <p
>So, the updated recipe for Debian Jessie:
</p
>
424 <li
>First, install required packages to get the source code and the
425 browser you need. Signal only work with Chrome/Chromium, as far as I
426 know, so you need to install it.
429 apt install git tor chromium
430 git clone https://github.com/WhisperSystems/Signal-Desktop.git
431 </pre
></li
>
433 <li
>Modify the source code using command listed in the the patch
434 block below.
</li
>
436 <li
>Start Signal using the run-signal-app wrapper (for example using
437 <tt
>`pwd`/run-signal-app
</tt
>).
439 <li
>Click on the
'Register without mobile phone
', will in a phone
440 number you can receive calls to the next minute, receive the
441 verification code and enter it into the form field and press
442 'Register
'. Note, the phone number you use will be user Signal
443 username, ie the way others can find you on Signal.
</li
>
445 <li
>You can now use Signal to contact others. Note, new contacts do
446 not show up in the contact list until you restart Signal, and there is
447 no way to assign names to Contacts. There is also no way to create or
448 update chat groups. I suspect this is because the web app do not have
449 a associated contact database.
</li
>
453 <p
>I am still a bit uneasy about using Signal, because of the way its
454 main author moxie0 reject federation and accept dependencies to major
455 corporations like Google (part of the code is fetched from Google) and
456 Amazon (the central coordination point is owned by Amazon). See for
458 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
459 LibreSignal issue tracker
</a
> for a thread documenting the authors
460 view on these issues. But the network effect is strong in this case,
461 and several of the people I want to communicate with already use
462 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
463 once it
<a href=
"https://bugs.debian.org/
830265">work on my
464 laptop
</a
>? It already work on Windows and Android, and is included
465 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
466 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
467 working on Debian Stable.
</p
>
469 <p
>Anyway, this is the patch I apply to the Signal code to get it
470 working. It switch to the production servers, disable to timeout,
471 make registration easier and add the shell wrapper:
</p
>
474 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
475 diff --git a/js/background.js b/js/background.js
476 index
24b4c1d.
.579345f
100644
477 --- a/js/background.js
478 +++ b/js/background.js
483 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
484 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
485 var SERVER_PORTS = [
80,
4433,
8443];
486 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
487 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
489 window.getSocketStatus = function() {
490 if (messageReceiver) {
491 diff --git a/js/expire.js b/js/expire.js
492 index
639aeae..beb91c3
100644
497 'use strict
';
498 - var BUILD_EXPIRATION =
0;
499 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
501 window.extension = window.extension || {};
503 diff --git a/js/views/install_view.js b/js/views/install_view.js
504 index
7816f4f.
.1d6233b
100644
505 --- a/js/views/install_view.js
506 +++ b/js/views/install_view.js
509 'click .step1
': this.selectStep.bind(this,
1),
510 'click .step2
': this.selectStep.bind(this,
2),
511 -
'click .step3
': this.selectStep.bind(this,
3)
512 +
'click .step3
': this.selectStep.bind(this,
3),
513 +
'click .callreg
': function() { extension.install(
'standalone
') },
516 clearQR: function() {
517 diff --git a/options.html b/options.html
518 index dc0f28e.
.8d709f6
100644
522 &lt;div class=
'nav
'>
523 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
524 &lt;p
>{{ installTagline }}
&lt;/p
>
525 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
526 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
527 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
530 &lt;span class=
'dot step1 selected
'>&lt;/span
>
531 &lt;span class=
'dot step2
'>&lt;/span
>
532 &lt;span class=
'dot step3
'>&lt;/span
>
533 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
534 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
540 +userdata=
"`pwd`/userdata
"
541 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
542 + (cd $userdata
&& git init)
544 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
546 + --proxy-server=
"socks://localhost:
9050" \
547 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
549 chmod a+rx run-signal-app
552 <p
>As usual, if you use Bitcoin and want to show your support of my
553 activities, please send Bitcoin donations to my address
554 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
559 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
560 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
561 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
562 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
563 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
564 system
</a
> provide a practical and easy way to figure out which
565 packages support the hardware in a given machine. The command line
566 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
567 convenient way to list and install packages relevant for the current
568 hardware during system installation, both user space packages and
569 firmware packages. The GUI background daemon on the other hand provide
570 a pop-up proposing to install packages when a new dongle is inserted
571 while using the computer. For example, if you plug in a smart card
572 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
573 that package isn
't already installed, and if you plug in a USB video
574 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
575 cheese is currently missing. This already work just fine.
</p
>
577 <p
>But Isenkram depend on a database mapping from hardware IDs to
578 package names. When I started no such database existed in Debian, so
579 I made my own data set and included it with the isenkram package and
580 made isenkram fetch the latest version of this database from git using
581 http. This way the isenkram users would get updated package proposals
582 as soon as I learned more about hardware related packages.
</p
>
584 <p
>The hardware is identified using modalias strings. The modalias
585 design is from the Linux kernel where most hardware descriptors are
586 made available as a strings that can be matched using filename style
587 globbing. It handle USB, PCI, DMI and a lot of other hardware related
588 identifiers.
</p
>
590 <p
>The downside to the Isenkram specific database is that there is no
591 information about relevant distribution / Debian version, making
592 isenkram propose obsolete packages too. But along came AppStream, a
593 cross distribution mechanism to store and collect metadata about
594 software packages. When I heard about the proposal, I contacted the
595 people involved and suggested to add a hardware matching rule using
596 modalias strings in the specification, to be able to use AppStream for
597 mapping hardware to packages. This idea was accepted and AppStream is
598 now a great way for a package to announce the hardware it support in a
599 distribution neutral way. I wrote
600 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
601 recipe on how to add such meta-information
</a
> in a blog post last
602 December. If you have a hardware related package in Debian, please
603 announce the relevant hardware IDs using AppStream.
</p
>
605 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
606 RCX or NXT unit, announce this support using AppStream. The effect is
607 that when you insert such LEGO robot controller into your Debian
608 machine, Isenkram will propose to install the packages needed to get
609 it working. The intention is that this should allow the local user to
610 start programming his robot controller right away without having to
611 guess what packages to use or which permissions to fix.
</p
>
613 <p
>But when I sat down with my son the other day to program our NXT
614 unit using his Debian Stretch computer, I discovered something
615 annoying. The local console user (ie my son) did not get access to
616 the USB device for programming the unit. This used to work, but no
617 longer in Jessie and Stretch. After some investigation and asking
618 around on #debian-devel, I discovered that this was because udev had
619 changed the mechanism used to grant access to local devices. The
620 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
621 no longer applied, because LDAP users no longer was added to the
622 plugdev group during login. Michael Biebl told me that this method
623 was obsolete and the new method used ACLs instead. This was good
624 news, as the plugdev mechanism is a mess when using a remote user
625 directory like LDAP. Using ACLs would make sure a user lost device
626 access when she logged out, even if the user left behind a background
627 process which would retain the plugdev membership with the ConsoleKit
628 setup. Armed with this knowledge I moved on to fix the access problem
629 for the LEGO Mindstorms related packages.
</p
>
631 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
632 applied directly for a device, or is applied in
633 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
634 LEGO Mindstorms udev rules did not have a class, I decided to add the
635 tag directly in the udev rules files included in the packages. Here
636 is one example. For the nqc C compiler for the RCX, the
637 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
640 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
641 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
642 </pre
></p
>
644 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
645 packages using plugdev in their /lib/udev/rules.d/ files should be
646 changed to use this tag (either directly or indirectly via
647 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
648 to detect this?
</p
>
650 <p
>I
've been unable to find good documentation on the uaccess feature.
651 It is unclear to me if the uaccess tag is an internal implementation
652 detail like the udev-acl tag used by
653 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
654 indirect method is the preferred way. Michael
655 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
656 documentation from the systemd project
</a
> and I hope it will make
657 this clearer. For now I use the generic classes when they exist and
658 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
659 directly if no such class exist.
</p
>
661 <p
>To learn more about the isenkram system, please check out
662 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
663 blog posts tagged isenkram
</a
>.
</p
>
665 <p
>To help out making life for LEGO constructors in Debian easier,
666 please join us on our IRC channel
667 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
668 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
669 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
670 list is not yet created, but we are working on it. :)
</p
>
672 <p
>As usual, if you use Bitcoin and want to show your support of my
673 activities, please send Bitcoin donations to my address
674 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
679 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
680 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
681 <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>
682 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
683 <description><p
>In April we
684 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
685 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
686 how to set up and administrate a Debian system. Today I am happy to
687 report that the first draft is now publicly available. You can find
688 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
689 Administrator
's Handbook page
</a
> (under Other languages). The first
690 eight chapters have a first draft translation, and we are working on
691 proofreading the content. If you want to help out, please start
693 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
694 hosted weblate project page
</a
>, and get in touch using
695 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
696 translators mailing list
</a
>. Please also check out
697 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
698 contributors
</a
>. A good way to contribute is to proofread the text
699 and update weblate if you find errors.
</p
>
701 <p
>Our goal is still to make the Norwegian book available on paper as well as
702 electronic form.
</p
>
707 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
708 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
710 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
711 <description><p
>This summer, I read a great article
712 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
713 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
714 how to profile multi-threaded programs. It presented a system for
715 profiling software by running experiences in the running program,
716 testing how run time performance is affected by
"speeding up
" parts of
717 the code to various degrees compared to a normal run. It does this by
718 slowing down parallel threads while the
"faster up
" code is running
719 and measure how this affect processing time. The processing time is
720 measured using probes inserted into the code, either using progress
721 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
722 can also measure unmodified code by measuring complete the program
723 runtime and running the program several times instead.
</p
>
725 <p
>The project and presentation was so inspiring that I would like to
726 get the system into Debian. I
727 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
728 a WNPP request for it
</a
> and contacted upstream to try to make the
729 system ready for Debian by sending patches. The build process need to
730 be changed a bit to avoid running
'git clone
' to get dependencies, and
731 to include the JavaScript web page used to visualize the collected
732 profiling information included in the source package.
733 But I expect that should work out fairly soon.
</p
>
735 <p
>The way the system work is fairly simple. To run an coz experiment
736 on a binary with debug symbols available, start the program like this:
738 <p
><blockquote
><pre
>
739 coz run --- program-to-run
740 </pre
></blockquote
></p
>
742 <p
>This will create a text file profile.coz with the instrumentation
743 information. To show what part of the code affect the performance
744 most, use a web browser and either point it to
745 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
746 or use the copy from git (in the gh-pages branch). Check out this web
747 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
748 profiling more useful you include
&lt;coz.h
&gt; and insert the
749 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
750 code, rebuild and run the profiler. This allow coz to do more
751 targeted experiments.
</p
>
753 <p
>A video published by ACM
754 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
755 Coz profiler
</a
> is available from Youtube. There is also a paper
756 from the
25th Symposium on Operating Systems Principles available
758 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
759 finding code that counts with causal profiling
</a
>.
</p
>
761 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
762 for Coz is available from github. It will only build with clang
764 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
765 feature missing in GCC
</a
>, but I
've submitted
766 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
767 it
</a
> and hope it will be included in the upstream source soon.
</p
>
769 <p
>Please get in touch if you, like me, would like to see this piece
770 of software in Debian. I would very much like some help with the
771 packaging effort, as I lack the in depth knowledge on how to package
772 C++ libraries.
</p
>
777 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
778 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
780 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
781 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
782 to be a slight challenge. Here is the recipe if I ever need to do it
783 again. It all started by me wanting to try the recipe to set up
784 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
785 hardened Android installation
</a
> from the Tor project blog on a
786 device I had access to. It is a old mobile phone with a broken
787 microphone The initial idea had been to just
788 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
789 CyanogenMod on it
</a
>, but did not quite find time to start on it
790 until a few days ago.
</p
>
792 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
793 loader (press volume down and power at the same time), (
2) select
794 'fastboot
' before (
3) connecting the device via USB to a Linux
795 machine, (
4) request the device identifier token by running
'fastboot
796 oem get_identifier_token
', (
5) request the device unlocking key using
797 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
798 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
800 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
801 or newer, and the device I was working on had
2.00.0027. This
802 apparently can be easily fixed by downloading a Windows program and
803 running it on your Windows machine, if you accept the terms Microsoft
804 require you to accept to use Windows - which I do not. So I had to
805 come up with a different approach. I got a lot of help from AndyCap
806 on #nuug, and would not have been able to get this working without
809 <p
>First I needed to extract the hboot firmware from
810 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
811 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
812 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
813 project named unruu
</a
> using libunshield. The unshield tool did not
814 recognise the file format, but unruu worked and extracted rom.zip,
815 containing the new hboot firmware and a text file describing which
816 devices it would work for.
</p
>
818 <p
>Next, I needed to get the new firmware into the device. For this I
819 followed some instructions
820 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
821 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
822 machine with Debian testing:
</p
>
825 adb reboot-bootloader
826 fastboot oem rebootRUU
827 fastboot flash zip rom.zip
828 fastboot flash zip rom.zip
830 </pre
></p
>
832 <p
>The flash command apparently need to be done twice to take effect,
833 as the first is just preparations and the second one do the flashing.
834 The adb command is just to get to the boot loader menu, so turning the
835 device on while holding volume down and the power button should work
838 <p
>With the new hboot version in place I could start following the
839 instructions on the HTC developer web site. I got the device token
843 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
846 <p
>And once I got the unlock code via email, I could use it like
850 fastboot flash unlocktoken Unlock_code.bin
851 </pre
></p
>
853 <p
>And with that final step in place, the phone was unlocked and I
854 could start stuffing the software of my own choosing into the device.
855 So far I only inserted a replacement recovery image to wipe the phone
856 before I start. We will see what happen next. Perhaps I should
857 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
862 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
863 <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>
864 <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>
865 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
866 <description><p
>For a while now, I have wanted to test
867 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
868 said to provide end to end encrypted communication and several of my
869 friends and family are already using it. As I by choice do not own a
870 mobile phone, this proved to be harder than expected. And I wanted to
871 have the source of the client and know that it was the code used on my
872 machine. But yesterday I managed to get it working. I used the
873 Github source, compared it to the source in
874 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
875 Signal Chrome app
</a
> available from the Chrome web store, applied
876 patches to use the production Signal servers, started the app and
877 asked for the hidden
"register without a smart phone
" form. Here is
878 the recipe how I did it.
</p
>
880 <p
>First, I fetched the Signal desktop source from Github, using
883 git clone https://github.com/WhisperSystems/Signal-Desktop.git
886 <p
>Next, I patched the source to use the production servers, to be
887 able to talk to other Signal users:
</p
>
890 cat
&lt;
&lt;EOF | patch -p0
891 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
892 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
893 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
898 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
899 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
900 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
901 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
903 window.getSocketStatus = function() {
904 if (messageReceiver) {
905 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
906 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
907 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
910 'use strict
';
911 - var BUILD_EXPIRATION =
0;
912 + var BUILD_EXPIRATION =
1474492690000;
914 window.extension = window.extension || {};
919 <p
>The first part is changing the servers, and the second is updating
920 an expiration timestamp. This timestamp need to be updated regularly.
921 It is set
90 days in the future by the build process (Gruntfile.js).
922 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
924 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
925 script to launch Signal in Chromium.
</p
>
932 --proxy-server=
"socks://localhost:
9050" \
933 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
936 <p
> The script start the app and configure Chromium to use the Tor
937 SOCKS5 proxy to make sure those controlling the Signal servers (today
938 Amazon and Whisper Systems) as well as those listening on the lines
939 will have a harder time location my laptop based on the Signal
940 connections if they use source IP address.
</p
>
942 <p
>When the script starts, one need to follow the instructions under
943 "Standalone Registration
" in the CONTRIBUTING.md file in the git
944 repository. I right clicked on the Signal window to get up the
945 Chromium debugging tool, visited the
'Console
' tab and wrote
946 'extension.install(
"standalone
")
' on the console prompt to get the
947 registration form. Then I entered by land line phone number and
948 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
949 repeated the verification code three times. After entering the number
950 into the verification code field in the form, I could start using
951 Signal from my laptop.
953 <p
>As far as I can tell, The Signal app will leak who is talking to
954 whom and thus who know who to those controlling the central server,
955 but such leakage is hard to avoid with a centrally controlled server
956 setup. It is something to keep in mind when using Signal - the
957 content of your chats are harder to intercept, but the meta data
958 exposing your contact network is available to people you do not know.
959 So better than many options, but not great. And sadly the usage is
960 connected to my land line, thus allowing those controlling the server
961 to associate it to my home and person. I would prefer it if only
962 those I knew could tell who I was on Signal. There are options
963 avoiding such information leakage, but most of my friends are not
964 using them, so I am stuck with Signal for now.
</p
>
969 <title>The new
"best
" multimedia player in Debian?
</title>
970 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
971 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
972 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
973 <description><p
>When I set out a few weeks ago to figure out
974 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
975 multimedia player in Debian claimed to support most file formats /
976 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
977 the various players claimed support for. The range was from
55 to
130
978 MIME types. I suspect most media formats are supported by all
979 players, but this is not really reflected in the MimeTypes values in
980 their desktop files. There are probably also some bogus MIME types
981 listed, but it is hard to identify which one this is.
</p
>
983 <p
>Anyway, in the mean time I got in touch with upstream for some of
984 the players suggesting to add more MIME types to their desktop files,
985 and decided to spend some time myself improving the situation for my
986 favorite media player VLC. The fixes for VLC entered Debian unstable
987 yesterday. The complete list of MIME types can be seen on the
988 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
989 player MIME type support status
</a
> Debian wiki page.
</p
>
991 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
992 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
993 kmplayer. I am sure some of the other players desktop files support
994 several of the formats currently listed as working only with vlc,
995 toten and parole.
</p
>
997 <p
>A sad observation is that only
14 MIME types are listed as
998 supported by all the tested multimedia players in Debian in their
999 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1000 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1001 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1002 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1003 it sad that video/ogg and video/webm is not supported by all the media
1004 players in Debian. As far as I can tell, all of them can handle both
1010 <title>A program should be able to open its own files on Linux
</title>
1011 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1012 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1013 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1014 <description><p
>Many years ago, when koffice was fresh and with few users, I
1015 decided to test its presentation tool when making the slides for a
1016 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1017 wrote the first draft of the slides, saved the result and went to bed
1018 the day before I would give the talk. The next day I took a plane to
1019 the location where the meeting should take place, and on the plane I
1020 started up koffice again to polish the talk a bit, only to discover
1021 that kpresenter refused to load its own data file. I cursed a bit and
1022 started making the slides again from memory, to have something to
1023 present when I arrived. I tested that the saved files could be
1024 loaded, and the day seemed to be rescued. I continued to polish the
1025 slides until I suddenly discovered that the saved file could no longer
1026 be loaded into kpresenter. In the end I had to rewrite the slides
1027 three times, condensing the content until the talk became shorter and
1028 shorter. After the talk I was able to pinpoint the problem
&ndash;
1029 kpresenter wrote inline images in a way itself could not understand.
1030 Eventually that bug was fixed and kpresenter ended up being a great
1031 program to make slides. The point I
'm trying to make is that we
1032 expect a program to be able to load its own data files, and it is
1033 embarrassing to its developers if it can
't.
</p
>
1035 <p
>Did you ever experience a program failing to load its own data
1036 files from the desktop file browser? It is not a uncommon problem. A
1037 while back I discovered that the screencast recorder
1038 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1039 browser would refuse to open. No video player claimed to understand
1040 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1041 returning the application/ogg MIME type, which no video player I had
1042 installed listed as a MIME type they would understand. I asked for
1043 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1044 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1045 several video players to add video/ogg to their desktop files, to give
1046 the file browser an idea what to do about Ogg Theora files. After a
1047 while, the desktop file browsers in Debian started to handle the
1048 output from gtk-recordmydesktop properly.
</p
>
1050 <p
>But history repeats itself. A few days ago I tested the music
1051 system Rosegarden again, and I discovered that the KDE and xfce file
1052 browsers did not know what to do with the Rosegarden project files
1053 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1054 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1055 included in the next upload. To increase the chance of me remembering
1056 how to fix the problem next time some program fail to load its files
1057 from the file browser, here are some notes on how to fix it.
</p
>
1059 <p
>The file browsers in Debian in general operates on MIME types.
1060 There are two sources for the MIME type of a given file. The output from
1061 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1062 shared MIME type registry (under /usr/share/mime/). The file MIME
1063 type is mapped to programs supporting the MIME type, and this
1064 information is collected from
1065 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1066 desktop files
</a
> available in /usr/share/applications/. If there is
1067 one desktop file claiming support for the MIME type of the file, it is
1068 activated when asking to open a given file. If there are more, one
1069 can normally select which one to use by right-clicking on the file and
1070 selecting the wanted one using
'Open with
' or similar. In general
1071 this work well. But it depend on each program picking a good MIME
1073 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1074 MIME type registered with IANA
</a
>), file and/or the shared MIME
1075 registry recognizing the file and the desktop file to list the MIME
1076 type in its list of supported MIME types.
</p
>
1078 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1079 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1080 Shared MIME database
</a
> look like this:
</p
>
1082 <p
><blockquote
><pre
>
1083 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1084 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1085 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1086 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1087 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1088 &lt;glob pattern=
"*.rg
"/
&gt;
1089 &lt;/mime-type
&gt;
1090 &lt;/mime-info
&gt;
1091 </pre
></blockquote
></p
>
1093 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1094 (it is a gzipped XML file). Note, it is much better to use an
1095 official MIME type registered with IANA than it is to make up ones own
1096 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1098 <p
>The desktop file of the rosegarden program failed to list
1099 audio/x-rosegarden in its list of supported MIME types, causing the
1100 file browsers to have no idea what to do with *.rg files:
</p
>
1102 <p
><blockquote
><pre
>
1103 % grep Mime /usr/share/applications/rosegarden.desktop
1104 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1105 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1107 </pre
></blockquote
></p
>
1109 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1110 MimeType= line.
</p
>
1112 <p
>If you run into a file which fail to open the correct program when
1113 selected from the file browser, please check out the output from
1114 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1115 MIME type is registered somewhere under /usr/share/mime/ and check
1116 that some desktop file under /usr/share/applications/ is claiming
1117 support for this MIME type. If not, please report a bug to have it
1123 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1124 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1125 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1126 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1127 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1128 system
</a
> is a user-focused solution in Debian for handling hardware
1129 related packages. The idea is to have a database of mappings between
1130 hardware and packages, and pop up a dialog suggesting for the user to
1131 install the packages to use a given hardware dongle. Some use cases
1132 are when you insert a Yubikey, it proposes to install the software
1133 needed to control it; when you insert a braille reader list it
1134 proposes to install the packages needed to send text to the reader;
1135 and when you insert a ColorHug screen calibrator it suggests to
1136 install the driver for it. The system work well, and even have a few
1137 command line tools to install firmware packages and packages for the
1138 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1140 <p
>The system was initially written using aptdaemon, because I found
1141 good documentation and example code on how to use it. But aptdaemon
1142 is going away and is generally being replaced by
1143 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1144 so Isenkram needed a rewrite. And today, thanks to the great patch
1145 from my college Sunil Mohan Adapa in the FreedomBox project, the
1146 rewrite finally took place. I
've just uploaded a new version of
1147 Isenkram into Debian Unstable with the patch included, and the default
1148 for the background daemon is now to use PackageKit. To check it out,
1149 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1150 and see if it is recognised.
</p
>
1152 <p
>If you want to know what kind of packages isenkram would propose for
1153 the machine it is running on, you can check out the isenkram-lookup
1154 program. This is what it look like on a Thinkpad X230:
</p
>
1156 <p
><blockquote
><pre
>
1172 </pre
></blockquote
></p
>
1174 <p
>The hardware mappings come from several places. The preferred way
1175 is for packages to announce their hardware support using
1176 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1177 cross distribution appstream system
</a
>.
1179 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1180 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1185 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1186 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1187 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1188 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1189 <description><p
>Yesterday I updated the
1190 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1191 package in Debian
</a
> with a few patches sent to me by skilled and
1192 enterprising users. There were some nice user and visible changes.
1193 First of all, both desktop menu entries now work. A design flaw in
1194 one of the script made the history graph fail to show up (its PNG was
1195 dumped in ~/.xsession-errors) if no controlling TTY was available.
1196 The script worked when called from the command line, but not when
1197 called from the desktop menu. I changed this to look for a DISPLAY
1198 variable or a TTY before deciding where to draw the graph, and now the
1199 graph window pop up as expected.
</p
>
1201 <p
>The next new feature is a discharge rate estimator in one of the
1202 graphs (the one showing the last few hours). New is also the user of
1203 colours showing charging in blue and discharge in red. The percentages
1204 of this graph is relative to last full charge, not battery design
1207 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1209 <p
>The other graph show the entire history of the collected battery
1210 statistics, comparing it to the design capacity of the battery to
1211 visualise how the battery life time get shorter over time. The red
1212 line in this graph is what the previous graph considers
100 percent:
1214 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1216 <p
>In this graph you can see that I only charge the battery to
80
1217 percent of last full capacity, and how the capacity of the battery is
1218 shrinking. :(
</p
>
1220 <p
>The last new feature is in the collector, which now will handle
1221 more hardware models. On some hardware, Linux power supply
1222 information is stored in /sys/class/power_supply/ACAD/, while the
1223 collector previously only looked in /sys/class/power_supply/AC/. Now
1224 both are checked to figure if there is power connected to the
1227 <p
>If you are interested in how your laptop battery is doing, please
1229 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1230 in Debian unstable, or rebuild it on Jessie to get it working on
1231 Debian stable. :) The upstream source is available from
<a
1232 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1233 Patches are very welcome.
</p
>
1235 <p
>As usual, if you use Bitcoin and want to show your support of my
1236 activities, please send Bitcoin donations to my address
1237 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1242 <title>Debian now with ZFS on Linux included
</title>
1243 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1244 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1245 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1246 <description><p
>Today, after many years of hard work from many people,
1247 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1248 Debian. The package status can be seen on
1249 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1250 for zfs-linux
</a
>. and
1251 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1252 team status page
</a
>. If you want to help out, please join us.
1253 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1254 source code
</a
> is available via git on Alioth. It would also be
1255 great if you could help out with
1256 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1257 it is an important piece of the puzzle to get ZFS working.
</p
>
1262 <title>What is the best multimedia player in Debian?
</title>
1263 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1264 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1265 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1266 <description><p
><strong
>Where I set out to figure out which multimedia player in
1267 Debian claim support for most file formats.
</strong
></p
>
1269 <p
>A few years ago, I had a look at the media support for Browser
1270 plugins in Debian, to get an idea which plugins to include in Debian
1271 Edu. I created a script to extract the set of supported MIME types
1272 for each plugin, and used this to find out which multimedia browser
1273 plugin supported most file formats / media types.
1274 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1275 result
</a
> can still be seen on the Debian wiki, even though it have
1276 not been updated for a while. But browser plugins are less relevant
1277 these days, so I thought it was time to look at standalone
1280 <p
>A few days ago I was tired of VLC not being listed as a viable
1281 player when I wanted to play videos from the Norwegian National
1282 Broadcasting Company, and decided to investigate why. The cause is a
1283 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1284 desktop file
</a
>. In the process I wrote a script to compare the set
1285 of MIME types announced in the desktop file and the browser plugin,
1286 only to discover that there is quite a large difference between the
1287 two for VLC. This discovery made me dig up the script I used to
1288 compare browser plugins, and adjust it to compare desktop files
1289 instead, to try to figure out which multimedia player in Debian
1290 support most file formats.
</p
>
1292 <p
>The result can be seen on the Debian Wiki, as
1293 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1294 table listing all MIME types supported by one of the packages included
1295 in the table
</a
>, with the package supporting most MIME types being
1296 listed first in the table.
</p
>
1298 </p
>The best multimedia player in Debian? It is totem, followed by
1299 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1300 kmplayer. Time for the other players to update their announced MIME
1306 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1307 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1308 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1309 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1310 <description>A friend of mine made me aware of
1311 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1312 handheld computer which will be delivered with Debian preinstalled. I
1313 would love to get one of those for my birthday. :)
</p
>
1315 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1316 plugs and many others connectors, and include a full keyboard and a
5"
1317 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1318 day of battery life time, but I have not seen any independent tests
1319 confirming this. The vendor is still collecting preorders, and the
1320 last I heard last night was that
22 more orders were needed before
1321 production started.
</p
>
1323 <p
>As far as I know, this is the first handheld preinstalled with
1324 Debian. Please let me know if you know of any others. Is it the
1325 first computer being sold with Debian preinstalled?
</p
>
1330 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1331 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1333 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1334 <description><p
>During this weekends
1335 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1336 squashing party and developer gathering
</a
>, we decided to do our part
1337 to make sure there are good books about Debian available in Norwegian
1338 Bokmål, and got in touch with the people behind the
1339 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1340 project
</a
> to get started. If you want to help out, please start
1342 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1343 hosted weblate project page
</a
>, and get in touch using
1344 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1345 translators mailing list
</a
>. Please also check out
1346 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1347 contributors
</a
>.
</p
>
1349 <p
>The book is already available on paper in English, French and
1350 Japanese, and our goal is to get it available on paper in Norwegian
1351 Bokmål too. In addition to the paper edition, there are also EPUB and
1352 Mobi versions available. And there are incomplete translations
1353 available for many more languages.
</p
>
1358 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1359 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1360 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1361 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1362 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1363 packages in Debian, and was quite surprised with what I found. I use
1364 ZFS myself at home, but did not really expect many others to do so.
1365 But I might be wrong.
</p
>
1367 <p
>According to
1368 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1369 results for spl-linux
</a
>, there are
1019 Debian installations, or
1370 0.53% of the population, with the package installed. As far as I know
1371 the only use of the spl-linux package is as a support library for ZFS
1372 on Linux, so I use it here as proxy for measuring the number of ZFS
1373 installation on Linux in Debian. In the kFreeBSD variant of Debian
1374 the ZFS feature is already available, and there
1375 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1376 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1377 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1379 <p
>But even though the Debian project leader Lucas Nussbaum
1380 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1381 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1382 cleared, the package is still not in Debian. The package is again in
1383 the NEW queue. Several uploads have been rejected so far because the
1384 debian/copyright file was incomplete or wrong, but there is no reason
1385 to give up. The current status can be seen on
1386 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1387 team status page
</a
>, and
1388 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1389 source code
</a
> is available on Alioth.
</p
>
1391 <p
>As I want ZFS to be included in next version of Debian to make sure
1392 my home server can function in the future using only official Debian
1393 packages, and the current blocker is to get the debian/copyright file
1394 accepted by the FTP masters in Debian, I decided a while back to try
1395 to help out the team. This was the background for my blog post about
1396 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1397 updating and checking debian/copyright semi-automatically
</a
>, and I
1398 used the techniques I explored there to try to find any errors in the
1399 copyright file. It is not very easy to check every one of the around
1400 2000 files in the source package, but I hope we this time got it
1401 right. If you want to help out, check out the git source and try to
1402 find missing entries in the debian/copyright file.
</p
>
1407 <title>Full battery stats collector is now available in Debian
</title>
1408 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1409 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1410 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1411 <description><p
>Since this morning, the battery-stats package in Debian include an
1412 extended collector that will collect the complete battery history for
1413 later processing and graphing. The original collector store the
1414 battery level as percentage of last full level, while the new
1415 collector also record battery vendor, model, serial number, design
1416 full level, last full level and current battery level. This make it
1417 possible to predict the lifetime of the battery as well as visualise
1418 the energy flow when the battery is charging or discharging.
</p
>
1420 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1421 in the version
0.5.1 package in unstable. Get the new battery level graph
1422 and lifetime prediction by running:
1424 <p
><pre
>
1425 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1426 </pre
></p
>
1428 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1430 <p
>The flow in/out of the battery can be seen by running (no menu
1431 entry yet):
</p
>
1433 <p
><pre
>
1434 /usr/share/battery-stats/battery-stats-graph-flow
1435 </pre
></p
>
1437 <p
>I
'm not quite happy with the way the data is visualised, at least
1438 when there are few data points. The graphs look a bit better with a
1439 few years of data.
</p
>
1441 <p
>A while back one important feature I use in the battery stats
1442 collector broke in Debian. The scripts in
1443 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1444 suspect it happened when Jessie started using systemd, but I do not
1445 know. The issue is reported as
1446 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1447 pm-utils. I managed to work around it by adding an udev rule to call
1448 the collector script every time the power connector is connected and
1449 disconnected. With this fix in place it was finally time to make a
1450 new release of the package, and get it into Debian.
</p
>
1452 <p
>If you are interested in how your laptop battery is doing, please
1454 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1455 in Debian unstable, or rebuild it on Jessie to get it working on
1456 Debian stable. :) The upstream source is available from
1457 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1458 As always, patches are very welcome.
</p
>
1463 <title>Making battery measurements a little easier in Debian
</title>
1464 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1465 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1466 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1467 <description><p
>Back in September, I blogged about
1468 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1469 system I wrote to collect statistics about my laptop battery
</a
>, and
1470 how it showed the decay and death of this battery (now replaced). I
1471 created a simple deb package to handle the collection and graphing,
1472 but did not want to upload it to Debian as there were already
1473 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1474 package in Debian
</a
> that should do the same thing, and I did not see
1475 a point of uploading a competing package when battery-stats could be
1476 fixed instead. I reported a few bugs about its non-function, and
1477 hoped someone would step in and fix it. But no-one did.
</p
>
1479 <p
>I got tired of waiting a few days ago, and took matters in my own
1480 hands. The end result is that I am now the new upstream developer of
1481 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1482 battery-stats in Debian, and the package in Debian unstable is finally
1483 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1484 information provided by the Linux kernel. If you install the
1485 battery-stats package from unstable now, you will be able to get a
1486 graph of the current battery fill level, to get some idea about the
1487 status of the battery. The source package build and work just fine in
1488 Debian testing and stable (and probably oldstable too, but I have not
1489 tested). The default graph you get for that system look like this:
</p
>
1491 <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
>
1493 <p
>My plans for the future is to merge my old scripts into the
1494 battery-stats package, as my old scripts collected a lot more details
1495 about the battery. The scripts are merged into the upstream
1496 battery-stats git repository already, but I am not convinced they work
1497 yet, as I changed a lot of paths along the way. Will have to test a
1498 bit more before I make a new release.
</p
>
1500 <p
>I will also consider changing the file format slightly, as I
1501 suspect the way I combine several values into one field might make it
1502 impossible to know the type of the value when using it for processing
1503 and graphing.
</p
>
1505 <p
>If you would like I would like to keep an close eye on your laptop
1506 battery, check out the battery-stats package in
1507 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1509 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1510 I would love some help to improve the system further.
</p
>
1515 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1516 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1517 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1518 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1519 <description><p
>Making packages for Debian requires quite a lot of attention to
1520 details. And one of the details is the content of the
1521 debian/copyright file, which should list all relevant licenses used by
1522 the code in the package in question, preferably in
1523 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1524 readable DEP5 format
</a
>.
</p
>
1526 <p
>For large packages with lots of contributors it is hard to write
1527 and update this file manually, and if you get some detail wrong, the
1528 package is normally rejected by the ftpmasters. So getting it right
1529 the first time around get the package into Debian faster, and save
1530 both you and the ftpmasters some work.. Today, while trying to figure
1531 out what was wrong with
1532 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1533 zfsonlinux copyright file
</a
>, I decided to spend some time on
1534 figuring out the options for doing this job automatically, or at least
1535 semi-automatically.
</p
>
1537 <p
>Lucikly, there are at least two tools available for generating the
1538 file based on the code in the source package,
1539 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1540 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1541 not sure which one of them came first, but both seem to be able to
1542 create a sensible draft file. As far as I can tell, none of them can
1543 be trusted to get the result just right, so the content need to be
1544 polished a bit before the file is OK to upload. I found the debmake
1546 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1547 blog posts from
2014</a
>.
1549 <p
>To generate using debmake, use the -cc option:
1551 <p
><pre
>
1552 debmake -cc
> debian/copyright
1553 </pre
></p
>
1555 <p
>Note there are some problems with python and non-ASCII names, so
1556 this might not be the best option.
</p
>
1558 <p
>The cme option is based on a config parsing library, and I found
1560 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1561 blog post from
2015</a
>. To generate using cme, use the
'update
1562 dpkg-copyright
' option:
1564 <p
><pre
>
1565 cme update dpkg-copyright
1566 </pre
></p
>
1568 <p
>This will create or update debian/copyright. The cme tool seem to
1569 handle UTF-
8 names better than debmake.
</p
>
1571 <p
>When the copyright file is created, I would also like some help to
1572 check if the file is correct. For this I found two good options,
1573 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1574 to focus on license types and file matching, and is able to detect
1575 ineffective blocks in the copyright file. The latter reports missing
1576 copyright holders and years, but was confused by inconsistent license
1577 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1578 fix all issues reported by them before uploading. But I do not know
1579 if the tools and the ftpmasters agree on what is important to fix in a
1580 copyright file, so the package might still be rejected.
</p
>
1582 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1583 will read through the source and try to find all copyright statements.
1584 It is not comparing the result to the content of debian/copyright, but
1585 can be useful when verifying the content of the copyright file.
</p
>
1587 <p
>Are you aware of better tools in Debian to create and update
1588 debian/copyright file. Please let me know, or blog about it on
1589 planet.debian.org.
</p
>
1591 <p
>As usual, if you use Bitcoin and want to show your support of my
1592 activities, please send Bitcoin donations to my address
1593 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1595 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1596 on how to use licensecheck and cdbs to create a draft copyright file
1598 <p
><pre
>
1599 licensecheck --copyright -r `find * -type f` | \
1600 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1601 </pre
></p
>
1603 <p
>He mentioned that he normally check the generated file into the
1604 version control system to make it easier to discover license and
1605 copyright changes in the upstream source. I will try to do the same
1606 with my packages in the future.
</p
>
1608 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1609 against using -quiet for new users, so I removed it from the proposed
1610 command line.
</p
>
1615 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1616 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1618 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1619 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1620 is taking shape in Debian, and one provided feature is a very
1621 convenient way to tell you which package to install to make a given
1622 firmware file available when the kernel is looking for it. This can
1623 be done using apt-file too, but that is for someone else to blog
1626 <p
>Here is a small recipe to find the package with a given firmware
1627 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1628 picked from the set of firmware announced using appstream in Debian
1629 unstable. In general you would be looking for the firmware requested
1630 by the kernel during kernel module loading. To find the package
1631 providing the example file, do like this:
</p
>
1633 <blockquote
><pre
>
1634 % apt install appstream
1638 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1639 awk
'/Package:/ {print $
2}
'
1642 </pre
></blockquote
>
1644 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1645 appstream wiki
</a
> page to learn how to embed the package metadata in
1646 a way appstream can use.
</p
>
1648 <p
>This same approach can be used to find any package supporting a
1649 given MIME type. This is very useful when you get a file you do not
1650 know how to handle. First find the mime type using
<tt
>file
1651 --mime-type
</tt
>, and next look up the package providing support for
1652 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1653 and you can find all packages handling this type like this:
</p
>
1655 <blockquote
><pre
>
1656 % apt install appstream
1660 % appstreamcli what-provides mimetype image/svg+xml | \
1661 awk
'/Package:/ {print $
2}
'
1683 </pre
></blockquote
>
1685 <p
>I believe the MIME types are fetched from the desktop file for
1686 packages providing appstream metadata.
</p
>
1691 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1692 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1693 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1694 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1695 <description><p
>Most people seem not to realise that every time they walk around
1696 with the computerised radio beacon known as a mobile phone their
1697 position is tracked by the phone company and often stored for a long
1698 time (like every time a SMS is received or sent). And if their
1699 computerised radio beacon is capable of running programs (often called
1700 mobile apps) downloaded from the Internet, these programs are often
1701 also capable of tracking their location (if the app requested access
1702 during installation). And when these programs send out information to
1703 central collection points, the location is often included, unless
1704 extra care is taken to not send the location. The provided
1705 information is used by several entities, for good and bad (what is
1706 good and bad, depend on your point of view). What is certain, is that
1707 the private sphere and the right to free movement is challenged and
1708 perhaps even eradicated for those announcing their location this way,
1709 when they share their whereabouts with private and public
1712 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1714 <p
>The phone company logs provide a register of locations to check out
1715 when one want to figure out what the tracked person was doing. It is
1716 unavailable for most of us, but provided to selected government
1717 officials, company staff, those illegally buying information from
1718 unfaithful servants and crackers stealing the information. But the
1719 public information can be collected and analysed, and a free software
1720 tool to do so is called
1721 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1722 discovered it when I read
1723 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1724 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1725 November
2014, and decided to check if it was available in Debian.
1726 The python program was in Debian, but
1727 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1728 Debian
</a
> was completely broken and practically unmaintained. I
1729 uploaded a new version which did not work quite right, but did not
1730 have time to fix it then. This Christmas I decided to finally try to
1731 get Creepy operational in Debian. Now a fixed version is available in
1732 Debian unstable and testing, and almost all Debian specific patches
1734 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1736 <p
>The Creepy program visualises geolocation information fetched from
1737 Twitter, Instagram, Flickr and Google+, and allow one to get a
1738 complete picture of every social media message posted recently in a
1739 given area, or track the movement of a given individual across all
1740 these services. Earlier it was possible to use the search API of at
1741 least some of these services without identifying oneself, but these
1742 days it is impossible. This mean that to use Creepy, you need to
1743 configure it to log in as yourself on these services, and provide
1744 information to them about your search interests. This should be taken
1745 into account when using Creepy, as it will also share information
1746 about yourself with the services.
</p
>
1748 <p
>The picture above show the twitter messages sent from (or at least
1749 geotagged with a position from) the city centre of Oslo, the capital
1750 of Norway. One useful way to use Creepy is to first look at
1751 information tagged with an area of interest, and next look at all the
1752 information provided by one or more individuals who was in the area.
1753 I tested it by checking out which celebrity provide their location in
1754 twitter messages by checkout out who sent twitter messages near a
1755 Norwegian TV station, and next could track their position over time,
1756 making it possible to locate their home and work place, among other
1757 things. A similar technique have been
1758 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
1759 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
1760 tool to discover lying governments, and a useful tool to help people
1761 understand the value of the private information they provide to the
1764 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
1765 it depend on several python modules currently missing in Jessie (at
1766 least python-instagram, python-flickrapi and
1767 python-requests-toolbelt).
</p
>
1769 <p
>(I have uploaded
1770 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1771 screenshots.debian.net
</a
> and licensed it under the same terms as the
1772 Creepy program in Debian.)
</p
>
1777 <title>Always download Debian packages using Tor - the simple recipe
</title>
1778 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1780 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1781 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1782 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1783 that those listening on the Internet lines would have good reason to
1784 believe a computer have a given security hole
</a
> if it download a
1785 security fix from a Debian mirror. This is a good reason to always
1786 use encrypted connections to the Debian mirror, to make sure those
1787 listening do not know which IP address to attack. In August, Richard
1788 Hartmann observed that encryption was not enough, when it was possible
1789 to interfere download size to security patches or the fact that
1790 download took place shortly after a security fix was released, and
1791 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1792 to always use Tor to download packages from the Debian mirror
</a
>. He
1793 was not the first to propose this, as the
1794 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1795 package by Tim Retout already existed to make it easy to convince apt
1796 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1797 aware of that package when I read the blog post from Richard.
</p
>
1799 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1800 sysadmins, and he set up a Tor hidden service on one of the central
1801 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1802 it possible to download packages directly between two tor nodes,
1803 making sure the network traffic always were encrypted.
</p
>
1805 <p
>Here is a short recipe for enabling this on your machine, by
1806 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1807 urls with tor+http and tor+https, and using the hidden service instead
1808 of the official Debian mirror site. I recommend installing
1809 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1810 done in /etc/.
</p
>
1812 <blockquote
><pre
>
1813 apt install apt-transport-tor
1814 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1815 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1816 </pre
></blockquote
>
1818 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1819 the sed commands for these too. The sed command is assuming your are
1820 using the ftp.debian.org Debian mirror. Adjust the command (or just
1821 edit the file manually) to match your mirror.
</p
>
1823 <p
>This work in Debian Jessie and later. Note that tools like
1824 <tt
>apt-file
</tt
> only recently started using the apt transport
1825 system, and do not work with these tor+http URLs. For
1826 <tt
>apt-file
</tt
> you need the version currently in experimental,
1827 which need a recent apt version currently only in unstable. So if you
1828 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1830 <p
>Another advantage from this change is that your machine will start
1831 using Tor regularly and at fairly random intervals (every time you
1832 update the package lists or upgrade or install a new package), thus
1833 masking other Tor traffic done from the same machine. Using Tor will
1834 become normal for the machine in question.
</p
>
1836 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1837 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1838 enabled. It would be great if it was the default on any Debian
1844 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1845 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1846 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1847 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1848 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1849 call the car license plate numbers in those days. I would write the
1850 numbers down in my little book and compare notes with the other kids
1851 to see how many region codes we had seen and if we had seen some
1852 exotic or special region codes and numbers. It was a fun game to pass
1853 time, as we kids have plenty of it.
</p
>
1855 <p
>A few days I came across
1856 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1857 project
</a
>, a free software project to automatically discover and
1858 report license plates in images and video streams, and provide the
1859 "car numbers
" in a machine readable format. I
've been looking for
1860 such system for a while now, because I believe it is a bad idea that the
1861 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1862 number plate recognition
</a
> tool only is available in the hands of
1863 the powerful, and want it to be available also for the powerless to
1864 even the score when it comes to surveillance and sousveillance. I
1865 discovered the developer
1866 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1867 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1868 help him get it into shape to get the package uploaded into the Debian
1871 <p
>Today we finally managed to get the package into shape and uploaded
1872 it into Debian, where it currently
1873 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1874 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1876 <p
>I guess you are wondering why on earth such tool would be useful
1877 for the common folks, ie those not running a large government
1878 surveillance system? Well, I plan to put it in a computer on my bike
1879 and in my car, tracking the cars nearby and allowing me to be notified
1880 when number plates on my watch list are discovered. Another use case
1881 was suggested by a friend of mine, who wanted to set it up at his home
1882 to open the car port automatically when it discovered the plate on his
1883 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1884 capable of placing his license plate number of a piece of cardboard to
1885 open his car port, men replied that it was always unlocked anyway. I
1886 guess for such use case it make sense. I am sure there are other use
1887 cases too, for those with imagination and a vision.
</p
>
1889 <p
>If you want to build your own version of the Debian package, check
1890 out the upstream git source and symlink ./distros/debian to ./debian/
1891 before running
"debuild
" to build the source. Or wait a bit until the
1892 package show up in unstable.
</p
>
1897 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1898 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1899 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1900 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1901 <description><p
>Around three years ago, I created
1902 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1903 system
</a
> to get a more practical solution in Debian for handing
1904 hardware related packages. A GUI system in the isenkram package will
1905 present a pop-up dialog when some hardware dongle supported by
1906 relevant packages in Debian is inserted into the machine. The same
1907 lookup mechanism to detect packages is available as command line
1908 tools in the isenkram-cli package. In addition to mapping hardware,
1909 it will also map kernel firmware files to packages and make it easy to
1910 install needed firmware packages automatically. The key for this
1911 system to work is a good way to map hardware to packages, in other
1912 words, allow packages to announce what hardware they will work
1915 <p
>I started by providing data files in the isenkram source, and
1916 adding code to download the latest version of these data files at run
1917 time, to ensure every user had the most up to date mapping available.
1918 I also added support for storing the mapping in the Packages file in
1919 the apt repositories, but did not push this approach because while I
1920 was trying to figure out how to best store hardware/package mappings,
1921 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
1922 appstream system
</a
> was announced. I got in touch and suggested to
1923 add the hardware mapping into that data set to be able to use
1924 appstream as a data source, and this was accepted at least for the
1925 Debian version of appstream.
</p
>
1927 <p
>A few days ago using appstream in Debian for this became possible,
1928 and today I uploaded a new version
0.20 of isenkram adding support for
1929 appstream as a data source for mapping hardware to packages. The only
1930 package so far using appstream to announce its hardware support is my
1931 pymissile package. I got help from Matthias Klumpp with figuring out
1932 how do add the required
1933 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
1934 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
1935 this content:
</p
>
1937 <blockquote
><pre
>
1938 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1939 &lt;component
&gt;
1940 &lt;id
&gt;pymissile
&lt;/id
&gt;
1941 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
1942 &lt;name
&gt;pymissile
&lt;/name
&gt;
1943 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
1944 &lt;description
&gt;
1946 Pymissile provides a curses interface to control an original
1947 Marks and Spencer / Striker USB Missile Launcher, as well as a
1948 motion control script to allow a webcamera to control the
1951 &lt;/description
&gt;
1952 &lt;provides
&gt;
1953 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
1954 &lt;/provides
&gt;
1955 &lt;/component
&gt;
1956 </pre
></blockquote
>
1958 <p
>The key for isenkram is the component/provides/modalias value,
1959 which is a glob style match rule for hardware specific strings
1960 (modalias strings) provided by the Linux kernel. In this case, it
1961 will map to all USB devices with vendor code
1130 and product code
1964 <p
>Note, it is important that the license of all the metadata files
1965 are compatible to have permissions to aggregate them into archive wide
1966 appstream files. Matthias suggested to use MIT or BSD licenses for
1967 these files. A challenge is figuring out a good id for the data, as
1968 it is supposed to be globally unique and shared across distributions
1969 (in other words, best to coordinate with upstream what to use). But
1970 it can be changed later or, so we went with the package name as
1971 upstream for this project is dormant.
</p
>
1973 <p
>To get the metadata file installed in the correct location for the
1974 mirror update scripts to pick it up and include its content the
1975 appstream data source, the file must be installed in the binary
1976 package under /usr/share/appdata/. I did this by adding the following
1977 line to debian/pymissile.install:
</p
>
1979 <blockquote
><pre
>
1980 debian/pymissile.metainfo.xml usr/share/appdata
1981 </pre
></blockquote
>
1983 <p
>With that in place, the command line tool isenkram-lookup will list
1984 all packages useful on the current computer automatically, and the GUI
1985 pop-up handler will propose to install the package not already
1986 installed if a hardware dongle is inserted into the machine in
1989 <p
>Details of the modalias field in appstream is available from the
1990 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
1992 <p
>To locate the modalias values of all hardware present in a machine,
1993 try running this command on the command line:
</p
>
1995 <blockquote
><pre
>
1996 cat $(find /sys/devices/|grep modalias)
1997 </pre
></blockquote
>
1999 <p
>To learn more about the isenkram system, please check out
2000 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2001 blog posts tagged isenkram
</a
>.
</p
>
2006 <title>The GNU General Public License is not magic pixie dust
</title>
2007 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2008 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2009 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2010 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2011 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2012 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2013 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2014 I quote the blog post from Paul in full here with his permission:
<p
>
2018 <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
>
2021 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2023 The first step is to choose a
2024 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2027 The next step is, when someone fails to follow that copyleft license,
2028 <b
>it must be enforced
</b
><br/
>
2030 and its a simple fact of our modern society that such type of
2033 is incredibly expensive to do and incredibly difficult to do.
2036 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2037 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2038 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2039 0x57</a
></small
></p
>
2041 <p
>As the Debian Website
2042 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2043 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2044 imply, public domain and permissively licensed software can lead to
2045 the production of more proprietary software as people discover useful
2046 software, extend it and or incorporate it into their hardware or
2047 software products. Copyleft licenses such as the GNU GPL were created
2048 to close off this avenue to the production of proprietary software but
2049 such licenses are not enough. With the ongoing adoption of Free
2050 Software by individuals and groups, inevitably the community
's
2051 expectations of license compliance are violated, usually out of
2052 ignorance of the way Free Software works, but not always. As Karen
2053 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2054 Freedom
">FaiF
</a
>
2055 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2056 copyleft is nothing if no-one is willing and able to stand up in court
2057 to protect it. The reality of today
's world is that legal
2058 representation is expensive, difficult and time consuming. With
2059 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2060 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2061 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2062 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2063 of the Linux project, Debian and other groups against GPL violations.
2064 In March the SFC supported a
2065 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2066 by Christoph Hellwig
</a
> against VMware for refusing to
2067 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2068 with the GPL
</a
> in relation to their use of parts of the Linux
2069 kernel. Since then two of their sponsors pulled corporate funding and
2071 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2072 or cancelled their talks
</a
>. As a result they have decided to rely
2073 less on corporate funding and more on the broad community of
2074 individuals who support Free Software and copyleft. So the SFC has
2075 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2076 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2077 a community of folks who stand up for copyleft and the GPL by
2078 supporting their work on promoting and supporting copyleft and Free
2081 <p
>If you support Free Software,
2082 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2083 what the SFC do, agree with their
2084 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2085 principles
</a
>, are happy about their
2086 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2087 work on a project that is an SFC
2088 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2089 just want to stand up for copyleft, please join
2090 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2091 Allan Webber
</a
>,
2092 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2094 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2095 Bacon
</a
>, myself and
2096 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2098 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2099 next week your donation will be
2100 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2101 by an anonymous donor. Please also consider asking your employer to
2102 match your donation or become a sponsor of SFC. Don
't forget to
2103 spread the word about your support for SFC via email, your blog and or
2104 social media accounts.
</p
>
2108 <p
>I agree with Paul on this topic and just signed up as a Supporter
2109 of Software Freedom Conservancy myself. Perhaps you should be a
2110 supporter too?
</p
>
2115 <title>PGP key transition statement for key EE4E02F9
</title>
2116 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2117 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2118 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2119 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2120 set it up properly. I wanted to generate it offline and have it
2121 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2122 smart card
</a
> for daily use, and learning how to do it and finding
2123 time to sit down with an offline machine almost took forever. But
2124 finally I
've been able to complete the process, and have now moved
2125 from my old GPG key to a new GPG key. See
2126 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2127 full transition statement, signed with both my old and new key
</a
> for
2128 the details. This is my new key:
</p
>
2131 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2132 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2133 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2134 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2135 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2136 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2137 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2140 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2141 my old key.
</p
>
2143 <p
>If you signed my old key
2144 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2145 I
'd very much appreciate a signature on my new key, details and
2146 instructions in the transition statement. I m happy to reciprocate if
2147 you have a similarly signed transition statement to present.
</p
>
2152 <title>The life and death of a laptop battery
</title>
2153 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2154 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2155 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2156 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2157 But this do not last. The last few laptops gave me a feeling that
2158 within a year, the life time is just a fraction of what it used to be,
2159 and it slowly become painful to use the laptop without power connected
2160 all the time. Because of this, when I got a new Thinkpad X230 laptop
2161 about two years ago, I decided to monitor its battery state to have
2162 more hard facts when the battery started to fail.
</p
>
2164 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2166 <p
>First I tried to find a sensible Debian package to record the
2167 battery status, assuming that this must be a problem already handled
2168 by someone else. I found
2169 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2170 which collects statistics from the battery, but it was completely
2171 broken. I sent a few suggestions to the maintainer, but decided to
2172 write my own collector as a shell script while I waited for feedback
2174 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2175 blog post about the battery development on a MacBook Air
</a
> I also
2177 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2178 available in Debian.
</p
>
2180 <p
>I started my collector
2013-
07-
15, and it has been collecting
2181 battery stats ever since. Now my
2182 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2183 measurements, from the time the battery was working great until now,
2184 when it is unable to charge above
7% of original capacity. My
2185 collector shell script is quite simple and look like this:
</p
>
2190 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2192 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2193 logfile=/var/log/hjemmenett-battery-status.log
2195 files=
"manufacturer model_name technology serial_number \
2196 energy_full energy_full_design energy_now cycle_count status
"
2198 if [ ! -e
"$logfile
" ] ; then
2200 printf
"timestamp,
"
2202 printf
"%s,
" $f
2205 )
> "$logfile
"
2209 # Print complete message in one echo call, to avoid race condition
2210 # when several log processes run in parallel.
2211 msg=$(printf
"%s,
" $(date +%s); \
2212 for f in $files; do \
2213 printf
"%s,
" $(cat $f); \
2215 echo
"$msg
"
2218 cd /sys/class/power_supply
2221 (cd $bat
&& log_battery
>> "$logfile
")
2225 <p
>The script is called when the power management system detect a
2226 change in the power status (power plug in or out), and when going into
2227 and out of hibernation and suspend. In addition, it collect a value
2228 every
10 minutes. This make it possible for me know when the battery
2229 is discharging, charging and how the maximum charge change over time.
2230 The code for the Debian package
2231 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2232 available on github
</a
>.
</p
>
2234 <p
>The collected log file look like this:
</p
>
2237 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2238 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2240 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2241 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2244 <p
>I wrote a small script to create a graph of the charge development
2245 over time. This graph depicted above show the slow death of my laptop
2248 <p
>But why is this happening? Why are my laptop batteries always
2249 dying in a year or two, while the batteries of space probes and
2250 satellites keep working year after year. If we are to believe
2251 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2252 University
</a
>, the cause is me charging the battery whenever I have a
2253 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2254 all the time, but to stay below
90% of full charge most of the time.
2255 I
've been told that the Tesla electric cars
2256 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2257 the charge of their batteries to
80%
</a
>, with the option to charge to
2258 100% when preparing for a longer trip (not that I would want a car
2259 like Tesla where rights to privacy is abandoned, but that is another
2260 story), which I guess is the option we should have for laptops on
2261 Linux too.
</p
>
2263 <p
>Is there a good and generic way with Linux to tell the battery to
2264 stop charging at
80%, unless requested to charge to
100% once in
2265 preparation for a longer trip? I found
2266 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2267 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2268 80%
</a
>, but could not get it to work (kernel module refused to
2271 <p
>I wonder why the battery capacity was reported to be more than
100%
2272 at the start. I also wonder why the
"full capacity
" increases some
2273 times, and if it is possible to repeat the process to get the battery
2274 back to design capacity. And I wonder if the discharge and charge
2275 speed change over time, or if this stay the same. I did not yet try
2276 to write a tool to calculate the derivative values of the battery
2277 level, but suspect some interesting insights might be learned from
2280 <p
>Update
2015-
09-
24: I got a tip to install the packages
2281 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2282 packages instead of the tp-smapi-dkms package I had tried to use
2283 initially, and use
'tlp setcharge
40 80' to change when charging start
2284 and stop. I
've done so now, but expect my existing battery is toast
2285 and need to be replaced. The proposal is unfortunately Thinkpad
2291 <title>New laptop - some more clues and ideas based on feedback
</title>
2292 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2293 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2294 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2295 <description><p
>Several people contacted me after my previous blog post about my
2296 need for a new laptop, and provided very useful feedback. I wish to
2297 thank every one of these. Several pointed me to the possibility of
2298 fixing my X230, and I am already in the process of getting Lenovo to
2299 do so thanks to the on site, next day support contract covering the
2300 machine. But the battery is almost useless (I expect to replace it
2301 with a non-official battery) and I do not expect the machine to live
2302 for many more years, so it is time to plan its replacement. If I did
2303 not have a support contract, it was suggested to find replacement parts
2304 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2305 might present a language barrier as I do not understand French.
</p
>
2307 <p
>One tip I got was to use the
2308 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2309 compare laptop models. It seem to have more models available than
2310 prisjakt.no. Another tip I got from someone I know have similar
2311 keyboard preferences was that the HP EliteBook
840 keyboard is not
2312 very good, and this matches my experience with earlier EliteBook
2313 keyboards I tested. Because of this, I will not consider it any further.
2315 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2316 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2317 (which is missing from the X240), and is working fairly well with
2318 Debian Sid/Unstable according to
2319 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2320 got on the keyboard quality are not consistent. Some say the keyboard
2321 is good, others say it is ok, while others say it is not very good.
2322 Those with experience from X41 and and X60 agree that the X250
2323 keyboard is not as good as those trusty old laptops, and suggest I
2324 keep and fix my X230 instead of upgrading, or get a used X230 to
2325 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2326 activity and battery status, which is very convenient on my X230. I
'm
2327 also told that the CPU fan is running very often, making it a bit
2328 noisy. In any case, the X250 do not work out of the box with Debian
2329 Stable/Jessie, one of my requirements.
</p
>
2331 <p
>I have also gotten a few vendor proposals, one was
2332 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2333 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2334 The latter look very attractive to me.
</p
>
2336 <p
>Again, thank you all for the very useful feedback. It help a lot
2337 as I keep looking for a replacement.
</p
>
2339 <p
>Update
2015-
07-
06: I was recommended to check out the
2340 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2342 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2343 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2348 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2349 <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>
2350 <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>
2351 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2352 <description><p
>My primary work horse laptop is failing, and will need a
2353 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2354 started flickering yesterday, and I suspect the cause is a broken
2355 cable, as changing the angle of the screen some times get rid of the
2356 flickering.
</p
>
2358 <p
>My requirements have not really changed since I bought it, and is
2360 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2361 described them in
2013</a
>. The last time I bought a laptop, I had
2363 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2364 where I could select at least a few of the requirements (mouse pin,
2365 wifi, weight) and go through the rest manually. Three button mouse
2366 and a good keyboard is not available as an option, and all the three
2367 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2368 G2) lack three mouse buttons). It is also unclear to me how good the
2369 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2370 the keyboard, even if the quality and robustness in the X series have
2371 deteriorated since X41.
</p
>
2373 <p
>I wonder how I can find a sensible laptop when none of the options
2374 seem sensible to me? Are there better services around to search the
2375 set of available laptops for features? Please send me an email if you
2376 have suggestions.
</p
>
2378 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2379 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2380 of endorsed hardware
</a
>, which is useful background information.
</p
>
2385 <title>How to stay with sysvinit in Debian Jessie
</title>
2386 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2388 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2389 <description><p
>By now, it is well known that Debian Jessie will not be using
2390 sysvinit as its boot system by default. But how can one keep using
2391 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2393 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2394 Schubert
</a
> and
2395 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2398 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2399 keep sysvinit as your boot system, create a file
2400 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2401 you upgrade:
</p
>
2403 <p
><blockquote
><pre
>
2404 Package: systemd-sysv
2405 Pin: release o=Debian
2407 </pre
></blockquote
><p
>
2409 <p
>This file content will tell apt and aptitude to not consider
2410 installing systemd-sysv as part of any installation and upgrade
2411 solution when resolving dependencies, and thus tell it to avoid
2412 systemd as a default boot system. The end result should be that the
2413 upgraded system keep using sysvinit.
</p
>
2415 <p
>If you are installing Jessie for the first time, there is no way to
2416 get sysvinit installed by default (debootstrap used by
2417 debian-installer have no option for this), but one can tell the
2418 installer to switch to sysvinit before the first boot. Either by
2419 using a kernel argument to the installer, or by adding a line to the
2420 preseed file used. First, the kernel command line argument:
2422 <p
><blockquote
><pre
>
2423 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2424 </pre
></blockquote
><p
>
2426 <p
>Next, the line to use in a preseed file:
</p
>
2428 <p
><blockquote
><pre
>
2429 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2430 </pre
></blockquote
><p
>
2432 <p
>One can of course also do this after the first boot by installing
2433 the sysvinit-core package.
</p
>
2435 <p
>I recommend only using sysvinit if you really need it, as the
2436 sysvinit boot sequence in Debian have several hardware specific bugs
2437 on Linux caused by the fact that it is unpredictable when hardware
2438 devices show up during boot. But on the other hand, the new default
2439 boot system still have a few rough edges I hope will be fixed before
2440 Jessie is released.
</p
>
2442 <p
>Update
2014-
11-
26: Inspired by
2443 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2444 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2450 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2451 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2452 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2453 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2454 <description><p
>The right to communicate with your friends and family in private,
2455 without anyone snooping, is a right every citicen have in a liberal
2456 democracy. But this right is under serious attack these days.
</p
>
2458 <p
>A while back it occurred to me that one way to make the dragnet
2459 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2460 the whisleblower Snowden) more expensive for Internet email,
2461 is to deliver all email using SMTP via Tor. Such SMTP option would be
2462 a nice addition to the FreedomBox project if we could send email
2463 between FreedomBox machines without leaking metadata about the emails
2464 to the people peeking on the wire. I
2465 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2466 this on the FreedomBox project mailing list in October
</a
> and got a
2467 lot of useful feedback and suggestions. It also became obvious to me
2468 that this was not a novel idea, as the same idea was tested and
2469 documented by Johannes Berg as early as
2006, and both
2470 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2471 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2472 propose a similar method / protocol to pass emails between users.
</p
>
2474 <p
>To implement such system one need to set up a Tor hidden service
2475 providing the SMTP protocol on port
25, and use email addresses
2476 looking like username@hidden-service-name.onion. With such addresses
2477 the connections to port
25 on hidden-service-name.onion using Tor will
2478 go to the correct SMTP server. To do this, one need to configure the
2479 Tor daemon to provide the hidden service and the mail server to accept
2480 emails for this .onion domain. To learn more about Exim configuration
2481 in Debian and test the design provided by Johannes Berg in his FAQ, I
2482 set out yesterday to create a Debian package for making it trivial to
2483 set up such SMTP over Tor service based on Debian. Getting it to work
2484 were fairly easy, and
2485 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2486 source code for the Debian package
</a
> is available from github. I
2487 plan to move it into Debian if further testing prove this to be a
2488 useful approach.
</p
>
2490 <p
>If you want to test this, set up a blank Debian machine without any
2491 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2492 get rid of exim4). Install tor, clone the git repository mentioned
2493 above, build the deb and install it on the machine. Next, run
2494 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2495 the instructions to get the service up and running. Restart tor and
2496 exim when it is done, and test mail delivery using swaks like
2499 <p
><blockquote
><pre
>
2500 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2501 --to fbx@dutlqrrmjhtfa3vp.onion
2502 </pre
></blockquote
></p
>
2504 <p
>This will test the SMTP delivery using tor. Replace the email
2505 address with your own address to test your server. :)
</p
>
2507 <p
>The setup procedure is still to complex, and I hope it can be made
2508 easier and more automatic. Especially the tor setup need more work.
2509 Also, the package include a tor-smtp tool written in C, but its task
2510 should probably be rewritten in some script language to make the deb
2511 architecture independent. It would probably also make the code easier
2512 to review. The tor-smtp tool currently need to listen on a socket for
2513 exim to talk to it and is started using xinetd. It would be better if
2514 no daemon and no socket is needed. I suspect it is possible to get
2515 exim to run a command line tool for delivery instead of talking to a
2516 socket, and hope to figure out how in a future version of this
2519 <p
>Until I wipe my test machine, I can be reached using the
2520 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2521 SMTorP. :)
</p
>
2526 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2527 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2528 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2529 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2530 <description><p
>If you ever had to moderate a mailman list, like the ones on
2531 alioth.debian.org, you know the web interface is fairly slow to
2532 operate. First you visit one web page, enter the moderation password
2533 and get a new page shown with a list of all the messages to moderate
2534 and various options for each email address. This take a while for
2535 every list you moderate, and you need to do it regularly to do a good
2536 job as a list moderator. But there is a quick alternative,
2537 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2538 listadmin program
</a
>. It allow you to check lists for new messages
2539 to moderate in a fraction of a second. Here is a test run on two
2540 lists I recently took over:
</p
>
2542 <p
><blockquote
><pre
>
2543 % time listadmin xiph
2544 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2545 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2551 </pre
></blockquote
></p
>
2553 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2554 there are no message in the moderation queue. Every morning I
2555 currently moderate
68 mailman lists, and it normally take around two
2556 minutes. When I took over the two pkg-xiph lists above a few days
2557 ago, there were
400 emails waiting in the moderator queue. It took me
2558 less than
15 minutes to process them all using the listadmin
2561 <p
>If you install
2562 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2563 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2564 with content like this, the moderation task is a breeze:
</p
>
2566 <p
><blockquote
><pre
>
2567 username username@example.org
2570 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2573 adminurl https://{domain}/mailman/admindb/{list}
2574 mailman-list@lists.example.com
2577 other-list@otherserver.example.org
2578 </pre
></blockquote
></p
>
2580 <p
>There are other options to set as well. Check the manual page to
2581 learn the details.
</p
>
2583 <p
>If you are forced to moderate lists on a mailman installation where
2584 the SSL certificate is self signed or not properly signed by a
2585 generally accepted signing authority, you can set a environment
2586 variable when calling listadmin to disable SSL verification:
</p
>
2588 <p
><blockquote
><pre
>
2589 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2590 </pre
></blockquote
></p
>
2592 <p
>If you want to moderate a subset of the lists you take care of, you
2593 can provide an argument to the listadmin script like I do in the
2594 initial screen dump (the xiph argument). Using an argument, only
2595 lists matching the argument string will be processed. This make it
2596 quick to accept messages if you notice the moderation request in your
2599 <p
>Without the listadmin program, I would never be the moderator of
68
2600 mailing lists, as I simply do not have time to spend on that if the
2601 process was any slower. The listadmin program have saved me hours of
2602 time I could spend elsewhere over the years. It truly is nice free
2605 <p
>As usual, if you use Bitcoin and want to show your support of my
2606 activities, please send Bitcoin donations to my address
2607 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2609 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2610 configuration example. Also, I
've been told that the
2611 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2617 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2618 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2620 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2621 <description><p
>When PXE installing laptops with Debian, I often run into the
2622 problem that the WiFi card require some firmware to work properly.
2623 And it has been a pain to fix this using preseeding in Debian.
2624 Normally something more is needed. But thanks to
2625 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2626 package
</a
> and its recent tasksel extension, it has now become easy
2627 to do this using simple preseeding.
</p
>
2629 <p
>The isenkram-cli package provide tasksel tasks which will install
2630 firmware for the hardware found in the machine (actually, requested by
2631 the kernel modules for the hardware). (It can also install user space
2632 programs supporting the hardware detected, but that is not the focus
2633 of this story.)
</p
>
2635 <p
>To get this working in the default installation, two preeseding
2636 values are needed. First, the isenkram-cli package must be installed
2637 into the target chroot (aka the hard drive) before tasksel is executed
2638 in the pkgsel step of the debian-installer system. This is done by
2639 preseeding the base-installer/includes debconf value to include the
2640 isenkram-cli package. The package name is next passed to debootstrap
2641 for installation. With the isenkram-cli package in place, tasksel
2642 will automatically use the isenkram tasks to detect hardware specific
2643 packages for the machine being installed and install them, because
2644 isenkram-cli contain tasksel tasks.
</p
>
2646 <p
>Second, one need to enable the non-free APT repository, because
2647 most firmware unfortunately is non-free. This is done by preseeding
2648 the apt-mirror-setup step. This is unfortunate, but for a lot of
2649 hardware it is the only option in Debian.
</p
>
2651 <p
>The end result is two lines needed in your preseeding file to get
2652 firmware installed automatically by the installer:
</p
>
2654 <p
><blockquote
><pre
>
2655 base-installer base-installer/includes string isenkram-cli
2656 apt-mirror-setup apt-setup/non-free boolean true
2657 </pre
></blockquote
></p
>
2659 <p
>The current version of isenkram-cli in testing/jessie will install
2660 both firmware and user space packages when using this method. It also
2661 do not work well, so use version
0.15 or later. Installing both
2662 firmware and user space packages might give you a bit more than you
2663 want, so I decided to split the tasksel task in two, one for firmware
2664 and one for user space programs. The firmware task is enabled by
2665 default, while the one for user space programs is not. This split is
2666 implemented in the package currently in unstable.
</p
>
2668 <p
>If you decide to give this a go, please let me know (via email) how
2669 this recipe work for you. :)
</p
>
2671 <p
>So, I bet you are wondering, how can this work. First and
2672 foremost, it work because tasksel is modular, and driven by whatever
2673 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2674 isenkram-cli package place two files for tasksel to find. First there
2675 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2677 <p
><blockquote
><pre
>
2678 Task: isenkram-packages
2680 Description: Hardware specific packages (autodetected by isenkram)
2681 Based on the detected hardware various hardware specific packages are
2683 Test-new-install: show show
2685 Packages: for-current-hardware
2687 Task: isenkram-firmware
2689 Description: Hardware specific firmware packages (autodetected by isenkram)
2690 Based on the detected hardware various hardware specific firmware
2691 packages are proposed.
2692 Test-new-install: mark show
2694 Packages: for-current-hardware-firmware
2695 </pre
></blockquote
></p
>
2697 <p
>The key parts are Test-new-install which indicate how the task
2698 should be handled and the Packages line referencing to a script in
2699 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2700 list of packages to install. The for-current-hardware-firmware script
2701 look like this to list relevant firmware for the machine:
2703 <p
><blockquote
><pre
>
2706 PATH=/usr/sbin:$PATH
2708 isenkram-autoinstall-firmware -l
2709 </pre
></blockquote
></p
>
2711 <p
>With those two pieces in place, the firmware is installed by
2712 tasksel during the normal d-i run. :)
</p
>
2714 <p
>If you want to test what tasksel will install when isenkram-cli is
2715 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2716 --new-install
</tt
> to get the list of packages that tasksel would
2719 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2720 pilots in testing this feature, as isenkram is used there now to
2721 install firmware, replacing the earlier scripts.
</p
>
2726 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2727 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2728 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2729 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2730 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2731 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2732 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2733 on a screen normally showing the bread types and prizes:
</p
>
2735 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2737 <p
>If it had booted as it was supposed to, I would never had known
2738 about this hidden Linux installation. It is interesting what
2739 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2744 <title>New lsdvd release version
0.17 is ready
</title>
2745 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2746 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2747 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2748 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
2749 got a new set of developers a few weeks ago, after the original
2750 developer decided to step down and pass the project to fresh blood.
2751 This project is now maintained by Petter Reinholdtsen and Steve
2754 <p
>I just wrapped up
2755 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
2756 new lsdvd release
</a
>, available in git or from
2757 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
2758 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
2763 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
2764 <li
>Check for garbage in the program chains, which indicate that a track is
2765 non-existant, to work around additional copy protection
</li
>
2766 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2767 <li
>Fix pallete display of first entry
</li
>
2768 <li
>Fix include orders
</li
>
2769 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2770 <li
>Fix the chapter count
</li
>
2771 <li
>Make sure the array size and the array limit used when initialising
2772 the palette size is the same.
</li
>
2773 <li
>Fix array printing.
</li
>
2774 <li
>Correct subsecond calculations.
</li
>
2775 <li
>Add sector information to the output format.
</li
>
2776 <li
>Clean up code to be closer to ANSI C and compile without warnings
2777 with more GCC compiler warnings.
</li
>
2781 <p
>This change bring together patches for lsdvd in use in various
2782 Linux and Unix distributions, as well as patches submitted to the
2783 project the last nine years. Please check it out. :)
</p
>
2788 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2789 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2790 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2791 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2792 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2793 project
</a
> provide a Linux solution for schools, including a
2794 powerful desktop with education software, a central server providing
2795 web pages, user database, user home directories, central login and PXE
2796 boot of both clients without disk and the installation to install Debian
2797 Edu on machines with disk (and a few other services perhaps to small
2798 to mention here). We in the Debian Edu team are currently working on
2799 the Jessie based version, trying to get everything in shape before the
2800 freeze, to avoid having to maintain our own package repository in the
2802 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2803 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2804 work left. Some fatal problems block testing, breaking the installer,
2805 but it is possible to work around these to get anyway. Here is a
2806 recipe on how to get the installation limping along.
</p
>
2808 <p
>First, download the test ISO via
2809 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2810 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2812 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2813 The ISO build was broken on Tuesday, so we do not get a new ISO every
2814 12 hours or so, but thankfully the ISO we already got we are able to
2815 install with some tweaking.
</p
>
2817 <p
>When you get to the Debian Edu profile question, go to tty2
2818 (use Alt-Ctrl-F2), run
</p
>
2820 <p
><blockquote
><pre
>
2821 nano /usr/bin/edu-eatmydata-install
2822 </pre
></blockquote
></p
>
2824 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2825 optimization. Return to the installation, select the profile you want
2826 and continue. Without this change, exim4-config will fail to install
2827 due to a known bug in eatmydata.
</p
>
2829 <p
>When you get the grub question at the end, answer /dev/sda (or if
2830 this do not work, figure out what your correct value would be. All my
2831 test machines need /dev/sda, so I have no advice if it do not fit
2832 your need.
</p
>
2834 <p
>If you installed a profile including a graphical desktop, log in as
2835 root after the initial boot from hard drive, and install the
2836 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2837 or mate. If you want several desktop options, install more than one
2838 metapackage. Once this is done, reboot and you should have a working
2839 graphical login screen. This workaround should no longer be needed
2840 once the education-tasks package version
1.801 enter testing in two
2843 <p
>I believe the ISO build will start working on two days when the new
2844 tasksel package enter testing and Steve McIntyre get a chance to
2845 update the debian-cd git repository. The eatmydata, grub and desktop
2846 issues are already fixed in unstable and testing, and should show up
2847 on the ISO as soon as the ISO build start working again. Well the
2848 eatmydata optimization is really just disabled. The proper fix
2849 require an upload by the eatmydata maintainer applying the patch
2850 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2851 The rest have proper fixes in unstable.
</p
>
2853 <p
>I hope this get you going with the installation testing, as we are
2854 quickly running out of time trying to get our Jessie based
2855 installation ready before the distribution freeze in a month.
</p
>
2860 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2861 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2862 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2863 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2864 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2865 to handle my fairly large DVD collection. It is a nice command line
2866 tool to get details about a DVD, like title, tracks, track length,
2867 etc, in XML, Perl or human readable format. But lsdvd have not seen
2868 any new development since
2006 and had a few irritating bugs affecting
2869 its use with some DVDs. Upstream seemed to be dead, and in January I
2870 sent a small probe asking for a version control repository for the
2871 project, without any reply. But I use it regularly and would like to
2872 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2873 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2874 the project admin, and after getting a reply from him explaining that
2875 he was no longer interested in the project, I asked if I could take
2876 over. And yesterday, I became project admin.
</p
>
2878 <p
>I
've been in touch with a Gentoo developer and the Debian
2879 maintainer interested in joining forces to maintain the upstream
2880 project, and I hope we can get a new release out fairly quickly,
2881 collecting the patches spread around on the internet into on place.
2882 I
've added the relevant Debian patches to the freshly created git
2883 repository, and expect the Gentoo patches to make it too. If you got
2884 a DVD collection and care about command line tools, check out
2885 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2886 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2887 list
</a
>. :)
</p
>
2892 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2893 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2894 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2895 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2896 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2897 a lot quicker. When we install more than
2000 packages in
2898 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2899 tasksel in the installer, unpacking the binary packages take forever.
2900 A part of the slow I/O issue was discussed in
2901 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2902 much file system sync-ing done by dpkg, which is the package
2903 responsible for unpacking the binary packages. Other parts (like code
2904 executed by postinst scripts) might also sync to disk during
2905 installation. All this sync-ing to disk do not really make sense to
2906 me. If the machine crash half-way through, I start over, I do not try
2907 to salvage the half installed system. So the failure sync-ing is
2908 supposed to protect against, hardware or system crash, is not really
2909 relevant while the installer is running.
</p
>
2911 <p
>A few days ago, I thought of a way to get rid of all the file
2912 system sync()-ing in a fairly non-intrusive way, without the need to
2913 change the code in several packages. The idea is not new, but I have
2914 not heard anyone propose the approach using dpkg-divert before. It
2915 depend on the small and clever package
2916 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
2917 uses LD_PRELOAD to replace the system functions for syncing data to
2918 disk with functions doing nothing, thus allowing programs to live
2919 dangerous while speeding up disk I/O significantly. Instead of
2920 modifying the implementation of dpkg, apt and tasksel (which are the
2921 packages responsible for selecting, fetching and installing packages),
2922 it occurred to me that we could just divert the programs away, replace
2923 them with a simple shell wrapper calling
2924 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
2925 Two days ago I decided to test the idea, and wrapped up a simple
2926 implementation for the Debian Edu udeb.
</p
>
2928 <p
>The effect was stunning. In my first test it reduced the running
2929 time of the pkgsel step (installing tasks) from
64 to less than
44
2930 minutes (
20 minutes shaved off the installation) on an old Dell
2931 Latitude D505 machine. I am not quite sure what the optimised time
2932 would have been, as I messed up the testing a bit, causing the debconf
2933 priority to get low enough for two questions to pop up during
2934 installation. As soon as I saw the questions I moved the installation
2935 along, but do not know how long the question were holding up the
2936 installation. I did some more measurements using Debian Edu Jessie,
2937 and got these results. The time measured is the time stamp in
2938 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
2939 "pkgsel: finishing up
" lines, if you want to do the same measurement
2940 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2941 timing thus do not depend on how quickly the user handle the tasksel
2944 <p
><table
>
2947 <th
>Machine/setup
</th
>
2948 <th
>Original tasksel
</th
>
2949 <th
>Optimised tasksel
</th
>
2950 <th
>Reduction
</th
>
2954 <td
>Latitude D505 Main+LTSP LXDE
</td
>
2955 <td
>64 min (
07:
46-
08:
50)
</td
>
2956 <td
><44 min (
11:
27-
12:
11)
</td
>
2957 <td
>>20 min
18%
</td
>
2961 <td
>Latitude D505 Roaming LXDE
</td
>
2962 <td
>57 min (
08:
48-
09:
45)
</td
>
2963 <td
>34 min (
07:
43-
08:
17)
</td
>
2964 <td
>23 min
40%
</td
>
2968 <td
>Latitude D505 Minimal
</td
>
2969 <td
>22 min (
10:
37-
10:
59)
</td
>
2970 <td
>11 min (
11:
16-
11:
27)
</td
>
2971 <td
>11 min
50%
</td
>
2975 <td
>Thinkpad X200 Minimal
</td
>
2976 <td
>6 min (
08:
19-
08:
25)
</td
>
2977 <td
>4 min (
08:
04-
08:
08)
</td
>
2978 <td
>2 min
33%
</td
>
2982 <td
>Thinkpad X200 Roaming KDE
</td
>
2983 <td
>19 min (
09:
21-
09:
40)
</td
>
2984 <td
>15 min (
10:
25-
10:
40)
</td
>
2985 <td
>4 min
21%
</td
>
2988 </table
></p
>
2990 <p
>The test is done using a netinst ISO on a USB stick, so some of the
2991 time is spent downloading packages. The connection to the Internet
2992 was
100Mbit/s during testing, so downloading should not be a
2993 significant factor in the measurement. Download typically took a few
2994 seconds to a few minutes, depending on the amount of packages being
2995 installed.
</p
>
2997 <p
>The speedup is implemented by using two hooks in
2998 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
2999 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3000 finish-install.d hook to remove the divert at the end of the
3001 installation. I picked the pre-pkgsel.d hook instead of the
3002 post-base-installer.d hook because I test using an ISO without the
3003 eatmydata package included, and the post-base-installer.d hook in
3004 Debian Edu can only operate on packages included in the ISO. The
3005 negative effect of this is that I am unable to activate this
3006 optimization for the kernel installation step in d-i. If the code is
3007 moved to the post-base-installer.d hook, the speedup would be larger
3008 for the entire installation.
</p
>
3010 <p
>I
've implemented this in the
3011 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3012 git repository, and plan to provide the optimization as part of the
3013 Debian Edu installation. If you want to test this yourself, you can
3014 create two files in the installer (or in an udeb). One shell script
3015 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3017 <p
><blockquote
><pre
>
3020 . /usr/share/debconf/confmodule
3022 logger -t my-pkgsel
"info: $*
"
3025 logger -t my-pkgsel
"error: $*
"
3027 override_install() {
3028 apt-install eatmydata || true
3029 if [ -x /target/usr/bin/eatmydata ] ; then
3030 for bin in dpkg apt-get aptitude tasksel ; do
3032 # Test that the file exist and have not been diverted already.
3033 if [ -f /target$file ] ; then
3034 info
"diverting $file using eatmydata
"
3035 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3036 > /target$file.edu
3037 chmod
755 /target$file.edu
3038 in-target dpkg-divert --package debian-edu-config \
3039 --rename --quiet --add $file
3040 ln -sf ./$bin.edu /target$file
3042 error
"unable to divert $file, as it is missing.
"
3046 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3051 </pre
></blockquote
></p
>
3053 <p
>To clean up, another shell script should go into
3054 /usr/lib/finish-install.d/ with code like this:
3056 <p
><blockquote
><pre
>
3058 . /usr/share/debconf/confmodule
3060 logger -t my-finish-install
"error: $@
"
3062 remove_install_override() {
3063 for bin in dpkg apt-get aptitude tasksel ; do
3065 if [ -x /target$file.edu ] ; then
3067 in-target dpkg-divert --package debian-edu-config \
3068 --rename --quiet --remove $file
3071 error
"Missing divert for $file.
"
3074 sync # Flush file buffers before continuing
3077 remove_install_override
3078 </pre
></blockquote
></p
>
3080 <p
>In Debian Edu, I placed both code fragments in a separate script
3081 edu-eatmydata-install and call it from the pre-pkgsel.d and
3082 finish-install.d scripts.
</p
>
3084 <p
>By now you might ask if this change should get into the normal
3085 Debian installer too? I suspect it should, but am not sure the
3086 current debian-installer coordinators find it useful enough. It also
3087 depend on the side effects of the change. I
'm not aware of any, but I
3088 guess we will see if the change is safe after some more testing.
3089 Perhaps there is some package in Debian depending on sync() and
3090 fsync() having effect? Perhaps it should go into its own udeb, to
3091 allow those of us wanting to enable it to do so without affecting
3094 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3095 will break installation of all programs using gnutls because of
3096 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3097 eatmydata package in Debian will solve it.
</p
>
3099 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3100 the optimization work again. And I have discovered that the
3101 dpkg-divert trick is not really needed and implemented a slightly
3102 simpler approach as part of the debian-edu-install package. See
3103 tools/edu-eatmydata-install in the source package.
</p
>
3105 <p
>Update
2014-
11-
11: Unfortunately, a new
3106 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3107 triggering on i386 made it into testing, and broke this installation
3108 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3109 request
768893</a
> is accepted, it should be working again.
</p
>
3114 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3115 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3116 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3117 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3118 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3119 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3120 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3121 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3122 learn that there is a large set of publicly available key servers to
3123 use when looking for peoples public key. So far I have used
3124 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3125 were misbehaving, but those days are ended. The servers I have used
3126 up until yesterday have been slow and some times unavailable. I hope
3127 those problems are gone now.
</p
>
3129 <p
>Behind the round robin DNS entry of the
3130 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3131 there is a pool of more than
100 keyservers which are checked every
3132 day to ensure they are well connected and up to date. It must be
3133 better than what I have used so far. :)
</p
>
3135 <p
>Yesterdays speaker told me that the service is the default
3136 keyserver provided by the default configuration in GnuPG, but this do
3137 not seem to be used in Debian. Perhaps it should?
</p
>
3139 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3142 <p
><blockquote
><pre
>
3143 keyserver pool.sks-keyservers.net
3144 </pre
></blockquote
></p
>
3146 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3147 entries in DNS. Just for fun, I did just that at work, so now every
3148 user of GnuPG at the University of Oslo should find a OpenGPG
3149 keyserver automatically should their need it:
</p
>
3151 <p
><blockquote
><pre
>
3152 % host -t srv _pgpkey-http._tcp.uio.no
3153 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3155 </pre
></blockquote
></p
>
3157 <p
>Now if only
3158 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3159 HKP lookup protocol
</a
> supported finding signature paths, I would be
3160 very happy. It can look up a given key or search for a user ID, but I
3161 normally do not want that, but to find a trust path from my key to
3162 another key. Given a user ID or key ID, I would like to find (and
3163 download) the keys representing a signature path from my key to the
3164 key in question, to be able to get a trust path between the two keys.
3165 This is as far as I can tell not possible today. Perhaps something
3166 for a future version of the protocol?
</p
>
3171 <title>From English wiki to translated PDF and epub via Docbook
</title>
3172 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3173 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3174 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3175 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3176 project
</a
> provide an instruction manual for teachers, system
3177 administrators and other users that contain useful tips for setting up
3178 and maintaining a Debian Edu installation. This text is about how the
3179 text processing of this manual is handled in the project.
</p
>
3181 <p
>One goal of the project is to provide information in the native
3182 language of its users, and for this we need to handle translations.
3183 But we also want to make sure each language contain the same
3184 information, so for this we need a good way to keep the translations
3185 in sync. And we want it to be easy for our users to improve the
3186 documentation, avoiding the need to learn special formats or tools to
3187 contribute, and the obvious way to do this is to make it possible to
3188 edit the documentation using a web browser. We also want it to be
3189 easy for translators to keep the translation up to date, and give them
3190 help in figuring out what need to be translated. Here is the list of
3191 tools and the process we have found trying to reach all these
3194 <p
>We maintain the authoritative source of our manual in the
3195 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3196 wiki
</a
>, as several wiki pages written in English. It consist of one
3197 front page with references to the different chapters, several pages
3198 for each chapter, and finally one
"collection page
" gluing all the
3199 chapters together into one large web page (aka
3200 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3201 AllInOne page
</a
>). The AllInOne page is the one used for further
3202 processing and translations. Thanks to the fact that the
3203 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3204 wiki.debian.org support exporting pages in
3205 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3206 the list of pages to export using the raw version of the AllInOne
3207 page, loop over each of them to generate a Docbook XML version of the
3208 manual. This process also download images and transform image
3209 references to use the locally downloaded images. The generated
3210 Docbook XML files are slightly broken, so some post-processing is done
3211 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3212 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3213 a handfull of images. The XML file can now be used to generate PDF, HTML
3214 and epub versions of the English manual. This is the basic step of
3215 our process, making PDF (using dblatex), HTML (using xsltproc) and
3216 epub (using dbtoepub) version from Docbook XML, and the resulting files
3217 are placed in the debian-edu-doc-en binary package.
</p
>
3219 <p
>But English documentation is not enough for us. We want translated
3220 documentation too, and we want to make it easy for translators to
3221 track the English original. For this we use the
3222 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3223 which allow us to transform the English Docbook XML file into a
3224 translation file (a .pot file), usable with the normal gettext based
3225 translation tools used by those translating free software. The pot
3226 file is used to create and maintain translation files (several .po
3227 files), which the translations update with the native language
3228 translations of all titles, paragraphs and blocks of text in the
3229 original. The next step is combining the original English Docbook XML
3230 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3231 create a translated Docbook XML file (in this case
3232 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3233 translated, if the translation is not complete) Docbook XML file can
3234 then be used like the original to create a PDF, HTML and epub version
3235 of the documentation.
</p
>
3237 <p
>The translators use different tools to edit the .po files. We
3239 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3240 while some use emacs and vi, others can use web based editors like
3241 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3242 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3243 is where the .po file end up, in our git repository. Updated
3244 translations can either be committed directly to git, or submitted as
3245 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3246 against the debian-edu-doc package
</a
>.
</p
>
3248 <p
>One challenge is images, which both might need to be translated (if
3249 they show translated user applications), and are needed in different
3250 formats when creating PDF and HTML versions (epub is a HTML version in
3251 this regard). For this we transform the original PNG images to the
3252 needed density and format during build, and have a way to provide
3253 translated images by storing translated versions in
3254 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3255 package maintainers know more.
</p
>
3257 <p
>If you wonder what the result look like, we provide
3258 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3259 of the documentation packages on the web
</a
>. See for example the
3260 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3261 PDF version
</a
> or the
3262 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3263 HTML version
</a
>. We do not yet build the epub version by default,
3264 but perhaps it will be done in the future.
</p
>
3266 <p
>To learn more, check out
3267 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3268 debian-edu-doc package
</a
>,
3269 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3270 manual on the wiki
</a
> and
3271 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3272 translation instructions
</a
> in the manual.
</p
>
3277 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3278 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3279 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3280 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3281 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3282 related packages relevant for the computer installed automatically.
3283 So I implemented one, using
3284 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3285 package
</a
>. To use it, install the tasksel and isenkram packages and
3286 run tasksel as user root. You should be presented with a new option,
3287 "Hardware specific packages (autodetected by isenkram)
". When you
3288 select it, tasksel will install the packages isenkram claim is fit for
3289 the current hardware, hot pluggable or not.
<p
>
3291 <p
>The implementation is in two files, one is the tasksel menu entry
3292 description, and the other is the script used to extract the list of
3293 packages to install. The first part is in
3294 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3297 <p
><blockquote
><pre
>
3300 Description: Hardware specific packages (autodetected by isenkram)
3301 Based on the detected hardware various hardware specific packages are
3303 Test-new-install: mark show
3305 Packages: for-current-hardware
3306 </pre
></blockquote
></p
>
3308 <p
>The second part is in
3309 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3312 <p
><blockquote
><pre
>
3317 isenkram-autoinstall-firmware -l
3319 </pre
></blockquote
></p
>
3321 <p
>All in all, a very short and simple implementation making it
3322 trivial to install the hardware dependent package we all may want to
3323 have installed on our machines. I
've not been able to find a way to
3324 get tasksel to tell you exactly which packages it plan to install
3325 before doing the installation. So if you are curious or careful,
3326 check the output from the isenkram-* command line tools first.
</p
>
3328 <p
>The information about which packages are handling which hardware is
3329 fetched either from the isenkram package itself in
3330 /usr/share/isenkram/, from git.debian.org or from the APT package
3331 database (using the Modaliases header). The APT package database
3332 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3333 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3334 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3335 the python-apt code (bug
3336 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3337 workaround I was able to get rid of the file descriptor leak and
3338 reduce the memory leak from ~
30 MiB per hardware detection down to
3339 around
2 MiB per hardware detection. It should make the desktop
3340 daemon a lot more useful. The fix is in version
0.7 uploaded to
3341 unstable today.
</p
>
3343 <p
>I believe the current way of mapping hardware to packages in
3344 Isenkram is is a good draft, but in the future I expect isenkram to
3345 use the AppStream data source for this. A proposal for getting proper
3346 AppStream support into Debian is floating around as
3347 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3348 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3349 project
</a
> will take place this summer to improve the situation. I
3350 look forward to seeing the result, and welcome patches for isenkram to
3351 start using the information when it is ready.
</p
>
3353 <p
>If you want your package to map to some specific hardware, either
3354 add a
"Xb-Modaliases
" header to your control file like I did in
3355 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3356 package
</a
> or submit a bug report with the details to the isenkram
3358 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3359 blog posts tagged isenkram
</a
> for details on the notation. I expect
3360 the information will be migrated to AppStream eventually, but for the
3361 moment I got no better place to store it.
</p
>
3366 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3367 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3369 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3370 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3371 project
</a
> is working on providing the software and hardware to make
3372 it easy for non-technical people to host their data and communication
3373 at home, and being able to communicate with their friends and family
3374 encrypted and away from prying eyes. It is still going strong, and
3375 today a major mile stone was reached.
</p
>
3377 <p
>Today, the last of the packages currently used by the project to
3378 created the system images were accepted into Debian Unstable. It was
3379 the freedombox-setup package, which is used to configure the images
3380 during build and on the first boot. Now all one need to get going is
3381 the build code from the freedom-maker git repository and packages from
3382 Debian. And once the freedombox-setup package enter testing, we can
3383 build everything directly from Debian. :)
</p
>
3385 <p
>Some key packages used by Freedombox are
3386 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3387 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3388 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3389 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3390 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3391 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3392 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3393 are plans to integrate more packages into the setup. User
3394 documentation is maintained on the Debian wiki. Please
3395 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3396 the manual
</a
> and help us improve it.
</p
>
3398 <p
>To test for yourself and create boot images with the FreedomBox
3399 setup, run this on a Debian machine using a user with sudo rights to
3400 become root:
</p
>
3402 <p
><pre
>
3403 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3404 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3406 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3408 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3409 </pre
></p
>
3411 <p
>Root access is needed to run debootstrap and mount loopback
3412 devices. See the README in the freedom-maker git repo for more
3413 details on the build. If you do not want all three images, trim the
3414 make line. Note that the virtualbox-image target is not really
3415 virtualbox specific. It create a x86 image usable in kvm, qemu,
3416 vmware and any other x86 virtual machine environment. You might need
3417 the version of vmdebootstrap in Jessie to get the build working, as it
3418 include fixes for a race condition with kpartx.
</p
>
3420 <p
>If you instead want to install using a Debian CD and the preseed
3421 method, boot a Debian Wheezy ISO and use this boot argument to load
3422 the preseed values:
</p
>
3424 <p
><pre
>
3425 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3426 </pre
></p
>
3428 <p
>I have not tested it myself the last few weeks, so I do not know if
3429 it still work.
</p
>
3431 <p
>If you wonder how to help, one task you could look at is using
3432 systemd as the boot system. It will become the default for Linux in
3433 Jessie, so we need to make sure it is usable on the Freedombox. I did
3434 a simple test a few weeks ago, and noticed dnsmasq failed to start
3435 during boot when using systemd. I suspect there are other problems
3436 too. :) To detect problems, there is a test suite included, which can
3437 be run from the plinth web interface.
</p
>
3439 <p
>Give it a go and let us know how it goes on the mailing list, and help
3440 us get the new release published. :) Please join us on
3441 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3442 irc.debian.org)
</a
> and
3443 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3444 mailing list
</a
> if you want to help make this vision come true.
</p
>
3449 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3450 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3451 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3452 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3453 <description><p
>For a while now, I have been looking for a sensible offsite backup
3454 solution for use at home. My requirements are simple, it must be
3455 cheap and locally encrypted (in other words, I keep the encryption
3456 keys, the storage provider do not have access to my private files).
3457 One idea me and my friends had many years ago, before the cloud
3458 storage providers showed up, was to use Google mail as storage,
3459 writing a Linux block device storing blocks as emails in the mail
3460 service provided by Google, and thus get heaps of free space. On top
3461 of this one can add encryption, RAID and volume management to have
3462 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3463 I never found time to implement such system. But the last few weeks I
3464 have looked at a system called
3465 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3466 mounted network backed file system with the features I need.
</p
>
3468 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3469 handling several different storage providers, any with Amazon S3,
3470 Google Drive or OpenStack API. There are heaps of such storage
3471 providers. S3QL can also use a local directory as storage, which
3472 combined with sshfs allow for file storage on any ssh server. S3QL
3473 include support for encryption, compression, de-duplication, snapshots
3474 and immutable file systems, allowing me to mount the remote storage as
3475 a local mount point, look at and use the files as if they were local,
3476 while the content is stored in the cloud as well. This allow me to
3477 have a backup that should survive fire. The file system can not be
3478 shared between several machines at the same time, as only one can
3479 mount it at the time, but any machine with the encryption key and
3480 access to the storage service can mount it if it is unmounted.
</p
>
3482 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3483 package is included already. So to get started, run
<tt
>apt-get
3484 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3485 Greenqloud, after reading their nice recipe on
3486 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3487 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3488 in Iceland more than those in USA when it come to keeping my personal
3489 data safe and private, and thus would rather spend money on a company
3490 in Iceland. Another nice recipe is available from the article
3491 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3492 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3493 Admin magazine. When the provider is picked, figure out how to get
3494 the API key needed to connect to the storage API. With Greencloud,
3495 the key did not show up until I had added payment details to my
3498 <p
>Armed with the API access details, it is time to create the file
3499 system. First, create a new bucket in the cloud. This bucket is the
3500 file system storage area. I picked a bucket name reflecting the
3501 machine that was going to store data there, but any name will do.
3502 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3503 the API login and password, and a locally created password. Store it
3504 all in ~root/.s3ql/authinfo2 like this:
3506 <p
><blockquote
><pre
>
3508 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3509 backend-login: API-login
3510 backend-password: API-password
3511 fs-passphrase: local-password
3512 </pre
></blockquote
></p
>
3514 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3515 but any sensible way to create a fairly random password should do it.
3516 Armed with these details, it is now time to run mkfs, entering the API
3517 details and password to create it:
</p
>
3519 <p
><blockquote
><pre
>
3520 # mkdir -m
700 /var/lib/s3ql-cache
3521 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3522 --ssl s3c://s.greenqloud.com:
443/bucket-name
3523 Enter backend login:
3524 Enter backend password:
3525 Before using S3QL, make sure to read the user
's guide, especially
3526 the
'Important Rules to Avoid Loosing Data
' section.
3527 Enter encryption password:
3528 Confirm encryption password:
3529 Generating random encryption key...
3530 Creating metadata tables...
3540 Compressing and uploading metadata...
3541 Wrote
0.00 MB of compressed metadata.
3542 #
</pre
></blockquote
></p
>
3544 <p
>The next step is mounting the file system to make the storage available.
3546 <p
><blockquote
><pre
>
3547 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3548 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3549 Using
4 upload threads.
3550 Downloading and decompressing metadata...
3560 Mounting filesystem...
3562 Filesystem Size Used Avail Use% Mounted on
3563 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3565 </pre
></blockquote
></p
>
3567 <p
>The file system is now ready for use. I use rsync to store my
3568 backups in it, and as the metadata used by rsync is downloaded at
3569 mount time, no network traffic (and storage cost) is triggered by
3570 running rsync. To unmount, one should not use the normal umount
3571 command, as this will not flush the cache to the cloud storage, but
3572 instead running the umount.s3ql command like this:
3574 <p
><blockquote
><pre
>
3577 </pre
></blockquote
></p
>
3579 <p
>There is a fsck command available to check the file system and
3580 correct any problems detected. This can be used if the local server
3581 crashes while the file system is mounted, to reset the
"already
3582 mounted
" flag. This is what it look like when processing a working
3583 file system:
</p
>
3585 <p
><blockquote
><pre
>
3586 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3587 Using cached metadata.
3588 File system seems clean, checking anyway.
3589 Checking DB integrity...
3590 Creating temporary extra indices...
3591 Checking lost+found...
3592 Checking cached objects...
3593 Checking names (refcounts)...
3594 Checking contents (names)...
3595 Checking contents (inodes)...
3596 Checking contents (parent inodes)...
3597 Checking objects (reference counts)...
3598 Checking objects (backend)...
3599 ..processed
5000 objects so far..
3600 ..processed
10000 objects so far..
3601 ..processed
15000 objects so far..
3602 Checking objects (sizes)...
3603 Checking blocks (referenced objects)...
3604 Checking blocks (refcounts)...
3605 Checking inode-block mapping (blocks)...
3606 Checking inode-block mapping (inodes)...
3607 Checking inodes (refcounts)...
3608 Checking inodes (sizes)...
3609 Checking extended attributes (names)...
3610 Checking extended attributes (inodes)...
3611 Checking symlinks (inodes)...
3612 Checking directory reachability...
3613 Checking unix conventions...
3614 Checking referential integrity...
3615 Dropping temporary indices...
3616 Backing up old metadata...
3626 Compressing and uploading metadata...
3627 Wrote
0.89 MB of compressed metadata.
3629 </pre
></blockquote
></p
>
3631 <p
>Thanks to the cache, working on files that fit in the cache is very
3632 quick, about the same speed as local file access. Uploading large
3633 amount of data is to me limited by the bandwidth out of and into my
3634 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3635 which is very close to my upload speed, and downloading the same
3636 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3637 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3638 network, not the file system code. I do not know what a good cache
3639 size would be, but suspect that the cache should e larger than your
3640 working set.
</p
>
3642 <p
>I mentioned that only one machine can mount the file system at the
3643 time. If another machine try, it is told that the file system is
3646 <p
><blockquote
><pre
>
3647 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3648 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3649 Using
8 upload threads.
3650 Backend reports that fs is still mounted elsewhere, aborting.
3652 </pre
></blockquote
></p
>
3654 <p
>The file content is uploaded when the cache is full, while the
3655 metadata is uploaded once every
24 hour by default. To ensure the
3656 file system content is flushed to the cloud, one can either umount the
3657 file system, or ask S3QL to flush the cache and metadata using
3660 <p
><blockquote
><pre
>
3661 # s3qlctrl upload-meta /s3ql
3662 # s3qlctrl flushcache /s3ql
3664 </pre
></blockquote
></p
>
3666 <p
>If you are curious about how much space your data uses in the
3667 cloud, and how much compression and deduplication cut down on the
3668 storage usage, you can use s3qlstat on the mounted file system to get
3671 <p
><blockquote
><pre
>
3673 Directory entries:
9141
3676 Total data size:
22049.38 MB
3677 After de-duplication:
21955.46 MB (
99.57% of total)
3678 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3679 Database size:
2.39 MB (uncompressed)
3680 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3682 </pre
></blockquote
></p
>
3684 <p
>I mentioned earlier that there are several possible suppliers of
3685 storage. I did not try to locate them all, but am aware of at least
3686 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3687 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3688 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3689 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3690 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3691 accept payment in Bitcoin. Pick one that suit your need. Some of
3692 them provide several GiB of free storage, but the prize models are
3693 quite different and you will have to figure out what suits you
3696 <p
>While researching this blog post, I had a look at research papers
3697 and posters discussing the S3QL file system. There are several, which
3698 told me that the file system is getting a critical check by the
3699 science community and increased my confidence in using it. One nice
3701 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3702 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3703 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3704 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3705 and Pamela Smith. Please have a look.
</p
>
3707 <p
>Given my problems with different file systems earlier, I decided to
3708 check out the mounted S3QL file system to see if it would be usable as
3709 a home directory (in other word, that it provided POSIX semantics when
3710 it come to locking and umask handling etc). Running
3711 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3712 test code to check file system semantics
</a
>, I was happy to discover that
3713 no error was found. So the file system can be used for home
3714 directories, if one chooses to do so.
</p
>
3716 <p
>If you do not want a locally file system, and want something that
3717 work without the Linux fuse file system, I would like to mention the
3718 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3719 provide locally encrypted backup using a command line client. It have
3720 a nicer access control system, where one can split out read and write
3721 access, allowing some systems to write to the backup and others to
3722 only read from it.
</p
>
3724 <p
>As usual, if you use Bitcoin and want to show your support of my
3725 activities, please send Bitcoin donations to my address
3726 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3731 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3732 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3733 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3734 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3735 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3736 project
</a
> is working on providing the software and hardware for
3737 making it easy for non-technical people to host their data and
3738 communication at home, and being able to communicate with their
3739 friends and family encrypted and away from prying eyes. It has been
3740 going on for a while, and is slowly progressing towards a new test
3741 release (
0.2).
</p
>
3743 <p
>And what day could be better than the Pi day to announce that the
3744 new version will provide
"hard drive
" / SD card / USB stick images for
3745 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3746 system), and can also be installed using a Debian installer preseed
3747 file. The Debian based Freedombox is now based on Debian Jessie,
3748 where most of the needed packages used are already present. Only one,
3749 the freedombox-setup package, is missing. To try to build your own
3750 boot image to test the current status, fetch the freedom-maker scripts
3752 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
3753 with a user with sudo access to become root:
3756 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3758 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3759 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3761 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3764 <p
>Root access is needed to run debootstrap and mount loopback
3765 devices. See the README for more details on the build. If you do not
3766 want all three images, trim the make line. But note that thanks to
<a
3767 href=
"https://bugs.debian.org/
741407">a race condition in
3768 vmdebootstrap
</a
>, the build might fail without the patch to the
3769 kpartx call.
</p
>
3771 <p
>If you instead want to install using a Debian CD and the preseed
3772 method, boot a Debian Wheezy ISO and use this boot argument to load
3773 the preseed values:
</p
>
3776 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3779 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3780 recently introduced bug in apt in Jessie
</a
>, the installer will
3781 currently hang while setting up APT sources. Killing the
3782 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3783 installation will get the installation going. This affect all
3784 installations in Jessie, and I expect it will be fixed soon.
</p
>
3786 <p
>Give it a go and let us know how it goes on the mailing list, and help
3787 us get the new release published. :) Please join us on
3788 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3789 irc.debian.org)
</a
> and
3790 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3791 mailing list
</a
> if you want to help make this vision come true.
</p
>
3796 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3797 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3798 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3799 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3800 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3801 innetgr tools, because I needed them in
3802 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3803 ng-utils, and it has served me well. I placed the project under the
3804 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3805 repository. But many years ago, the CVS repository was dropped (lost,
3806 not migrated to new hardware, not sure), and the project have lacked a
3807 proper home since then.
</p
>
3809 <p
>Last summer, I had a look at the package and made a new release
3810 fixing a irritating crash bug, but was unable to store the changes in
3811 a proper source control system. I applied for a project on
3812 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3813 to follow up on it. Until today. :)
</p
>
3815 <p
>After many hours of cleaning and migration, the ng-utils project
3816 now have a new home, and a git repository with the highlight of the
3817 history of the project. I published all release tarballs and imported
3818 them into the git repository. As the project is really stable and not
3819 expected to gain new features any time soon, I decided to make a new
3820 release and call it
1.0. Visit the new project home on
3821 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3822 if you want to check it out. The new version is also uploaded into
3823 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3828 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3829 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3830 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3831 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3832 <description><p
>A few days ago I decided to try to help the Hurd people to get
3833 their changes into sysvinit, to allow them to use the normal sysvinit
3834 boot system instead of their old one. This follow up on the
3835 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3836 Google Summer of Code work
</a
> done last summer by Justus Winter to
3837 get Debian on Hurd working more like Debian on Linux. To get started,
3838 I downloaded a prebuilt hard disk image from
3839 <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
>,
3840 and started it using virt-manager.
</p
>
3842 <p
>The first think I had to do after logging in (root without any
3843 password) was to get the network operational. I followed
3844 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3845 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3846 commands as root to get the machine to accept a IP address from the
3847 kvm internal DHCP server:
</p
>
3849 <p
><blockquote
><pre
>
3850 settrans -fgap /dev/netdde /hurd/netdde
3851 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3852 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3854 </pre
></blockquote
></p
>
3856 <p
>After this, the machine had internet connectivity, and I could
3857 upgrade it and install the sysvinit packages from experimental and
3858 enable it as the default boot system in Hurd.
</p
>
3860 <p
>But before I did that, I set a password on the root user, as ssh is
3861 running on the machine it for ssh login to work a password need to be
3862 set. Also, note that a bug somewhere in openssh on Hurd block
3863 compression from working. Remember to turn that off on the client
3866 <p
>Run these commands as root to upgrade and test the new sysvinit
3869 <p
><blockquote
><pre
>
3870 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3871 deb http://http.debian.net/debian/ experimental main
3874 apt-get dist-upgrade
3875 apt-get install -t experimental initscripts sysv-rc sysvinit \
3876 sysvinit-core sysvinit-utils
3877 update-alternatives --config runsystem
3878 </pre
></blockquote
></p
>
3880 <p
>To reboot after switching boot system, you have to use
3881 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3882 yet a sysvinit process able to receive the signals from the normal
3883 'reboot
' command. After switching to sysvinit as the boot system,
3884 upgrading every package and rebooting, the network come up with DHCP
3885 after boot as it should, and the settrans/pkill hack mentioned at the
3886 start is no longer needed. But for some strange reason, there are no
3887 longer any login prompt in the virtual console, so I logged in using
3890 <p
>Note that there are some race conditions in Hurd making the boot
3891 fail some times. No idea what the cause is, but hope the Hurd porters
3892 figure it out. At least Justus said on IRC (#debian-hurd on
3893 irc.debian.org) that they are aware of the problem. A way to reduce
3894 the impact is to upgrade to the Hurd packages built by Justus by
3895 adding this repository to the machine:
</p
>
3897 <p
><blockquote
><pre
>
3898 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3899 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3901 </pre
></blockquote
></p
>
3903 <p
>At the moment the prebuilt virtual machine get some packages from
3904 http://ftp.debian-ports.org/debian, because some of the packages in
3905 unstable do not yet include the required patches that are lingering in
3906 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
3908 <p
><blockquote
><pre
>
3909 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
3910 i emacs - GNU Emacs editor (metapackage)
3911 i gdb - GNU Debugger
3912 i hurd-recommended - Miscellaneous translators
3913 i isc-dhcp-client - ISC DHCP client
3914 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3915 i libc-bin - Embedded GNU C Library: Binaries
3916 i libc-dev-bin - Embedded GNU C Library: Development binaries
3917 i libc0.3 - Embedded GNU C Library: Shared libraries
3918 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3919 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3920 i multiarch-support - Transitional package to ensure multiarch compatibilit
3921 i A x11-common - X Window System (X.Org) infrastructure
3922 i xorg - X.Org X Window System
3923 i A xserver-xorg - X.Org X server
3924 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3926 </pre
></blockquote
></p
>
3928 <p
>All in all, testing hurd has been an interesting experience. :)
3929 X.org did not work out of the box and I never took the time to follow
3930 the porters instructions to fix it. This time I was interested in the
3931 command line stuff.
<p
>
3936 <title>New chrpath release
0.16</title>
3937 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
3938 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
3939 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
3940 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
3941 find problems in C, C++ and Java code using static source code
3942 analysis. It can detect a lot of different problems, and is very
3943 useful to find memory and locking bugs in the error handling part of
3944 the source. The company behind it provide
3945 <a href=
"https://scan.coverity.com/
">check of free software projects as
3946 a community service
</a
>, and many hundred free software projects are
3947 already checked. A few days ago I decided to have a closer look at
3948 the Coverity system, and discovered that the
3949 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
3950 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
3951 projects I am involved with was already registered. But these are
3952 fairly big, and I would also like to have a small and easy project to
3953 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
3954 checking of the chrpath project
</a
>. It was
3955 added to the checker and discovered seven potential defects. Six of
3956 these were real, mostly resource
"leak
" when the program detected an
3957 error. Nothing serious, as the resources would be released a fraction
3958 of a second later when the program exited because of the error, but it
3959 is nice to do it right in case the source of the program some time in
3960 the future end up in a library. Having fixed all defects and added
3961 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
3962 mailing list for the chrpath developers
</a
>, I decided it was time to
3963 publish a new release. These are the release notes:
</p
>
3965 <p
>New in
0.16 released
2014-
01-
14:
</p
>
3969 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
3970 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
3971 <li
>Mention new project mailing list in the documentation.
</li
>
3976 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
3977 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
3978 project if something is wrong with the new release. The test suite
3979 did not discover any old errors, so if you find a new one, please also
3980 include a test suite check.
</p
>
3985 <title>New chrpath release
0.15</title>
3986 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
3987 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
3988 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
3989 <description><p
>After many years break from the package and a vain hope that
3990 development would be continued by someone else, I finally pulled my
3991 acts together this morning and wrapped up a new release of chrpath,
3992 the command line tool to modify the rpath and runpath of already
3993 compiled ELF programs. The update was triggered by the persistence of
3994 Isha Vishnoi at IBM, which needed a new config.guess file to get
3995 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
3996 is working on. I checked the
3997 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
3998 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
3999 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4000 packages for interesting patches (failed to find the source from
4001 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4002 These are the release notes:
</p
>
4004 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4008 <li
>Updated config.sub and config.guess from the GNU project to work
4009 with newer architectures. Thanks to isha vishnoi for the heads
4012 <li
>Updated README with current URLs.
</li
>
4014 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4015 Matthias Klose.
</li
>
4017 <li
>Added missing help for -k|--keepgoing option, using patch by
4018 Petr Machata found in Fedora.
</li
>
4020 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4021 .dynamic is a NULL terminated string. Based on patch found in
4022 Fedora credited Axel Thimm and Christian Krause.
</li
>
4027 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4028 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4029 project if something is wrong with the new release. The test suite
4030 did not discover any old errors, so if you find a new one, please also
4031 include a testsuite check.
</p
>
4036 <title>Debian init.d boot script example for rsyslog
</title>
4037 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4038 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4039 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4040 <description><p
>If one of the points of switching to a new init system in Debian is
4041 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4042 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4043 init.d scripts at all. Here is an example init.d script, ie a rewrite
4044 of /etc/init.d/rsyslog:
</p
>
4046 <p
><pre
>
4047 #!/lib/init/init-d-script
4050 # Required-Start: $remote_fs $time
4051 # Required-Stop: umountnfs $time
4052 # X-Stop-After: sendsigs
4053 # Default-Start:
2 3 4 5
4054 # Default-Stop:
0 1 6
4055 # Short-Description: enhanced syslogd
4056 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4057 # It is quite compatible to stock sysklogd and can be
4058 # used as a drop-in replacement.
4060 DESC=
"enhanced syslogd
"
4061 DAEMON=/usr/sbin/rsyslogd
4062 </pre
></p
>
4064 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4065 script was
137 lines, and the above is just
15 lines, most of it meta
4066 info/comments.
</p
>
4068 <p
>How to do this, you ask? Well, one create a new script
4069 /lib/init/init-d-script looking something like this:
4071 <p
><pre
>
4074 # Define LSB log_* functions.
4075 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4076 # and status_of_proc is working.
4077 . /lib/lsb/init-functions
4080 # Function that starts the daemon/service
4086 #
0 if daemon has been started
4087 #
1 if daemon was already running
4088 #
2 if daemon could not be started
4089 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4091 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4094 # Add code here, if necessary, that waits for the process to be ready
4095 # to handle requests from services started subsequently which depend
4096 # on this one. As a last resort, sleep for some time.
4100 # Function that stops the daemon/service
4105 #
0 if daemon has been stopped
4106 #
1 if daemon was already stopped
4107 #
2 if daemon could not be stopped
4108 # other if a failure occurred
4109 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4110 RETVAL=
"$?
"
4111 [
"$RETVAL
" =
2 ]
&& return
2
4112 # Wait for children to finish too if this is a daemon that forks
4113 # and if the daemon is only ever run from this initscript.
4114 # If the above conditions are not satisfied then add some other code
4115 # that waits for the process to drop all resources that could be
4116 # needed by services started subsequently. A last resort is to
4117 # sleep for some time.
4118 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4119 [
"$?
" =
2 ]
&& return
2
4120 # Many daemons don
't delete their pidfiles when they exit.
4122 return
"$RETVAL
"
4126 # Function that sends a SIGHUP to the daemon/service
4130 # If the daemon can reload its configuration without
4131 # restarting (for example, when it is sent a SIGHUP),
4132 # then implement that here.
4134 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4139 scriptbasename=
"$(basename $
1)
"
4140 echo
"SN: $scriptbasename
"
4141 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4142 script=
"$
1"
4149 NAME=$(basename $DAEMON)
4150 PIDFILE=/var/run/$NAME.pid
4152 # Exit if the package is not installed
4153 #[ -x
"$DAEMON
" ] || exit
0
4155 # Read configuration variable file if it is present
4156 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4158 # Load the VERBOSE setting and other rcS variables
4161 case
"$
1" in
4163 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4165 case
"$?
" in
4166 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4167 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4171 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4173 case
"$?
" in
4174 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4175 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4179 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4181 #reload|force-reload)
4183 # If do_reload() is not implemented then leave this commented out
4184 # and leave
'force-reload
' as an alias for
'restart
'.
4186 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4190 restart|force-reload)
4192 # If the
"reload
" option is implemented then remove the
4193 #
'force-reload
' alias
4195 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4197 case
"$?
" in
4200 case
"$?
" in
4202 1) log_end_msg
1 ;; # Old process is still running
4203 *) log_end_msg
1 ;; # Failed to start
4213 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4219 </pre
></p
>
4221 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4222 lot. I did not really polish the approach, so it might not always
4223 work out of the box, but you get the idea. I did not try very hard to
4224 optimize it nor make it more robust either.
</p
>
4226 <p
>A better argument for switching init system in Debian than reducing
4227 the size of init scripts (which is a good thing to do anyway), is to
4228 get boot system that is able to handle the kernel events sensibly and
4229 robustly, and do not depend on the boot to run sequentially. The boot
4230 and the kernel have not behaved sequentially in years.
</p
>
4235 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4236 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4237 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4238 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4239 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4240 remote display access is the preferred solution with oVirt and RedHat
4241 Enterprise Virtualization, and I was sad to discover the other day
4242 that the browser plugin needed to use these systems seamlessly was
4243 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4244 for a package
</a
> was from
2012-
04-
10 with no progress since
4245 2013-
04-
01, so I decided to wrap up a package based on the great work
4246 from Cajus Pollmeier and put it in a collab-maint maintained git
4247 repository to get a package I could use. I would very much like
4248 others to help me maintain the package (or just take over, I do not
4249 mind), but as no-one had volunteered so far, I just uploaded it to
4250 NEW. I hope it will be available in Debian in a few days.
</p
>
4252 <p
>The source is now available from
4253 <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
>
4258 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4259 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4260 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4261 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4262 <description><p
>The
4263 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4264 program is a a very nice system to create virtual machine images. It
4265 create a image file, add a partition table, mount it and run
4266 debootstrap in the mounted directory to create a Debian system on a
4267 stick. Yesterday, I decided to try to teach it how to make images for
4268 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4269 of a plan to simplify the build system for
4270 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4271 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4272 the virtualbox images, but its current build system made multistrap
4273 based system for Dreamplug images, and it is lacking support for
4274 Raspberry Pi.
</p
>
4276 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4277 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4278 code and adjusted it to be able to build armel images on my amd64
4279 Debian laptop. I ended up giving vmdebootstrap five new options,
4280 allowing me to replicate the image creation process I use to make
4281 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4282 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4283 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4284 call debootstrap with --foreign and to copy the handler into the
4285 generated chroot before running the second stage. This allow
4286 vmdebootstrap to create armel images on an amd64 host. Next I added
4287 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4288 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4289 given file system type, allowing me to create an image with a vfat
4290 partition for the /boot/ stuff. I also added a
<tt
>--variant
4291 variant
</tt
> option to allow me to create smaller images without the
4292 Debian base system packages installed. Finally, I added an option
4293 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4294 as a boot loader. It is not needed on the Raspberry Pi and probably
4295 most other non-x86 architectures. The changes were accepted by the
4296 upstream author of vmdebootstrap yesterday and today, and is now
4298 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4299 upstream project page
</a
>.
</p
>
4301 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4302 create a small script (the customize script) to add the non-free
4303 binary blob needed to boot the Raspberry Pi and the APT source
4306 <p
><pre
>
4308 set -e # Exit on first error
4309 rootdir=
"$
1"
4310 cd
"$rootdir
"
4311 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4312 deb http://http.debian.net/debian/ jessie main contrib non-free
4314 # Install non-free binary blob needed to boot Raspberry Pi. This
4315 # install a kernel somewhere too.
4316 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4317 -O $rootdir/usr/bin/rpi-update
4318 chmod a+x $rootdir/usr/bin/rpi-update
4319 mkdir -p $rootdir/lib/modules
4320 touch $rootdir/boot/start.elf
4321 chroot $rootdir rpi-update
4322 </pre
></p
>
4324 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4325 to build the image:
</p
>
4328 sudo ./vmdebootstrap \
4331 --distribution jessie \
4332 --mirror http://http.debian.net/debian \
4341 --root-password raspberry \
4342 --hostname raspberrypi \
4343 --foreign /usr/bin/qemu-arm-static \
4344 --customize `pwd`/customize \
4346 --package git-core \
4347 --package binutils \
4348 --package ca-certificates \
4351 </pre
></p
>
4353 <p
>The list of packages being installed are the ones needed by
4354 rpi-update to make the image bootable on the Raspberry Pi, with the
4355 exception of netbase, which is needed by debootstrap to find
4356 /etc/hosts with the minbase variant. I really wish there was a way to
4357 set up an Raspberry Pi using only packages in the Debian archive, but
4358 that is not possible as far as I know, because it boots from the GPU
4359 using a non-free binary blob.
</p
>
4361 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4362 probably a few others installed. I have not checked the complete
4363 build dependency list.
</p
>
4365 <p
>The resulting image will not use the hardware floating point unit
4366 on the Raspberry PI, because the armel architecture in Debian is not
4367 optimized for that use. So the images created will be a bit slower
4368 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4373 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4374 <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>
4375 <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>
4376 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4377 <description><p
>The last few days I came across a few good causes that should get
4378 wider attention. I recommend signing and donating to each one of
4381 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4382 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4383 Women program which is a Google Summer of Code like initiative to get
4384 more women involved in free software. One debian sponsor has offered
4385 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4386 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4387 hope you will to. :)
</p
>
4389 <p
>And the Electronic Frontier Foundation just announced plans to
4390 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4391 documentaries about the excessive spying
</a
> on every Internet user that
4392 take place these days, and their need to fund the work. I
've already
4393 donated. Are you next?
</p
>
4395 <p
>For my Norwegian audience, the organisation Studentenes og
4396 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4397 statement under the heading
4398 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4399 Access
</a
> for those of us asking for more focus on open access in the
4400 Norwegian government. So far
499 signatures. I hope you will sign it
4406 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4407 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4408 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4409 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4410 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4411 project
</a
> have been going on for a while, and have presented the
4412 vision, ideas and solution several places. Here is a little
4413 collection of videos of talks and presentation of the project.
</p
>
4417 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4418 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4420 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4421 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4423 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4424 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4425 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4426 (Youtube)
</li
>
4428 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4429 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4431 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4432 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4434 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4435 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4436 York City in
2012</a
> (Youtube)
</li
>
4438 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4439 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4440 (Youtube)
</li
>
4442 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4443 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4445 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4446 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4448 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4449 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4450 2013</a
> (Youtube)
</li
>
4454 <p
>A larger list is available from
4455 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4456 Freedombox Wiki
</a
>.
</p
>
4458 <p
>On other news, I am happy to report that Freedombox based on Debian
4459 Jessie is coming along quite well, and soon both Owncloud and using
4460 Tor should be available for testers of the Freedombox solution. :) In
4461 a few weeks I hope everything needed to test it is included in Debian.
4462 The withsqlite package is already in Debian, and the plinth package is
4463 pending in NEW. The third and vital part of that puzzle is the
4464 metapackage/setup framework, which is still pending an upload. Join
4465 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4466 (#freedombox on irc.debian.org)
</a
> and
4467 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4468 mailing list
</a
> if you want to help make this vision come true.
</p
>
4473 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4474 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4475 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4476 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4477 <description><p
>I was introduced to the
4478 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4479 in
2010, when Eben Moglen presented his vision about serving the need
4480 of non-technical people to keep their personal information private and
4481 within the legal protection of their own homes. The idea is to give
4482 people back the power over their network and machines, and return
4483 Internet back to its intended peer-to-peer architecture. Instead of
4484 depending on a central service, the Freedombox will give everyone
4485 control over their own basic infrastructure.
</p
>
4487 <p
>I
've intended to join the effort since then, but other tasks have
4488 taken priority. But this summers nasty news about the misuse of trust
4489 and privilege exercised by the
"western
" intelligence gathering
4490 communities increased my eagerness to contribute to a point where I
4491 actually started working on the project a while back.
</p
>
4493 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4494 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4495 create a simple and cheap Debian based appliance that anyone can hook
4496 up in their home and get access to secure and private services and
4497 communication. The initial deployment platform have been the
4498 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4499 which is a piece of hardware I do not own. So to be able to test what
4500 the current Freedombox setup look like, I had to come up with a way to install
4501 it on some hardware I do have access to. I have rewritten the
4502 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4503 image build framework to use .deb packages instead of only copying
4504 setup into the boot images, and thanks to this rewrite I am able to
4505 set up any machine supported by Debian Wheezy as a Freedombox, using
4506 the previously mentioned deb (and a few support debs for packages
4507 missing in Debian).
</p
>
4509 <p
>The current Freedombox setup consist of a set of bootstrapping
4511 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4512 and a administrative web interface
4513 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4514 withsqlite), as well as a privacy enhancing proxy based on
4515 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4516 (freedombox-privoxy). There is also a web/javascript based XMPP
4517 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4518 trying (unsuccessfully so far) to talk to the XMPP server
4519 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4520 web interface is pluggable, and the goal is to use it to enable OpenID
4521 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4522 this is really working yet, see
4523 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4524 project TODO
</a
> for links to GIT repositories. Most of the code is
4525 on github at the moment. The HTTP proxy is operational out of the
4526 box, and the admin web interface can be used to add/remove plinth
4527 users. I
've not been able to do anything else with it so far, but
4528 know there are several branches spread around github and other places
4529 with lots of half baked features.
</p
>
4531 <p
>Anyway, if you want to have a look at the current state, the
4532 following recipes should work to give you a test machine to poke
4535 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4539 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4540 <li
>Boot from it, either as CD or USB stick.
</li
>
4541 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4542 to the Debian installer:
<p
>
4543 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4545 <li
>Answer the few language/region/password questions and pick disk to
4546 install on.
</li
>
4548 <li
>When the installation is finished and the machine have rebooted a
4549 few times, your Freedombox is ready for testing.
</li
>
4553 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4557 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4558 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4559 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4561 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4562 </pre
></li
>
4563 <li
><p
>Run this as root:
</p
>
4565 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4568 apt-get install freedombox-setup
4569 /usr/lib/freedombox/setup
4570 </pre
></li
>
4571 <li
>Reboot into your freshly created Freedombox.
</li
>
4575 <p
>You can test it on other architectures too, but because the
4576 freedombox-privoxy package is binary, it will only work as intended on
4577 the architectures where I have had time to build the binary and put it
4578 in my APT repository. But do not let this stop you. It is only a
4579 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4581 <p
>Note that by default Freedombox is a DHCP server on the
4582 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4583 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4584 disable
</tt
>" as root.
</p
>
4586 <p
>Please let me know if this works for you, or if you have any
4587 problems. We gather on the IRC channel
4588 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4589 irc.debian.org and the
4590 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4591 mailing list
</a
>.
</p
>
4593 <p
>Once you get your freedombox operational, you can visit
4594 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4595 welcome screen (dead end - do not be surprised if you are unable to
4596 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4597 to look at the rest of plinth. The default user is
'admin
' and the
4598 default password is
'secret
'.
</p
>
4603 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4604 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4605 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4606 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4607 <description><p
>Earlier, I reported about
4608 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4609 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4610 told by IBM that the original disk should be thrown away. And as
4611 there no longer was a problem if I bricked the firmware, I decided
4612 today to try to install Intel firmware to replace the Lenovo firmware
4613 currently on the disk.
</p
>
4615 <p
>I searched the Intel site for firmware, and found
4616 <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
>
4617 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4618 according to the site should contain the latest firmware for SSD
4619 disks. I inserted the broken disk in one of my spare laptops and
4620 booted the ISO from a USB stick. The disk was recognized, but the
4621 program claimed the newest firmware already were installed and refused
4622 to insert any Intel firmware. So no change, and the disk is still
4623 unable to handle write load. :( I guess the only way to get them
4624 working would be if Lenovo releases new firmware. No idea how likely
4625 that is. Anyway, just blogging about this test for completeness. I
4626 got a working Samsung disk, and see no point in spending more time on
4627 the broken disks.
</p
>
4632 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4633 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4634 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4635 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4636 <description><p
>Today I switched to
4637 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4638 new laptop
</a
>. I
've previously written about the problems I had with
4639 my new Thinkpad X230, which was delivered with an
4640 <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
4641 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4642 sustained writes. My hardware supplier have been very forthcoming in
4643 trying to find a solution, and after first trying with another
4644 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4645 disk instead to fix it once and for all. The Samsung disk survived
4646 the installation of Debian with encrypted disks (filling the disk with
4647 random data during installation killed the first two), and I thus
4648 decided to trust it with my data. I have installed it as a Debian Edu
4649 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4650 server at home using Kerberos and LDAP, and will use it as my work
4651 station from now on.
</p
>
4653 <p
>As this is a solid state disk with no moving parts, I believe the
4654 Debian Wheezy default installation need to be tuned a bit to increase
4655 performance and increase life time of the disk. The Linux kernel and
4656 user space applications do not yet adjust automatically to such
4657 environment. To make it easier for my self, I created a draft Debian
4658 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4659 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4660 for the ssd-setup package
</a
> is available from collab-maint, and it
4661 is set up to adjust the setup of the machine by just installing the
4662 package. If there is any non-SSD disk in the machine, the package
4663 will refuse to install, as I did not try to write any logic to sort
4664 file systems in SSD and non-SSD file systems.
</p
>
4666 <p
>I consider the package a draft, as I am a bit unsure how to best
4667 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4668 where I set up the machine with one large encrypted partition (in
4669 addition to /boot), put LVM on top of this and set up partitions on
4670 top of this again. See the README file in the package source for the
4671 references I used to pick the settings. At the moment these
4672 parameters are tuned:
</p
>
4676 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4677 (adding discard to /etc/crypttab)
</li
>
4679 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4680 this case a cryptsetup partition) by changing issue_discards from
4681 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4683 <li
>Set relatime as a file system option for ext3 and ext4 file
4686 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4687 /etc/fstab.
</li
>
4689 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4691 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4692 cron.daily).
</li
>
4694 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4695 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4699 <p
>During installation, I cancelled the part where the installer fill
4700 the disk with random data, as this would kill the SSD performance for
4701 little gain. My goal with the encrypted file system is to ensure
4702 those stealing my laptop end up with a brick and not a working
4703 computer. I have no hope in keeping the really resourceful people
4704 from getting the data on the disk (see
4705 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4706 Thus I concluded that adding the discard option to crypttab is the
4707 right thing to do.
</p
>
4709 <p
>I considered using the noop I/O scheduler, as several recommended
4710 it for SSD, but others recommended deadline and a benchmark I found
4711 indicated that deadline might be better for interactive use.
</p
>
4713 <p
>I also considered using the
'discard
' file system option for ext3
4714 and ext4, but read that it would give a performance hit ever time a
4715 file is removed, and thought it best to that that slowdown once a day
4716 instead of during my work.
</p
>
4718 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4719 this is already done by Debian Edu.
</p
>
4721 <p
>I have not yet started on the user space tuning. I expect
4722 iceweasel need some tuning, and perhaps other applications too, but
4723 have not yet had time to investigate those parts.
</p
>
4725 <p
>The package should work on Ubuntu too, but I have not yet tested it
4728 <p
>As for the answer to the question in the title of this blog post,
4729 as far as I know, the only solution I know about is to replace the
4730 disk. It might be possible to flash it with Intel firmware instead of
4731 the Lenovo firmware. But I have not tried and did not want to do so
4732 without approval from Lenovo as I wanted to keep the warranty on the
4733 disk until a solution was found and they wanted the broken disks
4739 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4740 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4741 <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>
4742 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4743 <description><p
>A few days ago, I wrote about
4744 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4745 problems I experienced with my new X230 and its SSD disk
</a
>, which
4746 was dying during installation because it is unable to cope with
4747 sustained write. My supplier is in contact with
4748 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
4749 replacement disk to try to fix the problem. They decided to send an
4750 identical model, so my hopes for a permanent fix was slim.
</p
>
4752 <p
>Anyway, today I got the replacement disk and tried to install
4753 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4754 same firmware version as the original. This time my hope raised
4755 slightly as the installation progressed, as the original disk used to
4756 die after
4-
7% of the disk was written to, while this time it kept
4757 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
4758 died again and I was back on square one. I still do not have a new
4759 laptop with a disk I can trust. I can not live with a disk that might
4760 lock up when I download a new
4761 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
4762 other large files. I look forward to hearing from my supplier with
4763 the next proposal from Lenovo.
</p
>
4765 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
4766 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4767 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4768 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4769 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4770 P/N
45N8295, P0C38732.
</p
>
4772 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4773 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4774 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4775 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4776 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4777 P/N
45N8295, P0C38732.
</p
>
4779 <p
>The only difference is in the first number (serial number?), ISN,
4780 SA, date and WNPP values. Mentioning all the details here in case
4781 someone is able to use the information to find a way to identify the
4782 failing disk among working ones (if any such working disk actually
4788 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4789 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4790 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4791 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4792 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4793 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4794 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4795 member assosiation NUUG
</a
> and
4796 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4797 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4798 Bitraf
</a
>.
</p
>
4800 <p
>It starts
10:
00 and continue until late evening. Everyone is
4801 welcome, and there is no fee to participate. There is on the other
4802 hand limited space, and only room for
30 people. Please put your name
4803 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4804 wiki page
</a
> if you plan to join us.
</p
>
4809 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4810 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4811 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4812 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4813 <description><p
>Half a year ago, I reported that I had to find a
4814 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4815 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4816 time to spend on it, and it took a while to find a model I believe
4817 will do the job, but two days ago the replacement finally arrived. I
4819 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4820 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4821 a roaming workstation, and it seemed to work flawlessly. But my
4822 second installation with encrypted disk was not as successful. More
4823 on that below.
</p
>
4825 <p
>I had a hard time trying to track down a good laptop, as my most
4826 important requirements (robust and with a good keyboard) are never
4827 listed in the feature list. But I did get good help from the search
4828 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4829 allowed me to limit the list of interesting laptops based on my other
4830 requirements. A bit surprising that SSD disk are not disks according
4831 to that search interface, so I had to drop specifying the number of
4832 disks from my search parameters. I also asked around among friends to
4833 get their impression on keyboards and robustness.
</p
>
4835 <p
>So the new laptop arrived, and it is quite a lot wider than the
4836 X41. I am not quite convinced about the keyboard, as it is
4837 significantly wider than my old keyboard, and I have to stretch my
4838 hand a lot more to reach the edges. But the key response is fairly
4839 good and the individual key shape is fairly easy to handle, so I hope
4840 I will get used to it. My old X40 was starting to fail, and I really
4841 needed a new laptop now. :)
</p
>
4843 <p
>Turning off the touch pad was simple. All it took was a quick
4844 visit to the BIOS during boot it disable it.
</p
>
4846 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4847 lock up during load. And this happen when installing Debian Wheezy
4848 with encrypted disk, while the disk is being filled with random data.
4849 I also tested to install Ubuntu Raring, and it happen there too if I
4850 reenable the code to fill the disk with random data (it is disabled by
4851 default in Ubuntu). And the bug with is already known. It was
4852 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4853 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4854 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4855 kernel developers as
4856 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4857 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4858 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4859 Lenovo forums, both for
4860 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4861 2012-
11-
10</a
> and for
4862 <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
4863 03-
20-
2013</a
>. The problem do not only affect installation. The
4864 reports state that the disk lock up during use if many writes are done
4865 on the disk, so it is much no use to work around the installation
4866 problem and end up with a computer that can lock up at any moment.
4868 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4869 available
</a
> that will lock up the hard drive after running a few
4870 minutes by writing to a file.
</p
>
4872 <p
>I
've contacted my supplier and asked how to handle this, and after
4873 contacting PCHELP Norway (request
01D1FDP) which handle support
4874 requests for Lenovo, his first suggestion was to upgrade the disk
4875 firmware. Unfortunately there is no newer firmware available from
4876 Lenovo, as my disk already have the most recent one (version LF1i). I
4877 hope to hear more from him today and hope the problem can be
4883 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4884 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4885 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4886 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4887 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4888 trusty old Thinkpad X41. Unfortunately I did not have much time to
4889 spend on it, but today the replacement finally arrived. I ended up
4890 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4891 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4892 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4893 this, it is installing what I hope will be a more final installation,
4894 with a encrypted hard drive to ensure any dope head stealing it end up
4895 with an expencive door stop.
</p
>
4897 <p
>I had a hard time trying to track down a good laptop, as my most
4898 important requirements (robust and with a good keyboard) are never
4899 listed in the feature list. But I did get good help from the search
4900 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4901 allowed me to limit the list of interesting laptops based on my other
4902 requirements. A bit surprising that SSD disk are not disks, so I had
4903 to drop number of disks from my search parameters.
</p
>
4905 <p
>I am not quite convinced about the keyboard, as it is significantly
4906 wider than my old keyboard, and I have to stretch my hand a lot more
4907 to reach the edges. But the key response is fairly good and the
4908 individual key shape is fairly easy to handle, so I hope I will get
4909 used to it. My old X40 was starting to fail, and I really needed a
4910 new laptop now. :)
</p
>
4912 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
4917 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
4918 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
4919 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
4920 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
4921 <description><p
>It annoys me when the computer fail to do automatically what it is
4922 perfectly capable of, and I have to do it manually to get things
4923 working. One such task is to find out what firmware packages are
4924 needed to get the hardware on my computer working. Most often this
4925 affect the wifi card, but some times it even affect the RAID
4926 controller or the ethernet card. Today I pushed version
0.4 of the
4927 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
4928 including a new script isenkram-autoinstall-firmware handling the
4929 process of asking all the loaded kernel modules what firmware files
4930 they want, find debian packages providing these files and install the
4931 debian packages. Here is a test run on my laptop:
</p
>
4933 <p
><pre
>
4934 # isenkram-autoinstall-firmware
4935 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4936 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4937 info: locating packages with the requested firmware files
4938 info: Updating APT sources after adding non-free APT source
4939 info: trying to install firmware-ipw2x00
4942 Preconfiguring packages ...
4943 Selecting previously deselected package firmware-ipw2x00.
4944 (Reading database ...
259727 files and directories currently installed.)
4945 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4946 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
4948 </pre
></p
>
4950 <p
>When all the requested firmware is present, a simple message is
4951 printed instead:
</p
>
4953 <p
><pre
>
4954 # isenkram-autoinstall-firmware
4955 info: did not find any firmware files requested by loaded kernel modules. exiting
4957 </pre
></p
>
4959 <p
>It could use some polish, but it is already working well and saving
4960 me some time when setting up new machines. :)
</p
>
4962 <p
>So, how does it work? It look at the set of currently loaded
4963 kernel modules, and look up each one of them using modinfo, to find
4964 the firmware files listed in the module meta-information. Next, it
4965 download the Contents file from a nearby APT mirror, and search for
4966 the firmware files in this file to locate the package with the
4967 requested firmware file. If the package is in the non-free section, a
4968 non-free APT source is added and the package is installed using
4969 <tt
>apt-get install
</tt
>. The end result is a slightly better working
4972 <p
>I hope someone find time to implement a more polished version of
4973 this script as part of the hw-detect debian-installer module, to
4974 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
4975 #
655507</a
>. There really is no need to insert USB sticks with
4976 firmware during a PXE install when the packages already are available
4977 from the nearby Debian mirror.
</p
>
4982 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
4983 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
4984 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
4985 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
4986 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4987 the screen just turn black when Linux boot, either during installation
4988 or on first boot from the hard disk. I
've seen it once in a while the
4989 last few years, but only recently understood the cause. I
've seen it
4990 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4991 The reason seem to be in the wiring of some laptops. The system to
4992 control the screen background light is inverted, so when Linux try to
4993 turn the brightness fully on, it end up turning it off instead. I do
4994 not know which Linux drivers are affected, but this post is about the
4995 i915 driver used by the
4996 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
4997 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
4999 <p
>The problem can be worked around two ways. Either by adding
5000 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5001 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5002 option when it load the i915 kernel module. On Debian and Ubuntu, it
5003 can be done by running these commands as root:
</p
>
5006 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5007 update-initramfs -u -k all
5010 <p
>Since March
2012 there is
5011 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5012 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5013 hardware have this problem, and get the driver to invert the
5014 brightness setting automatically. To use it, one need to add a row in
5015 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5016 intel_quirks array
</a
> in the driver source
5017 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5018 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5019 number (vendor number
8086 is assumed) and subdevice vendor and device
5022 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5023 -vvnn
</tt
> for the video card in question:
</p
>
5025 <p
><pre
>
5026 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5027 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5028 (rev
09) (prog-if
00 [VGA controller])
5029 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5030 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5031 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5032 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5033 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5035 Interrupt: pin A routed to IRQ
42
5036 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5037 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5038 Region
4: I/O ports at
4000 [size=
64]
5039 Expansion ROM at
<unassigned
> [disabled]
5040 Capabilities:
<access denied
>
5041 Kernel driver in use: i915
5042 </pre
></p
>
5044 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5046 <p
><pre
>
5047 struct intel_quirk intel_quirks[] = {
5049 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5050 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5053 </pre
></p
>
5055 <p
>According to the kernel module instructions (as seen using
5056 <tt
>modinfo i915
</tt
>), information about hardware needing the
5057 invert_brightness flag should be sent to the
5058 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5059 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5060 developers. But my email about the laptop sent
2013-
06-
03 have not
5062 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5063 web archive for the mailing list
</a
>, so I suspect they do not accept
5064 emails from non-subscribers. Because of this, I sent my patch also to
5065 the Debian bug tracking system instead as
5066 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5067 sure the patch is not lost.
</p
>
5069 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5070 with this problem working properly with Linux. If you use Gnome, your
5071 worries should be over at this point. But if you use KDE, there is
5072 something in KDE ignoring the invert_brightness setting and turning on
5073 the screen during login. I
've reported it to Debian as
5074 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5075 have no idea yet how to figure out exactly what subsystem is doing
5076 this. Perhaps you can help? Perhaps you know what the Gnome
5077 developers did to handle this, and this can give a clue to the KDE
5078 developers? Or you know where in KDE the screen brightness is changed
5079 during login? If so, please update the BTS report (or get in touch if
5080 you do not know how to update BTS).
</p
>
5082 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5083 acpi_backlight=vendor, to disable ACPI backlight support completely,
5084 as the ACPI information on the machine is trash and it is better to
5085 leave it to the intel video driver to control the screen
5086 backlight.
</p
>
5091 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5092 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5093 <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>
5094 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5095 <description><p
>Two days ago, I asked
5096 <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
5097 I could install Linux on a Packard Bell EasyNote LV computer
5098 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5099 with the obstacles put in the way of Linux users on a laptop with UEFI
5100 and Windows
8.
</p
>
5102 <p
>I never found out if the cause of my problems were the use of UEFI
5103 secure booting or fast boot. I suspect fast boot was the problem,
5104 causing the firmware to boot directly from HD without considering any
5105 key presses and alternative devices, but do not know UEFI settings
5106 enough to tell.
</p
>
5108 <p
>There is no way to install Linux on the machine in question without
5109 opening the box and disconnecting the hard drive! This is as far as I
5110 can tell, the only way to get access to the firmware setup menu
5111 without accepting the Windows
8 license agreement. I am told (and
5112 found description on how to) that it is possible to configure the
5113 firmware setup once booted into Windows
8. But as I believe the terms
5114 of that agreement are completely unacceptable, accepting the license
5115 was never an alternative. I do not enter agreements I do not intend
5116 to follow.
</p
>
5118 <p
>I feared I had to return the laptops and ask for a refund, and
5119 waste many hours on this, but luckily there was a way to get it to
5120 work. But I would not recommend it to anyone planning to run Linux on
5121 it, and I have become sceptical to Windows
8 certified laptops. Is
5122 this the way Linux will be forced out of the market place, by making
5123 it close to impossible for
"normal
" users to install Linux without
5124 accepting the Microsoft Windows license terms? Or at least not
5125 without risking to loose the warranty?
</p
>
5127 <p
>I
've updated the
5128 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5129 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5130 do not have to struggle as much as I did to get Linux into the
5133 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5134 Michael Tokarev and others for feedback and ideas.
</p
>
5139 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5140 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5141 <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>
5142 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5143 <description><p
>I
've run into quite a problem the last few days. I bought three
5144 new laptops for my parents and a few others. I bought Packard Bell
5145 Easynote LV to run Kubuntu on and use as their home computer. But I
5146 am completely unable to figure out how to install Linux on it. The
5147 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5148 instead of a BIOS to boot.
</p
>
5150 <p
>The problem is that I am unable to get it to PXE boot, and unable
5151 to get it to boot the Linux installer from my USB stick. I have yet
5152 to try the DVD install, and still hope it will work. when I turn on
5153 the computer, there is no information on what buttons to press to get
5154 the normal boot menu. I expect to get some boot menu to select PXE or
5155 USB stick booting. When booting, it first ask for the language to
5156 use, then for some regional settings, and finally if I will accept the
5157 Windows
8 terms of use. As these terms are completely unacceptable to
5158 me, I have no other choice but to turn off the computer and try again
5159 to get it to boot the Linux installer.
</p
>
5161 <p
>I have gathered my findings so far on a Linlap page about the
5162 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5163 EasyNote LV
</a
> model. If you have any idea how to get Linux
5164 installed on this machine, please get in touch or update that wiki
5165 page. If I can
't find a way to install Linux, I will have to return
5166 the laptop to the seller and find another machine for my parents.
</p
>
5168 <p
>I wonder, is this the way Linux will be forced out of the market
5169 using UEFI and
"secure boot
" by making it impossible to install Linux
5170 on new Laptops?
</p
>
5175 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5176 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5177 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5178 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5179 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5180 an operating system based on Debian intended for use in schools. It
5181 contain a turn-key solution for the computer network provided to
5182 pupils in the primary schools. It provide both the central server,
5183 network boot servers and desktop environments with heaps of
5184 educational software. The project was founded almost
12 years ago,
5185 2001-
07-
02. If you want to support the project, which is in need for
5186 cash to fund developer gatherings and other project related activity,
5187 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5188 donate some money
</a
>.
5190 <p
>A topic that come up again and again on the Debian Edu mailing
5191 lists and elsewhere, is the question on how to transform a Debian or
5192 Ubuntu installation into a Debian Edu installation. It isn
't very
5193 hard, and last week I wrote a script to replicate the steps done by
5194 the Debian Edu installer.
</p
>
5196 <p
>The script,
5197 <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/
>
5198 in the debian-edu-config package, will go through these six steps and
5199 transform an existing Debian Wheezy or Ubuntu (untested) installation
5200 into a Debian Edu Workstation:
</p
>
5204 <li
>Add skolelinux related APT sources.
</li
>
5205 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5206 <li
>Install debian-edu-install to load preseeding values and pull in
5207 our configuration.
</li
>
5208 <li
>Preseed debconf database with profile setup in
5209 /etc/debian-edu/config, and run tasksel to install packages
5210 according to the profile specified in the config above,
5211 overriding some of the Debian automation machinery.
</li
>
5212 <li
>Run debian-edu-cfengine-D installation to configure everything
5213 that could not be done using preseeding.
</li
>
5214 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5218 <p
>There are some steps in the Debian Edu installation that can not be
5219 replicated like this. Disk partitioning and LVM setup, for example.
5220 So this script just assume there is enough disk space to install all
5221 the needed packages.
</p
>
5223 <p
>The script was created to help a Debian Edu student working on
5224 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5225 Debian Edu client, and using it he can take the existing
5226 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5227 transform it into a fully functioning Debian Edu Workstation (or
5228 Roaming Workstation, or whatever :).
</p
>
5230 <p
>The default setting in the script is to create a KDE Workstation.
5231 If a LXDE based Roaming workstation is wanted instead, modify the
5232 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5234 <p
><pre
>
5235 PROFILE=
"Roaming-Workstation
"
5236 DESKTOP=
"lxde
"
5237 </pre
></p
>
5239 <p
>The script could even become useful to set up Debian Edu servers in
5240 the cloud, by starting with a virtual Debian installation at some
5241 virtual hosting service and setting up all the services on first
5247 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5248 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5249 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5250 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5251 <description><P
>In January,
5252 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5253 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5254 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5255 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5256 marvellous construction system from Denmark. We also created
5257 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5258 a place to take notes and write down our plans and hopes. And several
5259 people showed up to help. I was very happy to see the effect of my
5260 call. Since the small start, we have a debtags tag
5261 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5262 tag for LEGO related packages, and now count
10 packages related to
5263 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5265 <p
><table
>
5266 <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
>
5267 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5268 <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
>
5269 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5270 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5271 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5272 <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
>
5273 <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
>
5274 <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
>
5275 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5276 </table
></p
>
5278 <p
>Some of these are available in Wheezy, and all but one are
5279 currently available in Jessie/testing. leocad is so far only
5280 available in experimental.
</p
>
5282 <p
>If you care about LEGO in Debian, please join us on IRC and help
5283 adding the rest of the great free software tools available on Linux
5284 for LEGO designers.
</p
>
5289 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5290 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5291 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5292 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5293 <description><p
>When I woke up this morning, I was very happy to see that the
5294 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5295 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5296 Debian release, and I expect to move my machines at home over to it fairly
5299 <p
>The new debian release contain heaps of new stuff, and one program
5300 in particular make me very happy to see included. The
5301 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5302 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5303 included for the first time. Alongside similar programs like
5304 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5305 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5306 it allow for visual programming where syntax errors can not happen,
5307 and a friendly programming environment for learning to control the
5308 computer. Scratch will also be included in the next release of Debian
5311 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5312 Edu/Skolelinux release too. The
5313 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5314 alpha release
</a
> went out last week, and the next should soon
5320 <title>Isenkram
0.2 finally in the Debian archive
</title>
5321 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5322 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5323 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5324 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5325 package
</a
> finally made it into the archive, after lingering in NEW
5326 for many months. I uploaded it to the Debian experimental suite
5327 2013-
01-
27, and today it was accepted into the archive.
</p
>
5329 <p
>Isenkram is a system for suggesting to users what packages to
5330 install to work with a pluggable hardware device. The suggestion pop
5331 up when the device is plugged in. For example if a Lego Mindstorm NXT
5332 is inserted, it will suggest to install the program needed to program
5333 the NXT controller. Give it a go, and report bugs and suggestions to
5339 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5340 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5342 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5343 <description><p
>My
5344 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5345 bitcoin related blog post
</a
> mentioned that the new
5346 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5347 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5348 2013-
01-
19, and have been available in unstable since then. It was
5349 automatically copied to Ubuntu, and is available in their Raring
5350 version too.
</p
>
5352 <p
>But there is a strange problem with the build that block this new
5353 version from being available on the i386 and kfreebsd-i386
5354 architectures. For some strange reason, the autobuilders in Debian
5355 for these architectures fail to run the test suite on these
5356 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5357 We are so far unable to reproduce it when building it manually, and
5358 no-one have been able to propose a fix. If you got an idea what is
5359 failing, please let us know via the BTS.
</p
>
5361 <p
>One feature that is annoying me with of the bitcoin client, because
5362 I often run low on disk space, is the fact that the client will exit
5363 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5364 #
696715</a
>). So make sure you have enough disk space when you run
5367 <p
>As usual, if you use bitcoin and want to show your support of my
5368 activities, please send Bitcoin donations to my address
5369 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5374 <title>Welcome to the world, Isenkram!
</title>
5375 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5376 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5377 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5378 <description><p
>Yesterday, I
5379 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5380 for testers
</a
> for my prototype for making Debian better at handling
5381 pluggable hardware devices, which I
5382 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5383 out to create
</a
> earlier this month. Several valuable testers showed
5384 up, and caused me to really want to to open up the development to more
5385 people. But before I did this, I want to come up with a sensible name
5386 for this project. Today I finally decided on a new name, and I have
5387 renamed the project from hw-support-handler to this new name. In the
5388 process, I moved the source to git and made it available as a
5389 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5390 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5391 To fetch and build the latest version of the source, use
</p
>
5394 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5395 cd isenkram
&& git-buildpackage -us -uc
5398 <p
>I have not yet adjusted all files to use the new name yet. If you
5399 want to hack on the source or improve the package, please go ahead.
5400 But please talk to me first on IRC or via email before you do major
5401 changes, to make sure we do not step on each others toes. :)
</p
>
5403 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5404 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5405 stuff, in other words. I
've been told it is the Norwegian variant of
5406 the German word eisenkram, for those that are familiar with that
5409 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5410 instructions, to avoid confusing people with an error from the signing
5413 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5414 clone argument to avoid the need for authentication.
</p
>
5419 <title>First prototype ready making hardware easier to use in Debian
</title>
5420 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5421 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5422 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5423 <description><p
>Early this month I set out to try to
5424 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5425 the Debian support for pluggable hardware devices
</a
>. Now my
5426 prototype is working, and it is ready for a larger audience. To test
5428 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5429 from the Debian Edu subversion repository
</a
>, build and install the
5430 package. You might have to log out and in again activate the
5431 autostart script.
</p
>
5433 <p
>The design is simple:
</p
>
5437 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5438 hw-support-handlerd to start when the user log in.
</li
>
5440 <li
>This program listen for kernel events about new hardware (directly
5441 from the kernel like udev does), not using HAL dbus events as I
5442 initially did.
</li
>
5444 <li
>When new hardware is inserted, look up the hardware modalias in
5445 the APT database, a database
5446 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5447 via HTTP
</a
> and a database available as part of the package.
</li
>
5449 <li
>If a package is mapped to the hardware in question, the package
5450 isn
't installed yet and this is the first time the hardware was
5451 plugged in, show a desktop notification suggesting to install the
5452 package or packages.
</li
>
5454 <li
>If the user click on the
'install package now
' button, ask
5455 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5457 <li
>aptdaemon ask for root password or sudo password, and install the
5458 package while showing progress information in a window.
</li
>
5462 <p
>I still need to come up with a better name for the system. Here
5463 are some screen shots showing the prototype in action. First the
5464 notification, then the password request, and finally the request to
5465 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5467 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5468 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5469 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5470 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5471 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5473 <p
>The prototype still need to be improved with longer timeouts, but
5474 is already useful. The database of hardware to package mappings also
5475 need more work. It is currently compatible with the Ubuntu way of
5476 storing such information in the package control file, but could be
5477 changed to use other formats instead or in addition to the current
5478 method. I
've dropped the use of discover for this mapping, as the
5479 modalias approach is more flexible and easier to use on Linux as long
5480 as the Linux kernel expose its modalias strings directly.
</p
>
5482 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5483 here is the command required to check out and build the source: Use
5484 '<tt
>svn checkout
5485 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5486 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5487 devscripts package.
</p
>
5489 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5490 renamed to Isenkram and the source moved from the Debian Edu
5491 subversion repository to a Debian collab-maint git repository. See
5492 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5493 instructions
</a
> for details.
</p
>
5498 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5499 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5500 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5501 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5502 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5503 suddenly in bed. With a quiet whimper, it went completely quiet and
5504 black. The power button was no longer able to turn it on. It was a
5505 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5506 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5507 Compaq I had before that. Now I need to find a replacement. To keep
5508 going during Christmas, I moved the one year old SSD disk to my old
5509 X40 where it fitted (only one I had left that could use it), but it is
5510 not a durable solution.
5512 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5513 got a new one more than
10 years ago. It still holds true.:)
</p
>
5517 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5518 than A4).
</li
>
5519 <li
>Robust, it will be in my backpack every day.
</li
>
5520 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5521 <li
>Long battery life time. Preferable a week.
</li
>
5522 <li
>Internal WIFI network card.
</li
>
5523 <li
>Internal Twisted Pair network card.
</li
>
5524 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5525 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5526 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5528 <li
>Hardware supported by Debian Stable, ie the default kernel and
5529 X.org packages.
</li
>
5530 <li
>Quiet, preferably fan free (or at least not using the fan most of
5535 <p
>You will notice that there are no RAM and CPU requirements in the
5536 list. The reason is simply that the specifications on laptops the
5537 last
10-
15 years have been sufficient for my needs, and I have to look
5538 at other features to choose my laptop. But are there still made as
5539 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5540 robust, and Thinkpads seem to be heading in the wrong direction since
5541 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5542 still be useful.
</p
>
5544 <p
>Perhaps I should rethink my needs, and look for a pad with an
5545 external keyboard? I
'll have to check the
5546 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5547 well-supported laptops, or perhaps just buy one preinstalled from one
5548 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5549 Pre-loaded site
</a
>.
</p
>
5554 <title>How to find a browser plugin supporting a given MIME type
</title>
5555 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5556 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5557 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5558 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5559 install to get support for a given MIME type. Thanks to
5560 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5561 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5562 Unfortunately, not very many packages provide the needed meta
5563 information, Anyway, here is a small script to look up all browser
5564 plugin packages announcing ther MIME support using this specification:
</p
>
5570 def pkgs_handling_mimetype(mimetype):
5575 version = pkg.candidate
5577 version = pkg.installed
5580 record = version.record
5581 if not record.has_key(
'Npp-MimeType
'):
5583 mime_types = record[
'Npp-MimeType
'].split(
',
')
5584 for t in mime_types:
5585 t = t.rstrip().strip()
5587 thepkgs.append(pkg.name)
5589 mimetype =
"audio/ogg
"
5590 if
1 < len(sys.argv):
5591 mimetype = sys.argv[
1]
5592 print
"Browser plugin packages supporting %s:
" % mimetype
5593 for pkg in pkgs_handling_mimetype(mimetype):
5594 print
" %s
" %pkg
5597 <p
>It can be used like this to look up a given MIME type:
</p
>
5600 % ./apt-find-browserplug-for-mimetype
5601 Browser plugin packages supporting audio/ogg:
5603 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5604 Browser plugin packages supporting application/x-shockwave-flash:
5605 browser-plugin-gnash
5609 <p
>In Ubuntu this mechanism is combined with support in the browser
5610 itself to query for plugins and propose to install the needed
5611 packages. It would be great if Debian supported such feature too. Is
5612 anyone working on adding it?
</p
>
5614 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5615 request for icweasel support for this feature is
5616 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5617 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5618 of manpower and wish for a different design is the reason thus feature
5619 is not yet in iceweasel from Debian.
</p
>
5624 <title>What is the most supported MIME type in Debian?
</title>
5625 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5626 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5627 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5628 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5629 proposal to add AppStream information to the Debian archive
</a
>, is a
5630 proposal to make it possible for a Desktop application to propose to
5631 the user some package to install to gain support for a given MIME
5632 type, font, library etc. that is currently missing. With such
5633 mechanism in place, it would be possible for the desktop to
5634 automatically propose and install leocad if some LDraw file is
5635 downloaded by the browser.
</p
>
5637 <p
>To get some idea about the current content of the archive, I decided
5638 to write a simple program to extract all .desktop files from the
5639 Debian archive and look up the claimed MIME support there. The result
5641 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5642 site
</a
>. Using the collected information, it become possible to
5643 answer the question in the title. Here are the
20 most supported MIME
5644 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5645 The complete list is available from the link above.
</p
>
5647 <p
><strong
>Debian Stable:
</strong
></p
>
5651 ----- -----------------------
5667 18 application/x-ogg
5674 <p
><strong
>Debian Testing:
</strong
></p
>
5678 ----- -----------------------
5694 18 application/x-ogg
5701 <p
><strong
>Debian Unstable:
</strong
></p
>
5705 ----- -----------------------
5722 18 application/x-ogg
5728 <p
>I am told that PackageKit can provide an API to access the kind of
5729 information mentioned in DEP-
11. I have not yet had time to look at
5730 it, but hope the PackageKit people in Debian are on top of these
5733 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5734 discovering a typo in my script.
</p
>
5739 <title>Using modalias info to find packages handling my hardware
</title>
5740 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5741 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5742 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5743 <description><p
>Yesterday, I wrote about the
5744 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5745 values provided by the Linux kernel
</a
> following my hope for
5746 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5747 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5748 modalias values attached to package names can be used to map packages
5749 to hardware. This allow the system to look up and suggest relevant
5750 packages when I plug in some new hardware into my machine, and replace
5751 discover and discover-data as the database used to map hardware to
5754 <p
>I create a modaliases file with entries like the following,
5755 containing package name, kernel module name (if relevant, otherwise
5756 the package name) and globs matching the relevant hardware
5759 <p
><blockquote
>
5760 Package: package-name
5761 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
5762 </blockquote
></p
>
5764 <p
>It is fairly trivial to write code to find the relevant packages
5765 for a given modalias value using this file.
</p
>
5767 <p
>An entry like this would suggest the video and picture application
5768 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5770 <p
><blockquote
>
5772 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5773 </blockquote
></p
>
5775 <p
>An entry like this would suggest the pcmciautils package when a
5776 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5778 <p
><blockquote
>
5779 Package: pcmciautils
5780 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5781 </blockquote
></p
>
5783 <p
>An entry like this would suggest the package colorhug-client when
5784 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5786 <p
><blockquote
>
5787 Package: colorhug-client
5788 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5789 </blockquote
></p
>
5791 <p
>I believe the format is compatible with the format of the Packages
5792 file in the Debian archive. Ubuntu already uses their Packages file
5793 to store their mappings from packages to hardware.
</p
>
5795 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5796 announce the hardware it support in a way my prototype understand.
5797 This allow those publishing packages in an APT source outside the
5798 Debian archive as well as those backporting packages to make sure the
5799 hardware mapping are included in the package meta information. I
've
5800 tested such header in the pymissile package, and its modalias mapping
5801 is working as it should with my prototype. It even made it to Ubuntu
5804 <p
>To test if it was possible to look up supported hardware using only
5805 the shell tools available in the Debian installer, I wrote a shell
5806 implementation of the lookup code. The idea is to create files for
5807 each modalias and let the shell do the matching. Please check out and
5809 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5810 shell script. It run without any extra dependencies and fetch the
5811 hardware mappings from the Debian archive and the subversion
5812 repository where I currently work on my prototype.
</p
>
5814 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5815 install yubikey-personalization:
</p
>
5817 <p
><blockquote
>
5818 % ./hw-support-lookup
5819 <br
>yubikey-personalization
5821 </blockquote
></p
>
5823 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5824 propose to install the pcmciautils package:
</p
>
5826 <p
><blockquote
>
5827 % ./hw-support-lookup
5828 <br
>pcmciautils
5830 </blockquote
></p
>
5832 <p
>If you know of any hardware-package mapping that should be added to
5833 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5834 database
</a
>, please tell me about it.
</p
>
5836 <p
>It could be possible to generate several of the mappings between
5837 packages and hardware. One source would be to look at packages with
5838 kernel modules, ie packages with *.ko files in /lib/modules/, and
5839 extract their modalias information. Another would be to look at
5840 packages with udev rules, ie packages with files in
5841 /lib/udev/rules.d/, and extract their vendor/model information to
5842 generate a modalias matching rule. I have not tested any of these to
5843 see if it work.
</p
>
5845 <p
>If you want to help implementing a system to let us propose what
5846 packages to install when new hardware is plugged into a Debian
5847 machine, please send me an email or talk to me on
5848 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5853 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5854 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5855 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5856 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5857 <description><p
>While looking into how to look up Debian packages based on hardware
5858 information, to find the packages that support a given piece of
5859 hardware, I refreshed my memory regarding modalias values, and decided
5860 to document the details. Here are my findings so far, also available
5862 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5863 Debian Edu subversion repository
</a
>:
5865 <p
><strong
>Modalias decoded
</strong
></p
>
5867 <p
>This document try to explain what the different types of modalias
5868 values stands for. It is in part based on information from
5869 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5870 &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;,
5871 &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
5872 &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;.
5874 <p
>The modalias entries for a given Linux machine can be found using
5875 this shell script:
</p
>
5878 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5881 <p
>The supported modalias globs for a given kernel module can be found
5882 using modinfo:
</p
>
5885 % /sbin/modinfo psmouse | grep alias:
5886 alias: serio:ty05pr*id*ex*
5887 alias: serio:ty01pr*id*ex*
5891 <p
><strong
>PCI subtype
</strong
></p
>
5893 <p
>A typical PCI entry can look like this. This is an Intel Host
5894 Bridge memory controller:
</p
>
5896 <p
><blockquote
>
5897 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5898 </blockquote
></p
>
5900 <p
>This represent these values:
</p
>
5905 sv
00001028 (subvendor)
5906 sd
000001AD (subdevice)
5908 sc
00 (bus subclass)
5912 <p
>The vendor/device values are the same values outputted from
'lspci
5913 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
5914 0600. The
0600 class is a host bridge. Other useful bus values are
5915 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
5917 <p
>Not sure how to figure out the interface value, nor what it
5920 <p
><strong
>USB subtype
</strong
></p
>
5922 <p
>Some typical USB entries can look like this. This is an internal
5923 USB hub in a laptop:
</p
>
5925 <p
><blockquote
>
5926 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5927 </blockquote
></p
>
5929 <p
>Here is the values included in this alias:
</p
>
5932 v
1D6B (device vendor)
5933 p
0001 (device product)
5935 dc
09 (device class)
5936 dsc
00 (device subclass)
5937 dp
00 (device protocol)
5938 ic
09 (interface class)
5939 isc
00 (interface subclass)
5940 ip
00 (interface protocol)
5943 <p
>The
0900 device class/subclass means hub. Some times the relevant
5944 class is in the interface class section. For a simple USB web camera,
5945 these alias entries show up:
</p
>
5947 <p
><blockquote
>
5948 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5949 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5950 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5951 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5952 </blockquote
></p
>
5954 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
5955 camera),
0101 is audio control device and
0102 is audio streaming (aka
5956 microphone). Thus this is a camera with microphone included.
</p
>
5958 <p
><strong
>ACPI subtype
</strong
></p
>
5960 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
5961 receiver in a Thinkpad X40:
</p
>
5963 <p
><blockquote
>
5964 acpi:IBM0071:PNP0511:
5965 </blockquote
></p
>
5967 <p
>The values between the colons are IDs.
</p
>
5969 <p
><strong
>DMI subtype
</strong
></p
>
5971 <p
>The DMI table contain lots of information about the computer case
5972 and model. This is an entry for a IBM Thinkpad X40, fetched from
5973 /sys/devices/virtual/dmi/id/modalias:
</p
>
5975 <p
><blockquote
>
5976 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5977 </blockquote
></p
>
5979 <p
>The values present are
</p
>
5982 bvn IBM (BIOS vendor)
5983 bvr
1UETB
6WW(
1.66) (BIOS version)
5984 bd
06/
15/
2005 (BIOS date)
5985 svn IBM (system vendor)
5986 pn
2371H4G (product name)
5987 pvr ThinkPadX40 (product version)
5988 rvn IBM (board vendor)
5989 rn
2371H4G (board name)
5990 rvr NotAvailable (board version)
5991 cvn IBM (chassis vendor)
5992 ct
10 (chassis type)
5993 cvr NotAvailable (chassis version)
5996 <p
>The chassis type
10 is Notebook. Other interesting values can be
5997 found in the dmidecode source:
</p
>
6001 4 Low Profile Desktop
6014 17 Main Server Chassis
6015 18 Expansion Chassis
6017 20 Bus Expansion Chassis
6018 21 Peripheral Chassis
6020 23 Rack Mount Chassis
6029 <p
>The chassis type values are not always accurately set in the DMI
6030 table. For example my home server is a tower, but the DMI modalias
6031 claim it is a desktop.
</p
>
6033 <p
><strong
>SerIO subtype
</strong
></p
>
6035 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6036 test machine:
</p
>
6038 <p
><blockquote
>
6039 serio:ty01pr00id00ex00
6040 </blockquote
></p
>
6042 <p
>The values present are
</p
>
6051 <p
>This type is supported by the psmouse driver. I am not sure what
6052 the valid values are.
</p
>
6054 <p
><strong
>Other subtypes
</strong
></p
>
6056 <p
>There are heaps of other modalias subtypes according to
6057 file2alias.c. There is the rest of the list from that source: amba,
6058 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6059 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6060 vmbus, x86cpu and zorro. I did not spend time documenting all of
6061 these, as they do not seem relevant for my intended use with mapping
6062 hardware to packages when new stuff is inserted during run time.
</p
>
6064 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6066 <p
>To check which kernel modules provide support for a given modalias,
6067 one can use the following shell script:
</p
>
6070 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6071 echo
"$id
" ; \
6072 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6076 <p
>The output can look like this (only the first few entries as the
6077 list is very long on my test machine):
</p
>
6081 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6083 FATAL: Module acpi:device: not found.
6085 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6086 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6087 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6088 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6089 acpi:IBM0071:PNP0511:
6090 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6091 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6092 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6096 <p
>If you want to help implementing a system to let us propose what
6097 packages to install when new hardware is plugged into a Debian
6098 machine, please send me an email or talk to me on
6099 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6101 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6102 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6103 in /sys/ with space in them.
</p
>
6108 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6109 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6110 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6111 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6112 <description><p
>As part of my investigation on how to improve the support in Debian
6113 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6114 Launcher and updated the Debian package
6115 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6116 sure udev will fix the device permissions when it is plugged in. I
6117 also added a
"Modaliases
" header to test it in the Debian archive and
6118 hopefully make the package be proposed by jockey in Ubuntu when a user
6119 plug in his rocket launcher. In the process I moved the source to a
6120 git repository under collab-maint, to make it easier for any DD to
6121 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6122 is not very active, but the software still work for me even after five
6123 years of relative silence. The new git repository is not listed in
6124 the uploaded package yet, because I want to test the other changes a
6125 bit more before I upload the new version. If you want to check out
6126 the new version with a .desktop file included, visit the
6127 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6128 view
</a
> or use
"<tt
>git clone
6129 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6134 <title>Lets make hardware dongles easier to use in Debian
</title>
6135 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6137 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6138 <description><p
>One thing that annoys me with Debian and Linux distributions in
6139 general, is that there is a great package management system with the
6140 ability to automatically install software packages by downloading them
6141 from the distribution mirrors, but no way to get it to automatically
6142 install the packages I need to use the hardware I plug into my
6143 machine. Even if the package to use it is easily available from the
6144 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6145 suggest to automatically install the python-nxt, nbc and t2n packages
6146 I need to talk to it. When I plug in a Yubikey, it could propose the
6147 yubikey-personalization package. The information required to do this
6148 is available, but no-one have pulled all the pieces together.
</p
>
6150 <p
>Some years ago, I proposed to
6151 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6152 the discover subsystem to implement this
</a
>. The idea is fairly
6157 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6158 starting when a user log in.
</li
>
6160 <li
>Set this program up to listen for kernel events emitted when new
6161 hardware is inserted into the computer.
</li
>
6163 <li
>When new hardware is inserted, look up the hardware ID in a
6164 database mapping to packages, and take note of any non-installed
6165 packages.
</li
>
6167 <li
>Show a message to the user proposing to install the discovered
6168 package, and make it easy to install it.
</li
>
6172 <p
>I am not sure what the best way to implement this is, but my
6173 initial idea was to use dbus events to discover new hardware, the
6174 discover database to find packages and
6175 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6178 <p
>Yesterday, I found time to try to implement this idea, and the
6179 draft package is now checked into
6180 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6181 Debian Edu subversion repository
</a
>. In the process, I updated the
6182 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6183 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6184 the relevant packages in Debian, and uploaded a new version
6185 2.2013.01.09 to unstable. I also discovered that the current
6186 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6187 package in Debian no longer discovered any USB devices, because
6188 /proc/bus/usb/devices is no longer present. I ported it to use
6189 libusb as a fall back option to get it working. The fixed package
6190 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6191 because of the freeze).
</p
>
6193 <p
>With this prototype in place, I can insert my Yubikey, and get this
6194 desktop notification to show up (only once, the first time it is
6195 inserted):
</p
>
6197 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6199 <p
>For this prototype to be really useful, some way to automatically
6200 install the proposed packages by pressing the
"Please install
6201 program(s)
" button should to be implemented.
</p
>
6203 <p
>If this idea seem useful to you, and you want to help make it
6204 happen, please help me update the discover-data database with mappings
6205 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6206 list the package you would like to have installed when a given
6207 hardware device is inserted into your computer, and report bugs using
6208 reportbug if it isn
't. Or, if you know of a better way to provide
6209 such mapping, please let me know.
</p
>
6211 <p
>This prototype need more work, and there are several questions that
6212 should be considered before it is ready for production use. Is dbus
6213 the correct way to detect new hardware? At the moment I look for HAL
6214 dbus events on the system bus, because that is the events I could see
6215 on my Debian Squeeze KDE desktop. Are there better events to use?
6216 How should the user be notified? Is the desktop notification
6217 mechanism the best option, or should the background daemon raise a
6218 popup instead? How should packages be installed? When should they
6219 not be installed?
</p
>
6221 <p
>If you want to help getting such feature implemented in Debian,
6222 please send me an email. :)
</p
>
6227 <title>New IRC channel for LEGO designers using Debian
</title>
6228 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6229 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6230 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6231 <description><p
>During Christmas, I have worked a bit on the Debian support for
6232 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6233 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6234 discovered I had to build all the tools myself because none were
6235 already in Debian Squeeze. If Debian support for LEGO is something
6236 you care about, please join me on the IRC channel
6237 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6238 irc.debian.org). There is a lot that could be done to improve the
6239 Debian support for LEGO designers. For example both CAD software
6240 and Mindstorm compilers are missing. :)
</p
>
6242 <p
>Update
2012-
01-
03: A
6243 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6244 including links to Lego related packages is now available.
</p
>
6249 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6250 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6251 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6252 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6253 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6254 year! I hope next year will prove to be a good year.
</p
>
6256 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6257 decentralised
"currency
" that allow people to transfer bitcoins
6258 between each other with minimal overhead, is a very interesting
6259 experiment. And as I wrote a few days ago, the bitcoin situation in
6260 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6261 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6262 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6263 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6264 for one of the ftpmasters to approve the new bitcoin-qt package
6267 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6268 team in Debian, you can easily test the package in Debian Squeeze
6269 using the following steps to get a set of working packages:
</p
>
6271 <blockquote
><pre
>
6272 git clone git://git.debian.org/git/collab-maint/bitcoin
6274 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6275 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6276 </pre
></blockquote
>
6278 <p
>You might have to install some build dependencies as well. The
6279 list of commands should give you two packages, bitcoind and
6280 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6281 client will download the complete set of bitcoin
"blocks
", which need
6282 around
5.6 GiB of data on my machine at the moment. Make sure your
6283 ~/.bitcoin/ directory have lots of spare room if you want to download
6284 all the blocks. The client will warn if the disk is getting full, so
6285 there is not really a problem if you got too little room, but you will
6286 not be able to get all the features out of the client.
</p
>
6288 <p
>As usual, if you use bitcoin and want to show your support of my
6289 activities, please send Bitcoin donations to my address
6290 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6295 <title>A word on bitcoin support in Debian
</title>
6296 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6297 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6298 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6299 <description><p
>It has been a while since I wrote about
6300 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6301 peer-to-peer based crypto-currency, and the reason is simply that I
6302 have been busy elsewhere. But two days ago, I started looking at the
6303 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6304 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6305 is now maintained by a
6306 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6307 people
</a
>, and the grunt work had already been done by this team. We
6308 owe a huge thank you to all these team members. :)
6309 But I was sad to discover that the bitcoin client is missing in
6310 Wheezy. It is only available in Sid (and an outdated client from
6311 backports). The client had several RC bugs registered in BTS blocking
6312 it from entering testing. To try to help the team and improve the
6313 situation, I spent some time providing patches and triaging the bug
6314 reports. I also had a look at the bitcoin package available from Matt
6316 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6317 Ubuntu
</a
>, and moved the useful pieces from that version into the
6318 Debian package.
</p
>
6320 <p
>After checking with the main package maintainer Jonas Smedegaard on
6321 IRC, I pushed several patches into the collab-maint git repository to
6322 improve the package. It now contains fixes for the RC issues (not from
6323 me, but fixed by Scott Howard), build rules for a Qt GUI client
6324 package, konqueror support for the bitcoin: URI and bash completion
6325 setup. As I work on Debian Squeeze, I also created
6326 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6327 patch to backport
</a
> the latest version. Jonas is going to look at
6328 it and try to integrate it into the git repository before uploading a
6329 new version to unstable.
6331 <p
>I would very much like bitcoin to succeed, to get rid of the
6332 centralized control currently exercised in the monetary system. I
6333 find it completely unacceptable that the USA government is collecting
6334 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6335 that the major credit card companies can block legal money
6336 transactions to Wikileaks. But for bitcoin to succeed, more people
6337 need to use bitcoins, and more people need to accept bitcoins when
6338 they sell products and services. Improving the bitcoin support in
6339 Debian is a small step in the right direction, but not enough.
6340 Unfortunately the user experience when browsing the web and wanting to
6341 pay with bitcoin is still not very good. The bitcoin: URI is a step
6342 in the right direction, but need to work in most or every browser in
6343 use. Also the bitcoin-qt client is too heavy to fire up to do a
6344 quick transaction. I believe there are other clients available, but
6345 have not tested them.
</p
>
6348 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6349 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6350 I received
20.15 BTC so far on the address I provided in my blog two
6351 years ago, as can be
6352 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6353 on the blockexplorer service
</a
>. Thank you everyone for your
6354 donation. The blockexplorer service demonstrates quite well that
6355 bitcoin is not quite anonymous and untracked. :) I wonder if the
6356 number of users have gone up since then. If you use bitcoin and want
6357 to show your support of my activity, please send Bitcoin donations to
6358 the same address as last time,
6359 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6364 <title>Git repository for song book for Computer Scientists
</title>
6365 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6366 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6367 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6368 <description><p
>As I
6369 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6370 this summer
</a
>, I have created a Computer Science song book a few
6371 years ago, and today I finally found time to create a public
6372 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6373 repository for the project
</a
>.
</p
>
6375 <p
>If you want to help out, please clone the source and submit patches
6376 to the HTML version. To generate the PDF and PostScript version,
6377 please use prince XML, or let me know about a useful free software
6378 processor capable of creating a good looking PDF from the HTML.
</p
>
6380 <p
>Want to sing? You can still find the song book in HTML, PDF and
6381 PostScript formats at
6382 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6383 Science Songbook
</a
>.
</p
>
6388 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6389 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6390 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6391 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6392 <description><p
>I dag fyller
6393 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6394 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6395 si gratulerer med dagen, Debian!
</p
>
6400 <title>Song book for Computer Scientists
</title>
6401 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6402 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6403 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6404 <description><p
>Many years ago, while studying Computer Science at the
6405 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6406 collecting computer related songs for use at parties. The original
6407 version was written in LaTeX, but a few years ago I got help from
6408 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6409 while keeping the ability to create a nice book in PDF format. I have
6410 not had time to maintain the book for a while now, and guess I should
6411 put it up on some public version control repository where others can
6412 help me extend and update the book. If anyone is volunteering to help
6413 me with this, send me an email. Also let me know if there are songs
6414 missing in my book.
</p
>
6416 <p
>I have not mentioned the book on my blog so far, and it occured to
6417 me today that I really should let all my readers share the joys of
6418 singing out load about programming, computers and computer networks.
6419 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6420 12</a
> is about to start (and I am not going). Want to sing? Check
6421 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6422 Computer Science Songbook
</a
>.
6427 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6428 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6429 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6430 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6431 <description><p
>At work we have heaps of servers. I believe the total count is
6432 around
1000 at the moment. To be able to get help from the vendors
6433 when something go wrong, we want to keep the firmware on the servers
6434 up to date. If the firmware isn
't the latest and greatest, the
6435 vendors typically refuse to start debugging any problems until the
6436 firmware is upgraded. So before every reboot, we want to upgrade the
6437 firmware, and we would really like everyone handling servers at the
6438 university to do this themselves when they plan to reboot a machine.
6439 For that to happen we at the unix server admin group need to provide
6440 the tools to do so.
</p
>
6442 <p
>To make firmware upgrading easier, I am working on a script to
6443 fetch and install the latest firmware for the servers we got. Most of
6444 our hardware are from Dell and HP, so I have focused on these servers
6445 so far. This blog post is about the Dell part.
</P
>
6447 <p
>On the Dell FTP site I was lucky enough to find
6448 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6449 with firmware information for all
11th generation servers, listing
6450 which firmware should be used on a given model and where on the FTP
6451 site I can find it. Using a simple perl XML parser I can then
6452 download the shell scripts Dell provides to do firmware upgrades from
6453 within Linux and reboot when all the firmware is primed and ready to
6454 be activated on the first reboot.
</p
>
6456 <p
>This is the Dell related fragment of the perl code I am working on.
6457 Are there anyone working on similar tools for firmware upgrading all
6458 servers at a site? Please get in touch and lets share resources.
</p
>
6460 <p
><pre
>
6464 use File::Temp qw(tempdir);
6466 # Install needed RHEL packages if missing
6468 'XML::Simple
' =
> 'perl-XML-Simple
',
6470 for my $module (keys %rhelmodules) {
6471 eval
"use $module;
";
6473 my $pkg = $rhelmodules{$module};
6474 system(
"yum install -y $pkg
");
6475 eval
"use $module;
";
6479 my $errorsto =
'pere@hungry.com
';
6485 sub run_firmware_script {
6486 my ($opts, $script) = @_;
6488 print STDERR
"fail: missing script name\n
";
6491 print STDERR
"Running $script\n\n
";
6493 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6494 print STDERR
"success: firmware script ran succcessfully\n
";
6496 print STDERR
"fail: firmware script returned error\n
";
6500 sub run_firmware_scripts {
6501 my ($opts, @dirs) = @_;
6502 # Run firmware packages
6503 for my $dir (@dirs) {
6504 print STDERR
"info: Running scripts in $dir\n
";
6505 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6506 while (my $s = readdir $dh) {
6507 next if $s =~ m/^\.\.?/;
6508 run_firmware_script($opts,
"$dir/$s
");
6516 print STDERR
"info: Downloading $url\n
";
6517 system(
"wget --quiet \
"$url\
"");
6522 my $product = `dmidecode -s system-product-name`;
6525 if ($product =~ m/PowerEdge/) {
6527 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6528 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6530 my $tmpdir = tempdir(
6534 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6535 system(
'gunzip Catalog.xml.gz
');
6536 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6537 # -q is quiet, disabling interactivity and reducing console output
6538 my $fwopts =
"-q
";
6540 for my $url (@paths) {
6541 fetch_dell_fw($url);
6543 run_firmware_scripts($fwopts, $tmpdir);
6545 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6546 print STDERR
"error: Please report to $errorsto.\n
";
6550 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6551 print STDERR
"error: Please report to $errorsto.\n
";
6557 my $url =
"ftp://ftp.us.dell.com/$path
";
6561 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6562 # firmware packages to download from Dell. Only work for Linux
6563 # machines and
11th generation Dell servers.
6564 sub fetch_dell_fw_list {
6565 my $filename = shift;
6567 my $product = `dmidecode -s system-product-name`;
6569 my ($mybrand, $mymodel) = split(/\s+/, $product);
6571 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6573 my $xml = XMLin($filename);
6575 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6576 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6577 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6579 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6580 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6582 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6584 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6586 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6589 for my $component (@{$xml-
>{SoftwareComponent}}) {
6590 my $componenttype = $component-
>{ComponentType}-
>{value};
6592 # Drop application packages, only firmware and BIOS
6593 next if
'APAC
' eq $componenttype;
6595 my $cpath = $component-
>{path};
6596 for my $path (@paths) {
6597 if ($cpath =~ m%/$path$%) {
6598 push(@paths, $cpath);
6606 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6607 it could work on other platforms with some tweaking. Anyone know a
6608 index like Catalog.xml is available from HP for HP servers? At the
6609 moment I maintain a similar list manually and it is quickly getting
6615 <title>How is booting into runlevel
1 different from single user boots?
</title>
6616 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6618 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6619 <description><p
>Wouter Verhelst have some
6620 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6621 comments and opinions
</a
> on my blog post on
6622 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6623 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6624 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6625 default KDE desktop in Debian
</a
>. I only have time to address one
6626 small piece of his comment now, and though it best to address the
6627 misunderstanding he bring forward:
</p
>
6629 <p
><blockquote
>
6630 Currently, a system admin has four options: [...] boot to a
6631 single-user system (by adding
'single
' to the kernel command line;
6632 this runs rcS and rc1 scripts)
6633 </blockquote
></p
>
6635 <p
>This make me believe Wouter believe booting into single user mode
6636 and booting into runlevel
1 is the same. I am not surprised he
6637 believe this, because it would make sense and is a quite sensible
6638 thing to believe. But because the boot in Debian is slightly broken,
6639 runlevel
1 do not work properly and it isn
't the same as single user
6640 mode. I
'll try to explain what is actually happing, but it is a bit
6641 hard to explain.
</p
>
6643 <p
>Single user mode is defined like this in /etc/inittab:
6644 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6645 executed in single user mode is sulogin. Single user mode is a boot
6646 state
"between
" the runlevels, and when booting into single user mode,
6647 only the scripts in /etc/rcS.d/ are executed before the init process
6648 enters the single user state. When switching to runlevel
1, the state
6649 is in fact not ending in runlevel
1, but it passes through runlevel
1
6650 and end up in the single user mode (see /etc/rc1.d/S03single, which
6651 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6652 1. It is confusing that the
'S
' (single user) init mode is not the
6653 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6656 <p
>This summary might make it clearer. When booting for the first
6657 time into single user mode, the following commands are executed:
6658 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6659 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6660 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6661 trying to continue after visiting single user mode. Not all services
6662 are started again as they should, causing the machine to end up in an
6663 unpredicatble state. This is why Debian admins recommend rebooting
6664 after visiting single user mode.
</p
>
6666 <p
>A similar problem with runlevel
1 is caused by the amount of
6667 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6668 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6669 stopped when passing through the scripts in /etc/rc1.d/, and not
6670 started again when switching away from runlevel
1 to the runlevels
6671 2-
5. I believe the problem is best fixed by moving all the scripts
6672 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6673 functioning single user mode during boot.
</p
>
6675 <p
>I have spent several years investigating the Debian boot system,
6676 and discovered this problem a few years ago. I suspect it originates
6677 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6682 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6683 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6685 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6686 <description><p
>In the Debian boot system, several packages include scripts that
6687 are started from /etc/rcS.d/. In fact, there is a bite more of them
6688 than make sense, and this causes a few problems. What kind of
6689 problems, you might ask. There are at least two problems. The first
6690 is that it is not possible to recover a machine after switching to
6691 runlevel
1. One need to actually reboot to get the machine back to
6692 the expected state. The other is that single user boot will sometimes
6693 run into problems because some of the subsystems are activated before
6694 the root login is presented, causing problems when trying to recover a
6695 machine from a problem in that subsystem. A minor additional point is
6696 that moving more scripts out of rcS.d/ and into the other rc#.d/
6697 directories will increase the amount of scripts that can run in
6698 parallel during boot, and thus decrease the boot time.
</p
>
6700 <p
>So, which scripts should start from rcS.d/. In short, only the
6701 scripts that _have_ to execute before the root login prompt is
6702 presented during a single user boot should go there. Everything else
6703 should go into the numeric runlevels. This means things like
6704 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6705 the numeric runlevels. Today in Debian, there are around
115 init.d
6706 scripts that are started from rcS.d/, and most of them should be moved
6707 out. Do your package have one of them? Please help us make single
6708 user and runlevel
1 better by moving it.
</p
>
6710 <p
>Scripts setting up the screen, keyboard, system partitions
6711 etc. should still be started from rcS.d/, but there is for example no
6712 need to have the network enabled before the single user login prompt
6713 is presented.
</p
>
6715 <p
>As always, things are not so easy to fix as they sound. To keep
6716 Debian systems working while scripts migrate and during upgrades, the
6717 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6718 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6719 and the next ones can only be moved when their dependencies have been
6720 moved first. This migration must be done sequentially while we ensure
6721 that the package system upgrade packages in the right order to keep
6722 the system state correct. This will require some coordination when it
6723 comes to network related packages, but most of the packages with
6724 scripts that should migrate do not have anything in rcS.d/ depending
6725 on them. Some packages have already been updated, like the sudo
6726 package, while others are still left to do. I wish I had time to work
6727 on this myself, but real live constrains make it unlikely that I will
6728 find time to push this forward.
</p
>
6733 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6734 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6735 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6736 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6737 <description><p
>While at Debconf11, I have several times during discussions
6738 mentioned the issues I believe should be improved in Debian for its
6739 desktop to be useful for more people. The use case for this is my
6740 parents, which are currently running Kubuntu which solve the
6743 <p
>I suspect these four missing features are not very hard to
6744 implement. After all, they are present in Ubuntu, so if we wanted to
6745 do this in Debian we would have a source.
</p
>
6749 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
6750 are new packages available for upgrades, a icon in the KDE status bar
6751 indicate this, and clicking on it will activate the simple upgrade
6752 tool to handle it. I have no problem guiding both of my parents
6753 through the process over the phone. If a kernel reboot is required,
6754 this too is indicated by the status bars and the upgrade tool. Last
6755 time I checked, nothing with the same features was working in KDE in
6758 <li
><strong
>Simple handling of missing Firefox browser
6759 plugins.
</strong
> When the browser encounter a MIME type it do not
6760 currently have a handler for, it will ask the user if the system
6761 should search for a package that would add support for this MIME type,
6762 and if the user say yes, the APT sources will be searched for packages
6763 advertising the MIME type in their control file (visible in the
6764 Packages file in the APT archive). If one or more packages are found,
6765 it is a simple click of the mouse to add support for the missing mime
6766 type. If the package require the user to accept some non-free
6767 license, this is explained to the user. The entire process make it
6768 more clear to the user why something do not work in the browser, and
6769 make the chances higher for the user to blame the web page authors and
6770 not the browser for any missing features.
</li
>
6772 <li
><strong
>Simple handling of missing multimedia codec/format
6773 handlers.
</strong
> When the media players encounter a format or codec
6774 it is not supporting, a dialog pop up asking the user if the system
6775 should search for a package that would add support for it. This
6776 happen with things like MP3, Windows Media or H
.264. The selection
6777 and installation procedure is very similar to the Firefox browser
6778 plugin handling. This is as far as I know implemented using a
6779 gstreamer hook. The end result is that the user easily get access to
6780 the codecs that are present from the APT archives available, while
6781 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6783 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6784 displaying a text/plain file in my Debian browser, it will propose to
6785 start emacs to show it. If I remember correctly, when doing the same
6786 in Kunbutu it show the file as a text file in the browser. At least I
6787 know Opera will show text files within the browser. I much prefer the
6788 latter behaviour.
</li
>
6792 <p
>There are other nice features as well, like the simplified suite
6793 upgrader, but given that I am the one mostly doing the dist-upgrade,
6794 it do not matter much.
</p
>
6796 <p
>I really hope we could get these features in place for the next
6797 Debian release. It would require the coordinated effort of several
6798 maintainers, but would make the end user experience a lot better.
</p
>
6803 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6804 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6805 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6806 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6807 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6808 site is build on Debian/Squeeze, and this platform was chosen because
6809 I am most familiar with Debian (being a Debian Developer for around
10
6810 years) because it is the latest stable Debian release which should get
6811 security support for a few years.
</p
>
6813 <p
>The web service is written in Perl, and depend on some perl modules
6814 that are missing in Debian at the moment. It would be great if these
6815 modules were added to the Debian archive, allowing anyone to set up
6816 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6817 in their own country using only Debian packages. The list of modules
6818 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6819 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6820 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6821 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6822 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6823 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6824 easier in the future.
</p
>
6826 <p
>Thanks to the great tools in Debian, getting the missing modules
6827 installed on my server was a simple call to
'cpan2deb Module::Name
'
6828 and
'dpkg -i
' to install the resulting package. But this leave me
6829 with the responsibility of tracking security problems, which I really
6830 do not have time for.
</p
>
6835 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6836 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6837 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6838 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6839 <description><p
>Here is a small update for my English readers. Most of my blog
6840 posts have been in Norwegian the last few weeks, so here is a short
6841 update in English.
</p
>
6843 <p
>The kids still keep me too busy to get much free software work
6844 done, but I did manage to organise a project to get a Norwegian port
6845 of the British service
6846 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6847 and it has been running for a month now. The entire project has been
6848 organised by me and two others. Around Christmas we gathered sponsors
6849 to fund the development work. In January I drafted a contract with
6850 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6851 and in February the development took place. Most of it involved
6852 converting the source to use GPS coordinates instead of British
6853 easting/northing, and the resulting code should be a lot easier to get
6854 running in any country by now. The Norwegian
6855 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6856 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6857 source and the source for administrative borders in Norway, and
6858 support for this had to be added/fixed.
</p
>
6860 <p
>The Norwegian version went live March
3th, and we spent the weekend
6861 polishing the system before we announced it March
7th. The system is
6862 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6863 problem reports in a few weeks. Soon we hope to announce the Android
6864 and iPhone versions making it even easier to report problems with the
6865 public infrastructure.
</p
>
6867 <p
>Perhaps something to consider for those of you in countries without
6868 such service?
</p
>
6873 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6874 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6875 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6876 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6877 <description><p
>The last few days I have looked at ways to track open security
6878 issues here at my work with the University of Oslo. My idea is that
6879 it should be possible to use the information about security issues
6880 available on the Internet, and check our locally
6881 maintained/distributed software against this information. It should
6882 allow us to verify that no known security issues are forgotten. The
6883 CVE database listing vulnerabilities seem like a great central point,
6884 and by using the package lists from Debian mapped to CVEs provided by
6885 the testing security team, I believed it should be possible to figure
6886 out which security holes were present in our free software
6887 collection.
</p
>
6889 <p
>After reading up on the topic, it became obvious that the first
6890 building block is to be able to name software packages in a unique and
6891 consistent way across data sources. I considered several ways to do
6892 this, for example coming up with my own naming scheme like using URLs
6893 to project home pages or URLs to the Freshmeat entries, or using some
6894 existing naming scheme. And it seem like I am not the first one to
6895 come across this problem, as MITRE already proposed and implemented a
6896 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6897 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6898 software, hardware and other platform components. The CPE ids are
6899 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6900 Vulnerability Database
</a
>, allowing me to look up know security
6901 issues for any CPE name. With this in place, all I need to do is to
6902 locate the CPE id for the software packages we use at the university.
6903 This is fairly trivial (I google for
'cve cpe $package
' and check the
6904 NVD entry if a CVE for the package exist).
</p
>
6906 <p
>To give you an example. The GNU gzip source package have the CPE
6907 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
6908 check out, one could look up
6909 <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
6910 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
6911 The most recent one is
6912 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
6913 and at the bottom of the NVD page for this vulnerability the complete
6914 list of affected versions is provided.
</p
>
6916 <p
>The NVD database of CVEs is also available as a XML dump, allowing
6917 for offline processing of issues. Using this dump, I
've written a
6918 small script taking a list of CPEs as input and list all CVEs
6919 affecting the packages represented by these CPEs. One give it CPEs
6920 with version numbers as specified above and get a list of open
6921 security issues out.
</p
>
6923 <p
>Of course for this approach to be useful, the quality of the NVD
6924 information need to be high. For that to happen, I believe as many as
6925 possible need to use and contribute to the NVD database. I notice
6927 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
6928 map from CVE to CPE
</a
>, indicating that they are using the CPE
6929 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
6931 <p
>To get an idea about the quality for free software, I spent some
6932 time making it possible to compare the CVE database from Debian with
6933 the CVE database in NVD. The result look fairly good, but there are
6934 some inconsistencies in NVD (same software package having several
6935 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6936 Debian believe are affected by a CVE). Hope to find time to improve
6937 the quality of NVD, but that require being able to get in touch with
6938 someone maintaining it. So far my three emails with questions and
6939 corrections have not seen any reply, but I hope contact can be
6940 established soon.
</p
>
6942 <p
>An interesting application for CPEs is cross platform package
6943 mapping. It would be useful to know which packages in for example
6944 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6945 this would be trivial if all linux distributions provided CPE entries
6946 for their packages.
</p
>
6951 <title>Which module is loaded for a given PCI and USB device?
</title>
6952 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
6953 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
6954 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
6955 <description><p
>In the
6956 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
6957 package in Debian, there is a script to report useful information
6958 about the running hardware for use when people report missing
6959 information. One part of this script that I find very useful when
6960 debugging hardware problems, is the part mapping loaded kernel module
6961 to the PCI device it claims. It allow me to quickly see if the kernel
6962 module I expect is driving the hardware I am struggling with. To see
6963 the output, make sure discover-data is installed and run
6964 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
6965 one of my machines like this:
</p
>
6969 10de:
03eb i2c_nforce2
6972 10de:
03f0 snd_hda_intel
6981 <p
>The code in question look like this, slightly modified for
6982 readability and to drop the output to file descriptor
3:
</p
>
6985 if [ -d /sys/bus/pci/devices/ ] ; then
6986 echo loaded pci modules:
6988 cd /sys/bus/pci/devices/
6989 for address in * ; do
6990 if [ -d
"$address/driver/module
" ] ; then
6991 module=`cd $address/driver/module ; pwd -P | xargs basename`
6992 if grep -q
"^$module
" /proc/modules ; then
6993 address=$(echo $address |sed s/
0000://)
6994 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
6995 echo
"$id $module
"
7004 <p
>Similar code could be used to extract USB device module
7008 if [ -d /sys/bus/usb/devices/ ] ; then
7009 echo loaded usb modules:
7011 cd /sys/bus/usb/devices/
7012 for address in * ; do
7013 if [ -d
"$address/driver/module
" ] ; then
7014 module=`cd $address/driver/module ; pwd -P | xargs basename`
7015 if grep -q
"^$module
" /proc/modules ; then
7016 address=$(echo $address |sed s/
0000://)
7017 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7018 if [
"$id
" ] ; then
7019 echo
"$id $module
"
7029 <p
>This might perhaps be something to include in other tools as
7035 <title>How to test if a laptop is working with Linux
</title>
7036 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7037 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7038 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7039 <description><p
>The last few days I have spent at work here at the
<a
7040 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7041 batch of computers will work with Linux. Every year for the last few
7042 years the university have organised shared bid of a few thousand
7043 computers, and this year HP won the bid. Two different desktops and
7044 five different laptops are on the list this year. We in the UNIX
7045 group want to know which one of these computers work well with RHEL
7046 and Ubuntu, the two Linux distributions we currently handle at the
7047 university.
</p
>
7049 <p
>My test method is simple, and I share it here to get feedback and
7050 perhaps inspire others to test hardware as well. To test, I PXE
7051 install the OS version of choice, and log in as my normal user and run
7052 a few applications and plug in selected pieces of hardware. When
7053 something fail, I make a note about this in the test matrix and move
7054 on. If I have some spare time I try to report the bug to the OS
7055 vendor, but as I only have the machines for a short time, I rarely
7056 have the time to do this for all the problems I find.
</p
>
7058 <p
>Anyway, to get to the point of this post. Here is the simple tests
7059 I perform on a new model.
</p
>
7063 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7064 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7065 RHEL5 and Debian Edu/Squeeze.
</li
>
7067 <li
>Is X.org working? If the graphical login screen show up after
7068 installation, X.org is working.
</li
>
7070 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7071 package mesa-utils on Ubuntu) and writing down the frames per second
7072 reported by the program.
</li
>
7074 <li
>Is sound working? With Gnome and KDE, a sound is played when
7075 logging in, and if I can hear this the test is successful. If there
7076 are several audio exits on the machine, I try them all and check if
7077 the Gnome/KDE audio mixer can control where to send the sound. I
7078 normally test this by playing
7079 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7080 video
</a
> in Firefox/Iceweasel.
</li
>
7082 <li
>Is the USB subsystem working? I test this by plugging in a USB
7083 memory stick and see if Gnome/KDE notices this.
</li
>
7085 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7086 I have lying around, and see if Gnome/KDE notices this.
</li
>
7088 <li
>Is any built in camera working? Test using cheese, and see if a
7089 picture from the v4l device show up.
</li
>
7091 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7092 any bluetooth devices are discovered. In my office, I normally see a
7095 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7096 memory modules lying around, and stick them in and see if Gnome/KDE
7097 notice this.
</li
>
7099 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7100 special button work, and if the laptop continue to work after
7103 <li
>For laptops, is the extra buttons working, like audio level,
7104 adjusting background light, switching on/off external video output,
7105 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7106 laptop to laptop, so I just write down which are working and which are
7109 <li
>Some laptops have smart card readers, finger print readers,
7110 acceleration sensors etc. I rarely test these, as I do not know how
7111 to quickly test if they are working or not, so I only document their
7112 existence.
</li
>
7116 <p
>By now I suspect you are really curious what the test results are
7117 for the HP machines I am testing. I
'm not done yet, so I will report
7118 the test results later. For now I can report that HP
8100 Elite work
7119 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7120 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7121 can see, I have most machines left to test. One interesting
7122 observation is that Ubuntu Lucid has almost twice the frame rate than
7123 RHEL6 with glxgears. No idea why.
</p
>
7128 <title>Some thoughts on BitCoins
</title>
7129 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7130 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7131 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7132 <description><p
>As I continue to explore
7133 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7134 what properties the system have, and how it will be affected by laws
7135 and regulations here in Norway. Here are some random notes.
</p
>
7137 <p
>One interesting thing to note is that since the transactions are
7138 verified using a peer to peer network, all details about a transaction
7139 is known to everyone. This means that if a BitCoin address has been
7140 published like I did with mine in my initial post about BitCoin, it is
7141 possible for everyone to see how many BitCoins have been transfered to
7142 that address. There is even a web service to look at the details for
7143 all transactions. There I can see that my address
7144 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7145 have received
16.06 Bitcoin, the
7146 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7147 address of Simon Phipps have received
181.97 BitCoin and the address
7148 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7149 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7150 every one of you that donated bitcoins to support my activity. The
7151 fact that anyone can see how much money was transfered to a given
7152 address make it more obvious why the BitCoin community recommend to
7153 generate and hand out a new address for each transaction. I
'm told
7154 there is no way to track which addresses belong to a given person or
7155 organisation without the person or organisation revealing it
7156 themselves, as Simon, EFF and I have done.
</p
>
7158 <p
>In Norway, and in most other countries, there are laws and
7159 regulations limiting how much money one can transfer across the border
7160 without declaring it. There are money laundering, tax and accounting
7161 laws and regulations I would expect to apply to the use of BitCoin.
7162 If the Skolelinux foundation
7163 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7164 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7165 normal bank transfers like EFF is doing, how should this be accounted?
7166 Given that it is impossible to know if money can cross the border or
7167 not, should everything or nothing be declared? What exchange rate
7168 should be used when calculating taxes? Would receivers have to pay
7169 income tax if the foundation were to pay Skolelinux contributors in
7170 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7172 <p
>For a currency to be useful and successful, it must be trusted and
7173 accepted by a lot of users. It must be possible to get easy access to
7174 the currency (as a wage or using currency exchanges), and it must be
7175 easy to spend it. At the moment BitCoin seem fairly easy to get
7176 access to, but there are very few places to spend it. I am not really
7177 a regular user of any of the vendor types currently accepting BitCoin,
7178 so I wonder when my kind of shop would start accepting BitCoins. I
7179 would like to buy electronics, travels and subway tickets, not herbs
7180 and books. :) The currency is young, and this will improve over time
7181 if it become popular, but I suspect regular banks will start to lobby
7182 to get BitCoin declared illegal if it become popular. I
'm sure they
7183 will claim it is helping fund terrorism and money laundering (which
7184 probably would be true, as is any currency in existence), but I
7185 believe the problems should be solved elsewhere and not by blaming
7186 currencies.
</p
>
7188 <p
>The process of creating new BitCoins is called mining, and it is
7189 CPU intensive process that depend on a bit of luck as well (as one is
7190 competing against all the other miners currently spending CPU cycles
7191 to see which one get the next lump of cash). The
"winner
" get
50
7192 BitCoin when this happen. Yesterday I came across the obvious way to
7193 join forces to increase ones changes of getting at least some coins,
7194 by coordinating the work on mining BitCoins across several machines
7195 and people, and sharing the result if one is lucky and get the
50
7197 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7198 if this sounds interesting. I have not had time to try to set up a
7199 machine to participate there yet, but have seen that running on ones
7200 own for a few days have not yield any BitCoins througth mining
7203 <p
>Update
2010-
12-
15: Found an
<a
7204 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7205 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7206 it was interesting to read. The arguments presented seem to be
7207 equally valid for gold, which was used as a currency for many years.
</p
>
7212 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7213 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7214 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7215 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7216 <description><p
>With this weeks lawless
7217 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7218 attacks
</a
> on Wikileak and
7219 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7220 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7221 not be trusted to handle money transactions.
7223 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7224 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7225 mine mentioned earlier. I decided to follow Simon
's example, and get
7226 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7227 some help from my friend to get it all running, and he even handed me
7228 some bitcoins to get started. I even donated a few bitcoins to Simon
7229 for helping me remember BitCoin.
</p
>
7231 <p
>So, what is bitcoins, you probably wonder? It is a digital
7232 crypto-currency, decentralised and handled using peer-to-peer
7233 networks. It allows anonymous transactions and prohibits central
7234 control over the transactions, making it impossible for governments
7235 and companies alike to block donations and other transactions. The
7236 source is free software, and while the key dependency wxWidgets
2.9
7237 for the graphical user interface is missing in Debian, the command
7238 line client builds just fine. Hopefully Jonas
7239 <a href=
"http://bugs.debian.org/
578157">will get the package into
7240 Debian
</a
> soon.
</p
>
7242 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7243 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7244 bitcoins
</a
> when selling services and goods, and there are even
7245 currency
"stock
" markets where the exchange rate is decided. There
7246 are not many users so far, but the concept seems promising. If you
7247 want to get started and lack a friend with any bitcoins to spare,
7249 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7250 bitcoin at the time of writing). Use
7251 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7252 on the current exchange rates.
</p
>
7254 <p
>As an experiment, I have decided to set up bitcoind on one of my
7255 machines. If you want to support my activity, please send Bitcoin
7256 donations to the address
7257 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7262 <title>Why isn
't Debian Edu using VLC?
</title>
7263 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7264 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7265 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7266 <description><p
>In the latest issue of Linux Journal, the readers choices were
7267 presented, and the winner among the multimedia player were VLC.
7268 Personally, I like VLC, and it is my player of choice when I first try
7269 to play a video file or stream. Only if VLC fail will I drag out
7270 gmplayer to see if it can do better. The reason is mostly the failure
7271 model and trust. When VLC fail, it normally pop up a error message
7272 reporting the problem. When mplayer fail, it normally segfault or
7273 just hangs. The latter failure mode drain my trust in the program.
<p
>
7275 <p
>But even if VLC is my player of choice, we have choosen to use
7276 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7277 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7278 plugin to play web videos seamlessly, and the VLC browser plugin is
7279 not very good. For example, it lack in-line control buttons, so there
7280 is no way for the user to pause the video. Also, when I
7281 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7282 tested the browser plugins
</a
> available in Debian, the VLC plugin
7283 failed on several video pages where mplayer based plugins worked. If
7284 the browser plugin for VLC was as good as the gecko-mediaplayer
7285 package (which uses mplayer), we would switch.
</P
>
7287 <p
>While VLC is a good player, its user interface is slightly
7288 annoying. The most annoying feature is its inconsistent use of
7289 keyboard shortcuts. When the player is in full screen mode, its
7290 shortcuts are different from when it is playing the video in a window.
7291 For example, space only work as pause when in full screen mode. I
7292 wish it had consisten shortcuts and that space also would work when in
7293 window mode. Another nice shortcut in gmplayer is [enter] to restart
7294 the current video. It is very nice when playing short videos from the
7295 web and want to restart it when new people arrive to have a look at
7296 what is going on.
</p
>
7301 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7302 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7303 <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>
7304 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7305 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7306 upgrade testing of the
7307 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7308 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7309 This seem like a very good idea, so I adjusted by test scripts and
7310 can now present the updated result from today:
</p
>
7312 <p
>This is for Gnome:
</p
>
7314 <p
>Installed using apt-get, missing with aptitude
</p
>
7316 <blockquote
><p
>
7321 browser-plugin-gnash
7328 freedesktop-sound-theme
7330 gconf-defaults-service
7345 gnome-desktop-environment
7349 gnome-session-canberra
7354 gstreamer0.10-fluendo-mp3
7360 libapache2-mod-dnssd
7363 libaprutil1-dbd-sqlite3
7366 libboost-date-time1.42
.0
7367 libboost-python1.42
.0
7368 libboost-thread1.42
.0
7370 libchamplain-gtk-
0.4-
0
7372 libclutter-gtk-
0.10-
0
7379 libfreerdp-plugins-standard
7394 libgnomepanel2.24-cil
7399 libgtksourceview2.0-common
7400 libmono-addins-gui0.2-cil
7401 libmono-addins0.2-cil
7402 libmono-cairo2.0-cil
7403 libmono-corlib2.0-cil
7404 libmono-i18n-west2.0-cil
7405 libmono-posix2.0-cil
7406 libmono-security2.0-cil
7407 libmono-sharpzip2.84-cil
7408 libmono-system2.0-cil
7411 libndesk-dbus-glib1.0-cil
7412 libndesk-dbus1.0-cil
7422 libtelepathy-farsight0
7431 nautilus-sendto-empathy
7435 python-aptdaemon-gtk
7437 python-beautifulsoup
7452 python-gtksourceview2
7463 python-pkg-resources
7470 python-twisted-conch
7476 python-zope.interface
7481 rhythmbox-plugin-cdrecorder
7488 system-config-printer-udev
7490 telepathy-mission-control-
5
7501 </p
></blockquote
>
7503 <p
>Installed using apt-get, removed with aptitude
</p
>
7505 <blockquote
><p
>
7511 fast-user-switch-applet
7530 libgtksourceview2.0-
0
7532 libsdl1.2debian-alsa
7538 system-config-printer
7543 </p
></blockquote
>
7545 <p
>Installed using aptitude, missing with apt-get
</p
>
7547 <blockquote
><p
>
7548 gstreamer0.10-gnomevfs
7549 </p
></blockquote
>
7551 <p
>Installed using aptitude, removed with apt-get
</p
>
7553 <blockquote
><p
>
7555 </p
></blockquote
>
7557 <p
>This is for KDE:
</p
>
7559 <p
>Installed using apt-get, missing with aptitude
</p
>
7561 <blockquote
><p
>
7563 </p
></blockquote
>
7565 <p
>Installed using apt-get, removed with aptitude
</p
>
7567 <blockquote
><p
>
7570 </p
></blockquote
>
7572 <p
>Installed using aptitude, missing with apt-get
</p
>
7574 <blockquote
><p
>
7588 kdeartwork-emoticons
7590 kdeartwork-theme-icon
7594 kdebase-workspace-bin
7595 kdebase-workspace-data
7609 kscreensaver-xsavers
7624 plasma-dataengines-workspace
7626 plasma-desktopthemes-artwork
7627 plasma-runners-addons
7628 plasma-scriptengine-googlegadgets
7629 plasma-scriptengine-python
7630 plasma-scriptengine-qedje
7631 plasma-scriptengine-ruby
7632 plasma-scriptengine-webkit
7633 plasma-scriptengines
7634 plasma-wallpapers-addons
7635 plasma-widget-folderview
7636 plasma-widget-networkmanagement
7640 xscreensaver-data-extra
7642 xscreensaver-gl-extra
7643 xscreensaver-screensaver-bsod
7644 </p
></blockquote
>
7646 <p
>Installed using aptitude, removed with apt-get
</p
>
7648 <blockquote
><p
>
7650 google-gadgets-common
7668 libggadget-qt-
1.0-
0b
7673 libkonqsidebarplugin4a
7682 libplasma-geolocation-interface4
7684 libplasmagenericshell4
7698 libsmokeknewstuff2-
3
7699 libsmokeknewstuff3-
3
7701 libsmokektexteditor3
7709 libsmokeqtnetwork4-
3
7715 libsmokeqtuitools4-
3
7727 plasma-dataengines-addons
7728 plasma-scriptengine-superkaramba
7729 plasma-widget-lancelot
7730 plasma-widgets-addons
7731 plasma-widgets-workspace
7735 update-notifier-common
7736 </p
></blockquote
>
7738 <p
>Running apt-get autoremove made the results using apt-get and
7739 aptitude a bit more similar, but there are still quite a lott of
7740 differences. I have no idea what packages should be installed after
7741 the upgrade, but hope those that do can have a look.
</p
>
7746 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7747 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7748 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
7749 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
7750 <description><p
>Most of the computers in use by the
7751 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
7752 are virtual machines. And they have been Xen machines running on a
7753 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
7754 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
7755 bit harder that it could have been, because we set up the Xen virtual
7756 machines to get the virtual partitions from LVM, which as far as I
7757 know is not supported by KVM. So to migrate, we had to convert
7758 several LVM logical volumes to partitions on a virtual disk file.
</p
>
7761 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
7762 nice recipe
</a
> to do this, and wrote the following script to do the
7763 migration. It uses qemu-img from the qemu package to make the disk
7764 image, parted to partition it, losetup and kpartx to present the disk
7765 image partions as devices, and dd to copy the data. I NFS mounted the
7766 new servers storage area on the old server to do the migration.
</p
>
7772 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7777 if [ -z
"$
1" ] ; then
7778 echo
"Usage: $
0 &lt;hostname
&gt;
"
7784 if [ ! -e /dev/vg_data/$host-disk ] ; then
7785 echo
"error: unable to find LVM volume for $host
"
7789 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7790 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7791 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7792 totalsize=$(( ( $disksize + $swapsize ) ))
7795 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7796 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7798 parted $img mklabel msdos
7799 parted $img mkpart primary linux-swap
0 $disksize
7800 parted $img mkpart primary ext2 $disksize $totalsize
7801 parted $img set
1 boot on
7804 losetup /dev/loop0 $img
7805 kpartx -a /dev/loop0
7807 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7808 fsck.ext3 -f /dev/mapper/loop0p1 || true
7809 mkswap /dev/mapper/loop0p2
7811 kpartx -d /dev/loop0
7812 losetup -d /dev/loop0
7815 <p
>The script is perhaps so simple that it is not copyrightable, but
7816 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7818 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7819 the new disk image attached, installed grub-pc and linux-image-
686 and
7820 set up grub to boot from the disk image. After this, the KVM machines
7821 seem to work just fine.
</p
>
7826 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7827 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7828 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7829 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7830 <description><p
>I
'm still running upgrade testing of the
7831 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7832 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7833 status. Here is a short update based on a test I ran
20101118.
</p
>
7835 <p
>I still do not know what a correct migration should look like, so I
7836 report any differences between apt and aptitude and hope someone else
7837 can see if anything should be changed.
</p
>
7839 <p
>This is for Gnome:
</p
>
7841 <p
>Installed using apt-get, missing with aptitude
</p
>
7843 <blockquote
><p
>
7844 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7845 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7846 dmz-cursor-theme empathy empathy-common finger
7847 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7848 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7849 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7850 gnome-cards-data gnome-codec-install gnome-core
7851 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7852 gnome-search-tool gnome-session-canberra gnome-spell
7853 gnome-system-log gnome-themes-extras gnome-themes-more
7854 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7855 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7856 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7857 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7858 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7859 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7860 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7861 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7862 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7863 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7864 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7865 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7866 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7867 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7868 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7869 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7870 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7871 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7872 libmono-security2.0-cil libmono-sharpzip2.84-cil
7873 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7874 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7875 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7876 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7877 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7878 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7879 libxalan2-java libxerces2-java media-player-info mesa-utils
7880 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7881 nautilus-sendto-empathy openoffice.org-writer2latex
7882 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7883 python-aptdaemon python-aptdaemon-gtk python-axiom
7884 python-beautifulsoup python-bugbuddy python-clientform
7885 python-coherence python-configobj python-crypto python-cupshelpers
7886 python-cupsutils python-eggtrayicon python-elementtree
7887 python-epsilon python-evolution python-feedparser python-gdata
7888 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7889 python-gtksourceview2 python-httplib2 python-louie python-mako
7890 python-markupsafe python-mechanize python-nevow python-notify
7891 python-opengl python-openssl python-pam python-pkg-resources
7892 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7893 python-tagpy python-twisted-bin python-twisted-conch
7894 python-twisted-core python-twisted-web python-utidylib python-webkit
7895 python-xdg python-zope.interface remmina remmina-plugin-data
7896 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7897 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7898 software-center svgalibg1 system-config-printer-udev
7899 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7900 totem totem-coherence totem-mozilla totem-plugins
7901 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7903 </p
></blockquote
>
7905 Installed using apt-get, removed with aptitude
7907 <blockquote
><p
>
7908 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7909 epiphany-extensions epiphany-gecko evolution-exchange
7910 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7911 gedit-common gnome-app-install gnome-games gnome-games-data
7912 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7913 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7914 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7915 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
7916 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
7917 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
7918 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
7919 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
7920 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
7921 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
7922 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
7923 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
7924 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7925 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7926 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7927 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7928 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
7929 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
7930 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
7931 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
7932 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
7933 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7934 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7935 sound-juicer swfdec-gnome system-config-printer totem-common
7936 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7937 </p
></blockquote
>
7939 <p
>Installed using aptitude, missing with apt-get
</p
>
7941 <blockquote
><p
>
7942 gstreamer0.10-gnomevfs
7943 </p
></blockquote
>
7945 <p
>Installed using aptitude, removed with apt-get
</p
>
7947 <blockquote
><p
>
7949 </p
></blockquote
>
7951 <p
>This is for KDE:
</p
>
7953 <p
>Installed using apt-get, missing with aptitude
</p
>
7955 <blockquote
><p
>
7956 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
7957 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7958 ghostscript-x git gnome-audio gnugo granatier gs-common
7959 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7960 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7961 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7962 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7963 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7964 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7965 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7966 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7967 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7968 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7969 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7970 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
7971 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7972 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7973 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7974 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7975 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7976 libkrossui4 libmailtools-perl libmime-tools-perl
7977 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7978 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7979 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7980 lirc luatex marble networkstatus noatun-plugins
7981 openoffice.org-writer2latex palapeli palapeli-data parley
7982 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7983 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7984 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7986 </p
></blockquote
>
7988 <p
>Installed using apt-get, removed with aptitude
</p
>
7990 <blockquote
><p
>
7991 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7992 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7993 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7994 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7995 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7996 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7997 kitchensync kiten kjumpingcube klatin klettres klickety klines
7998 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7999 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8000 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8001 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8002 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8003 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8004 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8005 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8006 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8007 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8008 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8009 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8010 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8011 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8012 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8013 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8014 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8015 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8016 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8017 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8018 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8019 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8020 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8021 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8022 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8023 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8024 </p
></blockquote
>
8026 <p
>Installed using aptitude, missing with apt-get
</p
>
8028 <blockquote
><p
>
8029 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8030 kdeartwork kdebase kdebase-apps kdebase-workspace
8031 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8032 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8033 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8034 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8035 xscreensaver-screensaver-bsod
8036 </p
></blockquote
>
8038 <p
>Installed using aptitude, removed with apt-get
</p
>
8040 <blockquote
><p
>
8041 kdebase-bin konq-plugins konqueror
8042 </p
></blockquote
>
8047 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8048 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8049 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8050 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8051 <description><p
>Answering
8052 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8053 call from the Gnash project
</a
> for
8054 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8055 current source, I have set up a virtual KVM machine on the Debian
8056 Edu/Skolelinux virtualization host to test the git source on
8057 Debian/Squeeze. I hope this can help the developers in getting new
8058 releases out more often.
</p
>
8060 <p
>As the developers want less main-stream build platforms tested to,
8061 I have considered setting up a
<a
8062 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8063 machine as well. I have also considered using the kfreebsd
8064 architecture in Debian as a file server in NUUG to get access to the
5
8065 TB zfs volume we currently use to store DV video. Because of this, I
8066 finally got around to do a test installation of Debian/Squeeze with
8067 kfreebsd. Installation went fairly smooth, thought I noticed some
8068 visual glitches in the cdebconf dialogs (black cursor left on the
8069 screen at random locations). Have not gotten very far with the
8070 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8071 fatal problem. Have to spend some more time on it to see if it is
8072 useful as a file server for NUUG. Will try to find time to set up a
8073 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8078 <title>Debian in
3D
</title>
8079 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8080 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8081 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8082 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8084 <p
>3D printing is just great. I just came across this Debian logo in
8086 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8087 thingiverse blog
</a
>.
</p
>
8092 <title>Software updates
2010-
10-
24</title>
8093 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8094 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8095 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8096 <description><p
>Some updates.
</p
>
8098 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8099 raise money for the project is going well. The lower limit of
10
8100 signers was reached in
24 hours, and so far
13 people have signed it.
8101 More signers and more funding is most welcome, and I am really curious
8102 how far we can get before the time limit of December
24 is reached.
8105 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8106 about what appear to be a great code coverage tool capable of
8107 generating code coverage stats without any changes to the source code.
8109 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8110 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8111 It is missing in Debian, but the git source built just fine in Squeeze
8112 after I installed libelf-dev, libdwarf-dev, pkg-config and
8113 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8114 solvable. I hope kcov make it into Debian soon.
</p
>
8116 <p
>Finally found time to wrap up the release notes for
<a
8117 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8118 new alpha release of Debian Edu
</a
>, and just published the second
8119 alpha test release of the Squeeze based Debian Edu /
8120 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8121 release. Give it a try if you need a complete linux solution for your
8122 school, including central infrastructure server, workstations, thin
8123 client servers and diskless workstations. A nice touch added
8124 yesterday is RDP support on the thin client servers, for windows
8125 clients to get a Linux desktop on request.
</p
>
8130 <title>Some notes on Flash in Debian and Debian Edu
</title>
8131 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8132 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8133 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8134 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8135 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8136 second most popular used package that is missing in Debian. The sixth
8137 most popular is flashplayer-mozilla. This is a clear indication that
8138 working flash is important for Debian users. Around
10 percent of the
8139 users submitting data to popcon.debian.org have this package
8140 installed.
</p
>
8142 <p
>In the report written by Lars Risan in August
2008
8143 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8144 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8145 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8146 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8147 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8148 web sites require Flash to work, and lacking working Flash support in
8149 the web browser and the problems with installing it was perceived as a
8150 good reason to stay with Windows.
</p
>
8152 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8153 said to be the retarded cousin that did not really understand
8154 everything you told him but could work fairly well. This was a
8155 comment regarding the problems Linux have with proprietary formats and
8156 non-standard web pages, and is sad because it exposes a fairly common
8157 understanding of whose fault it is if web pages that only work in for
8158 example Internet Explorer
6 fail to work on Firefox, and funny because
8159 it explain very well how annoying it is for users when Linux
8160 distributions do not work with the documents they receive or the web
8161 pages they want to visit.
</p
>
8163 <p
>This is part of the reason why I believe it is important for Debian
8164 and Debian Edu to have a well working Flash implementation in the
8165 distribution, to get at least popular sites as Youtube and Google
8166 Video to working out of the box. For Squeeze, Debian have the chance
8167 to include the latest version of Gnash that will make this happen, as
8168 the new release
0.8.8 was published a few weeks ago and is resting in
8169 unstable. The new version work with more sites that version
0.8.7.
8170 The Gnash maintainers have asked for a freeze exception, but the
8171 release team have not had time to reply to it yet. I hope they agree
8172 with me that Flash is important for the Debian desktop users, and thus
8173 accept the new package into Squeeze.
</p
>
8178 <title>Circular package dependencies harms apt recovery
</title>
8179 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8180 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8181 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8182 <description><p
>I discovered this while doing
8183 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8184 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8185 in Debian still got circular dependencies, and it is often claimed
8186 that apt and aptitude should be able to handle this just fine, but
8187 some times these dependency loops causes apt to fail.
</p
>
8189 <p
>An example is from todays
8190 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8191 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8192 causes perl-modules to fail to upgrade. The cause is simple. If a
8193 package fail to unpack, then only part of packages with the circular
8194 dependency might end up being unpacked when unpacking aborts, and the
8195 ones already unpacked will fail to configure in the recovery phase
8196 because its dependencies are unavailable.
</p
>
8198 <p
>In this log, the problem manifest itself with this error:
</p
>
8200 <blockquote
><pre
>
8201 dpkg: dependency problems prevent configuration of perl-modules:
8202 perl-modules depends on perl (
>=
5.10.1-
1); however:
8203 Version of perl on system is
5.10.0-
19lenny
2.
8204 dpkg: error processing perl-modules (--configure):
8205 dependency problems - leaving unconfigured
8206 </pre
></blockquote
>
8208 <p
>The perl/perl-modules circular dependency is already
8209 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8210 hopefully be solved as soon as possible, but it is not the only one,
8211 and each one of these loops in the dependency tree can cause similar
8212 failures. Of course, they only occur when there are bugs in other
8213 packages causing the unpacking to fail, but it is rather nasty when
8214 the failure of one package causes the problem to become worse because
8215 of dependency loops.
</p
>
8218 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8219 tireless effort by Bill Allombert
</a
>, the number of circular
8221 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8222 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8224 <p
>Todays testing also exposed a bug in
8225 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8226 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8227 apt-get and aptitude, the latter possibly caused by some circular
8228 dependency. Reported both to BTS to try to get someone to look at
8234 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8235 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8236 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8237 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8238 <description><p
>This is a
8239 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8241 <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
8243 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8244 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8246 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8247 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8248 and dhcp3-server-ldap in Debian use the LDAP server. The two
8249 implementations are quite different in how they use LDAP.
</p
>
8251 To get this information, I started slapd with debugging enabled and
8252 dumped the debug output to a file to get the LDAP searches performed
8253 on a Debian Edu main-server. Here is a summary.
8255 <p
><strong
>powerdns
</strong
></p
>
8257 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8258 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8261 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8262 One
"strict
" mode where the forward and reverse DNS lookups are done
8263 using the same LDAP objects, and a
"tree
" mode where the forward and
8264 reverse entries are in two different subtrees in LDAP with a structure
8265 based on the DNS names, as in tjener.intern and
8266 2.2.0.10.in-addr.arpa.
</p
>
8268 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8269 base, and uses a
"base
" scoped search for the DNS name by adding
8270 "dc=tjener,dc=intern,
" to the base with a filter for
8271 "(associateddomain=tjener.intern)
" for the forward entry and
8272 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8273 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8274 forward entries, it is looking for attributes named dnsttl, arecord,
8275 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8276 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8277 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8278 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8279 spfrecord and modifytimestamp. For reverse entries it is looking for
8280 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8281 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8282 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8283 ldapsearch commands could look like this:
</p
>
8285 <blockquote
><pre
>
8286 ldapsearch -h ldap \
8287 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8288 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8289 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8290 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8291 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8292 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8294 ldapsearch -h ldap \
8295 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8296 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8297 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8298 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8299 srvrecord naptrrecord modifytimestamp
8300 </pre
></blockquote
>
8302 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8303 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8304 example LDAP objects used there. In addition to these objects, the
8305 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8306 also exist.
</p
>
8308 <blockquote
><pre
>
8309 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8311 objectclass: dnsdomain
8312 objectclass: domainrelatedobject
8315 associateddomain: tjener.intern
8317 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8319 objectclass: dnsdomain2
8320 objectclass: domainrelatedobject
8322 ptrrecord: tjener.intern
8323 associateddomain:
2.2.0.10.in-addr.arpa
8324 </pre
></blockquote
>
8326 <p
>In strict mode, the server behaves differently. When looking for
8327 forward DNS entries, it is doing a
"subtree
" scoped search with the
8328 same base as in the tree mode for a object with filter
8329 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8330 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8331 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8332 naptrrecord and modifytimestamp. For reverse entires it also do a
8333 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8334 and the requested attributes are associateddomain, dnsttl and
8335 modifytimestamp. In short, in strict mode the objects with ptrrecord
8336 go away, and the arecord attribute in the forward object is used
8339 <p
>The forward and reverse searches can be simulated using ldapsearch
8340 like this:
</p
>
8342 <blockquote
><pre
>
8343 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8344 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8345 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8346 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8347 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8348 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8350 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8351 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8352 </pre
></blockquote
>
8354 <p
>In addition to the forward and reverse searches , there is also a
8355 search for SOA records, which behave similar to the forward and
8356 reverse lookups.
</p
>
8358 <p
>A thing to note with the PowerDNS behaviour is that it do not
8359 specify any objectclass names, and instead look for the attributes it
8360 need to generate a DNS reply. This make it able to work with any
8361 objectclass that provide the needed attributes.
</p
>
8363 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8364 dnsdomain2 schemas. The latter is used for reverse entries like
8365 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8367 <p
>In Debian Edu, we have created DNS objects using the object classes
8368 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8369 attributes) and domainrelatedobject (for associatedDomain). The use
8370 of structural object classes make it impossible to combine these
8371 classes with the object classes used by DHCP.
</p
>
8373 <p
>There are other schemas that could be used too, for example the
8374 dnszone structural object class used by Gosa and bind-sdb for the DNS
8375 attributes combined with the domainrelatedobject object class, but in
8376 this case some unused attributes would have to be included as well
8377 (zonename and relativedomainname).
</p
>
8379 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8380 mode and not use any of the existing objectclasses (dnsdomain,
8381 dnsdomain2 and dnszone) when one want to combine the DNS information
8382 with DHCP information, and instead create a auxiliary object class
8383 defined something like this (using the attributes defined for
8384 dnsdomain and dnsdomain2 or dnszone):
</p
>
8386 <blockquote
><pre
>
8387 objectclass ( some-oid NAME
'dnsDomainAux
'
8390 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8391 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8392 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8393 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8394 A6Record $ DNAMERecord
8396 </pre
></blockquote
>
8398 <p
>This will allow any object to become a DNS entry when combined with
8399 the domainrelatedobject object class, and allow any entity to include
8400 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8401 developers asking for their view on this schema and if they are
8402 interested in providing such schema with PowerDNS, and I hope my
8403 message will be accepted into their mailing list soon.
</p
>
8405 <p
><strong
>ISC dhcp
</strong
></p
>
8407 <p
>The DHCP server searches for specific objectclass and requests all
8408 the object attributes, and then uses the attributes it want. This
8409 make it harder to figure out exactly what attributes are used, but
8410 thanks to the working example in Debian Edu I can at least get an idea
8411 what is needed without having to read the source code.
</p
>
8413 <p
>In the DHCP server configuration, the LDAP base to use and the
8414 search filter to use to locate the correct dhcpServer entity is
8415 stored. These are the relevant entries from
8416 /etc/dhcp3/dhcpd.conf:
</p
>
8418 <blockquote
><pre
>
8419 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8420 ldap-dhcp-server-cn
"dhcp
";
8421 </pre
></blockquote
>
8423 <p
>The DHCP server uses this information to nest all the DHCP
8424 configuration it need. The cn
"dhcp
" is located using the given LDAP
8425 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8426 search result is this entry:
</p
>
8428 <blockquote
><pre
>
8429 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8432 objectClass: dhcpServer
8433 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8434 </pre
></blockquote
>
8436 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8437 subtree with DHCP configuration. The DHCP configuration subtree base
8438 is located using a base scope search with base
"cn=DHCP
8439 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8440 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8441 The search result is this entry:
</p
>
8443 <blockquote
><pre
>
8444 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8447 objectClass: dhcpService
8448 objectClass: dhcpOptions
8449 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8450 dhcpStatements: ddns-update-style none
8451 dhcpStatements: authoritative
8452 dhcpOption: smtp-server code
69 = array of ip-address
8453 dhcpOption: www-server code
72 = array of ip-address
8454 dhcpOption: wpad-url code
252 = text
8455 </pre
></blockquote
>
8457 <p
>Next, the entire subtree is processed, one level at the time. When
8458 all the DHCP configuration is loaded, it is ready to receive requests.
8459 The subtree in Debian Edu contain objects with object classes
8460 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8461 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8462 and information about netmasks, dynamic range etc. Leaving out the
8463 details here because it is not relevant for the focus of my
8464 investigation, which is to see if it is possible to merge dns and dhcp
8465 related computer objects.
</p
>
8467 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8468 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8469 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8470 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8471 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8474 <blockquote
><pre
>
8475 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8478 objectClass: dhcpHost
8479 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8480 dhcpStatements: fixed-address hostname
8481 </pre
></blockquote
>
8483 <p
>There is less flexiblity in the way LDAP searches are done here.
8484 The object classes need to have fixed names, and the configuration
8485 need to be stored in a fairly specific LDAP structure. On the
8486 positive side, the invidiual dhcpHost entires can be anywhere without
8487 the DN pointed to by the dhcpServer entries. The latter should make
8488 it possible to group all host entries in a subtree next to the
8489 configuration entries, and this subtree can also be shared with the
8490 DNS server if the schema proposed above is combined with the dhcpHost
8491 structural object class.
8493 <p
><strong
>Conclusion
</strong
></p
>
8495 <p
>The PowerDNS implementation seem to be very flexible when it come
8496 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8497 come to the the LDAP structure, the
"strict
" mode is very flexible,
8498 allowing DNS objects to be stored anywhere under the base cn specified
8499 in the configuration.
</p
>
8501 <p
>The DHCP implementation on the other hand is very inflexible, both
8502 regarding which LDAP schemas to use and which LDAP structure to use.
8503 I guess one could implement ones own schema, as long as the
8504 objectclasses and attributes have the names used, but this do not
8505 really help when the DHCP subtree need to have a fairly fixed
8506 structure.
</p
>
8508 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8509 this might work for Debian Edu:
</p
>
8511 <blockquote
><pre
>
8513 cn=machine-info (dhcpService) - dhcpServiceDN points here
8514 cn=dhcp (dhcpServer)
8515 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8516 cn=
10.0.2.0 (dhcpSubnet)
8517 cn=group1 (dhcpGroup/dhcpOptions)
8518 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8519 cn=
192.168.0.0 (dhcpSubnet)
8520 cn=group1 (dhcpGroup/dhcpOptions)
8521 ou=machines - PowerDNS base points here
8522 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8523 </pre
></blockquote
>
8525 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8526 entries to be in the dhcpGroup subtrees, the entries can be stored
8527 there instead of a common machines subtree, and the PowerDNS base
8528 would have to be moved one level up to the machine-info subtree.
</p
>
8530 <p
>The combined object under the machines subtree would look something
8531 like this:
</p
>
8533 <blockquote
><pre
>
8534 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8537 objectClass: dhcpHost
8538 objectclass: domainrelatedobject
8539 objectclass: dnsDomainAux
8540 associateddomain: hostname.intern
8541 arecord:
10.11.12.13
8542 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8543 dhcpStatements: fixed-address hostname.intern
8544 </pre
></blockquote
>
8546 </p
>One could even add the LTSP configuration associated with a given
8547 machine, as long as the required attributes are available in a
8548 auxiliary object class.
</p
>
8553 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8554 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8555 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8556 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8557 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8558 DHCP services in Debian Edu to use the same LDAP objects for a given
8559 computer, to avoid the possibility of having a inconsistent state for
8560 a computer in LDAP (as in DHCP but no DNS entry or the other way
8561 around) and make it easier to add computers to LDAP.
</p
>
8563 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8564 information finally found a solution that seem to work.
</p
>
8566 <p
>The old setup required three LDAP objects for a given computer.
8567 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8568 we switch powerdns to use its strict LDAP method (ldap-method=strict
8569 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8570 merged into one while making it impossible to transfer the reverse map
8571 to a slave DNS server.
</p
>
8573 <p
>If we also replace the object class used to get the DNS related
8574 attributes to one allowing these attributes to be combined with the
8575 dhcphost object class, we can merge the DNS and DHCP entries into one.
8576 I
've written such object class in the dnsdomainaux.schema file (need
8577 proper OIDs, but that is a minor issue), and tested the setup. It
8578 seem to work.
</p
>
8580 <p
>With this test setup in place, we can get away with one LDAP object
8581 for both DNS and DHCP, and even the LTSP configuration I suggested in
8582 an earlier email. The combined LDAP object will look something like
8585 <blockquote
><pre
>
8586 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8588 objectClass: dhcphost
8589 objectclass: domainrelatedobject
8590 objectclass: dnsdomainaux
8591 associateddomain: hostname.intern
8592 arecord:
10.11.12.13
8593 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8594 dhcpstatements: fixed-address hostname
8596 </pre
></blockquote
>
8598 <p
>The DNS server uses the associateddomain and arecord entries, while
8599 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8600 before asking DNS to resolve the fixed-adddress. LTSP will use
8601 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8603 <p
>I am not yet sure if I can get the DHCP server to look for its
8604 dhcphost in a different location, to allow us to put the objects
8605 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8606 that. If I can
't figure out a way to do that, we can still get rid of
8607 the hosts subtree and move all its content into the DHCP Config tree
8608 (which probably should be renamed to be more related to the new
8609 content. I suspect cn=dnsdhcp,ou=services or something like that
8610 might be a good place to put it.
</p
>
8612 <p
>If you want to help out with implementing this for Debian Edu,
8613 please contact us on debian-edu@lists.debian.org.
</p
>
8618 <title>Idea for storing LTSP configuration in LDAP
</title>
8619 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8620 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8621 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8622 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8623 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8624 clients, and that this can be used to fetch configuration from LDAP if
8625 Debian Edu choose to store configuration there.
</p
>
8627 <p
>Armed with this information, I got inspired and wrote a test module
8628 to get configuration from LDAP. The idea is to look up the MAC
8629 address of the client in LDAP, and look for attributes on the form
8630 ltspconfigsetting=value, and use this to export SETTING=value to the
8631 LTSP clients.
</p
>
8633 <p
>The goal is to be able to store the LTSP configuration attributes
8634 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8635 allowing us to store all information about a computer in one place.
</p
>
8637 <p
>This is a untested draft implementation, and I welcome feedback on
8638 this approach. A real LDAP schema for the ltspClientAux objectclass
8639 need to be written. Comments, suggestions, etc?
</p
>
8641 <blockquote
><pre
>
8642 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8644 # Fetch LTSP client settings from LDAP based on MAC address
8646 # Uses ethernet address as stored in the dhcpHost objectclass using
8647 # the dhcpHWAddress attribute or ethernet address stored in the
8648 # ieee802Device objectclass with the macAddress attribute.
8650 # This module is written to be schema agnostic, and only depend on the
8651 # existence of attribute names.
8653 # The LTSP configuration variables are saved directly using a
8654 # ltspConfig prefix and uppercasing the rest of the attribute name.
8655 # To set the SERVER variable, set the ltspConfigServer attribute.
8657 # Some LDAP schema should be created with all the relevant
8658 # configuration settings. Something like this should work:
8660 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8663 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8665 LDAPSERVER=$(debian-edu-ldapserver)
8666 if [
"$LDAPSERVER
" ] ; then
8667 LDAPBASE=$(debian-edu-ldapserver -b)
8668 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8669 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8670 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8671 grep
'^ltspConfig
' | while read attr value ; do
8672 # Remove prefix and convert to upper case
8673 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8674 # bass value on to clients
8675 eval
"$attr=$value; export $attr
"
8679 </pre
></blockquote
>
8681 <p
>I
'm not sure this shell construction will work, because I suspect
8682 the while block might end up in a subshell causing the variables set
8683 there to not show up in ltsp-config, but if that is the case I am sure
8684 the code can be restructured to make sure the variables are passed on.
8685 I expect that can be solved with some testing. :)
</p
>
8687 <p
>If you want to help out with implementing this for Debian Edu,
8688 please contact us on debian-edu@lists.debian.org.
</p
>
8690 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8691 configuration in LDAP that was created around year
2000 by
8692 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8693 Xperience, Inc.,
2000</a
>. I found its
8694 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8695 personal home page over at redhat.com.
</p
>
8700 <title>jXplorer, a very nice LDAP GUI
</title>
8701 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8702 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8703 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8704 <description><p
>Since
8705 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8706 last post
</a
> about available LDAP tools in Debian, I was told about a
8707 LDAP GUI that is even better than luma. The java application
8708 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8709 moving LDAP objects and subtrees using drag-and-drop, and can
8710 authenticate using Kerberos. I have only tested the Kerberos
8711 authentication, but do not have a LDAP setup allowing me to rewrite
8712 LDAP with my test user yet. It is
8713 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8714 Debian
</a
> testing and unstable at the moment. The only problem I
8715 have with it is how it handle errors. If something go wrong, its
8716 non-intuitive behaviour require me to go through some query work list
8717 and remove the failing query. Nothing big, but very annoying.
</p
>
8722 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8723 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8725 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8726 <description><p
>Here is a short update on my
<a
8727 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8728 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8729 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8730 not reporting the status for KDE, because the upgrade crashes when
8731 aptitude try because of missing conflicts
8732 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8733 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8735 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8736 complete list of the installed packages. Based on this I see these
8737 differences when I did a test run today. As usual, I do not really
8738 know what the correct set of packages would be, but thought it best to
8739 publish the difference.
</p
>
8741 <p
>Installed using apt-get, missing with aptitude
</p
>
8743 <blockquote
><p
>
8744 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8745 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8746 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8747 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8748 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8749 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8750 python-
4suite-xml python-eggtrayicon python-gtkhtml2
8751 python-gtkmozembed svgalibg1 xserver-xephyr zip
8752 </p
></blockquote
>
8754 <p
>Installed using apt-get, removed with aptitude
</p
>
8756 <blockquote
><p
>
8757 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8758 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8759 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
8760 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
8761 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
8762 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
8763 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8764 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8765 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8766 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8767 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8768 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8769 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8770 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8771 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8772 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8773 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8774 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8775 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8776 mysql-common swfdec-gnome totem-gstreamer wodim
8777 </p
></blockquote
>
8779 <p
>Installed using aptitude, missing with apt-get
</p
>
8781 <blockquote
><p
>
8782 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8783 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8784 xserver-xorg-input-all xserver-xorg-input-evdev
8785 xserver-xorg-input-kbd xserver-xorg-input-mouse
8786 xserver-xorg-input-synaptics xserver-xorg-video-all
8787 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8788 xserver-xorg-video-chips xserver-xorg-video-cirrus
8789 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8790 xserver-xorg-video-glint xserver-xorg-video-i128
8791 xserver-xorg-video-i740 xserver-xorg-video-mach64
8792 xserver-xorg-video-mga xserver-xorg-video-neomagic
8793 xserver-xorg-video-nouveau xserver-xorg-video-nv
8794 xserver-xorg-video-r128 xserver-xorg-video-radeon
8795 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8796 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8797 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8798 xserver-xorg-video-sis xserver-xorg-video-sisusb
8799 xserver-xorg-video-tdfx xserver-xorg-video-tga
8800 xserver-xorg-video-trident xserver-xorg-video-tseng
8801 xserver-xorg-video-vesa xserver-xorg-video-vmware
8802 xserver-xorg-video-voodoo
8803 </p
></blockquote
>
8805 <p
>Installed using aptitude, removed with apt-get
</p
>
8807 <blockquote
><p
>
8808 deskbar-applet xserver-xorg xserver-xorg-core
8809 xserver-xorg-input-wacom xserver-xorg-video-intel
8810 xserver-xorg-video-openchrome
8811 </p
></blockquote
>
8813 <p
>I was told on IRC that the xorg-xserver package was
8814 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8815 in git
</a
> today to try to get apt-get to not remove xorg completely.
8816 No idea when it hits Squeeze, but when it does I hope it will reduce
8817 the difference somewhat.
8822 <title>LUMA, a very nice LDAP GUI
</title>
8823 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8824 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8825 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8826 <description><p
>The last few days I have been looking into the status of the LDAP
8827 directory in Debian Edu, and in the process I started to miss a GUI
8828 tool to browse the LDAP tree. The only one I was able to find in
8829 Debian/Squeeze and Lenny is
8830 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8831 be a great tool to get a overview of the current LDAP directory
8832 populated by default in Skolelinux. Thanks to it, I have been able to
8833 find empty and obsolete subtrees, misplaced objects and duplicate
8834 objects. It will be installed by default in Debian/Squeeze. If you
8835 are working with LDAP, give it a go. :)
</p
>
8837 <p
>I did notice one problem with it I have not had time to report to
8838 the BTS yet. There is no .desktop file in the package, so the tool do
8839 not show up in the Gnome and KDE menus, but only deep down in in the
8840 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8843 <p
>I have not yet been able to get it to modify the tree yet. I would
8844 like to move objects and remove subtrees directly in the GUI, but have
8845 not found a way to do that with LUMA yet. So in the mean time, I use
8846 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8848 <p
>If you have tips on other GUI tools for LDAP that might be useful
8849 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8851 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8852 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8853 useful GUI alternative. It seem like a good tool, but is unmaintained
8854 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8855 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8860 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8861 <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>
8862 <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>
8863 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8864 <description><p
>A while back, I
8865 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8866 about the fact
</a
> that it is not possible with the provided schemas
8867 for storing DNS and DHCP information in LDAP to combine the two sets
8868 of information into one LDAP object representing a computer.
</p
>
8870 <p
>In the mean time, I discovered that a simple fix would be to make
8871 the dhcpHost object class auxiliary, to allow it to be combined with
8872 the dNSDomain object class, and thus forming one object for one
8873 computer when storing both DHCP and DNS information in LDAP.
</p
>
8875 <p
>If I understand this correctly, it is not safe to do this change
8876 without also changing the assigned number for the object class, and I
8877 do not know enough about LDAP schema design to do that properly for
8878 Debian Edu.
</p
>
8880 <p
>Anyway, for future reference, this is how I believe we could change
8882 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8883 schema
</a
> to solve at least part of the problem with the LDAP schemas
8884 available today from IETF.
</p
>
8887 --- dhcp.schema (revision
65192)
8888 +++ dhcp.schema (working copy)
8890 objectclass (
2.16.840.1.113719.1.203.6.6
8891 NAME
'dhcpHost
'
8892 DESC
'This represents information about a particular client
'
8896 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8897 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8900 <p
>I very much welcome clues on how to do this properly for Debian
8901 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8902 package, and should thus be free to rewrite it as we see fit.
</p
>
8904 <p
>If you want to help out with implementing this for Debian Edu,
8905 please contact us on debian-edu@lists.debian.org.
</p
>
8910 <title>Calling tasksel like the installer, while still getting useful output
</title>
8911 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
8912 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
8913 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
8914 <description><p
>A few times I have had the need to simulate the way tasksel
8915 installs packages during the normal debian-installer run. Until now,
8916 I have ended up letting tasksel do the work, with the annoying problem
8917 of not getting any feedback at all when something fails (like a
8918 conffile question from dpkg or a download that fails), using code like
8921 <blockquote
><pre
>
8922 export DEBIAN_FRONTEND=noninteractive
8923 tasksel --new-install
8924 </pre
></blockquote
>
8926 This would invoke tasksel, let its automatic task selection pick the
8927 tasks to install, and continue to install the requested tasks without
8928 any output what so ever.
8930 Recently I revisited this problem while working on the automatic
8931 package upgrade testing, because tasksel would some times hang without
8932 any useful feedback, and I want to see what is going on when it
8933 happen. Then it occured to me, I can parse the output from tasksel
8934 when asked to run in test mode, and use that aptitude command line
8935 printed by tasksel then to simulate the tasksel run. I ended up using
8938 <blockquote
><pre
>
8939 export DEBIAN_FRONTEND=noninteractive
8940 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
8942 </pre
></blockquote
>
8944 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
8945 --without-recommends -o APT::Install-Recommends=no -y install
8946 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8947 ~pimportant
</tt
>", which will install the gnome desktop task, the
8948 laptop task and all packages with priority standard , required and
8949 important, just like tasksel would have done it during
8950 installation.
</p
>
8952 <p
>A better approach is probably to extend tasksel to be able to
8953 install packages without using debconf-apt-progress, for use cases
8954 like this.
</p
>
8959 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
8960 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
8961 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
8962 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
8963 <description><p
>My
8964 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
8965 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
8966 finally made the upgrade logs available from
8967 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
8968 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8969 apt and aptitude, and found their differences interesting. This time
8970 I will only focus on their removal plans.
</p
>
8972 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
8973 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
8974 surprising part is that it want to remove xorg and all
8975 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8976 sure why. When asking aptitude to do the same, it want to remove
129
8977 packages, but most of them are library packages I suspect are no
8978 longer needed. Both of them want to remove bluetooth packages, which
8979 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
8981 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
8982 which seem like a bad idea and xorg the same way as with Gnome. Asking
8983 aptitude for the same, it wants to remove
192 packages, none which are
8984 too surprising.
</p
>
8986 <p
>I guess the removal of xorg during upgrades should be investigated
8987 and avoided, and perhaps others as well. Here are the complete list
8988 of planned removals. The complete logs is available from the URL
8989 above. Note if you want to repeat these tests, that the upgrade test
8990 for kde+apt-get hung in the tasksel setup because of dpkg asking
8991 conffile questions. No idea why. I worked around it by using
8992 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
8995 <p
><b
>apt-get gnome
72</b
>
8996 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
8997 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8998 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
8999 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9000 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9001 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9002 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9003 xserver-xorg-input-kbd xserver-xorg-input-mouse
9004 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9005 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9006 xserver-xorg-video-ati xserver-xorg-video-chips
9007 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9008 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9009 xserver-xorg-video-glint xserver-xorg-video-i128
9010 xserver-xorg-video-i740 xserver-xorg-video-imstt
9011 xserver-xorg-video-intel xserver-xorg-video-mach64
9012 xserver-xorg-video-mga xserver-xorg-video-neomagic
9013 xserver-xorg-video-nsc xserver-xorg-video-nv
9014 xserver-xorg-video-openchrome xserver-xorg-video-r128
9015 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9016 xserver-xorg-video-rendition xserver-xorg-video-s3
9017 xserver-xorg-video-s3virge xserver-xorg-video-savage
9018 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9019 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9020 xserver-xorg-video-tga xserver-xorg-video-trident
9021 xserver-xorg-video-tseng xserver-xorg-video-v4l
9022 xserver-xorg-video-vesa xserver-xorg-video-vga
9023 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9024 xulrunner-
1.9-gnome-support
</p
>
9026 <p
><b
>aptitude gnome
129</b
>
9028 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9029 djvulibre-desktop finger gnome-app-install gnome-mount
9030 gnome-network-admin gnome-spell gnome-vfs-obexftp
9031 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9032 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9033 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9034 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9035 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9036 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9037 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9038 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9039 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9040 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9041 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9042 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9043 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9044 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9045 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9046 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9047 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9048 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9049 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9050 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9051 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9052 openoffice.org-writer2latex openssl-blacklist p7zip
9053 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9054 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9055 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9056 swfdec-mozilla totem-gstreamer update-manager wodim
9057 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9058 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9061 <p
><b
>apt-get kde
82</b
>
9063 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9064 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9065 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9066 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9067 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9068 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9069 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9070 xserver-xorg-input-kbd xserver-xorg-input-mouse
9071 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9072 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9073 xserver-xorg-video-ati xserver-xorg-video-chips
9074 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9075 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9076 xserver-xorg-video-glint xserver-xorg-video-i128
9077 xserver-xorg-video-i740 xserver-xorg-video-imstt
9078 xserver-xorg-video-intel xserver-xorg-video-mach64
9079 xserver-xorg-video-mga xserver-xorg-video-neomagic
9080 xserver-xorg-video-nsc xserver-xorg-video-nv
9081 xserver-xorg-video-openchrome xserver-xorg-video-r128
9082 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9083 xserver-xorg-video-rendition xserver-xorg-video-s3
9084 xserver-xorg-video-s3virge xserver-xorg-video-savage
9085 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9086 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9087 xserver-xorg-video-tga xserver-xorg-video-trident
9088 xserver-xorg-video-tseng xserver-xorg-video-v4l
9089 xserver-xorg-video-vesa xserver-xorg-video-vga
9090 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9092 <p
><b
>aptitude kde
192</b
>
9093 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9094 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9095 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9096 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9097 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9098 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9099 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9100 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9101 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9102 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9103 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9104 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9105 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9106 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9107 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9108 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9109 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9110 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9111 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9112 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9113 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9114 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9115 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9116 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9117 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9118 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9119 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9120 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9121 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9122 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9123 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9124 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9125 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9126 texlive-common texlive-doc-base texlive-fonts-recommended
9127 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9128 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9129 xulrunner-
1.9</p
>
9135 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9136 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9137 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9138 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9139 <description><p
>The last few days I have done some upgrade testing in Debian, to
9140 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9141 have been discovered and reported in the process
9142 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9143 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9144 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9145 kdebase-workspace-data), and to get a more regular testing going on, I
9146 am working on a script to automate the test.
</p
>
9148 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9149 Gnome or KDE desktop installation inside the chroot before upgrading
9150 it. To ensure no services are started in the chroot, a policy-rc.d
9151 script is inserted. To make sure tasksel believe it is to install a
9152 desktop on a laptop, the tasksel tests are replaced in the chroot
9153 (only acceptable because this is a throw-away chroot).
</p
>
9155 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9156 currently always fail because udev refuses to upgrade with the kernel
9157 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9158 is created. The bug report
9159 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9160 this problem do not trigger in a chroot, but I touch the file anyway
9161 to make sure the upgrade go well. Testing on virtual and real
9162 hardware have failed me because of udev so far, and creating this file
9163 do the trick in such settings anyway. This is a
9164 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9165 issue
</a
> and the current udev behaviour is intended by the udev
9166 maintainer because he lack the resources to rewrite udev to keep
9167 working with old kernels or something like that. I really wish the
9168 udev upstream would keep udev backwards compatible, to avoid such
9169 upgrade problem, but given that they fail to do so, I guess
9170 documenting the way out of this mess is the best option we got for
9171 Debian Squeeze.
</p
>
9173 <p
>Anyway, back to the task at hand, testing upgrades. This test
9174 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9177 <blockquote
><pre
>
9181 if [
"$
1" ] ; then
9190 exec
&lt; /dev/null
9192 mirror=http://ftp.skolelinux.org/debian
9193 tmpdir=chroot-$from-upgrade-$to-$desktop
9195 debootstrap $from $tmpdir $mirror
9196 chroot $tmpdir aptitude update
9197 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9201 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9205 mount -t proc proc $tmpdir/proc
9206 # Make sure proc is unmounted also on failure
9207 trap exit_cleanup EXIT INT
9209 chroot $tmpdir aptitude -y install debconf-utils
9211 # Make sure tasksel autoselection trigger. It need the test scripts
9212 # to return the correct answers.
9213 echo tasksel tasksel/desktop multiselect $desktop | \
9214 chroot $tmpdir debconf-set-selections
9216 # Include the desktop and laptop task
9217 for test in desktop laptop ; do
9218 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9222 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9225 DEBIAN_FRONTEND=noninteractive
9226 DEBIAN_PRIORITY=critical
9227 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9228 chroot $tmpdir tasksel --new-install
9230 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9231 chroot $tmpdir aptitude update
9232 touch $tmpdir/etc/udev/kernel-upgrade
9233 chroot $tmpdir aptitude -y dist-upgrade
9235 </pre
></blockquote
>
9237 <p
>I suspect it would be useful to test upgrades with both apt-get and
9238 with aptitude, but I have not had time to look at how they behave
9239 differently so far. I hope to get a cron job running to do the test
9240 regularly and post the result on the web. The Gnome upgrade currently
9241 work, while the KDE upgrade fail because of the bug in
9242 kdebase-workspace-data
</p
>
9244 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9245 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9246 post, so I will refrain from trying. I can report that for Gnome,
9247 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9248 remove and
1 not upgraded and
1024MB need to be downloaded while for
9249 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9250 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9252 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9253 is able to migrate to dependency based boot sequencing and parallel
9254 booting without a hitch. Was unsure if there were still bugs with
9255 packages failing to clean up their obsolete init.d script during
9256 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9262 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9263 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9264 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9265 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9266 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9267 scripts to migrate (some of) their operations to upstart job while
9268 keeping the init.d for hurd and kfreebsd. The packages with such
9269 needs will need a way to get their init.d scripts to behave
9270 differently when used with sysvinit and with upstart. Because of
9271 this, I had a look at the environment variables set when a init.d
9272 script is running under upstart, and when it is not.
</p
>
9274 <p
>With upstart, I notice these environment variables are set when a
9275 script is started from rcS.d/ (ignoring some irrelevant ones like
9278 <blockquote
><pre
>
9284 UPSTART_EVENTS=startup
9286 UPSTART_JOB=rc-sysinit
9287 </pre
></blockquote
>
9289 <p
>With sysvinit, these environment variables are set for the same
9292 <blockquote
><pre
>
9293 INIT_VERSION=sysvinit-
2.88
9298 </pre
></blockquote
>
9300 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9301 sysvinit are not set by upstart. Not sure if it is intentional or not
9302 to not be compatible with sysvinit in this regard.
</p
>
9304 <p
>For scripts needing to behave differently when upstart is used,
9305 looking for the UPSTART_JOB environment variable seem to be a good
9311 <title>A manual for standards wars...
</title>
9312 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9313 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9314 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9315 <description><p
>Via the
9316 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9317 of Rob Weir
</a
> I came across the very interesting essay named
9318 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9319 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9320 following the standards wars of today.
</p
>
9325 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9326 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9327 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9328 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9329 <description><p
>When using sitesummary at a site to track machines, it is possible
9330 to get a list of the machine types in use thanks to the DMI
9331 information extracted from each machine. The script to do so is
9332 included in the sitesummary package, and here is example output from
9333 the Skolelinux build servers:
</p
>
9335 <blockquote
><pre
>
9336 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9338 Dell Computer Corporation
1
9341 eserver xSeries
345 -[
8670M1X]-
1
9345 </pre
></blockquote
>
9347 <p
>The quality of the report depend on the quality of the DMI tables
9348 provided in each machine. Here there are Intel machines without model
9349 information listed with Intel as vendor and no model, and virtual Xen
9350 machines listed as [no-dmi-info]. One can add -l as a command line
9351 option to list the individual machines.
</p
>
9353 <p
>A larger list is
9354 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9355 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9356 provide the basic sitesummary report publicly. In their report there
9357 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9358 their machines, and as sitesummary is available in both distributions,
9359 it is trivial to get all of them to report to the same central
9360 collector.
</p
>
9365 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9366 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9367 <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>
9368 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9369 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9370 start at boot when an NVidia video card is used is handled. The
9371 problem seem to be that the nvidia X.org driver uses a long time to
9372 initialize, and this duration is longer than kdm is configured to
9375 <p
>I came across two bugs related to this issue,
9376 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9377 against initscripts and passed on to nvidia-glx when it became obvious
9378 that the nvidia drivers were involved, and
9379 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9380 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9382 <p
>To me, it seem that no-one is interested in actually solving the
9383 problem nvidia video card owners experience and make sure the Debian
9384 distribution work out of the box for these users. The nvidia driver
9385 maintainers expect kdm to be set up to wait longer, while kdm expect
9386 the nvidia driver maintainers to fix the driver to start faster, and
9387 while they wait for each other I guess the users end up switching to a
9388 distribution that work for them. I have no idea what the solution is,
9389 but I am pretty sure that waiting for each other is not it.
</p
>
9391 <p
>I wonder why we end up handling bugs this way.
</p
>
9396 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9397 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9398 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9399 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9400 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9401 The feature seem to hold up pretty well, but three fairly serious
9402 issues are known and should be solved:
9406 <li
>The wicd package seen to
9407 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9408 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9409 parallel booting is enabled. No idea why, but the wicd maintainer
9410 seem to be on the case.
</li
>
9412 <li
>The nvidia X driver seem to
9413 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9414 triggered more easily when parallel booting is in effect. The
9415 maintainer is on the case.
</li
>
9417 <li
>The sysv-rc package fail to properly enable dependency based boot
9418 sequencing (the shutdown is broken) when old file-rc users
9419 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9420 sysv-rc. One way to solve it would be for file-rc to create
9421 /etc/init.d/.legacy-bootordering, and another is to try to make
9422 sysv-rc more robust. Will investigate some more and probably upload a
9423 workaround in sysv-rc to help those trying to move from file-rc to
9424 sysv-rc get a working shutdown.
</li
>
9426 </ul
></p
>
9428 <p
>All in all not many surprising issues, and all of them seem
9429 solvable before Squeeze is released. In addition to these there are
9430 some packages with bugs in their dependencies and run level settings,
9431 which I expect will be fixed in a reasonable time span.
</p
>
9433 <p
>If you report any problems with dependencies in init.d scripts to
9434 the BTS, please usertag the report to get it to show up at
9435 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9436 list of usertagged bugs related to this
</a
>.
</p
>
9438 <p
>Update: Correct bug number to file-rc issue.
</p
>
9443 <title>More flexible firmware handling in debian-installer
</title>
9444 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9445 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9446 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9447 <description><p
>After a long break from debian-installer development, I finally
9448 found time today to return to the project. Having to spend less time
9449 working dependency based boot in debian, as it is almost complete now,
9450 definitely helped freeing some time.
</p
>
9452 <p
>A while back, I ran into a problem while working on Debian Edu. We
9453 include some firmware packages on the Debian Edu CDs, those needed to
9454 get disk and network controllers working. Without having these
9455 firmware packages available during installation, it is impossible to
9456 install Debian Edu on the given machine, and because our target group
9457 are non-technical people, asking them to provide firmware packages on
9458 an external medium is a support pain. Initially, I expected it to be
9459 enough to include the firmware packages on the CD to get
9460 debian-installer to find and use them. This proved to be wrong.
9461 Next, I hoped it was enough to symlink the relevant firmware packages
9462 to some useful location on the CD (tried /cdrom/ and
9463 /cdrom/firmware/). This also proved to not work, and at this point I
9464 found time to look at the debian-installer code to figure out what was
9465 going to work.
</p
>
9467 <p
>The firmware loading code is in the hw-detect package, and a closer
9468 look revealed that it would only look for firmware packages outside
9469 the installation media, so the CD was never checked for firmware
9470 packages. It would only check USB sticks, floppies and other
9471 "external
" media devices. Today I changed it to also look in the
9472 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9473 solve the problem I ran into with Debian edu. I also changed it to
9474 look in /firmware/, to make sure the installer also find firmware
9475 provided in the initrd when booting the installer via PXE, to allow us
9476 to provide the same feature in the PXE setup included in Debian
9479 <p
>To make sure firmware deb packages with a license questions are not
9480 activated without asking if the license is accepted, I extended
9481 hw-detect to look for preinst scripts in the firmware packages, and
9482 run these before activating the firmware during installation. The
9483 license question is asked using debconf in the preinst, so this should
9484 solve the issue for the firmware packages I have looked at so far.
</p
>
9486 <p
>If you want to discuss the details of these features, please
9487 contact us on debian-boot@lists.debian.org.
</p
>
9492 <title>Parallellized boot is now the default in Debian/unstable
</title>
9493 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9494 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9495 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9496 <description><p
>Since this evening, parallel booting is the default in
9497 Debian/unstable for machines using dependency based boot sequencing.
9498 Apparently the testing of concurrent booting has been wider than
9499 expected, if I am to believe the
9500 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9501 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9502 with the feature this weekend, to give us some time to detect any
9503 remaining problems before Squeeze is frozen. If serious problems are
9504 detected, it is simple to change the default back to sequential boot.
9505 The upload of the new sysvinit package also activate a new upstream
9508 More information about
9509 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9510 based boot sequencing
</a
> is available from the Debian wiki. It is
9511 currently possible to disable parallel booting when one run into
9512 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9514 <blockquote
><pre
>
9516 </pre
></blockquote
>
9518 <p
>If you report any problems with dependencies in init.d scripts to
9519 the BTS, please usertag the report to get it to show up at
9520 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9521 list of usertagged bugs related to this
</a
>.
</p
>
9526 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9527 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9528 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9529 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9530 <description><p
>In the recent Debian Edu versions, the
9531 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9532 system
</a
> is used to keep track of the machines in the school
9533 network. Each machine will automatically report its status to the
9534 central server after boot and once per night. The network setup is
9535 also reported, and using this information it is possible to get the
9536 MAC address of all network interfaces in the machines. This is useful
9537 to update the DHCP configuration.
</p
>
9539 <p
>To give some idea how to use sitesummary, here is a one-liner to
9540 ist all MAC addresses of all machines reporting to sitesummary. Run
9541 this on the collector host:
</p
>
9543 <blockquote
><pre
>
9544 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9545 </pre
></blockquote
>
9547 <p
>This will list all MAC addresses assosiated with all machine, one
9548 line per machine and with space between the MAC addresses.
</p
>
9550 <p
>To allow system administrators easier job at adding static DHCP
9551 addresses for hosts, it would be possible to extend this to fetch
9552 machine information from sitesummary and update the DHCP and DNS
9553 tables in LDAP using this information. Such tool is unfortunately not
9554 written yet.
</p
>
9559 <title>systemd, an interesting alternative to upstart
</title>
9560 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9561 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9562 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9563 <description><p
>The last few days a new boot system called
9564 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9566 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9568 to the free software world. I have not yet had time to play around
9569 with it, but it seem to be a very interesting alternative to
9570 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9571 a good alternative for Debian when we are able to switch to an event
9572 based boot system. Tollef is
9573 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9574 systemd into Debian, and I look forward to seeing how well it work. I
9575 like the fact that systemd handles init.d scripts with dependency
9576 information natively, allowing them to run in parallel where upstart
9577 at the moment do not.
</p
>
9579 <p
>Unfortunately do systemd have the same problem as upstart regarding
9580 platform support. It only work on recent Linux kernels, and also need
9581 some new kernel features enabled to function properly. This means
9582 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9583 system. Not sure how that will be handled if systemd proves to be the
9584 way forward.
</p
>
9586 <p
>In the mean time, based on the
9587 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9588 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9589 decided to enable full parallel booting as the default in Debian as
9590 soon as possible (probably this weekend or early next week), to see if
9591 there are any remaining serious bugs in the init.d dependencies. A
9592 new version of the sysvinit package implementing this change is
9593 already in experimental. If all go well, Squeeze will be released
9594 with parallel booting enabled by default.
</p
>
9599 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9600 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9601 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9602 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9603 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9604 complete, so complete that it is actually possible to run all the
9605 init.d scripts in parallell based on these dependencies. If you want
9606 to test your Squeeze system, make sure
9607 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9608 based boot sequencing
</a
> is enabled, and add this line to
9609 /etc/default/rcS:
</p
>
9611 <blockquote
><pre
>
9612 CONCURRENCY=makefile
9613 </pre
></blockquote
>
9615 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9616 scripts in parallel using the dependency information stored in
9617 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9618 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9619 to try to start the kdm and gdm scripts as early as possible, and will
9620 start the facilities required by kdm or gdm as early as possible to
9621 make this happen.
</p
>
9623 <p
>Give it a try, and see if you like the result. If some services
9624 fail to start properly, it is most likely because they have incomplete
9625 init.d script dependencies in their startup script (or some of their
9626 dependent scripts have incomplete dependencies). Report bugs and get
9627 the package maintainers to fix it. :)
</p
>
9629 <p
>Running scripts in parallel could be the default in Debian when we
9630 manage to get the init.d script dependencies complete and correct. I
9631 expect we will get there in Squeeze+
1, if we get manage to test and
9632 fix the remaining issues.
</p
>
9634 <p
>If you report any problems with dependencies in init.d scripts to
9635 the BTS, please usertag the report to get it to show up at
9636 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9637 list of usertagged bugs related to this
</a
>.
</p
>
9642 <title>Debian has switched to dependency based boot sequencing
</title>
9643 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9645 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9646 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9647 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9648 have been migrated to using dependency based boot sequencing. This
9649 conclude work me and others have been doing for the last three days.
9650 It feels great to see this finally part of the default Debian
9651 installation. Now we just need to weed out the last few problems that
9652 are bound to show up, to get everything ready for Squeeze.
</p
>
9654 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9655 fixing the more fundamental problem of handing the event based
9656 non-predictable kernel in the early boot.
</p
>
9661 <title>Taking over sysvinit development
</title>
9662 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9663 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9664 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9665 <description><p
>After several years of frustration with the lack of activity from
9666 the existing sysvinit upstream developer, I decided a few weeks ago to
9667 take over the package and become the new upstream. The number of
9668 patches to track for the Debian package was becoming a burden, and the
9669 lack of synchronization between the distribution made it hard to keep
9670 the package up to date.
</p
>
9672 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9673 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9674 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9675 and Fedora), based on the patches currently in use in these
9676 distributions. We Debian maintainers plan to move to this tarball as
9677 the new upstream as soon as we find time to do the merge. Since the
9678 new tarball was created, we agreed with Werner at SuSe to make a new
9679 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9680 development there. The project is registered and currently waiting
9681 for approval by the Savannah administrators, and as soon as it is
9682 approved, we will import the old versions from svn and continue
9683 working on the future release.
</p
>
9685 <p
>It is a bit ironic that this is done now, when some of the involved
9686 distributions are moving to upstart as a syvinit replacement.
</p
>
9691 <title>Debian boots quicker and quicker
</title>
9692 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9693 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9694 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9695 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9696 people involved in the boot system on Debian and Ubuntu, to see if we
9697 could find more ways to speed up the boot system. This was an Ubuntu
9699 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9700 gathering
</a
>. It was quite productive. We also discussed the future
9701 of boot systems, and ways to handle the increasing number of boot
9702 issues introduced by the Linux kernel becoming more and more
9703 asynchronous and event base. The Ubuntu approach using udev and
9704 upstart might be a good way forward. Time will show.
</p
>
9706 <p
>Anyway, there are a few ways at the moment to speed up the boot
9707 process in Debian. All of these should be applied to get a quick
9712 <li
>Use dash as /bin/sh.
</li
>
9714 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9715 clock is in UTC.
</li
>
9717 <li
>Install and activate the insserv package to enable
9718 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9719 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9723 These points are based on the Google summer of code work done by
9724 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9727 <p
>Support for makefile-style concurrency during boot was uploaded to
9728 unstable yesterday. When we tested it, we were able to cut
6 seconds
9729 from the boot sequence. It depend on very correct dependency
9730 declaration in all init.d scripts, so I expect us to find edge cases
9731 where the dependences in some scripts are slightly wrong when we start
9732 using this.
</p
>
9734 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9735 introduced by Raphael Geissert today, one that could affect the
9736 startup speed as well. Instead of starting some scripts concurrently
9737 from rcS.d/ and another set of scripts from rc2.d/, it would be
9738 possible to run a of them in the same process. A quick way to test
9739 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9740 insserv
'. Will need to test if that work. :)
</p
>
9745 <title>BSAs påstander om piratkopiering møter motstand
</title>
9746 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9748 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
9749 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
9750 programvareselskapene som Microsoft og Apple, publisert en rapport der
9751 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9752 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9754 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
9755 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
9756 dagene. Et spesielt interessant kommentar fra Sverige,
9757 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
9758 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
9761 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
9762 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9763 företag.
"Man bör nog kanske inte se de här siffrorna som helt
9764 exakta
", säger BSAs Sverigechef John Hugosson.
9767 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9768 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9769 piracy figures need a shot of reality
</a
> og
<a
9770 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9771 Copyright Treaty Work?
</a
></p
>
9773 <p
>Fant lenkene via
<a
9774 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9775 på Slashdot
</a
>.
</p
>
9780 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9781 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9782 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9783 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9784 <description><p
>Kom over
9785 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9786 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9787 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9788 jobber til daglig. En rask opptelling forteller meg at vi har
490
9789 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9790 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9791 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9796 <title>Kryptert harddisk - naturligvis
</title>
9797 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9798 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9799 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9800 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9801 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9802 når en tar tap av arbeidstid, fortrolige dokumenter,
9803 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9804 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9805 til at jeg har kryptert harddisken på både kontormaskinen og min
9806 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9807 komme på avveie, den første informasjon relatert til jobben min ved
9808 Universitetet i Oslo, og den andre relatert til blant annet
9809 foreningsarbeide. Kryptering av diskene gjør at det er lite
9810 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9811 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9812 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9813 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9814 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9815 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9816 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9817 det er gjort slik jeg gjør det er minimale, og gevinstene er
9818 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9819 maskinen reinstalleres og alt er tapt.
</p
>
9821 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9822 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9823 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9824 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9825 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9826 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9827 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9828 betydelige.
</p
>
9833 <title>Two projects that have improved the quality of free software a lot
</title>
9834 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9835 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9836 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9837 <description><p
>There are two software projects that have had huge influence on the
9838 quality of free software, and I wanted to mention both in case someone
9839 do not yet know them.
</p
>
9841 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9842 tool to detect and expose errors in the memory handling of programs.
9843 It is easy to use, all one need to do is to run
'valgrind program
',
9844 and it will report any problems on stdout. It is even better if the
9845 program include debug information. With debug information, it is able
9846 to report the source file name and line number where the problem
9847 occurs. It can report things like
'reading past memory block in file
9848 X line N, the memory block was allocated in file Y, line M
', and
9849 'using uninitialised value in control logic
'. This tool has made it
9850 trivial to investigate reproducible crash bugs in programs, and have
9851 reduced the number of this kind of bugs in free software a lot.
9853 <p
>The second one is
9854 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9855 a source code checker. It is able to process the source of a program
9856 and find problems in the logic without running the program. It
9857 started out as the Stanford Checker and became well known when it was
9858 used to find bugs in the Linux kernel. It is now a commercial tool
9859 and the company behind it is running
9860 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9861 free software community, where a lot of free software projects get
9862 their source checked for free. Several thousand defects have been
9863 found and fixed so far. It can find errors like
'lock L taken in file
9864 X line N is never released if exiting in line M
', or
'the code in file
9865 Y lines O to P can never be executed
'. The projects included in the
9866 community service project have managed to get rid of a lot of
9867 reliability problems thanks to Coverity.
</p
>
9869 <p
>I believe tools like this, that are able to automatically find
9870 errors in the source, are vital to improve the quality of software and
9871 make sure we can get rid of the crashing and failing software we are
9872 surrounded by today.
</p
>
9877 <title>No patch is not better than a useless patch
</title>
9878 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9879 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9880 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9881 <description><p
>Julien Blache
9882 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9883 patch is better than a useless patch
</a
>. I completely disagree, as a
9884 patch allow one to discuss a concrete and proposed solution, and also
9885 prove that the issue at hand is important enough for someone to spent
9886 time on fixing it. No patch do not provide any of these positive
9887 properties.
</p
>
9892 <title>Standardize on protocols and formats, not vendors and applications
</title>
9893 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9894 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9895 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9896 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9897 very good one to form a long lived computer infrastructure. It is the
9898 simple one, lost by many in todays computer industry: Standardize on
9899 open network protocols and open exchange/storage formats, not applications.
9900 Applications come and go, while protocols and files tend to stay, and
9901 thus one want to make it easy to change application and vendor, while
9902 avoiding conversion costs and locking users to a specific platform or
9903 application.
</p
>
9905 <p
>This approach make it possible to replace the client applications
9906 independently of the server applications. One can even allow users to
9907 use several different applications as long as they handle the selected
9908 protocol and format. In the normal case, only one client application
9909 is recommended and users only get help if they choose to use this
9910 application, but those that want to deviate from the easy path are not
9911 blocked from doing so.
</p
>
9913 <p
>It also allow us to replace the server side without forcing the
9914 users to replace their applications, and thus allow us to select the
9915 best server implementation at any moment, when scale and resouce
9916 requirements change.
</p
>
9918 <p
>I strongly recommend standardizing - on open network protocols and
9919 open formats, but I would never recommend standardizing on a single
9920 application that do not use open network protocol or open formats.
</p
>
9925 <title>Returning from Skolelinux developer gathering
</title>
9926 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
9927 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
9928 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
9929 <description><p
>I
'm sitting on the train going home from this weekends Debian
9930 Edu/Skolelinux development gathering. I got a bit done tuning the
9931 desktop, and looked into the dynamic service location protocol
9932 implementation avahi. It look like it could be useful for us. Almost
9933 30 people participated, and I believe it was a great environment to
9934 get to know the Skolelinux system. Walter Bender, involved in the
9935 development of the Sugar educational platform, presented his stuff and
9936 also helped me improve my OLPC installation. He also showed me that
9937 his Turtle Art application can be used in standalone mode, and we
9938 agreed that I would help getting it packaged for Debian. As a
9939 standalone application it would be great for Debian Edu. We also
9940 tried to get the video conferencing working with two OLPCs, but that
9941 proved to be too hard for us. The application seem to need more work
9942 before it is ready for me. I look forward to getting home and relax
9948 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
9949 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
9950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
9951 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
9952 <description><p
>The state of standardized LDAP schemas on Linux is far from
9953 optimal. There is RFC
2307 documenting one way to store NIS maps in
9954 LDAP, and a modified version of this normally called RFC
2307bis, with
9955 some modifications to be compatible with Active Directory. The RFC
9956 specification handle the content of a lot of system databases, but do
9957 not handle DNS zones and DHCP configuration.
</p
>
9959 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
9960 we would like to store information about users, SMB clients/hosts,
9961 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9962 and LTSP configuration in LDAP. These objects have a lot in common,
9963 but with the current LDAP schemas it is not possible to have one
9964 object per entity. For example, one need to have at least three LDAP
9965 objects for a given computer, one with the SMB related stuff, one with
9966 DNS information and another with DHCP information. The schemas
9967 provided for DNS and DHCP are impossible to combine into one LDAP
9968 object. In addition, it is impossible to implement quick queries for
9969 netgroup membership, because of the way NIS triples are implemented.
9970 It just do not scale. I believe it is time for a few RFC
9971 specifications to cleam up this mess.
</p
>
9973 <p
>I would like to have one LDAP object representing each computer in
9974 the network, and this object can then keep the SMB (ie host key), DHCP
9975 (mac address/name) and DNS (name/IP address) settings in one place.
9976 It need to be efficently stored to make sure it scale well.
</p
>
9978 <p
>I would also like to have a quick way to map from a user or
9979 computer and to the net group this user or computer is a member.
</p
>
9981 <p
>Active Directory have done a better job than unix heads like myself
9982 in this regard, and the unix side need to catch up. Time to start a
9983 new IETF work group?
</p
>
9988 <title>Endelig er Debian Lenny gitt ut
</title>
9989 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
9990 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
9991 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
9992 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
9993 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
9994 Et langt steg videre for Debian-prosjektet, og en rekke nye
9995 programpakker blir nå tilgjengelig for de av oss som bruker den
9996 stabile utgaven av Debian. Neste steg er nå å få
9997 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
9998 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
9999 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10000 slippes løs på skolene. Takk til alle debian-utviklerne som har
10001 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10002 bootsekvens tilgjengelig i stabil utgave, vha pakken
10003 <tt
>insserv
</tt
>.
</p
>
10008 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10009 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10010 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10011 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10012 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10013 Oslo. Most of Saturday was used for the general assemly for the
10014 member organization, but the rest of the weekend I used to tune the
10015 LTSP installation. LTSP now work out of the box on the
10-network.
10016 Acer Aspire One proved to be a very nice thin client, with both
10017 screen, mouse and keybard in a small box. Was working on getting the
10018 diskless workstation setup configured out of the box, but did not
10019 finish it before the weekend was up.
</p
>
10021 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10022 the Brazilian group, so that will have to wait for the next
10023 development gathering. Would love to have the Debian Edu installer
10024 automatically detect and configure a multiseat setup when it find one
10025 of these cards.
</p
>
10030 <title>The sorry state of multimedia browser plugins in Debian
</title>
10031 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10032 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10033 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10034 <description><p
>Recently I have spent some time evaluating the multimedia browser
10035 plugins available in Debian Lenny, to see which one we should use by
10036 default in Debian Edu. We need an embedded video playing plugin with
10037 control buttons to pause or stop the video, and capable of streaming
10038 all the multimedia content available on the web. The test results and
10039 notes are available on
10040 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10041 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10042 fill this need. My personal video player favorite, VLC, has a really
10043 bad plugin which fail on a lot of the test pages. A lot of the MIME
10044 types I would expect to work with any free software player (like
10045 video/ogg), just do not work. And simple formats like the
10046 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10047 totem and vlc plugins. I hope the situation will improve soon. No
10048 wonder sites use the proprietary Adobe flash to play video.
</p
>
10050 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10051 be the only one fitting our needs. :/
</p
>