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>Unlimited randomness with the ChaosKey?
</title>
11 <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
13 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
14 <description><p
>A few days ago I ordered a small batch of
15 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
16 USB dongle for generating entropy created by Bdale Garbee and Keith
17 Packard. Yesterday it arrived, and I am very happy to report that it
18 work great! According to its designers, to get it to work out of the
19 box, you need the Linux kernel version
4.1 or later. I tested on a
20 Debian Stretch machine (kernel version
4.9), and there it worked just
21 fine, increasing the available entropy very quickly. I wrote a small
22 test oneliner to test. It first print the current entropy level,
23 drain /dev/random, and then print the entropy level for five seconds.
24 Here is the situation without the ChaosKey inserted:
</p
>
26 <blockquote
><pre
>
27 % cat /proc/sys/kernel/random/entropy_avail; \
28 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
29 for n in $(seq
1 5); do \
30 cat /proc/sys/kernel/random/entropy_avail; \
36 28 byte kopiert,
0,
000264565 s,
106 kB/s
43 </pre
></blockquote
>
45 <p
>The entropy level increases by
3-
4 every second. In such case any
46 application requiring random bits (like a HTTPS enabled web server)
47 will halt and wait for more entrpy. And here is the situation with
48 the ChaosKey inserted:
</p
>
50 <blockquote
><pre
>
51 % cat /proc/sys/kernel/random/entropy_avail; \
52 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
53 for n in $(seq
1 5); do \
54 cat /proc/sys/kernel/random/entropy_avail; \
60 104 byte kopiert,
0,
000487647 s,
213 kB/s
67 </pre
></blockquote
>
69 <p
>Quite the difference. :) I bought a few more than I need, in case
70 someone want to buy one here in Norway. :)
</p
>
75 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
76 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
77 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
78 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
79 <description><p
>Did you ever wonder where the web trafic really flow to reach the
80 web servers, and who own the network equipment it is flowing through?
81 It is possible to get a glimpse of this from using traceroute, but it
82 is hard to find all the details. Many years ago, I wrote a system to
83 map the Norwegian Internet (trying to figure out if our plans for a
84 network game service would get low enough latency, and who we needed
85 to talk to about setting up game servers close to the users. Back
86 then I used traceroute output from many locations (I asked my friends
87 to run a script and send me their traceroute output) to create the
88 graph and the map. The output from traceroute typically look like
92 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
93 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
94 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
95 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
96 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
97 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
98 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
99 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
103 </pre
></p
>
105 <p
>This show the DNS names and IP addresses of (at least some of the)
106 network equipment involved in getting the data traffic from me to the
107 www.stortinget.no server, and how long it took in milliseconds for a
108 package to reach the equipment and return to me. Three packages are
109 sent, and some times the packages do not follow the same path. This
110 is shown for hop
5, where three different IP addresses replied to the
111 traceroute request.
</p
>
113 <p
>There are many ways to measure trace routes. Other good traceroute
114 implementations I use are traceroute (using ICMP packages) mtr (can do
115 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
116 traceroute and a lot of other capabilities). All of them are easily
117 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
119 <p
>This time around, I wanted to know the geographic location of
120 different route points, to visualize how visiting a web page spread
121 information about the visit to a lot of servers around the globe. The
122 background is that a web site today often will ask the browser to get
123 from many servers the parts (for example HTML, JSON, fonts,
124 JavaScript, CSS, video) required to display the content. This will
125 leak information about the visit to those controlling these servers
126 and anyone able to peek at the data traffic passing by (like your ISP,
127 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
129 <p
>Lets pick an example, the Norwegian parliament web site
130 www.stortinget.no. It is read daily by all members of parliament and
131 their staff, as well as political journalists, activits and many other
132 citizens of Norway. A visit to the www.stortinget.no web site will
133 ask your browser to contact
8 other servers: ajax.googleapis.com,
134 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
135 stats.g.doubleclick.net, www.google-analytics.com,
136 www.googletagmanager.com and www.netigate.se. I extracted this by
137 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
138 Stortinget web page and tell me all the URLs PhantomJS downloaded to
139 render the page (in HAR format using
140 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
141 netsniff example
</a
>. I am very grateful to Gorm for showing me how
142 to do this). My goal is to visualize network traces to all IP
143 addresses behind these DNS names, do show where visitors personal
144 information is spread when visiting the page.
</p
>
146 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
147 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
>
149 <p
>When I had a look around for options, I could not find any good
150 free software tools to do this, and decided I needed my own traceroute
151 wrapper outputting KML based on locations looked up using GeoIP. KML
152 is easy to work with and easy to generate, and understood by several
153 of the GIS tools I have available. I got good help from by NUUG
154 colleague Anders Einar with this, and the result can be seen in
155 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
156 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
157 free GeoIP databases I could find (and the for-pay databases my
158 friends had access to) is not up to the task. The IP addresses of
159 central Internet infrastructure would typically be placed near the
160 controlling companies main office, and not where the router is really
161 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
162 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
164 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
165 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
>
167 <p
>I also had a look at the visual traceroute graph created by
168 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
169 showing IP network ownership (aka AS owner) for the IP address in
171 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
172 graph display a lot of useful information about the traceroute in SVG
173 format
</a
>, and give a good indication on who control the network
174 equipment involved, but it do not include geolocation. This graph
175 make it possible to see the information is made available at least for
176 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
177 3 Communications and NetDNA.
</p
>
179 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
180 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
>
182 <p
>In the process, I came across the
183 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
184 Salim Gasmi. Its methology of combining guesses based on DNS names,
185 various location databases and finally use latecy times to rule out
186 candidate locations seemed to do a very good job of guessing correct
187 geolocation. But it could only do one trace at the time, did not have
188 a sensor in Norway and did not make the geolocations easily available
189 for postprocessing. So I contacted the developer and asked if he
190 would be willing to share the code (he refused until he had time to
191 clean it up), but he was interested in providing the geolocations in a
192 machine readable format, and willing to set up a sensor in Norway. So
193 since yesterday, it is possible to run traces from Norway in this
194 service thanks to a sensor node set up by
195 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
196 trace in KML format for further processing.
</p
>
198 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
199 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
>
201 <p
>Here we can see a lot of trafic passes Sweden on its way to
202 Denmark, Germany, Holland and Ireland. Plenty of places where the
203 Snowden confirmations verified the traffic is read by various actors
204 without your best interest as their top priority.
</p
>
206 <p
>Combining KML files is trivial using a text editor, so I could loop
207 over all the hosts behind the urls imported by www.stortinget.no and
208 ask for the KML file from GeoTraceroute, and create a combined KML
209 file with all the traces (unfortunately only one of the IP addresses
210 behind the DNS name is traced this time. To get them all, one would
211 have to request traces using IP number instead of DNS names from
212 GeoTraceroute). That might be the next step in this project.
</p
>
214 <p
>Armed with these tools, I find it a lot easier to figure out where
215 the IP traffic moves and who control the boxes involved in moving it.
216 And every time the link crosses for example the Swedish border, we can
217 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
218 Britain and NSA in USA and cables around the globe. (Hm, what should
219 we tell them? :) Keep that in mind if you ever send anything
220 unencrypted over the Internet.
</p
>
222 <p
>PS: KML files are drawn using
223 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
224 Rublev
<a/
>, as it was less cluttered than the local Linux application
225 Marble. There are heaps of other options too.
</p
>
227 <p
>As usual, if you use Bitcoin and want to show your support of my
228 activities, please send Bitcoin donations to my address
229 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
234 <title>Appstream just learned how to map hardware to packages too!
</title>
235 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
236 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
237 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
238 <description><p
>I received a very nice Christmas present today. As my regular
239 readers probably know, I have been working on the
240 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
241 system
</a
> for many years. The goal of the Isenkram system is to make
242 it easier for users to figure out what to install to get a given piece
243 of hardware to work in Debian, and a key part of this system is a way
244 to map hardware to packages. Isenkram have its own mapping database,
245 and also uses data provided by each package using the AppStream
246 metadata format. And today,
247 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
248 Debian learned to look up hardware the same way Isenkram is doing it,
249 ie using fnmatch():
</p
>
252 % appstreamcli what-provides modalias \
253 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
254 Identifier: pymissile [generic]
256 Summary: Control original Striker USB Missile Launcher
258 % appstreamcli what-provides modalias usb:v0694p0002d0000
259 Identifier: libnxt [generic]
261 Summary: utility library for talking to the LEGO Mindstorms NXT brick
264 Identifier: t2n [generic]
266 Summary: Simple command-line tool for Lego NXT
269 Identifier: python-nxt [generic]
271 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
274 Identifier: nbc [generic]
276 Summary: C compiler for LEGO Mindstorms NXT bricks
279 </pre
></p
>
281 <p
>A similar query can be done using the combined AppStream and
282 Isenkram databases using the isenkram-lookup tool:
</p
>
285 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
287 % isenkram-lookup usb:v0694p0002d0000
293 </pre
></p
>
295 <p
>You can find modalias values relevant for your machine using
296 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
298 <p
>If you want to make this system a success and help Debian users
299 make the most of the hardware they have, please
300 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
301 AppStream metadata for your package following the guidelines
</a
>
302 documented in the wiki. So far only
11 packages provide such
303 information, among the several hundred hardware specific packages in
304 Debian. The Isenkram database on the other hand contain
101 packages,
305 mostly related to USB dongles. Most of the packages with hardware
306 mapping in AppStream are LEGO Mindstorms related, because I have, as
307 part of my involvement in
308 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
309 team
</a
> given priority to making sure LEGO users get proposed the
310 complete set of packages in Debian for that particular hardware. The
311 team also got a nice Christmas present today. The
312 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
313 package
</a
> made it into Debian. With this package in place, it is
314 now possible to use the LEGO Mindstorms NXT unit with only free
315 software, as the nxt-firmware package contain the source and firmware
316 binaries for the NXT brick.
</p
>
318 <p
>As usual, if you use Bitcoin and want to show your support of my
319 activities, please send Bitcoin donations to my address
320 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
325 <title>Isenkram updated with a lot more hardware-package mappings
</title>
326 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
327 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
328 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
329 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
330 system
</a
> I wrote two years ago to make it easier in Debian to find
331 and install packages to get your hardware dongles to work, is still
332 going strong. It is a system to look up the hardware present on or
333 connected to the current system, and map the hardware to Debian
334 packages. It can either be done using the tools in isenkram-cli or
335 using the user space daemon in the isenkram package. The latter will
336 notify you, when inserting new hardware, about what packages to
337 install to get the dongle working. It will even provide a button to
338 click on to ask packagekit to install the packages.
</p
>
340 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
359 </pre
></p
>
361 <p
>It can also list the firware package providing firmware requested
362 by the load kernel modules, which in my case is an empty list because
363 I have all the firmware my machine need:
366 % /usr/sbin/isenkram-autoinstall-firmware -l
367 info: did not find any firmware files requested by loaded kernel modules. exiting
369 </pre
></p
>
371 <p
>The last few days I had a look at several of the around
250
372 packages in Debian with udev rules. These seem like good candidates
373 to install when a given hardware dongle is inserted, and I found
374 several that should be proposed by isenkram. I have not had time to
375 check all of them, but am happy to report that now there are
97
376 packages packages mapped to hardware by Isenkram.
11 of these
377 packages provide hardware mapping using AppStream, while the rest are
378 listed in the modaliases file provided in isenkram.
</p
>
380 <p
>These are the packages with hardware mappings at the moment. The
381 <strong
>marked packages
</strong
> are also announcing their hardware
382 support using AppStream, for everyone to use:
</p
>
384 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
385 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
386 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
387 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
388 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
389 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
390 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
391 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
392 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
393 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
394 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
395 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
396 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
397 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
398 pcscd, pidgin-blinklight, printer-driver-splix,
399 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
400 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
401 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
402 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
403 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
404 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
405 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
406 xserver-xorg-video-vmware, yubikey-personalization and
407 zd1211-firmware
</p
>
409 <p
>If you know of other packages, please let me know with a wishlist
410 bug report against the isenkram-cli package, and ask the package
412 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
413 metadata according to the guidelines
</a
> to provide the information
414 for everyone. In time, I hope to get rid of the isenkram specific
415 hardware mapping and depend exclusively on AppStream.
</p
>
417 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
418 much hardware, and suggest that the package with with any ethernet
419 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
420 the details. I hope the maintainer find time to address it soon. In
421 the mean time I provide an override in isenkram.
</p
>
426 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
427 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
428 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
429 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
430 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
432 <p
>In my early years, I played
433 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
434 Elite
</a
> on my PC. I spent many months trading and fighting in
435 space, and reached the
'elite
' fighting status before I moved on. The
436 original Elite game was available on Commodore
64 and the IBM PC
437 edition I played had a
64 KB executable. I am still impressed today
438 that the authors managed to squeeze both a
3D engine and details about
439 more than
2000 planet systems across
7 galaxies into a binary so
442 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
443 software game Oolite inspired by Elite
</a
> for a while, but did not
444 really have time to test it properly until a few days ago. It was
445 great to discover that my old knowledge about trading routes were
446 still valid. But my fighting and flying abilities were gone, so I had
447 to retrain to be able to dock on a space station. And I am still not
448 able to make much resistance when I am attacked by pirates, so I
449 bougth and mounted the most powerful laser in the rear to be able to
450 put up at least some resistance while fleeing for my life. :)
</p
>
452 <p
>When playing Elite in the late eighties, I had to discover
453 everything on my own, and I had long lists of prices seen on different
454 planets to be able to decide where to trade what. This time I had the
456 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
457 where information about each planet is easily available with common
458 price ranges and suggested trading routes. This improved my ability
459 to earn money and I have been able to earn enough to buy a lot of
460 useful equipent in a few days. I believe I originally played for
461 months before I could get a docking computer, while now I could get it
462 after less then a week.
</p
>
464 <p
>If you like science fiction and dreamed of a life as a vagabond in
465 space, you should try out Oolite. It is available for Linux, MacOSX
466 and Windows, and is included in Debian and derivatives since
2011.
</p
>
468 <p
>As usual, if you use Bitcoin and want to show your support of my
469 activities, please send Bitcoin donations to my address
470 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
475 <title>Quicker Debian installations using eatmydata
</title>
476 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
477 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
478 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
479 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
480 installation system, observing how using
481 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
482 could speed up the installation
</a
> quite a bit. My testing measured
483 speedup around
20-
40 percent for Debian Edu, where we install around
484 1000 packages from within the installer. The eatmydata package
485 provide a way to disable/delay file system flushing. This is a bit
486 risky in the general case, as files that should be stored on disk will
487 stay only in memory a bit longer than expected, causing problems if a
488 machine crashes at an inconvenient time. But for an installation, if
489 the machine crashes during installation the process is normally
490 restarted, and avoiding disk operations as much as possible to speed
491 up the process make perfect sense.
493 <p
>I added code in the Debian Edu specific installation code to enable
494 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
495 but did not have time to push it any further. But a few months ago I
496 picked it up again and worked with the libeatmydata package maintainer
497 Mattia Rizzolo to make it easier for everyone to get this installation
498 speedup in Debian. Thanks to our cooperation There is now an
499 eatmydata-udeb package in Debian testing and unstable, and simply
500 enabling/installing it in debian-installer (d-i) is enough to get the
501 quicker installations. It can be enabled using preseeding. The
502 following untested kernel argument should do the trick:
</p
>
504 <blockquote
><pre
>
505 preseed/early_command=
"anna-install eatmydata-udeb
"
506 </pre
></blockquote
>
508 <p
>This should ask d-i to install the package inside the d-i
509 environment early in the installation sequence. Having it installed
510 in d-i in turn will make sure the relevant scripts are called just
511 after debootstrap filled /target/ with the freshly installed Debian
512 system to configure apt to run dpkg with eatmydata. This is enough to
513 speed up the installation process. There is a proposal to
514 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
515 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
516 tested its impact.
</p
>
522 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
523 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
524 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
525 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
526 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
527 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
528 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
529 elever over det ganske land skal levere inn hvert år. Det mange ikke
530 vet er at selv om de kommersielle alternativene
531 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
532 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
533 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
534 utmerket fri programvarealternativ som kan. Oversetterverktøyet
535 Apertium har støtte for en rekke språkkombinasjoner, og takket være
536 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
537 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
538 nynorsk, og få den automatoversatt til det andre skriftspråket.
539 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
540 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
541 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
542 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
543 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
544 teksten din i webskjemaet der.
546 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
547 teknologien kan du enten installere pakken
548 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
549 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
551 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
552 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
553 denne teksten som ble skrevet på bokmål over maskinoversatt til
558 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
559 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
560 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
561 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
562 veit er at sjølv om dei kommersielle alternativa
563 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
564 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
565 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
566 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
567 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
568 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
569 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
570 nynorsk, og få den *automatoversatt til det andre skriftspråket.
571 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
572 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
573 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
574 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
575 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
576 teksta di i *webskjemaet der.
578 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
579 teknologien kan du anten installera pakken
580 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
581 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
582 *api.*apertium.org. Sjå
583 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
584 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
585 for denne teksta som vart skreva på bokmål over *maskinoversatt til
591 <title>Coz profiler for multi-threaded software is now in Debian
</title>
592 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
593 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
594 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
595 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
596 profiler able to run benchmarking experiments on the instrumented
597 multi-threaded program, finally
598 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
599 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
601 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
602 blogged about the coz tool
</a
> in August working with upstream to make
603 it suitable for Debian. There are still issues with clang
604 compatibility, inline assembly only working x86 and minimized
605 JavaScript libraries.
</p
>
607 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
609 <p
><blockquote
>
610 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
611 </blockquote
></p
>
613 <p
>This will produce a profile.coz file in the current working
614 directory with the profiling information. This is then given to a
615 JavaScript application provided in the package and available from
616 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
617 To start the local copy, invoke it in a browser like this:
</p
>
619 <p
><blockquote
>
620 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
621 </blockquote
></p
>
623 <p
>See the project home page and the
624 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
625 ;login: article on Coz
</a
> for more information on how it is
631 <title>My own self balancing Lego Segway
</title>
632 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
633 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
634 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
635 <description><p
>A while back I received a Gyro sensor for the NXT
636 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
637 present. It had been on my wishlist for a while, because I wanted to
638 build a Segway like balancing lego robot. I had already built
639 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
640 robot
</a
> with the kids, using the light/color sensor included in the
641 NXT kit as the balance sensor, but it was not working very well. It
642 could balance for a while, but was very sensitive to the light
643 condition in the room and the reflective properties of the surface and
644 would fall over after a short while. I wanted something more robust,
646 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
647 gyro sensor from HiTechnic
</a
> I believed would solve it on my
648 wishlist for some years before it suddenly showed up as a gift from my
649 loved ones. :)
</p
>
651 <p
>Unfortunately I have not had time to sit down and play with it
652 since then. But that changed some days ago, when I was searching for
653 lego segway information and came across a recipe from HiTechnic for
655 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
656 HTWay
</a
>, a segway like balancing robot. Build instructions and
657 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
658 code
</a
> was included, so it was just a question of putting it all
659 together. And thanks to the great work of many Debian developers, the
660 compiler needed to build the source for the NXT is already included in
661 Debian, so I was read to go in less than an hour. The resulting robot
662 do not look very impressive in its simplicity:
</p
>
664 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
666 <p
>Because I lack the infrared sensor used to control the robot in the
667 design from HiTechnic, I had to comment out the last task
668 (taskControl). I simply placed /* and */ around it get the program
669 working without that sensor present. Now it balances just fine until
670 the battery status run low:
</p
>
672 <p align=
"center
"><video width=
"70%
" controls=
"true
">
673 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
674 </video
></p
>
676 <p
>Now we would like to teach it how to follow a line and take remote
677 control instructions using the included Bluetooth receiver in the NXT.
</p
>
679 <p
>If you, like me, love LEGO and want to make sure we find the tools
680 they need to work with LEGO in Debian and all our derivative
681 distributions like Ubuntu, check out
682 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
683 project page
</a
> and join the Debian LEGO team. Personally I own a
684 RCX and NXT controller (no EV3), and would like to make sure the
685 Debian tools needed to program the systems I own work as they
691 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
692 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
693 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
694 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
695 <description><p
>In July
696 <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
697 wrote how to get the Signal Chrome/Chromium app working
</a
> without
698 the ability to receive SMS messages (aka without a cell phone). It is
699 time to share some experiences and provide an updated setup.
</p
>
701 <p
>The Signal app have worked fine for several months now, and I use
702 it regularly to chat with my loved ones. I had a major snag at the
703 end of my summer vacation, when the the app completely forgot my
704 setup, identity and keys. The reason behind this major mess was
705 running out of disk space. To avoid that ever happening again I have
706 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
707 roll back to an earlier version if the files are wiped by mistake. I
708 had to use it once after introducing the git backup. When rolling
709 back to an earlier version, one need to use the
'reset session
' option
710 in Signal to get going, and notify the people you talk with about the
711 problem. I assume there is some sequence number tracking in the
712 protocol to detect rollback attacks. The git repository is rather big
713 (
674 MiB so far), but I have not tried to figure out if some of the
714 content can be added to a .gitignore file due to lack of spare
717 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
718 make it impossible to send messages using Signal. I could still
719 receive them, but had to patch the code with a new timestamp to send.
720 I believe the timeout is added by the developers to force people to
721 upgrade to the latest version of the app, even when there is no
722 protocol changes, to reduce the version skew among the user base and
723 thus try to keep the number of support requests down.
</p
>
725 <p
>Since my original recipe, the Signal source code changed slightly,
726 making the old patch fail to apply cleanly. Below is an updated
727 patch, including the shell wrapper I use to start Signal. The
728 original version required a new user to locate the JavaScript console
729 and call a function from there. I got help from a friend with more
730 JavaScript knowledge than me to modify the code to provide a GUI
731 button instead. This mean that to get started you just need to run
732 the wrapper and click the
'Register without mobile phone
' to get going
733 now. I
've also modified the timeout code to always set it to
90 days
734 in the future, to avoid having to patch the code regularly.
</p
>
736 <p
>So, the updated recipe for Debian Jessie:
</p
>
740 <li
>First, install required packages to get the source code and the
741 browser you need. Signal only work with Chrome/Chromium, as far as I
742 know, so you need to install it.
745 apt install git tor chromium
746 git clone https://github.com/WhisperSystems/Signal-Desktop.git
747 </pre
></li
>
749 <li
>Modify the source code using command listed in the the patch
750 block below.
</li
>
752 <li
>Start Signal using the run-signal-app wrapper (for example using
753 <tt
>`pwd`/run-signal-app
</tt
>).
755 <li
>Click on the
'Register without mobile phone
', will in a phone
756 number you can receive calls to the next minute, receive the
757 verification code and enter it into the form field and press
758 'Register
'. Note, the phone number you use will be user Signal
759 username, ie the way others can find you on Signal.
</li
>
761 <li
>You can now use Signal to contact others. Note, new contacts do
762 not show up in the contact list until you restart Signal, and there is
763 no way to assign names to Contacts. There is also no way to create or
764 update chat groups. I suspect this is because the web app do not have
765 a associated contact database.
</li
>
769 <p
>I am still a bit uneasy about using Signal, because of the way its
770 main author moxie0 reject federation and accept dependencies to major
771 corporations like Google (part of the code is fetched from Google) and
772 Amazon (the central coordination point is owned by Amazon). See for
774 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
775 LibreSignal issue tracker
</a
> for a thread documenting the authors
776 view on these issues. But the network effect is strong in this case,
777 and several of the people I want to communicate with already use
778 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
779 once it
<a href=
"https://bugs.debian.org/
830265">work on my
780 laptop
</a
>? It already work on Windows and Android, and is included
781 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
782 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
783 working on Debian Stable.
</p
>
785 <p
>Anyway, this is the patch I apply to the Signal code to get it
786 working. It switch to the production servers, disable to timeout,
787 make registration easier and add the shell wrapper:
</p
>
790 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
791 diff --git a/js/background.js b/js/background.js
792 index
24b4c1d.
.579345f
100644
793 --- a/js/background.js
794 +++ b/js/background.js
799 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
800 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
801 var SERVER_PORTS = [
80,
4433,
8443];
802 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
803 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
805 window.getSocketStatus = function() {
806 if (messageReceiver) {
807 diff --git a/js/expire.js b/js/expire.js
808 index
639aeae..beb91c3
100644
813 'use strict
';
814 - var BUILD_EXPIRATION =
0;
815 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
817 window.extension = window.extension || {};
819 diff --git a/js/views/install_view.js b/js/views/install_view.js
820 index
7816f4f.
.1d6233b
100644
821 --- a/js/views/install_view.js
822 +++ b/js/views/install_view.js
825 'click .step1
': this.selectStep.bind(this,
1),
826 'click .step2
': this.selectStep.bind(this,
2),
827 -
'click .step3
': this.selectStep.bind(this,
3)
828 +
'click .step3
': this.selectStep.bind(this,
3),
829 +
'click .callreg
': function() { extension.install(
'standalone
') },
832 clearQR: function() {
833 diff --git a/options.html b/options.html
834 index dc0f28e.
.8d709f6
100644
838 &lt;div class=
'nav
'>
839 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
840 &lt;p
>{{ installTagline }}
&lt;/p
>
841 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
842 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
843 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
846 &lt;span class=
'dot step1 selected
'>&lt;/span
>
847 &lt;span class=
'dot step2
'>&lt;/span
>
848 &lt;span class=
'dot step3
'>&lt;/span
>
849 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
850 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
856 +userdata=
"`pwd`/userdata
"
857 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
858 + (cd $userdata
&& git init)
860 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
862 + --proxy-server=
"socks://localhost:
9050" \
863 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
865 chmod a+rx run-signal-app
868 <p
>As usual, if you use Bitcoin and want to show your support of my
869 activities, please send Bitcoin donations to my address
870 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
875 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
876 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
878 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
879 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
880 system
</a
> provide a practical and easy way to figure out which
881 packages support the hardware in a given machine. The command line
882 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
883 convenient way to list and install packages relevant for the current
884 hardware during system installation, both user space packages and
885 firmware packages. The GUI background daemon on the other hand provide
886 a pop-up proposing to install packages when a new dongle is inserted
887 while using the computer. For example, if you plug in a smart card
888 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
889 that package isn
't already installed, and if you plug in a USB video
890 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
891 cheese is currently missing. This already work just fine.
</p
>
893 <p
>But Isenkram depend on a database mapping from hardware IDs to
894 package names. When I started no such database existed in Debian, so
895 I made my own data set and included it with the isenkram package and
896 made isenkram fetch the latest version of this database from git using
897 http. This way the isenkram users would get updated package proposals
898 as soon as I learned more about hardware related packages.
</p
>
900 <p
>The hardware is identified using modalias strings. The modalias
901 design is from the Linux kernel where most hardware descriptors are
902 made available as a strings that can be matched using filename style
903 globbing. It handle USB, PCI, DMI and a lot of other hardware related
904 identifiers.
</p
>
906 <p
>The downside to the Isenkram specific database is that there is no
907 information about relevant distribution / Debian version, making
908 isenkram propose obsolete packages too. But along came AppStream, a
909 cross distribution mechanism to store and collect metadata about
910 software packages. When I heard about the proposal, I contacted the
911 people involved and suggested to add a hardware matching rule using
912 modalias strings in the specification, to be able to use AppStream for
913 mapping hardware to packages. This idea was accepted and AppStream is
914 now a great way for a package to announce the hardware it support in a
915 distribution neutral way. I wrote
916 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
917 recipe on how to add such meta-information
</a
> in a blog post last
918 December. If you have a hardware related package in Debian, please
919 announce the relevant hardware IDs using AppStream.
</p
>
921 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
922 RCX or NXT unit, announce this support using AppStream. The effect is
923 that when you insert such LEGO robot controller into your Debian
924 machine, Isenkram will propose to install the packages needed to get
925 it working. The intention is that this should allow the local user to
926 start programming his robot controller right away without having to
927 guess what packages to use or which permissions to fix.
</p
>
929 <p
>But when I sat down with my son the other day to program our NXT
930 unit using his Debian Stretch computer, I discovered something
931 annoying. The local console user (ie my son) did not get access to
932 the USB device for programming the unit. This used to work, but no
933 longer in Jessie and Stretch. After some investigation and asking
934 around on #debian-devel, I discovered that this was because udev had
935 changed the mechanism used to grant access to local devices. The
936 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
937 no longer applied, because LDAP users no longer was added to the
938 plugdev group during login. Michael Biebl told me that this method
939 was obsolete and the new method used ACLs instead. This was good
940 news, as the plugdev mechanism is a mess when using a remote user
941 directory like LDAP. Using ACLs would make sure a user lost device
942 access when she logged out, even if the user left behind a background
943 process which would retain the plugdev membership with the ConsoleKit
944 setup. Armed with this knowledge I moved on to fix the access problem
945 for the LEGO Mindstorms related packages.
</p
>
947 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
948 applied directly for a device, or is applied in
949 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
950 LEGO Mindstorms udev rules did not have a class, I decided to add the
951 tag directly in the udev rules files included in the packages. Here
952 is one example. For the nqc C compiler for the RCX, the
953 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
956 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
957 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
958 </pre
></p
>
960 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
961 packages using plugdev in their /lib/udev/rules.d/ files should be
962 changed to use this tag (either directly or indirectly via
963 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
964 to detect this?
</p
>
966 <p
>I
've been unable to find good documentation on the uaccess feature.
967 It is unclear to me if the uaccess tag is an internal implementation
968 detail like the udev-acl tag used by
969 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
970 indirect method is the preferred way. Michael
971 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
972 documentation from the systemd project
</a
> and I hope it will make
973 this clearer. For now I use the generic classes when they exist and
974 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
975 directly if no such class exist.
</p
>
977 <p
>To learn more about the isenkram system, please check out
978 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
979 blog posts tagged isenkram
</a
>.
</p
>
981 <p
>To help out making life for LEGO constructors in Debian easier,
982 please join us on our IRC channel
983 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
984 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
985 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
986 list is not yet created, but we are working on it. :)
</p
>
988 <p
>As usual, if you use Bitcoin and want to show your support of my
989 activities, please send Bitcoin donations to my address
990 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
995 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
996 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
997 <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>
998 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
999 <description><p
>In April we
1000 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
1001 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
1002 how to set up and administrate a Debian system. Today I am happy to
1003 report that the first draft is now publicly available. You can find
1004 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
1005 Administrator
's Handbook page
</a
> (under Other languages). The first
1006 eight chapters have a first draft translation, and we are working on
1007 proofreading the content. If you want to help out, please start
1009 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1010 hosted weblate project page
</a
>, and get in touch using
1011 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1012 translators mailing list
</a
>. Please also check out
1013 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1014 contributors
</a
>. A good way to contribute is to proofread the text
1015 and update weblate if you find errors.
</p
>
1017 <p
>Our goal is still to make the Norwegian book available on paper as well as
1018 electronic form.
</p
>
1023 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
1024 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
1025 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
1026 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
1027 <description><p
>This summer, I read a great article
1028 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
1029 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
1030 how to profile multi-threaded programs. It presented a system for
1031 profiling software by running experiences in the running program,
1032 testing how run time performance is affected by
"speeding up
" parts of
1033 the code to various degrees compared to a normal run. It does this by
1034 slowing down parallel threads while the
"faster up
" code is running
1035 and measure how this affect processing time. The processing time is
1036 measured using probes inserted into the code, either using progress
1037 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
1038 can also measure unmodified code by measuring complete the program
1039 runtime and running the program several times instead.
</p
>
1041 <p
>The project and presentation was so inspiring that I would like to
1042 get the system into Debian. I
1043 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
1044 a WNPP request for it
</a
> and contacted upstream to try to make the
1045 system ready for Debian by sending patches. The build process need to
1046 be changed a bit to avoid running
'git clone
' to get dependencies, and
1047 to include the JavaScript web page used to visualize the collected
1048 profiling information included in the source package.
1049 But I expect that should work out fairly soon.
</p
>
1051 <p
>The way the system work is fairly simple. To run an coz experiment
1052 on a binary with debug symbols available, start the program like this:
1054 <p
><blockquote
><pre
>
1055 coz run --- program-to-run
1056 </pre
></blockquote
></p
>
1058 <p
>This will create a text file profile.coz with the instrumentation
1059 information. To show what part of the code affect the performance
1060 most, use a web browser and either point it to
1061 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
1062 or use the copy from git (in the gh-pages branch). Check out this web
1063 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
1064 profiling more useful you include
&lt;coz.h
&gt; and insert the
1065 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1066 code, rebuild and run the profiler. This allow coz to do more
1067 targeted experiments.
</p
>
1069 <p
>A video published by ACM
1070 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1071 Coz profiler
</a
> is available from Youtube. There is also a paper
1072 from the
25th Symposium on Operating Systems Principles available
1074 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1075 finding code that counts with causal profiling
</a
>.
</p
>
1077 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1078 for Coz is available from github. It will only build with clang
1080 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1081 feature missing in GCC
</a
>, but I
've submitted
1082 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1083 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1085 <p
>Please get in touch if you, like me, would like to see this piece
1086 of software in Debian. I would very much like some help with the
1087 packaging effort, as I lack the in depth knowledge on how to package
1088 C++ libraries.
</p
>
1093 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1094 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1095 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1096 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1097 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1098 to be a slight challenge. Here is the recipe if I ever need to do it
1099 again. It all started by me wanting to try the recipe to set up
1100 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1101 hardened Android installation
</a
> from the Tor project blog on a
1102 device I had access to. It is a old mobile phone with a broken
1103 microphone The initial idea had been to just
1104 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1105 CyanogenMod on it
</a
>, but did not quite find time to start on it
1106 until a few days ago.
</p
>
1108 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1109 loader (press volume down and power at the same time), (
2) select
1110 'fastboot
' before (
3) connecting the device via USB to a Linux
1111 machine, (
4) request the device identifier token by running
'fastboot
1112 oem get_identifier_token
', (
5) request the device unlocking key using
1113 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1114 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1116 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1117 or newer, and the device I was working on had
2.00.0027. This
1118 apparently can be easily fixed by downloading a Windows program and
1119 running it on your Windows machine, if you accept the terms Microsoft
1120 require you to accept to use Windows - which I do not. So I had to
1121 come up with a different approach. I got a lot of help from AndyCap
1122 on #nuug, and would not have been able to get this working without
1125 <p
>First I needed to extract the hboot firmware from
1126 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1127 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1128 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1129 project named unruu
</a
> using libunshield. The unshield tool did not
1130 recognise the file format, but unruu worked and extracted rom.zip,
1131 containing the new hboot firmware and a text file describing which
1132 devices it would work for.
</p
>
1134 <p
>Next, I needed to get the new firmware into the device. For this I
1135 followed some instructions
1136 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1137 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1138 machine with Debian testing:
</p
>
1140 <p
><pre
>
1141 adb reboot-bootloader
1142 fastboot oem rebootRUU
1143 fastboot flash zip rom.zip
1144 fastboot flash zip rom.zip
1146 </pre
></p
>
1148 <p
>The flash command apparently need to be done twice to take effect,
1149 as the first is just preparations and the second one do the flashing.
1150 The adb command is just to get to the boot loader menu, so turning the
1151 device on while holding volume down and the power button should work
1154 <p
>With the new hboot version in place I could start following the
1155 instructions on the HTC developer web site. I got the device token
1156 like this:
</p
>
1158 <p
><pre
>
1159 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1162 <p
>And once I got the unlock code via email, I could use it like
1165 <p
><pre
>
1166 fastboot flash unlocktoken Unlock_code.bin
1167 </pre
></p
>
1169 <p
>And with that final step in place, the phone was unlocked and I
1170 could start stuffing the software of my own choosing into the device.
1171 So far I only inserted a replacement recovery image to wipe the phone
1172 before I start. We will see what happen next. Perhaps I should
1173 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1178 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1179 <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>
1180 <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>
1181 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1182 <description><p
>For a while now, I have wanted to test
1183 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1184 said to provide end to end encrypted communication and several of my
1185 friends and family are already using it. As I by choice do not own a
1186 mobile phone, this proved to be harder than expected. And I wanted to
1187 have the source of the client and know that it was the code used on my
1188 machine. But yesterday I managed to get it working. I used the
1189 Github source, compared it to the source in
1190 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1191 Signal Chrome app
</a
> available from the Chrome web store, applied
1192 patches to use the production Signal servers, started the app and
1193 asked for the hidden
"register without a smart phone
" form. Here is
1194 the recipe how I did it.
</p
>
1196 <p
>First, I fetched the Signal desktop source from Github, using
1199 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1202 <p
>Next, I patched the source to use the production servers, to be
1203 able to talk to other Signal users:
</p
>
1206 cat
&lt;
&lt;EOF | patch -p0
1207 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1208 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1209 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1214 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1215 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1216 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1217 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1218 var messageReceiver;
1219 window.getSocketStatus = function() {
1220 if (messageReceiver) {
1221 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1222 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1223 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1226 'use strict
';
1227 - var BUILD_EXPIRATION =
0;
1228 + var BUILD_EXPIRATION =
1474492690000;
1230 window.extension = window.extension || {};
1235 <p
>The first part is changing the servers, and the second is updating
1236 an expiration timestamp. This timestamp need to be updated regularly.
1237 It is set
90 days in the future by the build process (Gruntfile.js).
1238 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1240 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1241 script to launch Signal in Chromium.
</p
>
1248 --proxy-server=
"socks://localhost:
9050" \
1249 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1252 <p
> The script start the app and configure Chromium to use the Tor
1253 SOCKS5 proxy to make sure those controlling the Signal servers (today
1254 Amazon and Whisper Systems) as well as those listening on the lines
1255 will have a harder time location my laptop based on the Signal
1256 connections if they use source IP address.
</p
>
1258 <p
>When the script starts, one need to follow the instructions under
1259 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1260 repository. I right clicked on the Signal window to get up the
1261 Chromium debugging tool, visited the
'Console
' tab and wrote
1262 'extension.install(
"standalone
")
' on the console prompt to get the
1263 registration form. Then I entered by land line phone number and
1264 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1265 repeated the verification code three times. After entering the number
1266 into the verification code field in the form, I could start using
1267 Signal from my laptop.
1269 <p
>As far as I can tell, The Signal app will leak who is talking to
1270 whom and thus who know who to those controlling the central server,
1271 but such leakage is hard to avoid with a centrally controlled server
1272 setup. It is something to keep in mind when using Signal - the
1273 content of your chats are harder to intercept, but the meta data
1274 exposing your contact network is available to people you do not know.
1275 So better than many options, but not great. And sadly the usage is
1276 connected to my land line, thus allowing those controlling the server
1277 to associate it to my home and person. I would prefer it if only
1278 those I knew could tell who I was on Signal. There are options
1279 avoiding such information leakage, but most of my friends are not
1280 using them, so I am stuck with Signal for now.
</p
>
1282 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1284 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1285 and updated recipe for using the Signal app without a mobile
1286 phone
</a
>.
</p
>
1291 <title>The new
"best
" multimedia player in Debian?
</title>
1292 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1293 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1294 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1295 <description><p
>When I set out a few weeks ago to figure out
1296 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1297 multimedia player in Debian claimed to support most file formats /
1298 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1299 the various players claimed support for. The range was from
55 to
130
1300 MIME types. I suspect most media formats are supported by all
1301 players, but this is not really reflected in the MimeTypes values in
1302 their desktop files. There are probably also some bogus MIME types
1303 listed, but it is hard to identify which one this is.
</p
>
1305 <p
>Anyway, in the mean time I got in touch with upstream for some of
1306 the players suggesting to add more MIME types to their desktop files,
1307 and decided to spend some time myself improving the situation for my
1308 favorite media player VLC. The fixes for VLC entered Debian unstable
1309 yesterday. The complete list of MIME types can be seen on the
1310 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1311 player MIME type support status
</a
> Debian wiki page.
</p
>
1313 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1314 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1315 kmplayer. I am sure some of the other players desktop files support
1316 several of the formats currently listed as working only with vlc,
1317 toten and parole.
</p
>
1319 <p
>A sad observation is that only
14 MIME types are listed as
1320 supported by all the tested multimedia players in Debian in their
1321 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1322 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1323 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1324 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1325 it sad that video/ogg and video/webm is not supported by all the media
1326 players in Debian. As far as I can tell, all of them can handle both
1332 <title>A program should be able to open its own files on Linux
</title>
1333 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1334 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1335 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1336 <description><p
>Many years ago, when koffice was fresh and with few users, I
1337 decided to test its presentation tool when making the slides for a
1338 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1339 wrote the first draft of the slides, saved the result and went to bed
1340 the day before I would give the talk. The next day I took a plane to
1341 the location where the meeting should take place, and on the plane I
1342 started up koffice again to polish the talk a bit, only to discover
1343 that kpresenter refused to load its own data file. I cursed a bit and
1344 started making the slides again from memory, to have something to
1345 present when I arrived. I tested that the saved files could be
1346 loaded, and the day seemed to be rescued. I continued to polish the
1347 slides until I suddenly discovered that the saved file could no longer
1348 be loaded into kpresenter. In the end I had to rewrite the slides
1349 three times, condensing the content until the talk became shorter and
1350 shorter. After the talk I was able to pinpoint the problem
&ndash;
1351 kpresenter wrote inline images in a way itself could not understand.
1352 Eventually that bug was fixed and kpresenter ended up being a great
1353 program to make slides. The point I
'm trying to make is that we
1354 expect a program to be able to load its own data files, and it is
1355 embarrassing to its developers if it can
't.
</p
>
1357 <p
>Did you ever experience a program failing to load its own data
1358 files from the desktop file browser? It is not a uncommon problem. A
1359 while back I discovered that the screencast recorder
1360 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1361 browser would refuse to open. No video player claimed to understand
1362 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1363 returning the application/ogg MIME type, which no video player I had
1364 installed listed as a MIME type they would understand. I asked for
1365 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1366 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1367 several video players to add video/ogg to their desktop files, to give
1368 the file browser an idea what to do about Ogg Theora files. After a
1369 while, the desktop file browsers in Debian started to handle the
1370 output from gtk-recordmydesktop properly.
</p
>
1372 <p
>But history repeats itself. A few days ago I tested the music
1373 system Rosegarden again, and I discovered that the KDE and xfce file
1374 browsers did not know what to do with the Rosegarden project files
1375 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1376 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1377 included in the next upload. To increase the chance of me remembering
1378 how to fix the problem next time some program fail to load its files
1379 from the file browser, here are some notes on how to fix it.
</p
>
1381 <p
>The file browsers in Debian in general operates on MIME types.
1382 There are two sources for the MIME type of a given file. The output from
1383 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1384 shared MIME type registry (under /usr/share/mime/). The file MIME
1385 type is mapped to programs supporting the MIME type, and this
1386 information is collected from
1387 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1388 desktop files
</a
> available in /usr/share/applications/. If there is
1389 one desktop file claiming support for the MIME type of the file, it is
1390 activated when asking to open a given file. If there are more, one
1391 can normally select which one to use by right-clicking on the file and
1392 selecting the wanted one using
'Open with
' or similar. In general
1393 this work well. But it depend on each program picking a good MIME
1395 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1396 MIME type registered with IANA
</a
>), file and/or the shared MIME
1397 registry recognizing the file and the desktop file to list the MIME
1398 type in its list of supported MIME types.
</p
>
1400 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1401 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1402 Shared MIME database
</a
> look like this:
</p
>
1404 <p
><blockquote
><pre
>
1405 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1406 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1407 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1408 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1409 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1410 &lt;glob pattern=
"*.rg
"/
&gt;
1411 &lt;/mime-type
&gt;
1412 &lt;/mime-info
&gt;
1413 </pre
></blockquote
></p
>
1415 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1416 (it is a gzipped XML file). Note, it is much better to use an
1417 official MIME type registered with IANA than it is to make up ones own
1418 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1420 <p
>The desktop file of the rosegarden program failed to list
1421 audio/x-rosegarden in its list of supported MIME types, causing the
1422 file browsers to have no idea what to do with *.rg files:
</p
>
1424 <p
><blockquote
><pre
>
1425 % grep Mime /usr/share/applications/rosegarden.desktop
1426 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1427 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1429 </pre
></blockquote
></p
>
1431 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1432 MimeType= line.
</p
>
1434 <p
>If you run into a file which fail to open the correct program when
1435 selected from the file browser, please check out the output from
1436 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1437 MIME type is registered somewhere under /usr/share/mime/ and check
1438 that some desktop file under /usr/share/applications/ is claiming
1439 support for this MIME type. If not, please report a bug to have it
1445 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1446 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1447 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1448 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1449 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1450 system
</a
> is a user-focused solution in Debian for handling hardware
1451 related packages. The idea is to have a database of mappings between
1452 hardware and packages, and pop up a dialog suggesting for the user to
1453 install the packages to use a given hardware dongle. Some use cases
1454 are when you insert a Yubikey, it proposes to install the software
1455 needed to control it; when you insert a braille reader list it
1456 proposes to install the packages needed to send text to the reader;
1457 and when you insert a ColorHug screen calibrator it suggests to
1458 install the driver for it. The system work well, and even have a few
1459 command line tools to install firmware packages and packages for the
1460 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1462 <p
>The system was initially written using aptdaemon, because I found
1463 good documentation and example code on how to use it. But aptdaemon
1464 is going away and is generally being replaced by
1465 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1466 so Isenkram needed a rewrite. And today, thanks to the great patch
1467 from my college Sunil Mohan Adapa in the FreedomBox project, the
1468 rewrite finally took place. I
've just uploaded a new version of
1469 Isenkram into Debian Unstable with the patch included, and the default
1470 for the background daemon is now to use PackageKit. To check it out,
1471 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1472 and see if it is recognised.
</p
>
1474 <p
>If you want to know what kind of packages isenkram would propose for
1475 the machine it is running on, you can check out the isenkram-lookup
1476 program. This is what it look like on a Thinkpad X230:
</p
>
1478 <p
><blockquote
><pre
>
1494 </pre
></blockquote
></p
>
1496 <p
>The hardware mappings come from several places. The preferred way
1497 is for packages to announce their hardware support using
1498 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1499 cross distribution appstream system
</a
>.
1501 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1502 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1507 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1508 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1509 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1510 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1511 <description><p
>Yesterday I updated the
1512 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1513 package in Debian
</a
> with a few patches sent to me by skilled and
1514 enterprising users. There were some nice user and visible changes.
1515 First of all, both desktop menu entries now work. A design flaw in
1516 one of the script made the history graph fail to show up (its PNG was
1517 dumped in ~/.xsession-errors) if no controlling TTY was available.
1518 The script worked when called from the command line, but not when
1519 called from the desktop menu. I changed this to look for a DISPLAY
1520 variable or a TTY before deciding where to draw the graph, and now the
1521 graph window pop up as expected.
</p
>
1523 <p
>The next new feature is a discharge rate estimator in one of the
1524 graphs (the one showing the last few hours). New is also the user of
1525 colours showing charging in blue and discharge in red. The percentages
1526 of this graph is relative to last full charge, not battery design
1529 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1531 <p
>The other graph show the entire history of the collected battery
1532 statistics, comparing it to the design capacity of the battery to
1533 visualise how the battery life time get shorter over time. The red
1534 line in this graph is what the previous graph considers
100 percent:
1536 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1538 <p
>In this graph you can see that I only charge the battery to
80
1539 percent of last full capacity, and how the capacity of the battery is
1540 shrinking. :(
</p
>
1542 <p
>The last new feature is in the collector, which now will handle
1543 more hardware models. On some hardware, Linux power supply
1544 information is stored in /sys/class/power_supply/ACAD/, while the
1545 collector previously only looked in /sys/class/power_supply/AC/. Now
1546 both are checked to figure if there is power connected to the
1549 <p
>If you are interested in how your laptop battery is doing, please
1551 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1552 in Debian unstable, or rebuild it on Jessie to get it working on
1553 Debian stable. :) The upstream source is available from
<a
1554 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1555 Patches are very welcome.
</p
>
1557 <p
>As usual, if you use Bitcoin and want to show your support of my
1558 activities, please send Bitcoin donations to my address
1559 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1564 <title>Debian now with ZFS on Linux included
</title>
1565 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1566 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1567 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1568 <description><p
>Today, after many years of hard work from many people,
1569 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1570 Debian. The package status can be seen on
1571 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1572 for zfs-linux
</a
>. and
1573 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1574 team status page
</a
>. If you want to help out, please join us.
1575 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1576 source code
</a
> is available via git on Alioth. It would also be
1577 great if you could help out with
1578 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1579 it is an important piece of the puzzle to get ZFS working.
</p
>
1584 <title>What is the best multimedia player in Debian?
</title>
1585 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1587 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1588 <description><p
><strong
>Where I set out to figure out which multimedia player in
1589 Debian claim support for most file formats.
</strong
></p
>
1591 <p
>A few years ago, I had a look at the media support for Browser
1592 plugins in Debian, to get an idea which plugins to include in Debian
1593 Edu. I created a script to extract the set of supported MIME types
1594 for each plugin, and used this to find out which multimedia browser
1595 plugin supported most file formats / media types.
1596 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1597 result
</a
> can still be seen on the Debian wiki, even though it have
1598 not been updated for a while. But browser plugins are less relevant
1599 these days, so I thought it was time to look at standalone
1602 <p
>A few days ago I was tired of VLC not being listed as a viable
1603 player when I wanted to play videos from the Norwegian National
1604 Broadcasting Company, and decided to investigate why. The cause is a
1605 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1606 desktop file
</a
>. In the process I wrote a script to compare the set
1607 of MIME types announced in the desktop file and the browser plugin,
1608 only to discover that there is quite a large difference between the
1609 two for VLC. This discovery made me dig up the script I used to
1610 compare browser plugins, and adjust it to compare desktop files
1611 instead, to try to figure out which multimedia player in Debian
1612 support most file formats.
</p
>
1614 <p
>The result can be seen on the Debian Wiki, as
1615 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1616 table listing all MIME types supported by one of the packages included
1617 in the table
</a
>, with the package supporting most MIME types being
1618 listed first in the table.
</p
>
1620 </p
>The best multimedia player in Debian? It is totem, followed by
1621 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1622 kmplayer. Time for the other players to update their announced MIME
1628 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1629 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1630 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1631 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1632 <description>A friend of mine made me aware of
1633 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1634 handheld computer which will be delivered with Debian preinstalled. I
1635 would love to get one of those for my birthday. :)
</p
>
1637 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1638 plugs and many others connectors, and include a full keyboard and a
5"
1639 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1640 day of battery life time, but I have not seen any independent tests
1641 confirming this. The vendor is still collecting preorders, and the
1642 last I heard last night was that
22 more orders were needed before
1643 production started.
</p
>
1645 <p
>As far as I know, this is the first handheld preinstalled with
1646 Debian. Please let me know if you know of any others. Is it the
1647 first computer being sold with Debian preinstalled?
</p
>
1652 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1653 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1654 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1655 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1656 <description><p
>During this weekends
1657 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1658 squashing party and developer gathering
</a
>, we decided to do our part
1659 to make sure there are good books about Debian available in Norwegian
1660 Bokmål, and got in touch with the people behind the
1661 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1662 project
</a
> to get started. If you want to help out, please start
1664 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1665 hosted weblate project page
</a
>, and get in touch using
1666 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1667 translators mailing list
</a
>. Please also check out
1668 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1669 contributors
</a
>.
</p
>
1671 <p
>The book is already available on paper in English, French and
1672 Japanese, and our goal is to get it available on paper in Norwegian
1673 Bokmål too. In addition to the paper edition, there are also EPUB and
1674 Mobi versions available. And there are incomplete translations
1675 available for many more languages.
</p
>
1680 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1681 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1682 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1683 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1684 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1685 packages in Debian, and was quite surprised with what I found. I use
1686 ZFS myself at home, but did not really expect many others to do so.
1687 But I might be wrong.
</p
>
1689 <p
>According to
1690 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1691 results for spl-linux
</a
>, there are
1019 Debian installations, or
1692 0.53% of the population, with the package installed. As far as I know
1693 the only use of the spl-linux package is as a support library for ZFS
1694 on Linux, so I use it here as proxy for measuring the number of ZFS
1695 installation on Linux in Debian. In the kFreeBSD variant of Debian
1696 the ZFS feature is already available, and there
1697 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1698 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1699 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1701 <p
>But even though the Debian project leader Lucas Nussbaum
1702 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1703 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1704 cleared, the package is still not in Debian. The package is again in
1705 the NEW queue. Several uploads have been rejected so far because the
1706 debian/copyright file was incomplete or wrong, but there is no reason
1707 to give up. The current status can be seen on
1708 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1709 team status page
</a
>, and
1710 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1711 source code
</a
> is available on Alioth.
</p
>
1713 <p
>As I want ZFS to be included in next version of Debian to make sure
1714 my home server can function in the future using only official Debian
1715 packages, and the current blocker is to get the debian/copyright file
1716 accepted by the FTP masters in Debian, I decided a while back to try
1717 to help out the team. This was the background for my blog post about
1718 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1719 updating and checking debian/copyright semi-automatically
</a
>, and I
1720 used the techniques I explored there to try to find any errors in the
1721 copyright file. It is not very easy to check every one of the around
1722 2000 files in the source package, but I hope we this time got it
1723 right. If you want to help out, check out the git source and try to
1724 find missing entries in the debian/copyright file.
</p
>
1729 <title>Full battery stats collector is now available in Debian
</title>
1730 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1731 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1732 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1733 <description><p
>Since this morning, the battery-stats package in Debian include an
1734 extended collector that will collect the complete battery history for
1735 later processing and graphing. The original collector store the
1736 battery level as percentage of last full level, while the new
1737 collector also record battery vendor, model, serial number, design
1738 full level, last full level and current battery level. This make it
1739 possible to predict the lifetime of the battery as well as visualise
1740 the energy flow when the battery is charging or discharging.
</p
>
1742 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1743 in the version
0.5.1 package in unstable. Get the new battery level graph
1744 and lifetime prediction by running:
1746 <p
><pre
>
1747 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1748 </pre
></p
>
1750 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1752 <p
>The flow in/out of the battery can be seen by running (no menu
1753 entry yet):
</p
>
1755 <p
><pre
>
1756 /usr/share/battery-stats/battery-stats-graph-flow
1757 </pre
></p
>
1759 <p
>I
'm not quite happy with the way the data is visualised, at least
1760 when there are few data points. The graphs look a bit better with a
1761 few years of data.
</p
>
1763 <p
>A while back one important feature I use in the battery stats
1764 collector broke in Debian. The scripts in
1765 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1766 suspect it happened when Jessie started using systemd, but I do not
1767 know. The issue is reported as
1768 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1769 pm-utils. I managed to work around it by adding an udev rule to call
1770 the collector script every time the power connector is connected and
1771 disconnected. With this fix in place it was finally time to make a
1772 new release of the package, and get it into Debian.
</p
>
1774 <p
>If you are interested in how your laptop battery is doing, please
1776 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1777 in Debian unstable, or rebuild it on Jessie to get it working on
1778 Debian stable. :) The upstream source is available from
1779 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1780 As always, patches are very welcome.
</p
>
1785 <title>Making battery measurements a little easier in Debian
</title>
1786 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1787 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1788 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1789 <description><p
>Back in September, I blogged about
1790 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1791 system I wrote to collect statistics about my laptop battery
</a
>, and
1792 how it showed the decay and death of this battery (now replaced). I
1793 created a simple deb package to handle the collection and graphing,
1794 but did not want to upload it to Debian as there were already
1795 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1796 package in Debian
</a
> that should do the same thing, and I did not see
1797 a point of uploading a competing package when battery-stats could be
1798 fixed instead. I reported a few bugs about its non-function, and
1799 hoped someone would step in and fix it. But no-one did.
</p
>
1801 <p
>I got tired of waiting a few days ago, and took matters in my own
1802 hands. The end result is that I am now the new upstream developer of
1803 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1804 battery-stats in Debian, and the package in Debian unstable is finally
1805 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1806 information provided by the Linux kernel. If you install the
1807 battery-stats package from unstable now, you will be able to get a
1808 graph of the current battery fill level, to get some idea about the
1809 status of the battery. The source package build and work just fine in
1810 Debian testing and stable (and probably oldstable too, but I have not
1811 tested). The default graph you get for that system look like this:
</p
>
1813 <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
>
1815 <p
>My plans for the future is to merge my old scripts into the
1816 battery-stats package, as my old scripts collected a lot more details
1817 about the battery. The scripts are merged into the upstream
1818 battery-stats git repository already, but I am not convinced they work
1819 yet, as I changed a lot of paths along the way. Will have to test a
1820 bit more before I make a new release.
</p
>
1822 <p
>I will also consider changing the file format slightly, as I
1823 suspect the way I combine several values into one field might make it
1824 impossible to know the type of the value when using it for processing
1825 and graphing.
</p
>
1827 <p
>If you would like I would like to keep an close eye on your laptop
1828 battery, check out the battery-stats package in
1829 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1831 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1832 I would love some help to improve the system further.
</p
>
1837 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1838 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1839 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1840 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1841 <description><p
>Making packages for Debian requires quite a lot of attention to
1842 details. And one of the details is the content of the
1843 debian/copyright file, which should list all relevant licenses used by
1844 the code in the package in question, preferably in
1845 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1846 readable DEP5 format
</a
>.
</p
>
1848 <p
>For large packages with lots of contributors it is hard to write
1849 and update this file manually, and if you get some detail wrong, the
1850 package is normally rejected by the ftpmasters. So getting it right
1851 the first time around get the package into Debian faster, and save
1852 both you and the ftpmasters some work.. Today, while trying to figure
1853 out what was wrong with
1854 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1855 zfsonlinux copyright file
</a
>, I decided to spend some time on
1856 figuring out the options for doing this job automatically, or at least
1857 semi-automatically.
</p
>
1859 <p
>Lucikly, there are at least two tools available for generating the
1860 file based on the code in the source package,
1861 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1862 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1863 not sure which one of them came first, but both seem to be able to
1864 create a sensible draft file. As far as I can tell, none of them can
1865 be trusted to get the result just right, so the content need to be
1866 polished a bit before the file is OK to upload. I found the debmake
1868 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1869 blog posts from
2014</a
>.
1871 <p
>To generate using debmake, use the -cc option:
1873 <p
><pre
>
1874 debmake -cc
> debian/copyright
1875 </pre
></p
>
1877 <p
>Note there are some problems with python and non-ASCII names, so
1878 this might not be the best option.
</p
>
1880 <p
>The cme option is based on a config parsing library, and I found
1882 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1883 blog post from
2015</a
>. To generate using cme, use the
'update
1884 dpkg-copyright
' option:
1886 <p
><pre
>
1887 cme update dpkg-copyright
1888 </pre
></p
>
1890 <p
>This will create or update debian/copyright. The cme tool seem to
1891 handle UTF-
8 names better than debmake.
</p
>
1893 <p
>When the copyright file is created, I would also like some help to
1894 check if the file is correct. For this I found two good options,
1895 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1896 to focus on license types and file matching, and is able to detect
1897 ineffective blocks in the copyright file. The latter reports missing
1898 copyright holders and years, but was confused by inconsistent license
1899 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1900 fix all issues reported by them before uploading. But I do not know
1901 if the tools and the ftpmasters agree on what is important to fix in a
1902 copyright file, so the package might still be rejected.
</p
>
1904 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1905 will read through the source and try to find all copyright statements.
1906 It is not comparing the result to the content of debian/copyright, but
1907 can be useful when verifying the content of the copyright file.
</p
>
1909 <p
>Are you aware of better tools in Debian to create and update
1910 debian/copyright file. Please let me know, or blog about it on
1911 planet.debian.org.
</p
>
1913 <p
>As usual, if you use Bitcoin and want to show your support of my
1914 activities, please send Bitcoin donations to my address
1915 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1917 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1918 on how to use licensecheck and cdbs to create a draft copyright file
1920 <p
><pre
>
1921 licensecheck --copyright -r `find * -type f` | \
1922 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1923 </pre
></p
>
1925 <p
>He mentioned that he normally check the generated file into the
1926 version control system to make it easier to discover license and
1927 copyright changes in the upstream source. I will try to do the same
1928 with my packages in the future.
</p
>
1930 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1931 against using -quiet for new users, so I removed it from the proposed
1932 command line.
</p
>
1937 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1938 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1939 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1940 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1941 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1942 is taking shape in Debian, and one provided feature is a very
1943 convenient way to tell you which package to install to make a given
1944 firmware file available when the kernel is looking for it. This can
1945 be done using apt-file too, but that is for someone else to blog
1948 <p
>Here is a small recipe to find the package with a given firmware
1949 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1950 picked from the set of firmware announced using appstream in Debian
1951 unstable. In general you would be looking for the firmware requested
1952 by the kernel during kernel module loading. To find the package
1953 providing the example file, do like this:
</p
>
1955 <blockquote
><pre
>
1956 % apt install appstream
1960 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1961 awk
'/Package:/ {print $
2}
'
1964 </pre
></blockquote
>
1966 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1967 appstream wiki
</a
> page to learn how to embed the package metadata in
1968 a way appstream can use.
</p
>
1970 <p
>This same approach can be used to find any package supporting a
1971 given MIME type. This is very useful when you get a file you do not
1972 know how to handle. First find the mime type using
<tt
>file
1973 --mime-type
</tt
>, and next look up the package providing support for
1974 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1975 and you can find all packages handling this type like this:
</p
>
1977 <blockquote
><pre
>
1978 % apt install appstream
1982 % appstreamcli what-provides mimetype image/svg+xml | \
1983 awk
'/Package:/ {print $
2}
'
2005 </pre
></blockquote
>
2007 <p
>I believe the MIME types are fetched from the desktop file for
2008 packages providing appstream metadata.
</p
>
2013 <title>Creepy, visualise geotagged social media information - nice free software
</title>
2014 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
2015 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
2016 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
2017 <description><p
>Most people seem not to realise that every time they walk around
2018 with the computerised radio beacon known as a mobile phone their
2019 position is tracked by the phone company and often stored for a long
2020 time (like every time a SMS is received or sent). And if their
2021 computerised radio beacon is capable of running programs (often called
2022 mobile apps) downloaded from the Internet, these programs are often
2023 also capable of tracking their location (if the app requested access
2024 during installation). And when these programs send out information to
2025 central collection points, the location is often included, unless
2026 extra care is taken to not send the location. The provided
2027 information is used by several entities, for good and bad (what is
2028 good and bad, depend on your point of view). What is certain, is that
2029 the private sphere and the right to free movement is challenged and
2030 perhaps even eradicated for those announcing their location this way,
2031 when they share their whereabouts with private and public
2034 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
2036 <p
>The phone company logs provide a register of locations to check out
2037 when one want to figure out what the tracked person was doing. It is
2038 unavailable for most of us, but provided to selected government
2039 officials, company staff, those illegally buying information from
2040 unfaithful servants and crackers stealing the information. But the
2041 public information can be collected and analysed, and a free software
2042 tool to do so is called
2043 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
2044 discovered it when I read
2045 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
2046 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
2047 November
2014, and decided to check if it was available in Debian.
2048 The python program was in Debian, but
2049 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
2050 Debian
</a
> was completely broken and practically unmaintained. I
2051 uploaded a new version which did not work quite right, but did not
2052 have time to fix it then. This Christmas I decided to finally try to
2053 get Creepy operational in Debian. Now a fixed version is available in
2054 Debian unstable and testing, and almost all Debian specific patches
2056 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
2058 <p
>The Creepy program visualises geolocation information fetched from
2059 Twitter, Instagram, Flickr and Google+, and allow one to get a
2060 complete picture of every social media message posted recently in a
2061 given area, or track the movement of a given individual across all
2062 these services. Earlier it was possible to use the search API of at
2063 least some of these services without identifying oneself, but these
2064 days it is impossible. This mean that to use Creepy, you need to
2065 configure it to log in as yourself on these services, and provide
2066 information to them about your search interests. This should be taken
2067 into account when using Creepy, as it will also share information
2068 about yourself with the services.
</p
>
2070 <p
>The picture above show the twitter messages sent from (or at least
2071 geotagged with a position from) the city centre of Oslo, the capital
2072 of Norway. One useful way to use Creepy is to first look at
2073 information tagged with an area of interest, and next look at all the
2074 information provided by one or more individuals who was in the area.
2075 I tested it by checking out which celebrity provide their location in
2076 twitter messages by checkout out who sent twitter messages near a
2077 Norwegian TV station, and next could track their position over time,
2078 making it possible to locate their home and work place, among other
2079 things. A similar technique have been
2080 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2081 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2082 tool to discover lying governments, and a useful tool to help people
2083 understand the value of the private information they provide to the
2086 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2087 it depend on several python modules currently missing in Jessie (at
2088 least python-instagram, python-flickrapi and
2089 python-requests-toolbelt).
</p
>
2091 <p
>(I have uploaded
2092 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2093 screenshots.debian.net
</a
> and licensed it under the same terms as the
2094 Creepy program in Debian.)
</p
>
2099 <title>Always download Debian packages using Tor - the simple recipe
</title>
2100 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2101 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2102 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2103 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2104 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2105 that those listening on the Internet lines would have good reason to
2106 believe a computer have a given security hole
</a
> if it download a
2107 security fix from a Debian mirror. This is a good reason to always
2108 use encrypted connections to the Debian mirror, to make sure those
2109 listening do not know which IP address to attack. In August, Richard
2110 Hartmann observed that encryption was not enough, when it was possible
2111 to interfere download size to security patches or the fact that
2112 download took place shortly after a security fix was released, and
2113 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2114 to always use Tor to download packages from the Debian mirror
</a
>. He
2115 was not the first to propose this, as the
2116 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2117 package by Tim Retout already existed to make it easy to convince apt
2118 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2119 aware of that package when I read the blog post from Richard.
</p
>
2121 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2122 sysadmins, and he set up a Tor hidden service on one of the central
2123 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2124 it possible to download packages directly between two tor nodes,
2125 making sure the network traffic always were encrypted.
</p
>
2127 <p
>Here is a short recipe for enabling this on your machine, by
2128 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2129 urls with tor+http and tor+https, and using the hidden service instead
2130 of the official Debian mirror site. I recommend installing
2131 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2132 done in /etc/.
</p
>
2134 <blockquote
><pre
>
2135 apt install apt-transport-tor
2136 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2137 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2138 </pre
></blockquote
>
2140 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2141 the sed commands for these too. The sed command is assuming your are
2142 using the ftp.debian.org Debian mirror. Adjust the command (or just
2143 edit the file manually) to match your mirror.
</p
>
2145 <p
>This work in Debian Jessie and later. Note that tools like
2146 <tt
>apt-file
</tt
> only recently started using the apt transport
2147 system, and do not work with these tor+http URLs. For
2148 <tt
>apt-file
</tt
> you need the version currently in experimental,
2149 which need a recent apt version currently only in unstable. So if you
2150 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2152 <p
>Another advantage from this change is that your machine will start
2153 using Tor regularly and at fairly random intervals (every time you
2154 update the package lists or upgrade or install a new package), thus
2155 masking other Tor traffic done from the same machine. Using Tor will
2156 become normal for the machine in question.
</p
>
2158 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2159 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2160 enabled. It would be great if it was the default on any Debian
2166 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2167 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2168 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2169 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2170 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2171 call the car license plate numbers in those days. I would write the
2172 numbers down in my little book and compare notes with the other kids
2173 to see how many region codes we had seen and if we had seen some
2174 exotic or special region codes and numbers. It was a fun game to pass
2175 time, as we kids have plenty of it.
</p
>
2177 <p
>A few days I came across
2178 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2179 project
</a
>, a free software project to automatically discover and
2180 report license plates in images and video streams, and provide the
2181 "car numbers
" in a machine readable format. I
've been looking for
2182 such system for a while now, because I believe it is a bad idea that the
2183 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2184 number plate recognition
</a
> tool only is available in the hands of
2185 the powerful, and want it to be available also for the powerless to
2186 even the score when it comes to surveillance and sousveillance. I
2187 discovered the developer
2188 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2189 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2190 help him get it into shape to get the package uploaded into the Debian
2193 <p
>Today we finally managed to get the package into shape and uploaded
2194 it into Debian, where it currently
2195 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2196 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2198 <p
>I guess you are wondering why on earth such tool would be useful
2199 for the common folks, ie those not running a large government
2200 surveillance system? Well, I plan to put it in a computer on my bike
2201 and in my car, tracking the cars nearby and allowing me to be notified
2202 when number plates on my watch list are discovered. Another use case
2203 was suggested by a friend of mine, who wanted to set it up at his home
2204 to open the car port automatically when it discovered the plate on his
2205 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2206 capable of placing his license plate number of a piece of cardboard to
2207 open his car port, men replied that it was always unlocked anyway. I
2208 guess for such use case it make sense. I am sure there are other use
2209 cases too, for those with imagination and a vision.
</p
>
2211 <p
>If you want to build your own version of the Debian package, check
2212 out the upstream git source and symlink ./distros/debian to ./debian/
2213 before running
"debuild
" to build the source. Or wait a bit until the
2214 package show up in unstable.
</p
>
2219 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2220 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2221 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2222 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2223 <description><p
>Around three years ago, I created
2224 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2225 system
</a
> to get a more practical solution in Debian for handing
2226 hardware related packages. A GUI system in the isenkram package will
2227 present a pop-up dialog when some hardware dongle supported by
2228 relevant packages in Debian is inserted into the machine. The same
2229 lookup mechanism to detect packages is available as command line
2230 tools in the isenkram-cli package. In addition to mapping hardware,
2231 it will also map kernel firmware files to packages and make it easy to
2232 install needed firmware packages automatically. The key for this
2233 system to work is a good way to map hardware to packages, in other
2234 words, allow packages to announce what hardware they will work
2237 <p
>I started by providing data files in the isenkram source, and
2238 adding code to download the latest version of these data files at run
2239 time, to ensure every user had the most up to date mapping available.
2240 I also added support for storing the mapping in the Packages file in
2241 the apt repositories, but did not push this approach because while I
2242 was trying to figure out how to best store hardware/package mappings,
2243 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2244 appstream system
</a
> was announced. I got in touch and suggested to
2245 add the hardware mapping into that data set to be able to use
2246 appstream as a data source, and this was accepted at least for the
2247 Debian version of appstream.
</p
>
2249 <p
>A few days ago using appstream in Debian for this became possible,
2250 and today I uploaded a new version
0.20 of isenkram adding support for
2251 appstream as a data source for mapping hardware to packages. The only
2252 package so far using appstream to announce its hardware support is my
2253 pymissile package. I got help from Matthias Klumpp with figuring out
2254 how do add the required
2255 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2256 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2257 this content:
</p
>
2259 <blockquote
><pre
>
2260 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2261 &lt;component
&gt;
2262 &lt;id
&gt;pymissile
&lt;/id
&gt;
2263 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2264 &lt;name
&gt;pymissile
&lt;/name
&gt;
2265 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2266 &lt;description
&gt;
2268 Pymissile provides a curses interface to control an original
2269 Marks and Spencer / Striker USB Missile Launcher, as well as a
2270 motion control script to allow a webcamera to control the
2273 &lt;/description
&gt;
2274 &lt;provides
&gt;
2275 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2276 &lt;/provides
&gt;
2277 &lt;/component
&gt;
2278 </pre
></blockquote
>
2280 <p
>The key for isenkram is the component/provides/modalias value,
2281 which is a glob style match rule for hardware specific strings
2282 (modalias strings) provided by the Linux kernel. In this case, it
2283 will map to all USB devices with vendor code
1130 and product code
2286 <p
>Note, it is important that the license of all the metadata files
2287 are compatible to have permissions to aggregate them into archive wide
2288 appstream files. Matthias suggested to use MIT or BSD licenses for
2289 these files. A challenge is figuring out a good id for the data, as
2290 it is supposed to be globally unique and shared across distributions
2291 (in other words, best to coordinate with upstream what to use). But
2292 it can be changed later or, so we went with the package name as
2293 upstream for this project is dormant.
</p
>
2295 <p
>To get the metadata file installed in the correct location for the
2296 mirror update scripts to pick it up and include its content the
2297 appstream data source, the file must be installed in the binary
2298 package under /usr/share/appdata/. I did this by adding the following
2299 line to debian/pymissile.install:
</p
>
2301 <blockquote
><pre
>
2302 debian/pymissile.metainfo.xml usr/share/appdata
2303 </pre
></blockquote
>
2305 <p
>With that in place, the command line tool isenkram-lookup will list
2306 all packages useful on the current computer automatically, and the GUI
2307 pop-up handler will propose to install the package not already
2308 installed if a hardware dongle is inserted into the machine in
2311 <p
>Details of the modalias field in appstream is available from the
2312 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2314 <p
>To locate the modalias values of all hardware present in a machine,
2315 try running this command on the command line:
</p
>
2317 <blockquote
><pre
>
2318 cat $(find /sys/devices/|grep modalias)
2319 </pre
></blockquote
>
2321 <p
>To learn more about the isenkram system, please check out
2322 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2323 blog posts tagged isenkram
</a
>.
</p
>
2328 <title>The GNU General Public License is not magic pixie dust
</title>
2329 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2330 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2331 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2332 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2333 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2334 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2335 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2336 I quote the blog post from Paul in full here with his permission:
<p
>
2340 <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
>
2343 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2345 The first step is to choose a
2346 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2349 The next step is, when someone fails to follow that copyleft license,
2350 <b
>it must be enforced
</b
><br/
>
2352 and its a simple fact of our modern society that such type of
2355 is incredibly expensive to do and incredibly difficult to do.
2358 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2359 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2360 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2361 0x57</a
></small
></p
>
2363 <p
>As the Debian Website
2364 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2365 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2366 imply, public domain and permissively licensed software can lead to
2367 the production of more proprietary software as people discover useful
2368 software, extend it and or incorporate it into their hardware or
2369 software products. Copyleft licenses such as the GNU GPL were created
2370 to close off this avenue to the production of proprietary software but
2371 such licenses are not enough. With the ongoing adoption of Free
2372 Software by individuals and groups, inevitably the community
's
2373 expectations of license compliance are violated, usually out of
2374 ignorance of the way Free Software works, but not always. As Karen
2375 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2376 Freedom
">FaiF
</a
>
2377 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2378 copyleft is nothing if no-one is willing and able to stand up in court
2379 to protect it. The reality of today
's world is that legal
2380 representation is expensive, difficult and time consuming. With
2381 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2382 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2383 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2384 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2385 of the Linux project, Debian and other groups against GPL violations.
2386 In March the SFC supported a
2387 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2388 by Christoph Hellwig
</a
> against VMware for refusing to
2389 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2390 with the GPL
</a
> in relation to their use of parts of the Linux
2391 kernel. Since then two of their sponsors pulled corporate funding and
2393 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2394 or cancelled their talks
</a
>. As a result they have decided to rely
2395 less on corporate funding and more on the broad community of
2396 individuals who support Free Software and copyleft. So the SFC has
2397 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2398 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2399 a community of folks who stand up for copyleft and the GPL by
2400 supporting their work on promoting and supporting copyleft and Free
2403 <p
>If you support Free Software,
2404 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2405 what the SFC do, agree with their
2406 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2407 principles
</a
>, are happy about their
2408 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2409 work on a project that is an SFC
2410 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2411 just want to stand up for copyleft, please join
2412 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2413 Allan Webber
</a
>,
2414 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2416 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2417 Bacon
</a
>, myself and
2418 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2420 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2421 next week your donation will be
2422 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2423 by an anonymous donor. Please also consider asking your employer to
2424 match your donation or become a sponsor of SFC. Don
't forget to
2425 spread the word about your support for SFC via email, your blog and or
2426 social media accounts.
</p
>
2430 <p
>I agree with Paul on this topic and just signed up as a Supporter
2431 of Software Freedom Conservancy myself. Perhaps you should be a
2432 supporter too?
</p
>
2437 <title>PGP key transition statement for key EE4E02F9
</title>
2438 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2439 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2440 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2441 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2442 set it up properly. I wanted to generate it offline and have it
2443 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2444 smart card
</a
> for daily use, and learning how to do it and finding
2445 time to sit down with an offline machine almost took forever. But
2446 finally I
've been able to complete the process, and have now moved
2447 from my old GPG key to a new GPG key. See
2448 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2449 full transition statement, signed with both my old and new key
</a
> for
2450 the details. This is my new key:
</p
>
2453 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2454 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2455 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2456 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2457 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2458 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2459 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2462 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2463 my old key.
</p
>
2465 <p
>If you signed my old key
2466 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2467 I
'd very much appreciate a signature on my new key, details and
2468 instructions in the transition statement. I m happy to reciprocate if
2469 you have a similarly signed transition statement to present.
</p
>
2474 <title>The life and death of a laptop battery
</title>
2475 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2476 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2477 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2478 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2479 But this do not last. The last few laptops gave me a feeling that
2480 within a year, the life time is just a fraction of what it used to be,
2481 and it slowly become painful to use the laptop without power connected
2482 all the time. Because of this, when I got a new Thinkpad X230 laptop
2483 about two years ago, I decided to monitor its battery state to have
2484 more hard facts when the battery started to fail.
</p
>
2486 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2488 <p
>First I tried to find a sensible Debian package to record the
2489 battery status, assuming that this must be a problem already handled
2490 by someone else. I found
2491 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2492 which collects statistics from the battery, but it was completely
2493 broken. I sent a few suggestions to the maintainer, but decided to
2494 write my own collector as a shell script while I waited for feedback
2496 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2497 blog post about the battery development on a MacBook Air
</a
> I also
2499 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2500 available in Debian.
</p
>
2502 <p
>I started my collector
2013-
07-
15, and it has been collecting
2503 battery stats ever since. Now my
2504 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2505 measurements, from the time the battery was working great until now,
2506 when it is unable to charge above
7% of original capacity. My
2507 collector shell script is quite simple and look like this:
</p
>
2512 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2514 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2515 logfile=/var/log/hjemmenett-battery-status.log
2517 files=
"manufacturer model_name technology serial_number \
2518 energy_full energy_full_design energy_now cycle_count status
"
2520 if [ ! -e
"$logfile
" ] ; then
2522 printf
"timestamp,
"
2524 printf
"%s,
" $f
2527 )
> "$logfile
"
2531 # Print complete message in one echo call, to avoid race condition
2532 # when several log processes run in parallel.
2533 msg=$(printf
"%s,
" $(date +%s); \
2534 for f in $files; do \
2535 printf
"%s,
" $(cat $f); \
2537 echo
"$msg
"
2540 cd /sys/class/power_supply
2543 (cd $bat
&& log_battery
>> "$logfile
")
2547 <p
>The script is called when the power management system detect a
2548 change in the power status (power plug in or out), and when going into
2549 and out of hibernation and suspend. In addition, it collect a value
2550 every
10 minutes. This make it possible for me know when the battery
2551 is discharging, charging and how the maximum charge change over time.
2552 The code for the Debian package
2553 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2554 available on github
</a
>.
</p
>
2556 <p
>The collected log file look like this:
</p
>
2559 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2560 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2562 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2563 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2566 <p
>I wrote a small script to create a graph of the charge development
2567 over time. This graph depicted above show the slow death of my laptop
2570 <p
>But why is this happening? Why are my laptop batteries always
2571 dying in a year or two, while the batteries of space probes and
2572 satellites keep working year after year. If we are to believe
2573 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2574 University
</a
>, the cause is me charging the battery whenever I have a
2575 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2576 all the time, but to stay below
90% of full charge most of the time.
2577 I
've been told that the Tesla electric cars
2578 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2579 the charge of their batteries to
80%
</a
>, with the option to charge to
2580 100% when preparing for a longer trip (not that I would want a car
2581 like Tesla where rights to privacy is abandoned, but that is another
2582 story), which I guess is the option we should have for laptops on
2583 Linux too.
</p
>
2585 <p
>Is there a good and generic way with Linux to tell the battery to
2586 stop charging at
80%, unless requested to charge to
100% once in
2587 preparation for a longer trip? I found
2588 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2589 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2590 80%
</a
>, but could not get it to work (kernel module refused to
2593 <p
>I wonder why the battery capacity was reported to be more than
100%
2594 at the start. I also wonder why the
"full capacity
" increases some
2595 times, and if it is possible to repeat the process to get the battery
2596 back to design capacity. And I wonder if the discharge and charge
2597 speed change over time, or if this stay the same. I did not yet try
2598 to write a tool to calculate the derivative values of the battery
2599 level, but suspect some interesting insights might be learned from
2602 <p
>Update
2015-
09-
24: I got a tip to install the packages
2603 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2604 packages instead of the tp-smapi-dkms package I had tried to use
2605 initially, and use
'tlp setcharge
40 80' to change when charging start
2606 and stop. I
've done so now, but expect my existing battery is toast
2607 and need to be replaced. The proposal is unfortunately Thinkpad
2613 <title>New laptop - some more clues and ideas based on feedback
</title>
2614 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2616 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2617 <description><p
>Several people contacted me after my previous blog post about my
2618 need for a new laptop, and provided very useful feedback. I wish to
2619 thank every one of these. Several pointed me to the possibility of
2620 fixing my X230, and I am already in the process of getting Lenovo to
2621 do so thanks to the on site, next day support contract covering the
2622 machine. But the battery is almost useless (I expect to replace it
2623 with a non-official battery) and I do not expect the machine to live
2624 for many more years, so it is time to plan its replacement. If I did
2625 not have a support contract, it was suggested to find replacement parts
2626 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2627 might present a language barrier as I do not understand French.
</p
>
2629 <p
>One tip I got was to use the
2630 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2631 compare laptop models. It seem to have more models available than
2632 prisjakt.no. Another tip I got from someone I know have similar
2633 keyboard preferences was that the HP EliteBook
840 keyboard is not
2634 very good, and this matches my experience with earlier EliteBook
2635 keyboards I tested. Because of this, I will not consider it any further.
2637 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2638 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2639 (which is missing from the X240), and is working fairly well with
2640 Debian Sid/Unstable according to
2641 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2642 got on the keyboard quality are not consistent. Some say the keyboard
2643 is good, others say it is ok, while others say it is not very good.
2644 Those with experience from X41 and and X60 agree that the X250
2645 keyboard is not as good as those trusty old laptops, and suggest I
2646 keep and fix my X230 instead of upgrading, or get a used X230 to
2647 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2648 activity and battery status, which is very convenient on my X230. I
'm
2649 also told that the CPU fan is running very often, making it a bit
2650 noisy. In any case, the X250 do not work out of the box with Debian
2651 Stable/Jessie, one of my requirements.
</p
>
2653 <p
>I have also gotten a few vendor proposals, one was
2654 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2655 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2656 The latter look very attractive to me.
</p
>
2658 <p
>Again, thank you all for the very useful feedback. It help a lot
2659 as I keep looking for a replacement.
</p
>
2661 <p
>Update
2015-
07-
06: I was recommended to check out the
2662 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2664 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2665 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2670 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2671 <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>
2672 <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>
2673 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2674 <description><p
>My primary work horse laptop is failing, and will need a
2675 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2676 started flickering yesterday, and I suspect the cause is a broken
2677 cable, as changing the angle of the screen some times get rid of the
2678 flickering.
</p
>
2680 <p
>My requirements have not really changed since I bought it, and is
2682 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2683 described them in
2013</a
>. The last time I bought a laptop, I had
2685 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2686 where I could select at least a few of the requirements (mouse pin,
2687 wifi, weight) and go through the rest manually. Three button mouse
2688 and a good keyboard is not available as an option, and all the three
2689 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2690 G2) lack three mouse buttons). It is also unclear to me how good the
2691 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2692 the keyboard, even if the quality and robustness in the X series have
2693 deteriorated since X41.
</p
>
2695 <p
>I wonder how I can find a sensible laptop when none of the options
2696 seem sensible to me? Are there better services around to search the
2697 set of available laptops for features? Please send me an email if you
2698 have suggestions.
</p
>
2700 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2701 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2702 of endorsed hardware
</a
>, which is useful background information.
</p
>
2707 <title>How to stay with sysvinit in Debian Jessie
</title>
2708 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2710 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2711 <description><p
>By now, it is well known that Debian Jessie will not be using
2712 sysvinit as its boot system by default. But how can one keep using
2713 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2715 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2716 Schubert
</a
> and
2717 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2720 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2721 keep sysvinit as your boot system, create a file
2722 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2723 you upgrade:
</p
>
2725 <p
><blockquote
><pre
>
2726 Package: systemd-sysv
2727 Pin: release o=Debian
2729 </pre
></blockquote
><p
>
2731 <p
>This file content will tell apt and aptitude to not consider
2732 installing systemd-sysv as part of any installation and upgrade
2733 solution when resolving dependencies, and thus tell it to avoid
2734 systemd as a default boot system. The end result should be that the
2735 upgraded system keep using sysvinit.
</p
>
2737 <p
>If you are installing Jessie for the first time, there is no way to
2738 get sysvinit installed by default (debootstrap used by
2739 debian-installer have no option for this), but one can tell the
2740 installer to switch to sysvinit before the first boot. Either by
2741 using a kernel argument to the installer, or by adding a line to the
2742 preseed file used. First, the kernel command line argument:
2744 <p
><blockquote
><pre
>
2745 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2746 </pre
></blockquote
><p
>
2748 <p
>Next, the line to use in a preseed file:
</p
>
2750 <p
><blockquote
><pre
>
2751 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2752 </pre
></blockquote
><p
>
2754 <p
>One can of course also do this after the first boot by installing
2755 the sysvinit-core package.
</p
>
2757 <p
>I recommend only using sysvinit if you really need it, as the
2758 sysvinit boot sequence in Debian have several hardware specific bugs
2759 on Linux caused by the fact that it is unpredictable when hardware
2760 devices show up during boot. But on the other hand, the new default
2761 boot system still have a few rough edges I hope will be fixed before
2762 Jessie is released.
</p
>
2764 <p
>Update
2014-
11-
26: Inspired by
2765 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2766 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2772 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2773 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2774 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2775 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2776 <description><p
>The right to communicate with your friends and family in private,
2777 without anyone snooping, is a right every citicen have in a liberal
2778 democracy. But this right is under serious attack these days.
</p
>
2780 <p
>A while back it occurred to me that one way to make the dragnet
2781 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2782 the whisleblower Snowden) more expensive for Internet email,
2783 is to deliver all email using SMTP via Tor. Such SMTP option would be
2784 a nice addition to the FreedomBox project if we could send email
2785 between FreedomBox machines without leaking metadata about the emails
2786 to the people peeking on the wire. I
2787 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2788 this on the FreedomBox project mailing list in October
</a
> and got a
2789 lot of useful feedback and suggestions. It also became obvious to me
2790 that this was not a novel idea, as the same idea was tested and
2791 documented by Johannes Berg as early as
2006, and both
2792 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2793 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2794 propose a similar method / protocol to pass emails between users.
</p
>
2796 <p
>To implement such system one need to set up a Tor hidden service
2797 providing the SMTP protocol on port
25, and use email addresses
2798 looking like username@hidden-service-name.onion. With such addresses
2799 the connections to port
25 on hidden-service-name.onion using Tor will
2800 go to the correct SMTP server. To do this, one need to configure the
2801 Tor daemon to provide the hidden service and the mail server to accept
2802 emails for this .onion domain. To learn more about Exim configuration
2803 in Debian and test the design provided by Johannes Berg in his FAQ, I
2804 set out yesterday to create a Debian package for making it trivial to
2805 set up such SMTP over Tor service based on Debian. Getting it to work
2806 were fairly easy, and
2807 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2808 source code for the Debian package
</a
> is available from github. I
2809 plan to move it into Debian if further testing prove this to be a
2810 useful approach.
</p
>
2812 <p
>If you want to test this, set up a blank Debian machine without any
2813 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2814 get rid of exim4). Install tor, clone the git repository mentioned
2815 above, build the deb and install it on the machine. Next, run
2816 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2817 the instructions to get the service up and running. Restart tor and
2818 exim when it is done, and test mail delivery using swaks like
2821 <p
><blockquote
><pre
>
2822 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2823 --to fbx@dutlqrrmjhtfa3vp.onion
2824 </pre
></blockquote
></p
>
2826 <p
>This will test the SMTP delivery using tor. Replace the email
2827 address with your own address to test your server. :)
</p
>
2829 <p
>The setup procedure is still to complex, and I hope it can be made
2830 easier and more automatic. Especially the tor setup need more work.
2831 Also, the package include a tor-smtp tool written in C, but its task
2832 should probably be rewritten in some script language to make the deb
2833 architecture independent. It would probably also make the code easier
2834 to review. The tor-smtp tool currently need to listen on a socket for
2835 exim to talk to it and is started using xinetd. It would be better if
2836 no daemon and no socket is needed. I suspect it is possible to get
2837 exim to run a command line tool for delivery instead of talking to a
2838 socket, and hope to figure out how in a future version of this
2841 <p
>Until I wipe my test machine, I can be reached using the
2842 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2843 SMTorP. :)
</p
>
2848 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2849 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2850 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2851 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2852 <description><p
>If you ever had to moderate a mailman list, like the ones on
2853 alioth.debian.org, you know the web interface is fairly slow to
2854 operate. First you visit one web page, enter the moderation password
2855 and get a new page shown with a list of all the messages to moderate
2856 and various options for each email address. This take a while for
2857 every list you moderate, and you need to do it regularly to do a good
2858 job as a list moderator. But there is a quick alternative,
2859 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2860 listadmin program
</a
>. It allow you to check lists for new messages
2861 to moderate in a fraction of a second. Here is a test run on two
2862 lists I recently took over:
</p
>
2864 <p
><blockquote
><pre
>
2865 % time listadmin xiph
2866 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2867 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2873 </pre
></blockquote
></p
>
2875 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2876 there are no message in the moderation queue. Every morning I
2877 currently moderate
68 mailman lists, and it normally take around two
2878 minutes. When I took over the two pkg-xiph lists above a few days
2879 ago, there were
400 emails waiting in the moderator queue. It took me
2880 less than
15 minutes to process them all using the listadmin
2883 <p
>If you install
2884 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2885 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2886 with content like this, the moderation task is a breeze:
</p
>
2888 <p
><blockquote
><pre
>
2889 username username@example.org
2892 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2895 adminurl https://{domain}/mailman/admindb/{list}
2896 mailman-list@lists.example.com
2899 other-list@otherserver.example.org
2900 </pre
></blockquote
></p
>
2902 <p
>There are other options to set as well. Check the manual page to
2903 learn the details.
</p
>
2905 <p
>If you are forced to moderate lists on a mailman installation where
2906 the SSL certificate is self signed or not properly signed by a
2907 generally accepted signing authority, you can set a environment
2908 variable when calling listadmin to disable SSL verification:
</p
>
2910 <p
><blockquote
><pre
>
2911 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2912 </pre
></blockquote
></p
>
2914 <p
>If you want to moderate a subset of the lists you take care of, you
2915 can provide an argument to the listadmin script like I do in the
2916 initial screen dump (the xiph argument). Using an argument, only
2917 lists matching the argument string will be processed. This make it
2918 quick to accept messages if you notice the moderation request in your
2921 <p
>Without the listadmin program, I would never be the moderator of
68
2922 mailing lists, as I simply do not have time to spend on that if the
2923 process was any slower. The listadmin program have saved me hours of
2924 time I could spend elsewhere over the years. It truly is nice free
2927 <p
>As usual, if you use Bitcoin and want to show your support of my
2928 activities, please send Bitcoin donations to my address
2929 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2931 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2932 configuration example. Also, I
've been told that the
2933 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2939 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2940 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2941 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2942 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2943 <description><p
>When PXE installing laptops with Debian, I often run into the
2944 problem that the WiFi card require some firmware to work properly.
2945 And it has been a pain to fix this using preseeding in Debian.
2946 Normally something more is needed. But thanks to
2947 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2948 package
</a
> and its recent tasksel extension, it has now become easy
2949 to do this using simple preseeding.
</p
>
2951 <p
>The isenkram-cli package provide tasksel tasks which will install
2952 firmware for the hardware found in the machine (actually, requested by
2953 the kernel modules for the hardware). (It can also install user space
2954 programs supporting the hardware detected, but that is not the focus
2955 of this story.)
</p
>
2957 <p
>To get this working in the default installation, two preeseding
2958 values are needed. First, the isenkram-cli package must be installed
2959 into the target chroot (aka the hard drive) before tasksel is executed
2960 in the pkgsel step of the debian-installer system. This is done by
2961 preseeding the base-installer/includes debconf value to include the
2962 isenkram-cli package. The package name is next passed to debootstrap
2963 for installation. With the isenkram-cli package in place, tasksel
2964 will automatically use the isenkram tasks to detect hardware specific
2965 packages for the machine being installed and install them, because
2966 isenkram-cli contain tasksel tasks.
</p
>
2968 <p
>Second, one need to enable the non-free APT repository, because
2969 most firmware unfortunately is non-free. This is done by preseeding
2970 the apt-mirror-setup step. This is unfortunate, but for a lot of
2971 hardware it is the only option in Debian.
</p
>
2973 <p
>The end result is two lines needed in your preseeding file to get
2974 firmware installed automatically by the installer:
</p
>
2976 <p
><blockquote
><pre
>
2977 base-installer base-installer/includes string isenkram-cli
2978 apt-mirror-setup apt-setup/non-free boolean true
2979 </pre
></blockquote
></p
>
2981 <p
>The current version of isenkram-cli in testing/jessie will install
2982 both firmware and user space packages when using this method. It also
2983 do not work well, so use version
0.15 or later. Installing both
2984 firmware and user space packages might give you a bit more than you
2985 want, so I decided to split the tasksel task in two, one for firmware
2986 and one for user space programs. The firmware task is enabled by
2987 default, while the one for user space programs is not. This split is
2988 implemented in the package currently in unstable.
</p
>
2990 <p
>If you decide to give this a go, please let me know (via email) how
2991 this recipe work for you. :)
</p
>
2993 <p
>So, I bet you are wondering, how can this work. First and
2994 foremost, it work because tasksel is modular, and driven by whatever
2995 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2996 isenkram-cli package place two files for tasksel to find. First there
2997 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2999 <p
><blockquote
><pre
>
3000 Task: isenkram-packages
3002 Description: Hardware specific packages (autodetected by isenkram)
3003 Based on the detected hardware various hardware specific packages are
3005 Test-new-install: show show
3007 Packages: for-current-hardware
3009 Task: isenkram-firmware
3011 Description: Hardware specific firmware packages (autodetected by isenkram)
3012 Based on the detected hardware various hardware specific firmware
3013 packages are proposed.
3014 Test-new-install: mark show
3016 Packages: for-current-hardware-firmware
3017 </pre
></blockquote
></p
>
3019 <p
>The key parts are Test-new-install which indicate how the task
3020 should be handled and the Packages line referencing to a script in
3021 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
3022 list of packages to install. The for-current-hardware-firmware script
3023 look like this to list relevant firmware for the machine:
3025 <p
><blockquote
><pre
>
3028 PATH=/usr/sbin:$PATH
3030 isenkram-autoinstall-firmware -l
3031 </pre
></blockquote
></p
>
3033 <p
>With those two pieces in place, the firmware is installed by
3034 tasksel during the normal d-i run. :)
</p
>
3036 <p
>If you want to test what tasksel will install when isenkram-cli is
3037 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
3038 --new-install
</tt
> to get the list of packages that tasksel would
3041 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
3042 pilots in testing this feature, as isenkram is used there now to
3043 install firmware, replacing the earlier scripts.
</p
>
3048 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
3049 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
3050 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
3051 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
3052 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
3053 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
3054 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
3055 on a screen normally showing the bread types and prizes:
</p
>
3057 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
3059 <p
>If it had booted as it was supposed to, I would never had known
3060 about this hidden Linux installation. It is interesting what
3061 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3066 <title>New lsdvd release version
0.17 is ready
</title>
3067 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3068 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3069 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3070 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3071 got a new set of developers a few weeks ago, after the original
3072 developer decided to step down and pass the project to fresh blood.
3073 This project is now maintained by Petter Reinholdtsen and Steve
3076 <p
>I just wrapped up
3077 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3078 new lsdvd release
</a
>, available in git or from
3079 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3080 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3085 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3086 <li
>Check for garbage in the program chains, which indicate that a track is
3087 non-existant, to work around additional copy protection
</li
>
3088 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3089 <li
>Fix pallete display of first entry
</li
>
3090 <li
>Fix include orders
</li
>
3091 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3092 <li
>Fix the chapter count
</li
>
3093 <li
>Make sure the array size and the array limit used when initialising
3094 the palette size is the same.
</li
>
3095 <li
>Fix array printing.
</li
>
3096 <li
>Correct subsecond calculations.
</li
>
3097 <li
>Add sector information to the output format.
</li
>
3098 <li
>Clean up code to be closer to ANSI C and compile without warnings
3099 with more GCC compiler warnings.
</li
>
3103 <p
>This change bring together patches for lsdvd in use in various
3104 Linux and Unix distributions, as well as patches submitted to the
3105 project the last nine years. Please check it out. :)
</p
>
3110 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3111 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3113 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3114 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3115 project
</a
> provide a Linux solution for schools, including a
3116 powerful desktop with education software, a central server providing
3117 web pages, user database, user home directories, central login and PXE
3118 boot of both clients without disk and the installation to install Debian
3119 Edu on machines with disk (and a few other services perhaps to small
3120 to mention here). We in the Debian Edu team are currently working on
3121 the Jessie based version, trying to get everything in shape before the
3122 freeze, to avoid having to maintain our own package repository in the
3124 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3125 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3126 work left. Some fatal problems block testing, breaking the installer,
3127 but it is possible to work around these to get anyway. Here is a
3128 recipe on how to get the installation limping along.
</p
>
3130 <p
>First, download the test ISO via
3131 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3132 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3134 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3135 The ISO build was broken on Tuesday, so we do not get a new ISO every
3136 12 hours or so, but thankfully the ISO we already got we are able to
3137 install with some tweaking.
</p
>
3139 <p
>When you get to the Debian Edu profile question, go to tty2
3140 (use Alt-Ctrl-F2), run
</p
>
3142 <p
><blockquote
><pre
>
3143 nano /usr/bin/edu-eatmydata-install
3144 </pre
></blockquote
></p
>
3146 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3147 optimization. Return to the installation, select the profile you want
3148 and continue. Without this change, exim4-config will fail to install
3149 due to a known bug in eatmydata.
</p
>
3151 <p
>When you get the grub question at the end, answer /dev/sda (or if
3152 this do not work, figure out what your correct value would be. All my
3153 test machines need /dev/sda, so I have no advice if it do not fit
3154 your need.
</p
>
3156 <p
>If you installed a profile including a graphical desktop, log in as
3157 root after the initial boot from hard drive, and install the
3158 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3159 or mate. If you want several desktop options, install more than one
3160 metapackage. Once this is done, reboot and you should have a working
3161 graphical login screen. This workaround should no longer be needed
3162 once the education-tasks package version
1.801 enter testing in two
3165 <p
>I believe the ISO build will start working on two days when the new
3166 tasksel package enter testing and Steve McIntyre get a chance to
3167 update the debian-cd git repository. The eatmydata, grub and desktop
3168 issues are already fixed in unstable and testing, and should show up
3169 on the ISO as soon as the ISO build start working again. Well the
3170 eatmydata optimization is really just disabled. The proper fix
3171 require an upload by the eatmydata maintainer applying the patch
3172 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3173 The rest have proper fixes in unstable.
</p
>
3175 <p
>I hope this get you going with the installation testing, as we are
3176 quickly running out of time trying to get our Jessie based
3177 installation ready before the distribution freeze in a month.
</p
>
3182 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3183 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3184 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3185 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3186 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3187 to handle my fairly large DVD collection. It is a nice command line
3188 tool to get details about a DVD, like title, tracks, track length,
3189 etc, in XML, Perl or human readable format. But lsdvd have not seen
3190 any new development since
2006 and had a few irritating bugs affecting
3191 its use with some DVDs. Upstream seemed to be dead, and in January I
3192 sent a small probe asking for a version control repository for the
3193 project, without any reply. But I use it regularly and would like to
3194 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3195 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3196 the project admin, and after getting a reply from him explaining that
3197 he was no longer interested in the project, I asked if I could take
3198 over. And yesterday, I became project admin.
</p
>
3200 <p
>I
've been in touch with a Gentoo developer and the Debian
3201 maintainer interested in joining forces to maintain the upstream
3202 project, and I hope we can get a new release out fairly quickly,
3203 collecting the patches spread around on the internet into on place.
3204 I
've added the relevant Debian patches to the freshly created git
3205 repository, and expect the Gentoo patches to make it too. If you got
3206 a DVD collection and care about command line tools, check out
3207 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3208 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3209 list
</a
>. :)
</p
>
3214 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3215 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3216 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3217 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3218 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3219 a lot quicker. When we install more than
2000 packages in
3220 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3221 tasksel in the installer, unpacking the binary packages take forever.
3222 A part of the slow I/O issue was discussed in
3223 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3224 much file system sync-ing done by dpkg, which is the package
3225 responsible for unpacking the binary packages. Other parts (like code
3226 executed by postinst scripts) might also sync to disk during
3227 installation. All this sync-ing to disk do not really make sense to
3228 me. If the machine crash half-way through, I start over, I do not try
3229 to salvage the half installed system. So the failure sync-ing is
3230 supposed to protect against, hardware or system crash, is not really
3231 relevant while the installer is running.
</p
>
3233 <p
>A few days ago, I thought of a way to get rid of all the file
3234 system sync()-ing in a fairly non-intrusive way, without the need to
3235 change the code in several packages. The idea is not new, but I have
3236 not heard anyone propose the approach using dpkg-divert before. It
3237 depend on the small and clever package
3238 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3239 uses LD_PRELOAD to replace the system functions for syncing data to
3240 disk with functions doing nothing, thus allowing programs to live
3241 dangerous while speeding up disk I/O significantly. Instead of
3242 modifying the implementation of dpkg, apt and tasksel (which are the
3243 packages responsible for selecting, fetching and installing packages),
3244 it occurred to me that we could just divert the programs away, replace
3245 them with a simple shell wrapper calling
3246 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3247 Two days ago I decided to test the idea, and wrapped up a simple
3248 implementation for the Debian Edu udeb.
</p
>
3250 <p
>The effect was stunning. In my first test it reduced the running
3251 time of the pkgsel step (installing tasks) from
64 to less than
44
3252 minutes (
20 minutes shaved off the installation) on an old Dell
3253 Latitude D505 machine. I am not quite sure what the optimised time
3254 would have been, as I messed up the testing a bit, causing the debconf
3255 priority to get low enough for two questions to pop up during
3256 installation. As soon as I saw the questions I moved the installation
3257 along, but do not know how long the question were holding up the
3258 installation. I did some more measurements using Debian Edu Jessie,
3259 and got these results. The time measured is the time stamp in
3260 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3261 "pkgsel: finishing up
" lines, if you want to do the same measurement
3262 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3263 timing thus do not depend on how quickly the user handle the tasksel
3266 <p
><table
>
3269 <th
>Machine/setup
</th
>
3270 <th
>Original tasksel
</th
>
3271 <th
>Optimised tasksel
</th
>
3272 <th
>Reduction
</th
>
3276 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3277 <td
>64 min (
07:
46-
08:
50)
</td
>
3278 <td
><44 min (
11:
27-
12:
11)
</td
>
3279 <td
>>20 min
18%
</td
>
3283 <td
>Latitude D505 Roaming LXDE
</td
>
3284 <td
>57 min (
08:
48-
09:
45)
</td
>
3285 <td
>34 min (
07:
43-
08:
17)
</td
>
3286 <td
>23 min
40%
</td
>
3290 <td
>Latitude D505 Minimal
</td
>
3291 <td
>22 min (
10:
37-
10:
59)
</td
>
3292 <td
>11 min (
11:
16-
11:
27)
</td
>
3293 <td
>11 min
50%
</td
>
3297 <td
>Thinkpad X200 Minimal
</td
>
3298 <td
>6 min (
08:
19-
08:
25)
</td
>
3299 <td
>4 min (
08:
04-
08:
08)
</td
>
3300 <td
>2 min
33%
</td
>
3304 <td
>Thinkpad X200 Roaming KDE
</td
>
3305 <td
>19 min (
09:
21-
09:
40)
</td
>
3306 <td
>15 min (
10:
25-
10:
40)
</td
>
3307 <td
>4 min
21%
</td
>
3310 </table
></p
>
3312 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3313 time is spent downloading packages. The connection to the Internet
3314 was
100Mbit/s during testing, so downloading should not be a
3315 significant factor in the measurement. Download typically took a few
3316 seconds to a few minutes, depending on the amount of packages being
3317 installed.
</p
>
3319 <p
>The speedup is implemented by using two hooks in
3320 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3321 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3322 finish-install.d hook to remove the divert at the end of the
3323 installation. I picked the pre-pkgsel.d hook instead of the
3324 post-base-installer.d hook because I test using an ISO without the
3325 eatmydata package included, and the post-base-installer.d hook in
3326 Debian Edu can only operate on packages included in the ISO. The
3327 negative effect of this is that I am unable to activate this
3328 optimization for the kernel installation step in d-i. If the code is
3329 moved to the post-base-installer.d hook, the speedup would be larger
3330 for the entire installation.
</p
>
3332 <p
>I
've implemented this in the
3333 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3334 git repository, and plan to provide the optimization as part of the
3335 Debian Edu installation. If you want to test this yourself, you can
3336 create two files in the installer (or in an udeb). One shell script
3337 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3339 <p
><blockquote
><pre
>
3342 . /usr/share/debconf/confmodule
3344 logger -t my-pkgsel
"info: $*
"
3347 logger -t my-pkgsel
"error: $*
"
3349 override_install() {
3350 apt-install eatmydata || true
3351 if [ -x /target/usr/bin/eatmydata ] ; then
3352 for bin in dpkg apt-get aptitude tasksel ; do
3354 # Test that the file exist and have not been diverted already.
3355 if [ -f /target$file ] ; then
3356 info
"diverting $file using eatmydata
"
3357 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3358 > /target$file.edu
3359 chmod
755 /target$file.edu
3360 in-target dpkg-divert --package debian-edu-config \
3361 --rename --quiet --add $file
3362 ln -sf ./$bin.edu /target$file
3364 error
"unable to divert $file, as it is missing.
"
3368 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3373 </pre
></blockquote
></p
>
3375 <p
>To clean up, another shell script should go into
3376 /usr/lib/finish-install.d/ with code like this:
3378 <p
><blockquote
><pre
>
3380 . /usr/share/debconf/confmodule
3382 logger -t my-finish-install
"error: $@
"
3384 remove_install_override() {
3385 for bin in dpkg apt-get aptitude tasksel ; do
3387 if [ -x /target$file.edu ] ; then
3389 in-target dpkg-divert --package debian-edu-config \
3390 --rename --quiet --remove $file
3393 error
"Missing divert for $file.
"
3396 sync # Flush file buffers before continuing
3399 remove_install_override
3400 </pre
></blockquote
></p
>
3402 <p
>In Debian Edu, I placed both code fragments in a separate script
3403 edu-eatmydata-install and call it from the pre-pkgsel.d and
3404 finish-install.d scripts.
</p
>
3406 <p
>By now you might ask if this change should get into the normal
3407 Debian installer too? I suspect it should, but am not sure the
3408 current debian-installer coordinators find it useful enough. It also
3409 depend on the side effects of the change. I
'm not aware of any, but I
3410 guess we will see if the change is safe after some more testing.
3411 Perhaps there is some package in Debian depending on sync() and
3412 fsync() having effect? Perhaps it should go into its own udeb, to
3413 allow those of us wanting to enable it to do so without affecting
3416 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3417 will break installation of all programs using gnutls because of
3418 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3419 eatmydata package in Debian will solve it.
</p
>
3421 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3422 the optimization work again. And I have discovered that the
3423 dpkg-divert trick is not really needed and implemented a slightly
3424 simpler approach as part of the debian-edu-install package. See
3425 tools/edu-eatmydata-install in the source package.
</p
>
3427 <p
>Update
2014-
11-
11: Unfortunately, a new
3428 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3429 triggering on i386 made it into testing, and broke this installation
3430 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3431 request
768893</a
> is accepted, it should be working again.
</p
>
3436 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3437 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3438 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3439 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3440 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3441 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3442 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3443 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3444 learn that there is a large set of publicly available key servers to
3445 use when looking for peoples public key. So far I have used
3446 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3447 were misbehaving, but those days are ended. The servers I have used
3448 up until yesterday have been slow and some times unavailable. I hope
3449 those problems are gone now.
</p
>
3451 <p
>Behind the round robin DNS entry of the
3452 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3453 there is a pool of more than
100 keyservers which are checked every
3454 day to ensure they are well connected and up to date. It must be
3455 better than what I have used so far. :)
</p
>
3457 <p
>Yesterdays speaker told me that the service is the default
3458 keyserver provided by the default configuration in GnuPG, but this do
3459 not seem to be used in Debian. Perhaps it should?
</p
>
3461 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3464 <p
><blockquote
><pre
>
3465 keyserver pool.sks-keyservers.net
3466 </pre
></blockquote
></p
>
3468 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3469 entries in DNS. Just for fun, I did just that at work, so now every
3470 user of GnuPG at the University of Oslo should find a OpenGPG
3471 keyserver automatically should their need it:
</p
>
3473 <p
><blockquote
><pre
>
3474 % host -t srv _pgpkey-http._tcp.uio.no
3475 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3477 </pre
></blockquote
></p
>
3479 <p
>Now if only
3480 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3481 HKP lookup protocol
</a
> supported finding signature paths, I would be
3482 very happy. It can look up a given key or search for a user ID, but I
3483 normally do not want that, but to find a trust path from my key to
3484 another key. Given a user ID or key ID, I would like to find (and
3485 download) the keys representing a signature path from my key to the
3486 key in question, to be able to get a trust path between the two keys.
3487 This is as far as I can tell not possible today. Perhaps something
3488 for a future version of the protocol?
</p
>
3493 <title>From English wiki to translated PDF and epub via Docbook
</title>
3494 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3495 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3496 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3497 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3498 project
</a
> provide an instruction manual for teachers, system
3499 administrators and other users that contain useful tips for setting up
3500 and maintaining a Debian Edu installation. This text is about how the
3501 text processing of this manual is handled in the project.
</p
>
3503 <p
>One goal of the project is to provide information in the native
3504 language of its users, and for this we need to handle translations.
3505 But we also want to make sure each language contain the same
3506 information, so for this we need a good way to keep the translations
3507 in sync. And we want it to be easy for our users to improve the
3508 documentation, avoiding the need to learn special formats or tools to
3509 contribute, and the obvious way to do this is to make it possible to
3510 edit the documentation using a web browser. We also want it to be
3511 easy for translators to keep the translation up to date, and give them
3512 help in figuring out what need to be translated. Here is the list of
3513 tools and the process we have found trying to reach all these
3516 <p
>We maintain the authoritative source of our manual in the
3517 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3518 wiki
</a
>, as several wiki pages written in English. It consist of one
3519 front page with references to the different chapters, several pages
3520 for each chapter, and finally one
"collection page
" gluing all the
3521 chapters together into one large web page (aka
3522 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3523 AllInOne page
</a
>). The AllInOne page is the one used for further
3524 processing and translations. Thanks to the fact that the
3525 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3526 wiki.debian.org support exporting pages in
3527 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3528 the list of pages to export using the raw version of the AllInOne
3529 page, loop over each of them to generate a Docbook XML version of the
3530 manual. This process also download images and transform image
3531 references to use the locally downloaded images. The generated
3532 Docbook XML files are slightly broken, so some post-processing is done
3533 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3534 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3535 a handfull of images. The XML file can now be used to generate PDF, HTML
3536 and epub versions of the English manual. This is the basic step of
3537 our process, making PDF (using dblatex), HTML (using xsltproc) and
3538 epub (using dbtoepub) version from Docbook XML, and the resulting files
3539 are placed in the debian-edu-doc-en binary package.
</p
>
3541 <p
>But English documentation is not enough for us. We want translated
3542 documentation too, and we want to make it easy for translators to
3543 track the English original. For this we use the
3544 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3545 which allow us to transform the English Docbook XML file into a
3546 translation file (a .pot file), usable with the normal gettext based
3547 translation tools used by those translating free software. The pot
3548 file is used to create and maintain translation files (several .po
3549 files), which the translations update with the native language
3550 translations of all titles, paragraphs and blocks of text in the
3551 original. The next step is combining the original English Docbook XML
3552 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3553 create a translated Docbook XML file (in this case
3554 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3555 translated, if the translation is not complete) Docbook XML file can
3556 then be used like the original to create a PDF, HTML and epub version
3557 of the documentation.
</p
>
3559 <p
>The translators use different tools to edit the .po files. We
3561 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3562 while some use emacs and vi, others can use web based editors like
3563 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3564 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3565 is where the .po file end up, in our git repository. Updated
3566 translations can either be committed directly to git, or submitted as
3567 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3568 against the debian-edu-doc package
</a
>.
</p
>
3570 <p
>One challenge is images, which both might need to be translated (if
3571 they show translated user applications), and are needed in different
3572 formats when creating PDF and HTML versions (epub is a HTML version in
3573 this regard). For this we transform the original PNG images to the
3574 needed density and format during build, and have a way to provide
3575 translated images by storing translated versions in
3576 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3577 package maintainers know more.
</p
>
3579 <p
>If you wonder what the result look like, we provide
3580 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3581 of the documentation packages on the web
</a
>. See for example the
3582 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3583 PDF version
</a
> or the
3584 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3585 HTML version
</a
>. We do not yet build the epub version by default,
3586 but perhaps it will be done in the future.
</p
>
3588 <p
>To learn more, check out
3589 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3590 debian-edu-doc package
</a
>,
3591 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3592 manual on the wiki
</a
> and
3593 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3594 translation instructions
</a
> in the manual.
</p
>
3599 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3600 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3601 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3602 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3603 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3604 related packages relevant for the computer installed automatically.
3605 So I implemented one, using
3606 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3607 package
</a
>. To use it, install the tasksel and isenkram packages and
3608 run tasksel as user root. You should be presented with a new option,
3609 "Hardware specific packages (autodetected by isenkram)
". When you
3610 select it, tasksel will install the packages isenkram claim is fit for
3611 the current hardware, hot pluggable or not.
<p
>
3613 <p
>The implementation is in two files, one is the tasksel menu entry
3614 description, and the other is the script used to extract the list of
3615 packages to install. The first part is in
3616 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3619 <p
><blockquote
><pre
>
3622 Description: Hardware specific packages (autodetected by isenkram)
3623 Based on the detected hardware various hardware specific packages are
3625 Test-new-install: mark show
3627 Packages: for-current-hardware
3628 </pre
></blockquote
></p
>
3630 <p
>The second part is in
3631 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3634 <p
><blockquote
><pre
>
3639 isenkram-autoinstall-firmware -l
3641 </pre
></blockquote
></p
>
3643 <p
>All in all, a very short and simple implementation making it
3644 trivial to install the hardware dependent package we all may want to
3645 have installed on our machines. I
've not been able to find a way to
3646 get tasksel to tell you exactly which packages it plan to install
3647 before doing the installation. So if you are curious or careful,
3648 check the output from the isenkram-* command line tools first.
</p
>
3650 <p
>The information about which packages are handling which hardware is
3651 fetched either from the isenkram package itself in
3652 /usr/share/isenkram/, from git.debian.org or from the APT package
3653 database (using the Modaliases header). The APT package database
3654 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3655 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3656 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3657 the python-apt code (bug
3658 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3659 workaround I was able to get rid of the file descriptor leak and
3660 reduce the memory leak from ~
30 MiB per hardware detection down to
3661 around
2 MiB per hardware detection. It should make the desktop
3662 daemon a lot more useful. The fix is in version
0.7 uploaded to
3663 unstable today.
</p
>
3665 <p
>I believe the current way of mapping hardware to packages in
3666 Isenkram is is a good draft, but in the future I expect isenkram to
3667 use the AppStream data source for this. A proposal for getting proper
3668 AppStream support into Debian is floating around as
3669 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3670 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3671 project
</a
> will take place this summer to improve the situation. I
3672 look forward to seeing the result, and welcome patches for isenkram to
3673 start using the information when it is ready.
</p
>
3675 <p
>If you want your package to map to some specific hardware, either
3676 add a
"Xb-Modaliases
" header to your control file like I did in
3677 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3678 package
</a
> or submit a bug report with the details to the isenkram
3680 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3681 blog posts tagged isenkram
</a
> for details on the notation. I expect
3682 the information will be migrated to AppStream eventually, but for the
3683 moment I got no better place to store it.
</p
>
3688 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3689 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3690 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3691 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3692 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3693 project
</a
> is working on providing the software and hardware to make
3694 it easy for non-technical people to host their data and communication
3695 at home, and being able to communicate with their friends and family
3696 encrypted and away from prying eyes. It is still going strong, and
3697 today a major mile stone was reached.
</p
>
3699 <p
>Today, the last of the packages currently used by the project to
3700 created the system images were accepted into Debian Unstable. It was
3701 the freedombox-setup package, which is used to configure the images
3702 during build and on the first boot. Now all one need to get going is
3703 the build code from the freedom-maker git repository and packages from
3704 Debian. And once the freedombox-setup package enter testing, we can
3705 build everything directly from Debian. :)
</p
>
3707 <p
>Some key packages used by Freedombox are
3708 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3709 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3710 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3711 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3712 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3713 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3714 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3715 are plans to integrate more packages into the setup. User
3716 documentation is maintained on the Debian wiki. Please
3717 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3718 the manual
</a
> and help us improve it.
</p
>
3720 <p
>To test for yourself and create boot images with the FreedomBox
3721 setup, run this on a Debian machine using a user with sudo rights to
3722 become root:
</p
>
3724 <p
><pre
>
3725 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3726 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3728 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3730 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3731 </pre
></p
>
3733 <p
>Root access is needed to run debootstrap and mount loopback
3734 devices. See the README in the freedom-maker git repo for more
3735 details on the build. If you do not want all three images, trim the
3736 make line. Note that the virtualbox-image target is not really
3737 virtualbox specific. It create a x86 image usable in kvm, qemu,
3738 vmware and any other x86 virtual machine environment. You might need
3739 the version of vmdebootstrap in Jessie to get the build working, as it
3740 include fixes for a race condition with kpartx.
</p
>
3742 <p
>If you instead want to install using a Debian CD and the preseed
3743 method, boot a Debian Wheezy ISO and use this boot argument to load
3744 the preseed values:
</p
>
3746 <p
><pre
>
3747 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3748 </pre
></p
>
3750 <p
>I have not tested it myself the last few weeks, so I do not know if
3751 it still work.
</p
>
3753 <p
>If you wonder how to help, one task you could look at is using
3754 systemd as the boot system. It will become the default for Linux in
3755 Jessie, so we need to make sure it is usable on the Freedombox. I did
3756 a simple test a few weeks ago, and noticed dnsmasq failed to start
3757 during boot when using systemd. I suspect there are other problems
3758 too. :) To detect problems, there is a test suite included, which can
3759 be run from the plinth web interface.
</p
>
3761 <p
>Give it a go and let us know how it goes on the mailing list, and help
3762 us get the new release published. :) Please join us on
3763 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3764 irc.debian.org)
</a
> and
3765 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3766 mailing list
</a
> if you want to help make this vision come true.
</p
>
3771 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3772 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3773 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3774 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3775 <description><p
>For a while now, I have been looking for a sensible offsite backup
3776 solution for use at home. My requirements are simple, it must be
3777 cheap and locally encrypted (in other words, I keep the encryption
3778 keys, the storage provider do not have access to my private files).
3779 One idea me and my friends had many years ago, before the cloud
3780 storage providers showed up, was to use Google mail as storage,
3781 writing a Linux block device storing blocks as emails in the mail
3782 service provided by Google, and thus get heaps of free space. On top
3783 of this one can add encryption, RAID and volume management to have
3784 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3785 I never found time to implement such system. But the last few weeks I
3786 have looked at a system called
3787 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3788 mounted network backed file system with the features I need.
</p
>
3790 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3791 handling several different storage providers, any with Amazon S3,
3792 Google Drive or OpenStack API. There are heaps of such storage
3793 providers. S3QL can also use a local directory as storage, which
3794 combined with sshfs allow for file storage on any ssh server. S3QL
3795 include support for encryption, compression, de-duplication, snapshots
3796 and immutable file systems, allowing me to mount the remote storage as
3797 a local mount point, look at and use the files as if they were local,
3798 while the content is stored in the cloud as well. This allow me to
3799 have a backup that should survive fire. The file system can not be
3800 shared between several machines at the same time, as only one can
3801 mount it at the time, but any machine with the encryption key and
3802 access to the storage service can mount it if it is unmounted.
</p
>
3804 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3805 package is included already. So to get started, run
<tt
>apt-get
3806 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3807 Greenqloud, after reading their nice recipe on
3808 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3809 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3810 in Iceland more than those in USA when it come to keeping my personal
3811 data safe and private, and thus would rather spend money on a company
3812 in Iceland. Another nice recipe is available from the article
3813 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3814 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3815 Admin magazine. When the provider is picked, figure out how to get
3816 the API key needed to connect to the storage API. With Greencloud,
3817 the key did not show up until I had added payment details to my
3820 <p
>Armed with the API access details, it is time to create the file
3821 system. First, create a new bucket in the cloud. This bucket is the
3822 file system storage area. I picked a bucket name reflecting the
3823 machine that was going to store data there, but any name will do.
3824 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3825 the API login and password, and a locally created password. Store it
3826 all in ~root/.s3ql/authinfo2 like this:
3828 <p
><blockquote
><pre
>
3830 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3831 backend-login: API-login
3832 backend-password: API-password
3833 fs-passphrase: local-password
3834 </pre
></blockquote
></p
>
3836 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3837 but any sensible way to create a fairly random password should do it.
3838 Armed with these details, it is now time to run mkfs, entering the API
3839 details and password to create it:
</p
>
3841 <p
><blockquote
><pre
>
3842 # mkdir -m
700 /var/lib/s3ql-cache
3843 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3844 --ssl s3c://s.greenqloud.com:
443/bucket-name
3845 Enter backend login:
3846 Enter backend password:
3847 Before using S3QL, make sure to read the user
's guide, especially
3848 the
'Important Rules to Avoid Loosing Data
' section.
3849 Enter encryption password:
3850 Confirm encryption password:
3851 Generating random encryption key...
3852 Creating metadata tables...
3862 Compressing and uploading metadata...
3863 Wrote
0.00 MB of compressed metadata.
3864 #
</pre
></blockquote
></p
>
3866 <p
>The next step is mounting the file system to make the storage available.
3868 <p
><blockquote
><pre
>
3869 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3870 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3871 Using
4 upload threads.
3872 Downloading and decompressing metadata...
3882 Mounting filesystem...
3884 Filesystem Size Used Avail Use% Mounted on
3885 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3887 </pre
></blockquote
></p
>
3889 <p
>The file system is now ready for use. I use rsync to store my
3890 backups in it, and as the metadata used by rsync is downloaded at
3891 mount time, no network traffic (and storage cost) is triggered by
3892 running rsync. To unmount, one should not use the normal umount
3893 command, as this will not flush the cache to the cloud storage, but
3894 instead running the umount.s3ql command like this:
3896 <p
><blockquote
><pre
>
3899 </pre
></blockquote
></p
>
3901 <p
>There is a fsck command available to check the file system and
3902 correct any problems detected. This can be used if the local server
3903 crashes while the file system is mounted, to reset the
"already
3904 mounted
" flag. This is what it look like when processing a working
3905 file system:
</p
>
3907 <p
><blockquote
><pre
>
3908 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3909 Using cached metadata.
3910 File system seems clean, checking anyway.
3911 Checking DB integrity...
3912 Creating temporary extra indices...
3913 Checking lost+found...
3914 Checking cached objects...
3915 Checking names (refcounts)...
3916 Checking contents (names)...
3917 Checking contents (inodes)...
3918 Checking contents (parent inodes)...
3919 Checking objects (reference counts)...
3920 Checking objects (backend)...
3921 ..processed
5000 objects so far..
3922 ..processed
10000 objects so far..
3923 ..processed
15000 objects so far..
3924 Checking objects (sizes)...
3925 Checking blocks (referenced objects)...
3926 Checking blocks (refcounts)...
3927 Checking inode-block mapping (blocks)...
3928 Checking inode-block mapping (inodes)...
3929 Checking inodes (refcounts)...
3930 Checking inodes (sizes)...
3931 Checking extended attributes (names)...
3932 Checking extended attributes (inodes)...
3933 Checking symlinks (inodes)...
3934 Checking directory reachability...
3935 Checking unix conventions...
3936 Checking referential integrity...
3937 Dropping temporary indices...
3938 Backing up old metadata...
3948 Compressing and uploading metadata...
3949 Wrote
0.89 MB of compressed metadata.
3951 </pre
></blockquote
></p
>
3953 <p
>Thanks to the cache, working on files that fit in the cache is very
3954 quick, about the same speed as local file access. Uploading large
3955 amount of data is to me limited by the bandwidth out of and into my
3956 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3957 which is very close to my upload speed, and downloading the same
3958 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3959 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3960 network, not the file system code. I do not know what a good cache
3961 size would be, but suspect that the cache should e larger than your
3962 working set.
</p
>
3964 <p
>I mentioned that only one machine can mount the file system at the
3965 time. If another machine try, it is told that the file system is
3968 <p
><blockquote
><pre
>
3969 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3970 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3971 Using
8 upload threads.
3972 Backend reports that fs is still mounted elsewhere, aborting.
3974 </pre
></blockquote
></p
>
3976 <p
>The file content is uploaded when the cache is full, while the
3977 metadata is uploaded once every
24 hour by default. To ensure the
3978 file system content is flushed to the cloud, one can either umount the
3979 file system, or ask S3QL to flush the cache and metadata using
3982 <p
><blockquote
><pre
>
3983 # s3qlctrl upload-meta /s3ql
3984 # s3qlctrl flushcache /s3ql
3986 </pre
></blockquote
></p
>
3988 <p
>If you are curious about how much space your data uses in the
3989 cloud, and how much compression and deduplication cut down on the
3990 storage usage, you can use s3qlstat on the mounted file system to get
3993 <p
><blockquote
><pre
>
3995 Directory entries:
9141
3998 Total data size:
22049.38 MB
3999 After de-duplication:
21955.46 MB (
99.57% of total)
4000 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
4001 Database size:
2.39 MB (uncompressed)
4002 (some values do not take into account not-yet-uploaded dirty blocks in cache)
4004 </pre
></blockquote
></p
>
4006 <p
>I mentioned earlier that there are several possible suppliers of
4007 storage. I did not try to locate them all, but am aware of at least
4008 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
4009 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
4010 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
4011 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
4012 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
4013 accept payment in Bitcoin. Pick one that suit your need. Some of
4014 them provide several GiB of free storage, but the prize models are
4015 quite different and you will have to figure out what suits you
4018 <p
>While researching this blog post, I had a look at research papers
4019 and posters discussing the S3QL file system. There are several, which
4020 told me that the file system is getting a critical check by the
4021 science community and increased my confidence in using it. One nice
4023 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
4024 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
4025 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
4026 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
4027 and Pamela Smith. Please have a look.
</p
>
4029 <p
>Given my problems with different file systems earlier, I decided to
4030 check out the mounted S3QL file system to see if it would be usable as
4031 a home directory (in other word, that it provided POSIX semantics when
4032 it come to locking and umask handling etc). Running
4033 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
4034 test code to check file system semantics
</a
>, I was happy to discover that
4035 no error was found. So the file system can be used for home
4036 directories, if one chooses to do so.
</p
>
4038 <p
>If you do not want a locally file system, and want something that
4039 work without the Linux fuse file system, I would like to mention the
4040 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
4041 provide locally encrypted backup using a command line client. It have
4042 a nicer access control system, where one can split out read and write
4043 access, allowing some systems to write to the backup and others to
4044 only read from it.
</p
>
4046 <p
>As usual, if you use Bitcoin and want to show your support of my
4047 activities, please send Bitcoin donations to my address
4048 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4053 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
4054 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
4055 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
4056 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
4057 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
4058 project
</a
> is working on providing the software and hardware for
4059 making it easy for non-technical people to host their data and
4060 communication at home, and being able to communicate with their
4061 friends and family encrypted and away from prying eyes. It has been
4062 going on for a while, and is slowly progressing towards a new test
4063 release (
0.2).
</p
>
4065 <p
>And what day could be better than the Pi day to announce that the
4066 new version will provide
"hard drive
" / SD card / USB stick images for
4067 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4068 system), and can also be installed using a Debian installer preseed
4069 file. The Debian based Freedombox is now based on Debian Jessie,
4070 where most of the needed packages used are already present. Only one,
4071 the freedombox-setup package, is missing. To try to build your own
4072 boot image to test the current status, fetch the freedom-maker scripts
4074 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4075 with a user with sudo access to become root:
4078 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4080 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4081 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4083 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4086 <p
>Root access is needed to run debootstrap and mount loopback
4087 devices. See the README for more details on the build. If you do not
4088 want all three images, trim the make line. But note that thanks to
<a
4089 href=
"https://bugs.debian.org/
741407">a race condition in
4090 vmdebootstrap
</a
>, the build might fail without the patch to the
4091 kpartx call.
</p
>
4093 <p
>If you instead want to install using a Debian CD and the preseed
4094 method, boot a Debian Wheezy ISO and use this boot argument to load
4095 the preseed values:
</p
>
4098 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4101 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4102 recently introduced bug in apt in Jessie
</a
>, the installer will
4103 currently hang while setting up APT sources. Killing the
4104 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4105 installation will get the installation going. This affect all
4106 installations in Jessie, and I expect it will be fixed soon.
</p
>
4108 <p
>Give it a go and let us know how it goes on the mailing list, and help
4109 us get the new release published. :) Please join us on
4110 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4111 irc.debian.org)
</a
> and
4112 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4113 mailing list
</a
> if you want to help make this vision come true.
</p
>
4118 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4119 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4120 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4121 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4122 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4123 innetgr tools, because I needed them in
4124 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4125 ng-utils, and it has served me well. I placed the project under the
4126 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4127 repository. But many years ago, the CVS repository was dropped (lost,
4128 not migrated to new hardware, not sure), and the project have lacked a
4129 proper home since then.
</p
>
4131 <p
>Last summer, I had a look at the package and made a new release
4132 fixing a irritating crash bug, but was unable to store the changes in
4133 a proper source control system. I applied for a project on
4134 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4135 to follow up on it. Until today. :)
</p
>
4137 <p
>After many hours of cleaning and migration, the ng-utils project
4138 now have a new home, and a git repository with the highlight of the
4139 history of the project. I published all release tarballs and imported
4140 them into the git repository. As the project is really stable and not
4141 expected to gain new features any time soon, I decided to make a new
4142 release and call it
1.0. Visit the new project home on
4143 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4144 if you want to check it out. The new version is also uploaded into
4145 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4150 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4151 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4152 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4153 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4154 <description><p
>A few days ago I decided to try to help the Hurd people to get
4155 their changes into sysvinit, to allow them to use the normal sysvinit
4156 boot system instead of their old one. This follow up on the
4157 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4158 Google Summer of Code work
</a
> done last summer by Justus Winter to
4159 get Debian on Hurd working more like Debian on Linux. To get started,
4160 I downloaded a prebuilt hard disk image from
4161 <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
>,
4162 and started it using virt-manager.
</p
>
4164 <p
>The first think I had to do after logging in (root without any
4165 password) was to get the network operational. I followed
4166 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4167 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4168 commands as root to get the machine to accept a IP address from the
4169 kvm internal DHCP server:
</p
>
4171 <p
><blockquote
><pre
>
4172 settrans -fgap /dev/netdde /hurd/netdde
4173 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4174 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4176 </pre
></blockquote
></p
>
4178 <p
>After this, the machine had internet connectivity, and I could
4179 upgrade it and install the sysvinit packages from experimental and
4180 enable it as the default boot system in Hurd.
</p
>
4182 <p
>But before I did that, I set a password on the root user, as ssh is
4183 running on the machine it for ssh login to work a password need to be
4184 set. Also, note that a bug somewhere in openssh on Hurd block
4185 compression from working. Remember to turn that off on the client
4188 <p
>Run these commands as root to upgrade and test the new sysvinit
4191 <p
><blockquote
><pre
>
4192 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4193 deb http://http.debian.net/debian/ experimental main
4196 apt-get dist-upgrade
4197 apt-get install -t experimental initscripts sysv-rc sysvinit \
4198 sysvinit-core sysvinit-utils
4199 update-alternatives --config runsystem
4200 </pre
></blockquote
></p
>
4202 <p
>To reboot after switching boot system, you have to use
4203 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4204 yet a sysvinit process able to receive the signals from the normal
4205 'reboot
' command. After switching to sysvinit as the boot system,
4206 upgrading every package and rebooting, the network come up with DHCP
4207 after boot as it should, and the settrans/pkill hack mentioned at the
4208 start is no longer needed. But for some strange reason, there are no
4209 longer any login prompt in the virtual console, so I logged in using
4212 <p
>Note that there are some race conditions in Hurd making the boot
4213 fail some times. No idea what the cause is, but hope the Hurd porters
4214 figure it out. At least Justus said on IRC (#debian-hurd on
4215 irc.debian.org) that they are aware of the problem. A way to reduce
4216 the impact is to upgrade to the Hurd packages built by Justus by
4217 adding this repository to the machine:
</p
>
4219 <p
><blockquote
><pre
>
4220 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4221 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4223 </pre
></blockquote
></p
>
4225 <p
>At the moment the prebuilt virtual machine get some packages from
4226 http://ftp.debian-ports.org/debian, because some of the packages in
4227 unstable do not yet include the required patches that are lingering in
4228 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4230 <p
><blockquote
><pre
>
4231 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4232 i emacs - GNU Emacs editor (metapackage)
4233 i gdb - GNU Debugger
4234 i hurd-recommended - Miscellaneous translators
4235 i isc-dhcp-client - ISC DHCP client
4236 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4237 i libc-bin - Embedded GNU C Library: Binaries
4238 i libc-dev-bin - Embedded GNU C Library: Development binaries
4239 i libc0.3 - Embedded GNU C Library: Shared libraries
4240 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4241 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4242 i multiarch-support - Transitional package to ensure multiarch compatibilit
4243 i A x11-common - X Window System (X.Org) infrastructure
4244 i xorg - X.Org X Window System
4245 i A xserver-xorg - X.Org X server
4246 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4248 </pre
></blockquote
></p
>
4250 <p
>All in all, testing hurd has been an interesting experience. :)
4251 X.org did not work out of the box and I never took the time to follow
4252 the porters instructions to fix it. This time I was interested in the
4253 command line stuff.
<p
>
4258 <title>New chrpath release
0.16</title>
4259 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4260 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4261 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4262 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4263 find problems in C, C++ and Java code using static source code
4264 analysis. It can detect a lot of different problems, and is very
4265 useful to find memory and locking bugs in the error handling part of
4266 the source. The company behind it provide
4267 <a href=
"https://scan.coverity.com/
">check of free software projects as
4268 a community service
</a
>, and many hundred free software projects are
4269 already checked. A few days ago I decided to have a closer look at
4270 the Coverity system, and discovered that the
4271 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4272 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4273 projects I am involved with was already registered. But these are
4274 fairly big, and I would also like to have a small and easy project to
4275 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4276 checking of the chrpath project
</a
>. It was
4277 added to the checker and discovered seven potential defects. Six of
4278 these were real, mostly resource
"leak
" when the program detected an
4279 error. Nothing serious, as the resources would be released a fraction
4280 of a second later when the program exited because of the error, but it
4281 is nice to do it right in case the source of the program some time in
4282 the future end up in a library. Having fixed all defects and added
4283 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4284 mailing list for the chrpath developers
</a
>, I decided it was time to
4285 publish a new release. These are the release notes:
</p
>
4287 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4291 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4292 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4293 <li
>Mention new project mailing list in the documentation.
</li
>
4298 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4299 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4300 project if something is wrong with the new release. The test suite
4301 did not discover any old errors, so if you find a new one, please also
4302 include a test suite check.
</p
>
4307 <title>New chrpath release
0.15</title>
4308 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4309 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4310 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4311 <description><p
>After many years break from the package and a vain hope that
4312 development would be continued by someone else, I finally pulled my
4313 acts together this morning and wrapped up a new release of chrpath,
4314 the command line tool to modify the rpath and runpath of already
4315 compiled ELF programs. The update was triggered by the persistence of
4316 Isha Vishnoi at IBM, which needed a new config.guess file to get
4317 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4318 is working on. I checked the
4319 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4320 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4321 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4322 packages for interesting patches (failed to find the source from
4323 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4324 These are the release notes:
</p
>
4326 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4330 <li
>Updated config.sub and config.guess from the GNU project to work
4331 with newer architectures. Thanks to isha vishnoi for the heads
4334 <li
>Updated README with current URLs.
</li
>
4336 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4337 Matthias Klose.
</li
>
4339 <li
>Added missing help for -k|--keepgoing option, using patch by
4340 Petr Machata found in Fedora.
</li
>
4342 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4343 .dynamic is a NULL terminated string. Based on patch found in
4344 Fedora credited Axel Thimm and Christian Krause.
</li
>
4349 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4350 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4351 project if something is wrong with the new release. The test suite
4352 did not discover any old errors, so if you find a new one, please also
4353 include a testsuite check.
</p
>
4358 <title>Debian init.d boot script example for rsyslog
</title>
4359 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4360 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4361 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4362 <description><p
>If one of the points of switching to a new init system in Debian is
4363 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4364 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4365 init.d scripts at all. Here is an example init.d script, ie a rewrite
4366 of /etc/init.d/rsyslog:
</p
>
4368 <p
><pre
>
4369 #!/lib/init/init-d-script
4372 # Required-Start: $remote_fs $time
4373 # Required-Stop: umountnfs $time
4374 # X-Stop-After: sendsigs
4375 # Default-Start:
2 3 4 5
4376 # Default-Stop:
0 1 6
4377 # Short-Description: enhanced syslogd
4378 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4379 # It is quite compatible to stock sysklogd and can be
4380 # used as a drop-in replacement.
4382 DESC=
"enhanced syslogd
"
4383 DAEMON=/usr/sbin/rsyslogd
4384 </pre
></p
>
4386 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4387 script was
137 lines, and the above is just
15 lines, most of it meta
4388 info/comments.
</p
>
4390 <p
>How to do this, you ask? Well, one create a new script
4391 /lib/init/init-d-script looking something like this:
4393 <p
><pre
>
4396 # Define LSB log_* functions.
4397 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4398 # and status_of_proc is working.
4399 . /lib/lsb/init-functions
4402 # Function that starts the daemon/service
4408 #
0 if daemon has been started
4409 #
1 if daemon was already running
4410 #
2 if daemon could not be started
4411 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4413 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4416 # Add code here, if necessary, that waits for the process to be ready
4417 # to handle requests from services started subsequently which depend
4418 # on this one. As a last resort, sleep for some time.
4422 # Function that stops the daemon/service
4427 #
0 if daemon has been stopped
4428 #
1 if daemon was already stopped
4429 #
2 if daemon could not be stopped
4430 # other if a failure occurred
4431 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4432 RETVAL=
"$?
"
4433 [
"$RETVAL
" =
2 ]
&& return
2
4434 # Wait for children to finish too if this is a daemon that forks
4435 # and if the daemon is only ever run from this initscript.
4436 # If the above conditions are not satisfied then add some other code
4437 # that waits for the process to drop all resources that could be
4438 # needed by services started subsequently. A last resort is to
4439 # sleep for some time.
4440 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4441 [
"$?
" =
2 ]
&& return
2
4442 # Many daemons don
't delete their pidfiles when they exit.
4444 return
"$RETVAL
"
4448 # Function that sends a SIGHUP to the daemon/service
4452 # If the daemon can reload its configuration without
4453 # restarting (for example, when it is sent a SIGHUP),
4454 # then implement that here.
4456 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4461 scriptbasename=
"$(basename $
1)
"
4462 echo
"SN: $scriptbasename
"
4463 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4464 script=
"$
1"
4471 NAME=$(basename $DAEMON)
4472 PIDFILE=/var/run/$NAME.pid
4474 # Exit if the package is not installed
4475 #[ -x
"$DAEMON
" ] || exit
0
4477 # Read configuration variable file if it is present
4478 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4480 # Load the VERBOSE setting and other rcS variables
4483 case
"$
1" in
4485 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4487 case
"$?
" in
4488 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4489 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4493 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4495 case
"$?
" in
4496 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4497 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4501 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4503 #reload|force-reload)
4505 # If do_reload() is not implemented then leave this commented out
4506 # and leave
'force-reload
' as an alias for
'restart
'.
4508 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4512 restart|force-reload)
4514 # If the
"reload
" option is implemented then remove the
4515 #
'force-reload
' alias
4517 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4519 case
"$?
" in
4522 case
"$?
" in
4524 1) log_end_msg
1 ;; # Old process is still running
4525 *) log_end_msg
1 ;; # Failed to start
4535 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4541 </pre
></p
>
4543 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4544 lot. I did not really polish the approach, so it might not always
4545 work out of the box, but you get the idea. I did not try very hard to
4546 optimize it nor make it more robust either.
</p
>
4548 <p
>A better argument for switching init system in Debian than reducing
4549 the size of init scripts (which is a good thing to do anyway), is to
4550 get boot system that is able to handle the kernel events sensibly and
4551 robustly, and do not depend on the boot to run sequentially. The boot
4552 and the kernel have not behaved sequentially in years.
</p
>
4557 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4558 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4560 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4561 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4562 remote display access is the preferred solution with oVirt and RedHat
4563 Enterprise Virtualization, and I was sad to discover the other day
4564 that the browser plugin needed to use these systems seamlessly was
4565 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4566 for a package
</a
> was from
2012-
04-
10 with no progress since
4567 2013-
04-
01, so I decided to wrap up a package based on the great work
4568 from Cajus Pollmeier and put it in a collab-maint maintained git
4569 repository to get a package I could use. I would very much like
4570 others to help me maintain the package (or just take over, I do not
4571 mind), but as no-one had volunteered so far, I just uploaded it to
4572 NEW. I hope it will be available in Debian in a few days.
</p
>
4574 <p
>The source is now available from
4575 <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
>
4580 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4581 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4582 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4583 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4584 <description><p
>The
4585 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4586 program is a a very nice system to create virtual machine images. It
4587 create a image file, add a partition table, mount it and run
4588 debootstrap in the mounted directory to create a Debian system on a
4589 stick. Yesterday, I decided to try to teach it how to make images for
4590 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4591 of a plan to simplify the build system for
4592 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4593 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4594 the virtualbox images, but its current build system made multistrap
4595 based system for Dreamplug images, and it is lacking support for
4596 Raspberry Pi.
</p
>
4598 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4599 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4600 code and adjusted it to be able to build armel images on my amd64
4601 Debian laptop. I ended up giving vmdebootstrap five new options,
4602 allowing me to replicate the image creation process I use to make
4603 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4604 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4605 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4606 call debootstrap with --foreign and to copy the handler into the
4607 generated chroot before running the second stage. This allow
4608 vmdebootstrap to create armel images on an amd64 host. Next I added
4609 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4610 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4611 given file system type, allowing me to create an image with a vfat
4612 partition for the /boot/ stuff. I also added a
<tt
>--variant
4613 variant
</tt
> option to allow me to create smaller images without the
4614 Debian base system packages installed. Finally, I added an option
4615 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4616 as a boot loader. It is not needed on the Raspberry Pi and probably
4617 most other non-x86 architectures. The changes were accepted by the
4618 upstream author of vmdebootstrap yesterday and today, and is now
4620 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4621 upstream project page
</a
>.
</p
>
4623 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4624 create a small script (the customize script) to add the non-free
4625 binary blob needed to boot the Raspberry Pi and the APT source
4628 <p
><pre
>
4630 set -e # Exit on first error
4631 rootdir=
"$
1"
4632 cd
"$rootdir
"
4633 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4634 deb http://http.debian.net/debian/ jessie main contrib non-free
4636 # Install non-free binary blob needed to boot Raspberry Pi. This
4637 # install a kernel somewhere too.
4638 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4639 -O $rootdir/usr/bin/rpi-update
4640 chmod a+x $rootdir/usr/bin/rpi-update
4641 mkdir -p $rootdir/lib/modules
4642 touch $rootdir/boot/start.elf
4643 chroot $rootdir rpi-update
4644 </pre
></p
>
4646 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4647 to build the image:
</p
>
4650 sudo ./vmdebootstrap \
4653 --distribution jessie \
4654 --mirror http://http.debian.net/debian \
4663 --root-password raspberry \
4664 --hostname raspberrypi \
4665 --foreign /usr/bin/qemu-arm-static \
4666 --customize `pwd`/customize \
4668 --package git-core \
4669 --package binutils \
4670 --package ca-certificates \
4673 </pre
></p
>
4675 <p
>The list of packages being installed are the ones needed by
4676 rpi-update to make the image bootable on the Raspberry Pi, with the
4677 exception of netbase, which is needed by debootstrap to find
4678 /etc/hosts with the minbase variant. I really wish there was a way to
4679 set up an Raspberry Pi using only packages in the Debian archive, but
4680 that is not possible as far as I know, because it boots from the GPU
4681 using a non-free binary blob.
</p
>
4683 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4684 probably a few others installed. I have not checked the complete
4685 build dependency list.
</p
>
4687 <p
>The resulting image will not use the hardware floating point unit
4688 on the Raspberry PI, because the armel architecture in Debian is not
4689 optimized for that use. So the images created will be a bit slower
4690 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4695 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4696 <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>
4697 <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>
4698 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4699 <description><p
>The last few days I came across a few good causes that should get
4700 wider attention. I recommend signing and donating to each one of
4703 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4704 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4705 Women program which is a Google Summer of Code like initiative to get
4706 more women involved in free software. One debian sponsor has offered
4707 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4708 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4709 hope you will to. :)
</p
>
4711 <p
>And the Electronic Frontier Foundation just announced plans to
4712 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4713 documentaries about the excessive spying
</a
> on every Internet user that
4714 take place these days, and their need to fund the work. I
've already
4715 donated. Are you next?
</p
>
4717 <p
>For my Norwegian audience, the organisation Studentenes og
4718 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4719 statement under the heading
4720 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4721 Access
</a
> for those of us asking for more focus on open access in the
4722 Norwegian government. So far
499 signatures. I hope you will sign it
4728 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4729 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4730 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4731 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4732 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4733 project
</a
> have been going on for a while, and have presented the
4734 vision, ideas and solution several places. Here is a little
4735 collection of videos of talks and presentation of the project.
</p
>
4739 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4740 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4742 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4743 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4745 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4746 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4747 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4748 (Youtube)
</li
>
4750 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4751 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4753 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4754 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4756 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4757 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4758 York City in
2012</a
> (Youtube)
</li
>
4760 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4761 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4762 (Youtube)
</li
>
4764 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4765 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4767 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4768 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4770 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4771 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4772 2013</a
> (Youtube)
</li
>
4776 <p
>A larger list is available from
4777 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4778 Freedombox Wiki
</a
>.
</p
>
4780 <p
>On other news, I am happy to report that Freedombox based on Debian
4781 Jessie is coming along quite well, and soon both Owncloud and using
4782 Tor should be available for testers of the Freedombox solution. :) In
4783 a few weeks I hope everything needed to test it is included in Debian.
4784 The withsqlite package is already in Debian, and the plinth package is
4785 pending in NEW. The third and vital part of that puzzle is the
4786 metapackage/setup framework, which is still pending an upload. Join
4787 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4788 (#freedombox on irc.debian.org)
</a
> and
4789 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4790 mailing list
</a
> if you want to help make this vision come true.
</p
>
4795 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4796 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4797 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4798 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4799 <description><p
>I was introduced to the
4800 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4801 in
2010, when Eben Moglen presented his vision about serving the need
4802 of non-technical people to keep their personal information private and
4803 within the legal protection of their own homes. The idea is to give
4804 people back the power over their network and machines, and return
4805 Internet back to its intended peer-to-peer architecture. Instead of
4806 depending on a central service, the Freedombox will give everyone
4807 control over their own basic infrastructure.
</p
>
4809 <p
>I
've intended to join the effort since then, but other tasks have
4810 taken priority. But this summers nasty news about the misuse of trust
4811 and privilege exercised by the
"western
" intelligence gathering
4812 communities increased my eagerness to contribute to a point where I
4813 actually started working on the project a while back.
</p
>
4815 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4816 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4817 create a simple and cheap Debian based appliance that anyone can hook
4818 up in their home and get access to secure and private services and
4819 communication. The initial deployment platform have been the
4820 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4821 which is a piece of hardware I do not own. So to be able to test what
4822 the current Freedombox setup look like, I had to come up with a way to install
4823 it on some hardware I do have access to. I have rewritten the
4824 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4825 image build framework to use .deb packages instead of only copying
4826 setup into the boot images, and thanks to this rewrite I am able to
4827 set up any machine supported by Debian Wheezy as a Freedombox, using
4828 the previously mentioned deb (and a few support debs for packages
4829 missing in Debian).
</p
>
4831 <p
>The current Freedombox setup consist of a set of bootstrapping
4833 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4834 and a administrative web interface
4835 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4836 withsqlite), as well as a privacy enhancing proxy based on
4837 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4838 (freedombox-privoxy). There is also a web/javascript based XMPP
4839 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4840 trying (unsuccessfully so far) to talk to the XMPP server
4841 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4842 web interface is pluggable, and the goal is to use it to enable OpenID
4843 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4844 this is really working yet, see
4845 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4846 project TODO
</a
> for links to GIT repositories. Most of the code is
4847 on github at the moment. The HTTP proxy is operational out of the
4848 box, and the admin web interface can be used to add/remove plinth
4849 users. I
've not been able to do anything else with it so far, but
4850 know there are several branches spread around github and other places
4851 with lots of half baked features.
</p
>
4853 <p
>Anyway, if you want to have a look at the current state, the
4854 following recipes should work to give you a test machine to poke
4857 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4861 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4862 <li
>Boot from it, either as CD or USB stick.
</li
>
4863 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4864 to the Debian installer:
<p
>
4865 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4867 <li
>Answer the few language/region/password questions and pick disk to
4868 install on.
</li
>
4870 <li
>When the installation is finished and the machine have rebooted a
4871 few times, your Freedombox is ready for testing.
</li
>
4875 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4879 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4880 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4881 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4883 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4884 </pre
></li
>
4885 <li
><p
>Run this as root:
</p
>
4887 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4890 apt-get install freedombox-setup
4891 /usr/lib/freedombox/setup
4892 </pre
></li
>
4893 <li
>Reboot into your freshly created Freedombox.
</li
>
4897 <p
>You can test it on other architectures too, but because the
4898 freedombox-privoxy package is binary, it will only work as intended on
4899 the architectures where I have had time to build the binary and put it
4900 in my APT repository. But do not let this stop you. It is only a
4901 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4903 <p
>Note that by default Freedombox is a DHCP server on the
4904 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4905 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4906 disable
</tt
>" as root.
</p
>
4908 <p
>Please let me know if this works for you, or if you have any
4909 problems. We gather on the IRC channel
4910 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4911 irc.debian.org and the
4912 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4913 mailing list
</a
>.
</p
>
4915 <p
>Once you get your freedombox operational, you can visit
4916 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4917 welcome screen (dead end - do not be surprised if you are unable to
4918 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4919 to look at the rest of plinth. The default user is
'admin
' and the
4920 default password is
'secret
'.
</p
>
4925 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4926 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4927 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4928 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4929 <description><p
>Earlier, I reported about
4930 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4931 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4932 told by IBM that the original disk should be thrown away. And as
4933 there no longer was a problem if I bricked the firmware, I decided
4934 today to try to install Intel firmware to replace the Lenovo firmware
4935 currently on the disk.
</p
>
4937 <p
>I searched the Intel site for firmware, and found
4938 <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
>
4939 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4940 according to the site should contain the latest firmware for SSD
4941 disks. I inserted the broken disk in one of my spare laptops and
4942 booted the ISO from a USB stick. The disk was recognized, but the
4943 program claimed the newest firmware already were installed and refused
4944 to insert any Intel firmware. So no change, and the disk is still
4945 unable to handle write load. :( I guess the only way to get them
4946 working would be if Lenovo releases new firmware. No idea how likely
4947 that is. Anyway, just blogging about this test for completeness. I
4948 got a working Samsung disk, and see no point in spending more time on
4949 the broken disks.
</p
>
4954 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4955 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4956 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4957 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4958 <description><p
>Today I switched to
4959 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4960 new laptop
</a
>. I
've previously written about the problems I had with
4961 my new Thinkpad X230, which was delivered with an
4962 <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
4963 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4964 sustained writes. My hardware supplier have been very forthcoming in
4965 trying to find a solution, and after first trying with another
4966 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4967 disk instead to fix it once and for all. The Samsung disk survived
4968 the installation of Debian with encrypted disks (filling the disk with
4969 random data during installation killed the first two), and I thus
4970 decided to trust it with my data. I have installed it as a Debian Edu
4971 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4972 server at home using Kerberos and LDAP, and will use it as my work
4973 station from now on.
</p
>
4975 <p
>As this is a solid state disk with no moving parts, I believe the
4976 Debian Wheezy default installation need to be tuned a bit to increase
4977 performance and increase life time of the disk. The Linux kernel and
4978 user space applications do not yet adjust automatically to such
4979 environment. To make it easier for my self, I created a draft Debian
4980 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4981 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4982 for the ssd-setup package
</a
> is available from collab-maint, and it
4983 is set up to adjust the setup of the machine by just installing the
4984 package. If there is any non-SSD disk in the machine, the package
4985 will refuse to install, as I did not try to write any logic to sort
4986 file systems in SSD and non-SSD file systems.
</p
>
4988 <p
>I consider the package a draft, as I am a bit unsure how to best
4989 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4990 where I set up the machine with one large encrypted partition (in
4991 addition to /boot), put LVM on top of this and set up partitions on
4992 top of this again. See the README file in the package source for the
4993 references I used to pick the settings. At the moment these
4994 parameters are tuned:
</p
>
4998 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4999 (adding discard to /etc/crypttab)
</li
>
5001 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
5002 this case a cryptsetup partition) by changing issue_discards from
5003 0 to
1 in /etc/lvm/lvm.conf.
</li
>
5005 <li
>Set relatime as a file system option for ext3 and ext4 file
5008 <li
>Tell swap to use TRIM commands by adding
'discard
' to
5009 /etc/fstab.
</li
>
5011 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
5013 <li
>Run fstrim on every ext3 and ext4 file system every night (from
5014 cron.daily).
</li
>
5016 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
5017 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
5021 <p
>During installation, I cancelled the part where the installer fill
5022 the disk with random data, as this would kill the SSD performance for
5023 little gain. My goal with the encrypted file system is to ensure
5024 those stealing my laptop end up with a brick and not a working
5025 computer. I have no hope in keeping the really resourceful people
5026 from getting the data on the disk (see
5027 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
5028 Thus I concluded that adding the discard option to crypttab is the
5029 right thing to do.
</p
>
5031 <p
>I considered using the noop I/O scheduler, as several recommended
5032 it for SSD, but others recommended deadline and a benchmark I found
5033 indicated that deadline might be better for interactive use.
</p
>
5035 <p
>I also considered using the
'discard
' file system option for ext3
5036 and ext4, but read that it would give a performance hit ever time a
5037 file is removed, and thought it best to that that slowdown once a day
5038 instead of during my work.
</p
>
5040 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
5041 this is already done by Debian Edu.
</p
>
5043 <p
>I have not yet started on the user space tuning. I expect
5044 iceweasel need some tuning, and perhaps other applications too, but
5045 have not yet had time to investigate those parts.
</p
>
5047 <p
>The package should work on Ubuntu too, but I have not yet tested it
5050 <p
>As for the answer to the question in the title of this blog post,
5051 as far as I know, the only solution I know about is to replace the
5052 disk. It might be possible to flash it with Intel firmware instead of
5053 the Lenovo firmware. But I have not tried and did not want to do so
5054 without approval from Lenovo as I wanted to keep the warranty on the
5055 disk until a solution was found and they wanted the broken disks
5061 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
5062 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
5063 <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>
5064 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5065 <description><p
>A few days ago, I wrote about
5066 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5067 problems I experienced with my new X230 and its SSD disk
</a
>, which
5068 was dying during installation because it is unable to cope with
5069 sustained write. My supplier is in contact with
5070 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5071 replacement disk to try to fix the problem. They decided to send an
5072 identical model, so my hopes for a permanent fix was slim.
</p
>
5074 <p
>Anyway, today I got the replacement disk and tried to install
5075 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5076 same firmware version as the original. This time my hope raised
5077 slightly as the installation progressed, as the original disk used to
5078 die after
4-
7% of the disk was written to, while this time it kept
5079 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5080 died again and I was back on square one. I still do not have a new
5081 laptop with a disk I can trust. I can not live with a disk that might
5082 lock up when I download a new
5083 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5084 other large files. I look forward to hearing from my supplier with
5085 the next proposal from Lenovo.
</p
>
5087 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5088 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5089 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5090 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5091 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5092 P/N
45N8295, P0C38732.
</p
>
5094 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5095 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5096 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5097 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5098 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5099 P/N
45N8295, P0C38732.
</p
>
5101 <p
>The only difference is in the first number (serial number?), ISN,
5102 SA, date and WNPP values. Mentioning all the details here in case
5103 someone is able to use the information to find a way to identify the
5104 failing disk among working ones (if any such working disk actually
5110 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5111 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5113 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5114 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5115 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5116 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5117 member assosiation NUUG
</a
> and
5118 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5119 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5120 Bitraf
</a
>.
</p
>
5122 <p
>It starts
10:
00 and continue until late evening. Everyone is
5123 welcome, and there is no fee to participate. There is on the other
5124 hand limited space, and only room for
30 people. Please put your name
5125 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5126 wiki page
</a
> if you plan to join us.
</p
>
5131 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5132 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5133 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5134 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5135 <description><p
>Half a year ago, I reported that I had to find a
5136 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5137 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5138 time to spend on it, and it took a while to find a model I believe
5139 will do the job, but two days ago the replacement finally arrived. I
5141 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5142 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5143 a roaming workstation, and it seemed to work flawlessly. But my
5144 second installation with encrypted disk was not as successful. More
5145 on that below.
</p
>
5147 <p
>I had a hard time trying to track down a good laptop, as my most
5148 important requirements (robust and with a good keyboard) are never
5149 listed in the feature list. But I did get good help from the search
5150 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5151 allowed me to limit the list of interesting laptops based on my other
5152 requirements. A bit surprising that SSD disk are not disks according
5153 to that search interface, so I had to drop specifying the number of
5154 disks from my search parameters. I also asked around among friends to
5155 get their impression on keyboards and robustness.
</p
>
5157 <p
>So the new laptop arrived, and it is quite a lot wider than the
5158 X41. I am not quite convinced about the keyboard, as it is
5159 significantly wider than my old keyboard, and I have to stretch my
5160 hand a lot more to reach the edges. But the key response is fairly
5161 good and the individual key shape is fairly easy to handle, so I hope
5162 I will get used to it. My old X40 was starting to fail, and I really
5163 needed a new laptop now. :)
</p
>
5165 <p
>Turning off the touch pad was simple. All it took was a quick
5166 visit to the BIOS during boot it disable it.
</p
>
5168 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5169 lock up during load. And this happen when installing Debian Wheezy
5170 with encrypted disk, while the disk is being filled with random data.
5171 I also tested to install Ubuntu Raring, and it happen there too if I
5172 reenable the code to fill the disk with random data (it is disabled by
5173 default in Ubuntu). And the bug with is already known. It was
5174 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5175 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5176 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5177 kernel developers as
5178 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5179 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5180 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5181 Lenovo forums, both for
5182 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5183 2012-
11-
10</a
> and for
5184 <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
5185 03-
20-
2013</a
>. The problem do not only affect installation. The
5186 reports state that the disk lock up during use if many writes are done
5187 on the disk, so it is much no use to work around the installation
5188 problem and end up with a computer that can lock up at any moment.
5190 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5191 available
</a
> that will lock up the hard drive after running a few
5192 minutes by writing to a file.
</p
>
5194 <p
>I
've contacted my supplier and asked how to handle this, and after
5195 contacting PCHELP Norway (request
01D1FDP) which handle support
5196 requests for Lenovo, his first suggestion was to upgrade the disk
5197 firmware. Unfortunately there is no newer firmware available from
5198 Lenovo, as my disk already have the most recent one (version LF1i). I
5199 hope to hear more from him today and hope the problem can be
5205 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5206 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5207 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5208 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5209 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5210 trusty old Thinkpad X41. Unfortunately I did not have much time to
5211 spend on it, but today the replacement finally arrived. I ended up
5212 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5213 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5214 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5215 this, it is installing what I hope will be a more final installation,
5216 with a encrypted hard drive to ensure any dope head stealing it end up
5217 with an expencive door stop.
</p
>
5219 <p
>I had a hard time trying to track down a good laptop, as my most
5220 important requirements (robust and with a good keyboard) are never
5221 listed in the feature list. But I did get good help from the search
5222 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5223 allowed me to limit the list of interesting laptops based on my other
5224 requirements. A bit surprising that SSD disk are not disks, so I had
5225 to drop number of disks from my search parameters.
</p
>
5227 <p
>I am not quite convinced about the keyboard, as it is significantly
5228 wider than my old keyboard, and I have to stretch my hand a lot more
5229 to reach the edges. But the key response is fairly good and the
5230 individual key shape is fairly easy to handle, so I hope I will get
5231 used to it. My old X40 was starting to fail, and I really needed a
5232 new laptop now. :)
</p
>
5234 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5239 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5240 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5242 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5243 <description><p
>It annoys me when the computer fail to do automatically what it is
5244 perfectly capable of, and I have to do it manually to get things
5245 working. One such task is to find out what firmware packages are
5246 needed to get the hardware on my computer working. Most often this
5247 affect the wifi card, but some times it even affect the RAID
5248 controller or the ethernet card. Today I pushed version
0.4 of the
5249 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5250 including a new script isenkram-autoinstall-firmware handling the
5251 process of asking all the loaded kernel modules what firmware files
5252 they want, find debian packages providing these files and install the
5253 debian packages. Here is a test run on my laptop:
</p
>
5255 <p
><pre
>
5256 # isenkram-autoinstall-firmware
5257 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5258 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5259 info: locating packages with the requested firmware files
5260 info: Updating APT sources after adding non-free APT source
5261 info: trying to install firmware-ipw2x00
5264 Preconfiguring packages ...
5265 Selecting previously deselected package firmware-ipw2x00.
5266 (Reading database ...
259727 files and directories currently installed.)
5267 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5268 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5270 </pre
></p
>
5272 <p
>When all the requested firmware is present, a simple message is
5273 printed instead:
</p
>
5275 <p
><pre
>
5276 # isenkram-autoinstall-firmware
5277 info: did not find any firmware files requested by loaded kernel modules. exiting
5279 </pre
></p
>
5281 <p
>It could use some polish, but it is already working well and saving
5282 me some time when setting up new machines. :)
</p
>
5284 <p
>So, how does it work? It look at the set of currently loaded
5285 kernel modules, and look up each one of them using modinfo, to find
5286 the firmware files listed in the module meta-information. Next, it
5287 download the Contents file from a nearby APT mirror, and search for
5288 the firmware files in this file to locate the package with the
5289 requested firmware file. If the package is in the non-free section, a
5290 non-free APT source is added and the package is installed using
5291 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5294 <p
>I hope someone find time to implement a more polished version of
5295 this script as part of the hw-detect debian-installer module, to
5296 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5297 #
655507</a
>. There really is no need to insert USB sticks with
5298 firmware during a PXE install when the packages already are available
5299 from the nearby Debian mirror.
</p
>
5304 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5305 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5306 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5307 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5308 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5309 the screen just turn black when Linux boot, either during installation
5310 or on first boot from the hard disk. I
've seen it once in a while the
5311 last few years, but only recently understood the cause. I
've seen it
5312 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5313 The reason seem to be in the wiring of some laptops. The system to
5314 control the screen background light is inverted, so when Linux try to
5315 turn the brightness fully on, it end up turning it off instead. I do
5316 not know which Linux drivers are affected, but this post is about the
5317 i915 driver used by the
5318 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5319 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5321 <p
>The problem can be worked around two ways. Either by adding
5322 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5323 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5324 option when it load the i915 kernel module. On Debian and Ubuntu, it
5325 can be done by running these commands as root:
</p
>
5328 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5329 update-initramfs -u -k all
5332 <p
>Since March
2012 there is
5333 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5334 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5335 hardware have this problem, and get the driver to invert the
5336 brightness setting automatically. To use it, one need to add a row in
5337 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5338 intel_quirks array
</a
> in the driver source
5339 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5340 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5341 number (vendor number
8086 is assumed) and subdevice vendor and device
5344 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5345 -vvnn
</tt
> for the video card in question:
</p
>
5347 <p
><pre
>
5348 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5349 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5350 (rev
09) (prog-if
00 [VGA controller])
5351 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5352 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5353 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5354 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5355 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5357 Interrupt: pin A routed to IRQ
42
5358 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5359 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5360 Region
4: I/O ports at
4000 [size=
64]
5361 Expansion ROM at
<unassigned
> [disabled]
5362 Capabilities:
<access denied
>
5363 Kernel driver in use: i915
5364 </pre
></p
>
5366 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5368 <p
><pre
>
5369 struct intel_quirk intel_quirks[] = {
5371 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5372 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5375 </pre
></p
>
5377 <p
>According to the kernel module instructions (as seen using
5378 <tt
>modinfo i915
</tt
>), information about hardware needing the
5379 invert_brightness flag should be sent to the
5380 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5381 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5382 developers. But my email about the laptop sent
2013-
06-
03 have not
5384 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5385 web archive for the mailing list
</a
>, so I suspect they do not accept
5386 emails from non-subscribers. Because of this, I sent my patch also to
5387 the Debian bug tracking system instead as
5388 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5389 sure the patch is not lost.
</p
>
5391 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5392 with this problem working properly with Linux. If you use Gnome, your
5393 worries should be over at this point. But if you use KDE, there is
5394 something in KDE ignoring the invert_brightness setting and turning on
5395 the screen during login. I
've reported it to Debian as
5396 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5397 have no idea yet how to figure out exactly what subsystem is doing
5398 this. Perhaps you can help? Perhaps you know what the Gnome
5399 developers did to handle this, and this can give a clue to the KDE
5400 developers? Or you know where in KDE the screen brightness is changed
5401 during login? If so, please update the BTS report (or get in touch if
5402 you do not know how to update BTS).
</p
>
5404 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5405 acpi_backlight=vendor, to disable ACPI backlight support completely,
5406 as the ACPI information on the machine is trash and it is better to
5407 leave it to the intel video driver to control the screen
5408 backlight.
</p
>
5413 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5414 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5415 <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>
5416 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5417 <description><p
>Two days ago, I asked
5418 <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
5419 I could install Linux on a Packard Bell EasyNote LV computer
5420 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5421 with the obstacles put in the way of Linux users on a laptop with UEFI
5422 and Windows
8.
</p
>
5424 <p
>I never found out if the cause of my problems were the use of UEFI
5425 secure booting or fast boot. I suspect fast boot was the problem,
5426 causing the firmware to boot directly from HD without considering any
5427 key presses and alternative devices, but do not know UEFI settings
5428 enough to tell.
</p
>
5430 <p
>There is no way to install Linux on the machine in question without
5431 opening the box and disconnecting the hard drive! This is as far as I
5432 can tell, the only way to get access to the firmware setup menu
5433 without accepting the Windows
8 license agreement. I am told (and
5434 found description on how to) that it is possible to configure the
5435 firmware setup once booted into Windows
8. But as I believe the terms
5436 of that agreement are completely unacceptable, accepting the license
5437 was never an alternative. I do not enter agreements I do not intend
5438 to follow.
</p
>
5440 <p
>I feared I had to return the laptops and ask for a refund, and
5441 waste many hours on this, but luckily there was a way to get it to
5442 work. But I would not recommend it to anyone planning to run Linux on
5443 it, and I have become sceptical to Windows
8 certified laptops. Is
5444 this the way Linux will be forced out of the market place, by making
5445 it close to impossible for
"normal
" users to install Linux without
5446 accepting the Microsoft Windows license terms? Or at least not
5447 without risking to loose the warranty?
</p
>
5449 <p
>I
've updated the
5450 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5451 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5452 do not have to struggle as much as I did to get Linux into the
5455 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5456 Michael Tokarev and others for feedback and ideas.
</p
>
5461 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5462 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5463 <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>
5464 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5465 <description><p
>I
've run into quite a problem the last few days. I bought three
5466 new laptops for my parents and a few others. I bought Packard Bell
5467 Easynote LV to run Kubuntu on and use as their home computer. But I
5468 am completely unable to figure out how to install Linux on it. The
5469 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5470 instead of a BIOS to boot.
</p
>
5472 <p
>The problem is that I am unable to get it to PXE boot, and unable
5473 to get it to boot the Linux installer from my USB stick. I have yet
5474 to try the DVD install, and still hope it will work. when I turn on
5475 the computer, there is no information on what buttons to press to get
5476 the normal boot menu. I expect to get some boot menu to select PXE or
5477 USB stick booting. When booting, it first ask for the language to
5478 use, then for some regional settings, and finally if I will accept the
5479 Windows
8 terms of use. As these terms are completely unacceptable to
5480 me, I have no other choice but to turn off the computer and try again
5481 to get it to boot the Linux installer.
</p
>
5483 <p
>I have gathered my findings so far on a Linlap page about the
5484 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5485 EasyNote LV
</a
> model. If you have any idea how to get Linux
5486 installed on this machine, please get in touch or update that wiki
5487 page. If I can
't find a way to install Linux, I will have to return
5488 the laptop to the seller and find another machine for my parents.
</p
>
5490 <p
>I wonder, is this the way Linux will be forced out of the market
5491 using UEFI and
"secure boot
" by making it impossible to install Linux
5492 on new Laptops?
</p
>
5497 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5498 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5499 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5500 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5501 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5502 an operating system based on Debian intended for use in schools. It
5503 contain a turn-key solution for the computer network provided to
5504 pupils in the primary schools. It provide both the central server,
5505 network boot servers and desktop environments with heaps of
5506 educational software. The project was founded almost
12 years ago,
5507 2001-
07-
02. If you want to support the project, which is in need for
5508 cash to fund developer gatherings and other project related activity,
5509 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5510 donate some money
</a
>.
5512 <p
>A topic that come up again and again on the Debian Edu mailing
5513 lists and elsewhere, is the question on how to transform a Debian or
5514 Ubuntu installation into a Debian Edu installation. It isn
't very
5515 hard, and last week I wrote a script to replicate the steps done by
5516 the Debian Edu installer.
</p
>
5518 <p
>The script,
5519 <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/
>
5520 in the debian-edu-config package, will go through these six steps and
5521 transform an existing Debian Wheezy or Ubuntu (untested) installation
5522 into a Debian Edu Workstation:
</p
>
5526 <li
>Add skolelinux related APT sources.
</li
>
5527 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5528 <li
>Install debian-edu-install to load preseeding values and pull in
5529 our configuration.
</li
>
5530 <li
>Preseed debconf database with profile setup in
5531 /etc/debian-edu/config, and run tasksel to install packages
5532 according to the profile specified in the config above,
5533 overriding some of the Debian automation machinery.
</li
>
5534 <li
>Run debian-edu-cfengine-D installation to configure everything
5535 that could not be done using preseeding.
</li
>
5536 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5540 <p
>There are some steps in the Debian Edu installation that can not be
5541 replicated like this. Disk partitioning and LVM setup, for example.
5542 So this script just assume there is enough disk space to install all
5543 the needed packages.
</p
>
5545 <p
>The script was created to help a Debian Edu student working on
5546 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5547 Debian Edu client, and using it he can take the existing
5548 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5549 transform it into a fully functioning Debian Edu Workstation (or
5550 Roaming Workstation, or whatever :).
</p
>
5552 <p
>The default setting in the script is to create a KDE Workstation.
5553 If a LXDE based Roaming workstation is wanted instead, modify the
5554 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5556 <p
><pre
>
5557 PROFILE=
"Roaming-Workstation
"
5558 DESKTOP=
"lxde
"
5559 </pre
></p
>
5561 <p
>The script could even become useful to set up Debian Edu servers in
5562 the cloud, by starting with a virtual Debian installation at some
5563 virtual hosting service and setting up all the services on first
5569 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5570 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5571 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5572 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5573 <description><P
>In January,
5574 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5575 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5576 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5577 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5578 marvellous construction system from Denmark. We also created
5579 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5580 a place to take notes and write down our plans and hopes. And several
5581 people showed up to help. I was very happy to see the effect of my
5582 call. Since the small start, we have a debtags tag
5583 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5584 tag for LEGO related packages, and now count
10 packages related to
5585 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5587 <p
><table
>
5588 <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
>
5589 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5590 <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
>
5591 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5592 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5593 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5594 <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
>
5595 <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
>
5596 <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
>
5597 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5598 </table
></p
>
5600 <p
>Some of these are available in Wheezy, and all but one are
5601 currently available in Jessie/testing. leocad is so far only
5602 available in experimental.
</p
>
5604 <p
>If you care about LEGO in Debian, please join us on IRC and help
5605 adding the rest of the great free software tools available on Linux
5606 for LEGO designers.
</p
>
5611 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5612 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5613 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5614 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5615 <description><p
>When I woke up this morning, I was very happy to see that the
5616 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5617 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5618 Debian release, and I expect to move my machines at home over to it fairly
5621 <p
>The new debian release contain heaps of new stuff, and one program
5622 in particular make me very happy to see included. The
5623 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5624 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5625 included for the first time. Alongside similar programs like
5626 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5627 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5628 it allow for visual programming where syntax errors can not happen,
5629 and a friendly programming environment for learning to control the
5630 computer. Scratch will also be included in the next release of Debian
5633 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5634 Edu/Skolelinux release too. The
5635 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5636 alpha release
</a
> went out last week, and the next should soon
5642 <title>Isenkram
0.2 finally in the Debian archive
</title>
5643 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5645 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5646 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5647 package
</a
> finally made it into the archive, after lingering in NEW
5648 for many months. I uploaded it to the Debian experimental suite
5649 2013-
01-
27, and today it was accepted into the archive.
</p
>
5651 <p
>Isenkram is a system for suggesting to users what packages to
5652 install to work with a pluggable hardware device. The suggestion pop
5653 up when the device is plugged in. For example if a Lego Mindstorm NXT
5654 is inserted, it will suggest to install the program needed to program
5655 the NXT controller. Give it a go, and report bugs and suggestions to
5661 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5662 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5663 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5664 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5665 <description><p
>My
5666 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5667 bitcoin related blog post
</a
> mentioned that the new
5668 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5669 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5670 2013-
01-
19, and have been available in unstable since then. It was
5671 automatically copied to Ubuntu, and is available in their Raring
5672 version too.
</p
>
5674 <p
>But there is a strange problem with the build that block this new
5675 version from being available on the i386 and kfreebsd-i386
5676 architectures. For some strange reason, the autobuilders in Debian
5677 for these architectures fail to run the test suite on these
5678 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5679 We are so far unable to reproduce it when building it manually, and
5680 no-one have been able to propose a fix. If you got an idea what is
5681 failing, please let us know via the BTS.
</p
>
5683 <p
>One feature that is annoying me with of the bitcoin client, because
5684 I often run low on disk space, is the fact that the client will exit
5685 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5686 #
696715</a
>). So make sure you have enough disk space when you run
5689 <p
>As usual, if you use bitcoin and want to show your support of my
5690 activities, please send Bitcoin donations to my address
5691 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5696 <title>Welcome to the world, Isenkram!
</title>
5697 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5698 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5699 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5700 <description><p
>Yesterday, I
5701 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5702 for testers
</a
> for my prototype for making Debian better at handling
5703 pluggable hardware devices, which I
5704 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5705 out to create
</a
> earlier this month. Several valuable testers showed
5706 up, and caused me to really want to to open up the development to more
5707 people. But before I did this, I want to come up with a sensible name
5708 for this project. Today I finally decided on a new name, and I have
5709 renamed the project from hw-support-handler to this new name. In the
5710 process, I moved the source to git and made it available as a
5711 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5712 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5713 To fetch and build the latest version of the source, use
</p
>
5716 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5717 cd isenkram
&& git-buildpackage -us -uc
5720 <p
>I have not yet adjusted all files to use the new name yet. If you
5721 want to hack on the source or improve the package, please go ahead.
5722 But please talk to me first on IRC or via email before you do major
5723 changes, to make sure we do not step on each others toes. :)
</p
>
5725 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5726 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5727 stuff, in other words. I
've been told it is the Norwegian variant of
5728 the German word eisenkram, for those that are familiar with that
5731 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5732 instructions, to avoid confusing people with an error from the signing
5735 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5736 clone argument to avoid the need for authentication.
</p
>
5741 <title>First prototype ready making hardware easier to use in Debian
</title>
5742 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5743 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5744 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5745 <description><p
>Early this month I set out to try to
5746 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5747 the Debian support for pluggable hardware devices
</a
>. Now my
5748 prototype is working, and it is ready for a larger audience. To test
5750 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5751 from the Debian Edu subversion repository
</a
>, build and install the
5752 package. You might have to log out and in again activate the
5753 autostart script.
</p
>
5755 <p
>The design is simple:
</p
>
5759 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5760 hw-support-handlerd to start when the user log in.
</li
>
5762 <li
>This program listen for kernel events about new hardware (directly
5763 from the kernel like udev does), not using HAL dbus events as I
5764 initially did.
</li
>
5766 <li
>When new hardware is inserted, look up the hardware modalias in
5767 the APT database, a database
5768 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5769 via HTTP
</a
> and a database available as part of the package.
</li
>
5771 <li
>If a package is mapped to the hardware in question, the package
5772 isn
't installed yet and this is the first time the hardware was
5773 plugged in, show a desktop notification suggesting to install the
5774 package or packages.
</li
>
5776 <li
>If the user click on the
'install package now
' button, ask
5777 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5779 <li
>aptdaemon ask for root password or sudo password, and install the
5780 package while showing progress information in a window.
</li
>
5784 <p
>I still need to come up with a better name for the system. Here
5785 are some screen shots showing the prototype in action. First the
5786 notification, then the password request, and finally the request to
5787 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5789 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5790 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5791 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5792 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5793 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5795 <p
>The prototype still need to be improved with longer timeouts, but
5796 is already useful. The database of hardware to package mappings also
5797 need more work. It is currently compatible with the Ubuntu way of
5798 storing such information in the package control file, but could be
5799 changed to use other formats instead or in addition to the current
5800 method. I
've dropped the use of discover for this mapping, as the
5801 modalias approach is more flexible and easier to use on Linux as long
5802 as the Linux kernel expose its modalias strings directly.
</p
>
5804 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5805 here is the command required to check out and build the source: Use
5806 '<tt
>svn checkout
5807 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5808 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5809 devscripts package.
</p
>
5811 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5812 renamed to Isenkram and the source moved from the Debian Edu
5813 subversion repository to a Debian collab-maint git repository. See
5814 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5815 instructions
</a
> for details.
</p
>
5820 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5821 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5822 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5823 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5824 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5825 suddenly in bed. With a quiet whimper, it went completely quiet and
5826 black. The power button was no longer able to turn it on. It was a
5827 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5828 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5829 Compaq I had before that. Now I need to find a replacement. To keep
5830 going during Christmas, I moved the one year old SSD disk to my old
5831 X40 where it fitted (only one I had left that could use it), but it is
5832 not a durable solution.
5834 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5835 got a new one more than
10 years ago. It still holds true.:)
</p
>
5839 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5840 than A4).
</li
>
5841 <li
>Robust, it will be in my backpack every day.
</li
>
5842 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5843 <li
>Long battery life time. Preferable a week.
</li
>
5844 <li
>Internal WIFI network card.
</li
>
5845 <li
>Internal Twisted Pair network card.
</li
>
5846 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5847 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5848 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5850 <li
>Hardware supported by Debian Stable, ie the default kernel and
5851 X.org packages.
</li
>
5852 <li
>Quiet, preferably fan free (or at least not using the fan most of
5857 <p
>You will notice that there are no RAM and CPU requirements in the
5858 list. The reason is simply that the specifications on laptops the
5859 last
10-
15 years have been sufficient for my needs, and I have to look
5860 at other features to choose my laptop. But are there still made as
5861 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5862 robust, and Thinkpads seem to be heading in the wrong direction since
5863 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5864 still be useful.
</p
>
5866 <p
>Perhaps I should rethink my needs, and look for a pad with an
5867 external keyboard? I
'll have to check the
5868 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5869 well-supported laptops, or perhaps just buy one preinstalled from one
5870 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5871 Pre-loaded site
</a
>.
</p
>
5876 <title>How to find a browser plugin supporting a given MIME type
</title>
5877 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5878 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5879 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5880 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5881 install to get support for a given MIME type. Thanks to
5882 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5883 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5884 Unfortunately, not very many packages provide the needed meta
5885 information, Anyway, here is a small script to look up all browser
5886 plugin packages announcing ther MIME support using this specification:
</p
>
5892 def pkgs_handling_mimetype(mimetype):
5897 version = pkg.candidate
5899 version = pkg.installed
5902 record = version.record
5903 if not record.has_key(
'Npp-MimeType
'):
5905 mime_types = record[
'Npp-MimeType
'].split(
',
')
5906 for t in mime_types:
5907 t = t.rstrip().strip()
5909 thepkgs.append(pkg.name)
5911 mimetype =
"audio/ogg
"
5912 if
1 < len(sys.argv):
5913 mimetype = sys.argv[
1]
5914 print
"Browser plugin packages supporting %s:
" % mimetype
5915 for pkg in pkgs_handling_mimetype(mimetype):
5916 print
" %s
" %pkg
5919 <p
>It can be used like this to look up a given MIME type:
</p
>
5922 % ./apt-find-browserplug-for-mimetype
5923 Browser plugin packages supporting audio/ogg:
5925 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5926 Browser plugin packages supporting application/x-shockwave-flash:
5927 browser-plugin-gnash
5931 <p
>In Ubuntu this mechanism is combined with support in the browser
5932 itself to query for plugins and propose to install the needed
5933 packages. It would be great if Debian supported such feature too. Is
5934 anyone working on adding it?
</p
>
5936 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5937 request for icweasel support for this feature is
5938 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5939 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5940 of manpower and wish for a different design is the reason thus feature
5941 is not yet in iceweasel from Debian.
</p
>
5946 <title>What is the most supported MIME type in Debian?
</title>
5947 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5948 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5949 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5950 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5951 proposal to add AppStream information to the Debian archive
</a
>, is a
5952 proposal to make it possible for a Desktop application to propose to
5953 the user some package to install to gain support for a given MIME
5954 type, font, library etc. that is currently missing. With such
5955 mechanism in place, it would be possible for the desktop to
5956 automatically propose and install leocad if some LDraw file is
5957 downloaded by the browser.
</p
>
5959 <p
>To get some idea about the current content of the archive, I decided
5960 to write a simple program to extract all .desktop files from the
5961 Debian archive and look up the claimed MIME support there. The result
5963 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5964 site
</a
>. Using the collected information, it become possible to
5965 answer the question in the title. Here are the
20 most supported MIME
5966 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5967 The complete list is available from the link above.
</p
>
5969 <p
><strong
>Debian Stable:
</strong
></p
>
5973 ----- -----------------------
5989 18 application/x-ogg
5996 <p
><strong
>Debian Testing:
</strong
></p
>
6000 ----- -----------------------
6016 18 application/x-ogg
6023 <p
><strong
>Debian Unstable:
</strong
></p
>
6027 ----- -----------------------
6044 18 application/x-ogg
6050 <p
>I am told that PackageKit can provide an API to access the kind of
6051 information mentioned in DEP-
11. I have not yet had time to look at
6052 it, but hope the PackageKit people in Debian are on top of these
6055 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
6056 discovering a typo in my script.
</p
>
6061 <title>Using modalias info to find packages handling my hardware
</title>
6062 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
6063 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
6064 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6065 <description><p
>Yesterday, I wrote about the
6066 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6067 values provided by the Linux kernel
</a
> following my hope for
6068 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6069 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6070 modalias values attached to package names can be used to map packages
6071 to hardware. This allow the system to look up and suggest relevant
6072 packages when I plug in some new hardware into my machine, and replace
6073 discover and discover-data as the database used to map hardware to
6076 <p
>I create a modaliases file with entries like the following,
6077 containing package name, kernel module name (if relevant, otherwise
6078 the package name) and globs matching the relevant hardware
6081 <p
><blockquote
>
6082 Package: package-name
6083 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6084 </blockquote
></p
>
6086 <p
>It is fairly trivial to write code to find the relevant packages
6087 for a given modalias value using this file.
</p
>
6089 <p
>An entry like this would suggest the video and picture application
6090 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6092 <p
><blockquote
>
6094 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6095 </blockquote
></p
>
6097 <p
>An entry like this would suggest the pcmciautils package when a
6098 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6100 <p
><blockquote
>
6101 Package: pcmciautils
6102 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6103 </blockquote
></p
>
6105 <p
>An entry like this would suggest the package colorhug-client when
6106 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6108 <p
><blockquote
>
6109 Package: colorhug-client
6110 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6111 </blockquote
></p
>
6113 <p
>I believe the format is compatible with the format of the Packages
6114 file in the Debian archive. Ubuntu already uses their Packages file
6115 to store their mappings from packages to hardware.
</p
>
6117 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6118 announce the hardware it support in a way my prototype understand.
6119 This allow those publishing packages in an APT source outside the
6120 Debian archive as well as those backporting packages to make sure the
6121 hardware mapping are included in the package meta information. I
've
6122 tested such header in the pymissile package, and its modalias mapping
6123 is working as it should with my prototype. It even made it to Ubuntu
6126 <p
>To test if it was possible to look up supported hardware using only
6127 the shell tools available in the Debian installer, I wrote a shell
6128 implementation of the lookup code. The idea is to create files for
6129 each modalias and let the shell do the matching. Please check out and
6131 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6132 shell script. It run without any extra dependencies and fetch the
6133 hardware mappings from the Debian archive and the subversion
6134 repository where I currently work on my prototype.
</p
>
6136 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6137 install yubikey-personalization:
</p
>
6139 <p
><blockquote
>
6140 % ./hw-support-lookup
6141 <br
>yubikey-personalization
6143 </blockquote
></p
>
6145 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6146 propose to install the pcmciautils package:
</p
>
6148 <p
><blockquote
>
6149 % ./hw-support-lookup
6150 <br
>pcmciautils
6152 </blockquote
></p
>
6154 <p
>If you know of any hardware-package mapping that should be added to
6155 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6156 database
</a
>, please tell me about it.
</p
>
6158 <p
>It could be possible to generate several of the mappings between
6159 packages and hardware. One source would be to look at packages with
6160 kernel modules, ie packages with *.ko files in /lib/modules/, and
6161 extract their modalias information. Another would be to look at
6162 packages with udev rules, ie packages with files in
6163 /lib/udev/rules.d/, and extract their vendor/model information to
6164 generate a modalias matching rule. I have not tested any of these to
6165 see if it work.
</p
>
6167 <p
>If you want to help implementing a system to let us propose what
6168 packages to install when new hardware is plugged into a Debian
6169 machine, please send me an email or talk to me on
6170 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6175 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6176 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6177 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6178 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6179 <description><p
>While looking into how to look up Debian packages based on hardware
6180 information, to find the packages that support a given piece of
6181 hardware, I refreshed my memory regarding modalias values, and decided
6182 to document the details. Here are my findings so far, also available
6184 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6185 Debian Edu subversion repository
</a
>:
6187 <p
><strong
>Modalias decoded
</strong
></p
>
6189 <p
>This document try to explain what the different types of modalias
6190 values stands for. It is in part based on information from
6191 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6192 &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;,
6193 &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
6194 &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;.
6196 <p
>The modalias entries for a given Linux machine can be found using
6197 this shell script:
</p
>
6200 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6203 <p
>The supported modalias globs for a given kernel module can be found
6204 using modinfo:
</p
>
6207 % /sbin/modinfo psmouse | grep alias:
6208 alias: serio:ty05pr*id*ex*
6209 alias: serio:ty01pr*id*ex*
6213 <p
><strong
>PCI subtype
</strong
></p
>
6215 <p
>A typical PCI entry can look like this. This is an Intel Host
6216 Bridge memory controller:
</p
>
6218 <p
><blockquote
>
6219 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6220 </blockquote
></p
>
6222 <p
>This represent these values:
</p
>
6227 sv
00001028 (subvendor)
6228 sd
000001AD (subdevice)
6230 sc
00 (bus subclass)
6234 <p
>The vendor/device values are the same values outputted from
'lspci
6235 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6236 0600. The
0600 class is a host bridge. Other useful bus values are
6237 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6239 <p
>Not sure how to figure out the interface value, nor what it
6242 <p
><strong
>USB subtype
</strong
></p
>
6244 <p
>Some typical USB entries can look like this. This is an internal
6245 USB hub in a laptop:
</p
>
6247 <p
><blockquote
>
6248 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6249 </blockquote
></p
>
6251 <p
>Here is the values included in this alias:
</p
>
6254 v
1D6B (device vendor)
6255 p
0001 (device product)
6257 dc
09 (device class)
6258 dsc
00 (device subclass)
6259 dp
00 (device protocol)
6260 ic
09 (interface class)
6261 isc
00 (interface subclass)
6262 ip
00 (interface protocol)
6265 <p
>The
0900 device class/subclass means hub. Some times the relevant
6266 class is in the interface class section. For a simple USB web camera,
6267 these alias entries show up:
</p
>
6269 <p
><blockquote
>
6270 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6271 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6272 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6273 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6274 </blockquote
></p
>
6276 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6277 camera),
0101 is audio control device and
0102 is audio streaming (aka
6278 microphone). Thus this is a camera with microphone included.
</p
>
6280 <p
><strong
>ACPI subtype
</strong
></p
>
6282 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6283 receiver in a Thinkpad X40:
</p
>
6285 <p
><blockquote
>
6286 acpi:IBM0071:PNP0511:
6287 </blockquote
></p
>
6289 <p
>The values between the colons are IDs.
</p
>
6291 <p
><strong
>DMI subtype
</strong
></p
>
6293 <p
>The DMI table contain lots of information about the computer case
6294 and model. This is an entry for a IBM Thinkpad X40, fetched from
6295 /sys/devices/virtual/dmi/id/modalias:
</p
>
6297 <p
><blockquote
>
6298 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6299 </blockquote
></p
>
6301 <p
>The values present are
</p
>
6304 bvn IBM (BIOS vendor)
6305 bvr
1UETB
6WW(
1.66) (BIOS version)
6306 bd
06/
15/
2005 (BIOS date)
6307 svn IBM (system vendor)
6308 pn
2371H4G (product name)
6309 pvr ThinkPadX40 (product version)
6310 rvn IBM (board vendor)
6311 rn
2371H4G (board name)
6312 rvr NotAvailable (board version)
6313 cvn IBM (chassis vendor)
6314 ct
10 (chassis type)
6315 cvr NotAvailable (chassis version)
6318 <p
>The chassis type
10 is Notebook. Other interesting values can be
6319 found in the dmidecode source:
</p
>
6323 4 Low Profile Desktop
6336 17 Main Server Chassis
6337 18 Expansion Chassis
6339 20 Bus Expansion Chassis
6340 21 Peripheral Chassis
6342 23 Rack Mount Chassis
6351 <p
>The chassis type values are not always accurately set in the DMI
6352 table. For example my home server is a tower, but the DMI modalias
6353 claim it is a desktop.
</p
>
6355 <p
><strong
>SerIO subtype
</strong
></p
>
6357 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6358 test machine:
</p
>
6360 <p
><blockquote
>
6361 serio:ty01pr00id00ex00
6362 </blockquote
></p
>
6364 <p
>The values present are
</p
>
6373 <p
>This type is supported by the psmouse driver. I am not sure what
6374 the valid values are.
</p
>
6376 <p
><strong
>Other subtypes
</strong
></p
>
6378 <p
>There are heaps of other modalias subtypes according to
6379 file2alias.c. There is the rest of the list from that source: amba,
6380 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6381 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6382 vmbus, x86cpu and zorro. I did not spend time documenting all of
6383 these, as they do not seem relevant for my intended use with mapping
6384 hardware to packages when new stuff is inserted during run time.
</p
>
6386 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6388 <p
>To check which kernel modules provide support for a given modalias,
6389 one can use the following shell script:
</p
>
6392 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6393 echo
"$id
" ; \
6394 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6398 <p
>The output can look like this (only the first few entries as the
6399 list is very long on my test machine):
</p
>
6403 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6405 FATAL: Module acpi:device: not found.
6407 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6408 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6409 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6410 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6411 acpi:IBM0071:PNP0511:
6412 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6413 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6414 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6418 <p
>If you want to help implementing a system to let us propose what
6419 packages to install when new hardware is plugged into a Debian
6420 machine, please send me an email or talk to me on
6421 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6423 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6424 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6425 in /sys/ with space in them.
</p
>
6430 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6431 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6432 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6433 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6434 <description><p
>As part of my investigation on how to improve the support in Debian
6435 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6436 Launcher and updated the Debian package
6437 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6438 sure udev will fix the device permissions when it is plugged in. I
6439 also added a
"Modaliases
" header to test it in the Debian archive and
6440 hopefully make the package be proposed by jockey in Ubuntu when a user
6441 plug in his rocket launcher. In the process I moved the source to a
6442 git repository under collab-maint, to make it easier for any DD to
6443 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6444 is not very active, but the software still work for me even after five
6445 years of relative silence. The new git repository is not listed in
6446 the uploaded package yet, because I want to test the other changes a
6447 bit more before I upload the new version. If you want to check out
6448 the new version with a .desktop file included, visit the
6449 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6450 view
</a
> or use
"<tt
>git clone
6451 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6456 <title>Lets make hardware dongles easier to use in Debian
</title>
6457 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6458 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6459 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6460 <description><p
>One thing that annoys me with Debian and Linux distributions in
6461 general, is that there is a great package management system with the
6462 ability to automatically install software packages by downloading them
6463 from the distribution mirrors, but no way to get it to automatically
6464 install the packages I need to use the hardware I plug into my
6465 machine. Even if the package to use it is easily available from the
6466 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6467 suggest to automatically install the python-nxt, nbc and t2n packages
6468 I need to talk to it. When I plug in a Yubikey, it could propose the
6469 yubikey-personalization package. The information required to do this
6470 is available, but no-one have pulled all the pieces together.
</p
>
6472 <p
>Some years ago, I proposed to
6473 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6474 the discover subsystem to implement this
</a
>. The idea is fairly
6479 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6480 starting when a user log in.
</li
>
6482 <li
>Set this program up to listen for kernel events emitted when new
6483 hardware is inserted into the computer.
</li
>
6485 <li
>When new hardware is inserted, look up the hardware ID in a
6486 database mapping to packages, and take note of any non-installed
6487 packages.
</li
>
6489 <li
>Show a message to the user proposing to install the discovered
6490 package, and make it easy to install it.
</li
>
6494 <p
>I am not sure what the best way to implement this is, but my
6495 initial idea was to use dbus events to discover new hardware, the
6496 discover database to find packages and
6497 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6500 <p
>Yesterday, I found time to try to implement this idea, and the
6501 draft package is now checked into
6502 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6503 Debian Edu subversion repository
</a
>. In the process, I updated the
6504 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6505 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6506 the relevant packages in Debian, and uploaded a new version
6507 2.2013.01.09 to unstable. I also discovered that the current
6508 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6509 package in Debian no longer discovered any USB devices, because
6510 /proc/bus/usb/devices is no longer present. I ported it to use
6511 libusb as a fall back option to get it working. The fixed package
6512 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6513 because of the freeze).
</p
>
6515 <p
>With this prototype in place, I can insert my Yubikey, and get this
6516 desktop notification to show up (only once, the first time it is
6517 inserted):
</p
>
6519 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6521 <p
>For this prototype to be really useful, some way to automatically
6522 install the proposed packages by pressing the
"Please install
6523 program(s)
" button should to be implemented.
</p
>
6525 <p
>If this idea seem useful to you, and you want to help make it
6526 happen, please help me update the discover-data database with mappings
6527 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6528 list the package you would like to have installed when a given
6529 hardware device is inserted into your computer, and report bugs using
6530 reportbug if it isn
't. Or, if you know of a better way to provide
6531 such mapping, please let me know.
</p
>
6533 <p
>This prototype need more work, and there are several questions that
6534 should be considered before it is ready for production use. Is dbus
6535 the correct way to detect new hardware? At the moment I look for HAL
6536 dbus events on the system bus, because that is the events I could see
6537 on my Debian Squeeze KDE desktop. Are there better events to use?
6538 How should the user be notified? Is the desktop notification
6539 mechanism the best option, or should the background daemon raise a
6540 popup instead? How should packages be installed? When should they
6541 not be installed?
</p
>
6543 <p
>If you want to help getting such feature implemented in Debian,
6544 please send me an email. :)
</p
>
6549 <title>New IRC channel for LEGO designers using Debian
</title>
6550 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6551 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6552 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6553 <description><p
>During Christmas, I have worked a bit on the Debian support for
6554 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6555 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6556 discovered I had to build all the tools myself because none were
6557 already in Debian Squeeze. If Debian support for LEGO is something
6558 you care about, please join me on the IRC channel
6559 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6560 irc.debian.org). There is a lot that could be done to improve the
6561 Debian support for LEGO designers. For example both CAD software
6562 and Mindstorm compilers are missing. :)
</p
>
6564 <p
>Update
2012-
01-
03: A
6565 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6566 including links to Lego related packages is now available.
</p
>
6571 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6572 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6573 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6574 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6575 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6576 year! I hope next year will prove to be a good year.
</p
>
6578 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6579 decentralised
"currency
" that allow people to transfer bitcoins
6580 between each other with minimal overhead, is a very interesting
6581 experiment. And as I wrote a few days ago, the bitcoin situation in
6582 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6583 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6584 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6585 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6586 for one of the ftpmasters to approve the new bitcoin-qt package
6589 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6590 team in Debian, you can easily test the package in Debian Squeeze
6591 using the following steps to get a set of working packages:
</p
>
6593 <blockquote
><pre
>
6594 git clone git://git.debian.org/git/collab-maint/bitcoin
6596 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6597 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6598 </pre
></blockquote
>
6600 <p
>You might have to install some build dependencies as well. The
6601 list of commands should give you two packages, bitcoind and
6602 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6603 client will download the complete set of bitcoin
"blocks
", which need
6604 around
5.6 GiB of data on my machine at the moment. Make sure your
6605 ~/.bitcoin/ directory have lots of spare room if you want to download
6606 all the blocks. The client will warn if the disk is getting full, so
6607 there is not really a problem if you got too little room, but you will
6608 not be able to get all the features out of the client.
</p
>
6610 <p
>As usual, if you use bitcoin and want to show your support of my
6611 activities, please send Bitcoin donations to my address
6612 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6617 <title>A word on bitcoin support in Debian
</title>
6618 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6620 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6621 <description><p
>It has been a while since I wrote about
6622 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6623 peer-to-peer based crypto-currency, and the reason is simply that I
6624 have been busy elsewhere. But two days ago, I started looking at the
6625 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6626 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6627 is now maintained by a
6628 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6629 people
</a
>, and the grunt work had already been done by this team. We
6630 owe a huge thank you to all these team members. :)
6631 But I was sad to discover that the bitcoin client is missing in
6632 Wheezy. It is only available in Sid (and an outdated client from
6633 backports). The client had several RC bugs registered in BTS blocking
6634 it from entering testing. To try to help the team and improve the
6635 situation, I spent some time providing patches and triaging the bug
6636 reports. I also had a look at the bitcoin package available from Matt
6638 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6639 Ubuntu
</a
>, and moved the useful pieces from that version into the
6640 Debian package.
</p
>
6642 <p
>After checking with the main package maintainer Jonas Smedegaard on
6643 IRC, I pushed several patches into the collab-maint git repository to
6644 improve the package. It now contains fixes for the RC issues (not from
6645 me, but fixed by Scott Howard), build rules for a Qt GUI client
6646 package, konqueror support for the bitcoin: URI and bash completion
6647 setup. As I work on Debian Squeeze, I also created
6648 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6649 patch to backport
</a
> the latest version. Jonas is going to look at
6650 it and try to integrate it into the git repository before uploading a
6651 new version to unstable.
6653 <p
>I would very much like bitcoin to succeed, to get rid of the
6654 centralized control currently exercised in the monetary system. I
6655 find it completely unacceptable that the USA government is collecting
6656 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6657 that the major credit card companies can block legal money
6658 transactions to Wikileaks. But for bitcoin to succeed, more people
6659 need to use bitcoins, and more people need to accept bitcoins when
6660 they sell products and services. Improving the bitcoin support in
6661 Debian is a small step in the right direction, but not enough.
6662 Unfortunately the user experience when browsing the web and wanting to
6663 pay with bitcoin is still not very good. The bitcoin: URI is a step
6664 in the right direction, but need to work in most or every browser in
6665 use. Also the bitcoin-qt client is too heavy to fire up to do a
6666 quick transaction. I believe there are other clients available, but
6667 have not tested them.
</p
>
6670 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6671 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6672 I received
20.15 BTC so far on the address I provided in my blog two
6673 years ago, as can be
6674 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6675 on the blockexplorer service
</a
>. Thank you everyone for your
6676 donation. The blockexplorer service demonstrates quite well that
6677 bitcoin is not quite anonymous and untracked. :) I wonder if the
6678 number of users have gone up since then. If you use bitcoin and want
6679 to show your support of my activity, please send Bitcoin donations to
6680 the same address as last time,
6681 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6686 <title>Git repository for song book for Computer Scientists
</title>
6687 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6688 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6689 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6690 <description><p
>As I
6691 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6692 this summer
</a
>, I have created a Computer Science song book a few
6693 years ago, and today I finally found time to create a public
6694 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6695 repository for the project
</a
>.
</p
>
6697 <p
>If you want to help out, please clone the source and submit patches
6698 to the HTML version. To generate the PDF and PostScript version,
6699 please use prince XML, or let me know about a useful free software
6700 processor capable of creating a good looking PDF from the HTML.
</p
>
6702 <p
>Want to sing? You can still find the song book in HTML, PDF and
6703 PostScript formats at
6704 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6705 Science Songbook
</a
>.
</p
>
6710 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6711 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6712 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6713 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6714 <description><p
>I dag fyller
6715 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6716 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6717 si gratulerer med dagen, Debian!
</p
>
6722 <title>Song book for Computer Scientists
</title>
6723 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6725 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6726 <description><p
>Many years ago, while studying Computer Science at the
6727 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6728 collecting computer related songs for use at parties. The original
6729 version was written in LaTeX, but a few years ago I got help from
6730 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6731 while keeping the ability to create a nice book in PDF format. I have
6732 not had time to maintain the book for a while now, and guess I should
6733 put it up on some public version control repository where others can
6734 help me extend and update the book. If anyone is volunteering to help
6735 me with this, send me an email. Also let me know if there are songs
6736 missing in my book.
</p
>
6738 <p
>I have not mentioned the book on my blog so far, and it occured to
6739 me today that I really should let all my readers share the joys of
6740 singing out load about programming, computers and computer networks.
6741 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6742 12</a
> is about to start (and I am not going). Want to sing? Check
6743 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6744 Computer Science Songbook
</a
>.
6749 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6750 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6751 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6752 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6753 <description><p
>At work we have heaps of servers. I believe the total count is
6754 around
1000 at the moment. To be able to get help from the vendors
6755 when something go wrong, we want to keep the firmware on the servers
6756 up to date. If the firmware isn
't the latest and greatest, the
6757 vendors typically refuse to start debugging any problems until the
6758 firmware is upgraded. So before every reboot, we want to upgrade the
6759 firmware, and we would really like everyone handling servers at the
6760 university to do this themselves when they plan to reboot a machine.
6761 For that to happen we at the unix server admin group need to provide
6762 the tools to do so.
</p
>
6764 <p
>To make firmware upgrading easier, I am working on a script to
6765 fetch and install the latest firmware for the servers we got. Most of
6766 our hardware are from Dell and HP, so I have focused on these servers
6767 so far. This blog post is about the Dell part.
</P
>
6769 <p
>On the Dell FTP site I was lucky enough to find
6770 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6771 with firmware information for all
11th generation servers, listing
6772 which firmware should be used on a given model and where on the FTP
6773 site I can find it. Using a simple perl XML parser I can then
6774 download the shell scripts Dell provides to do firmware upgrades from
6775 within Linux and reboot when all the firmware is primed and ready to
6776 be activated on the first reboot.
</p
>
6778 <p
>This is the Dell related fragment of the perl code I am working on.
6779 Are there anyone working on similar tools for firmware upgrading all
6780 servers at a site? Please get in touch and lets share resources.
</p
>
6782 <p
><pre
>
6786 use File::Temp qw(tempdir);
6788 # Install needed RHEL packages if missing
6790 'XML::Simple
' =
> 'perl-XML-Simple
',
6792 for my $module (keys %rhelmodules) {
6793 eval
"use $module;
";
6795 my $pkg = $rhelmodules{$module};
6796 system(
"yum install -y $pkg
");
6797 eval
"use $module;
";
6801 my $errorsto =
'pere@hungry.com
';
6807 sub run_firmware_script {
6808 my ($opts, $script) = @_;
6810 print STDERR
"fail: missing script name\n
";
6813 print STDERR
"Running $script\n\n
";
6815 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6816 print STDERR
"success: firmware script ran succcessfully\n
";
6818 print STDERR
"fail: firmware script returned error\n
";
6822 sub run_firmware_scripts {
6823 my ($opts, @dirs) = @_;
6824 # Run firmware packages
6825 for my $dir (@dirs) {
6826 print STDERR
"info: Running scripts in $dir\n
";
6827 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6828 while (my $s = readdir $dh) {
6829 next if $s =~ m/^\.\.?/;
6830 run_firmware_script($opts,
"$dir/$s
");
6838 print STDERR
"info: Downloading $url\n
";
6839 system(
"wget --quiet \
"$url\
"");
6844 my $product = `dmidecode -s system-product-name`;
6847 if ($product =~ m/PowerEdge/) {
6849 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6850 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6852 my $tmpdir = tempdir(
6856 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6857 system(
'gunzip Catalog.xml.gz
');
6858 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6859 # -q is quiet, disabling interactivity and reducing console output
6860 my $fwopts =
"-q
";
6862 for my $url (@paths) {
6863 fetch_dell_fw($url);
6865 run_firmware_scripts($fwopts, $tmpdir);
6867 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6868 print STDERR
"error: Please report to $errorsto.\n
";
6872 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6873 print STDERR
"error: Please report to $errorsto.\n
";
6879 my $url =
"ftp://ftp.us.dell.com/$path
";
6883 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6884 # firmware packages to download from Dell. Only work for Linux
6885 # machines and
11th generation Dell servers.
6886 sub fetch_dell_fw_list {
6887 my $filename = shift;
6889 my $product = `dmidecode -s system-product-name`;
6891 my ($mybrand, $mymodel) = split(/\s+/, $product);
6893 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6895 my $xml = XMLin($filename);
6897 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6898 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6899 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6901 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6902 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6904 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6906 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6908 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6911 for my $component (@{$xml-
>{SoftwareComponent}}) {
6912 my $componenttype = $component-
>{ComponentType}-
>{value};
6914 # Drop application packages, only firmware and BIOS
6915 next if
'APAC
' eq $componenttype;
6917 my $cpath = $component-
>{path};
6918 for my $path (@paths) {
6919 if ($cpath =~ m%/$path$%) {
6920 push(@paths, $cpath);
6928 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6929 it could work on other platforms with some tweaking. Anyone know a
6930 index like Catalog.xml is available from HP for HP servers? At the
6931 moment I maintain a similar list manually and it is quickly getting
6937 <title>How is booting into runlevel
1 different from single user boots?
</title>
6938 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6939 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6940 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6941 <description><p
>Wouter Verhelst have some
6942 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6943 comments and opinions
</a
> on my blog post on
6944 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6945 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6946 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6947 default KDE desktop in Debian
</a
>. I only have time to address one
6948 small piece of his comment now, and though it best to address the
6949 misunderstanding he bring forward:
</p
>
6951 <p
><blockquote
>
6952 Currently, a system admin has four options: [...] boot to a
6953 single-user system (by adding
'single
' to the kernel command line;
6954 this runs rcS and rc1 scripts)
6955 </blockquote
></p
>
6957 <p
>This make me believe Wouter believe booting into single user mode
6958 and booting into runlevel
1 is the same. I am not surprised he
6959 believe this, because it would make sense and is a quite sensible
6960 thing to believe. But because the boot in Debian is slightly broken,
6961 runlevel
1 do not work properly and it isn
't the same as single user
6962 mode. I
'll try to explain what is actually happing, but it is a bit
6963 hard to explain.
</p
>
6965 <p
>Single user mode is defined like this in /etc/inittab:
6966 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6967 executed in single user mode is sulogin. Single user mode is a boot
6968 state
"between
" the runlevels, and when booting into single user mode,
6969 only the scripts in /etc/rcS.d/ are executed before the init process
6970 enters the single user state. When switching to runlevel
1, the state
6971 is in fact not ending in runlevel
1, but it passes through runlevel
1
6972 and end up in the single user mode (see /etc/rc1.d/S03single, which
6973 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6974 1. It is confusing that the
'S
' (single user) init mode is not the
6975 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6978 <p
>This summary might make it clearer. When booting for the first
6979 time into single user mode, the following commands are executed:
6980 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6981 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6982 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6983 trying to continue after visiting single user mode. Not all services
6984 are started again as they should, causing the machine to end up in an
6985 unpredicatble state. This is why Debian admins recommend rebooting
6986 after visiting single user mode.
</p
>
6988 <p
>A similar problem with runlevel
1 is caused by the amount of
6989 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6990 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6991 stopped when passing through the scripts in /etc/rc1.d/, and not
6992 started again when switching away from runlevel
1 to the runlevels
6993 2-
5. I believe the problem is best fixed by moving all the scripts
6994 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6995 functioning single user mode during boot.
</p
>
6997 <p
>I have spent several years investigating the Debian boot system,
6998 and discovered this problem a few years ago. I suspect it originates
6999 from when sysvinit was introduced into Debian, a long time ago.
</p
>
7004 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
7005 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
7006 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
7007 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
7008 <description><p
>In the Debian boot system, several packages include scripts that
7009 are started from /etc/rcS.d/. In fact, there is a bite more of them
7010 than make sense, and this causes a few problems. What kind of
7011 problems, you might ask. There are at least two problems. The first
7012 is that it is not possible to recover a machine after switching to
7013 runlevel
1. One need to actually reboot to get the machine back to
7014 the expected state. The other is that single user boot will sometimes
7015 run into problems because some of the subsystems are activated before
7016 the root login is presented, causing problems when trying to recover a
7017 machine from a problem in that subsystem. A minor additional point is
7018 that moving more scripts out of rcS.d/ and into the other rc#.d/
7019 directories will increase the amount of scripts that can run in
7020 parallel during boot, and thus decrease the boot time.
</p
>
7022 <p
>So, which scripts should start from rcS.d/. In short, only the
7023 scripts that _have_ to execute before the root login prompt is
7024 presented during a single user boot should go there. Everything else
7025 should go into the numeric runlevels. This means things like
7026 lm-sensors, fuse and x11-common should not run from rcS.d, but from
7027 the numeric runlevels. Today in Debian, there are around
115 init.d
7028 scripts that are started from rcS.d/, and most of them should be moved
7029 out. Do your package have one of them? Please help us make single
7030 user and runlevel
1 better by moving it.
</p
>
7032 <p
>Scripts setting up the screen, keyboard, system partitions
7033 etc. should still be started from rcS.d/, but there is for example no
7034 need to have the network enabled before the single user login prompt
7035 is presented.
</p
>
7037 <p
>As always, things are not so easy to fix as they sound. To keep
7038 Debian systems working while scripts migrate and during upgrades, the
7039 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
7040 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
7041 and the next ones can only be moved when their dependencies have been
7042 moved first. This migration must be done sequentially while we ensure
7043 that the package system upgrade packages in the right order to keep
7044 the system state correct. This will require some coordination when it
7045 comes to network related packages, but most of the packages with
7046 scripts that should migrate do not have anything in rcS.d/ depending
7047 on them. Some packages have already been updated, like the sudo
7048 package, while others are still left to do. I wish I had time to work
7049 on this myself, but real live constrains make it unlikely that I will
7050 find time to push this forward.
</p
>
7055 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
7056 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
7057 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
7058 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
7059 <description><p
>While at Debconf11, I have several times during discussions
7060 mentioned the issues I believe should be improved in Debian for its
7061 desktop to be useful for more people. The use case for this is my
7062 parents, which are currently running Kubuntu which solve the
7065 <p
>I suspect these four missing features are not very hard to
7066 implement. After all, they are present in Ubuntu, so if we wanted to
7067 do this in Debian we would have a source.
</p
>
7071 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7072 are new packages available for upgrades, a icon in the KDE status bar
7073 indicate this, and clicking on it will activate the simple upgrade
7074 tool to handle it. I have no problem guiding both of my parents
7075 through the process over the phone. If a kernel reboot is required,
7076 this too is indicated by the status bars and the upgrade tool. Last
7077 time I checked, nothing with the same features was working in KDE in
7080 <li
><strong
>Simple handling of missing Firefox browser
7081 plugins.
</strong
> When the browser encounter a MIME type it do not
7082 currently have a handler for, it will ask the user if the system
7083 should search for a package that would add support for this MIME type,
7084 and if the user say yes, the APT sources will be searched for packages
7085 advertising the MIME type in their control file (visible in the
7086 Packages file in the APT archive). If one or more packages are found,
7087 it is a simple click of the mouse to add support for the missing mime
7088 type. If the package require the user to accept some non-free
7089 license, this is explained to the user. The entire process make it
7090 more clear to the user why something do not work in the browser, and
7091 make the chances higher for the user to blame the web page authors and
7092 not the browser for any missing features.
</li
>
7094 <li
><strong
>Simple handling of missing multimedia codec/format
7095 handlers.
</strong
> When the media players encounter a format or codec
7096 it is not supporting, a dialog pop up asking the user if the system
7097 should search for a package that would add support for it. This
7098 happen with things like MP3, Windows Media or H
.264. The selection
7099 and installation procedure is very similar to the Firefox browser
7100 plugin handling. This is as far as I know implemented using a
7101 gstreamer hook. The end result is that the user easily get access to
7102 the codecs that are present from the APT archives available, while
7103 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7105 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7106 displaying a text/plain file in my Debian browser, it will propose to
7107 start emacs to show it. If I remember correctly, when doing the same
7108 in Kunbutu it show the file as a text file in the browser. At least I
7109 know Opera will show text files within the browser. I much prefer the
7110 latter behaviour.
</li
>
7114 <p
>There are other nice features as well, like the simplified suite
7115 upgrader, but given that I am the one mostly doing the dist-upgrade,
7116 it do not matter much.
</p
>
7118 <p
>I really hope we could get these features in place for the next
7119 Debian release. It would require the coordinated effort of several
7120 maintainers, but would make the end user experience a lot better.
</p
>
7125 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7126 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7127 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7128 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7129 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7130 site is build on Debian/Squeeze, and this platform was chosen because
7131 I am most familiar with Debian (being a Debian Developer for around
10
7132 years) because it is the latest stable Debian release which should get
7133 security support for a few years.
</p
>
7135 <p
>The web service is written in Perl, and depend on some perl modules
7136 that are missing in Debian at the moment. It would be great if these
7137 modules were added to the Debian archive, allowing anyone to set up
7138 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7139 in their own country using only Debian packages. The list of modules
7140 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7141 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7142 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7143 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7144 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7145 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7146 easier in the future.
</p
>
7148 <p
>Thanks to the great tools in Debian, getting the missing modules
7149 installed on my server was a simple call to
'cpan2deb Module::Name
'
7150 and
'dpkg -i
' to install the resulting package. But this leave me
7151 with the responsibility of tracking security problems, which I really
7152 do not have time for.
</p
>
7157 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7158 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7159 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7160 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7161 <description><p
>Here is a small update for my English readers. Most of my blog
7162 posts have been in Norwegian the last few weeks, so here is a short
7163 update in English.
</p
>
7165 <p
>The kids still keep me too busy to get much free software work
7166 done, but I did manage to organise a project to get a Norwegian port
7167 of the British service
7168 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7169 and it has been running for a month now. The entire project has been
7170 organised by me and two others. Around Christmas we gathered sponsors
7171 to fund the development work. In January I drafted a contract with
7172 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7173 and in February the development took place. Most of it involved
7174 converting the source to use GPS coordinates instead of British
7175 easting/northing, and the resulting code should be a lot easier to get
7176 running in any country by now. The Norwegian
7177 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7178 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7179 source and the source for administrative borders in Norway, and
7180 support for this had to be added/fixed.
</p
>
7182 <p
>The Norwegian version went live March
3th, and we spent the weekend
7183 polishing the system before we announced it March
7th. The system is
7184 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7185 problem reports in a few weeks. Soon we hope to announce the Android
7186 and iPhone versions making it even easier to report problems with the
7187 public infrastructure.
</p
>
7189 <p
>Perhaps something to consider for those of you in countries without
7190 such service?
</p
>
7195 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7196 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7197 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7198 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7199 <description><p
>The last few days I have looked at ways to track open security
7200 issues here at my work with the University of Oslo. My idea is that
7201 it should be possible to use the information about security issues
7202 available on the Internet, and check our locally
7203 maintained/distributed software against this information. It should
7204 allow us to verify that no known security issues are forgotten. The
7205 CVE database listing vulnerabilities seem like a great central point,
7206 and by using the package lists from Debian mapped to CVEs provided by
7207 the testing security team, I believed it should be possible to figure
7208 out which security holes were present in our free software
7209 collection.
</p
>
7211 <p
>After reading up on the topic, it became obvious that the first
7212 building block is to be able to name software packages in a unique and
7213 consistent way across data sources. I considered several ways to do
7214 this, for example coming up with my own naming scheme like using URLs
7215 to project home pages or URLs to the Freshmeat entries, or using some
7216 existing naming scheme. And it seem like I am not the first one to
7217 come across this problem, as MITRE already proposed and implemented a
7218 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7219 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7220 software, hardware and other platform components. The CPE ids are
7221 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7222 Vulnerability Database
</a
>, allowing me to look up know security
7223 issues for any CPE name. With this in place, all I need to do is to
7224 locate the CPE id for the software packages we use at the university.
7225 This is fairly trivial (I google for
'cve cpe $package
' and check the
7226 NVD entry if a CVE for the package exist).
</p
>
7228 <p
>To give you an example. The GNU gzip source package have the CPE
7229 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7230 check out, one could look up
7231 <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
7232 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7233 The most recent one is
7234 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7235 and at the bottom of the NVD page for this vulnerability the complete
7236 list of affected versions is provided.
</p
>
7238 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7239 for offline processing of issues. Using this dump, I
've written a
7240 small script taking a list of CPEs as input and list all CVEs
7241 affecting the packages represented by these CPEs. One give it CPEs
7242 with version numbers as specified above and get a list of open
7243 security issues out.
</p
>
7245 <p
>Of course for this approach to be useful, the quality of the NVD
7246 information need to be high. For that to happen, I believe as many as
7247 possible need to use and contribute to the NVD database. I notice
7249 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7250 map from CVE to CPE
</a
>, indicating that they are using the CPE
7251 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7253 <p
>To get an idea about the quality for free software, I spent some
7254 time making it possible to compare the CVE database from Debian with
7255 the CVE database in NVD. The result look fairly good, but there are
7256 some inconsistencies in NVD (same software package having several
7257 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7258 Debian believe are affected by a CVE). Hope to find time to improve
7259 the quality of NVD, but that require being able to get in touch with
7260 someone maintaining it. So far my three emails with questions and
7261 corrections have not seen any reply, but I hope contact can be
7262 established soon.
</p
>
7264 <p
>An interesting application for CPEs is cross platform package
7265 mapping. It would be useful to know which packages in for example
7266 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7267 this would be trivial if all linux distributions provided CPE entries
7268 for their packages.
</p
>
7273 <title>Which module is loaded for a given PCI and USB device?
</title>
7274 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7275 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7276 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7277 <description><p
>In the
7278 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7279 package in Debian, there is a script to report useful information
7280 about the running hardware for use when people report missing
7281 information. One part of this script that I find very useful when
7282 debugging hardware problems, is the part mapping loaded kernel module
7283 to the PCI device it claims. It allow me to quickly see if the kernel
7284 module I expect is driving the hardware I am struggling with. To see
7285 the output, make sure discover-data is installed and run
7286 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7287 one of my machines like this:
</p
>
7291 10de:
03eb i2c_nforce2
7294 10de:
03f0 snd_hda_intel
7303 <p
>The code in question look like this, slightly modified for
7304 readability and to drop the output to file descriptor
3:
</p
>
7307 if [ -d /sys/bus/pci/devices/ ] ; then
7308 echo loaded pci modules:
7310 cd /sys/bus/pci/devices/
7311 for address in * ; do
7312 if [ -d
"$address/driver/module
" ] ; then
7313 module=`cd $address/driver/module ; pwd -P | xargs basename`
7314 if grep -q
"^$module
" /proc/modules ; then
7315 address=$(echo $address |sed s/
0000://)
7316 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7317 echo
"$id $module
"
7326 <p
>Similar code could be used to extract USB device module
7330 if [ -d /sys/bus/usb/devices/ ] ; then
7331 echo loaded usb modules:
7333 cd /sys/bus/usb/devices/
7334 for address in * ; do
7335 if [ -d
"$address/driver/module
" ] ; then
7336 module=`cd $address/driver/module ; pwd -P | xargs basename`
7337 if grep -q
"^$module
" /proc/modules ; then
7338 address=$(echo $address |sed s/
0000://)
7339 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7340 if [
"$id
" ] ; then
7341 echo
"$id $module
"
7351 <p
>This might perhaps be something to include in other tools as
7357 <title>How to test if a laptop is working with Linux
</title>
7358 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7359 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7360 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7361 <description><p
>The last few days I have spent at work here at the
<a
7362 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7363 batch of computers will work with Linux. Every year for the last few
7364 years the university have organised shared bid of a few thousand
7365 computers, and this year HP won the bid. Two different desktops and
7366 five different laptops are on the list this year. We in the UNIX
7367 group want to know which one of these computers work well with RHEL
7368 and Ubuntu, the two Linux distributions we currently handle at the
7369 university.
</p
>
7371 <p
>My test method is simple, and I share it here to get feedback and
7372 perhaps inspire others to test hardware as well. To test, I PXE
7373 install the OS version of choice, and log in as my normal user and run
7374 a few applications and plug in selected pieces of hardware. When
7375 something fail, I make a note about this in the test matrix and move
7376 on. If I have some spare time I try to report the bug to the OS
7377 vendor, but as I only have the machines for a short time, I rarely
7378 have the time to do this for all the problems I find.
</p
>
7380 <p
>Anyway, to get to the point of this post. Here is the simple tests
7381 I perform on a new model.
</p
>
7385 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7386 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7387 RHEL5 and Debian Edu/Squeeze.
</li
>
7389 <li
>Is X.org working? If the graphical login screen show up after
7390 installation, X.org is working.
</li
>
7392 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7393 package mesa-utils on Ubuntu) and writing down the frames per second
7394 reported by the program.
</li
>
7396 <li
>Is sound working? With Gnome and KDE, a sound is played when
7397 logging in, and if I can hear this the test is successful. If there
7398 are several audio exits on the machine, I try them all and check if
7399 the Gnome/KDE audio mixer can control where to send the sound. I
7400 normally test this by playing
7401 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7402 video
</a
> in Firefox/Iceweasel.
</li
>
7404 <li
>Is the USB subsystem working? I test this by plugging in a USB
7405 memory stick and see if Gnome/KDE notices this.
</li
>
7407 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7408 I have lying around, and see if Gnome/KDE notices this.
</li
>
7410 <li
>Is any built in camera working? Test using cheese, and see if a
7411 picture from the v4l device show up.
</li
>
7413 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7414 any bluetooth devices are discovered. In my office, I normally see a
7417 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7418 memory modules lying around, and stick them in and see if Gnome/KDE
7419 notice this.
</li
>
7421 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7422 special button work, and if the laptop continue to work after
7425 <li
>For laptops, is the extra buttons working, like audio level,
7426 adjusting background light, switching on/off external video output,
7427 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7428 laptop to laptop, so I just write down which are working and which are
7431 <li
>Some laptops have smart card readers, finger print readers,
7432 acceleration sensors etc. I rarely test these, as I do not know how
7433 to quickly test if they are working or not, so I only document their
7434 existence.
</li
>
7438 <p
>By now I suspect you are really curious what the test results are
7439 for the HP machines I am testing. I
'm not done yet, so I will report
7440 the test results later. For now I can report that HP
8100 Elite work
7441 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7442 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7443 can see, I have most machines left to test. One interesting
7444 observation is that Ubuntu Lucid has almost twice the frame rate than
7445 RHEL6 with glxgears. No idea why.
</p
>
7450 <title>Some thoughts on BitCoins
</title>
7451 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7452 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7453 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7454 <description><p
>As I continue to explore
7455 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7456 what properties the system have, and how it will be affected by laws
7457 and regulations here in Norway. Here are some random notes.
</p
>
7459 <p
>One interesting thing to note is that since the transactions are
7460 verified using a peer to peer network, all details about a transaction
7461 is known to everyone. This means that if a BitCoin address has been
7462 published like I did with mine in my initial post about BitCoin, it is
7463 possible for everyone to see how many BitCoins have been transfered to
7464 that address. There is even a web service to look at the details for
7465 all transactions. There I can see that my address
7466 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7467 have received
16.06 Bitcoin, the
7468 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7469 address of Simon Phipps have received
181.97 BitCoin and the address
7470 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7471 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7472 every one of you that donated bitcoins to support my activity. The
7473 fact that anyone can see how much money was transfered to a given
7474 address make it more obvious why the BitCoin community recommend to
7475 generate and hand out a new address for each transaction. I
'm told
7476 there is no way to track which addresses belong to a given person or
7477 organisation without the person or organisation revealing it
7478 themselves, as Simon, EFF and I have done.
</p
>
7480 <p
>In Norway, and in most other countries, there are laws and
7481 regulations limiting how much money one can transfer across the border
7482 without declaring it. There are money laundering, tax and accounting
7483 laws and regulations I would expect to apply to the use of BitCoin.
7484 If the Skolelinux foundation
7485 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7486 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7487 normal bank transfers like EFF is doing, how should this be accounted?
7488 Given that it is impossible to know if money can cross the border or
7489 not, should everything or nothing be declared? What exchange rate
7490 should be used when calculating taxes? Would receivers have to pay
7491 income tax if the foundation were to pay Skolelinux contributors in
7492 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7494 <p
>For a currency to be useful and successful, it must be trusted and
7495 accepted by a lot of users. It must be possible to get easy access to
7496 the currency (as a wage or using currency exchanges), and it must be
7497 easy to spend it. At the moment BitCoin seem fairly easy to get
7498 access to, but there are very few places to spend it. I am not really
7499 a regular user of any of the vendor types currently accepting BitCoin,
7500 so I wonder when my kind of shop would start accepting BitCoins. I
7501 would like to buy electronics, travels and subway tickets, not herbs
7502 and books. :) The currency is young, and this will improve over time
7503 if it become popular, but I suspect regular banks will start to lobby
7504 to get BitCoin declared illegal if it become popular. I
'm sure they
7505 will claim it is helping fund terrorism and money laundering (which
7506 probably would be true, as is any currency in existence), but I
7507 believe the problems should be solved elsewhere and not by blaming
7508 currencies.
</p
>
7510 <p
>The process of creating new BitCoins is called mining, and it is
7511 CPU intensive process that depend on a bit of luck as well (as one is
7512 competing against all the other miners currently spending CPU cycles
7513 to see which one get the next lump of cash). The
"winner
" get
50
7514 BitCoin when this happen. Yesterday I came across the obvious way to
7515 join forces to increase ones changes of getting at least some coins,
7516 by coordinating the work on mining BitCoins across several machines
7517 and people, and sharing the result if one is lucky and get the
50
7519 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7520 if this sounds interesting. I have not had time to try to set up a
7521 machine to participate there yet, but have seen that running on ones
7522 own for a few days have not yield any BitCoins througth mining
7525 <p
>Update
2010-
12-
15: Found an
<a
7526 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7527 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7528 it was interesting to read. The arguments presented seem to be
7529 equally valid for gold, which was used as a currency for many years.
</p
>
7534 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7535 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7536 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7537 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7538 <description><p
>With this weeks lawless
7539 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7540 attacks
</a
> on Wikileak and
7541 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7542 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7543 not be trusted to handle money transactions.
7545 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7546 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7547 mine mentioned earlier. I decided to follow Simon
's example, and get
7548 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7549 some help from my friend to get it all running, and he even handed me
7550 some bitcoins to get started. I even donated a few bitcoins to Simon
7551 for helping me remember BitCoin.
</p
>
7553 <p
>So, what is bitcoins, you probably wonder? It is a digital
7554 crypto-currency, decentralised and handled using peer-to-peer
7555 networks. It allows anonymous transactions and prohibits central
7556 control over the transactions, making it impossible for governments
7557 and companies alike to block donations and other transactions. The
7558 source is free software, and while the key dependency wxWidgets
2.9
7559 for the graphical user interface is missing in Debian, the command
7560 line client builds just fine. Hopefully Jonas
7561 <a href=
"http://bugs.debian.org/
578157">will get the package into
7562 Debian
</a
> soon.
</p
>
7564 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7565 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7566 bitcoins
</a
> when selling services and goods, and there are even
7567 currency
"stock
" markets where the exchange rate is decided. There
7568 are not many users so far, but the concept seems promising. If you
7569 want to get started and lack a friend with any bitcoins to spare,
7571 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7572 bitcoin at the time of writing). Use
7573 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7574 on the current exchange rates.
</p
>
7576 <p
>As an experiment, I have decided to set up bitcoind on one of my
7577 machines. If you want to support my activity, please send Bitcoin
7578 donations to the address
7579 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7584 <title>Why isn
't Debian Edu using VLC?
</title>
7585 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7587 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7588 <description><p
>In the latest issue of Linux Journal, the readers choices were
7589 presented, and the winner among the multimedia player were VLC.
7590 Personally, I like VLC, and it is my player of choice when I first try
7591 to play a video file or stream. Only if VLC fail will I drag out
7592 gmplayer to see if it can do better. The reason is mostly the failure
7593 model and trust. When VLC fail, it normally pop up a error message
7594 reporting the problem. When mplayer fail, it normally segfault or
7595 just hangs. The latter failure mode drain my trust in the program.
<p
>
7597 <p
>But even if VLC is my player of choice, we have choosen to use
7598 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7599 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7600 plugin to play web videos seamlessly, and the VLC browser plugin is
7601 not very good. For example, it lack in-line control buttons, so there
7602 is no way for the user to pause the video. Also, when I
7603 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7604 tested the browser plugins
</a
> available in Debian, the VLC plugin
7605 failed on several video pages where mplayer based plugins worked. If
7606 the browser plugin for VLC was as good as the gecko-mediaplayer
7607 package (which uses mplayer), we would switch.
</P
>
7609 <p
>While VLC is a good player, its user interface is slightly
7610 annoying. The most annoying feature is its inconsistent use of
7611 keyboard shortcuts. When the player is in full screen mode, its
7612 shortcuts are different from when it is playing the video in a window.
7613 For example, space only work as pause when in full screen mode. I
7614 wish it had consisten shortcuts and that space also would work when in
7615 window mode. Another nice shortcut in gmplayer is [enter] to restart
7616 the current video. It is very nice when playing short videos from the
7617 web and want to restart it when new people arrive to have a look at
7618 what is going on.
</p
>
7623 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7624 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7625 <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>
7626 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7627 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7628 upgrade testing of the
7629 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7630 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7631 This seem like a very good idea, so I adjusted by test scripts and
7632 can now present the updated result from today:
</p
>
7634 <p
>This is for Gnome:
</p
>
7636 <p
>Installed using apt-get, missing with aptitude
</p
>
7638 <blockquote
><p
>
7643 browser-plugin-gnash
7650 freedesktop-sound-theme
7652 gconf-defaults-service
7667 gnome-desktop-environment
7671 gnome-session-canberra
7676 gstreamer0.10-fluendo-mp3
7682 libapache2-mod-dnssd
7685 libaprutil1-dbd-sqlite3
7688 libboost-date-time1.42
.0
7689 libboost-python1.42
.0
7690 libboost-thread1.42
.0
7692 libchamplain-gtk-
0.4-
0
7694 libclutter-gtk-
0.10-
0
7701 libfreerdp-plugins-standard
7716 libgnomepanel2.24-cil
7721 libgtksourceview2.0-common
7722 libmono-addins-gui0.2-cil
7723 libmono-addins0.2-cil
7724 libmono-cairo2.0-cil
7725 libmono-corlib2.0-cil
7726 libmono-i18n-west2.0-cil
7727 libmono-posix2.0-cil
7728 libmono-security2.0-cil
7729 libmono-sharpzip2.84-cil
7730 libmono-system2.0-cil
7733 libndesk-dbus-glib1.0-cil
7734 libndesk-dbus1.0-cil
7744 libtelepathy-farsight0
7753 nautilus-sendto-empathy
7757 python-aptdaemon-gtk
7759 python-beautifulsoup
7774 python-gtksourceview2
7785 python-pkg-resources
7792 python-twisted-conch
7798 python-zope.interface
7803 rhythmbox-plugin-cdrecorder
7810 system-config-printer-udev
7812 telepathy-mission-control-
5
7823 </p
></blockquote
>
7825 <p
>Installed using apt-get, removed with aptitude
</p
>
7827 <blockquote
><p
>
7833 fast-user-switch-applet
7852 libgtksourceview2.0-
0
7854 libsdl1.2debian-alsa
7860 system-config-printer
7865 </p
></blockquote
>
7867 <p
>Installed using aptitude, missing with apt-get
</p
>
7869 <blockquote
><p
>
7870 gstreamer0.10-gnomevfs
7871 </p
></blockquote
>
7873 <p
>Installed using aptitude, removed with apt-get
</p
>
7875 <blockquote
><p
>
7877 </p
></blockquote
>
7879 <p
>This is for KDE:
</p
>
7881 <p
>Installed using apt-get, missing with aptitude
</p
>
7883 <blockquote
><p
>
7885 </p
></blockquote
>
7887 <p
>Installed using apt-get, removed with aptitude
</p
>
7889 <blockquote
><p
>
7892 </p
></blockquote
>
7894 <p
>Installed using aptitude, missing with apt-get
</p
>
7896 <blockquote
><p
>
7910 kdeartwork-emoticons
7912 kdeartwork-theme-icon
7916 kdebase-workspace-bin
7917 kdebase-workspace-data
7931 kscreensaver-xsavers
7946 plasma-dataengines-workspace
7948 plasma-desktopthemes-artwork
7949 plasma-runners-addons
7950 plasma-scriptengine-googlegadgets
7951 plasma-scriptengine-python
7952 plasma-scriptengine-qedje
7953 plasma-scriptengine-ruby
7954 plasma-scriptengine-webkit
7955 plasma-scriptengines
7956 plasma-wallpapers-addons
7957 plasma-widget-folderview
7958 plasma-widget-networkmanagement
7962 xscreensaver-data-extra
7964 xscreensaver-gl-extra
7965 xscreensaver-screensaver-bsod
7966 </p
></blockquote
>
7968 <p
>Installed using aptitude, removed with apt-get
</p
>
7970 <blockquote
><p
>
7972 google-gadgets-common
7990 libggadget-qt-
1.0-
0b
7995 libkonqsidebarplugin4a
8004 libplasma-geolocation-interface4
8006 libplasmagenericshell4
8020 libsmokeknewstuff2-
3
8021 libsmokeknewstuff3-
3
8023 libsmokektexteditor3
8031 libsmokeqtnetwork4-
3
8037 libsmokeqtuitools4-
3
8049 plasma-dataengines-addons
8050 plasma-scriptengine-superkaramba
8051 plasma-widget-lancelot
8052 plasma-widgets-addons
8053 plasma-widgets-workspace
8057 update-notifier-common
8058 </p
></blockquote
>
8060 <p
>Running apt-get autoremove made the results using apt-get and
8061 aptitude a bit more similar, but there are still quite a lott of
8062 differences. I have no idea what packages should be installed after
8063 the upgrade, but hope those that do can have a look.
</p
>
8068 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8069 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8070 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8071 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8072 <description><p
>Most of the computers in use by the
8073 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8074 are virtual machines. And they have been Xen machines running on a
8075 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8076 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8077 bit harder that it could have been, because we set up the Xen virtual
8078 machines to get the virtual partitions from LVM, which as far as I
8079 know is not supported by KVM. So to migrate, we had to convert
8080 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8083 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8084 nice recipe
</a
> to do this, and wrote the following script to do the
8085 migration. It uses qemu-img from the qemu package to make the disk
8086 image, parted to partition it, losetup and kpartx to present the disk
8087 image partions as devices, and dd to copy the data. I NFS mounted the
8088 new servers storage area on the old server to do the migration.
</p
>
8094 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8099 if [ -z
"$
1" ] ; then
8100 echo
"Usage: $
0 &lt;hostname
&gt;
"
8106 if [ ! -e /dev/vg_data/$host-disk ] ; then
8107 echo
"error: unable to find LVM volume for $host
"
8111 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8112 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8113 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8114 totalsize=$(( ( $disksize + $swapsize ) ))
8117 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8118 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8120 parted $img mklabel msdos
8121 parted $img mkpart primary linux-swap
0 $disksize
8122 parted $img mkpart primary ext2 $disksize $totalsize
8123 parted $img set
1 boot on
8126 losetup /dev/loop0 $img
8127 kpartx -a /dev/loop0
8129 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8130 fsck.ext3 -f /dev/mapper/loop0p1 || true
8131 mkswap /dev/mapper/loop0p2
8133 kpartx -d /dev/loop0
8134 losetup -d /dev/loop0
8137 <p
>The script is perhaps so simple that it is not copyrightable, but
8138 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8140 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8141 the new disk image attached, installed grub-pc and linux-image-
686 and
8142 set up grub to boot from the disk image. After this, the KVM machines
8143 seem to work just fine.
</p
>
8148 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8149 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8150 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8151 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8152 <description><p
>I
'm still running upgrade testing of the
8153 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8154 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8155 status. Here is a short update based on a test I ran
20101118.
</p
>
8157 <p
>I still do not know what a correct migration should look like, so I
8158 report any differences between apt and aptitude and hope someone else
8159 can see if anything should be changed.
</p
>
8161 <p
>This is for Gnome:
</p
>
8163 <p
>Installed using apt-get, missing with aptitude
</p
>
8165 <blockquote
><p
>
8166 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8167 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8168 dmz-cursor-theme empathy empathy-common finger
8169 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8170 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8171 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8172 gnome-cards-data gnome-codec-install gnome-core
8173 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8174 gnome-search-tool gnome-session-canberra gnome-spell
8175 gnome-system-log gnome-themes-extras gnome-themes-more
8176 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8177 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8178 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8179 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8180 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8181 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8182 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8183 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8184 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8185 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8186 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8187 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8188 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8189 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8190 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8191 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8192 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8193 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8194 libmono-security2.0-cil libmono-sharpzip2.84-cil
8195 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8196 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8197 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8198 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8199 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8200 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8201 libxalan2-java libxerces2-java media-player-info mesa-utils
8202 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8203 nautilus-sendto-empathy openoffice.org-writer2latex
8204 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8205 python-aptdaemon python-aptdaemon-gtk python-axiom
8206 python-beautifulsoup python-bugbuddy python-clientform
8207 python-coherence python-configobj python-crypto python-cupshelpers
8208 python-cupsutils python-eggtrayicon python-elementtree
8209 python-epsilon python-evolution python-feedparser python-gdata
8210 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8211 python-gtksourceview2 python-httplib2 python-louie python-mako
8212 python-markupsafe python-mechanize python-nevow python-notify
8213 python-opengl python-openssl python-pam python-pkg-resources
8214 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8215 python-tagpy python-twisted-bin python-twisted-conch
8216 python-twisted-core python-twisted-web python-utidylib python-webkit
8217 python-xdg python-zope.interface remmina remmina-plugin-data
8218 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8219 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8220 software-center svgalibg1 system-config-printer-udev
8221 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8222 totem totem-coherence totem-mozilla totem-plugins
8223 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8225 </p
></blockquote
>
8227 Installed using apt-get, removed with aptitude
8229 <blockquote
><p
>
8230 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8231 epiphany-extensions epiphany-gecko evolution-exchange
8232 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8233 gedit-common gnome-app-install gnome-games gnome-games-data
8234 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8235 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8236 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8237 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8238 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8239 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8240 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8241 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8242 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8243 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8244 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8245 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8246 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8247 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8248 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8249 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8250 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8251 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8252 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8253 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8254 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8255 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8256 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8257 sound-juicer swfdec-gnome system-config-printer totem-common
8258 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8259 </p
></blockquote
>
8261 <p
>Installed using aptitude, missing with apt-get
</p
>
8263 <blockquote
><p
>
8264 gstreamer0.10-gnomevfs
8265 </p
></blockquote
>
8267 <p
>Installed using aptitude, removed with apt-get
</p
>
8269 <blockquote
><p
>
8271 </p
></blockquote
>
8273 <p
>This is for KDE:
</p
>
8275 <p
>Installed using apt-get, missing with aptitude
</p
>
8277 <blockquote
><p
>
8278 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8279 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8280 ghostscript-x git gnome-audio gnugo granatier gs-common
8281 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8282 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8283 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8284 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8285 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8286 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8287 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8288 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8289 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8290 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8291 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8292 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8293 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8294 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8295 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8296 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8297 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8298 libkrossui4 libmailtools-perl libmime-tools-perl
8299 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8300 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8301 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8302 lirc luatex marble networkstatus noatun-plugins
8303 openoffice.org-writer2latex palapeli palapeli-data parley
8304 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8305 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8306 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8308 </p
></blockquote
>
8310 <p
>Installed using apt-get, removed with aptitude
</p
>
8312 <blockquote
><p
>
8313 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8314 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8315 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8316 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8317 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8318 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8319 kitchensync kiten kjumpingcube klatin klettres klickety klines
8320 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8321 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8322 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8323 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8324 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8325 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8326 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8327 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8328 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8329 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8330 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8331 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8332 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8333 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8334 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8335 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8336 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8337 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8338 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8339 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8340 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8341 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8342 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8343 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8344 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8345 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8346 </p
></blockquote
>
8348 <p
>Installed using aptitude, missing with apt-get
</p
>
8350 <blockquote
><p
>
8351 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8352 kdeartwork kdebase kdebase-apps kdebase-workspace
8353 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8354 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8355 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8356 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8357 xscreensaver-screensaver-bsod
8358 </p
></blockquote
>
8360 <p
>Installed using aptitude, removed with apt-get
</p
>
8362 <blockquote
><p
>
8363 kdebase-bin konq-plugins konqueror
8364 </p
></blockquote
>
8369 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8370 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8371 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8372 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8373 <description><p
>Answering
8374 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8375 call from the Gnash project
</a
> for
8376 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8377 current source, I have set up a virtual KVM machine on the Debian
8378 Edu/Skolelinux virtualization host to test the git source on
8379 Debian/Squeeze. I hope this can help the developers in getting new
8380 releases out more often.
</p
>
8382 <p
>As the developers want less main-stream build platforms tested to,
8383 I have considered setting up a
<a
8384 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8385 machine as well. I have also considered using the kfreebsd
8386 architecture in Debian as a file server in NUUG to get access to the
5
8387 TB zfs volume we currently use to store DV video. Because of this, I
8388 finally got around to do a test installation of Debian/Squeeze with
8389 kfreebsd. Installation went fairly smooth, thought I noticed some
8390 visual glitches in the cdebconf dialogs (black cursor left on the
8391 screen at random locations). Have not gotten very far with the
8392 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8393 fatal problem. Have to spend some more time on it to see if it is
8394 useful as a file server for NUUG. Will try to find time to set up a
8395 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8400 <title>Debian in
3D
</title>
8401 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8402 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8403 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8404 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8406 <p
>3D printing is just great. I just came across this Debian logo in
8408 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8409 thingiverse blog
</a
>.
</p
>
8414 <title>Software updates
2010-
10-
24</title>
8415 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8416 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8417 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8418 <description><p
>Some updates.
</p
>
8420 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8421 raise money for the project is going well. The lower limit of
10
8422 signers was reached in
24 hours, and so far
13 people have signed it.
8423 More signers and more funding is most welcome, and I am really curious
8424 how far we can get before the time limit of December
24 is reached.
8427 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8428 about what appear to be a great code coverage tool capable of
8429 generating code coverage stats without any changes to the source code.
8431 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8432 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8433 It is missing in Debian, but the git source built just fine in Squeeze
8434 after I installed libelf-dev, libdwarf-dev, pkg-config and
8435 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8436 solvable. I hope kcov make it into Debian soon.
</p
>
8438 <p
>Finally found time to wrap up the release notes for
<a
8439 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8440 new alpha release of Debian Edu
</a
>, and just published the second
8441 alpha test release of the Squeeze based Debian Edu /
8442 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8443 release. Give it a try if you need a complete linux solution for your
8444 school, including central infrastructure server, workstations, thin
8445 client servers and diskless workstations. A nice touch added
8446 yesterday is RDP support on the thin client servers, for windows
8447 clients to get a Linux desktop on request.
</p
>
8452 <title>Some notes on Flash in Debian and Debian Edu
</title>
8453 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8454 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8455 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8456 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8457 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8458 second most popular used package that is missing in Debian. The sixth
8459 most popular is flashplayer-mozilla. This is a clear indication that
8460 working flash is important for Debian users. Around
10 percent of the
8461 users submitting data to popcon.debian.org have this package
8462 installed.
</p
>
8464 <p
>In the report written by Lars Risan in August
2008
8465 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8466 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8467 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8468 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8469 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8470 web sites require Flash to work, and lacking working Flash support in
8471 the web browser and the problems with installing it was perceived as a
8472 good reason to stay with Windows.
</p
>
8474 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8475 said to be the retarded cousin that did not really understand
8476 everything you told him but could work fairly well. This was a
8477 comment regarding the problems Linux have with proprietary formats and
8478 non-standard web pages, and is sad because it exposes a fairly common
8479 understanding of whose fault it is if web pages that only work in for
8480 example Internet Explorer
6 fail to work on Firefox, and funny because
8481 it explain very well how annoying it is for users when Linux
8482 distributions do not work with the documents they receive or the web
8483 pages they want to visit.
</p
>
8485 <p
>This is part of the reason why I believe it is important for Debian
8486 and Debian Edu to have a well working Flash implementation in the
8487 distribution, to get at least popular sites as Youtube and Google
8488 Video to working out of the box. For Squeeze, Debian have the chance
8489 to include the latest version of Gnash that will make this happen, as
8490 the new release
0.8.8 was published a few weeks ago and is resting in
8491 unstable. The new version work with more sites that version
0.8.7.
8492 The Gnash maintainers have asked for a freeze exception, but the
8493 release team have not had time to reply to it yet. I hope they agree
8494 with me that Flash is important for the Debian desktop users, and thus
8495 accept the new package into Squeeze.
</p
>
8500 <title>Circular package dependencies harms apt recovery
</title>
8501 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8502 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8503 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8504 <description><p
>I discovered this while doing
8505 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8506 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8507 in Debian still got circular dependencies, and it is often claimed
8508 that apt and aptitude should be able to handle this just fine, but
8509 some times these dependency loops causes apt to fail.
</p
>
8511 <p
>An example is from todays
8512 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8513 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8514 causes perl-modules to fail to upgrade. The cause is simple. If a
8515 package fail to unpack, then only part of packages with the circular
8516 dependency might end up being unpacked when unpacking aborts, and the
8517 ones already unpacked will fail to configure in the recovery phase
8518 because its dependencies are unavailable.
</p
>
8520 <p
>In this log, the problem manifest itself with this error:
</p
>
8522 <blockquote
><pre
>
8523 dpkg: dependency problems prevent configuration of perl-modules:
8524 perl-modules depends on perl (
>=
5.10.1-
1); however:
8525 Version of perl on system is
5.10.0-
19lenny
2.
8526 dpkg: error processing perl-modules (--configure):
8527 dependency problems - leaving unconfigured
8528 </pre
></blockquote
>
8530 <p
>The perl/perl-modules circular dependency is already
8531 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8532 hopefully be solved as soon as possible, but it is not the only one,
8533 and each one of these loops in the dependency tree can cause similar
8534 failures. Of course, they only occur when there are bugs in other
8535 packages causing the unpacking to fail, but it is rather nasty when
8536 the failure of one package causes the problem to become worse because
8537 of dependency loops.
</p
>
8540 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8541 tireless effort by Bill Allombert
</a
>, the number of circular
8543 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8544 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8546 <p
>Todays testing also exposed a bug in
8547 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8548 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8549 apt-get and aptitude, the latter possibly caused by some circular
8550 dependency. Reported both to BTS to try to get someone to look at
8556 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8557 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8558 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8559 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8560 <description><p
>This is a
8561 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8563 <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
8565 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8566 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8568 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8569 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8570 and dhcp3-server-ldap in Debian use the LDAP server. The two
8571 implementations are quite different in how they use LDAP.
</p
>
8573 To get this information, I started slapd with debugging enabled and
8574 dumped the debug output to a file to get the LDAP searches performed
8575 on a Debian Edu main-server. Here is a summary.
8577 <p
><strong
>powerdns
</strong
></p
>
8579 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8580 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8583 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8584 One
"strict
" mode where the forward and reverse DNS lookups are done
8585 using the same LDAP objects, and a
"tree
" mode where the forward and
8586 reverse entries are in two different subtrees in LDAP with a structure
8587 based on the DNS names, as in tjener.intern and
8588 2.2.0.10.in-addr.arpa.
</p
>
8590 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8591 base, and uses a
"base
" scoped search for the DNS name by adding
8592 "dc=tjener,dc=intern,
" to the base with a filter for
8593 "(associateddomain=tjener.intern)
" for the forward entry and
8594 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8595 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8596 forward entries, it is looking for attributes named dnsttl, arecord,
8597 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8598 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8599 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8600 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8601 spfrecord and modifytimestamp. For reverse entries it is looking for
8602 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8603 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8604 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8605 ldapsearch commands could look like this:
</p
>
8607 <blockquote
><pre
>
8608 ldapsearch -h ldap \
8609 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8610 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8611 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8612 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8613 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8614 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8616 ldapsearch -h ldap \
8617 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8618 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8619 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8620 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8621 srvrecord naptrrecord modifytimestamp
8622 </pre
></blockquote
>
8624 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8625 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8626 example LDAP objects used there. In addition to these objects, the
8627 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8628 also exist.
</p
>
8630 <blockquote
><pre
>
8631 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8633 objectclass: dnsdomain
8634 objectclass: domainrelatedobject
8637 associateddomain: tjener.intern
8639 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8641 objectclass: dnsdomain2
8642 objectclass: domainrelatedobject
8644 ptrrecord: tjener.intern
8645 associateddomain:
2.2.0.10.in-addr.arpa
8646 </pre
></blockquote
>
8648 <p
>In strict mode, the server behaves differently. When looking for
8649 forward DNS entries, it is doing a
"subtree
" scoped search with the
8650 same base as in the tree mode for a object with filter
8651 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8652 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8653 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8654 naptrrecord and modifytimestamp. For reverse entires it also do a
8655 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8656 and the requested attributes are associateddomain, dnsttl and
8657 modifytimestamp. In short, in strict mode the objects with ptrrecord
8658 go away, and the arecord attribute in the forward object is used
8661 <p
>The forward and reverse searches can be simulated using ldapsearch
8662 like this:
</p
>
8664 <blockquote
><pre
>
8665 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8666 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8667 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8668 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8669 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8670 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8672 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8673 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8674 </pre
></blockquote
>
8676 <p
>In addition to the forward and reverse searches , there is also a
8677 search for SOA records, which behave similar to the forward and
8678 reverse lookups.
</p
>
8680 <p
>A thing to note with the PowerDNS behaviour is that it do not
8681 specify any objectclass names, and instead look for the attributes it
8682 need to generate a DNS reply. This make it able to work with any
8683 objectclass that provide the needed attributes.
</p
>
8685 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8686 dnsdomain2 schemas. The latter is used for reverse entries like
8687 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8689 <p
>In Debian Edu, we have created DNS objects using the object classes
8690 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8691 attributes) and domainrelatedobject (for associatedDomain). The use
8692 of structural object classes make it impossible to combine these
8693 classes with the object classes used by DHCP.
</p
>
8695 <p
>There are other schemas that could be used too, for example the
8696 dnszone structural object class used by Gosa and bind-sdb for the DNS
8697 attributes combined with the domainrelatedobject object class, but in
8698 this case some unused attributes would have to be included as well
8699 (zonename and relativedomainname).
</p
>
8701 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8702 mode and not use any of the existing objectclasses (dnsdomain,
8703 dnsdomain2 and dnszone) when one want to combine the DNS information
8704 with DHCP information, and instead create a auxiliary object class
8705 defined something like this (using the attributes defined for
8706 dnsdomain and dnsdomain2 or dnszone):
</p
>
8708 <blockquote
><pre
>
8709 objectclass ( some-oid NAME
'dnsDomainAux
'
8712 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8713 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8714 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8715 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8716 A6Record $ DNAMERecord
8718 </pre
></blockquote
>
8720 <p
>This will allow any object to become a DNS entry when combined with
8721 the domainrelatedobject object class, and allow any entity to include
8722 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8723 developers asking for their view on this schema and if they are
8724 interested in providing such schema with PowerDNS, and I hope my
8725 message will be accepted into their mailing list soon.
</p
>
8727 <p
><strong
>ISC dhcp
</strong
></p
>
8729 <p
>The DHCP server searches for specific objectclass and requests all
8730 the object attributes, and then uses the attributes it want. This
8731 make it harder to figure out exactly what attributes are used, but
8732 thanks to the working example in Debian Edu I can at least get an idea
8733 what is needed without having to read the source code.
</p
>
8735 <p
>In the DHCP server configuration, the LDAP base to use and the
8736 search filter to use to locate the correct dhcpServer entity is
8737 stored. These are the relevant entries from
8738 /etc/dhcp3/dhcpd.conf:
</p
>
8740 <blockquote
><pre
>
8741 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8742 ldap-dhcp-server-cn
"dhcp
";
8743 </pre
></blockquote
>
8745 <p
>The DHCP server uses this information to nest all the DHCP
8746 configuration it need. The cn
"dhcp
" is located using the given LDAP
8747 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8748 search result is this entry:
</p
>
8750 <blockquote
><pre
>
8751 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8754 objectClass: dhcpServer
8755 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8756 </pre
></blockquote
>
8758 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8759 subtree with DHCP configuration. The DHCP configuration subtree base
8760 is located using a base scope search with base
"cn=DHCP
8761 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8762 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8763 The search result is this entry:
</p
>
8765 <blockquote
><pre
>
8766 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8769 objectClass: dhcpService
8770 objectClass: dhcpOptions
8771 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8772 dhcpStatements: ddns-update-style none
8773 dhcpStatements: authoritative
8774 dhcpOption: smtp-server code
69 = array of ip-address
8775 dhcpOption: www-server code
72 = array of ip-address
8776 dhcpOption: wpad-url code
252 = text
8777 </pre
></blockquote
>
8779 <p
>Next, the entire subtree is processed, one level at the time. When
8780 all the DHCP configuration is loaded, it is ready to receive requests.
8781 The subtree in Debian Edu contain objects with object classes
8782 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8783 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8784 and information about netmasks, dynamic range etc. Leaving out the
8785 details here because it is not relevant for the focus of my
8786 investigation, which is to see if it is possible to merge dns and dhcp
8787 related computer objects.
</p
>
8789 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8790 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8791 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8792 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8793 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8796 <blockquote
><pre
>
8797 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8800 objectClass: dhcpHost
8801 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8802 dhcpStatements: fixed-address hostname
8803 </pre
></blockquote
>
8805 <p
>There is less flexiblity in the way LDAP searches are done here.
8806 The object classes need to have fixed names, and the configuration
8807 need to be stored in a fairly specific LDAP structure. On the
8808 positive side, the invidiual dhcpHost entires can be anywhere without
8809 the DN pointed to by the dhcpServer entries. The latter should make
8810 it possible to group all host entries in a subtree next to the
8811 configuration entries, and this subtree can also be shared with the
8812 DNS server if the schema proposed above is combined with the dhcpHost
8813 structural object class.
8815 <p
><strong
>Conclusion
</strong
></p
>
8817 <p
>The PowerDNS implementation seem to be very flexible when it come
8818 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8819 come to the the LDAP structure, the
"strict
" mode is very flexible,
8820 allowing DNS objects to be stored anywhere under the base cn specified
8821 in the configuration.
</p
>
8823 <p
>The DHCP implementation on the other hand is very inflexible, both
8824 regarding which LDAP schemas to use and which LDAP structure to use.
8825 I guess one could implement ones own schema, as long as the
8826 objectclasses and attributes have the names used, but this do not
8827 really help when the DHCP subtree need to have a fairly fixed
8828 structure.
</p
>
8830 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8831 this might work for Debian Edu:
</p
>
8833 <blockquote
><pre
>
8835 cn=machine-info (dhcpService) - dhcpServiceDN points here
8836 cn=dhcp (dhcpServer)
8837 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8838 cn=
10.0.2.0 (dhcpSubnet)
8839 cn=group1 (dhcpGroup/dhcpOptions)
8840 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8841 cn=
192.168.0.0 (dhcpSubnet)
8842 cn=group1 (dhcpGroup/dhcpOptions)
8843 ou=machines - PowerDNS base points here
8844 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8845 </pre
></blockquote
>
8847 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8848 entries to be in the dhcpGroup subtrees, the entries can be stored
8849 there instead of a common machines subtree, and the PowerDNS base
8850 would have to be moved one level up to the machine-info subtree.
</p
>
8852 <p
>The combined object under the machines subtree would look something
8853 like this:
</p
>
8855 <blockquote
><pre
>
8856 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8859 objectClass: dhcpHost
8860 objectclass: domainrelatedobject
8861 objectclass: dnsDomainAux
8862 associateddomain: hostname.intern
8863 arecord:
10.11.12.13
8864 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8865 dhcpStatements: fixed-address hostname.intern
8866 </pre
></blockquote
>
8868 </p
>One could even add the LTSP configuration associated with a given
8869 machine, as long as the required attributes are available in a
8870 auxiliary object class.
</p
>
8875 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8876 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8878 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8879 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8880 DHCP services in Debian Edu to use the same LDAP objects for a given
8881 computer, to avoid the possibility of having a inconsistent state for
8882 a computer in LDAP (as in DHCP but no DNS entry or the other way
8883 around) and make it easier to add computers to LDAP.
</p
>
8885 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8886 information finally found a solution that seem to work.
</p
>
8888 <p
>The old setup required three LDAP objects for a given computer.
8889 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8890 we switch powerdns to use its strict LDAP method (ldap-method=strict
8891 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8892 merged into one while making it impossible to transfer the reverse map
8893 to a slave DNS server.
</p
>
8895 <p
>If we also replace the object class used to get the DNS related
8896 attributes to one allowing these attributes to be combined with the
8897 dhcphost object class, we can merge the DNS and DHCP entries into one.
8898 I
've written such object class in the dnsdomainaux.schema file (need
8899 proper OIDs, but that is a minor issue), and tested the setup. It
8900 seem to work.
</p
>
8902 <p
>With this test setup in place, we can get away with one LDAP object
8903 for both DNS and DHCP, and even the LTSP configuration I suggested in
8904 an earlier email. The combined LDAP object will look something like
8907 <blockquote
><pre
>
8908 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8910 objectClass: dhcphost
8911 objectclass: domainrelatedobject
8912 objectclass: dnsdomainaux
8913 associateddomain: hostname.intern
8914 arecord:
10.11.12.13
8915 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8916 dhcpstatements: fixed-address hostname
8918 </pre
></blockquote
>
8920 <p
>The DNS server uses the associateddomain and arecord entries, while
8921 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8922 before asking DNS to resolve the fixed-adddress. LTSP will use
8923 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8925 <p
>I am not yet sure if I can get the DHCP server to look for its
8926 dhcphost in a different location, to allow us to put the objects
8927 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8928 that. If I can
't figure out a way to do that, we can still get rid of
8929 the hosts subtree and move all its content into the DHCP Config tree
8930 (which probably should be renamed to be more related to the new
8931 content. I suspect cn=dnsdhcp,ou=services or something like that
8932 might be a good place to put it.
</p
>
8934 <p
>If you want to help out with implementing this for Debian Edu,
8935 please contact us on debian-edu@lists.debian.org.
</p
>
8940 <title>Idea for storing LTSP configuration in LDAP
</title>
8941 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8942 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8943 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8944 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8945 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8946 clients, and that this can be used to fetch configuration from LDAP if
8947 Debian Edu choose to store configuration there.
</p
>
8949 <p
>Armed with this information, I got inspired and wrote a test module
8950 to get configuration from LDAP. The idea is to look up the MAC
8951 address of the client in LDAP, and look for attributes on the form
8952 ltspconfigsetting=value, and use this to export SETTING=value to the
8953 LTSP clients.
</p
>
8955 <p
>The goal is to be able to store the LTSP configuration attributes
8956 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8957 allowing us to store all information about a computer in one place.
</p
>
8959 <p
>This is a untested draft implementation, and I welcome feedback on
8960 this approach. A real LDAP schema for the ltspClientAux objectclass
8961 need to be written. Comments, suggestions, etc?
</p
>
8963 <blockquote
><pre
>
8964 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8966 # Fetch LTSP client settings from LDAP based on MAC address
8968 # Uses ethernet address as stored in the dhcpHost objectclass using
8969 # the dhcpHWAddress attribute or ethernet address stored in the
8970 # ieee802Device objectclass with the macAddress attribute.
8972 # This module is written to be schema agnostic, and only depend on the
8973 # existence of attribute names.
8975 # The LTSP configuration variables are saved directly using a
8976 # ltspConfig prefix and uppercasing the rest of the attribute name.
8977 # To set the SERVER variable, set the ltspConfigServer attribute.
8979 # Some LDAP schema should be created with all the relevant
8980 # configuration settings. Something like this should work:
8982 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8985 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8987 LDAPSERVER=$(debian-edu-ldapserver)
8988 if [
"$LDAPSERVER
" ] ; then
8989 LDAPBASE=$(debian-edu-ldapserver -b)
8990 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8991 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8992 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8993 grep
'^ltspConfig
' | while read attr value ; do
8994 # Remove prefix and convert to upper case
8995 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8996 # bass value on to clients
8997 eval
"$attr=$value; export $attr
"
9001 </pre
></blockquote
>
9003 <p
>I
'm not sure this shell construction will work, because I suspect
9004 the while block might end up in a subshell causing the variables set
9005 there to not show up in ltsp-config, but if that is the case I am sure
9006 the code can be restructured to make sure the variables are passed on.
9007 I expect that can be solved with some testing. :)
</p
>
9009 <p
>If you want to help out with implementing this for Debian Edu,
9010 please contact us on debian-edu@lists.debian.org.
</p
>
9012 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
9013 configuration in LDAP that was created around year
2000 by
9014 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
9015 Xperience, Inc.,
2000</a
>. I found its
9016 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
9017 personal home page over at redhat.com.
</p
>
9022 <title>jXplorer, a very nice LDAP GUI
</title>
9023 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
9024 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
9025 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
9026 <description><p
>Since
9027 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
9028 last post
</a
> about available LDAP tools in Debian, I was told about a
9029 LDAP GUI that is even better than luma. The java application
9030 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
9031 moving LDAP objects and subtrees using drag-and-drop, and can
9032 authenticate using Kerberos. I have only tested the Kerberos
9033 authentication, but do not have a LDAP setup allowing me to rewrite
9034 LDAP with my test user yet. It is
9035 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
9036 Debian
</a
> testing and unstable at the moment. The only problem I
9037 have with it is how it handle errors. If something go wrong, its
9038 non-intuitive behaviour require me to go through some query work list
9039 and remove the failing query. Nothing big, but very annoying.
</p
>
9044 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
9045 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
9046 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
9047 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
9048 <description><p
>Here is a short update on my
<a
9049 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
9050 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
9051 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
9052 not reporting the status for KDE, because the upgrade crashes when
9053 aptitude try because of missing conflicts
9054 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
9055 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
9057 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
9058 complete list of the installed packages. Based on this I see these
9059 differences when I did a test run today. As usual, I do not really
9060 know what the correct set of packages would be, but thought it best to
9061 publish the difference.
</p
>
9063 <p
>Installed using apt-get, missing with aptitude
</p
>
9065 <blockquote
><p
>
9066 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9067 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9068 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9069 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9070 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9071 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9072 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9073 python-gtkmozembed svgalibg1 xserver-xephyr zip
9074 </p
></blockquote
>
9076 <p
>Installed using apt-get, removed with aptitude
</p
>
9078 <blockquote
><p
>
9079 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9080 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9081 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9082 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9083 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9084 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9085 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9086 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9087 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9088 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9089 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9090 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9091 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9092 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9093 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9094 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9095 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9096 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9097 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9098 mysql-common swfdec-gnome totem-gstreamer wodim
9099 </p
></blockquote
>
9101 <p
>Installed using aptitude, missing with apt-get
</p
>
9103 <blockquote
><p
>
9104 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9105 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9106 xserver-xorg-input-all xserver-xorg-input-evdev
9107 xserver-xorg-input-kbd xserver-xorg-input-mouse
9108 xserver-xorg-input-synaptics xserver-xorg-video-all
9109 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9110 xserver-xorg-video-chips xserver-xorg-video-cirrus
9111 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9112 xserver-xorg-video-glint xserver-xorg-video-i128
9113 xserver-xorg-video-i740 xserver-xorg-video-mach64
9114 xserver-xorg-video-mga xserver-xorg-video-neomagic
9115 xserver-xorg-video-nouveau xserver-xorg-video-nv
9116 xserver-xorg-video-r128 xserver-xorg-video-radeon
9117 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9118 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9119 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9120 xserver-xorg-video-sis xserver-xorg-video-sisusb
9121 xserver-xorg-video-tdfx xserver-xorg-video-tga
9122 xserver-xorg-video-trident xserver-xorg-video-tseng
9123 xserver-xorg-video-vesa xserver-xorg-video-vmware
9124 xserver-xorg-video-voodoo
9125 </p
></blockquote
>
9127 <p
>Installed using aptitude, removed with apt-get
</p
>
9129 <blockquote
><p
>
9130 deskbar-applet xserver-xorg xserver-xorg-core
9131 xserver-xorg-input-wacom xserver-xorg-video-intel
9132 xserver-xorg-video-openchrome
9133 </p
></blockquote
>
9135 <p
>I was told on IRC that the xorg-xserver package was
9136 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9137 in git
</a
> today to try to get apt-get to not remove xorg completely.
9138 No idea when it hits Squeeze, but when it does I hope it will reduce
9139 the difference somewhat.
9144 <title>LUMA, a very nice LDAP GUI
</title>
9145 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9146 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9147 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9148 <description><p
>The last few days I have been looking into the status of the LDAP
9149 directory in Debian Edu, and in the process I started to miss a GUI
9150 tool to browse the LDAP tree. The only one I was able to find in
9151 Debian/Squeeze and Lenny is
9152 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9153 be a great tool to get a overview of the current LDAP directory
9154 populated by default in Skolelinux. Thanks to it, I have been able to
9155 find empty and obsolete subtrees, misplaced objects and duplicate
9156 objects. It will be installed by default in Debian/Squeeze. If you
9157 are working with LDAP, give it a go. :)
</p
>
9159 <p
>I did notice one problem with it I have not had time to report to
9160 the BTS yet. There is no .desktop file in the package, so the tool do
9161 not show up in the Gnome and KDE menus, but only deep down in in the
9162 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9165 <p
>I have not yet been able to get it to modify the tree yet. I would
9166 like to move objects and remove subtrees directly in the GUI, but have
9167 not found a way to do that with LUMA yet. So in the mean time, I use
9168 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9170 <p
>If you have tips on other GUI tools for LDAP that might be useful
9171 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9173 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9174 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9175 useful GUI alternative. It seem like a good tool, but is unmaintained
9176 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9177 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9182 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9183 <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>
9184 <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>
9185 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9186 <description><p
>A while back, I
9187 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9188 about the fact
</a
> that it is not possible with the provided schemas
9189 for storing DNS and DHCP information in LDAP to combine the two sets
9190 of information into one LDAP object representing a computer.
</p
>
9192 <p
>In the mean time, I discovered that a simple fix would be to make
9193 the dhcpHost object class auxiliary, to allow it to be combined with
9194 the dNSDomain object class, and thus forming one object for one
9195 computer when storing both DHCP and DNS information in LDAP.
</p
>
9197 <p
>If I understand this correctly, it is not safe to do this change
9198 without also changing the assigned number for the object class, and I
9199 do not know enough about LDAP schema design to do that properly for
9200 Debian Edu.
</p
>
9202 <p
>Anyway, for future reference, this is how I believe we could change
9204 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9205 schema
</a
> to solve at least part of the problem with the LDAP schemas
9206 available today from IETF.
</p
>
9209 --- dhcp.schema (revision
65192)
9210 +++ dhcp.schema (working copy)
9212 objectclass (
2.16.840.1.113719.1.203.6.6
9213 NAME
'dhcpHost
'
9214 DESC
'This represents information about a particular client
'
9218 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9219 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9222 <p
>I very much welcome clues on how to do this properly for Debian
9223 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9224 package, and should thus be free to rewrite it as we see fit.
</p
>
9226 <p
>If you want to help out with implementing this for Debian Edu,
9227 please contact us on debian-edu@lists.debian.org.
</p
>
9232 <title>Calling tasksel like the installer, while still getting useful output
</title>
9233 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9234 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9235 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9236 <description><p
>A few times I have had the need to simulate the way tasksel
9237 installs packages during the normal debian-installer run. Until now,
9238 I have ended up letting tasksel do the work, with the annoying problem
9239 of not getting any feedback at all when something fails (like a
9240 conffile question from dpkg or a download that fails), using code like
9243 <blockquote
><pre
>
9244 export DEBIAN_FRONTEND=noninteractive
9245 tasksel --new-install
9246 </pre
></blockquote
>
9248 This would invoke tasksel, let its automatic task selection pick the
9249 tasks to install, and continue to install the requested tasks without
9250 any output what so ever.
9252 Recently I revisited this problem while working on the automatic
9253 package upgrade testing, because tasksel would some times hang without
9254 any useful feedback, and I want to see what is going on when it
9255 happen. Then it occured to me, I can parse the output from tasksel
9256 when asked to run in test mode, and use that aptitude command line
9257 printed by tasksel then to simulate the tasksel run. I ended up using
9260 <blockquote
><pre
>
9261 export DEBIAN_FRONTEND=noninteractive
9262 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9264 </pre
></blockquote
>
9266 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9267 --without-recommends -o APT::Install-Recommends=no -y install
9268 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9269 ~pimportant
</tt
>", which will install the gnome desktop task, the
9270 laptop task and all packages with priority standard , required and
9271 important, just like tasksel would have done it during
9272 installation.
</p
>
9274 <p
>A better approach is probably to extend tasksel to be able to
9275 install packages without using debconf-apt-progress, for use cases
9276 like this.
</p
>
9281 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9282 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9283 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9284 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9285 <description><p
>My
9286 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9287 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9288 finally made the upgrade logs available from
9289 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9290 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9291 apt and aptitude, and found their differences interesting. This time
9292 I will only focus on their removal plans.
</p
>
9294 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9295 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9296 surprising part is that it want to remove xorg and all
9297 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9298 sure why. When asking aptitude to do the same, it want to remove
129
9299 packages, but most of them are library packages I suspect are no
9300 longer needed. Both of them want to remove bluetooth packages, which
9301 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9303 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9304 which seem like a bad idea and xorg the same way as with Gnome. Asking
9305 aptitude for the same, it wants to remove
192 packages, none which are
9306 too surprising.
</p
>
9308 <p
>I guess the removal of xorg during upgrades should be investigated
9309 and avoided, and perhaps others as well. Here are the complete list
9310 of planned removals. The complete logs is available from the URL
9311 above. Note if you want to repeat these tests, that the upgrade test
9312 for kde+apt-get hung in the tasksel setup because of dpkg asking
9313 conffile questions. No idea why. I worked around it by using
9314 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9317 <p
><b
>apt-get gnome
72</b
>
9318 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9319 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9320 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9321 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9322 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9323 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9324 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9325 xserver-xorg-input-kbd xserver-xorg-input-mouse
9326 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9327 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9328 xserver-xorg-video-ati xserver-xorg-video-chips
9329 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9330 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9331 xserver-xorg-video-glint xserver-xorg-video-i128
9332 xserver-xorg-video-i740 xserver-xorg-video-imstt
9333 xserver-xorg-video-intel xserver-xorg-video-mach64
9334 xserver-xorg-video-mga xserver-xorg-video-neomagic
9335 xserver-xorg-video-nsc xserver-xorg-video-nv
9336 xserver-xorg-video-openchrome xserver-xorg-video-r128
9337 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9338 xserver-xorg-video-rendition xserver-xorg-video-s3
9339 xserver-xorg-video-s3virge xserver-xorg-video-savage
9340 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9341 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9342 xserver-xorg-video-tga xserver-xorg-video-trident
9343 xserver-xorg-video-tseng xserver-xorg-video-v4l
9344 xserver-xorg-video-vesa xserver-xorg-video-vga
9345 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9346 xulrunner-
1.9-gnome-support
</p
>
9348 <p
><b
>aptitude gnome
129</b
>
9350 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9351 djvulibre-desktop finger gnome-app-install gnome-mount
9352 gnome-network-admin gnome-spell gnome-vfs-obexftp
9353 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9354 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9355 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9356 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9357 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9358 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9359 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9360 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9361 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9362 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9363 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9364 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9365 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9366 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9367 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9368 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9369 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9370 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9371 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9372 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9373 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9374 openoffice.org-writer2latex openssl-blacklist p7zip
9375 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9376 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9377 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9378 swfdec-mozilla totem-gstreamer update-manager wodim
9379 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9380 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9383 <p
><b
>apt-get kde
82</b
>
9385 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9386 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9387 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9388 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9389 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9390 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9391 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9392 xserver-xorg-input-kbd xserver-xorg-input-mouse
9393 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9394 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9395 xserver-xorg-video-ati xserver-xorg-video-chips
9396 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9397 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9398 xserver-xorg-video-glint xserver-xorg-video-i128
9399 xserver-xorg-video-i740 xserver-xorg-video-imstt
9400 xserver-xorg-video-intel xserver-xorg-video-mach64
9401 xserver-xorg-video-mga xserver-xorg-video-neomagic
9402 xserver-xorg-video-nsc xserver-xorg-video-nv
9403 xserver-xorg-video-openchrome xserver-xorg-video-r128
9404 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9405 xserver-xorg-video-rendition xserver-xorg-video-s3
9406 xserver-xorg-video-s3virge xserver-xorg-video-savage
9407 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9408 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9409 xserver-xorg-video-tga xserver-xorg-video-trident
9410 xserver-xorg-video-tseng xserver-xorg-video-v4l
9411 xserver-xorg-video-vesa xserver-xorg-video-vga
9412 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9414 <p
><b
>aptitude kde
192</b
>
9415 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9416 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9417 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9418 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9419 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9420 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9421 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9422 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9423 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9424 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9425 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9426 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9427 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9428 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9429 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9430 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9431 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9432 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9433 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9434 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9435 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9436 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9437 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9438 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9439 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9440 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9441 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9442 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9443 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9444 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9445 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9446 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9447 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9448 texlive-common texlive-doc-base texlive-fonts-recommended
9449 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9450 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9451 xulrunner-
1.9</p
>
9457 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9458 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9459 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9460 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9461 <description><p
>The last few days I have done some upgrade testing in Debian, to
9462 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9463 have been discovered and reported in the process
9464 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9465 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9466 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9467 kdebase-workspace-data), and to get a more regular testing going on, I
9468 am working on a script to automate the test.
</p
>
9470 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9471 Gnome or KDE desktop installation inside the chroot before upgrading
9472 it. To ensure no services are started in the chroot, a policy-rc.d
9473 script is inserted. To make sure tasksel believe it is to install a
9474 desktop on a laptop, the tasksel tests are replaced in the chroot
9475 (only acceptable because this is a throw-away chroot).
</p
>
9477 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9478 currently always fail because udev refuses to upgrade with the kernel
9479 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9480 is created. The bug report
9481 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9482 this problem do not trigger in a chroot, but I touch the file anyway
9483 to make sure the upgrade go well. Testing on virtual and real
9484 hardware have failed me because of udev so far, and creating this file
9485 do the trick in such settings anyway. This is a
9486 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9487 issue
</a
> and the current udev behaviour is intended by the udev
9488 maintainer because he lack the resources to rewrite udev to keep
9489 working with old kernels or something like that. I really wish the
9490 udev upstream would keep udev backwards compatible, to avoid such
9491 upgrade problem, but given that they fail to do so, I guess
9492 documenting the way out of this mess is the best option we got for
9493 Debian Squeeze.
</p
>
9495 <p
>Anyway, back to the task at hand, testing upgrades. This test
9496 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9499 <blockquote
><pre
>
9503 if [
"$
1" ] ; then
9512 exec
&lt; /dev/null
9514 mirror=http://ftp.skolelinux.org/debian
9515 tmpdir=chroot-$from-upgrade-$to-$desktop
9517 debootstrap $from $tmpdir $mirror
9518 chroot $tmpdir aptitude update
9519 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9523 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9527 mount -t proc proc $tmpdir/proc
9528 # Make sure proc is unmounted also on failure
9529 trap exit_cleanup EXIT INT
9531 chroot $tmpdir aptitude -y install debconf-utils
9533 # Make sure tasksel autoselection trigger. It need the test scripts
9534 # to return the correct answers.
9535 echo tasksel tasksel/desktop multiselect $desktop | \
9536 chroot $tmpdir debconf-set-selections
9538 # Include the desktop and laptop task
9539 for test in desktop laptop ; do
9540 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9544 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9547 DEBIAN_FRONTEND=noninteractive
9548 DEBIAN_PRIORITY=critical
9549 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9550 chroot $tmpdir tasksel --new-install
9552 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9553 chroot $tmpdir aptitude update
9554 touch $tmpdir/etc/udev/kernel-upgrade
9555 chroot $tmpdir aptitude -y dist-upgrade
9557 </pre
></blockquote
>
9559 <p
>I suspect it would be useful to test upgrades with both apt-get and
9560 with aptitude, but I have not had time to look at how they behave
9561 differently so far. I hope to get a cron job running to do the test
9562 regularly and post the result on the web. The Gnome upgrade currently
9563 work, while the KDE upgrade fail because of the bug in
9564 kdebase-workspace-data
</p
>
9566 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9567 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9568 post, so I will refrain from trying. I can report that for Gnome,
9569 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9570 remove and
1 not upgraded and
1024MB need to be downloaded while for
9571 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9572 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9574 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9575 is able to migrate to dependency based boot sequencing and parallel
9576 booting without a hitch. Was unsure if there were still bugs with
9577 packages failing to clean up their obsolete init.d script during
9578 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9584 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9585 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9586 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9587 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9588 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9589 scripts to migrate (some of) their operations to upstart job while
9590 keeping the init.d for hurd and kfreebsd. The packages with such
9591 needs will need a way to get their init.d scripts to behave
9592 differently when used with sysvinit and with upstart. Because of
9593 this, I had a look at the environment variables set when a init.d
9594 script is running under upstart, and when it is not.
</p
>
9596 <p
>With upstart, I notice these environment variables are set when a
9597 script is started from rcS.d/ (ignoring some irrelevant ones like
9600 <blockquote
><pre
>
9606 UPSTART_EVENTS=startup
9608 UPSTART_JOB=rc-sysinit
9609 </pre
></blockquote
>
9611 <p
>With sysvinit, these environment variables are set for the same
9614 <blockquote
><pre
>
9615 INIT_VERSION=sysvinit-
2.88
9620 </pre
></blockquote
>
9622 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9623 sysvinit are not set by upstart. Not sure if it is intentional or not
9624 to not be compatible with sysvinit in this regard.
</p
>
9626 <p
>For scripts needing to behave differently when upstart is used,
9627 looking for the UPSTART_JOB environment variable seem to be a good
9633 <title>A manual for standards wars...
</title>
9634 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9636 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9637 <description><p
>Via the
9638 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9639 of Rob Weir
</a
> I came across the very interesting essay named
9640 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9641 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9642 following the standards wars of today.
</p
>
9647 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9648 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9649 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9650 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9651 <description><p
>When using sitesummary at a site to track machines, it is possible
9652 to get a list of the machine types in use thanks to the DMI
9653 information extracted from each machine. The script to do so is
9654 included in the sitesummary package, and here is example output from
9655 the Skolelinux build servers:
</p
>
9657 <blockquote
><pre
>
9658 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9660 Dell Computer Corporation
1
9663 eserver xSeries
345 -[
8670M1X]-
1
9667 </pre
></blockquote
>
9669 <p
>The quality of the report depend on the quality of the DMI tables
9670 provided in each machine. Here there are Intel machines without model
9671 information listed with Intel as vendor and no model, and virtual Xen
9672 machines listed as [no-dmi-info]. One can add -l as a command line
9673 option to list the individual machines.
</p
>
9675 <p
>A larger list is
9676 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9677 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9678 provide the basic sitesummary report publicly. In their report there
9679 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9680 their machines, and as sitesummary is available in both distributions,
9681 it is trivial to get all of them to report to the same central
9682 collector.
</p
>
9687 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9688 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9689 <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>
9690 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9691 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9692 start at boot when an NVidia video card is used is handled. The
9693 problem seem to be that the nvidia X.org driver uses a long time to
9694 initialize, and this duration is longer than kdm is configured to
9697 <p
>I came across two bugs related to this issue,
9698 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9699 against initscripts and passed on to nvidia-glx when it became obvious
9700 that the nvidia drivers were involved, and
9701 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9702 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9704 <p
>To me, it seem that no-one is interested in actually solving the
9705 problem nvidia video card owners experience and make sure the Debian
9706 distribution work out of the box for these users. The nvidia driver
9707 maintainers expect kdm to be set up to wait longer, while kdm expect
9708 the nvidia driver maintainers to fix the driver to start faster, and
9709 while they wait for each other I guess the users end up switching to a
9710 distribution that work for them. I have no idea what the solution is,
9711 but I am pretty sure that waiting for each other is not it.
</p
>
9713 <p
>I wonder why we end up handling bugs this way.
</p
>
9718 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9719 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9720 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9721 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9722 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9723 The feature seem to hold up pretty well, but three fairly serious
9724 issues are known and should be solved:
9728 <li
>The wicd package seen to
9729 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9730 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9731 parallel booting is enabled. No idea why, but the wicd maintainer
9732 seem to be on the case.
</li
>
9734 <li
>The nvidia X driver seem to
9735 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9736 triggered more easily when parallel booting is in effect. The
9737 maintainer is on the case.
</li
>
9739 <li
>The sysv-rc package fail to properly enable dependency based boot
9740 sequencing (the shutdown is broken) when old file-rc users
9741 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9742 sysv-rc. One way to solve it would be for file-rc to create
9743 /etc/init.d/.legacy-bootordering, and another is to try to make
9744 sysv-rc more robust. Will investigate some more and probably upload a
9745 workaround in sysv-rc to help those trying to move from file-rc to
9746 sysv-rc get a working shutdown.
</li
>
9748 </ul
></p
>
9750 <p
>All in all not many surprising issues, and all of them seem
9751 solvable before Squeeze is released. In addition to these there are
9752 some packages with bugs in their dependencies and run level settings,
9753 which I expect will be fixed in a reasonable time span.
</p
>
9755 <p
>If you report any problems with dependencies in init.d scripts to
9756 the BTS, please usertag the report to get it to show up at
9757 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9758 list of usertagged bugs related to this
</a
>.
</p
>
9760 <p
>Update: Correct bug number to file-rc issue.
</p
>
9765 <title>More flexible firmware handling in debian-installer
</title>
9766 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9767 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9768 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9769 <description><p
>After a long break from debian-installer development, I finally
9770 found time today to return to the project. Having to spend less time
9771 working dependency based boot in debian, as it is almost complete now,
9772 definitely helped freeing some time.
</p
>
9774 <p
>A while back, I ran into a problem while working on Debian Edu. We
9775 include some firmware packages on the Debian Edu CDs, those needed to
9776 get disk and network controllers working. Without having these
9777 firmware packages available during installation, it is impossible to
9778 install Debian Edu on the given machine, and because our target group
9779 are non-technical people, asking them to provide firmware packages on
9780 an external medium is a support pain. Initially, I expected it to be
9781 enough to include the firmware packages on the CD to get
9782 debian-installer to find and use them. This proved to be wrong.
9783 Next, I hoped it was enough to symlink the relevant firmware packages
9784 to some useful location on the CD (tried /cdrom/ and
9785 /cdrom/firmware/). This also proved to not work, and at this point I
9786 found time to look at the debian-installer code to figure out what was
9787 going to work.
</p
>
9789 <p
>The firmware loading code is in the hw-detect package, and a closer
9790 look revealed that it would only look for firmware packages outside
9791 the installation media, so the CD was never checked for firmware
9792 packages. It would only check USB sticks, floppies and other
9793 "external
" media devices. Today I changed it to also look in the
9794 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9795 solve the problem I ran into with Debian edu. I also changed it to
9796 look in /firmware/, to make sure the installer also find firmware
9797 provided in the initrd when booting the installer via PXE, to allow us
9798 to provide the same feature in the PXE setup included in Debian
9801 <p
>To make sure firmware deb packages with a license questions are not
9802 activated without asking if the license is accepted, I extended
9803 hw-detect to look for preinst scripts in the firmware packages, and
9804 run these before activating the firmware during installation. The
9805 license question is asked using debconf in the preinst, so this should
9806 solve the issue for the firmware packages I have looked at so far.
</p
>
9808 <p
>If you want to discuss the details of these features, please
9809 contact us on debian-boot@lists.debian.org.
</p
>
9814 <title>Parallellized boot is now the default in Debian/unstable
</title>
9815 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9816 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9817 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9818 <description><p
>Since this evening, parallel booting is the default in
9819 Debian/unstable for machines using dependency based boot sequencing.
9820 Apparently the testing of concurrent booting has been wider than
9821 expected, if I am to believe the
9822 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9823 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9824 with the feature this weekend, to give us some time to detect any
9825 remaining problems before Squeeze is frozen. If serious problems are
9826 detected, it is simple to change the default back to sequential boot.
9827 The upload of the new sysvinit package also activate a new upstream
9830 More information about
9831 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9832 based boot sequencing
</a
> is available from the Debian wiki. It is
9833 currently possible to disable parallel booting when one run into
9834 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9836 <blockquote
><pre
>
9838 </pre
></blockquote
>
9840 <p
>If you report any problems with dependencies in init.d scripts to
9841 the BTS, please usertag the report to get it to show up at
9842 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9843 list of usertagged bugs related to this
</a
>.
</p
>
9848 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9849 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9850 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9851 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9852 <description><p
>In the recent Debian Edu versions, the
9853 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9854 system
</a
> is used to keep track of the machines in the school
9855 network. Each machine will automatically report its status to the
9856 central server after boot and once per night. The network setup is
9857 also reported, and using this information it is possible to get the
9858 MAC address of all network interfaces in the machines. This is useful
9859 to update the DHCP configuration.
</p
>
9861 <p
>To give some idea how to use sitesummary, here is a one-liner to
9862 ist all MAC addresses of all machines reporting to sitesummary. Run
9863 this on the collector host:
</p
>
9865 <blockquote
><pre
>
9866 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9867 </pre
></blockquote
>
9869 <p
>This will list all MAC addresses assosiated with all machine, one
9870 line per machine and with space between the MAC addresses.
</p
>
9872 <p
>To allow system administrators easier job at adding static DHCP
9873 addresses for hosts, it would be possible to extend this to fetch
9874 machine information from sitesummary and update the DHCP and DNS
9875 tables in LDAP using this information. Such tool is unfortunately not
9876 written yet.
</p
>
9881 <title>systemd, an interesting alternative to upstart
</title>
9882 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9883 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9884 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9885 <description><p
>The last few days a new boot system called
9886 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9888 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9890 to the free software world. I have not yet had time to play around
9891 with it, but it seem to be a very interesting alternative to
9892 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9893 a good alternative for Debian when we are able to switch to an event
9894 based boot system. Tollef is
9895 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9896 systemd into Debian, and I look forward to seeing how well it work. I
9897 like the fact that systemd handles init.d scripts with dependency
9898 information natively, allowing them to run in parallel where upstart
9899 at the moment do not.
</p
>
9901 <p
>Unfortunately do systemd have the same problem as upstart regarding
9902 platform support. It only work on recent Linux kernels, and also need
9903 some new kernel features enabled to function properly. This means
9904 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9905 system. Not sure how that will be handled if systemd proves to be the
9906 way forward.
</p
>
9908 <p
>In the mean time, based on the
9909 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9910 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9911 decided to enable full parallel booting as the default in Debian as
9912 soon as possible (probably this weekend or early next week), to see if
9913 there are any remaining serious bugs in the init.d dependencies. A
9914 new version of the sysvinit package implementing this change is
9915 already in experimental. If all go well, Squeeze will be released
9916 with parallel booting enabled by default.
</p
>
9921 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9922 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9923 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9924 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9925 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9926 complete, so complete that it is actually possible to run all the
9927 init.d scripts in parallell based on these dependencies. If you want
9928 to test your Squeeze system, make sure
9929 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9930 based boot sequencing
</a
> is enabled, and add this line to
9931 /etc/default/rcS:
</p
>
9933 <blockquote
><pre
>
9934 CONCURRENCY=makefile
9935 </pre
></blockquote
>
9937 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9938 scripts in parallel using the dependency information stored in
9939 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9940 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9941 to try to start the kdm and gdm scripts as early as possible, and will
9942 start the facilities required by kdm or gdm as early as possible to
9943 make this happen.
</p
>
9945 <p
>Give it a try, and see if you like the result. If some services
9946 fail to start properly, it is most likely because they have incomplete
9947 init.d script dependencies in their startup script (or some of their
9948 dependent scripts have incomplete dependencies). Report bugs and get
9949 the package maintainers to fix it. :)
</p
>
9951 <p
>Running scripts in parallel could be the default in Debian when we
9952 manage to get the init.d script dependencies complete and correct. I
9953 expect we will get there in Squeeze+
1, if we get manage to test and
9954 fix the remaining issues.
</p
>
9956 <p
>If you report any problems with dependencies in init.d scripts to
9957 the BTS, please usertag the report to get it to show up at
9958 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9959 list of usertagged bugs related to this
</a
>.
</p
>
9964 <title>Debian has switched to dependency based boot sequencing
</title>
9965 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9966 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9967 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9968 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9969 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9970 have been migrated to using dependency based boot sequencing. This
9971 conclude work me and others have been doing for the last three days.
9972 It feels great to see this finally part of the default Debian
9973 installation. Now we just need to weed out the last few problems that
9974 are bound to show up, to get everything ready for Squeeze.
</p
>
9976 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9977 fixing the more fundamental problem of handing the event based
9978 non-predictable kernel in the early boot.
</p
>
9983 <title>Taking over sysvinit development
</title>
9984 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9985 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9986 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9987 <description><p
>After several years of frustration with the lack of activity from
9988 the existing sysvinit upstream developer, I decided a few weeks ago to
9989 take over the package and become the new upstream. The number of
9990 patches to track for the Debian package was becoming a burden, and the
9991 lack of synchronization between the distribution made it hard to keep
9992 the package up to date.
</p
>
9994 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9995 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9996 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9997 and Fedora), based on the patches currently in use in these
9998 distributions. We Debian maintainers plan to move to this tarball as
9999 the new upstream as soon as we find time to do the merge. Since the
10000 new tarball was created, we agreed with Werner at SuSe to make a new
10001 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
10002 development there. The project is registered and currently waiting
10003 for approval by the Savannah administrators, and as soon as it is
10004 approved, we will import the old versions from svn and continue
10005 working on the future release.
</p
>
10007 <p
>It is a bit ironic that this is done now, when some of the involved
10008 distributions are moving to upstart as a syvinit replacement.
</p
>
10013 <title>Debian boots quicker and quicker
</title>
10014 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
10015 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
10016 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
10017 <description><p
>I spent Monday and tuesday this week in London with a lot of the
10018 people involved in the boot system on Debian and Ubuntu, to see if we
10019 could find more ways to speed up the boot system. This was an Ubuntu
10021 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
10022 gathering
</a
>. It was quite productive. We also discussed the future
10023 of boot systems, and ways to handle the increasing number of boot
10024 issues introduced by the Linux kernel becoming more and more
10025 asynchronous and event base. The Ubuntu approach using udev and
10026 upstart might be a good way forward. Time will show.
</p
>
10028 <p
>Anyway, there are a few ways at the moment to speed up the boot
10029 process in Debian. All of these should be applied to get a quick
10034 <li
>Use dash as /bin/sh.
</li
>
10036 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
10037 clock is in UTC.
</li
>
10039 <li
>Install and activate the insserv package to enable
10040 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
10041 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
10045 These points are based on the Google summer of code work done by
10046 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
10047 Villegas
</a
>.
10049 <p
>Support for makefile-style concurrency during boot was uploaded to
10050 unstable yesterday. When we tested it, we were able to cut
6 seconds
10051 from the boot sequence. It depend on very correct dependency
10052 declaration in all init.d scripts, so I expect us to find edge cases
10053 where the dependences in some scripts are slightly wrong when we start
10054 using this.
</p
>
10056 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
10057 introduced by Raphael Geissert today, one that could affect the
10058 startup speed as well. Instead of starting some scripts concurrently
10059 from rcS.d/ and another set of scripts from rc2.d/, it would be
10060 possible to run a of them in the same process. A quick way to test
10061 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
10062 insserv
'. Will need to test if that work. :)
</p
>
10067 <title>BSAs påstander om piratkopiering møter motstand
</title>
10068 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10069 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10070 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10071 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10072 programvareselskapene som Microsoft og Apple, publisert en rapport der
10073 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10074 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10076 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10077 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10078 dagene. Et spesielt interessant kommentar fra Sverige,
10079 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10080 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10083 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10084 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10085 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10086 exakta
", säger BSAs Sverigechef John Hugosson.
10087 </blockquote
>
10089 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10090 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10091 piracy figures need a shot of reality
</a
> og
<a
10092 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10093 Copyright Treaty Work?
</a
></p
>
10095 <p
>Fant lenkene via
<a
10096 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10097 på Slashdot
</a
>.
</p
>
10102 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10103 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10104 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10105 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10106 <description><p
>Kom over
10107 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10108 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10109 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10110 jobber til daglig. En rask opptelling forteller meg at vi har
490
10111 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10112 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10113 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10118 <title>Kryptert harddisk - naturligvis
</title>
10119 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10120 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10121 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10122 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10123 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10124 når en tar tap av arbeidstid, fortrolige dokumenter,
10125 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10126 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10127 til at jeg har kryptert harddisken på både kontormaskinen og min
10128 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10129 komme på avveie, den første informasjon relatert til jobben min ved
10130 Universitetet i Oslo, og den andre relatert til blant annet
10131 foreningsarbeide. Kryptering av diskene gjør at det er lite
10132 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10133 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10134 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10135 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10136 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10137 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10138 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10139 det er gjort slik jeg gjør det er minimale, og gevinstene er
10140 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10141 maskinen reinstalleres og alt er tapt.
</p
>
10143 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10144 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10145 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10146 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10147 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10148 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10149 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10150 betydelige.
</p
>
10155 <title>Two projects that have improved the quality of free software a lot
</title>
10156 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10157 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10158 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10159 <description><p
>There are two software projects that have had huge influence on the
10160 quality of free software, and I wanted to mention both in case someone
10161 do not yet know them.
</p
>
10163 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10164 tool to detect and expose errors in the memory handling of programs.
10165 It is easy to use, all one need to do is to run
'valgrind program
',
10166 and it will report any problems on stdout. It is even better if the
10167 program include debug information. With debug information, it is able
10168 to report the source file name and line number where the problem
10169 occurs. It can report things like
'reading past memory block in file
10170 X line N, the memory block was allocated in file Y, line M
', and
10171 'using uninitialised value in control logic
'. This tool has made it
10172 trivial to investigate reproducible crash bugs in programs, and have
10173 reduced the number of this kind of bugs in free software a lot.
10175 <p
>The second one is
10176 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10177 a source code checker. It is able to process the source of a program
10178 and find problems in the logic without running the program. It
10179 started out as the Stanford Checker and became well known when it was
10180 used to find bugs in the Linux kernel. It is now a commercial tool
10181 and the company behind it is running
10182 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10183 free software community, where a lot of free software projects get
10184 their source checked for free. Several thousand defects have been
10185 found and fixed so far. It can find errors like
'lock L taken in file
10186 X line N is never released if exiting in line M
', or
'the code in file
10187 Y lines O to P can never be executed
'. The projects included in the
10188 community service project have managed to get rid of a lot of
10189 reliability problems thanks to Coverity.
</p
>
10191 <p
>I believe tools like this, that are able to automatically find
10192 errors in the source, are vital to improve the quality of software and
10193 make sure we can get rid of the crashing and failing software we are
10194 surrounded by today.
</p
>
10199 <title>No patch is not better than a useless patch
</title>
10200 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10201 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10202 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10203 <description><p
>Julien Blache
10204 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10205 patch is better than a useless patch
</a
>. I completely disagree, as a
10206 patch allow one to discuss a concrete and proposed solution, and also
10207 prove that the issue at hand is important enough for someone to spent
10208 time on fixing it. No patch do not provide any of these positive
10209 properties.
</p
>
10214 <title>Standardize on protocols and formats, not vendors and applications
</title>
10215 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10216 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10217 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10218 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10219 very good one to form a long lived computer infrastructure. It is the
10220 simple one, lost by many in todays computer industry: Standardize on
10221 open network protocols and open exchange/storage formats, not applications.
10222 Applications come and go, while protocols and files tend to stay, and
10223 thus one want to make it easy to change application and vendor, while
10224 avoiding conversion costs and locking users to a specific platform or
10225 application.
</p
>
10227 <p
>This approach make it possible to replace the client applications
10228 independently of the server applications. One can even allow users to
10229 use several different applications as long as they handle the selected
10230 protocol and format. In the normal case, only one client application
10231 is recommended and users only get help if they choose to use this
10232 application, but those that want to deviate from the easy path are not
10233 blocked from doing so.
</p
>
10235 <p
>It also allow us to replace the server side without forcing the
10236 users to replace their applications, and thus allow us to select the
10237 best server implementation at any moment, when scale and resouce
10238 requirements change.
</p
>
10240 <p
>I strongly recommend standardizing - on open network protocols and
10241 open formats, but I would never recommend standardizing on a single
10242 application that do not use open network protocol or open formats.
</p
>
10247 <title>Returning from Skolelinux developer gathering
</title>
10248 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10249 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10250 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10251 <description><p
>I
'm sitting on the train going home from this weekends Debian
10252 Edu/Skolelinux development gathering. I got a bit done tuning the
10253 desktop, and looked into the dynamic service location protocol
10254 implementation avahi. It look like it could be useful for us. Almost
10255 30 people participated, and I believe it was a great environment to
10256 get to know the Skolelinux system. Walter Bender, involved in the
10257 development of the Sugar educational platform, presented his stuff and
10258 also helped me improve my OLPC installation. He also showed me that
10259 his Turtle Art application can be used in standalone mode, and we
10260 agreed that I would help getting it packaged for Debian. As a
10261 standalone application it would be great for Debian Edu. We also
10262 tried to get the video conferencing working with two OLPCs, but that
10263 proved to be too hard for us. The application seem to need more work
10264 before it is ready for me. I look forward to getting home and relax
10270 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10271 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10272 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10273 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10274 <description><p
>The state of standardized LDAP schemas on Linux is far from
10275 optimal. There is RFC
2307 documenting one way to store NIS maps in
10276 LDAP, and a modified version of this normally called RFC
2307bis, with
10277 some modifications to be compatible with Active Directory. The RFC
10278 specification handle the content of a lot of system databases, but do
10279 not handle DNS zones and DHCP configuration.
</p
>
10281 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10282 we would like to store information about users, SMB clients/hosts,
10283 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10284 and LTSP configuration in LDAP. These objects have a lot in common,
10285 but with the current LDAP schemas it is not possible to have one
10286 object per entity. For example, one need to have at least three LDAP
10287 objects for a given computer, one with the SMB related stuff, one with
10288 DNS information and another with DHCP information. The schemas
10289 provided for DNS and DHCP are impossible to combine into one LDAP
10290 object. In addition, it is impossible to implement quick queries for
10291 netgroup membership, because of the way NIS triples are implemented.
10292 It just do not scale. I believe it is time for a few RFC
10293 specifications to cleam up this mess.
</p
>
10295 <p
>I would like to have one LDAP object representing each computer in
10296 the network, and this object can then keep the SMB (ie host key), DHCP
10297 (mac address/name) and DNS (name/IP address) settings in one place.
10298 It need to be efficently stored to make sure it scale well.
</p
>
10300 <p
>I would also like to have a quick way to map from a user or
10301 computer and to the net group this user or computer is a member.
</p
>
10303 <p
>Active Directory have done a better job than unix heads like myself
10304 in this regard, and the unix side need to catch up. Time to start a
10305 new IETF work group?
</p
>
10310 <title>Endelig er Debian Lenny gitt ut
</title>
10311 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10312 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10313 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10314 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10315 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10316 Et langt steg videre for Debian-prosjektet, og en rekke nye
10317 programpakker blir nå tilgjengelig for de av oss som bruker den
10318 stabile utgaven av Debian. Neste steg er nå å få
10319 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10320 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10321 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10322 slippes løs på skolene. Takk til alle debian-utviklerne som har
10323 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10324 bootsekvens tilgjengelig i stabil utgave, vha pakken
10325 <tt
>insserv
</tt
>.
</p
>
10330 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10331 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10332 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10333 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10334 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10335 Oslo. Most of Saturday was used for the general assemly for the
10336 member organization, but the rest of the weekend I used to tune the
10337 LTSP installation. LTSP now work out of the box on the
10-network.
10338 Acer Aspire One proved to be a very nice thin client, with both
10339 screen, mouse and keybard in a small box. Was working on getting the
10340 diskless workstation setup configured out of the box, but did not
10341 finish it before the weekend was up.
</p
>
10343 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10344 the Brazilian group, so that will have to wait for the next
10345 development gathering. Would love to have the Debian Edu installer
10346 automatically detect and configure a multiseat setup when it find one
10347 of these cards.
</p
>
10352 <title>The sorry state of multimedia browser plugins in Debian
</title>
10353 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10354 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10355 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10356 <description><p
>Recently I have spent some time evaluating the multimedia browser
10357 plugins available in Debian Lenny, to see which one we should use by
10358 default in Debian Edu. We need an embedded video playing plugin with
10359 control buttons to pause or stop the video, and capable of streaming
10360 all the multimedia content available on the web. The test results and
10361 notes are available on
10362 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10363 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10364 fill this need. My personal video player favorite, VLC, has a really
10365 bad plugin which fail on a lot of the test pages. A lot of the MIME
10366 types I would expect to work with any free software player (like
10367 video/ogg), just do not work. And simple formats like the
10368 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10369 totem and vlc plugins. I hope the situation will improve soon. No
10370 wonder sites use the proprietary Adobe flash to play video.
</p
>
10372 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10373 be the only one fitting our needs. :/
</p
>