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>Appstream just learned how to map hardware to packages too!
</title>
11 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
13 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
14 <description><p
>I received a very nice Christmas present today. As my regular
15 readers probably know, I have been working on the
16 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
17 system
</a
> for many years. The goal of the Isenkram system is to make
18 it easier for users to figure out what to install to get a given piece
19 of hardware to work in Debian, and a key part of this system is a way
20 to map hardware to packages. Isenkram have its own mapping database,
21 and also uses data provided by each package using the AppStream
22 metadata format. And today,
23 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
24 Debian learned to look up hardware the same way Isenkram is doing it,
25 ie using fnmatch():
</p
>
28 % appstreamcli what-provides modalias \
29 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
30 Identifier: pymissile [generic]
32 Summary: Control original Striker USB Missile Launcher
34 % appstreamcli what-provides modalias usb:v0694p0002d0000
35 Identifier: libnxt [generic]
37 Summary: utility library for talking to the LEGO Mindstorms NXT brick
40 Identifier: t2n [generic]
42 Summary: Simple command-line tool for Lego NXT
45 Identifier: python-nxt [generic]
47 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
50 Identifier: nbc [generic]
52 Summary: C compiler for LEGO Mindstorms NXT bricks
55 </pre
></p
>
57 <p
>A similar query can be done using the combined AppStream and
58 Isenkram databases using the isenkram-lookup tool:
</p
>
61 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
63 % isenkram-lookup usb:v0694p0002d0000
69 </pre
></p
>
71 <p
>You can find modalias values relevant for your machine using
72 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
74 <p
>If you want to make this system a success and help Debian users
75 make the most of the hardware they have, please
76 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
77 AppStream metadata for your package following the guidelines
</a
>
78 documented in the wiki. So far only
11 packages provide such
79 information, among the several hundred hardware specific packages in
80 Debian. The Isenkram database on the other hand contain
101 packages,
81 mostly related to USB dongles. Most of the packages with hardware
82 mapping in AppStream are LEGO Mindstorms related, because I have, as
83 part of my involvement in
84 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
85 team
</a
> given priority to making sure LEGO users get proposed the
86 complete set of packages in Debian for that particular hardware. The
87 team also got a nice Christmas present today. The
88 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
89 package
</a
> made it into Debian. With this package in place, it is
90 not possible to use the LEGO Mindstorms NXT unit with only free
91 software, as the nxt-firmware package contain the source and firmware
92 binaries for the NXT brick.
</p
>
94 <p
>As usual, if you use Bitcoin and want to show your support of my
95 activities, please send Bitcoin donations to my address
96 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
101 <title>Isenkram updated with a lot more hardware-package mappings
</title>
102 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
104 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
105 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
106 system
</a
> I wrote two years ago to make it easier in Debian to find
107 and install packages to get your hardware dongles to work, is still
108 going strong. It is a system to look up the hardware present on or
109 connected to the current system, and map the hardware to Debian
110 packages. It can either be done using the tools in isenkram-cli or
111 using the user space daemon in the isenkram package. The latter will
112 notify you, when inserting new hardware, about what packages to
113 install to get the dongle working. It will even provide a button to
114 click on to ask packagekit to install the packages.
</p
>
116 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
135 </pre
></p
>
137 <p
>It can also list the firware package providing firmware requested
138 by the load kernel modules, which in my case is an empty list because
139 I have all the firmware my machine need:
142 % /usr/sbin/isenkram-autoinstall-firmware -l
143 info: did not find any firmware files requested by loaded kernel modules. exiting
145 </pre
></p
>
147 <p
>The last few days I had a look at several of the around
250
148 packages in Debian with udev rules. These seem like good candidates
149 to install when a given hardware dongle is inserted, and I found
150 several that should be proposed by isenkram. I have not had time to
151 check all of them, but am happy to report that now there are
97
152 packages packages mapped to hardware by Isenkram.
11 of these
153 packages provide hardware mapping using AppStream, while the rest are
154 listed in the modaliases file provided in isenkram.
</p
>
156 <p
>These are the packages with hardware mappings at the moment. The
157 <strong
>marked packages
</strong
> are also announcing their hardware
158 support using AppStream, for everyone to use:
</p
>
160 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
161 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
162 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
163 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
164 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
165 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
166 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
167 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
168 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
169 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
170 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
171 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
172 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
173 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
174 pcscd, pidgin-blinklight, printer-driver-splix,
175 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
176 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
177 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
178 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
179 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
180 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
181 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
182 xserver-xorg-video-vmware, yubikey-personalization and
183 zd1211-firmware
</p
>
185 <p
>If you know of other packages, please let me know with a wishlist
186 bug report against the isenkram-cli package, and ask the package
188 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
189 metadata according to the guidelines
</a
> to provide the information
190 for everyone. In time, I hope to get rid of the isenkram specific
191 hardware mapping and depend exclusively on AppStream.
</p
>
193 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
194 much hardware, and suggest that the package with with any ethernet
195 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
196 the details. I hope the maintainer find time to address it soon. In
197 the mean time I provide an override in isenkram.
</p
>
202 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
203 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
204 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
205 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
206 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
208 <p
>In my early years, I played
209 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
210 Elite
</a
> on my PC. I spent many months trading and fighting in
211 space, and reached the
'elite
' fighting status before I moved on. The
212 original Elite game was available on Commodore
64 and the IBM PC
213 edition I played had a
64 KB executable. I am still impressed today
214 that the authors managed to squeeze both a
3D engine and details about
215 more than
2000 planet systems across
7 galaxies into a binary so
218 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
219 software game Oolite inspired by Elite
</a
> for a while, but did not
220 really have time to test it properly until a few days ago. It was
221 great to discover that my old knowledge about trading routes were
222 still valid. But my fighting and flying abilities were gone, so I had
223 to retrain to be able to dock on a space station. And I am still not
224 able to make much resistance when I am attacked by pirates, so I
225 bougth and mounted the most powerful laser in the rear to be able to
226 put up at least some resistance while fleeing for my life. :)
</p
>
228 <p
>When playing Elite in the late eighties, I had to discover
229 everything on my own, and I had long lists of prices seen on different
230 planets to be able to decide where to trade what. This time I had the
232 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
233 where information about each planet is easily available with common
234 price ranges and suggested trading routes. This improved my ability
235 to earn money and I have been able to earn enough to buy a lot of
236 useful equipent in a few days. I believe I originally played for
237 months before I could get a docking computer, while now I could get it
238 after less then a week.
</p
>
240 <p
>If you like science fiction and dreamed of a life as a vagabond in
241 space, you should try out Oolite. It is available for Linux, MacOSX
242 and Windows, and is included in Debian and derivatives since
2011.
</p
>
244 <p
>As usual, if you use Bitcoin and want to show your support of my
245 activities, please send Bitcoin donations to my address
246 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
251 <title>Quicker Debian installations using eatmydata
</title>
252 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
253 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
254 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
255 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
256 installation system, observing how using
257 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
258 could speed up the installation
</a
> quite a bit. My testing measured
259 speedup around
20-
40 percent for Debian Edu, where we install around
260 1000 packages from within the installer. The eatmydata package
261 provide a way to disable/delay file system flushing. This is a bit
262 risky in the general case, as files that should be stored on disk will
263 stay only in memory a bit longer than expected, causing problems if a
264 machine crashes at an inconvenient time. But for an installation, if
265 the machine crashes during installation the process is normally
266 restarted, and avoiding disk operations as much as possible to speed
267 up the process make perfect sense.
269 <p
>I added code in the Debian Edu specific installation code to enable
270 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
271 but did not have time to push it any further. But a few months ago I
272 picked it up again and worked with the libeatmydata package maintainer
273 Mattia Rizzolo to make it easier for everyone to get this installation
274 speedup in Debian. Thanks to our cooperation There is now an
275 eatmydata-udeb package in Debian testing and unstable, and simply
276 enabling/installing it in debian-installer (d-i) is enough to get the
277 quicker installations. It can be enabled using preseeding. The
278 following untested kernel argument should do the trick:
</p
>
280 <blockquote
><pre
>
281 preseed/early_command=
"anna-install eatmydata-udeb
"
282 </pre
></blockquote
>
284 <p
>This should ask d-i to install the package inside the d-i
285 environment early in the installation sequence. Having it installed
286 in d-i in turn will make sure the relevant scripts are called just
287 after debootstrap filled /target/ with the freshly installed Debian
288 system to configure apt to run dpkg with eatmydata. This is enough to
289 speed up the installation process. There is a proposal to
290 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
291 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
292 tested its impact.
</p
>
298 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
299 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
300 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
301 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
302 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
303 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
304 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
305 elever over det ganske land skal levere inn hvert år. Det mange ikke
306 vet er at selv om de kommersielle alternativene
307 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
308 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
309 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
310 utmerket fri programvarealternativ som kan. Oversetterverktøyet
311 Apertium har støtte for en rekke språkkombinasjoner, og takket være
312 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
313 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
314 nynorsk, og få den automatoversatt til det andre skriftspråket.
315 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
316 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
317 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
318 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
319 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
320 teksten din i webskjemaet der.
322 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
323 teknologien kan du enten installere pakken
324 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
325 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
327 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
328 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
329 denne teksten som ble skrevet på bokmål over maskinoversatt til
334 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
335 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
336 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
337 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
338 veit er at sjølv om dei kommersielle alternativa
339 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
340 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
341 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
342 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
343 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
344 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
345 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
346 nynorsk, og få den *automatoversatt til det andre skriftspråket.
347 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
348 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
349 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
350 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
351 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
352 teksta di i *webskjemaet der.
354 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
355 teknologien kan du anten installera pakken
356 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
357 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
358 *api.*apertium.org. Sjå
359 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
360 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
361 for denne teksta som vart skreva på bokmål over *maskinoversatt til
367 <title>Coz profiler for multi-threaded software is now in Debian
</title>
368 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
369 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
370 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
371 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
372 profiler able to run benchmarking experiments on the instrumented
373 multi-threaded program, finally
374 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
375 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
377 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
378 blogged about the coz tool
</a
> in August working with upstream to make
379 it suitable for Debian. There are still issues with clang
380 compatibility, inline assembly only working x86 and minimized
381 JavaScript libraries.
</p
>
383 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
385 <p
><blockquote
>
386 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
387 </blockquote
></p
>
389 <p
>This will produce a profile.coz file in the current working
390 directory with the profiling information. This is then given to a
391 JavaScript application provided in the package and available from
392 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
393 To start the local copy, invoke it in a browser like this:
</p
>
395 <p
><blockquote
>
396 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
397 </blockquote
></p
>
399 <p
>See the project home page and the
400 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
401 ;login: article on Coz
</a
> for more information on how it is
407 <title>My own self balancing Lego Segway
</title>
408 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
409 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
410 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
411 <description><p
>A while back I received a Gyro sensor for the NXT
412 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
413 present. It had been on my wishlist for a while, because I wanted to
414 build a Segway like balancing lego robot. I had already built
415 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
416 robot
</a
> with the kids, using the light/color sensor included in the
417 NXT kit as the balance sensor, but it was not working very well. It
418 could balance for a while, but was very sensitive to the light
419 condition in the room and the reflective properties of the surface and
420 would fall over after a short while. I wanted something more robust,
422 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
423 gyro sensor from HiTechnic
</a
> I believed would solve it on my
424 wishlist for some years before it suddenly showed up as a gift from my
425 loved ones. :)
</p
>
427 <p
>Unfortunately I have not had time to sit down and play with it
428 since then. But that changed some days ago, when I was searching for
429 lego segway information and came across a recipe from HiTechnic for
431 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
432 HTWay
</a
>, a segway like balancing robot. Build instructions and
433 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
434 code
</a
> was included, so it was just a question of putting it all
435 together. And thanks to the great work of many Debian developers, the
436 compiler needed to build the source for the NXT is already included in
437 Debian, so I was read to go in less than an hour. The resulting robot
438 do not look very impressive in its simplicity:
</p
>
440 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
442 <p
>Because I lack the infrared sensor used to control the robot in the
443 design from HiTechnic, I had to comment out the last task
444 (taskControl). I simply placed /* and */ around it get the program
445 working without that sensor present. Now it balances just fine until
446 the battery status run low:
</p
>
448 <p align=
"center
"><video width=
"70%
" controls=
"true
">
449 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
450 </video
></p
>
452 <p
>Now we would like to teach it how to follow a line and take remote
453 control instructions using the included Bluetooth receiver in the NXT.
</p
>
455 <p
>If you, like me, love LEGO and want to make sure we find the tools
456 they need to work with LEGO in Debian and all our derivative
457 distributions like Ubuntu, check out
458 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
459 project page
</a
> and join the Debian LEGO team. Personally I own a
460 RCX and NXT controller (no EV3), and would like to make sure the
461 Debian tools needed to program the systems I own work as they
467 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
468 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
469 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
470 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
471 <description><p
>In July
472 <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
473 wrote how to get the Signal Chrome/Chromium app working
</a
> without
474 the ability to receive SMS messages (aka without a cell phone). It is
475 time to share some experiences and provide an updated setup.
</p
>
477 <p
>The Signal app have worked fine for several months now, and I use
478 it regularly to chat with my loved ones. I had a major snag at the
479 end of my summer vacation, when the the app completely forgot my
480 setup, identity and keys. The reason behind this major mess was
481 running out of disk space. To avoid that ever happening again I have
482 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
483 roll back to an earlier version if the files are wiped by mistake. I
484 had to use it once after introducing the git backup. When rolling
485 back to an earlier version, one need to use the
'reset session
' option
486 in Signal to get going, and notify the people you talk with about the
487 problem. I assume there is some sequence number tracking in the
488 protocol to detect rollback attacks. The git repository is rather big
489 (
674 MiB so far), but I have not tried to figure out if some of the
490 content can be added to a .gitignore file due to lack of spare
493 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
494 make it impossible to send messages using Signal. I could still
495 receive them, but had to patch the code with a new timestamp to send.
496 I believe the timeout is added by the developers to force people to
497 upgrade to the latest version of the app, even when there is no
498 protocol changes, to reduce the version skew among the user base and
499 thus try to keep the number of support requests down.
</p
>
501 <p
>Since my original recipe, the Signal source code changed slightly,
502 making the old patch fail to apply cleanly. Below is an updated
503 patch, including the shell wrapper I use to start Signal. The
504 original version required a new user to locate the JavaScript console
505 and call a function from there. I got help from a friend with more
506 JavaScript knowledge than me to modify the code to provide a GUI
507 button instead. This mean that to get started you just need to run
508 the wrapper and click the
'Register without mobile phone
' to get going
509 now. I
've also modified the timeout code to always set it to
90 days
510 in the future, to avoid having to patch the code regularly.
</p
>
512 <p
>So, the updated recipe for Debian Jessie:
</p
>
516 <li
>First, install required packages to get the source code and the
517 browser you need. Signal only work with Chrome/Chromium, as far as I
518 know, so you need to install it.
521 apt install git tor chromium
522 git clone https://github.com/WhisperSystems/Signal-Desktop.git
523 </pre
></li
>
525 <li
>Modify the source code using command listed in the the patch
526 block below.
</li
>
528 <li
>Start Signal using the run-signal-app wrapper (for example using
529 <tt
>`pwd`/run-signal-app
</tt
>).
531 <li
>Click on the
'Register without mobile phone
', will in a phone
532 number you can receive calls to the next minute, receive the
533 verification code and enter it into the form field and press
534 'Register
'. Note, the phone number you use will be user Signal
535 username, ie the way others can find you on Signal.
</li
>
537 <li
>You can now use Signal to contact others. Note, new contacts do
538 not show up in the contact list until you restart Signal, and there is
539 no way to assign names to Contacts. There is also no way to create or
540 update chat groups. I suspect this is because the web app do not have
541 a associated contact database.
</li
>
545 <p
>I am still a bit uneasy about using Signal, because of the way its
546 main author moxie0 reject federation and accept dependencies to major
547 corporations like Google (part of the code is fetched from Google) and
548 Amazon (the central coordination point is owned by Amazon). See for
550 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
551 LibreSignal issue tracker
</a
> for a thread documenting the authors
552 view on these issues. But the network effect is strong in this case,
553 and several of the people I want to communicate with already use
554 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
555 once it
<a href=
"https://bugs.debian.org/
830265">work on my
556 laptop
</a
>? It already work on Windows and Android, and is included
557 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
558 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
559 working on Debian Stable.
</p
>
561 <p
>Anyway, this is the patch I apply to the Signal code to get it
562 working. It switch to the production servers, disable to timeout,
563 make registration easier and add the shell wrapper:
</p
>
566 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
567 diff --git a/js/background.js b/js/background.js
568 index
24b4c1d.
.579345f
100644
569 --- a/js/background.js
570 +++ b/js/background.js
575 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
576 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
577 var SERVER_PORTS = [
80,
4433,
8443];
578 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
579 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
581 window.getSocketStatus = function() {
582 if (messageReceiver) {
583 diff --git a/js/expire.js b/js/expire.js
584 index
639aeae..beb91c3
100644
589 'use strict
';
590 - var BUILD_EXPIRATION =
0;
591 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
593 window.extension = window.extension || {};
595 diff --git a/js/views/install_view.js b/js/views/install_view.js
596 index
7816f4f.
.1d6233b
100644
597 --- a/js/views/install_view.js
598 +++ b/js/views/install_view.js
601 'click .step1
': this.selectStep.bind(this,
1),
602 'click .step2
': this.selectStep.bind(this,
2),
603 -
'click .step3
': this.selectStep.bind(this,
3)
604 +
'click .step3
': this.selectStep.bind(this,
3),
605 +
'click .callreg
': function() { extension.install(
'standalone
') },
608 clearQR: function() {
609 diff --git a/options.html b/options.html
610 index dc0f28e.
.8d709f6
100644
614 &lt;div class=
'nav
'>
615 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
616 &lt;p
>{{ installTagline }}
&lt;/p
>
617 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
618 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
619 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
622 &lt;span class=
'dot step1 selected
'>&lt;/span
>
623 &lt;span class=
'dot step2
'>&lt;/span
>
624 &lt;span class=
'dot step3
'>&lt;/span
>
625 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
626 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
632 +userdata=
"`pwd`/userdata
"
633 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
634 + (cd $userdata
&& git init)
636 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
638 + --proxy-server=
"socks://localhost:
9050" \
639 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
641 chmod a+rx run-signal-app
644 <p
>As usual, if you use Bitcoin and want to show your support of my
645 activities, please send Bitcoin donations to my address
646 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
651 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
652 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
654 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
655 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
656 system
</a
> provide a practical and easy way to figure out which
657 packages support the hardware in a given machine. The command line
658 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
659 convenient way to list and install packages relevant for the current
660 hardware during system installation, both user space packages and
661 firmware packages. The GUI background daemon on the other hand provide
662 a pop-up proposing to install packages when a new dongle is inserted
663 while using the computer. For example, if you plug in a smart card
664 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
665 that package isn
't already installed, and if you plug in a USB video
666 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
667 cheese is currently missing. This already work just fine.
</p
>
669 <p
>But Isenkram depend on a database mapping from hardware IDs to
670 package names. When I started no such database existed in Debian, so
671 I made my own data set and included it with the isenkram package and
672 made isenkram fetch the latest version of this database from git using
673 http. This way the isenkram users would get updated package proposals
674 as soon as I learned more about hardware related packages.
</p
>
676 <p
>The hardware is identified using modalias strings. The modalias
677 design is from the Linux kernel where most hardware descriptors are
678 made available as a strings that can be matched using filename style
679 globbing. It handle USB, PCI, DMI and a lot of other hardware related
680 identifiers.
</p
>
682 <p
>The downside to the Isenkram specific database is that there is no
683 information about relevant distribution / Debian version, making
684 isenkram propose obsolete packages too. But along came AppStream, a
685 cross distribution mechanism to store and collect metadata about
686 software packages. When I heard about the proposal, I contacted the
687 people involved and suggested to add a hardware matching rule using
688 modalias strings in the specification, to be able to use AppStream for
689 mapping hardware to packages. This idea was accepted and AppStream is
690 now a great way for a package to announce the hardware it support in a
691 distribution neutral way. I wrote
692 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
693 recipe on how to add such meta-information
</a
> in a blog post last
694 December. If you have a hardware related package in Debian, please
695 announce the relevant hardware IDs using AppStream.
</p
>
697 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
698 RCX or NXT unit, announce this support using AppStream. The effect is
699 that when you insert such LEGO robot controller into your Debian
700 machine, Isenkram will propose to install the packages needed to get
701 it working. The intention is that this should allow the local user to
702 start programming his robot controller right away without having to
703 guess what packages to use or which permissions to fix.
</p
>
705 <p
>But when I sat down with my son the other day to program our NXT
706 unit using his Debian Stretch computer, I discovered something
707 annoying. The local console user (ie my son) did not get access to
708 the USB device for programming the unit. This used to work, but no
709 longer in Jessie and Stretch. After some investigation and asking
710 around on #debian-devel, I discovered that this was because udev had
711 changed the mechanism used to grant access to local devices. The
712 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
713 no longer applied, because LDAP users no longer was added to the
714 plugdev group during login. Michael Biebl told me that this method
715 was obsolete and the new method used ACLs instead. This was good
716 news, as the plugdev mechanism is a mess when using a remote user
717 directory like LDAP. Using ACLs would make sure a user lost device
718 access when she logged out, even if the user left behind a background
719 process which would retain the plugdev membership with the ConsoleKit
720 setup. Armed with this knowledge I moved on to fix the access problem
721 for the LEGO Mindstorms related packages.
</p
>
723 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
724 applied directly for a device, or is applied in
725 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
726 LEGO Mindstorms udev rules did not have a class, I decided to add the
727 tag directly in the udev rules files included in the packages. Here
728 is one example. For the nqc C compiler for the RCX, the
729 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
732 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
733 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
734 </pre
></p
>
736 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
737 packages using plugdev in their /lib/udev/rules.d/ files should be
738 changed to use this tag (either directly or indirectly via
739 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
740 to detect this?
</p
>
742 <p
>I
've been unable to find good documentation on the uaccess feature.
743 It is unclear to me if the uaccess tag is an internal implementation
744 detail like the udev-acl tag used by
745 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
746 indirect method is the preferred way. Michael
747 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
748 documentation from the systemd project
</a
> and I hope it will make
749 this clearer. For now I use the generic classes when they exist and
750 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
751 directly if no such class exist.
</p
>
753 <p
>To learn more about the isenkram system, please check out
754 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
755 blog posts tagged isenkram
</a
>.
</p
>
757 <p
>To help out making life for LEGO constructors in Debian easier,
758 please join us on our IRC channel
759 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
760 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
761 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
762 list is not yet created, but we are working on it. :)
</p
>
764 <p
>As usual, if you use Bitcoin and want to show your support of my
765 activities, please send Bitcoin donations to my address
766 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
771 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
772 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
773 <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>
774 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
775 <description><p
>In April we
776 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
777 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
778 how to set up and administrate a Debian system. Today I am happy to
779 report that the first draft is now publicly available. You can find
780 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
781 Administrator
's Handbook page
</a
> (under Other languages). The first
782 eight chapters have a first draft translation, and we are working on
783 proofreading the content. If you want to help out, please start
785 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
786 hosted weblate project page
</a
>, and get in touch using
787 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
788 translators mailing list
</a
>. Please also check out
789 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
790 contributors
</a
>. A good way to contribute is to proofread the text
791 and update weblate if you find errors.
</p
>
793 <p
>Our goal is still to make the Norwegian book available on paper as well as
794 electronic form.
</p
>
799 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
800 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
801 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
802 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
803 <description><p
>This summer, I read a great article
804 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
805 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
806 how to profile multi-threaded programs. It presented a system for
807 profiling software by running experiences in the running program,
808 testing how run time performance is affected by
"speeding up
" parts of
809 the code to various degrees compared to a normal run. It does this by
810 slowing down parallel threads while the
"faster up
" code is running
811 and measure how this affect processing time. The processing time is
812 measured using probes inserted into the code, either using progress
813 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
814 can also measure unmodified code by measuring complete the program
815 runtime and running the program several times instead.
</p
>
817 <p
>The project and presentation was so inspiring that I would like to
818 get the system into Debian. I
819 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
820 a WNPP request for it
</a
> and contacted upstream to try to make the
821 system ready for Debian by sending patches. The build process need to
822 be changed a bit to avoid running
'git clone
' to get dependencies, and
823 to include the JavaScript web page used to visualize the collected
824 profiling information included in the source package.
825 But I expect that should work out fairly soon.
</p
>
827 <p
>The way the system work is fairly simple. To run an coz experiment
828 on a binary with debug symbols available, start the program like this:
830 <p
><blockquote
><pre
>
831 coz run --- program-to-run
832 </pre
></blockquote
></p
>
834 <p
>This will create a text file profile.coz with the instrumentation
835 information. To show what part of the code affect the performance
836 most, use a web browser and either point it to
837 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
838 or use the copy from git (in the gh-pages branch). Check out this web
839 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
840 profiling more useful you include
&lt;coz.h
&gt; and insert the
841 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
842 code, rebuild and run the profiler. This allow coz to do more
843 targeted experiments.
</p
>
845 <p
>A video published by ACM
846 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
847 Coz profiler
</a
> is available from Youtube. There is also a paper
848 from the
25th Symposium on Operating Systems Principles available
850 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
851 finding code that counts with causal profiling
</a
>.
</p
>
853 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
854 for Coz is available from github. It will only build with clang
856 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
857 feature missing in GCC
</a
>, but I
've submitted
858 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
859 it
</a
> and hope it will be included in the upstream source soon.
</p
>
861 <p
>Please get in touch if you, like me, would like to see this piece
862 of software in Debian. I would very much like some help with the
863 packaging effort, as I lack the in depth knowledge on how to package
864 C++ libraries.
</p
>
869 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
870 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
872 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
873 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
874 to be a slight challenge. Here is the recipe if I ever need to do it
875 again. It all started by me wanting to try the recipe to set up
876 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
877 hardened Android installation
</a
> from the Tor project blog on a
878 device I had access to. It is a old mobile phone with a broken
879 microphone The initial idea had been to just
880 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
881 CyanogenMod on it
</a
>, but did not quite find time to start on it
882 until a few days ago.
</p
>
884 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
885 loader (press volume down and power at the same time), (
2) select
886 'fastboot
' before (
3) connecting the device via USB to a Linux
887 machine, (
4) request the device identifier token by running
'fastboot
888 oem get_identifier_token
', (
5) request the device unlocking key using
889 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
890 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
892 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
893 or newer, and the device I was working on had
2.00.0027. This
894 apparently can be easily fixed by downloading a Windows program and
895 running it on your Windows machine, if you accept the terms Microsoft
896 require you to accept to use Windows - which I do not. So I had to
897 come up with a different approach. I got a lot of help from AndyCap
898 on #nuug, and would not have been able to get this working without
901 <p
>First I needed to extract the hboot firmware from
902 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
903 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
904 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
905 project named unruu
</a
> using libunshield. The unshield tool did not
906 recognise the file format, but unruu worked and extracted rom.zip,
907 containing the new hboot firmware and a text file describing which
908 devices it would work for.
</p
>
910 <p
>Next, I needed to get the new firmware into the device. For this I
911 followed some instructions
912 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
913 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
914 machine with Debian testing:
</p
>
917 adb reboot-bootloader
918 fastboot oem rebootRUU
919 fastboot flash zip rom.zip
920 fastboot flash zip rom.zip
922 </pre
></p
>
924 <p
>The flash command apparently need to be done twice to take effect,
925 as the first is just preparations and the second one do the flashing.
926 The adb command is just to get to the boot loader menu, so turning the
927 device on while holding volume down and the power button should work
930 <p
>With the new hboot version in place I could start following the
931 instructions on the HTC developer web site. I got the device token
935 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
938 <p
>And once I got the unlock code via email, I could use it like
942 fastboot flash unlocktoken Unlock_code.bin
943 </pre
></p
>
945 <p
>And with that final step in place, the phone was unlocked and I
946 could start stuffing the software of my own choosing into the device.
947 So far I only inserted a replacement recovery image to wipe the phone
948 before I start. We will see what happen next. Perhaps I should
949 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
954 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
955 <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>
956 <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>
957 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
958 <description><p
>For a while now, I have wanted to test
959 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
960 said to provide end to end encrypted communication and several of my
961 friends and family are already using it. As I by choice do not own a
962 mobile phone, this proved to be harder than expected. And I wanted to
963 have the source of the client and know that it was the code used on my
964 machine. But yesterday I managed to get it working. I used the
965 Github source, compared it to the source in
966 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
967 Signal Chrome app
</a
> available from the Chrome web store, applied
968 patches to use the production Signal servers, started the app and
969 asked for the hidden
"register without a smart phone
" form. Here is
970 the recipe how I did it.
</p
>
972 <p
>First, I fetched the Signal desktop source from Github, using
975 git clone https://github.com/WhisperSystems/Signal-Desktop.git
978 <p
>Next, I patched the source to use the production servers, to be
979 able to talk to other Signal users:
</p
>
982 cat
&lt;
&lt;EOF | patch -p0
983 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
984 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
985 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
990 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
991 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
992 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
993 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
995 window.getSocketStatus = function() {
996 if (messageReceiver) {
997 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
998 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
999 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1002 'use strict
';
1003 - var BUILD_EXPIRATION =
0;
1004 + var BUILD_EXPIRATION =
1474492690000;
1006 window.extension = window.extension || {};
1011 <p
>The first part is changing the servers, and the second is updating
1012 an expiration timestamp. This timestamp need to be updated regularly.
1013 It is set
90 days in the future by the build process (Gruntfile.js).
1014 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1016 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1017 script to launch Signal in Chromium.
</p
>
1024 --proxy-server=
"socks://localhost:
9050" \
1025 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1028 <p
> The script start the app and configure Chromium to use the Tor
1029 SOCKS5 proxy to make sure those controlling the Signal servers (today
1030 Amazon and Whisper Systems) as well as those listening on the lines
1031 will have a harder time location my laptop based on the Signal
1032 connections if they use source IP address.
</p
>
1034 <p
>When the script starts, one need to follow the instructions under
1035 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1036 repository. I right clicked on the Signal window to get up the
1037 Chromium debugging tool, visited the
'Console
' tab and wrote
1038 'extension.install(
"standalone
")
' on the console prompt to get the
1039 registration form. Then I entered by land line phone number and
1040 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1041 repeated the verification code three times. After entering the number
1042 into the verification code field in the form, I could start using
1043 Signal from my laptop.
1045 <p
>As far as I can tell, The Signal app will leak who is talking to
1046 whom and thus who know who to those controlling the central server,
1047 but such leakage is hard to avoid with a centrally controlled server
1048 setup. It is something to keep in mind when using Signal - the
1049 content of your chats are harder to intercept, but the meta data
1050 exposing your contact network is available to people you do not know.
1051 So better than many options, but not great. And sadly the usage is
1052 connected to my land line, thus allowing those controlling the server
1053 to associate it to my home and person. I would prefer it if only
1054 those I knew could tell who I was on Signal. There are options
1055 avoiding such information leakage, but most of my friends are not
1056 using them, so I am stuck with Signal for now.
</p
>
1061 <title>The new
"best
" multimedia player in Debian?
</title>
1062 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1063 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1064 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1065 <description><p
>When I set out a few weeks ago to figure out
1066 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1067 multimedia player in Debian claimed to support most file formats /
1068 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1069 the various players claimed support for. The range was from
55 to
130
1070 MIME types. I suspect most media formats are supported by all
1071 players, but this is not really reflected in the MimeTypes values in
1072 their desktop files. There are probably also some bogus MIME types
1073 listed, but it is hard to identify which one this is.
</p
>
1075 <p
>Anyway, in the mean time I got in touch with upstream for some of
1076 the players suggesting to add more MIME types to their desktop files,
1077 and decided to spend some time myself improving the situation for my
1078 favorite media player VLC. The fixes for VLC entered Debian unstable
1079 yesterday. The complete list of MIME types can be seen on the
1080 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1081 player MIME type support status
</a
> Debian wiki page.
</p
>
1083 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1084 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1085 kmplayer. I am sure some of the other players desktop files support
1086 several of the formats currently listed as working only with vlc,
1087 toten and parole.
</p
>
1089 <p
>A sad observation is that only
14 MIME types are listed as
1090 supported by all the tested multimedia players in Debian in their
1091 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1092 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1093 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1094 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1095 it sad that video/ogg and video/webm is not supported by all the media
1096 players in Debian. As far as I can tell, all of them can handle both
1102 <title>A program should be able to open its own files on Linux
</title>
1103 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1104 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1105 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1106 <description><p
>Many years ago, when koffice was fresh and with few users, I
1107 decided to test its presentation tool when making the slides for a
1108 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1109 wrote the first draft of the slides, saved the result and went to bed
1110 the day before I would give the talk. The next day I took a plane to
1111 the location where the meeting should take place, and on the plane I
1112 started up koffice again to polish the talk a bit, only to discover
1113 that kpresenter refused to load its own data file. I cursed a bit and
1114 started making the slides again from memory, to have something to
1115 present when I arrived. I tested that the saved files could be
1116 loaded, and the day seemed to be rescued. I continued to polish the
1117 slides until I suddenly discovered that the saved file could no longer
1118 be loaded into kpresenter. In the end I had to rewrite the slides
1119 three times, condensing the content until the talk became shorter and
1120 shorter. After the talk I was able to pinpoint the problem
&ndash;
1121 kpresenter wrote inline images in a way itself could not understand.
1122 Eventually that bug was fixed and kpresenter ended up being a great
1123 program to make slides. The point I
'm trying to make is that we
1124 expect a program to be able to load its own data files, and it is
1125 embarrassing to its developers if it can
't.
</p
>
1127 <p
>Did you ever experience a program failing to load its own data
1128 files from the desktop file browser? It is not a uncommon problem. A
1129 while back I discovered that the screencast recorder
1130 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1131 browser would refuse to open. No video player claimed to understand
1132 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1133 returning the application/ogg MIME type, which no video player I had
1134 installed listed as a MIME type they would understand. I asked for
1135 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1136 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1137 several video players to add video/ogg to their desktop files, to give
1138 the file browser an idea what to do about Ogg Theora files. After a
1139 while, the desktop file browsers in Debian started to handle the
1140 output from gtk-recordmydesktop properly.
</p
>
1142 <p
>But history repeats itself. A few days ago I tested the music
1143 system Rosegarden again, and I discovered that the KDE and xfce file
1144 browsers did not know what to do with the Rosegarden project files
1145 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1146 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1147 included in the next upload. To increase the chance of me remembering
1148 how to fix the problem next time some program fail to load its files
1149 from the file browser, here are some notes on how to fix it.
</p
>
1151 <p
>The file browsers in Debian in general operates on MIME types.
1152 There are two sources for the MIME type of a given file. The output from
1153 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1154 shared MIME type registry (under /usr/share/mime/). The file MIME
1155 type is mapped to programs supporting the MIME type, and this
1156 information is collected from
1157 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1158 desktop files
</a
> available in /usr/share/applications/. If there is
1159 one desktop file claiming support for the MIME type of the file, it is
1160 activated when asking to open a given file. If there are more, one
1161 can normally select which one to use by right-clicking on the file and
1162 selecting the wanted one using
'Open with
' or similar. In general
1163 this work well. But it depend on each program picking a good MIME
1165 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1166 MIME type registered with IANA
</a
>), file and/or the shared MIME
1167 registry recognizing the file and the desktop file to list the MIME
1168 type in its list of supported MIME types.
</p
>
1170 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1171 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1172 Shared MIME database
</a
> look like this:
</p
>
1174 <p
><blockquote
><pre
>
1175 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1176 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1177 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1178 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1179 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1180 &lt;glob pattern=
"*.rg
"/
&gt;
1181 &lt;/mime-type
&gt;
1182 &lt;/mime-info
&gt;
1183 </pre
></blockquote
></p
>
1185 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1186 (it is a gzipped XML file). Note, it is much better to use an
1187 official MIME type registered with IANA than it is to make up ones own
1188 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1190 <p
>The desktop file of the rosegarden program failed to list
1191 audio/x-rosegarden in its list of supported MIME types, causing the
1192 file browsers to have no idea what to do with *.rg files:
</p
>
1194 <p
><blockquote
><pre
>
1195 % grep Mime /usr/share/applications/rosegarden.desktop
1196 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1197 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1199 </pre
></blockquote
></p
>
1201 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1202 MimeType= line.
</p
>
1204 <p
>If you run into a file which fail to open the correct program when
1205 selected from the file browser, please check out the output from
1206 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1207 MIME type is registered somewhere under /usr/share/mime/ and check
1208 that some desktop file under /usr/share/applications/ is claiming
1209 support for this MIME type. If not, please report a bug to have it
1215 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1216 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1217 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1218 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1219 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1220 system
</a
> is a user-focused solution in Debian for handling hardware
1221 related packages. The idea is to have a database of mappings between
1222 hardware and packages, and pop up a dialog suggesting for the user to
1223 install the packages to use a given hardware dongle. Some use cases
1224 are when you insert a Yubikey, it proposes to install the software
1225 needed to control it; when you insert a braille reader list it
1226 proposes to install the packages needed to send text to the reader;
1227 and when you insert a ColorHug screen calibrator it suggests to
1228 install the driver for it. The system work well, and even have a few
1229 command line tools to install firmware packages and packages for the
1230 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1232 <p
>The system was initially written using aptdaemon, because I found
1233 good documentation and example code on how to use it. But aptdaemon
1234 is going away and is generally being replaced by
1235 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1236 so Isenkram needed a rewrite. And today, thanks to the great patch
1237 from my college Sunil Mohan Adapa in the FreedomBox project, the
1238 rewrite finally took place. I
've just uploaded a new version of
1239 Isenkram into Debian Unstable with the patch included, and the default
1240 for the background daemon is now to use PackageKit. To check it out,
1241 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1242 and see if it is recognised.
</p
>
1244 <p
>If you want to know what kind of packages isenkram would propose for
1245 the machine it is running on, you can check out the isenkram-lookup
1246 program. This is what it look like on a Thinkpad X230:
</p
>
1248 <p
><blockquote
><pre
>
1264 </pre
></blockquote
></p
>
1266 <p
>The hardware mappings come from several places. The preferred way
1267 is for packages to announce their hardware support using
1268 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1269 cross distribution appstream system
</a
>.
1271 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1272 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1277 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1278 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1279 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1280 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1281 <description><p
>Yesterday I updated the
1282 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1283 package in Debian
</a
> with a few patches sent to me by skilled and
1284 enterprising users. There were some nice user and visible changes.
1285 First of all, both desktop menu entries now work. A design flaw in
1286 one of the script made the history graph fail to show up (its PNG was
1287 dumped in ~/.xsession-errors) if no controlling TTY was available.
1288 The script worked when called from the command line, but not when
1289 called from the desktop menu. I changed this to look for a DISPLAY
1290 variable or a TTY before deciding where to draw the graph, and now the
1291 graph window pop up as expected.
</p
>
1293 <p
>The next new feature is a discharge rate estimator in one of the
1294 graphs (the one showing the last few hours). New is also the user of
1295 colours showing charging in blue and discharge in red. The percentages
1296 of this graph is relative to last full charge, not battery design
1299 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1301 <p
>The other graph show the entire history of the collected battery
1302 statistics, comparing it to the design capacity of the battery to
1303 visualise how the battery life time get shorter over time. The red
1304 line in this graph is what the previous graph considers
100 percent:
1306 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1308 <p
>In this graph you can see that I only charge the battery to
80
1309 percent of last full capacity, and how the capacity of the battery is
1310 shrinking. :(
</p
>
1312 <p
>The last new feature is in the collector, which now will handle
1313 more hardware models. On some hardware, Linux power supply
1314 information is stored in /sys/class/power_supply/ACAD/, while the
1315 collector previously only looked in /sys/class/power_supply/AC/. Now
1316 both are checked to figure if there is power connected to the
1319 <p
>If you are interested in how your laptop battery is doing, please
1321 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1322 in Debian unstable, or rebuild it on Jessie to get it working on
1323 Debian stable. :) The upstream source is available from
<a
1324 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1325 Patches are very welcome.
</p
>
1327 <p
>As usual, if you use Bitcoin and want to show your support of my
1328 activities, please send Bitcoin donations to my address
1329 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1334 <title>Debian now with ZFS on Linux included
</title>
1335 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1336 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1337 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1338 <description><p
>Today, after many years of hard work from many people,
1339 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1340 Debian. The package status can be seen on
1341 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1342 for zfs-linux
</a
>. and
1343 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1344 team status page
</a
>. If you want to help out, please join us.
1345 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1346 source code
</a
> is available via git on Alioth. It would also be
1347 great if you could help out with
1348 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1349 it is an important piece of the puzzle to get ZFS working.
</p
>
1354 <title>What is the best multimedia player in Debian?
</title>
1355 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1356 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1357 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1358 <description><p
><strong
>Where I set out to figure out which multimedia player in
1359 Debian claim support for most file formats.
</strong
></p
>
1361 <p
>A few years ago, I had a look at the media support for Browser
1362 plugins in Debian, to get an idea which plugins to include in Debian
1363 Edu. I created a script to extract the set of supported MIME types
1364 for each plugin, and used this to find out which multimedia browser
1365 plugin supported most file formats / media types.
1366 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1367 result
</a
> can still be seen on the Debian wiki, even though it have
1368 not been updated for a while. But browser plugins are less relevant
1369 these days, so I thought it was time to look at standalone
1372 <p
>A few days ago I was tired of VLC not being listed as a viable
1373 player when I wanted to play videos from the Norwegian National
1374 Broadcasting Company, and decided to investigate why. The cause is a
1375 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1376 desktop file
</a
>. In the process I wrote a script to compare the set
1377 of MIME types announced in the desktop file and the browser plugin,
1378 only to discover that there is quite a large difference between the
1379 two for VLC. This discovery made me dig up the script I used to
1380 compare browser plugins, and adjust it to compare desktop files
1381 instead, to try to figure out which multimedia player in Debian
1382 support most file formats.
</p
>
1384 <p
>The result can be seen on the Debian Wiki, as
1385 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1386 table listing all MIME types supported by one of the packages included
1387 in the table
</a
>, with the package supporting most MIME types being
1388 listed first in the table.
</p
>
1390 </p
>The best multimedia player in Debian? It is totem, followed by
1391 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1392 kmplayer. Time for the other players to update their announced MIME
1398 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1399 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1400 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1401 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1402 <description>A friend of mine made me aware of
1403 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1404 handheld computer which will be delivered with Debian preinstalled. I
1405 would love to get one of those for my birthday. :)
</p
>
1407 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1408 plugs and many others connectors, and include a full keyboard and a
5"
1409 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1410 day of battery life time, but I have not seen any independent tests
1411 confirming this. The vendor is still collecting preorders, and the
1412 last I heard last night was that
22 more orders were needed before
1413 production started.
</p
>
1415 <p
>As far as I know, this is the first handheld preinstalled with
1416 Debian. Please let me know if you know of any others. Is it the
1417 first computer being sold with Debian preinstalled?
</p
>
1422 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1423 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1424 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1425 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1426 <description><p
>During this weekends
1427 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1428 squashing party and developer gathering
</a
>, we decided to do our part
1429 to make sure there are good books about Debian available in Norwegian
1430 Bokmål, and got in touch with the people behind the
1431 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1432 project
</a
> to get started. If you want to help out, please start
1434 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1435 hosted weblate project page
</a
>, and get in touch using
1436 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1437 translators mailing list
</a
>. Please also check out
1438 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1439 contributors
</a
>.
</p
>
1441 <p
>The book is already available on paper in English, French and
1442 Japanese, and our goal is to get it available on paper in Norwegian
1443 Bokmål too. In addition to the paper edition, there are also EPUB and
1444 Mobi versions available. And there are incomplete translations
1445 available for many more languages.
</p
>
1450 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1451 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1452 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1453 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1454 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1455 packages in Debian, and was quite surprised with what I found. I use
1456 ZFS myself at home, but did not really expect many others to do so.
1457 But I might be wrong.
</p
>
1459 <p
>According to
1460 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1461 results for spl-linux
</a
>, there are
1019 Debian installations, or
1462 0.53% of the population, with the package installed. As far as I know
1463 the only use of the spl-linux package is as a support library for ZFS
1464 on Linux, so I use it here as proxy for measuring the number of ZFS
1465 installation on Linux in Debian. In the kFreeBSD variant of Debian
1466 the ZFS feature is already available, and there
1467 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1468 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1469 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1471 <p
>But even though the Debian project leader Lucas Nussbaum
1472 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1473 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1474 cleared, the package is still not in Debian. The package is again in
1475 the NEW queue. Several uploads have been rejected so far because the
1476 debian/copyright file was incomplete or wrong, but there is no reason
1477 to give up. The current status can be seen on
1478 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1479 team status page
</a
>, and
1480 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1481 source code
</a
> is available on Alioth.
</p
>
1483 <p
>As I want ZFS to be included in next version of Debian to make sure
1484 my home server can function in the future using only official Debian
1485 packages, and the current blocker is to get the debian/copyright file
1486 accepted by the FTP masters in Debian, I decided a while back to try
1487 to help out the team. This was the background for my blog post about
1488 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1489 updating and checking debian/copyright semi-automatically
</a
>, and I
1490 used the techniques I explored there to try to find any errors in the
1491 copyright file. It is not very easy to check every one of the around
1492 2000 files in the source package, but I hope we this time got it
1493 right. If you want to help out, check out the git source and try to
1494 find missing entries in the debian/copyright file.
</p
>
1499 <title>Full battery stats collector is now available in Debian
</title>
1500 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1501 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1502 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1503 <description><p
>Since this morning, the battery-stats package in Debian include an
1504 extended collector that will collect the complete battery history for
1505 later processing and graphing. The original collector store the
1506 battery level as percentage of last full level, while the new
1507 collector also record battery vendor, model, serial number, design
1508 full level, last full level and current battery level. This make it
1509 possible to predict the lifetime of the battery as well as visualise
1510 the energy flow when the battery is charging or discharging.
</p
>
1512 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1513 in the version
0.5.1 package in unstable. Get the new battery level graph
1514 and lifetime prediction by running:
1516 <p
><pre
>
1517 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1518 </pre
></p
>
1520 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1522 <p
>The flow in/out of the battery can be seen by running (no menu
1523 entry yet):
</p
>
1525 <p
><pre
>
1526 /usr/share/battery-stats/battery-stats-graph-flow
1527 </pre
></p
>
1529 <p
>I
'm not quite happy with the way the data is visualised, at least
1530 when there are few data points. The graphs look a bit better with a
1531 few years of data.
</p
>
1533 <p
>A while back one important feature I use in the battery stats
1534 collector broke in Debian. The scripts in
1535 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1536 suspect it happened when Jessie started using systemd, but I do not
1537 know. The issue is reported as
1538 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1539 pm-utils. I managed to work around it by adding an udev rule to call
1540 the collector script every time the power connector is connected and
1541 disconnected. With this fix in place it was finally time to make a
1542 new release of the package, and get it into Debian.
</p
>
1544 <p
>If you are interested in how your laptop battery is doing, please
1546 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1547 in Debian unstable, or rebuild it on Jessie to get it working on
1548 Debian stable. :) The upstream source is available from
1549 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1550 As always, patches are very welcome.
</p
>
1555 <title>Making battery measurements a little easier in Debian
</title>
1556 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1557 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1558 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1559 <description><p
>Back in September, I blogged about
1560 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1561 system I wrote to collect statistics about my laptop battery
</a
>, and
1562 how it showed the decay and death of this battery (now replaced). I
1563 created a simple deb package to handle the collection and graphing,
1564 but did not want to upload it to Debian as there were already
1565 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1566 package in Debian
</a
> that should do the same thing, and I did not see
1567 a point of uploading a competing package when battery-stats could be
1568 fixed instead. I reported a few bugs about its non-function, and
1569 hoped someone would step in and fix it. But no-one did.
</p
>
1571 <p
>I got tired of waiting a few days ago, and took matters in my own
1572 hands. The end result is that I am now the new upstream developer of
1573 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1574 battery-stats in Debian, and the package in Debian unstable is finally
1575 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1576 information provided by the Linux kernel. If you install the
1577 battery-stats package from unstable now, you will be able to get a
1578 graph of the current battery fill level, to get some idea about the
1579 status of the battery. The source package build and work just fine in
1580 Debian testing and stable (and probably oldstable too, but I have not
1581 tested). The default graph you get for that system look like this:
</p
>
1583 <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
>
1585 <p
>My plans for the future is to merge my old scripts into the
1586 battery-stats package, as my old scripts collected a lot more details
1587 about the battery. The scripts are merged into the upstream
1588 battery-stats git repository already, but I am not convinced they work
1589 yet, as I changed a lot of paths along the way. Will have to test a
1590 bit more before I make a new release.
</p
>
1592 <p
>I will also consider changing the file format slightly, as I
1593 suspect the way I combine several values into one field might make it
1594 impossible to know the type of the value when using it for processing
1595 and graphing.
</p
>
1597 <p
>If you would like I would like to keep an close eye on your laptop
1598 battery, check out the battery-stats package in
1599 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1601 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1602 I would love some help to improve the system further.
</p
>
1607 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1608 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1609 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1610 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1611 <description><p
>Making packages for Debian requires quite a lot of attention to
1612 details. And one of the details is the content of the
1613 debian/copyright file, which should list all relevant licenses used by
1614 the code in the package in question, preferably in
1615 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1616 readable DEP5 format
</a
>.
</p
>
1618 <p
>For large packages with lots of contributors it is hard to write
1619 and update this file manually, and if you get some detail wrong, the
1620 package is normally rejected by the ftpmasters. So getting it right
1621 the first time around get the package into Debian faster, and save
1622 both you and the ftpmasters some work.. Today, while trying to figure
1623 out what was wrong with
1624 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1625 zfsonlinux copyright file
</a
>, I decided to spend some time on
1626 figuring out the options for doing this job automatically, or at least
1627 semi-automatically.
</p
>
1629 <p
>Lucikly, there are at least two tools available for generating the
1630 file based on the code in the source package,
1631 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1632 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1633 not sure which one of them came first, but both seem to be able to
1634 create a sensible draft file. As far as I can tell, none of them can
1635 be trusted to get the result just right, so the content need to be
1636 polished a bit before the file is OK to upload. I found the debmake
1638 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1639 blog posts from
2014</a
>.
1641 <p
>To generate using debmake, use the -cc option:
1643 <p
><pre
>
1644 debmake -cc
> debian/copyright
1645 </pre
></p
>
1647 <p
>Note there are some problems with python and non-ASCII names, so
1648 this might not be the best option.
</p
>
1650 <p
>The cme option is based on a config parsing library, and I found
1652 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1653 blog post from
2015</a
>. To generate using cme, use the
'update
1654 dpkg-copyright
' option:
1656 <p
><pre
>
1657 cme update dpkg-copyright
1658 </pre
></p
>
1660 <p
>This will create or update debian/copyright. The cme tool seem to
1661 handle UTF-
8 names better than debmake.
</p
>
1663 <p
>When the copyright file is created, I would also like some help to
1664 check if the file is correct. For this I found two good options,
1665 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1666 to focus on license types and file matching, and is able to detect
1667 ineffective blocks in the copyright file. The latter reports missing
1668 copyright holders and years, but was confused by inconsistent license
1669 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1670 fix all issues reported by them before uploading. But I do not know
1671 if the tools and the ftpmasters agree on what is important to fix in a
1672 copyright file, so the package might still be rejected.
</p
>
1674 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1675 will read through the source and try to find all copyright statements.
1676 It is not comparing the result to the content of debian/copyright, but
1677 can be useful when verifying the content of the copyright file.
</p
>
1679 <p
>Are you aware of better tools in Debian to create and update
1680 debian/copyright file. Please let me know, or blog about it on
1681 planet.debian.org.
</p
>
1683 <p
>As usual, if you use Bitcoin and want to show your support of my
1684 activities, please send Bitcoin donations to my address
1685 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1687 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1688 on how to use licensecheck and cdbs to create a draft copyright file
1690 <p
><pre
>
1691 licensecheck --copyright -r `find * -type f` | \
1692 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1693 </pre
></p
>
1695 <p
>He mentioned that he normally check the generated file into the
1696 version control system to make it easier to discover license and
1697 copyright changes in the upstream source. I will try to do the same
1698 with my packages in the future.
</p
>
1700 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1701 against using -quiet for new users, so I removed it from the proposed
1702 command line.
</p
>
1707 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1708 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1710 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1711 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1712 is taking shape in Debian, and one provided feature is a very
1713 convenient way to tell you which package to install to make a given
1714 firmware file available when the kernel is looking for it. This can
1715 be done using apt-file too, but that is for someone else to blog
1718 <p
>Here is a small recipe to find the package with a given firmware
1719 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1720 picked from the set of firmware announced using appstream in Debian
1721 unstable. In general you would be looking for the firmware requested
1722 by the kernel during kernel module loading. To find the package
1723 providing the example file, do like this:
</p
>
1725 <blockquote
><pre
>
1726 % apt install appstream
1730 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1731 awk
'/Package:/ {print $
2}
'
1734 </pre
></blockquote
>
1736 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1737 appstream wiki
</a
> page to learn how to embed the package metadata in
1738 a way appstream can use.
</p
>
1740 <p
>This same approach can be used to find any package supporting a
1741 given MIME type. This is very useful when you get a file you do not
1742 know how to handle. First find the mime type using
<tt
>file
1743 --mime-type
</tt
>, and next look up the package providing support for
1744 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1745 and you can find all packages handling this type like this:
</p
>
1747 <blockquote
><pre
>
1748 % apt install appstream
1752 % appstreamcli what-provides mimetype image/svg+xml | \
1753 awk
'/Package:/ {print $
2}
'
1775 </pre
></blockquote
>
1777 <p
>I believe the MIME types are fetched from the desktop file for
1778 packages providing appstream metadata.
</p
>
1783 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1784 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1785 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1786 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1787 <description><p
>Most people seem not to realise that every time they walk around
1788 with the computerised radio beacon known as a mobile phone their
1789 position is tracked by the phone company and often stored for a long
1790 time (like every time a SMS is received or sent). And if their
1791 computerised radio beacon is capable of running programs (often called
1792 mobile apps) downloaded from the Internet, these programs are often
1793 also capable of tracking their location (if the app requested access
1794 during installation). And when these programs send out information to
1795 central collection points, the location is often included, unless
1796 extra care is taken to not send the location. The provided
1797 information is used by several entities, for good and bad (what is
1798 good and bad, depend on your point of view). What is certain, is that
1799 the private sphere and the right to free movement is challenged and
1800 perhaps even eradicated for those announcing their location this way,
1801 when they share their whereabouts with private and public
1804 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1806 <p
>The phone company logs provide a register of locations to check out
1807 when one want to figure out what the tracked person was doing. It is
1808 unavailable for most of us, but provided to selected government
1809 officials, company staff, those illegally buying information from
1810 unfaithful servants and crackers stealing the information. But the
1811 public information can be collected and analysed, and a free software
1812 tool to do so is called
1813 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1814 discovered it when I read
1815 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1816 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1817 November
2014, and decided to check if it was available in Debian.
1818 The python program was in Debian, but
1819 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1820 Debian
</a
> was completely broken and practically unmaintained. I
1821 uploaded a new version which did not work quite right, but did not
1822 have time to fix it then. This Christmas I decided to finally try to
1823 get Creepy operational in Debian. Now a fixed version is available in
1824 Debian unstable and testing, and almost all Debian specific patches
1826 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1828 <p
>The Creepy program visualises geolocation information fetched from
1829 Twitter, Instagram, Flickr and Google+, and allow one to get a
1830 complete picture of every social media message posted recently in a
1831 given area, or track the movement of a given individual across all
1832 these services. Earlier it was possible to use the search API of at
1833 least some of these services without identifying oneself, but these
1834 days it is impossible. This mean that to use Creepy, you need to
1835 configure it to log in as yourself on these services, and provide
1836 information to them about your search interests. This should be taken
1837 into account when using Creepy, as it will also share information
1838 about yourself with the services.
</p
>
1840 <p
>The picture above show the twitter messages sent from (or at least
1841 geotagged with a position from) the city centre of Oslo, the capital
1842 of Norway. One useful way to use Creepy is to first look at
1843 information tagged with an area of interest, and next look at all the
1844 information provided by one or more individuals who was in the area.
1845 I tested it by checking out which celebrity provide their location in
1846 twitter messages by checkout out who sent twitter messages near a
1847 Norwegian TV station, and next could track their position over time,
1848 making it possible to locate their home and work place, among other
1849 things. A similar technique have been
1850 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
1851 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
1852 tool to discover lying governments, and a useful tool to help people
1853 understand the value of the private information they provide to the
1856 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
1857 it depend on several python modules currently missing in Jessie (at
1858 least python-instagram, python-flickrapi and
1859 python-requests-toolbelt).
</p
>
1861 <p
>(I have uploaded
1862 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
1863 screenshots.debian.net
</a
> and licensed it under the same terms as the
1864 Creepy program in Debian.)
</p
>
1869 <title>Always download Debian packages using Tor - the simple recipe
</title>
1870 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
1871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
1872 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
1873 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
1874 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
1875 that those listening on the Internet lines would have good reason to
1876 believe a computer have a given security hole
</a
> if it download a
1877 security fix from a Debian mirror. This is a good reason to always
1878 use encrypted connections to the Debian mirror, to make sure those
1879 listening do not know which IP address to attack. In August, Richard
1880 Hartmann observed that encryption was not enough, when it was possible
1881 to interfere download size to security patches or the fact that
1882 download took place shortly after a security fix was released, and
1883 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
1884 to always use Tor to download packages from the Debian mirror
</a
>. He
1885 was not the first to propose this, as the
1886 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
1887 package by Tim Retout already existed to make it easy to convince apt
1888 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
1889 aware of that package when I read the blog post from Richard.
</p
>
1891 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
1892 sysadmins, and he set up a Tor hidden service on one of the central
1893 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
1894 it possible to download packages directly between two tor nodes,
1895 making sure the network traffic always were encrypted.
</p
>
1897 <p
>Here is a short recipe for enabling this on your machine, by
1898 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
1899 urls with tor+http and tor+https, and using the hidden service instead
1900 of the official Debian mirror site. I recommend installing
1901 <tt
>etckeeper
</tt
> before you start to have a history of the changes
1902 done in /etc/.
</p
>
1904 <blockquote
><pre
>
1905 apt install apt-transport-tor
1906 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
1907 sed -i
's% http% tor+http%
' /etc/apt/sources.list
1908 </pre
></blockquote
>
1910 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
1911 the sed commands for these too. The sed command is assuming your are
1912 using the ftp.debian.org Debian mirror. Adjust the command (or just
1913 edit the file manually) to match your mirror.
</p
>
1915 <p
>This work in Debian Jessie and later. Note that tools like
1916 <tt
>apt-file
</tt
> only recently started using the apt transport
1917 system, and do not work with these tor+http URLs. For
1918 <tt
>apt-file
</tt
> you need the version currently in experimental,
1919 which need a recent apt version currently only in unstable. So if you
1920 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
1922 <p
>Another advantage from this change is that your machine will start
1923 using Tor regularly and at fairly random intervals (every time you
1924 update the package lists or upgrade or install a new package), thus
1925 masking other Tor traffic done from the same machine. Using Tor will
1926 become normal for the machine in question.
</p
>
1928 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
1929 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
1930 enabled. It would be great if it was the default on any Debian
1936 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
1937 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
1938 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
1939 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
1940 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
1941 call the car license plate numbers in those days. I would write the
1942 numbers down in my little book and compare notes with the other kids
1943 to see how many region codes we had seen and if we had seen some
1944 exotic or special region codes and numbers. It was a fun game to pass
1945 time, as we kids have plenty of it.
</p
>
1947 <p
>A few days I came across
1948 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
1949 project
</a
>, a free software project to automatically discover and
1950 report license plates in images and video streams, and provide the
1951 "car numbers
" in a machine readable format. I
've been looking for
1952 such system for a while now, because I believe it is a bad idea that the
1953 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
1954 number plate recognition
</a
> tool only is available in the hands of
1955 the powerful, and want it to be available also for the powerless to
1956 even the score when it comes to surveillance and sousveillance. I
1957 discovered the developer
1958 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
1959 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
1960 help him get it into shape to get the package uploaded into the Debian
1963 <p
>Today we finally managed to get the package into shape and uploaded
1964 it into Debian, where it currently
1965 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
1966 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
1968 <p
>I guess you are wondering why on earth such tool would be useful
1969 for the common folks, ie those not running a large government
1970 surveillance system? Well, I plan to put it in a computer on my bike
1971 and in my car, tracking the cars nearby and allowing me to be notified
1972 when number plates on my watch list are discovered. Another use case
1973 was suggested by a friend of mine, who wanted to set it up at his home
1974 to open the car port automatically when it discovered the plate on his
1975 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1976 capable of placing his license plate number of a piece of cardboard to
1977 open his car port, men replied that it was always unlocked anyway. I
1978 guess for such use case it make sense. I am sure there are other use
1979 cases too, for those with imagination and a vision.
</p
>
1981 <p
>If you want to build your own version of the Debian package, check
1982 out the upstream git source and symlink ./distros/debian to ./debian/
1983 before running
"debuild
" to build the source. Or wait a bit until the
1984 package show up in unstable.
</p
>
1989 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
1990 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
1991 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
1992 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
1993 <description><p
>Around three years ago, I created
1994 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
1995 system
</a
> to get a more practical solution in Debian for handing
1996 hardware related packages. A GUI system in the isenkram package will
1997 present a pop-up dialog when some hardware dongle supported by
1998 relevant packages in Debian is inserted into the machine. The same
1999 lookup mechanism to detect packages is available as command line
2000 tools in the isenkram-cli package. In addition to mapping hardware,
2001 it will also map kernel firmware files to packages and make it easy to
2002 install needed firmware packages automatically. The key for this
2003 system to work is a good way to map hardware to packages, in other
2004 words, allow packages to announce what hardware they will work
2007 <p
>I started by providing data files in the isenkram source, and
2008 adding code to download the latest version of these data files at run
2009 time, to ensure every user had the most up to date mapping available.
2010 I also added support for storing the mapping in the Packages file in
2011 the apt repositories, but did not push this approach because while I
2012 was trying to figure out how to best store hardware/package mappings,
2013 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2014 appstream system
</a
> was announced. I got in touch and suggested to
2015 add the hardware mapping into that data set to be able to use
2016 appstream as a data source, and this was accepted at least for the
2017 Debian version of appstream.
</p
>
2019 <p
>A few days ago using appstream in Debian for this became possible,
2020 and today I uploaded a new version
0.20 of isenkram adding support for
2021 appstream as a data source for mapping hardware to packages. The only
2022 package so far using appstream to announce its hardware support is my
2023 pymissile package. I got help from Matthias Klumpp with figuring out
2024 how do add the required
2025 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2026 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2027 this content:
</p
>
2029 <blockquote
><pre
>
2030 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2031 &lt;component
&gt;
2032 &lt;id
&gt;pymissile
&lt;/id
&gt;
2033 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2034 &lt;name
&gt;pymissile
&lt;/name
&gt;
2035 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2036 &lt;description
&gt;
2038 Pymissile provides a curses interface to control an original
2039 Marks and Spencer / Striker USB Missile Launcher, as well as a
2040 motion control script to allow a webcamera to control the
2043 &lt;/description
&gt;
2044 &lt;provides
&gt;
2045 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2046 &lt;/provides
&gt;
2047 &lt;/component
&gt;
2048 </pre
></blockquote
>
2050 <p
>The key for isenkram is the component/provides/modalias value,
2051 which is a glob style match rule for hardware specific strings
2052 (modalias strings) provided by the Linux kernel. In this case, it
2053 will map to all USB devices with vendor code
1130 and product code
2056 <p
>Note, it is important that the license of all the metadata files
2057 are compatible to have permissions to aggregate them into archive wide
2058 appstream files. Matthias suggested to use MIT or BSD licenses for
2059 these files. A challenge is figuring out a good id for the data, as
2060 it is supposed to be globally unique and shared across distributions
2061 (in other words, best to coordinate with upstream what to use). But
2062 it can be changed later or, so we went with the package name as
2063 upstream for this project is dormant.
</p
>
2065 <p
>To get the metadata file installed in the correct location for the
2066 mirror update scripts to pick it up and include its content the
2067 appstream data source, the file must be installed in the binary
2068 package under /usr/share/appdata/. I did this by adding the following
2069 line to debian/pymissile.install:
</p
>
2071 <blockquote
><pre
>
2072 debian/pymissile.metainfo.xml usr/share/appdata
2073 </pre
></blockquote
>
2075 <p
>With that in place, the command line tool isenkram-lookup will list
2076 all packages useful on the current computer automatically, and the GUI
2077 pop-up handler will propose to install the package not already
2078 installed if a hardware dongle is inserted into the machine in
2081 <p
>Details of the modalias field in appstream is available from the
2082 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2084 <p
>To locate the modalias values of all hardware present in a machine,
2085 try running this command on the command line:
</p
>
2087 <blockquote
><pre
>
2088 cat $(find /sys/devices/|grep modalias)
2089 </pre
></blockquote
>
2091 <p
>To learn more about the isenkram system, please check out
2092 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2093 blog posts tagged isenkram
</a
>.
</p
>
2098 <title>The GNU General Public License is not magic pixie dust
</title>
2099 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2100 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2101 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2102 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2103 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2104 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2105 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2106 I quote the blog post from Paul in full here with his permission:
<p
>
2110 <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
>
2113 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2115 The first step is to choose a
2116 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2119 The next step is, when someone fails to follow that copyleft license,
2120 <b
>it must be enforced
</b
><br/
>
2122 and its a simple fact of our modern society that such type of
2125 is incredibly expensive to do and incredibly difficult to do.
2128 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2129 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2130 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2131 0x57</a
></small
></p
>
2133 <p
>As the Debian Website
2134 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2135 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2136 imply, public domain and permissively licensed software can lead to
2137 the production of more proprietary software as people discover useful
2138 software, extend it and or incorporate it into their hardware or
2139 software products. Copyleft licenses such as the GNU GPL were created
2140 to close off this avenue to the production of proprietary software but
2141 such licenses are not enough. With the ongoing adoption of Free
2142 Software by individuals and groups, inevitably the community
's
2143 expectations of license compliance are violated, usually out of
2144 ignorance of the way Free Software works, but not always. As Karen
2145 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2146 Freedom
">FaiF
</a
>
2147 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2148 copyleft is nothing if no-one is willing and able to stand up in court
2149 to protect it. The reality of today
's world is that legal
2150 representation is expensive, difficult and time consuming. With
2151 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2152 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2153 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2154 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2155 of the Linux project, Debian and other groups against GPL violations.
2156 In March the SFC supported a
2157 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2158 by Christoph Hellwig
</a
> against VMware for refusing to
2159 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2160 with the GPL
</a
> in relation to their use of parts of the Linux
2161 kernel. Since then two of their sponsors pulled corporate funding and
2163 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2164 or cancelled their talks
</a
>. As a result they have decided to rely
2165 less on corporate funding and more on the broad community of
2166 individuals who support Free Software and copyleft. So the SFC has
2167 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2168 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2169 a community of folks who stand up for copyleft and the GPL by
2170 supporting their work on promoting and supporting copyleft and Free
2173 <p
>If you support Free Software,
2174 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2175 what the SFC do, agree with their
2176 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2177 principles
</a
>, are happy about their
2178 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2179 work on a project that is an SFC
2180 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2181 just want to stand up for copyleft, please join
2182 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2183 Allan Webber
</a
>,
2184 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2186 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2187 Bacon
</a
>, myself and
2188 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2190 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2191 next week your donation will be
2192 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2193 by an anonymous donor. Please also consider asking your employer to
2194 match your donation or become a sponsor of SFC. Don
't forget to
2195 spread the word about your support for SFC via email, your blog and or
2196 social media accounts.
</p
>
2200 <p
>I agree with Paul on this topic and just signed up as a Supporter
2201 of Software Freedom Conservancy myself. Perhaps you should be a
2202 supporter too?
</p
>
2207 <title>PGP key transition statement for key EE4E02F9
</title>
2208 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2209 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2210 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2211 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2212 set it up properly. I wanted to generate it offline and have it
2213 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2214 smart card
</a
> for daily use, and learning how to do it and finding
2215 time to sit down with an offline machine almost took forever. But
2216 finally I
've been able to complete the process, and have now moved
2217 from my old GPG key to a new GPG key. See
2218 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2219 full transition statement, signed with both my old and new key
</a
> for
2220 the details. This is my new key:
</p
>
2223 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2224 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2225 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2226 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2227 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2228 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2229 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2232 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2233 my old key.
</p
>
2235 <p
>If you signed my old key
2236 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2237 I
'd very much appreciate a signature on my new key, details and
2238 instructions in the transition statement. I m happy to reciprocate if
2239 you have a similarly signed transition statement to present.
</p
>
2244 <title>The life and death of a laptop battery
</title>
2245 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2246 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2247 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2248 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2249 But this do not last. The last few laptops gave me a feeling that
2250 within a year, the life time is just a fraction of what it used to be,
2251 and it slowly become painful to use the laptop without power connected
2252 all the time. Because of this, when I got a new Thinkpad X230 laptop
2253 about two years ago, I decided to monitor its battery state to have
2254 more hard facts when the battery started to fail.
</p
>
2256 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2258 <p
>First I tried to find a sensible Debian package to record the
2259 battery status, assuming that this must be a problem already handled
2260 by someone else. I found
2261 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2262 which collects statistics from the battery, but it was completely
2263 broken. I sent a few suggestions to the maintainer, but decided to
2264 write my own collector as a shell script while I waited for feedback
2266 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2267 blog post about the battery development on a MacBook Air
</a
> I also
2269 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2270 available in Debian.
</p
>
2272 <p
>I started my collector
2013-
07-
15, and it has been collecting
2273 battery stats ever since. Now my
2274 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2275 measurements, from the time the battery was working great until now,
2276 when it is unable to charge above
7% of original capacity. My
2277 collector shell script is quite simple and look like this:
</p
>
2282 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2284 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2285 logfile=/var/log/hjemmenett-battery-status.log
2287 files=
"manufacturer model_name technology serial_number \
2288 energy_full energy_full_design energy_now cycle_count status
"
2290 if [ ! -e
"$logfile
" ] ; then
2292 printf
"timestamp,
"
2294 printf
"%s,
" $f
2297 )
> "$logfile
"
2301 # Print complete message in one echo call, to avoid race condition
2302 # when several log processes run in parallel.
2303 msg=$(printf
"%s,
" $(date +%s); \
2304 for f in $files; do \
2305 printf
"%s,
" $(cat $f); \
2307 echo
"$msg
"
2310 cd /sys/class/power_supply
2313 (cd $bat
&& log_battery
>> "$logfile
")
2317 <p
>The script is called when the power management system detect a
2318 change in the power status (power plug in or out), and when going into
2319 and out of hibernation and suspend. In addition, it collect a value
2320 every
10 minutes. This make it possible for me know when the battery
2321 is discharging, charging and how the maximum charge change over time.
2322 The code for the Debian package
2323 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2324 available on github
</a
>.
</p
>
2326 <p
>The collected log file look like this:
</p
>
2329 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2330 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2332 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2333 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2336 <p
>I wrote a small script to create a graph of the charge development
2337 over time. This graph depicted above show the slow death of my laptop
2340 <p
>But why is this happening? Why are my laptop batteries always
2341 dying in a year or two, while the batteries of space probes and
2342 satellites keep working year after year. If we are to believe
2343 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2344 University
</a
>, the cause is me charging the battery whenever I have a
2345 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2346 all the time, but to stay below
90% of full charge most of the time.
2347 I
've been told that the Tesla electric cars
2348 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2349 the charge of their batteries to
80%
</a
>, with the option to charge to
2350 100% when preparing for a longer trip (not that I would want a car
2351 like Tesla where rights to privacy is abandoned, but that is another
2352 story), which I guess is the option we should have for laptops on
2353 Linux too.
</p
>
2355 <p
>Is there a good and generic way with Linux to tell the battery to
2356 stop charging at
80%, unless requested to charge to
100% once in
2357 preparation for a longer trip? I found
2358 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2359 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2360 80%
</a
>, but could not get it to work (kernel module refused to
2363 <p
>I wonder why the battery capacity was reported to be more than
100%
2364 at the start. I also wonder why the
"full capacity
" increases some
2365 times, and if it is possible to repeat the process to get the battery
2366 back to design capacity. And I wonder if the discharge and charge
2367 speed change over time, or if this stay the same. I did not yet try
2368 to write a tool to calculate the derivative values of the battery
2369 level, but suspect some interesting insights might be learned from
2372 <p
>Update
2015-
09-
24: I got a tip to install the packages
2373 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2374 packages instead of the tp-smapi-dkms package I had tried to use
2375 initially, and use
'tlp setcharge
40 80' to change when charging start
2376 and stop. I
've done so now, but expect my existing battery is toast
2377 and need to be replaced. The proposal is unfortunately Thinkpad
2383 <title>New laptop - some more clues and ideas based on feedback
</title>
2384 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2385 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2386 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2387 <description><p
>Several people contacted me after my previous blog post about my
2388 need for a new laptop, and provided very useful feedback. I wish to
2389 thank every one of these. Several pointed me to the possibility of
2390 fixing my X230, and I am already in the process of getting Lenovo to
2391 do so thanks to the on site, next day support contract covering the
2392 machine. But the battery is almost useless (I expect to replace it
2393 with a non-official battery) and I do not expect the machine to live
2394 for many more years, so it is time to plan its replacement. If I did
2395 not have a support contract, it was suggested to find replacement parts
2396 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2397 might present a language barrier as I do not understand French.
</p
>
2399 <p
>One tip I got was to use the
2400 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2401 compare laptop models. It seem to have more models available than
2402 prisjakt.no. Another tip I got from someone I know have similar
2403 keyboard preferences was that the HP EliteBook
840 keyboard is not
2404 very good, and this matches my experience with earlier EliteBook
2405 keyboards I tested. Because of this, I will not consider it any further.
2407 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2408 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2409 (which is missing from the X240), and is working fairly well with
2410 Debian Sid/Unstable according to
2411 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2412 got on the keyboard quality are not consistent. Some say the keyboard
2413 is good, others say it is ok, while others say it is not very good.
2414 Those with experience from X41 and and X60 agree that the X250
2415 keyboard is not as good as those trusty old laptops, and suggest I
2416 keep and fix my X230 instead of upgrading, or get a used X230 to
2417 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2418 activity and battery status, which is very convenient on my X230. I
'm
2419 also told that the CPU fan is running very often, making it a bit
2420 noisy. In any case, the X250 do not work out of the box with Debian
2421 Stable/Jessie, one of my requirements.
</p
>
2423 <p
>I have also gotten a few vendor proposals, one was
2424 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2425 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2426 The latter look very attractive to me.
</p
>
2428 <p
>Again, thank you all for the very useful feedback. It help a lot
2429 as I keep looking for a replacement.
</p
>
2431 <p
>Update
2015-
07-
06: I was recommended to check out the
2432 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2434 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2435 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2440 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2441 <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>
2442 <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>
2443 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2444 <description><p
>My primary work horse laptop is failing, and will need a
2445 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2446 started flickering yesterday, and I suspect the cause is a broken
2447 cable, as changing the angle of the screen some times get rid of the
2448 flickering.
</p
>
2450 <p
>My requirements have not really changed since I bought it, and is
2452 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2453 described them in
2013</a
>. The last time I bought a laptop, I had
2455 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2456 where I could select at least a few of the requirements (mouse pin,
2457 wifi, weight) and go through the rest manually. Three button mouse
2458 and a good keyboard is not available as an option, and all the three
2459 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2460 G2) lack three mouse buttons). It is also unclear to me how good the
2461 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2462 the keyboard, even if the quality and robustness in the X series have
2463 deteriorated since X41.
</p
>
2465 <p
>I wonder how I can find a sensible laptop when none of the options
2466 seem sensible to me? Are there better services around to search the
2467 set of available laptops for features? Please send me an email if you
2468 have suggestions.
</p
>
2470 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2471 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2472 of endorsed hardware
</a
>, which is useful background information.
</p
>
2477 <title>How to stay with sysvinit in Debian Jessie
</title>
2478 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2479 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2480 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2481 <description><p
>By now, it is well known that Debian Jessie will not be using
2482 sysvinit as its boot system by default. But how can one keep using
2483 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2485 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2486 Schubert
</a
> and
2487 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2490 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2491 keep sysvinit as your boot system, create a file
2492 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2493 you upgrade:
</p
>
2495 <p
><blockquote
><pre
>
2496 Package: systemd-sysv
2497 Pin: release o=Debian
2499 </pre
></blockquote
><p
>
2501 <p
>This file content will tell apt and aptitude to not consider
2502 installing systemd-sysv as part of any installation and upgrade
2503 solution when resolving dependencies, and thus tell it to avoid
2504 systemd as a default boot system. The end result should be that the
2505 upgraded system keep using sysvinit.
</p
>
2507 <p
>If you are installing Jessie for the first time, there is no way to
2508 get sysvinit installed by default (debootstrap used by
2509 debian-installer have no option for this), but one can tell the
2510 installer to switch to sysvinit before the first boot. Either by
2511 using a kernel argument to the installer, or by adding a line to the
2512 preseed file used. First, the kernel command line argument:
2514 <p
><blockquote
><pre
>
2515 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2516 </pre
></blockquote
><p
>
2518 <p
>Next, the line to use in a preseed file:
</p
>
2520 <p
><blockquote
><pre
>
2521 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2522 </pre
></blockquote
><p
>
2524 <p
>One can of course also do this after the first boot by installing
2525 the sysvinit-core package.
</p
>
2527 <p
>I recommend only using sysvinit if you really need it, as the
2528 sysvinit boot sequence in Debian have several hardware specific bugs
2529 on Linux caused by the fact that it is unpredictable when hardware
2530 devices show up during boot. But on the other hand, the new default
2531 boot system still have a few rough edges I hope will be fixed before
2532 Jessie is released.
</p
>
2534 <p
>Update
2014-
11-
26: Inspired by
2535 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2536 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2542 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2543 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2545 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2546 <description><p
>The right to communicate with your friends and family in private,
2547 without anyone snooping, is a right every citicen have in a liberal
2548 democracy. But this right is under serious attack these days.
</p
>
2550 <p
>A while back it occurred to me that one way to make the dragnet
2551 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2552 the whisleblower Snowden) more expensive for Internet email,
2553 is to deliver all email using SMTP via Tor. Such SMTP option would be
2554 a nice addition to the FreedomBox project if we could send email
2555 between FreedomBox machines without leaking metadata about the emails
2556 to the people peeking on the wire. I
2557 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2558 this on the FreedomBox project mailing list in October
</a
> and got a
2559 lot of useful feedback and suggestions. It also became obvious to me
2560 that this was not a novel idea, as the same idea was tested and
2561 documented by Johannes Berg as early as
2006, and both
2562 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2563 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2564 propose a similar method / protocol to pass emails between users.
</p
>
2566 <p
>To implement such system one need to set up a Tor hidden service
2567 providing the SMTP protocol on port
25, and use email addresses
2568 looking like username@hidden-service-name.onion. With such addresses
2569 the connections to port
25 on hidden-service-name.onion using Tor will
2570 go to the correct SMTP server. To do this, one need to configure the
2571 Tor daemon to provide the hidden service and the mail server to accept
2572 emails for this .onion domain. To learn more about Exim configuration
2573 in Debian and test the design provided by Johannes Berg in his FAQ, I
2574 set out yesterday to create a Debian package for making it trivial to
2575 set up such SMTP over Tor service based on Debian. Getting it to work
2576 were fairly easy, and
2577 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2578 source code for the Debian package
</a
> is available from github. I
2579 plan to move it into Debian if further testing prove this to be a
2580 useful approach.
</p
>
2582 <p
>If you want to test this, set up a blank Debian machine without any
2583 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2584 get rid of exim4). Install tor, clone the git repository mentioned
2585 above, build the deb and install it on the machine. Next, run
2586 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2587 the instructions to get the service up and running. Restart tor and
2588 exim when it is done, and test mail delivery using swaks like
2591 <p
><blockquote
><pre
>
2592 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2593 --to fbx@dutlqrrmjhtfa3vp.onion
2594 </pre
></blockquote
></p
>
2596 <p
>This will test the SMTP delivery using tor. Replace the email
2597 address with your own address to test your server. :)
</p
>
2599 <p
>The setup procedure is still to complex, and I hope it can be made
2600 easier and more automatic. Especially the tor setup need more work.
2601 Also, the package include a tor-smtp tool written in C, but its task
2602 should probably be rewritten in some script language to make the deb
2603 architecture independent. It would probably also make the code easier
2604 to review. The tor-smtp tool currently need to listen on a socket for
2605 exim to talk to it and is started using xinetd. It would be better if
2606 no daemon and no socket is needed. I suspect it is possible to get
2607 exim to run a command line tool for delivery instead of talking to a
2608 socket, and hope to figure out how in a future version of this
2611 <p
>Until I wipe my test machine, I can be reached using the
2612 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2613 SMTorP. :)
</p
>
2618 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2619 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2620 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2621 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2622 <description><p
>If you ever had to moderate a mailman list, like the ones on
2623 alioth.debian.org, you know the web interface is fairly slow to
2624 operate. First you visit one web page, enter the moderation password
2625 and get a new page shown with a list of all the messages to moderate
2626 and various options for each email address. This take a while for
2627 every list you moderate, and you need to do it regularly to do a good
2628 job as a list moderator. But there is a quick alternative,
2629 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2630 listadmin program
</a
>. It allow you to check lists for new messages
2631 to moderate in a fraction of a second. Here is a test run on two
2632 lists I recently took over:
</p
>
2634 <p
><blockquote
><pre
>
2635 % time listadmin xiph
2636 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2637 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2643 </pre
></blockquote
></p
>
2645 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2646 there are no message in the moderation queue. Every morning I
2647 currently moderate
68 mailman lists, and it normally take around two
2648 minutes. When I took over the two pkg-xiph lists above a few days
2649 ago, there were
400 emails waiting in the moderator queue. It took me
2650 less than
15 minutes to process them all using the listadmin
2653 <p
>If you install
2654 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2655 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2656 with content like this, the moderation task is a breeze:
</p
>
2658 <p
><blockquote
><pre
>
2659 username username@example.org
2662 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2665 adminurl https://{domain}/mailman/admindb/{list}
2666 mailman-list@lists.example.com
2669 other-list@otherserver.example.org
2670 </pre
></blockquote
></p
>
2672 <p
>There are other options to set as well. Check the manual page to
2673 learn the details.
</p
>
2675 <p
>If you are forced to moderate lists on a mailman installation where
2676 the SSL certificate is self signed or not properly signed by a
2677 generally accepted signing authority, you can set a environment
2678 variable when calling listadmin to disable SSL verification:
</p
>
2680 <p
><blockquote
><pre
>
2681 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2682 </pre
></blockquote
></p
>
2684 <p
>If you want to moderate a subset of the lists you take care of, you
2685 can provide an argument to the listadmin script like I do in the
2686 initial screen dump (the xiph argument). Using an argument, only
2687 lists matching the argument string will be processed. This make it
2688 quick to accept messages if you notice the moderation request in your
2691 <p
>Without the listadmin program, I would never be the moderator of
68
2692 mailing lists, as I simply do not have time to spend on that if the
2693 process was any slower. The listadmin program have saved me hours of
2694 time I could spend elsewhere over the years. It truly is nice free
2697 <p
>As usual, if you use Bitcoin and want to show your support of my
2698 activities, please send Bitcoin donations to my address
2699 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2701 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2702 configuration example. Also, I
've been told that the
2703 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2709 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2710 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2711 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2712 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2713 <description><p
>When PXE installing laptops with Debian, I often run into the
2714 problem that the WiFi card require some firmware to work properly.
2715 And it has been a pain to fix this using preseeding in Debian.
2716 Normally something more is needed. But thanks to
2717 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2718 package
</a
> and its recent tasksel extension, it has now become easy
2719 to do this using simple preseeding.
</p
>
2721 <p
>The isenkram-cli package provide tasksel tasks which will install
2722 firmware for the hardware found in the machine (actually, requested by
2723 the kernel modules for the hardware). (It can also install user space
2724 programs supporting the hardware detected, but that is not the focus
2725 of this story.)
</p
>
2727 <p
>To get this working in the default installation, two preeseding
2728 values are needed. First, the isenkram-cli package must be installed
2729 into the target chroot (aka the hard drive) before tasksel is executed
2730 in the pkgsel step of the debian-installer system. This is done by
2731 preseeding the base-installer/includes debconf value to include the
2732 isenkram-cli package. The package name is next passed to debootstrap
2733 for installation. With the isenkram-cli package in place, tasksel
2734 will automatically use the isenkram tasks to detect hardware specific
2735 packages for the machine being installed and install them, because
2736 isenkram-cli contain tasksel tasks.
</p
>
2738 <p
>Second, one need to enable the non-free APT repository, because
2739 most firmware unfortunately is non-free. This is done by preseeding
2740 the apt-mirror-setup step. This is unfortunate, but for a lot of
2741 hardware it is the only option in Debian.
</p
>
2743 <p
>The end result is two lines needed in your preseeding file to get
2744 firmware installed automatically by the installer:
</p
>
2746 <p
><blockquote
><pre
>
2747 base-installer base-installer/includes string isenkram-cli
2748 apt-mirror-setup apt-setup/non-free boolean true
2749 </pre
></blockquote
></p
>
2751 <p
>The current version of isenkram-cli in testing/jessie will install
2752 both firmware and user space packages when using this method. It also
2753 do not work well, so use version
0.15 or later. Installing both
2754 firmware and user space packages might give you a bit more than you
2755 want, so I decided to split the tasksel task in two, one for firmware
2756 and one for user space programs. The firmware task is enabled by
2757 default, while the one for user space programs is not. This split is
2758 implemented in the package currently in unstable.
</p
>
2760 <p
>If you decide to give this a go, please let me know (via email) how
2761 this recipe work for you. :)
</p
>
2763 <p
>So, I bet you are wondering, how can this work. First and
2764 foremost, it work because tasksel is modular, and driven by whatever
2765 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2766 isenkram-cli package place two files for tasksel to find. First there
2767 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2769 <p
><blockquote
><pre
>
2770 Task: isenkram-packages
2772 Description: Hardware specific packages (autodetected by isenkram)
2773 Based on the detected hardware various hardware specific packages are
2775 Test-new-install: show show
2777 Packages: for-current-hardware
2779 Task: isenkram-firmware
2781 Description: Hardware specific firmware packages (autodetected by isenkram)
2782 Based on the detected hardware various hardware specific firmware
2783 packages are proposed.
2784 Test-new-install: mark show
2786 Packages: for-current-hardware-firmware
2787 </pre
></blockquote
></p
>
2789 <p
>The key parts are Test-new-install which indicate how the task
2790 should be handled and the Packages line referencing to a script in
2791 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2792 list of packages to install. The for-current-hardware-firmware script
2793 look like this to list relevant firmware for the machine:
2795 <p
><blockquote
><pre
>
2798 PATH=/usr/sbin:$PATH
2800 isenkram-autoinstall-firmware -l
2801 </pre
></blockquote
></p
>
2803 <p
>With those two pieces in place, the firmware is installed by
2804 tasksel during the normal d-i run. :)
</p
>
2806 <p
>If you want to test what tasksel will install when isenkram-cli is
2807 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2808 --new-install
</tt
> to get the list of packages that tasksel would
2811 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2812 pilots in testing this feature, as isenkram is used there now to
2813 install firmware, replacing the earlier scripts.
</p
>
2818 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2819 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2820 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2821 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2822 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2823 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2824 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2825 on a screen normally showing the bread types and prizes:
</p
>
2827 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2829 <p
>If it had booted as it was supposed to, I would never had known
2830 about this hidden Linux installation. It is interesting what
2831 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2836 <title>New lsdvd release version
0.17 is ready
</title>
2837 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2838 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2839 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2840 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
2841 got a new set of developers a few weeks ago, after the original
2842 developer decided to step down and pass the project to fresh blood.
2843 This project is now maintained by Petter Reinholdtsen and Steve
2846 <p
>I just wrapped up
2847 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
2848 new lsdvd release
</a
>, available in git or from
2849 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
2850 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
2855 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
2856 <li
>Check for garbage in the program chains, which indicate that a track is
2857 non-existant, to work around additional copy protection
</li
>
2858 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
2859 <li
>Fix pallete display of first entry
</li
>
2860 <li
>Fix include orders
</li
>
2861 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
2862 <li
>Fix the chapter count
</li
>
2863 <li
>Make sure the array size and the array limit used when initialising
2864 the palette size is the same.
</li
>
2865 <li
>Fix array printing.
</li
>
2866 <li
>Correct subsecond calculations.
</li
>
2867 <li
>Add sector information to the output format.
</li
>
2868 <li
>Clean up code to be closer to ANSI C and compile without warnings
2869 with more GCC compiler warnings.
</li
>
2873 <p
>This change bring together patches for lsdvd in use in various
2874 Linux and Unix distributions, as well as patches submitted to the
2875 project the last nine years. Please check it out. :)
</p
>
2880 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
2881 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
2882 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
2883 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
2884 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
2885 project
</a
> provide a Linux solution for schools, including a
2886 powerful desktop with education software, a central server providing
2887 web pages, user database, user home directories, central login and PXE
2888 boot of both clients without disk and the installation to install Debian
2889 Edu on machines with disk (and a few other services perhaps to small
2890 to mention here). We in the Debian Edu team are currently working on
2891 the Jessie based version, trying to get everything in shape before the
2892 freeze, to avoid having to maintain our own package repository in the
2894 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
2895 status
</a
> can be seen on the Debian wiki, and there is still heaps of
2896 work left. Some fatal problems block testing, breaking the installer,
2897 but it is possible to work around these to get anyway. Here is a
2898 recipe on how to get the installation limping along.
</p
>
2900 <p
>First, download the test ISO via
2901 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
2902 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
2904 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
2905 The ISO build was broken on Tuesday, so we do not get a new ISO every
2906 12 hours or so, but thankfully the ISO we already got we are able to
2907 install with some tweaking.
</p
>
2909 <p
>When you get to the Debian Edu profile question, go to tty2
2910 (use Alt-Ctrl-F2), run
</p
>
2912 <p
><blockquote
><pre
>
2913 nano /usr/bin/edu-eatmydata-install
2914 </pre
></blockquote
></p
>
2916 <p
>and add
'exit
0' as the second line, disabling the eatmydata
2917 optimization. Return to the installation, select the profile you want
2918 and continue. Without this change, exim4-config will fail to install
2919 due to a known bug in eatmydata.
</p
>
2921 <p
>When you get the grub question at the end, answer /dev/sda (or if
2922 this do not work, figure out what your correct value would be. All my
2923 test machines need /dev/sda, so I have no advice if it do not fit
2924 your need.
</p
>
2926 <p
>If you installed a profile including a graphical desktop, log in as
2927 root after the initial boot from hard drive, and install the
2928 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
2929 or mate. If you want several desktop options, install more than one
2930 metapackage. Once this is done, reboot and you should have a working
2931 graphical login screen. This workaround should no longer be needed
2932 once the education-tasks package version
1.801 enter testing in two
2935 <p
>I believe the ISO build will start working on two days when the new
2936 tasksel package enter testing and Steve McIntyre get a chance to
2937 update the debian-cd git repository. The eatmydata, grub and desktop
2938 issues are already fixed in unstable and testing, and should show up
2939 on the ISO as soon as the ISO build start working again. Well the
2940 eatmydata optimization is really just disabled. The proper fix
2941 require an upload by the eatmydata maintainer applying the patch
2942 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
2943 The rest have proper fixes in unstable.
</p
>
2945 <p
>I hope this get you going with the installation testing, as we are
2946 quickly running out of time trying to get our Jessie based
2947 installation ready before the distribution freeze in a month.
</p
>
2952 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
2953 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
2954 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
2955 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
2956 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
2957 to handle my fairly large DVD collection. It is a nice command line
2958 tool to get details about a DVD, like title, tracks, track length,
2959 etc, in XML, Perl or human readable format. But lsdvd have not seen
2960 any new development since
2006 and had a few irritating bugs affecting
2961 its use with some DVDs. Upstream seemed to be dead, and in January I
2962 sent a small probe asking for a version control repository for the
2963 project, without any reply. But I use it regularly and would like to
2964 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
2965 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
2966 the project admin, and after getting a reply from him explaining that
2967 he was no longer interested in the project, I asked if I could take
2968 over. And yesterday, I became project admin.
</p
>
2970 <p
>I
've been in touch with a Gentoo developer and the Debian
2971 maintainer interested in joining forces to maintain the upstream
2972 project, and I hope we can get a new release out fairly quickly,
2973 collecting the patches spread around on the internet into on place.
2974 I
've added the relevant Debian patches to the freshly created git
2975 repository, and expect the Gentoo patches to make it too. If you got
2976 a DVD collection and care about command line tools, check out
2977 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
2978 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
2979 list
</a
>. :)
</p
>
2984 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
2985 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
2986 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
2987 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
2988 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
2989 a lot quicker. When we install more than
2000 packages in
2990 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
2991 tasksel in the installer, unpacking the binary packages take forever.
2992 A part of the slow I/O issue was discussed in
2993 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
2994 much file system sync-ing done by dpkg, which is the package
2995 responsible for unpacking the binary packages. Other parts (like code
2996 executed by postinst scripts) might also sync to disk during
2997 installation. All this sync-ing to disk do not really make sense to
2998 me. If the machine crash half-way through, I start over, I do not try
2999 to salvage the half installed system. So the failure sync-ing is
3000 supposed to protect against, hardware or system crash, is not really
3001 relevant while the installer is running.
</p
>
3003 <p
>A few days ago, I thought of a way to get rid of all the file
3004 system sync()-ing in a fairly non-intrusive way, without the need to
3005 change the code in several packages. The idea is not new, but I have
3006 not heard anyone propose the approach using dpkg-divert before. It
3007 depend on the small and clever package
3008 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3009 uses LD_PRELOAD to replace the system functions for syncing data to
3010 disk with functions doing nothing, thus allowing programs to live
3011 dangerous while speeding up disk I/O significantly. Instead of
3012 modifying the implementation of dpkg, apt and tasksel (which are the
3013 packages responsible for selecting, fetching and installing packages),
3014 it occurred to me that we could just divert the programs away, replace
3015 them with a simple shell wrapper calling
3016 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3017 Two days ago I decided to test the idea, and wrapped up a simple
3018 implementation for the Debian Edu udeb.
</p
>
3020 <p
>The effect was stunning. In my first test it reduced the running
3021 time of the pkgsel step (installing tasks) from
64 to less than
44
3022 minutes (
20 minutes shaved off the installation) on an old Dell
3023 Latitude D505 machine. I am not quite sure what the optimised time
3024 would have been, as I messed up the testing a bit, causing the debconf
3025 priority to get low enough for two questions to pop up during
3026 installation. As soon as I saw the questions I moved the installation
3027 along, but do not know how long the question were holding up the
3028 installation. I did some more measurements using Debian Edu Jessie,
3029 and got these results. The time measured is the time stamp in
3030 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3031 "pkgsel: finishing up
" lines, if you want to do the same measurement
3032 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3033 timing thus do not depend on how quickly the user handle the tasksel
3036 <p
><table
>
3039 <th
>Machine/setup
</th
>
3040 <th
>Original tasksel
</th
>
3041 <th
>Optimised tasksel
</th
>
3042 <th
>Reduction
</th
>
3046 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3047 <td
>64 min (
07:
46-
08:
50)
</td
>
3048 <td
><44 min (
11:
27-
12:
11)
</td
>
3049 <td
>>20 min
18%
</td
>
3053 <td
>Latitude D505 Roaming LXDE
</td
>
3054 <td
>57 min (
08:
48-
09:
45)
</td
>
3055 <td
>34 min (
07:
43-
08:
17)
</td
>
3056 <td
>23 min
40%
</td
>
3060 <td
>Latitude D505 Minimal
</td
>
3061 <td
>22 min (
10:
37-
10:
59)
</td
>
3062 <td
>11 min (
11:
16-
11:
27)
</td
>
3063 <td
>11 min
50%
</td
>
3067 <td
>Thinkpad X200 Minimal
</td
>
3068 <td
>6 min (
08:
19-
08:
25)
</td
>
3069 <td
>4 min (
08:
04-
08:
08)
</td
>
3070 <td
>2 min
33%
</td
>
3074 <td
>Thinkpad X200 Roaming KDE
</td
>
3075 <td
>19 min (
09:
21-
09:
40)
</td
>
3076 <td
>15 min (
10:
25-
10:
40)
</td
>
3077 <td
>4 min
21%
</td
>
3080 </table
></p
>
3082 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3083 time is spent downloading packages. The connection to the Internet
3084 was
100Mbit/s during testing, so downloading should not be a
3085 significant factor in the measurement. Download typically took a few
3086 seconds to a few minutes, depending on the amount of packages being
3087 installed.
</p
>
3089 <p
>The speedup is implemented by using two hooks in
3090 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3091 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3092 finish-install.d hook to remove the divert at the end of the
3093 installation. I picked the pre-pkgsel.d hook instead of the
3094 post-base-installer.d hook because I test using an ISO without the
3095 eatmydata package included, and the post-base-installer.d hook in
3096 Debian Edu can only operate on packages included in the ISO. The
3097 negative effect of this is that I am unable to activate this
3098 optimization for the kernel installation step in d-i. If the code is
3099 moved to the post-base-installer.d hook, the speedup would be larger
3100 for the entire installation.
</p
>
3102 <p
>I
've implemented this in the
3103 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3104 git repository, and plan to provide the optimization as part of the
3105 Debian Edu installation. If you want to test this yourself, you can
3106 create two files in the installer (or in an udeb). One shell script
3107 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3109 <p
><blockquote
><pre
>
3112 . /usr/share/debconf/confmodule
3114 logger -t my-pkgsel
"info: $*
"
3117 logger -t my-pkgsel
"error: $*
"
3119 override_install() {
3120 apt-install eatmydata || true
3121 if [ -x /target/usr/bin/eatmydata ] ; then
3122 for bin in dpkg apt-get aptitude tasksel ; do
3124 # Test that the file exist and have not been diverted already.
3125 if [ -f /target$file ] ; then
3126 info
"diverting $file using eatmydata
"
3127 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3128 > /target$file.edu
3129 chmod
755 /target$file.edu
3130 in-target dpkg-divert --package debian-edu-config \
3131 --rename --quiet --add $file
3132 ln -sf ./$bin.edu /target$file
3134 error
"unable to divert $file, as it is missing.
"
3138 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3143 </pre
></blockquote
></p
>
3145 <p
>To clean up, another shell script should go into
3146 /usr/lib/finish-install.d/ with code like this:
3148 <p
><blockquote
><pre
>
3150 . /usr/share/debconf/confmodule
3152 logger -t my-finish-install
"error: $@
"
3154 remove_install_override() {
3155 for bin in dpkg apt-get aptitude tasksel ; do
3157 if [ -x /target$file.edu ] ; then
3159 in-target dpkg-divert --package debian-edu-config \
3160 --rename --quiet --remove $file
3163 error
"Missing divert for $file.
"
3166 sync # Flush file buffers before continuing
3169 remove_install_override
3170 </pre
></blockquote
></p
>
3172 <p
>In Debian Edu, I placed both code fragments in a separate script
3173 edu-eatmydata-install and call it from the pre-pkgsel.d and
3174 finish-install.d scripts.
</p
>
3176 <p
>By now you might ask if this change should get into the normal
3177 Debian installer too? I suspect it should, but am not sure the
3178 current debian-installer coordinators find it useful enough. It also
3179 depend on the side effects of the change. I
'm not aware of any, but I
3180 guess we will see if the change is safe after some more testing.
3181 Perhaps there is some package in Debian depending on sync() and
3182 fsync() having effect? Perhaps it should go into its own udeb, to
3183 allow those of us wanting to enable it to do so without affecting
3186 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3187 will break installation of all programs using gnutls because of
3188 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3189 eatmydata package in Debian will solve it.
</p
>
3191 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3192 the optimization work again. And I have discovered that the
3193 dpkg-divert trick is not really needed and implemented a slightly
3194 simpler approach as part of the debian-edu-install package. See
3195 tools/edu-eatmydata-install in the source package.
</p
>
3197 <p
>Update
2014-
11-
11: Unfortunately, a new
3198 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3199 triggering on i386 made it into testing, and broke this installation
3200 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3201 request
768893</a
> is accepted, it should be working again.
</p
>
3206 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3207 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3208 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3209 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3210 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3211 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3212 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3213 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3214 learn that there is a large set of publicly available key servers to
3215 use when looking for peoples public key. So far I have used
3216 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3217 were misbehaving, but those days are ended. The servers I have used
3218 up until yesterday have been slow and some times unavailable. I hope
3219 those problems are gone now.
</p
>
3221 <p
>Behind the round robin DNS entry of the
3222 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3223 there is a pool of more than
100 keyservers which are checked every
3224 day to ensure they are well connected and up to date. It must be
3225 better than what I have used so far. :)
</p
>
3227 <p
>Yesterdays speaker told me that the service is the default
3228 keyserver provided by the default configuration in GnuPG, but this do
3229 not seem to be used in Debian. Perhaps it should?
</p
>
3231 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3234 <p
><blockquote
><pre
>
3235 keyserver pool.sks-keyservers.net
3236 </pre
></blockquote
></p
>
3238 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3239 entries in DNS. Just for fun, I did just that at work, so now every
3240 user of GnuPG at the University of Oslo should find a OpenGPG
3241 keyserver automatically should their need it:
</p
>
3243 <p
><blockquote
><pre
>
3244 % host -t srv _pgpkey-http._tcp.uio.no
3245 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3247 </pre
></blockquote
></p
>
3249 <p
>Now if only
3250 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3251 HKP lookup protocol
</a
> supported finding signature paths, I would be
3252 very happy. It can look up a given key or search for a user ID, but I
3253 normally do not want that, but to find a trust path from my key to
3254 another key. Given a user ID or key ID, I would like to find (and
3255 download) the keys representing a signature path from my key to the
3256 key in question, to be able to get a trust path between the two keys.
3257 This is as far as I can tell not possible today. Perhaps something
3258 for a future version of the protocol?
</p
>
3263 <title>From English wiki to translated PDF and epub via Docbook
</title>
3264 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3265 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3266 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3267 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3268 project
</a
> provide an instruction manual for teachers, system
3269 administrators and other users that contain useful tips for setting up
3270 and maintaining a Debian Edu installation. This text is about how the
3271 text processing of this manual is handled in the project.
</p
>
3273 <p
>One goal of the project is to provide information in the native
3274 language of its users, and for this we need to handle translations.
3275 But we also want to make sure each language contain the same
3276 information, so for this we need a good way to keep the translations
3277 in sync. And we want it to be easy for our users to improve the
3278 documentation, avoiding the need to learn special formats or tools to
3279 contribute, and the obvious way to do this is to make it possible to
3280 edit the documentation using a web browser. We also want it to be
3281 easy for translators to keep the translation up to date, and give them
3282 help in figuring out what need to be translated. Here is the list of
3283 tools and the process we have found trying to reach all these
3286 <p
>We maintain the authoritative source of our manual in the
3287 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3288 wiki
</a
>, as several wiki pages written in English. It consist of one
3289 front page with references to the different chapters, several pages
3290 for each chapter, and finally one
"collection page
" gluing all the
3291 chapters together into one large web page (aka
3292 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3293 AllInOne page
</a
>). The AllInOne page is the one used for further
3294 processing and translations. Thanks to the fact that the
3295 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3296 wiki.debian.org support exporting pages in
3297 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3298 the list of pages to export using the raw version of the AllInOne
3299 page, loop over each of them to generate a Docbook XML version of the
3300 manual. This process also download images and transform image
3301 references to use the locally downloaded images. The generated
3302 Docbook XML files are slightly broken, so some post-processing is done
3303 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3304 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3305 a handfull of images. The XML file can now be used to generate PDF, HTML
3306 and epub versions of the English manual. This is the basic step of
3307 our process, making PDF (using dblatex), HTML (using xsltproc) and
3308 epub (using dbtoepub) version from Docbook XML, and the resulting files
3309 are placed in the debian-edu-doc-en binary package.
</p
>
3311 <p
>But English documentation is not enough for us. We want translated
3312 documentation too, and we want to make it easy for translators to
3313 track the English original. For this we use the
3314 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3315 which allow us to transform the English Docbook XML file into a
3316 translation file (a .pot file), usable with the normal gettext based
3317 translation tools used by those translating free software. The pot
3318 file is used to create and maintain translation files (several .po
3319 files), which the translations update with the native language
3320 translations of all titles, paragraphs and blocks of text in the
3321 original. The next step is combining the original English Docbook XML
3322 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3323 create a translated Docbook XML file (in this case
3324 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3325 translated, if the translation is not complete) Docbook XML file can
3326 then be used like the original to create a PDF, HTML and epub version
3327 of the documentation.
</p
>
3329 <p
>The translators use different tools to edit the .po files. We
3331 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3332 while some use emacs and vi, others can use web based editors like
3333 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3334 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3335 is where the .po file end up, in our git repository. Updated
3336 translations can either be committed directly to git, or submitted as
3337 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3338 against the debian-edu-doc package
</a
>.
</p
>
3340 <p
>One challenge is images, which both might need to be translated (if
3341 they show translated user applications), and are needed in different
3342 formats when creating PDF and HTML versions (epub is a HTML version in
3343 this regard). For this we transform the original PNG images to the
3344 needed density and format during build, and have a way to provide
3345 translated images by storing translated versions in
3346 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3347 package maintainers know more.
</p
>
3349 <p
>If you wonder what the result look like, we provide
3350 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3351 of the documentation packages on the web
</a
>. See for example the
3352 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3353 PDF version
</a
> or the
3354 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3355 HTML version
</a
>. We do not yet build the epub version by default,
3356 but perhaps it will be done in the future.
</p
>
3358 <p
>To learn more, check out
3359 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3360 debian-edu-doc package
</a
>,
3361 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3362 manual on the wiki
</a
> and
3363 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3364 translation instructions
</a
> in the manual.
</p
>
3369 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3370 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3371 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3372 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3373 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3374 related packages relevant for the computer installed automatically.
3375 So I implemented one, using
3376 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3377 package
</a
>. To use it, install the tasksel and isenkram packages and
3378 run tasksel as user root. You should be presented with a new option,
3379 "Hardware specific packages (autodetected by isenkram)
". When you
3380 select it, tasksel will install the packages isenkram claim is fit for
3381 the current hardware, hot pluggable or not.
<p
>
3383 <p
>The implementation is in two files, one is the tasksel menu entry
3384 description, and the other is the script used to extract the list of
3385 packages to install. The first part is in
3386 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3389 <p
><blockquote
><pre
>
3392 Description: Hardware specific packages (autodetected by isenkram)
3393 Based on the detected hardware various hardware specific packages are
3395 Test-new-install: mark show
3397 Packages: for-current-hardware
3398 </pre
></blockquote
></p
>
3400 <p
>The second part is in
3401 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3404 <p
><blockquote
><pre
>
3409 isenkram-autoinstall-firmware -l
3411 </pre
></blockquote
></p
>
3413 <p
>All in all, a very short and simple implementation making it
3414 trivial to install the hardware dependent package we all may want to
3415 have installed on our machines. I
've not been able to find a way to
3416 get tasksel to tell you exactly which packages it plan to install
3417 before doing the installation. So if you are curious or careful,
3418 check the output from the isenkram-* command line tools first.
</p
>
3420 <p
>The information about which packages are handling which hardware is
3421 fetched either from the isenkram package itself in
3422 /usr/share/isenkram/, from git.debian.org or from the APT package
3423 database (using the Modaliases header). The APT package database
3424 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3425 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3426 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3427 the python-apt code (bug
3428 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3429 workaround I was able to get rid of the file descriptor leak and
3430 reduce the memory leak from ~
30 MiB per hardware detection down to
3431 around
2 MiB per hardware detection. It should make the desktop
3432 daemon a lot more useful. The fix is in version
0.7 uploaded to
3433 unstable today.
</p
>
3435 <p
>I believe the current way of mapping hardware to packages in
3436 Isenkram is is a good draft, but in the future I expect isenkram to
3437 use the AppStream data source for this. A proposal for getting proper
3438 AppStream support into Debian is floating around as
3439 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3440 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3441 project
</a
> will take place this summer to improve the situation. I
3442 look forward to seeing the result, and welcome patches for isenkram to
3443 start using the information when it is ready.
</p
>
3445 <p
>If you want your package to map to some specific hardware, either
3446 add a
"Xb-Modaliases
" header to your control file like I did in
3447 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3448 package
</a
> or submit a bug report with the details to the isenkram
3450 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3451 blog posts tagged isenkram
</a
> for details on the notation. I expect
3452 the information will be migrated to AppStream eventually, but for the
3453 moment I got no better place to store it.
</p
>
3458 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3459 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3460 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3461 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3462 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3463 project
</a
> is working on providing the software and hardware to make
3464 it easy for non-technical people to host their data and communication
3465 at home, and being able to communicate with their friends and family
3466 encrypted and away from prying eyes. It is still going strong, and
3467 today a major mile stone was reached.
</p
>
3469 <p
>Today, the last of the packages currently used by the project to
3470 created the system images were accepted into Debian Unstable. It was
3471 the freedombox-setup package, which is used to configure the images
3472 during build and on the first boot. Now all one need to get going is
3473 the build code from the freedom-maker git repository and packages from
3474 Debian. And once the freedombox-setup package enter testing, we can
3475 build everything directly from Debian. :)
</p
>
3477 <p
>Some key packages used by Freedombox are
3478 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3479 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3480 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3481 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3482 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3483 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3484 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3485 are plans to integrate more packages into the setup. User
3486 documentation is maintained on the Debian wiki. Please
3487 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3488 the manual
</a
> and help us improve it.
</p
>
3490 <p
>To test for yourself and create boot images with the FreedomBox
3491 setup, run this on a Debian machine using a user with sudo rights to
3492 become root:
</p
>
3494 <p
><pre
>
3495 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3496 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3498 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3500 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3501 </pre
></p
>
3503 <p
>Root access is needed to run debootstrap and mount loopback
3504 devices. See the README in the freedom-maker git repo for more
3505 details on the build. If you do not want all three images, trim the
3506 make line. Note that the virtualbox-image target is not really
3507 virtualbox specific. It create a x86 image usable in kvm, qemu,
3508 vmware and any other x86 virtual machine environment. You might need
3509 the version of vmdebootstrap in Jessie to get the build working, as it
3510 include fixes for a race condition with kpartx.
</p
>
3512 <p
>If you instead want to install using a Debian CD and the preseed
3513 method, boot a Debian Wheezy ISO and use this boot argument to load
3514 the preseed values:
</p
>
3516 <p
><pre
>
3517 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3518 </pre
></p
>
3520 <p
>I have not tested it myself the last few weeks, so I do not know if
3521 it still work.
</p
>
3523 <p
>If you wonder how to help, one task you could look at is using
3524 systemd as the boot system. It will become the default for Linux in
3525 Jessie, so we need to make sure it is usable on the Freedombox. I did
3526 a simple test a few weeks ago, and noticed dnsmasq failed to start
3527 during boot when using systemd. I suspect there are other problems
3528 too. :) To detect problems, there is a test suite included, which can
3529 be run from the plinth web interface.
</p
>
3531 <p
>Give it a go and let us know how it goes on the mailing list, and help
3532 us get the new release published. :) Please join us on
3533 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3534 irc.debian.org)
</a
> and
3535 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3536 mailing list
</a
> if you want to help make this vision come true.
</p
>
3541 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3542 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3543 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3544 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3545 <description><p
>For a while now, I have been looking for a sensible offsite backup
3546 solution for use at home. My requirements are simple, it must be
3547 cheap and locally encrypted (in other words, I keep the encryption
3548 keys, the storage provider do not have access to my private files).
3549 One idea me and my friends had many years ago, before the cloud
3550 storage providers showed up, was to use Google mail as storage,
3551 writing a Linux block device storing blocks as emails in the mail
3552 service provided by Google, and thus get heaps of free space. On top
3553 of this one can add encryption, RAID and volume management to have
3554 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3555 I never found time to implement such system. But the last few weeks I
3556 have looked at a system called
3557 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3558 mounted network backed file system with the features I need.
</p
>
3560 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3561 handling several different storage providers, any with Amazon S3,
3562 Google Drive or OpenStack API. There are heaps of such storage
3563 providers. S3QL can also use a local directory as storage, which
3564 combined with sshfs allow for file storage on any ssh server. S3QL
3565 include support for encryption, compression, de-duplication, snapshots
3566 and immutable file systems, allowing me to mount the remote storage as
3567 a local mount point, look at and use the files as if they were local,
3568 while the content is stored in the cloud as well. This allow me to
3569 have a backup that should survive fire. The file system can not be
3570 shared between several machines at the same time, as only one can
3571 mount it at the time, but any machine with the encryption key and
3572 access to the storage service can mount it if it is unmounted.
</p
>
3574 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3575 package is included already. So to get started, run
<tt
>apt-get
3576 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3577 Greenqloud, after reading their nice recipe on
3578 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3579 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3580 in Iceland more than those in USA when it come to keeping my personal
3581 data safe and private, and thus would rather spend money on a company
3582 in Iceland. Another nice recipe is available from the article
3583 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3584 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3585 Admin magazine. When the provider is picked, figure out how to get
3586 the API key needed to connect to the storage API. With Greencloud,
3587 the key did not show up until I had added payment details to my
3590 <p
>Armed with the API access details, it is time to create the file
3591 system. First, create a new bucket in the cloud. This bucket is the
3592 file system storage area. I picked a bucket name reflecting the
3593 machine that was going to store data there, but any name will do.
3594 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3595 the API login and password, and a locally created password. Store it
3596 all in ~root/.s3ql/authinfo2 like this:
3598 <p
><blockquote
><pre
>
3600 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3601 backend-login: API-login
3602 backend-password: API-password
3603 fs-passphrase: local-password
3604 </pre
></blockquote
></p
>
3606 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3607 but any sensible way to create a fairly random password should do it.
3608 Armed with these details, it is now time to run mkfs, entering the API
3609 details and password to create it:
</p
>
3611 <p
><blockquote
><pre
>
3612 # mkdir -m
700 /var/lib/s3ql-cache
3613 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3614 --ssl s3c://s.greenqloud.com:
443/bucket-name
3615 Enter backend login:
3616 Enter backend password:
3617 Before using S3QL, make sure to read the user
's guide, especially
3618 the
'Important Rules to Avoid Loosing Data
' section.
3619 Enter encryption password:
3620 Confirm encryption password:
3621 Generating random encryption key...
3622 Creating metadata tables...
3632 Compressing and uploading metadata...
3633 Wrote
0.00 MB of compressed metadata.
3634 #
</pre
></blockquote
></p
>
3636 <p
>The next step is mounting the file system to make the storage available.
3638 <p
><blockquote
><pre
>
3639 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3640 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3641 Using
4 upload threads.
3642 Downloading and decompressing metadata...
3652 Mounting filesystem...
3654 Filesystem Size Used Avail Use% Mounted on
3655 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3657 </pre
></blockquote
></p
>
3659 <p
>The file system is now ready for use. I use rsync to store my
3660 backups in it, and as the metadata used by rsync is downloaded at
3661 mount time, no network traffic (and storage cost) is triggered by
3662 running rsync. To unmount, one should not use the normal umount
3663 command, as this will not flush the cache to the cloud storage, but
3664 instead running the umount.s3ql command like this:
3666 <p
><blockquote
><pre
>
3669 </pre
></blockquote
></p
>
3671 <p
>There is a fsck command available to check the file system and
3672 correct any problems detected. This can be used if the local server
3673 crashes while the file system is mounted, to reset the
"already
3674 mounted
" flag. This is what it look like when processing a working
3675 file system:
</p
>
3677 <p
><blockquote
><pre
>
3678 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3679 Using cached metadata.
3680 File system seems clean, checking anyway.
3681 Checking DB integrity...
3682 Creating temporary extra indices...
3683 Checking lost+found...
3684 Checking cached objects...
3685 Checking names (refcounts)...
3686 Checking contents (names)...
3687 Checking contents (inodes)...
3688 Checking contents (parent inodes)...
3689 Checking objects (reference counts)...
3690 Checking objects (backend)...
3691 ..processed
5000 objects so far..
3692 ..processed
10000 objects so far..
3693 ..processed
15000 objects so far..
3694 Checking objects (sizes)...
3695 Checking blocks (referenced objects)...
3696 Checking blocks (refcounts)...
3697 Checking inode-block mapping (blocks)...
3698 Checking inode-block mapping (inodes)...
3699 Checking inodes (refcounts)...
3700 Checking inodes (sizes)...
3701 Checking extended attributes (names)...
3702 Checking extended attributes (inodes)...
3703 Checking symlinks (inodes)...
3704 Checking directory reachability...
3705 Checking unix conventions...
3706 Checking referential integrity...
3707 Dropping temporary indices...
3708 Backing up old metadata...
3718 Compressing and uploading metadata...
3719 Wrote
0.89 MB of compressed metadata.
3721 </pre
></blockquote
></p
>
3723 <p
>Thanks to the cache, working on files that fit in the cache is very
3724 quick, about the same speed as local file access. Uploading large
3725 amount of data is to me limited by the bandwidth out of and into my
3726 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3727 which is very close to my upload speed, and downloading the same
3728 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3729 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3730 network, not the file system code. I do not know what a good cache
3731 size would be, but suspect that the cache should e larger than your
3732 working set.
</p
>
3734 <p
>I mentioned that only one machine can mount the file system at the
3735 time. If another machine try, it is told that the file system is
3738 <p
><blockquote
><pre
>
3739 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3740 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3741 Using
8 upload threads.
3742 Backend reports that fs is still mounted elsewhere, aborting.
3744 </pre
></blockquote
></p
>
3746 <p
>The file content is uploaded when the cache is full, while the
3747 metadata is uploaded once every
24 hour by default. To ensure the
3748 file system content is flushed to the cloud, one can either umount the
3749 file system, or ask S3QL to flush the cache and metadata using
3752 <p
><blockquote
><pre
>
3753 # s3qlctrl upload-meta /s3ql
3754 # s3qlctrl flushcache /s3ql
3756 </pre
></blockquote
></p
>
3758 <p
>If you are curious about how much space your data uses in the
3759 cloud, and how much compression and deduplication cut down on the
3760 storage usage, you can use s3qlstat on the mounted file system to get
3763 <p
><blockquote
><pre
>
3765 Directory entries:
9141
3768 Total data size:
22049.38 MB
3769 After de-duplication:
21955.46 MB (
99.57% of total)
3770 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3771 Database size:
2.39 MB (uncompressed)
3772 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3774 </pre
></blockquote
></p
>
3776 <p
>I mentioned earlier that there are several possible suppliers of
3777 storage. I did not try to locate them all, but am aware of at least
3778 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3779 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3780 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3781 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3782 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3783 accept payment in Bitcoin. Pick one that suit your need. Some of
3784 them provide several GiB of free storage, but the prize models are
3785 quite different and you will have to figure out what suits you
3788 <p
>While researching this blog post, I had a look at research papers
3789 and posters discussing the S3QL file system. There are several, which
3790 told me that the file system is getting a critical check by the
3791 science community and increased my confidence in using it. One nice
3793 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3794 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3795 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3796 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3797 and Pamela Smith. Please have a look.
</p
>
3799 <p
>Given my problems with different file systems earlier, I decided to
3800 check out the mounted S3QL file system to see if it would be usable as
3801 a home directory (in other word, that it provided POSIX semantics when
3802 it come to locking and umask handling etc). Running
3803 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3804 test code to check file system semantics
</a
>, I was happy to discover that
3805 no error was found. So the file system can be used for home
3806 directories, if one chooses to do so.
</p
>
3808 <p
>If you do not want a locally file system, and want something that
3809 work without the Linux fuse file system, I would like to mention the
3810 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3811 provide locally encrypted backup using a command line client. It have
3812 a nicer access control system, where one can split out read and write
3813 access, allowing some systems to write to the backup and others to
3814 only read from it.
</p
>
3816 <p
>As usual, if you use Bitcoin and want to show your support of my
3817 activities, please send Bitcoin donations to my address
3818 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3823 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3824 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3825 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3826 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3827 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3828 project
</a
> is working on providing the software and hardware for
3829 making it easy for non-technical people to host their data and
3830 communication at home, and being able to communicate with their
3831 friends and family encrypted and away from prying eyes. It has been
3832 going on for a while, and is slowly progressing towards a new test
3833 release (
0.2).
</p
>
3835 <p
>And what day could be better than the Pi day to announce that the
3836 new version will provide
"hard drive
" / SD card / USB stick images for
3837 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3838 system), and can also be installed using a Debian installer preseed
3839 file. The Debian based Freedombox is now based on Debian Jessie,
3840 where most of the needed packages used are already present. Only one,
3841 the freedombox-setup package, is missing. To try to build your own
3842 boot image to test the current status, fetch the freedom-maker scripts
3844 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
3845 with a user with sudo access to become root:
3848 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3850 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3851 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3853 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3856 <p
>Root access is needed to run debootstrap and mount loopback
3857 devices. See the README for more details on the build. If you do not
3858 want all three images, trim the make line. But note that thanks to
<a
3859 href=
"https://bugs.debian.org/
741407">a race condition in
3860 vmdebootstrap
</a
>, the build might fail without the patch to the
3861 kpartx call.
</p
>
3863 <p
>If you instead want to install using a Debian CD and the preseed
3864 method, boot a Debian Wheezy ISO and use this boot argument to load
3865 the preseed values:
</p
>
3868 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3871 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
3872 recently introduced bug in apt in Jessie
</a
>, the installer will
3873 currently hang while setting up APT sources. Killing the
3874 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
3875 installation will get the installation going. This affect all
3876 installations in Jessie, and I expect it will be fixed soon.
</p
>
3878 <p
>Give it a go and let us know how it goes on the mailing list, and help
3879 us get the new release published. :) Please join us on
3880 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3881 irc.debian.org)
</a
> and
3882 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3883 mailing list
</a
> if you want to help make this vision come true.
</p
>
3888 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
3889 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
3890 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
3891 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
3892 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
3893 innetgr tools, because I needed them in
3894 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
3895 ng-utils, and it has served me well. I placed the project under the
3896 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
3897 repository. But many years ago, the CVS repository was dropped (lost,
3898 not migrated to new hardware, not sure), and the project have lacked a
3899 proper home since then.
</p
>
3901 <p
>Last summer, I had a look at the package and made a new release
3902 fixing a irritating crash bug, but was unable to store the changes in
3903 a proper source control system. I applied for a project on
3904 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
3905 to follow up on it. Until today. :)
</p
>
3907 <p
>After many hours of cleaning and migration, the ng-utils project
3908 now have a new home, and a git repository with the highlight of the
3909 history of the project. I published all release tarballs and imported
3910 them into the git repository. As the project is really stable and not
3911 expected to gain new features any time soon, I decided to make a new
3912 release and call it
1.0. Visit the new project home on
3913 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
3914 if you want to check it out. The new version is also uploaded into
3915 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
3920 <title>Testing sysvinit from experimental in Debian Hurd
</title>
3921 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
3922 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
3923 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
3924 <description><p
>A few days ago I decided to try to help the Hurd people to get
3925 their changes into sysvinit, to allow them to use the normal sysvinit
3926 boot system instead of their old one. This follow up on the
3927 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
3928 Google Summer of Code work
</a
> done last summer by Justus Winter to
3929 get Debian on Hurd working more like Debian on Linux. To get started,
3930 I downloaded a prebuilt hard disk image from
3931 <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
>,
3932 and started it using virt-manager.
</p
>
3934 <p
>The first think I had to do after logging in (root without any
3935 password) was to get the network operational. I followed
3936 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
3937 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
3938 commands as root to get the machine to accept a IP address from the
3939 kvm internal DHCP server:
</p
>
3941 <p
><blockquote
><pre
>
3942 settrans -fgap /dev/netdde /hurd/netdde
3943 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
3944 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
3946 </pre
></blockquote
></p
>
3948 <p
>After this, the machine had internet connectivity, and I could
3949 upgrade it and install the sysvinit packages from experimental and
3950 enable it as the default boot system in Hurd.
</p
>
3952 <p
>But before I did that, I set a password on the root user, as ssh is
3953 running on the machine it for ssh login to work a password need to be
3954 set. Also, note that a bug somewhere in openssh on Hurd block
3955 compression from working. Remember to turn that off on the client
3958 <p
>Run these commands as root to upgrade and test the new sysvinit
3961 <p
><blockquote
><pre
>
3962 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
3963 deb http://http.debian.net/debian/ experimental main
3966 apt-get dist-upgrade
3967 apt-get install -t experimental initscripts sysv-rc sysvinit \
3968 sysvinit-core sysvinit-utils
3969 update-alternatives --config runsystem
3970 </pre
></blockquote
></p
>
3972 <p
>To reboot after switching boot system, you have to use
3973 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
3974 yet a sysvinit process able to receive the signals from the normal
3975 'reboot
' command. After switching to sysvinit as the boot system,
3976 upgrading every package and rebooting, the network come up with DHCP
3977 after boot as it should, and the settrans/pkill hack mentioned at the
3978 start is no longer needed. But for some strange reason, there are no
3979 longer any login prompt in the virtual console, so I logged in using
3982 <p
>Note that there are some race conditions in Hurd making the boot
3983 fail some times. No idea what the cause is, but hope the Hurd porters
3984 figure it out. At least Justus said on IRC (#debian-hurd on
3985 irc.debian.org) that they are aware of the problem. A way to reduce
3986 the impact is to upgrade to the Hurd packages built by Justus by
3987 adding this repository to the machine:
</p
>
3989 <p
><blockquote
><pre
>
3990 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
3991 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3993 </pre
></blockquote
></p
>
3995 <p
>At the moment the prebuilt virtual machine get some packages from
3996 http://ftp.debian-ports.org/debian, because some of the packages in
3997 unstable do not yet include the required patches that are lingering in
3998 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4000 <p
><blockquote
><pre
>
4001 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4002 i emacs - GNU Emacs editor (metapackage)
4003 i gdb - GNU Debugger
4004 i hurd-recommended - Miscellaneous translators
4005 i isc-dhcp-client - ISC DHCP client
4006 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4007 i libc-bin - Embedded GNU C Library: Binaries
4008 i libc-dev-bin - Embedded GNU C Library: Development binaries
4009 i libc0.3 - Embedded GNU C Library: Shared libraries
4010 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4011 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4012 i multiarch-support - Transitional package to ensure multiarch compatibilit
4013 i A x11-common - X Window System (X.Org) infrastructure
4014 i xorg - X.Org X Window System
4015 i A xserver-xorg - X.Org X server
4016 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4018 </pre
></blockquote
></p
>
4020 <p
>All in all, testing hurd has been an interesting experience. :)
4021 X.org did not work out of the box and I never took the time to follow
4022 the porters instructions to fix it. This time I was interested in the
4023 command line stuff.
<p
>
4028 <title>New chrpath release
0.16</title>
4029 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4030 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4031 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4032 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4033 find problems in C, C++ and Java code using static source code
4034 analysis. It can detect a lot of different problems, and is very
4035 useful to find memory and locking bugs in the error handling part of
4036 the source. The company behind it provide
4037 <a href=
"https://scan.coverity.com/
">check of free software projects as
4038 a community service
</a
>, and many hundred free software projects are
4039 already checked. A few days ago I decided to have a closer look at
4040 the Coverity system, and discovered that the
4041 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4042 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4043 projects I am involved with was already registered. But these are
4044 fairly big, and I would also like to have a small and easy project to
4045 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4046 checking of the chrpath project
</a
>. It was
4047 added to the checker and discovered seven potential defects. Six of
4048 these were real, mostly resource
"leak
" when the program detected an
4049 error. Nothing serious, as the resources would be released a fraction
4050 of a second later when the program exited because of the error, but it
4051 is nice to do it right in case the source of the program some time in
4052 the future end up in a library. Having fixed all defects and added
4053 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4054 mailing list for the chrpath developers
</a
>, I decided it was time to
4055 publish a new release. These are the release notes:
</p
>
4057 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4061 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4062 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4063 <li
>Mention new project mailing list in the documentation.
</li
>
4068 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4069 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4070 project if something is wrong with the new release. The test suite
4071 did not discover any old errors, so if you find a new one, please also
4072 include a test suite check.
</p
>
4077 <title>New chrpath release
0.15</title>
4078 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4080 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4081 <description><p
>After many years break from the package and a vain hope that
4082 development would be continued by someone else, I finally pulled my
4083 acts together this morning and wrapped up a new release of chrpath,
4084 the command line tool to modify the rpath and runpath of already
4085 compiled ELF programs. The update was triggered by the persistence of
4086 Isha Vishnoi at IBM, which needed a new config.guess file to get
4087 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4088 is working on. I checked the
4089 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4090 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4091 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4092 packages for interesting patches (failed to find the source from
4093 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4094 These are the release notes:
</p
>
4096 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4100 <li
>Updated config.sub and config.guess from the GNU project to work
4101 with newer architectures. Thanks to isha vishnoi for the heads
4104 <li
>Updated README with current URLs.
</li
>
4106 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4107 Matthias Klose.
</li
>
4109 <li
>Added missing help for -k|--keepgoing option, using patch by
4110 Petr Machata found in Fedora.
</li
>
4112 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4113 .dynamic is a NULL terminated string. Based on patch found in
4114 Fedora credited Axel Thimm and Christian Krause.
</li
>
4119 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4120 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4121 project if something is wrong with the new release. The test suite
4122 did not discover any old errors, so if you find a new one, please also
4123 include a testsuite check.
</p
>
4128 <title>Debian init.d boot script example for rsyslog
</title>
4129 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4130 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4131 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4132 <description><p
>If one of the points of switching to a new init system in Debian is
4133 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4134 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4135 init.d scripts at all. Here is an example init.d script, ie a rewrite
4136 of /etc/init.d/rsyslog:
</p
>
4138 <p
><pre
>
4139 #!/lib/init/init-d-script
4142 # Required-Start: $remote_fs $time
4143 # Required-Stop: umountnfs $time
4144 # X-Stop-After: sendsigs
4145 # Default-Start:
2 3 4 5
4146 # Default-Stop:
0 1 6
4147 # Short-Description: enhanced syslogd
4148 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4149 # It is quite compatible to stock sysklogd and can be
4150 # used as a drop-in replacement.
4152 DESC=
"enhanced syslogd
"
4153 DAEMON=/usr/sbin/rsyslogd
4154 </pre
></p
>
4156 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4157 script was
137 lines, and the above is just
15 lines, most of it meta
4158 info/comments.
</p
>
4160 <p
>How to do this, you ask? Well, one create a new script
4161 /lib/init/init-d-script looking something like this:
4163 <p
><pre
>
4166 # Define LSB log_* functions.
4167 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4168 # and status_of_proc is working.
4169 . /lib/lsb/init-functions
4172 # Function that starts the daemon/service
4178 #
0 if daemon has been started
4179 #
1 if daemon was already running
4180 #
2 if daemon could not be started
4181 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4183 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4186 # Add code here, if necessary, that waits for the process to be ready
4187 # to handle requests from services started subsequently which depend
4188 # on this one. As a last resort, sleep for some time.
4192 # Function that stops the daemon/service
4197 #
0 if daemon has been stopped
4198 #
1 if daemon was already stopped
4199 #
2 if daemon could not be stopped
4200 # other if a failure occurred
4201 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4202 RETVAL=
"$?
"
4203 [
"$RETVAL
" =
2 ]
&& return
2
4204 # Wait for children to finish too if this is a daemon that forks
4205 # and if the daemon is only ever run from this initscript.
4206 # If the above conditions are not satisfied then add some other code
4207 # that waits for the process to drop all resources that could be
4208 # needed by services started subsequently. A last resort is to
4209 # sleep for some time.
4210 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4211 [
"$?
" =
2 ]
&& return
2
4212 # Many daemons don
't delete their pidfiles when they exit.
4214 return
"$RETVAL
"
4218 # Function that sends a SIGHUP to the daemon/service
4222 # If the daemon can reload its configuration without
4223 # restarting (for example, when it is sent a SIGHUP),
4224 # then implement that here.
4226 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4231 scriptbasename=
"$(basename $
1)
"
4232 echo
"SN: $scriptbasename
"
4233 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4234 script=
"$
1"
4241 NAME=$(basename $DAEMON)
4242 PIDFILE=/var/run/$NAME.pid
4244 # Exit if the package is not installed
4245 #[ -x
"$DAEMON
" ] || exit
0
4247 # Read configuration variable file if it is present
4248 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4250 # Load the VERBOSE setting and other rcS variables
4253 case
"$
1" in
4255 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4257 case
"$?
" in
4258 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4259 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4263 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4265 case
"$?
" in
4266 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4267 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4271 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4273 #reload|force-reload)
4275 # If do_reload() is not implemented then leave this commented out
4276 # and leave
'force-reload
' as an alias for
'restart
'.
4278 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4282 restart|force-reload)
4284 # If the
"reload
" option is implemented then remove the
4285 #
'force-reload
' alias
4287 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4289 case
"$?
" in
4292 case
"$?
" in
4294 1) log_end_msg
1 ;; # Old process is still running
4295 *) log_end_msg
1 ;; # Failed to start
4305 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4311 </pre
></p
>
4313 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4314 lot. I did not really polish the approach, so it might not always
4315 work out of the box, but you get the idea. I did not try very hard to
4316 optimize it nor make it more robust either.
</p
>
4318 <p
>A better argument for switching init system in Debian than reducing
4319 the size of init scripts (which is a good thing to do anyway), is to
4320 get boot system that is able to handle the kernel events sensibly and
4321 robustly, and do not depend on the boot to run sequentially. The boot
4322 and the kernel have not behaved sequentially in years.
</p
>
4327 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4328 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4329 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4330 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4331 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4332 remote display access is the preferred solution with oVirt and RedHat
4333 Enterprise Virtualization, and I was sad to discover the other day
4334 that the browser plugin needed to use these systems seamlessly was
4335 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4336 for a package
</a
> was from
2012-
04-
10 with no progress since
4337 2013-
04-
01, so I decided to wrap up a package based on the great work
4338 from Cajus Pollmeier and put it in a collab-maint maintained git
4339 repository to get a package I could use. I would very much like
4340 others to help me maintain the package (or just take over, I do not
4341 mind), but as no-one had volunteered so far, I just uploaded it to
4342 NEW. I hope it will be available in Debian in a few days.
</p
>
4344 <p
>The source is now available from
4345 <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
>
4350 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4351 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4352 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4353 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4354 <description><p
>The
4355 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4356 program is a a very nice system to create virtual machine images. It
4357 create a image file, add a partition table, mount it and run
4358 debootstrap in the mounted directory to create a Debian system on a
4359 stick. Yesterday, I decided to try to teach it how to make images for
4360 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4361 of a plan to simplify the build system for
4362 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4363 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4364 the virtualbox images, but its current build system made multistrap
4365 based system for Dreamplug images, and it is lacking support for
4366 Raspberry Pi.
</p
>
4368 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4369 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4370 code and adjusted it to be able to build armel images on my amd64
4371 Debian laptop. I ended up giving vmdebootstrap five new options,
4372 allowing me to replicate the image creation process I use to make
4373 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4374 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4375 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4376 call debootstrap with --foreign and to copy the handler into the
4377 generated chroot before running the second stage. This allow
4378 vmdebootstrap to create armel images on an amd64 host. Next I added
4379 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4380 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4381 given file system type, allowing me to create an image with a vfat
4382 partition for the /boot/ stuff. I also added a
<tt
>--variant
4383 variant
</tt
> option to allow me to create smaller images without the
4384 Debian base system packages installed. Finally, I added an option
4385 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4386 as a boot loader. It is not needed on the Raspberry Pi and probably
4387 most other non-x86 architectures. The changes were accepted by the
4388 upstream author of vmdebootstrap yesterday and today, and is now
4390 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4391 upstream project page
</a
>.
</p
>
4393 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4394 create a small script (the customize script) to add the non-free
4395 binary blob needed to boot the Raspberry Pi and the APT source
4398 <p
><pre
>
4400 set -e # Exit on first error
4401 rootdir=
"$
1"
4402 cd
"$rootdir
"
4403 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4404 deb http://http.debian.net/debian/ jessie main contrib non-free
4406 # Install non-free binary blob needed to boot Raspberry Pi. This
4407 # install a kernel somewhere too.
4408 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4409 -O $rootdir/usr/bin/rpi-update
4410 chmod a+x $rootdir/usr/bin/rpi-update
4411 mkdir -p $rootdir/lib/modules
4412 touch $rootdir/boot/start.elf
4413 chroot $rootdir rpi-update
4414 </pre
></p
>
4416 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4417 to build the image:
</p
>
4420 sudo ./vmdebootstrap \
4423 --distribution jessie \
4424 --mirror http://http.debian.net/debian \
4433 --root-password raspberry \
4434 --hostname raspberrypi \
4435 --foreign /usr/bin/qemu-arm-static \
4436 --customize `pwd`/customize \
4438 --package git-core \
4439 --package binutils \
4440 --package ca-certificates \
4443 </pre
></p
>
4445 <p
>The list of packages being installed are the ones needed by
4446 rpi-update to make the image bootable on the Raspberry Pi, with the
4447 exception of netbase, which is needed by debootstrap to find
4448 /etc/hosts with the minbase variant. I really wish there was a way to
4449 set up an Raspberry Pi using only packages in the Debian archive, but
4450 that is not possible as far as I know, because it boots from the GPU
4451 using a non-free binary blob.
</p
>
4453 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4454 probably a few others installed. I have not checked the complete
4455 build dependency list.
</p
>
4457 <p
>The resulting image will not use the hardware floating point unit
4458 on the Raspberry PI, because the armel architecture in Debian is not
4459 optimized for that use. So the images created will be a bit slower
4460 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4465 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4466 <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>
4467 <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>
4468 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4469 <description><p
>The last few days I came across a few good causes that should get
4470 wider attention. I recommend signing and donating to each one of
4473 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4474 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4475 Women program which is a Google Summer of Code like initiative to get
4476 more women involved in free software. One debian sponsor has offered
4477 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4478 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4479 hope you will to. :)
</p
>
4481 <p
>And the Electronic Frontier Foundation just announced plans to
4482 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4483 documentaries about the excessive spying
</a
> on every Internet user that
4484 take place these days, and their need to fund the work. I
've already
4485 donated. Are you next?
</p
>
4487 <p
>For my Norwegian audience, the organisation Studentenes og
4488 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4489 statement under the heading
4490 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4491 Access
</a
> for those of us asking for more focus on open access in the
4492 Norwegian government. So far
499 signatures. I hope you will sign it
4498 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4499 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4500 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4501 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4502 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4503 project
</a
> have been going on for a while, and have presented the
4504 vision, ideas and solution several places. Here is a little
4505 collection of videos of talks and presentation of the project.
</p
>
4509 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4510 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4512 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4513 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4515 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4516 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4517 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4518 (Youtube)
</li
>
4520 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4521 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4523 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4524 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4526 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4527 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4528 York City in
2012</a
> (Youtube)
</li
>
4530 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4531 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4532 (Youtube)
</li
>
4534 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4535 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4537 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4538 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4540 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4541 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4542 2013</a
> (Youtube)
</li
>
4546 <p
>A larger list is available from
4547 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4548 Freedombox Wiki
</a
>.
</p
>
4550 <p
>On other news, I am happy to report that Freedombox based on Debian
4551 Jessie is coming along quite well, and soon both Owncloud and using
4552 Tor should be available for testers of the Freedombox solution. :) In
4553 a few weeks I hope everything needed to test it is included in Debian.
4554 The withsqlite package is already in Debian, and the plinth package is
4555 pending in NEW. The third and vital part of that puzzle is the
4556 metapackage/setup framework, which is still pending an upload. Join
4557 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4558 (#freedombox on irc.debian.org)
</a
> and
4559 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4560 mailing list
</a
> if you want to help make this vision come true.
</p
>
4565 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4566 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4567 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4568 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4569 <description><p
>I was introduced to the
4570 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4571 in
2010, when Eben Moglen presented his vision about serving the need
4572 of non-technical people to keep their personal information private and
4573 within the legal protection of their own homes. The idea is to give
4574 people back the power over their network and machines, and return
4575 Internet back to its intended peer-to-peer architecture. Instead of
4576 depending on a central service, the Freedombox will give everyone
4577 control over their own basic infrastructure.
</p
>
4579 <p
>I
've intended to join the effort since then, but other tasks have
4580 taken priority. But this summers nasty news about the misuse of trust
4581 and privilege exercised by the
"western
" intelligence gathering
4582 communities increased my eagerness to contribute to a point where I
4583 actually started working on the project a while back.
</p
>
4585 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4586 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4587 create a simple and cheap Debian based appliance that anyone can hook
4588 up in their home and get access to secure and private services and
4589 communication. The initial deployment platform have been the
4590 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4591 which is a piece of hardware I do not own. So to be able to test what
4592 the current Freedombox setup look like, I had to come up with a way to install
4593 it on some hardware I do have access to. I have rewritten the
4594 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4595 image build framework to use .deb packages instead of only copying
4596 setup into the boot images, and thanks to this rewrite I am able to
4597 set up any machine supported by Debian Wheezy as a Freedombox, using
4598 the previously mentioned deb (and a few support debs for packages
4599 missing in Debian).
</p
>
4601 <p
>The current Freedombox setup consist of a set of bootstrapping
4603 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4604 and a administrative web interface
4605 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4606 withsqlite), as well as a privacy enhancing proxy based on
4607 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4608 (freedombox-privoxy). There is also a web/javascript based XMPP
4609 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4610 trying (unsuccessfully so far) to talk to the XMPP server
4611 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4612 web interface is pluggable, and the goal is to use it to enable OpenID
4613 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4614 this is really working yet, see
4615 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4616 project TODO
</a
> for links to GIT repositories. Most of the code is
4617 on github at the moment. The HTTP proxy is operational out of the
4618 box, and the admin web interface can be used to add/remove plinth
4619 users. I
've not been able to do anything else with it so far, but
4620 know there are several branches spread around github and other places
4621 with lots of half baked features.
</p
>
4623 <p
>Anyway, if you want to have a look at the current state, the
4624 following recipes should work to give you a test machine to poke
4627 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4631 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4632 <li
>Boot from it, either as CD or USB stick.
</li
>
4633 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4634 to the Debian installer:
<p
>
4635 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4637 <li
>Answer the few language/region/password questions and pick disk to
4638 install on.
</li
>
4640 <li
>When the installation is finished and the machine have rebooted a
4641 few times, your Freedombox is ready for testing.
</li
>
4645 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4649 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4650 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4651 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4653 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4654 </pre
></li
>
4655 <li
><p
>Run this as root:
</p
>
4657 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4660 apt-get install freedombox-setup
4661 /usr/lib/freedombox/setup
4662 </pre
></li
>
4663 <li
>Reboot into your freshly created Freedombox.
</li
>
4667 <p
>You can test it on other architectures too, but because the
4668 freedombox-privoxy package is binary, it will only work as intended on
4669 the architectures where I have had time to build the binary and put it
4670 in my APT repository. But do not let this stop you. It is only a
4671 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4673 <p
>Note that by default Freedombox is a DHCP server on the
4674 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4675 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4676 disable
</tt
>" as root.
</p
>
4678 <p
>Please let me know if this works for you, or if you have any
4679 problems. We gather on the IRC channel
4680 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4681 irc.debian.org and the
4682 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4683 mailing list
</a
>.
</p
>
4685 <p
>Once you get your freedombox operational, you can visit
4686 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4687 welcome screen (dead end - do not be surprised if you are unable to
4688 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4689 to look at the rest of plinth. The default user is
'admin
' and the
4690 default password is
'secret
'.
</p
>
4695 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4696 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4697 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4698 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4699 <description><p
>Earlier, I reported about
4700 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4701 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4702 told by IBM that the original disk should be thrown away. And as
4703 there no longer was a problem if I bricked the firmware, I decided
4704 today to try to install Intel firmware to replace the Lenovo firmware
4705 currently on the disk.
</p
>
4707 <p
>I searched the Intel site for firmware, and found
4708 <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
>
4709 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4710 according to the site should contain the latest firmware for SSD
4711 disks. I inserted the broken disk in one of my spare laptops and
4712 booted the ISO from a USB stick. The disk was recognized, but the
4713 program claimed the newest firmware already were installed and refused
4714 to insert any Intel firmware. So no change, and the disk is still
4715 unable to handle write load. :( I guess the only way to get them
4716 working would be if Lenovo releases new firmware. No idea how likely
4717 that is. Anyway, just blogging about this test for completeness. I
4718 got a working Samsung disk, and see no point in spending more time on
4719 the broken disks.
</p
>
4724 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4725 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4726 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4727 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4728 <description><p
>Today I switched to
4729 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4730 new laptop
</a
>. I
've previously written about the problems I had with
4731 my new Thinkpad X230, which was delivered with an
4732 <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
4733 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4734 sustained writes. My hardware supplier have been very forthcoming in
4735 trying to find a solution, and after first trying with another
4736 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4737 disk instead to fix it once and for all. The Samsung disk survived
4738 the installation of Debian with encrypted disks (filling the disk with
4739 random data during installation killed the first two), and I thus
4740 decided to trust it with my data. I have installed it as a Debian Edu
4741 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4742 server at home using Kerberos and LDAP, and will use it as my work
4743 station from now on.
</p
>
4745 <p
>As this is a solid state disk with no moving parts, I believe the
4746 Debian Wheezy default installation need to be tuned a bit to increase
4747 performance and increase life time of the disk. The Linux kernel and
4748 user space applications do not yet adjust automatically to such
4749 environment. To make it easier for my self, I created a draft Debian
4750 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4751 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4752 for the ssd-setup package
</a
> is available from collab-maint, and it
4753 is set up to adjust the setup of the machine by just installing the
4754 package. If there is any non-SSD disk in the machine, the package
4755 will refuse to install, as I did not try to write any logic to sort
4756 file systems in SSD and non-SSD file systems.
</p
>
4758 <p
>I consider the package a draft, as I am a bit unsure how to best
4759 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4760 where I set up the machine with one large encrypted partition (in
4761 addition to /boot), put LVM on top of this and set up partitions on
4762 top of this again. See the README file in the package source for the
4763 references I used to pick the settings. At the moment these
4764 parameters are tuned:
</p
>
4768 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4769 (adding discard to /etc/crypttab)
</li
>
4771 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4772 this case a cryptsetup partition) by changing issue_discards from
4773 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4775 <li
>Set relatime as a file system option for ext3 and ext4 file
4778 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4779 /etc/fstab.
</li
>
4781 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4783 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4784 cron.daily).
</li
>
4786 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4787 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4791 <p
>During installation, I cancelled the part where the installer fill
4792 the disk with random data, as this would kill the SSD performance for
4793 little gain. My goal with the encrypted file system is to ensure
4794 those stealing my laptop end up with a brick and not a working
4795 computer. I have no hope in keeping the really resourceful people
4796 from getting the data on the disk (see
4797 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4798 Thus I concluded that adding the discard option to crypttab is the
4799 right thing to do.
</p
>
4801 <p
>I considered using the noop I/O scheduler, as several recommended
4802 it for SSD, but others recommended deadline and a benchmark I found
4803 indicated that deadline might be better for interactive use.
</p
>
4805 <p
>I also considered using the
'discard
' file system option for ext3
4806 and ext4, but read that it would give a performance hit ever time a
4807 file is removed, and thought it best to that that slowdown once a day
4808 instead of during my work.
</p
>
4810 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4811 this is already done by Debian Edu.
</p
>
4813 <p
>I have not yet started on the user space tuning. I expect
4814 iceweasel need some tuning, and perhaps other applications too, but
4815 have not yet had time to investigate those parts.
</p
>
4817 <p
>The package should work on Ubuntu too, but I have not yet tested it
4820 <p
>As for the answer to the question in the title of this blog post,
4821 as far as I know, the only solution I know about is to replace the
4822 disk. It might be possible to flash it with Intel firmware instead of
4823 the Lenovo firmware. But I have not tried and did not want to do so
4824 without approval from Lenovo as I wanted to keep the warranty on the
4825 disk until a solution was found and they wanted the broken disks
4831 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4832 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4833 <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>
4834 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4835 <description><p
>A few days ago, I wrote about
4836 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4837 problems I experienced with my new X230 and its SSD disk
</a
>, which
4838 was dying during installation because it is unable to cope with
4839 sustained write. My supplier is in contact with
4840 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
4841 replacement disk to try to fix the problem. They decided to send an
4842 identical model, so my hopes for a permanent fix was slim.
</p
>
4844 <p
>Anyway, today I got the replacement disk and tried to install
4845 Debian Edu Wheezy with encrypted disk on it. The new disk have the
4846 same firmware version as the original. This time my hope raised
4847 slightly as the installation progressed, as the original disk used to
4848 die after
4-
7% of the disk was written to, while this time it kept
4849 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
4850 died again and I was back on square one. I still do not have a new
4851 laptop with a disk I can trust. I can not live with a disk that might
4852 lock up when I download a new
4853 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
4854 other large files. I look forward to hearing from my supplier with
4855 the next proposal from Lenovo.
</p
>
4857 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
4858 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
4859 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4860 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
4861 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4862 P/N
45N8295, P0C38732.
</p
>
4864 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
4865 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
4866 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
4867 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
4868 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
4869 P/N
45N8295, P0C38732.
</p
>
4871 <p
>The only difference is in the first number (serial number?), ISN,
4872 SA, date and WNPP values. Mentioning all the details here in case
4873 someone is able to use the information to find a way to identify the
4874 failing disk among working ones (if any such working disk actually
4880 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
4881 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
4882 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
4883 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
4884 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
4885 Debian Edu developer gathering and Debian and Ubuntu bug squashing
4886 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
4887 member assosiation NUUG
</a
> and
4888 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
4889 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
4890 Bitraf
</a
>.
</p
>
4892 <p
>It starts
10:
00 and continue until late evening. Everyone is
4893 welcome, and there is no fee to participate. There is on the other
4894 hand limited space, and only room for
30 people. Please put your name
4895 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
4896 wiki page
</a
> if you plan to join us.
</p
>
4901 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
4902 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
4903 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
4904 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
4905 <description><p
>Half a year ago, I reported that I had to find a
4906 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
4907 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
4908 time to spend on it, and it took a while to find a model I believe
4909 will do the job, but two days ago the replacement finally arrived. I
4911 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
4912 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
4913 a roaming workstation, and it seemed to work flawlessly. But my
4914 second installation with encrypted disk was not as successful. More
4915 on that below.
</p
>
4917 <p
>I had a hard time trying to track down a good laptop, as my most
4918 important requirements (robust and with a good keyboard) are never
4919 listed in the feature list. But I did get good help from the search
4920 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4921 allowed me to limit the list of interesting laptops based on my other
4922 requirements. A bit surprising that SSD disk are not disks according
4923 to that search interface, so I had to drop specifying the number of
4924 disks from my search parameters. I also asked around among friends to
4925 get their impression on keyboards and robustness.
</p
>
4927 <p
>So the new laptop arrived, and it is quite a lot wider than the
4928 X41. I am not quite convinced about the keyboard, as it is
4929 significantly wider than my old keyboard, and I have to stretch my
4930 hand a lot more to reach the edges. But the key response is fairly
4931 good and the individual key shape is fairly easy to handle, so I hope
4932 I will get used to it. My old X40 was starting to fail, and I really
4933 needed a new laptop now. :)
</p
>
4935 <p
>Turning off the touch pad was simple. All it took was a quick
4936 visit to the BIOS during boot it disable it.
</p
>
4938 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
4939 lock up during load. And this happen when installing Debian Wheezy
4940 with encrypted disk, while the disk is being filled with random data.
4941 I also tested to install Ubuntu Raring, and it happen there too if I
4942 reenable the code to fill the disk with random data (it is disabled by
4943 default in Ubuntu). And the bug with is already known. It was
4944 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
4945 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
4946 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4947 kernel developers as
4948 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
4949 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
4950 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4951 Lenovo forums, both for
4952 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
4953 2012-
11-
10</a
> and for
4954 <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
4955 03-
20-
2013</a
>. The problem do not only affect installation. The
4956 reports state that the disk lock up during use if many writes are done
4957 on the disk, so it is much no use to work around the installation
4958 problem and end up with a computer that can lock up at any moment.
4960 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
4961 available
</a
> that will lock up the hard drive after running a few
4962 minutes by writing to a file.
</p
>
4964 <p
>I
've contacted my supplier and asked how to handle this, and after
4965 contacting PCHELP Norway (request
01D1FDP) which handle support
4966 requests for Lenovo, his first suggestion was to upgrade the disk
4967 firmware. Unfortunately there is no newer firmware available from
4968 Lenovo, as my disk already have the most recent one (version LF1i). I
4969 hope to hear more from him today and hope the problem can be
4975 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
4976 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
4977 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
4978 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
4979 <description><p
>Half a year ago, I reported that I had to find a replacement for my
4980 trusty old Thinkpad X41. Unfortunately I did not have much time to
4981 spend on it, but today the replacement finally arrived. I ended up
4982 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
4983 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
4984 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4985 this, it is installing what I hope will be a more final installation,
4986 with a encrypted hard drive to ensure any dope head stealing it end up
4987 with an expencive door stop.
</p
>
4989 <p
>I had a hard time trying to track down a good laptop, as my most
4990 important requirements (robust and with a good keyboard) are never
4991 listed in the feature list. But I did get good help from the search
4992 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
4993 allowed me to limit the list of interesting laptops based on my other
4994 requirements. A bit surprising that SSD disk are not disks, so I had
4995 to drop number of disks from my search parameters.
</p
>
4997 <p
>I am not quite convinced about the keyboard, as it is significantly
4998 wider than my old keyboard, and I have to stretch my hand a lot more
4999 to reach the edges. But the key response is fairly good and the
5000 individual key shape is fairly easy to handle, so I hope I will get
5001 used to it. My old X40 was starting to fail, and I really needed a
5002 new laptop now. :)
</p
>
5004 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5009 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5010 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5011 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5012 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5013 <description><p
>It annoys me when the computer fail to do automatically what it is
5014 perfectly capable of, and I have to do it manually to get things
5015 working. One such task is to find out what firmware packages are
5016 needed to get the hardware on my computer working. Most often this
5017 affect the wifi card, but some times it even affect the RAID
5018 controller or the ethernet card. Today I pushed version
0.4 of the
5019 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5020 including a new script isenkram-autoinstall-firmware handling the
5021 process of asking all the loaded kernel modules what firmware files
5022 they want, find debian packages providing these files and install the
5023 debian packages. Here is a test run on my laptop:
</p
>
5025 <p
><pre
>
5026 # isenkram-autoinstall-firmware
5027 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5028 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5029 info: locating packages with the requested firmware files
5030 info: Updating APT sources after adding non-free APT source
5031 info: trying to install firmware-ipw2x00
5034 Preconfiguring packages ...
5035 Selecting previously deselected package firmware-ipw2x00.
5036 (Reading database ...
259727 files and directories currently installed.)
5037 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5038 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5040 </pre
></p
>
5042 <p
>When all the requested firmware is present, a simple message is
5043 printed instead:
</p
>
5045 <p
><pre
>
5046 # isenkram-autoinstall-firmware
5047 info: did not find any firmware files requested by loaded kernel modules. exiting
5049 </pre
></p
>
5051 <p
>It could use some polish, but it is already working well and saving
5052 me some time when setting up new machines. :)
</p
>
5054 <p
>So, how does it work? It look at the set of currently loaded
5055 kernel modules, and look up each one of them using modinfo, to find
5056 the firmware files listed in the module meta-information. Next, it
5057 download the Contents file from a nearby APT mirror, and search for
5058 the firmware files in this file to locate the package with the
5059 requested firmware file. If the package is in the non-free section, a
5060 non-free APT source is added and the package is installed using
5061 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5064 <p
>I hope someone find time to implement a more polished version of
5065 this script as part of the hw-detect debian-installer module, to
5066 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5067 #
655507</a
>. There really is no need to insert USB sticks with
5068 firmware during a PXE install when the packages already are available
5069 from the nearby Debian mirror.
</p
>
5074 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5075 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5076 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5077 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5078 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5079 the screen just turn black when Linux boot, either during installation
5080 or on first boot from the hard disk. I
've seen it once in a while the
5081 last few years, but only recently understood the cause. I
've seen it
5082 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5083 The reason seem to be in the wiring of some laptops. The system to
5084 control the screen background light is inverted, so when Linux try to
5085 turn the brightness fully on, it end up turning it off instead. I do
5086 not know which Linux drivers are affected, but this post is about the
5087 i915 driver used by the
5088 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5089 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5091 <p
>The problem can be worked around two ways. Either by adding
5092 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5093 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5094 option when it load the i915 kernel module. On Debian and Ubuntu, it
5095 can be done by running these commands as root:
</p
>
5098 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5099 update-initramfs -u -k all
5102 <p
>Since March
2012 there is
5103 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5104 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5105 hardware have this problem, and get the driver to invert the
5106 brightness setting automatically. To use it, one need to add a row in
5107 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5108 intel_quirks array
</a
> in the driver source
5109 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5110 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5111 number (vendor number
8086 is assumed) and subdevice vendor and device
5114 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5115 -vvnn
</tt
> for the video card in question:
</p
>
5117 <p
><pre
>
5118 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5119 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5120 (rev
09) (prog-if
00 [VGA controller])
5121 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5122 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5123 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5124 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5125 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5127 Interrupt: pin A routed to IRQ
42
5128 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5129 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5130 Region
4: I/O ports at
4000 [size=
64]
5131 Expansion ROM at
<unassigned
> [disabled]
5132 Capabilities:
<access denied
>
5133 Kernel driver in use: i915
5134 </pre
></p
>
5136 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5138 <p
><pre
>
5139 struct intel_quirk intel_quirks[] = {
5141 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5142 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5145 </pre
></p
>
5147 <p
>According to the kernel module instructions (as seen using
5148 <tt
>modinfo i915
</tt
>), information about hardware needing the
5149 invert_brightness flag should be sent to the
5150 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5151 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5152 developers. But my email about the laptop sent
2013-
06-
03 have not
5154 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5155 web archive for the mailing list
</a
>, so I suspect they do not accept
5156 emails from non-subscribers. Because of this, I sent my patch also to
5157 the Debian bug tracking system instead as
5158 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5159 sure the patch is not lost.
</p
>
5161 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5162 with this problem working properly with Linux. If you use Gnome, your
5163 worries should be over at this point. But if you use KDE, there is
5164 something in KDE ignoring the invert_brightness setting and turning on
5165 the screen during login. I
've reported it to Debian as
5166 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5167 have no idea yet how to figure out exactly what subsystem is doing
5168 this. Perhaps you can help? Perhaps you know what the Gnome
5169 developers did to handle this, and this can give a clue to the KDE
5170 developers? Or you know where in KDE the screen brightness is changed
5171 during login? If so, please update the BTS report (or get in touch if
5172 you do not know how to update BTS).
</p
>
5174 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5175 acpi_backlight=vendor, to disable ACPI backlight support completely,
5176 as the ACPI information on the machine is trash and it is better to
5177 leave it to the intel video driver to control the screen
5178 backlight.
</p
>
5183 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5184 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5185 <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>
5186 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5187 <description><p
>Two days ago, I asked
5188 <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
5189 I could install Linux on a Packard Bell EasyNote LV computer
5190 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5191 with the obstacles put in the way of Linux users on a laptop with UEFI
5192 and Windows
8.
</p
>
5194 <p
>I never found out if the cause of my problems were the use of UEFI
5195 secure booting or fast boot. I suspect fast boot was the problem,
5196 causing the firmware to boot directly from HD without considering any
5197 key presses and alternative devices, but do not know UEFI settings
5198 enough to tell.
</p
>
5200 <p
>There is no way to install Linux on the machine in question without
5201 opening the box and disconnecting the hard drive! This is as far as I
5202 can tell, the only way to get access to the firmware setup menu
5203 without accepting the Windows
8 license agreement. I am told (and
5204 found description on how to) that it is possible to configure the
5205 firmware setup once booted into Windows
8. But as I believe the terms
5206 of that agreement are completely unacceptable, accepting the license
5207 was never an alternative. I do not enter agreements I do not intend
5208 to follow.
</p
>
5210 <p
>I feared I had to return the laptops and ask for a refund, and
5211 waste many hours on this, but luckily there was a way to get it to
5212 work. But I would not recommend it to anyone planning to run Linux on
5213 it, and I have become sceptical to Windows
8 certified laptops. Is
5214 this the way Linux will be forced out of the market place, by making
5215 it close to impossible for
"normal
" users to install Linux without
5216 accepting the Microsoft Windows license terms? Or at least not
5217 without risking to loose the warranty?
</p
>
5219 <p
>I
've updated the
5220 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5221 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5222 do not have to struggle as much as I did to get Linux into the
5225 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5226 Michael Tokarev and others for feedback and ideas.
</p
>
5231 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5232 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5233 <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>
5234 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5235 <description><p
>I
've run into quite a problem the last few days. I bought three
5236 new laptops for my parents and a few others. I bought Packard Bell
5237 Easynote LV to run Kubuntu on and use as their home computer. But I
5238 am completely unable to figure out how to install Linux on it. The
5239 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5240 instead of a BIOS to boot.
</p
>
5242 <p
>The problem is that I am unable to get it to PXE boot, and unable
5243 to get it to boot the Linux installer from my USB stick. I have yet
5244 to try the DVD install, and still hope it will work. when I turn on
5245 the computer, there is no information on what buttons to press to get
5246 the normal boot menu. I expect to get some boot menu to select PXE or
5247 USB stick booting. When booting, it first ask for the language to
5248 use, then for some regional settings, and finally if I will accept the
5249 Windows
8 terms of use. As these terms are completely unacceptable to
5250 me, I have no other choice but to turn off the computer and try again
5251 to get it to boot the Linux installer.
</p
>
5253 <p
>I have gathered my findings so far on a Linlap page about the
5254 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5255 EasyNote LV
</a
> model. If you have any idea how to get Linux
5256 installed on this machine, please get in touch or update that wiki
5257 page. If I can
't find a way to install Linux, I will have to return
5258 the laptop to the seller and find another machine for my parents.
</p
>
5260 <p
>I wonder, is this the way Linux will be forced out of the market
5261 using UEFI and
"secure boot
" by making it impossible to install Linux
5262 on new Laptops?
</p
>
5267 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5268 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5270 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5271 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5272 an operating system based on Debian intended for use in schools. It
5273 contain a turn-key solution for the computer network provided to
5274 pupils in the primary schools. It provide both the central server,
5275 network boot servers and desktop environments with heaps of
5276 educational software. The project was founded almost
12 years ago,
5277 2001-
07-
02. If you want to support the project, which is in need for
5278 cash to fund developer gatherings and other project related activity,
5279 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5280 donate some money
</a
>.
5282 <p
>A topic that come up again and again on the Debian Edu mailing
5283 lists and elsewhere, is the question on how to transform a Debian or
5284 Ubuntu installation into a Debian Edu installation. It isn
't very
5285 hard, and last week I wrote a script to replicate the steps done by
5286 the Debian Edu installer.
</p
>
5288 <p
>The script,
5289 <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/
>
5290 in the debian-edu-config package, will go through these six steps and
5291 transform an existing Debian Wheezy or Ubuntu (untested) installation
5292 into a Debian Edu Workstation:
</p
>
5296 <li
>Add skolelinux related APT sources.
</li
>
5297 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5298 <li
>Install debian-edu-install to load preseeding values and pull in
5299 our configuration.
</li
>
5300 <li
>Preseed debconf database with profile setup in
5301 /etc/debian-edu/config, and run tasksel to install packages
5302 according to the profile specified in the config above,
5303 overriding some of the Debian automation machinery.
</li
>
5304 <li
>Run debian-edu-cfengine-D installation to configure everything
5305 that could not be done using preseeding.
</li
>
5306 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5310 <p
>There are some steps in the Debian Edu installation that can not be
5311 replicated like this. Disk partitioning and LVM setup, for example.
5312 So this script just assume there is enough disk space to install all
5313 the needed packages.
</p
>
5315 <p
>The script was created to help a Debian Edu student working on
5316 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5317 Debian Edu client, and using it he can take the existing
5318 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5319 transform it into a fully functioning Debian Edu Workstation (or
5320 Roaming Workstation, or whatever :).
</p
>
5322 <p
>The default setting in the script is to create a KDE Workstation.
5323 If a LXDE based Roaming workstation is wanted instead, modify the
5324 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5326 <p
><pre
>
5327 PROFILE=
"Roaming-Workstation
"
5328 DESKTOP=
"lxde
"
5329 </pre
></p
>
5331 <p
>The script could even become useful to set up Debian Edu servers in
5332 the cloud, by starting with a virtual Debian installation at some
5333 virtual hosting service and setting up all the services on first
5339 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5340 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5342 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5343 <description><P
>In January,
5344 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5345 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5346 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5347 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5348 marvellous construction system from Denmark. We also created
5349 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5350 a place to take notes and write down our plans and hopes. And several
5351 people showed up to help. I was very happy to see the effect of my
5352 call. Since the small start, we have a debtags tag
5353 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5354 tag for LEGO related packages, and now count
10 packages related to
5355 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5357 <p
><table
>
5358 <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
>
5359 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5360 <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
>
5361 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5362 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5363 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5364 <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
>
5365 <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
>
5366 <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
>
5367 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5368 </table
></p
>
5370 <p
>Some of these are available in Wheezy, and all but one are
5371 currently available in Jessie/testing. leocad is so far only
5372 available in experimental.
</p
>
5374 <p
>If you care about LEGO in Debian, please join us on IRC and help
5375 adding the rest of the great free software tools available on Linux
5376 for LEGO designers.
</p
>
5381 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5382 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5383 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5384 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5385 <description><p
>When I woke up this morning, I was very happy to see that the
5386 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5387 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5388 Debian release, and I expect to move my machines at home over to it fairly
5391 <p
>The new debian release contain heaps of new stuff, and one program
5392 in particular make me very happy to see included. The
5393 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5394 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5395 included for the first time. Alongside similar programs like
5396 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5397 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5398 it allow for visual programming where syntax errors can not happen,
5399 and a friendly programming environment for learning to control the
5400 computer. Scratch will also be included in the next release of Debian
5403 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5404 Edu/Skolelinux release too. The
5405 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5406 alpha release
</a
> went out last week, and the next should soon
5412 <title>Isenkram
0.2 finally in the Debian archive
</title>
5413 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5414 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5415 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5416 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5417 package
</a
> finally made it into the archive, after lingering in NEW
5418 for many months. I uploaded it to the Debian experimental suite
5419 2013-
01-
27, and today it was accepted into the archive.
</p
>
5421 <p
>Isenkram is a system for suggesting to users what packages to
5422 install to work with a pluggable hardware device. The suggestion pop
5423 up when the device is plugged in. For example if a Lego Mindstorm NXT
5424 is inserted, it will suggest to install the program needed to program
5425 the NXT controller. Give it a go, and report bugs and suggestions to
5431 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5432 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5433 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5434 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5435 <description><p
>My
5436 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5437 bitcoin related blog post
</a
> mentioned that the new
5438 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5439 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5440 2013-
01-
19, and have been available in unstable since then. It was
5441 automatically copied to Ubuntu, and is available in their Raring
5442 version too.
</p
>
5444 <p
>But there is a strange problem with the build that block this new
5445 version from being available on the i386 and kfreebsd-i386
5446 architectures. For some strange reason, the autobuilders in Debian
5447 for these architectures fail to run the test suite on these
5448 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5449 We are so far unable to reproduce it when building it manually, and
5450 no-one have been able to propose a fix. If you got an idea what is
5451 failing, please let us know via the BTS.
</p
>
5453 <p
>One feature that is annoying me with of the bitcoin client, because
5454 I often run low on disk space, is the fact that the client will exit
5455 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5456 #
696715</a
>). So make sure you have enough disk space when you run
5459 <p
>As usual, if you use bitcoin and want to show your support of my
5460 activities, please send Bitcoin donations to my address
5461 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5466 <title>Welcome to the world, Isenkram!
</title>
5467 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5468 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5469 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5470 <description><p
>Yesterday, I
5471 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5472 for testers
</a
> for my prototype for making Debian better at handling
5473 pluggable hardware devices, which I
5474 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5475 out to create
</a
> earlier this month. Several valuable testers showed
5476 up, and caused me to really want to to open up the development to more
5477 people. But before I did this, I want to come up with a sensible name
5478 for this project. Today I finally decided on a new name, and I have
5479 renamed the project from hw-support-handler to this new name. In the
5480 process, I moved the source to git and made it available as a
5481 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5482 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5483 To fetch and build the latest version of the source, use
</p
>
5486 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5487 cd isenkram
&& git-buildpackage -us -uc
5490 <p
>I have not yet adjusted all files to use the new name yet. If you
5491 want to hack on the source or improve the package, please go ahead.
5492 But please talk to me first on IRC or via email before you do major
5493 changes, to make sure we do not step on each others toes. :)
</p
>
5495 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5496 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5497 stuff, in other words. I
've been told it is the Norwegian variant of
5498 the German word eisenkram, for those that are familiar with that
5501 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5502 instructions, to avoid confusing people with an error from the signing
5505 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5506 clone argument to avoid the need for authentication.
</p
>
5511 <title>First prototype ready making hardware easier to use in Debian
</title>
5512 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5514 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5515 <description><p
>Early this month I set out to try to
5516 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5517 the Debian support for pluggable hardware devices
</a
>. Now my
5518 prototype is working, and it is ready for a larger audience. To test
5520 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5521 from the Debian Edu subversion repository
</a
>, build and install the
5522 package. You might have to log out and in again activate the
5523 autostart script.
</p
>
5525 <p
>The design is simple:
</p
>
5529 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5530 hw-support-handlerd to start when the user log in.
</li
>
5532 <li
>This program listen for kernel events about new hardware (directly
5533 from the kernel like udev does), not using HAL dbus events as I
5534 initially did.
</li
>
5536 <li
>When new hardware is inserted, look up the hardware modalias in
5537 the APT database, a database
5538 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5539 via HTTP
</a
> and a database available as part of the package.
</li
>
5541 <li
>If a package is mapped to the hardware in question, the package
5542 isn
't installed yet and this is the first time the hardware was
5543 plugged in, show a desktop notification suggesting to install the
5544 package or packages.
</li
>
5546 <li
>If the user click on the
'install package now
' button, ask
5547 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5549 <li
>aptdaemon ask for root password or sudo password, and install the
5550 package while showing progress information in a window.
</li
>
5554 <p
>I still need to come up with a better name for the system. Here
5555 are some screen shots showing the prototype in action. First the
5556 notification, then the password request, and finally the request to
5557 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5559 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5560 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5561 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5562 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5563 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5565 <p
>The prototype still need to be improved with longer timeouts, but
5566 is already useful. The database of hardware to package mappings also
5567 need more work. It is currently compatible with the Ubuntu way of
5568 storing such information in the package control file, but could be
5569 changed to use other formats instead or in addition to the current
5570 method. I
've dropped the use of discover for this mapping, as the
5571 modalias approach is more flexible and easier to use on Linux as long
5572 as the Linux kernel expose its modalias strings directly.
</p
>
5574 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5575 here is the command required to check out and build the source: Use
5576 '<tt
>svn checkout
5577 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5578 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5579 devscripts package.
</p
>
5581 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5582 renamed to Isenkram and the source moved from the Debian Edu
5583 subversion repository to a Debian collab-maint git repository. See
5584 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5585 instructions
</a
> for details.
</p
>
5590 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5591 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5592 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5593 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5594 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5595 suddenly in bed. With a quiet whimper, it went completely quiet and
5596 black. The power button was no longer able to turn it on. It was a
5597 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5598 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5599 Compaq I had before that. Now I need to find a replacement. To keep
5600 going during Christmas, I moved the one year old SSD disk to my old
5601 X40 where it fitted (only one I had left that could use it), but it is
5602 not a durable solution.
5604 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5605 got a new one more than
10 years ago. It still holds true.:)
</p
>
5609 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5610 than A4).
</li
>
5611 <li
>Robust, it will be in my backpack every day.
</li
>
5612 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5613 <li
>Long battery life time. Preferable a week.
</li
>
5614 <li
>Internal WIFI network card.
</li
>
5615 <li
>Internal Twisted Pair network card.
</li
>
5616 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5617 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5618 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5620 <li
>Hardware supported by Debian Stable, ie the default kernel and
5621 X.org packages.
</li
>
5622 <li
>Quiet, preferably fan free (or at least not using the fan most of
5627 <p
>You will notice that there are no RAM and CPU requirements in the
5628 list. The reason is simply that the specifications on laptops the
5629 last
10-
15 years have been sufficient for my needs, and I have to look
5630 at other features to choose my laptop. But are there still made as
5631 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5632 robust, and Thinkpads seem to be heading in the wrong direction since
5633 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5634 still be useful.
</p
>
5636 <p
>Perhaps I should rethink my needs, and look for a pad with an
5637 external keyboard? I
'll have to check the
5638 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5639 well-supported laptops, or perhaps just buy one preinstalled from one
5640 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5641 Pre-loaded site
</a
>.
</p
>
5646 <title>How to find a browser plugin supporting a given MIME type
</title>
5647 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5648 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5649 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5650 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5651 install to get support for a given MIME type. Thanks to
5652 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5653 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5654 Unfortunately, not very many packages provide the needed meta
5655 information, Anyway, here is a small script to look up all browser
5656 plugin packages announcing ther MIME support using this specification:
</p
>
5662 def pkgs_handling_mimetype(mimetype):
5667 version = pkg.candidate
5669 version = pkg.installed
5672 record = version.record
5673 if not record.has_key(
'Npp-MimeType
'):
5675 mime_types = record[
'Npp-MimeType
'].split(
',
')
5676 for t in mime_types:
5677 t = t.rstrip().strip()
5679 thepkgs.append(pkg.name)
5681 mimetype =
"audio/ogg
"
5682 if
1 < len(sys.argv):
5683 mimetype = sys.argv[
1]
5684 print
"Browser plugin packages supporting %s:
" % mimetype
5685 for pkg in pkgs_handling_mimetype(mimetype):
5686 print
" %s
" %pkg
5689 <p
>It can be used like this to look up a given MIME type:
</p
>
5692 % ./apt-find-browserplug-for-mimetype
5693 Browser plugin packages supporting audio/ogg:
5695 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5696 Browser plugin packages supporting application/x-shockwave-flash:
5697 browser-plugin-gnash
5701 <p
>In Ubuntu this mechanism is combined with support in the browser
5702 itself to query for plugins and propose to install the needed
5703 packages. It would be great if Debian supported such feature too. Is
5704 anyone working on adding it?
</p
>
5706 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5707 request for icweasel support for this feature is
5708 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5709 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5710 of manpower and wish for a different design is the reason thus feature
5711 is not yet in iceweasel from Debian.
</p
>
5716 <title>What is the most supported MIME type in Debian?
</title>
5717 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5718 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5719 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5720 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5721 proposal to add AppStream information to the Debian archive
</a
>, is a
5722 proposal to make it possible for a Desktop application to propose to
5723 the user some package to install to gain support for a given MIME
5724 type, font, library etc. that is currently missing. With such
5725 mechanism in place, it would be possible for the desktop to
5726 automatically propose and install leocad if some LDraw file is
5727 downloaded by the browser.
</p
>
5729 <p
>To get some idea about the current content of the archive, I decided
5730 to write a simple program to extract all .desktop files from the
5731 Debian archive and look up the claimed MIME support there. The result
5733 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5734 site
</a
>. Using the collected information, it become possible to
5735 answer the question in the title. Here are the
20 most supported MIME
5736 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5737 The complete list is available from the link above.
</p
>
5739 <p
><strong
>Debian Stable:
</strong
></p
>
5743 ----- -----------------------
5759 18 application/x-ogg
5766 <p
><strong
>Debian Testing:
</strong
></p
>
5770 ----- -----------------------
5786 18 application/x-ogg
5793 <p
><strong
>Debian Unstable:
</strong
></p
>
5797 ----- -----------------------
5814 18 application/x-ogg
5820 <p
>I am told that PackageKit can provide an API to access the kind of
5821 information mentioned in DEP-
11. I have not yet had time to look at
5822 it, but hope the PackageKit people in Debian are on top of these
5825 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5826 discovering a typo in my script.
</p
>
5831 <title>Using modalias info to find packages handling my hardware
</title>
5832 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5833 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5834 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5835 <description><p
>Yesterday, I wrote about the
5836 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5837 values provided by the Linux kernel
</a
> following my hope for
5838 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5839 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5840 modalias values attached to package names can be used to map packages
5841 to hardware. This allow the system to look up and suggest relevant
5842 packages when I plug in some new hardware into my machine, and replace
5843 discover and discover-data as the database used to map hardware to
5846 <p
>I create a modaliases file with entries like the following,
5847 containing package name, kernel module name (if relevant, otherwise
5848 the package name) and globs matching the relevant hardware
5851 <p
><blockquote
>
5852 Package: package-name
5853 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
5854 </blockquote
></p
>
5856 <p
>It is fairly trivial to write code to find the relevant packages
5857 for a given modalias value using this file.
</p
>
5859 <p
>An entry like this would suggest the video and picture application
5860 cheese for many USB web cameras (interface bus class
0E01):
</p
>
5862 <p
><blockquote
>
5864 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
5865 </blockquote
></p
>
5867 <p
>An entry like this would suggest the pcmciautils package when a
5868 CardBus bridge (bus class
0607) PCI device is present:
</p
>
5870 <p
><blockquote
>
5871 Package: pcmciautils
5872 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
5873 </blockquote
></p
>
5875 <p
>An entry like this would suggest the package colorhug-client when
5876 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
5878 <p
><blockquote
>
5879 Package: colorhug-client
5880 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
5881 </blockquote
></p
>
5883 <p
>I believe the format is compatible with the format of the Packages
5884 file in the Debian archive. Ubuntu already uses their Packages file
5885 to store their mappings from packages to hardware.
</p
>
5887 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
5888 announce the hardware it support in a way my prototype understand.
5889 This allow those publishing packages in an APT source outside the
5890 Debian archive as well as those backporting packages to make sure the
5891 hardware mapping are included in the package meta information. I
've
5892 tested such header in the pymissile package, and its modalias mapping
5893 is working as it should with my prototype. It even made it to Ubuntu
5896 <p
>To test if it was possible to look up supported hardware using only
5897 the shell tools available in the Debian installer, I wrote a shell
5898 implementation of the lookup code. The idea is to create files for
5899 each modalias and let the shell do the matching. Please check out and
5901 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
5902 shell script. It run without any extra dependencies and fetch the
5903 hardware mappings from the Debian archive and the subversion
5904 repository where I currently work on my prototype.
</p
>
5906 <p
>When I use it on a machine with a yubikey inserted, it suggest to
5907 install yubikey-personalization:
</p
>
5909 <p
><blockquote
>
5910 % ./hw-support-lookup
5911 <br
>yubikey-personalization
5913 </blockquote
></p
>
5915 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
5916 propose to install the pcmciautils package:
</p
>
5918 <p
><blockquote
>
5919 % ./hw-support-lookup
5920 <br
>pcmciautils
5922 </blockquote
></p
>
5924 <p
>If you know of any hardware-package mapping that should be added to
5925 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
5926 database
</a
>, please tell me about it.
</p
>
5928 <p
>It could be possible to generate several of the mappings between
5929 packages and hardware. One source would be to look at packages with
5930 kernel modules, ie packages with *.ko files in /lib/modules/, and
5931 extract their modalias information. Another would be to look at
5932 packages with udev rules, ie packages with files in
5933 /lib/udev/rules.d/, and extract their vendor/model information to
5934 generate a modalias matching rule. I have not tested any of these to
5935 see if it work.
</p
>
5937 <p
>If you want to help implementing a system to let us propose what
5938 packages to install when new hardware is plugged into a Debian
5939 machine, please send me an email or talk to me on
5940 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
5945 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
5946 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
5947 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
5948 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
5949 <description><p
>While looking into how to look up Debian packages based on hardware
5950 information, to find the packages that support a given piece of
5951 hardware, I refreshed my memory regarding modalias values, and decided
5952 to document the details. Here are my findings so far, also available
5954 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
5955 Debian Edu subversion repository
</a
>:
5957 <p
><strong
>Modalias decoded
</strong
></p
>
5959 <p
>This document try to explain what the different types of modalias
5960 values stands for. It is in part based on information from
5961 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
5962 &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;,
5963 &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
5964 &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;.
5966 <p
>The modalias entries for a given Linux machine can be found using
5967 this shell script:
</p
>
5970 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
5973 <p
>The supported modalias globs for a given kernel module can be found
5974 using modinfo:
</p
>
5977 % /sbin/modinfo psmouse | grep alias:
5978 alias: serio:ty05pr*id*ex*
5979 alias: serio:ty01pr*id*ex*
5983 <p
><strong
>PCI subtype
</strong
></p
>
5985 <p
>A typical PCI entry can look like this. This is an Intel Host
5986 Bridge memory controller:
</p
>
5988 <p
><blockquote
>
5989 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5990 </blockquote
></p
>
5992 <p
>This represent these values:
</p
>
5997 sv
00001028 (subvendor)
5998 sd
000001AD (subdevice)
6000 sc
00 (bus subclass)
6004 <p
>The vendor/device values are the same values outputted from
'lspci
6005 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6006 0600. The
0600 class is a host bridge. Other useful bus values are
6007 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6009 <p
>Not sure how to figure out the interface value, nor what it
6012 <p
><strong
>USB subtype
</strong
></p
>
6014 <p
>Some typical USB entries can look like this. This is an internal
6015 USB hub in a laptop:
</p
>
6017 <p
><blockquote
>
6018 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6019 </blockquote
></p
>
6021 <p
>Here is the values included in this alias:
</p
>
6024 v
1D6B (device vendor)
6025 p
0001 (device product)
6027 dc
09 (device class)
6028 dsc
00 (device subclass)
6029 dp
00 (device protocol)
6030 ic
09 (interface class)
6031 isc
00 (interface subclass)
6032 ip
00 (interface protocol)
6035 <p
>The
0900 device class/subclass means hub. Some times the relevant
6036 class is in the interface class section. For a simple USB web camera,
6037 these alias entries show up:
</p
>
6039 <p
><blockquote
>
6040 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6041 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6042 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6043 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6044 </blockquote
></p
>
6046 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6047 camera),
0101 is audio control device and
0102 is audio streaming (aka
6048 microphone). Thus this is a camera with microphone included.
</p
>
6050 <p
><strong
>ACPI subtype
</strong
></p
>
6052 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6053 receiver in a Thinkpad X40:
</p
>
6055 <p
><blockquote
>
6056 acpi:IBM0071:PNP0511:
6057 </blockquote
></p
>
6059 <p
>The values between the colons are IDs.
</p
>
6061 <p
><strong
>DMI subtype
</strong
></p
>
6063 <p
>The DMI table contain lots of information about the computer case
6064 and model. This is an entry for a IBM Thinkpad X40, fetched from
6065 /sys/devices/virtual/dmi/id/modalias:
</p
>
6067 <p
><blockquote
>
6068 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6069 </blockquote
></p
>
6071 <p
>The values present are
</p
>
6074 bvn IBM (BIOS vendor)
6075 bvr
1UETB
6WW(
1.66) (BIOS version)
6076 bd
06/
15/
2005 (BIOS date)
6077 svn IBM (system vendor)
6078 pn
2371H4G (product name)
6079 pvr ThinkPadX40 (product version)
6080 rvn IBM (board vendor)
6081 rn
2371H4G (board name)
6082 rvr NotAvailable (board version)
6083 cvn IBM (chassis vendor)
6084 ct
10 (chassis type)
6085 cvr NotAvailable (chassis version)
6088 <p
>The chassis type
10 is Notebook. Other interesting values can be
6089 found in the dmidecode source:
</p
>
6093 4 Low Profile Desktop
6106 17 Main Server Chassis
6107 18 Expansion Chassis
6109 20 Bus Expansion Chassis
6110 21 Peripheral Chassis
6112 23 Rack Mount Chassis
6121 <p
>The chassis type values are not always accurately set in the DMI
6122 table. For example my home server is a tower, but the DMI modalias
6123 claim it is a desktop.
</p
>
6125 <p
><strong
>SerIO subtype
</strong
></p
>
6127 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6128 test machine:
</p
>
6130 <p
><blockquote
>
6131 serio:ty01pr00id00ex00
6132 </blockquote
></p
>
6134 <p
>The values present are
</p
>
6143 <p
>This type is supported by the psmouse driver. I am not sure what
6144 the valid values are.
</p
>
6146 <p
><strong
>Other subtypes
</strong
></p
>
6148 <p
>There are heaps of other modalias subtypes according to
6149 file2alias.c. There is the rest of the list from that source: amba,
6150 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6151 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6152 vmbus, x86cpu and zorro. I did not spend time documenting all of
6153 these, as they do not seem relevant for my intended use with mapping
6154 hardware to packages when new stuff is inserted during run time.
</p
>
6156 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6158 <p
>To check which kernel modules provide support for a given modalias,
6159 one can use the following shell script:
</p
>
6162 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6163 echo
"$id
" ; \
6164 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6168 <p
>The output can look like this (only the first few entries as the
6169 list is very long on my test machine):
</p
>
6173 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6175 FATAL: Module acpi:device: not found.
6177 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6178 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6179 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6180 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6181 acpi:IBM0071:PNP0511:
6182 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6183 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6184 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6188 <p
>If you want to help implementing a system to let us propose what
6189 packages to install when new hardware is plugged into a Debian
6190 machine, please send me an email or talk to me on
6191 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6193 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6194 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6195 in /sys/ with space in them.
</p
>
6200 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6201 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6202 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6203 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6204 <description><p
>As part of my investigation on how to improve the support in Debian
6205 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6206 Launcher and updated the Debian package
6207 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6208 sure udev will fix the device permissions when it is plugged in. I
6209 also added a
"Modaliases
" header to test it in the Debian archive and
6210 hopefully make the package be proposed by jockey in Ubuntu when a user
6211 plug in his rocket launcher. In the process I moved the source to a
6212 git repository under collab-maint, to make it easier for any DD to
6213 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6214 is not very active, but the software still work for me even after five
6215 years of relative silence. The new git repository is not listed in
6216 the uploaded package yet, because I want to test the other changes a
6217 bit more before I upload the new version. If you want to check out
6218 the new version with a .desktop file included, visit the
6219 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6220 view
</a
> or use
"<tt
>git clone
6221 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6226 <title>Lets make hardware dongles easier to use in Debian
</title>
6227 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6229 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6230 <description><p
>One thing that annoys me with Debian and Linux distributions in
6231 general, is that there is a great package management system with the
6232 ability to automatically install software packages by downloading them
6233 from the distribution mirrors, but no way to get it to automatically
6234 install the packages I need to use the hardware I plug into my
6235 machine. Even if the package to use it is easily available from the
6236 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6237 suggest to automatically install the python-nxt, nbc and t2n packages
6238 I need to talk to it. When I plug in a Yubikey, it could propose the
6239 yubikey-personalization package. The information required to do this
6240 is available, but no-one have pulled all the pieces together.
</p
>
6242 <p
>Some years ago, I proposed to
6243 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6244 the discover subsystem to implement this
</a
>. The idea is fairly
6249 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6250 starting when a user log in.
</li
>
6252 <li
>Set this program up to listen for kernel events emitted when new
6253 hardware is inserted into the computer.
</li
>
6255 <li
>When new hardware is inserted, look up the hardware ID in a
6256 database mapping to packages, and take note of any non-installed
6257 packages.
</li
>
6259 <li
>Show a message to the user proposing to install the discovered
6260 package, and make it easy to install it.
</li
>
6264 <p
>I am not sure what the best way to implement this is, but my
6265 initial idea was to use dbus events to discover new hardware, the
6266 discover database to find packages and
6267 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6270 <p
>Yesterday, I found time to try to implement this idea, and the
6271 draft package is now checked into
6272 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6273 Debian Edu subversion repository
</a
>. In the process, I updated the
6274 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6275 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6276 the relevant packages in Debian, and uploaded a new version
6277 2.2013.01.09 to unstable. I also discovered that the current
6278 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6279 package in Debian no longer discovered any USB devices, because
6280 /proc/bus/usb/devices is no longer present. I ported it to use
6281 libusb as a fall back option to get it working. The fixed package
6282 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6283 because of the freeze).
</p
>
6285 <p
>With this prototype in place, I can insert my Yubikey, and get this
6286 desktop notification to show up (only once, the first time it is
6287 inserted):
</p
>
6289 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6291 <p
>For this prototype to be really useful, some way to automatically
6292 install the proposed packages by pressing the
"Please install
6293 program(s)
" button should to be implemented.
</p
>
6295 <p
>If this idea seem useful to you, and you want to help make it
6296 happen, please help me update the discover-data database with mappings
6297 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6298 list the package you would like to have installed when a given
6299 hardware device is inserted into your computer, and report bugs using
6300 reportbug if it isn
't. Or, if you know of a better way to provide
6301 such mapping, please let me know.
</p
>
6303 <p
>This prototype need more work, and there are several questions that
6304 should be considered before it is ready for production use. Is dbus
6305 the correct way to detect new hardware? At the moment I look for HAL
6306 dbus events on the system bus, because that is the events I could see
6307 on my Debian Squeeze KDE desktop. Are there better events to use?
6308 How should the user be notified? Is the desktop notification
6309 mechanism the best option, or should the background daemon raise a
6310 popup instead? How should packages be installed? When should they
6311 not be installed?
</p
>
6313 <p
>If you want to help getting such feature implemented in Debian,
6314 please send me an email. :)
</p
>
6319 <title>New IRC channel for LEGO designers using Debian
</title>
6320 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6321 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6322 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6323 <description><p
>During Christmas, I have worked a bit on the Debian support for
6324 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6325 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6326 discovered I had to build all the tools myself because none were
6327 already in Debian Squeeze. If Debian support for LEGO is something
6328 you care about, please join me on the IRC channel
6329 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6330 irc.debian.org). There is a lot that could be done to improve the
6331 Debian support for LEGO designers. For example both CAD software
6332 and Mindstorm compilers are missing. :)
</p
>
6334 <p
>Update
2012-
01-
03: A
6335 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6336 including links to Lego related packages is now available.
</p
>
6341 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6342 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6343 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6344 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6345 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6346 year! I hope next year will prove to be a good year.
</p
>
6348 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6349 decentralised
"currency
" that allow people to transfer bitcoins
6350 between each other with minimal overhead, is a very interesting
6351 experiment. And as I wrote a few days ago, the bitcoin situation in
6352 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6353 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6354 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6355 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6356 for one of the ftpmasters to approve the new bitcoin-qt package
6359 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6360 team in Debian, you can easily test the package in Debian Squeeze
6361 using the following steps to get a set of working packages:
</p
>
6363 <blockquote
><pre
>
6364 git clone git://git.debian.org/git/collab-maint/bitcoin
6366 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6367 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6368 </pre
></blockquote
>
6370 <p
>You might have to install some build dependencies as well. The
6371 list of commands should give you two packages, bitcoind and
6372 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6373 client will download the complete set of bitcoin
"blocks
", which need
6374 around
5.6 GiB of data on my machine at the moment. Make sure your
6375 ~/.bitcoin/ directory have lots of spare room if you want to download
6376 all the blocks. The client will warn if the disk is getting full, so
6377 there is not really a problem if you got too little room, but you will
6378 not be able to get all the features out of the client.
</p
>
6380 <p
>As usual, if you use bitcoin and want to show your support of my
6381 activities, please send Bitcoin donations to my address
6382 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6387 <title>A word on bitcoin support in Debian
</title>
6388 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6390 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6391 <description><p
>It has been a while since I wrote about
6392 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6393 peer-to-peer based crypto-currency, and the reason is simply that I
6394 have been busy elsewhere. But two days ago, I started looking at the
6395 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6396 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6397 is now maintained by a
6398 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6399 people
</a
>, and the grunt work had already been done by this team. We
6400 owe a huge thank you to all these team members. :)
6401 But I was sad to discover that the bitcoin client is missing in
6402 Wheezy. It is only available in Sid (and an outdated client from
6403 backports). The client had several RC bugs registered in BTS blocking
6404 it from entering testing. To try to help the team and improve the
6405 situation, I spent some time providing patches and triaging the bug
6406 reports. I also had a look at the bitcoin package available from Matt
6408 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6409 Ubuntu
</a
>, and moved the useful pieces from that version into the
6410 Debian package.
</p
>
6412 <p
>After checking with the main package maintainer Jonas Smedegaard on
6413 IRC, I pushed several patches into the collab-maint git repository to
6414 improve the package. It now contains fixes for the RC issues (not from
6415 me, but fixed by Scott Howard), build rules for a Qt GUI client
6416 package, konqueror support for the bitcoin: URI and bash completion
6417 setup. As I work on Debian Squeeze, I also created
6418 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6419 patch to backport
</a
> the latest version. Jonas is going to look at
6420 it and try to integrate it into the git repository before uploading a
6421 new version to unstable.
6423 <p
>I would very much like bitcoin to succeed, to get rid of the
6424 centralized control currently exercised in the monetary system. I
6425 find it completely unacceptable that the USA government is collecting
6426 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6427 that the major credit card companies can block legal money
6428 transactions to Wikileaks. But for bitcoin to succeed, more people
6429 need to use bitcoins, and more people need to accept bitcoins when
6430 they sell products and services. Improving the bitcoin support in
6431 Debian is a small step in the right direction, but not enough.
6432 Unfortunately the user experience when browsing the web and wanting to
6433 pay with bitcoin is still not very good. The bitcoin: URI is a step
6434 in the right direction, but need to work in most or every browser in
6435 use. Also the bitcoin-qt client is too heavy to fire up to do a
6436 quick transaction. I believe there are other clients available, but
6437 have not tested them.
</p
>
6440 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6441 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6442 I received
20.15 BTC so far on the address I provided in my blog two
6443 years ago, as can be
6444 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6445 on the blockexplorer service
</a
>. Thank you everyone for your
6446 donation. The blockexplorer service demonstrates quite well that
6447 bitcoin is not quite anonymous and untracked. :) I wonder if the
6448 number of users have gone up since then. If you use bitcoin and want
6449 to show your support of my activity, please send Bitcoin donations to
6450 the same address as last time,
6451 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6456 <title>Git repository for song book for Computer Scientists
</title>
6457 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6458 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6459 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6460 <description><p
>As I
6461 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6462 this summer
</a
>, I have created a Computer Science song book a few
6463 years ago, and today I finally found time to create a public
6464 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6465 repository for the project
</a
>.
</p
>
6467 <p
>If you want to help out, please clone the source and submit patches
6468 to the HTML version. To generate the PDF and PostScript version,
6469 please use prince XML, or let me know about a useful free software
6470 processor capable of creating a good looking PDF from the HTML.
</p
>
6472 <p
>Want to sing? You can still find the song book in HTML, PDF and
6473 PostScript formats at
6474 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6475 Science Songbook
</a
>.
</p
>
6480 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6481 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6482 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6483 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6484 <description><p
>I dag fyller
6485 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6486 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6487 si gratulerer med dagen, Debian!
</p
>
6492 <title>Song book for Computer Scientists
</title>
6493 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6494 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6495 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6496 <description><p
>Many years ago, while studying Computer Science at the
6497 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6498 collecting computer related songs for use at parties. The original
6499 version was written in LaTeX, but a few years ago I got help from
6500 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6501 while keeping the ability to create a nice book in PDF format. I have
6502 not had time to maintain the book for a while now, and guess I should
6503 put it up on some public version control repository where others can
6504 help me extend and update the book. If anyone is volunteering to help
6505 me with this, send me an email. Also let me know if there are songs
6506 missing in my book.
</p
>
6508 <p
>I have not mentioned the book on my blog so far, and it occured to
6509 me today that I really should let all my readers share the joys of
6510 singing out load about programming, computers and computer networks.
6511 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6512 12</a
> is about to start (and I am not going). Want to sing? Check
6513 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6514 Computer Science Songbook
</a
>.
6519 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6520 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6522 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6523 <description><p
>At work we have heaps of servers. I believe the total count is
6524 around
1000 at the moment. To be able to get help from the vendors
6525 when something go wrong, we want to keep the firmware on the servers
6526 up to date. If the firmware isn
't the latest and greatest, the
6527 vendors typically refuse to start debugging any problems until the
6528 firmware is upgraded. So before every reboot, we want to upgrade the
6529 firmware, and we would really like everyone handling servers at the
6530 university to do this themselves when they plan to reboot a machine.
6531 For that to happen we at the unix server admin group need to provide
6532 the tools to do so.
</p
>
6534 <p
>To make firmware upgrading easier, I am working on a script to
6535 fetch and install the latest firmware for the servers we got. Most of
6536 our hardware are from Dell and HP, so I have focused on these servers
6537 so far. This blog post is about the Dell part.
</P
>
6539 <p
>On the Dell FTP site I was lucky enough to find
6540 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6541 with firmware information for all
11th generation servers, listing
6542 which firmware should be used on a given model and where on the FTP
6543 site I can find it. Using a simple perl XML parser I can then
6544 download the shell scripts Dell provides to do firmware upgrades from
6545 within Linux and reboot when all the firmware is primed and ready to
6546 be activated on the first reboot.
</p
>
6548 <p
>This is the Dell related fragment of the perl code I am working on.
6549 Are there anyone working on similar tools for firmware upgrading all
6550 servers at a site? Please get in touch and lets share resources.
</p
>
6552 <p
><pre
>
6556 use File::Temp qw(tempdir);
6558 # Install needed RHEL packages if missing
6560 'XML::Simple
' =
> 'perl-XML-Simple
',
6562 for my $module (keys %rhelmodules) {
6563 eval
"use $module;
";
6565 my $pkg = $rhelmodules{$module};
6566 system(
"yum install -y $pkg
");
6567 eval
"use $module;
";
6571 my $errorsto =
'pere@hungry.com
';
6577 sub run_firmware_script {
6578 my ($opts, $script) = @_;
6580 print STDERR
"fail: missing script name\n
";
6583 print STDERR
"Running $script\n\n
";
6585 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6586 print STDERR
"success: firmware script ran succcessfully\n
";
6588 print STDERR
"fail: firmware script returned error\n
";
6592 sub run_firmware_scripts {
6593 my ($opts, @dirs) = @_;
6594 # Run firmware packages
6595 for my $dir (@dirs) {
6596 print STDERR
"info: Running scripts in $dir\n
";
6597 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6598 while (my $s = readdir $dh) {
6599 next if $s =~ m/^\.\.?/;
6600 run_firmware_script($opts,
"$dir/$s
");
6608 print STDERR
"info: Downloading $url\n
";
6609 system(
"wget --quiet \
"$url\
"");
6614 my $product = `dmidecode -s system-product-name`;
6617 if ($product =~ m/PowerEdge/) {
6619 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6620 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6622 my $tmpdir = tempdir(
6626 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6627 system(
'gunzip Catalog.xml.gz
');
6628 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6629 # -q is quiet, disabling interactivity and reducing console output
6630 my $fwopts =
"-q
";
6632 for my $url (@paths) {
6633 fetch_dell_fw($url);
6635 run_firmware_scripts($fwopts, $tmpdir);
6637 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6638 print STDERR
"error: Please report to $errorsto.\n
";
6642 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6643 print STDERR
"error: Please report to $errorsto.\n
";
6649 my $url =
"ftp://ftp.us.dell.com/$path
";
6653 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6654 # firmware packages to download from Dell. Only work for Linux
6655 # machines and
11th generation Dell servers.
6656 sub fetch_dell_fw_list {
6657 my $filename = shift;
6659 my $product = `dmidecode -s system-product-name`;
6661 my ($mybrand, $mymodel) = split(/\s+/, $product);
6663 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6665 my $xml = XMLin($filename);
6667 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6668 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6669 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6671 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6672 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6674 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6676 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6678 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6681 for my $component (@{$xml-
>{SoftwareComponent}}) {
6682 my $componenttype = $component-
>{ComponentType}-
>{value};
6684 # Drop application packages, only firmware and BIOS
6685 next if
'APAC
' eq $componenttype;
6687 my $cpath = $component-
>{path};
6688 for my $path (@paths) {
6689 if ($cpath =~ m%/$path$%) {
6690 push(@paths, $cpath);
6698 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6699 it could work on other platforms with some tweaking. Anyone know a
6700 index like Catalog.xml is available from HP for HP servers? At the
6701 moment I maintain a similar list manually and it is quickly getting
6707 <title>How is booting into runlevel
1 different from single user boots?
</title>
6708 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6710 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6711 <description><p
>Wouter Verhelst have some
6712 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6713 comments and opinions
</a
> on my blog post on
6714 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6715 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6716 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6717 default KDE desktop in Debian
</a
>. I only have time to address one
6718 small piece of his comment now, and though it best to address the
6719 misunderstanding he bring forward:
</p
>
6721 <p
><blockquote
>
6722 Currently, a system admin has four options: [...] boot to a
6723 single-user system (by adding
'single
' to the kernel command line;
6724 this runs rcS and rc1 scripts)
6725 </blockquote
></p
>
6727 <p
>This make me believe Wouter believe booting into single user mode
6728 and booting into runlevel
1 is the same. I am not surprised he
6729 believe this, because it would make sense and is a quite sensible
6730 thing to believe. But because the boot in Debian is slightly broken,
6731 runlevel
1 do not work properly and it isn
't the same as single user
6732 mode. I
'll try to explain what is actually happing, but it is a bit
6733 hard to explain.
</p
>
6735 <p
>Single user mode is defined like this in /etc/inittab:
6736 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6737 executed in single user mode is sulogin. Single user mode is a boot
6738 state
"between
" the runlevels, and when booting into single user mode,
6739 only the scripts in /etc/rcS.d/ are executed before the init process
6740 enters the single user state. When switching to runlevel
1, the state
6741 is in fact not ending in runlevel
1, but it passes through runlevel
1
6742 and end up in the single user mode (see /etc/rc1.d/S03single, which
6743 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6744 1. It is confusing that the
'S
' (single user) init mode is not the
6745 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6748 <p
>This summary might make it clearer. When booting for the first
6749 time into single user mode, the following commands are executed:
6750 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6751 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6752 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6753 trying to continue after visiting single user mode. Not all services
6754 are started again as they should, causing the machine to end up in an
6755 unpredicatble state. This is why Debian admins recommend rebooting
6756 after visiting single user mode.
</p
>
6758 <p
>A similar problem with runlevel
1 is caused by the amount of
6759 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6760 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6761 stopped when passing through the scripts in /etc/rc1.d/, and not
6762 started again when switching away from runlevel
1 to the runlevels
6763 2-
5. I believe the problem is best fixed by moving all the scripts
6764 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6765 functioning single user mode during boot.
</p
>
6767 <p
>I have spent several years investigating the Debian boot system,
6768 and discovered this problem a few years ago. I suspect it originates
6769 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6774 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6775 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6777 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6778 <description><p
>In the Debian boot system, several packages include scripts that
6779 are started from /etc/rcS.d/. In fact, there is a bite more of them
6780 than make sense, and this causes a few problems. What kind of
6781 problems, you might ask. There are at least two problems. The first
6782 is that it is not possible to recover a machine after switching to
6783 runlevel
1. One need to actually reboot to get the machine back to
6784 the expected state. The other is that single user boot will sometimes
6785 run into problems because some of the subsystems are activated before
6786 the root login is presented, causing problems when trying to recover a
6787 machine from a problem in that subsystem. A minor additional point is
6788 that moving more scripts out of rcS.d/ and into the other rc#.d/
6789 directories will increase the amount of scripts that can run in
6790 parallel during boot, and thus decrease the boot time.
</p
>
6792 <p
>So, which scripts should start from rcS.d/. In short, only the
6793 scripts that _have_ to execute before the root login prompt is
6794 presented during a single user boot should go there. Everything else
6795 should go into the numeric runlevels. This means things like
6796 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6797 the numeric runlevels. Today in Debian, there are around
115 init.d
6798 scripts that are started from rcS.d/, and most of them should be moved
6799 out. Do your package have one of them? Please help us make single
6800 user and runlevel
1 better by moving it.
</p
>
6802 <p
>Scripts setting up the screen, keyboard, system partitions
6803 etc. should still be started from rcS.d/, but there is for example no
6804 need to have the network enabled before the single user login prompt
6805 is presented.
</p
>
6807 <p
>As always, things are not so easy to fix as they sound. To keep
6808 Debian systems working while scripts migrate and during upgrades, the
6809 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6810 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6811 and the next ones can only be moved when their dependencies have been
6812 moved first. This migration must be done sequentially while we ensure
6813 that the package system upgrade packages in the right order to keep
6814 the system state correct. This will require some coordination when it
6815 comes to network related packages, but most of the packages with
6816 scripts that should migrate do not have anything in rcS.d/ depending
6817 on them. Some packages have already been updated, like the sudo
6818 package, while others are still left to do. I wish I had time to work
6819 on this myself, but real live constrains make it unlikely that I will
6820 find time to push this forward.
</p
>
6825 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6826 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6827 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6828 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6829 <description><p
>While at Debconf11, I have several times during discussions
6830 mentioned the issues I believe should be improved in Debian for its
6831 desktop to be useful for more people. The use case for this is my
6832 parents, which are currently running Kubuntu which solve the
6835 <p
>I suspect these four missing features are not very hard to
6836 implement. After all, they are present in Ubuntu, so if we wanted to
6837 do this in Debian we would have a source.
</p
>
6841 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
6842 are new packages available for upgrades, a icon in the KDE status bar
6843 indicate this, and clicking on it will activate the simple upgrade
6844 tool to handle it. I have no problem guiding both of my parents
6845 through the process over the phone. If a kernel reboot is required,
6846 this too is indicated by the status bars and the upgrade tool. Last
6847 time I checked, nothing with the same features was working in KDE in
6850 <li
><strong
>Simple handling of missing Firefox browser
6851 plugins.
</strong
> When the browser encounter a MIME type it do not
6852 currently have a handler for, it will ask the user if the system
6853 should search for a package that would add support for this MIME type,
6854 and if the user say yes, the APT sources will be searched for packages
6855 advertising the MIME type in their control file (visible in the
6856 Packages file in the APT archive). If one or more packages are found,
6857 it is a simple click of the mouse to add support for the missing mime
6858 type. If the package require the user to accept some non-free
6859 license, this is explained to the user. The entire process make it
6860 more clear to the user why something do not work in the browser, and
6861 make the chances higher for the user to blame the web page authors and
6862 not the browser for any missing features.
</li
>
6864 <li
><strong
>Simple handling of missing multimedia codec/format
6865 handlers.
</strong
> When the media players encounter a format or codec
6866 it is not supporting, a dialog pop up asking the user if the system
6867 should search for a package that would add support for it. This
6868 happen with things like MP3, Windows Media or H
.264. The selection
6869 and installation procedure is very similar to the Firefox browser
6870 plugin handling. This is as far as I know implemented using a
6871 gstreamer hook. The end result is that the user easily get access to
6872 the codecs that are present from the APT archives available, while
6873 explaining more on why a given format is unsupported by Ubuntu.
</li
>
6875 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
6876 displaying a text/plain file in my Debian browser, it will propose to
6877 start emacs to show it. If I remember correctly, when doing the same
6878 in Kunbutu it show the file as a text file in the browser. At least I
6879 know Opera will show text files within the browser. I much prefer the
6880 latter behaviour.
</li
>
6884 <p
>There are other nice features as well, like the simplified suite
6885 upgrader, but given that I am the one mostly doing the dist-upgrade,
6886 it do not matter much.
</p
>
6888 <p
>I really hope we could get these features in place for the next
6889 Debian release. It would require the coordinated effort of several
6890 maintainers, but would make the end user experience a lot better.
</p
>
6895 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
6896 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
6897 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
6898 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
6899 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
6900 site is build on Debian/Squeeze, and this platform was chosen because
6901 I am most familiar with Debian (being a Debian Developer for around
10
6902 years) because it is the latest stable Debian release which should get
6903 security support for a few years.
</p
>
6905 <p
>The web service is written in Perl, and depend on some perl modules
6906 that are missing in Debian at the moment. It would be great if these
6907 modules were added to the Debian archive, allowing anyone to set up
6908 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
6909 in their own country using only Debian packages. The list of modules
6910 missing in Debian/Squeeze isn
't very long, and I hope the perl group
6911 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
6912 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
6913 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
6914 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
6915 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
6916 easier in the future.
</p
>
6918 <p
>Thanks to the great tools in Debian, getting the missing modules
6919 installed on my server was a simple call to
'cpan2deb Module::Name
'
6920 and
'dpkg -i
' to install the resulting package. But this leave me
6921 with the responsibility of tracking security problems, which I really
6922 do not have time for.
</p
>
6927 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
6928 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
6929 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
6930 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
6931 <description><p
>Here is a small update for my English readers. Most of my blog
6932 posts have been in Norwegian the last few weeks, so here is a short
6933 update in English.
</p
>
6935 <p
>The kids still keep me too busy to get much free software work
6936 done, but I did manage to organise a project to get a Norwegian port
6937 of the British service
6938 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
6939 and it has been running for a month now. The entire project has been
6940 organised by me and two others. Around Christmas we gathered sponsors
6941 to fund the development work. In January I drafted a contract with
6942 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
6943 and in February the development took place. Most of it involved
6944 converting the source to use GPS coordinates instead of British
6945 easting/northing, and the resulting code should be a lot easier to get
6946 running in any country by now. The Norwegian
6947 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
6948 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
6949 source and the source for administrative borders in Norway, and
6950 support for this had to be added/fixed.
</p
>
6952 <p
>The Norwegian version went live March
3th, and we spent the weekend
6953 polishing the system before we announced it March
7th. The system is
6954 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
6955 problem reports in a few weeks. Soon we hope to announce the Android
6956 and iPhone versions making it even easier to report problems with the
6957 public infrastructure.
</p
>
6959 <p
>Perhaps something to consider for those of you in countries without
6960 such service?
</p
>
6965 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
6966 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
6967 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
6968 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
6969 <description><p
>The last few days I have looked at ways to track open security
6970 issues here at my work with the University of Oslo. My idea is that
6971 it should be possible to use the information about security issues
6972 available on the Internet, and check our locally
6973 maintained/distributed software against this information. It should
6974 allow us to verify that no known security issues are forgotten. The
6975 CVE database listing vulnerabilities seem like a great central point,
6976 and by using the package lists from Debian mapped to CVEs provided by
6977 the testing security team, I believed it should be possible to figure
6978 out which security holes were present in our free software
6979 collection.
</p
>
6981 <p
>After reading up on the topic, it became obvious that the first
6982 building block is to be able to name software packages in a unique and
6983 consistent way across data sources. I considered several ways to do
6984 this, for example coming up with my own naming scheme like using URLs
6985 to project home pages or URLs to the Freshmeat entries, or using some
6986 existing naming scheme. And it seem like I am not the first one to
6987 come across this problem, as MITRE already proposed and implemented a
6988 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
6989 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
6990 software, hardware and other platform components. The CPE ids are
6991 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
6992 Vulnerability Database
</a
>, allowing me to look up know security
6993 issues for any CPE name. With this in place, all I need to do is to
6994 locate the CPE id for the software packages we use at the university.
6995 This is fairly trivial (I google for
'cve cpe $package
' and check the
6996 NVD entry if a CVE for the package exist).
</p
>
6998 <p
>To give you an example. The GNU gzip source package have the CPE
6999 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7000 check out, one could look up
7001 <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
7002 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7003 The most recent one is
7004 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7005 and at the bottom of the NVD page for this vulnerability the complete
7006 list of affected versions is provided.
</p
>
7008 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7009 for offline processing of issues. Using this dump, I
've written a
7010 small script taking a list of CPEs as input and list all CVEs
7011 affecting the packages represented by these CPEs. One give it CPEs
7012 with version numbers as specified above and get a list of open
7013 security issues out.
</p
>
7015 <p
>Of course for this approach to be useful, the quality of the NVD
7016 information need to be high. For that to happen, I believe as many as
7017 possible need to use and contribute to the NVD database. I notice
7019 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7020 map from CVE to CPE
</a
>, indicating that they are using the CPE
7021 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7023 <p
>To get an idea about the quality for free software, I spent some
7024 time making it possible to compare the CVE database from Debian with
7025 the CVE database in NVD. The result look fairly good, but there are
7026 some inconsistencies in NVD (same software package having several
7027 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7028 Debian believe are affected by a CVE). Hope to find time to improve
7029 the quality of NVD, but that require being able to get in touch with
7030 someone maintaining it. So far my three emails with questions and
7031 corrections have not seen any reply, but I hope contact can be
7032 established soon.
</p
>
7034 <p
>An interesting application for CPEs is cross platform package
7035 mapping. It would be useful to know which packages in for example
7036 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7037 this would be trivial if all linux distributions provided CPE entries
7038 for their packages.
</p
>
7043 <title>Which module is loaded for a given PCI and USB device?
</title>
7044 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7045 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7046 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7047 <description><p
>In the
7048 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7049 package in Debian, there is a script to report useful information
7050 about the running hardware for use when people report missing
7051 information. One part of this script that I find very useful when
7052 debugging hardware problems, is the part mapping loaded kernel module
7053 to the PCI device it claims. It allow me to quickly see if the kernel
7054 module I expect is driving the hardware I am struggling with. To see
7055 the output, make sure discover-data is installed and run
7056 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7057 one of my machines like this:
</p
>
7061 10de:
03eb i2c_nforce2
7064 10de:
03f0 snd_hda_intel
7073 <p
>The code in question look like this, slightly modified for
7074 readability and to drop the output to file descriptor
3:
</p
>
7077 if [ -d /sys/bus/pci/devices/ ] ; then
7078 echo loaded pci modules:
7080 cd /sys/bus/pci/devices/
7081 for address in * ; do
7082 if [ -d
"$address/driver/module
" ] ; then
7083 module=`cd $address/driver/module ; pwd -P | xargs basename`
7084 if grep -q
"^$module
" /proc/modules ; then
7085 address=$(echo $address |sed s/
0000://)
7086 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7087 echo
"$id $module
"
7096 <p
>Similar code could be used to extract USB device module
7100 if [ -d /sys/bus/usb/devices/ ] ; then
7101 echo loaded usb modules:
7103 cd /sys/bus/usb/devices/
7104 for address in * ; do
7105 if [ -d
"$address/driver/module
" ] ; then
7106 module=`cd $address/driver/module ; pwd -P | xargs basename`
7107 if grep -q
"^$module
" /proc/modules ; then
7108 address=$(echo $address |sed s/
0000://)
7109 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7110 if [
"$id
" ] ; then
7111 echo
"$id $module
"
7121 <p
>This might perhaps be something to include in other tools as
7127 <title>How to test if a laptop is working with Linux
</title>
7128 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7130 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7131 <description><p
>The last few days I have spent at work here at the
<a
7132 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7133 batch of computers will work with Linux. Every year for the last few
7134 years the university have organised shared bid of a few thousand
7135 computers, and this year HP won the bid. Two different desktops and
7136 five different laptops are on the list this year. We in the UNIX
7137 group want to know which one of these computers work well with RHEL
7138 and Ubuntu, the two Linux distributions we currently handle at the
7139 university.
</p
>
7141 <p
>My test method is simple, and I share it here to get feedback and
7142 perhaps inspire others to test hardware as well. To test, I PXE
7143 install the OS version of choice, and log in as my normal user and run
7144 a few applications and plug in selected pieces of hardware. When
7145 something fail, I make a note about this in the test matrix and move
7146 on. If I have some spare time I try to report the bug to the OS
7147 vendor, but as I only have the machines for a short time, I rarely
7148 have the time to do this for all the problems I find.
</p
>
7150 <p
>Anyway, to get to the point of this post. Here is the simple tests
7151 I perform on a new model.
</p
>
7155 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7156 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7157 RHEL5 and Debian Edu/Squeeze.
</li
>
7159 <li
>Is X.org working? If the graphical login screen show up after
7160 installation, X.org is working.
</li
>
7162 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7163 package mesa-utils on Ubuntu) and writing down the frames per second
7164 reported by the program.
</li
>
7166 <li
>Is sound working? With Gnome and KDE, a sound is played when
7167 logging in, and if I can hear this the test is successful. If there
7168 are several audio exits on the machine, I try them all and check if
7169 the Gnome/KDE audio mixer can control where to send the sound. I
7170 normally test this by playing
7171 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7172 video
</a
> in Firefox/Iceweasel.
</li
>
7174 <li
>Is the USB subsystem working? I test this by plugging in a USB
7175 memory stick and see if Gnome/KDE notices this.
</li
>
7177 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7178 I have lying around, and see if Gnome/KDE notices this.
</li
>
7180 <li
>Is any built in camera working? Test using cheese, and see if a
7181 picture from the v4l device show up.
</li
>
7183 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7184 any bluetooth devices are discovered. In my office, I normally see a
7187 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7188 memory modules lying around, and stick them in and see if Gnome/KDE
7189 notice this.
</li
>
7191 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7192 special button work, and if the laptop continue to work after
7195 <li
>For laptops, is the extra buttons working, like audio level,
7196 adjusting background light, switching on/off external video output,
7197 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7198 laptop to laptop, so I just write down which are working and which are
7201 <li
>Some laptops have smart card readers, finger print readers,
7202 acceleration sensors etc. I rarely test these, as I do not know how
7203 to quickly test if they are working or not, so I only document their
7204 existence.
</li
>
7208 <p
>By now I suspect you are really curious what the test results are
7209 for the HP machines I am testing. I
'm not done yet, so I will report
7210 the test results later. For now I can report that HP
8100 Elite work
7211 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7212 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7213 can see, I have most machines left to test. One interesting
7214 observation is that Ubuntu Lucid has almost twice the frame rate than
7215 RHEL6 with glxgears. No idea why.
</p
>
7220 <title>Some thoughts on BitCoins
</title>
7221 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7222 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7223 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7224 <description><p
>As I continue to explore
7225 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7226 what properties the system have, and how it will be affected by laws
7227 and regulations here in Norway. Here are some random notes.
</p
>
7229 <p
>One interesting thing to note is that since the transactions are
7230 verified using a peer to peer network, all details about a transaction
7231 is known to everyone. This means that if a BitCoin address has been
7232 published like I did with mine in my initial post about BitCoin, it is
7233 possible for everyone to see how many BitCoins have been transfered to
7234 that address. There is even a web service to look at the details for
7235 all transactions. There I can see that my address
7236 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7237 have received
16.06 Bitcoin, the
7238 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7239 address of Simon Phipps have received
181.97 BitCoin and the address
7240 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7241 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7242 every one of you that donated bitcoins to support my activity. The
7243 fact that anyone can see how much money was transfered to a given
7244 address make it more obvious why the BitCoin community recommend to
7245 generate and hand out a new address for each transaction. I
'm told
7246 there is no way to track which addresses belong to a given person or
7247 organisation without the person or organisation revealing it
7248 themselves, as Simon, EFF and I have done.
</p
>
7250 <p
>In Norway, and in most other countries, there are laws and
7251 regulations limiting how much money one can transfer across the border
7252 without declaring it. There are money laundering, tax and accounting
7253 laws and regulations I would expect to apply to the use of BitCoin.
7254 If the Skolelinux foundation
7255 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7256 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7257 normal bank transfers like EFF is doing, how should this be accounted?
7258 Given that it is impossible to know if money can cross the border or
7259 not, should everything or nothing be declared? What exchange rate
7260 should be used when calculating taxes? Would receivers have to pay
7261 income tax if the foundation were to pay Skolelinux contributors in
7262 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7264 <p
>For a currency to be useful and successful, it must be trusted and
7265 accepted by a lot of users. It must be possible to get easy access to
7266 the currency (as a wage or using currency exchanges), and it must be
7267 easy to spend it. At the moment BitCoin seem fairly easy to get
7268 access to, but there are very few places to spend it. I am not really
7269 a regular user of any of the vendor types currently accepting BitCoin,
7270 so I wonder when my kind of shop would start accepting BitCoins. I
7271 would like to buy electronics, travels and subway tickets, not herbs
7272 and books. :) The currency is young, and this will improve over time
7273 if it become popular, but I suspect regular banks will start to lobby
7274 to get BitCoin declared illegal if it become popular. I
'm sure they
7275 will claim it is helping fund terrorism and money laundering (which
7276 probably would be true, as is any currency in existence), but I
7277 believe the problems should be solved elsewhere and not by blaming
7278 currencies.
</p
>
7280 <p
>The process of creating new BitCoins is called mining, and it is
7281 CPU intensive process that depend on a bit of luck as well (as one is
7282 competing against all the other miners currently spending CPU cycles
7283 to see which one get the next lump of cash). The
"winner
" get
50
7284 BitCoin when this happen. Yesterday I came across the obvious way to
7285 join forces to increase ones changes of getting at least some coins,
7286 by coordinating the work on mining BitCoins across several machines
7287 and people, and sharing the result if one is lucky and get the
50
7289 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7290 if this sounds interesting. I have not had time to try to set up a
7291 machine to participate there yet, but have seen that running on ones
7292 own for a few days have not yield any BitCoins througth mining
7295 <p
>Update
2010-
12-
15: Found an
<a
7296 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7297 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7298 it was interesting to read. The arguments presented seem to be
7299 equally valid for gold, which was used as a currency for many years.
</p
>
7304 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7305 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7306 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7307 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7308 <description><p
>With this weeks lawless
7309 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7310 attacks
</a
> on Wikileak and
7311 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7312 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7313 not be trusted to handle money transactions.
7315 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7316 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7317 mine mentioned earlier. I decided to follow Simon
's example, and get
7318 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7319 some help from my friend to get it all running, and he even handed me
7320 some bitcoins to get started. I even donated a few bitcoins to Simon
7321 for helping me remember BitCoin.
</p
>
7323 <p
>So, what is bitcoins, you probably wonder? It is a digital
7324 crypto-currency, decentralised and handled using peer-to-peer
7325 networks. It allows anonymous transactions and prohibits central
7326 control over the transactions, making it impossible for governments
7327 and companies alike to block donations and other transactions. The
7328 source is free software, and while the key dependency wxWidgets
2.9
7329 for the graphical user interface is missing in Debian, the command
7330 line client builds just fine. Hopefully Jonas
7331 <a href=
"http://bugs.debian.org/
578157">will get the package into
7332 Debian
</a
> soon.
</p
>
7334 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7335 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7336 bitcoins
</a
> when selling services and goods, and there are even
7337 currency
"stock
" markets where the exchange rate is decided. There
7338 are not many users so far, but the concept seems promising. If you
7339 want to get started and lack a friend with any bitcoins to spare,
7341 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7342 bitcoin at the time of writing). Use
7343 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7344 on the current exchange rates.
</p
>
7346 <p
>As an experiment, I have decided to set up bitcoind on one of my
7347 machines. If you want to support my activity, please send Bitcoin
7348 donations to the address
7349 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7354 <title>Why isn
't Debian Edu using VLC?
</title>
7355 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7356 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7357 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7358 <description><p
>In the latest issue of Linux Journal, the readers choices were
7359 presented, and the winner among the multimedia player were VLC.
7360 Personally, I like VLC, and it is my player of choice when I first try
7361 to play a video file or stream. Only if VLC fail will I drag out
7362 gmplayer to see if it can do better. The reason is mostly the failure
7363 model and trust. When VLC fail, it normally pop up a error message
7364 reporting the problem. When mplayer fail, it normally segfault or
7365 just hangs. The latter failure mode drain my trust in the program.
<p
>
7367 <p
>But even if VLC is my player of choice, we have choosen to use
7368 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7369 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7370 plugin to play web videos seamlessly, and the VLC browser plugin is
7371 not very good. For example, it lack in-line control buttons, so there
7372 is no way for the user to pause the video. Also, when I
7373 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7374 tested the browser plugins
</a
> available in Debian, the VLC plugin
7375 failed on several video pages where mplayer based plugins worked. If
7376 the browser plugin for VLC was as good as the gecko-mediaplayer
7377 package (which uses mplayer), we would switch.
</P
>
7379 <p
>While VLC is a good player, its user interface is slightly
7380 annoying. The most annoying feature is its inconsistent use of
7381 keyboard shortcuts. When the player is in full screen mode, its
7382 shortcuts are different from when it is playing the video in a window.
7383 For example, space only work as pause when in full screen mode. I
7384 wish it had consisten shortcuts and that space also would work when in
7385 window mode. Another nice shortcut in gmplayer is [enter] to restart
7386 the current video. It is very nice when playing short videos from the
7387 web and want to restart it when new people arrive to have a look at
7388 what is going on.
</p
>
7393 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7394 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7395 <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>
7396 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7397 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7398 upgrade testing of the
7399 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7400 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7401 This seem like a very good idea, so I adjusted by test scripts and
7402 can now present the updated result from today:
</p
>
7404 <p
>This is for Gnome:
</p
>
7406 <p
>Installed using apt-get, missing with aptitude
</p
>
7408 <blockquote
><p
>
7413 browser-plugin-gnash
7420 freedesktop-sound-theme
7422 gconf-defaults-service
7437 gnome-desktop-environment
7441 gnome-session-canberra
7446 gstreamer0.10-fluendo-mp3
7452 libapache2-mod-dnssd
7455 libaprutil1-dbd-sqlite3
7458 libboost-date-time1.42
.0
7459 libboost-python1.42
.0
7460 libboost-thread1.42
.0
7462 libchamplain-gtk-
0.4-
0
7464 libclutter-gtk-
0.10-
0
7471 libfreerdp-plugins-standard
7486 libgnomepanel2.24-cil
7491 libgtksourceview2.0-common
7492 libmono-addins-gui0.2-cil
7493 libmono-addins0.2-cil
7494 libmono-cairo2.0-cil
7495 libmono-corlib2.0-cil
7496 libmono-i18n-west2.0-cil
7497 libmono-posix2.0-cil
7498 libmono-security2.0-cil
7499 libmono-sharpzip2.84-cil
7500 libmono-system2.0-cil
7503 libndesk-dbus-glib1.0-cil
7504 libndesk-dbus1.0-cil
7514 libtelepathy-farsight0
7523 nautilus-sendto-empathy
7527 python-aptdaemon-gtk
7529 python-beautifulsoup
7544 python-gtksourceview2
7555 python-pkg-resources
7562 python-twisted-conch
7568 python-zope.interface
7573 rhythmbox-plugin-cdrecorder
7580 system-config-printer-udev
7582 telepathy-mission-control-
5
7593 </p
></blockquote
>
7595 <p
>Installed using apt-get, removed with aptitude
</p
>
7597 <blockquote
><p
>
7603 fast-user-switch-applet
7622 libgtksourceview2.0-
0
7624 libsdl1.2debian-alsa
7630 system-config-printer
7635 </p
></blockquote
>
7637 <p
>Installed using aptitude, missing with apt-get
</p
>
7639 <blockquote
><p
>
7640 gstreamer0.10-gnomevfs
7641 </p
></blockquote
>
7643 <p
>Installed using aptitude, removed with apt-get
</p
>
7645 <blockquote
><p
>
7647 </p
></blockquote
>
7649 <p
>This is for KDE:
</p
>
7651 <p
>Installed using apt-get, missing with aptitude
</p
>
7653 <blockquote
><p
>
7655 </p
></blockquote
>
7657 <p
>Installed using apt-get, removed with aptitude
</p
>
7659 <blockquote
><p
>
7662 </p
></blockquote
>
7664 <p
>Installed using aptitude, missing with apt-get
</p
>
7666 <blockquote
><p
>
7680 kdeartwork-emoticons
7682 kdeartwork-theme-icon
7686 kdebase-workspace-bin
7687 kdebase-workspace-data
7701 kscreensaver-xsavers
7716 plasma-dataengines-workspace
7718 plasma-desktopthemes-artwork
7719 plasma-runners-addons
7720 plasma-scriptengine-googlegadgets
7721 plasma-scriptengine-python
7722 plasma-scriptengine-qedje
7723 plasma-scriptengine-ruby
7724 plasma-scriptengine-webkit
7725 plasma-scriptengines
7726 plasma-wallpapers-addons
7727 plasma-widget-folderview
7728 plasma-widget-networkmanagement
7732 xscreensaver-data-extra
7734 xscreensaver-gl-extra
7735 xscreensaver-screensaver-bsod
7736 </p
></blockquote
>
7738 <p
>Installed using aptitude, removed with apt-get
</p
>
7740 <blockquote
><p
>
7742 google-gadgets-common
7760 libggadget-qt-
1.0-
0b
7765 libkonqsidebarplugin4a
7774 libplasma-geolocation-interface4
7776 libplasmagenericshell4
7790 libsmokeknewstuff2-
3
7791 libsmokeknewstuff3-
3
7793 libsmokektexteditor3
7801 libsmokeqtnetwork4-
3
7807 libsmokeqtuitools4-
3
7819 plasma-dataengines-addons
7820 plasma-scriptengine-superkaramba
7821 plasma-widget-lancelot
7822 plasma-widgets-addons
7823 plasma-widgets-workspace
7827 update-notifier-common
7828 </p
></blockquote
>
7830 <p
>Running apt-get autoremove made the results using apt-get and
7831 aptitude a bit more similar, but there are still quite a lott of
7832 differences. I have no idea what packages should be installed after
7833 the upgrade, but hope those that do can have a look.
</p
>
7838 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7839 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7840 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
7841 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
7842 <description><p
>Most of the computers in use by the
7843 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
7844 are virtual machines. And they have been Xen machines running on a
7845 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
7846 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
7847 bit harder that it could have been, because we set up the Xen virtual
7848 machines to get the virtual partitions from LVM, which as far as I
7849 know is not supported by KVM. So to migrate, we had to convert
7850 several LVM logical volumes to partitions on a virtual disk file.
</p
>
7853 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
7854 nice recipe
</a
> to do this, and wrote the following script to do the
7855 migration. It uses qemu-img from the qemu package to make the disk
7856 image, parted to partition it, losetup and kpartx to present the disk
7857 image partions as devices, and dd to copy the data. I NFS mounted the
7858 new servers storage area on the old server to do the migration.
</p
>
7864 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
7869 if [ -z
"$
1" ] ; then
7870 echo
"Usage: $
0 &lt;hostname
&gt;
"
7876 if [ ! -e /dev/vg_data/$host-disk ] ; then
7877 echo
"error: unable to find LVM volume for $host
"
7881 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
7882 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7883 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
7884 totalsize=$(( ( $disksize + $swapsize ) ))
7887 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
7888 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
7890 parted $img mklabel msdos
7891 parted $img mkpart primary linux-swap
0 $disksize
7892 parted $img mkpart primary ext2 $disksize $totalsize
7893 parted $img set
1 boot on
7896 losetup /dev/loop0 $img
7897 kpartx -a /dev/loop0
7899 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
7900 fsck.ext3 -f /dev/mapper/loop0p1 || true
7901 mkswap /dev/mapper/loop0p2
7903 kpartx -d /dev/loop0
7904 losetup -d /dev/loop0
7907 <p
>The script is perhaps so simple that it is not copyrightable, but
7908 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
7910 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
7911 the new disk image attached, installed grub-pc and linux-image-
686 and
7912 set up grub to boot from the disk image. After this, the KVM machines
7913 seem to work just fine.
</p
>
7918 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
7919 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
7920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
7921 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
7922 <description><p
>I
'm still running upgrade testing of the
7923 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7924 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
7925 status. Here is a short update based on a test I ran
20101118.
</p
>
7927 <p
>I still do not know what a correct migration should look like, so I
7928 report any differences between apt and aptitude and hope someone else
7929 can see if anything should be changed.
</p
>
7931 <p
>This is for Gnome:
</p
>
7933 <p
>Installed using apt-get, missing with aptitude
</p
>
7935 <blockquote
><p
>
7936 apache2.2-bin aptdaemon at-spi baobab binfmt-support
7937 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
7938 dmz-cursor-theme empathy empathy-common finger
7939 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
7940 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
7941 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
7942 gnome-cards-data gnome-codec-install gnome-core
7943 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7944 gnome-search-tool gnome-session-canberra gnome-spell
7945 gnome-system-log gnome-themes-extras gnome-themes-more
7946 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7947 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7948 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7949 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7950 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
7951 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
7952 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
7953 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
7954 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
7955 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7956 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
7957 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7958 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7959 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7960 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7961 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7962 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7963 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7964 libmono-security2.0-cil libmono-sharpzip2.84-cil
7965 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
7966 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
7967 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
7968 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
7969 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
7970 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
7971 libxalan2-java libxerces2-java media-player-info mesa-utils
7972 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
7973 nautilus-sendto-empathy openoffice.org-writer2latex
7974 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
7975 python-aptdaemon python-aptdaemon-gtk python-axiom
7976 python-beautifulsoup python-bugbuddy python-clientform
7977 python-coherence python-configobj python-crypto python-cupshelpers
7978 python-cupsutils python-eggtrayicon python-elementtree
7979 python-epsilon python-evolution python-feedparser python-gdata
7980 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7981 python-gtksourceview2 python-httplib2 python-louie python-mako
7982 python-markupsafe python-mechanize python-nevow python-notify
7983 python-opengl python-openssl python-pam python-pkg-resources
7984 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7985 python-tagpy python-twisted-bin python-twisted-conch
7986 python-twisted-core python-twisted-web python-utidylib python-webkit
7987 python-xdg python-zope.interface remmina remmina-plugin-data
7988 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7989 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7990 software-center svgalibg1 system-config-printer-udev
7991 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
7992 totem totem-coherence totem-mozilla totem-plugins
7993 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7995 </p
></blockquote
>
7997 Installed using apt-get, removed with aptitude
7999 <blockquote
><p
>
8000 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8001 epiphany-extensions epiphany-gecko evolution-exchange
8002 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8003 gedit-common gnome-app-install gnome-games gnome-games-data
8004 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8005 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8006 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8007 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8008 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8009 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8010 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8011 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8012 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8013 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8014 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8015 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8016 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8017 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8018 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8019 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8020 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8021 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8022 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8023 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8024 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8025 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8026 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8027 sound-juicer swfdec-gnome system-config-printer totem-common
8028 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8029 </p
></blockquote
>
8031 <p
>Installed using aptitude, missing with apt-get
</p
>
8033 <blockquote
><p
>
8034 gstreamer0.10-gnomevfs
8035 </p
></blockquote
>
8037 <p
>Installed using aptitude, removed with apt-get
</p
>
8039 <blockquote
><p
>
8041 </p
></blockquote
>
8043 <p
>This is for KDE:
</p
>
8045 <p
>Installed using apt-get, missing with aptitude
</p
>
8047 <blockquote
><p
>
8048 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8049 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8050 ghostscript-x git gnome-audio gnugo granatier gs-common
8051 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8052 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8053 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8054 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8055 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8056 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8057 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8058 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8059 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8060 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8061 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8062 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8063 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8064 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8065 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8066 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8067 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8068 libkrossui4 libmailtools-perl libmime-tools-perl
8069 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8070 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8071 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8072 lirc luatex marble networkstatus noatun-plugins
8073 openoffice.org-writer2latex palapeli palapeli-data parley
8074 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8075 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8076 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8078 </p
></blockquote
>
8080 <p
>Installed using apt-get, removed with aptitude
</p
>
8082 <blockquote
><p
>
8083 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8084 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8085 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8086 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8087 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8088 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8089 kitchensync kiten kjumpingcube klatin klettres klickety klines
8090 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8091 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8092 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8093 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8094 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8095 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8096 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8097 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8098 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8099 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8100 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8101 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8102 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8103 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8104 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8105 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8106 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8107 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8108 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8109 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8110 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8111 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8112 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8113 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8114 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8115 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8116 </p
></blockquote
>
8118 <p
>Installed using aptitude, missing with apt-get
</p
>
8120 <blockquote
><p
>
8121 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8122 kdeartwork kdebase kdebase-apps kdebase-workspace
8123 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8124 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8125 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8126 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8127 xscreensaver-screensaver-bsod
8128 </p
></blockquote
>
8130 <p
>Installed using aptitude, removed with apt-get
</p
>
8132 <blockquote
><p
>
8133 kdebase-bin konq-plugins konqueror
8134 </p
></blockquote
>
8139 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8140 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8141 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8142 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8143 <description><p
>Answering
8144 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8145 call from the Gnash project
</a
> for
8146 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8147 current source, I have set up a virtual KVM machine on the Debian
8148 Edu/Skolelinux virtualization host to test the git source on
8149 Debian/Squeeze. I hope this can help the developers in getting new
8150 releases out more often.
</p
>
8152 <p
>As the developers want less main-stream build platforms tested to,
8153 I have considered setting up a
<a
8154 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8155 machine as well. I have also considered using the kfreebsd
8156 architecture in Debian as a file server in NUUG to get access to the
5
8157 TB zfs volume we currently use to store DV video. Because of this, I
8158 finally got around to do a test installation of Debian/Squeeze with
8159 kfreebsd. Installation went fairly smooth, thought I noticed some
8160 visual glitches in the cdebconf dialogs (black cursor left on the
8161 screen at random locations). Have not gotten very far with the
8162 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8163 fatal problem. Have to spend some more time on it to see if it is
8164 useful as a file server for NUUG. Will try to find time to set up a
8165 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8170 <title>Debian in
3D
</title>
8171 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8172 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8173 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8174 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8176 <p
>3D printing is just great. I just came across this Debian logo in
8178 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8179 thingiverse blog
</a
>.
</p
>
8184 <title>Software updates
2010-
10-
24</title>
8185 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8186 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8187 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8188 <description><p
>Some updates.
</p
>
8190 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8191 raise money for the project is going well. The lower limit of
10
8192 signers was reached in
24 hours, and so far
13 people have signed it.
8193 More signers and more funding is most welcome, and I am really curious
8194 how far we can get before the time limit of December
24 is reached.
8197 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8198 about what appear to be a great code coverage tool capable of
8199 generating code coverage stats without any changes to the source code.
8201 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8202 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8203 It is missing in Debian, but the git source built just fine in Squeeze
8204 after I installed libelf-dev, libdwarf-dev, pkg-config and
8205 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8206 solvable. I hope kcov make it into Debian soon.
</p
>
8208 <p
>Finally found time to wrap up the release notes for
<a
8209 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8210 new alpha release of Debian Edu
</a
>, and just published the second
8211 alpha test release of the Squeeze based Debian Edu /
8212 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8213 release. Give it a try if you need a complete linux solution for your
8214 school, including central infrastructure server, workstations, thin
8215 client servers and diskless workstations. A nice touch added
8216 yesterday is RDP support on the thin client servers, for windows
8217 clients to get a Linux desktop on request.
</p
>
8222 <title>Some notes on Flash in Debian and Debian Edu
</title>
8223 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8224 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8225 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8226 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8227 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8228 second most popular used package that is missing in Debian. The sixth
8229 most popular is flashplayer-mozilla. This is a clear indication that
8230 working flash is important for Debian users. Around
10 percent of the
8231 users submitting data to popcon.debian.org have this package
8232 installed.
</p
>
8234 <p
>In the report written by Lars Risan in August
2008
8235 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8236 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8237 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8238 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8239 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8240 web sites require Flash to work, and lacking working Flash support in
8241 the web browser and the problems with installing it was perceived as a
8242 good reason to stay with Windows.
</p
>
8244 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8245 said to be the retarded cousin that did not really understand
8246 everything you told him but could work fairly well. This was a
8247 comment regarding the problems Linux have with proprietary formats and
8248 non-standard web pages, and is sad because it exposes a fairly common
8249 understanding of whose fault it is if web pages that only work in for
8250 example Internet Explorer
6 fail to work on Firefox, and funny because
8251 it explain very well how annoying it is for users when Linux
8252 distributions do not work with the documents they receive or the web
8253 pages they want to visit.
</p
>
8255 <p
>This is part of the reason why I believe it is important for Debian
8256 and Debian Edu to have a well working Flash implementation in the
8257 distribution, to get at least popular sites as Youtube and Google
8258 Video to working out of the box. For Squeeze, Debian have the chance
8259 to include the latest version of Gnash that will make this happen, as
8260 the new release
0.8.8 was published a few weeks ago and is resting in
8261 unstable. The new version work with more sites that version
0.8.7.
8262 The Gnash maintainers have asked for a freeze exception, but the
8263 release team have not had time to reply to it yet. I hope they agree
8264 with me that Flash is important for the Debian desktop users, and thus
8265 accept the new package into Squeeze.
</p
>
8270 <title>Circular package dependencies harms apt recovery
</title>
8271 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8272 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8273 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8274 <description><p
>I discovered this while doing
8275 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8276 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8277 in Debian still got circular dependencies, and it is often claimed
8278 that apt and aptitude should be able to handle this just fine, but
8279 some times these dependency loops causes apt to fail.
</p
>
8281 <p
>An example is from todays
8282 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8283 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8284 causes perl-modules to fail to upgrade. The cause is simple. If a
8285 package fail to unpack, then only part of packages with the circular
8286 dependency might end up being unpacked when unpacking aborts, and the
8287 ones already unpacked will fail to configure in the recovery phase
8288 because its dependencies are unavailable.
</p
>
8290 <p
>In this log, the problem manifest itself with this error:
</p
>
8292 <blockquote
><pre
>
8293 dpkg: dependency problems prevent configuration of perl-modules:
8294 perl-modules depends on perl (
>=
5.10.1-
1); however:
8295 Version of perl on system is
5.10.0-
19lenny
2.
8296 dpkg: error processing perl-modules (--configure):
8297 dependency problems - leaving unconfigured
8298 </pre
></blockquote
>
8300 <p
>The perl/perl-modules circular dependency is already
8301 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8302 hopefully be solved as soon as possible, but it is not the only one,
8303 and each one of these loops in the dependency tree can cause similar
8304 failures. Of course, they only occur when there are bugs in other
8305 packages causing the unpacking to fail, but it is rather nasty when
8306 the failure of one package causes the problem to become worse because
8307 of dependency loops.
</p
>
8310 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8311 tireless effort by Bill Allombert
</a
>, the number of circular
8313 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8314 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8316 <p
>Todays testing also exposed a bug in
8317 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8318 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8319 apt-get and aptitude, the latter possibly caused by some circular
8320 dependency. Reported both to BTS to try to get someone to look at
8326 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8327 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8329 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8330 <description><p
>This is a
8331 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8333 <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
8335 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8336 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8338 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8339 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8340 and dhcp3-server-ldap in Debian use the LDAP server. The two
8341 implementations are quite different in how they use LDAP.
</p
>
8343 To get this information, I started slapd with debugging enabled and
8344 dumped the debug output to a file to get the LDAP searches performed
8345 on a Debian Edu main-server. Here is a summary.
8347 <p
><strong
>powerdns
</strong
></p
>
8349 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8350 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8353 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8354 One
"strict
" mode where the forward and reverse DNS lookups are done
8355 using the same LDAP objects, and a
"tree
" mode where the forward and
8356 reverse entries are in two different subtrees in LDAP with a structure
8357 based on the DNS names, as in tjener.intern and
8358 2.2.0.10.in-addr.arpa.
</p
>
8360 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8361 base, and uses a
"base
" scoped search for the DNS name by adding
8362 "dc=tjener,dc=intern,
" to the base with a filter for
8363 "(associateddomain=tjener.intern)
" for the forward entry and
8364 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8365 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8366 forward entries, it is looking for attributes named dnsttl, arecord,
8367 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8368 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8369 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8370 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8371 spfrecord and modifytimestamp. For reverse entries it is looking for
8372 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8373 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8374 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8375 ldapsearch commands could look like this:
</p
>
8377 <blockquote
><pre
>
8378 ldapsearch -h ldap \
8379 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8380 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8381 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8382 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8383 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8384 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8386 ldapsearch -h ldap \
8387 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8388 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8389 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8390 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8391 srvrecord naptrrecord modifytimestamp
8392 </pre
></blockquote
>
8394 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8395 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8396 example LDAP objects used there. In addition to these objects, the
8397 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8398 also exist.
</p
>
8400 <blockquote
><pre
>
8401 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8403 objectclass: dnsdomain
8404 objectclass: domainrelatedobject
8407 associateddomain: tjener.intern
8409 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8411 objectclass: dnsdomain2
8412 objectclass: domainrelatedobject
8414 ptrrecord: tjener.intern
8415 associateddomain:
2.2.0.10.in-addr.arpa
8416 </pre
></blockquote
>
8418 <p
>In strict mode, the server behaves differently. When looking for
8419 forward DNS entries, it is doing a
"subtree
" scoped search with the
8420 same base as in the tree mode for a object with filter
8421 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8422 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8423 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8424 naptrrecord and modifytimestamp. For reverse entires it also do a
8425 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8426 and the requested attributes are associateddomain, dnsttl and
8427 modifytimestamp. In short, in strict mode the objects with ptrrecord
8428 go away, and the arecord attribute in the forward object is used
8431 <p
>The forward and reverse searches can be simulated using ldapsearch
8432 like this:
</p
>
8434 <blockquote
><pre
>
8435 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8436 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8437 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8438 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8439 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8440 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8442 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8443 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8444 </pre
></blockquote
>
8446 <p
>In addition to the forward and reverse searches , there is also a
8447 search for SOA records, which behave similar to the forward and
8448 reverse lookups.
</p
>
8450 <p
>A thing to note with the PowerDNS behaviour is that it do not
8451 specify any objectclass names, and instead look for the attributes it
8452 need to generate a DNS reply. This make it able to work with any
8453 objectclass that provide the needed attributes.
</p
>
8455 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8456 dnsdomain2 schemas. The latter is used for reverse entries like
8457 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8459 <p
>In Debian Edu, we have created DNS objects using the object classes
8460 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8461 attributes) and domainrelatedobject (for associatedDomain). The use
8462 of structural object classes make it impossible to combine these
8463 classes with the object classes used by DHCP.
</p
>
8465 <p
>There are other schemas that could be used too, for example the
8466 dnszone structural object class used by Gosa and bind-sdb for the DNS
8467 attributes combined with the domainrelatedobject object class, but in
8468 this case some unused attributes would have to be included as well
8469 (zonename and relativedomainname).
</p
>
8471 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8472 mode and not use any of the existing objectclasses (dnsdomain,
8473 dnsdomain2 and dnszone) when one want to combine the DNS information
8474 with DHCP information, and instead create a auxiliary object class
8475 defined something like this (using the attributes defined for
8476 dnsdomain and dnsdomain2 or dnszone):
</p
>
8478 <blockquote
><pre
>
8479 objectclass ( some-oid NAME
'dnsDomainAux
'
8482 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8483 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8484 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8485 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8486 A6Record $ DNAMERecord
8488 </pre
></blockquote
>
8490 <p
>This will allow any object to become a DNS entry when combined with
8491 the domainrelatedobject object class, and allow any entity to include
8492 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8493 developers asking for their view on this schema and if they are
8494 interested in providing such schema with PowerDNS, and I hope my
8495 message will be accepted into their mailing list soon.
</p
>
8497 <p
><strong
>ISC dhcp
</strong
></p
>
8499 <p
>The DHCP server searches for specific objectclass and requests all
8500 the object attributes, and then uses the attributes it want. This
8501 make it harder to figure out exactly what attributes are used, but
8502 thanks to the working example in Debian Edu I can at least get an idea
8503 what is needed without having to read the source code.
</p
>
8505 <p
>In the DHCP server configuration, the LDAP base to use and the
8506 search filter to use to locate the correct dhcpServer entity is
8507 stored. These are the relevant entries from
8508 /etc/dhcp3/dhcpd.conf:
</p
>
8510 <blockquote
><pre
>
8511 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8512 ldap-dhcp-server-cn
"dhcp
";
8513 </pre
></blockquote
>
8515 <p
>The DHCP server uses this information to nest all the DHCP
8516 configuration it need. The cn
"dhcp
" is located using the given LDAP
8517 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8518 search result is this entry:
</p
>
8520 <blockquote
><pre
>
8521 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8524 objectClass: dhcpServer
8525 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8526 </pre
></blockquote
>
8528 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8529 subtree with DHCP configuration. The DHCP configuration subtree base
8530 is located using a base scope search with base
"cn=DHCP
8531 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8532 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8533 The search result is this entry:
</p
>
8535 <blockquote
><pre
>
8536 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8539 objectClass: dhcpService
8540 objectClass: dhcpOptions
8541 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8542 dhcpStatements: ddns-update-style none
8543 dhcpStatements: authoritative
8544 dhcpOption: smtp-server code
69 = array of ip-address
8545 dhcpOption: www-server code
72 = array of ip-address
8546 dhcpOption: wpad-url code
252 = text
8547 </pre
></blockquote
>
8549 <p
>Next, the entire subtree is processed, one level at the time. When
8550 all the DHCP configuration is loaded, it is ready to receive requests.
8551 The subtree in Debian Edu contain objects with object classes
8552 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8553 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8554 and information about netmasks, dynamic range etc. Leaving out the
8555 details here because it is not relevant for the focus of my
8556 investigation, which is to see if it is possible to merge dns and dhcp
8557 related computer objects.
</p
>
8559 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8560 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8561 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8562 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8563 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8566 <blockquote
><pre
>
8567 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8570 objectClass: dhcpHost
8571 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8572 dhcpStatements: fixed-address hostname
8573 </pre
></blockquote
>
8575 <p
>There is less flexiblity in the way LDAP searches are done here.
8576 The object classes need to have fixed names, and the configuration
8577 need to be stored in a fairly specific LDAP structure. On the
8578 positive side, the invidiual dhcpHost entires can be anywhere without
8579 the DN pointed to by the dhcpServer entries. The latter should make
8580 it possible to group all host entries in a subtree next to the
8581 configuration entries, and this subtree can also be shared with the
8582 DNS server if the schema proposed above is combined with the dhcpHost
8583 structural object class.
8585 <p
><strong
>Conclusion
</strong
></p
>
8587 <p
>The PowerDNS implementation seem to be very flexible when it come
8588 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8589 come to the the LDAP structure, the
"strict
" mode is very flexible,
8590 allowing DNS objects to be stored anywhere under the base cn specified
8591 in the configuration.
</p
>
8593 <p
>The DHCP implementation on the other hand is very inflexible, both
8594 regarding which LDAP schemas to use and which LDAP structure to use.
8595 I guess one could implement ones own schema, as long as the
8596 objectclasses and attributes have the names used, but this do not
8597 really help when the DHCP subtree need to have a fairly fixed
8598 structure.
</p
>
8600 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8601 this might work for Debian Edu:
</p
>
8603 <blockquote
><pre
>
8605 cn=machine-info (dhcpService) - dhcpServiceDN points here
8606 cn=dhcp (dhcpServer)
8607 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8608 cn=
10.0.2.0 (dhcpSubnet)
8609 cn=group1 (dhcpGroup/dhcpOptions)
8610 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8611 cn=
192.168.0.0 (dhcpSubnet)
8612 cn=group1 (dhcpGroup/dhcpOptions)
8613 ou=machines - PowerDNS base points here
8614 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8615 </pre
></blockquote
>
8617 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8618 entries to be in the dhcpGroup subtrees, the entries can be stored
8619 there instead of a common machines subtree, and the PowerDNS base
8620 would have to be moved one level up to the machine-info subtree.
</p
>
8622 <p
>The combined object under the machines subtree would look something
8623 like this:
</p
>
8625 <blockquote
><pre
>
8626 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8629 objectClass: dhcpHost
8630 objectclass: domainrelatedobject
8631 objectclass: dnsDomainAux
8632 associateddomain: hostname.intern
8633 arecord:
10.11.12.13
8634 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8635 dhcpStatements: fixed-address hostname.intern
8636 </pre
></blockquote
>
8638 </p
>One could even add the LTSP configuration associated with a given
8639 machine, as long as the required attributes are available in a
8640 auxiliary object class.
</p
>
8645 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8646 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8647 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8648 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8649 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8650 DHCP services in Debian Edu to use the same LDAP objects for a given
8651 computer, to avoid the possibility of having a inconsistent state for
8652 a computer in LDAP (as in DHCP but no DNS entry or the other way
8653 around) and make it easier to add computers to LDAP.
</p
>
8655 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8656 information finally found a solution that seem to work.
</p
>
8658 <p
>The old setup required three LDAP objects for a given computer.
8659 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8660 we switch powerdns to use its strict LDAP method (ldap-method=strict
8661 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8662 merged into one while making it impossible to transfer the reverse map
8663 to a slave DNS server.
</p
>
8665 <p
>If we also replace the object class used to get the DNS related
8666 attributes to one allowing these attributes to be combined with the
8667 dhcphost object class, we can merge the DNS and DHCP entries into one.
8668 I
've written such object class in the dnsdomainaux.schema file (need
8669 proper OIDs, but that is a minor issue), and tested the setup. It
8670 seem to work.
</p
>
8672 <p
>With this test setup in place, we can get away with one LDAP object
8673 for both DNS and DHCP, and even the LTSP configuration I suggested in
8674 an earlier email. The combined LDAP object will look something like
8677 <blockquote
><pre
>
8678 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8680 objectClass: dhcphost
8681 objectclass: domainrelatedobject
8682 objectclass: dnsdomainaux
8683 associateddomain: hostname.intern
8684 arecord:
10.11.12.13
8685 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8686 dhcpstatements: fixed-address hostname
8688 </pre
></blockquote
>
8690 <p
>The DNS server uses the associateddomain and arecord entries, while
8691 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8692 before asking DNS to resolve the fixed-adddress. LTSP will use
8693 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8695 <p
>I am not yet sure if I can get the DHCP server to look for its
8696 dhcphost in a different location, to allow us to put the objects
8697 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8698 that. If I can
't figure out a way to do that, we can still get rid of
8699 the hosts subtree and move all its content into the DHCP Config tree
8700 (which probably should be renamed to be more related to the new
8701 content. I suspect cn=dnsdhcp,ou=services or something like that
8702 might be a good place to put it.
</p
>
8704 <p
>If you want to help out with implementing this for Debian Edu,
8705 please contact us on debian-edu@lists.debian.org.
</p
>
8710 <title>Idea for storing LTSP configuration in LDAP
</title>
8711 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8712 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8713 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8714 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8715 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8716 clients, and that this can be used to fetch configuration from LDAP if
8717 Debian Edu choose to store configuration there.
</p
>
8719 <p
>Armed with this information, I got inspired and wrote a test module
8720 to get configuration from LDAP. The idea is to look up the MAC
8721 address of the client in LDAP, and look for attributes on the form
8722 ltspconfigsetting=value, and use this to export SETTING=value to the
8723 LTSP clients.
</p
>
8725 <p
>The goal is to be able to store the LTSP configuration attributes
8726 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8727 allowing us to store all information about a computer in one place.
</p
>
8729 <p
>This is a untested draft implementation, and I welcome feedback on
8730 this approach. A real LDAP schema for the ltspClientAux objectclass
8731 need to be written. Comments, suggestions, etc?
</p
>
8733 <blockquote
><pre
>
8734 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8736 # Fetch LTSP client settings from LDAP based on MAC address
8738 # Uses ethernet address as stored in the dhcpHost objectclass using
8739 # the dhcpHWAddress attribute or ethernet address stored in the
8740 # ieee802Device objectclass with the macAddress attribute.
8742 # This module is written to be schema agnostic, and only depend on the
8743 # existence of attribute names.
8745 # The LTSP configuration variables are saved directly using a
8746 # ltspConfig prefix and uppercasing the rest of the attribute name.
8747 # To set the SERVER variable, set the ltspConfigServer attribute.
8749 # Some LDAP schema should be created with all the relevant
8750 # configuration settings. Something like this should work:
8752 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8755 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8757 LDAPSERVER=$(debian-edu-ldapserver)
8758 if [
"$LDAPSERVER
" ] ; then
8759 LDAPBASE=$(debian-edu-ldapserver -b)
8760 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8761 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8762 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8763 grep
'^ltspConfig
' | while read attr value ; do
8764 # Remove prefix and convert to upper case
8765 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8766 # bass value on to clients
8767 eval
"$attr=$value; export $attr
"
8771 </pre
></blockquote
>
8773 <p
>I
'm not sure this shell construction will work, because I suspect
8774 the while block might end up in a subshell causing the variables set
8775 there to not show up in ltsp-config, but if that is the case I am sure
8776 the code can be restructured to make sure the variables are passed on.
8777 I expect that can be solved with some testing. :)
</p
>
8779 <p
>If you want to help out with implementing this for Debian Edu,
8780 please contact us on debian-edu@lists.debian.org.
</p
>
8782 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8783 configuration in LDAP that was created around year
2000 by
8784 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8785 Xperience, Inc.,
2000</a
>. I found its
8786 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8787 personal home page over at redhat.com.
</p
>
8792 <title>jXplorer, a very nice LDAP GUI
</title>
8793 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8794 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8795 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8796 <description><p
>Since
8797 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8798 last post
</a
> about available LDAP tools in Debian, I was told about a
8799 LDAP GUI that is even better than luma. The java application
8800 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8801 moving LDAP objects and subtrees using drag-and-drop, and can
8802 authenticate using Kerberos. I have only tested the Kerberos
8803 authentication, but do not have a LDAP setup allowing me to rewrite
8804 LDAP with my test user yet. It is
8805 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8806 Debian
</a
> testing and unstable at the moment. The only problem I
8807 have with it is how it handle errors. If something go wrong, its
8808 non-intuitive behaviour require me to go through some query work list
8809 and remove the failing query. Nothing big, but very annoying.
</p
>
8814 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8815 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8816 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8817 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8818 <description><p
>Here is a short update on my
<a
8819 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8820 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8821 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8822 not reporting the status for KDE, because the upgrade crashes when
8823 aptitude try because of missing conflicts
8824 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8825 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8827 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8828 complete list of the installed packages. Based on this I see these
8829 differences when I did a test run today. As usual, I do not really
8830 know what the correct set of packages would be, but thought it best to
8831 publish the difference.
</p
>
8833 <p
>Installed using apt-get, missing with aptitude
</p
>
8835 <blockquote
><p
>
8836 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8837 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8838 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8839 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8840 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
8841 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
8842 python-
4suite-xml python-eggtrayicon python-gtkhtml2
8843 python-gtkmozembed svgalibg1 xserver-xephyr zip
8844 </p
></blockquote
>
8846 <p
>Installed using apt-get, removed with aptitude
</p
>
8848 <blockquote
><p
>
8849 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
8850 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
8851 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
8852 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
8853 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
8854 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
8855 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8856 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8857 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8858 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
8859 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
8860 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
8861 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
8862 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
8863 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
8864 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
8865 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
8866 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
8867 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
8868 mysql-common swfdec-gnome totem-gstreamer wodim
8869 </p
></blockquote
>
8871 <p
>Installed using aptitude, missing with apt-get
</p
>
8873 <blockquote
><p
>
8874 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
8875 python-gnomekeyring python-wnck rhythmbox-plugins xorg
8876 xserver-xorg-input-all xserver-xorg-input-evdev
8877 xserver-xorg-input-kbd xserver-xorg-input-mouse
8878 xserver-xorg-input-synaptics xserver-xorg-video-all
8879 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
8880 xserver-xorg-video-chips xserver-xorg-video-cirrus
8881 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8882 xserver-xorg-video-glint xserver-xorg-video-i128
8883 xserver-xorg-video-i740 xserver-xorg-video-mach64
8884 xserver-xorg-video-mga xserver-xorg-video-neomagic
8885 xserver-xorg-video-nouveau xserver-xorg-video-nv
8886 xserver-xorg-video-r128 xserver-xorg-video-radeon
8887 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
8888 xserver-xorg-video-s3 xserver-xorg-video-s3virge
8889 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
8890 xserver-xorg-video-sis xserver-xorg-video-sisusb
8891 xserver-xorg-video-tdfx xserver-xorg-video-tga
8892 xserver-xorg-video-trident xserver-xorg-video-tseng
8893 xserver-xorg-video-vesa xserver-xorg-video-vmware
8894 xserver-xorg-video-voodoo
8895 </p
></blockquote
>
8897 <p
>Installed using aptitude, removed with apt-get
</p
>
8899 <blockquote
><p
>
8900 deskbar-applet xserver-xorg xserver-xorg-core
8901 xserver-xorg-input-wacom xserver-xorg-video-intel
8902 xserver-xorg-video-openchrome
8903 </p
></blockquote
>
8905 <p
>I was told on IRC that the xorg-xserver package was
8906 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
8907 in git
</a
> today to try to get apt-get to not remove xorg completely.
8908 No idea when it hits Squeeze, but when it does I hope it will reduce
8909 the difference somewhat.
8914 <title>LUMA, a very nice LDAP GUI
</title>
8915 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
8916 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
8917 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
8918 <description><p
>The last few days I have been looking into the status of the LDAP
8919 directory in Debian Edu, and in the process I started to miss a GUI
8920 tool to browse the LDAP tree. The only one I was able to find in
8921 Debian/Squeeze and Lenny is
8922 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
8923 be a great tool to get a overview of the current LDAP directory
8924 populated by default in Skolelinux. Thanks to it, I have been able to
8925 find empty and obsolete subtrees, misplaced objects and duplicate
8926 objects. It will be installed by default in Debian/Squeeze. If you
8927 are working with LDAP, give it a go. :)
</p
>
8929 <p
>I did notice one problem with it I have not had time to report to
8930 the BTS yet. There is no .desktop file in the package, so the tool do
8931 not show up in the Gnome and KDE menus, but only deep down in in the
8932 Debian submenu in KDE. I hope that can be fixed before Squeeze is
8935 <p
>I have not yet been able to get it to modify the tree yet. I would
8936 like to move objects and remove subtrees directly in the GUI, but have
8937 not found a way to do that with LUMA yet. So in the mean time, I use
8938 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
8940 <p
>If you have tips on other GUI tools for LDAP that might be useful
8941 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
8943 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
8944 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
8945 useful GUI alternative. It seem like a good tool, but is unmaintained
8946 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8947 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
8952 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
8953 <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>
8954 <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>
8955 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
8956 <description><p
>A while back, I
8957 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
8958 about the fact
</a
> that it is not possible with the provided schemas
8959 for storing DNS and DHCP information in LDAP to combine the two sets
8960 of information into one LDAP object representing a computer.
</p
>
8962 <p
>In the mean time, I discovered that a simple fix would be to make
8963 the dhcpHost object class auxiliary, to allow it to be combined with
8964 the dNSDomain object class, and thus forming one object for one
8965 computer when storing both DHCP and DNS information in LDAP.
</p
>
8967 <p
>If I understand this correctly, it is not safe to do this change
8968 without also changing the assigned number for the object class, and I
8969 do not know enough about LDAP schema design to do that properly for
8970 Debian Edu.
</p
>
8972 <p
>Anyway, for future reference, this is how I believe we could change
8974 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
8975 schema
</a
> to solve at least part of the problem with the LDAP schemas
8976 available today from IETF.
</p
>
8979 --- dhcp.schema (revision
65192)
8980 +++ dhcp.schema (working copy)
8982 objectclass (
2.16.840.1.113719.1.203.6.6
8983 NAME
'dhcpHost
'
8984 DESC
'This represents information about a particular client
'
8988 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8989 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
8992 <p
>I very much welcome clues on how to do this properly for Debian
8993 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8994 package, and should thus be free to rewrite it as we see fit.
</p
>
8996 <p
>If you want to help out with implementing this for Debian Edu,
8997 please contact us on debian-edu@lists.debian.org.
</p
>
9002 <title>Calling tasksel like the installer, while still getting useful output
</title>
9003 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9004 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9005 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9006 <description><p
>A few times I have had the need to simulate the way tasksel
9007 installs packages during the normal debian-installer run. Until now,
9008 I have ended up letting tasksel do the work, with the annoying problem
9009 of not getting any feedback at all when something fails (like a
9010 conffile question from dpkg or a download that fails), using code like
9013 <blockquote
><pre
>
9014 export DEBIAN_FRONTEND=noninteractive
9015 tasksel --new-install
9016 </pre
></blockquote
>
9018 This would invoke tasksel, let its automatic task selection pick the
9019 tasks to install, and continue to install the requested tasks without
9020 any output what so ever.
9022 Recently I revisited this problem while working on the automatic
9023 package upgrade testing, because tasksel would some times hang without
9024 any useful feedback, and I want to see what is going on when it
9025 happen. Then it occured to me, I can parse the output from tasksel
9026 when asked to run in test mode, and use that aptitude command line
9027 printed by tasksel then to simulate the tasksel run. I ended up using
9030 <blockquote
><pre
>
9031 export DEBIAN_FRONTEND=noninteractive
9032 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9034 </pre
></blockquote
>
9036 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9037 --without-recommends -o APT::Install-Recommends=no -y install
9038 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9039 ~pimportant
</tt
>", which will install the gnome desktop task, the
9040 laptop task and all packages with priority standard , required and
9041 important, just like tasksel would have done it during
9042 installation.
</p
>
9044 <p
>A better approach is probably to extend tasksel to be able to
9045 install packages without using debconf-apt-progress, for use cases
9046 like this.
</p
>
9051 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9052 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9053 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9054 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9055 <description><p
>My
9056 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9057 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9058 finally made the upgrade logs available from
9059 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9060 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9061 apt and aptitude, and found their differences interesting. This time
9062 I will only focus on their removal plans.
</p
>
9064 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9065 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9066 surprising part is that it want to remove xorg and all
9067 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9068 sure why. When asking aptitude to do the same, it want to remove
129
9069 packages, but most of them are library packages I suspect are no
9070 longer needed. Both of them want to remove bluetooth packages, which
9071 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9073 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9074 which seem like a bad idea and xorg the same way as with Gnome. Asking
9075 aptitude for the same, it wants to remove
192 packages, none which are
9076 too surprising.
</p
>
9078 <p
>I guess the removal of xorg during upgrades should be investigated
9079 and avoided, and perhaps others as well. Here are the complete list
9080 of planned removals. The complete logs is available from the URL
9081 above. Note if you want to repeat these tests, that the upgrade test
9082 for kde+apt-get hung in the tasksel setup because of dpkg asking
9083 conffile questions. No idea why. I worked around it by using
9084 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9087 <p
><b
>apt-get gnome
72</b
>
9088 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9089 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9090 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9091 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9092 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9093 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9094 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9095 xserver-xorg-input-kbd xserver-xorg-input-mouse
9096 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9097 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9098 xserver-xorg-video-ati xserver-xorg-video-chips
9099 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9100 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9101 xserver-xorg-video-glint xserver-xorg-video-i128
9102 xserver-xorg-video-i740 xserver-xorg-video-imstt
9103 xserver-xorg-video-intel xserver-xorg-video-mach64
9104 xserver-xorg-video-mga xserver-xorg-video-neomagic
9105 xserver-xorg-video-nsc xserver-xorg-video-nv
9106 xserver-xorg-video-openchrome xserver-xorg-video-r128
9107 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9108 xserver-xorg-video-rendition xserver-xorg-video-s3
9109 xserver-xorg-video-s3virge xserver-xorg-video-savage
9110 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9111 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9112 xserver-xorg-video-tga xserver-xorg-video-trident
9113 xserver-xorg-video-tseng xserver-xorg-video-v4l
9114 xserver-xorg-video-vesa xserver-xorg-video-vga
9115 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9116 xulrunner-
1.9-gnome-support
</p
>
9118 <p
><b
>aptitude gnome
129</b
>
9120 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9121 djvulibre-desktop finger gnome-app-install gnome-mount
9122 gnome-network-admin gnome-spell gnome-vfs-obexftp
9123 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9124 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9125 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9126 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9127 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9128 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9129 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9130 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9131 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9132 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9133 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9134 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9135 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9136 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9137 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9138 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9139 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9140 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9141 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9142 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9143 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9144 openoffice.org-writer2latex openssl-blacklist p7zip
9145 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9146 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9147 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9148 swfdec-mozilla totem-gstreamer update-manager wodim
9149 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9150 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9153 <p
><b
>apt-get kde
82</b
>
9155 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9156 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9157 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9158 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9159 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9160 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9161 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9162 xserver-xorg-input-kbd xserver-xorg-input-mouse
9163 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9164 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9165 xserver-xorg-video-ati xserver-xorg-video-chips
9166 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9167 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9168 xserver-xorg-video-glint xserver-xorg-video-i128
9169 xserver-xorg-video-i740 xserver-xorg-video-imstt
9170 xserver-xorg-video-intel xserver-xorg-video-mach64
9171 xserver-xorg-video-mga xserver-xorg-video-neomagic
9172 xserver-xorg-video-nsc xserver-xorg-video-nv
9173 xserver-xorg-video-openchrome xserver-xorg-video-r128
9174 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9175 xserver-xorg-video-rendition xserver-xorg-video-s3
9176 xserver-xorg-video-s3virge xserver-xorg-video-savage
9177 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9178 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9179 xserver-xorg-video-tga xserver-xorg-video-trident
9180 xserver-xorg-video-tseng xserver-xorg-video-v4l
9181 xserver-xorg-video-vesa xserver-xorg-video-vga
9182 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9184 <p
><b
>aptitude kde
192</b
>
9185 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9186 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9187 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9188 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9189 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9190 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9191 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9192 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9193 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9194 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9195 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9196 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9197 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9198 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9199 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9200 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9201 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9202 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9203 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9204 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9205 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9206 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9207 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9208 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9209 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9210 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9211 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9212 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9213 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9214 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9215 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9216 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9217 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9218 texlive-common texlive-doc-base texlive-fonts-recommended
9219 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9220 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9221 xulrunner-
1.9</p
>
9227 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9228 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9229 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9230 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9231 <description><p
>The last few days I have done some upgrade testing in Debian, to
9232 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9233 have been discovered and reported in the process
9234 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9235 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9236 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9237 kdebase-workspace-data), and to get a more regular testing going on, I
9238 am working on a script to automate the test.
</p
>
9240 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9241 Gnome or KDE desktop installation inside the chroot before upgrading
9242 it. To ensure no services are started in the chroot, a policy-rc.d
9243 script is inserted. To make sure tasksel believe it is to install a
9244 desktop on a laptop, the tasksel tests are replaced in the chroot
9245 (only acceptable because this is a throw-away chroot).
</p
>
9247 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9248 currently always fail because udev refuses to upgrade with the kernel
9249 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9250 is created. The bug report
9251 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9252 this problem do not trigger in a chroot, but I touch the file anyway
9253 to make sure the upgrade go well. Testing on virtual and real
9254 hardware have failed me because of udev so far, and creating this file
9255 do the trick in such settings anyway. This is a
9256 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9257 issue
</a
> and the current udev behaviour is intended by the udev
9258 maintainer because he lack the resources to rewrite udev to keep
9259 working with old kernels or something like that. I really wish the
9260 udev upstream would keep udev backwards compatible, to avoid such
9261 upgrade problem, but given that they fail to do so, I guess
9262 documenting the way out of this mess is the best option we got for
9263 Debian Squeeze.
</p
>
9265 <p
>Anyway, back to the task at hand, testing upgrades. This test
9266 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9269 <blockquote
><pre
>
9273 if [
"$
1" ] ; then
9282 exec
&lt; /dev/null
9284 mirror=http://ftp.skolelinux.org/debian
9285 tmpdir=chroot-$from-upgrade-$to-$desktop
9287 debootstrap $from $tmpdir $mirror
9288 chroot $tmpdir aptitude update
9289 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9293 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9297 mount -t proc proc $tmpdir/proc
9298 # Make sure proc is unmounted also on failure
9299 trap exit_cleanup EXIT INT
9301 chroot $tmpdir aptitude -y install debconf-utils
9303 # Make sure tasksel autoselection trigger. It need the test scripts
9304 # to return the correct answers.
9305 echo tasksel tasksel/desktop multiselect $desktop | \
9306 chroot $tmpdir debconf-set-selections
9308 # Include the desktop and laptop task
9309 for test in desktop laptop ; do
9310 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9314 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9317 DEBIAN_FRONTEND=noninteractive
9318 DEBIAN_PRIORITY=critical
9319 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9320 chroot $tmpdir tasksel --new-install
9322 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9323 chroot $tmpdir aptitude update
9324 touch $tmpdir/etc/udev/kernel-upgrade
9325 chroot $tmpdir aptitude -y dist-upgrade
9327 </pre
></blockquote
>
9329 <p
>I suspect it would be useful to test upgrades with both apt-get and
9330 with aptitude, but I have not had time to look at how they behave
9331 differently so far. I hope to get a cron job running to do the test
9332 regularly and post the result on the web. The Gnome upgrade currently
9333 work, while the KDE upgrade fail because of the bug in
9334 kdebase-workspace-data
</p
>
9336 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9337 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9338 post, so I will refrain from trying. I can report that for Gnome,
9339 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9340 remove and
1 not upgraded and
1024MB need to be downloaded while for
9341 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9342 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9344 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9345 is able to migrate to dependency based boot sequencing and parallel
9346 booting without a hitch. Was unsure if there were still bugs with
9347 packages failing to clean up their obsolete init.d script during
9348 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9354 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9355 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9356 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9357 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9358 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9359 scripts to migrate (some of) their operations to upstart job while
9360 keeping the init.d for hurd and kfreebsd. The packages with such
9361 needs will need a way to get their init.d scripts to behave
9362 differently when used with sysvinit and with upstart. Because of
9363 this, I had a look at the environment variables set when a init.d
9364 script is running under upstart, and when it is not.
</p
>
9366 <p
>With upstart, I notice these environment variables are set when a
9367 script is started from rcS.d/ (ignoring some irrelevant ones like
9370 <blockquote
><pre
>
9376 UPSTART_EVENTS=startup
9378 UPSTART_JOB=rc-sysinit
9379 </pre
></blockquote
>
9381 <p
>With sysvinit, these environment variables are set for the same
9384 <blockquote
><pre
>
9385 INIT_VERSION=sysvinit-
2.88
9390 </pre
></blockquote
>
9392 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9393 sysvinit are not set by upstart. Not sure if it is intentional or not
9394 to not be compatible with sysvinit in this regard.
</p
>
9396 <p
>For scripts needing to behave differently when upstart is used,
9397 looking for the UPSTART_JOB environment variable seem to be a good
9403 <title>A manual for standards wars...
</title>
9404 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9405 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9406 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9407 <description><p
>Via the
9408 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9409 of Rob Weir
</a
> I came across the very interesting essay named
9410 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9411 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9412 following the standards wars of today.
</p
>
9417 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9418 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9419 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9420 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9421 <description><p
>When using sitesummary at a site to track machines, it is possible
9422 to get a list of the machine types in use thanks to the DMI
9423 information extracted from each machine. The script to do so is
9424 included in the sitesummary package, and here is example output from
9425 the Skolelinux build servers:
</p
>
9427 <blockquote
><pre
>
9428 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9430 Dell Computer Corporation
1
9433 eserver xSeries
345 -[
8670M1X]-
1
9437 </pre
></blockquote
>
9439 <p
>The quality of the report depend on the quality of the DMI tables
9440 provided in each machine. Here there are Intel machines without model
9441 information listed with Intel as vendor and no model, and virtual Xen
9442 machines listed as [no-dmi-info]. One can add -l as a command line
9443 option to list the individual machines.
</p
>
9445 <p
>A larger list is
9446 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9447 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9448 provide the basic sitesummary report publicly. In their report there
9449 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9450 their machines, and as sitesummary is available in both distributions,
9451 it is trivial to get all of them to report to the same central
9452 collector.
</p
>
9457 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9458 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9459 <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>
9460 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9461 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9462 start at boot when an NVidia video card is used is handled. The
9463 problem seem to be that the nvidia X.org driver uses a long time to
9464 initialize, and this duration is longer than kdm is configured to
9467 <p
>I came across two bugs related to this issue,
9468 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9469 against initscripts and passed on to nvidia-glx when it became obvious
9470 that the nvidia drivers were involved, and
9471 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9472 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9474 <p
>To me, it seem that no-one is interested in actually solving the
9475 problem nvidia video card owners experience and make sure the Debian
9476 distribution work out of the box for these users. The nvidia driver
9477 maintainers expect kdm to be set up to wait longer, while kdm expect
9478 the nvidia driver maintainers to fix the driver to start faster, and
9479 while they wait for each other I guess the users end up switching to a
9480 distribution that work for them. I have no idea what the solution is,
9481 but I am pretty sure that waiting for each other is not it.
</p
>
9483 <p
>I wonder why we end up handling bugs this way.
</p
>
9488 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9489 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9490 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9491 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9492 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9493 The feature seem to hold up pretty well, but three fairly serious
9494 issues are known and should be solved:
9498 <li
>The wicd package seen to
9499 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9500 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9501 parallel booting is enabled. No idea why, but the wicd maintainer
9502 seem to be on the case.
</li
>
9504 <li
>The nvidia X driver seem to
9505 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9506 triggered more easily when parallel booting is in effect. The
9507 maintainer is on the case.
</li
>
9509 <li
>The sysv-rc package fail to properly enable dependency based boot
9510 sequencing (the shutdown is broken) when old file-rc users
9511 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9512 sysv-rc. One way to solve it would be for file-rc to create
9513 /etc/init.d/.legacy-bootordering, and another is to try to make
9514 sysv-rc more robust. Will investigate some more and probably upload a
9515 workaround in sysv-rc to help those trying to move from file-rc to
9516 sysv-rc get a working shutdown.
</li
>
9518 </ul
></p
>
9520 <p
>All in all not many surprising issues, and all of them seem
9521 solvable before Squeeze is released. In addition to these there are
9522 some packages with bugs in their dependencies and run level settings,
9523 which I expect will be fixed in a reasonable time span.
</p
>
9525 <p
>If you report any problems with dependencies in init.d scripts to
9526 the BTS, please usertag the report to get it to show up at
9527 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9528 list of usertagged bugs related to this
</a
>.
</p
>
9530 <p
>Update: Correct bug number to file-rc issue.
</p
>
9535 <title>More flexible firmware handling in debian-installer
</title>
9536 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9537 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9538 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9539 <description><p
>After a long break from debian-installer development, I finally
9540 found time today to return to the project. Having to spend less time
9541 working dependency based boot in debian, as it is almost complete now,
9542 definitely helped freeing some time.
</p
>
9544 <p
>A while back, I ran into a problem while working on Debian Edu. We
9545 include some firmware packages on the Debian Edu CDs, those needed to
9546 get disk and network controllers working. Without having these
9547 firmware packages available during installation, it is impossible to
9548 install Debian Edu on the given machine, and because our target group
9549 are non-technical people, asking them to provide firmware packages on
9550 an external medium is a support pain. Initially, I expected it to be
9551 enough to include the firmware packages on the CD to get
9552 debian-installer to find and use them. This proved to be wrong.
9553 Next, I hoped it was enough to symlink the relevant firmware packages
9554 to some useful location on the CD (tried /cdrom/ and
9555 /cdrom/firmware/). This also proved to not work, and at this point I
9556 found time to look at the debian-installer code to figure out what was
9557 going to work.
</p
>
9559 <p
>The firmware loading code is in the hw-detect package, and a closer
9560 look revealed that it would only look for firmware packages outside
9561 the installation media, so the CD was never checked for firmware
9562 packages. It would only check USB sticks, floppies and other
9563 "external
" media devices. Today I changed it to also look in the
9564 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9565 solve the problem I ran into with Debian edu. I also changed it to
9566 look in /firmware/, to make sure the installer also find firmware
9567 provided in the initrd when booting the installer via PXE, to allow us
9568 to provide the same feature in the PXE setup included in Debian
9571 <p
>To make sure firmware deb packages with a license questions are not
9572 activated without asking if the license is accepted, I extended
9573 hw-detect to look for preinst scripts in the firmware packages, and
9574 run these before activating the firmware during installation. The
9575 license question is asked using debconf in the preinst, so this should
9576 solve the issue for the firmware packages I have looked at so far.
</p
>
9578 <p
>If you want to discuss the details of these features, please
9579 contact us on debian-boot@lists.debian.org.
</p
>
9584 <title>Parallellized boot is now the default in Debian/unstable
</title>
9585 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9587 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9588 <description><p
>Since this evening, parallel booting is the default in
9589 Debian/unstable for machines using dependency based boot sequencing.
9590 Apparently the testing of concurrent booting has been wider than
9591 expected, if I am to believe the
9592 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9593 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9594 with the feature this weekend, to give us some time to detect any
9595 remaining problems before Squeeze is frozen. If serious problems are
9596 detected, it is simple to change the default back to sequential boot.
9597 The upload of the new sysvinit package also activate a new upstream
9600 More information about
9601 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9602 based boot sequencing
</a
> is available from the Debian wiki. It is
9603 currently possible to disable parallel booting when one run into
9604 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9606 <blockquote
><pre
>
9608 </pre
></blockquote
>
9610 <p
>If you report any problems with dependencies in init.d scripts to
9611 the BTS, please usertag the report to get it to show up at
9612 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9613 list of usertagged bugs related to this
</a
>.
</p
>
9618 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9619 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9620 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9621 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9622 <description><p
>In the recent Debian Edu versions, the
9623 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9624 system
</a
> is used to keep track of the machines in the school
9625 network. Each machine will automatically report its status to the
9626 central server after boot and once per night. The network setup is
9627 also reported, and using this information it is possible to get the
9628 MAC address of all network interfaces in the machines. This is useful
9629 to update the DHCP configuration.
</p
>
9631 <p
>To give some idea how to use sitesummary, here is a one-liner to
9632 ist all MAC addresses of all machines reporting to sitesummary. Run
9633 this on the collector host:
</p
>
9635 <blockquote
><pre
>
9636 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9637 </pre
></blockquote
>
9639 <p
>This will list all MAC addresses assosiated with all machine, one
9640 line per machine and with space between the MAC addresses.
</p
>
9642 <p
>To allow system administrators easier job at adding static DHCP
9643 addresses for hosts, it would be possible to extend this to fetch
9644 machine information from sitesummary and update the DHCP and DNS
9645 tables in LDAP using this information. Such tool is unfortunately not
9646 written yet.
</p
>
9651 <title>systemd, an interesting alternative to upstart
</title>
9652 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9654 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9655 <description><p
>The last few days a new boot system called
9656 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9658 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9660 to the free software world. I have not yet had time to play around
9661 with it, but it seem to be a very interesting alternative to
9662 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9663 a good alternative for Debian when we are able to switch to an event
9664 based boot system. Tollef is
9665 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9666 systemd into Debian, and I look forward to seeing how well it work. I
9667 like the fact that systemd handles init.d scripts with dependency
9668 information natively, allowing them to run in parallel where upstart
9669 at the moment do not.
</p
>
9671 <p
>Unfortunately do systemd have the same problem as upstart regarding
9672 platform support. It only work on recent Linux kernels, and also need
9673 some new kernel features enabled to function properly. This means
9674 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9675 system. Not sure how that will be handled if systemd proves to be the
9676 way forward.
</p
>
9678 <p
>In the mean time, based on the
9679 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9680 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9681 decided to enable full parallel booting as the default in Debian as
9682 soon as possible (probably this weekend or early next week), to see if
9683 there are any remaining serious bugs in the init.d dependencies. A
9684 new version of the sysvinit package implementing this change is
9685 already in experimental. If all go well, Squeeze will be released
9686 with parallel booting enabled by default.
</p
>
9691 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9692 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9693 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9694 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9695 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9696 complete, so complete that it is actually possible to run all the
9697 init.d scripts in parallell based on these dependencies. If you want
9698 to test your Squeeze system, make sure
9699 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9700 based boot sequencing
</a
> is enabled, and add this line to
9701 /etc/default/rcS:
</p
>
9703 <blockquote
><pre
>
9704 CONCURRENCY=makefile
9705 </pre
></blockquote
>
9707 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9708 scripts in parallel using the dependency information stored in
9709 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9710 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9711 to try to start the kdm and gdm scripts as early as possible, and will
9712 start the facilities required by kdm or gdm as early as possible to
9713 make this happen.
</p
>
9715 <p
>Give it a try, and see if you like the result. If some services
9716 fail to start properly, it is most likely because they have incomplete
9717 init.d script dependencies in their startup script (or some of their
9718 dependent scripts have incomplete dependencies). Report bugs and get
9719 the package maintainers to fix it. :)
</p
>
9721 <p
>Running scripts in parallel could be the default in Debian when we
9722 manage to get the init.d script dependencies complete and correct. I
9723 expect we will get there in Squeeze+
1, if we get manage to test and
9724 fix the remaining issues.
</p
>
9726 <p
>If you report any problems with dependencies in init.d scripts to
9727 the BTS, please usertag the report to get it to show up at
9728 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9729 list of usertagged bugs related to this
</a
>.
</p
>
9734 <title>Debian has switched to dependency based boot sequencing
</title>
9735 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9736 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9737 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9738 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9739 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9740 have been migrated to using dependency based boot sequencing. This
9741 conclude work me and others have been doing for the last three days.
9742 It feels great to see this finally part of the default Debian
9743 installation. Now we just need to weed out the last few problems that
9744 are bound to show up, to get everything ready for Squeeze.
</p
>
9746 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9747 fixing the more fundamental problem of handing the event based
9748 non-predictable kernel in the early boot.
</p
>
9753 <title>Taking over sysvinit development
</title>
9754 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9755 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9756 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9757 <description><p
>After several years of frustration with the lack of activity from
9758 the existing sysvinit upstream developer, I decided a few weeks ago to
9759 take over the package and become the new upstream. The number of
9760 patches to track for the Debian package was becoming a burden, and the
9761 lack of synchronization between the distribution made it hard to keep
9762 the package up to date.
</p
>
9764 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9765 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9766 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9767 and Fedora), based on the patches currently in use in these
9768 distributions. We Debian maintainers plan to move to this tarball as
9769 the new upstream as soon as we find time to do the merge. Since the
9770 new tarball was created, we agreed with Werner at SuSe to make a new
9771 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9772 development there. The project is registered and currently waiting
9773 for approval by the Savannah administrators, and as soon as it is
9774 approved, we will import the old versions from svn and continue
9775 working on the future release.
</p
>
9777 <p
>It is a bit ironic that this is done now, when some of the involved
9778 distributions are moving to upstart as a syvinit replacement.
</p
>
9783 <title>Debian boots quicker and quicker
</title>
9784 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9785 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9786 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9787 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9788 people involved in the boot system on Debian and Ubuntu, to see if we
9789 could find more ways to speed up the boot system. This was an Ubuntu
9791 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9792 gathering
</a
>. It was quite productive. We also discussed the future
9793 of boot systems, and ways to handle the increasing number of boot
9794 issues introduced by the Linux kernel becoming more and more
9795 asynchronous and event base. The Ubuntu approach using udev and
9796 upstart might be a good way forward. Time will show.
</p
>
9798 <p
>Anyway, there are a few ways at the moment to speed up the boot
9799 process in Debian. All of these should be applied to get a quick
9804 <li
>Use dash as /bin/sh.
</li
>
9806 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9807 clock is in UTC.
</li
>
9809 <li
>Install and activate the insserv package to enable
9810 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9811 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9815 These points are based on the Google summer of code work done by
9816 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9819 <p
>Support for makefile-style concurrency during boot was uploaded to
9820 unstable yesterday. When we tested it, we were able to cut
6 seconds
9821 from the boot sequence. It depend on very correct dependency
9822 declaration in all init.d scripts, so I expect us to find edge cases
9823 where the dependences in some scripts are slightly wrong when we start
9824 using this.
</p
>
9826 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9827 introduced by Raphael Geissert today, one that could affect the
9828 startup speed as well. Instead of starting some scripts concurrently
9829 from rcS.d/ and another set of scripts from rc2.d/, it would be
9830 possible to run a of them in the same process. A quick way to test
9831 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9832 insserv
'. Will need to test if that work. :)
</p
>
9837 <title>BSAs påstander om piratkopiering møter motstand
</title>
9838 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9839 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9840 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
9841 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
9842 programvareselskapene som Microsoft og Apple, publisert en rapport der
9843 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
9844 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
9846 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
9847 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
9848 dagene. Et spesielt interessant kommentar fra Sverige,
9849 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
9850 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
9853 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
9854 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
9855 företag.
"Man bör nog kanske inte se de här siffrorna som helt
9856 exakta
", säger BSAs Sverigechef John Hugosson.
9859 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
9860 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
9861 piracy figures need a shot of reality
</a
> og
<a
9862 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
9863 Copyright Treaty Work?
</a
></p
>
9865 <p
>Fant lenkene via
<a
9866 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
9867 på Slashdot
</a
>.
</p
>
9872 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
9873 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
9874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
9875 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
9876 <description><p
>Kom over
9877 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
9878 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
9879 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
9880 jobber til daglig. En rask opptelling forteller meg at vi har
490
9881 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
9882 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
9883 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
9888 <title>Kryptert harddisk - naturligvis
</title>
9889 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
9890 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
9891 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
9892 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
9893 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
9894 når en tar tap av arbeidstid, fortrolige dokumenter,
9895 personopplysninger og alt annet det innebærer. Det er ingen tvil om
9896 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
9897 til at jeg har kryptert harddisken på både kontormaskinen og min
9898 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
9899 komme på avveie, den første informasjon relatert til jobben min ved
9900 Universitetet i Oslo, og den andre relatert til blant annet
9901 foreningsarbeide. Kryptering av diskene gjør at det er lite
9902 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
9903 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
9904 og en reboot vil gjøre at de ber om passord før de vil starte opp.
9905 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
9906 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
9907 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
9908 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
9909 det er gjort slik jeg gjør det er minimale, og gevinstene er
9910 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
9911 maskinen reinstalleres og alt er tapt.
</p
>
9913 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
9914 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
9915 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
9916 er for min del høyere enn gevinsten. Jeg tror oddsene for at
9917 f.eks. etteretningsorganisasjoner har glede av å titte på mine
9918 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
9919 gjøre det vanskeligere for angripere med kompetanse og ressurser er
9920 betydelige.
</p
>
9925 <title>Two projects that have improved the quality of free software a lot
</title>
9926 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
9927 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
9928 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
9929 <description><p
>There are two software projects that have had huge influence on the
9930 quality of free software, and I wanted to mention both in case someone
9931 do not yet know them.
</p
>
9933 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
9934 tool to detect and expose errors in the memory handling of programs.
9935 It is easy to use, all one need to do is to run
'valgrind program
',
9936 and it will report any problems on stdout. It is even better if the
9937 program include debug information. With debug information, it is able
9938 to report the source file name and line number where the problem
9939 occurs. It can report things like
'reading past memory block in file
9940 X line N, the memory block was allocated in file Y, line M
', and
9941 'using uninitialised value in control logic
'. This tool has made it
9942 trivial to investigate reproducible crash bugs in programs, and have
9943 reduced the number of this kind of bugs in free software a lot.
9945 <p
>The second one is
9946 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
9947 a source code checker. It is able to process the source of a program
9948 and find problems in the logic without running the program. It
9949 started out as the Stanford Checker and became well known when it was
9950 used to find bugs in the Linux kernel. It is now a commercial tool
9951 and the company behind it is running
9952 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
9953 free software community, where a lot of free software projects get
9954 their source checked for free. Several thousand defects have been
9955 found and fixed so far. It can find errors like
'lock L taken in file
9956 X line N is never released if exiting in line M
', or
'the code in file
9957 Y lines O to P can never be executed
'. The projects included in the
9958 community service project have managed to get rid of a lot of
9959 reliability problems thanks to Coverity.
</p
>
9961 <p
>I believe tools like this, that are able to automatically find
9962 errors in the source, are vital to improve the quality of software and
9963 make sure we can get rid of the crashing and failing software we are
9964 surrounded by today.
</p
>
9969 <title>No patch is not better than a useless patch
</title>
9970 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
9971 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
9972 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
9973 <description><p
>Julien Blache
9974 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
9975 patch is better than a useless patch
</a
>. I completely disagree, as a
9976 patch allow one to discuss a concrete and proposed solution, and also
9977 prove that the issue at hand is important enough for someone to spent
9978 time on fixing it. No patch do not provide any of these positive
9979 properties.
</p
>
9984 <title>Standardize on protocols and formats, not vendors and applications
</title>
9985 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
9986 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
9987 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
9988 <description><p
>Where I work at the University of Oslo, one decision stand out as a
9989 very good one to form a long lived computer infrastructure. It is the
9990 simple one, lost by many in todays computer industry: Standardize on
9991 open network protocols and open exchange/storage formats, not applications.
9992 Applications come and go, while protocols and files tend to stay, and
9993 thus one want to make it easy to change application and vendor, while
9994 avoiding conversion costs and locking users to a specific platform or
9995 application.
</p
>
9997 <p
>This approach make it possible to replace the client applications
9998 independently of the server applications. One can even allow users to
9999 use several different applications as long as they handle the selected
10000 protocol and format. In the normal case, only one client application
10001 is recommended and users only get help if they choose to use this
10002 application, but those that want to deviate from the easy path are not
10003 blocked from doing so.
</p
>
10005 <p
>It also allow us to replace the server side without forcing the
10006 users to replace their applications, and thus allow us to select the
10007 best server implementation at any moment, when scale and resouce
10008 requirements change.
</p
>
10010 <p
>I strongly recommend standardizing - on open network protocols and
10011 open formats, but I would never recommend standardizing on a single
10012 application that do not use open network protocol or open formats.
</p
>
10017 <title>Returning from Skolelinux developer gathering
</title>
10018 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10019 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10020 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10021 <description><p
>I
'm sitting on the train going home from this weekends Debian
10022 Edu/Skolelinux development gathering. I got a bit done tuning the
10023 desktop, and looked into the dynamic service location protocol
10024 implementation avahi. It look like it could be useful for us. Almost
10025 30 people participated, and I believe it was a great environment to
10026 get to know the Skolelinux system. Walter Bender, involved in the
10027 development of the Sugar educational platform, presented his stuff and
10028 also helped me improve my OLPC installation. He also showed me that
10029 his Turtle Art application can be used in standalone mode, and we
10030 agreed that I would help getting it packaged for Debian. As a
10031 standalone application it would be great for Debian Edu. We also
10032 tried to get the video conferencing working with two OLPCs, but that
10033 proved to be too hard for us. The application seem to need more work
10034 before it is ready for me. I look forward to getting home and relax
10040 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10041 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10042 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10043 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10044 <description><p
>The state of standardized LDAP schemas on Linux is far from
10045 optimal. There is RFC
2307 documenting one way to store NIS maps in
10046 LDAP, and a modified version of this normally called RFC
2307bis, with
10047 some modifications to be compatible with Active Directory. The RFC
10048 specification handle the content of a lot of system databases, but do
10049 not handle DNS zones and DHCP configuration.
</p
>
10051 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10052 we would like to store information about users, SMB clients/hosts,
10053 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10054 and LTSP configuration in LDAP. These objects have a lot in common,
10055 but with the current LDAP schemas it is not possible to have one
10056 object per entity. For example, one need to have at least three LDAP
10057 objects for a given computer, one with the SMB related stuff, one with
10058 DNS information and another with DHCP information. The schemas
10059 provided for DNS and DHCP are impossible to combine into one LDAP
10060 object. In addition, it is impossible to implement quick queries for
10061 netgroup membership, because of the way NIS triples are implemented.
10062 It just do not scale. I believe it is time for a few RFC
10063 specifications to cleam up this mess.
</p
>
10065 <p
>I would like to have one LDAP object representing each computer in
10066 the network, and this object can then keep the SMB (ie host key), DHCP
10067 (mac address/name) and DNS (name/IP address) settings in one place.
10068 It need to be efficently stored to make sure it scale well.
</p
>
10070 <p
>I would also like to have a quick way to map from a user or
10071 computer and to the net group this user or computer is a member.
</p
>
10073 <p
>Active Directory have done a better job than unix heads like myself
10074 in this regard, and the unix side need to catch up. Time to start a
10075 new IETF work group?
</p
>
10080 <title>Endelig er Debian Lenny gitt ut
</title>
10081 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10082 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10083 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10084 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10085 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10086 Et langt steg videre for Debian-prosjektet, og en rekke nye
10087 programpakker blir nå tilgjengelig for de av oss som bruker den
10088 stabile utgaven av Debian. Neste steg er nå å få
10089 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10090 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10091 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10092 slippes løs på skolene. Takk til alle debian-utviklerne som har
10093 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10094 bootsekvens tilgjengelig i stabil utgave, vha pakken
10095 <tt
>insserv
</tt
>.
</p
>
10100 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10101 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10102 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10103 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10104 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10105 Oslo. Most of Saturday was used for the general assemly for the
10106 member organization, but the rest of the weekend I used to tune the
10107 LTSP installation. LTSP now work out of the box on the
10-network.
10108 Acer Aspire One proved to be a very nice thin client, with both
10109 screen, mouse and keybard in a small box. Was working on getting the
10110 diskless workstation setup configured out of the box, but did not
10111 finish it before the weekend was up.
</p
>
10113 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10114 the Brazilian group, so that will have to wait for the next
10115 development gathering. Would love to have the Debian Edu installer
10116 automatically detect and configure a multiseat setup when it find one
10117 of these cards.
</p
>
10122 <title>The sorry state of multimedia browser plugins in Debian
</title>
10123 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10124 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10125 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10126 <description><p
>Recently I have spent some time evaluating the multimedia browser
10127 plugins available in Debian Lenny, to see which one we should use by
10128 default in Debian Edu. We need an embedded video playing plugin with
10129 control buttons to pause or stop the video, and capable of streaming
10130 all the multimedia content available on the web. The test results and
10131 notes are available on
10132 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10133 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10134 fill this need. My personal video player favorite, VLC, has a really
10135 bad plugin which fail on a lot of the test pages. A lot of the MIME
10136 types I would expect to work with any free software player (like
10137 video/ogg), just do not work. And simple formats like the
10138 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10139 totem and vlc plugins. I hope the situation will improve soon. No
10140 wonder sites use the proprietary Adobe flash to play video.
</p
>
10142 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10143 be the only one fitting our needs. :/
</p
>