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>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
11 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</guid>
13 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
14 <description><p
>For almost a year now, we have been working on making a Norwegian
15 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
16 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
17 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
18 we are working on the proof reading to ensure consistent language and
19 use of correct computer science terms. The plan is to make the book
20 available on paper, as well as in electronic form. For that to
21 happen, the proof reading must be completed and all the figures need
22 to be translated. If you want to help out, get in touch.
</p
>
24 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
26 fresh PDF edition
</a
> in A4 format (the final book will have smaller
27 pages) of the book created every morning is available for
28 proofreading. If you find any errors, please
29 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
30 Weblate and correct the error
</a
>. The
31 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
32 of the translation including figures
</a
> is a useful source for those
33 provide Norwegian bokmål screen shots and figures.
</p
>
38 <title>Unlimited randomness with the ChaosKey?
</title>
39 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
40 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
41 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
42 <description><p
>A few days ago I ordered a small batch of
43 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
44 USB dongle for generating entropy created by Bdale Garbee and Keith
45 Packard. Yesterday it arrived, and I am very happy to report that it
46 work great! According to its designers, to get it to work out of the
47 box, you need the Linux kernel version
4.1 or later. I tested on a
48 Debian Stretch machine (kernel version
4.9), and there it worked just
49 fine, increasing the available entropy very quickly. I wrote a small
50 test oneliner to test. It first print the current entropy level,
51 drain /dev/random, and then print the entropy level for five seconds.
52 Here is the situation without the ChaosKey inserted:
</p
>
54 <blockquote
><pre
>
55 % cat /proc/sys/kernel/random/entropy_avail; \
56 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
57 for n in $(seq
1 5); do \
58 cat /proc/sys/kernel/random/entropy_avail; \
64 28 byte kopiert,
0,
000264565 s,
106 kB/s
71 </pre
></blockquote
>
73 <p
>The entropy level increases by
3-
4 every second. In such case any
74 application requiring random bits (like a HTTPS enabled web server)
75 will halt and wait for more entrpy. And here is the situation with
76 the ChaosKey inserted:
</p
>
78 <blockquote
><pre
>
79 % cat /proc/sys/kernel/random/entropy_avail; \
80 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
81 for n in $(seq
1 5); do \
82 cat /proc/sys/kernel/random/entropy_avail; \
88 104 byte kopiert,
0,
000487647 s,
213 kB/s
95 </pre
></blockquote
>
97 <p
>Quite the difference. :) I bought a few more than I need, in case
98 someone want to buy one here in Norway. :)
</p
>
100 <p
>Update: The dongle was presented at Debconf last year. You might
101 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
102 recording illuminating
</a
>. It explains exactly what the source of
103 randomness is, if you are unable to spot it from the schema drawing
104 available from the ChaosKey web site linked at the start of this blog
110 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
111 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
113 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
114 <description><p
>Did you ever wonder where the web trafic really flow to reach the
115 web servers, and who own the network equipment it is flowing through?
116 It is possible to get a glimpse of this from using traceroute, but it
117 is hard to find all the details. Many years ago, I wrote a system to
118 map the Norwegian Internet (trying to figure out if our plans for a
119 network game service would get low enough latency, and who we needed
120 to talk to about setting up game servers close to the users. Back
121 then I used traceroute output from many locations (I asked my friends
122 to run a script and send me their traceroute output) to create the
123 graph and the map. The output from traceroute typically look like
127 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
128 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
129 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
130 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
131 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
132 5 he16-
1-
1.cr1.san110.as2116.net (
195.0.244.234)
2.627 ms he16-
1-
1.cr2.oslosda310.as2116.net (
195.0.244.48)
3.172 ms he16-
1-
1.cr1.san110.as2116.net (
195.0.244.234)
2.857 ms
133 6 ae1.ar8.oslosda310.as2116.net (
195.0.242.39)
0.662 ms
0.637 ms ae0.ar8.oslosda310.as2116.net (
195.0.242.23)
0.622 ms
134 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
138 </pre
></p
>
140 <p
>This show the DNS names and IP addresses of (at least some of the)
141 network equipment involved in getting the data traffic from me to the
142 www.stortinget.no server, and how long it took in milliseconds for a
143 package to reach the equipment and return to me. Three packages are
144 sent, and some times the packages do not follow the same path. This
145 is shown for hop
5, where three different IP addresses replied to the
146 traceroute request.
</p
>
148 <p
>There are many ways to measure trace routes. Other good traceroute
149 implementations I use are traceroute (using ICMP packages) mtr (can do
150 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
151 traceroute and a lot of other capabilities). All of them are easily
152 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
154 <p
>This time around, I wanted to know the geographic location of
155 different route points, to visualize how visiting a web page spread
156 information about the visit to a lot of servers around the globe. The
157 background is that a web site today often will ask the browser to get
158 from many servers the parts (for example HTML, JSON, fonts,
159 JavaScript, CSS, video) required to display the content. This will
160 leak information about the visit to those controlling these servers
161 and anyone able to peek at the data traffic passing by (like your ISP,
162 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
164 <p
>Lets pick an example, the Norwegian parliament web site
165 www.stortinget.no. It is read daily by all members of parliament and
166 their staff, as well as political journalists, activits and many other
167 citizens of Norway. A visit to the www.stortinget.no web site will
168 ask your browser to contact
8 other servers: ajax.googleapis.com,
169 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
170 stats.g.doubleclick.net, www.google-analytics.com,
171 www.googletagmanager.com and www.netigate.se. I extracted this by
172 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
173 Stortinget web page and tell me all the URLs PhantomJS downloaded to
174 render the page (in HAR format using
175 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
176 netsniff example
</a
>. I am very grateful to Gorm for showing me how
177 to do this). My goal is to visualize network traces to all IP
178 addresses behind these DNS names, do show where visitors personal
179 information is spread when visiting the page.
</p
>
181 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
182 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geoip-small.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using GeoIP
"/
></a
></p
>
184 <p
>When I had a look around for options, I could not find any good
185 free software tools to do this, and decided I needed my own traceroute
186 wrapper outputting KML based on locations looked up using GeoIP. KML
187 is easy to work with and easy to generate, and understood by several
188 of the GIS tools I have available. I got good help from by NUUG
189 colleague Anders Einar with this, and the result can be seen in
190 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
191 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
192 free GeoIP databases I could find (and the for-pay databases my
193 friends had access to) is not up to the task. The IP addresses of
194 central Internet infrastructure would typically be placed near the
195 controlling companies main office, and not where the router is really
196 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
197 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
199 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
200 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy-small.png
" alt=
"scapy traceroute graph for URLs used by www.stortinget.no
"/
></a
></p
>
202 <p
>I also had a look at the visual traceroute graph created by
203 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
204 showing IP network ownership (aka AS owner) for the IP address in
206 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
207 graph display a lot of useful information about the traceroute in SVG
208 format
</a
>, and give a good indication on who control the network
209 equipment involved, but it do not include geolocation. This graph
210 make it possible to see the information is made available at least for
211 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
212 3 Communications and NetDNA.
</p
>
214 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
215 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-small.png
" alt=
"example geotraceroute view for www.stortinget.no
"/
></a
></p
>
217 <p
>In the process, I came across the
218 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
219 Salim Gasmi. Its methology of combining guesses based on DNS names,
220 various location databases and finally use latecy times to rule out
221 candidate locations seemed to do a very good job of guessing correct
222 geolocation. But it could only do one trace at the time, did not have
223 a sensor in Norway and did not make the geolocations easily available
224 for postprocessing. So I contacted the developer and asked if he
225 would be willing to share the code (he refused until he had time to
226 clean it up), but he was interested in providing the geolocations in a
227 machine readable format, and willing to set up a sensor in Norway. So
228 since yesterday, it is possible to run traces from Norway in this
229 service thanks to a sensor node set up by
230 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
231 trace in KML format for further processing.
</p
>
233 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
234 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using geotraceroute
"/
></a
></p
>
236 <p
>Here we can see a lot of trafic passes Sweden on its way to
237 Denmark, Germany, Holland and Ireland. Plenty of places where the
238 Snowden confirmations verified the traffic is read by various actors
239 without your best interest as their top priority.
</p
>
241 <p
>Combining KML files is trivial using a text editor, so I could loop
242 over all the hosts behind the urls imported by www.stortinget.no and
243 ask for the KML file from GeoTraceroute, and create a combined KML
244 file with all the traces (unfortunately only one of the IP addresses
245 behind the DNS name is traced this time. To get them all, one would
246 have to request traces using IP number instead of DNS names from
247 GeoTraceroute). That might be the next step in this project.
</p
>
249 <p
>Armed with these tools, I find it a lot easier to figure out where
250 the IP traffic moves and who control the boxes involved in moving it.
251 And every time the link crosses for example the Swedish border, we can
252 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
253 Britain and NSA in USA and cables around the globe. (Hm, what should
254 we tell them? :) Keep that in mind if you ever send anything
255 unencrypted over the Internet.
</p
>
257 <p
>PS: KML files are drawn using
258 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
259 Rublev
<a/
>, as it was less cluttered than the local Linux application
260 Marble. There are heaps of other options too.
</p
>
262 <p
>As usual, if you use Bitcoin and want to show your support of my
263 activities, please send Bitcoin donations to my address
264 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
269 <title>Appstream just learned how to map hardware to packages too!
</title>
270 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
271 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
272 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
273 <description><p
>I received a very nice Christmas present today. As my regular
274 readers probably know, I have been working on the
275 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
276 system
</a
> for many years. The goal of the Isenkram system is to make
277 it easier for users to figure out what to install to get a given piece
278 of hardware to work in Debian, and a key part of this system is a way
279 to map hardware to packages. Isenkram have its own mapping database,
280 and also uses data provided by each package using the AppStream
281 metadata format. And today,
282 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
283 Debian learned to look up hardware the same way Isenkram is doing it,
284 ie using fnmatch():
</p
>
287 % appstreamcli what-provides modalias \
288 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
289 Identifier: pymissile [generic]
291 Summary: Control original Striker USB Missile Launcher
293 % appstreamcli what-provides modalias usb:v0694p0002d0000
294 Identifier: libnxt [generic]
296 Summary: utility library for talking to the LEGO Mindstorms NXT brick
299 Identifier: t2n [generic]
301 Summary: Simple command-line tool for Lego NXT
304 Identifier: python-nxt [generic]
306 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
309 Identifier: nbc [generic]
311 Summary: C compiler for LEGO Mindstorms NXT bricks
314 </pre
></p
>
316 <p
>A similar query can be done using the combined AppStream and
317 Isenkram databases using the isenkram-lookup tool:
</p
>
320 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
322 % isenkram-lookup usb:v0694p0002d0000
328 </pre
></p
>
330 <p
>You can find modalias values relevant for your machine using
331 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
333 <p
>If you want to make this system a success and help Debian users
334 make the most of the hardware they have, please
335 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
336 AppStream metadata for your package following the guidelines
</a
>
337 documented in the wiki. So far only
11 packages provide such
338 information, among the several hundred hardware specific packages in
339 Debian. The Isenkram database on the other hand contain
101 packages,
340 mostly related to USB dongles. Most of the packages with hardware
341 mapping in AppStream are LEGO Mindstorms related, because I have, as
342 part of my involvement in
343 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
344 team
</a
> given priority to making sure LEGO users get proposed the
345 complete set of packages in Debian for that particular hardware. The
346 team also got a nice Christmas present today. The
347 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
348 package
</a
> made it into Debian. With this package in place, it is
349 now possible to use the LEGO Mindstorms NXT unit with only free
350 software, as the nxt-firmware package contain the source and firmware
351 binaries for the NXT brick.
</p
>
353 <p
>As usual, if you use Bitcoin and want to show your support of my
354 activities, please send Bitcoin donations to my address
355 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
360 <title>Isenkram updated with a lot more hardware-package mappings
</title>
361 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
362 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
363 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
364 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
365 system
</a
> I wrote two years ago to make it easier in Debian to find
366 and install packages to get your hardware dongles to work, is still
367 going strong. It is a system to look up the hardware present on or
368 connected to the current system, and map the hardware to Debian
369 packages. It can either be done using the tools in isenkram-cli or
370 using the user space daemon in the isenkram package. The latter will
371 notify you, when inserting new hardware, about what packages to
372 install to get the dongle working. It will even provide a button to
373 click on to ask packagekit to install the packages.
</p
>
375 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
394 </pre
></p
>
396 <p
>It can also list the firware package providing firmware requested
397 by the load kernel modules, which in my case is an empty list because
398 I have all the firmware my machine need:
401 % /usr/sbin/isenkram-autoinstall-firmware -l
402 info: did not find any firmware files requested by loaded kernel modules. exiting
404 </pre
></p
>
406 <p
>The last few days I had a look at several of the around
250
407 packages in Debian with udev rules. These seem like good candidates
408 to install when a given hardware dongle is inserted, and I found
409 several that should be proposed by isenkram. I have not had time to
410 check all of them, but am happy to report that now there are
97
411 packages packages mapped to hardware by Isenkram.
11 of these
412 packages provide hardware mapping using AppStream, while the rest are
413 listed in the modaliases file provided in isenkram.
</p
>
415 <p
>These are the packages with hardware mappings at the moment. The
416 <strong
>marked packages
</strong
> are also announcing their hardware
417 support using AppStream, for everyone to use:
</p
>
419 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
420 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
421 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
422 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
423 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
424 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
425 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
426 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
427 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
428 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
429 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
430 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
431 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
432 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
433 pcscd, pidgin-blinklight, printer-driver-splix,
434 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
435 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
436 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
437 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
438 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
439 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
440 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
441 xserver-xorg-video-vmware, yubikey-personalization and
442 zd1211-firmware
</p
>
444 <p
>If you know of other packages, please let me know with a wishlist
445 bug report against the isenkram-cli package, and ask the package
447 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
448 metadata according to the guidelines
</a
> to provide the information
449 for everyone. In time, I hope to get rid of the isenkram specific
450 hardware mapping and depend exclusively on AppStream.
</p
>
452 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
453 much hardware, and suggest that the package with with any ethernet
454 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
455 the details. I hope the maintainer find time to address it soon. In
456 the mean time I provide an override in isenkram.
</p
>
461 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
462 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
463 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
464 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
465 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
467 <p
>In my early years, I played
468 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
469 Elite
</a
> on my PC. I spent many months trading and fighting in
470 space, and reached the
'elite
' fighting status before I moved on. The
471 original Elite game was available on Commodore
64 and the IBM PC
472 edition I played had a
64 KB executable. I am still impressed today
473 that the authors managed to squeeze both a
3D engine and details about
474 more than
2000 planet systems across
7 galaxies into a binary so
477 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
478 software game Oolite inspired by Elite
</a
> for a while, but did not
479 really have time to test it properly until a few days ago. It was
480 great to discover that my old knowledge about trading routes were
481 still valid. But my fighting and flying abilities were gone, so I had
482 to retrain to be able to dock on a space station. And I am still not
483 able to make much resistance when I am attacked by pirates, so I
484 bougth and mounted the most powerful laser in the rear to be able to
485 put up at least some resistance while fleeing for my life. :)
</p
>
487 <p
>When playing Elite in the late eighties, I had to discover
488 everything on my own, and I had long lists of prices seen on different
489 planets to be able to decide where to trade what. This time I had the
491 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
492 where information about each planet is easily available with common
493 price ranges and suggested trading routes. This improved my ability
494 to earn money and I have been able to earn enough to buy a lot of
495 useful equipent in a few days. I believe I originally played for
496 months before I could get a docking computer, while now I could get it
497 after less then a week.
</p
>
499 <p
>If you like science fiction and dreamed of a life as a vagabond in
500 space, you should try out Oolite. It is available for Linux, MacOSX
501 and Windows, and is included in Debian and derivatives since
2011.
</p
>
503 <p
>As usual, if you use Bitcoin and want to show your support of my
504 activities, please send Bitcoin donations to my address
505 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
510 <title>Quicker Debian installations using eatmydata
</title>
511 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
512 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
513 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
514 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
515 installation system, observing how using
516 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
517 could speed up the installation
</a
> quite a bit. My testing measured
518 speedup around
20-
40 percent for Debian Edu, where we install around
519 1000 packages from within the installer. The eatmydata package
520 provide a way to disable/delay file system flushing. This is a bit
521 risky in the general case, as files that should be stored on disk will
522 stay only in memory a bit longer than expected, causing problems if a
523 machine crashes at an inconvenient time. But for an installation, if
524 the machine crashes during installation the process is normally
525 restarted, and avoiding disk operations as much as possible to speed
526 up the process make perfect sense.
528 <p
>I added code in the Debian Edu specific installation code to enable
529 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
530 but did not have time to push it any further. But a few months ago I
531 picked it up again and worked with the libeatmydata package maintainer
532 Mattia Rizzolo to make it easier for everyone to get this installation
533 speedup in Debian. Thanks to our cooperation There is now an
534 eatmydata-udeb package in Debian testing and unstable, and simply
535 enabling/installing it in debian-installer (d-i) is enough to get the
536 quicker installations. It can be enabled using preseeding. The
537 following untested kernel argument should do the trick:
</p
>
539 <blockquote
><pre
>
540 preseed/early_command=
"anna-install eatmydata-udeb
"
541 </pre
></blockquote
>
543 <p
>This should ask d-i to install the package inside the d-i
544 environment early in the installation sequence. Having it installed
545 in d-i in turn will make sure the relevant scripts are called just
546 after debootstrap filled /target/ with the freshly installed Debian
547 system to configure apt to run dpkg with eatmydata. This is enough to
548 speed up the installation process. There is a proposal to
549 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
550 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
551 tested its impact.
</p
>
557 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
558 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
560 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
561 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
562 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
563 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
564 elever over det ganske land skal levere inn hvert år. Det mange ikke
565 vet er at selv om de kommersielle alternativene
566 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
567 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
568 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
569 utmerket fri programvarealternativ som kan. Oversetterverktøyet
570 Apertium har støtte for en rekke språkkombinasjoner, og takket være
571 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
572 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
573 nynorsk, og få den automatoversatt til det andre skriftspråket.
574 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
575 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
576 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
577 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
578 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
579 teksten din i webskjemaet der.
581 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
582 teknologien kan du enten installere pakken
583 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
584 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
586 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
587 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
588 denne teksten som ble skrevet på bokmål over maskinoversatt til
593 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
594 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
595 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
596 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
597 veit er at sjølv om dei kommersielle alternativa
598 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
599 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
600 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
601 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
602 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
603 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
604 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
605 nynorsk, og få den *automatoversatt til det andre skriftspråket.
606 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
607 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
608 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
609 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
610 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
611 teksta di i *webskjemaet der.
613 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
614 teknologien kan du anten installera pakken
615 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
616 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
617 *api.*apertium.org. Sjå
618 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
619 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
620 for denne teksta som vart skreva på bokmål over *maskinoversatt til
626 <title>Coz profiler for multi-threaded software is now in Debian
</title>
627 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
628 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
629 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
630 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
631 profiler able to run benchmarking experiments on the instrumented
632 multi-threaded program, finally
633 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
634 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
636 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
637 blogged about the coz tool
</a
> in August working with upstream to make
638 it suitable for Debian. There are still issues with clang
639 compatibility, inline assembly only working x86 and minimized
640 JavaScript libraries.
</p
>
642 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
644 <p
><blockquote
>
645 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
646 </blockquote
></p
>
648 <p
>This will produce a profile.coz file in the current working
649 directory with the profiling information. This is then given to a
650 JavaScript application provided in the package and available from
651 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
652 To start the local copy, invoke it in a browser like this:
</p
>
654 <p
><blockquote
>
655 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
656 </blockquote
></p
>
658 <p
>See the project home page and the
659 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
660 ;login: article on Coz
</a
> for more information on how it is
666 <title>My own self balancing Lego Segway
</title>
667 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
668 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
669 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
670 <description><p
>A while back I received a Gyro sensor for the NXT
671 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
672 present. It had been on my wishlist for a while, because I wanted to
673 build a Segway like balancing lego robot. I had already built
674 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
675 robot
</a
> with the kids, using the light/color sensor included in the
676 NXT kit as the balance sensor, but it was not working very well. It
677 could balance for a while, but was very sensitive to the light
678 condition in the room and the reflective properties of the surface and
679 would fall over after a short while. I wanted something more robust,
681 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
682 gyro sensor from HiTechnic
</a
> I believed would solve it on my
683 wishlist for some years before it suddenly showed up as a gift from my
684 loved ones. :)
</p
>
686 <p
>Unfortunately I have not had time to sit down and play with it
687 since then. But that changed some days ago, when I was searching for
688 lego segway information and came across a recipe from HiTechnic for
690 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
691 HTWay
</a
>, a segway like balancing robot. Build instructions and
692 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
693 code
</a
> was included, so it was just a question of putting it all
694 together. And thanks to the great work of many Debian developers, the
695 compiler needed to build the source for the NXT is already included in
696 Debian, so I was read to go in less than an hour. The resulting robot
697 do not look very impressive in its simplicity:
</p
>
699 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
701 <p
>Because I lack the infrared sensor used to control the robot in the
702 design from HiTechnic, I had to comment out the last task
703 (taskControl). I simply placed /* and */ around it get the program
704 working without that sensor present. Now it balances just fine until
705 the battery status run low:
</p
>
707 <p align=
"center
"><video width=
"70%
" controls=
"true
">
708 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
709 </video
></p
>
711 <p
>Now we would like to teach it how to follow a line and take remote
712 control instructions using the included Bluetooth receiver in the NXT.
</p
>
714 <p
>If you, like me, love LEGO and want to make sure we find the tools
715 they need to work with LEGO in Debian and all our derivative
716 distributions like Ubuntu, check out
717 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
718 project page
</a
> and join the Debian LEGO team. Personally I own a
719 RCX and NXT controller (no EV3), and would like to make sure the
720 Debian tools needed to program the systems I own work as they
726 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
727 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
728 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
729 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
730 <description><p
>In July
731 <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
732 wrote how to get the Signal Chrome/Chromium app working
</a
> without
733 the ability to receive SMS messages (aka without a cell phone). It is
734 time to share some experiences and provide an updated setup.
</p
>
736 <p
>The Signal app have worked fine for several months now, and I use
737 it regularly to chat with my loved ones. I had a major snag at the
738 end of my summer vacation, when the the app completely forgot my
739 setup, identity and keys. The reason behind this major mess was
740 running out of disk space. To avoid that ever happening again I have
741 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
742 roll back to an earlier version if the files are wiped by mistake. I
743 had to use it once after introducing the git backup. When rolling
744 back to an earlier version, one need to use the
'reset session
' option
745 in Signal to get going, and notify the people you talk with about the
746 problem. I assume there is some sequence number tracking in the
747 protocol to detect rollback attacks. The git repository is rather big
748 (
674 MiB so far), but I have not tried to figure out if some of the
749 content can be added to a .gitignore file due to lack of spare
752 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
753 make it impossible to send messages using Signal. I could still
754 receive them, but had to patch the code with a new timestamp to send.
755 I believe the timeout is added by the developers to force people to
756 upgrade to the latest version of the app, even when there is no
757 protocol changes, to reduce the version skew among the user base and
758 thus try to keep the number of support requests down.
</p
>
760 <p
>Since my original recipe, the Signal source code changed slightly,
761 making the old patch fail to apply cleanly. Below is an updated
762 patch, including the shell wrapper I use to start Signal. The
763 original version required a new user to locate the JavaScript console
764 and call a function from there. I got help from a friend with more
765 JavaScript knowledge than me to modify the code to provide a GUI
766 button instead. This mean that to get started you just need to run
767 the wrapper and click the
'Register without mobile phone
' to get going
768 now. I
've also modified the timeout code to always set it to
90 days
769 in the future, to avoid having to patch the code regularly.
</p
>
771 <p
>So, the updated recipe for Debian Jessie:
</p
>
775 <li
>First, install required packages to get the source code and the
776 browser you need. Signal only work with Chrome/Chromium, as far as I
777 know, so you need to install it.
780 apt install git tor chromium
781 git clone https://github.com/WhisperSystems/Signal-Desktop.git
782 </pre
></li
>
784 <li
>Modify the source code using command listed in the the patch
785 block below.
</li
>
787 <li
>Start Signal using the run-signal-app wrapper (for example using
788 <tt
>`pwd`/run-signal-app
</tt
>).
790 <li
>Click on the
'Register without mobile phone
', will in a phone
791 number you can receive calls to the next minute, receive the
792 verification code and enter it into the form field and press
793 'Register
'. Note, the phone number you use will be user Signal
794 username, ie the way others can find you on Signal.
</li
>
796 <li
>You can now use Signal to contact others. Note, new contacts do
797 not show up in the contact list until you restart Signal, and there is
798 no way to assign names to Contacts. There is also no way to create or
799 update chat groups. I suspect this is because the web app do not have
800 a associated contact database.
</li
>
804 <p
>I am still a bit uneasy about using Signal, because of the way its
805 main author moxie0 reject federation and accept dependencies to major
806 corporations like Google (part of the code is fetched from Google) and
807 Amazon (the central coordination point is owned by Amazon). See for
809 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
810 LibreSignal issue tracker
</a
> for a thread documenting the authors
811 view on these issues. But the network effect is strong in this case,
812 and several of the people I want to communicate with already use
813 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
814 once it
<a href=
"https://bugs.debian.org/
830265">work on my
815 laptop
</a
>? It already work on Windows and Android, and is included
816 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
817 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
818 working on Debian Stable.
</p
>
820 <p
>Anyway, this is the patch I apply to the Signal code to get it
821 working. It switch to the production servers, disable to timeout,
822 make registration easier and add the shell wrapper:
</p
>
825 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
826 diff --git a/js/background.js b/js/background.js
827 index
24b4c1d.
.579345f
100644
828 --- a/js/background.js
829 +++ b/js/background.js
834 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
835 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
836 var SERVER_PORTS = [
80,
4433,
8443];
837 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
838 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
840 window.getSocketStatus = function() {
841 if (messageReceiver) {
842 diff --git a/js/expire.js b/js/expire.js
843 index
639aeae..beb91c3
100644
848 'use strict
';
849 - var BUILD_EXPIRATION =
0;
850 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
852 window.extension = window.extension || {};
854 diff --git a/js/views/install_view.js b/js/views/install_view.js
855 index
7816f4f.
.1d6233b
100644
856 --- a/js/views/install_view.js
857 +++ b/js/views/install_view.js
860 'click .step1
': this.selectStep.bind(this,
1),
861 'click .step2
': this.selectStep.bind(this,
2),
862 -
'click .step3
': this.selectStep.bind(this,
3)
863 +
'click .step3
': this.selectStep.bind(this,
3),
864 +
'click .callreg
': function() { extension.install(
'standalone
') },
867 clearQR: function() {
868 diff --git a/options.html b/options.html
869 index dc0f28e.
.8d709f6
100644
873 &lt;div class=
'nav
'>
874 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
875 &lt;p
>{{ installTagline }}
&lt;/p
>
876 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
877 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
878 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
881 &lt;span class=
'dot step1 selected
'>&lt;/span
>
882 &lt;span class=
'dot step2
'>&lt;/span
>
883 &lt;span class=
'dot step3
'>&lt;/span
>
884 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
885 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
891 +userdata=
"`pwd`/userdata
"
892 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
893 + (cd $userdata
&& git init)
895 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
897 + --proxy-server=
"socks://localhost:
9050" \
898 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
900 chmod a+rx run-signal-app
903 <p
>As usual, if you use Bitcoin and want to show your support of my
904 activities, please send Bitcoin donations to my address
905 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
910 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
911 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
912 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
913 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
914 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
915 system
</a
> provide a practical and easy way to figure out which
916 packages support the hardware in a given machine. The command line
917 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
918 convenient way to list and install packages relevant for the current
919 hardware during system installation, both user space packages and
920 firmware packages. The GUI background daemon on the other hand provide
921 a pop-up proposing to install packages when a new dongle is inserted
922 while using the computer. For example, if you plug in a smart card
923 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
924 that package isn
't already installed, and if you plug in a USB video
925 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
926 cheese is currently missing. This already work just fine.
</p
>
928 <p
>But Isenkram depend on a database mapping from hardware IDs to
929 package names. When I started no such database existed in Debian, so
930 I made my own data set and included it with the isenkram package and
931 made isenkram fetch the latest version of this database from git using
932 http. This way the isenkram users would get updated package proposals
933 as soon as I learned more about hardware related packages.
</p
>
935 <p
>The hardware is identified using modalias strings. The modalias
936 design is from the Linux kernel where most hardware descriptors are
937 made available as a strings that can be matched using filename style
938 globbing. It handle USB, PCI, DMI and a lot of other hardware related
939 identifiers.
</p
>
941 <p
>The downside to the Isenkram specific database is that there is no
942 information about relevant distribution / Debian version, making
943 isenkram propose obsolete packages too. But along came AppStream, a
944 cross distribution mechanism to store and collect metadata about
945 software packages. When I heard about the proposal, I contacted the
946 people involved and suggested to add a hardware matching rule using
947 modalias strings in the specification, to be able to use AppStream for
948 mapping hardware to packages. This idea was accepted and AppStream is
949 now a great way for a package to announce the hardware it support in a
950 distribution neutral way. I wrote
951 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
952 recipe on how to add such meta-information
</a
> in a blog post last
953 December. If you have a hardware related package in Debian, please
954 announce the relevant hardware IDs using AppStream.
</p
>
956 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
957 RCX or NXT unit, announce this support using AppStream. The effect is
958 that when you insert such LEGO robot controller into your Debian
959 machine, Isenkram will propose to install the packages needed to get
960 it working. The intention is that this should allow the local user to
961 start programming his robot controller right away without having to
962 guess what packages to use or which permissions to fix.
</p
>
964 <p
>But when I sat down with my son the other day to program our NXT
965 unit using his Debian Stretch computer, I discovered something
966 annoying. The local console user (ie my son) did not get access to
967 the USB device for programming the unit. This used to work, but no
968 longer in Jessie and Stretch. After some investigation and asking
969 around on #debian-devel, I discovered that this was because udev had
970 changed the mechanism used to grant access to local devices. The
971 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
972 no longer applied, because LDAP users no longer was added to the
973 plugdev group during login. Michael Biebl told me that this method
974 was obsolete and the new method used ACLs instead. This was good
975 news, as the plugdev mechanism is a mess when using a remote user
976 directory like LDAP. Using ACLs would make sure a user lost device
977 access when she logged out, even if the user left behind a background
978 process which would retain the plugdev membership with the ConsoleKit
979 setup. Armed with this knowledge I moved on to fix the access problem
980 for the LEGO Mindstorms related packages.
</p
>
982 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
983 applied directly for a device, or is applied in
984 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
985 LEGO Mindstorms udev rules did not have a class, I decided to add the
986 tag directly in the udev rules files included in the packages. Here
987 is one example. For the nqc C compiler for the RCX, the
988 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
991 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
992 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
993 </pre
></p
>
995 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
996 packages using plugdev in their /lib/udev/rules.d/ files should be
997 changed to use this tag (either directly or indirectly via
998 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
999 to detect this?
</p
>
1001 <p
>I
've been unable to find good documentation on the uaccess feature.
1002 It is unclear to me if the uaccess tag is an internal implementation
1003 detail like the udev-acl tag used by
1004 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
1005 indirect method is the preferred way. Michael
1006 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
1007 documentation from the systemd project
</a
> and I hope it will make
1008 this clearer. For now I use the generic classes when they exist and
1009 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
1010 directly if no such class exist.
</p
>
1012 <p
>To learn more about the isenkram system, please check out
1013 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
1014 blog posts tagged isenkram
</a
>.
</p
>
1016 <p
>To help out making life for LEGO constructors in Debian easier,
1017 please join us on our IRC channel
1018 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
1019 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
1020 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
1021 list is not yet created, but we are working on it. :)
</p
>
1023 <p
>As usual, if you use Bitcoin and want to show your support of my
1024 activities, please send Bitcoin donations to my address
1025 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1030 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
1031 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
1032 <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>
1033 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
1034 <description><p
>In April we
1035 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1036 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1037 how to set up and administrate a Debian system. Today I am happy to
1038 report that the first draft is now publicly available. You can find
1039 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1040 Administrator
's Handbook page
</a
> (under Other languages). The first
1041 eight chapters have a first draft translation, and we are working on
1042 proofreading the content. If you want to help out, please start
1044 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1045 hosted weblate project page
</a
>, and get in touch using
1046 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1047 translators mailing list
</a
>. Please also check out
1048 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1049 contributors
</a
>. A good way to contribute is to proofread the text
1050 and update weblate if you find errors.
</p
>
1052 <p
>Our goal is still to make the Norwegian book available on paper as well as
1053 electronic form.
</p
>
1058 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1059 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1060 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1061 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1062 <description><p
>This summer, I read a great article
1063 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1064 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1065 how to profile multi-threaded programs. It presented a system for
1066 profiling software by running experiences in the running program,
1067 testing how run time performance is affected by
"speeding up
" parts of
1068 the code to various degrees compared to a normal run. It does this by
1069 slowing down parallel threads while the
"faster up
" code is running
1070 and measure how this affect processing time. The processing time is
1071 measured using probes inserted into the code, either using progress
1072 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1073 can also measure unmodified code by measuring complete the program
1074 runtime and running the program several times instead.
</p
>
1076 <p
>The project and presentation was so inspiring that I would like to
1077 get the system into Debian. I
1078 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1079 a WNPP request for it
</a
> and contacted upstream to try to make the
1080 system ready for Debian by sending patches. The build process need to
1081 be changed a bit to avoid running
'git clone
' to get dependencies, and
1082 to include the JavaScript web page used to visualize the collected
1083 profiling information included in the source package.
1084 But I expect that should work out fairly soon.
</p
>
1086 <p
>The way the system work is fairly simple. To run an coz experiment
1087 on a binary with debug symbols available, start the program like this:
1089 <p
><blockquote
><pre
>
1090 coz run --- program-to-run
1091 </pre
></blockquote
></p
>
1093 <p
>This will create a text file profile.coz with the instrumentation
1094 information. To show what part of the code affect the performance
1095 most, use a web browser and either point it to
1096 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1097 or use the copy from git (in the gh-pages branch). Check out this web
1098 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
1099 profiling more useful you include
&lt;coz.h
&gt; and insert the
1100 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1101 code, rebuild and run the profiler. This allow coz to do more
1102 targeted experiments.
</p
>
1104 <p
>A video published by ACM
1105 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1106 Coz profiler
</a
> is available from Youtube. There is also a paper
1107 from the
25th Symposium on Operating Systems Principles available
1109 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1110 finding code that counts with causal profiling
</a
>.
</p
>
1112 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1113 for Coz is available from github. It will only build with clang
1115 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1116 feature missing in GCC
</a
>, but I
've submitted
1117 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1118 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1120 <p
>Please get in touch if you, like me, would like to see this piece
1121 of software in Debian. I would very much like some help with the
1122 packaging effort, as I lack the in depth knowledge on how to package
1123 C++ libraries.
</p
>
1128 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1129 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1130 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1131 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1132 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1133 to be a slight challenge. Here is the recipe if I ever need to do it
1134 again. It all started by me wanting to try the recipe to set up
1135 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1136 hardened Android installation
</a
> from the Tor project blog on a
1137 device I had access to. It is a old mobile phone with a broken
1138 microphone The initial idea had been to just
1139 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1140 CyanogenMod on it
</a
>, but did not quite find time to start on it
1141 until a few days ago.
</p
>
1143 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1144 loader (press volume down and power at the same time), (
2) select
1145 'fastboot
' before (
3) connecting the device via USB to a Linux
1146 machine, (
4) request the device identifier token by running
'fastboot
1147 oem get_identifier_token
', (
5) request the device unlocking key using
1148 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1149 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1151 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1152 or newer, and the device I was working on had
2.00.0027. This
1153 apparently can be easily fixed by downloading a Windows program and
1154 running it on your Windows machine, if you accept the terms Microsoft
1155 require you to accept to use Windows - which I do not. So I had to
1156 come up with a different approach. I got a lot of help from AndyCap
1157 on #nuug, and would not have been able to get this working without
1160 <p
>First I needed to extract the hboot firmware from
1161 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1162 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1163 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1164 project named unruu
</a
> using libunshield. The unshield tool did not
1165 recognise the file format, but unruu worked and extracted rom.zip,
1166 containing the new hboot firmware and a text file describing which
1167 devices it would work for.
</p
>
1169 <p
>Next, I needed to get the new firmware into the device. For this I
1170 followed some instructions
1171 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1172 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1173 machine with Debian testing:
</p
>
1175 <p
><pre
>
1176 adb reboot-bootloader
1177 fastboot oem rebootRUU
1178 fastboot flash zip rom.zip
1179 fastboot flash zip rom.zip
1181 </pre
></p
>
1183 <p
>The flash command apparently need to be done twice to take effect,
1184 as the first is just preparations and the second one do the flashing.
1185 The adb command is just to get to the boot loader menu, so turning the
1186 device on while holding volume down and the power button should work
1189 <p
>With the new hboot version in place I could start following the
1190 instructions on the HTC developer web site. I got the device token
1191 like this:
</p
>
1193 <p
><pre
>
1194 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1197 <p
>And once I got the unlock code via email, I could use it like
1200 <p
><pre
>
1201 fastboot flash unlocktoken Unlock_code.bin
1202 </pre
></p
>
1204 <p
>And with that final step in place, the phone was unlocked and I
1205 could start stuffing the software of my own choosing into the device.
1206 So far I only inserted a replacement recovery image to wipe the phone
1207 before I start. We will see what happen next. Perhaps I should
1208 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1213 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1214 <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>
1215 <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>
1216 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1217 <description><p
>For a while now, I have wanted to test
1218 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1219 said to provide end to end encrypted communication and several of my
1220 friends and family are already using it. As I by choice do not own a
1221 mobile phone, this proved to be harder than expected. And I wanted to
1222 have the source of the client and know that it was the code used on my
1223 machine. But yesterday I managed to get it working. I used the
1224 Github source, compared it to the source in
1225 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1226 Signal Chrome app
</a
> available from the Chrome web store, applied
1227 patches to use the production Signal servers, started the app and
1228 asked for the hidden
"register without a smart phone
" form. Here is
1229 the recipe how I did it.
</p
>
1231 <p
>First, I fetched the Signal desktop source from Github, using
1234 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1237 <p
>Next, I patched the source to use the production servers, to be
1238 able to talk to other Signal users:
</p
>
1241 cat
&lt;
&lt;EOF | patch -p0
1242 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1243 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1244 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1249 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1250 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1251 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1252 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1253 var messageReceiver;
1254 window.getSocketStatus = function() {
1255 if (messageReceiver) {
1256 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1257 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1258 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1261 'use strict
';
1262 - var BUILD_EXPIRATION =
0;
1263 + var BUILD_EXPIRATION =
1474492690000;
1265 window.extension = window.extension || {};
1270 <p
>The first part is changing the servers, and the second is updating
1271 an expiration timestamp. This timestamp need to be updated regularly.
1272 It is set
90 days in the future by the build process (Gruntfile.js).
1273 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1275 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1276 script to launch Signal in Chromium.
</p
>
1283 --proxy-server=
"socks://localhost:
9050" \
1284 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1287 <p
> The script start the app and configure Chromium to use the Tor
1288 SOCKS5 proxy to make sure those controlling the Signal servers (today
1289 Amazon and Whisper Systems) as well as those listening on the lines
1290 will have a harder time location my laptop based on the Signal
1291 connections if they use source IP address.
</p
>
1293 <p
>When the script starts, one need to follow the instructions under
1294 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1295 repository. I right clicked on the Signal window to get up the
1296 Chromium debugging tool, visited the
'Console
' tab and wrote
1297 'extension.install(
"standalone
")
' on the console prompt to get the
1298 registration form. Then I entered by land line phone number and
1299 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1300 repeated the verification code three times. After entering the number
1301 into the verification code field in the form, I could start using
1302 Signal from my laptop.
1304 <p
>As far as I can tell, The Signal app will leak who is talking to
1305 whom and thus who know who to those controlling the central server,
1306 but such leakage is hard to avoid with a centrally controlled server
1307 setup. It is something to keep in mind when using Signal - the
1308 content of your chats are harder to intercept, but the meta data
1309 exposing your contact network is available to people you do not know.
1310 So better than many options, but not great. And sadly the usage is
1311 connected to my land line, thus allowing those controlling the server
1312 to associate it to my home and person. I would prefer it if only
1313 those I knew could tell who I was on Signal. There are options
1314 avoiding such information leakage, but most of my friends are not
1315 using them, so I am stuck with Signal for now.
</p
>
1317 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1319 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1320 and updated recipe for using the Signal app without a mobile
1321 phone
</a
>.
</p
>
1326 <title>The new
"best
" multimedia player in Debian?
</title>
1327 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1329 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1330 <description><p
>When I set out a few weeks ago to figure out
1331 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1332 multimedia player in Debian claimed to support most file formats /
1333 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1334 the various players claimed support for. The range was from
55 to
130
1335 MIME types. I suspect most media formats are supported by all
1336 players, but this is not really reflected in the MimeTypes values in
1337 their desktop files. There are probably also some bogus MIME types
1338 listed, but it is hard to identify which one this is.
</p
>
1340 <p
>Anyway, in the mean time I got in touch with upstream for some of
1341 the players suggesting to add more MIME types to their desktop files,
1342 and decided to spend some time myself improving the situation for my
1343 favorite media player VLC. The fixes for VLC entered Debian unstable
1344 yesterday. The complete list of MIME types can be seen on the
1345 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1346 player MIME type support status
</a
> Debian wiki page.
</p
>
1348 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1349 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1350 kmplayer. I am sure some of the other players desktop files support
1351 several of the formats currently listed as working only with vlc,
1352 toten and parole.
</p
>
1354 <p
>A sad observation is that only
14 MIME types are listed as
1355 supported by all the tested multimedia players in Debian in their
1356 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1357 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1358 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1359 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1360 it sad that video/ogg and video/webm is not supported by all the media
1361 players in Debian. As far as I can tell, all of them can handle both
1367 <title>A program should be able to open its own files on Linux
</title>
1368 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1369 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1370 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1371 <description><p
>Many years ago, when koffice was fresh and with few users, I
1372 decided to test its presentation tool when making the slides for a
1373 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1374 wrote the first draft of the slides, saved the result and went to bed
1375 the day before I would give the talk. The next day I took a plane to
1376 the location where the meeting should take place, and on the plane I
1377 started up koffice again to polish the talk a bit, only to discover
1378 that kpresenter refused to load its own data file. I cursed a bit and
1379 started making the slides again from memory, to have something to
1380 present when I arrived. I tested that the saved files could be
1381 loaded, and the day seemed to be rescued. I continued to polish the
1382 slides until I suddenly discovered that the saved file could no longer
1383 be loaded into kpresenter. In the end I had to rewrite the slides
1384 three times, condensing the content until the talk became shorter and
1385 shorter. After the talk I was able to pinpoint the problem
&ndash;
1386 kpresenter wrote inline images in a way itself could not understand.
1387 Eventually that bug was fixed and kpresenter ended up being a great
1388 program to make slides. The point I
'm trying to make is that we
1389 expect a program to be able to load its own data files, and it is
1390 embarrassing to its developers if it can
't.
</p
>
1392 <p
>Did you ever experience a program failing to load its own data
1393 files from the desktop file browser? It is not a uncommon problem. A
1394 while back I discovered that the screencast recorder
1395 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1396 browser would refuse to open. No video player claimed to understand
1397 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1398 returning the application/ogg MIME type, which no video player I had
1399 installed listed as a MIME type they would understand. I asked for
1400 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1401 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1402 several video players to add video/ogg to their desktop files, to give
1403 the file browser an idea what to do about Ogg Theora files. After a
1404 while, the desktop file browsers in Debian started to handle the
1405 output from gtk-recordmydesktop properly.
</p
>
1407 <p
>But history repeats itself. A few days ago I tested the music
1408 system Rosegarden again, and I discovered that the KDE and xfce file
1409 browsers did not know what to do with the Rosegarden project files
1410 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1411 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1412 included in the next upload. To increase the chance of me remembering
1413 how to fix the problem next time some program fail to load its files
1414 from the file browser, here are some notes on how to fix it.
</p
>
1416 <p
>The file browsers in Debian in general operates on MIME types.
1417 There are two sources for the MIME type of a given file. The output from
1418 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1419 shared MIME type registry (under /usr/share/mime/). The file MIME
1420 type is mapped to programs supporting the MIME type, and this
1421 information is collected from
1422 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1423 desktop files
</a
> available in /usr/share/applications/. If there is
1424 one desktop file claiming support for the MIME type of the file, it is
1425 activated when asking to open a given file. If there are more, one
1426 can normally select which one to use by right-clicking on the file and
1427 selecting the wanted one using
'Open with
' or similar. In general
1428 this work well. But it depend on each program picking a good MIME
1430 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1431 MIME type registered with IANA
</a
>), file and/or the shared MIME
1432 registry recognizing the file and the desktop file to list the MIME
1433 type in its list of supported MIME types.
</p
>
1435 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1436 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1437 Shared MIME database
</a
> look like this:
</p
>
1439 <p
><blockquote
><pre
>
1440 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1441 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1442 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1443 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1444 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1445 &lt;glob pattern=
"*.rg
"/
&gt;
1446 &lt;/mime-type
&gt;
1447 &lt;/mime-info
&gt;
1448 </pre
></blockquote
></p
>
1450 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1451 (it is a gzipped XML file). Note, it is much better to use an
1452 official MIME type registered with IANA than it is to make up ones own
1453 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1455 <p
>The desktop file of the rosegarden program failed to list
1456 audio/x-rosegarden in its list of supported MIME types, causing the
1457 file browsers to have no idea what to do with *.rg files:
</p
>
1459 <p
><blockquote
><pre
>
1460 % grep Mime /usr/share/applications/rosegarden.desktop
1461 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1462 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1464 </pre
></blockquote
></p
>
1466 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1467 MimeType= line.
</p
>
1469 <p
>If you run into a file which fail to open the correct program when
1470 selected from the file browser, please check out the output from
1471 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1472 MIME type is registered somewhere under /usr/share/mime/ and check
1473 that some desktop file under /usr/share/applications/ is claiming
1474 support for this MIME type. If not, please report a bug to have it
1480 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1481 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1482 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1483 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1484 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1485 system
</a
> is a user-focused solution in Debian for handling hardware
1486 related packages. The idea is to have a database of mappings between
1487 hardware and packages, and pop up a dialog suggesting for the user to
1488 install the packages to use a given hardware dongle. Some use cases
1489 are when you insert a Yubikey, it proposes to install the software
1490 needed to control it; when you insert a braille reader list it
1491 proposes to install the packages needed to send text to the reader;
1492 and when you insert a ColorHug screen calibrator it suggests to
1493 install the driver for it. The system work well, and even have a few
1494 command line tools to install firmware packages and packages for the
1495 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1497 <p
>The system was initially written using aptdaemon, because I found
1498 good documentation and example code on how to use it. But aptdaemon
1499 is going away and is generally being replaced by
1500 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1501 so Isenkram needed a rewrite. And today, thanks to the great patch
1502 from my college Sunil Mohan Adapa in the FreedomBox project, the
1503 rewrite finally took place. I
've just uploaded a new version of
1504 Isenkram into Debian Unstable with the patch included, and the default
1505 for the background daemon is now to use PackageKit. To check it out,
1506 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1507 and see if it is recognised.
</p
>
1509 <p
>If you want to know what kind of packages isenkram would propose for
1510 the machine it is running on, you can check out the isenkram-lookup
1511 program. This is what it look like on a Thinkpad X230:
</p
>
1513 <p
><blockquote
><pre
>
1529 </pre
></blockquote
></p
>
1531 <p
>The hardware mappings come from several places. The preferred way
1532 is for packages to announce their hardware support using
1533 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1534 cross distribution appstream system
</a
>.
1536 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1537 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1542 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1543 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1545 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1546 <description><p
>Yesterday I updated the
1547 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1548 package in Debian
</a
> with a few patches sent to me by skilled and
1549 enterprising users. There were some nice user and visible changes.
1550 First of all, both desktop menu entries now work. A design flaw in
1551 one of the script made the history graph fail to show up (its PNG was
1552 dumped in ~/.xsession-errors) if no controlling TTY was available.
1553 The script worked when called from the command line, but not when
1554 called from the desktop menu. I changed this to look for a DISPLAY
1555 variable or a TTY before deciding where to draw the graph, and now the
1556 graph window pop up as expected.
</p
>
1558 <p
>The next new feature is a discharge rate estimator in one of the
1559 graphs (the one showing the last few hours). New is also the user of
1560 colours showing charging in blue and discharge in red. The percentages
1561 of this graph is relative to last full charge, not battery design
1564 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1566 <p
>The other graph show the entire history of the collected battery
1567 statistics, comparing it to the design capacity of the battery to
1568 visualise how the battery life time get shorter over time. The red
1569 line in this graph is what the previous graph considers
100 percent:
1571 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1573 <p
>In this graph you can see that I only charge the battery to
80
1574 percent of last full capacity, and how the capacity of the battery is
1575 shrinking. :(
</p
>
1577 <p
>The last new feature is in the collector, which now will handle
1578 more hardware models. On some hardware, Linux power supply
1579 information is stored in /sys/class/power_supply/ACAD/, while the
1580 collector previously only looked in /sys/class/power_supply/AC/. Now
1581 both are checked to figure if there is power connected to the
1584 <p
>If you are interested in how your laptop battery is doing, please
1586 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1587 in Debian unstable, or rebuild it on Jessie to get it working on
1588 Debian stable. :) The upstream source is available from
<a
1589 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1590 Patches are very welcome.
</p
>
1592 <p
>As usual, if you use Bitcoin and want to show your support of my
1593 activities, please send Bitcoin donations to my address
1594 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1599 <title>Debian now with ZFS on Linux included
</title>
1600 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1601 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1602 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1603 <description><p
>Today, after many years of hard work from many people,
1604 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1605 Debian. The package status can be seen on
1606 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1607 for zfs-linux
</a
>. and
1608 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1609 team status page
</a
>. If you want to help out, please join us.
1610 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1611 source code
</a
> is available via git on Alioth. It would also be
1612 great if you could help out with
1613 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1614 it is an important piece of the puzzle to get ZFS working.
</p
>
1619 <title>What is the best multimedia player in Debian?
</title>
1620 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1621 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1622 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1623 <description><p
><strong
>Where I set out to figure out which multimedia player in
1624 Debian claim support for most file formats.
</strong
></p
>
1626 <p
>A few years ago, I had a look at the media support for Browser
1627 plugins in Debian, to get an idea which plugins to include in Debian
1628 Edu. I created a script to extract the set of supported MIME types
1629 for each plugin, and used this to find out which multimedia browser
1630 plugin supported most file formats / media types.
1631 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1632 result
</a
> can still be seen on the Debian wiki, even though it have
1633 not been updated for a while. But browser plugins are less relevant
1634 these days, so I thought it was time to look at standalone
1637 <p
>A few days ago I was tired of VLC not being listed as a viable
1638 player when I wanted to play videos from the Norwegian National
1639 Broadcasting Company, and decided to investigate why. The cause is a
1640 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1641 desktop file
</a
>. In the process I wrote a script to compare the set
1642 of MIME types announced in the desktop file and the browser plugin,
1643 only to discover that there is quite a large difference between the
1644 two for VLC. This discovery made me dig up the script I used to
1645 compare browser plugins, and adjust it to compare desktop files
1646 instead, to try to figure out which multimedia player in Debian
1647 support most file formats.
</p
>
1649 <p
>The result can be seen on the Debian Wiki, as
1650 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1651 table listing all MIME types supported by one of the packages included
1652 in the table
</a
>, with the package supporting most MIME types being
1653 listed first in the table.
</p
>
1655 </p
>The best multimedia player in Debian? It is totem, followed by
1656 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1657 kmplayer. Time for the other players to update their announced MIME
1663 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1664 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1665 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1666 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1667 <description>A friend of mine made me aware of
1668 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1669 handheld computer which will be delivered with Debian preinstalled. I
1670 would love to get one of those for my birthday. :)
</p
>
1672 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1673 plugs and many others connectors, and include a full keyboard and a
5"
1674 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1675 day of battery life time, but I have not seen any independent tests
1676 confirming this. The vendor is still collecting preorders, and the
1677 last I heard last night was that
22 more orders were needed before
1678 production started.
</p
>
1680 <p
>As far as I know, this is the first handheld preinstalled with
1681 Debian. Please let me know if you know of any others. Is it the
1682 first computer being sold with Debian preinstalled?
</p
>
1687 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1688 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1689 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1690 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1691 <description><p
>During this weekends
1692 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1693 squashing party and developer gathering
</a
>, we decided to do our part
1694 to make sure there are good books about Debian available in Norwegian
1695 Bokmål, and got in touch with the people behind the
1696 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1697 project
</a
> to get started. If you want to help out, please start
1699 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1700 hosted weblate project page
</a
>, and get in touch using
1701 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1702 translators mailing list
</a
>. Please also check out
1703 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1704 contributors
</a
>.
</p
>
1706 <p
>The book is already available on paper in English, French and
1707 Japanese, and our goal is to get it available on paper in Norwegian
1708 Bokmål too. In addition to the paper edition, there are also EPUB and
1709 Mobi versions available. And there are incomplete translations
1710 available for many more languages.
</p
>
1715 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1716 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1717 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1718 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1719 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1720 packages in Debian, and was quite surprised with what I found. I use
1721 ZFS myself at home, but did not really expect many others to do so.
1722 But I might be wrong.
</p
>
1724 <p
>According to
1725 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1726 results for spl-linux
</a
>, there are
1019 Debian installations, or
1727 0.53% of the population, with the package installed. As far as I know
1728 the only use of the spl-linux package is as a support library for ZFS
1729 on Linux, so I use it here as proxy for measuring the number of ZFS
1730 installation on Linux in Debian. In the kFreeBSD variant of Debian
1731 the ZFS feature is already available, and there
1732 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1733 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1734 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1736 <p
>But even though the Debian project leader Lucas Nussbaum
1737 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1738 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1739 cleared, the package is still not in Debian. The package is again in
1740 the NEW queue. Several uploads have been rejected so far because the
1741 debian/copyright file was incomplete or wrong, but there is no reason
1742 to give up. The current status can be seen on
1743 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1744 team status page
</a
>, and
1745 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1746 source code
</a
> is available on Alioth.
</p
>
1748 <p
>As I want ZFS to be included in next version of Debian to make sure
1749 my home server can function in the future using only official Debian
1750 packages, and the current blocker is to get the debian/copyright file
1751 accepted by the FTP masters in Debian, I decided a while back to try
1752 to help out the team. This was the background for my blog post about
1753 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1754 updating and checking debian/copyright semi-automatically
</a
>, and I
1755 used the techniques I explored there to try to find any errors in the
1756 copyright file. It is not very easy to check every one of the around
1757 2000 files in the source package, but I hope we this time got it
1758 right. If you want to help out, check out the git source and try to
1759 find missing entries in the debian/copyright file.
</p
>
1764 <title>Full battery stats collector is now available in Debian
</title>
1765 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1766 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1767 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1768 <description><p
>Since this morning, the battery-stats package in Debian include an
1769 extended collector that will collect the complete battery history for
1770 later processing and graphing. The original collector store the
1771 battery level as percentage of last full level, while the new
1772 collector also record battery vendor, model, serial number, design
1773 full level, last full level and current battery level. This make it
1774 possible to predict the lifetime of the battery as well as visualise
1775 the energy flow when the battery is charging or discharging.
</p
>
1777 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1778 in the version
0.5.1 package in unstable. Get the new battery level graph
1779 and lifetime prediction by running:
1781 <p
><pre
>
1782 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1783 </pre
></p
>
1785 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1787 <p
>The flow in/out of the battery can be seen by running (no menu
1788 entry yet):
</p
>
1790 <p
><pre
>
1791 /usr/share/battery-stats/battery-stats-graph-flow
1792 </pre
></p
>
1794 <p
>I
'm not quite happy with the way the data is visualised, at least
1795 when there are few data points. The graphs look a bit better with a
1796 few years of data.
</p
>
1798 <p
>A while back one important feature I use in the battery stats
1799 collector broke in Debian. The scripts in
1800 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1801 suspect it happened when Jessie started using systemd, but I do not
1802 know. The issue is reported as
1803 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1804 pm-utils. I managed to work around it by adding an udev rule to call
1805 the collector script every time the power connector is connected and
1806 disconnected. With this fix in place it was finally time to make a
1807 new release of the package, and get it into Debian.
</p
>
1809 <p
>If you are interested in how your laptop battery is doing, please
1811 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1812 in Debian unstable, or rebuild it on Jessie to get it working on
1813 Debian stable. :) The upstream source is available from
1814 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1815 As always, patches are very welcome.
</p
>
1820 <title>Making battery measurements a little easier in Debian
</title>
1821 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1822 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1823 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1824 <description><p
>Back in September, I blogged about
1825 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1826 system I wrote to collect statistics about my laptop battery
</a
>, and
1827 how it showed the decay and death of this battery (now replaced). I
1828 created a simple deb package to handle the collection and graphing,
1829 but did not want to upload it to Debian as there were already
1830 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1831 package in Debian
</a
> that should do the same thing, and I did not see
1832 a point of uploading a competing package when battery-stats could be
1833 fixed instead. I reported a few bugs about its non-function, and
1834 hoped someone would step in and fix it. But no-one did.
</p
>
1836 <p
>I got tired of waiting a few days ago, and took matters in my own
1837 hands. The end result is that I am now the new upstream developer of
1838 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1839 battery-stats in Debian, and the package in Debian unstable is finally
1840 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1841 information provided by the Linux kernel. If you install the
1842 battery-stats package from unstable now, you will be able to get a
1843 graph of the current battery fill level, to get some idea about the
1844 status of the battery. The source package build and work just fine in
1845 Debian testing and stable (and probably oldstable too, but I have not
1846 tested). The default graph you get for that system look like this:
</p
>
1848 <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
>
1850 <p
>My plans for the future is to merge my old scripts into the
1851 battery-stats package, as my old scripts collected a lot more details
1852 about the battery. The scripts are merged into the upstream
1853 battery-stats git repository already, but I am not convinced they work
1854 yet, as I changed a lot of paths along the way. Will have to test a
1855 bit more before I make a new release.
</p
>
1857 <p
>I will also consider changing the file format slightly, as I
1858 suspect the way I combine several values into one field might make it
1859 impossible to know the type of the value when using it for processing
1860 and graphing.
</p
>
1862 <p
>If you would like I would like to keep an close eye on your laptop
1863 battery, check out the battery-stats package in
1864 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1866 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1867 I would love some help to improve the system further.
</p
>
1872 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1873 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1875 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1876 <description><p
>Making packages for Debian requires quite a lot of attention to
1877 details. And one of the details is the content of the
1878 debian/copyright file, which should list all relevant licenses used by
1879 the code in the package in question, preferably in
1880 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1881 readable DEP5 format
</a
>.
</p
>
1883 <p
>For large packages with lots of contributors it is hard to write
1884 and update this file manually, and if you get some detail wrong, the
1885 package is normally rejected by the ftpmasters. So getting it right
1886 the first time around get the package into Debian faster, and save
1887 both you and the ftpmasters some work.. Today, while trying to figure
1888 out what was wrong with
1889 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1890 zfsonlinux copyright file
</a
>, I decided to spend some time on
1891 figuring out the options for doing this job automatically, or at least
1892 semi-automatically.
</p
>
1894 <p
>Lucikly, there are at least two tools available for generating the
1895 file based on the code in the source package,
1896 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1897 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1898 not sure which one of them came first, but both seem to be able to
1899 create a sensible draft file. As far as I can tell, none of them can
1900 be trusted to get the result just right, so the content need to be
1901 polished a bit before the file is OK to upload. I found the debmake
1903 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1904 blog posts from
2014</a
>.
1906 <p
>To generate using debmake, use the -cc option:
1908 <p
><pre
>
1909 debmake -cc
> debian/copyright
1910 </pre
></p
>
1912 <p
>Note there are some problems with python and non-ASCII names, so
1913 this might not be the best option.
</p
>
1915 <p
>The cme option is based on a config parsing library, and I found
1917 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1918 blog post from
2015</a
>. To generate using cme, use the
'update
1919 dpkg-copyright
' option:
1921 <p
><pre
>
1922 cme update dpkg-copyright
1923 </pre
></p
>
1925 <p
>This will create or update debian/copyright. The cme tool seem to
1926 handle UTF-
8 names better than debmake.
</p
>
1928 <p
>When the copyright file is created, I would also like some help to
1929 check if the file is correct. For this I found two good options,
1930 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1931 to focus on license types and file matching, and is able to detect
1932 ineffective blocks in the copyright file. The latter reports missing
1933 copyright holders and years, but was confused by inconsistent license
1934 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1935 fix all issues reported by them before uploading. But I do not know
1936 if the tools and the ftpmasters agree on what is important to fix in a
1937 copyright file, so the package might still be rejected.
</p
>
1939 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1940 will read through the source and try to find all copyright statements.
1941 It is not comparing the result to the content of debian/copyright, but
1942 can be useful when verifying the content of the copyright file.
</p
>
1944 <p
>Are you aware of better tools in Debian to create and update
1945 debian/copyright file. Please let me know, or blog about it on
1946 planet.debian.org.
</p
>
1948 <p
>As usual, if you use Bitcoin and want to show your support of my
1949 activities, please send Bitcoin donations to my address
1950 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1952 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1953 on how to use licensecheck and cdbs to create a draft copyright file
1955 <p
><pre
>
1956 licensecheck --copyright -r `find * -type f` | \
1957 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1958 </pre
></p
>
1960 <p
>He mentioned that he normally check the generated file into the
1961 version control system to make it easier to discover license and
1962 copyright changes in the upstream source. I will try to do the same
1963 with my packages in the future.
</p
>
1965 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1966 against using -quiet for new users, so I removed it from the proposed
1967 command line.
</p
>
1972 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1973 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1974 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1975 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1976 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1977 is taking shape in Debian, and one provided feature is a very
1978 convenient way to tell you which package to install to make a given
1979 firmware file available when the kernel is looking for it. This can
1980 be done using apt-file too, but that is for someone else to blog
1983 <p
>Here is a small recipe to find the package with a given firmware
1984 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1985 picked from the set of firmware announced using appstream in Debian
1986 unstable. In general you would be looking for the firmware requested
1987 by the kernel during kernel module loading. To find the package
1988 providing the example file, do like this:
</p
>
1990 <blockquote
><pre
>
1991 % apt install appstream
1995 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1996 awk
'/Package:/ {print $
2}
'
1999 </pre
></blockquote
>
2001 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
2002 appstream wiki
</a
> page to learn how to embed the package metadata in
2003 a way appstream can use.
</p
>
2005 <p
>This same approach can be used to find any package supporting a
2006 given MIME type. This is very useful when you get a file you do not
2007 know how to handle. First find the mime type using
<tt
>file
2008 --mime-type
</tt
>, and next look up the package providing support for
2009 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
2010 and you can find all packages handling this type like this:
</p
>
2012 <blockquote
><pre
>
2013 % apt install appstream
2017 % appstreamcli what-provides mimetype image/svg+xml | \
2018 awk
'/Package:/ {print $
2}
'
2040 </pre
></blockquote
>
2042 <p
>I believe the MIME types are fetched from the desktop file for
2043 packages providing appstream metadata.
</p
>
2048 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2049 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2050 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2051 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2052 <description><p
>Most people seem not to realise that every time they walk around
2053 with the computerised radio beacon known as a mobile phone their
2054 position is tracked by the phone company and often stored for a long
2055 time (like every time a SMS is received or sent). And if their
2056 computerised radio beacon is capable of running programs (often called
2057 mobile apps) downloaded from the Internet, these programs are often
2058 also capable of tracking their location (if the app requested access
2059 during installation). And when these programs send out information to
2060 central collection points, the location is often included, unless
2061 extra care is taken to not send the location. The provided
2062 information is used by several entities, for good and bad (what is
2063 good and bad, depend on your point of view). What is certain, is that
2064 the private sphere and the right to free movement is challenged and
2065 perhaps even eradicated for those announcing their location this way,
2066 when they share their whereabouts with private and public
2069 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2071 <p
>The phone company logs provide a register of locations to check out
2072 when one want to figure out what the tracked person was doing. It is
2073 unavailable for most of us, but provided to selected government
2074 officials, company staff, those illegally buying information from
2075 unfaithful servants and crackers stealing the information. But the
2076 public information can be collected and analysed, and a free software
2077 tool to do so is called
2078 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2079 discovered it when I read
2080 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2081 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2082 November
2014, and decided to check if it was available in Debian.
2083 The python program was in Debian, but
2084 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2085 Debian
</a
> was completely broken and practically unmaintained. I
2086 uploaded a new version which did not work quite right, but did not
2087 have time to fix it then. This Christmas I decided to finally try to
2088 get Creepy operational in Debian. Now a fixed version is available in
2089 Debian unstable and testing, and almost all Debian specific patches
2091 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2093 <p
>The Creepy program visualises geolocation information fetched from
2094 Twitter, Instagram, Flickr and Google+, and allow one to get a
2095 complete picture of every social media message posted recently in a
2096 given area, or track the movement of a given individual across all
2097 these services. Earlier it was possible to use the search API of at
2098 least some of these services without identifying oneself, but these
2099 days it is impossible. This mean that to use Creepy, you need to
2100 configure it to log in as yourself on these services, and provide
2101 information to them about your search interests. This should be taken
2102 into account when using Creepy, as it will also share information
2103 about yourself with the services.
</p
>
2105 <p
>The picture above show the twitter messages sent from (or at least
2106 geotagged with a position from) the city centre of Oslo, the capital
2107 of Norway. One useful way to use Creepy is to first look at
2108 information tagged with an area of interest, and next look at all the
2109 information provided by one or more individuals who was in the area.
2110 I tested it by checking out which celebrity provide their location in
2111 twitter messages by checkout out who sent twitter messages near a
2112 Norwegian TV station, and next could track their position over time,
2113 making it possible to locate their home and work place, among other
2114 things. A similar technique have been
2115 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2116 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2117 tool to discover lying governments, and a useful tool to help people
2118 understand the value of the private information they provide to the
2121 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2122 it depend on several python modules currently missing in Jessie (at
2123 least python-instagram, python-flickrapi and
2124 python-requests-toolbelt).
</p
>
2126 <p
>(I have uploaded
2127 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2128 screenshots.debian.net
</a
> and licensed it under the same terms as the
2129 Creepy program in Debian.)
</p
>
2134 <title>Always download Debian packages using Tor - the simple recipe
</title>
2135 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2137 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2138 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2139 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2140 that those listening on the Internet lines would have good reason to
2141 believe a computer have a given security hole
</a
> if it download a
2142 security fix from a Debian mirror. This is a good reason to always
2143 use encrypted connections to the Debian mirror, to make sure those
2144 listening do not know which IP address to attack. In August, Richard
2145 Hartmann observed that encryption was not enough, when it was possible
2146 to interfere download size to security patches or the fact that
2147 download took place shortly after a security fix was released, and
2148 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2149 to always use Tor to download packages from the Debian mirror
</a
>. He
2150 was not the first to propose this, as the
2151 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2152 package by Tim Retout already existed to make it easy to convince apt
2153 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2154 aware of that package when I read the blog post from Richard.
</p
>
2156 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2157 sysadmins, and he set up a Tor hidden service on one of the central
2158 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2159 it possible to download packages directly between two tor nodes,
2160 making sure the network traffic always were encrypted.
</p
>
2162 <p
>Here is a short recipe for enabling this on your machine, by
2163 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2164 urls with tor+http and tor+https, and using the hidden service instead
2165 of the official Debian mirror site. I recommend installing
2166 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2167 done in /etc/.
</p
>
2169 <blockquote
><pre
>
2170 apt install apt-transport-tor
2171 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2172 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2173 </pre
></blockquote
>
2175 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2176 the sed commands for these too. The sed command is assuming your are
2177 using the ftp.debian.org Debian mirror. Adjust the command (or just
2178 edit the file manually) to match your mirror.
</p
>
2180 <p
>This work in Debian Jessie and later. Note that tools like
2181 <tt
>apt-file
</tt
> only recently started using the apt transport
2182 system, and do not work with these tor+http URLs. For
2183 <tt
>apt-file
</tt
> you need the version currently in experimental,
2184 which need a recent apt version currently only in unstable. So if you
2185 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2187 <p
>Another advantage from this change is that your machine will start
2188 using Tor regularly and at fairly random intervals (every time you
2189 update the package lists or upgrade or install a new package), thus
2190 masking other Tor traffic done from the same machine. Using Tor will
2191 become normal for the machine in question.
</p
>
2193 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2194 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2195 enabled. It would be great if it was the default on any Debian
2201 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2202 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2203 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2204 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2205 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2206 call the car license plate numbers in those days. I would write the
2207 numbers down in my little book and compare notes with the other kids
2208 to see how many region codes we had seen and if we had seen some
2209 exotic or special region codes and numbers. It was a fun game to pass
2210 time, as we kids have plenty of it.
</p
>
2212 <p
>A few days I came across
2213 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2214 project
</a
>, a free software project to automatically discover and
2215 report license plates in images and video streams, and provide the
2216 "car numbers
" in a machine readable format. I
've been looking for
2217 such system for a while now, because I believe it is a bad idea that the
2218 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2219 number plate recognition
</a
> tool only is available in the hands of
2220 the powerful, and want it to be available also for the powerless to
2221 even the score when it comes to surveillance and sousveillance. I
2222 discovered the developer
2223 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2224 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2225 help him get it into shape to get the package uploaded into the Debian
2228 <p
>Today we finally managed to get the package into shape and uploaded
2229 it into Debian, where it currently
2230 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2231 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2233 <p
>I guess you are wondering why on earth such tool would be useful
2234 for the common folks, ie those not running a large government
2235 surveillance system? Well, I plan to put it in a computer on my bike
2236 and in my car, tracking the cars nearby and allowing me to be notified
2237 when number plates on my watch list are discovered. Another use case
2238 was suggested by a friend of mine, who wanted to set it up at his home
2239 to open the car port automatically when it discovered the plate on his
2240 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2241 capable of placing his license plate number of a piece of cardboard to
2242 open his car port, men replied that it was always unlocked anyway. I
2243 guess for such use case it make sense. I am sure there are other use
2244 cases too, for those with imagination and a vision.
</p
>
2246 <p
>If you want to build your own version of the Debian package, check
2247 out the upstream git source and symlink ./distros/debian to ./debian/
2248 before running
"debuild
" to build the source. Or wait a bit until the
2249 package show up in unstable.
</p
>
2254 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2255 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2256 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2257 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2258 <description><p
>Around three years ago, I created
2259 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2260 system
</a
> to get a more practical solution in Debian for handing
2261 hardware related packages. A GUI system in the isenkram package will
2262 present a pop-up dialog when some hardware dongle supported by
2263 relevant packages in Debian is inserted into the machine. The same
2264 lookup mechanism to detect packages is available as command line
2265 tools in the isenkram-cli package. In addition to mapping hardware,
2266 it will also map kernel firmware files to packages and make it easy to
2267 install needed firmware packages automatically. The key for this
2268 system to work is a good way to map hardware to packages, in other
2269 words, allow packages to announce what hardware they will work
2272 <p
>I started by providing data files in the isenkram source, and
2273 adding code to download the latest version of these data files at run
2274 time, to ensure every user had the most up to date mapping available.
2275 I also added support for storing the mapping in the Packages file in
2276 the apt repositories, but did not push this approach because while I
2277 was trying to figure out how to best store hardware/package mappings,
2278 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2279 appstream system
</a
> was announced. I got in touch and suggested to
2280 add the hardware mapping into that data set to be able to use
2281 appstream as a data source, and this was accepted at least for the
2282 Debian version of appstream.
</p
>
2284 <p
>A few days ago using appstream in Debian for this became possible,
2285 and today I uploaded a new version
0.20 of isenkram adding support for
2286 appstream as a data source for mapping hardware to packages. The only
2287 package so far using appstream to announce its hardware support is my
2288 pymissile package. I got help from Matthias Klumpp with figuring out
2289 how do add the required
2290 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2291 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2292 this content:
</p
>
2294 <blockquote
><pre
>
2295 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2296 &lt;component
&gt;
2297 &lt;id
&gt;pymissile
&lt;/id
&gt;
2298 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2299 &lt;name
&gt;pymissile
&lt;/name
&gt;
2300 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2301 &lt;description
&gt;
2303 Pymissile provides a curses interface to control an original
2304 Marks and Spencer / Striker USB Missile Launcher, as well as a
2305 motion control script to allow a webcamera to control the
2308 &lt;/description
&gt;
2309 &lt;provides
&gt;
2310 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2311 &lt;/provides
&gt;
2312 &lt;/component
&gt;
2313 </pre
></blockquote
>
2315 <p
>The key for isenkram is the component/provides/modalias value,
2316 which is a glob style match rule for hardware specific strings
2317 (modalias strings) provided by the Linux kernel. In this case, it
2318 will map to all USB devices with vendor code
1130 and product code
2321 <p
>Note, it is important that the license of all the metadata files
2322 are compatible to have permissions to aggregate them into archive wide
2323 appstream files. Matthias suggested to use MIT or BSD licenses for
2324 these files. A challenge is figuring out a good id for the data, as
2325 it is supposed to be globally unique and shared across distributions
2326 (in other words, best to coordinate with upstream what to use). But
2327 it can be changed later or, so we went with the package name as
2328 upstream for this project is dormant.
</p
>
2330 <p
>To get the metadata file installed in the correct location for the
2331 mirror update scripts to pick it up and include its content the
2332 appstream data source, the file must be installed in the binary
2333 package under /usr/share/appdata/. I did this by adding the following
2334 line to debian/pymissile.install:
</p
>
2336 <blockquote
><pre
>
2337 debian/pymissile.metainfo.xml usr/share/appdata
2338 </pre
></blockquote
>
2340 <p
>With that in place, the command line tool isenkram-lookup will list
2341 all packages useful on the current computer automatically, and the GUI
2342 pop-up handler will propose to install the package not already
2343 installed if a hardware dongle is inserted into the machine in
2346 <p
>Details of the modalias field in appstream is available from the
2347 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2349 <p
>To locate the modalias values of all hardware present in a machine,
2350 try running this command on the command line:
</p
>
2352 <blockquote
><pre
>
2353 cat $(find /sys/devices/|grep modalias)
2354 </pre
></blockquote
>
2356 <p
>To learn more about the isenkram system, please check out
2357 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2358 blog posts tagged isenkram
</a
>.
</p
>
2363 <title>The GNU General Public License is not magic pixie dust
</title>
2364 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2365 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2366 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2367 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2368 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2369 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2370 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2371 I quote the blog post from Paul in full here with his permission:
<p
>
2375 <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
>
2378 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2380 The first step is to choose a
2381 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2384 The next step is, when someone fails to follow that copyleft license,
2385 <b
>it must be enforced
</b
><br/
>
2387 and its a simple fact of our modern society that such type of
2390 is incredibly expensive to do and incredibly difficult to do.
2393 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2394 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2395 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2396 0x57</a
></small
></p
>
2398 <p
>As the Debian Website
2399 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2400 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2401 imply, public domain and permissively licensed software can lead to
2402 the production of more proprietary software as people discover useful
2403 software, extend it and or incorporate it into their hardware or
2404 software products. Copyleft licenses such as the GNU GPL were created
2405 to close off this avenue to the production of proprietary software but
2406 such licenses are not enough. With the ongoing adoption of Free
2407 Software by individuals and groups, inevitably the community
's
2408 expectations of license compliance are violated, usually out of
2409 ignorance of the way Free Software works, but not always. As Karen
2410 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2411 Freedom
">FaiF
</a
>
2412 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2413 copyleft is nothing if no-one is willing and able to stand up in court
2414 to protect it. The reality of today
's world is that legal
2415 representation is expensive, difficult and time consuming. With
2416 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2417 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2418 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2419 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2420 of the Linux project, Debian and other groups against GPL violations.
2421 In March the SFC supported a
2422 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2423 by Christoph Hellwig
</a
> against VMware for refusing to
2424 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2425 with the GPL
</a
> in relation to their use of parts of the Linux
2426 kernel. Since then two of their sponsors pulled corporate funding and
2428 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2429 or cancelled their talks
</a
>. As a result they have decided to rely
2430 less on corporate funding and more on the broad community of
2431 individuals who support Free Software and copyleft. So the SFC has
2432 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2433 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2434 a community of folks who stand up for copyleft and the GPL by
2435 supporting their work on promoting and supporting copyleft and Free
2438 <p
>If you support Free Software,
2439 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2440 what the SFC do, agree with their
2441 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2442 principles
</a
>, are happy about their
2443 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2444 work on a project that is an SFC
2445 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2446 just want to stand up for copyleft, please join
2447 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2448 Allan Webber
</a
>,
2449 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2451 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2452 Bacon
</a
>, myself and
2453 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2455 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2456 next week your donation will be
2457 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2458 by an anonymous donor. Please also consider asking your employer to
2459 match your donation or become a sponsor of SFC. Don
't forget to
2460 spread the word about your support for SFC via email, your blog and or
2461 social media accounts.
</p
>
2465 <p
>I agree with Paul on this topic and just signed up as a Supporter
2466 of Software Freedom Conservancy myself. Perhaps you should be a
2467 supporter too?
</p
>
2472 <title>PGP key transition statement for key EE4E02F9
</title>
2473 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2474 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2475 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2476 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2477 set it up properly. I wanted to generate it offline and have it
2478 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2479 smart card
</a
> for daily use, and learning how to do it and finding
2480 time to sit down with an offline machine almost took forever. But
2481 finally I
've been able to complete the process, and have now moved
2482 from my old GPG key to a new GPG key. See
2483 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2484 full transition statement, signed with both my old and new key
</a
> for
2485 the details. This is my new key:
</p
>
2488 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2489 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2490 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2491 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2492 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2493 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2494 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2497 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2498 my old key.
</p
>
2500 <p
>If you signed my old key
2501 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2502 I
'd very much appreciate a signature on my new key, details and
2503 instructions in the transition statement. I m happy to reciprocate if
2504 you have a similarly signed transition statement to present.
</p
>
2509 <title>The life and death of a laptop battery
</title>
2510 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2512 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2513 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2514 But this do not last. The last few laptops gave me a feeling that
2515 within a year, the life time is just a fraction of what it used to be,
2516 and it slowly become painful to use the laptop without power connected
2517 all the time. Because of this, when I got a new Thinkpad X230 laptop
2518 about two years ago, I decided to monitor its battery state to have
2519 more hard facts when the battery started to fail.
</p
>
2521 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2523 <p
>First I tried to find a sensible Debian package to record the
2524 battery status, assuming that this must be a problem already handled
2525 by someone else. I found
2526 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2527 which collects statistics from the battery, but it was completely
2528 broken. I sent a few suggestions to the maintainer, but decided to
2529 write my own collector as a shell script while I waited for feedback
2531 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2532 blog post about the battery development on a MacBook Air
</a
> I also
2534 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2535 available in Debian.
</p
>
2537 <p
>I started my collector
2013-
07-
15, and it has been collecting
2538 battery stats ever since. Now my
2539 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2540 measurements, from the time the battery was working great until now,
2541 when it is unable to charge above
7% of original capacity. My
2542 collector shell script is quite simple and look like this:
</p
>
2547 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2549 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2550 logfile=/var/log/hjemmenett-battery-status.log
2552 files=
"manufacturer model_name technology serial_number \
2553 energy_full energy_full_design energy_now cycle_count status
"
2555 if [ ! -e
"$logfile
" ] ; then
2557 printf
"timestamp,
"
2559 printf
"%s,
" $f
2562 )
> "$logfile
"
2566 # Print complete message in one echo call, to avoid race condition
2567 # when several log processes run in parallel.
2568 msg=$(printf
"%s,
" $(date +%s); \
2569 for f in $files; do \
2570 printf
"%s,
" $(cat $f); \
2572 echo
"$msg
"
2575 cd /sys/class/power_supply
2578 (cd $bat
&& log_battery
>> "$logfile
")
2582 <p
>The script is called when the power management system detect a
2583 change in the power status (power plug in or out), and when going into
2584 and out of hibernation and suspend. In addition, it collect a value
2585 every
10 minutes. This make it possible for me know when the battery
2586 is discharging, charging and how the maximum charge change over time.
2587 The code for the Debian package
2588 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2589 available on github
</a
>.
</p
>
2591 <p
>The collected log file look like this:
</p
>
2594 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2595 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2597 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2598 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2601 <p
>I wrote a small script to create a graph of the charge development
2602 over time. This graph depicted above show the slow death of my laptop
2605 <p
>But why is this happening? Why are my laptop batteries always
2606 dying in a year or two, while the batteries of space probes and
2607 satellites keep working year after year. If we are to believe
2608 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2609 University
</a
>, the cause is me charging the battery whenever I have a
2610 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2611 all the time, but to stay below
90% of full charge most of the time.
2612 I
've been told that the Tesla electric cars
2613 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2614 the charge of their batteries to
80%
</a
>, with the option to charge to
2615 100% when preparing for a longer trip (not that I would want a car
2616 like Tesla where rights to privacy is abandoned, but that is another
2617 story), which I guess is the option we should have for laptops on
2618 Linux too.
</p
>
2620 <p
>Is there a good and generic way with Linux to tell the battery to
2621 stop charging at
80%, unless requested to charge to
100% once in
2622 preparation for a longer trip? I found
2623 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2624 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2625 80%
</a
>, but could not get it to work (kernel module refused to
2628 <p
>I wonder why the battery capacity was reported to be more than
100%
2629 at the start. I also wonder why the
"full capacity
" increases some
2630 times, and if it is possible to repeat the process to get the battery
2631 back to design capacity. And I wonder if the discharge and charge
2632 speed change over time, or if this stay the same. I did not yet try
2633 to write a tool to calculate the derivative values of the battery
2634 level, but suspect some interesting insights might be learned from
2637 <p
>Update
2015-
09-
24: I got a tip to install the packages
2638 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2639 packages instead of the tp-smapi-dkms package I had tried to use
2640 initially, and use
'tlp setcharge
40 80' to change when charging start
2641 and stop. I
've done so now, but expect my existing battery is toast
2642 and need to be replaced. The proposal is unfortunately Thinkpad
2648 <title>New laptop - some more clues and ideas based on feedback
</title>
2649 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2650 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2651 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2652 <description><p
>Several people contacted me after my previous blog post about my
2653 need for a new laptop, and provided very useful feedback. I wish to
2654 thank every one of these. Several pointed me to the possibility of
2655 fixing my X230, and I am already in the process of getting Lenovo to
2656 do so thanks to the on site, next day support contract covering the
2657 machine. But the battery is almost useless (I expect to replace it
2658 with a non-official battery) and I do not expect the machine to live
2659 for many more years, so it is time to plan its replacement. If I did
2660 not have a support contract, it was suggested to find replacement parts
2661 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2662 might present a language barrier as I do not understand French.
</p
>
2664 <p
>One tip I got was to use the
2665 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2666 compare laptop models. It seem to have more models available than
2667 prisjakt.no. Another tip I got from someone I know have similar
2668 keyboard preferences was that the HP EliteBook
840 keyboard is not
2669 very good, and this matches my experience with earlier EliteBook
2670 keyboards I tested. Because of this, I will not consider it any further.
2672 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2673 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2674 (which is missing from the X240), and is working fairly well with
2675 Debian Sid/Unstable according to
2676 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2677 got on the keyboard quality are not consistent. Some say the keyboard
2678 is good, others say it is ok, while others say it is not very good.
2679 Those with experience from X41 and and X60 agree that the X250
2680 keyboard is not as good as those trusty old laptops, and suggest I
2681 keep and fix my X230 instead of upgrading, or get a used X230 to
2682 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2683 activity and battery status, which is very convenient on my X230. I
'm
2684 also told that the CPU fan is running very often, making it a bit
2685 noisy. In any case, the X250 do not work out of the box with Debian
2686 Stable/Jessie, one of my requirements.
</p
>
2688 <p
>I have also gotten a few vendor proposals, one was
2689 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2690 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2691 The latter look very attractive to me.
</p
>
2693 <p
>Again, thank you all for the very useful feedback. It help a lot
2694 as I keep looking for a replacement.
</p
>
2696 <p
>Update
2015-
07-
06: I was recommended to check out the
2697 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2699 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2700 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2705 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2706 <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>
2707 <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>
2708 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2709 <description><p
>My primary work horse laptop is failing, and will need a
2710 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2711 started flickering yesterday, and I suspect the cause is a broken
2712 cable, as changing the angle of the screen some times get rid of the
2713 flickering.
</p
>
2715 <p
>My requirements have not really changed since I bought it, and is
2717 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2718 described them in
2013</a
>. The last time I bought a laptop, I had
2720 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2721 where I could select at least a few of the requirements (mouse pin,
2722 wifi, weight) and go through the rest manually. Three button mouse
2723 and a good keyboard is not available as an option, and all the three
2724 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2725 G2) lack three mouse buttons). It is also unclear to me how good the
2726 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2727 the keyboard, even if the quality and robustness in the X series have
2728 deteriorated since X41.
</p
>
2730 <p
>I wonder how I can find a sensible laptop when none of the options
2731 seem sensible to me? Are there better services around to search the
2732 set of available laptops for features? Please send me an email if you
2733 have suggestions.
</p
>
2735 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2736 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2737 of endorsed hardware
</a
>, which is useful background information.
</p
>
2742 <title>How to stay with sysvinit in Debian Jessie
</title>
2743 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2744 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2745 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2746 <description><p
>By now, it is well known that Debian Jessie will not be using
2747 sysvinit as its boot system by default. But how can one keep using
2748 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2750 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2751 Schubert
</a
> and
2752 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2755 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2756 keep sysvinit as your boot system, create a file
2757 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2758 you upgrade:
</p
>
2760 <p
><blockquote
><pre
>
2761 Package: systemd-sysv
2762 Pin: release o=Debian
2764 </pre
></blockquote
><p
>
2766 <p
>This file content will tell apt and aptitude to not consider
2767 installing systemd-sysv as part of any installation and upgrade
2768 solution when resolving dependencies, and thus tell it to avoid
2769 systemd as a default boot system. The end result should be that the
2770 upgraded system keep using sysvinit.
</p
>
2772 <p
>If you are installing Jessie for the first time, there is no way to
2773 get sysvinit installed by default (debootstrap used by
2774 debian-installer have no option for this), but one can tell the
2775 installer to switch to sysvinit before the first boot. Either by
2776 using a kernel argument to the installer, or by adding a line to the
2777 preseed file used. First, the kernel command line argument:
2779 <p
><blockquote
><pre
>
2780 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2781 </pre
></blockquote
><p
>
2783 <p
>Next, the line to use in a preseed file:
</p
>
2785 <p
><blockquote
><pre
>
2786 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2787 </pre
></blockquote
><p
>
2789 <p
>One can of course also do this after the first boot by installing
2790 the sysvinit-core package.
</p
>
2792 <p
>I recommend only using sysvinit if you really need it, as the
2793 sysvinit boot sequence in Debian have several hardware specific bugs
2794 on Linux caused by the fact that it is unpredictable when hardware
2795 devices show up during boot. But on the other hand, the new default
2796 boot system still have a few rough edges I hope will be fixed before
2797 Jessie is released.
</p
>
2799 <p
>Update
2014-
11-
26: Inspired by
2800 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2801 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2807 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2808 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2809 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2810 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2811 <description><p
>The right to communicate with your friends and family in private,
2812 without anyone snooping, is a right every citicen have in a liberal
2813 democracy. But this right is under serious attack these days.
</p
>
2815 <p
>A while back it occurred to me that one way to make the dragnet
2816 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2817 the whisleblower Snowden) more expensive for Internet email,
2818 is to deliver all email using SMTP via Tor. Such SMTP option would be
2819 a nice addition to the FreedomBox project if we could send email
2820 between FreedomBox machines without leaking metadata about the emails
2821 to the people peeking on the wire. I
2822 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2823 this on the FreedomBox project mailing list in October
</a
> and got a
2824 lot of useful feedback and suggestions. It also became obvious to me
2825 that this was not a novel idea, as the same idea was tested and
2826 documented by Johannes Berg as early as
2006, and both
2827 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2828 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2829 propose a similar method / protocol to pass emails between users.
</p
>
2831 <p
>To implement such system one need to set up a Tor hidden service
2832 providing the SMTP protocol on port
25, and use email addresses
2833 looking like username@hidden-service-name.onion. With such addresses
2834 the connections to port
25 on hidden-service-name.onion using Tor will
2835 go to the correct SMTP server. To do this, one need to configure the
2836 Tor daemon to provide the hidden service and the mail server to accept
2837 emails for this .onion domain. To learn more about Exim configuration
2838 in Debian and test the design provided by Johannes Berg in his FAQ, I
2839 set out yesterday to create a Debian package for making it trivial to
2840 set up such SMTP over Tor service based on Debian. Getting it to work
2841 were fairly easy, and
2842 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2843 source code for the Debian package
</a
> is available from github. I
2844 plan to move it into Debian if further testing prove this to be a
2845 useful approach.
</p
>
2847 <p
>If you want to test this, set up a blank Debian machine without any
2848 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2849 get rid of exim4). Install tor, clone the git repository mentioned
2850 above, build the deb and install it on the machine. Next, run
2851 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2852 the instructions to get the service up and running. Restart tor and
2853 exim when it is done, and test mail delivery using swaks like
2856 <p
><blockquote
><pre
>
2857 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2858 --to fbx@dutlqrrmjhtfa3vp.onion
2859 </pre
></blockquote
></p
>
2861 <p
>This will test the SMTP delivery using tor. Replace the email
2862 address with your own address to test your server. :)
</p
>
2864 <p
>The setup procedure is still to complex, and I hope it can be made
2865 easier and more automatic. Especially the tor setup need more work.
2866 Also, the package include a tor-smtp tool written in C, but its task
2867 should probably be rewritten in some script language to make the deb
2868 architecture independent. It would probably also make the code easier
2869 to review. The tor-smtp tool currently need to listen on a socket for
2870 exim to talk to it and is started using xinetd. It would be better if
2871 no daemon and no socket is needed. I suspect it is possible to get
2872 exim to run a command line tool for delivery instead of talking to a
2873 socket, and hope to figure out how in a future version of this
2876 <p
>Until I wipe my test machine, I can be reached using the
2877 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2878 SMTorP. :)
</p
>
2883 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2884 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2885 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2886 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2887 <description><p
>If you ever had to moderate a mailman list, like the ones on
2888 alioth.debian.org, you know the web interface is fairly slow to
2889 operate. First you visit one web page, enter the moderation password
2890 and get a new page shown with a list of all the messages to moderate
2891 and various options for each email address. This take a while for
2892 every list you moderate, and you need to do it regularly to do a good
2893 job as a list moderator. But there is a quick alternative,
2894 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2895 listadmin program
</a
>. It allow you to check lists for new messages
2896 to moderate in a fraction of a second. Here is a test run on two
2897 lists I recently took over:
</p
>
2899 <p
><blockquote
><pre
>
2900 % time listadmin xiph
2901 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2902 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2908 </pre
></blockquote
></p
>
2910 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2911 there are no message in the moderation queue. Every morning I
2912 currently moderate
68 mailman lists, and it normally take around two
2913 minutes. When I took over the two pkg-xiph lists above a few days
2914 ago, there were
400 emails waiting in the moderator queue. It took me
2915 less than
15 minutes to process them all using the listadmin
2918 <p
>If you install
2919 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2920 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2921 with content like this, the moderation task is a breeze:
</p
>
2923 <p
><blockquote
><pre
>
2924 username username@example.org
2927 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2930 adminurl https://{domain}/mailman/admindb/{list}
2931 mailman-list@lists.example.com
2934 other-list@otherserver.example.org
2935 </pre
></blockquote
></p
>
2937 <p
>There are other options to set as well. Check the manual page to
2938 learn the details.
</p
>
2940 <p
>If you are forced to moderate lists on a mailman installation where
2941 the SSL certificate is self signed or not properly signed by a
2942 generally accepted signing authority, you can set a environment
2943 variable when calling listadmin to disable SSL verification:
</p
>
2945 <p
><blockquote
><pre
>
2946 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2947 </pre
></blockquote
></p
>
2949 <p
>If you want to moderate a subset of the lists you take care of, you
2950 can provide an argument to the listadmin script like I do in the
2951 initial screen dump (the xiph argument). Using an argument, only
2952 lists matching the argument string will be processed. This make it
2953 quick to accept messages if you notice the moderation request in your
2956 <p
>Without the listadmin program, I would never be the moderator of
68
2957 mailing lists, as I simply do not have time to spend on that if the
2958 process was any slower. The listadmin program have saved me hours of
2959 time I could spend elsewhere over the years. It truly is nice free
2962 <p
>As usual, if you use Bitcoin and want to show your support of my
2963 activities, please send Bitcoin donations to my address
2964 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2966 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2967 configuration example. Also, I
've been told that the
2968 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2974 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2975 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2976 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2977 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2978 <description><p
>When PXE installing laptops with Debian, I often run into the
2979 problem that the WiFi card require some firmware to work properly.
2980 And it has been a pain to fix this using preseeding in Debian.
2981 Normally something more is needed. But thanks to
2982 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2983 package
</a
> and its recent tasksel extension, it has now become easy
2984 to do this using simple preseeding.
</p
>
2986 <p
>The isenkram-cli package provide tasksel tasks which will install
2987 firmware for the hardware found in the machine (actually, requested by
2988 the kernel modules for the hardware). (It can also install user space
2989 programs supporting the hardware detected, but that is not the focus
2990 of this story.)
</p
>
2992 <p
>To get this working in the default installation, two preeseding
2993 values are needed. First, the isenkram-cli package must be installed
2994 into the target chroot (aka the hard drive) before tasksel is executed
2995 in the pkgsel step of the debian-installer system. This is done by
2996 preseeding the base-installer/includes debconf value to include the
2997 isenkram-cli package. The package name is next passed to debootstrap
2998 for installation. With the isenkram-cli package in place, tasksel
2999 will automatically use the isenkram tasks to detect hardware specific
3000 packages for the machine being installed and install them, because
3001 isenkram-cli contain tasksel tasks.
</p
>
3003 <p
>Second, one need to enable the non-free APT repository, because
3004 most firmware unfortunately is non-free. This is done by preseeding
3005 the apt-mirror-setup step. This is unfortunate, but for a lot of
3006 hardware it is the only option in Debian.
</p
>
3008 <p
>The end result is two lines needed in your preseeding file to get
3009 firmware installed automatically by the installer:
</p
>
3011 <p
><blockquote
><pre
>
3012 base-installer base-installer/includes string isenkram-cli
3013 apt-mirror-setup apt-setup/non-free boolean true
3014 </pre
></blockquote
></p
>
3016 <p
>The current version of isenkram-cli in testing/jessie will install
3017 both firmware and user space packages when using this method. It also
3018 do not work well, so use version
0.15 or later. Installing both
3019 firmware and user space packages might give you a bit more than you
3020 want, so I decided to split the tasksel task in two, one for firmware
3021 and one for user space programs. The firmware task is enabled by
3022 default, while the one for user space programs is not. This split is
3023 implemented in the package currently in unstable.
</p
>
3025 <p
>If you decide to give this a go, please let me know (via email) how
3026 this recipe work for you. :)
</p
>
3028 <p
>So, I bet you are wondering, how can this work. First and
3029 foremost, it work because tasksel is modular, and driven by whatever
3030 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
3031 isenkram-cli package place two files for tasksel to find. First there
3032 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
3034 <p
><blockquote
><pre
>
3035 Task: isenkram-packages
3037 Description: Hardware specific packages (autodetected by isenkram)
3038 Based on the detected hardware various hardware specific packages are
3040 Test-new-install: show show
3042 Packages: for-current-hardware
3044 Task: isenkram-firmware
3046 Description: Hardware specific firmware packages (autodetected by isenkram)
3047 Based on the detected hardware various hardware specific firmware
3048 packages are proposed.
3049 Test-new-install: mark show
3051 Packages: for-current-hardware-firmware
3052 </pre
></blockquote
></p
>
3054 <p
>The key parts are Test-new-install which indicate how the task
3055 should be handled and the Packages line referencing to a script in
3056 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3057 list of packages to install. The for-current-hardware-firmware script
3058 look like this to list relevant firmware for the machine:
3060 <p
><blockquote
><pre
>
3063 PATH=/usr/sbin:$PATH
3065 isenkram-autoinstall-firmware -l
3066 </pre
></blockquote
></p
>
3068 <p
>With those two pieces in place, the firmware is installed by
3069 tasksel during the normal d-i run. :)
</p
>
3071 <p
>If you want to test what tasksel will install when isenkram-cli is
3072 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3073 --new-install
</tt
> to get the list of packages that tasksel would
3076 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3077 pilots in testing this feature, as isenkram is used there now to
3078 install firmware, replacing the earlier scripts.
</p
>
3083 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3084 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3085 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3086 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3087 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3088 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3089 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3090 on a screen normally showing the bread types and prizes:
</p
>
3092 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3094 <p
>If it had booted as it was supposed to, I would never had known
3095 about this hidden Linux installation. It is interesting what
3096 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3101 <title>New lsdvd release version
0.17 is ready
</title>
3102 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3104 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3105 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3106 got a new set of developers a few weeks ago, after the original
3107 developer decided to step down and pass the project to fresh blood.
3108 This project is now maintained by Petter Reinholdtsen and Steve
3111 <p
>I just wrapped up
3112 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3113 new lsdvd release
</a
>, available in git or from
3114 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3115 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3120 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3121 <li
>Check for garbage in the program chains, which indicate that a track is
3122 non-existant, to work around additional copy protection
</li
>
3123 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3124 <li
>Fix pallete display of first entry
</li
>
3125 <li
>Fix include orders
</li
>
3126 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3127 <li
>Fix the chapter count
</li
>
3128 <li
>Make sure the array size and the array limit used when initialising
3129 the palette size is the same.
</li
>
3130 <li
>Fix array printing.
</li
>
3131 <li
>Correct subsecond calculations.
</li
>
3132 <li
>Add sector information to the output format.
</li
>
3133 <li
>Clean up code to be closer to ANSI C and compile without warnings
3134 with more GCC compiler warnings.
</li
>
3138 <p
>This change bring together patches for lsdvd in use in various
3139 Linux and Unix distributions, as well as patches submitted to the
3140 project the last nine years. Please check it out. :)
</p
>
3145 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3146 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3148 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3149 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3150 project
</a
> provide a Linux solution for schools, including a
3151 powerful desktop with education software, a central server providing
3152 web pages, user database, user home directories, central login and PXE
3153 boot of both clients without disk and the installation to install Debian
3154 Edu on machines with disk (and a few other services perhaps to small
3155 to mention here). We in the Debian Edu team are currently working on
3156 the Jessie based version, trying to get everything in shape before the
3157 freeze, to avoid having to maintain our own package repository in the
3159 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3160 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3161 work left. Some fatal problems block testing, breaking the installer,
3162 but it is possible to work around these to get anyway. Here is a
3163 recipe on how to get the installation limping along.
</p
>
3165 <p
>First, download the test ISO via
3166 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3167 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3169 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3170 The ISO build was broken on Tuesday, so we do not get a new ISO every
3171 12 hours or so, but thankfully the ISO we already got we are able to
3172 install with some tweaking.
</p
>
3174 <p
>When you get to the Debian Edu profile question, go to tty2
3175 (use Alt-Ctrl-F2), run
</p
>
3177 <p
><blockquote
><pre
>
3178 nano /usr/bin/edu-eatmydata-install
3179 </pre
></blockquote
></p
>
3181 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3182 optimization. Return to the installation, select the profile you want
3183 and continue. Without this change, exim4-config will fail to install
3184 due to a known bug in eatmydata.
</p
>
3186 <p
>When you get the grub question at the end, answer /dev/sda (or if
3187 this do not work, figure out what your correct value would be. All my
3188 test machines need /dev/sda, so I have no advice if it do not fit
3189 your need.
</p
>
3191 <p
>If you installed a profile including a graphical desktop, log in as
3192 root after the initial boot from hard drive, and install the
3193 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3194 or mate. If you want several desktop options, install more than one
3195 metapackage. Once this is done, reboot and you should have a working
3196 graphical login screen. This workaround should no longer be needed
3197 once the education-tasks package version
1.801 enter testing in two
3200 <p
>I believe the ISO build will start working on two days when the new
3201 tasksel package enter testing and Steve McIntyre get a chance to
3202 update the debian-cd git repository. The eatmydata, grub and desktop
3203 issues are already fixed in unstable and testing, and should show up
3204 on the ISO as soon as the ISO build start working again. Well the
3205 eatmydata optimization is really just disabled. The proper fix
3206 require an upload by the eatmydata maintainer applying the patch
3207 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3208 The rest have proper fixes in unstable.
</p
>
3210 <p
>I hope this get you going with the installation testing, as we are
3211 quickly running out of time trying to get our Jessie based
3212 installation ready before the distribution freeze in a month.
</p
>
3217 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3218 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3219 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3220 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3221 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3222 to handle my fairly large DVD collection. It is a nice command line
3223 tool to get details about a DVD, like title, tracks, track length,
3224 etc, in XML, Perl or human readable format. But lsdvd have not seen
3225 any new development since
2006 and had a few irritating bugs affecting
3226 its use with some DVDs. Upstream seemed to be dead, and in January I
3227 sent a small probe asking for a version control repository for the
3228 project, without any reply. But I use it regularly and would like to
3229 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3230 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3231 the project admin, and after getting a reply from him explaining that
3232 he was no longer interested in the project, I asked if I could take
3233 over. And yesterday, I became project admin.
</p
>
3235 <p
>I
've been in touch with a Gentoo developer and the Debian
3236 maintainer interested in joining forces to maintain the upstream
3237 project, and I hope we can get a new release out fairly quickly,
3238 collecting the patches spread around on the internet into on place.
3239 I
've added the relevant Debian patches to the freshly created git
3240 repository, and expect the Gentoo patches to make it too. If you got
3241 a DVD collection and care about command line tools, check out
3242 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3243 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3244 list
</a
>. :)
</p
>
3249 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3250 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3251 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3252 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3253 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3254 a lot quicker. When we install more than
2000 packages in
3255 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3256 tasksel in the installer, unpacking the binary packages take forever.
3257 A part of the slow I/O issue was discussed in
3258 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3259 much file system sync-ing done by dpkg, which is the package
3260 responsible for unpacking the binary packages. Other parts (like code
3261 executed by postinst scripts) might also sync to disk during
3262 installation. All this sync-ing to disk do not really make sense to
3263 me. If the machine crash half-way through, I start over, I do not try
3264 to salvage the half installed system. So the failure sync-ing is
3265 supposed to protect against, hardware or system crash, is not really
3266 relevant while the installer is running.
</p
>
3268 <p
>A few days ago, I thought of a way to get rid of all the file
3269 system sync()-ing in a fairly non-intrusive way, without the need to
3270 change the code in several packages. The idea is not new, but I have
3271 not heard anyone propose the approach using dpkg-divert before. It
3272 depend on the small and clever package
3273 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3274 uses LD_PRELOAD to replace the system functions for syncing data to
3275 disk with functions doing nothing, thus allowing programs to live
3276 dangerous while speeding up disk I/O significantly. Instead of
3277 modifying the implementation of dpkg, apt and tasksel (which are the
3278 packages responsible for selecting, fetching and installing packages),
3279 it occurred to me that we could just divert the programs away, replace
3280 them with a simple shell wrapper calling
3281 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3282 Two days ago I decided to test the idea, and wrapped up a simple
3283 implementation for the Debian Edu udeb.
</p
>
3285 <p
>The effect was stunning. In my first test it reduced the running
3286 time of the pkgsel step (installing tasks) from
64 to less than
44
3287 minutes (
20 minutes shaved off the installation) on an old Dell
3288 Latitude D505 machine. I am not quite sure what the optimised time
3289 would have been, as I messed up the testing a bit, causing the debconf
3290 priority to get low enough for two questions to pop up during
3291 installation. As soon as I saw the questions I moved the installation
3292 along, but do not know how long the question were holding up the
3293 installation. I did some more measurements using Debian Edu Jessie,
3294 and got these results. The time measured is the time stamp in
3295 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3296 "pkgsel: finishing up
" lines, if you want to do the same measurement
3297 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3298 timing thus do not depend on how quickly the user handle the tasksel
3301 <p
><table
>
3304 <th
>Machine/setup
</th
>
3305 <th
>Original tasksel
</th
>
3306 <th
>Optimised tasksel
</th
>
3307 <th
>Reduction
</th
>
3311 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3312 <td
>64 min (
07:
46-
08:
50)
</td
>
3313 <td
><44 min (
11:
27-
12:
11)
</td
>
3314 <td
>>20 min
18%
</td
>
3318 <td
>Latitude D505 Roaming LXDE
</td
>
3319 <td
>57 min (
08:
48-
09:
45)
</td
>
3320 <td
>34 min (
07:
43-
08:
17)
</td
>
3321 <td
>23 min
40%
</td
>
3325 <td
>Latitude D505 Minimal
</td
>
3326 <td
>22 min (
10:
37-
10:
59)
</td
>
3327 <td
>11 min (
11:
16-
11:
27)
</td
>
3328 <td
>11 min
50%
</td
>
3332 <td
>Thinkpad X200 Minimal
</td
>
3333 <td
>6 min (
08:
19-
08:
25)
</td
>
3334 <td
>4 min (
08:
04-
08:
08)
</td
>
3335 <td
>2 min
33%
</td
>
3339 <td
>Thinkpad X200 Roaming KDE
</td
>
3340 <td
>19 min (
09:
21-
09:
40)
</td
>
3341 <td
>15 min (
10:
25-
10:
40)
</td
>
3342 <td
>4 min
21%
</td
>
3345 </table
></p
>
3347 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3348 time is spent downloading packages. The connection to the Internet
3349 was
100Mbit/s during testing, so downloading should not be a
3350 significant factor in the measurement. Download typically took a few
3351 seconds to a few minutes, depending on the amount of packages being
3352 installed.
</p
>
3354 <p
>The speedup is implemented by using two hooks in
3355 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3356 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3357 finish-install.d hook to remove the divert at the end of the
3358 installation. I picked the pre-pkgsel.d hook instead of the
3359 post-base-installer.d hook because I test using an ISO without the
3360 eatmydata package included, and the post-base-installer.d hook in
3361 Debian Edu can only operate on packages included in the ISO. The
3362 negative effect of this is that I am unable to activate this
3363 optimization for the kernel installation step in d-i. If the code is
3364 moved to the post-base-installer.d hook, the speedup would be larger
3365 for the entire installation.
</p
>
3367 <p
>I
've implemented this in the
3368 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3369 git repository, and plan to provide the optimization as part of the
3370 Debian Edu installation. If you want to test this yourself, you can
3371 create two files in the installer (or in an udeb). One shell script
3372 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3374 <p
><blockquote
><pre
>
3377 . /usr/share/debconf/confmodule
3379 logger -t my-pkgsel
"info: $*
"
3382 logger -t my-pkgsel
"error: $*
"
3384 override_install() {
3385 apt-install eatmydata || true
3386 if [ -x /target/usr/bin/eatmydata ] ; then
3387 for bin in dpkg apt-get aptitude tasksel ; do
3389 # Test that the file exist and have not been diverted already.
3390 if [ -f /target$file ] ; then
3391 info
"diverting $file using eatmydata
"
3392 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3393 > /target$file.edu
3394 chmod
755 /target$file.edu
3395 in-target dpkg-divert --package debian-edu-config \
3396 --rename --quiet --add $file
3397 ln -sf ./$bin.edu /target$file
3399 error
"unable to divert $file, as it is missing.
"
3403 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3408 </pre
></blockquote
></p
>
3410 <p
>To clean up, another shell script should go into
3411 /usr/lib/finish-install.d/ with code like this:
3413 <p
><blockquote
><pre
>
3415 . /usr/share/debconf/confmodule
3417 logger -t my-finish-install
"error: $@
"
3419 remove_install_override() {
3420 for bin in dpkg apt-get aptitude tasksel ; do
3422 if [ -x /target$file.edu ] ; then
3424 in-target dpkg-divert --package debian-edu-config \
3425 --rename --quiet --remove $file
3428 error
"Missing divert for $file.
"
3431 sync # Flush file buffers before continuing
3434 remove_install_override
3435 </pre
></blockquote
></p
>
3437 <p
>In Debian Edu, I placed both code fragments in a separate script
3438 edu-eatmydata-install and call it from the pre-pkgsel.d and
3439 finish-install.d scripts.
</p
>
3441 <p
>By now you might ask if this change should get into the normal
3442 Debian installer too? I suspect it should, but am not sure the
3443 current debian-installer coordinators find it useful enough. It also
3444 depend on the side effects of the change. I
'm not aware of any, but I
3445 guess we will see if the change is safe after some more testing.
3446 Perhaps there is some package in Debian depending on sync() and
3447 fsync() having effect? Perhaps it should go into its own udeb, to
3448 allow those of us wanting to enable it to do so without affecting
3451 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3452 will break installation of all programs using gnutls because of
3453 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3454 eatmydata package in Debian will solve it.
</p
>
3456 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3457 the optimization work again. And I have discovered that the
3458 dpkg-divert trick is not really needed and implemented a slightly
3459 simpler approach as part of the debian-edu-install package. See
3460 tools/edu-eatmydata-install in the source package.
</p
>
3462 <p
>Update
2014-
11-
11: Unfortunately, a new
3463 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3464 triggering on i386 made it into testing, and broke this installation
3465 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3466 request
768893</a
> is accepted, it should be working again.
</p
>
3471 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3472 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3473 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3474 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3475 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3476 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3477 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3478 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3479 learn that there is a large set of publicly available key servers to
3480 use when looking for peoples public key. So far I have used
3481 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3482 were misbehaving, but those days are ended. The servers I have used
3483 up until yesterday have been slow and some times unavailable. I hope
3484 those problems are gone now.
</p
>
3486 <p
>Behind the round robin DNS entry of the
3487 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3488 there is a pool of more than
100 keyservers which are checked every
3489 day to ensure they are well connected and up to date. It must be
3490 better than what I have used so far. :)
</p
>
3492 <p
>Yesterdays speaker told me that the service is the default
3493 keyserver provided by the default configuration in GnuPG, but this do
3494 not seem to be used in Debian. Perhaps it should?
</p
>
3496 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3499 <p
><blockquote
><pre
>
3500 keyserver pool.sks-keyservers.net
3501 </pre
></blockquote
></p
>
3503 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3504 entries in DNS. Just for fun, I did just that at work, so now every
3505 user of GnuPG at the University of Oslo should find a OpenGPG
3506 keyserver automatically should their need it:
</p
>
3508 <p
><blockquote
><pre
>
3509 % host -t srv _pgpkey-http._tcp.uio.no
3510 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3512 </pre
></blockquote
></p
>
3514 <p
>Now if only
3515 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3516 HKP lookup protocol
</a
> supported finding signature paths, I would be
3517 very happy. It can look up a given key or search for a user ID, but I
3518 normally do not want that, but to find a trust path from my key to
3519 another key. Given a user ID or key ID, I would like to find (and
3520 download) the keys representing a signature path from my key to the
3521 key in question, to be able to get a trust path between the two keys.
3522 This is as far as I can tell not possible today. Perhaps something
3523 for a future version of the protocol?
</p
>
3528 <title>From English wiki to translated PDF and epub via Docbook
</title>
3529 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3530 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3531 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3532 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3533 project
</a
> provide an instruction manual for teachers, system
3534 administrators and other users that contain useful tips for setting up
3535 and maintaining a Debian Edu installation. This text is about how the
3536 text processing of this manual is handled in the project.
</p
>
3538 <p
>One goal of the project is to provide information in the native
3539 language of its users, and for this we need to handle translations.
3540 But we also want to make sure each language contain the same
3541 information, so for this we need a good way to keep the translations
3542 in sync. And we want it to be easy for our users to improve the
3543 documentation, avoiding the need to learn special formats or tools to
3544 contribute, and the obvious way to do this is to make it possible to
3545 edit the documentation using a web browser. We also want it to be
3546 easy for translators to keep the translation up to date, and give them
3547 help in figuring out what need to be translated. Here is the list of
3548 tools and the process we have found trying to reach all these
3551 <p
>We maintain the authoritative source of our manual in the
3552 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3553 wiki
</a
>, as several wiki pages written in English. It consist of one
3554 front page with references to the different chapters, several pages
3555 for each chapter, and finally one
"collection page
" gluing all the
3556 chapters together into one large web page (aka
3557 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3558 AllInOne page
</a
>). The AllInOne page is the one used for further
3559 processing and translations. Thanks to the fact that the
3560 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3561 wiki.debian.org support exporting pages in
3562 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3563 the list of pages to export using the raw version of the AllInOne
3564 page, loop over each of them to generate a Docbook XML version of the
3565 manual. This process also download images and transform image
3566 references to use the locally downloaded images. The generated
3567 Docbook XML files are slightly broken, so some post-processing is done
3568 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3569 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3570 a handfull of images. The XML file can now be used to generate PDF, HTML
3571 and epub versions of the English manual. This is the basic step of
3572 our process, making PDF (using dblatex), HTML (using xsltproc) and
3573 epub (using dbtoepub) version from Docbook XML, and the resulting files
3574 are placed in the debian-edu-doc-en binary package.
</p
>
3576 <p
>But English documentation is not enough for us. We want translated
3577 documentation too, and we want to make it easy for translators to
3578 track the English original. For this we use the
3579 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3580 which allow us to transform the English Docbook XML file into a
3581 translation file (a .pot file), usable with the normal gettext based
3582 translation tools used by those translating free software. The pot
3583 file is used to create and maintain translation files (several .po
3584 files), which the translations update with the native language
3585 translations of all titles, paragraphs and blocks of text in the
3586 original. The next step is combining the original English Docbook XML
3587 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3588 create a translated Docbook XML file (in this case
3589 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3590 translated, if the translation is not complete) Docbook XML file can
3591 then be used like the original to create a PDF, HTML and epub version
3592 of the documentation.
</p
>
3594 <p
>The translators use different tools to edit the .po files. We
3596 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3597 while some use emacs and vi, others can use web based editors like
3598 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3599 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3600 is where the .po file end up, in our git repository. Updated
3601 translations can either be committed directly to git, or submitted as
3602 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3603 against the debian-edu-doc package
</a
>.
</p
>
3605 <p
>One challenge is images, which both might need to be translated (if
3606 they show translated user applications), and are needed in different
3607 formats when creating PDF and HTML versions (epub is a HTML version in
3608 this regard). For this we transform the original PNG images to the
3609 needed density and format during build, and have a way to provide
3610 translated images by storing translated versions in
3611 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3612 package maintainers know more.
</p
>
3614 <p
>If you wonder what the result look like, we provide
3615 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3616 of the documentation packages on the web
</a
>. See for example the
3617 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3618 PDF version
</a
> or the
3619 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3620 HTML version
</a
>. We do not yet build the epub version by default,
3621 but perhaps it will be done in the future.
</p
>
3623 <p
>To learn more, check out
3624 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3625 debian-edu-doc package
</a
>,
3626 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3627 manual on the wiki
</a
> and
3628 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3629 translation instructions
</a
> in the manual.
</p
>
3634 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3635 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3636 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3637 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3638 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3639 related packages relevant for the computer installed automatically.
3640 So I implemented one, using
3641 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3642 package
</a
>. To use it, install the tasksel and isenkram packages and
3643 run tasksel as user root. You should be presented with a new option,
3644 "Hardware specific packages (autodetected by isenkram)
". When you
3645 select it, tasksel will install the packages isenkram claim is fit for
3646 the current hardware, hot pluggable or not.
<p
>
3648 <p
>The implementation is in two files, one is the tasksel menu entry
3649 description, and the other is the script used to extract the list of
3650 packages to install. The first part is in
3651 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3654 <p
><blockquote
><pre
>
3657 Description: Hardware specific packages (autodetected by isenkram)
3658 Based on the detected hardware various hardware specific packages are
3660 Test-new-install: mark show
3662 Packages: for-current-hardware
3663 </pre
></blockquote
></p
>
3665 <p
>The second part is in
3666 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3669 <p
><blockquote
><pre
>
3674 isenkram-autoinstall-firmware -l
3676 </pre
></blockquote
></p
>
3678 <p
>All in all, a very short and simple implementation making it
3679 trivial to install the hardware dependent package we all may want to
3680 have installed on our machines. I
've not been able to find a way to
3681 get tasksel to tell you exactly which packages it plan to install
3682 before doing the installation. So if you are curious or careful,
3683 check the output from the isenkram-* command line tools first.
</p
>
3685 <p
>The information about which packages are handling which hardware is
3686 fetched either from the isenkram package itself in
3687 /usr/share/isenkram/, from git.debian.org or from the APT package
3688 database (using the Modaliases header). The APT package database
3689 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3690 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3691 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3692 the python-apt code (bug
3693 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3694 workaround I was able to get rid of the file descriptor leak and
3695 reduce the memory leak from ~
30 MiB per hardware detection down to
3696 around
2 MiB per hardware detection. It should make the desktop
3697 daemon a lot more useful. The fix is in version
0.7 uploaded to
3698 unstable today.
</p
>
3700 <p
>I believe the current way of mapping hardware to packages in
3701 Isenkram is is a good draft, but in the future I expect isenkram to
3702 use the AppStream data source for this. A proposal for getting proper
3703 AppStream support into Debian is floating around as
3704 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3705 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3706 project
</a
> will take place this summer to improve the situation. I
3707 look forward to seeing the result, and welcome patches for isenkram to
3708 start using the information when it is ready.
</p
>
3710 <p
>If you want your package to map to some specific hardware, either
3711 add a
"Xb-Modaliases
" header to your control file like I did in
3712 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3713 package
</a
> or submit a bug report with the details to the isenkram
3715 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3716 blog posts tagged isenkram
</a
> for details on the notation. I expect
3717 the information will be migrated to AppStream eventually, but for the
3718 moment I got no better place to store it.
</p
>
3723 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3724 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3725 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3726 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3727 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3728 project
</a
> is working on providing the software and hardware to make
3729 it easy for non-technical people to host their data and communication
3730 at home, and being able to communicate with their friends and family
3731 encrypted and away from prying eyes. It is still going strong, and
3732 today a major mile stone was reached.
</p
>
3734 <p
>Today, the last of the packages currently used by the project to
3735 created the system images were accepted into Debian Unstable. It was
3736 the freedombox-setup package, which is used to configure the images
3737 during build and on the first boot. Now all one need to get going is
3738 the build code from the freedom-maker git repository and packages from
3739 Debian. And once the freedombox-setup package enter testing, we can
3740 build everything directly from Debian. :)
</p
>
3742 <p
>Some key packages used by Freedombox are
3743 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3744 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3745 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3746 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3747 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3748 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3749 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3750 are plans to integrate more packages into the setup. User
3751 documentation is maintained on the Debian wiki. Please
3752 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3753 the manual
</a
> and help us improve it.
</p
>
3755 <p
>To test for yourself and create boot images with the FreedomBox
3756 setup, run this on a Debian machine using a user with sudo rights to
3757 become root:
</p
>
3759 <p
><pre
>
3760 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3761 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3763 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3765 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3766 </pre
></p
>
3768 <p
>Root access is needed to run debootstrap and mount loopback
3769 devices. See the README in the freedom-maker git repo for more
3770 details on the build. If you do not want all three images, trim the
3771 make line. Note that the virtualbox-image target is not really
3772 virtualbox specific. It create a x86 image usable in kvm, qemu,
3773 vmware and any other x86 virtual machine environment. You might need
3774 the version of vmdebootstrap in Jessie to get the build working, as it
3775 include fixes for a race condition with kpartx.
</p
>
3777 <p
>If you instead want to install using a Debian CD and the preseed
3778 method, boot a Debian Wheezy ISO and use this boot argument to load
3779 the preseed values:
</p
>
3781 <p
><pre
>
3782 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3783 </pre
></p
>
3785 <p
>I have not tested it myself the last few weeks, so I do not know if
3786 it still work.
</p
>
3788 <p
>If you wonder how to help, one task you could look at is using
3789 systemd as the boot system. It will become the default for Linux in
3790 Jessie, so we need to make sure it is usable on the Freedombox. I did
3791 a simple test a few weeks ago, and noticed dnsmasq failed to start
3792 during boot when using systemd. I suspect there are other problems
3793 too. :) To detect problems, there is a test suite included, which can
3794 be run from the plinth web interface.
</p
>
3796 <p
>Give it a go and let us know how it goes on the mailing list, and help
3797 us get the new release published. :) Please join us on
3798 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3799 irc.debian.org)
</a
> and
3800 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3801 mailing list
</a
> if you want to help make this vision come true.
</p
>
3806 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3807 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3808 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3809 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3810 <description><p
>For a while now, I have been looking for a sensible offsite backup
3811 solution for use at home. My requirements are simple, it must be
3812 cheap and locally encrypted (in other words, I keep the encryption
3813 keys, the storage provider do not have access to my private files).
3814 One idea me and my friends had many years ago, before the cloud
3815 storage providers showed up, was to use Google mail as storage,
3816 writing a Linux block device storing blocks as emails in the mail
3817 service provided by Google, and thus get heaps of free space. On top
3818 of this one can add encryption, RAID and volume management to have
3819 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3820 I never found time to implement such system. But the last few weeks I
3821 have looked at a system called
3822 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3823 mounted network backed file system with the features I need.
</p
>
3825 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3826 handling several different storage providers, any with Amazon S3,
3827 Google Drive or OpenStack API. There are heaps of such storage
3828 providers. S3QL can also use a local directory as storage, which
3829 combined with sshfs allow for file storage on any ssh server. S3QL
3830 include support for encryption, compression, de-duplication, snapshots
3831 and immutable file systems, allowing me to mount the remote storage as
3832 a local mount point, look at and use the files as if they were local,
3833 while the content is stored in the cloud as well. This allow me to
3834 have a backup that should survive fire. The file system can not be
3835 shared between several machines at the same time, as only one can
3836 mount it at the time, but any machine with the encryption key and
3837 access to the storage service can mount it if it is unmounted.
</p
>
3839 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3840 package is included already. So to get started, run
<tt
>apt-get
3841 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3842 Greenqloud, after reading their nice recipe on
3843 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3844 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3845 in Iceland more than those in USA when it come to keeping my personal
3846 data safe and private, and thus would rather spend money on a company
3847 in Iceland. Another nice recipe is available from the article
3848 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3849 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3850 Admin magazine. When the provider is picked, figure out how to get
3851 the API key needed to connect to the storage API. With Greencloud,
3852 the key did not show up until I had added payment details to my
3855 <p
>Armed with the API access details, it is time to create the file
3856 system. First, create a new bucket in the cloud. This bucket is the
3857 file system storage area. I picked a bucket name reflecting the
3858 machine that was going to store data there, but any name will do.
3859 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3860 the API login and password, and a locally created password. Store it
3861 all in ~root/.s3ql/authinfo2 like this:
3863 <p
><blockquote
><pre
>
3865 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3866 backend-login: API-login
3867 backend-password: API-password
3868 fs-passphrase: local-password
3869 </pre
></blockquote
></p
>
3871 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3872 but any sensible way to create a fairly random password should do it.
3873 Armed with these details, it is now time to run mkfs, entering the API
3874 details and password to create it:
</p
>
3876 <p
><blockquote
><pre
>
3877 # mkdir -m
700 /var/lib/s3ql-cache
3878 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3879 --ssl s3c://s.greenqloud.com:
443/bucket-name
3880 Enter backend login:
3881 Enter backend password:
3882 Before using S3QL, make sure to read the user
's guide, especially
3883 the
'Important Rules to Avoid Loosing Data
' section.
3884 Enter encryption password:
3885 Confirm encryption password:
3886 Generating random encryption key...
3887 Creating metadata tables...
3897 Compressing and uploading metadata...
3898 Wrote
0.00 MB of compressed metadata.
3899 #
</pre
></blockquote
></p
>
3901 <p
>The next step is mounting the file system to make the storage available.
3903 <p
><blockquote
><pre
>
3904 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3905 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3906 Using
4 upload threads.
3907 Downloading and decompressing metadata...
3917 Mounting filesystem...
3919 Filesystem Size Used Avail Use% Mounted on
3920 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3922 </pre
></blockquote
></p
>
3924 <p
>The file system is now ready for use. I use rsync to store my
3925 backups in it, and as the metadata used by rsync is downloaded at
3926 mount time, no network traffic (and storage cost) is triggered by
3927 running rsync. To unmount, one should not use the normal umount
3928 command, as this will not flush the cache to the cloud storage, but
3929 instead running the umount.s3ql command like this:
3931 <p
><blockquote
><pre
>
3934 </pre
></blockquote
></p
>
3936 <p
>There is a fsck command available to check the file system and
3937 correct any problems detected. This can be used if the local server
3938 crashes while the file system is mounted, to reset the
"already
3939 mounted
" flag. This is what it look like when processing a working
3940 file system:
</p
>
3942 <p
><blockquote
><pre
>
3943 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3944 Using cached metadata.
3945 File system seems clean, checking anyway.
3946 Checking DB integrity...
3947 Creating temporary extra indices...
3948 Checking lost+found...
3949 Checking cached objects...
3950 Checking names (refcounts)...
3951 Checking contents (names)...
3952 Checking contents (inodes)...
3953 Checking contents (parent inodes)...
3954 Checking objects (reference counts)...
3955 Checking objects (backend)...
3956 ..processed
5000 objects so far..
3957 ..processed
10000 objects so far..
3958 ..processed
15000 objects so far..
3959 Checking objects (sizes)...
3960 Checking blocks (referenced objects)...
3961 Checking blocks (refcounts)...
3962 Checking inode-block mapping (blocks)...
3963 Checking inode-block mapping (inodes)...
3964 Checking inodes (refcounts)...
3965 Checking inodes (sizes)...
3966 Checking extended attributes (names)...
3967 Checking extended attributes (inodes)...
3968 Checking symlinks (inodes)...
3969 Checking directory reachability...
3970 Checking unix conventions...
3971 Checking referential integrity...
3972 Dropping temporary indices...
3973 Backing up old metadata...
3983 Compressing and uploading metadata...
3984 Wrote
0.89 MB of compressed metadata.
3986 </pre
></blockquote
></p
>
3988 <p
>Thanks to the cache, working on files that fit in the cache is very
3989 quick, about the same speed as local file access. Uploading large
3990 amount of data is to me limited by the bandwidth out of and into my
3991 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3992 which is very close to my upload speed, and downloading the same
3993 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3994 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3995 network, not the file system code. I do not know what a good cache
3996 size would be, but suspect that the cache should e larger than your
3997 working set.
</p
>
3999 <p
>I mentioned that only one machine can mount the file system at the
4000 time. If another machine try, it is told that the file system is
4003 <p
><blockquote
><pre
>
4004 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
4005 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
4006 Using
8 upload threads.
4007 Backend reports that fs is still mounted elsewhere, aborting.
4009 </pre
></blockquote
></p
>
4011 <p
>The file content is uploaded when the cache is full, while the
4012 metadata is uploaded once every
24 hour by default. To ensure the
4013 file system content is flushed to the cloud, one can either umount the
4014 file system, or ask S3QL to flush the cache and metadata using
4017 <p
><blockquote
><pre
>
4018 # s3qlctrl upload-meta /s3ql
4019 # s3qlctrl flushcache /s3ql
4021 </pre
></blockquote
></p
>
4023 <p
>If you are curious about how much space your data uses in the
4024 cloud, and how much compression and deduplication cut down on the
4025 storage usage, you can use s3qlstat on the mounted file system to get
4028 <p
><blockquote
><pre
>
4030 Directory entries:
9141
4033 Total data size:
22049.38 MB
4034 After de-duplication:
21955.46 MB (
99.57% of total)
4035 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4036 Database size:
2.39 MB (uncompressed)
4037 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4039 </pre
></blockquote
></p
>
4041 <p
>I mentioned earlier that there are several possible suppliers of
4042 storage. I did not try to locate them all, but am aware of at least
4043 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4044 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4045 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4046 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4047 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4048 accept payment in Bitcoin. Pick one that suit your need. Some of
4049 them provide several GiB of free storage, but the prize models are
4050 quite different and you will have to figure out what suits you
4053 <p
>While researching this blog post, I had a look at research papers
4054 and posters discussing the S3QL file system. There are several, which
4055 told me that the file system is getting a critical check by the
4056 science community and increased my confidence in using it. One nice
4058 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4059 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4060 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4061 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4062 and Pamela Smith. Please have a look.
</p
>
4064 <p
>Given my problems with different file systems earlier, I decided to
4065 check out the mounted S3QL file system to see if it would be usable as
4066 a home directory (in other word, that it provided POSIX semantics when
4067 it come to locking and umask handling etc). Running
4068 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4069 test code to check file system semantics
</a
>, I was happy to discover that
4070 no error was found. So the file system can be used for home
4071 directories, if one chooses to do so.
</p
>
4073 <p
>If you do not want a locally file system, and want something that
4074 work without the Linux fuse file system, I would like to mention the
4075 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4076 provide locally encrypted backup using a command line client. It have
4077 a nicer access control system, where one can split out read and write
4078 access, allowing some systems to write to the backup and others to
4079 only read from it.
</p
>
4081 <p
>As usual, if you use Bitcoin and want to show your support of my
4082 activities, please send Bitcoin donations to my address
4083 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4088 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4089 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4090 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4091 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4092 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4093 project
</a
> is working on providing the software and hardware for
4094 making it easy for non-technical people to host their data and
4095 communication at home, and being able to communicate with their
4096 friends and family encrypted and away from prying eyes. It has been
4097 going on for a while, and is slowly progressing towards a new test
4098 release (
0.2).
</p
>
4100 <p
>And what day could be better than the Pi day to announce that the
4101 new version will provide
"hard drive
" / SD card / USB stick images for
4102 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4103 system), and can also be installed using a Debian installer preseed
4104 file. The Debian based Freedombox is now based on Debian Jessie,
4105 where most of the needed packages used are already present. Only one,
4106 the freedombox-setup package, is missing. To try to build your own
4107 boot image to test the current status, fetch the freedom-maker scripts
4109 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4110 with a user with sudo access to become root:
4113 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4115 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4116 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4118 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4121 <p
>Root access is needed to run debootstrap and mount loopback
4122 devices. See the README for more details on the build. If you do not
4123 want all three images, trim the make line. But note that thanks to
<a
4124 href=
"https://bugs.debian.org/
741407">a race condition in
4125 vmdebootstrap
</a
>, the build might fail without the patch to the
4126 kpartx call.
</p
>
4128 <p
>If you instead want to install using a Debian CD and the preseed
4129 method, boot a Debian Wheezy ISO and use this boot argument to load
4130 the preseed values:
</p
>
4133 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4136 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4137 recently introduced bug in apt in Jessie
</a
>, the installer will
4138 currently hang while setting up APT sources. Killing the
4139 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4140 installation will get the installation going. This affect all
4141 installations in Jessie, and I expect it will be fixed soon.
</p
>
4143 <p
>Give it a go and let us know how it goes on the mailing list, and help
4144 us get the new release published. :) Please join us on
4145 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4146 irc.debian.org)
</a
> and
4147 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4148 mailing list
</a
> if you want to help make this vision come true.
</p
>
4153 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4154 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4155 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4156 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4157 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4158 innetgr tools, because I needed them in
4159 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4160 ng-utils, and it has served me well. I placed the project under the
4161 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4162 repository. But many years ago, the CVS repository was dropped (lost,
4163 not migrated to new hardware, not sure), and the project have lacked a
4164 proper home since then.
</p
>
4166 <p
>Last summer, I had a look at the package and made a new release
4167 fixing a irritating crash bug, but was unable to store the changes in
4168 a proper source control system. I applied for a project on
4169 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4170 to follow up on it. Until today. :)
</p
>
4172 <p
>After many hours of cleaning and migration, the ng-utils project
4173 now have a new home, and a git repository with the highlight of the
4174 history of the project. I published all release tarballs and imported
4175 them into the git repository. As the project is really stable and not
4176 expected to gain new features any time soon, I decided to make a new
4177 release and call it
1.0. Visit the new project home on
4178 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4179 if you want to check it out. The new version is also uploaded into
4180 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4185 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4186 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4187 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4188 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4189 <description><p
>A few days ago I decided to try to help the Hurd people to get
4190 their changes into sysvinit, to allow them to use the normal sysvinit
4191 boot system instead of their old one. This follow up on the
4192 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4193 Google Summer of Code work
</a
> done last summer by Justus Winter to
4194 get Debian on Hurd working more like Debian on Linux. To get started,
4195 I downloaded a prebuilt hard disk image from
4196 <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
>,
4197 and started it using virt-manager.
</p
>
4199 <p
>The first think I had to do after logging in (root without any
4200 password) was to get the network operational. I followed
4201 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4202 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4203 commands as root to get the machine to accept a IP address from the
4204 kvm internal DHCP server:
</p
>
4206 <p
><blockquote
><pre
>
4207 settrans -fgap /dev/netdde /hurd/netdde
4208 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4209 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4211 </pre
></blockquote
></p
>
4213 <p
>After this, the machine had internet connectivity, and I could
4214 upgrade it and install the sysvinit packages from experimental and
4215 enable it as the default boot system in Hurd.
</p
>
4217 <p
>But before I did that, I set a password on the root user, as ssh is
4218 running on the machine it for ssh login to work a password need to be
4219 set. Also, note that a bug somewhere in openssh on Hurd block
4220 compression from working. Remember to turn that off on the client
4223 <p
>Run these commands as root to upgrade and test the new sysvinit
4226 <p
><blockquote
><pre
>
4227 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4228 deb http://http.debian.net/debian/ experimental main
4231 apt-get dist-upgrade
4232 apt-get install -t experimental initscripts sysv-rc sysvinit \
4233 sysvinit-core sysvinit-utils
4234 update-alternatives --config runsystem
4235 </pre
></blockquote
></p
>
4237 <p
>To reboot after switching boot system, you have to use
4238 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4239 yet a sysvinit process able to receive the signals from the normal
4240 'reboot
' command. After switching to sysvinit as the boot system,
4241 upgrading every package and rebooting, the network come up with DHCP
4242 after boot as it should, and the settrans/pkill hack mentioned at the
4243 start is no longer needed. But for some strange reason, there are no
4244 longer any login prompt in the virtual console, so I logged in using
4247 <p
>Note that there are some race conditions in Hurd making the boot
4248 fail some times. No idea what the cause is, but hope the Hurd porters
4249 figure it out. At least Justus said on IRC (#debian-hurd on
4250 irc.debian.org) that they are aware of the problem. A way to reduce
4251 the impact is to upgrade to the Hurd packages built by Justus by
4252 adding this repository to the machine:
</p
>
4254 <p
><blockquote
><pre
>
4255 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4256 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4258 </pre
></blockquote
></p
>
4260 <p
>At the moment the prebuilt virtual machine get some packages from
4261 http://ftp.debian-ports.org/debian, because some of the packages in
4262 unstable do not yet include the required patches that are lingering in
4263 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4265 <p
><blockquote
><pre
>
4266 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4267 i emacs - GNU Emacs editor (metapackage)
4268 i gdb - GNU Debugger
4269 i hurd-recommended - Miscellaneous translators
4270 i isc-dhcp-client - ISC DHCP client
4271 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4272 i libc-bin - Embedded GNU C Library: Binaries
4273 i libc-dev-bin - Embedded GNU C Library: Development binaries
4274 i libc0.3 - Embedded GNU C Library: Shared libraries
4275 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4276 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4277 i multiarch-support - Transitional package to ensure multiarch compatibilit
4278 i A x11-common - X Window System (X.Org) infrastructure
4279 i xorg - X.Org X Window System
4280 i A xserver-xorg - X.Org X server
4281 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4283 </pre
></blockquote
></p
>
4285 <p
>All in all, testing hurd has been an interesting experience. :)
4286 X.org did not work out of the box and I never took the time to follow
4287 the porters instructions to fix it. This time I was interested in the
4288 command line stuff.
<p
>
4293 <title>New chrpath release
0.16</title>
4294 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4295 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4296 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4297 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4298 find problems in C, C++ and Java code using static source code
4299 analysis. It can detect a lot of different problems, and is very
4300 useful to find memory and locking bugs in the error handling part of
4301 the source. The company behind it provide
4302 <a href=
"https://scan.coverity.com/
">check of free software projects as
4303 a community service
</a
>, and many hundred free software projects are
4304 already checked. A few days ago I decided to have a closer look at
4305 the Coverity system, and discovered that the
4306 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4307 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4308 projects I am involved with was already registered. But these are
4309 fairly big, and I would also like to have a small and easy project to
4310 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4311 checking of the chrpath project
</a
>. It was
4312 added to the checker and discovered seven potential defects. Six of
4313 these were real, mostly resource
"leak
" when the program detected an
4314 error. Nothing serious, as the resources would be released a fraction
4315 of a second later when the program exited because of the error, but it
4316 is nice to do it right in case the source of the program some time in
4317 the future end up in a library. Having fixed all defects and added
4318 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4319 mailing list for the chrpath developers
</a
>, I decided it was time to
4320 publish a new release. These are the release notes:
</p
>
4322 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4326 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4327 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4328 <li
>Mention new project mailing list in the documentation.
</li
>
4333 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4334 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4335 project if something is wrong with the new release. The test suite
4336 did not discover any old errors, so if you find a new one, please also
4337 include a test suite check.
</p
>
4342 <title>New chrpath release
0.15</title>
4343 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4344 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4345 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4346 <description><p
>After many years break from the package and a vain hope that
4347 development would be continued by someone else, I finally pulled my
4348 acts together this morning and wrapped up a new release of chrpath,
4349 the command line tool to modify the rpath and runpath of already
4350 compiled ELF programs. The update was triggered by the persistence of
4351 Isha Vishnoi at IBM, which needed a new config.guess file to get
4352 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4353 is working on. I checked the
4354 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4355 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4356 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4357 packages for interesting patches (failed to find the source from
4358 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4359 These are the release notes:
</p
>
4361 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4365 <li
>Updated config.sub and config.guess from the GNU project to work
4366 with newer architectures. Thanks to isha vishnoi for the heads
4369 <li
>Updated README with current URLs.
</li
>
4371 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4372 Matthias Klose.
</li
>
4374 <li
>Added missing help for -k|--keepgoing option, using patch by
4375 Petr Machata found in Fedora.
</li
>
4377 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4378 .dynamic is a NULL terminated string. Based on patch found in
4379 Fedora credited Axel Thimm and Christian Krause.
</li
>
4384 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4385 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4386 project if something is wrong with the new release. The test suite
4387 did not discover any old errors, so if you find a new one, please also
4388 include a testsuite check.
</p
>
4393 <title>Debian init.d boot script example for rsyslog
</title>
4394 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4395 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4396 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4397 <description><p
>If one of the points of switching to a new init system in Debian is
4398 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4399 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4400 init.d scripts at all. Here is an example init.d script, ie a rewrite
4401 of /etc/init.d/rsyslog:
</p
>
4403 <p
><pre
>
4404 #!/lib/init/init-d-script
4407 # Required-Start: $remote_fs $time
4408 # Required-Stop: umountnfs $time
4409 # X-Stop-After: sendsigs
4410 # Default-Start:
2 3 4 5
4411 # Default-Stop:
0 1 6
4412 # Short-Description: enhanced syslogd
4413 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4414 # It is quite compatible to stock sysklogd and can be
4415 # used as a drop-in replacement.
4417 DESC=
"enhanced syslogd
"
4418 DAEMON=/usr/sbin/rsyslogd
4419 </pre
></p
>
4421 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4422 script was
137 lines, and the above is just
15 lines, most of it meta
4423 info/comments.
</p
>
4425 <p
>How to do this, you ask? Well, one create a new script
4426 /lib/init/init-d-script looking something like this:
4428 <p
><pre
>
4431 # Define LSB log_* functions.
4432 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4433 # and status_of_proc is working.
4434 . /lib/lsb/init-functions
4437 # Function that starts the daemon/service
4443 #
0 if daemon has been started
4444 #
1 if daemon was already running
4445 #
2 if daemon could not be started
4446 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4448 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4451 # Add code here, if necessary, that waits for the process to be ready
4452 # to handle requests from services started subsequently which depend
4453 # on this one. As a last resort, sleep for some time.
4457 # Function that stops the daemon/service
4462 #
0 if daemon has been stopped
4463 #
1 if daemon was already stopped
4464 #
2 if daemon could not be stopped
4465 # other if a failure occurred
4466 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4467 RETVAL=
"$?
"
4468 [
"$RETVAL
" =
2 ]
&& return
2
4469 # Wait for children to finish too if this is a daemon that forks
4470 # and if the daemon is only ever run from this initscript.
4471 # If the above conditions are not satisfied then add some other code
4472 # that waits for the process to drop all resources that could be
4473 # needed by services started subsequently. A last resort is to
4474 # sleep for some time.
4475 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4476 [
"$?
" =
2 ]
&& return
2
4477 # Many daemons don
't delete their pidfiles when they exit.
4479 return
"$RETVAL
"
4483 # Function that sends a SIGHUP to the daemon/service
4487 # If the daemon can reload its configuration without
4488 # restarting (for example, when it is sent a SIGHUP),
4489 # then implement that here.
4491 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4496 scriptbasename=
"$(basename $
1)
"
4497 echo
"SN: $scriptbasename
"
4498 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4499 script=
"$
1"
4506 NAME=$(basename $DAEMON)
4507 PIDFILE=/var/run/$NAME.pid
4509 # Exit if the package is not installed
4510 #[ -x
"$DAEMON
" ] || exit
0
4512 # Read configuration variable file if it is present
4513 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4515 # Load the VERBOSE setting and other rcS variables
4518 case
"$
1" in
4520 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4522 case
"$?
" in
4523 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4524 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4528 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4530 case
"$?
" in
4531 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4532 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4536 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4538 #reload|force-reload)
4540 # If do_reload() is not implemented then leave this commented out
4541 # and leave
'force-reload
' as an alias for
'restart
'.
4543 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4547 restart|force-reload)
4549 # If the
"reload
" option is implemented then remove the
4550 #
'force-reload
' alias
4552 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4554 case
"$?
" in
4557 case
"$?
" in
4559 1) log_end_msg
1 ;; # Old process is still running
4560 *) log_end_msg
1 ;; # Failed to start
4570 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4576 </pre
></p
>
4578 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4579 lot. I did not really polish the approach, so it might not always
4580 work out of the box, but you get the idea. I did not try very hard to
4581 optimize it nor make it more robust either.
</p
>
4583 <p
>A better argument for switching init system in Debian than reducing
4584 the size of init scripts (which is a good thing to do anyway), is to
4585 get boot system that is able to handle the kernel events sensibly and
4586 robustly, and do not depend on the boot to run sequentially. The boot
4587 and the kernel have not behaved sequentially in years.
</p
>
4592 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4593 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4594 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4595 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4596 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4597 remote display access is the preferred solution with oVirt and RedHat
4598 Enterprise Virtualization, and I was sad to discover the other day
4599 that the browser plugin needed to use these systems seamlessly was
4600 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4601 for a package
</a
> was from
2012-
04-
10 with no progress since
4602 2013-
04-
01, so I decided to wrap up a package based on the great work
4603 from Cajus Pollmeier and put it in a collab-maint maintained git
4604 repository to get a package I could use. I would very much like
4605 others to help me maintain the package (or just take over, I do not
4606 mind), but as no-one had volunteered so far, I just uploaded it to
4607 NEW. I hope it will be available in Debian in a few days.
</p
>
4609 <p
>The source is now available from
4610 <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
>
4615 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4616 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4618 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4619 <description><p
>The
4620 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4621 program is a a very nice system to create virtual machine images. It
4622 create a image file, add a partition table, mount it and run
4623 debootstrap in the mounted directory to create a Debian system on a
4624 stick. Yesterday, I decided to try to teach it how to make images for
4625 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4626 of a plan to simplify the build system for
4627 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4628 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4629 the virtualbox images, but its current build system made multistrap
4630 based system for Dreamplug images, and it is lacking support for
4631 Raspberry Pi.
</p
>
4633 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4634 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4635 code and adjusted it to be able to build armel images on my amd64
4636 Debian laptop. I ended up giving vmdebootstrap five new options,
4637 allowing me to replicate the image creation process I use to make
4638 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4639 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4640 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4641 call debootstrap with --foreign and to copy the handler into the
4642 generated chroot before running the second stage. This allow
4643 vmdebootstrap to create armel images on an amd64 host. Next I added
4644 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4645 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4646 given file system type, allowing me to create an image with a vfat
4647 partition for the /boot/ stuff. I also added a
<tt
>--variant
4648 variant
</tt
> option to allow me to create smaller images without the
4649 Debian base system packages installed. Finally, I added an option
4650 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4651 as a boot loader. It is not needed on the Raspberry Pi and probably
4652 most other non-x86 architectures. The changes were accepted by the
4653 upstream author of vmdebootstrap yesterday and today, and is now
4655 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4656 upstream project page
</a
>.
</p
>
4658 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4659 create a small script (the customize script) to add the non-free
4660 binary blob needed to boot the Raspberry Pi and the APT source
4663 <p
><pre
>
4665 set -e # Exit on first error
4666 rootdir=
"$
1"
4667 cd
"$rootdir
"
4668 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4669 deb http://http.debian.net/debian/ jessie main contrib non-free
4671 # Install non-free binary blob needed to boot Raspberry Pi. This
4672 # install a kernel somewhere too.
4673 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4674 -O $rootdir/usr/bin/rpi-update
4675 chmod a+x $rootdir/usr/bin/rpi-update
4676 mkdir -p $rootdir/lib/modules
4677 touch $rootdir/boot/start.elf
4678 chroot $rootdir rpi-update
4679 </pre
></p
>
4681 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4682 to build the image:
</p
>
4685 sudo ./vmdebootstrap \
4688 --distribution jessie \
4689 --mirror http://http.debian.net/debian \
4698 --root-password raspberry \
4699 --hostname raspberrypi \
4700 --foreign /usr/bin/qemu-arm-static \
4701 --customize `pwd`/customize \
4703 --package git-core \
4704 --package binutils \
4705 --package ca-certificates \
4708 </pre
></p
>
4710 <p
>The list of packages being installed are the ones needed by
4711 rpi-update to make the image bootable on the Raspberry Pi, with the
4712 exception of netbase, which is needed by debootstrap to find
4713 /etc/hosts with the minbase variant. I really wish there was a way to
4714 set up an Raspberry Pi using only packages in the Debian archive, but
4715 that is not possible as far as I know, because it boots from the GPU
4716 using a non-free binary blob.
</p
>
4718 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4719 probably a few others installed. I have not checked the complete
4720 build dependency list.
</p
>
4722 <p
>The resulting image will not use the hardware floating point unit
4723 on the Raspberry PI, because the armel architecture in Debian is not
4724 optimized for that use. So the images created will be a bit slower
4725 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4730 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4731 <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>
4732 <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>
4733 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4734 <description><p
>The last few days I came across a few good causes that should get
4735 wider attention. I recommend signing and donating to each one of
4738 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4739 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4740 Women program which is a Google Summer of Code like initiative to get
4741 more women involved in free software. One debian sponsor has offered
4742 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4743 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4744 hope you will to. :)
</p
>
4746 <p
>And the Electronic Frontier Foundation just announced plans to
4747 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4748 documentaries about the excessive spying
</a
> on every Internet user that
4749 take place these days, and their need to fund the work. I
've already
4750 donated. Are you next?
</p
>
4752 <p
>For my Norwegian audience, the organisation Studentenes og
4753 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4754 statement under the heading
4755 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4756 Access
</a
> for those of us asking for more focus on open access in the
4757 Norwegian government. So far
499 signatures. I hope you will sign it
4763 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4764 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4765 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4766 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4767 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4768 project
</a
> have been going on for a while, and have presented the
4769 vision, ideas and solution several places. Here is a little
4770 collection of videos of talks and presentation of the project.
</p
>
4774 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4775 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4777 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4778 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4780 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4781 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4782 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4783 (Youtube)
</li
>
4785 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4786 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4788 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4789 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4791 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4792 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4793 York City in
2012</a
> (Youtube)
</li
>
4795 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4796 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4797 (Youtube)
</li
>
4799 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4800 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4802 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4803 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4805 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4806 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4807 2013</a
> (Youtube)
</li
>
4811 <p
>A larger list is available from
4812 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4813 Freedombox Wiki
</a
>.
</p
>
4815 <p
>On other news, I am happy to report that Freedombox based on Debian
4816 Jessie is coming along quite well, and soon both Owncloud and using
4817 Tor should be available for testers of the Freedombox solution. :) In
4818 a few weeks I hope everything needed to test it is included in Debian.
4819 The withsqlite package is already in Debian, and the plinth package is
4820 pending in NEW. The third and vital part of that puzzle is the
4821 metapackage/setup framework, which is still pending an upload. Join
4822 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4823 (#freedombox on irc.debian.org)
</a
> and
4824 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4825 mailing list
</a
> if you want to help make this vision come true.
</p
>
4830 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4831 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4832 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4833 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4834 <description><p
>I was introduced to the
4835 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4836 in
2010, when Eben Moglen presented his vision about serving the need
4837 of non-technical people to keep their personal information private and
4838 within the legal protection of their own homes. The idea is to give
4839 people back the power over their network and machines, and return
4840 Internet back to its intended peer-to-peer architecture. Instead of
4841 depending on a central service, the Freedombox will give everyone
4842 control over their own basic infrastructure.
</p
>
4844 <p
>I
've intended to join the effort since then, but other tasks have
4845 taken priority. But this summers nasty news about the misuse of trust
4846 and privilege exercised by the
"western
" intelligence gathering
4847 communities increased my eagerness to contribute to a point where I
4848 actually started working on the project a while back.
</p
>
4850 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4851 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4852 create a simple and cheap Debian based appliance that anyone can hook
4853 up in their home and get access to secure and private services and
4854 communication. The initial deployment platform have been the
4855 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4856 which is a piece of hardware I do not own. So to be able to test what
4857 the current Freedombox setup look like, I had to come up with a way to install
4858 it on some hardware I do have access to. I have rewritten the
4859 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4860 image build framework to use .deb packages instead of only copying
4861 setup into the boot images, and thanks to this rewrite I am able to
4862 set up any machine supported by Debian Wheezy as a Freedombox, using
4863 the previously mentioned deb (and a few support debs for packages
4864 missing in Debian).
</p
>
4866 <p
>The current Freedombox setup consist of a set of bootstrapping
4868 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4869 and a administrative web interface
4870 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4871 withsqlite), as well as a privacy enhancing proxy based on
4872 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4873 (freedombox-privoxy). There is also a web/javascript based XMPP
4874 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4875 trying (unsuccessfully so far) to talk to the XMPP server
4876 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4877 web interface is pluggable, and the goal is to use it to enable OpenID
4878 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4879 this is really working yet, see
4880 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4881 project TODO
</a
> for links to GIT repositories. Most of the code is
4882 on github at the moment. The HTTP proxy is operational out of the
4883 box, and the admin web interface can be used to add/remove plinth
4884 users. I
've not been able to do anything else with it so far, but
4885 know there are several branches spread around github and other places
4886 with lots of half baked features.
</p
>
4888 <p
>Anyway, if you want to have a look at the current state, the
4889 following recipes should work to give you a test machine to poke
4892 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4896 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4897 <li
>Boot from it, either as CD or USB stick.
</li
>
4898 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4899 to the Debian installer:
<p
>
4900 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4902 <li
>Answer the few language/region/password questions and pick disk to
4903 install on.
</li
>
4905 <li
>When the installation is finished and the machine have rebooted a
4906 few times, your Freedombox is ready for testing.
</li
>
4910 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4914 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4915 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4916 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4918 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4919 </pre
></li
>
4920 <li
><p
>Run this as root:
</p
>
4922 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4925 apt-get install freedombox-setup
4926 /usr/lib/freedombox/setup
4927 </pre
></li
>
4928 <li
>Reboot into your freshly created Freedombox.
</li
>
4932 <p
>You can test it on other architectures too, but because the
4933 freedombox-privoxy package is binary, it will only work as intended on
4934 the architectures where I have had time to build the binary and put it
4935 in my APT repository. But do not let this stop you. It is only a
4936 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4938 <p
>Note that by default Freedombox is a DHCP server on the
4939 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4940 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4941 disable
</tt
>" as root.
</p
>
4943 <p
>Please let me know if this works for you, or if you have any
4944 problems. We gather on the IRC channel
4945 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4946 irc.debian.org and the
4947 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4948 mailing list
</a
>.
</p
>
4950 <p
>Once you get your freedombox operational, you can visit
4951 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4952 welcome screen (dead end - do not be surprised if you are unable to
4953 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4954 to look at the rest of plinth. The default user is
'admin
' and the
4955 default password is
'secret
'.
</p
>
4960 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4961 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4962 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4963 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4964 <description><p
>Earlier, I reported about
4965 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4966 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4967 told by IBM that the original disk should be thrown away. And as
4968 there no longer was a problem if I bricked the firmware, I decided
4969 today to try to install Intel firmware to replace the Lenovo firmware
4970 currently on the disk.
</p
>
4972 <p
>I searched the Intel site for firmware, and found
4973 <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
>
4974 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4975 according to the site should contain the latest firmware for SSD
4976 disks. I inserted the broken disk in one of my spare laptops and
4977 booted the ISO from a USB stick. The disk was recognized, but the
4978 program claimed the newest firmware already were installed and refused
4979 to insert any Intel firmware. So no change, and the disk is still
4980 unable to handle write load. :( I guess the only way to get them
4981 working would be if Lenovo releases new firmware. No idea how likely
4982 that is. Anyway, just blogging about this test for completeness. I
4983 got a working Samsung disk, and see no point in spending more time on
4984 the broken disks.
</p
>
4989 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4990 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4991 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4992 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4993 <description><p
>Today I switched to
4994 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4995 new laptop
</a
>. I
've previously written about the problems I had with
4996 my new Thinkpad X230, which was delivered with an
4997 <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
4998 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4999 sustained writes. My hardware supplier have been very forthcoming in
5000 trying to find a solution, and after first trying with another
5001 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
5002 disk instead to fix it once and for all. The Samsung disk survived
5003 the installation of Debian with encrypted disks (filling the disk with
5004 random data during installation killed the first two), and I thus
5005 decided to trust it with my data. I have installed it as a Debian Edu
5006 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
5007 server at home using Kerberos and LDAP, and will use it as my work
5008 station from now on.
</p
>
5010 <p
>As this is a solid state disk with no moving parts, I believe the
5011 Debian Wheezy default installation need to be tuned a bit to increase
5012 performance and increase life time of the disk. The Linux kernel and
5013 user space applications do not yet adjust automatically to such
5014 environment. To make it easier for my self, I created a draft Debian
5015 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
5016 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
5017 for the ssd-setup package
</a
> is available from collab-maint, and it
5018 is set up to adjust the setup of the machine by just installing the
5019 package. If there is any non-SSD disk in the machine, the package
5020 will refuse to install, as I did not try to write any logic to sort
5021 file systems in SSD and non-SSD file systems.
</p
>
5023 <p
>I consider the package a draft, as I am a bit unsure how to best
5024 set up Debian Wheezy with an SSD. It is adjusted to my use case,
5025 where I set up the machine with one large encrypted partition (in
5026 addition to /boot), put LVM on top of this and set up partitions on
5027 top of this again. See the README file in the package source for the
5028 references I used to pick the settings. At the moment these
5029 parameters are tuned:
</p
>
5033 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
5034 (adding discard to /etc/crypttab)
</li
>
5036 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5037 this case a cryptsetup partition) by changing issue_discards from
5038 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5040 <li
>Set relatime as a file system option for ext3 and ext4 file
5043 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5044 /etc/fstab.
</li
>
5046 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5048 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5049 cron.daily).
</li
>
5051 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5052 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5056 <p
>During installation, I cancelled the part where the installer fill
5057 the disk with random data, as this would kill the SSD performance for
5058 little gain. My goal with the encrypted file system is to ensure
5059 those stealing my laptop end up with a brick and not a working
5060 computer. I have no hope in keeping the really resourceful people
5061 from getting the data on the disk (see
5062 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5063 Thus I concluded that adding the discard option to crypttab is the
5064 right thing to do.
</p
>
5066 <p
>I considered using the noop I/O scheduler, as several recommended
5067 it for SSD, but others recommended deadline and a benchmark I found
5068 indicated that deadline might be better for interactive use.
</p
>
5070 <p
>I also considered using the
'discard
' file system option for ext3
5071 and ext4, but read that it would give a performance hit ever time a
5072 file is removed, and thought it best to that that slowdown once a day
5073 instead of during my work.
</p
>
5075 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5076 this is already done by Debian Edu.
</p
>
5078 <p
>I have not yet started on the user space tuning. I expect
5079 iceweasel need some tuning, and perhaps other applications too, but
5080 have not yet had time to investigate those parts.
</p
>
5082 <p
>The package should work on Ubuntu too, but I have not yet tested it
5085 <p
>As for the answer to the question in the title of this blog post,
5086 as far as I know, the only solution I know about is to replace the
5087 disk. It might be possible to flash it with Intel firmware instead of
5088 the Lenovo firmware. But I have not tried and did not want to do so
5089 without approval from Lenovo as I wanted to keep the warranty on the
5090 disk until a solution was found and they wanted the broken disks
5096 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5097 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5098 <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>
5099 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5100 <description><p
>A few days ago, I wrote about
5101 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5102 problems I experienced with my new X230 and its SSD disk
</a
>, which
5103 was dying during installation because it is unable to cope with
5104 sustained write. My supplier is in contact with
5105 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5106 replacement disk to try to fix the problem. They decided to send an
5107 identical model, so my hopes for a permanent fix was slim.
</p
>
5109 <p
>Anyway, today I got the replacement disk and tried to install
5110 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5111 same firmware version as the original. This time my hope raised
5112 slightly as the installation progressed, as the original disk used to
5113 die after
4-
7% of the disk was written to, while this time it kept
5114 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5115 died again and I was back on square one. I still do not have a new
5116 laptop with a disk I can trust. I can not live with a disk that might
5117 lock up when I download a new
5118 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5119 other large files. I look forward to hearing from my supplier with
5120 the next proposal from Lenovo.
</p
>
5122 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5123 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5124 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5125 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5126 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5127 P/N
45N8295, P0C38732.
</p
>
5129 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5130 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5131 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5132 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5133 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5134 P/N
45N8295, P0C38732.
</p
>
5136 <p
>The only difference is in the first number (serial number?), ISN,
5137 SA, date and WNPP values. Mentioning all the details here in case
5138 someone is able to use the information to find a way to identify the
5139 failing disk among working ones (if any such working disk actually
5145 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5146 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5148 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5149 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5150 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5151 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5152 member assosiation NUUG
</a
> and
5153 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5154 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5155 Bitraf
</a
>.
</p
>
5157 <p
>It starts
10:
00 and continue until late evening. Everyone is
5158 welcome, and there is no fee to participate. There is on the other
5159 hand limited space, and only room for
30 people. Please put your name
5160 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5161 wiki page
</a
> if you plan to join us.
</p
>
5166 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5167 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5168 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5169 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5170 <description><p
>Half a year ago, I reported that I had to find a
5171 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5172 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5173 time to spend on it, and it took a while to find a model I believe
5174 will do the job, but two days ago the replacement finally arrived. I
5176 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5177 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5178 a roaming workstation, and it seemed to work flawlessly. But my
5179 second installation with encrypted disk was not as successful. More
5180 on that below.
</p
>
5182 <p
>I had a hard time trying to track down a good laptop, as my most
5183 important requirements (robust and with a good keyboard) are never
5184 listed in the feature list. But I did get good help from the search
5185 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5186 allowed me to limit the list of interesting laptops based on my other
5187 requirements. A bit surprising that SSD disk are not disks according
5188 to that search interface, so I had to drop specifying the number of
5189 disks from my search parameters. I also asked around among friends to
5190 get their impression on keyboards and robustness.
</p
>
5192 <p
>So the new laptop arrived, and it is quite a lot wider than the
5193 X41. I am not quite convinced about the keyboard, as it is
5194 significantly wider than my old keyboard, and I have to stretch my
5195 hand a lot more to reach the edges. But the key response is fairly
5196 good and the individual key shape is fairly easy to handle, so I hope
5197 I will get used to it. My old X40 was starting to fail, and I really
5198 needed a new laptop now. :)
</p
>
5200 <p
>Turning off the touch pad was simple. All it took was a quick
5201 visit to the BIOS during boot it disable it.
</p
>
5203 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5204 lock up during load. And this happen when installing Debian Wheezy
5205 with encrypted disk, while the disk is being filled with random data.
5206 I also tested to install Ubuntu Raring, and it happen there too if I
5207 reenable the code to fill the disk with random data (it is disabled by
5208 default in Ubuntu). And the bug with is already known. It was
5209 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5210 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5211 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5212 kernel developers as
5213 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5214 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5215 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5216 Lenovo forums, both for
5217 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5218 2012-
11-
10</a
> and for
5219 <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
5220 03-
20-
2013</a
>. The problem do not only affect installation. The
5221 reports state that the disk lock up during use if many writes are done
5222 on the disk, so it is much no use to work around the installation
5223 problem and end up with a computer that can lock up at any moment.
5225 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5226 available
</a
> that will lock up the hard drive after running a few
5227 minutes by writing to a file.
</p
>
5229 <p
>I
've contacted my supplier and asked how to handle this, and after
5230 contacting PCHELP Norway (request
01D1FDP) which handle support
5231 requests for Lenovo, his first suggestion was to upgrade the disk
5232 firmware. Unfortunately there is no newer firmware available from
5233 Lenovo, as my disk already have the most recent one (version LF1i). I
5234 hope to hear more from him today and hope the problem can be
5240 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5241 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5242 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5243 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5244 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5245 trusty old Thinkpad X41. Unfortunately I did not have much time to
5246 spend on it, but today the replacement finally arrived. I ended up
5247 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5248 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5249 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5250 this, it is installing what I hope will be a more final installation,
5251 with a encrypted hard drive to ensure any dope head stealing it end up
5252 with an expencive door stop.
</p
>
5254 <p
>I had a hard time trying to track down a good laptop, as my most
5255 important requirements (robust and with a good keyboard) are never
5256 listed in the feature list. But I did get good help from the search
5257 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5258 allowed me to limit the list of interesting laptops based on my other
5259 requirements. A bit surprising that SSD disk are not disks, so I had
5260 to drop number of disks from my search parameters.
</p
>
5262 <p
>I am not quite convinced about the keyboard, as it is significantly
5263 wider than my old keyboard, and I have to stretch my hand a lot more
5264 to reach the edges. But the key response is fairly good and the
5265 individual key shape is fairly easy to handle, so I hope I will get
5266 used to it. My old X40 was starting to fail, and I really needed a
5267 new laptop now. :)
</p
>
5269 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5274 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5275 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5276 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5277 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5278 <description><p
>It annoys me when the computer fail to do automatically what it is
5279 perfectly capable of, and I have to do it manually to get things
5280 working. One such task is to find out what firmware packages are
5281 needed to get the hardware on my computer working. Most often this
5282 affect the wifi card, but some times it even affect the RAID
5283 controller or the ethernet card. Today I pushed version
0.4 of the
5284 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5285 including a new script isenkram-autoinstall-firmware handling the
5286 process of asking all the loaded kernel modules what firmware files
5287 they want, find debian packages providing these files and install the
5288 debian packages. Here is a test run on my laptop:
</p
>
5290 <p
><pre
>
5291 # isenkram-autoinstall-firmware
5292 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5293 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5294 info: locating packages with the requested firmware files
5295 info: Updating APT sources after adding non-free APT source
5296 info: trying to install firmware-ipw2x00
5299 Preconfiguring packages ...
5300 Selecting previously deselected package firmware-ipw2x00.
5301 (Reading database ...
259727 files and directories currently installed.)
5302 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5303 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5305 </pre
></p
>
5307 <p
>When all the requested firmware is present, a simple message is
5308 printed instead:
</p
>
5310 <p
><pre
>
5311 # isenkram-autoinstall-firmware
5312 info: did not find any firmware files requested by loaded kernel modules. exiting
5314 </pre
></p
>
5316 <p
>It could use some polish, but it is already working well and saving
5317 me some time when setting up new machines. :)
</p
>
5319 <p
>So, how does it work? It look at the set of currently loaded
5320 kernel modules, and look up each one of them using modinfo, to find
5321 the firmware files listed in the module meta-information. Next, it
5322 download the Contents file from a nearby APT mirror, and search for
5323 the firmware files in this file to locate the package with the
5324 requested firmware file. If the package is in the non-free section, a
5325 non-free APT source is added and the package is installed using
5326 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5329 <p
>I hope someone find time to implement a more polished version of
5330 this script as part of the hw-detect debian-installer module, to
5331 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5332 #
655507</a
>. There really is no need to insert USB sticks with
5333 firmware during a PXE install when the packages already are available
5334 from the nearby Debian mirror.
</p
>
5339 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5340 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5341 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5342 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5343 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5344 the screen just turn black when Linux boot, either during installation
5345 or on first boot from the hard disk. I
've seen it once in a while the
5346 last few years, but only recently understood the cause. I
've seen it
5347 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5348 The reason seem to be in the wiring of some laptops. The system to
5349 control the screen background light is inverted, so when Linux try to
5350 turn the brightness fully on, it end up turning it off instead. I do
5351 not know which Linux drivers are affected, but this post is about the
5352 i915 driver used by the
5353 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5354 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5356 <p
>The problem can be worked around two ways. Either by adding
5357 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5358 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5359 option when it load the i915 kernel module. On Debian and Ubuntu, it
5360 can be done by running these commands as root:
</p
>
5363 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5364 update-initramfs -u -k all
5367 <p
>Since March
2012 there is
5368 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5369 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5370 hardware have this problem, and get the driver to invert the
5371 brightness setting automatically. To use it, one need to add a row in
5372 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5373 intel_quirks array
</a
> in the driver source
5374 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5375 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5376 number (vendor number
8086 is assumed) and subdevice vendor and device
5379 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5380 -vvnn
</tt
> for the video card in question:
</p
>
5382 <p
><pre
>
5383 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5384 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5385 (rev
09) (prog-if
00 [VGA controller])
5386 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5387 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5388 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5389 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5390 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5392 Interrupt: pin A routed to IRQ
42
5393 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5394 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5395 Region
4: I/O ports at
4000 [size=
64]
5396 Expansion ROM at
<unassigned
> [disabled]
5397 Capabilities:
<access denied
>
5398 Kernel driver in use: i915
5399 </pre
></p
>
5401 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5403 <p
><pre
>
5404 struct intel_quirk intel_quirks[] = {
5406 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5407 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5410 </pre
></p
>
5412 <p
>According to the kernel module instructions (as seen using
5413 <tt
>modinfo i915
</tt
>), information about hardware needing the
5414 invert_brightness flag should be sent to the
5415 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5416 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5417 developers. But my email about the laptop sent
2013-
06-
03 have not
5419 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5420 web archive for the mailing list
</a
>, so I suspect they do not accept
5421 emails from non-subscribers. Because of this, I sent my patch also to
5422 the Debian bug tracking system instead as
5423 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5424 sure the patch is not lost.
</p
>
5426 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5427 with this problem working properly with Linux. If you use Gnome, your
5428 worries should be over at this point. But if you use KDE, there is
5429 something in KDE ignoring the invert_brightness setting and turning on
5430 the screen during login. I
've reported it to Debian as
5431 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5432 have no idea yet how to figure out exactly what subsystem is doing
5433 this. Perhaps you can help? Perhaps you know what the Gnome
5434 developers did to handle this, and this can give a clue to the KDE
5435 developers? Or you know where in KDE the screen brightness is changed
5436 during login? If so, please update the BTS report (or get in touch if
5437 you do not know how to update BTS).
</p
>
5439 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5440 acpi_backlight=vendor, to disable ACPI backlight support completely,
5441 as the ACPI information on the machine is trash and it is better to
5442 leave it to the intel video driver to control the screen
5443 backlight.
</p
>
5448 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5449 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5450 <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>
5451 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5452 <description><p
>Two days ago, I asked
5453 <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
5454 I could install Linux on a Packard Bell EasyNote LV computer
5455 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5456 with the obstacles put in the way of Linux users on a laptop with UEFI
5457 and Windows
8.
</p
>
5459 <p
>I never found out if the cause of my problems were the use of UEFI
5460 secure booting or fast boot. I suspect fast boot was the problem,
5461 causing the firmware to boot directly from HD without considering any
5462 key presses and alternative devices, but do not know UEFI settings
5463 enough to tell.
</p
>
5465 <p
>There is no way to install Linux on the machine in question without
5466 opening the box and disconnecting the hard drive! This is as far as I
5467 can tell, the only way to get access to the firmware setup menu
5468 without accepting the Windows
8 license agreement. I am told (and
5469 found description on how to) that it is possible to configure the
5470 firmware setup once booted into Windows
8. But as I believe the terms
5471 of that agreement are completely unacceptable, accepting the license
5472 was never an alternative. I do not enter agreements I do not intend
5473 to follow.
</p
>
5475 <p
>I feared I had to return the laptops and ask for a refund, and
5476 waste many hours on this, but luckily there was a way to get it to
5477 work. But I would not recommend it to anyone planning to run Linux on
5478 it, and I have become sceptical to Windows
8 certified laptops. Is
5479 this the way Linux will be forced out of the market place, by making
5480 it close to impossible for
"normal
" users to install Linux without
5481 accepting the Microsoft Windows license terms? Or at least not
5482 without risking to loose the warranty?
</p
>
5484 <p
>I
've updated the
5485 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5486 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5487 do not have to struggle as much as I did to get Linux into the
5490 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5491 Michael Tokarev and others for feedback and ideas.
</p
>
5496 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5497 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5498 <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>
5499 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5500 <description><p
>I
've run into quite a problem the last few days. I bought three
5501 new laptops for my parents and a few others. I bought Packard Bell
5502 Easynote LV to run Kubuntu on and use as their home computer. But I
5503 am completely unable to figure out how to install Linux on it. The
5504 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5505 instead of a BIOS to boot.
</p
>
5507 <p
>The problem is that I am unable to get it to PXE boot, and unable
5508 to get it to boot the Linux installer from my USB stick. I have yet
5509 to try the DVD install, and still hope it will work. when I turn on
5510 the computer, there is no information on what buttons to press to get
5511 the normal boot menu. I expect to get some boot menu to select PXE or
5512 USB stick booting. When booting, it first ask for the language to
5513 use, then for some regional settings, and finally if I will accept the
5514 Windows
8 terms of use. As these terms are completely unacceptable to
5515 me, I have no other choice but to turn off the computer and try again
5516 to get it to boot the Linux installer.
</p
>
5518 <p
>I have gathered my findings so far on a Linlap page about the
5519 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5520 EasyNote LV
</a
> model. If you have any idea how to get Linux
5521 installed on this machine, please get in touch or update that wiki
5522 page. If I can
't find a way to install Linux, I will have to return
5523 the laptop to the seller and find another machine for my parents.
</p
>
5525 <p
>I wonder, is this the way Linux will be forced out of the market
5526 using UEFI and
"secure boot
" by making it impossible to install Linux
5527 on new Laptops?
</p
>
5532 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5533 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5534 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5535 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5536 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5537 an operating system based on Debian intended for use in schools. It
5538 contain a turn-key solution for the computer network provided to
5539 pupils in the primary schools. It provide both the central server,
5540 network boot servers and desktop environments with heaps of
5541 educational software. The project was founded almost
12 years ago,
5542 2001-
07-
02. If you want to support the project, which is in need for
5543 cash to fund developer gatherings and other project related activity,
5544 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5545 donate some money
</a
>.
5547 <p
>A topic that come up again and again on the Debian Edu mailing
5548 lists and elsewhere, is the question on how to transform a Debian or
5549 Ubuntu installation into a Debian Edu installation. It isn
't very
5550 hard, and last week I wrote a script to replicate the steps done by
5551 the Debian Edu installer.
</p
>
5553 <p
>The script,
5554 <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/
>
5555 in the debian-edu-config package, will go through these six steps and
5556 transform an existing Debian Wheezy or Ubuntu (untested) installation
5557 into a Debian Edu Workstation:
</p
>
5561 <li
>Add skolelinux related APT sources.
</li
>
5562 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5563 <li
>Install debian-edu-install to load preseeding values and pull in
5564 our configuration.
</li
>
5565 <li
>Preseed debconf database with profile setup in
5566 /etc/debian-edu/config, and run tasksel to install packages
5567 according to the profile specified in the config above,
5568 overriding some of the Debian automation machinery.
</li
>
5569 <li
>Run debian-edu-cfengine-D installation to configure everything
5570 that could not be done using preseeding.
</li
>
5571 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5575 <p
>There are some steps in the Debian Edu installation that can not be
5576 replicated like this. Disk partitioning and LVM setup, for example.
5577 So this script just assume there is enough disk space to install all
5578 the needed packages.
</p
>
5580 <p
>The script was created to help a Debian Edu student working on
5581 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5582 Debian Edu client, and using it he can take the existing
5583 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5584 transform it into a fully functioning Debian Edu Workstation (or
5585 Roaming Workstation, or whatever :).
</p
>
5587 <p
>The default setting in the script is to create a KDE Workstation.
5588 If a LXDE based Roaming workstation is wanted instead, modify the
5589 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5591 <p
><pre
>
5592 PROFILE=
"Roaming-Workstation
"
5593 DESKTOP=
"lxde
"
5594 </pre
></p
>
5596 <p
>The script could even become useful to set up Debian Edu servers in
5597 the cloud, by starting with a virtual Debian installation at some
5598 virtual hosting service and setting up all the services on first
5604 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5605 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5606 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5607 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5608 <description><P
>In January,
5609 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5610 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5611 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5612 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5613 marvellous construction system from Denmark. We also created
5614 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5615 a place to take notes and write down our plans and hopes. And several
5616 people showed up to help. I was very happy to see the effect of my
5617 call. Since the small start, we have a debtags tag
5618 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5619 tag for LEGO related packages, and now count
10 packages related to
5620 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5622 <p
><table
>
5623 <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
>
5624 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5625 <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
>
5626 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5627 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5628 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5629 <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
>
5630 <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
>
5631 <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
>
5632 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5633 </table
></p
>
5635 <p
>Some of these are available in Wheezy, and all but one are
5636 currently available in Jessie/testing. leocad is so far only
5637 available in experimental.
</p
>
5639 <p
>If you care about LEGO in Debian, please join us on IRC and help
5640 adding the rest of the great free software tools available on Linux
5641 for LEGO designers.
</p
>
5646 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5647 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5648 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5649 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5650 <description><p
>When I woke up this morning, I was very happy to see that the
5651 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5652 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5653 Debian release, and I expect to move my machines at home over to it fairly
5656 <p
>The new debian release contain heaps of new stuff, and one program
5657 in particular make me very happy to see included. The
5658 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5659 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5660 included for the first time. Alongside similar programs like
5661 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5662 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5663 it allow for visual programming where syntax errors can not happen,
5664 and a friendly programming environment for learning to control the
5665 computer. Scratch will also be included in the next release of Debian
5668 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5669 Edu/Skolelinux release too. The
5670 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5671 alpha release
</a
> went out last week, and the next should soon
5677 <title>Isenkram
0.2 finally in the Debian archive
</title>
5678 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5679 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5680 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5681 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5682 package
</a
> finally made it into the archive, after lingering in NEW
5683 for many months. I uploaded it to the Debian experimental suite
5684 2013-
01-
27, and today it was accepted into the archive.
</p
>
5686 <p
>Isenkram is a system for suggesting to users what packages to
5687 install to work with a pluggable hardware device. The suggestion pop
5688 up when the device is plugged in. For example if a Lego Mindstorm NXT
5689 is inserted, it will suggest to install the program needed to program
5690 the NXT controller. Give it a go, and report bugs and suggestions to
5696 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5697 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5698 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5699 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5700 <description><p
>My
5701 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5702 bitcoin related blog post
</a
> mentioned that the new
5703 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5704 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5705 2013-
01-
19, and have been available in unstable since then. It was
5706 automatically copied to Ubuntu, and is available in their Raring
5707 version too.
</p
>
5709 <p
>But there is a strange problem with the build that block this new
5710 version from being available on the i386 and kfreebsd-i386
5711 architectures. For some strange reason, the autobuilders in Debian
5712 for these architectures fail to run the test suite on these
5713 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5714 We are so far unable to reproduce it when building it manually, and
5715 no-one have been able to propose a fix. If you got an idea what is
5716 failing, please let us know via the BTS.
</p
>
5718 <p
>One feature that is annoying me with of the bitcoin client, because
5719 I often run low on disk space, is the fact that the client will exit
5720 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5721 #
696715</a
>). So make sure you have enough disk space when you run
5724 <p
>As usual, if you use bitcoin and want to show your support of my
5725 activities, please send Bitcoin donations to my address
5726 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5731 <title>Welcome to the world, Isenkram!
</title>
5732 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5733 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5734 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5735 <description><p
>Yesterday, I
5736 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5737 for testers
</a
> for my prototype for making Debian better at handling
5738 pluggable hardware devices, which I
5739 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5740 out to create
</a
> earlier this month. Several valuable testers showed
5741 up, and caused me to really want to to open up the development to more
5742 people. But before I did this, I want to come up with a sensible name
5743 for this project. Today I finally decided on a new name, and I have
5744 renamed the project from hw-support-handler to this new name. In the
5745 process, I moved the source to git and made it available as a
5746 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5747 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5748 To fetch and build the latest version of the source, use
</p
>
5751 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5752 cd isenkram
&& git-buildpackage -us -uc
5755 <p
>I have not yet adjusted all files to use the new name yet. If you
5756 want to hack on the source or improve the package, please go ahead.
5757 But please talk to me first on IRC or via email before you do major
5758 changes, to make sure we do not step on each others toes. :)
</p
>
5760 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5761 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5762 stuff, in other words. I
've been told it is the Norwegian variant of
5763 the German word eisenkram, for those that are familiar with that
5766 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5767 instructions, to avoid confusing people with an error from the signing
5770 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5771 clone argument to avoid the need for authentication.
</p
>
5776 <title>First prototype ready making hardware easier to use in Debian
</title>
5777 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5778 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5779 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5780 <description><p
>Early this month I set out to try to
5781 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5782 the Debian support for pluggable hardware devices
</a
>. Now my
5783 prototype is working, and it is ready for a larger audience. To test
5785 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5786 from the Debian Edu subversion repository
</a
>, build and install the
5787 package. You might have to log out and in again activate the
5788 autostart script.
</p
>
5790 <p
>The design is simple:
</p
>
5794 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5795 hw-support-handlerd to start when the user log in.
</li
>
5797 <li
>This program listen for kernel events about new hardware (directly
5798 from the kernel like udev does), not using HAL dbus events as I
5799 initially did.
</li
>
5801 <li
>When new hardware is inserted, look up the hardware modalias in
5802 the APT database, a database
5803 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5804 via HTTP
</a
> and a database available as part of the package.
</li
>
5806 <li
>If a package is mapped to the hardware in question, the package
5807 isn
't installed yet and this is the first time the hardware was
5808 plugged in, show a desktop notification suggesting to install the
5809 package or packages.
</li
>
5811 <li
>If the user click on the
'install package now
' button, ask
5812 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5814 <li
>aptdaemon ask for root password or sudo password, and install the
5815 package while showing progress information in a window.
</li
>
5819 <p
>I still need to come up with a better name for the system. Here
5820 are some screen shots showing the prototype in action. First the
5821 notification, then the password request, and finally the request to
5822 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5824 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5825 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5826 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5827 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5828 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5830 <p
>The prototype still need to be improved with longer timeouts, but
5831 is already useful. The database of hardware to package mappings also
5832 need more work. It is currently compatible with the Ubuntu way of
5833 storing such information in the package control file, but could be
5834 changed to use other formats instead or in addition to the current
5835 method. I
've dropped the use of discover for this mapping, as the
5836 modalias approach is more flexible and easier to use on Linux as long
5837 as the Linux kernel expose its modalias strings directly.
</p
>
5839 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5840 here is the command required to check out and build the source: Use
5841 '<tt
>svn checkout
5842 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5843 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5844 devscripts package.
</p
>
5846 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5847 renamed to Isenkram and the source moved from the Debian Edu
5848 subversion repository to a Debian collab-maint git repository. See
5849 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5850 instructions
</a
> for details.
</p
>
5855 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5856 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5857 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5858 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5859 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5860 suddenly in bed. With a quiet whimper, it went completely quiet and
5861 black. The power button was no longer able to turn it on. It was a
5862 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5863 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5864 Compaq I had before that. Now I need to find a replacement. To keep
5865 going during Christmas, I moved the one year old SSD disk to my old
5866 X40 where it fitted (only one I had left that could use it), but it is
5867 not a durable solution.
5869 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5870 got a new one more than
10 years ago. It still holds true.:)
</p
>
5874 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5875 than A4).
</li
>
5876 <li
>Robust, it will be in my backpack every day.
</li
>
5877 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5878 <li
>Long battery life time. Preferable a week.
</li
>
5879 <li
>Internal WIFI network card.
</li
>
5880 <li
>Internal Twisted Pair network card.
</li
>
5881 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5882 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5883 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5885 <li
>Hardware supported by Debian Stable, ie the default kernel and
5886 X.org packages.
</li
>
5887 <li
>Quiet, preferably fan free (or at least not using the fan most of
5892 <p
>You will notice that there are no RAM and CPU requirements in the
5893 list. The reason is simply that the specifications on laptops the
5894 last
10-
15 years have been sufficient for my needs, and I have to look
5895 at other features to choose my laptop. But are there still made as
5896 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5897 robust, and Thinkpads seem to be heading in the wrong direction since
5898 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5899 still be useful.
</p
>
5901 <p
>Perhaps I should rethink my needs, and look for a pad with an
5902 external keyboard? I
'll have to check the
5903 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5904 well-supported laptops, or perhaps just buy one preinstalled from one
5905 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5906 Pre-loaded site
</a
>.
</p
>
5911 <title>How to find a browser plugin supporting a given MIME type
</title>
5912 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5913 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5914 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5915 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5916 install to get support for a given MIME type. Thanks to
5917 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5918 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5919 Unfortunately, not very many packages provide the needed meta
5920 information, Anyway, here is a small script to look up all browser
5921 plugin packages announcing ther MIME support using this specification:
</p
>
5927 def pkgs_handling_mimetype(mimetype):
5932 version = pkg.candidate
5934 version = pkg.installed
5937 record = version.record
5938 if not record.has_key(
'Npp-MimeType
'):
5940 mime_types = record[
'Npp-MimeType
'].split(
',
')
5941 for t in mime_types:
5942 t = t.rstrip().strip()
5944 thepkgs.append(pkg.name)
5946 mimetype =
"audio/ogg
"
5947 if
1 < len(sys.argv):
5948 mimetype = sys.argv[
1]
5949 print
"Browser plugin packages supporting %s:
" % mimetype
5950 for pkg in pkgs_handling_mimetype(mimetype):
5951 print
" %s
" %pkg
5954 <p
>It can be used like this to look up a given MIME type:
</p
>
5957 % ./apt-find-browserplug-for-mimetype
5958 Browser plugin packages supporting audio/ogg:
5960 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5961 Browser plugin packages supporting application/x-shockwave-flash:
5962 browser-plugin-gnash
5966 <p
>In Ubuntu this mechanism is combined with support in the browser
5967 itself to query for plugins and propose to install the needed
5968 packages. It would be great if Debian supported such feature too. Is
5969 anyone working on adding it?
</p
>
5971 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5972 request for icweasel support for this feature is
5973 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5974 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5975 of manpower and wish for a different design is the reason thus feature
5976 is not yet in iceweasel from Debian.
</p
>
5981 <title>What is the most supported MIME type in Debian?
</title>
5982 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5983 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5984 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5985 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5986 proposal to add AppStream information to the Debian archive
</a
>, is a
5987 proposal to make it possible for a Desktop application to propose to
5988 the user some package to install to gain support for a given MIME
5989 type, font, library etc. that is currently missing. With such
5990 mechanism in place, it would be possible for the desktop to
5991 automatically propose and install leocad if some LDraw file is
5992 downloaded by the browser.
</p
>
5994 <p
>To get some idea about the current content of the archive, I decided
5995 to write a simple program to extract all .desktop files from the
5996 Debian archive and look up the claimed MIME support there. The result
5998 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5999 site
</a
>. Using the collected information, it become possible to
6000 answer the question in the title. Here are the
20 most supported MIME
6001 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
6002 The complete list is available from the link above.
</p
>
6004 <p
><strong
>Debian Stable:
</strong
></p
>
6008 ----- -----------------------
6024 18 application/x-ogg
6031 <p
><strong
>Debian Testing:
</strong
></p
>
6035 ----- -----------------------
6051 18 application/x-ogg
6058 <p
><strong
>Debian Unstable:
</strong
></p
>
6062 ----- -----------------------
6079 18 application/x-ogg
6085 <p
>I am told that PackageKit can provide an API to access the kind of
6086 information mentioned in DEP-
11. I have not yet had time to look at
6087 it, but hope the PackageKit people in Debian are on top of these
6090 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6091 discovering a typo in my script.
</p
>
6096 <title>Using modalias info to find packages handling my hardware
</title>
6097 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6098 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6099 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6100 <description><p
>Yesterday, I wrote about the
6101 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6102 values provided by the Linux kernel
</a
> following my hope for
6103 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6104 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6105 modalias values attached to package names can be used to map packages
6106 to hardware. This allow the system to look up and suggest relevant
6107 packages when I plug in some new hardware into my machine, and replace
6108 discover and discover-data as the database used to map hardware to
6111 <p
>I create a modaliases file with entries like the following,
6112 containing package name, kernel module name (if relevant, otherwise
6113 the package name) and globs matching the relevant hardware
6116 <p
><blockquote
>
6117 Package: package-name
6118 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6119 </blockquote
></p
>
6121 <p
>It is fairly trivial to write code to find the relevant packages
6122 for a given modalias value using this file.
</p
>
6124 <p
>An entry like this would suggest the video and picture application
6125 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6127 <p
><blockquote
>
6129 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6130 </blockquote
></p
>
6132 <p
>An entry like this would suggest the pcmciautils package when a
6133 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6135 <p
><blockquote
>
6136 Package: pcmciautils
6137 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6138 </blockquote
></p
>
6140 <p
>An entry like this would suggest the package colorhug-client when
6141 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6143 <p
><blockquote
>
6144 Package: colorhug-client
6145 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6146 </blockquote
></p
>
6148 <p
>I believe the format is compatible with the format of the Packages
6149 file in the Debian archive. Ubuntu already uses their Packages file
6150 to store their mappings from packages to hardware.
</p
>
6152 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6153 announce the hardware it support in a way my prototype understand.
6154 This allow those publishing packages in an APT source outside the
6155 Debian archive as well as those backporting packages to make sure the
6156 hardware mapping are included in the package meta information. I
've
6157 tested such header in the pymissile package, and its modalias mapping
6158 is working as it should with my prototype. It even made it to Ubuntu
6161 <p
>To test if it was possible to look up supported hardware using only
6162 the shell tools available in the Debian installer, I wrote a shell
6163 implementation of the lookup code. The idea is to create files for
6164 each modalias and let the shell do the matching. Please check out and
6166 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6167 shell script. It run without any extra dependencies and fetch the
6168 hardware mappings from the Debian archive and the subversion
6169 repository where I currently work on my prototype.
</p
>
6171 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6172 install yubikey-personalization:
</p
>
6174 <p
><blockquote
>
6175 % ./hw-support-lookup
6176 <br
>yubikey-personalization
6178 </blockquote
></p
>
6180 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6181 propose to install the pcmciautils package:
</p
>
6183 <p
><blockquote
>
6184 % ./hw-support-lookup
6185 <br
>pcmciautils
6187 </blockquote
></p
>
6189 <p
>If you know of any hardware-package mapping that should be added to
6190 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6191 database
</a
>, please tell me about it.
</p
>
6193 <p
>It could be possible to generate several of the mappings between
6194 packages and hardware. One source would be to look at packages with
6195 kernel modules, ie packages with *.ko files in /lib/modules/, and
6196 extract their modalias information. Another would be to look at
6197 packages with udev rules, ie packages with files in
6198 /lib/udev/rules.d/, and extract their vendor/model information to
6199 generate a modalias matching rule. I have not tested any of these to
6200 see if it work.
</p
>
6202 <p
>If you want to help implementing a system to let us propose what
6203 packages to install when new hardware is plugged into a Debian
6204 machine, please send me an email or talk to me on
6205 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6210 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6211 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6212 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6213 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6214 <description><p
>While looking into how to look up Debian packages based on hardware
6215 information, to find the packages that support a given piece of
6216 hardware, I refreshed my memory regarding modalias values, and decided
6217 to document the details. Here are my findings so far, also available
6219 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6220 Debian Edu subversion repository
</a
>:
6222 <p
><strong
>Modalias decoded
</strong
></p
>
6224 <p
>This document try to explain what the different types of modalias
6225 values stands for. It is in part based on information from
6226 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6227 &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;,
6228 &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
6229 &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;.
6231 <p
>The modalias entries for a given Linux machine can be found using
6232 this shell script:
</p
>
6235 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6238 <p
>The supported modalias globs for a given kernel module can be found
6239 using modinfo:
</p
>
6242 % /sbin/modinfo psmouse | grep alias:
6243 alias: serio:ty05pr*id*ex*
6244 alias: serio:ty01pr*id*ex*
6248 <p
><strong
>PCI subtype
</strong
></p
>
6250 <p
>A typical PCI entry can look like this. This is an Intel Host
6251 Bridge memory controller:
</p
>
6253 <p
><blockquote
>
6254 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6255 </blockquote
></p
>
6257 <p
>This represent these values:
</p
>
6262 sv
00001028 (subvendor)
6263 sd
000001AD (subdevice)
6265 sc
00 (bus subclass)
6269 <p
>The vendor/device values are the same values outputted from
'lspci
6270 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6271 0600. The
0600 class is a host bridge. Other useful bus values are
6272 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6274 <p
>Not sure how to figure out the interface value, nor what it
6277 <p
><strong
>USB subtype
</strong
></p
>
6279 <p
>Some typical USB entries can look like this. This is an internal
6280 USB hub in a laptop:
</p
>
6282 <p
><blockquote
>
6283 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6284 </blockquote
></p
>
6286 <p
>Here is the values included in this alias:
</p
>
6289 v
1D6B (device vendor)
6290 p
0001 (device product)
6292 dc
09 (device class)
6293 dsc
00 (device subclass)
6294 dp
00 (device protocol)
6295 ic
09 (interface class)
6296 isc
00 (interface subclass)
6297 ip
00 (interface protocol)
6300 <p
>The
0900 device class/subclass means hub. Some times the relevant
6301 class is in the interface class section. For a simple USB web camera,
6302 these alias entries show up:
</p
>
6304 <p
><blockquote
>
6305 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6306 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6307 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6308 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6309 </blockquote
></p
>
6311 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6312 camera),
0101 is audio control device and
0102 is audio streaming (aka
6313 microphone). Thus this is a camera with microphone included.
</p
>
6315 <p
><strong
>ACPI subtype
</strong
></p
>
6317 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6318 receiver in a Thinkpad X40:
</p
>
6320 <p
><blockquote
>
6321 acpi:IBM0071:PNP0511:
6322 </blockquote
></p
>
6324 <p
>The values between the colons are IDs.
</p
>
6326 <p
><strong
>DMI subtype
</strong
></p
>
6328 <p
>The DMI table contain lots of information about the computer case
6329 and model. This is an entry for a IBM Thinkpad X40, fetched from
6330 /sys/devices/virtual/dmi/id/modalias:
</p
>
6332 <p
><blockquote
>
6333 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6334 </blockquote
></p
>
6336 <p
>The values present are
</p
>
6339 bvn IBM (BIOS vendor)
6340 bvr
1UETB
6WW(
1.66) (BIOS version)
6341 bd
06/
15/
2005 (BIOS date)
6342 svn IBM (system vendor)
6343 pn
2371H4G (product name)
6344 pvr ThinkPadX40 (product version)
6345 rvn IBM (board vendor)
6346 rn
2371H4G (board name)
6347 rvr NotAvailable (board version)
6348 cvn IBM (chassis vendor)
6349 ct
10 (chassis type)
6350 cvr NotAvailable (chassis version)
6353 <p
>The chassis type
10 is Notebook. Other interesting values can be
6354 found in the dmidecode source:
</p
>
6358 4 Low Profile Desktop
6371 17 Main Server Chassis
6372 18 Expansion Chassis
6374 20 Bus Expansion Chassis
6375 21 Peripheral Chassis
6377 23 Rack Mount Chassis
6386 <p
>The chassis type values are not always accurately set in the DMI
6387 table. For example my home server is a tower, but the DMI modalias
6388 claim it is a desktop.
</p
>
6390 <p
><strong
>SerIO subtype
</strong
></p
>
6392 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6393 test machine:
</p
>
6395 <p
><blockquote
>
6396 serio:ty01pr00id00ex00
6397 </blockquote
></p
>
6399 <p
>The values present are
</p
>
6408 <p
>This type is supported by the psmouse driver. I am not sure what
6409 the valid values are.
</p
>
6411 <p
><strong
>Other subtypes
</strong
></p
>
6413 <p
>There are heaps of other modalias subtypes according to
6414 file2alias.c. There is the rest of the list from that source: amba,
6415 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6416 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6417 vmbus, x86cpu and zorro. I did not spend time documenting all of
6418 these, as they do not seem relevant for my intended use with mapping
6419 hardware to packages when new stuff is inserted during run time.
</p
>
6421 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6423 <p
>To check which kernel modules provide support for a given modalias,
6424 one can use the following shell script:
</p
>
6427 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6428 echo
"$id
" ; \
6429 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6433 <p
>The output can look like this (only the first few entries as the
6434 list is very long on my test machine):
</p
>
6438 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6440 FATAL: Module acpi:device: not found.
6442 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6443 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6444 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6445 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6446 acpi:IBM0071:PNP0511:
6447 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6448 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6449 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6453 <p
>If you want to help implementing a system to let us propose what
6454 packages to install when new hardware is plugged into a Debian
6455 machine, please send me an email or talk to me on
6456 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6458 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6459 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6460 in /sys/ with space in them.
</p
>
6465 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6466 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6467 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6468 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6469 <description><p
>As part of my investigation on how to improve the support in Debian
6470 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6471 Launcher and updated the Debian package
6472 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6473 sure udev will fix the device permissions when it is plugged in. I
6474 also added a
"Modaliases
" header to test it in the Debian archive and
6475 hopefully make the package be proposed by jockey in Ubuntu when a user
6476 plug in his rocket launcher. In the process I moved the source to a
6477 git repository under collab-maint, to make it easier for any DD to
6478 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6479 is not very active, but the software still work for me even after five
6480 years of relative silence. The new git repository is not listed in
6481 the uploaded package yet, because I want to test the other changes a
6482 bit more before I upload the new version. If you want to check out
6483 the new version with a .desktop file included, visit the
6484 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6485 view
</a
> or use
"<tt
>git clone
6486 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6491 <title>Lets make hardware dongles easier to use in Debian
</title>
6492 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6493 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6494 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6495 <description><p
>One thing that annoys me with Debian and Linux distributions in
6496 general, is that there is a great package management system with the
6497 ability to automatically install software packages by downloading them
6498 from the distribution mirrors, but no way to get it to automatically
6499 install the packages I need to use the hardware I plug into my
6500 machine. Even if the package to use it is easily available from the
6501 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6502 suggest to automatically install the python-nxt, nbc and t2n packages
6503 I need to talk to it. When I plug in a Yubikey, it could propose the
6504 yubikey-personalization package. The information required to do this
6505 is available, but no-one have pulled all the pieces together.
</p
>
6507 <p
>Some years ago, I proposed to
6508 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6509 the discover subsystem to implement this
</a
>. The idea is fairly
6514 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6515 starting when a user log in.
</li
>
6517 <li
>Set this program up to listen for kernel events emitted when new
6518 hardware is inserted into the computer.
</li
>
6520 <li
>When new hardware is inserted, look up the hardware ID in a
6521 database mapping to packages, and take note of any non-installed
6522 packages.
</li
>
6524 <li
>Show a message to the user proposing to install the discovered
6525 package, and make it easy to install it.
</li
>
6529 <p
>I am not sure what the best way to implement this is, but my
6530 initial idea was to use dbus events to discover new hardware, the
6531 discover database to find packages and
6532 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6535 <p
>Yesterday, I found time to try to implement this idea, and the
6536 draft package is now checked into
6537 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6538 Debian Edu subversion repository
</a
>. In the process, I updated the
6539 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6540 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6541 the relevant packages in Debian, and uploaded a new version
6542 2.2013.01.09 to unstable. I also discovered that the current
6543 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6544 package in Debian no longer discovered any USB devices, because
6545 /proc/bus/usb/devices is no longer present. I ported it to use
6546 libusb as a fall back option to get it working. The fixed package
6547 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6548 because of the freeze).
</p
>
6550 <p
>With this prototype in place, I can insert my Yubikey, and get this
6551 desktop notification to show up (only once, the first time it is
6552 inserted):
</p
>
6554 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6556 <p
>For this prototype to be really useful, some way to automatically
6557 install the proposed packages by pressing the
"Please install
6558 program(s)
" button should to be implemented.
</p
>
6560 <p
>If this idea seem useful to you, and you want to help make it
6561 happen, please help me update the discover-data database with mappings
6562 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6563 list the package you would like to have installed when a given
6564 hardware device is inserted into your computer, and report bugs using
6565 reportbug if it isn
't. Or, if you know of a better way to provide
6566 such mapping, please let me know.
</p
>
6568 <p
>This prototype need more work, and there are several questions that
6569 should be considered before it is ready for production use. Is dbus
6570 the correct way to detect new hardware? At the moment I look for HAL
6571 dbus events on the system bus, because that is the events I could see
6572 on my Debian Squeeze KDE desktop. Are there better events to use?
6573 How should the user be notified? Is the desktop notification
6574 mechanism the best option, or should the background daemon raise a
6575 popup instead? How should packages be installed? When should they
6576 not be installed?
</p
>
6578 <p
>If you want to help getting such feature implemented in Debian,
6579 please send me an email. :)
</p
>
6584 <title>New IRC channel for LEGO designers using Debian
</title>
6585 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6587 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6588 <description><p
>During Christmas, I have worked a bit on the Debian support for
6589 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6590 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6591 discovered I had to build all the tools myself because none were
6592 already in Debian Squeeze. If Debian support for LEGO is something
6593 you care about, please join me on the IRC channel
6594 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6595 irc.debian.org). There is a lot that could be done to improve the
6596 Debian support for LEGO designers. For example both CAD software
6597 and Mindstorm compilers are missing. :)
</p
>
6599 <p
>Update
2012-
01-
03: A
6600 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6601 including links to Lego related packages is now available.
</p
>
6606 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6607 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6608 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6609 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6610 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6611 year! I hope next year will prove to be a good year.
</p
>
6613 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6614 decentralised
"currency
" that allow people to transfer bitcoins
6615 between each other with minimal overhead, is a very interesting
6616 experiment. And as I wrote a few days ago, the bitcoin situation in
6617 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6618 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6619 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6620 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6621 for one of the ftpmasters to approve the new bitcoin-qt package
6624 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6625 team in Debian, you can easily test the package in Debian Squeeze
6626 using the following steps to get a set of working packages:
</p
>
6628 <blockquote
><pre
>
6629 git clone git://git.debian.org/git/collab-maint/bitcoin
6631 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6632 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6633 </pre
></blockquote
>
6635 <p
>You might have to install some build dependencies as well. The
6636 list of commands should give you two packages, bitcoind and
6637 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6638 client will download the complete set of bitcoin
"blocks
", which need
6639 around
5.6 GiB of data on my machine at the moment. Make sure your
6640 ~/.bitcoin/ directory have lots of spare room if you want to download
6641 all the blocks. The client will warn if the disk is getting full, so
6642 there is not really a problem if you got too little room, but you will
6643 not be able to get all the features out of the client.
</p
>
6645 <p
>As usual, if you use bitcoin and want to show your support of my
6646 activities, please send Bitcoin donations to my address
6647 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6652 <title>A word on bitcoin support in Debian
</title>
6653 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6654 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6655 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6656 <description><p
>It has been a while since I wrote about
6657 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6658 peer-to-peer based crypto-currency, and the reason is simply that I
6659 have been busy elsewhere. But two days ago, I started looking at the
6660 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6661 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6662 is now maintained by a
6663 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6664 people
</a
>, and the grunt work had already been done by this team. We
6665 owe a huge thank you to all these team members. :)
6666 But I was sad to discover that the bitcoin client is missing in
6667 Wheezy. It is only available in Sid (and an outdated client from
6668 backports). The client had several RC bugs registered in BTS blocking
6669 it from entering testing. To try to help the team and improve the
6670 situation, I spent some time providing patches and triaging the bug
6671 reports. I also had a look at the bitcoin package available from Matt
6673 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6674 Ubuntu
</a
>, and moved the useful pieces from that version into the
6675 Debian package.
</p
>
6677 <p
>After checking with the main package maintainer Jonas Smedegaard on
6678 IRC, I pushed several patches into the collab-maint git repository to
6679 improve the package. It now contains fixes for the RC issues (not from
6680 me, but fixed by Scott Howard), build rules for a Qt GUI client
6681 package, konqueror support for the bitcoin: URI and bash completion
6682 setup. As I work on Debian Squeeze, I also created
6683 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6684 patch to backport
</a
> the latest version. Jonas is going to look at
6685 it and try to integrate it into the git repository before uploading a
6686 new version to unstable.
6688 <p
>I would very much like bitcoin to succeed, to get rid of the
6689 centralized control currently exercised in the monetary system. I
6690 find it completely unacceptable that the USA government is collecting
6691 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6692 that the major credit card companies can block legal money
6693 transactions to Wikileaks. But for bitcoin to succeed, more people
6694 need to use bitcoins, and more people need to accept bitcoins when
6695 they sell products and services. Improving the bitcoin support in
6696 Debian is a small step in the right direction, but not enough.
6697 Unfortunately the user experience when browsing the web and wanting to
6698 pay with bitcoin is still not very good. The bitcoin: URI is a step
6699 in the right direction, but need to work in most or every browser in
6700 use. Also the bitcoin-qt client is too heavy to fire up to do a
6701 quick transaction. I believe there are other clients available, but
6702 have not tested them.
</p
>
6705 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6706 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6707 I received
20.15 BTC so far on the address I provided in my blog two
6708 years ago, as can be
6709 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6710 on the blockexplorer service
</a
>. Thank you everyone for your
6711 donation. The blockexplorer service demonstrates quite well that
6712 bitcoin is not quite anonymous and untracked. :) I wonder if the
6713 number of users have gone up since then. If you use bitcoin and want
6714 to show your support of my activity, please send Bitcoin donations to
6715 the same address as last time,
6716 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6721 <title>Git repository for song book for Computer Scientists
</title>
6722 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6723 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6724 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6725 <description><p
>As I
6726 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6727 this summer
</a
>, I have created a Computer Science song book a few
6728 years ago, and today I finally found time to create a public
6729 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6730 repository for the project
</a
>.
</p
>
6732 <p
>If you want to help out, please clone the source and submit patches
6733 to the HTML version. To generate the PDF and PostScript version,
6734 please use prince XML, or let me know about a useful free software
6735 processor capable of creating a good looking PDF from the HTML.
</p
>
6737 <p
>Want to sing? You can still find the song book in HTML, PDF and
6738 PostScript formats at
6739 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6740 Science Songbook
</a
>.
</p
>
6745 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6746 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6748 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6749 <description><p
>I dag fyller
6750 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6751 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6752 si gratulerer med dagen, Debian!
</p
>
6757 <title>Song book for Computer Scientists
</title>
6758 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6759 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6760 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6761 <description><p
>Many years ago, while studying Computer Science at the
6762 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6763 collecting computer related songs for use at parties. The original
6764 version was written in LaTeX, but a few years ago I got help from
6765 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6766 while keeping the ability to create a nice book in PDF format. I have
6767 not had time to maintain the book for a while now, and guess I should
6768 put it up on some public version control repository where others can
6769 help me extend and update the book. If anyone is volunteering to help
6770 me with this, send me an email. Also let me know if there are songs
6771 missing in my book.
</p
>
6773 <p
>I have not mentioned the book on my blog so far, and it occured to
6774 me today that I really should let all my readers share the joys of
6775 singing out load about programming, computers and computer networks.
6776 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6777 12</a
> is about to start (and I am not going). Want to sing? Check
6778 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6779 Computer Science Songbook
</a
>.
6784 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6785 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6786 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6787 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6788 <description><p
>At work we have heaps of servers. I believe the total count is
6789 around
1000 at the moment. To be able to get help from the vendors
6790 when something go wrong, we want to keep the firmware on the servers
6791 up to date. If the firmware isn
't the latest and greatest, the
6792 vendors typically refuse to start debugging any problems until the
6793 firmware is upgraded. So before every reboot, we want to upgrade the
6794 firmware, and we would really like everyone handling servers at the
6795 university to do this themselves when they plan to reboot a machine.
6796 For that to happen we at the unix server admin group need to provide
6797 the tools to do so.
</p
>
6799 <p
>To make firmware upgrading easier, I am working on a script to
6800 fetch and install the latest firmware for the servers we got. Most of
6801 our hardware are from Dell and HP, so I have focused on these servers
6802 so far. This blog post is about the Dell part.
</P
>
6804 <p
>On the Dell FTP site I was lucky enough to find
6805 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6806 with firmware information for all
11th generation servers, listing
6807 which firmware should be used on a given model and where on the FTP
6808 site I can find it. Using a simple perl XML parser I can then
6809 download the shell scripts Dell provides to do firmware upgrades from
6810 within Linux and reboot when all the firmware is primed and ready to
6811 be activated on the first reboot.
</p
>
6813 <p
>This is the Dell related fragment of the perl code I am working on.
6814 Are there anyone working on similar tools for firmware upgrading all
6815 servers at a site? Please get in touch and lets share resources.
</p
>
6817 <p
><pre
>
6821 use File::Temp qw(tempdir);
6823 # Install needed RHEL packages if missing
6825 'XML::Simple
' =
> 'perl-XML-Simple
',
6827 for my $module (keys %rhelmodules) {
6828 eval
"use $module;
";
6830 my $pkg = $rhelmodules{$module};
6831 system(
"yum install -y $pkg
");
6832 eval
"use $module;
";
6836 my $errorsto =
'pere@hungry.com
';
6842 sub run_firmware_script {
6843 my ($opts, $script) = @_;
6845 print STDERR
"fail: missing script name\n
";
6848 print STDERR
"Running $script\n\n
";
6850 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6851 print STDERR
"success: firmware script ran succcessfully\n
";
6853 print STDERR
"fail: firmware script returned error\n
";
6857 sub run_firmware_scripts {
6858 my ($opts, @dirs) = @_;
6859 # Run firmware packages
6860 for my $dir (@dirs) {
6861 print STDERR
"info: Running scripts in $dir\n
";
6862 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6863 while (my $s = readdir $dh) {
6864 next if $s =~ m/^\.\.?/;
6865 run_firmware_script($opts,
"$dir/$s
");
6873 print STDERR
"info: Downloading $url\n
";
6874 system(
"wget --quiet \
"$url\
"");
6879 my $product = `dmidecode -s system-product-name`;
6882 if ($product =~ m/PowerEdge/) {
6884 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6885 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6887 my $tmpdir = tempdir(
6891 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6892 system(
'gunzip Catalog.xml.gz
');
6893 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6894 # -q is quiet, disabling interactivity and reducing console output
6895 my $fwopts =
"-q
";
6897 for my $url (@paths) {
6898 fetch_dell_fw($url);
6900 run_firmware_scripts($fwopts, $tmpdir);
6902 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6903 print STDERR
"error: Please report to $errorsto.\n
";
6907 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6908 print STDERR
"error: Please report to $errorsto.\n
";
6914 my $url =
"ftp://ftp.us.dell.com/$path
";
6918 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6919 # firmware packages to download from Dell. Only work for Linux
6920 # machines and
11th generation Dell servers.
6921 sub fetch_dell_fw_list {
6922 my $filename = shift;
6924 my $product = `dmidecode -s system-product-name`;
6926 my ($mybrand, $mymodel) = split(/\s+/, $product);
6928 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6930 my $xml = XMLin($filename);
6932 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6933 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6934 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6936 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6937 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6939 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6941 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6943 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6946 for my $component (@{$xml-
>{SoftwareComponent}}) {
6947 my $componenttype = $component-
>{ComponentType}-
>{value};
6949 # Drop application packages, only firmware and BIOS
6950 next if
'APAC
' eq $componenttype;
6952 my $cpath = $component-
>{path};
6953 for my $path (@paths) {
6954 if ($cpath =~ m%/$path$%) {
6955 push(@paths, $cpath);
6963 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6964 it could work on other platforms with some tweaking. Anyone know a
6965 index like Catalog.xml is available from HP for HP servers? At the
6966 moment I maintain a similar list manually and it is quickly getting
6972 <title>How is booting into runlevel
1 different from single user boots?
</title>
6973 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6974 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6975 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6976 <description><p
>Wouter Verhelst have some
6977 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6978 comments and opinions
</a
> on my blog post on
6979 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6980 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6981 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6982 default KDE desktop in Debian
</a
>. I only have time to address one
6983 small piece of his comment now, and though it best to address the
6984 misunderstanding he bring forward:
</p
>
6986 <p
><blockquote
>
6987 Currently, a system admin has four options: [...] boot to a
6988 single-user system (by adding
'single
' to the kernel command line;
6989 this runs rcS and rc1 scripts)
6990 </blockquote
></p
>
6992 <p
>This make me believe Wouter believe booting into single user mode
6993 and booting into runlevel
1 is the same. I am not surprised he
6994 believe this, because it would make sense and is a quite sensible
6995 thing to believe. But because the boot in Debian is slightly broken,
6996 runlevel
1 do not work properly and it isn
't the same as single user
6997 mode. I
'll try to explain what is actually happing, but it is a bit
6998 hard to explain.
</p
>
7000 <p
>Single user mode is defined like this in /etc/inittab:
7001 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
7002 executed in single user mode is sulogin. Single user mode is a boot
7003 state
"between
" the runlevels, and when booting into single user mode,
7004 only the scripts in /etc/rcS.d/ are executed before the init process
7005 enters the single user state. When switching to runlevel
1, the state
7006 is in fact not ending in runlevel
1, but it passes through runlevel
1
7007 and end up in the single user mode (see /etc/rc1.d/S03single, which
7008 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
7009 1. It is confusing that the
'S
' (single user) init mode is not the
7010 mode enabled by /etc/rcS.d/ (which is more like the initial boot
7013 <p
>This summary might make it clearer. When booting for the first
7014 time into single user mode, the following commands are executed:
7015 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
7016 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
7017 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
7018 trying to continue after visiting single user mode. Not all services
7019 are started again as they should, causing the machine to end up in an
7020 unpredicatble state. This is why Debian admins recommend rebooting
7021 after visiting single user mode.
</p
>
7023 <p
>A similar problem with runlevel
1 is caused by the amount of
7024 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
7025 to runlevel
1, the services started from /etc/rcS.d/ are not properly
7026 stopped when passing through the scripts in /etc/rc1.d/, and not
7027 started again when switching away from runlevel
1 to the runlevels
7028 2-
5. I believe the problem is best fixed by moving all the scripts
7029 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
7030 functioning single user mode during boot.
</p
>
7032 <p
>I have spent several years investigating the Debian boot system,
7033 and discovered this problem a few years ago. I suspect it originates
7034 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7039 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7040 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7042 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7043 <description><p
>In the Debian boot system, several packages include scripts that
7044 are started from /etc/rcS.d/. In fact, there is a bite more of them
7045 than make sense, and this causes a few problems. What kind of
7046 problems, you might ask. There are at least two problems. The first
7047 is that it is not possible to recover a machine after switching to
7048 runlevel
1. One need to actually reboot to get the machine back to
7049 the expected state. The other is that single user boot will sometimes
7050 run into problems because some of the subsystems are activated before
7051 the root login is presented, causing problems when trying to recover a
7052 machine from a problem in that subsystem. A minor additional point is
7053 that moving more scripts out of rcS.d/ and into the other rc#.d/
7054 directories will increase the amount of scripts that can run in
7055 parallel during boot, and thus decrease the boot time.
</p
>
7057 <p
>So, which scripts should start from rcS.d/. In short, only the
7058 scripts that _have_ to execute before the root login prompt is
7059 presented during a single user boot should go there. Everything else
7060 should go into the numeric runlevels. This means things like
7061 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7062 the numeric runlevels. Today in Debian, there are around
115 init.d
7063 scripts that are started from rcS.d/, and most of them should be moved
7064 out. Do your package have one of them? Please help us make single
7065 user and runlevel
1 better by moving it.
</p
>
7067 <p
>Scripts setting up the screen, keyboard, system partitions
7068 etc. should still be started from rcS.d/, but there is for example no
7069 need to have the network enabled before the single user login prompt
7070 is presented.
</p
>
7072 <p
>As always, things are not so easy to fix as they sound. To keep
7073 Debian systems working while scripts migrate and during upgrades, the
7074 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7075 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7076 and the next ones can only be moved when their dependencies have been
7077 moved first. This migration must be done sequentially while we ensure
7078 that the package system upgrade packages in the right order to keep
7079 the system state correct. This will require some coordination when it
7080 comes to network related packages, but most of the packages with
7081 scripts that should migrate do not have anything in rcS.d/ depending
7082 on them. Some packages have already been updated, like the sudo
7083 package, while others are still left to do. I wish I had time to work
7084 on this myself, but real live constrains make it unlikely that I will
7085 find time to push this forward.
</p
>
7090 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7091 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7092 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7093 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7094 <description><p
>While at Debconf11, I have several times during discussions
7095 mentioned the issues I believe should be improved in Debian for its
7096 desktop to be useful for more people. The use case for this is my
7097 parents, which are currently running Kubuntu which solve the
7100 <p
>I suspect these four missing features are not very hard to
7101 implement. After all, they are present in Ubuntu, so if we wanted to
7102 do this in Debian we would have a source.
</p
>
7106 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7107 are new packages available for upgrades, a icon in the KDE status bar
7108 indicate this, and clicking on it will activate the simple upgrade
7109 tool to handle it. I have no problem guiding both of my parents
7110 through the process over the phone. If a kernel reboot is required,
7111 this too is indicated by the status bars and the upgrade tool. Last
7112 time I checked, nothing with the same features was working in KDE in
7115 <li
><strong
>Simple handling of missing Firefox browser
7116 plugins.
</strong
> When the browser encounter a MIME type it do not
7117 currently have a handler for, it will ask the user if the system
7118 should search for a package that would add support for this MIME type,
7119 and if the user say yes, the APT sources will be searched for packages
7120 advertising the MIME type in their control file (visible in the
7121 Packages file in the APT archive). If one or more packages are found,
7122 it is a simple click of the mouse to add support for the missing mime
7123 type. If the package require the user to accept some non-free
7124 license, this is explained to the user. The entire process make it
7125 more clear to the user why something do not work in the browser, and
7126 make the chances higher for the user to blame the web page authors and
7127 not the browser for any missing features.
</li
>
7129 <li
><strong
>Simple handling of missing multimedia codec/format
7130 handlers.
</strong
> When the media players encounter a format or codec
7131 it is not supporting, a dialog pop up asking the user if the system
7132 should search for a package that would add support for it. This
7133 happen with things like MP3, Windows Media or H
.264. The selection
7134 and installation procedure is very similar to the Firefox browser
7135 plugin handling. This is as far as I know implemented using a
7136 gstreamer hook. The end result is that the user easily get access to
7137 the codecs that are present from the APT archives available, while
7138 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7140 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7141 displaying a text/plain file in my Debian browser, it will propose to
7142 start emacs to show it. If I remember correctly, when doing the same
7143 in Kunbutu it show the file as a text file in the browser. At least I
7144 know Opera will show text files within the browser. I much prefer the
7145 latter behaviour.
</li
>
7149 <p
>There are other nice features as well, like the simplified suite
7150 upgrader, but given that I am the one mostly doing the dist-upgrade,
7151 it do not matter much.
</p
>
7153 <p
>I really hope we could get these features in place for the next
7154 Debian release. It would require the coordinated effort of several
7155 maintainers, but would make the end user experience a lot better.
</p
>
7160 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7161 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7162 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7163 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7164 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7165 site is build on Debian/Squeeze, and this platform was chosen because
7166 I am most familiar with Debian (being a Debian Developer for around
10
7167 years) because it is the latest stable Debian release which should get
7168 security support for a few years.
</p
>
7170 <p
>The web service is written in Perl, and depend on some perl modules
7171 that are missing in Debian at the moment. It would be great if these
7172 modules were added to the Debian archive, allowing anyone to set up
7173 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7174 in their own country using only Debian packages. The list of modules
7175 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7176 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7177 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7178 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7179 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7180 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7181 easier in the future.
</p
>
7183 <p
>Thanks to the great tools in Debian, getting the missing modules
7184 installed on my server was a simple call to
'cpan2deb Module::Name
'
7185 and
'dpkg -i
' to install the resulting package. But this leave me
7186 with the responsibility of tracking security problems, which I really
7187 do not have time for.
</p
>
7192 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7193 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7194 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7195 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7196 <description><p
>Here is a small update for my English readers. Most of my blog
7197 posts have been in Norwegian the last few weeks, so here is a short
7198 update in English.
</p
>
7200 <p
>The kids still keep me too busy to get much free software work
7201 done, but I did manage to organise a project to get a Norwegian port
7202 of the British service
7203 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7204 and it has been running for a month now. The entire project has been
7205 organised by me and two others. Around Christmas we gathered sponsors
7206 to fund the development work. In January I drafted a contract with
7207 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7208 and in February the development took place. Most of it involved
7209 converting the source to use GPS coordinates instead of British
7210 easting/northing, and the resulting code should be a lot easier to get
7211 running in any country by now. The Norwegian
7212 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7213 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7214 source and the source for administrative borders in Norway, and
7215 support for this had to be added/fixed.
</p
>
7217 <p
>The Norwegian version went live March
3th, and we spent the weekend
7218 polishing the system before we announced it March
7th. The system is
7219 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7220 problem reports in a few weeks. Soon we hope to announce the Android
7221 and iPhone versions making it even easier to report problems with the
7222 public infrastructure.
</p
>
7224 <p
>Perhaps something to consider for those of you in countries without
7225 such service?
</p
>
7230 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7231 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7232 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7233 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7234 <description><p
>The last few days I have looked at ways to track open security
7235 issues here at my work with the University of Oslo. My idea is that
7236 it should be possible to use the information about security issues
7237 available on the Internet, and check our locally
7238 maintained/distributed software against this information. It should
7239 allow us to verify that no known security issues are forgotten. The
7240 CVE database listing vulnerabilities seem like a great central point,
7241 and by using the package lists from Debian mapped to CVEs provided by
7242 the testing security team, I believed it should be possible to figure
7243 out which security holes were present in our free software
7244 collection.
</p
>
7246 <p
>After reading up on the topic, it became obvious that the first
7247 building block is to be able to name software packages in a unique and
7248 consistent way across data sources. I considered several ways to do
7249 this, for example coming up with my own naming scheme like using URLs
7250 to project home pages or URLs to the Freshmeat entries, or using some
7251 existing naming scheme. And it seem like I am not the first one to
7252 come across this problem, as MITRE already proposed and implemented a
7253 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7254 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7255 software, hardware and other platform components. The CPE ids are
7256 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7257 Vulnerability Database
</a
>, allowing me to look up know security
7258 issues for any CPE name. With this in place, all I need to do is to
7259 locate the CPE id for the software packages we use at the university.
7260 This is fairly trivial (I google for
'cve cpe $package
' and check the
7261 NVD entry if a CVE for the package exist).
</p
>
7263 <p
>To give you an example. The GNU gzip source package have the CPE
7264 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7265 check out, one could look up
7266 <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
7267 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7268 The most recent one is
7269 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7270 and at the bottom of the NVD page for this vulnerability the complete
7271 list of affected versions is provided.
</p
>
7273 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7274 for offline processing of issues. Using this dump, I
've written a
7275 small script taking a list of CPEs as input and list all CVEs
7276 affecting the packages represented by these CPEs. One give it CPEs
7277 with version numbers as specified above and get a list of open
7278 security issues out.
</p
>
7280 <p
>Of course for this approach to be useful, the quality of the NVD
7281 information need to be high. For that to happen, I believe as many as
7282 possible need to use and contribute to the NVD database. I notice
7284 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7285 map from CVE to CPE
</a
>, indicating that they are using the CPE
7286 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7288 <p
>To get an idea about the quality for free software, I spent some
7289 time making it possible to compare the CVE database from Debian with
7290 the CVE database in NVD. The result look fairly good, but there are
7291 some inconsistencies in NVD (same software package having several
7292 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7293 Debian believe are affected by a CVE). Hope to find time to improve
7294 the quality of NVD, but that require being able to get in touch with
7295 someone maintaining it. So far my three emails with questions and
7296 corrections have not seen any reply, but I hope contact can be
7297 established soon.
</p
>
7299 <p
>An interesting application for CPEs is cross platform package
7300 mapping. It would be useful to know which packages in for example
7301 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7302 this would be trivial if all linux distributions provided CPE entries
7303 for their packages.
</p
>
7308 <title>Which module is loaded for a given PCI and USB device?
</title>
7309 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7310 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7311 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7312 <description><p
>In the
7313 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7314 package in Debian, there is a script to report useful information
7315 about the running hardware for use when people report missing
7316 information. One part of this script that I find very useful when
7317 debugging hardware problems, is the part mapping loaded kernel module
7318 to the PCI device it claims. It allow me to quickly see if the kernel
7319 module I expect is driving the hardware I am struggling with. To see
7320 the output, make sure discover-data is installed and run
7321 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7322 one of my machines like this:
</p
>
7326 10de:
03eb i2c_nforce2
7329 10de:
03f0 snd_hda_intel
7338 <p
>The code in question look like this, slightly modified for
7339 readability and to drop the output to file descriptor
3:
</p
>
7342 if [ -d /sys/bus/pci/devices/ ] ; then
7343 echo loaded pci modules:
7345 cd /sys/bus/pci/devices/
7346 for address in * ; do
7347 if [ -d
"$address/driver/module
" ] ; then
7348 module=`cd $address/driver/module ; pwd -P | xargs basename`
7349 if grep -q
"^$module
" /proc/modules ; then
7350 address=$(echo $address |sed s/
0000://)
7351 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7352 echo
"$id $module
"
7361 <p
>Similar code could be used to extract USB device module
7365 if [ -d /sys/bus/usb/devices/ ] ; then
7366 echo loaded usb modules:
7368 cd /sys/bus/usb/devices/
7369 for address in * ; do
7370 if [ -d
"$address/driver/module
" ] ; then
7371 module=`cd $address/driver/module ; pwd -P | xargs basename`
7372 if grep -q
"^$module
" /proc/modules ; then
7373 address=$(echo $address |sed s/
0000://)
7374 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7375 if [
"$id
" ] ; then
7376 echo
"$id $module
"
7386 <p
>This might perhaps be something to include in other tools as
7392 <title>How to test if a laptop is working with Linux
</title>
7393 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7394 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7395 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7396 <description><p
>The last few days I have spent at work here at the
<a
7397 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7398 batch of computers will work with Linux. Every year for the last few
7399 years the university have organised shared bid of a few thousand
7400 computers, and this year HP won the bid. Two different desktops and
7401 five different laptops are on the list this year. We in the UNIX
7402 group want to know which one of these computers work well with RHEL
7403 and Ubuntu, the two Linux distributions we currently handle at the
7404 university.
</p
>
7406 <p
>My test method is simple, and I share it here to get feedback and
7407 perhaps inspire others to test hardware as well. To test, I PXE
7408 install the OS version of choice, and log in as my normal user and run
7409 a few applications and plug in selected pieces of hardware. When
7410 something fail, I make a note about this in the test matrix and move
7411 on. If I have some spare time I try to report the bug to the OS
7412 vendor, but as I only have the machines for a short time, I rarely
7413 have the time to do this for all the problems I find.
</p
>
7415 <p
>Anyway, to get to the point of this post. Here is the simple tests
7416 I perform on a new model.
</p
>
7420 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7421 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7422 RHEL5 and Debian Edu/Squeeze.
</li
>
7424 <li
>Is X.org working? If the graphical login screen show up after
7425 installation, X.org is working.
</li
>
7427 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7428 package mesa-utils on Ubuntu) and writing down the frames per second
7429 reported by the program.
</li
>
7431 <li
>Is sound working? With Gnome and KDE, a sound is played when
7432 logging in, and if I can hear this the test is successful. If there
7433 are several audio exits on the machine, I try them all and check if
7434 the Gnome/KDE audio mixer can control where to send the sound. I
7435 normally test this by playing
7436 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7437 video
</a
> in Firefox/Iceweasel.
</li
>
7439 <li
>Is the USB subsystem working? I test this by plugging in a USB
7440 memory stick and see if Gnome/KDE notices this.
</li
>
7442 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7443 I have lying around, and see if Gnome/KDE notices this.
</li
>
7445 <li
>Is any built in camera working? Test using cheese, and see if a
7446 picture from the v4l device show up.
</li
>
7448 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7449 any bluetooth devices are discovered. In my office, I normally see a
7452 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7453 memory modules lying around, and stick them in and see if Gnome/KDE
7454 notice this.
</li
>
7456 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7457 special button work, and if the laptop continue to work after
7460 <li
>For laptops, is the extra buttons working, like audio level,
7461 adjusting background light, switching on/off external video output,
7462 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7463 laptop to laptop, so I just write down which are working and which are
7466 <li
>Some laptops have smart card readers, finger print readers,
7467 acceleration sensors etc. I rarely test these, as I do not know how
7468 to quickly test if they are working or not, so I only document their
7469 existence.
</li
>
7473 <p
>By now I suspect you are really curious what the test results are
7474 for the HP machines I am testing. I
'm not done yet, so I will report
7475 the test results later. For now I can report that HP
8100 Elite work
7476 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7477 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7478 can see, I have most machines left to test. One interesting
7479 observation is that Ubuntu Lucid has almost twice the frame rate than
7480 RHEL6 with glxgears. No idea why.
</p
>
7485 <title>Some thoughts on BitCoins
</title>
7486 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7487 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7488 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7489 <description><p
>As I continue to explore
7490 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7491 what properties the system have, and how it will be affected by laws
7492 and regulations here in Norway. Here are some random notes.
</p
>
7494 <p
>One interesting thing to note is that since the transactions are
7495 verified using a peer to peer network, all details about a transaction
7496 is known to everyone. This means that if a BitCoin address has been
7497 published like I did with mine in my initial post about BitCoin, it is
7498 possible for everyone to see how many BitCoins have been transfered to
7499 that address. There is even a web service to look at the details for
7500 all transactions. There I can see that my address
7501 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7502 have received
16.06 Bitcoin, the
7503 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7504 address of Simon Phipps have received
181.97 BitCoin and the address
7505 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7506 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7507 every one of you that donated bitcoins to support my activity. The
7508 fact that anyone can see how much money was transfered to a given
7509 address make it more obvious why the BitCoin community recommend to
7510 generate and hand out a new address for each transaction. I
'm told
7511 there is no way to track which addresses belong to a given person or
7512 organisation without the person or organisation revealing it
7513 themselves, as Simon, EFF and I have done.
</p
>
7515 <p
>In Norway, and in most other countries, there are laws and
7516 regulations limiting how much money one can transfer across the border
7517 without declaring it. There are money laundering, tax and accounting
7518 laws and regulations I would expect to apply to the use of BitCoin.
7519 If the Skolelinux foundation
7520 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7521 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7522 normal bank transfers like EFF is doing, how should this be accounted?
7523 Given that it is impossible to know if money can cross the border or
7524 not, should everything or nothing be declared? What exchange rate
7525 should be used when calculating taxes? Would receivers have to pay
7526 income tax if the foundation were to pay Skolelinux contributors in
7527 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7529 <p
>For a currency to be useful and successful, it must be trusted and
7530 accepted by a lot of users. It must be possible to get easy access to
7531 the currency (as a wage or using currency exchanges), and it must be
7532 easy to spend it. At the moment BitCoin seem fairly easy to get
7533 access to, but there are very few places to spend it. I am not really
7534 a regular user of any of the vendor types currently accepting BitCoin,
7535 so I wonder when my kind of shop would start accepting BitCoins. I
7536 would like to buy electronics, travels and subway tickets, not herbs
7537 and books. :) The currency is young, and this will improve over time
7538 if it become popular, but I suspect regular banks will start to lobby
7539 to get BitCoin declared illegal if it become popular. I
'm sure they
7540 will claim it is helping fund terrorism and money laundering (which
7541 probably would be true, as is any currency in existence), but I
7542 believe the problems should be solved elsewhere and not by blaming
7543 currencies.
</p
>
7545 <p
>The process of creating new BitCoins is called mining, and it is
7546 CPU intensive process that depend on a bit of luck as well (as one is
7547 competing against all the other miners currently spending CPU cycles
7548 to see which one get the next lump of cash). The
"winner
" get
50
7549 BitCoin when this happen. Yesterday I came across the obvious way to
7550 join forces to increase ones changes of getting at least some coins,
7551 by coordinating the work on mining BitCoins across several machines
7552 and people, and sharing the result if one is lucky and get the
50
7554 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7555 if this sounds interesting. I have not had time to try to set up a
7556 machine to participate there yet, but have seen that running on ones
7557 own for a few days have not yield any BitCoins througth mining
7560 <p
>Update
2010-
12-
15: Found an
<a
7561 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7562 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7563 it was interesting to read. The arguments presented seem to be
7564 equally valid for gold, which was used as a currency for many years.
</p
>
7569 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7570 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7571 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7572 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7573 <description><p
>With this weeks lawless
7574 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7575 attacks
</a
> on Wikileak and
7576 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7577 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7578 not be trusted to handle money transactions.
7580 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7581 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7582 mine mentioned earlier. I decided to follow Simon
's example, and get
7583 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7584 some help from my friend to get it all running, and he even handed me
7585 some bitcoins to get started. I even donated a few bitcoins to Simon
7586 for helping me remember BitCoin.
</p
>
7588 <p
>So, what is bitcoins, you probably wonder? It is a digital
7589 crypto-currency, decentralised and handled using peer-to-peer
7590 networks. It allows anonymous transactions and prohibits central
7591 control over the transactions, making it impossible for governments
7592 and companies alike to block donations and other transactions. The
7593 source is free software, and while the key dependency wxWidgets
2.9
7594 for the graphical user interface is missing in Debian, the command
7595 line client builds just fine. Hopefully Jonas
7596 <a href=
"http://bugs.debian.org/
578157">will get the package into
7597 Debian
</a
> soon.
</p
>
7599 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7600 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7601 bitcoins
</a
> when selling services and goods, and there are even
7602 currency
"stock
" markets where the exchange rate is decided. There
7603 are not many users so far, but the concept seems promising. If you
7604 want to get started and lack a friend with any bitcoins to spare,
7606 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7607 bitcoin at the time of writing). Use
7608 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7609 on the current exchange rates.
</p
>
7611 <p
>As an experiment, I have decided to set up bitcoind on one of my
7612 machines. If you want to support my activity, please send Bitcoin
7613 donations to the address
7614 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7619 <title>Why isn
't Debian Edu using VLC?
</title>
7620 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7621 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7622 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7623 <description><p
>In the latest issue of Linux Journal, the readers choices were
7624 presented, and the winner among the multimedia player were VLC.
7625 Personally, I like VLC, and it is my player of choice when I first try
7626 to play a video file or stream. Only if VLC fail will I drag out
7627 gmplayer to see if it can do better. The reason is mostly the failure
7628 model and trust. When VLC fail, it normally pop up a error message
7629 reporting the problem. When mplayer fail, it normally segfault or
7630 just hangs. The latter failure mode drain my trust in the program.
<p
>
7632 <p
>But even if VLC is my player of choice, we have choosen to use
7633 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7634 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7635 plugin to play web videos seamlessly, and the VLC browser plugin is
7636 not very good. For example, it lack in-line control buttons, so there
7637 is no way for the user to pause the video. Also, when I
7638 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7639 tested the browser plugins
</a
> available in Debian, the VLC plugin
7640 failed on several video pages where mplayer based plugins worked. If
7641 the browser plugin for VLC was as good as the gecko-mediaplayer
7642 package (which uses mplayer), we would switch.
</P
>
7644 <p
>While VLC is a good player, its user interface is slightly
7645 annoying. The most annoying feature is its inconsistent use of
7646 keyboard shortcuts. When the player is in full screen mode, its
7647 shortcuts are different from when it is playing the video in a window.
7648 For example, space only work as pause when in full screen mode. I
7649 wish it had consisten shortcuts and that space also would work when in
7650 window mode. Another nice shortcut in gmplayer is [enter] to restart
7651 the current video. It is very nice when playing short videos from the
7652 web and want to restart it when new people arrive to have a look at
7653 what is going on.
</p
>
7658 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7659 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7660 <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>
7661 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7662 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7663 upgrade testing of the
7664 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7665 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7666 This seem like a very good idea, so I adjusted by test scripts and
7667 can now present the updated result from today:
</p
>
7669 <p
>This is for Gnome:
</p
>
7671 <p
>Installed using apt-get, missing with aptitude
</p
>
7673 <blockquote
><p
>
7678 browser-plugin-gnash
7685 freedesktop-sound-theme
7687 gconf-defaults-service
7702 gnome-desktop-environment
7706 gnome-session-canberra
7711 gstreamer0.10-fluendo-mp3
7717 libapache2-mod-dnssd
7720 libaprutil1-dbd-sqlite3
7723 libboost-date-time1.42
.0
7724 libboost-python1.42
.0
7725 libboost-thread1.42
.0
7727 libchamplain-gtk-
0.4-
0
7729 libclutter-gtk-
0.10-
0
7736 libfreerdp-plugins-standard
7751 libgnomepanel2.24-cil
7756 libgtksourceview2.0-common
7757 libmono-addins-gui0.2-cil
7758 libmono-addins0.2-cil
7759 libmono-cairo2.0-cil
7760 libmono-corlib2.0-cil
7761 libmono-i18n-west2.0-cil
7762 libmono-posix2.0-cil
7763 libmono-security2.0-cil
7764 libmono-sharpzip2.84-cil
7765 libmono-system2.0-cil
7768 libndesk-dbus-glib1.0-cil
7769 libndesk-dbus1.0-cil
7779 libtelepathy-farsight0
7788 nautilus-sendto-empathy
7792 python-aptdaemon-gtk
7794 python-beautifulsoup
7809 python-gtksourceview2
7820 python-pkg-resources
7827 python-twisted-conch
7833 python-zope.interface
7838 rhythmbox-plugin-cdrecorder
7845 system-config-printer-udev
7847 telepathy-mission-control-
5
7858 </p
></blockquote
>
7860 <p
>Installed using apt-get, removed with aptitude
</p
>
7862 <blockquote
><p
>
7868 fast-user-switch-applet
7887 libgtksourceview2.0-
0
7889 libsdl1.2debian-alsa
7895 system-config-printer
7900 </p
></blockquote
>
7902 <p
>Installed using aptitude, missing with apt-get
</p
>
7904 <blockquote
><p
>
7905 gstreamer0.10-gnomevfs
7906 </p
></blockquote
>
7908 <p
>Installed using aptitude, removed with apt-get
</p
>
7910 <blockquote
><p
>
7912 </p
></blockquote
>
7914 <p
>This is for KDE:
</p
>
7916 <p
>Installed using apt-get, missing with aptitude
</p
>
7918 <blockquote
><p
>
7920 </p
></blockquote
>
7922 <p
>Installed using apt-get, removed with aptitude
</p
>
7924 <blockquote
><p
>
7927 </p
></blockquote
>
7929 <p
>Installed using aptitude, missing with apt-get
</p
>
7931 <blockquote
><p
>
7945 kdeartwork-emoticons
7947 kdeartwork-theme-icon
7951 kdebase-workspace-bin
7952 kdebase-workspace-data
7966 kscreensaver-xsavers
7981 plasma-dataengines-workspace
7983 plasma-desktopthemes-artwork
7984 plasma-runners-addons
7985 plasma-scriptengine-googlegadgets
7986 plasma-scriptengine-python
7987 plasma-scriptengine-qedje
7988 plasma-scriptengine-ruby
7989 plasma-scriptengine-webkit
7990 plasma-scriptengines
7991 plasma-wallpapers-addons
7992 plasma-widget-folderview
7993 plasma-widget-networkmanagement
7997 xscreensaver-data-extra
7999 xscreensaver-gl-extra
8000 xscreensaver-screensaver-bsod
8001 </p
></blockquote
>
8003 <p
>Installed using aptitude, removed with apt-get
</p
>
8005 <blockquote
><p
>
8007 google-gadgets-common
8025 libggadget-qt-
1.0-
0b
8030 libkonqsidebarplugin4a
8039 libplasma-geolocation-interface4
8041 libplasmagenericshell4
8055 libsmokeknewstuff2-
3
8056 libsmokeknewstuff3-
3
8058 libsmokektexteditor3
8066 libsmokeqtnetwork4-
3
8072 libsmokeqtuitools4-
3
8084 plasma-dataengines-addons
8085 plasma-scriptengine-superkaramba
8086 plasma-widget-lancelot
8087 plasma-widgets-addons
8088 plasma-widgets-workspace
8092 update-notifier-common
8093 </p
></blockquote
>
8095 <p
>Running apt-get autoremove made the results using apt-get and
8096 aptitude a bit more similar, but there are still quite a lott of
8097 differences. I have no idea what packages should be installed after
8098 the upgrade, but hope those that do can have a look.
</p
>
8103 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8104 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8105 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8106 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8107 <description><p
>Most of the computers in use by the
8108 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8109 are virtual machines. And they have been Xen machines running on a
8110 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8111 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8112 bit harder that it could have been, because we set up the Xen virtual
8113 machines to get the virtual partitions from LVM, which as far as I
8114 know is not supported by KVM. So to migrate, we had to convert
8115 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8118 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8119 nice recipe
</a
> to do this, and wrote the following script to do the
8120 migration. It uses qemu-img from the qemu package to make the disk
8121 image, parted to partition it, losetup and kpartx to present the disk
8122 image partions as devices, and dd to copy the data. I NFS mounted the
8123 new servers storage area on the old server to do the migration.
</p
>
8129 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8134 if [ -z
"$
1" ] ; then
8135 echo
"Usage: $
0 &lt;hostname
&gt;
"
8141 if [ ! -e /dev/vg_data/$host-disk ] ; then
8142 echo
"error: unable to find LVM volume for $host
"
8146 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8147 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8148 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8149 totalsize=$(( ( $disksize + $swapsize ) ))
8152 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8153 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8155 parted $img mklabel msdos
8156 parted $img mkpart primary linux-swap
0 $disksize
8157 parted $img mkpart primary ext2 $disksize $totalsize
8158 parted $img set
1 boot on
8161 losetup /dev/loop0 $img
8162 kpartx -a /dev/loop0
8164 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8165 fsck.ext3 -f /dev/mapper/loop0p1 || true
8166 mkswap /dev/mapper/loop0p2
8168 kpartx -d /dev/loop0
8169 losetup -d /dev/loop0
8172 <p
>The script is perhaps so simple that it is not copyrightable, but
8173 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8175 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8176 the new disk image attached, installed grub-pc and linux-image-
686 and
8177 set up grub to boot from the disk image. After this, the KVM machines
8178 seem to work just fine.
</p
>
8183 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8184 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8185 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8186 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8187 <description><p
>I
'm still running upgrade testing of the
8188 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8189 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8190 status. Here is a short update based on a test I ran
20101118.
</p
>
8192 <p
>I still do not know what a correct migration should look like, so I
8193 report any differences between apt and aptitude and hope someone else
8194 can see if anything should be changed.
</p
>
8196 <p
>This is for Gnome:
</p
>
8198 <p
>Installed using apt-get, missing with aptitude
</p
>
8200 <blockquote
><p
>
8201 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8202 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8203 dmz-cursor-theme empathy empathy-common finger
8204 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8205 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8206 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8207 gnome-cards-data gnome-codec-install gnome-core
8208 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8209 gnome-search-tool gnome-session-canberra gnome-spell
8210 gnome-system-log gnome-themes-extras gnome-themes-more
8211 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8212 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8213 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8214 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8215 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8216 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8217 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8218 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8219 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8220 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8221 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8222 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8223 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8224 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8225 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8226 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8227 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8228 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8229 libmono-security2.0-cil libmono-sharpzip2.84-cil
8230 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8231 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8232 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8233 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8234 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8235 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8236 libxalan2-java libxerces2-java media-player-info mesa-utils
8237 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8238 nautilus-sendto-empathy openoffice.org-writer2latex
8239 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8240 python-aptdaemon python-aptdaemon-gtk python-axiom
8241 python-beautifulsoup python-bugbuddy python-clientform
8242 python-coherence python-configobj python-crypto python-cupshelpers
8243 python-cupsutils python-eggtrayicon python-elementtree
8244 python-epsilon python-evolution python-feedparser python-gdata
8245 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8246 python-gtksourceview2 python-httplib2 python-louie python-mako
8247 python-markupsafe python-mechanize python-nevow python-notify
8248 python-opengl python-openssl python-pam python-pkg-resources
8249 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8250 python-tagpy python-twisted-bin python-twisted-conch
8251 python-twisted-core python-twisted-web python-utidylib python-webkit
8252 python-xdg python-zope.interface remmina remmina-plugin-data
8253 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8254 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8255 software-center svgalibg1 system-config-printer-udev
8256 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8257 totem totem-coherence totem-mozilla totem-plugins
8258 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8260 </p
></blockquote
>
8262 Installed using apt-get, removed with aptitude
8264 <blockquote
><p
>
8265 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8266 epiphany-extensions epiphany-gecko evolution-exchange
8267 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8268 gedit-common gnome-app-install gnome-games gnome-games-data
8269 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8270 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8271 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8272 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8273 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8274 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8275 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8276 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8277 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8278 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8279 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8280 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8281 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8282 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8283 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8284 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8285 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8286 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8287 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8288 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8289 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8290 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8291 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8292 sound-juicer swfdec-gnome system-config-printer totem-common
8293 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8294 </p
></blockquote
>
8296 <p
>Installed using aptitude, missing with apt-get
</p
>
8298 <blockquote
><p
>
8299 gstreamer0.10-gnomevfs
8300 </p
></blockquote
>
8302 <p
>Installed using aptitude, removed with apt-get
</p
>
8304 <blockquote
><p
>
8306 </p
></blockquote
>
8308 <p
>This is for KDE:
</p
>
8310 <p
>Installed using apt-get, missing with aptitude
</p
>
8312 <blockquote
><p
>
8313 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8314 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8315 ghostscript-x git gnome-audio gnugo granatier gs-common
8316 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8317 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8318 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8319 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8320 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8321 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8322 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8323 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8324 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8325 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8326 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8327 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8328 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8329 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8330 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8331 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8332 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8333 libkrossui4 libmailtools-perl libmime-tools-perl
8334 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8335 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8336 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8337 lirc luatex marble networkstatus noatun-plugins
8338 openoffice.org-writer2latex palapeli palapeli-data parley
8339 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8340 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8341 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8343 </p
></blockquote
>
8345 <p
>Installed using apt-get, removed with aptitude
</p
>
8347 <blockquote
><p
>
8348 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8349 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8350 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8351 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8352 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8353 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8354 kitchensync kiten kjumpingcube klatin klettres klickety klines
8355 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8356 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8357 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8358 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8359 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8360 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8361 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8362 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8363 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8364 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8365 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8366 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8367 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8368 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8369 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8370 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8371 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8372 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8373 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8374 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8375 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8376 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8377 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8378 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8379 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8380 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8381 </p
></blockquote
>
8383 <p
>Installed using aptitude, missing with apt-get
</p
>
8385 <blockquote
><p
>
8386 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8387 kdeartwork kdebase kdebase-apps kdebase-workspace
8388 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8389 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8390 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8391 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8392 xscreensaver-screensaver-bsod
8393 </p
></blockquote
>
8395 <p
>Installed using aptitude, removed with apt-get
</p
>
8397 <blockquote
><p
>
8398 kdebase-bin konq-plugins konqueror
8399 </p
></blockquote
>
8404 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8405 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8406 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8407 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8408 <description><p
>Answering
8409 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8410 call from the Gnash project
</a
> for
8411 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8412 current source, I have set up a virtual KVM machine on the Debian
8413 Edu/Skolelinux virtualization host to test the git source on
8414 Debian/Squeeze. I hope this can help the developers in getting new
8415 releases out more often.
</p
>
8417 <p
>As the developers want less main-stream build platforms tested to,
8418 I have considered setting up a
<a
8419 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8420 machine as well. I have also considered using the kfreebsd
8421 architecture in Debian as a file server in NUUG to get access to the
5
8422 TB zfs volume we currently use to store DV video. Because of this, I
8423 finally got around to do a test installation of Debian/Squeeze with
8424 kfreebsd. Installation went fairly smooth, thought I noticed some
8425 visual glitches in the cdebconf dialogs (black cursor left on the
8426 screen at random locations). Have not gotten very far with the
8427 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8428 fatal problem. Have to spend some more time on it to see if it is
8429 useful as a file server for NUUG. Will try to find time to set up a
8430 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8435 <title>Debian in
3D
</title>
8436 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8437 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8438 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8439 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8441 <p
>3D printing is just great. I just came across this Debian logo in
8443 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8444 thingiverse blog
</a
>.
</p
>
8449 <title>Software updates
2010-
10-
24</title>
8450 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8451 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8452 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8453 <description><p
>Some updates.
</p
>
8455 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8456 raise money for the project is going well. The lower limit of
10
8457 signers was reached in
24 hours, and so far
13 people have signed it.
8458 More signers and more funding is most welcome, and I am really curious
8459 how far we can get before the time limit of December
24 is reached.
8462 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8463 about what appear to be a great code coverage tool capable of
8464 generating code coverage stats without any changes to the source code.
8466 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8467 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8468 It is missing in Debian, but the git source built just fine in Squeeze
8469 after I installed libelf-dev, libdwarf-dev, pkg-config and
8470 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8471 solvable. I hope kcov make it into Debian soon.
</p
>
8473 <p
>Finally found time to wrap up the release notes for
<a
8474 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8475 new alpha release of Debian Edu
</a
>, and just published the second
8476 alpha test release of the Squeeze based Debian Edu /
8477 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8478 release. Give it a try if you need a complete linux solution for your
8479 school, including central infrastructure server, workstations, thin
8480 client servers and diskless workstations. A nice touch added
8481 yesterday is RDP support on the thin client servers, for windows
8482 clients to get a Linux desktop on request.
</p
>
8487 <title>Some notes on Flash in Debian and Debian Edu
</title>
8488 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8489 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8490 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8491 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8492 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8493 second most popular used package that is missing in Debian. The sixth
8494 most popular is flashplayer-mozilla. This is a clear indication that
8495 working flash is important for Debian users. Around
10 percent of the
8496 users submitting data to popcon.debian.org have this package
8497 installed.
</p
>
8499 <p
>In the report written by Lars Risan in August
2008
8500 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8501 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8502 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8503 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8504 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8505 web sites require Flash to work, and lacking working Flash support in
8506 the web browser and the problems with installing it was perceived as a
8507 good reason to stay with Windows.
</p
>
8509 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8510 said to be the retarded cousin that did not really understand
8511 everything you told him but could work fairly well. This was a
8512 comment regarding the problems Linux have with proprietary formats and
8513 non-standard web pages, and is sad because it exposes a fairly common
8514 understanding of whose fault it is if web pages that only work in for
8515 example Internet Explorer
6 fail to work on Firefox, and funny because
8516 it explain very well how annoying it is for users when Linux
8517 distributions do not work with the documents they receive or the web
8518 pages they want to visit.
</p
>
8520 <p
>This is part of the reason why I believe it is important for Debian
8521 and Debian Edu to have a well working Flash implementation in the
8522 distribution, to get at least popular sites as Youtube and Google
8523 Video to working out of the box. For Squeeze, Debian have the chance
8524 to include the latest version of Gnash that will make this happen, as
8525 the new release
0.8.8 was published a few weeks ago and is resting in
8526 unstable. The new version work with more sites that version
0.8.7.
8527 The Gnash maintainers have asked for a freeze exception, but the
8528 release team have not had time to reply to it yet. I hope they agree
8529 with me that Flash is important for the Debian desktop users, and thus
8530 accept the new package into Squeeze.
</p
>
8535 <title>Circular package dependencies harms apt recovery
</title>
8536 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8537 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8538 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8539 <description><p
>I discovered this while doing
8540 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8541 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8542 in Debian still got circular dependencies, and it is often claimed
8543 that apt and aptitude should be able to handle this just fine, but
8544 some times these dependency loops causes apt to fail.
</p
>
8546 <p
>An example is from todays
8547 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8548 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8549 causes perl-modules to fail to upgrade. The cause is simple. If a
8550 package fail to unpack, then only part of packages with the circular
8551 dependency might end up being unpacked when unpacking aborts, and the
8552 ones already unpacked will fail to configure in the recovery phase
8553 because its dependencies are unavailable.
</p
>
8555 <p
>In this log, the problem manifest itself with this error:
</p
>
8557 <blockquote
><pre
>
8558 dpkg: dependency problems prevent configuration of perl-modules:
8559 perl-modules depends on perl (
>=
5.10.1-
1); however:
8560 Version of perl on system is
5.10.0-
19lenny
2.
8561 dpkg: error processing perl-modules (--configure):
8562 dependency problems - leaving unconfigured
8563 </pre
></blockquote
>
8565 <p
>The perl/perl-modules circular dependency is already
8566 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8567 hopefully be solved as soon as possible, but it is not the only one,
8568 and each one of these loops in the dependency tree can cause similar
8569 failures. Of course, they only occur when there are bugs in other
8570 packages causing the unpacking to fail, but it is rather nasty when
8571 the failure of one package causes the problem to become worse because
8572 of dependency loops.
</p
>
8575 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8576 tireless effort by Bill Allombert
</a
>, the number of circular
8578 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8579 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8581 <p
>Todays testing also exposed a bug in
8582 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8583 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8584 apt-get and aptitude, the latter possibly caused by some circular
8585 dependency. Reported both to BTS to try to get someone to look at
8591 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8592 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8593 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8594 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8595 <description><p
>This is a
8596 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8598 <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
8600 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8601 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8603 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8604 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8605 and dhcp3-server-ldap in Debian use the LDAP server. The two
8606 implementations are quite different in how they use LDAP.
</p
>
8608 To get this information, I started slapd with debugging enabled and
8609 dumped the debug output to a file to get the LDAP searches performed
8610 on a Debian Edu main-server. Here is a summary.
8612 <p
><strong
>powerdns
</strong
></p
>
8614 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8615 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8618 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8619 One
"strict
" mode where the forward and reverse DNS lookups are done
8620 using the same LDAP objects, and a
"tree
" mode where the forward and
8621 reverse entries are in two different subtrees in LDAP with a structure
8622 based on the DNS names, as in tjener.intern and
8623 2.2.0.10.in-addr.arpa.
</p
>
8625 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8626 base, and uses a
"base
" scoped search for the DNS name by adding
8627 "dc=tjener,dc=intern,
" to the base with a filter for
8628 "(associateddomain=tjener.intern)
" for the forward entry and
8629 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8630 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8631 forward entries, it is looking for attributes named dnsttl, arecord,
8632 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8633 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8634 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8635 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8636 spfrecord and modifytimestamp. For reverse entries it is looking for
8637 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8638 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8639 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8640 ldapsearch commands could look like this:
</p
>
8642 <blockquote
><pre
>
8643 ldapsearch -h ldap \
8644 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8645 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8646 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8647 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8648 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8649 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8651 ldapsearch -h ldap \
8652 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8653 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8654 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8655 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8656 srvrecord naptrrecord modifytimestamp
8657 </pre
></blockquote
>
8659 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8660 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8661 example LDAP objects used there. In addition to these objects, the
8662 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8663 also exist.
</p
>
8665 <blockquote
><pre
>
8666 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8668 objectclass: dnsdomain
8669 objectclass: domainrelatedobject
8672 associateddomain: tjener.intern
8674 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8676 objectclass: dnsdomain2
8677 objectclass: domainrelatedobject
8679 ptrrecord: tjener.intern
8680 associateddomain:
2.2.0.10.in-addr.arpa
8681 </pre
></blockquote
>
8683 <p
>In strict mode, the server behaves differently. When looking for
8684 forward DNS entries, it is doing a
"subtree
" scoped search with the
8685 same base as in the tree mode for a object with filter
8686 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8687 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8688 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8689 naptrrecord and modifytimestamp. For reverse entires it also do a
8690 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8691 and the requested attributes are associateddomain, dnsttl and
8692 modifytimestamp. In short, in strict mode the objects with ptrrecord
8693 go away, and the arecord attribute in the forward object is used
8696 <p
>The forward and reverse searches can be simulated using ldapsearch
8697 like this:
</p
>
8699 <blockquote
><pre
>
8700 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8701 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8702 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8703 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8704 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8705 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8707 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8708 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8709 </pre
></blockquote
>
8711 <p
>In addition to the forward and reverse searches , there is also a
8712 search for SOA records, which behave similar to the forward and
8713 reverse lookups.
</p
>
8715 <p
>A thing to note with the PowerDNS behaviour is that it do not
8716 specify any objectclass names, and instead look for the attributes it
8717 need to generate a DNS reply. This make it able to work with any
8718 objectclass that provide the needed attributes.
</p
>
8720 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8721 dnsdomain2 schemas. The latter is used for reverse entries like
8722 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8724 <p
>In Debian Edu, we have created DNS objects using the object classes
8725 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8726 attributes) and domainrelatedobject (for associatedDomain). The use
8727 of structural object classes make it impossible to combine these
8728 classes with the object classes used by DHCP.
</p
>
8730 <p
>There are other schemas that could be used too, for example the
8731 dnszone structural object class used by Gosa and bind-sdb for the DNS
8732 attributes combined with the domainrelatedobject object class, but in
8733 this case some unused attributes would have to be included as well
8734 (zonename and relativedomainname).
</p
>
8736 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8737 mode and not use any of the existing objectclasses (dnsdomain,
8738 dnsdomain2 and dnszone) when one want to combine the DNS information
8739 with DHCP information, and instead create a auxiliary object class
8740 defined something like this (using the attributes defined for
8741 dnsdomain and dnsdomain2 or dnszone):
</p
>
8743 <blockquote
><pre
>
8744 objectclass ( some-oid NAME
'dnsDomainAux
'
8747 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8748 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8749 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8750 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8751 A6Record $ DNAMERecord
8753 </pre
></blockquote
>
8755 <p
>This will allow any object to become a DNS entry when combined with
8756 the domainrelatedobject object class, and allow any entity to include
8757 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8758 developers asking for their view on this schema and if they are
8759 interested in providing such schema with PowerDNS, and I hope my
8760 message will be accepted into their mailing list soon.
</p
>
8762 <p
><strong
>ISC dhcp
</strong
></p
>
8764 <p
>The DHCP server searches for specific objectclass and requests all
8765 the object attributes, and then uses the attributes it want. This
8766 make it harder to figure out exactly what attributes are used, but
8767 thanks to the working example in Debian Edu I can at least get an idea
8768 what is needed without having to read the source code.
</p
>
8770 <p
>In the DHCP server configuration, the LDAP base to use and the
8771 search filter to use to locate the correct dhcpServer entity is
8772 stored. These are the relevant entries from
8773 /etc/dhcp3/dhcpd.conf:
</p
>
8775 <blockquote
><pre
>
8776 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8777 ldap-dhcp-server-cn
"dhcp
";
8778 </pre
></blockquote
>
8780 <p
>The DHCP server uses this information to nest all the DHCP
8781 configuration it need. The cn
"dhcp
" is located using the given LDAP
8782 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8783 search result is this entry:
</p
>
8785 <blockquote
><pre
>
8786 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8789 objectClass: dhcpServer
8790 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8791 </pre
></blockquote
>
8793 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8794 subtree with DHCP configuration. The DHCP configuration subtree base
8795 is located using a base scope search with base
"cn=DHCP
8796 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8797 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8798 The search result is this entry:
</p
>
8800 <blockquote
><pre
>
8801 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8804 objectClass: dhcpService
8805 objectClass: dhcpOptions
8806 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8807 dhcpStatements: ddns-update-style none
8808 dhcpStatements: authoritative
8809 dhcpOption: smtp-server code
69 = array of ip-address
8810 dhcpOption: www-server code
72 = array of ip-address
8811 dhcpOption: wpad-url code
252 = text
8812 </pre
></blockquote
>
8814 <p
>Next, the entire subtree is processed, one level at the time. When
8815 all the DHCP configuration is loaded, it is ready to receive requests.
8816 The subtree in Debian Edu contain objects with object classes
8817 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8818 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8819 and information about netmasks, dynamic range etc. Leaving out the
8820 details here because it is not relevant for the focus of my
8821 investigation, which is to see if it is possible to merge dns and dhcp
8822 related computer objects.
</p
>
8824 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8825 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8826 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8827 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8828 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8831 <blockquote
><pre
>
8832 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8835 objectClass: dhcpHost
8836 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8837 dhcpStatements: fixed-address hostname
8838 </pre
></blockquote
>
8840 <p
>There is less flexiblity in the way LDAP searches are done here.
8841 The object classes need to have fixed names, and the configuration
8842 need to be stored in a fairly specific LDAP structure. On the
8843 positive side, the invidiual dhcpHost entires can be anywhere without
8844 the DN pointed to by the dhcpServer entries. The latter should make
8845 it possible to group all host entries in a subtree next to the
8846 configuration entries, and this subtree can also be shared with the
8847 DNS server if the schema proposed above is combined with the dhcpHost
8848 structural object class.
8850 <p
><strong
>Conclusion
</strong
></p
>
8852 <p
>The PowerDNS implementation seem to be very flexible when it come
8853 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8854 come to the the LDAP structure, the
"strict
" mode is very flexible,
8855 allowing DNS objects to be stored anywhere under the base cn specified
8856 in the configuration.
</p
>
8858 <p
>The DHCP implementation on the other hand is very inflexible, both
8859 regarding which LDAP schemas to use and which LDAP structure to use.
8860 I guess one could implement ones own schema, as long as the
8861 objectclasses and attributes have the names used, but this do not
8862 really help when the DHCP subtree need to have a fairly fixed
8863 structure.
</p
>
8865 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8866 this might work for Debian Edu:
</p
>
8868 <blockquote
><pre
>
8870 cn=machine-info (dhcpService) - dhcpServiceDN points here
8871 cn=dhcp (dhcpServer)
8872 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8873 cn=
10.0.2.0 (dhcpSubnet)
8874 cn=group1 (dhcpGroup/dhcpOptions)
8875 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8876 cn=
192.168.0.0 (dhcpSubnet)
8877 cn=group1 (dhcpGroup/dhcpOptions)
8878 ou=machines - PowerDNS base points here
8879 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8880 </pre
></blockquote
>
8882 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8883 entries to be in the dhcpGroup subtrees, the entries can be stored
8884 there instead of a common machines subtree, and the PowerDNS base
8885 would have to be moved one level up to the machine-info subtree.
</p
>
8887 <p
>The combined object under the machines subtree would look something
8888 like this:
</p
>
8890 <blockquote
><pre
>
8891 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8894 objectClass: dhcpHost
8895 objectclass: domainrelatedobject
8896 objectclass: dnsDomainAux
8897 associateddomain: hostname.intern
8898 arecord:
10.11.12.13
8899 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8900 dhcpStatements: fixed-address hostname.intern
8901 </pre
></blockquote
>
8903 </p
>One could even add the LTSP configuration associated with a given
8904 machine, as long as the required attributes are available in a
8905 auxiliary object class.
</p
>
8910 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8911 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8912 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8913 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8914 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8915 DHCP services in Debian Edu to use the same LDAP objects for a given
8916 computer, to avoid the possibility of having a inconsistent state for
8917 a computer in LDAP (as in DHCP but no DNS entry or the other way
8918 around) and make it easier to add computers to LDAP.
</p
>
8920 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8921 information finally found a solution that seem to work.
</p
>
8923 <p
>The old setup required three LDAP objects for a given computer.
8924 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8925 we switch powerdns to use its strict LDAP method (ldap-method=strict
8926 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8927 merged into one while making it impossible to transfer the reverse map
8928 to a slave DNS server.
</p
>
8930 <p
>If we also replace the object class used to get the DNS related
8931 attributes to one allowing these attributes to be combined with the
8932 dhcphost object class, we can merge the DNS and DHCP entries into one.
8933 I
've written such object class in the dnsdomainaux.schema file (need
8934 proper OIDs, but that is a minor issue), and tested the setup. It
8935 seem to work.
</p
>
8937 <p
>With this test setup in place, we can get away with one LDAP object
8938 for both DNS and DHCP, and even the LTSP configuration I suggested in
8939 an earlier email. The combined LDAP object will look something like
8942 <blockquote
><pre
>
8943 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8945 objectClass: dhcphost
8946 objectclass: domainrelatedobject
8947 objectclass: dnsdomainaux
8948 associateddomain: hostname.intern
8949 arecord:
10.11.12.13
8950 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8951 dhcpstatements: fixed-address hostname
8953 </pre
></blockquote
>
8955 <p
>The DNS server uses the associateddomain and arecord entries, while
8956 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8957 before asking DNS to resolve the fixed-adddress. LTSP will use
8958 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8960 <p
>I am not yet sure if I can get the DHCP server to look for its
8961 dhcphost in a different location, to allow us to put the objects
8962 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8963 that. If I can
't figure out a way to do that, we can still get rid of
8964 the hosts subtree and move all its content into the DHCP Config tree
8965 (which probably should be renamed to be more related to the new
8966 content. I suspect cn=dnsdhcp,ou=services or something like that
8967 might be a good place to put it.
</p
>
8969 <p
>If you want to help out with implementing this for Debian Edu,
8970 please contact us on debian-edu@lists.debian.org.
</p
>
8975 <title>Idea for storing LTSP configuration in LDAP
</title>
8976 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8977 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8978 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8979 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8980 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8981 clients, and that this can be used to fetch configuration from LDAP if
8982 Debian Edu choose to store configuration there.
</p
>
8984 <p
>Armed with this information, I got inspired and wrote a test module
8985 to get configuration from LDAP. The idea is to look up the MAC
8986 address of the client in LDAP, and look for attributes on the form
8987 ltspconfigsetting=value, and use this to export SETTING=value to the
8988 LTSP clients.
</p
>
8990 <p
>The goal is to be able to store the LTSP configuration attributes
8991 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8992 allowing us to store all information about a computer in one place.
</p
>
8994 <p
>This is a untested draft implementation, and I welcome feedback on
8995 this approach. A real LDAP schema for the ltspClientAux objectclass
8996 need to be written. Comments, suggestions, etc?
</p
>
8998 <blockquote
><pre
>
8999 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
9001 # Fetch LTSP client settings from LDAP based on MAC address
9003 # Uses ethernet address as stored in the dhcpHost objectclass using
9004 # the dhcpHWAddress attribute or ethernet address stored in the
9005 # ieee802Device objectclass with the macAddress attribute.
9007 # This module is written to be schema agnostic, and only depend on the
9008 # existence of attribute names.
9010 # The LTSP configuration variables are saved directly using a
9011 # ltspConfig prefix and uppercasing the rest of the attribute name.
9012 # To set the SERVER variable, set the ltspConfigServer attribute.
9014 # Some LDAP schema should be created with all the relevant
9015 # configuration settings. Something like this should work:
9017 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
9020 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
9022 LDAPSERVER=$(debian-edu-ldapserver)
9023 if [
"$LDAPSERVER
" ] ; then
9024 LDAPBASE=$(debian-edu-ldapserver -b)
9025 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
9026 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
9027 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
9028 grep
'^ltspConfig
' | while read attr value ; do
9029 # Remove prefix and convert to upper case
9030 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
9031 # bass value on to clients
9032 eval
"$attr=$value; export $attr
"
9036 </pre
></blockquote
>
9038 <p
>I
'm not sure this shell construction will work, because I suspect
9039 the while block might end up in a subshell causing the variables set
9040 there to not show up in ltsp-config, but if that is the case I am sure
9041 the code can be restructured to make sure the variables are passed on.
9042 I expect that can be solved with some testing. :)
</p
>
9044 <p
>If you want to help out with implementing this for Debian Edu,
9045 please contact us on debian-edu@lists.debian.org.
</p
>
9047 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9048 configuration in LDAP that was created around year
2000 by
9049 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9050 Xperience, Inc.,
2000</a
>. I found its
9051 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9052 personal home page over at redhat.com.
</p
>
9057 <title>jXplorer, a very nice LDAP GUI
</title>
9058 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9059 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9060 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9061 <description><p
>Since
9062 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9063 last post
</a
> about available LDAP tools in Debian, I was told about a
9064 LDAP GUI that is even better than luma. The java application
9065 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9066 moving LDAP objects and subtrees using drag-and-drop, and can
9067 authenticate using Kerberos. I have only tested the Kerberos
9068 authentication, but do not have a LDAP setup allowing me to rewrite
9069 LDAP with my test user yet. It is
9070 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9071 Debian
</a
> testing and unstable at the moment. The only problem I
9072 have with it is how it handle errors. If something go wrong, its
9073 non-intuitive behaviour require me to go through some query work list
9074 and remove the failing query. Nothing big, but very annoying.
</p
>
9079 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9080 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9081 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9082 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9083 <description><p
>Here is a short update on my
<a
9084 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9085 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9086 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9087 not reporting the status for KDE, because the upgrade crashes when
9088 aptitude try because of missing conflicts
9089 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9090 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9092 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9093 complete list of the installed packages. Based on this I see these
9094 differences when I did a test run today. As usual, I do not really
9095 know what the correct set of packages would be, but thought it best to
9096 publish the difference.
</p
>
9098 <p
>Installed using apt-get, missing with aptitude
</p
>
9100 <blockquote
><p
>
9101 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9102 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9103 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9104 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9105 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9106 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9107 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9108 python-gtkmozembed svgalibg1 xserver-xephyr zip
9109 </p
></blockquote
>
9111 <p
>Installed using apt-get, removed with aptitude
</p
>
9113 <blockquote
><p
>
9114 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9115 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9116 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9117 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9118 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9119 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9120 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9121 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9122 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9123 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9124 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9125 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9126 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9127 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9128 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9129 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9130 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9131 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9132 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9133 mysql-common swfdec-gnome totem-gstreamer wodim
9134 </p
></blockquote
>
9136 <p
>Installed using aptitude, missing with apt-get
</p
>
9138 <blockquote
><p
>
9139 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9140 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9141 xserver-xorg-input-all xserver-xorg-input-evdev
9142 xserver-xorg-input-kbd xserver-xorg-input-mouse
9143 xserver-xorg-input-synaptics xserver-xorg-video-all
9144 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9145 xserver-xorg-video-chips xserver-xorg-video-cirrus
9146 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9147 xserver-xorg-video-glint xserver-xorg-video-i128
9148 xserver-xorg-video-i740 xserver-xorg-video-mach64
9149 xserver-xorg-video-mga xserver-xorg-video-neomagic
9150 xserver-xorg-video-nouveau xserver-xorg-video-nv
9151 xserver-xorg-video-r128 xserver-xorg-video-radeon
9152 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9153 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9154 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9155 xserver-xorg-video-sis xserver-xorg-video-sisusb
9156 xserver-xorg-video-tdfx xserver-xorg-video-tga
9157 xserver-xorg-video-trident xserver-xorg-video-tseng
9158 xserver-xorg-video-vesa xserver-xorg-video-vmware
9159 xserver-xorg-video-voodoo
9160 </p
></blockquote
>
9162 <p
>Installed using aptitude, removed with apt-get
</p
>
9164 <blockquote
><p
>
9165 deskbar-applet xserver-xorg xserver-xorg-core
9166 xserver-xorg-input-wacom xserver-xorg-video-intel
9167 xserver-xorg-video-openchrome
9168 </p
></blockquote
>
9170 <p
>I was told on IRC that the xorg-xserver package was
9171 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9172 in git
</a
> today to try to get apt-get to not remove xorg completely.
9173 No idea when it hits Squeeze, but when it does I hope it will reduce
9174 the difference somewhat.
9179 <title>LUMA, a very nice LDAP GUI
</title>
9180 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9181 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9182 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9183 <description><p
>The last few days I have been looking into the status of the LDAP
9184 directory in Debian Edu, and in the process I started to miss a GUI
9185 tool to browse the LDAP tree. The only one I was able to find in
9186 Debian/Squeeze and Lenny is
9187 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9188 be a great tool to get a overview of the current LDAP directory
9189 populated by default in Skolelinux. Thanks to it, I have been able to
9190 find empty and obsolete subtrees, misplaced objects and duplicate
9191 objects. It will be installed by default in Debian/Squeeze. If you
9192 are working with LDAP, give it a go. :)
</p
>
9194 <p
>I did notice one problem with it I have not had time to report to
9195 the BTS yet. There is no .desktop file in the package, so the tool do
9196 not show up in the Gnome and KDE menus, but only deep down in in the
9197 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9200 <p
>I have not yet been able to get it to modify the tree yet. I would
9201 like to move objects and remove subtrees directly in the GUI, but have
9202 not found a way to do that with LUMA yet. So in the mean time, I use
9203 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9205 <p
>If you have tips on other GUI tools for LDAP that might be useful
9206 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9208 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9209 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9210 useful GUI alternative. It seem like a good tool, but is unmaintained
9211 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9212 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9217 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9218 <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>
9219 <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>
9220 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9221 <description><p
>A while back, I
9222 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9223 about the fact
</a
> that it is not possible with the provided schemas
9224 for storing DNS and DHCP information in LDAP to combine the two sets
9225 of information into one LDAP object representing a computer.
</p
>
9227 <p
>In the mean time, I discovered that a simple fix would be to make
9228 the dhcpHost object class auxiliary, to allow it to be combined with
9229 the dNSDomain object class, and thus forming one object for one
9230 computer when storing both DHCP and DNS information in LDAP.
</p
>
9232 <p
>If I understand this correctly, it is not safe to do this change
9233 without also changing the assigned number for the object class, and I
9234 do not know enough about LDAP schema design to do that properly for
9235 Debian Edu.
</p
>
9237 <p
>Anyway, for future reference, this is how I believe we could change
9239 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9240 schema
</a
> to solve at least part of the problem with the LDAP schemas
9241 available today from IETF.
</p
>
9244 --- dhcp.schema (revision
65192)
9245 +++ dhcp.schema (working copy)
9247 objectclass (
2.16.840.1.113719.1.203.6.6
9248 NAME
'dhcpHost
'
9249 DESC
'This represents information about a particular client
'
9253 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9254 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9257 <p
>I very much welcome clues on how to do this properly for Debian
9258 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9259 package, and should thus be free to rewrite it as we see fit.
</p
>
9261 <p
>If you want to help out with implementing this for Debian Edu,
9262 please contact us on debian-edu@lists.debian.org.
</p
>
9267 <title>Calling tasksel like the installer, while still getting useful output
</title>
9268 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9270 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9271 <description><p
>A few times I have had the need to simulate the way tasksel
9272 installs packages during the normal debian-installer run. Until now,
9273 I have ended up letting tasksel do the work, with the annoying problem
9274 of not getting any feedback at all when something fails (like a
9275 conffile question from dpkg or a download that fails), using code like
9278 <blockquote
><pre
>
9279 export DEBIAN_FRONTEND=noninteractive
9280 tasksel --new-install
9281 </pre
></blockquote
>
9283 This would invoke tasksel, let its automatic task selection pick the
9284 tasks to install, and continue to install the requested tasks without
9285 any output what so ever.
9287 Recently I revisited this problem while working on the automatic
9288 package upgrade testing, because tasksel would some times hang without
9289 any useful feedback, and I want to see what is going on when it
9290 happen. Then it occured to me, I can parse the output from tasksel
9291 when asked to run in test mode, and use that aptitude command line
9292 printed by tasksel then to simulate the tasksel run. I ended up using
9295 <blockquote
><pre
>
9296 export DEBIAN_FRONTEND=noninteractive
9297 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9299 </pre
></blockquote
>
9301 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9302 --without-recommends -o APT::Install-Recommends=no -y install
9303 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9304 ~pimportant
</tt
>", which will install the gnome desktop task, the
9305 laptop task and all packages with priority standard , required and
9306 important, just like tasksel would have done it during
9307 installation.
</p
>
9309 <p
>A better approach is probably to extend tasksel to be able to
9310 install packages without using debconf-apt-progress, for use cases
9311 like this.
</p
>
9316 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9317 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9318 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9319 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9320 <description><p
>My
9321 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9322 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9323 finally made the upgrade logs available from
9324 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9325 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9326 apt and aptitude, and found their differences interesting. This time
9327 I will only focus on their removal plans.
</p
>
9329 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9330 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9331 surprising part is that it want to remove xorg and all
9332 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9333 sure why. When asking aptitude to do the same, it want to remove
129
9334 packages, but most of them are library packages I suspect are no
9335 longer needed. Both of them want to remove bluetooth packages, which
9336 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9338 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9339 which seem like a bad idea and xorg the same way as with Gnome. Asking
9340 aptitude for the same, it wants to remove
192 packages, none which are
9341 too surprising.
</p
>
9343 <p
>I guess the removal of xorg during upgrades should be investigated
9344 and avoided, and perhaps others as well. Here are the complete list
9345 of planned removals. The complete logs is available from the URL
9346 above. Note if you want to repeat these tests, that the upgrade test
9347 for kde+apt-get hung in the tasksel setup because of dpkg asking
9348 conffile questions. No idea why. I worked around it by using
9349 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9352 <p
><b
>apt-get gnome
72</b
>
9353 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9354 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9355 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9356 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9357 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9358 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9359 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9360 xserver-xorg-input-kbd xserver-xorg-input-mouse
9361 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9362 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9363 xserver-xorg-video-ati xserver-xorg-video-chips
9364 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9365 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9366 xserver-xorg-video-glint xserver-xorg-video-i128
9367 xserver-xorg-video-i740 xserver-xorg-video-imstt
9368 xserver-xorg-video-intel xserver-xorg-video-mach64
9369 xserver-xorg-video-mga xserver-xorg-video-neomagic
9370 xserver-xorg-video-nsc xserver-xorg-video-nv
9371 xserver-xorg-video-openchrome xserver-xorg-video-r128
9372 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9373 xserver-xorg-video-rendition xserver-xorg-video-s3
9374 xserver-xorg-video-s3virge xserver-xorg-video-savage
9375 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9376 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9377 xserver-xorg-video-tga xserver-xorg-video-trident
9378 xserver-xorg-video-tseng xserver-xorg-video-v4l
9379 xserver-xorg-video-vesa xserver-xorg-video-vga
9380 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9381 xulrunner-
1.9-gnome-support
</p
>
9383 <p
><b
>aptitude gnome
129</b
>
9385 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9386 djvulibre-desktop finger gnome-app-install gnome-mount
9387 gnome-network-admin gnome-spell gnome-vfs-obexftp
9388 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9389 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9390 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9391 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9392 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9393 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9394 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9395 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9396 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9397 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9398 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9399 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9400 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9401 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9402 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9403 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9404 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9405 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9406 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9407 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9408 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9409 openoffice.org-writer2latex openssl-blacklist p7zip
9410 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9411 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9412 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9413 swfdec-mozilla totem-gstreamer update-manager wodim
9414 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9415 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9418 <p
><b
>apt-get kde
82</b
>
9420 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9421 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9422 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9423 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9424 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9425 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9426 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9427 xserver-xorg-input-kbd xserver-xorg-input-mouse
9428 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9429 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9430 xserver-xorg-video-ati xserver-xorg-video-chips
9431 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9432 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9433 xserver-xorg-video-glint xserver-xorg-video-i128
9434 xserver-xorg-video-i740 xserver-xorg-video-imstt
9435 xserver-xorg-video-intel xserver-xorg-video-mach64
9436 xserver-xorg-video-mga xserver-xorg-video-neomagic
9437 xserver-xorg-video-nsc xserver-xorg-video-nv
9438 xserver-xorg-video-openchrome xserver-xorg-video-r128
9439 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9440 xserver-xorg-video-rendition xserver-xorg-video-s3
9441 xserver-xorg-video-s3virge xserver-xorg-video-savage
9442 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9443 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9444 xserver-xorg-video-tga xserver-xorg-video-trident
9445 xserver-xorg-video-tseng xserver-xorg-video-v4l
9446 xserver-xorg-video-vesa xserver-xorg-video-vga
9447 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9449 <p
><b
>aptitude kde
192</b
>
9450 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9451 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9452 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9453 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9454 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9455 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9456 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9457 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9458 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9459 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9460 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9461 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9462 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9463 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9464 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9465 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9466 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9467 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9468 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9469 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9470 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9471 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9472 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9473 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9474 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9475 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9476 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9477 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9478 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9479 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9480 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9481 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9482 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9483 texlive-common texlive-doc-base texlive-fonts-recommended
9484 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9485 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9486 xulrunner-
1.9</p
>
9492 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9493 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9494 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9495 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9496 <description><p
>The last few days I have done some upgrade testing in Debian, to
9497 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9498 have been discovered and reported in the process
9499 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9500 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9501 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9502 kdebase-workspace-data), and to get a more regular testing going on, I
9503 am working on a script to automate the test.
</p
>
9505 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9506 Gnome or KDE desktop installation inside the chroot before upgrading
9507 it. To ensure no services are started in the chroot, a policy-rc.d
9508 script is inserted. To make sure tasksel believe it is to install a
9509 desktop on a laptop, the tasksel tests are replaced in the chroot
9510 (only acceptable because this is a throw-away chroot).
</p
>
9512 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9513 currently always fail because udev refuses to upgrade with the kernel
9514 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9515 is created. The bug report
9516 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9517 this problem do not trigger in a chroot, but I touch the file anyway
9518 to make sure the upgrade go well. Testing on virtual and real
9519 hardware have failed me because of udev so far, and creating this file
9520 do the trick in such settings anyway. This is a
9521 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9522 issue
</a
> and the current udev behaviour is intended by the udev
9523 maintainer because he lack the resources to rewrite udev to keep
9524 working with old kernels or something like that. I really wish the
9525 udev upstream would keep udev backwards compatible, to avoid such
9526 upgrade problem, but given that they fail to do so, I guess
9527 documenting the way out of this mess is the best option we got for
9528 Debian Squeeze.
</p
>
9530 <p
>Anyway, back to the task at hand, testing upgrades. This test
9531 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9534 <blockquote
><pre
>
9538 if [
"$
1" ] ; then
9547 exec
&lt; /dev/null
9549 mirror=http://ftp.skolelinux.org/debian
9550 tmpdir=chroot-$from-upgrade-$to-$desktop
9552 debootstrap $from $tmpdir $mirror
9553 chroot $tmpdir aptitude update
9554 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9558 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9562 mount -t proc proc $tmpdir/proc
9563 # Make sure proc is unmounted also on failure
9564 trap exit_cleanup EXIT INT
9566 chroot $tmpdir aptitude -y install debconf-utils
9568 # Make sure tasksel autoselection trigger. It need the test scripts
9569 # to return the correct answers.
9570 echo tasksel tasksel/desktop multiselect $desktop | \
9571 chroot $tmpdir debconf-set-selections
9573 # Include the desktop and laptop task
9574 for test in desktop laptop ; do
9575 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9579 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9582 DEBIAN_FRONTEND=noninteractive
9583 DEBIAN_PRIORITY=critical
9584 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9585 chroot $tmpdir tasksel --new-install
9587 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9588 chroot $tmpdir aptitude update
9589 touch $tmpdir/etc/udev/kernel-upgrade
9590 chroot $tmpdir aptitude -y dist-upgrade
9592 </pre
></blockquote
>
9594 <p
>I suspect it would be useful to test upgrades with both apt-get and
9595 with aptitude, but I have not had time to look at how they behave
9596 differently so far. I hope to get a cron job running to do the test
9597 regularly and post the result on the web. The Gnome upgrade currently
9598 work, while the KDE upgrade fail because of the bug in
9599 kdebase-workspace-data
</p
>
9601 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9602 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9603 post, so I will refrain from trying. I can report that for Gnome,
9604 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9605 remove and
1 not upgraded and
1024MB need to be downloaded while for
9606 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9607 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9609 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9610 is able to migrate to dependency based boot sequencing and parallel
9611 booting without a hitch. Was unsure if there were still bugs with
9612 packages failing to clean up their obsolete init.d script during
9613 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9619 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9620 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9621 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9622 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9623 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9624 scripts to migrate (some of) their operations to upstart job while
9625 keeping the init.d for hurd and kfreebsd. The packages with such
9626 needs will need a way to get their init.d scripts to behave
9627 differently when used with sysvinit and with upstart. Because of
9628 this, I had a look at the environment variables set when a init.d
9629 script is running under upstart, and when it is not.
</p
>
9631 <p
>With upstart, I notice these environment variables are set when a
9632 script is started from rcS.d/ (ignoring some irrelevant ones like
9635 <blockquote
><pre
>
9641 UPSTART_EVENTS=startup
9643 UPSTART_JOB=rc-sysinit
9644 </pre
></blockquote
>
9646 <p
>With sysvinit, these environment variables are set for the same
9649 <blockquote
><pre
>
9650 INIT_VERSION=sysvinit-
2.88
9655 </pre
></blockquote
>
9657 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9658 sysvinit are not set by upstart. Not sure if it is intentional or not
9659 to not be compatible with sysvinit in this regard.
</p
>
9661 <p
>For scripts needing to behave differently when upstart is used,
9662 looking for the UPSTART_JOB environment variable seem to be a good
9668 <title>A manual for standards wars...
</title>
9669 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9670 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9671 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9672 <description><p
>Via the
9673 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9674 of Rob Weir
</a
> I came across the very interesting essay named
9675 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9676 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9677 following the standards wars of today.
</p
>
9682 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9683 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9685 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9686 <description><p
>When using sitesummary at a site to track machines, it is possible
9687 to get a list of the machine types in use thanks to the DMI
9688 information extracted from each machine. The script to do so is
9689 included in the sitesummary package, and here is example output from
9690 the Skolelinux build servers:
</p
>
9692 <blockquote
><pre
>
9693 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9695 Dell Computer Corporation
1
9698 eserver xSeries
345 -[
8670M1X]-
1
9702 </pre
></blockquote
>
9704 <p
>The quality of the report depend on the quality of the DMI tables
9705 provided in each machine. Here there are Intel machines without model
9706 information listed with Intel as vendor and no model, and virtual Xen
9707 machines listed as [no-dmi-info]. One can add -l as a command line
9708 option to list the individual machines.
</p
>
9710 <p
>A larger list is
9711 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9712 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9713 provide the basic sitesummary report publicly. In their report there
9714 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9715 their machines, and as sitesummary is available in both distributions,
9716 it is trivial to get all of them to report to the same central
9717 collector.
</p
>
9722 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9723 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9724 <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>
9725 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9726 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9727 start at boot when an NVidia video card is used is handled. The
9728 problem seem to be that the nvidia X.org driver uses a long time to
9729 initialize, and this duration is longer than kdm is configured to
9732 <p
>I came across two bugs related to this issue,
9733 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9734 against initscripts and passed on to nvidia-glx when it became obvious
9735 that the nvidia drivers were involved, and
9736 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9737 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9739 <p
>To me, it seem that no-one is interested in actually solving the
9740 problem nvidia video card owners experience and make sure the Debian
9741 distribution work out of the box for these users. The nvidia driver
9742 maintainers expect kdm to be set up to wait longer, while kdm expect
9743 the nvidia driver maintainers to fix the driver to start faster, and
9744 while they wait for each other I guess the users end up switching to a
9745 distribution that work for them. I have no idea what the solution is,
9746 but I am pretty sure that waiting for each other is not it.
</p
>
9748 <p
>I wonder why we end up handling bugs this way.
</p
>
9753 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9754 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9755 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9756 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9757 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9758 The feature seem to hold up pretty well, but three fairly serious
9759 issues are known and should be solved:
9763 <li
>The wicd package seen to
9764 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9765 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9766 parallel booting is enabled. No idea why, but the wicd maintainer
9767 seem to be on the case.
</li
>
9769 <li
>The nvidia X driver seem to
9770 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9771 triggered more easily when parallel booting is in effect. The
9772 maintainer is on the case.
</li
>
9774 <li
>The sysv-rc package fail to properly enable dependency based boot
9775 sequencing (the shutdown is broken) when old file-rc users
9776 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9777 sysv-rc. One way to solve it would be for file-rc to create
9778 /etc/init.d/.legacy-bootordering, and another is to try to make
9779 sysv-rc more robust. Will investigate some more and probably upload a
9780 workaround in sysv-rc to help those trying to move from file-rc to
9781 sysv-rc get a working shutdown.
</li
>
9783 </ul
></p
>
9785 <p
>All in all not many surprising issues, and all of them seem
9786 solvable before Squeeze is released. In addition to these there are
9787 some packages with bugs in their dependencies and run level settings,
9788 which I expect will be fixed in a reasonable time span.
</p
>
9790 <p
>If you report any problems with dependencies in init.d scripts to
9791 the BTS, please usertag the report to get it to show up at
9792 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9793 list of usertagged bugs related to this
</a
>.
</p
>
9795 <p
>Update: Correct bug number to file-rc issue.
</p
>
9800 <title>More flexible firmware handling in debian-installer
</title>
9801 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9802 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9803 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9804 <description><p
>After a long break from debian-installer development, I finally
9805 found time today to return to the project. Having to spend less time
9806 working dependency based boot in debian, as it is almost complete now,
9807 definitely helped freeing some time.
</p
>
9809 <p
>A while back, I ran into a problem while working on Debian Edu. We
9810 include some firmware packages on the Debian Edu CDs, those needed to
9811 get disk and network controllers working. Without having these
9812 firmware packages available during installation, it is impossible to
9813 install Debian Edu on the given machine, and because our target group
9814 are non-technical people, asking them to provide firmware packages on
9815 an external medium is a support pain. Initially, I expected it to be
9816 enough to include the firmware packages on the CD to get
9817 debian-installer to find and use them. This proved to be wrong.
9818 Next, I hoped it was enough to symlink the relevant firmware packages
9819 to some useful location on the CD (tried /cdrom/ and
9820 /cdrom/firmware/). This also proved to not work, and at this point I
9821 found time to look at the debian-installer code to figure out what was
9822 going to work.
</p
>
9824 <p
>The firmware loading code is in the hw-detect package, and a closer
9825 look revealed that it would only look for firmware packages outside
9826 the installation media, so the CD was never checked for firmware
9827 packages. It would only check USB sticks, floppies and other
9828 "external
" media devices. Today I changed it to also look in the
9829 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9830 solve the problem I ran into with Debian edu. I also changed it to
9831 look in /firmware/, to make sure the installer also find firmware
9832 provided in the initrd when booting the installer via PXE, to allow us
9833 to provide the same feature in the PXE setup included in Debian
9836 <p
>To make sure firmware deb packages with a license questions are not
9837 activated without asking if the license is accepted, I extended
9838 hw-detect to look for preinst scripts in the firmware packages, and
9839 run these before activating the firmware during installation. The
9840 license question is asked using debconf in the preinst, so this should
9841 solve the issue for the firmware packages I have looked at so far.
</p
>
9843 <p
>If you want to discuss the details of these features, please
9844 contact us on debian-boot@lists.debian.org.
</p
>
9849 <title>Parallellized boot is now the default in Debian/unstable
</title>
9850 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9851 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9852 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9853 <description><p
>Since this evening, parallel booting is the default in
9854 Debian/unstable for machines using dependency based boot sequencing.
9855 Apparently the testing of concurrent booting has been wider than
9856 expected, if I am to believe the
9857 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9858 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9859 with the feature this weekend, to give us some time to detect any
9860 remaining problems before Squeeze is frozen. If serious problems are
9861 detected, it is simple to change the default back to sequential boot.
9862 The upload of the new sysvinit package also activate a new upstream
9865 More information about
9866 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9867 based boot sequencing
</a
> is available from the Debian wiki. It is
9868 currently possible to disable parallel booting when one run into
9869 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9871 <blockquote
><pre
>
9873 </pre
></blockquote
>
9875 <p
>If you report any problems with dependencies in init.d scripts to
9876 the BTS, please usertag the report to get it to show up at
9877 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9878 list of usertagged bugs related to this
</a
>.
</p
>
9883 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9884 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9885 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9886 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9887 <description><p
>In the recent Debian Edu versions, the
9888 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9889 system
</a
> is used to keep track of the machines in the school
9890 network. Each machine will automatically report its status to the
9891 central server after boot and once per night. The network setup is
9892 also reported, and using this information it is possible to get the
9893 MAC address of all network interfaces in the machines. This is useful
9894 to update the DHCP configuration.
</p
>
9896 <p
>To give some idea how to use sitesummary, here is a one-liner to
9897 ist all MAC addresses of all machines reporting to sitesummary. Run
9898 this on the collector host:
</p
>
9900 <blockquote
><pre
>
9901 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9902 </pre
></blockquote
>
9904 <p
>This will list all MAC addresses assosiated with all machine, one
9905 line per machine and with space between the MAC addresses.
</p
>
9907 <p
>To allow system administrators easier job at adding static DHCP
9908 addresses for hosts, it would be possible to extend this to fetch
9909 machine information from sitesummary and update the DHCP and DNS
9910 tables in LDAP using this information. Such tool is unfortunately not
9911 written yet.
</p
>
9916 <title>systemd, an interesting alternative to upstart
</title>
9917 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9918 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9919 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9920 <description><p
>The last few days a new boot system called
9921 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9923 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9925 to the free software world. I have not yet had time to play around
9926 with it, but it seem to be a very interesting alternative to
9927 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9928 a good alternative for Debian when we are able to switch to an event
9929 based boot system. Tollef is
9930 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9931 systemd into Debian, and I look forward to seeing how well it work. I
9932 like the fact that systemd handles init.d scripts with dependency
9933 information natively, allowing them to run in parallel where upstart
9934 at the moment do not.
</p
>
9936 <p
>Unfortunately do systemd have the same problem as upstart regarding
9937 platform support. It only work on recent Linux kernels, and also need
9938 some new kernel features enabled to function properly. This means
9939 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9940 system. Not sure how that will be handled if systemd proves to be the
9941 way forward.
</p
>
9943 <p
>In the mean time, based on the
9944 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9945 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9946 decided to enable full parallel booting as the default in Debian as
9947 soon as possible (probably this weekend or early next week), to see if
9948 there are any remaining serious bugs in the init.d dependencies. A
9949 new version of the sysvinit package implementing this change is
9950 already in experimental. If all go well, Squeeze will be released
9951 with parallel booting enabled by default.
</p
>
9956 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9957 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9958 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9959 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9960 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9961 complete, so complete that it is actually possible to run all the
9962 init.d scripts in parallell based on these dependencies. If you want
9963 to test your Squeeze system, make sure
9964 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9965 based boot sequencing
</a
> is enabled, and add this line to
9966 /etc/default/rcS:
</p
>
9968 <blockquote
><pre
>
9969 CONCURRENCY=makefile
9970 </pre
></blockquote
>
9972 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9973 scripts in parallel using the dependency information stored in
9974 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9975 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9976 to try to start the kdm and gdm scripts as early as possible, and will
9977 start the facilities required by kdm or gdm as early as possible to
9978 make this happen.
</p
>
9980 <p
>Give it a try, and see if you like the result. If some services
9981 fail to start properly, it is most likely because they have incomplete
9982 init.d script dependencies in their startup script (or some of their
9983 dependent scripts have incomplete dependencies). Report bugs and get
9984 the package maintainers to fix it. :)
</p
>
9986 <p
>Running scripts in parallel could be the default in Debian when we
9987 manage to get the init.d script dependencies complete and correct. I
9988 expect we will get there in Squeeze+
1, if we get manage to test and
9989 fix the remaining issues.
</p
>
9991 <p
>If you report any problems with dependencies in init.d scripts to
9992 the BTS, please usertag the report to get it to show up at
9993 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9994 list of usertagged bugs related to this
</a
>.
</p
>
9999 <title>Debian has switched to dependency based boot sequencing
</title>
10000 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
10001 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
10002 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
10003 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
10004 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
10005 have been migrated to using dependency based boot sequencing. This
10006 conclude work me and others have been doing for the last three days.
10007 It feels great to see this finally part of the default Debian
10008 installation. Now we just need to weed out the last few problems that
10009 are bound to show up, to get everything ready for Squeeze.
</p
>
10011 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
10012 fixing the more fundamental problem of handing the event based
10013 non-predictable kernel in the early boot.
</p
>
10018 <title>Taking over sysvinit development
</title>
10019 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
10020 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
10021 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
10022 <description><p
>After several years of frustration with the lack of activity from
10023 the existing sysvinit upstream developer, I decided a few weeks ago to
10024 take over the package and become the new upstream. The number of
10025 patches to track for the Debian package was becoming a burden, and the
10026 lack of synchronization between the distribution made it hard to keep
10027 the package up to date.
</p
>
10029 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
10030 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
10031 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
10032 and Fedora), based on the patches currently in use in these
10033 distributions. We Debian maintainers plan to move to this tarball as
10034 the new upstream as soon as we find time to do the merge. Since the
10035 new tarball was created, we agreed with Werner at SuSe to make a new
10036 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10037 development there. The project is registered and currently waiting
10038 for approval by the Savannah administrators, and as soon as it is
10039 approved, we will import the old versions from svn and continue
10040 working on the future release.
</p
>
10042 <p
>It is a bit ironic that this is done now, when some of the involved
10043 distributions are moving to upstart as a syvinit replacement.
</p
>
10048 <title>Debian boots quicker and quicker
</title>
10049 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10050 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10051 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10052 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10053 people involved in the boot system on Debian and Ubuntu, to see if we
10054 could find more ways to speed up the boot system. This was an Ubuntu
10056 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10057 gathering
</a
>. It was quite productive. We also discussed the future
10058 of boot systems, and ways to handle the increasing number of boot
10059 issues introduced by the Linux kernel becoming more and more
10060 asynchronous and event base. The Ubuntu approach using udev and
10061 upstart might be a good way forward. Time will show.
</p
>
10063 <p
>Anyway, there are a few ways at the moment to speed up the boot
10064 process in Debian. All of these should be applied to get a quick
10069 <li
>Use dash as /bin/sh.
</li
>
10071 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10072 clock is in UTC.
</li
>
10074 <li
>Install and activate the insserv package to enable
10075 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10076 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10080 These points are based on the Google summer of code work done by
10081 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10082 Villegas
</a
>.
10084 <p
>Support for makefile-style concurrency during boot was uploaded to
10085 unstable yesterday. When we tested it, we were able to cut
6 seconds
10086 from the boot sequence. It depend on very correct dependency
10087 declaration in all init.d scripts, so I expect us to find edge cases
10088 where the dependences in some scripts are slightly wrong when we start
10089 using this.
</p
>
10091 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10092 introduced by Raphael Geissert today, one that could affect the
10093 startup speed as well. Instead of starting some scripts concurrently
10094 from rcS.d/ and another set of scripts from rc2.d/, it would be
10095 possible to run a of them in the same process. A quick way to test
10096 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10097 insserv
'. Will need to test if that work. :)
</p
>
10102 <title>BSAs påstander om piratkopiering møter motstand
</title>
10103 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10104 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10105 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10106 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10107 programvareselskapene som Microsoft og Apple, publisert en rapport der
10108 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10109 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10111 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10112 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10113 dagene. Et spesielt interessant kommentar fra Sverige,
10114 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10115 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10118 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10119 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10120 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10121 exakta
", säger BSAs Sverigechef John Hugosson.
10122 </blockquote
>
10124 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10125 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10126 piracy figures need a shot of reality
</a
> og
<a
10127 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10128 Copyright Treaty Work?
</a
></p
>
10130 <p
>Fant lenkene via
<a
10131 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10132 på Slashdot
</a
>.
</p
>
10137 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10138 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10139 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10140 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10141 <description><p
>Kom over
10142 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10143 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10144 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10145 jobber til daglig. En rask opptelling forteller meg at vi har
490
10146 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10147 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10148 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10153 <title>Kryptert harddisk - naturligvis
</title>
10154 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10155 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10156 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10157 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10158 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10159 når en tar tap av arbeidstid, fortrolige dokumenter,
10160 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10161 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10162 til at jeg har kryptert harddisken på både kontormaskinen og min
10163 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10164 komme på avveie, den første informasjon relatert til jobben min ved
10165 Universitetet i Oslo, og den andre relatert til blant annet
10166 foreningsarbeide. Kryptering av diskene gjør at det er lite
10167 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10168 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10169 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10170 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10171 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10172 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10173 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10174 det er gjort slik jeg gjør det er minimale, og gevinstene er
10175 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10176 maskinen reinstalleres og alt er tapt.
</p
>
10178 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10179 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10180 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10181 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10182 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10183 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10184 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10185 betydelige.
</p
>
10190 <title>Two projects that have improved the quality of free software a lot
</title>
10191 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10192 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10193 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10194 <description><p
>There are two software projects that have had huge influence on the
10195 quality of free software, and I wanted to mention both in case someone
10196 do not yet know them.
</p
>
10198 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10199 tool to detect and expose errors in the memory handling of programs.
10200 It is easy to use, all one need to do is to run
'valgrind program
',
10201 and it will report any problems on stdout. It is even better if the
10202 program include debug information. With debug information, it is able
10203 to report the source file name and line number where the problem
10204 occurs. It can report things like
'reading past memory block in file
10205 X line N, the memory block was allocated in file Y, line M
', and
10206 'using uninitialised value in control logic
'. This tool has made it
10207 trivial to investigate reproducible crash bugs in programs, and have
10208 reduced the number of this kind of bugs in free software a lot.
10210 <p
>The second one is
10211 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10212 a source code checker. It is able to process the source of a program
10213 and find problems in the logic without running the program. It
10214 started out as the Stanford Checker and became well known when it was
10215 used to find bugs in the Linux kernel. It is now a commercial tool
10216 and the company behind it is running
10217 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10218 free software community, where a lot of free software projects get
10219 their source checked for free. Several thousand defects have been
10220 found and fixed so far. It can find errors like
'lock L taken in file
10221 X line N is never released if exiting in line M
', or
'the code in file
10222 Y lines O to P can never be executed
'. The projects included in the
10223 community service project have managed to get rid of a lot of
10224 reliability problems thanks to Coverity.
</p
>
10226 <p
>I believe tools like this, that are able to automatically find
10227 errors in the source, are vital to improve the quality of software and
10228 make sure we can get rid of the crashing and failing software we are
10229 surrounded by today.
</p
>
10234 <title>No patch is not better than a useless patch
</title>
10235 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10236 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10237 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10238 <description><p
>Julien Blache
10239 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10240 patch is better than a useless patch
</a
>. I completely disagree, as a
10241 patch allow one to discuss a concrete and proposed solution, and also
10242 prove that the issue at hand is important enough for someone to spent
10243 time on fixing it. No patch do not provide any of these positive
10244 properties.
</p
>
10249 <title>Standardize on protocols and formats, not vendors and applications
</title>
10250 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10251 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10252 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10253 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10254 very good one to form a long lived computer infrastructure. It is the
10255 simple one, lost by many in todays computer industry: Standardize on
10256 open network protocols and open exchange/storage formats, not applications.
10257 Applications come and go, while protocols and files tend to stay, and
10258 thus one want to make it easy to change application and vendor, while
10259 avoiding conversion costs and locking users to a specific platform or
10260 application.
</p
>
10262 <p
>This approach make it possible to replace the client applications
10263 independently of the server applications. One can even allow users to
10264 use several different applications as long as they handle the selected
10265 protocol and format. In the normal case, only one client application
10266 is recommended and users only get help if they choose to use this
10267 application, but those that want to deviate from the easy path are not
10268 blocked from doing so.
</p
>
10270 <p
>It also allow us to replace the server side without forcing the
10271 users to replace their applications, and thus allow us to select the
10272 best server implementation at any moment, when scale and resouce
10273 requirements change.
</p
>
10275 <p
>I strongly recommend standardizing - on open network protocols and
10276 open formats, but I would never recommend standardizing on a single
10277 application that do not use open network protocol or open formats.
</p
>
10282 <title>Returning from Skolelinux developer gathering
</title>
10283 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10284 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10285 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10286 <description><p
>I
'm sitting on the train going home from this weekends Debian
10287 Edu/Skolelinux development gathering. I got a bit done tuning the
10288 desktop, and looked into the dynamic service location protocol
10289 implementation avahi. It look like it could be useful for us. Almost
10290 30 people participated, and I believe it was a great environment to
10291 get to know the Skolelinux system. Walter Bender, involved in the
10292 development of the Sugar educational platform, presented his stuff and
10293 also helped me improve my OLPC installation. He also showed me that
10294 his Turtle Art application can be used in standalone mode, and we
10295 agreed that I would help getting it packaged for Debian. As a
10296 standalone application it would be great for Debian Edu. We also
10297 tried to get the video conferencing working with two OLPCs, but that
10298 proved to be too hard for us. The application seem to need more work
10299 before it is ready for me. I look forward to getting home and relax
10305 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10306 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10307 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10308 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10309 <description><p
>The state of standardized LDAP schemas on Linux is far from
10310 optimal. There is RFC
2307 documenting one way to store NIS maps in
10311 LDAP, and a modified version of this normally called RFC
2307bis, with
10312 some modifications to be compatible with Active Directory. The RFC
10313 specification handle the content of a lot of system databases, but do
10314 not handle DNS zones and DHCP configuration.
</p
>
10316 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10317 we would like to store information about users, SMB clients/hosts,
10318 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10319 and LTSP configuration in LDAP. These objects have a lot in common,
10320 but with the current LDAP schemas it is not possible to have one
10321 object per entity. For example, one need to have at least three LDAP
10322 objects for a given computer, one with the SMB related stuff, one with
10323 DNS information and another with DHCP information. The schemas
10324 provided for DNS and DHCP are impossible to combine into one LDAP
10325 object. In addition, it is impossible to implement quick queries for
10326 netgroup membership, because of the way NIS triples are implemented.
10327 It just do not scale. I believe it is time for a few RFC
10328 specifications to cleam up this mess.
</p
>
10330 <p
>I would like to have one LDAP object representing each computer in
10331 the network, and this object can then keep the SMB (ie host key), DHCP
10332 (mac address/name) and DNS (name/IP address) settings in one place.
10333 It need to be efficently stored to make sure it scale well.
</p
>
10335 <p
>I would also like to have a quick way to map from a user or
10336 computer and to the net group this user or computer is a member.
</p
>
10338 <p
>Active Directory have done a better job than unix heads like myself
10339 in this regard, and the unix side need to catch up. Time to start a
10340 new IETF work group?
</p
>
10345 <title>Endelig er Debian Lenny gitt ut
</title>
10346 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10347 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10348 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10349 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10350 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10351 Et langt steg videre for Debian-prosjektet, og en rekke nye
10352 programpakker blir nå tilgjengelig for de av oss som bruker den
10353 stabile utgaven av Debian. Neste steg er nå å få
10354 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10355 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10356 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10357 slippes løs på skolene. Takk til alle debian-utviklerne som har
10358 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10359 bootsekvens tilgjengelig i stabil utgave, vha pakken
10360 <tt
>insserv
</tt
>.
</p
>
10365 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10366 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10367 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10368 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10369 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10370 Oslo. Most of Saturday was used for the general assemly for the
10371 member organization, but the rest of the weekend I used to tune the
10372 LTSP installation. LTSP now work out of the box on the
10-network.
10373 Acer Aspire One proved to be a very nice thin client, with both
10374 screen, mouse and keybard in a small box. Was working on getting the
10375 diskless workstation setup configured out of the box, but did not
10376 finish it before the weekend was up.
</p
>
10378 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10379 the Brazilian group, so that will have to wait for the next
10380 development gathering. Would love to have the Debian Edu installer
10381 automatically detect and configure a multiseat setup when it find one
10382 of these cards.
</p
>
10387 <title>The sorry state of multimedia browser plugins in Debian
</title>
10388 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10390 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10391 <description><p
>Recently I have spent some time evaluating the multimedia browser
10392 plugins available in Debian Lenny, to see which one we should use by
10393 default in Debian Edu. We need an embedded video playing plugin with
10394 control buttons to pause or stop the video, and capable of streaming
10395 all the multimedia content available on the web. The test results and
10396 notes are available on
10397 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10398 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10399 fill this need. My personal video player favorite, VLC, has a really
10400 bad plugin which fail on a lot of the test pages. A lot of the MIME
10401 types I would expect to work with any free software player (like
10402 video/ogg), just do not work. And simple formats like the
10403 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10404 totem and vlc plugins. I hope the situation will improve soon. No
10405 wonder sites use the proprietary Adobe flash to play video.
</p
>
10407 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10408 be the only one fitting our needs. :/
</p
>