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>Where did that package go?
&mdash; geolocated IP traceroute
</title>
11 <link>http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
13 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
14 <description><p
>Did you ever wonder where the web trafic really flow to reach the
15 web servers, and who own the network equipment it is flowing through?
16 It is possible to get a glimpse of this from using traceroute, but it
17 is hard to find all the details. Many years ago, I wrote a system to
18 map the Norwegian Internet (trying to figure out if our plans for a
19 network game service would get low enough latency, and who we needed
20 to talk to about setting up game servers close to the users. Back
21 then I used traceroute output from many locations (I asked my friends
22 to run a script and send me their traceroute output) to create the
23 graph and the map. The output from traceroute typically look like
27 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
28 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
29 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
30 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
31 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
32 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
33 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
34 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
38 </pre
></p
>
40 <p
>This show the DNS names and IP addresses of (at least some of the)
41 network equipment involved in getting the data traffic from me to the
42 www.stortinget.no server, and how long it took in milliseconds for a
43 package to reach the equipment and return to me. Three packages are
44 sent, and some times the packages do not follow the same path. This
45 is shown for hop
5, where three different IP addresses replied to the
46 traceroute request.
</p
>
48 <p
>There are many ways to measure trace routes. Other good traceroute
49 implementations I use are traceroute (using ICMP packages) mtr (can do
50 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
51 traceroute and a lot of other capabilities). All of them are easily
52 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
54 <p
>This time around, I wanted to know the geographic location of
55 different route points, to visualize how visiting a web page spread
56 information about the visit to a lot of servers around the globe. The
57 background is that a web site today often will ask the browser to get
58 from many servers the parts (for example HTML, JSON, fonts,
59 JavaScript, CSS, video) required to display the content. This will
60 leak information about the visit to those controlling these servers
61 and anyone able to peek at the data traffic passing by (like your ISP,
62 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
64 <p
>Lets pick an example, the Norwegian parliament web site
65 www.stortinget.no. It is read daily by all members of parliament and
66 their staff, as well as political journalists, activits and many other
67 citizens of Norway. A visit to the www.stortinget.no web site will
68 ask your browser to contact
8 other servers: ajax.googleapis.com,
69 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
70 stats.g.doubleclick.net, www.google-analytics.com,
71 www.googletagmanager.com and www.netigate.se. I extracted this by
72 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
73 Stortinget web page and tell me all the URLs PhantomJS downloaded to
74 render the page (in HAR format using
75 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
76 netsniff example
</a
>. I am very grateful to Gorm for showing me how
77 to do this). My goal is to visualize network traces to all IP
78 addresses behind these DNS names, do show where visitors personal
79 information is spread when visiting the page.
</p
>
81 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
82 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
>
84 <p
>When I had a look around for options, I could not find any good
85 free software tools to do this, and decided I needed my own traceroute
86 wrapper outputting KML based on locations looked up using GeoIP. KML
87 is easy to work with and easy to generate, and understood by several
88 of the GIS tools I have available. I got good help from by NUUG
89 colleague Anders Einar with this, and the result can be seen in
90 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
91 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
92 free GeoIP databases I could find (and the for-pay databases my
93 friends had access to) is not up to the task. The IP addresses of
94 central Internet infrastructure would typically be placed near the
95 controlling companies main office, and not where the router is really
96 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
97 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
99 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
100 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
>
102 <p
>I also had a look at the visual traceroute graph created by
103 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
104 showing IP network ownership (aka AS owner) for the IP address in
106 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
107 graph display a lot of useful information about the traceroute in SVG
108 format
</a
>, and give a good indication on who control the network
109 equipment involved, but it do not include geolocation. This graph
110 make it possible to see the information is made available at least for
111 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
112 3 Communications and NetDNA.
</p
>
114 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
115 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
>
117 <p
>In the process, I came across the
118 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
119 Salim Gasmi. Its methology of combining guesses based on DNS names,
120 various location databases and finally use latecy times to rule out
121 candidate locations seemed to do a very good job of guessing correct
122 geolocation. But it could only do one trace at the time, did not have
123 a sensor in Norway and did not make the geolocations easily available
124 for postprocessing. So I contacted the developer and asked if he
125 would be willing to share the code (he refused until he had time to
126 clean it up), but he was interested in providing the geolocations in a
127 machine readable format, and willing to set up a sensor in Norway. So
128 since yesterday, it is possible to run traces from Norway in this
129 service thanks to a sensor node set up by
130 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
131 trace in KML format for further processing.
</p
>
133 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
134 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
>
136 <p
>Here we can see a lot of trafic passes Sweden on its way to
137 Denmark, Germany, Holland and Ireland. Plenty of places where the
138 Snowden confirmations verified the traffic is read by various actors
139 without your best interest as their top priority.
</p
>
141 <p
>Combining KML files is trivial using a text editor, so I could loop
142 over all the hosts behind the urls imported by www.stortinget.no and
143 ask for the KML file from GeoTraceroute, and create a combined KML
144 file with all the traces (unfortunately only one of the IP addresses
145 behind the DNS name is traced this time. To get them all, one would
146 have to request traces using IP number instead of DNS names from
147 GeoTraceroute). That might be the next step in this project.
</p
>
149 <p
>Armed with these tools, I find it a lot easier to figure out where
150 the IP traffic moves and who control the boxes involved in moving it.
151 And every time the link crosses for example the Swedish border, we can
152 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
153 Britain and NSA in USA and cables around the globe. (Hm, what should
154 we tell them? :) Keep that in mind if you ever send anything
155 unencrypted over the Internet.
</p
>
157 <p
>PS: KML files are drawn using
158 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
159 Rublev
<a/
>, as it was less cluttered than the local Linux application
160 Marble. There are heaps of other options too.
</p
>
162 <p
>As usual, if you use Bitcoin and want to show your support of my
163 activities, please send Bitcoin donations to my address
164 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
169 <title>Appstream just learned how to map hardware to packages too!
</title>
170 <link>http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
172 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
173 <description><p
>I received a very nice Christmas present today. As my regular
174 readers probably know, I have been working on the
175 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
176 system
</a
> for many years. The goal of the Isenkram system is to make
177 it easier for users to figure out what to install to get a given piece
178 of hardware to work in Debian, and a key part of this system is a way
179 to map hardware to packages. Isenkram have its own mapping database,
180 and also uses data provided by each package using the AppStream
181 metadata format. And today,
182 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
183 Debian learned to look up hardware the same way Isenkram is doing it,
184 ie using fnmatch():
</p
>
187 % appstreamcli what-provides modalias \
188 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
189 Identifier: pymissile [generic]
191 Summary: Control original Striker USB Missile Launcher
193 % appstreamcli what-provides modalias usb:v0694p0002d0000
194 Identifier: libnxt [generic]
196 Summary: utility library for talking to the LEGO Mindstorms NXT brick
199 Identifier: t2n [generic]
201 Summary: Simple command-line tool for Lego NXT
204 Identifier: python-nxt [generic]
206 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
209 Identifier: nbc [generic]
211 Summary: C compiler for LEGO Mindstorms NXT bricks
214 </pre
></p
>
216 <p
>A similar query can be done using the combined AppStream and
217 Isenkram databases using the isenkram-lookup tool:
</p
>
220 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
222 % isenkram-lookup usb:v0694p0002d0000
228 </pre
></p
>
230 <p
>You can find modalias values relevant for your machine using
231 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
233 <p
>If you want to make this system a success and help Debian users
234 make the most of the hardware they have, please
235 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
236 AppStream metadata for your package following the guidelines
</a
>
237 documented in the wiki. So far only
11 packages provide such
238 information, among the several hundred hardware specific packages in
239 Debian. The Isenkram database on the other hand contain
101 packages,
240 mostly related to USB dongles. Most of the packages with hardware
241 mapping in AppStream are LEGO Mindstorms related, because I have, as
242 part of my involvement in
243 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
244 team
</a
> given priority to making sure LEGO users get proposed the
245 complete set of packages in Debian for that particular hardware. The
246 team also got a nice Christmas present today. The
247 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
248 package
</a
> made it into Debian. With this package in place, it is
249 now possible to use the LEGO Mindstorms NXT unit with only free
250 software, as the nxt-firmware package contain the source and firmware
251 binaries for the NXT brick.
</p
>
253 <p
>As usual, if you use Bitcoin and want to show your support of my
254 activities, please send Bitcoin donations to my address
255 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
260 <title>Isenkram updated with a lot more hardware-package mappings
</title>
261 <link>http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
262 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
263 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
264 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
265 system
</a
> I wrote two years ago to make it easier in Debian to find
266 and install packages to get your hardware dongles to work, is still
267 going strong. It is a system to look up the hardware present on or
268 connected to the current system, and map the hardware to Debian
269 packages. It can either be done using the tools in isenkram-cli or
270 using the user space daemon in the isenkram package. The latter will
271 notify you, when inserting new hardware, about what packages to
272 install to get the dongle working. It will even provide a button to
273 click on to ask packagekit to install the packages.
</p
>
275 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
294 </pre
></p
>
296 <p
>It can also list the firware package providing firmware requested
297 by the load kernel modules, which in my case is an empty list because
298 I have all the firmware my machine need:
301 % /usr/sbin/isenkram-autoinstall-firmware -l
302 info: did not find any firmware files requested by loaded kernel modules. exiting
304 </pre
></p
>
306 <p
>The last few days I had a look at several of the around
250
307 packages in Debian with udev rules. These seem like good candidates
308 to install when a given hardware dongle is inserted, and I found
309 several that should be proposed by isenkram. I have not had time to
310 check all of them, but am happy to report that now there are
97
311 packages packages mapped to hardware by Isenkram.
11 of these
312 packages provide hardware mapping using AppStream, while the rest are
313 listed in the modaliases file provided in isenkram.
</p
>
315 <p
>These are the packages with hardware mappings at the moment. The
316 <strong
>marked packages
</strong
> are also announcing their hardware
317 support using AppStream, for everyone to use:
</p
>
319 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
320 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
321 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
322 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
323 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
324 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
325 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
326 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
327 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
328 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
329 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
330 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
331 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
332 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
333 pcscd, pidgin-blinklight, printer-driver-splix,
334 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
335 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
336 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
337 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
338 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
339 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
340 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
341 xserver-xorg-video-vmware, yubikey-personalization and
342 zd1211-firmware
</p
>
344 <p
>If you know of other packages, please let me know with a wishlist
345 bug report against the isenkram-cli package, and ask the package
347 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
348 metadata according to the guidelines
</a
> to provide the information
349 for everyone. In time, I hope to get rid of the isenkram specific
350 hardware mapping and depend exclusively on AppStream.
</p
>
352 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
353 much hardware, and suggest that the package with with any ethernet
354 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
355 the details. I hope the maintainer find time to address it soon. In
356 the mean time I provide an override in isenkram.
</p
>
361 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
362 <link>http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
363 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
364 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
365 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
367 <p
>In my early years, I played
368 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
369 Elite
</a
> on my PC. I spent many months trading and fighting in
370 space, and reached the
'elite
' fighting status before I moved on. The
371 original Elite game was available on Commodore
64 and the IBM PC
372 edition I played had a
64 KB executable. I am still impressed today
373 that the authors managed to squeeze both a
3D engine and details about
374 more than
2000 planet systems across
7 galaxies into a binary so
377 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
378 software game Oolite inspired by Elite
</a
> for a while, but did not
379 really have time to test it properly until a few days ago. It was
380 great to discover that my old knowledge about trading routes were
381 still valid. But my fighting and flying abilities were gone, so I had
382 to retrain to be able to dock on a space station. And I am still not
383 able to make much resistance when I am attacked by pirates, so I
384 bougth and mounted the most powerful laser in the rear to be able to
385 put up at least some resistance while fleeing for my life. :)
</p
>
387 <p
>When playing Elite in the late eighties, I had to discover
388 everything on my own, and I had long lists of prices seen on different
389 planets to be able to decide where to trade what. This time I had the
391 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
392 where information about each planet is easily available with common
393 price ranges and suggested trading routes. This improved my ability
394 to earn money and I have been able to earn enough to buy a lot of
395 useful equipent in a few days. I believe I originally played for
396 months before I could get a docking computer, while now I could get it
397 after less then a week.
</p
>
399 <p
>If you like science fiction and dreamed of a life as a vagabond in
400 space, you should try out Oolite. It is available for Linux, MacOSX
401 and Windows, and is included in Debian and derivatives since
2011.
</p
>
403 <p
>As usual, if you use Bitcoin and want to show your support of my
404 activities, please send Bitcoin donations to my address
405 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
410 <title>Quicker Debian installations using eatmydata
</title>
411 <link>http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
412 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
413 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
414 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
415 installation system, observing how using
416 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
417 could speed up the installation
</a
> quite a bit. My testing measured
418 speedup around
20-
40 percent for Debian Edu, where we install around
419 1000 packages from within the installer. The eatmydata package
420 provide a way to disable/delay file system flushing. This is a bit
421 risky in the general case, as files that should be stored on disk will
422 stay only in memory a bit longer than expected, causing problems if a
423 machine crashes at an inconvenient time. But for an installation, if
424 the machine crashes during installation the process is normally
425 restarted, and avoiding disk operations as much as possible to speed
426 up the process make perfect sense.
428 <p
>I added code in the Debian Edu specific installation code to enable
429 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
430 but did not have time to push it any further. But a few months ago I
431 picked it up again and worked with the libeatmydata package maintainer
432 Mattia Rizzolo to make it easier for everyone to get this installation
433 speedup in Debian. Thanks to our cooperation There is now an
434 eatmydata-udeb package in Debian testing and unstable, and simply
435 enabling/installing it in debian-installer (d-i) is enough to get the
436 quicker installations. It can be enabled using preseeding. The
437 following untested kernel argument should do the trick:
</p
>
439 <blockquote
><pre
>
440 preseed/early_command=
"anna-install eatmydata-udeb
"
441 </pre
></blockquote
>
443 <p
>This should ask d-i to install the package inside the d-i
444 environment early in the installation sequence. Having it installed
445 in d-i in turn will make sure the relevant scripts are called just
446 after debootstrap filled /target/ with the freshly installed Debian
447 system to configure apt to run dpkg with eatmydata. This is enough to
448 speed up the installation process. There is a proposal to
449 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
450 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
451 tested its impact.
</p
>
457 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
458 <link>http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
459 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
460 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
461 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
462 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
463 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
464 elever over det ganske land skal levere inn hvert år. Det mange ikke
465 vet er at selv om de kommersielle alternativene
466 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
467 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
468 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
469 utmerket fri programvarealternativ som kan. Oversetterverktøyet
470 Apertium har støtte for en rekke språkkombinasjoner, og takket være
471 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
472 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
473 nynorsk, og få den automatoversatt til det andre skriftspråket.
474 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
475 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
476 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
477 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
478 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
479 teksten din i webskjemaet der.
481 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
482 teknologien kan du enten installere pakken
483 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
484 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
486 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
487 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
488 denne teksten som ble skrevet på bokmål over maskinoversatt til
493 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
494 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
495 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
496 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
497 veit er at sjølv om dei kommersielle alternativa
498 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
499 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
500 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
501 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
502 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
503 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
504 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
505 nynorsk, og få den *automatoversatt til det andre skriftspråket.
506 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
507 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
508 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
509 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
510 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
511 teksta di i *webskjemaet der.
513 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
514 teknologien kan du anten installera pakken
515 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
516 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
517 *api.*apertium.org. Sjå
518 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
519 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
520 for denne teksta som vart skreva på bokmål over *maskinoversatt til
526 <title>Coz profiler for multi-threaded software is now in Debian
</title>
527 <link>http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
528 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
529 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
530 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
531 profiler able to run benchmarking experiments on the instrumented
532 multi-threaded program, finally
533 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
534 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
536 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
537 blogged about the coz tool
</a
> in August working with upstream to make
538 it suitable for Debian. There are still issues with clang
539 compatibility, inline assembly only working x86 and minimized
540 JavaScript libraries.
</p
>
542 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
544 <p
><blockquote
>
545 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
546 </blockquote
></p
>
548 <p
>This will produce a profile.coz file in the current working
549 directory with the profiling information. This is then given to a
550 JavaScript application provided in the package and available from
551 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
552 To start the local copy, invoke it in a browser like this:
</p
>
554 <p
><blockquote
>
555 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
556 </blockquote
></p
>
558 <p
>See the project home page and the
559 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
560 ;login: article on Coz
</a
> for more information on how it is
566 <title>My own self balancing Lego Segway
</title>
567 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
568 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
569 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
570 <description><p
>A while back I received a Gyro sensor for the NXT
571 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
572 present. It had been on my wishlist for a while, because I wanted to
573 build a Segway like balancing lego robot. I had already built
574 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
575 robot
</a
> with the kids, using the light/color sensor included in the
576 NXT kit as the balance sensor, but it was not working very well. It
577 could balance for a while, but was very sensitive to the light
578 condition in the room and the reflective properties of the surface and
579 would fall over after a short while. I wanted something more robust,
581 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
582 gyro sensor from HiTechnic
</a
> I believed would solve it on my
583 wishlist for some years before it suddenly showed up as a gift from my
584 loved ones. :)
</p
>
586 <p
>Unfortunately I have not had time to sit down and play with it
587 since then. But that changed some days ago, when I was searching for
588 lego segway information and came across a recipe from HiTechnic for
590 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
591 HTWay
</a
>, a segway like balancing robot. Build instructions and
592 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
593 code
</a
> was included, so it was just a question of putting it all
594 together. And thanks to the great work of many Debian developers, the
595 compiler needed to build the source for the NXT is already included in
596 Debian, so I was read to go in less than an hour. The resulting robot
597 do not look very impressive in its simplicity:
</p
>
599 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
601 <p
>Because I lack the infrared sensor used to control the robot in the
602 design from HiTechnic, I had to comment out the last task
603 (taskControl). I simply placed /* and */ around it get the program
604 working without that sensor present. Now it balances just fine until
605 the battery status run low:
</p
>
607 <p align=
"center
"><video width=
"70%
" controls=
"true
">
608 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
609 </video
></p
>
611 <p
>Now we would like to teach it how to follow a line and take remote
612 control instructions using the included Bluetooth receiver in the NXT.
</p
>
614 <p
>If you, like me, love LEGO and want to make sure we find the tools
615 they need to work with LEGO in Debian and all our derivative
616 distributions like Ubuntu, check out
617 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
618 project page
</a
> and join the Debian LEGO team. Personally I own a
619 RCX and NXT controller (no EV3), and would like to make sure the
620 Debian tools needed to program the systems I own work as they
626 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
627 <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
628 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
629 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
630 <description><p
>In July
631 <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
632 wrote how to get the Signal Chrome/Chromium app working
</a
> without
633 the ability to receive SMS messages (aka without a cell phone). It is
634 time to share some experiences and provide an updated setup.
</p
>
636 <p
>The Signal app have worked fine for several months now, and I use
637 it regularly to chat with my loved ones. I had a major snag at the
638 end of my summer vacation, when the the app completely forgot my
639 setup, identity and keys. The reason behind this major mess was
640 running out of disk space. To avoid that ever happening again I have
641 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
642 roll back to an earlier version if the files are wiped by mistake. I
643 had to use it once after introducing the git backup. When rolling
644 back to an earlier version, one need to use the
'reset session
' option
645 in Signal to get going, and notify the people you talk with about the
646 problem. I assume there is some sequence number tracking in the
647 protocol to detect rollback attacks. The git repository is rather big
648 (
674 MiB so far), but I have not tried to figure out if some of the
649 content can be added to a .gitignore file due to lack of spare
652 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
653 make it impossible to send messages using Signal. I could still
654 receive them, but had to patch the code with a new timestamp to send.
655 I believe the timeout is added by the developers to force people to
656 upgrade to the latest version of the app, even when there is no
657 protocol changes, to reduce the version skew among the user base and
658 thus try to keep the number of support requests down.
</p
>
660 <p
>Since my original recipe, the Signal source code changed slightly,
661 making the old patch fail to apply cleanly. Below is an updated
662 patch, including the shell wrapper I use to start Signal. The
663 original version required a new user to locate the JavaScript console
664 and call a function from there. I got help from a friend with more
665 JavaScript knowledge than me to modify the code to provide a GUI
666 button instead. This mean that to get started you just need to run
667 the wrapper and click the
'Register without mobile phone
' to get going
668 now. I
've also modified the timeout code to always set it to
90 days
669 in the future, to avoid having to patch the code regularly.
</p
>
671 <p
>So, the updated recipe for Debian Jessie:
</p
>
675 <li
>First, install required packages to get the source code and the
676 browser you need. Signal only work with Chrome/Chromium, as far as I
677 know, so you need to install it.
680 apt install git tor chromium
681 git clone https://github.com/WhisperSystems/Signal-Desktop.git
682 </pre
></li
>
684 <li
>Modify the source code using command listed in the the patch
685 block below.
</li
>
687 <li
>Start Signal using the run-signal-app wrapper (for example using
688 <tt
>`pwd`/run-signal-app
</tt
>).
690 <li
>Click on the
'Register without mobile phone
', will in a phone
691 number you can receive calls to the next minute, receive the
692 verification code and enter it into the form field and press
693 'Register
'. Note, the phone number you use will be user Signal
694 username, ie the way others can find you on Signal.
</li
>
696 <li
>You can now use Signal to contact others. Note, new contacts do
697 not show up in the contact list until you restart Signal, and there is
698 no way to assign names to Contacts. There is also no way to create or
699 update chat groups. I suspect this is because the web app do not have
700 a associated contact database.
</li
>
704 <p
>I am still a bit uneasy about using Signal, because of the way its
705 main author moxie0 reject federation and accept dependencies to major
706 corporations like Google (part of the code is fetched from Google) and
707 Amazon (the central coordination point is owned by Amazon). See for
709 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
710 LibreSignal issue tracker
</a
> for a thread documenting the authors
711 view on these issues. But the network effect is strong in this case,
712 and several of the people I want to communicate with already use
713 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
714 once it
<a href=
"https://bugs.debian.org/
830265">work on my
715 laptop
</a
>? It already work on Windows and Android, and is included
716 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
717 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
718 working on Debian Stable.
</p
>
720 <p
>Anyway, this is the patch I apply to the Signal code to get it
721 working. It switch to the production servers, disable to timeout,
722 make registration easier and add the shell wrapper:
</p
>
725 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
726 diff --git a/js/background.js b/js/background.js
727 index
24b4c1d.
.579345f
100644
728 --- a/js/background.js
729 +++ b/js/background.js
734 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
735 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
736 var SERVER_PORTS = [
80,
4433,
8443];
737 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
738 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
740 window.getSocketStatus = function() {
741 if (messageReceiver) {
742 diff --git a/js/expire.js b/js/expire.js
743 index
639aeae..beb91c3
100644
748 'use strict
';
749 - var BUILD_EXPIRATION =
0;
750 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
752 window.extension = window.extension || {};
754 diff --git a/js/views/install_view.js b/js/views/install_view.js
755 index
7816f4f.
.1d6233b
100644
756 --- a/js/views/install_view.js
757 +++ b/js/views/install_view.js
760 'click .step1
': this.selectStep.bind(this,
1),
761 'click .step2
': this.selectStep.bind(this,
2),
762 -
'click .step3
': this.selectStep.bind(this,
3)
763 +
'click .step3
': this.selectStep.bind(this,
3),
764 +
'click .callreg
': function() { extension.install(
'standalone
') },
767 clearQR: function() {
768 diff --git a/options.html b/options.html
769 index dc0f28e.
.8d709f6
100644
773 &lt;div class=
'nav
'>
774 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
775 &lt;p
>{{ installTagline }}
&lt;/p
>
776 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
777 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
778 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
781 &lt;span class=
'dot step1 selected
'>&lt;/span
>
782 &lt;span class=
'dot step2
'>&lt;/span
>
783 &lt;span class=
'dot step3
'>&lt;/span
>
784 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
785 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
791 +userdata=
"`pwd`/userdata
"
792 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
793 + (cd $userdata
&& git init)
795 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
797 + --proxy-server=
"socks://localhost:
9050" \
798 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
800 chmod a+rx run-signal-app
803 <p
>As usual, if you use Bitcoin and want to show your support of my
804 activities, please send Bitcoin donations to my address
805 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
810 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
811 <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
812 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
813 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
814 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
815 system
</a
> provide a practical and easy way to figure out which
816 packages support the hardware in a given machine. The command line
817 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
818 convenient way to list and install packages relevant for the current
819 hardware during system installation, both user space packages and
820 firmware packages. The GUI background daemon on the other hand provide
821 a pop-up proposing to install packages when a new dongle is inserted
822 while using the computer. For example, if you plug in a smart card
823 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
824 that package isn
't already installed, and if you plug in a USB video
825 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
826 cheese is currently missing. This already work just fine.
</p
>
828 <p
>But Isenkram depend on a database mapping from hardware IDs to
829 package names. When I started no such database existed in Debian, so
830 I made my own data set and included it with the isenkram package and
831 made isenkram fetch the latest version of this database from git using
832 http. This way the isenkram users would get updated package proposals
833 as soon as I learned more about hardware related packages.
</p
>
835 <p
>The hardware is identified using modalias strings. The modalias
836 design is from the Linux kernel where most hardware descriptors are
837 made available as a strings that can be matched using filename style
838 globbing. It handle USB, PCI, DMI and a lot of other hardware related
839 identifiers.
</p
>
841 <p
>The downside to the Isenkram specific database is that there is no
842 information about relevant distribution / Debian version, making
843 isenkram propose obsolete packages too. But along came AppStream, a
844 cross distribution mechanism to store and collect metadata about
845 software packages. When I heard about the proposal, I contacted the
846 people involved and suggested to add a hardware matching rule using
847 modalias strings in the specification, to be able to use AppStream for
848 mapping hardware to packages. This idea was accepted and AppStream is
849 now a great way for a package to announce the hardware it support in a
850 distribution neutral way. I wrote
851 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
852 recipe on how to add such meta-information
</a
> in a blog post last
853 December. If you have a hardware related package in Debian, please
854 announce the relevant hardware IDs using AppStream.
</p
>
856 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
857 RCX or NXT unit, announce this support using AppStream. The effect is
858 that when you insert such LEGO robot controller into your Debian
859 machine, Isenkram will propose to install the packages needed to get
860 it working. The intention is that this should allow the local user to
861 start programming his robot controller right away without having to
862 guess what packages to use or which permissions to fix.
</p
>
864 <p
>But when I sat down with my son the other day to program our NXT
865 unit using his Debian Stretch computer, I discovered something
866 annoying. The local console user (ie my son) did not get access to
867 the USB device for programming the unit. This used to work, but no
868 longer in Jessie and Stretch. After some investigation and asking
869 around on #debian-devel, I discovered that this was because udev had
870 changed the mechanism used to grant access to local devices. The
871 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
872 no longer applied, because LDAP users no longer was added to the
873 plugdev group during login. Michael Biebl told me that this method
874 was obsolete and the new method used ACLs instead. This was good
875 news, as the plugdev mechanism is a mess when using a remote user
876 directory like LDAP. Using ACLs would make sure a user lost device
877 access when she logged out, even if the user left behind a background
878 process which would retain the plugdev membership with the ConsoleKit
879 setup. Armed with this knowledge I moved on to fix the access problem
880 for the LEGO Mindstorms related packages.
</p
>
882 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
883 applied directly for a device, or is applied in
884 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
885 LEGO Mindstorms udev rules did not have a class, I decided to add the
886 tag directly in the udev rules files included in the packages. Here
887 is one example. For the nqc C compiler for the RCX, the
888 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
891 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
892 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
893 </pre
></p
>
895 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
896 packages using plugdev in their /lib/udev/rules.d/ files should be
897 changed to use this tag (either directly or indirectly via
898 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
899 to detect this?
</p
>
901 <p
>I
've been unable to find good documentation on the uaccess feature.
902 It is unclear to me if the uaccess tag is an internal implementation
903 detail like the udev-acl tag used by
904 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
905 indirect method is the preferred way. Michael
906 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
907 documentation from the systemd project
</a
> and I hope it will make
908 this clearer. For now I use the generic classes when they exist and
909 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
910 directly if no such class exist.
</p
>
912 <p
>To learn more about the isenkram system, please check out
913 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
914 blog posts tagged isenkram
</a
>.
</p
>
916 <p
>To help out making life for LEGO constructors in Debian easier,
917 please join us on our IRC channel
918 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
919 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
920 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
921 list is not yet created, but we are working on it. :)
</p
>
923 <p
>As usual, if you use Bitcoin and want to show your support of my
924 activities, please send Bitcoin donations to my address
925 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
930 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
931 <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
932 <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>
933 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
934 <description><p
>In April we
935 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
936 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
937 how to set up and administrate a Debian system. Today I am happy to
938 report that the first draft is now publicly available. You can find
939 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
940 Administrator
's Handbook page
</a
> (under Other languages). The first
941 eight chapters have a first draft translation, and we are working on
942 proofreading the content. If you want to help out, please start
944 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
945 hosted weblate project page
</a
>, and get in touch using
946 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
947 translators mailing list
</a
>. Please also check out
948 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
949 contributors
</a
>. A good way to contribute is to proofread the text
950 and update weblate if you find errors.
</p
>
952 <p
>Our goal is still to make the Norwegian book available on paper as well as
953 electronic form.
</p
>
958 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
959 <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
960 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
961 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
962 <description><p
>This summer, I read a great article
963 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
964 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
965 how to profile multi-threaded programs. It presented a system for
966 profiling software by running experiences in the running program,
967 testing how run time performance is affected by
"speeding up
" parts of
968 the code to various degrees compared to a normal run. It does this by
969 slowing down parallel threads while the
"faster up
" code is running
970 and measure how this affect processing time. The processing time is
971 measured using probes inserted into the code, either using progress
972 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
973 can also measure unmodified code by measuring complete the program
974 runtime and running the program several times instead.
</p
>
976 <p
>The project and presentation was so inspiring that I would like to
977 get the system into Debian. I
978 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
979 a WNPP request for it
</a
> and contacted upstream to try to make the
980 system ready for Debian by sending patches. The build process need to
981 be changed a bit to avoid running
'git clone
' to get dependencies, and
982 to include the JavaScript web page used to visualize the collected
983 profiling information included in the source package.
984 But I expect that should work out fairly soon.
</p
>
986 <p
>The way the system work is fairly simple. To run an coz experiment
987 on a binary with debug symbols available, start the program like this:
989 <p
><blockquote
><pre
>
990 coz run --- program-to-run
991 </pre
></blockquote
></p
>
993 <p
>This will create a text file profile.coz with the instrumentation
994 information. To show what part of the code affect the performance
995 most, use a web browser and either point it to
996 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
997 or use the copy from git (in the gh-pages branch). Check out this web
998 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
999 profiling more useful you include
&lt;coz.h
&gt; and insert the
1000 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
1001 code, rebuild and run the profiler. This allow coz to do more
1002 targeted experiments.
</p
>
1004 <p
>A video published by ACM
1005 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
1006 Coz profiler
</a
> is available from Youtube. There is also a paper
1007 from the
25th Symposium on Operating Systems Principles available
1009 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
1010 finding code that counts with causal profiling
</a
>.
</p
>
1012 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
1013 for Coz is available from github. It will only build with clang
1015 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
1016 feature missing in GCC
</a
>, but I
've submitted
1017 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
1018 it
</a
> and hope it will be included in the upstream source soon.
</p
>
1020 <p
>Please get in touch if you, like me, would like to see this piece
1021 of software in Debian. I would very much like some help with the
1022 packaging effort, as I lack the in depth knowledge on how to package
1023 C++ libraries.
</p
>
1028 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
1029 <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
1030 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
1031 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
1032 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
1033 to be a slight challenge. Here is the recipe if I ever need to do it
1034 again. It all started by me wanting to try the recipe to set up
1035 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
1036 hardened Android installation
</a
> from the Tor project blog on a
1037 device I had access to. It is a old mobile phone with a broken
1038 microphone The initial idea had been to just
1039 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
1040 CyanogenMod on it
</a
>, but did not quite find time to start on it
1041 until a few days ago.
</p
>
1043 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
1044 loader (press volume down and power at the same time), (
2) select
1045 'fastboot
' before (
3) connecting the device via USB to a Linux
1046 machine, (
4) request the device identifier token by running
'fastboot
1047 oem get_identifier_token
', (
5) request the device unlocking key using
1048 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
1049 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
1051 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
1052 or newer, and the device I was working on had
2.00.0027. This
1053 apparently can be easily fixed by downloading a Windows program and
1054 running it on your Windows machine, if you accept the terms Microsoft
1055 require you to accept to use Windows - which I do not. So I had to
1056 come up with a different approach. I got a lot of help from AndyCap
1057 on #nuug, and would not have been able to get this working without
1060 <p
>First I needed to extract the hboot firmware from
1061 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
1062 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
1063 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
1064 project named unruu
</a
> using libunshield. The unshield tool did not
1065 recognise the file format, but unruu worked and extracted rom.zip,
1066 containing the new hboot firmware and a text file describing which
1067 devices it would work for.
</p
>
1069 <p
>Next, I needed to get the new firmware into the device. For this I
1070 followed some instructions
1071 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
1072 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
1073 machine with Debian testing:
</p
>
1075 <p
><pre
>
1076 adb reboot-bootloader
1077 fastboot oem rebootRUU
1078 fastboot flash zip rom.zip
1079 fastboot flash zip rom.zip
1081 </pre
></p
>
1083 <p
>The flash command apparently need to be done twice to take effect,
1084 as the first is just preparations and the second one do the flashing.
1085 The adb command is just to get to the boot loader menu, so turning the
1086 device on while holding volume down and the power button should work
1089 <p
>With the new hboot version in place I could start following the
1090 instructions on the HTC developer web site. I got the device token
1091 like this:
</p
>
1093 <p
><pre
>
1094 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
1097 <p
>And once I got the unlock code via email, I could use it like
1100 <p
><pre
>
1101 fastboot flash unlocktoken Unlock_code.bin
1102 </pre
></p
>
1104 <p
>And with that final step in place, the phone was unlocked and I
1105 could start stuffing the software of my own choosing into the device.
1106 So far I only inserted a replacement recovery image to wipe the phone
1107 before I start. We will see what happen next. Perhaps I should
1108 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
1113 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
1114 <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>
1115 <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>
1116 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
1117 <description><p
>For a while now, I have wanted to test
1118 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
1119 said to provide end to end encrypted communication and several of my
1120 friends and family are already using it. As I by choice do not own a
1121 mobile phone, this proved to be harder than expected. And I wanted to
1122 have the source of the client and know that it was the code used on my
1123 machine. But yesterday I managed to get it working. I used the
1124 Github source, compared it to the source in
1125 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
1126 Signal Chrome app
</a
> available from the Chrome web store, applied
1127 patches to use the production Signal servers, started the app and
1128 asked for the hidden
"register without a smart phone
" form. Here is
1129 the recipe how I did it.
</p
>
1131 <p
>First, I fetched the Signal desktop source from Github, using
1134 git clone https://github.com/WhisperSystems/Signal-Desktop.git
1137 <p
>Next, I patched the source to use the production servers, to be
1138 able to talk to other Signal users:
</p
>
1141 cat
&lt;
&lt;EOF | patch -p0
1142 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
1143 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1144 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
1149 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
1150 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
1151 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
1152 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
1153 var messageReceiver;
1154 window.getSocketStatus = function() {
1155 if (messageReceiver) {
1156 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
1157 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
1158 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
1161 'use strict
';
1162 - var BUILD_EXPIRATION =
0;
1163 + var BUILD_EXPIRATION =
1474492690000;
1165 window.extension = window.extension || {};
1170 <p
>The first part is changing the servers, and the second is updating
1171 an expiration timestamp. This timestamp need to be updated regularly.
1172 It is set
90 days in the future by the build process (Gruntfile.js).
1173 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
1175 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
1176 script to launch Signal in Chromium.
</p
>
1183 --proxy-server=
"socks://localhost:
9050" \
1184 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
1187 <p
> The script start the app and configure Chromium to use the Tor
1188 SOCKS5 proxy to make sure those controlling the Signal servers (today
1189 Amazon and Whisper Systems) as well as those listening on the lines
1190 will have a harder time location my laptop based on the Signal
1191 connections if they use source IP address.
</p
>
1193 <p
>When the script starts, one need to follow the instructions under
1194 "Standalone Registration
" in the CONTRIBUTING.md file in the git
1195 repository. I right clicked on the Signal window to get up the
1196 Chromium debugging tool, visited the
'Console
' tab and wrote
1197 'extension.install(
"standalone
")
' on the console prompt to get the
1198 registration form. Then I entered by land line phone number and
1199 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
1200 repeated the verification code three times. After entering the number
1201 into the verification code field in the form, I could start using
1202 Signal from my laptop.
1204 <p
>As far as I can tell, The Signal app will leak who is talking to
1205 whom and thus who know who to those controlling the central server,
1206 but such leakage is hard to avoid with a centrally controlled server
1207 setup. It is something to keep in mind when using Signal - the
1208 content of your chats are harder to intercept, but the meta data
1209 exposing your contact network is available to people you do not know.
1210 So better than many options, but not great. And sadly the usage is
1211 connected to my land line, thus allowing those controlling the server
1212 to associate it to my home and person. I would prefer it if only
1213 those I knew could tell who I was on Signal. There are options
1214 avoiding such information leakage, but most of my friends are not
1215 using them, so I am stuck with Signal for now.
</p
>
1220 <title>The new
"best
" multimedia player in Debian?
</title>
1221 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1222 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1223 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1224 <description><p
>When I set out a few weeks ago to figure out
1225 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1226 multimedia player in Debian claimed to support most file formats /
1227 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1228 the various players claimed support for. The range was from
55 to
130
1229 MIME types. I suspect most media formats are supported by all
1230 players, but this is not really reflected in the MimeTypes values in
1231 their desktop files. There are probably also some bogus MIME types
1232 listed, but it is hard to identify which one this is.
</p
>
1234 <p
>Anyway, in the mean time I got in touch with upstream for some of
1235 the players suggesting to add more MIME types to their desktop files,
1236 and decided to spend some time myself improving the situation for my
1237 favorite media player VLC. The fixes for VLC entered Debian unstable
1238 yesterday. The complete list of MIME types can be seen on the
1239 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1240 player MIME type support status
</a
> Debian wiki page.
</p
>
1242 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1243 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1244 kmplayer. I am sure some of the other players desktop files support
1245 several of the formats currently listed as working only with vlc,
1246 toten and parole.
</p
>
1248 <p
>A sad observation is that only
14 MIME types are listed as
1249 supported by all the tested multimedia players in Debian in their
1250 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1251 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1252 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1253 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1254 it sad that video/ogg and video/webm is not supported by all the media
1255 players in Debian. As far as I can tell, all of them can handle both
1261 <title>A program should be able to open its own files on Linux
</title>
1262 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1263 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1264 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1265 <description><p
>Many years ago, when koffice was fresh and with few users, I
1266 decided to test its presentation tool when making the slides for a
1267 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1268 wrote the first draft of the slides, saved the result and went to bed
1269 the day before I would give the talk. The next day I took a plane to
1270 the location where the meeting should take place, and on the plane I
1271 started up koffice again to polish the talk a bit, only to discover
1272 that kpresenter refused to load its own data file. I cursed a bit and
1273 started making the slides again from memory, to have something to
1274 present when I arrived. I tested that the saved files could be
1275 loaded, and the day seemed to be rescued. I continued to polish the
1276 slides until I suddenly discovered that the saved file could no longer
1277 be loaded into kpresenter. In the end I had to rewrite the slides
1278 three times, condensing the content until the talk became shorter and
1279 shorter. After the talk I was able to pinpoint the problem
&ndash;
1280 kpresenter wrote inline images in a way itself could not understand.
1281 Eventually that bug was fixed and kpresenter ended up being a great
1282 program to make slides. The point I
'm trying to make is that we
1283 expect a program to be able to load its own data files, and it is
1284 embarrassing to its developers if it can
't.
</p
>
1286 <p
>Did you ever experience a program failing to load its own data
1287 files from the desktop file browser? It is not a uncommon problem. A
1288 while back I discovered that the screencast recorder
1289 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1290 browser would refuse to open. No video player claimed to understand
1291 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1292 returning the application/ogg MIME type, which no video player I had
1293 installed listed as a MIME type they would understand. I asked for
1294 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1295 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1296 several video players to add video/ogg to their desktop files, to give
1297 the file browser an idea what to do about Ogg Theora files. After a
1298 while, the desktop file browsers in Debian started to handle the
1299 output from gtk-recordmydesktop properly.
</p
>
1301 <p
>But history repeats itself. A few days ago I tested the music
1302 system Rosegarden again, and I discovered that the KDE and xfce file
1303 browsers did not know what to do with the Rosegarden project files
1304 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1305 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1306 included in the next upload. To increase the chance of me remembering
1307 how to fix the problem next time some program fail to load its files
1308 from the file browser, here are some notes on how to fix it.
</p
>
1310 <p
>The file browsers in Debian in general operates on MIME types.
1311 There are two sources for the MIME type of a given file. The output from
1312 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1313 shared MIME type registry (under /usr/share/mime/). The file MIME
1314 type is mapped to programs supporting the MIME type, and this
1315 information is collected from
1316 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1317 desktop files
</a
> available in /usr/share/applications/. If there is
1318 one desktop file claiming support for the MIME type of the file, it is
1319 activated when asking to open a given file. If there are more, one
1320 can normally select which one to use by right-clicking on the file and
1321 selecting the wanted one using
'Open with
' or similar. In general
1322 this work well. But it depend on each program picking a good MIME
1324 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1325 MIME type registered with IANA
</a
>), file and/or the shared MIME
1326 registry recognizing the file and the desktop file to list the MIME
1327 type in its list of supported MIME types.
</p
>
1329 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1330 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1331 Shared MIME database
</a
> look like this:
</p
>
1333 <p
><blockquote
><pre
>
1334 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1335 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1336 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1337 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1338 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1339 &lt;glob pattern=
"*.rg
"/
&gt;
1340 &lt;/mime-type
&gt;
1341 &lt;/mime-info
&gt;
1342 </pre
></blockquote
></p
>
1344 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1345 (it is a gzipped XML file). Note, it is much better to use an
1346 official MIME type registered with IANA than it is to make up ones own
1347 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1349 <p
>The desktop file of the rosegarden program failed to list
1350 audio/x-rosegarden in its list of supported MIME types, causing the
1351 file browsers to have no idea what to do with *.rg files:
</p
>
1353 <p
><blockquote
><pre
>
1354 % grep Mime /usr/share/applications/rosegarden.desktop
1355 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1356 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1358 </pre
></blockquote
></p
>
1360 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1361 MimeType= line.
</p
>
1363 <p
>If you run into a file which fail to open the correct program when
1364 selected from the file browser, please check out the output from
1365 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1366 MIME type is registered somewhere under /usr/share/mime/ and check
1367 that some desktop file under /usr/share/applications/ is claiming
1368 support for this MIME type. If not, please report a bug to have it
1374 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1375 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1376 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1377 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1378 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1379 system
</a
> is a user-focused solution in Debian for handling hardware
1380 related packages. The idea is to have a database of mappings between
1381 hardware and packages, and pop up a dialog suggesting for the user to
1382 install the packages to use a given hardware dongle. Some use cases
1383 are when you insert a Yubikey, it proposes to install the software
1384 needed to control it; when you insert a braille reader list it
1385 proposes to install the packages needed to send text to the reader;
1386 and when you insert a ColorHug screen calibrator it suggests to
1387 install the driver for it. The system work well, and even have a few
1388 command line tools to install firmware packages and packages for the
1389 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1391 <p
>The system was initially written using aptdaemon, because I found
1392 good documentation and example code on how to use it. But aptdaemon
1393 is going away and is generally being replaced by
1394 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1395 so Isenkram needed a rewrite. And today, thanks to the great patch
1396 from my college Sunil Mohan Adapa in the FreedomBox project, the
1397 rewrite finally took place. I
've just uploaded a new version of
1398 Isenkram into Debian Unstable with the patch included, and the default
1399 for the background daemon is now to use PackageKit. To check it out,
1400 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1401 and see if it is recognised.
</p
>
1403 <p
>If you want to know what kind of packages isenkram would propose for
1404 the machine it is running on, you can check out the isenkram-lookup
1405 program. This is what it look like on a Thinkpad X230:
</p
>
1407 <p
><blockquote
><pre
>
1423 </pre
></blockquote
></p
>
1425 <p
>The hardware mappings come from several places. The preferred way
1426 is for packages to announce their hardware support using
1427 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1428 cross distribution appstream system
</a
>.
1430 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1431 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1436 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1437 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1438 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1439 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1440 <description><p
>Yesterday I updated the
1441 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1442 package in Debian
</a
> with a few patches sent to me by skilled and
1443 enterprising users. There were some nice user and visible changes.
1444 First of all, both desktop menu entries now work. A design flaw in
1445 one of the script made the history graph fail to show up (its PNG was
1446 dumped in ~/.xsession-errors) if no controlling TTY was available.
1447 The script worked when called from the command line, but not when
1448 called from the desktop menu. I changed this to look for a DISPLAY
1449 variable or a TTY before deciding where to draw the graph, and now the
1450 graph window pop up as expected.
</p
>
1452 <p
>The next new feature is a discharge rate estimator in one of the
1453 graphs (the one showing the last few hours). New is also the user of
1454 colours showing charging in blue and discharge in red. The percentages
1455 of this graph is relative to last full charge, not battery design
1458 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1460 <p
>The other graph show the entire history of the collected battery
1461 statistics, comparing it to the design capacity of the battery to
1462 visualise how the battery life time get shorter over time. The red
1463 line in this graph is what the previous graph considers
100 percent:
1465 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1467 <p
>In this graph you can see that I only charge the battery to
80
1468 percent of last full capacity, and how the capacity of the battery is
1469 shrinking. :(
</p
>
1471 <p
>The last new feature is in the collector, which now will handle
1472 more hardware models. On some hardware, Linux power supply
1473 information is stored in /sys/class/power_supply/ACAD/, while the
1474 collector previously only looked in /sys/class/power_supply/AC/. Now
1475 both are checked to figure if there is power connected to the
1478 <p
>If you are interested in how your laptop battery is doing, please
1480 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1481 in Debian unstable, or rebuild it on Jessie to get it working on
1482 Debian stable. :) The upstream source is available from
<a
1483 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1484 Patches are very welcome.
</p
>
1486 <p
>As usual, if you use Bitcoin and want to show your support of my
1487 activities, please send Bitcoin donations to my address
1488 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1493 <title>Debian now with ZFS on Linux included
</title>
1494 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1495 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1496 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1497 <description><p
>Today, after many years of hard work from many people,
1498 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1499 Debian. The package status can be seen on
1500 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1501 for zfs-linux
</a
>. and
1502 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1503 team status page
</a
>. If you want to help out, please join us.
1504 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1505 source code
</a
> is available via git on Alioth. It would also be
1506 great if you could help out with
1507 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1508 it is an important piece of the puzzle to get ZFS working.
</p
>
1513 <title>What is the best multimedia player in Debian?
</title>
1514 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1515 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1516 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1517 <description><p
><strong
>Where I set out to figure out which multimedia player in
1518 Debian claim support for most file formats.
</strong
></p
>
1520 <p
>A few years ago, I had a look at the media support for Browser
1521 plugins in Debian, to get an idea which plugins to include in Debian
1522 Edu. I created a script to extract the set of supported MIME types
1523 for each plugin, and used this to find out which multimedia browser
1524 plugin supported most file formats / media types.
1525 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1526 result
</a
> can still be seen on the Debian wiki, even though it have
1527 not been updated for a while. But browser plugins are less relevant
1528 these days, so I thought it was time to look at standalone
1531 <p
>A few days ago I was tired of VLC not being listed as a viable
1532 player when I wanted to play videos from the Norwegian National
1533 Broadcasting Company, and decided to investigate why. The cause is a
1534 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1535 desktop file
</a
>. In the process I wrote a script to compare the set
1536 of MIME types announced in the desktop file and the browser plugin,
1537 only to discover that there is quite a large difference between the
1538 two for VLC. This discovery made me dig up the script I used to
1539 compare browser plugins, and adjust it to compare desktop files
1540 instead, to try to figure out which multimedia player in Debian
1541 support most file formats.
</p
>
1543 <p
>The result can be seen on the Debian Wiki, as
1544 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1545 table listing all MIME types supported by one of the packages included
1546 in the table
</a
>, with the package supporting most MIME types being
1547 listed first in the table.
</p
>
1549 </p
>The best multimedia player in Debian? It is totem, followed by
1550 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1551 kmplayer. Time for the other players to update their announced MIME
1557 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1558 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1559 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1560 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1561 <description>A friend of mine made me aware of
1562 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1563 handheld computer which will be delivered with Debian preinstalled. I
1564 would love to get one of those for my birthday. :)
</p
>
1566 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1567 plugs and many others connectors, and include a full keyboard and a
5"
1568 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1569 day of battery life time, but I have not seen any independent tests
1570 confirming this. The vendor is still collecting preorders, and the
1571 last I heard last night was that
22 more orders were needed before
1572 production started.
</p
>
1574 <p
>As far as I know, this is the first handheld preinstalled with
1575 Debian. Please let me know if you know of any others. Is it the
1576 first computer being sold with Debian preinstalled?
</p
>
1581 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1582 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1583 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1584 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1585 <description><p
>During this weekends
1586 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1587 squashing party and developer gathering
</a
>, we decided to do our part
1588 to make sure there are good books about Debian available in Norwegian
1589 Bokmål, and got in touch with the people behind the
1590 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1591 project
</a
> to get started. If you want to help out, please start
1593 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1594 hosted weblate project page
</a
>, and get in touch using
1595 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1596 translators mailing list
</a
>. Please also check out
1597 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1598 contributors
</a
>.
</p
>
1600 <p
>The book is already available on paper in English, French and
1601 Japanese, and our goal is to get it available on paper in Norwegian
1602 Bokmål too. In addition to the paper edition, there are also EPUB and
1603 Mobi versions available. And there are incomplete translations
1604 available for many more languages.
</p
>
1609 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1610 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1611 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1612 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1613 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1614 packages in Debian, and was quite surprised with what I found. I use
1615 ZFS myself at home, but did not really expect many others to do so.
1616 But I might be wrong.
</p
>
1618 <p
>According to
1619 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1620 results for spl-linux
</a
>, there are
1019 Debian installations, or
1621 0.53% of the population, with the package installed. As far as I know
1622 the only use of the spl-linux package is as a support library for ZFS
1623 on Linux, so I use it here as proxy for measuring the number of ZFS
1624 installation on Linux in Debian. In the kFreeBSD variant of Debian
1625 the ZFS feature is already available, and there
1626 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1627 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1628 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1630 <p
>But even though the Debian project leader Lucas Nussbaum
1631 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1632 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1633 cleared, the package is still not in Debian. The package is again in
1634 the NEW queue. Several uploads have been rejected so far because the
1635 debian/copyright file was incomplete or wrong, but there is no reason
1636 to give up. The current status can be seen on
1637 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1638 team status page
</a
>, and
1639 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1640 source code
</a
> is available on Alioth.
</p
>
1642 <p
>As I want ZFS to be included in next version of Debian to make sure
1643 my home server can function in the future using only official Debian
1644 packages, and the current blocker is to get the debian/copyright file
1645 accepted by the FTP masters in Debian, I decided a while back to try
1646 to help out the team. This was the background for my blog post about
1647 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1648 updating and checking debian/copyright semi-automatically
</a
>, and I
1649 used the techniques I explored there to try to find any errors in the
1650 copyright file. It is not very easy to check every one of the around
1651 2000 files in the source package, but I hope we this time got it
1652 right. If you want to help out, check out the git source and try to
1653 find missing entries in the debian/copyright file.
</p
>
1658 <title>Full battery stats collector is now available in Debian
</title>
1659 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1660 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1661 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1662 <description><p
>Since this morning, the battery-stats package in Debian include an
1663 extended collector that will collect the complete battery history for
1664 later processing and graphing. The original collector store the
1665 battery level as percentage of last full level, while the new
1666 collector also record battery vendor, model, serial number, design
1667 full level, last full level and current battery level. This make it
1668 possible to predict the lifetime of the battery as well as visualise
1669 the energy flow when the battery is charging or discharging.
</p
>
1671 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1672 in the version
0.5.1 package in unstable. Get the new battery level graph
1673 and lifetime prediction by running:
1675 <p
><pre
>
1676 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1677 </pre
></p
>
1679 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1681 <p
>The flow in/out of the battery can be seen by running (no menu
1682 entry yet):
</p
>
1684 <p
><pre
>
1685 /usr/share/battery-stats/battery-stats-graph-flow
1686 </pre
></p
>
1688 <p
>I
'm not quite happy with the way the data is visualised, at least
1689 when there are few data points. The graphs look a bit better with a
1690 few years of data.
</p
>
1692 <p
>A while back one important feature I use in the battery stats
1693 collector broke in Debian. The scripts in
1694 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1695 suspect it happened when Jessie started using systemd, but I do not
1696 know. The issue is reported as
1697 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1698 pm-utils. I managed to work around it by adding an udev rule to call
1699 the collector script every time the power connector is connected and
1700 disconnected. With this fix in place it was finally time to make a
1701 new release of the package, and get it into Debian.
</p
>
1703 <p
>If you are interested in how your laptop battery is doing, please
1705 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1706 in Debian unstable, or rebuild it on Jessie to get it working on
1707 Debian stable. :) The upstream source is available from
1708 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1709 As always, patches are very welcome.
</p
>
1714 <title>Making battery measurements a little easier in Debian
</title>
1715 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1716 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1717 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1718 <description><p
>Back in September, I blogged about
1719 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1720 system I wrote to collect statistics about my laptop battery
</a
>, and
1721 how it showed the decay and death of this battery (now replaced). I
1722 created a simple deb package to handle the collection and graphing,
1723 but did not want to upload it to Debian as there were already
1724 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1725 package in Debian
</a
> that should do the same thing, and I did not see
1726 a point of uploading a competing package when battery-stats could be
1727 fixed instead. I reported a few bugs about its non-function, and
1728 hoped someone would step in and fix it. But no-one did.
</p
>
1730 <p
>I got tired of waiting a few days ago, and took matters in my own
1731 hands. The end result is that I am now the new upstream developer of
1732 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1733 battery-stats in Debian, and the package in Debian unstable is finally
1734 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1735 information provided by the Linux kernel. If you install the
1736 battery-stats package from unstable now, you will be able to get a
1737 graph of the current battery fill level, to get some idea about the
1738 status of the battery. The source package build and work just fine in
1739 Debian testing and stable (and probably oldstable too, but I have not
1740 tested). The default graph you get for that system look like this:
</p
>
1742 <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
>
1744 <p
>My plans for the future is to merge my old scripts into the
1745 battery-stats package, as my old scripts collected a lot more details
1746 about the battery. The scripts are merged into the upstream
1747 battery-stats git repository already, but I am not convinced they work
1748 yet, as I changed a lot of paths along the way. Will have to test a
1749 bit more before I make a new release.
</p
>
1751 <p
>I will also consider changing the file format slightly, as I
1752 suspect the way I combine several values into one field might make it
1753 impossible to know the type of the value when using it for processing
1754 and graphing.
</p
>
1756 <p
>If you would like I would like to keep an close eye on your laptop
1757 battery, check out the battery-stats package in
1758 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1760 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1761 I would love some help to improve the system further.
</p
>
1766 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1767 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1768 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1769 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1770 <description><p
>Making packages for Debian requires quite a lot of attention to
1771 details. And one of the details is the content of the
1772 debian/copyright file, which should list all relevant licenses used by
1773 the code in the package in question, preferably in
1774 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1775 readable DEP5 format
</a
>.
</p
>
1777 <p
>For large packages with lots of contributors it is hard to write
1778 and update this file manually, and if you get some detail wrong, the
1779 package is normally rejected by the ftpmasters. So getting it right
1780 the first time around get the package into Debian faster, and save
1781 both you and the ftpmasters some work.. Today, while trying to figure
1782 out what was wrong with
1783 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1784 zfsonlinux copyright file
</a
>, I decided to spend some time on
1785 figuring out the options for doing this job automatically, or at least
1786 semi-automatically.
</p
>
1788 <p
>Lucikly, there are at least two tools available for generating the
1789 file based on the code in the source package,
1790 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1791 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1792 not sure which one of them came first, but both seem to be able to
1793 create a sensible draft file. As far as I can tell, none of them can
1794 be trusted to get the result just right, so the content need to be
1795 polished a bit before the file is OK to upload. I found the debmake
1797 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1798 blog posts from
2014</a
>.
1800 <p
>To generate using debmake, use the -cc option:
1802 <p
><pre
>
1803 debmake -cc
> debian/copyright
1804 </pre
></p
>
1806 <p
>Note there are some problems with python and non-ASCII names, so
1807 this might not be the best option.
</p
>
1809 <p
>The cme option is based on a config parsing library, and I found
1811 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1812 blog post from
2015</a
>. To generate using cme, use the
'update
1813 dpkg-copyright
' option:
1815 <p
><pre
>
1816 cme update dpkg-copyright
1817 </pre
></p
>
1819 <p
>This will create or update debian/copyright. The cme tool seem to
1820 handle UTF-
8 names better than debmake.
</p
>
1822 <p
>When the copyright file is created, I would also like some help to
1823 check if the file is correct. For this I found two good options,
1824 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1825 to focus on license types and file matching, and is able to detect
1826 ineffective blocks in the copyright file. The latter reports missing
1827 copyright holders and years, but was confused by inconsistent license
1828 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1829 fix all issues reported by them before uploading. But I do not know
1830 if the tools and the ftpmasters agree on what is important to fix in a
1831 copyright file, so the package might still be rejected.
</p
>
1833 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1834 will read through the source and try to find all copyright statements.
1835 It is not comparing the result to the content of debian/copyright, but
1836 can be useful when verifying the content of the copyright file.
</p
>
1838 <p
>Are you aware of better tools in Debian to create and update
1839 debian/copyright file. Please let me know, or blog about it on
1840 planet.debian.org.
</p
>
1842 <p
>As usual, if you use Bitcoin and want to show your support of my
1843 activities, please send Bitcoin donations to my address
1844 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1846 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1847 on how to use licensecheck and cdbs to create a draft copyright file
1849 <p
><pre
>
1850 licensecheck --copyright -r `find * -type f` | \
1851 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1852 </pre
></p
>
1854 <p
>He mentioned that he normally check the generated file into the
1855 version control system to make it easier to discover license and
1856 copyright changes in the upstream source. I will try to do the same
1857 with my packages in the future.
</p
>
1859 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1860 against using -quiet for new users, so I removed it from the proposed
1861 command line.
</p
>
1866 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1867 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1868 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1869 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1870 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1871 is taking shape in Debian, and one provided feature is a very
1872 convenient way to tell you which package to install to make a given
1873 firmware file available when the kernel is looking for it. This can
1874 be done using apt-file too, but that is for someone else to blog
1877 <p
>Here is a small recipe to find the package with a given firmware
1878 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1879 picked from the set of firmware announced using appstream in Debian
1880 unstable. In general you would be looking for the firmware requested
1881 by the kernel during kernel module loading. To find the package
1882 providing the example file, do like this:
</p
>
1884 <blockquote
><pre
>
1885 % apt install appstream
1889 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1890 awk
'/Package:/ {print $
2}
'
1893 </pre
></blockquote
>
1895 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1896 appstream wiki
</a
> page to learn how to embed the package metadata in
1897 a way appstream can use.
</p
>
1899 <p
>This same approach can be used to find any package supporting a
1900 given MIME type. This is very useful when you get a file you do not
1901 know how to handle. First find the mime type using
<tt
>file
1902 --mime-type
</tt
>, and next look up the package providing support for
1903 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1904 and you can find all packages handling this type like this:
</p
>
1906 <blockquote
><pre
>
1907 % apt install appstream
1911 % appstreamcli what-provides mimetype image/svg+xml | \
1912 awk
'/Package:/ {print $
2}
'
1934 </pre
></blockquote
>
1936 <p
>I believe the MIME types are fetched from the desktop file for
1937 packages providing appstream metadata.
</p
>
1942 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1943 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1944 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1945 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1946 <description><p
>Most people seem not to realise that every time they walk around
1947 with the computerised radio beacon known as a mobile phone their
1948 position is tracked by the phone company and often stored for a long
1949 time (like every time a SMS is received or sent). And if their
1950 computerised radio beacon is capable of running programs (often called
1951 mobile apps) downloaded from the Internet, these programs are often
1952 also capable of tracking their location (if the app requested access
1953 during installation). And when these programs send out information to
1954 central collection points, the location is often included, unless
1955 extra care is taken to not send the location. The provided
1956 information is used by several entities, for good and bad (what is
1957 good and bad, depend on your point of view). What is certain, is that
1958 the private sphere and the right to free movement is challenged and
1959 perhaps even eradicated for those announcing their location this way,
1960 when they share their whereabouts with private and public
1963 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1965 <p
>The phone company logs provide a register of locations to check out
1966 when one want to figure out what the tracked person was doing. It is
1967 unavailable for most of us, but provided to selected government
1968 officials, company staff, those illegally buying information from
1969 unfaithful servants and crackers stealing the information. But the
1970 public information can be collected and analysed, and a free software
1971 tool to do so is called
1972 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1973 discovered it when I read
1974 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1975 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1976 November
2014, and decided to check if it was available in Debian.
1977 The python program was in Debian, but
1978 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1979 Debian
</a
> was completely broken and practically unmaintained. I
1980 uploaded a new version which did not work quite right, but did not
1981 have time to fix it then. This Christmas I decided to finally try to
1982 get Creepy operational in Debian. Now a fixed version is available in
1983 Debian unstable and testing, and almost all Debian specific patches
1985 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1987 <p
>The Creepy program visualises geolocation information fetched from
1988 Twitter, Instagram, Flickr and Google+, and allow one to get a
1989 complete picture of every social media message posted recently in a
1990 given area, or track the movement of a given individual across all
1991 these services. Earlier it was possible to use the search API of at
1992 least some of these services without identifying oneself, but these
1993 days it is impossible. This mean that to use Creepy, you need to
1994 configure it to log in as yourself on these services, and provide
1995 information to them about your search interests. This should be taken
1996 into account when using Creepy, as it will also share information
1997 about yourself with the services.
</p
>
1999 <p
>The picture above show the twitter messages sent from (or at least
2000 geotagged with a position from) the city centre of Oslo, the capital
2001 of Norway. One useful way to use Creepy is to first look at
2002 information tagged with an area of interest, and next look at all the
2003 information provided by one or more individuals who was in the area.
2004 I tested it by checking out which celebrity provide their location in
2005 twitter messages by checkout out who sent twitter messages near a
2006 Norwegian TV station, and next could track their position over time,
2007 making it possible to locate their home and work place, among other
2008 things. A similar technique have been
2009 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2010 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2011 tool to discover lying governments, and a useful tool to help people
2012 understand the value of the private information they provide to the
2015 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2016 it depend on several python modules currently missing in Jessie (at
2017 least python-instagram, python-flickrapi and
2018 python-requests-toolbelt).
</p
>
2020 <p
>(I have uploaded
2021 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2022 screenshots.debian.net
</a
> and licensed it under the same terms as the
2023 Creepy program in Debian.)
</p
>
2028 <title>Always download Debian packages using Tor - the simple recipe
</title>
2029 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2030 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2031 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2032 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2033 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2034 that those listening on the Internet lines would have good reason to
2035 believe a computer have a given security hole
</a
> if it download a
2036 security fix from a Debian mirror. This is a good reason to always
2037 use encrypted connections to the Debian mirror, to make sure those
2038 listening do not know which IP address to attack. In August, Richard
2039 Hartmann observed that encryption was not enough, when it was possible
2040 to interfere download size to security patches or the fact that
2041 download took place shortly after a security fix was released, and
2042 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2043 to always use Tor to download packages from the Debian mirror
</a
>. He
2044 was not the first to propose this, as the
2045 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2046 package by Tim Retout already existed to make it easy to convince apt
2047 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2048 aware of that package when I read the blog post from Richard.
</p
>
2050 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2051 sysadmins, and he set up a Tor hidden service on one of the central
2052 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2053 it possible to download packages directly between two tor nodes,
2054 making sure the network traffic always were encrypted.
</p
>
2056 <p
>Here is a short recipe for enabling this on your machine, by
2057 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2058 urls with tor+http and tor+https, and using the hidden service instead
2059 of the official Debian mirror site. I recommend installing
2060 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2061 done in /etc/.
</p
>
2063 <blockquote
><pre
>
2064 apt install apt-transport-tor
2065 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2066 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2067 </pre
></blockquote
>
2069 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2070 the sed commands for these too. The sed command is assuming your are
2071 using the ftp.debian.org Debian mirror. Adjust the command (or just
2072 edit the file manually) to match your mirror.
</p
>
2074 <p
>This work in Debian Jessie and later. Note that tools like
2075 <tt
>apt-file
</tt
> only recently started using the apt transport
2076 system, and do not work with these tor+http URLs. For
2077 <tt
>apt-file
</tt
> you need the version currently in experimental,
2078 which need a recent apt version currently only in unstable. So if you
2079 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2081 <p
>Another advantage from this change is that your machine will start
2082 using Tor regularly and at fairly random intervals (every time you
2083 update the package lists or upgrade or install a new package), thus
2084 masking other Tor traffic done from the same machine. Using Tor will
2085 become normal for the machine in question.
</p
>
2087 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2088 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2089 enabled. It would be great if it was the default on any Debian
2095 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2096 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2097 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2098 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2099 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2100 call the car license plate numbers in those days. I would write the
2101 numbers down in my little book and compare notes with the other kids
2102 to see how many region codes we had seen and if we had seen some
2103 exotic or special region codes and numbers. It was a fun game to pass
2104 time, as we kids have plenty of it.
</p
>
2106 <p
>A few days I came across
2107 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2108 project
</a
>, a free software project to automatically discover and
2109 report license plates in images and video streams, and provide the
2110 "car numbers
" in a machine readable format. I
've been looking for
2111 such system for a while now, because I believe it is a bad idea that the
2112 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2113 number plate recognition
</a
> tool only is available in the hands of
2114 the powerful, and want it to be available also for the powerless to
2115 even the score when it comes to surveillance and sousveillance. I
2116 discovered the developer
2117 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2118 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2119 help him get it into shape to get the package uploaded into the Debian
2122 <p
>Today we finally managed to get the package into shape and uploaded
2123 it into Debian, where it currently
2124 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2125 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2127 <p
>I guess you are wondering why on earth such tool would be useful
2128 for the common folks, ie those not running a large government
2129 surveillance system? Well, I plan to put it in a computer on my bike
2130 and in my car, tracking the cars nearby and allowing me to be notified
2131 when number plates on my watch list are discovered. Another use case
2132 was suggested by a friend of mine, who wanted to set it up at his home
2133 to open the car port automatically when it discovered the plate on his
2134 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2135 capable of placing his license plate number of a piece of cardboard to
2136 open his car port, men replied that it was always unlocked anyway. I
2137 guess for such use case it make sense. I am sure there are other use
2138 cases too, for those with imagination and a vision.
</p
>
2140 <p
>If you want to build your own version of the Debian package, check
2141 out the upstream git source and symlink ./distros/debian to ./debian/
2142 before running
"debuild
" to build the source. Or wait a bit until the
2143 package show up in unstable.
</p
>
2148 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2149 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2150 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2151 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2152 <description><p
>Around three years ago, I created
2153 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2154 system
</a
> to get a more practical solution in Debian for handing
2155 hardware related packages. A GUI system in the isenkram package will
2156 present a pop-up dialog when some hardware dongle supported by
2157 relevant packages in Debian is inserted into the machine. The same
2158 lookup mechanism to detect packages is available as command line
2159 tools in the isenkram-cli package. In addition to mapping hardware,
2160 it will also map kernel firmware files to packages and make it easy to
2161 install needed firmware packages automatically. The key for this
2162 system to work is a good way to map hardware to packages, in other
2163 words, allow packages to announce what hardware they will work
2166 <p
>I started by providing data files in the isenkram source, and
2167 adding code to download the latest version of these data files at run
2168 time, to ensure every user had the most up to date mapping available.
2169 I also added support for storing the mapping in the Packages file in
2170 the apt repositories, but did not push this approach because while I
2171 was trying to figure out how to best store hardware/package mappings,
2172 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2173 appstream system
</a
> was announced. I got in touch and suggested to
2174 add the hardware mapping into that data set to be able to use
2175 appstream as a data source, and this was accepted at least for the
2176 Debian version of appstream.
</p
>
2178 <p
>A few days ago using appstream in Debian for this became possible,
2179 and today I uploaded a new version
0.20 of isenkram adding support for
2180 appstream as a data source for mapping hardware to packages. The only
2181 package so far using appstream to announce its hardware support is my
2182 pymissile package. I got help from Matthias Klumpp with figuring out
2183 how do add the required
2184 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2185 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2186 this content:
</p
>
2188 <blockquote
><pre
>
2189 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2190 &lt;component
&gt;
2191 &lt;id
&gt;pymissile
&lt;/id
&gt;
2192 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2193 &lt;name
&gt;pymissile
&lt;/name
&gt;
2194 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2195 &lt;description
&gt;
2197 Pymissile provides a curses interface to control an original
2198 Marks and Spencer / Striker USB Missile Launcher, as well as a
2199 motion control script to allow a webcamera to control the
2202 &lt;/description
&gt;
2203 &lt;provides
&gt;
2204 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2205 &lt;/provides
&gt;
2206 &lt;/component
&gt;
2207 </pre
></blockquote
>
2209 <p
>The key for isenkram is the component/provides/modalias value,
2210 which is a glob style match rule for hardware specific strings
2211 (modalias strings) provided by the Linux kernel. In this case, it
2212 will map to all USB devices with vendor code
1130 and product code
2215 <p
>Note, it is important that the license of all the metadata files
2216 are compatible to have permissions to aggregate them into archive wide
2217 appstream files. Matthias suggested to use MIT or BSD licenses for
2218 these files. A challenge is figuring out a good id for the data, as
2219 it is supposed to be globally unique and shared across distributions
2220 (in other words, best to coordinate with upstream what to use). But
2221 it can be changed later or, so we went with the package name as
2222 upstream for this project is dormant.
</p
>
2224 <p
>To get the metadata file installed in the correct location for the
2225 mirror update scripts to pick it up and include its content the
2226 appstream data source, the file must be installed in the binary
2227 package under /usr/share/appdata/. I did this by adding the following
2228 line to debian/pymissile.install:
</p
>
2230 <blockquote
><pre
>
2231 debian/pymissile.metainfo.xml usr/share/appdata
2232 </pre
></blockquote
>
2234 <p
>With that in place, the command line tool isenkram-lookup will list
2235 all packages useful on the current computer automatically, and the GUI
2236 pop-up handler will propose to install the package not already
2237 installed if a hardware dongle is inserted into the machine in
2240 <p
>Details of the modalias field in appstream is available from the
2241 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2243 <p
>To locate the modalias values of all hardware present in a machine,
2244 try running this command on the command line:
</p
>
2246 <blockquote
><pre
>
2247 cat $(find /sys/devices/|grep modalias)
2248 </pre
></blockquote
>
2250 <p
>To learn more about the isenkram system, please check out
2251 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2252 blog posts tagged isenkram
</a
>.
</p
>
2257 <title>The GNU General Public License is not magic pixie dust
</title>
2258 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2259 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2260 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2261 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2262 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2263 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2264 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2265 I quote the blog post from Paul in full here with his permission:
<p
>
2269 <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
>
2272 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2274 The first step is to choose a
2275 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2278 The next step is, when someone fails to follow that copyleft license,
2279 <b
>it must be enforced
</b
><br/
>
2281 and its a simple fact of our modern society that such type of
2284 is incredibly expensive to do and incredibly difficult to do.
2287 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2288 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2289 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2290 0x57</a
></small
></p
>
2292 <p
>As the Debian Website
2293 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2294 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2295 imply, public domain and permissively licensed software can lead to
2296 the production of more proprietary software as people discover useful
2297 software, extend it and or incorporate it into their hardware or
2298 software products. Copyleft licenses such as the GNU GPL were created
2299 to close off this avenue to the production of proprietary software but
2300 such licenses are not enough. With the ongoing adoption of Free
2301 Software by individuals and groups, inevitably the community
's
2302 expectations of license compliance are violated, usually out of
2303 ignorance of the way Free Software works, but not always. As Karen
2304 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2305 Freedom
">FaiF
</a
>
2306 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2307 copyleft is nothing if no-one is willing and able to stand up in court
2308 to protect it. The reality of today
's world is that legal
2309 representation is expensive, difficult and time consuming. With
2310 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2311 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2312 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2313 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2314 of the Linux project, Debian and other groups against GPL violations.
2315 In March the SFC supported a
2316 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2317 by Christoph Hellwig
</a
> against VMware for refusing to
2318 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2319 with the GPL
</a
> in relation to their use of parts of the Linux
2320 kernel. Since then two of their sponsors pulled corporate funding and
2322 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2323 or cancelled their talks
</a
>. As a result they have decided to rely
2324 less on corporate funding and more on the broad community of
2325 individuals who support Free Software and copyleft. So the SFC has
2326 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2327 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2328 a community of folks who stand up for copyleft and the GPL by
2329 supporting their work on promoting and supporting copyleft and Free
2332 <p
>If you support Free Software,
2333 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2334 what the SFC do, agree with their
2335 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2336 principles
</a
>, are happy about their
2337 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2338 work on a project that is an SFC
2339 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2340 just want to stand up for copyleft, please join
2341 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2342 Allan Webber
</a
>,
2343 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2345 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2346 Bacon
</a
>, myself and
2347 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2349 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2350 next week your donation will be
2351 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2352 by an anonymous donor. Please also consider asking your employer to
2353 match your donation or become a sponsor of SFC. Don
't forget to
2354 spread the word about your support for SFC via email, your blog and or
2355 social media accounts.
</p
>
2359 <p
>I agree with Paul on this topic and just signed up as a Supporter
2360 of Software Freedom Conservancy myself. Perhaps you should be a
2361 supporter too?
</p
>
2366 <title>PGP key transition statement for key EE4E02F9
</title>
2367 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2369 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2370 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2371 set it up properly. I wanted to generate it offline and have it
2372 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2373 smart card
</a
> for daily use, and learning how to do it and finding
2374 time to sit down with an offline machine almost took forever. But
2375 finally I
've been able to complete the process, and have now moved
2376 from my old GPG key to a new GPG key. See
2377 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2378 full transition statement, signed with both my old and new key
</a
> for
2379 the details. This is my new key:
</p
>
2382 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2383 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2384 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2385 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2386 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2387 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2388 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2391 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2392 my old key.
</p
>
2394 <p
>If you signed my old key
2395 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2396 I
'd very much appreciate a signature on my new key, details and
2397 instructions in the transition statement. I m happy to reciprocate if
2398 you have a similarly signed transition statement to present.
</p
>
2403 <title>The life and death of a laptop battery
</title>
2404 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2405 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2406 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2407 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2408 But this do not last. The last few laptops gave me a feeling that
2409 within a year, the life time is just a fraction of what it used to be,
2410 and it slowly become painful to use the laptop without power connected
2411 all the time. Because of this, when I got a new Thinkpad X230 laptop
2412 about two years ago, I decided to monitor its battery state to have
2413 more hard facts when the battery started to fail.
</p
>
2415 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2417 <p
>First I tried to find a sensible Debian package to record the
2418 battery status, assuming that this must be a problem already handled
2419 by someone else. I found
2420 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2421 which collects statistics from the battery, but it was completely
2422 broken. I sent a few suggestions to the maintainer, but decided to
2423 write my own collector as a shell script while I waited for feedback
2425 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2426 blog post about the battery development on a MacBook Air
</a
> I also
2428 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2429 available in Debian.
</p
>
2431 <p
>I started my collector
2013-
07-
15, and it has been collecting
2432 battery stats ever since. Now my
2433 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2434 measurements, from the time the battery was working great until now,
2435 when it is unable to charge above
7% of original capacity. My
2436 collector shell script is quite simple and look like this:
</p
>
2441 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2443 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2444 logfile=/var/log/hjemmenett-battery-status.log
2446 files=
"manufacturer model_name technology serial_number \
2447 energy_full energy_full_design energy_now cycle_count status
"
2449 if [ ! -e
"$logfile
" ] ; then
2451 printf
"timestamp,
"
2453 printf
"%s,
" $f
2456 )
> "$logfile
"
2460 # Print complete message in one echo call, to avoid race condition
2461 # when several log processes run in parallel.
2462 msg=$(printf
"%s,
" $(date +%s); \
2463 for f in $files; do \
2464 printf
"%s,
" $(cat $f); \
2466 echo
"$msg
"
2469 cd /sys/class/power_supply
2472 (cd $bat
&& log_battery
>> "$logfile
")
2476 <p
>The script is called when the power management system detect a
2477 change in the power status (power plug in or out), and when going into
2478 and out of hibernation and suspend. In addition, it collect a value
2479 every
10 minutes. This make it possible for me know when the battery
2480 is discharging, charging and how the maximum charge change over time.
2481 The code for the Debian package
2482 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2483 available on github
</a
>.
</p
>
2485 <p
>The collected log file look like this:
</p
>
2488 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2489 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2491 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2492 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2495 <p
>I wrote a small script to create a graph of the charge development
2496 over time. This graph depicted above show the slow death of my laptop
2499 <p
>But why is this happening? Why are my laptop batteries always
2500 dying in a year or two, while the batteries of space probes and
2501 satellites keep working year after year. If we are to believe
2502 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2503 University
</a
>, the cause is me charging the battery whenever I have a
2504 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2505 all the time, but to stay below
90% of full charge most of the time.
2506 I
've been told that the Tesla electric cars
2507 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2508 the charge of their batteries to
80%
</a
>, with the option to charge to
2509 100% when preparing for a longer trip (not that I would want a car
2510 like Tesla where rights to privacy is abandoned, but that is another
2511 story), which I guess is the option we should have for laptops on
2512 Linux too.
</p
>
2514 <p
>Is there a good and generic way with Linux to tell the battery to
2515 stop charging at
80%, unless requested to charge to
100% once in
2516 preparation for a longer trip? I found
2517 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2518 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2519 80%
</a
>, but could not get it to work (kernel module refused to
2522 <p
>I wonder why the battery capacity was reported to be more than
100%
2523 at the start. I also wonder why the
"full capacity
" increases some
2524 times, and if it is possible to repeat the process to get the battery
2525 back to design capacity. And I wonder if the discharge and charge
2526 speed change over time, or if this stay the same. I did not yet try
2527 to write a tool to calculate the derivative values of the battery
2528 level, but suspect some interesting insights might be learned from
2531 <p
>Update
2015-
09-
24: I got a tip to install the packages
2532 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2533 packages instead of the tp-smapi-dkms package I had tried to use
2534 initially, and use
'tlp setcharge
40 80' to change when charging start
2535 and stop. I
've done so now, but expect my existing battery is toast
2536 and need to be replaced. The proposal is unfortunately Thinkpad
2542 <title>New laptop - some more clues and ideas based on feedback
</title>
2543 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2545 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2546 <description><p
>Several people contacted me after my previous blog post about my
2547 need for a new laptop, and provided very useful feedback. I wish to
2548 thank every one of these. Several pointed me to the possibility of
2549 fixing my X230, and I am already in the process of getting Lenovo to
2550 do so thanks to the on site, next day support contract covering the
2551 machine. But the battery is almost useless (I expect to replace it
2552 with a non-official battery) and I do not expect the machine to live
2553 for many more years, so it is time to plan its replacement. If I did
2554 not have a support contract, it was suggested to find replacement parts
2555 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2556 might present a language barrier as I do not understand French.
</p
>
2558 <p
>One tip I got was to use the
2559 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2560 compare laptop models. It seem to have more models available than
2561 prisjakt.no. Another tip I got from someone I know have similar
2562 keyboard preferences was that the HP EliteBook
840 keyboard is not
2563 very good, and this matches my experience with earlier EliteBook
2564 keyboards I tested. Because of this, I will not consider it any further.
2566 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2567 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2568 (which is missing from the X240), and is working fairly well with
2569 Debian Sid/Unstable according to
2570 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2571 got on the keyboard quality are not consistent. Some say the keyboard
2572 is good, others say it is ok, while others say it is not very good.
2573 Those with experience from X41 and and X60 agree that the X250
2574 keyboard is not as good as those trusty old laptops, and suggest I
2575 keep and fix my X230 instead of upgrading, or get a used X230 to
2576 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2577 activity and battery status, which is very convenient on my X230. I
'm
2578 also told that the CPU fan is running very often, making it a bit
2579 noisy. In any case, the X250 do not work out of the box with Debian
2580 Stable/Jessie, one of my requirements.
</p
>
2582 <p
>I have also gotten a few vendor proposals, one was
2583 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2584 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2585 The latter look very attractive to me.
</p
>
2587 <p
>Again, thank you all for the very useful feedback. It help a lot
2588 as I keep looking for a replacement.
</p
>
2590 <p
>Update
2015-
07-
06: I was recommended to check out the
2591 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2593 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2594 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2599 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2600 <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>
2601 <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>
2602 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2603 <description><p
>My primary work horse laptop is failing, and will need a
2604 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2605 started flickering yesterday, and I suspect the cause is a broken
2606 cable, as changing the angle of the screen some times get rid of the
2607 flickering.
</p
>
2609 <p
>My requirements have not really changed since I bought it, and is
2611 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2612 described them in
2013</a
>. The last time I bought a laptop, I had
2614 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2615 where I could select at least a few of the requirements (mouse pin,
2616 wifi, weight) and go through the rest manually. Three button mouse
2617 and a good keyboard is not available as an option, and all the three
2618 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2619 G2) lack three mouse buttons). It is also unclear to me how good the
2620 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2621 the keyboard, even if the quality and robustness in the X series have
2622 deteriorated since X41.
</p
>
2624 <p
>I wonder how I can find a sensible laptop when none of the options
2625 seem sensible to me? Are there better services around to search the
2626 set of available laptops for features? Please send me an email if you
2627 have suggestions.
</p
>
2629 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2630 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2631 of endorsed hardware
</a
>, which is useful background information.
</p
>
2636 <title>How to stay with sysvinit in Debian Jessie
</title>
2637 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2638 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2639 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2640 <description><p
>By now, it is well known that Debian Jessie will not be using
2641 sysvinit as its boot system by default. But how can one keep using
2642 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2644 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2645 Schubert
</a
> and
2646 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2649 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2650 keep sysvinit as your boot system, create a file
2651 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2652 you upgrade:
</p
>
2654 <p
><blockquote
><pre
>
2655 Package: systemd-sysv
2656 Pin: release o=Debian
2658 </pre
></blockquote
><p
>
2660 <p
>This file content will tell apt and aptitude to not consider
2661 installing systemd-sysv as part of any installation and upgrade
2662 solution when resolving dependencies, and thus tell it to avoid
2663 systemd as a default boot system. The end result should be that the
2664 upgraded system keep using sysvinit.
</p
>
2666 <p
>If you are installing Jessie for the first time, there is no way to
2667 get sysvinit installed by default (debootstrap used by
2668 debian-installer have no option for this), but one can tell the
2669 installer to switch to sysvinit before the first boot. Either by
2670 using a kernel argument to the installer, or by adding a line to the
2671 preseed file used. First, the kernel command line argument:
2673 <p
><blockquote
><pre
>
2674 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2675 </pre
></blockquote
><p
>
2677 <p
>Next, the line to use in a preseed file:
</p
>
2679 <p
><blockquote
><pre
>
2680 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2681 </pre
></blockquote
><p
>
2683 <p
>One can of course also do this after the first boot by installing
2684 the sysvinit-core package.
</p
>
2686 <p
>I recommend only using sysvinit if you really need it, as the
2687 sysvinit boot sequence in Debian have several hardware specific bugs
2688 on Linux caused by the fact that it is unpredictable when hardware
2689 devices show up during boot. But on the other hand, the new default
2690 boot system still have a few rough edges I hope will be fixed before
2691 Jessie is released.
</p
>
2693 <p
>Update
2014-
11-
26: Inspired by
2694 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2695 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2701 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2702 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2703 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2704 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2705 <description><p
>The right to communicate with your friends and family in private,
2706 without anyone snooping, is a right every citicen have in a liberal
2707 democracy. But this right is under serious attack these days.
</p
>
2709 <p
>A while back it occurred to me that one way to make the dragnet
2710 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2711 the whisleblower Snowden) more expensive for Internet email,
2712 is to deliver all email using SMTP via Tor. Such SMTP option would be
2713 a nice addition to the FreedomBox project if we could send email
2714 between FreedomBox machines without leaking metadata about the emails
2715 to the people peeking on the wire. I
2716 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2717 this on the FreedomBox project mailing list in October
</a
> and got a
2718 lot of useful feedback and suggestions. It also became obvious to me
2719 that this was not a novel idea, as the same idea was tested and
2720 documented by Johannes Berg as early as
2006, and both
2721 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2722 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2723 propose a similar method / protocol to pass emails between users.
</p
>
2725 <p
>To implement such system one need to set up a Tor hidden service
2726 providing the SMTP protocol on port
25, and use email addresses
2727 looking like username@hidden-service-name.onion. With such addresses
2728 the connections to port
25 on hidden-service-name.onion using Tor will
2729 go to the correct SMTP server. To do this, one need to configure the
2730 Tor daemon to provide the hidden service and the mail server to accept
2731 emails for this .onion domain. To learn more about Exim configuration
2732 in Debian and test the design provided by Johannes Berg in his FAQ, I
2733 set out yesterday to create a Debian package for making it trivial to
2734 set up such SMTP over Tor service based on Debian. Getting it to work
2735 were fairly easy, and
2736 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2737 source code for the Debian package
</a
> is available from github. I
2738 plan to move it into Debian if further testing prove this to be a
2739 useful approach.
</p
>
2741 <p
>If you want to test this, set up a blank Debian machine without any
2742 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2743 get rid of exim4). Install tor, clone the git repository mentioned
2744 above, build the deb and install it on the machine. Next, run
2745 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2746 the instructions to get the service up and running. Restart tor and
2747 exim when it is done, and test mail delivery using swaks like
2750 <p
><blockquote
><pre
>
2751 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2752 --to fbx@dutlqrrmjhtfa3vp.onion
2753 </pre
></blockquote
></p
>
2755 <p
>This will test the SMTP delivery using tor. Replace the email
2756 address with your own address to test your server. :)
</p
>
2758 <p
>The setup procedure is still to complex, and I hope it can be made
2759 easier and more automatic. Especially the tor setup need more work.
2760 Also, the package include a tor-smtp tool written in C, but its task
2761 should probably be rewritten in some script language to make the deb
2762 architecture independent. It would probably also make the code easier
2763 to review. The tor-smtp tool currently need to listen on a socket for
2764 exim to talk to it and is started using xinetd. It would be better if
2765 no daemon and no socket is needed. I suspect it is possible to get
2766 exim to run a command line tool for delivery instead of talking to a
2767 socket, and hope to figure out how in a future version of this
2770 <p
>Until I wipe my test machine, I can be reached using the
2771 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2772 SMTorP. :)
</p
>
2777 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2778 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2780 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2781 <description><p
>If you ever had to moderate a mailman list, like the ones on
2782 alioth.debian.org, you know the web interface is fairly slow to
2783 operate. First you visit one web page, enter the moderation password
2784 and get a new page shown with a list of all the messages to moderate
2785 and various options for each email address. This take a while for
2786 every list you moderate, and you need to do it regularly to do a good
2787 job as a list moderator. But there is a quick alternative,
2788 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2789 listadmin program
</a
>. It allow you to check lists for new messages
2790 to moderate in a fraction of a second. Here is a test run on two
2791 lists I recently took over:
</p
>
2793 <p
><blockquote
><pre
>
2794 % time listadmin xiph
2795 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2796 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2802 </pre
></blockquote
></p
>
2804 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2805 there are no message in the moderation queue. Every morning I
2806 currently moderate
68 mailman lists, and it normally take around two
2807 minutes. When I took over the two pkg-xiph lists above a few days
2808 ago, there were
400 emails waiting in the moderator queue. It took me
2809 less than
15 minutes to process them all using the listadmin
2812 <p
>If you install
2813 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2814 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2815 with content like this, the moderation task is a breeze:
</p
>
2817 <p
><blockquote
><pre
>
2818 username username@example.org
2821 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2824 adminurl https://{domain}/mailman/admindb/{list}
2825 mailman-list@lists.example.com
2828 other-list@otherserver.example.org
2829 </pre
></blockquote
></p
>
2831 <p
>There are other options to set as well. Check the manual page to
2832 learn the details.
</p
>
2834 <p
>If you are forced to moderate lists on a mailman installation where
2835 the SSL certificate is self signed or not properly signed by a
2836 generally accepted signing authority, you can set a environment
2837 variable when calling listadmin to disable SSL verification:
</p
>
2839 <p
><blockquote
><pre
>
2840 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2841 </pre
></blockquote
></p
>
2843 <p
>If you want to moderate a subset of the lists you take care of, you
2844 can provide an argument to the listadmin script like I do in the
2845 initial screen dump (the xiph argument). Using an argument, only
2846 lists matching the argument string will be processed. This make it
2847 quick to accept messages if you notice the moderation request in your
2850 <p
>Without the listadmin program, I would never be the moderator of
68
2851 mailing lists, as I simply do not have time to spend on that if the
2852 process was any slower. The listadmin program have saved me hours of
2853 time I could spend elsewhere over the years. It truly is nice free
2856 <p
>As usual, if you use Bitcoin and want to show your support of my
2857 activities, please send Bitcoin donations to my address
2858 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2860 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2861 configuration example. Also, I
've been told that the
2862 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2868 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2869 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2870 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2871 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2872 <description><p
>When PXE installing laptops with Debian, I often run into the
2873 problem that the WiFi card require some firmware to work properly.
2874 And it has been a pain to fix this using preseeding in Debian.
2875 Normally something more is needed. But thanks to
2876 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2877 package
</a
> and its recent tasksel extension, it has now become easy
2878 to do this using simple preseeding.
</p
>
2880 <p
>The isenkram-cli package provide tasksel tasks which will install
2881 firmware for the hardware found in the machine (actually, requested by
2882 the kernel modules for the hardware). (It can also install user space
2883 programs supporting the hardware detected, but that is not the focus
2884 of this story.)
</p
>
2886 <p
>To get this working in the default installation, two preeseding
2887 values are needed. First, the isenkram-cli package must be installed
2888 into the target chroot (aka the hard drive) before tasksel is executed
2889 in the pkgsel step of the debian-installer system. This is done by
2890 preseeding the base-installer/includes debconf value to include the
2891 isenkram-cli package. The package name is next passed to debootstrap
2892 for installation. With the isenkram-cli package in place, tasksel
2893 will automatically use the isenkram tasks to detect hardware specific
2894 packages for the machine being installed and install them, because
2895 isenkram-cli contain tasksel tasks.
</p
>
2897 <p
>Second, one need to enable the non-free APT repository, because
2898 most firmware unfortunately is non-free. This is done by preseeding
2899 the apt-mirror-setup step. This is unfortunate, but for a lot of
2900 hardware it is the only option in Debian.
</p
>
2902 <p
>The end result is two lines needed in your preseeding file to get
2903 firmware installed automatically by the installer:
</p
>
2905 <p
><blockquote
><pre
>
2906 base-installer base-installer/includes string isenkram-cli
2907 apt-mirror-setup apt-setup/non-free boolean true
2908 </pre
></blockquote
></p
>
2910 <p
>The current version of isenkram-cli in testing/jessie will install
2911 both firmware and user space packages when using this method. It also
2912 do not work well, so use version
0.15 or later. Installing both
2913 firmware and user space packages might give you a bit more than you
2914 want, so I decided to split the tasksel task in two, one for firmware
2915 and one for user space programs. The firmware task is enabled by
2916 default, while the one for user space programs is not. This split is
2917 implemented in the package currently in unstable.
</p
>
2919 <p
>If you decide to give this a go, please let me know (via email) how
2920 this recipe work for you. :)
</p
>
2922 <p
>So, I bet you are wondering, how can this work. First and
2923 foremost, it work because tasksel is modular, and driven by whatever
2924 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2925 isenkram-cli package place two files for tasksel to find. First there
2926 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2928 <p
><blockquote
><pre
>
2929 Task: isenkram-packages
2931 Description: Hardware specific packages (autodetected by isenkram)
2932 Based on the detected hardware various hardware specific packages are
2934 Test-new-install: show show
2936 Packages: for-current-hardware
2938 Task: isenkram-firmware
2940 Description: Hardware specific firmware packages (autodetected by isenkram)
2941 Based on the detected hardware various hardware specific firmware
2942 packages are proposed.
2943 Test-new-install: mark show
2945 Packages: for-current-hardware-firmware
2946 </pre
></blockquote
></p
>
2948 <p
>The key parts are Test-new-install which indicate how the task
2949 should be handled and the Packages line referencing to a script in
2950 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2951 list of packages to install. The for-current-hardware-firmware script
2952 look like this to list relevant firmware for the machine:
2954 <p
><blockquote
><pre
>
2957 PATH=/usr/sbin:$PATH
2959 isenkram-autoinstall-firmware -l
2960 </pre
></blockquote
></p
>
2962 <p
>With those two pieces in place, the firmware is installed by
2963 tasksel during the normal d-i run. :)
</p
>
2965 <p
>If you want to test what tasksel will install when isenkram-cli is
2966 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2967 --new-install
</tt
> to get the list of packages that tasksel would
2970 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2971 pilots in testing this feature, as isenkram is used there now to
2972 install firmware, replacing the earlier scripts.
</p
>
2977 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2978 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2979 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2980 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2981 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2982 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2983 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2984 on a screen normally showing the bread types and prizes:
</p
>
2986 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2988 <p
>If it had booted as it was supposed to, I would never had known
2989 about this hidden Linux installation. It is interesting what
2990 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
2995 <title>New lsdvd release version
0.17 is ready
</title>
2996 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
2997 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
2998 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
2999 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3000 got a new set of developers a few weeks ago, after the original
3001 developer decided to step down and pass the project to fresh blood.
3002 This project is now maintained by Petter Reinholdtsen and Steve
3005 <p
>I just wrapped up
3006 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3007 new lsdvd release
</a
>, available in git or from
3008 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3009 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3014 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3015 <li
>Check for garbage in the program chains, which indicate that a track is
3016 non-existant, to work around additional copy protection
</li
>
3017 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3018 <li
>Fix pallete display of first entry
</li
>
3019 <li
>Fix include orders
</li
>
3020 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3021 <li
>Fix the chapter count
</li
>
3022 <li
>Make sure the array size and the array limit used when initialising
3023 the palette size is the same.
</li
>
3024 <li
>Fix array printing.
</li
>
3025 <li
>Correct subsecond calculations.
</li
>
3026 <li
>Add sector information to the output format.
</li
>
3027 <li
>Clean up code to be closer to ANSI C and compile without warnings
3028 with more GCC compiler warnings.
</li
>
3032 <p
>This change bring together patches for lsdvd in use in various
3033 Linux and Unix distributions, as well as patches submitted to the
3034 project the last nine years. Please check it out. :)
</p
>
3039 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3040 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3042 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3043 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3044 project
</a
> provide a Linux solution for schools, including a
3045 powerful desktop with education software, a central server providing
3046 web pages, user database, user home directories, central login and PXE
3047 boot of both clients without disk and the installation to install Debian
3048 Edu on machines with disk (and a few other services perhaps to small
3049 to mention here). We in the Debian Edu team are currently working on
3050 the Jessie based version, trying to get everything in shape before the
3051 freeze, to avoid having to maintain our own package repository in the
3053 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3054 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3055 work left. Some fatal problems block testing, breaking the installer,
3056 but it is possible to work around these to get anyway. Here is a
3057 recipe on how to get the installation limping along.
</p
>
3059 <p
>First, download the test ISO via
3060 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3061 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3063 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3064 The ISO build was broken on Tuesday, so we do not get a new ISO every
3065 12 hours or so, but thankfully the ISO we already got we are able to
3066 install with some tweaking.
</p
>
3068 <p
>When you get to the Debian Edu profile question, go to tty2
3069 (use Alt-Ctrl-F2), run
</p
>
3071 <p
><blockquote
><pre
>
3072 nano /usr/bin/edu-eatmydata-install
3073 </pre
></blockquote
></p
>
3075 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3076 optimization. Return to the installation, select the profile you want
3077 and continue. Without this change, exim4-config will fail to install
3078 due to a known bug in eatmydata.
</p
>
3080 <p
>When you get the grub question at the end, answer /dev/sda (or if
3081 this do not work, figure out what your correct value would be. All my
3082 test machines need /dev/sda, so I have no advice if it do not fit
3083 your need.
</p
>
3085 <p
>If you installed a profile including a graphical desktop, log in as
3086 root after the initial boot from hard drive, and install the
3087 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3088 or mate. If you want several desktop options, install more than one
3089 metapackage. Once this is done, reboot and you should have a working
3090 graphical login screen. This workaround should no longer be needed
3091 once the education-tasks package version
1.801 enter testing in two
3094 <p
>I believe the ISO build will start working on two days when the new
3095 tasksel package enter testing and Steve McIntyre get a chance to
3096 update the debian-cd git repository. The eatmydata, grub and desktop
3097 issues are already fixed in unstable and testing, and should show up
3098 on the ISO as soon as the ISO build start working again. Well the
3099 eatmydata optimization is really just disabled. The proper fix
3100 require an upload by the eatmydata maintainer applying the patch
3101 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3102 The rest have proper fixes in unstable.
</p
>
3104 <p
>I hope this get you going with the installation testing, as we are
3105 quickly running out of time trying to get our Jessie based
3106 installation ready before the distribution freeze in a month.
</p
>
3111 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3112 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3113 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3114 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3115 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3116 to handle my fairly large DVD collection. It is a nice command line
3117 tool to get details about a DVD, like title, tracks, track length,
3118 etc, in XML, Perl or human readable format. But lsdvd have not seen
3119 any new development since
2006 and had a few irritating bugs affecting
3120 its use with some DVDs. Upstream seemed to be dead, and in January I
3121 sent a small probe asking for a version control repository for the
3122 project, without any reply. But I use it regularly and would like to
3123 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3124 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3125 the project admin, and after getting a reply from him explaining that
3126 he was no longer interested in the project, I asked if I could take
3127 over. And yesterday, I became project admin.
</p
>
3129 <p
>I
've been in touch with a Gentoo developer and the Debian
3130 maintainer interested in joining forces to maintain the upstream
3131 project, and I hope we can get a new release out fairly quickly,
3132 collecting the patches spread around on the internet into on place.
3133 I
've added the relevant Debian patches to the freshly created git
3134 repository, and expect the Gentoo patches to make it too. If you got
3135 a DVD collection and care about command line tools, check out
3136 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3137 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3138 list
</a
>. :)
</p
>
3143 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3144 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3145 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3146 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3147 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3148 a lot quicker. When we install more than
2000 packages in
3149 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3150 tasksel in the installer, unpacking the binary packages take forever.
3151 A part of the slow I/O issue was discussed in
3152 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3153 much file system sync-ing done by dpkg, which is the package
3154 responsible for unpacking the binary packages. Other parts (like code
3155 executed by postinst scripts) might also sync to disk during
3156 installation. All this sync-ing to disk do not really make sense to
3157 me. If the machine crash half-way through, I start over, I do not try
3158 to salvage the half installed system. So the failure sync-ing is
3159 supposed to protect against, hardware or system crash, is not really
3160 relevant while the installer is running.
</p
>
3162 <p
>A few days ago, I thought of a way to get rid of all the file
3163 system sync()-ing in a fairly non-intrusive way, without the need to
3164 change the code in several packages. The idea is not new, but I have
3165 not heard anyone propose the approach using dpkg-divert before. It
3166 depend on the small and clever package
3167 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3168 uses LD_PRELOAD to replace the system functions for syncing data to
3169 disk with functions doing nothing, thus allowing programs to live
3170 dangerous while speeding up disk I/O significantly. Instead of
3171 modifying the implementation of dpkg, apt and tasksel (which are the
3172 packages responsible for selecting, fetching and installing packages),
3173 it occurred to me that we could just divert the programs away, replace
3174 them with a simple shell wrapper calling
3175 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3176 Two days ago I decided to test the idea, and wrapped up a simple
3177 implementation for the Debian Edu udeb.
</p
>
3179 <p
>The effect was stunning. In my first test it reduced the running
3180 time of the pkgsel step (installing tasks) from
64 to less than
44
3181 minutes (
20 minutes shaved off the installation) on an old Dell
3182 Latitude D505 machine. I am not quite sure what the optimised time
3183 would have been, as I messed up the testing a bit, causing the debconf
3184 priority to get low enough for two questions to pop up during
3185 installation. As soon as I saw the questions I moved the installation
3186 along, but do not know how long the question were holding up the
3187 installation. I did some more measurements using Debian Edu Jessie,
3188 and got these results. The time measured is the time stamp in
3189 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3190 "pkgsel: finishing up
" lines, if you want to do the same measurement
3191 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3192 timing thus do not depend on how quickly the user handle the tasksel
3195 <p
><table
>
3198 <th
>Machine/setup
</th
>
3199 <th
>Original tasksel
</th
>
3200 <th
>Optimised tasksel
</th
>
3201 <th
>Reduction
</th
>
3205 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3206 <td
>64 min (
07:
46-
08:
50)
</td
>
3207 <td
><44 min (
11:
27-
12:
11)
</td
>
3208 <td
>>20 min
18%
</td
>
3212 <td
>Latitude D505 Roaming LXDE
</td
>
3213 <td
>57 min (
08:
48-
09:
45)
</td
>
3214 <td
>34 min (
07:
43-
08:
17)
</td
>
3215 <td
>23 min
40%
</td
>
3219 <td
>Latitude D505 Minimal
</td
>
3220 <td
>22 min (
10:
37-
10:
59)
</td
>
3221 <td
>11 min (
11:
16-
11:
27)
</td
>
3222 <td
>11 min
50%
</td
>
3226 <td
>Thinkpad X200 Minimal
</td
>
3227 <td
>6 min (
08:
19-
08:
25)
</td
>
3228 <td
>4 min (
08:
04-
08:
08)
</td
>
3229 <td
>2 min
33%
</td
>
3233 <td
>Thinkpad X200 Roaming KDE
</td
>
3234 <td
>19 min (
09:
21-
09:
40)
</td
>
3235 <td
>15 min (
10:
25-
10:
40)
</td
>
3236 <td
>4 min
21%
</td
>
3239 </table
></p
>
3241 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3242 time is spent downloading packages. The connection to the Internet
3243 was
100Mbit/s during testing, so downloading should not be a
3244 significant factor in the measurement. Download typically took a few
3245 seconds to a few minutes, depending on the amount of packages being
3246 installed.
</p
>
3248 <p
>The speedup is implemented by using two hooks in
3249 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3250 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3251 finish-install.d hook to remove the divert at the end of the
3252 installation. I picked the pre-pkgsel.d hook instead of the
3253 post-base-installer.d hook because I test using an ISO without the
3254 eatmydata package included, and the post-base-installer.d hook in
3255 Debian Edu can only operate on packages included in the ISO. The
3256 negative effect of this is that I am unable to activate this
3257 optimization for the kernel installation step in d-i. If the code is
3258 moved to the post-base-installer.d hook, the speedup would be larger
3259 for the entire installation.
</p
>
3261 <p
>I
've implemented this in the
3262 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3263 git repository, and plan to provide the optimization as part of the
3264 Debian Edu installation. If you want to test this yourself, you can
3265 create two files in the installer (or in an udeb). One shell script
3266 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3268 <p
><blockquote
><pre
>
3271 . /usr/share/debconf/confmodule
3273 logger -t my-pkgsel
"info: $*
"
3276 logger -t my-pkgsel
"error: $*
"
3278 override_install() {
3279 apt-install eatmydata || true
3280 if [ -x /target/usr/bin/eatmydata ] ; then
3281 for bin in dpkg apt-get aptitude tasksel ; do
3283 # Test that the file exist and have not been diverted already.
3284 if [ -f /target$file ] ; then
3285 info
"diverting $file using eatmydata
"
3286 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3287 > /target$file.edu
3288 chmod
755 /target$file.edu
3289 in-target dpkg-divert --package debian-edu-config \
3290 --rename --quiet --add $file
3291 ln -sf ./$bin.edu /target$file
3293 error
"unable to divert $file, as it is missing.
"
3297 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3302 </pre
></blockquote
></p
>
3304 <p
>To clean up, another shell script should go into
3305 /usr/lib/finish-install.d/ with code like this:
3307 <p
><blockquote
><pre
>
3309 . /usr/share/debconf/confmodule
3311 logger -t my-finish-install
"error: $@
"
3313 remove_install_override() {
3314 for bin in dpkg apt-get aptitude tasksel ; do
3316 if [ -x /target$file.edu ] ; then
3318 in-target dpkg-divert --package debian-edu-config \
3319 --rename --quiet --remove $file
3322 error
"Missing divert for $file.
"
3325 sync # Flush file buffers before continuing
3328 remove_install_override
3329 </pre
></blockquote
></p
>
3331 <p
>In Debian Edu, I placed both code fragments in a separate script
3332 edu-eatmydata-install and call it from the pre-pkgsel.d and
3333 finish-install.d scripts.
</p
>
3335 <p
>By now you might ask if this change should get into the normal
3336 Debian installer too? I suspect it should, but am not sure the
3337 current debian-installer coordinators find it useful enough. It also
3338 depend on the side effects of the change. I
'm not aware of any, but I
3339 guess we will see if the change is safe after some more testing.
3340 Perhaps there is some package in Debian depending on sync() and
3341 fsync() having effect? Perhaps it should go into its own udeb, to
3342 allow those of us wanting to enable it to do so without affecting
3345 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3346 will break installation of all programs using gnutls because of
3347 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3348 eatmydata package in Debian will solve it.
</p
>
3350 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3351 the optimization work again. And I have discovered that the
3352 dpkg-divert trick is not really needed and implemented a slightly
3353 simpler approach as part of the debian-edu-install package. See
3354 tools/edu-eatmydata-install in the source package.
</p
>
3356 <p
>Update
2014-
11-
11: Unfortunately, a new
3357 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3358 triggering on i386 made it into testing, and broke this installation
3359 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3360 request
768893</a
> is accepted, it should be working again.
</p
>
3365 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3366 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3367 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3368 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3369 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3370 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3371 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3372 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3373 learn that there is a large set of publicly available key servers to
3374 use when looking for peoples public key. So far I have used
3375 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3376 were misbehaving, but those days are ended. The servers I have used
3377 up until yesterday have been slow and some times unavailable. I hope
3378 those problems are gone now.
</p
>
3380 <p
>Behind the round robin DNS entry of the
3381 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3382 there is a pool of more than
100 keyservers which are checked every
3383 day to ensure they are well connected and up to date. It must be
3384 better than what I have used so far. :)
</p
>
3386 <p
>Yesterdays speaker told me that the service is the default
3387 keyserver provided by the default configuration in GnuPG, but this do
3388 not seem to be used in Debian. Perhaps it should?
</p
>
3390 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3393 <p
><blockquote
><pre
>
3394 keyserver pool.sks-keyservers.net
3395 </pre
></blockquote
></p
>
3397 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3398 entries in DNS. Just for fun, I did just that at work, so now every
3399 user of GnuPG at the University of Oslo should find a OpenGPG
3400 keyserver automatically should their need it:
</p
>
3402 <p
><blockquote
><pre
>
3403 % host -t srv _pgpkey-http._tcp.uio.no
3404 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3406 </pre
></blockquote
></p
>
3408 <p
>Now if only
3409 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3410 HKP lookup protocol
</a
> supported finding signature paths, I would be
3411 very happy. It can look up a given key or search for a user ID, but I
3412 normally do not want that, but to find a trust path from my key to
3413 another key. Given a user ID or key ID, I would like to find (and
3414 download) the keys representing a signature path from my key to the
3415 key in question, to be able to get a trust path between the two keys.
3416 This is as far as I can tell not possible today. Perhaps something
3417 for a future version of the protocol?
</p
>
3422 <title>From English wiki to translated PDF and epub via Docbook
</title>
3423 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3424 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3425 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3426 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3427 project
</a
> provide an instruction manual for teachers, system
3428 administrators and other users that contain useful tips for setting up
3429 and maintaining a Debian Edu installation. This text is about how the
3430 text processing of this manual is handled in the project.
</p
>
3432 <p
>One goal of the project is to provide information in the native
3433 language of its users, and for this we need to handle translations.
3434 But we also want to make sure each language contain the same
3435 information, so for this we need a good way to keep the translations
3436 in sync. And we want it to be easy for our users to improve the
3437 documentation, avoiding the need to learn special formats or tools to
3438 contribute, and the obvious way to do this is to make it possible to
3439 edit the documentation using a web browser. We also want it to be
3440 easy for translators to keep the translation up to date, and give them
3441 help in figuring out what need to be translated. Here is the list of
3442 tools and the process we have found trying to reach all these
3445 <p
>We maintain the authoritative source of our manual in the
3446 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3447 wiki
</a
>, as several wiki pages written in English. It consist of one
3448 front page with references to the different chapters, several pages
3449 for each chapter, and finally one
"collection page
" gluing all the
3450 chapters together into one large web page (aka
3451 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3452 AllInOne page
</a
>). The AllInOne page is the one used for further
3453 processing and translations. Thanks to the fact that the
3454 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3455 wiki.debian.org support exporting pages in
3456 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3457 the list of pages to export using the raw version of the AllInOne
3458 page, loop over each of them to generate a Docbook XML version of the
3459 manual. This process also download images and transform image
3460 references to use the locally downloaded images. The generated
3461 Docbook XML files are slightly broken, so some post-processing is done
3462 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3463 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3464 a handfull of images. The XML file can now be used to generate PDF, HTML
3465 and epub versions of the English manual. This is the basic step of
3466 our process, making PDF (using dblatex), HTML (using xsltproc) and
3467 epub (using dbtoepub) version from Docbook XML, and the resulting files
3468 are placed in the debian-edu-doc-en binary package.
</p
>
3470 <p
>But English documentation is not enough for us. We want translated
3471 documentation too, and we want to make it easy for translators to
3472 track the English original. For this we use the
3473 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3474 which allow us to transform the English Docbook XML file into a
3475 translation file (a .pot file), usable with the normal gettext based
3476 translation tools used by those translating free software. The pot
3477 file is used to create and maintain translation files (several .po
3478 files), which the translations update with the native language
3479 translations of all titles, paragraphs and blocks of text in the
3480 original. The next step is combining the original English Docbook XML
3481 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3482 create a translated Docbook XML file (in this case
3483 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3484 translated, if the translation is not complete) Docbook XML file can
3485 then be used like the original to create a PDF, HTML and epub version
3486 of the documentation.
</p
>
3488 <p
>The translators use different tools to edit the .po files. We
3490 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3491 while some use emacs and vi, others can use web based editors like
3492 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3493 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3494 is where the .po file end up, in our git repository. Updated
3495 translations can either be committed directly to git, or submitted as
3496 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3497 against the debian-edu-doc package
</a
>.
</p
>
3499 <p
>One challenge is images, which both might need to be translated (if
3500 they show translated user applications), and are needed in different
3501 formats when creating PDF and HTML versions (epub is a HTML version in
3502 this regard). For this we transform the original PNG images to the
3503 needed density and format during build, and have a way to provide
3504 translated images by storing translated versions in
3505 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3506 package maintainers know more.
</p
>
3508 <p
>If you wonder what the result look like, we provide
3509 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3510 of the documentation packages on the web
</a
>. See for example the
3511 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3512 PDF version
</a
> or the
3513 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3514 HTML version
</a
>. We do not yet build the epub version by default,
3515 but perhaps it will be done in the future.
</p
>
3517 <p
>To learn more, check out
3518 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3519 debian-edu-doc package
</a
>,
3520 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3521 manual on the wiki
</a
> and
3522 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3523 translation instructions
</a
> in the manual.
</p
>
3528 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3529 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3530 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3531 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3532 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3533 related packages relevant for the computer installed automatically.
3534 So I implemented one, using
3535 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3536 package
</a
>. To use it, install the tasksel and isenkram packages and
3537 run tasksel as user root. You should be presented with a new option,
3538 "Hardware specific packages (autodetected by isenkram)
". When you
3539 select it, tasksel will install the packages isenkram claim is fit for
3540 the current hardware, hot pluggable or not.
<p
>
3542 <p
>The implementation is in two files, one is the tasksel menu entry
3543 description, and the other is the script used to extract the list of
3544 packages to install. The first part is in
3545 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3548 <p
><blockquote
><pre
>
3551 Description: Hardware specific packages (autodetected by isenkram)
3552 Based on the detected hardware various hardware specific packages are
3554 Test-new-install: mark show
3556 Packages: for-current-hardware
3557 </pre
></blockquote
></p
>
3559 <p
>The second part is in
3560 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3563 <p
><blockquote
><pre
>
3568 isenkram-autoinstall-firmware -l
3570 </pre
></blockquote
></p
>
3572 <p
>All in all, a very short and simple implementation making it
3573 trivial to install the hardware dependent package we all may want to
3574 have installed on our machines. I
've not been able to find a way to
3575 get tasksel to tell you exactly which packages it plan to install
3576 before doing the installation. So if you are curious or careful,
3577 check the output from the isenkram-* command line tools first.
</p
>
3579 <p
>The information about which packages are handling which hardware is
3580 fetched either from the isenkram package itself in
3581 /usr/share/isenkram/, from git.debian.org or from the APT package
3582 database (using the Modaliases header). The APT package database
3583 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3584 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3585 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3586 the python-apt code (bug
3587 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3588 workaround I was able to get rid of the file descriptor leak and
3589 reduce the memory leak from ~
30 MiB per hardware detection down to
3590 around
2 MiB per hardware detection. It should make the desktop
3591 daemon a lot more useful. The fix is in version
0.7 uploaded to
3592 unstable today.
</p
>
3594 <p
>I believe the current way of mapping hardware to packages in
3595 Isenkram is is a good draft, but in the future I expect isenkram to
3596 use the AppStream data source for this. A proposal for getting proper
3597 AppStream support into Debian is floating around as
3598 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3599 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3600 project
</a
> will take place this summer to improve the situation. I
3601 look forward to seeing the result, and welcome patches for isenkram to
3602 start using the information when it is ready.
</p
>
3604 <p
>If you want your package to map to some specific hardware, either
3605 add a
"Xb-Modaliases
" header to your control file like I did in
3606 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3607 package
</a
> or submit a bug report with the details to the isenkram
3609 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3610 blog posts tagged isenkram
</a
> for details on the notation. I expect
3611 the information will be migrated to AppStream eventually, but for the
3612 moment I got no better place to store it.
</p
>
3617 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3618 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3619 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3620 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3621 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3622 project
</a
> is working on providing the software and hardware to make
3623 it easy for non-technical people to host their data and communication
3624 at home, and being able to communicate with their friends and family
3625 encrypted and away from prying eyes. It is still going strong, and
3626 today a major mile stone was reached.
</p
>
3628 <p
>Today, the last of the packages currently used by the project to
3629 created the system images were accepted into Debian Unstable. It was
3630 the freedombox-setup package, which is used to configure the images
3631 during build and on the first boot. Now all one need to get going is
3632 the build code from the freedom-maker git repository and packages from
3633 Debian. And once the freedombox-setup package enter testing, we can
3634 build everything directly from Debian. :)
</p
>
3636 <p
>Some key packages used by Freedombox are
3637 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3638 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3639 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3640 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3641 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3642 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3643 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3644 are plans to integrate more packages into the setup. User
3645 documentation is maintained on the Debian wiki. Please
3646 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3647 the manual
</a
> and help us improve it.
</p
>
3649 <p
>To test for yourself and create boot images with the FreedomBox
3650 setup, run this on a Debian machine using a user with sudo rights to
3651 become root:
</p
>
3653 <p
><pre
>
3654 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3655 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3657 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3659 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3660 </pre
></p
>
3662 <p
>Root access is needed to run debootstrap and mount loopback
3663 devices. See the README in the freedom-maker git repo for more
3664 details on the build. If you do not want all three images, trim the
3665 make line. Note that the virtualbox-image target is not really
3666 virtualbox specific. It create a x86 image usable in kvm, qemu,
3667 vmware and any other x86 virtual machine environment. You might need
3668 the version of vmdebootstrap in Jessie to get the build working, as it
3669 include fixes for a race condition with kpartx.
</p
>
3671 <p
>If you instead want to install using a Debian CD and the preseed
3672 method, boot a Debian Wheezy ISO and use this boot argument to load
3673 the preseed values:
</p
>
3675 <p
><pre
>
3676 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3677 </pre
></p
>
3679 <p
>I have not tested it myself the last few weeks, so I do not know if
3680 it still work.
</p
>
3682 <p
>If you wonder how to help, one task you could look at is using
3683 systemd as the boot system. It will become the default for Linux in
3684 Jessie, so we need to make sure it is usable on the Freedombox. I did
3685 a simple test a few weeks ago, and noticed dnsmasq failed to start
3686 during boot when using systemd. I suspect there are other problems
3687 too. :) To detect problems, there is a test suite included, which can
3688 be run from the plinth web interface.
</p
>
3690 <p
>Give it a go and let us know how it goes on the mailing list, and help
3691 us get the new release published. :) Please join us on
3692 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3693 irc.debian.org)
</a
> and
3694 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3695 mailing list
</a
> if you want to help make this vision come true.
</p
>
3700 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3701 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3702 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3703 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3704 <description><p
>For a while now, I have been looking for a sensible offsite backup
3705 solution for use at home. My requirements are simple, it must be
3706 cheap and locally encrypted (in other words, I keep the encryption
3707 keys, the storage provider do not have access to my private files).
3708 One idea me and my friends had many years ago, before the cloud
3709 storage providers showed up, was to use Google mail as storage,
3710 writing a Linux block device storing blocks as emails in the mail
3711 service provided by Google, and thus get heaps of free space. On top
3712 of this one can add encryption, RAID and volume management to have
3713 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3714 I never found time to implement such system. But the last few weeks I
3715 have looked at a system called
3716 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3717 mounted network backed file system with the features I need.
</p
>
3719 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3720 handling several different storage providers, any with Amazon S3,
3721 Google Drive or OpenStack API. There are heaps of such storage
3722 providers. S3QL can also use a local directory as storage, which
3723 combined with sshfs allow for file storage on any ssh server. S3QL
3724 include support for encryption, compression, de-duplication, snapshots
3725 and immutable file systems, allowing me to mount the remote storage as
3726 a local mount point, look at and use the files as if they were local,
3727 while the content is stored in the cloud as well. This allow me to
3728 have a backup that should survive fire. The file system can not be
3729 shared between several machines at the same time, as only one can
3730 mount it at the time, but any machine with the encryption key and
3731 access to the storage service can mount it if it is unmounted.
</p
>
3733 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3734 package is included already. So to get started, run
<tt
>apt-get
3735 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3736 Greenqloud, after reading their nice recipe on
3737 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3738 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3739 in Iceland more than those in USA when it come to keeping my personal
3740 data safe and private, and thus would rather spend money on a company
3741 in Iceland. Another nice recipe is available from the article
3742 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3743 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3744 Admin magazine. When the provider is picked, figure out how to get
3745 the API key needed to connect to the storage API. With Greencloud,
3746 the key did not show up until I had added payment details to my
3749 <p
>Armed with the API access details, it is time to create the file
3750 system. First, create a new bucket in the cloud. This bucket is the
3751 file system storage area. I picked a bucket name reflecting the
3752 machine that was going to store data there, but any name will do.
3753 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3754 the API login and password, and a locally created password. Store it
3755 all in ~root/.s3ql/authinfo2 like this:
3757 <p
><blockquote
><pre
>
3759 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3760 backend-login: API-login
3761 backend-password: API-password
3762 fs-passphrase: local-password
3763 </pre
></blockquote
></p
>
3765 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3766 but any sensible way to create a fairly random password should do it.
3767 Armed with these details, it is now time to run mkfs, entering the API
3768 details and password to create it:
</p
>
3770 <p
><blockquote
><pre
>
3771 # mkdir -m
700 /var/lib/s3ql-cache
3772 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3773 --ssl s3c://s.greenqloud.com:
443/bucket-name
3774 Enter backend login:
3775 Enter backend password:
3776 Before using S3QL, make sure to read the user
's guide, especially
3777 the
'Important Rules to Avoid Loosing Data
' section.
3778 Enter encryption password:
3779 Confirm encryption password:
3780 Generating random encryption key...
3781 Creating metadata tables...
3791 Compressing and uploading metadata...
3792 Wrote
0.00 MB of compressed metadata.
3793 #
</pre
></blockquote
></p
>
3795 <p
>The next step is mounting the file system to make the storage available.
3797 <p
><blockquote
><pre
>
3798 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3799 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3800 Using
4 upload threads.
3801 Downloading and decompressing metadata...
3811 Mounting filesystem...
3813 Filesystem Size Used Avail Use% Mounted on
3814 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3816 </pre
></blockquote
></p
>
3818 <p
>The file system is now ready for use. I use rsync to store my
3819 backups in it, and as the metadata used by rsync is downloaded at
3820 mount time, no network traffic (and storage cost) is triggered by
3821 running rsync. To unmount, one should not use the normal umount
3822 command, as this will not flush the cache to the cloud storage, but
3823 instead running the umount.s3ql command like this:
3825 <p
><blockquote
><pre
>
3828 </pre
></blockquote
></p
>
3830 <p
>There is a fsck command available to check the file system and
3831 correct any problems detected. This can be used if the local server
3832 crashes while the file system is mounted, to reset the
"already
3833 mounted
" flag. This is what it look like when processing a working
3834 file system:
</p
>
3836 <p
><blockquote
><pre
>
3837 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3838 Using cached metadata.
3839 File system seems clean, checking anyway.
3840 Checking DB integrity...
3841 Creating temporary extra indices...
3842 Checking lost+found...
3843 Checking cached objects...
3844 Checking names (refcounts)...
3845 Checking contents (names)...
3846 Checking contents (inodes)...
3847 Checking contents (parent inodes)...
3848 Checking objects (reference counts)...
3849 Checking objects (backend)...
3850 ..processed
5000 objects so far..
3851 ..processed
10000 objects so far..
3852 ..processed
15000 objects so far..
3853 Checking objects (sizes)...
3854 Checking blocks (referenced objects)...
3855 Checking blocks (refcounts)...
3856 Checking inode-block mapping (blocks)...
3857 Checking inode-block mapping (inodes)...
3858 Checking inodes (refcounts)...
3859 Checking inodes (sizes)...
3860 Checking extended attributes (names)...
3861 Checking extended attributes (inodes)...
3862 Checking symlinks (inodes)...
3863 Checking directory reachability...
3864 Checking unix conventions...
3865 Checking referential integrity...
3866 Dropping temporary indices...
3867 Backing up old metadata...
3877 Compressing and uploading metadata...
3878 Wrote
0.89 MB of compressed metadata.
3880 </pre
></blockquote
></p
>
3882 <p
>Thanks to the cache, working on files that fit in the cache is very
3883 quick, about the same speed as local file access. Uploading large
3884 amount of data is to me limited by the bandwidth out of and into my
3885 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3886 which is very close to my upload speed, and downloading the same
3887 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3888 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3889 network, not the file system code. I do not know what a good cache
3890 size would be, but suspect that the cache should e larger than your
3891 working set.
</p
>
3893 <p
>I mentioned that only one machine can mount the file system at the
3894 time. If another machine try, it is told that the file system is
3897 <p
><blockquote
><pre
>
3898 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3899 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3900 Using
8 upload threads.
3901 Backend reports that fs is still mounted elsewhere, aborting.
3903 </pre
></blockquote
></p
>
3905 <p
>The file content is uploaded when the cache is full, while the
3906 metadata is uploaded once every
24 hour by default. To ensure the
3907 file system content is flushed to the cloud, one can either umount the
3908 file system, or ask S3QL to flush the cache and metadata using
3911 <p
><blockquote
><pre
>
3912 # s3qlctrl upload-meta /s3ql
3913 # s3qlctrl flushcache /s3ql
3915 </pre
></blockquote
></p
>
3917 <p
>If you are curious about how much space your data uses in the
3918 cloud, and how much compression and deduplication cut down on the
3919 storage usage, you can use s3qlstat on the mounted file system to get
3922 <p
><blockquote
><pre
>
3924 Directory entries:
9141
3927 Total data size:
22049.38 MB
3928 After de-duplication:
21955.46 MB (
99.57% of total)
3929 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3930 Database size:
2.39 MB (uncompressed)
3931 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3933 </pre
></blockquote
></p
>
3935 <p
>I mentioned earlier that there are several possible suppliers of
3936 storage. I did not try to locate them all, but am aware of at least
3937 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3938 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3939 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3940 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3941 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3942 accept payment in Bitcoin. Pick one that suit your need. Some of
3943 them provide several GiB of free storage, but the prize models are
3944 quite different and you will have to figure out what suits you
3947 <p
>While researching this blog post, I had a look at research papers
3948 and posters discussing the S3QL file system. There are several, which
3949 told me that the file system is getting a critical check by the
3950 science community and increased my confidence in using it. One nice
3952 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3953 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3954 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3955 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3956 and Pamela Smith. Please have a look.
</p
>
3958 <p
>Given my problems with different file systems earlier, I decided to
3959 check out the mounted S3QL file system to see if it would be usable as
3960 a home directory (in other word, that it provided POSIX semantics when
3961 it come to locking and umask handling etc). Running
3962 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3963 test code to check file system semantics
</a
>, I was happy to discover that
3964 no error was found. So the file system can be used for home
3965 directories, if one chooses to do so.
</p
>
3967 <p
>If you do not want a locally file system, and want something that
3968 work without the Linux fuse file system, I would like to mention the
3969 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3970 provide locally encrypted backup using a command line client. It have
3971 a nicer access control system, where one can split out read and write
3972 access, allowing some systems to write to the backup and others to
3973 only read from it.
</p
>
3975 <p
>As usual, if you use Bitcoin and want to show your support of my
3976 activities, please send Bitcoin donations to my address
3977 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3982 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3983 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3984 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3985 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3986 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3987 project
</a
> is working on providing the software and hardware for
3988 making it easy for non-technical people to host their data and
3989 communication at home, and being able to communicate with their
3990 friends and family encrypted and away from prying eyes. It has been
3991 going on for a while, and is slowly progressing towards a new test
3992 release (
0.2).
</p
>
3994 <p
>And what day could be better than the Pi day to announce that the
3995 new version will provide
"hard drive
" / SD card / USB stick images for
3996 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
3997 system), and can also be installed using a Debian installer preseed
3998 file. The Debian based Freedombox is now based on Debian Jessie,
3999 where most of the needed packages used are already present. Only one,
4000 the freedombox-setup package, is missing. To try to build your own
4001 boot image to test the current status, fetch the freedom-maker scripts
4003 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4004 with a user with sudo access to become root:
4007 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4009 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4010 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4012 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4015 <p
>Root access is needed to run debootstrap and mount loopback
4016 devices. See the README for more details on the build. If you do not
4017 want all three images, trim the make line. But note that thanks to
<a
4018 href=
"https://bugs.debian.org/
741407">a race condition in
4019 vmdebootstrap
</a
>, the build might fail without the patch to the
4020 kpartx call.
</p
>
4022 <p
>If you instead want to install using a Debian CD and the preseed
4023 method, boot a Debian Wheezy ISO and use this boot argument to load
4024 the preseed values:
</p
>
4027 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4030 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4031 recently introduced bug in apt in Jessie
</a
>, the installer will
4032 currently hang while setting up APT sources. Killing the
4033 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4034 installation will get the installation going. This affect all
4035 installations in Jessie, and I expect it will be fixed soon.
</p
>
4037 <p
>Give it a go and let us know how it goes on the mailing list, and help
4038 us get the new release published. :) Please join us on
4039 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4040 irc.debian.org)
</a
> and
4041 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4042 mailing list
</a
> if you want to help make this vision come true.
</p
>
4047 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4048 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4049 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4050 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4051 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4052 innetgr tools, because I needed them in
4053 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4054 ng-utils, and it has served me well. I placed the project under the
4055 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4056 repository. But many years ago, the CVS repository was dropped (lost,
4057 not migrated to new hardware, not sure), and the project have lacked a
4058 proper home since then.
</p
>
4060 <p
>Last summer, I had a look at the package and made a new release
4061 fixing a irritating crash bug, but was unable to store the changes in
4062 a proper source control system. I applied for a project on
4063 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4064 to follow up on it. Until today. :)
</p
>
4066 <p
>After many hours of cleaning and migration, the ng-utils project
4067 now have a new home, and a git repository with the highlight of the
4068 history of the project. I published all release tarballs and imported
4069 them into the git repository. As the project is really stable and not
4070 expected to gain new features any time soon, I decided to make a new
4071 release and call it
1.0. Visit the new project home on
4072 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4073 if you want to check it out. The new version is also uploaded into
4074 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4079 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4080 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4081 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4082 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4083 <description><p
>A few days ago I decided to try to help the Hurd people to get
4084 their changes into sysvinit, to allow them to use the normal sysvinit
4085 boot system instead of their old one. This follow up on the
4086 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4087 Google Summer of Code work
</a
> done last summer by Justus Winter to
4088 get Debian on Hurd working more like Debian on Linux. To get started,
4089 I downloaded a prebuilt hard disk image from
4090 <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
>,
4091 and started it using virt-manager.
</p
>
4093 <p
>The first think I had to do after logging in (root without any
4094 password) was to get the network operational. I followed
4095 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4096 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4097 commands as root to get the machine to accept a IP address from the
4098 kvm internal DHCP server:
</p
>
4100 <p
><blockquote
><pre
>
4101 settrans -fgap /dev/netdde /hurd/netdde
4102 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4103 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4105 </pre
></blockquote
></p
>
4107 <p
>After this, the machine had internet connectivity, and I could
4108 upgrade it and install the sysvinit packages from experimental and
4109 enable it as the default boot system in Hurd.
</p
>
4111 <p
>But before I did that, I set a password on the root user, as ssh is
4112 running on the machine it for ssh login to work a password need to be
4113 set. Also, note that a bug somewhere in openssh on Hurd block
4114 compression from working. Remember to turn that off on the client
4117 <p
>Run these commands as root to upgrade and test the new sysvinit
4120 <p
><blockquote
><pre
>
4121 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4122 deb http://http.debian.net/debian/ experimental main
4125 apt-get dist-upgrade
4126 apt-get install -t experimental initscripts sysv-rc sysvinit \
4127 sysvinit-core sysvinit-utils
4128 update-alternatives --config runsystem
4129 </pre
></blockquote
></p
>
4131 <p
>To reboot after switching boot system, you have to use
4132 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4133 yet a sysvinit process able to receive the signals from the normal
4134 'reboot
' command. After switching to sysvinit as the boot system,
4135 upgrading every package and rebooting, the network come up with DHCP
4136 after boot as it should, and the settrans/pkill hack mentioned at the
4137 start is no longer needed. But for some strange reason, there are no
4138 longer any login prompt in the virtual console, so I logged in using
4141 <p
>Note that there are some race conditions in Hurd making the boot
4142 fail some times. No idea what the cause is, but hope the Hurd porters
4143 figure it out. At least Justus said on IRC (#debian-hurd on
4144 irc.debian.org) that they are aware of the problem. A way to reduce
4145 the impact is to upgrade to the Hurd packages built by Justus by
4146 adding this repository to the machine:
</p
>
4148 <p
><blockquote
><pre
>
4149 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4150 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4152 </pre
></blockquote
></p
>
4154 <p
>At the moment the prebuilt virtual machine get some packages from
4155 http://ftp.debian-ports.org/debian, because some of the packages in
4156 unstable do not yet include the required patches that are lingering in
4157 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4159 <p
><blockquote
><pre
>
4160 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4161 i emacs - GNU Emacs editor (metapackage)
4162 i gdb - GNU Debugger
4163 i hurd-recommended - Miscellaneous translators
4164 i isc-dhcp-client - ISC DHCP client
4165 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4166 i libc-bin - Embedded GNU C Library: Binaries
4167 i libc-dev-bin - Embedded GNU C Library: Development binaries
4168 i libc0.3 - Embedded GNU C Library: Shared libraries
4169 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4170 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4171 i multiarch-support - Transitional package to ensure multiarch compatibilit
4172 i A x11-common - X Window System (X.Org) infrastructure
4173 i xorg - X.Org X Window System
4174 i A xserver-xorg - X.Org X server
4175 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4177 </pre
></blockquote
></p
>
4179 <p
>All in all, testing hurd has been an interesting experience. :)
4180 X.org did not work out of the box and I never took the time to follow
4181 the porters instructions to fix it. This time I was interested in the
4182 command line stuff.
<p
>
4187 <title>New chrpath release
0.16</title>
4188 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4189 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4190 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4191 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4192 find problems in C, C++ and Java code using static source code
4193 analysis. It can detect a lot of different problems, and is very
4194 useful to find memory and locking bugs in the error handling part of
4195 the source. The company behind it provide
4196 <a href=
"https://scan.coverity.com/
">check of free software projects as
4197 a community service
</a
>, and many hundred free software projects are
4198 already checked. A few days ago I decided to have a closer look at
4199 the Coverity system, and discovered that the
4200 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4201 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4202 projects I am involved with was already registered. But these are
4203 fairly big, and I would also like to have a small and easy project to
4204 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4205 checking of the chrpath project
</a
>. It was
4206 added to the checker and discovered seven potential defects. Six of
4207 these were real, mostly resource
"leak
" when the program detected an
4208 error. Nothing serious, as the resources would be released a fraction
4209 of a second later when the program exited because of the error, but it
4210 is nice to do it right in case the source of the program some time in
4211 the future end up in a library. Having fixed all defects and added
4212 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4213 mailing list for the chrpath developers
</a
>, I decided it was time to
4214 publish a new release. These are the release notes:
</p
>
4216 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4220 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4221 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4222 <li
>Mention new project mailing list in the documentation.
</li
>
4227 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4228 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4229 project if something is wrong with the new release. The test suite
4230 did not discover any old errors, so if you find a new one, please also
4231 include a test suite check.
</p
>
4236 <title>New chrpath release
0.15</title>
4237 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4238 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4239 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4240 <description><p
>After many years break from the package and a vain hope that
4241 development would be continued by someone else, I finally pulled my
4242 acts together this morning and wrapped up a new release of chrpath,
4243 the command line tool to modify the rpath and runpath of already
4244 compiled ELF programs. The update was triggered by the persistence of
4245 Isha Vishnoi at IBM, which needed a new config.guess file to get
4246 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4247 is working on. I checked the
4248 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4249 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4250 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4251 packages for interesting patches (failed to find the source from
4252 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4253 These are the release notes:
</p
>
4255 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4259 <li
>Updated config.sub and config.guess from the GNU project to work
4260 with newer architectures. Thanks to isha vishnoi for the heads
4263 <li
>Updated README with current URLs.
</li
>
4265 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4266 Matthias Klose.
</li
>
4268 <li
>Added missing help for -k|--keepgoing option, using patch by
4269 Petr Machata found in Fedora.
</li
>
4271 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4272 .dynamic is a NULL terminated string. Based on patch found in
4273 Fedora credited Axel Thimm and Christian Krause.
</li
>
4278 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4279 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4280 project if something is wrong with the new release. The test suite
4281 did not discover any old errors, so if you find a new one, please also
4282 include a testsuite check.
</p
>
4287 <title>Debian init.d boot script example for rsyslog
</title>
4288 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4290 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4291 <description><p
>If one of the points of switching to a new init system in Debian is
4292 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4293 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4294 init.d scripts at all. Here is an example init.d script, ie a rewrite
4295 of /etc/init.d/rsyslog:
</p
>
4297 <p
><pre
>
4298 #!/lib/init/init-d-script
4301 # Required-Start: $remote_fs $time
4302 # Required-Stop: umountnfs $time
4303 # X-Stop-After: sendsigs
4304 # Default-Start:
2 3 4 5
4305 # Default-Stop:
0 1 6
4306 # Short-Description: enhanced syslogd
4307 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4308 # It is quite compatible to stock sysklogd and can be
4309 # used as a drop-in replacement.
4311 DESC=
"enhanced syslogd
"
4312 DAEMON=/usr/sbin/rsyslogd
4313 </pre
></p
>
4315 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4316 script was
137 lines, and the above is just
15 lines, most of it meta
4317 info/comments.
</p
>
4319 <p
>How to do this, you ask? Well, one create a new script
4320 /lib/init/init-d-script looking something like this:
4322 <p
><pre
>
4325 # Define LSB log_* functions.
4326 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4327 # and status_of_proc is working.
4328 . /lib/lsb/init-functions
4331 # Function that starts the daemon/service
4337 #
0 if daemon has been started
4338 #
1 if daemon was already running
4339 #
2 if daemon could not be started
4340 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4342 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4345 # Add code here, if necessary, that waits for the process to be ready
4346 # to handle requests from services started subsequently which depend
4347 # on this one. As a last resort, sleep for some time.
4351 # Function that stops the daemon/service
4356 #
0 if daemon has been stopped
4357 #
1 if daemon was already stopped
4358 #
2 if daemon could not be stopped
4359 # other if a failure occurred
4360 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4361 RETVAL=
"$?
"
4362 [
"$RETVAL
" =
2 ]
&& return
2
4363 # Wait for children to finish too if this is a daemon that forks
4364 # and if the daemon is only ever run from this initscript.
4365 # If the above conditions are not satisfied then add some other code
4366 # that waits for the process to drop all resources that could be
4367 # needed by services started subsequently. A last resort is to
4368 # sleep for some time.
4369 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4370 [
"$?
" =
2 ]
&& return
2
4371 # Many daemons don
't delete their pidfiles when they exit.
4373 return
"$RETVAL
"
4377 # Function that sends a SIGHUP to the daemon/service
4381 # If the daemon can reload its configuration without
4382 # restarting (for example, when it is sent a SIGHUP),
4383 # then implement that here.
4385 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4390 scriptbasename=
"$(basename $
1)
"
4391 echo
"SN: $scriptbasename
"
4392 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4393 script=
"$
1"
4400 NAME=$(basename $DAEMON)
4401 PIDFILE=/var/run/$NAME.pid
4403 # Exit if the package is not installed
4404 #[ -x
"$DAEMON
" ] || exit
0
4406 # Read configuration variable file if it is present
4407 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4409 # Load the VERBOSE setting and other rcS variables
4412 case
"$
1" in
4414 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4416 case
"$?
" in
4417 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4418 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4422 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4424 case
"$?
" in
4425 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4426 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4430 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4432 #reload|force-reload)
4434 # If do_reload() is not implemented then leave this commented out
4435 # and leave
'force-reload
' as an alias for
'restart
'.
4437 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4441 restart|force-reload)
4443 # If the
"reload
" option is implemented then remove the
4444 #
'force-reload
' alias
4446 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4448 case
"$?
" in
4451 case
"$?
" in
4453 1) log_end_msg
1 ;; # Old process is still running
4454 *) log_end_msg
1 ;; # Failed to start
4464 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4470 </pre
></p
>
4472 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4473 lot. I did not really polish the approach, so it might not always
4474 work out of the box, but you get the idea. I did not try very hard to
4475 optimize it nor make it more robust either.
</p
>
4477 <p
>A better argument for switching init system in Debian than reducing
4478 the size of init scripts (which is a good thing to do anyway), is to
4479 get boot system that is able to handle the kernel events sensibly and
4480 robustly, and do not depend on the boot to run sequentially. The boot
4481 and the kernel have not behaved sequentially in years.
</p
>
4486 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4487 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4488 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4489 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4490 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4491 remote display access is the preferred solution with oVirt and RedHat
4492 Enterprise Virtualization, and I was sad to discover the other day
4493 that the browser plugin needed to use these systems seamlessly was
4494 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4495 for a package
</a
> was from
2012-
04-
10 with no progress since
4496 2013-
04-
01, so I decided to wrap up a package based on the great work
4497 from Cajus Pollmeier and put it in a collab-maint maintained git
4498 repository to get a package I could use. I would very much like
4499 others to help me maintain the package (or just take over, I do not
4500 mind), but as no-one had volunteered so far, I just uploaded it to
4501 NEW. I hope it will be available in Debian in a few days.
</p
>
4503 <p
>The source is now available from
4504 <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
>
4509 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4510 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4512 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4513 <description><p
>The
4514 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4515 program is a a very nice system to create virtual machine images. It
4516 create a image file, add a partition table, mount it and run
4517 debootstrap in the mounted directory to create a Debian system on a
4518 stick. Yesterday, I decided to try to teach it how to make images for
4519 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4520 of a plan to simplify the build system for
4521 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4522 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4523 the virtualbox images, but its current build system made multistrap
4524 based system for Dreamplug images, and it is lacking support for
4525 Raspberry Pi.
</p
>
4527 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4528 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4529 code and adjusted it to be able to build armel images on my amd64
4530 Debian laptop. I ended up giving vmdebootstrap five new options,
4531 allowing me to replicate the image creation process I use to make
4532 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4533 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4534 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4535 call debootstrap with --foreign and to copy the handler into the
4536 generated chroot before running the second stage. This allow
4537 vmdebootstrap to create armel images on an amd64 host. Next I added
4538 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4539 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4540 given file system type, allowing me to create an image with a vfat
4541 partition for the /boot/ stuff. I also added a
<tt
>--variant
4542 variant
</tt
> option to allow me to create smaller images without the
4543 Debian base system packages installed. Finally, I added an option
4544 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4545 as a boot loader. It is not needed on the Raspberry Pi and probably
4546 most other non-x86 architectures. The changes were accepted by the
4547 upstream author of vmdebootstrap yesterday and today, and is now
4549 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4550 upstream project page
</a
>.
</p
>
4552 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4553 create a small script (the customize script) to add the non-free
4554 binary blob needed to boot the Raspberry Pi and the APT source
4557 <p
><pre
>
4559 set -e # Exit on first error
4560 rootdir=
"$
1"
4561 cd
"$rootdir
"
4562 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4563 deb http://http.debian.net/debian/ jessie main contrib non-free
4565 # Install non-free binary blob needed to boot Raspberry Pi. This
4566 # install a kernel somewhere too.
4567 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4568 -O $rootdir/usr/bin/rpi-update
4569 chmod a+x $rootdir/usr/bin/rpi-update
4570 mkdir -p $rootdir/lib/modules
4571 touch $rootdir/boot/start.elf
4572 chroot $rootdir rpi-update
4573 </pre
></p
>
4575 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4576 to build the image:
</p
>
4579 sudo ./vmdebootstrap \
4582 --distribution jessie \
4583 --mirror http://http.debian.net/debian \
4592 --root-password raspberry \
4593 --hostname raspberrypi \
4594 --foreign /usr/bin/qemu-arm-static \
4595 --customize `pwd`/customize \
4597 --package git-core \
4598 --package binutils \
4599 --package ca-certificates \
4602 </pre
></p
>
4604 <p
>The list of packages being installed are the ones needed by
4605 rpi-update to make the image bootable on the Raspberry Pi, with the
4606 exception of netbase, which is needed by debootstrap to find
4607 /etc/hosts with the minbase variant. I really wish there was a way to
4608 set up an Raspberry Pi using only packages in the Debian archive, but
4609 that is not possible as far as I know, because it boots from the GPU
4610 using a non-free binary blob.
</p
>
4612 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4613 probably a few others installed. I have not checked the complete
4614 build dependency list.
</p
>
4616 <p
>The resulting image will not use the hardware floating point unit
4617 on the Raspberry PI, because the armel architecture in Debian is not
4618 optimized for that use. So the images created will be a bit slower
4619 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4624 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4625 <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>
4626 <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>
4627 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4628 <description><p
>The last few days I came across a few good causes that should get
4629 wider attention. I recommend signing and donating to each one of
4632 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4633 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4634 Women program which is a Google Summer of Code like initiative to get
4635 more women involved in free software. One debian sponsor has offered
4636 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4637 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4638 hope you will to. :)
</p
>
4640 <p
>And the Electronic Frontier Foundation just announced plans to
4641 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4642 documentaries about the excessive spying
</a
> on every Internet user that
4643 take place these days, and their need to fund the work. I
've already
4644 donated. Are you next?
</p
>
4646 <p
>For my Norwegian audience, the organisation Studentenes og
4647 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4648 statement under the heading
4649 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4650 Access
</a
> for those of us asking for more focus on open access in the
4651 Norwegian government. So far
499 signatures. I hope you will sign it
4657 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4658 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4660 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4661 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4662 project
</a
> have been going on for a while, and have presented the
4663 vision, ideas and solution several places. Here is a little
4664 collection of videos of talks and presentation of the project.
</p
>
4668 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4669 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4671 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4672 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4674 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4675 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4676 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4677 (Youtube)
</li
>
4679 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4680 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4682 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4683 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4685 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4686 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4687 York City in
2012</a
> (Youtube)
</li
>
4689 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4690 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4691 (Youtube)
</li
>
4693 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4694 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4696 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4697 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4699 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4700 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4701 2013</a
> (Youtube)
</li
>
4705 <p
>A larger list is available from
4706 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4707 Freedombox Wiki
</a
>.
</p
>
4709 <p
>On other news, I am happy to report that Freedombox based on Debian
4710 Jessie is coming along quite well, and soon both Owncloud and using
4711 Tor should be available for testers of the Freedombox solution. :) In
4712 a few weeks I hope everything needed to test it is included in Debian.
4713 The withsqlite package is already in Debian, and the plinth package is
4714 pending in NEW. The third and vital part of that puzzle is the
4715 metapackage/setup framework, which is still pending an upload. Join
4716 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4717 (#freedombox on irc.debian.org)
</a
> and
4718 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4719 mailing list
</a
> if you want to help make this vision come true.
</p
>
4724 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4725 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4726 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4727 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4728 <description><p
>I was introduced to the
4729 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4730 in
2010, when Eben Moglen presented his vision about serving the need
4731 of non-technical people to keep their personal information private and
4732 within the legal protection of their own homes. The idea is to give
4733 people back the power over their network and machines, and return
4734 Internet back to its intended peer-to-peer architecture. Instead of
4735 depending on a central service, the Freedombox will give everyone
4736 control over their own basic infrastructure.
</p
>
4738 <p
>I
've intended to join the effort since then, but other tasks have
4739 taken priority. But this summers nasty news about the misuse of trust
4740 and privilege exercised by the
"western
" intelligence gathering
4741 communities increased my eagerness to contribute to a point where I
4742 actually started working on the project a while back.
</p
>
4744 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4745 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4746 create a simple and cheap Debian based appliance that anyone can hook
4747 up in their home and get access to secure and private services and
4748 communication. The initial deployment platform have been the
4749 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4750 which is a piece of hardware I do not own. So to be able to test what
4751 the current Freedombox setup look like, I had to come up with a way to install
4752 it on some hardware I do have access to. I have rewritten the
4753 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4754 image build framework to use .deb packages instead of only copying
4755 setup into the boot images, and thanks to this rewrite I am able to
4756 set up any machine supported by Debian Wheezy as a Freedombox, using
4757 the previously mentioned deb (and a few support debs for packages
4758 missing in Debian).
</p
>
4760 <p
>The current Freedombox setup consist of a set of bootstrapping
4762 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4763 and a administrative web interface
4764 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4765 withsqlite), as well as a privacy enhancing proxy based on
4766 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4767 (freedombox-privoxy). There is also a web/javascript based XMPP
4768 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4769 trying (unsuccessfully so far) to talk to the XMPP server
4770 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4771 web interface is pluggable, and the goal is to use it to enable OpenID
4772 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4773 this is really working yet, see
4774 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4775 project TODO
</a
> for links to GIT repositories. Most of the code is
4776 on github at the moment. The HTTP proxy is operational out of the
4777 box, and the admin web interface can be used to add/remove plinth
4778 users. I
've not been able to do anything else with it so far, but
4779 know there are several branches spread around github and other places
4780 with lots of half baked features.
</p
>
4782 <p
>Anyway, if you want to have a look at the current state, the
4783 following recipes should work to give you a test machine to poke
4786 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4790 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4791 <li
>Boot from it, either as CD or USB stick.
</li
>
4792 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4793 to the Debian installer:
<p
>
4794 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4796 <li
>Answer the few language/region/password questions and pick disk to
4797 install on.
</li
>
4799 <li
>When the installation is finished and the machine have rebooted a
4800 few times, your Freedombox is ready for testing.
</li
>
4804 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4808 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4809 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4810 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4812 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4813 </pre
></li
>
4814 <li
><p
>Run this as root:
</p
>
4816 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4819 apt-get install freedombox-setup
4820 /usr/lib/freedombox/setup
4821 </pre
></li
>
4822 <li
>Reboot into your freshly created Freedombox.
</li
>
4826 <p
>You can test it on other architectures too, but because the
4827 freedombox-privoxy package is binary, it will only work as intended on
4828 the architectures where I have had time to build the binary and put it
4829 in my APT repository. But do not let this stop you. It is only a
4830 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4832 <p
>Note that by default Freedombox is a DHCP server on the
4833 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4834 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4835 disable
</tt
>" as root.
</p
>
4837 <p
>Please let me know if this works for you, or if you have any
4838 problems. We gather on the IRC channel
4839 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4840 irc.debian.org and the
4841 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4842 mailing list
</a
>.
</p
>
4844 <p
>Once you get your freedombox operational, you can visit
4845 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4846 welcome screen (dead end - do not be surprised if you are unable to
4847 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4848 to look at the rest of plinth. The default user is
'admin
' and the
4849 default password is
'secret
'.
</p
>
4854 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4855 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4856 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4857 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4858 <description><p
>Earlier, I reported about
4859 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4860 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4861 told by IBM that the original disk should be thrown away. And as
4862 there no longer was a problem if I bricked the firmware, I decided
4863 today to try to install Intel firmware to replace the Lenovo firmware
4864 currently on the disk.
</p
>
4866 <p
>I searched the Intel site for firmware, and found
4867 <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
>
4868 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4869 according to the site should contain the latest firmware for SSD
4870 disks. I inserted the broken disk in one of my spare laptops and
4871 booted the ISO from a USB stick. The disk was recognized, but the
4872 program claimed the newest firmware already were installed and refused
4873 to insert any Intel firmware. So no change, and the disk is still
4874 unable to handle write load. :( I guess the only way to get them
4875 working would be if Lenovo releases new firmware. No idea how likely
4876 that is. Anyway, just blogging about this test for completeness. I
4877 got a working Samsung disk, and see no point in spending more time on
4878 the broken disks.
</p
>
4883 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4884 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4885 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4886 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4887 <description><p
>Today I switched to
4888 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4889 new laptop
</a
>. I
've previously written about the problems I had with
4890 my new Thinkpad X230, which was delivered with an
4891 <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
4892 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4893 sustained writes. My hardware supplier have been very forthcoming in
4894 trying to find a solution, and after first trying with another
4895 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4896 disk instead to fix it once and for all. The Samsung disk survived
4897 the installation of Debian with encrypted disks (filling the disk with
4898 random data during installation killed the first two), and I thus
4899 decided to trust it with my data. I have installed it as a Debian Edu
4900 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4901 server at home using Kerberos and LDAP, and will use it as my work
4902 station from now on.
</p
>
4904 <p
>As this is a solid state disk with no moving parts, I believe the
4905 Debian Wheezy default installation need to be tuned a bit to increase
4906 performance and increase life time of the disk. The Linux kernel and
4907 user space applications do not yet adjust automatically to such
4908 environment. To make it easier for my self, I created a draft Debian
4909 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4910 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4911 for the ssd-setup package
</a
> is available from collab-maint, and it
4912 is set up to adjust the setup of the machine by just installing the
4913 package. If there is any non-SSD disk in the machine, the package
4914 will refuse to install, as I did not try to write any logic to sort
4915 file systems in SSD and non-SSD file systems.
</p
>
4917 <p
>I consider the package a draft, as I am a bit unsure how to best
4918 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4919 where I set up the machine with one large encrypted partition (in
4920 addition to /boot), put LVM on top of this and set up partitions on
4921 top of this again. See the README file in the package source for the
4922 references I used to pick the settings. At the moment these
4923 parameters are tuned:
</p
>
4927 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4928 (adding discard to /etc/crypttab)
</li
>
4930 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4931 this case a cryptsetup partition) by changing issue_discards from
4932 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4934 <li
>Set relatime as a file system option for ext3 and ext4 file
4937 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4938 /etc/fstab.
</li
>
4940 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4942 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4943 cron.daily).
</li
>
4945 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4946 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4950 <p
>During installation, I cancelled the part where the installer fill
4951 the disk with random data, as this would kill the SSD performance for
4952 little gain. My goal with the encrypted file system is to ensure
4953 those stealing my laptop end up with a brick and not a working
4954 computer. I have no hope in keeping the really resourceful people
4955 from getting the data on the disk (see
4956 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4957 Thus I concluded that adding the discard option to crypttab is the
4958 right thing to do.
</p
>
4960 <p
>I considered using the noop I/O scheduler, as several recommended
4961 it for SSD, but others recommended deadline and a benchmark I found
4962 indicated that deadline might be better for interactive use.
</p
>
4964 <p
>I also considered using the
'discard
' file system option for ext3
4965 and ext4, but read that it would give a performance hit ever time a
4966 file is removed, and thought it best to that that slowdown once a day
4967 instead of during my work.
</p
>
4969 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4970 this is already done by Debian Edu.
</p
>
4972 <p
>I have not yet started on the user space tuning. I expect
4973 iceweasel need some tuning, and perhaps other applications too, but
4974 have not yet had time to investigate those parts.
</p
>
4976 <p
>The package should work on Ubuntu too, but I have not yet tested it
4979 <p
>As for the answer to the question in the title of this blog post,
4980 as far as I know, the only solution I know about is to replace the
4981 disk. It might be possible to flash it with Intel firmware instead of
4982 the Lenovo firmware. But I have not tried and did not want to do so
4983 without approval from Lenovo as I wanted to keep the warranty on the
4984 disk until a solution was found and they wanted the broken disks
4990 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4991 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4992 <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>
4993 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
4994 <description><p
>A few days ago, I wrote about
4995 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
4996 problems I experienced with my new X230 and its SSD disk
</a
>, which
4997 was dying during installation because it is unable to cope with
4998 sustained write. My supplier is in contact with
4999 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5000 replacement disk to try to fix the problem. They decided to send an
5001 identical model, so my hopes for a permanent fix was slim.
</p
>
5003 <p
>Anyway, today I got the replacement disk and tried to install
5004 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5005 same firmware version as the original. This time my hope raised
5006 slightly as the installation progressed, as the original disk used to
5007 die after
4-
7% of the disk was written to, while this time it kept
5008 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5009 died again and I was back on square one. I still do not have a new
5010 laptop with a disk I can trust. I can not live with a disk that might
5011 lock up when I download a new
5012 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5013 other large files. I look forward to hearing from my supplier with
5014 the next proposal from Lenovo.
</p
>
5016 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5017 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5018 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5019 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5020 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5021 P/N
45N8295, P0C38732.
</p
>
5023 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5024 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5025 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5026 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5027 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5028 P/N
45N8295, P0C38732.
</p
>
5030 <p
>The only difference is in the first number (serial number?), ISN,
5031 SA, date and WNPP values. Mentioning all the details here in case
5032 someone is able to use the information to find a way to identify the
5033 failing disk among working ones (if any such working disk actually
5039 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5040 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5041 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5042 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5043 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5044 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5045 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5046 member assosiation NUUG
</a
> and
5047 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5048 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5049 Bitraf
</a
>.
</p
>
5051 <p
>It starts
10:
00 and continue until late evening. Everyone is
5052 welcome, and there is no fee to participate. There is on the other
5053 hand limited space, and only room for
30 people. Please put your name
5054 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5055 wiki page
</a
> if you plan to join us.
</p
>
5060 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5061 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5062 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5063 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5064 <description><p
>Half a year ago, I reported that I had to find a
5065 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5066 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5067 time to spend on it, and it took a while to find a model I believe
5068 will do the job, but two days ago the replacement finally arrived. I
5070 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5071 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5072 a roaming workstation, and it seemed to work flawlessly. But my
5073 second installation with encrypted disk was not as successful. More
5074 on that below.
</p
>
5076 <p
>I had a hard time trying to track down a good laptop, as my most
5077 important requirements (robust and with a good keyboard) are never
5078 listed in the feature list. But I did get good help from the search
5079 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5080 allowed me to limit the list of interesting laptops based on my other
5081 requirements. A bit surprising that SSD disk are not disks according
5082 to that search interface, so I had to drop specifying the number of
5083 disks from my search parameters. I also asked around among friends to
5084 get their impression on keyboards and robustness.
</p
>
5086 <p
>So the new laptop arrived, and it is quite a lot wider than the
5087 X41. I am not quite convinced about the keyboard, as it is
5088 significantly wider than my old keyboard, and I have to stretch my
5089 hand a lot more to reach the edges. But the key response is fairly
5090 good and the individual key shape is fairly easy to handle, so I hope
5091 I will get used to it. My old X40 was starting to fail, and I really
5092 needed a new laptop now. :)
</p
>
5094 <p
>Turning off the touch pad was simple. All it took was a quick
5095 visit to the BIOS during boot it disable it.
</p
>
5097 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5098 lock up during load. And this happen when installing Debian Wheezy
5099 with encrypted disk, while the disk is being filled with random data.
5100 I also tested to install Ubuntu Raring, and it happen there too if I
5101 reenable the code to fill the disk with random data (it is disabled by
5102 default in Ubuntu). And the bug with is already known. It was
5103 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5104 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5105 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5106 kernel developers as
5107 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5108 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5109 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5110 Lenovo forums, both for
5111 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5112 2012-
11-
10</a
> and for
5113 <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
5114 03-
20-
2013</a
>. The problem do not only affect installation. The
5115 reports state that the disk lock up during use if many writes are done
5116 on the disk, so it is much no use to work around the installation
5117 problem and end up with a computer that can lock up at any moment.
5119 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5120 available
</a
> that will lock up the hard drive after running a few
5121 minutes by writing to a file.
</p
>
5123 <p
>I
've contacted my supplier and asked how to handle this, and after
5124 contacting PCHELP Norway (request
01D1FDP) which handle support
5125 requests for Lenovo, his first suggestion was to upgrade the disk
5126 firmware. Unfortunately there is no newer firmware available from
5127 Lenovo, as my disk already have the most recent one (version LF1i). I
5128 hope to hear more from him today and hope the problem can be
5134 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5135 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5137 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5138 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5139 trusty old Thinkpad X41. Unfortunately I did not have much time to
5140 spend on it, but today the replacement finally arrived. I ended up
5141 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5142 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5143 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5144 this, it is installing what I hope will be a more final installation,
5145 with a encrypted hard drive to ensure any dope head stealing it end up
5146 with an expencive door stop.
</p
>
5148 <p
>I had a hard time trying to track down a good laptop, as my most
5149 important requirements (robust and with a good keyboard) are never
5150 listed in the feature list. But I did get good help from the search
5151 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5152 allowed me to limit the list of interesting laptops based on my other
5153 requirements. A bit surprising that SSD disk are not disks, so I had
5154 to drop number of disks from my search parameters.
</p
>
5156 <p
>I am not quite convinced about the keyboard, as it is significantly
5157 wider than my old keyboard, and I have to stretch my hand a lot more
5158 to reach the edges. But the key response is fairly good and the
5159 individual key shape is fairly easy to handle, so I hope I will get
5160 used to it. My old X40 was starting to fail, and I really needed a
5161 new laptop now. :)
</p
>
5163 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5168 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5169 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5170 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5171 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5172 <description><p
>It annoys me when the computer fail to do automatically what it is
5173 perfectly capable of, and I have to do it manually to get things
5174 working. One such task is to find out what firmware packages are
5175 needed to get the hardware on my computer working. Most often this
5176 affect the wifi card, but some times it even affect the RAID
5177 controller or the ethernet card. Today I pushed version
0.4 of the
5178 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5179 including a new script isenkram-autoinstall-firmware handling the
5180 process of asking all the loaded kernel modules what firmware files
5181 they want, find debian packages providing these files and install the
5182 debian packages. Here is a test run on my laptop:
</p
>
5184 <p
><pre
>
5185 # isenkram-autoinstall-firmware
5186 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5187 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5188 info: locating packages with the requested firmware files
5189 info: Updating APT sources after adding non-free APT source
5190 info: trying to install firmware-ipw2x00
5193 Preconfiguring packages ...
5194 Selecting previously deselected package firmware-ipw2x00.
5195 (Reading database ...
259727 files and directories currently installed.)
5196 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5197 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5199 </pre
></p
>
5201 <p
>When all the requested firmware is present, a simple message is
5202 printed instead:
</p
>
5204 <p
><pre
>
5205 # isenkram-autoinstall-firmware
5206 info: did not find any firmware files requested by loaded kernel modules. exiting
5208 </pre
></p
>
5210 <p
>It could use some polish, but it is already working well and saving
5211 me some time when setting up new machines. :)
</p
>
5213 <p
>So, how does it work? It look at the set of currently loaded
5214 kernel modules, and look up each one of them using modinfo, to find
5215 the firmware files listed in the module meta-information. Next, it
5216 download the Contents file from a nearby APT mirror, and search for
5217 the firmware files in this file to locate the package with the
5218 requested firmware file. If the package is in the non-free section, a
5219 non-free APT source is added and the package is installed using
5220 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5223 <p
>I hope someone find time to implement a more polished version of
5224 this script as part of the hw-detect debian-installer module, to
5225 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5226 #
655507</a
>. There really is no need to insert USB sticks with
5227 firmware during a PXE install when the packages already are available
5228 from the nearby Debian mirror.
</p
>
5233 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5234 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5235 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5236 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5237 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5238 the screen just turn black when Linux boot, either during installation
5239 or on first boot from the hard disk. I
've seen it once in a while the
5240 last few years, but only recently understood the cause. I
've seen it
5241 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5242 The reason seem to be in the wiring of some laptops. The system to
5243 control the screen background light is inverted, so when Linux try to
5244 turn the brightness fully on, it end up turning it off instead. I do
5245 not know which Linux drivers are affected, but this post is about the
5246 i915 driver used by the
5247 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5248 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5250 <p
>The problem can be worked around two ways. Either by adding
5251 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5252 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5253 option when it load the i915 kernel module. On Debian and Ubuntu, it
5254 can be done by running these commands as root:
</p
>
5257 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5258 update-initramfs -u -k all
5261 <p
>Since March
2012 there is
5262 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5263 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5264 hardware have this problem, and get the driver to invert the
5265 brightness setting automatically. To use it, one need to add a row in
5266 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5267 intel_quirks array
</a
> in the driver source
5268 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5269 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5270 number (vendor number
8086 is assumed) and subdevice vendor and device
5273 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5274 -vvnn
</tt
> for the video card in question:
</p
>
5276 <p
><pre
>
5277 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5278 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5279 (rev
09) (prog-if
00 [VGA controller])
5280 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5281 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5282 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5283 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5284 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5286 Interrupt: pin A routed to IRQ
42
5287 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5288 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5289 Region
4: I/O ports at
4000 [size=
64]
5290 Expansion ROM at
<unassigned
> [disabled]
5291 Capabilities:
<access denied
>
5292 Kernel driver in use: i915
5293 </pre
></p
>
5295 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5297 <p
><pre
>
5298 struct intel_quirk intel_quirks[] = {
5300 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5301 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5304 </pre
></p
>
5306 <p
>According to the kernel module instructions (as seen using
5307 <tt
>modinfo i915
</tt
>), information about hardware needing the
5308 invert_brightness flag should be sent to the
5309 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5310 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5311 developers. But my email about the laptop sent
2013-
06-
03 have not
5313 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5314 web archive for the mailing list
</a
>, so I suspect they do not accept
5315 emails from non-subscribers. Because of this, I sent my patch also to
5316 the Debian bug tracking system instead as
5317 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5318 sure the patch is not lost.
</p
>
5320 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5321 with this problem working properly with Linux. If you use Gnome, your
5322 worries should be over at this point. But if you use KDE, there is
5323 something in KDE ignoring the invert_brightness setting and turning on
5324 the screen during login. I
've reported it to Debian as
5325 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5326 have no idea yet how to figure out exactly what subsystem is doing
5327 this. Perhaps you can help? Perhaps you know what the Gnome
5328 developers did to handle this, and this can give a clue to the KDE
5329 developers? Or you know where in KDE the screen brightness is changed
5330 during login? If so, please update the BTS report (or get in touch if
5331 you do not know how to update BTS).
</p
>
5333 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5334 acpi_backlight=vendor, to disable ACPI backlight support completely,
5335 as the ACPI information on the machine is trash and it is better to
5336 leave it to the intel video driver to control the screen
5337 backlight.
</p
>
5342 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5343 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5344 <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>
5345 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5346 <description><p
>Two days ago, I asked
5347 <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
5348 I could install Linux on a Packard Bell EasyNote LV computer
5349 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5350 with the obstacles put in the way of Linux users on a laptop with UEFI
5351 and Windows
8.
</p
>
5353 <p
>I never found out if the cause of my problems were the use of UEFI
5354 secure booting or fast boot. I suspect fast boot was the problem,
5355 causing the firmware to boot directly from HD without considering any
5356 key presses and alternative devices, but do not know UEFI settings
5357 enough to tell.
</p
>
5359 <p
>There is no way to install Linux on the machine in question without
5360 opening the box and disconnecting the hard drive! This is as far as I
5361 can tell, the only way to get access to the firmware setup menu
5362 without accepting the Windows
8 license agreement. I am told (and
5363 found description on how to) that it is possible to configure the
5364 firmware setup once booted into Windows
8. But as I believe the terms
5365 of that agreement are completely unacceptable, accepting the license
5366 was never an alternative. I do not enter agreements I do not intend
5367 to follow.
</p
>
5369 <p
>I feared I had to return the laptops and ask for a refund, and
5370 waste many hours on this, but luckily there was a way to get it to
5371 work. But I would not recommend it to anyone planning to run Linux on
5372 it, and I have become sceptical to Windows
8 certified laptops. Is
5373 this the way Linux will be forced out of the market place, by making
5374 it close to impossible for
"normal
" users to install Linux without
5375 accepting the Microsoft Windows license terms? Or at least not
5376 without risking to loose the warranty?
</p
>
5378 <p
>I
've updated the
5379 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5380 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5381 do not have to struggle as much as I did to get Linux into the
5384 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5385 Michael Tokarev and others for feedback and ideas.
</p
>
5390 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5391 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5392 <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>
5393 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5394 <description><p
>I
've run into quite a problem the last few days. I bought three
5395 new laptops for my parents and a few others. I bought Packard Bell
5396 Easynote LV to run Kubuntu on and use as their home computer. But I
5397 am completely unable to figure out how to install Linux on it. The
5398 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5399 instead of a BIOS to boot.
</p
>
5401 <p
>The problem is that I am unable to get it to PXE boot, and unable
5402 to get it to boot the Linux installer from my USB stick. I have yet
5403 to try the DVD install, and still hope it will work. when I turn on
5404 the computer, there is no information on what buttons to press to get
5405 the normal boot menu. I expect to get some boot menu to select PXE or
5406 USB stick booting. When booting, it first ask for the language to
5407 use, then for some regional settings, and finally if I will accept the
5408 Windows
8 terms of use. As these terms are completely unacceptable to
5409 me, I have no other choice but to turn off the computer and try again
5410 to get it to boot the Linux installer.
</p
>
5412 <p
>I have gathered my findings so far on a Linlap page about the
5413 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5414 EasyNote LV
</a
> model. If you have any idea how to get Linux
5415 installed on this machine, please get in touch or update that wiki
5416 page. If I can
't find a way to install Linux, I will have to return
5417 the laptop to the seller and find another machine for my parents.
</p
>
5419 <p
>I wonder, is this the way Linux will be forced out of the market
5420 using UEFI and
"secure boot
" by making it impossible to install Linux
5421 on new Laptops?
</p
>
5426 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5427 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5428 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5429 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5430 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5431 an operating system based on Debian intended for use in schools. It
5432 contain a turn-key solution for the computer network provided to
5433 pupils in the primary schools. It provide both the central server,
5434 network boot servers and desktop environments with heaps of
5435 educational software. The project was founded almost
12 years ago,
5436 2001-
07-
02. If you want to support the project, which is in need for
5437 cash to fund developer gatherings and other project related activity,
5438 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5439 donate some money
</a
>.
5441 <p
>A topic that come up again and again on the Debian Edu mailing
5442 lists and elsewhere, is the question on how to transform a Debian or
5443 Ubuntu installation into a Debian Edu installation. It isn
't very
5444 hard, and last week I wrote a script to replicate the steps done by
5445 the Debian Edu installer.
</p
>
5447 <p
>The script,
5448 <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/
>
5449 in the debian-edu-config package, will go through these six steps and
5450 transform an existing Debian Wheezy or Ubuntu (untested) installation
5451 into a Debian Edu Workstation:
</p
>
5455 <li
>Add skolelinux related APT sources.
</li
>
5456 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5457 <li
>Install debian-edu-install to load preseeding values and pull in
5458 our configuration.
</li
>
5459 <li
>Preseed debconf database with profile setup in
5460 /etc/debian-edu/config, and run tasksel to install packages
5461 according to the profile specified in the config above,
5462 overriding some of the Debian automation machinery.
</li
>
5463 <li
>Run debian-edu-cfengine-D installation to configure everything
5464 that could not be done using preseeding.
</li
>
5465 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5469 <p
>There are some steps in the Debian Edu installation that can not be
5470 replicated like this. Disk partitioning and LVM setup, for example.
5471 So this script just assume there is enough disk space to install all
5472 the needed packages.
</p
>
5474 <p
>The script was created to help a Debian Edu student working on
5475 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5476 Debian Edu client, and using it he can take the existing
5477 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5478 transform it into a fully functioning Debian Edu Workstation (or
5479 Roaming Workstation, or whatever :).
</p
>
5481 <p
>The default setting in the script is to create a KDE Workstation.
5482 If a LXDE based Roaming workstation is wanted instead, modify the
5483 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5485 <p
><pre
>
5486 PROFILE=
"Roaming-Workstation
"
5487 DESKTOP=
"lxde
"
5488 </pre
></p
>
5490 <p
>The script could even become useful to set up Debian Edu servers in
5491 the cloud, by starting with a virtual Debian installation at some
5492 virtual hosting service and setting up all the services on first
5498 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5499 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5500 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5501 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5502 <description><P
>In January,
5503 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5504 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5505 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5506 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5507 marvellous construction system from Denmark. We also created
5508 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5509 a place to take notes and write down our plans and hopes. And several
5510 people showed up to help. I was very happy to see the effect of my
5511 call. Since the small start, we have a debtags tag
5512 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5513 tag for LEGO related packages, and now count
10 packages related to
5514 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5516 <p
><table
>
5517 <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
>
5518 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5519 <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
>
5520 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5521 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5522 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5523 <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
>
5524 <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
>
5525 <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
>
5526 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5527 </table
></p
>
5529 <p
>Some of these are available in Wheezy, and all but one are
5530 currently available in Jessie/testing. leocad is so far only
5531 available in experimental.
</p
>
5533 <p
>If you care about LEGO in Debian, please join us on IRC and help
5534 adding the rest of the great free software tools available on Linux
5535 for LEGO designers.
</p
>
5540 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5541 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5542 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5543 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5544 <description><p
>When I woke up this morning, I was very happy to see that the
5545 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5546 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5547 Debian release, and I expect to move my machines at home over to it fairly
5550 <p
>The new debian release contain heaps of new stuff, and one program
5551 in particular make me very happy to see included. The
5552 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5553 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5554 included for the first time. Alongside similar programs like
5555 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5556 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5557 it allow for visual programming where syntax errors can not happen,
5558 and a friendly programming environment for learning to control the
5559 computer. Scratch will also be included in the next release of Debian
5562 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5563 Edu/Skolelinux release too. The
5564 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5565 alpha release
</a
> went out last week, and the next should soon
5571 <title>Isenkram
0.2 finally in the Debian archive
</title>
5572 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5573 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5574 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5575 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5576 package
</a
> finally made it into the archive, after lingering in NEW
5577 for many months. I uploaded it to the Debian experimental suite
5578 2013-
01-
27, and today it was accepted into the archive.
</p
>
5580 <p
>Isenkram is a system for suggesting to users what packages to
5581 install to work with a pluggable hardware device. The suggestion pop
5582 up when the device is plugged in. For example if a Lego Mindstorm NXT
5583 is inserted, it will suggest to install the program needed to program
5584 the NXT controller. Give it a go, and report bugs and suggestions to
5590 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5591 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5592 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5593 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5594 <description><p
>My
5595 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5596 bitcoin related blog post
</a
> mentioned that the new
5597 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5598 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5599 2013-
01-
19, and have been available in unstable since then. It was
5600 automatically copied to Ubuntu, and is available in their Raring
5601 version too.
</p
>
5603 <p
>But there is a strange problem with the build that block this new
5604 version from being available on the i386 and kfreebsd-i386
5605 architectures. For some strange reason, the autobuilders in Debian
5606 for these architectures fail to run the test suite on these
5607 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5608 We are so far unable to reproduce it when building it manually, and
5609 no-one have been able to propose a fix. If you got an idea what is
5610 failing, please let us know via the BTS.
</p
>
5612 <p
>One feature that is annoying me with of the bitcoin client, because
5613 I often run low on disk space, is the fact that the client will exit
5614 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5615 #
696715</a
>). So make sure you have enough disk space when you run
5618 <p
>As usual, if you use bitcoin and want to show your support of my
5619 activities, please send Bitcoin donations to my address
5620 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5625 <title>Welcome to the world, Isenkram!
</title>
5626 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5627 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5628 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5629 <description><p
>Yesterday, I
5630 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5631 for testers
</a
> for my prototype for making Debian better at handling
5632 pluggable hardware devices, which I
5633 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5634 out to create
</a
> earlier this month. Several valuable testers showed
5635 up, and caused me to really want to to open up the development to more
5636 people. But before I did this, I want to come up with a sensible name
5637 for this project. Today I finally decided on a new name, and I have
5638 renamed the project from hw-support-handler to this new name. In the
5639 process, I moved the source to git and made it available as a
5640 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5641 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5642 To fetch and build the latest version of the source, use
</p
>
5645 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5646 cd isenkram
&& git-buildpackage -us -uc
5649 <p
>I have not yet adjusted all files to use the new name yet. If you
5650 want to hack on the source or improve the package, please go ahead.
5651 But please talk to me first on IRC or via email before you do major
5652 changes, to make sure we do not step on each others toes. :)
</p
>
5654 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5655 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5656 stuff, in other words. I
've been told it is the Norwegian variant of
5657 the German word eisenkram, for those that are familiar with that
5660 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5661 instructions, to avoid confusing people with an error from the signing
5664 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5665 clone argument to avoid the need for authentication.
</p
>
5670 <title>First prototype ready making hardware easier to use in Debian
</title>
5671 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5672 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5673 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5674 <description><p
>Early this month I set out to try to
5675 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5676 the Debian support for pluggable hardware devices
</a
>. Now my
5677 prototype is working, and it is ready for a larger audience. To test
5679 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5680 from the Debian Edu subversion repository
</a
>, build and install the
5681 package. You might have to log out and in again activate the
5682 autostart script.
</p
>
5684 <p
>The design is simple:
</p
>
5688 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5689 hw-support-handlerd to start when the user log in.
</li
>
5691 <li
>This program listen for kernel events about new hardware (directly
5692 from the kernel like udev does), not using HAL dbus events as I
5693 initially did.
</li
>
5695 <li
>When new hardware is inserted, look up the hardware modalias in
5696 the APT database, a database
5697 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5698 via HTTP
</a
> and a database available as part of the package.
</li
>
5700 <li
>If a package is mapped to the hardware in question, the package
5701 isn
't installed yet and this is the first time the hardware was
5702 plugged in, show a desktop notification suggesting to install the
5703 package or packages.
</li
>
5705 <li
>If the user click on the
'install package now
' button, ask
5706 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5708 <li
>aptdaemon ask for root password or sudo password, and install the
5709 package while showing progress information in a window.
</li
>
5713 <p
>I still need to come up with a better name for the system. Here
5714 are some screen shots showing the prototype in action. First the
5715 notification, then the password request, and finally the request to
5716 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5718 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5719 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5720 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5721 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5722 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5724 <p
>The prototype still need to be improved with longer timeouts, but
5725 is already useful. The database of hardware to package mappings also
5726 need more work. It is currently compatible with the Ubuntu way of
5727 storing such information in the package control file, but could be
5728 changed to use other formats instead or in addition to the current
5729 method. I
've dropped the use of discover for this mapping, as the
5730 modalias approach is more flexible and easier to use on Linux as long
5731 as the Linux kernel expose its modalias strings directly.
</p
>
5733 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5734 here is the command required to check out and build the source: Use
5735 '<tt
>svn checkout
5736 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5737 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5738 devscripts package.
</p
>
5740 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5741 renamed to Isenkram and the source moved from the Debian Edu
5742 subversion repository to a Debian collab-maint git repository. See
5743 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5744 instructions
</a
> for details.
</p
>
5749 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5750 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5751 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5752 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5753 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5754 suddenly in bed. With a quiet whimper, it went completely quiet and
5755 black. The power button was no longer able to turn it on. It was a
5756 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5757 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5758 Compaq I had before that. Now I need to find a replacement. To keep
5759 going during Christmas, I moved the one year old SSD disk to my old
5760 X40 where it fitted (only one I had left that could use it), but it is
5761 not a durable solution.
5763 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5764 got a new one more than
10 years ago. It still holds true.:)
</p
>
5768 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5769 than A4).
</li
>
5770 <li
>Robust, it will be in my backpack every day.
</li
>
5771 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5772 <li
>Long battery life time. Preferable a week.
</li
>
5773 <li
>Internal WIFI network card.
</li
>
5774 <li
>Internal Twisted Pair network card.
</li
>
5775 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5776 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5777 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5779 <li
>Hardware supported by Debian Stable, ie the default kernel and
5780 X.org packages.
</li
>
5781 <li
>Quiet, preferably fan free (or at least not using the fan most of
5786 <p
>You will notice that there are no RAM and CPU requirements in the
5787 list. The reason is simply that the specifications on laptops the
5788 last
10-
15 years have been sufficient for my needs, and I have to look
5789 at other features to choose my laptop. But are there still made as
5790 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5791 robust, and Thinkpads seem to be heading in the wrong direction since
5792 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5793 still be useful.
</p
>
5795 <p
>Perhaps I should rethink my needs, and look for a pad with an
5796 external keyboard? I
'll have to check the
5797 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5798 well-supported laptops, or perhaps just buy one preinstalled from one
5799 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5800 Pre-loaded site
</a
>.
</p
>
5805 <title>How to find a browser plugin supporting a given MIME type
</title>
5806 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5807 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5808 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5809 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5810 install to get support for a given MIME type. Thanks to
5811 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5812 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5813 Unfortunately, not very many packages provide the needed meta
5814 information, Anyway, here is a small script to look up all browser
5815 plugin packages announcing ther MIME support using this specification:
</p
>
5821 def pkgs_handling_mimetype(mimetype):
5826 version = pkg.candidate
5828 version = pkg.installed
5831 record = version.record
5832 if not record.has_key(
'Npp-MimeType
'):
5834 mime_types = record[
'Npp-MimeType
'].split(
',
')
5835 for t in mime_types:
5836 t = t.rstrip().strip()
5838 thepkgs.append(pkg.name)
5840 mimetype =
"audio/ogg
"
5841 if
1 < len(sys.argv):
5842 mimetype = sys.argv[
1]
5843 print
"Browser plugin packages supporting %s:
" % mimetype
5844 for pkg in pkgs_handling_mimetype(mimetype):
5845 print
" %s
" %pkg
5848 <p
>It can be used like this to look up a given MIME type:
</p
>
5851 % ./apt-find-browserplug-for-mimetype
5852 Browser plugin packages supporting audio/ogg:
5854 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5855 Browser plugin packages supporting application/x-shockwave-flash:
5856 browser-plugin-gnash
5860 <p
>In Ubuntu this mechanism is combined with support in the browser
5861 itself to query for plugins and propose to install the needed
5862 packages. It would be great if Debian supported such feature too. Is
5863 anyone working on adding it?
</p
>
5865 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5866 request for icweasel support for this feature is
5867 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5868 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5869 of manpower and wish for a different design is the reason thus feature
5870 is not yet in iceweasel from Debian.
</p
>
5875 <title>What is the most supported MIME type in Debian?
</title>
5876 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5878 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5879 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5880 proposal to add AppStream information to the Debian archive
</a
>, is a
5881 proposal to make it possible for a Desktop application to propose to
5882 the user some package to install to gain support for a given MIME
5883 type, font, library etc. that is currently missing. With such
5884 mechanism in place, it would be possible for the desktop to
5885 automatically propose and install leocad if some LDraw file is
5886 downloaded by the browser.
</p
>
5888 <p
>To get some idea about the current content of the archive, I decided
5889 to write a simple program to extract all .desktop files from the
5890 Debian archive and look up the claimed MIME support there. The result
5892 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5893 site
</a
>. Using the collected information, it become possible to
5894 answer the question in the title. Here are the
20 most supported MIME
5895 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5896 The complete list is available from the link above.
</p
>
5898 <p
><strong
>Debian Stable:
</strong
></p
>
5902 ----- -----------------------
5918 18 application/x-ogg
5925 <p
><strong
>Debian Testing:
</strong
></p
>
5929 ----- -----------------------
5945 18 application/x-ogg
5952 <p
><strong
>Debian Unstable:
</strong
></p
>
5956 ----- -----------------------
5973 18 application/x-ogg
5979 <p
>I am told that PackageKit can provide an API to access the kind of
5980 information mentioned in DEP-
11. I have not yet had time to look at
5981 it, but hope the PackageKit people in Debian are on top of these
5984 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5985 discovering a typo in my script.
</p
>
5990 <title>Using modalias info to find packages handling my hardware
</title>
5991 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5992 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5993 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
5994 <description><p
>Yesterday, I wrote about the
5995 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
5996 values provided by the Linux kernel
</a
> following my hope for
5997 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
5998 dongle support in Debian
</a
>. Using this knowledge, I have tested how
5999 modalias values attached to package names can be used to map packages
6000 to hardware. This allow the system to look up and suggest relevant
6001 packages when I plug in some new hardware into my machine, and replace
6002 discover and discover-data as the database used to map hardware to
6005 <p
>I create a modaliases file with entries like the following,
6006 containing package name, kernel module name (if relevant, otherwise
6007 the package name) and globs matching the relevant hardware
6010 <p
><blockquote
>
6011 Package: package-name
6012 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6013 </blockquote
></p
>
6015 <p
>It is fairly trivial to write code to find the relevant packages
6016 for a given modalias value using this file.
</p
>
6018 <p
>An entry like this would suggest the video and picture application
6019 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6021 <p
><blockquote
>
6023 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6024 </blockquote
></p
>
6026 <p
>An entry like this would suggest the pcmciautils package when a
6027 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6029 <p
><blockquote
>
6030 Package: pcmciautils
6031 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6032 </blockquote
></p
>
6034 <p
>An entry like this would suggest the package colorhug-client when
6035 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6037 <p
><blockquote
>
6038 Package: colorhug-client
6039 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6040 </blockquote
></p
>
6042 <p
>I believe the format is compatible with the format of the Packages
6043 file in the Debian archive. Ubuntu already uses their Packages file
6044 to store their mappings from packages to hardware.
</p
>
6046 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6047 announce the hardware it support in a way my prototype understand.
6048 This allow those publishing packages in an APT source outside the
6049 Debian archive as well as those backporting packages to make sure the
6050 hardware mapping are included in the package meta information. I
've
6051 tested such header in the pymissile package, and its modalias mapping
6052 is working as it should with my prototype. It even made it to Ubuntu
6055 <p
>To test if it was possible to look up supported hardware using only
6056 the shell tools available in the Debian installer, I wrote a shell
6057 implementation of the lookup code. The idea is to create files for
6058 each modalias and let the shell do the matching. Please check out and
6060 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6061 shell script. It run without any extra dependencies and fetch the
6062 hardware mappings from the Debian archive and the subversion
6063 repository where I currently work on my prototype.
</p
>
6065 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6066 install yubikey-personalization:
</p
>
6068 <p
><blockquote
>
6069 % ./hw-support-lookup
6070 <br
>yubikey-personalization
6072 </blockquote
></p
>
6074 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6075 propose to install the pcmciautils package:
</p
>
6077 <p
><blockquote
>
6078 % ./hw-support-lookup
6079 <br
>pcmciautils
6081 </blockquote
></p
>
6083 <p
>If you know of any hardware-package mapping that should be added to
6084 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6085 database
</a
>, please tell me about it.
</p
>
6087 <p
>It could be possible to generate several of the mappings between
6088 packages and hardware. One source would be to look at packages with
6089 kernel modules, ie packages with *.ko files in /lib/modules/, and
6090 extract their modalias information. Another would be to look at
6091 packages with udev rules, ie packages with files in
6092 /lib/udev/rules.d/, and extract their vendor/model information to
6093 generate a modalias matching rule. I have not tested any of these to
6094 see if it work.
</p
>
6096 <p
>If you want to help implementing a system to let us propose what
6097 packages to install when new hardware is plugged into a Debian
6098 machine, please send me an email or talk to me on
6099 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6104 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6105 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6106 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6107 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6108 <description><p
>While looking into how to look up Debian packages based on hardware
6109 information, to find the packages that support a given piece of
6110 hardware, I refreshed my memory regarding modalias values, and decided
6111 to document the details. Here are my findings so far, also available
6113 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6114 Debian Edu subversion repository
</a
>:
6116 <p
><strong
>Modalias decoded
</strong
></p
>
6118 <p
>This document try to explain what the different types of modalias
6119 values stands for. It is in part based on information from
6120 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6121 &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;,
6122 &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
6123 &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;.
6125 <p
>The modalias entries for a given Linux machine can be found using
6126 this shell script:
</p
>
6129 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6132 <p
>The supported modalias globs for a given kernel module can be found
6133 using modinfo:
</p
>
6136 % /sbin/modinfo psmouse | grep alias:
6137 alias: serio:ty05pr*id*ex*
6138 alias: serio:ty01pr*id*ex*
6142 <p
><strong
>PCI subtype
</strong
></p
>
6144 <p
>A typical PCI entry can look like this. This is an Intel Host
6145 Bridge memory controller:
</p
>
6147 <p
><blockquote
>
6148 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6149 </blockquote
></p
>
6151 <p
>This represent these values:
</p
>
6156 sv
00001028 (subvendor)
6157 sd
000001AD (subdevice)
6159 sc
00 (bus subclass)
6163 <p
>The vendor/device values are the same values outputted from
'lspci
6164 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6165 0600. The
0600 class is a host bridge. Other useful bus values are
6166 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6168 <p
>Not sure how to figure out the interface value, nor what it
6171 <p
><strong
>USB subtype
</strong
></p
>
6173 <p
>Some typical USB entries can look like this. This is an internal
6174 USB hub in a laptop:
</p
>
6176 <p
><blockquote
>
6177 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6178 </blockquote
></p
>
6180 <p
>Here is the values included in this alias:
</p
>
6183 v
1D6B (device vendor)
6184 p
0001 (device product)
6186 dc
09 (device class)
6187 dsc
00 (device subclass)
6188 dp
00 (device protocol)
6189 ic
09 (interface class)
6190 isc
00 (interface subclass)
6191 ip
00 (interface protocol)
6194 <p
>The
0900 device class/subclass means hub. Some times the relevant
6195 class is in the interface class section. For a simple USB web camera,
6196 these alias entries show up:
</p
>
6198 <p
><blockquote
>
6199 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6200 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6201 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6202 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6203 </blockquote
></p
>
6205 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6206 camera),
0101 is audio control device and
0102 is audio streaming (aka
6207 microphone). Thus this is a camera with microphone included.
</p
>
6209 <p
><strong
>ACPI subtype
</strong
></p
>
6211 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6212 receiver in a Thinkpad X40:
</p
>
6214 <p
><blockquote
>
6215 acpi:IBM0071:PNP0511:
6216 </blockquote
></p
>
6218 <p
>The values between the colons are IDs.
</p
>
6220 <p
><strong
>DMI subtype
</strong
></p
>
6222 <p
>The DMI table contain lots of information about the computer case
6223 and model. This is an entry for a IBM Thinkpad X40, fetched from
6224 /sys/devices/virtual/dmi/id/modalias:
</p
>
6226 <p
><blockquote
>
6227 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6228 </blockquote
></p
>
6230 <p
>The values present are
</p
>
6233 bvn IBM (BIOS vendor)
6234 bvr
1UETB
6WW(
1.66) (BIOS version)
6235 bd
06/
15/
2005 (BIOS date)
6236 svn IBM (system vendor)
6237 pn
2371H4G (product name)
6238 pvr ThinkPadX40 (product version)
6239 rvn IBM (board vendor)
6240 rn
2371H4G (board name)
6241 rvr NotAvailable (board version)
6242 cvn IBM (chassis vendor)
6243 ct
10 (chassis type)
6244 cvr NotAvailable (chassis version)
6247 <p
>The chassis type
10 is Notebook. Other interesting values can be
6248 found in the dmidecode source:
</p
>
6252 4 Low Profile Desktop
6265 17 Main Server Chassis
6266 18 Expansion Chassis
6268 20 Bus Expansion Chassis
6269 21 Peripheral Chassis
6271 23 Rack Mount Chassis
6280 <p
>The chassis type values are not always accurately set in the DMI
6281 table. For example my home server is a tower, but the DMI modalias
6282 claim it is a desktop.
</p
>
6284 <p
><strong
>SerIO subtype
</strong
></p
>
6286 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6287 test machine:
</p
>
6289 <p
><blockquote
>
6290 serio:ty01pr00id00ex00
6291 </blockquote
></p
>
6293 <p
>The values present are
</p
>
6302 <p
>This type is supported by the psmouse driver. I am not sure what
6303 the valid values are.
</p
>
6305 <p
><strong
>Other subtypes
</strong
></p
>
6307 <p
>There are heaps of other modalias subtypes according to
6308 file2alias.c. There is the rest of the list from that source: amba,
6309 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6310 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6311 vmbus, x86cpu and zorro. I did not spend time documenting all of
6312 these, as they do not seem relevant for my intended use with mapping
6313 hardware to packages when new stuff is inserted during run time.
</p
>
6315 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6317 <p
>To check which kernel modules provide support for a given modalias,
6318 one can use the following shell script:
</p
>
6321 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6322 echo
"$id
" ; \
6323 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6327 <p
>The output can look like this (only the first few entries as the
6328 list is very long on my test machine):
</p
>
6332 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6334 FATAL: Module acpi:device: not found.
6336 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6337 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6338 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6339 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6340 acpi:IBM0071:PNP0511:
6341 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6342 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6343 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6347 <p
>If you want to help implementing a system to let us propose what
6348 packages to install when new hardware is plugged into a Debian
6349 machine, please send me an email or talk to me on
6350 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6352 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6353 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6354 in /sys/ with space in them.
</p
>
6359 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6360 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6361 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6362 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6363 <description><p
>As part of my investigation on how to improve the support in Debian
6364 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6365 Launcher and updated the Debian package
6366 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6367 sure udev will fix the device permissions when it is plugged in. I
6368 also added a
"Modaliases
" header to test it in the Debian archive and
6369 hopefully make the package be proposed by jockey in Ubuntu when a user
6370 plug in his rocket launcher. In the process I moved the source to a
6371 git repository under collab-maint, to make it easier for any DD to
6372 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6373 is not very active, but the software still work for me even after five
6374 years of relative silence. The new git repository is not listed in
6375 the uploaded package yet, because I want to test the other changes a
6376 bit more before I upload the new version. If you want to check out
6377 the new version with a .desktop file included, visit the
6378 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6379 view
</a
> or use
"<tt
>git clone
6380 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6385 <title>Lets make hardware dongles easier to use in Debian
</title>
6386 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6388 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6389 <description><p
>One thing that annoys me with Debian and Linux distributions in
6390 general, is that there is a great package management system with the
6391 ability to automatically install software packages by downloading them
6392 from the distribution mirrors, but no way to get it to automatically
6393 install the packages I need to use the hardware I plug into my
6394 machine. Even if the package to use it is easily available from the
6395 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6396 suggest to automatically install the python-nxt, nbc and t2n packages
6397 I need to talk to it. When I plug in a Yubikey, it could propose the
6398 yubikey-personalization package. The information required to do this
6399 is available, but no-one have pulled all the pieces together.
</p
>
6401 <p
>Some years ago, I proposed to
6402 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6403 the discover subsystem to implement this
</a
>. The idea is fairly
6408 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6409 starting when a user log in.
</li
>
6411 <li
>Set this program up to listen for kernel events emitted when new
6412 hardware is inserted into the computer.
</li
>
6414 <li
>When new hardware is inserted, look up the hardware ID in a
6415 database mapping to packages, and take note of any non-installed
6416 packages.
</li
>
6418 <li
>Show a message to the user proposing to install the discovered
6419 package, and make it easy to install it.
</li
>
6423 <p
>I am not sure what the best way to implement this is, but my
6424 initial idea was to use dbus events to discover new hardware, the
6425 discover database to find packages and
6426 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6429 <p
>Yesterday, I found time to try to implement this idea, and the
6430 draft package is now checked into
6431 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6432 Debian Edu subversion repository
</a
>. In the process, I updated the
6433 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6434 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6435 the relevant packages in Debian, and uploaded a new version
6436 2.2013.01.09 to unstable. I also discovered that the current
6437 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6438 package in Debian no longer discovered any USB devices, because
6439 /proc/bus/usb/devices is no longer present. I ported it to use
6440 libusb as a fall back option to get it working. The fixed package
6441 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6442 because of the freeze).
</p
>
6444 <p
>With this prototype in place, I can insert my Yubikey, and get this
6445 desktop notification to show up (only once, the first time it is
6446 inserted):
</p
>
6448 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6450 <p
>For this prototype to be really useful, some way to automatically
6451 install the proposed packages by pressing the
"Please install
6452 program(s)
" button should to be implemented.
</p
>
6454 <p
>If this idea seem useful to you, and you want to help make it
6455 happen, please help me update the discover-data database with mappings
6456 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6457 list the package you would like to have installed when a given
6458 hardware device is inserted into your computer, and report bugs using
6459 reportbug if it isn
't. Or, if you know of a better way to provide
6460 such mapping, please let me know.
</p
>
6462 <p
>This prototype need more work, and there are several questions that
6463 should be considered before it is ready for production use. Is dbus
6464 the correct way to detect new hardware? At the moment I look for HAL
6465 dbus events on the system bus, because that is the events I could see
6466 on my Debian Squeeze KDE desktop. Are there better events to use?
6467 How should the user be notified? Is the desktop notification
6468 mechanism the best option, or should the background daemon raise a
6469 popup instead? How should packages be installed? When should they
6470 not be installed?
</p
>
6472 <p
>If you want to help getting such feature implemented in Debian,
6473 please send me an email. :)
</p
>
6478 <title>New IRC channel for LEGO designers using Debian
</title>
6479 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6480 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6481 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6482 <description><p
>During Christmas, I have worked a bit on the Debian support for
6483 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6484 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6485 discovered I had to build all the tools myself because none were
6486 already in Debian Squeeze. If Debian support for LEGO is something
6487 you care about, please join me on the IRC channel
6488 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6489 irc.debian.org). There is a lot that could be done to improve the
6490 Debian support for LEGO designers. For example both CAD software
6491 and Mindstorm compilers are missing. :)
</p
>
6493 <p
>Update
2012-
01-
03: A
6494 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6495 including links to Lego related packages is now available.
</p
>
6500 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6501 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6502 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6503 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6504 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6505 year! I hope next year will prove to be a good year.
</p
>
6507 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6508 decentralised
"currency
" that allow people to transfer bitcoins
6509 between each other with minimal overhead, is a very interesting
6510 experiment. And as I wrote a few days ago, the bitcoin situation in
6511 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6512 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6513 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6514 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6515 for one of the ftpmasters to approve the new bitcoin-qt package
6518 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6519 team in Debian, you can easily test the package in Debian Squeeze
6520 using the following steps to get a set of working packages:
</p
>
6522 <blockquote
><pre
>
6523 git clone git://git.debian.org/git/collab-maint/bitcoin
6525 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6526 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6527 </pre
></blockquote
>
6529 <p
>You might have to install some build dependencies as well. The
6530 list of commands should give you two packages, bitcoind and
6531 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6532 client will download the complete set of bitcoin
"blocks
", which need
6533 around
5.6 GiB of data on my machine at the moment. Make sure your
6534 ~/.bitcoin/ directory have lots of spare room if you want to download
6535 all the blocks. The client will warn if the disk is getting full, so
6536 there is not really a problem if you got too little room, but you will
6537 not be able to get all the features out of the client.
</p
>
6539 <p
>As usual, if you use bitcoin and want to show your support of my
6540 activities, please send Bitcoin donations to my address
6541 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6546 <title>A word on bitcoin support in Debian
</title>
6547 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6548 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6549 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6550 <description><p
>It has been a while since I wrote about
6551 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6552 peer-to-peer based crypto-currency, and the reason is simply that I
6553 have been busy elsewhere. But two days ago, I started looking at the
6554 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6555 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6556 is now maintained by a
6557 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6558 people
</a
>, and the grunt work had already been done by this team. We
6559 owe a huge thank you to all these team members. :)
6560 But I was sad to discover that the bitcoin client is missing in
6561 Wheezy. It is only available in Sid (and an outdated client from
6562 backports). The client had several RC bugs registered in BTS blocking
6563 it from entering testing. To try to help the team and improve the
6564 situation, I spent some time providing patches and triaging the bug
6565 reports. I also had a look at the bitcoin package available from Matt
6567 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6568 Ubuntu
</a
>, and moved the useful pieces from that version into the
6569 Debian package.
</p
>
6571 <p
>After checking with the main package maintainer Jonas Smedegaard on
6572 IRC, I pushed several patches into the collab-maint git repository to
6573 improve the package. It now contains fixes for the RC issues (not from
6574 me, but fixed by Scott Howard), build rules for a Qt GUI client
6575 package, konqueror support for the bitcoin: URI and bash completion
6576 setup. As I work on Debian Squeeze, I also created
6577 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6578 patch to backport
</a
> the latest version. Jonas is going to look at
6579 it and try to integrate it into the git repository before uploading a
6580 new version to unstable.
6582 <p
>I would very much like bitcoin to succeed, to get rid of the
6583 centralized control currently exercised in the monetary system. I
6584 find it completely unacceptable that the USA government is collecting
6585 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6586 that the major credit card companies can block legal money
6587 transactions to Wikileaks. But for bitcoin to succeed, more people
6588 need to use bitcoins, and more people need to accept bitcoins when
6589 they sell products and services. Improving the bitcoin support in
6590 Debian is a small step in the right direction, but not enough.
6591 Unfortunately the user experience when browsing the web and wanting to
6592 pay with bitcoin is still not very good. The bitcoin: URI is a step
6593 in the right direction, but need to work in most or every browser in
6594 use. Also the bitcoin-qt client is too heavy to fire up to do a
6595 quick transaction. I believe there are other clients available, but
6596 have not tested them.
</p
>
6599 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6600 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6601 I received
20.15 BTC so far on the address I provided in my blog two
6602 years ago, as can be
6603 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6604 on the blockexplorer service
</a
>. Thank you everyone for your
6605 donation. The blockexplorer service demonstrates quite well that
6606 bitcoin is not quite anonymous and untracked. :) I wonder if the
6607 number of users have gone up since then. If you use bitcoin and want
6608 to show your support of my activity, please send Bitcoin donations to
6609 the same address as last time,
6610 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6615 <title>Git repository for song book for Computer Scientists
</title>
6616 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6618 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6619 <description><p
>As I
6620 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6621 this summer
</a
>, I have created a Computer Science song book a few
6622 years ago, and today I finally found time to create a public
6623 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6624 repository for the project
</a
>.
</p
>
6626 <p
>If you want to help out, please clone the source and submit patches
6627 to the HTML version. To generate the PDF and PostScript version,
6628 please use prince XML, or let me know about a useful free software
6629 processor capable of creating a good looking PDF from the HTML.
</p
>
6631 <p
>Want to sing? You can still find the song book in HTML, PDF and
6632 PostScript formats at
6633 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6634 Science Songbook
</a
>.
</p
>
6639 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6640 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6642 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6643 <description><p
>I dag fyller
6644 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6645 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6646 si gratulerer med dagen, Debian!
</p
>
6651 <title>Song book for Computer Scientists
</title>
6652 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6653 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6654 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6655 <description><p
>Many years ago, while studying Computer Science at the
6656 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6657 collecting computer related songs for use at parties. The original
6658 version was written in LaTeX, but a few years ago I got help from
6659 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6660 while keeping the ability to create a nice book in PDF format. I have
6661 not had time to maintain the book for a while now, and guess I should
6662 put it up on some public version control repository where others can
6663 help me extend and update the book. If anyone is volunteering to help
6664 me with this, send me an email. Also let me know if there are songs
6665 missing in my book.
</p
>
6667 <p
>I have not mentioned the book on my blog so far, and it occured to
6668 me today that I really should let all my readers share the joys of
6669 singing out load about programming, computers and computer networks.
6670 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6671 12</a
> is about to start (and I am not going). Want to sing? Check
6672 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6673 Computer Science Songbook
</a
>.
6678 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6679 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6680 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6681 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6682 <description><p
>At work we have heaps of servers. I believe the total count is
6683 around
1000 at the moment. To be able to get help from the vendors
6684 when something go wrong, we want to keep the firmware on the servers
6685 up to date. If the firmware isn
't the latest and greatest, the
6686 vendors typically refuse to start debugging any problems until the
6687 firmware is upgraded. So before every reboot, we want to upgrade the
6688 firmware, and we would really like everyone handling servers at the
6689 university to do this themselves when they plan to reboot a machine.
6690 For that to happen we at the unix server admin group need to provide
6691 the tools to do so.
</p
>
6693 <p
>To make firmware upgrading easier, I am working on a script to
6694 fetch and install the latest firmware for the servers we got. Most of
6695 our hardware are from Dell and HP, so I have focused on these servers
6696 so far. This blog post is about the Dell part.
</P
>
6698 <p
>On the Dell FTP site I was lucky enough to find
6699 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6700 with firmware information for all
11th generation servers, listing
6701 which firmware should be used on a given model and where on the FTP
6702 site I can find it. Using a simple perl XML parser I can then
6703 download the shell scripts Dell provides to do firmware upgrades from
6704 within Linux and reboot when all the firmware is primed and ready to
6705 be activated on the first reboot.
</p
>
6707 <p
>This is the Dell related fragment of the perl code I am working on.
6708 Are there anyone working on similar tools for firmware upgrading all
6709 servers at a site? Please get in touch and lets share resources.
</p
>
6711 <p
><pre
>
6715 use File::Temp qw(tempdir);
6717 # Install needed RHEL packages if missing
6719 'XML::Simple
' =
> 'perl-XML-Simple
',
6721 for my $module (keys %rhelmodules) {
6722 eval
"use $module;
";
6724 my $pkg = $rhelmodules{$module};
6725 system(
"yum install -y $pkg
");
6726 eval
"use $module;
";
6730 my $errorsto =
'pere@hungry.com
';
6736 sub run_firmware_script {
6737 my ($opts, $script) = @_;
6739 print STDERR
"fail: missing script name\n
";
6742 print STDERR
"Running $script\n\n
";
6744 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6745 print STDERR
"success: firmware script ran succcessfully\n
";
6747 print STDERR
"fail: firmware script returned error\n
";
6751 sub run_firmware_scripts {
6752 my ($opts, @dirs) = @_;
6753 # Run firmware packages
6754 for my $dir (@dirs) {
6755 print STDERR
"info: Running scripts in $dir\n
";
6756 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6757 while (my $s = readdir $dh) {
6758 next if $s =~ m/^\.\.?/;
6759 run_firmware_script($opts,
"$dir/$s
");
6767 print STDERR
"info: Downloading $url\n
";
6768 system(
"wget --quiet \
"$url\
"");
6773 my $product = `dmidecode -s system-product-name`;
6776 if ($product =~ m/PowerEdge/) {
6778 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6779 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6781 my $tmpdir = tempdir(
6785 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6786 system(
'gunzip Catalog.xml.gz
');
6787 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6788 # -q is quiet, disabling interactivity and reducing console output
6789 my $fwopts =
"-q
";
6791 for my $url (@paths) {
6792 fetch_dell_fw($url);
6794 run_firmware_scripts($fwopts, $tmpdir);
6796 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6797 print STDERR
"error: Please report to $errorsto.\n
";
6801 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6802 print STDERR
"error: Please report to $errorsto.\n
";
6808 my $url =
"ftp://ftp.us.dell.com/$path
";
6812 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6813 # firmware packages to download from Dell. Only work for Linux
6814 # machines and
11th generation Dell servers.
6815 sub fetch_dell_fw_list {
6816 my $filename = shift;
6818 my $product = `dmidecode -s system-product-name`;
6820 my ($mybrand, $mymodel) = split(/\s+/, $product);
6822 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6824 my $xml = XMLin($filename);
6826 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6827 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6828 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6830 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6831 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6833 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6835 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6837 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6840 for my $component (@{$xml-
>{SoftwareComponent}}) {
6841 my $componenttype = $component-
>{ComponentType}-
>{value};
6843 # Drop application packages, only firmware and BIOS
6844 next if
'APAC
' eq $componenttype;
6846 my $cpath = $component-
>{path};
6847 for my $path (@paths) {
6848 if ($cpath =~ m%/$path$%) {
6849 push(@paths, $cpath);
6857 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6858 it could work on other platforms with some tweaking. Anyone know a
6859 index like Catalog.xml is available from HP for HP servers? At the
6860 moment I maintain a similar list manually and it is quickly getting
6866 <title>How is booting into runlevel
1 different from single user boots?
</title>
6867 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6868 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6869 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6870 <description><p
>Wouter Verhelst have some
6871 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6872 comments and opinions
</a
> on my blog post on
6873 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6874 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6875 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6876 default KDE desktop in Debian
</a
>. I only have time to address one
6877 small piece of his comment now, and though it best to address the
6878 misunderstanding he bring forward:
</p
>
6880 <p
><blockquote
>
6881 Currently, a system admin has four options: [...] boot to a
6882 single-user system (by adding
'single
' to the kernel command line;
6883 this runs rcS and rc1 scripts)
6884 </blockquote
></p
>
6886 <p
>This make me believe Wouter believe booting into single user mode
6887 and booting into runlevel
1 is the same. I am not surprised he
6888 believe this, because it would make sense and is a quite sensible
6889 thing to believe. But because the boot in Debian is slightly broken,
6890 runlevel
1 do not work properly and it isn
't the same as single user
6891 mode. I
'll try to explain what is actually happing, but it is a bit
6892 hard to explain.
</p
>
6894 <p
>Single user mode is defined like this in /etc/inittab:
6895 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6896 executed in single user mode is sulogin. Single user mode is a boot
6897 state
"between
" the runlevels, and when booting into single user mode,
6898 only the scripts in /etc/rcS.d/ are executed before the init process
6899 enters the single user state. When switching to runlevel
1, the state
6900 is in fact not ending in runlevel
1, but it passes through runlevel
1
6901 and end up in the single user mode (see /etc/rc1.d/S03single, which
6902 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6903 1. It is confusing that the
'S
' (single user) init mode is not the
6904 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6907 <p
>This summary might make it clearer. When booting for the first
6908 time into single user mode, the following commands are executed:
6909 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6910 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6911 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6912 trying to continue after visiting single user mode. Not all services
6913 are started again as they should, causing the machine to end up in an
6914 unpredicatble state. This is why Debian admins recommend rebooting
6915 after visiting single user mode.
</p
>
6917 <p
>A similar problem with runlevel
1 is caused by the amount of
6918 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6919 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6920 stopped when passing through the scripts in /etc/rc1.d/, and not
6921 started again when switching away from runlevel
1 to the runlevels
6922 2-
5. I believe the problem is best fixed by moving all the scripts
6923 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6924 functioning single user mode during boot.
</p
>
6926 <p
>I have spent several years investigating the Debian boot system,
6927 and discovered this problem a few years ago. I suspect it originates
6928 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6933 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6934 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6935 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6936 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6937 <description><p
>In the Debian boot system, several packages include scripts that
6938 are started from /etc/rcS.d/. In fact, there is a bite more of them
6939 than make sense, and this causes a few problems. What kind of
6940 problems, you might ask. There are at least two problems. The first
6941 is that it is not possible to recover a machine after switching to
6942 runlevel
1. One need to actually reboot to get the machine back to
6943 the expected state. The other is that single user boot will sometimes
6944 run into problems because some of the subsystems are activated before
6945 the root login is presented, causing problems when trying to recover a
6946 machine from a problem in that subsystem. A minor additional point is
6947 that moving more scripts out of rcS.d/ and into the other rc#.d/
6948 directories will increase the amount of scripts that can run in
6949 parallel during boot, and thus decrease the boot time.
</p
>
6951 <p
>So, which scripts should start from rcS.d/. In short, only the
6952 scripts that _have_ to execute before the root login prompt is
6953 presented during a single user boot should go there. Everything else
6954 should go into the numeric runlevels. This means things like
6955 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6956 the numeric runlevels. Today in Debian, there are around
115 init.d
6957 scripts that are started from rcS.d/, and most of them should be moved
6958 out. Do your package have one of them? Please help us make single
6959 user and runlevel
1 better by moving it.
</p
>
6961 <p
>Scripts setting up the screen, keyboard, system partitions
6962 etc. should still be started from rcS.d/, but there is for example no
6963 need to have the network enabled before the single user login prompt
6964 is presented.
</p
>
6966 <p
>As always, things are not so easy to fix as they sound. To keep
6967 Debian systems working while scripts migrate and during upgrades, the
6968 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6969 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6970 and the next ones can only be moved when their dependencies have been
6971 moved first. This migration must be done sequentially while we ensure
6972 that the package system upgrade packages in the right order to keep
6973 the system state correct. This will require some coordination when it
6974 comes to network related packages, but most of the packages with
6975 scripts that should migrate do not have anything in rcS.d/ depending
6976 on them. Some packages have already been updated, like the sudo
6977 package, while others are still left to do. I wish I had time to work
6978 on this myself, but real live constrains make it unlikely that I will
6979 find time to push this forward.
</p
>
6984 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6985 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6986 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6987 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6988 <description><p
>While at Debconf11, I have several times during discussions
6989 mentioned the issues I believe should be improved in Debian for its
6990 desktop to be useful for more people. The use case for this is my
6991 parents, which are currently running Kubuntu which solve the
6994 <p
>I suspect these four missing features are not very hard to
6995 implement. After all, they are present in Ubuntu, so if we wanted to
6996 do this in Debian we would have a source.
</p
>
7000 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7001 are new packages available for upgrades, a icon in the KDE status bar
7002 indicate this, and clicking on it will activate the simple upgrade
7003 tool to handle it. I have no problem guiding both of my parents
7004 through the process over the phone. If a kernel reboot is required,
7005 this too is indicated by the status bars and the upgrade tool. Last
7006 time I checked, nothing with the same features was working in KDE in
7009 <li
><strong
>Simple handling of missing Firefox browser
7010 plugins.
</strong
> When the browser encounter a MIME type it do not
7011 currently have a handler for, it will ask the user if the system
7012 should search for a package that would add support for this MIME type,
7013 and if the user say yes, the APT sources will be searched for packages
7014 advertising the MIME type in their control file (visible in the
7015 Packages file in the APT archive). If one or more packages are found,
7016 it is a simple click of the mouse to add support for the missing mime
7017 type. If the package require the user to accept some non-free
7018 license, this is explained to the user. The entire process make it
7019 more clear to the user why something do not work in the browser, and
7020 make the chances higher for the user to blame the web page authors and
7021 not the browser for any missing features.
</li
>
7023 <li
><strong
>Simple handling of missing multimedia codec/format
7024 handlers.
</strong
> When the media players encounter a format or codec
7025 it is not supporting, a dialog pop up asking the user if the system
7026 should search for a package that would add support for it. This
7027 happen with things like MP3, Windows Media or H
.264. The selection
7028 and installation procedure is very similar to the Firefox browser
7029 plugin handling. This is as far as I know implemented using a
7030 gstreamer hook. The end result is that the user easily get access to
7031 the codecs that are present from the APT archives available, while
7032 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7034 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7035 displaying a text/plain file in my Debian browser, it will propose to
7036 start emacs to show it. If I remember correctly, when doing the same
7037 in Kunbutu it show the file as a text file in the browser. At least I
7038 know Opera will show text files within the browser. I much prefer the
7039 latter behaviour.
</li
>
7043 <p
>There are other nice features as well, like the simplified suite
7044 upgrader, but given that I am the one mostly doing the dist-upgrade,
7045 it do not matter much.
</p
>
7047 <p
>I really hope we could get these features in place for the next
7048 Debian release. It would require the coordinated effort of several
7049 maintainers, but would make the end user experience a lot better.
</p
>
7054 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7055 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7056 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7057 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7058 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7059 site is build on Debian/Squeeze, and this platform was chosen because
7060 I am most familiar with Debian (being a Debian Developer for around
10
7061 years) because it is the latest stable Debian release which should get
7062 security support for a few years.
</p
>
7064 <p
>The web service is written in Perl, and depend on some perl modules
7065 that are missing in Debian at the moment. It would be great if these
7066 modules were added to the Debian archive, allowing anyone to set up
7067 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7068 in their own country using only Debian packages. The list of modules
7069 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7070 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7071 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7072 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7073 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7074 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7075 easier in the future.
</p
>
7077 <p
>Thanks to the great tools in Debian, getting the missing modules
7078 installed on my server was a simple call to
'cpan2deb Module::Name
'
7079 and
'dpkg -i
' to install the resulting package. But this leave me
7080 with the responsibility of tracking security problems, which I really
7081 do not have time for.
</p
>
7086 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7087 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7088 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7089 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7090 <description><p
>Here is a small update for my English readers. Most of my blog
7091 posts have been in Norwegian the last few weeks, so here is a short
7092 update in English.
</p
>
7094 <p
>The kids still keep me too busy to get much free software work
7095 done, but I did manage to organise a project to get a Norwegian port
7096 of the British service
7097 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7098 and it has been running for a month now. The entire project has been
7099 organised by me and two others. Around Christmas we gathered sponsors
7100 to fund the development work. In January I drafted a contract with
7101 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7102 and in February the development took place. Most of it involved
7103 converting the source to use GPS coordinates instead of British
7104 easting/northing, and the resulting code should be a lot easier to get
7105 running in any country by now. The Norwegian
7106 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7107 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7108 source and the source for administrative borders in Norway, and
7109 support for this had to be added/fixed.
</p
>
7111 <p
>The Norwegian version went live March
3th, and we spent the weekend
7112 polishing the system before we announced it March
7th. The system is
7113 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7114 problem reports in a few weeks. Soon we hope to announce the Android
7115 and iPhone versions making it even easier to report problems with the
7116 public infrastructure.
</p
>
7118 <p
>Perhaps something to consider for those of you in countries without
7119 such service?
</p
>
7124 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7125 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7126 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7127 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7128 <description><p
>The last few days I have looked at ways to track open security
7129 issues here at my work with the University of Oslo. My idea is that
7130 it should be possible to use the information about security issues
7131 available on the Internet, and check our locally
7132 maintained/distributed software against this information. It should
7133 allow us to verify that no known security issues are forgotten. The
7134 CVE database listing vulnerabilities seem like a great central point,
7135 and by using the package lists from Debian mapped to CVEs provided by
7136 the testing security team, I believed it should be possible to figure
7137 out which security holes were present in our free software
7138 collection.
</p
>
7140 <p
>After reading up on the topic, it became obvious that the first
7141 building block is to be able to name software packages in a unique and
7142 consistent way across data sources. I considered several ways to do
7143 this, for example coming up with my own naming scheme like using URLs
7144 to project home pages or URLs to the Freshmeat entries, or using some
7145 existing naming scheme. And it seem like I am not the first one to
7146 come across this problem, as MITRE already proposed and implemented a
7147 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7148 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7149 software, hardware and other platform components. The CPE ids are
7150 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7151 Vulnerability Database
</a
>, allowing me to look up know security
7152 issues for any CPE name. With this in place, all I need to do is to
7153 locate the CPE id for the software packages we use at the university.
7154 This is fairly trivial (I google for
'cve cpe $package
' and check the
7155 NVD entry if a CVE for the package exist).
</p
>
7157 <p
>To give you an example. The GNU gzip source package have the CPE
7158 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7159 check out, one could look up
7160 <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
7161 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7162 The most recent one is
7163 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7164 and at the bottom of the NVD page for this vulnerability the complete
7165 list of affected versions is provided.
</p
>
7167 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7168 for offline processing of issues. Using this dump, I
've written a
7169 small script taking a list of CPEs as input and list all CVEs
7170 affecting the packages represented by these CPEs. One give it CPEs
7171 with version numbers as specified above and get a list of open
7172 security issues out.
</p
>
7174 <p
>Of course for this approach to be useful, the quality of the NVD
7175 information need to be high. For that to happen, I believe as many as
7176 possible need to use and contribute to the NVD database. I notice
7178 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7179 map from CVE to CPE
</a
>, indicating that they are using the CPE
7180 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7182 <p
>To get an idea about the quality for free software, I spent some
7183 time making it possible to compare the CVE database from Debian with
7184 the CVE database in NVD. The result look fairly good, but there are
7185 some inconsistencies in NVD (same software package having several
7186 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7187 Debian believe are affected by a CVE). Hope to find time to improve
7188 the quality of NVD, but that require being able to get in touch with
7189 someone maintaining it. So far my three emails with questions and
7190 corrections have not seen any reply, but I hope contact can be
7191 established soon.
</p
>
7193 <p
>An interesting application for CPEs is cross platform package
7194 mapping. It would be useful to know which packages in for example
7195 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7196 this would be trivial if all linux distributions provided CPE entries
7197 for their packages.
</p
>
7202 <title>Which module is loaded for a given PCI and USB device?
</title>
7203 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7204 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7205 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7206 <description><p
>In the
7207 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7208 package in Debian, there is a script to report useful information
7209 about the running hardware for use when people report missing
7210 information. One part of this script that I find very useful when
7211 debugging hardware problems, is the part mapping loaded kernel module
7212 to the PCI device it claims. It allow me to quickly see if the kernel
7213 module I expect is driving the hardware I am struggling with. To see
7214 the output, make sure discover-data is installed and run
7215 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7216 one of my machines like this:
</p
>
7220 10de:
03eb i2c_nforce2
7223 10de:
03f0 snd_hda_intel
7232 <p
>The code in question look like this, slightly modified for
7233 readability and to drop the output to file descriptor
3:
</p
>
7236 if [ -d /sys/bus/pci/devices/ ] ; then
7237 echo loaded pci modules:
7239 cd /sys/bus/pci/devices/
7240 for address in * ; do
7241 if [ -d
"$address/driver/module
" ] ; then
7242 module=`cd $address/driver/module ; pwd -P | xargs basename`
7243 if grep -q
"^$module
" /proc/modules ; then
7244 address=$(echo $address |sed s/
0000://)
7245 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7246 echo
"$id $module
"
7255 <p
>Similar code could be used to extract USB device module
7259 if [ -d /sys/bus/usb/devices/ ] ; then
7260 echo loaded usb modules:
7262 cd /sys/bus/usb/devices/
7263 for address in * ; do
7264 if [ -d
"$address/driver/module
" ] ; then
7265 module=`cd $address/driver/module ; pwd -P | xargs basename`
7266 if grep -q
"^$module
" /proc/modules ; then
7267 address=$(echo $address |sed s/
0000://)
7268 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7269 if [
"$id
" ] ; then
7270 echo
"$id $module
"
7280 <p
>This might perhaps be something to include in other tools as
7286 <title>How to test if a laptop is working with Linux
</title>
7287 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7288 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7289 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7290 <description><p
>The last few days I have spent at work here at the
<a
7291 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7292 batch of computers will work with Linux. Every year for the last few
7293 years the university have organised shared bid of a few thousand
7294 computers, and this year HP won the bid. Two different desktops and
7295 five different laptops are on the list this year. We in the UNIX
7296 group want to know which one of these computers work well with RHEL
7297 and Ubuntu, the two Linux distributions we currently handle at the
7298 university.
</p
>
7300 <p
>My test method is simple, and I share it here to get feedback and
7301 perhaps inspire others to test hardware as well. To test, I PXE
7302 install the OS version of choice, and log in as my normal user and run
7303 a few applications and plug in selected pieces of hardware. When
7304 something fail, I make a note about this in the test matrix and move
7305 on. If I have some spare time I try to report the bug to the OS
7306 vendor, but as I only have the machines for a short time, I rarely
7307 have the time to do this for all the problems I find.
</p
>
7309 <p
>Anyway, to get to the point of this post. Here is the simple tests
7310 I perform on a new model.
</p
>
7314 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7315 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7316 RHEL5 and Debian Edu/Squeeze.
</li
>
7318 <li
>Is X.org working? If the graphical login screen show up after
7319 installation, X.org is working.
</li
>
7321 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7322 package mesa-utils on Ubuntu) and writing down the frames per second
7323 reported by the program.
</li
>
7325 <li
>Is sound working? With Gnome and KDE, a sound is played when
7326 logging in, and if I can hear this the test is successful. If there
7327 are several audio exits on the machine, I try them all and check if
7328 the Gnome/KDE audio mixer can control where to send the sound. I
7329 normally test this by playing
7330 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7331 video
</a
> in Firefox/Iceweasel.
</li
>
7333 <li
>Is the USB subsystem working? I test this by plugging in a USB
7334 memory stick and see if Gnome/KDE notices this.
</li
>
7336 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7337 I have lying around, and see if Gnome/KDE notices this.
</li
>
7339 <li
>Is any built in camera working? Test using cheese, and see if a
7340 picture from the v4l device show up.
</li
>
7342 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7343 any bluetooth devices are discovered. In my office, I normally see a
7346 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7347 memory modules lying around, and stick them in and see if Gnome/KDE
7348 notice this.
</li
>
7350 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7351 special button work, and if the laptop continue to work after
7354 <li
>For laptops, is the extra buttons working, like audio level,
7355 adjusting background light, switching on/off external video output,
7356 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7357 laptop to laptop, so I just write down which are working and which are
7360 <li
>Some laptops have smart card readers, finger print readers,
7361 acceleration sensors etc. I rarely test these, as I do not know how
7362 to quickly test if they are working or not, so I only document their
7363 existence.
</li
>
7367 <p
>By now I suspect you are really curious what the test results are
7368 for the HP machines I am testing. I
'm not done yet, so I will report
7369 the test results later. For now I can report that HP
8100 Elite work
7370 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7371 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7372 can see, I have most machines left to test. One interesting
7373 observation is that Ubuntu Lucid has almost twice the frame rate than
7374 RHEL6 with glxgears. No idea why.
</p
>
7379 <title>Some thoughts on BitCoins
</title>
7380 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7381 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7382 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7383 <description><p
>As I continue to explore
7384 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7385 what properties the system have, and how it will be affected by laws
7386 and regulations here in Norway. Here are some random notes.
</p
>
7388 <p
>One interesting thing to note is that since the transactions are
7389 verified using a peer to peer network, all details about a transaction
7390 is known to everyone. This means that if a BitCoin address has been
7391 published like I did with mine in my initial post about BitCoin, it is
7392 possible for everyone to see how many BitCoins have been transfered to
7393 that address. There is even a web service to look at the details for
7394 all transactions. There I can see that my address
7395 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7396 have received
16.06 Bitcoin, the
7397 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7398 address of Simon Phipps have received
181.97 BitCoin and the address
7399 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7400 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7401 every one of you that donated bitcoins to support my activity. The
7402 fact that anyone can see how much money was transfered to a given
7403 address make it more obvious why the BitCoin community recommend to
7404 generate and hand out a new address for each transaction. I
'm told
7405 there is no way to track which addresses belong to a given person or
7406 organisation without the person or organisation revealing it
7407 themselves, as Simon, EFF and I have done.
</p
>
7409 <p
>In Norway, and in most other countries, there are laws and
7410 regulations limiting how much money one can transfer across the border
7411 without declaring it. There are money laundering, tax and accounting
7412 laws and regulations I would expect to apply to the use of BitCoin.
7413 If the Skolelinux foundation
7414 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7415 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7416 normal bank transfers like EFF is doing, how should this be accounted?
7417 Given that it is impossible to know if money can cross the border or
7418 not, should everything or nothing be declared? What exchange rate
7419 should be used when calculating taxes? Would receivers have to pay
7420 income tax if the foundation were to pay Skolelinux contributors in
7421 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7423 <p
>For a currency to be useful and successful, it must be trusted and
7424 accepted by a lot of users. It must be possible to get easy access to
7425 the currency (as a wage or using currency exchanges), and it must be
7426 easy to spend it. At the moment BitCoin seem fairly easy to get
7427 access to, but there are very few places to spend it. I am not really
7428 a regular user of any of the vendor types currently accepting BitCoin,
7429 so I wonder when my kind of shop would start accepting BitCoins. I
7430 would like to buy electronics, travels and subway tickets, not herbs
7431 and books. :) The currency is young, and this will improve over time
7432 if it become popular, but I suspect regular banks will start to lobby
7433 to get BitCoin declared illegal if it become popular. I
'm sure they
7434 will claim it is helping fund terrorism and money laundering (which
7435 probably would be true, as is any currency in existence), but I
7436 believe the problems should be solved elsewhere and not by blaming
7437 currencies.
</p
>
7439 <p
>The process of creating new BitCoins is called mining, and it is
7440 CPU intensive process that depend on a bit of luck as well (as one is
7441 competing against all the other miners currently spending CPU cycles
7442 to see which one get the next lump of cash). The
"winner
" get
50
7443 BitCoin when this happen. Yesterday I came across the obvious way to
7444 join forces to increase ones changes of getting at least some coins,
7445 by coordinating the work on mining BitCoins across several machines
7446 and people, and sharing the result if one is lucky and get the
50
7448 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7449 if this sounds interesting. I have not had time to try to set up a
7450 machine to participate there yet, but have seen that running on ones
7451 own for a few days have not yield any BitCoins througth mining
7454 <p
>Update
2010-
12-
15: Found an
<a
7455 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7456 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7457 it was interesting to read. The arguments presented seem to be
7458 equally valid for gold, which was used as a currency for many years.
</p
>
7463 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7464 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7465 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7466 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7467 <description><p
>With this weeks lawless
7468 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7469 attacks
</a
> on Wikileak and
7470 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7471 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7472 not be trusted to handle money transactions.
7474 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7475 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7476 mine mentioned earlier. I decided to follow Simon
's example, and get
7477 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7478 some help from my friend to get it all running, and he even handed me
7479 some bitcoins to get started. I even donated a few bitcoins to Simon
7480 for helping me remember BitCoin.
</p
>
7482 <p
>So, what is bitcoins, you probably wonder? It is a digital
7483 crypto-currency, decentralised and handled using peer-to-peer
7484 networks. It allows anonymous transactions and prohibits central
7485 control over the transactions, making it impossible for governments
7486 and companies alike to block donations and other transactions. The
7487 source is free software, and while the key dependency wxWidgets
2.9
7488 for the graphical user interface is missing in Debian, the command
7489 line client builds just fine. Hopefully Jonas
7490 <a href=
"http://bugs.debian.org/
578157">will get the package into
7491 Debian
</a
> soon.
</p
>
7493 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7494 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7495 bitcoins
</a
> when selling services and goods, and there are even
7496 currency
"stock
" markets where the exchange rate is decided. There
7497 are not many users so far, but the concept seems promising. If you
7498 want to get started and lack a friend with any bitcoins to spare,
7500 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7501 bitcoin at the time of writing). Use
7502 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7503 on the current exchange rates.
</p
>
7505 <p
>As an experiment, I have decided to set up bitcoind on one of my
7506 machines. If you want to support my activity, please send Bitcoin
7507 donations to the address
7508 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7513 <title>Why isn
't Debian Edu using VLC?
</title>
7514 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7515 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7516 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7517 <description><p
>In the latest issue of Linux Journal, the readers choices were
7518 presented, and the winner among the multimedia player were VLC.
7519 Personally, I like VLC, and it is my player of choice when I first try
7520 to play a video file or stream. Only if VLC fail will I drag out
7521 gmplayer to see if it can do better. The reason is mostly the failure
7522 model and trust. When VLC fail, it normally pop up a error message
7523 reporting the problem. When mplayer fail, it normally segfault or
7524 just hangs. The latter failure mode drain my trust in the program.
<p
>
7526 <p
>But even if VLC is my player of choice, we have choosen to use
7527 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7528 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7529 plugin to play web videos seamlessly, and the VLC browser plugin is
7530 not very good. For example, it lack in-line control buttons, so there
7531 is no way for the user to pause the video. Also, when I
7532 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7533 tested the browser plugins
</a
> available in Debian, the VLC plugin
7534 failed on several video pages where mplayer based plugins worked. If
7535 the browser plugin for VLC was as good as the gecko-mediaplayer
7536 package (which uses mplayer), we would switch.
</P
>
7538 <p
>While VLC is a good player, its user interface is slightly
7539 annoying. The most annoying feature is its inconsistent use of
7540 keyboard shortcuts. When the player is in full screen mode, its
7541 shortcuts are different from when it is playing the video in a window.
7542 For example, space only work as pause when in full screen mode. I
7543 wish it had consisten shortcuts and that space also would work when in
7544 window mode. Another nice shortcut in gmplayer is [enter] to restart
7545 the current video. It is very nice when playing short videos from the
7546 web and want to restart it when new people arrive to have a look at
7547 what is going on.
</p
>
7552 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7553 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7554 <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>
7555 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7556 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7557 upgrade testing of the
7558 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7559 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7560 This seem like a very good idea, so I adjusted by test scripts and
7561 can now present the updated result from today:
</p
>
7563 <p
>This is for Gnome:
</p
>
7565 <p
>Installed using apt-get, missing with aptitude
</p
>
7567 <blockquote
><p
>
7572 browser-plugin-gnash
7579 freedesktop-sound-theme
7581 gconf-defaults-service
7596 gnome-desktop-environment
7600 gnome-session-canberra
7605 gstreamer0.10-fluendo-mp3
7611 libapache2-mod-dnssd
7614 libaprutil1-dbd-sqlite3
7617 libboost-date-time1.42
.0
7618 libboost-python1.42
.0
7619 libboost-thread1.42
.0
7621 libchamplain-gtk-
0.4-
0
7623 libclutter-gtk-
0.10-
0
7630 libfreerdp-plugins-standard
7645 libgnomepanel2.24-cil
7650 libgtksourceview2.0-common
7651 libmono-addins-gui0.2-cil
7652 libmono-addins0.2-cil
7653 libmono-cairo2.0-cil
7654 libmono-corlib2.0-cil
7655 libmono-i18n-west2.0-cil
7656 libmono-posix2.0-cil
7657 libmono-security2.0-cil
7658 libmono-sharpzip2.84-cil
7659 libmono-system2.0-cil
7662 libndesk-dbus-glib1.0-cil
7663 libndesk-dbus1.0-cil
7673 libtelepathy-farsight0
7682 nautilus-sendto-empathy
7686 python-aptdaemon-gtk
7688 python-beautifulsoup
7703 python-gtksourceview2
7714 python-pkg-resources
7721 python-twisted-conch
7727 python-zope.interface
7732 rhythmbox-plugin-cdrecorder
7739 system-config-printer-udev
7741 telepathy-mission-control-
5
7752 </p
></blockquote
>
7754 <p
>Installed using apt-get, removed with aptitude
</p
>
7756 <blockquote
><p
>
7762 fast-user-switch-applet
7781 libgtksourceview2.0-
0
7783 libsdl1.2debian-alsa
7789 system-config-printer
7794 </p
></blockquote
>
7796 <p
>Installed using aptitude, missing with apt-get
</p
>
7798 <blockquote
><p
>
7799 gstreamer0.10-gnomevfs
7800 </p
></blockquote
>
7802 <p
>Installed using aptitude, removed with apt-get
</p
>
7804 <blockquote
><p
>
7806 </p
></blockquote
>
7808 <p
>This is for KDE:
</p
>
7810 <p
>Installed using apt-get, missing with aptitude
</p
>
7812 <blockquote
><p
>
7814 </p
></blockquote
>
7816 <p
>Installed using apt-get, removed with aptitude
</p
>
7818 <blockquote
><p
>
7821 </p
></blockquote
>
7823 <p
>Installed using aptitude, missing with apt-get
</p
>
7825 <blockquote
><p
>
7839 kdeartwork-emoticons
7841 kdeartwork-theme-icon
7845 kdebase-workspace-bin
7846 kdebase-workspace-data
7860 kscreensaver-xsavers
7875 plasma-dataengines-workspace
7877 plasma-desktopthemes-artwork
7878 plasma-runners-addons
7879 plasma-scriptengine-googlegadgets
7880 plasma-scriptengine-python
7881 plasma-scriptengine-qedje
7882 plasma-scriptengine-ruby
7883 plasma-scriptengine-webkit
7884 plasma-scriptengines
7885 plasma-wallpapers-addons
7886 plasma-widget-folderview
7887 plasma-widget-networkmanagement
7891 xscreensaver-data-extra
7893 xscreensaver-gl-extra
7894 xscreensaver-screensaver-bsod
7895 </p
></blockquote
>
7897 <p
>Installed using aptitude, removed with apt-get
</p
>
7899 <blockquote
><p
>
7901 google-gadgets-common
7919 libggadget-qt-
1.0-
0b
7924 libkonqsidebarplugin4a
7933 libplasma-geolocation-interface4
7935 libplasmagenericshell4
7949 libsmokeknewstuff2-
3
7950 libsmokeknewstuff3-
3
7952 libsmokektexteditor3
7960 libsmokeqtnetwork4-
3
7966 libsmokeqtuitools4-
3
7978 plasma-dataengines-addons
7979 plasma-scriptengine-superkaramba
7980 plasma-widget-lancelot
7981 plasma-widgets-addons
7982 plasma-widgets-workspace
7986 update-notifier-common
7987 </p
></blockquote
>
7989 <p
>Running apt-get autoremove made the results using apt-get and
7990 aptitude a bit more similar, but there are still quite a lott of
7991 differences. I have no idea what packages should be installed after
7992 the upgrade, but hope those that do can have a look.
</p
>
7997 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
7998 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
7999 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8000 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8001 <description><p
>Most of the computers in use by the
8002 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8003 are virtual machines. And they have been Xen machines running on a
8004 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8005 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8006 bit harder that it could have been, because we set up the Xen virtual
8007 machines to get the virtual partitions from LVM, which as far as I
8008 know is not supported by KVM. So to migrate, we had to convert
8009 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8012 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8013 nice recipe
</a
> to do this, and wrote the following script to do the
8014 migration. It uses qemu-img from the qemu package to make the disk
8015 image, parted to partition it, losetup and kpartx to present the disk
8016 image partions as devices, and dd to copy the data. I NFS mounted the
8017 new servers storage area on the old server to do the migration.
</p
>
8023 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8028 if [ -z
"$
1" ] ; then
8029 echo
"Usage: $
0 &lt;hostname
&gt;
"
8035 if [ ! -e /dev/vg_data/$host-disk ] ; then
8036 echo
"error: unable to find LVM volume for $host
"
8040 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8041 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8042 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8043 totalsize=$(( ( $disksize + $swapsize ) ))
8046 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8047 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8049 parted $img mklabel msdos
8050 parted $img mkpart primary linux-swap
0 $disksize
8051 parted $img mkpart primary ext2 $disksize $totalsize
8052 parted $img set
1 boot on
8055 losetup /dev/loop0 $img
8056 kpartx -a /dev/loop0
8058 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8059 fsck.ext3 -f /dev/mapper/loop0p1 || true
8060 mkswap /dev/mapper/loop0p2
8062 kpartx -d /dev/loop0
8063 losetup -d /dev/loop0
8066 <p
>The script is perhaps so simple that it is not copyrightable, but
8067 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8069 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8070 the new disk image attached, installed grub-pc and linux-image-
686 and
8071 set up grub to boot from the disk image. After this, the KVM machines
8072 seem to work just fine.
</p
>
8077 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8078 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8079 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8080 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8081 <description><p
>I
'm still running upgrade testing of the
8082 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8083 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8084 status. Here is a short update based on a test I ran
20101118.
</p
>
8086 <p
>I still do not know what a correct migration should look like, so I
8087 report any differences between apt and aptitude and hope someone else
8088 can see if anything should be changed.
</p
>
8090 <p
>This is for Gnome:
</p
>
8092 <p
>Installed using apt-get, missing with aptitude
</p
>
8094 <blockquote
><p
>
8095 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8096 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8097 dmz-cursor-theme empathy empathy-common finger
8098 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8099 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8100 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8101 gnome-cards-data gnome-codec-install gnome-core
8102 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8103 gnome-search-tool gnome-session-canberra gnome-spell
8104 gnome-system-log gnome-themes-extras gnome-themes-more
8105 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8106 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8107 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8108 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8109 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8110 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8111 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8112 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8113 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8114 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8115 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8116 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8117 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8118 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8119 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8120 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8121 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8122 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8123 libmono-security2.0-cil libmono-sharpzip2.84-cil
8124 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8125 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8126 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8127 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8128 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8129 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8130 libxalan2-java libxerces2-java media-player-info mesa-utils
8131 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8132 nautilus-sendto-empathy openoffice.org-writer2latex
8133 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8134 python-aptdaemon python-aptdaemon-gtk python-axiom
8135 python-beautifulsoup python-bugbuddy python-clientform
8136 python-coherence python-configobj python-crypto python-cupshelpers
8137 python-cupsutils python-eggtrayicon python-elementtree
8138 python-epsilon python-evolution python-feedparser python-gdata
8139 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8140 python-gtksourceview2 python-httplib2 python-louie python-mako
8141 python-markupsafe python-mechanize python-nevow python-notify
8142 python-opengl python-openssl python-pam python-pkg-resources
8143 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8144 python-tagpy python-twisted-bin python-twisted-conch
8145 python-twisted-core python-twisted-web python-utidylib python-webkit
8146 python-xdg python-zope.interface remmina remmina-plugin-data
8147 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8148 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8149 software-center svgalibg1 system-config-printer-udev
8150 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8151 totem totem-coherence totem-mozilla totem-plugins
8152 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8154 </p
></blockquote
>
8156 Installed using apt-get, removed with aptitude
8158 <blockquote
><p
>
8159 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8160 epiphany-extensions epiphany-gecko evolution-exchange
8161 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8162 gedit-common gnome-app-install gnome-games gnome-games-data
8163 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8164 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8165 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8166 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8167 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8168 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8169 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8170 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8171 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8172 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8173 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8174 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8175 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8176 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8177 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8178 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8179 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8180 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8181 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8182 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8183 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8184 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8185 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8186 sound-juicer swfdec-gnome system-config-printer totem-common
8187 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8188 </p
></blockquote
>
8190 <p
>Installed using aptitude, missing with apt-get
</p
>
8192 <blockquote
><p
>
8193 gstreamer0.10-gnomevfs
8194 </p
></blockquote
>
8196 <p
>Installed using aptitude, removed with apt-get
</p
>
8198 <blockquote
><p
>
8200 </p
></blockquote
>
8202 <p
>This is for KDE:
</p
>
8204 <p
>Installed using apt-get, missing with aptitude
</p
>
8206 <blockquote
><p
>
8207 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8208 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8209 ghostscript-x git gnome-audio gnugo granatier gs-common
8210 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8211 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8212 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8213 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8214 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8215 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8216 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8217 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8218 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8219 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8220 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8221 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8222 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8223 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8224 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8225 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8226 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8227 libkrossui4 libmailtools-perl libmime-tools-perl
8228 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8229 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8230 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8231 lirc luatex marble networkstatus noatun-plugins
8232 openoffice.org-writer2latex palapeli palapeli-data parley
8233 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8234 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8235 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8237 </p
></blockquote
>
8239 <p
>Installed using apt-get, removed with aptitude
</p
>
8241 <blockquote
><p
>
8242 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8243 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8244 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8245 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8246 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8247 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8248 kitchensync kiten kjumpingcube klatin klettres klickety klines
8249 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8250 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8251 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8252 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8253 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8254 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8255 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8256 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8257 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8258 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8259 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8260 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8261 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8262 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8263 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8264 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8265 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8266 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8267 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8268 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8269 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8270 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8271 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8272 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8273 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8274 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8275 </p
></blockquote
>
8277 <p
>Installed using aptitude, missing with apt-get
</p
>
8279 <blockquote
><p
>
8280 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8281 kdeartwork kdebase kdebase-apps kdebase-workspace
8282 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8283 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8284 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8285 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8286 xscreensaver-screensaver-bsod
8287 </p
></blockquote
>
8289 <p
>Installed using aptitude, removed with apt-get
</p
>
8291 <blockquote
><p
>
8292 kdebase-bin konq-plugins konqueror
8293 </p
></blockquote
>
8298 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8299 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8300 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8301 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8302 <description><p
>Answering
8303 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8304 call from the Gnash project
</a
> for
8305 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8306 current source, I have set up a virtual KVM machine on the Debian
8307 Edu/Skolelinux virtualization host to test the git source on
8308 Debian/Squeeze. I hope this can help the developers in getting new
8309 releases out more often.
</p
>
8311 <p
>As the developers want less main-stream build platforms tested to,
8312 I have considered setting up a
<a
8313 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8314 machine as well. I have also considered using the kfreebsd
8315 architecture in Debian as a file server in NUUG to get access to the
5
8316 TB zfs volume we currently use to store DV video. Because of this, I
8317 finally got around to do a test installation of Debian/Squeeze with
8318 kfreebsd. Installation went fairly smooth, thought I noticed some
8319 visual glitches in the cdebconf dialogs (black cursor left on the
8320 screen at random locations). Have not gotten very far with the
8321 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8322 fatal problem. Have to spend some more time on it to see if it is
8323 useful as a file server for NUUG. Will try to find time to set up a
8324 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8329 <title>Debian in
3D
</title>
8330 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8331 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8332 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8333 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8335 <p
>3D printing is just great. I just came across this Debian logo in
8337 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8338 thingiverse blog
</a
>.
</p
>
8343 <title>Software updates
2010-
10-
24</title>
8344 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8345 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8346 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8347 <description><p
>Some updates.
</p
>
8349 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8350 raise money for the project is going well. The lower limit of
10
8351 signers was reached in
24 hours, and so far
13 people have signed it.
8352 More signers and more funding is most welcome, and I am really curious
8353 how far we can get before the time limit of December
24 is reached.
8356 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8357 about what appear to be a great code coverage tool capable of
8358 generating code coverage stats without any changes to the source code.
8360 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8361 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8362 It is missing in Debian, but the git source built just fine in Squeeze
8363 after I installed libelf-dev, libdwarf-dev, pkg-config and
8364 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8365 solvable. I hope kcov make it into Debian soon.
</p
>
8367 <p
>Finally found time to wrap up the release notes for
<a
8368 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8369 new alpha release of Debian Edu
</a
>, and just published the second
8370 alpha test release of the Squeeze based Debian Edu /
8371 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8372 release. Give it a try if you need a complete linux solution for your
8373 school, including central infrastructure server, workstations, thin
8374 client servers and diskless workstations. A nice touch added
8375 yesterday is RDP support on the thin client servers, for windows
8376 clients to get a Linux desktop on request.
</p
>
8381 <title>Some notes on Flash in Debian and Debian Edu
</title>
8382 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8383 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8384 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8385 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8386 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8387 second most popular used package that is missing in Debian. The sixth
8388 most popular is flashplayer-mozilla. This is a clear indication that
8389 working flash is important for Debian users. Around
10 percent of the
8390 users submitting data to popcon.debian.org have this package
8391 installed.
</p
>
8393 <p
>In the report written by Lars Risan in August
2008
8394 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8395 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8396 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8397 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8398 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8399 web sites require Flash to work, and lacking working Flash support in
8400 the web browser and the problems with installing it was perceived as a
8401 good reason to stay with Windows.
</p
>
8403 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8404 said to be the retarded cousin that did not really understand
8405 everything you told him but could work fairly well. This was a
8406 comment regarding the problems Linux have with proprietary formats and
8407 non-standard web pages, and is sad because it exposes a fairly common
8408 understanding of whose fault it is if web pages that only work in for
8409 example Internet Explorer
6 fail to work on Firefox, and funny because
8410 it explain very well how annoying it is for users when Linux
8411 distributions do not work with the documents they receive or the web
8412 pages they want to visit.
</p
>
8414 <p
>This is part of the reason why I believe it is important for Debian
8415 and Debian Edu to have a well working Flash implementation in the
8416 distribution, to get at least popular sites as Youtube and Google
8417 Video to working out of the box. For Squeeze, Debian have the chance
8418 to include the latest version of Gnash that will make this happen, as
8419 the new release
0.8.8 was published a few weeks ago and is resting in
8420 unstable. The new version work with more sites that version
0.8.7.
8421 The Gnash maintainers have asked for a freeze exception, but the
8422 release team have not had time to reply to it yet. I hope they agree
8423 with me that Flash is important for the Debian desktop users, and thus
8424 accept the new package into Squeeze.
</p
>
8429 <title>Circular package dependencies harms apt recovery
</title>
8430 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8431 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8432 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8433 <description><p
>I discovered this while doing
8434 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8435 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8436 in Debian still got circular dependencies, and it is often claimed
8437 that apt and aptitude should be able to handle this just fine, but
8438 some times these dependency loops causes apt to fail.
</p
>
8440 <p
>An example is from todays
8441 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8442 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8443 causes perl-modules to fail to upgrade. The cause is simple. If a
8444 package fail to unpack, then only part of packages with the circular
8445 dependency might end up being unpacked when unpacking aborts, and the
8446 ones already unpacked will fail to configure in the recovery phase
8447 because its dependencies are unavailable.
</p
>
8449 <p
>In this log, the problem manifest itself with this error:
</p
>
8451 <blockquote
><pre
>
8452 dpkg: dependency problems prevent configuration of perl-modules:
8453 perl-modules depends on perl (
>=
5.10.1-
1); however:
8454 Version of perl on system is
5.10.0-
19lenny
2.
8455 dpkg: error processing perl-modules (--configure):
8456 dependency problems - leaving unconfigured
8457 </pre
></blockquote
>
8459 <p
>The perl/perl-modules circular dependency is already
8460 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8461 hopefully be solved as soon as possible, but it is not the only one,
8462 and each one of these loops in the dependency tree can cause similar
8463 failures. Of course, they only occur when there are bugs in other
8464 packages causing the unpacking to fail, but it is rather nasty when
8465 the failure of one package causes the problem to become worse because
8466 of dependency loops.
</p
>
8469 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8470 tireless effort by Bill Allombert
</a
>, the number of circular
8472 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8473 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8475 <p
>Todays testing also exposed a bug in
8476 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8477 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8478 apt-get and aptitude, the latter possibly caused by some circular
8479 dependency. Reported both to BTS to try to get someone to look at
8485 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8486 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8487 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8488 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8489 <description><p
>This is a
8490 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8492 <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
8494 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8495 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8497 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8498 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8499 and dhcp3-server-ldap in Debian use the LDAP server. The two
8500 implementations are quite different in how they use LDAP.
</p
>
8502 To get this information, I started slapd with debugging enabled and
8503 dumped the debug output to a file to get the LDAP searches performed
8504 on a Debian Edu main-server. Here is a summary.
8506 <p
><strong
>powerdns
</strong
></p
>
8508 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8509 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8512 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8513 One
"strict
" mode where the forward and reverse DNS lookups are done
8514 using the same LDAP objects, and a
"tree
" mode where the forward and
8515 reverse entries are in two different subtrees in LDAP with a structure
8516 based on the DNS names, as in tjener.intern and
8517 2.2.0.10.in-addr.arpa.
</p
>
8519 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8520 base, and uses a
"base
" scoped search for the DNS name by adding
8521 "dc=tjener,dc=intern,
" to the base with a filter for
8522 "(associateddomain=tjener.intern)
" for the forward entry and
8523 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8524 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8525 forward entries, it is looking for attributes named dnsttl, arecord,
8526 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8527 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8528 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8529 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8530 spfrecord and modifytimestamp. For reverse entries it is looking for
8531 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8532 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8533 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8534 ldapsearch commands could look like this:
</p
>
8536 <blockquote
><pre
>
8537 ldapsearch -h ldap \
8538 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8539 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8540 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8541 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8542 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8543 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8545 ldapsearch -h ldap \
8546 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8547 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8548 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8549 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8550 srvrecord naptrrecord modifytimestamp
8551 </pre
></blockquote
>
8553 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8554 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8555 example LDAP objects used there. In addition to these objects, the
8556 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8557 also exist.
</p
>
8559 <blockquote
><pre
>
8560 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8562 objectclass: dnsdomain
8563 objectclass: domainrelatedobject
8566 associateddomain: tjener.intern
8568 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8570 objectclass: dnsdomain2
8571 objectclass: domainrelatedobject
8573 ptrrecord: tjener.intern
8574 associateddomain:
2.2.0.10.in-addr.arpa
8575 </pre
></blockquote
>
8577 <p
>In strict mode, the server behaves differently. When looking for
8578 forward DNS entries, it is doing a
"subtree
" scoped search with the
8579 same base as in the tree mode for a object with filter
8580 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8581 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8582 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8583 naptrrecord and modifytimestamp. For reverse entires it also do a
8584 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8585 and the requested attributes are associateddomain, dnsttl and
8586 modifytimestamp. In short, in strict mode the objects with ptrrecord
8587 go away, and the arecord attribute in the forward object is used
8590 <p
>The forward and reverse searches can be simulated using ldapsearch
8591 like this:
</p
>
8593 <blockquote
><pre
>
8594 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8595 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8596 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8597 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8598 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8599 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8601 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8602 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8603 </pre
></blockquote
>
8605 <p
>In addition to the forward and reverse searches , there is also a
8606 search for SOA records, which behave similar to the forward and
8607 reverse lookups.
</p
>
8609 <p
>A thing to note with the PowerDNS behaviour is that it do not
8610 specify any objectclass names, and instead look for the attributes it
8611 need to generate a DNS reply. This make it able to work with any
8612 objectclass that provide the needed attributes.
</p
>
8614 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8615 dnsdomain2 schemas. The latter is used for reverse entries like
8616 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8618 <p
>In Debian Edu, we have created DNS objects using the object classes
8619 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8620 attributes) and domainrelatedobject (for associatedDomain). The use
8621 of structural object classes make it impossible to combine these
8622 classes with the object classes used by DHCP.
</p
>
8624 <p
>There are other schemas that could be used too, for example the
8625 dnszone structural object class used by Gosa and bind-sdb for the DNS
8626 attributes combined with the domainrelatedobject object class, but in
8627 this case some unused attributes would have to be included as well
8628 (zonename and relativedomainname).
</p
>
8630 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8631 mode and not use any of the existing objectclasses (dnsdomain,
8632 dnsdomain2 and dnszone) when one want to combine the DNS information
8633 with DHCP information, and instead create a auxiliary object class
8634 defined something like this (using the attributes defined for
8635 dnsdomain and dnsdomain2 or dnszone):
</p
>
8637 <blockquote
><pre
>
8638 objectclass ( some-oid NAME
'dnsDomainAux
'
8641 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8642 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8643 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8644 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8645 A6Record $ DNAMERecord
8647 </pre
></blockquote
>
8649 <p
>This will allow any object to become a DNS entry when combined with
8650 the domainrelatedobject object class, and allow any entity to include
8651 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8652 developers asking for their view on this schema and if they are
8653 interested in providing such schema with PowerDNS, and I hope my
8654 message will be accepted into their mailing list soon.
</p
>
8656 <p
><strong
>ISC dhcp
</strong
></p
>
8658 <p
>The DHCP server searches for specific objectclass and requests all
8659 the object attributes, and then uses the attributes it want. This
8660 make it harder to figure out exactly what attributes are used, but
8661 thanks to the working example in Debian Edu I can at least get an idea
8662 what is needed without having to read the source code.
</p
>
8664 <p
>In the DHCP server configuration, the LDAP base to use and the
8665 search filter to use to locate the correct dhcpServer entity is
8666 stored. These are the relevant entries from
8667 /etc/dhcp3/dhcpd.conf:
</p
>
8669 <blockquote
><pre
>
8670 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8671 ldap-dhcp-server-cn
"dhcp
";
8672 </pre
></blockquote
>
8674 <p
>The DHCP server uses this information to nest all the DHCP
8675 configuration it need. The cn
"dhcp
" is located using the given LDAP
8676 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8677 search result is this entry:
</p
>
8679 <blockquote
><pre
>
8680 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8683 objectClass: dhcpServer
8684 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8685 </pre
></blockquote
>
8687 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8688 subtree with DHCP configuration. The DHCP configuration subtree base
8689 is located using a base scope search with base
"cn=DHCP
8690 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8691 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8692 The search result is this entry:
</p
>
8694 <blockquote
><pre
>
8695 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8698 objectClass: dhcpService
8699 objectClass: dhcpOptions
8700 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8701 dhcpStatements: ddns-update-style none
8702 dhcpStatements: authoritative
8703 dhcpOption: smtp-server code
69 = array of ip-address
8704 dhcpOption: www-server code
72 = array of ip-address
8705 dhcpOption: wpad-url code
252 = text
8706 </pre
></blockquote
>
8708 <p
>Next, the entire subtree is processed, one level at the time. When
8709 all the DHCP configuration is loaded, it is ready to receive requests.
8710 The subtree in Debian Edu contain objects with object classes
8711 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8712 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8713 and information about netmasks, dynamic range etc. Leaving out the
8714 details here because it is not relevant for the focus of my
8715 investigation, which is to see if it is possible to merge dns and dhcp
8716 related computer objects.
</p
>
8718 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8719 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8720 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8721 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8722 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8725 <blockquote
><pre
>
8726 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8729 objectClass: dhcpHost
8730 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8731 dhcpStatements: fixed-address hostname
8732 </pre
></blockquote
>
8734 <p
>There is less flexiblity in the way LDAP searches are done here.
8735 The object classes need to have fixed names, and the configuration
8736 need to be stored in a fairly specific LDAP structure. On the
8737 positive side, the invidiual dhcpHost entires can be anywhere without
8738 the DN pointed to by the dhcpServer entries. The latter should make
8739 it possible to group all host entries in a subtree next to the
8740 configuration entries, and this subtree can also be shared with the
8741 DNS server if the schema proposed above is combined with the dhcpHost
8742 structural object class.
8744 <p
><strong
>Conclusion
</strong
></p
>
8746 <p
>The PowerDNS implementation seem to be very flexible when it come
8747 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8748 come to the the LDAP structure, the
"strict
" mode is very flexible,
8749 allowing DNS objects to be stored anywhere under the base cn specified
8750 in the configuration.
</p
>
8752 <p
>The DHCP implementation on the other hand is very inflexible, both
8753 regarding which LDAP schemas to use and which LDAP structure to use.
8754 I guess one could implement ones own schema, as long as the
8755 objectclasses and attributes have the names used, but this do not
8756 really help when the DHCP subtree need to have a fairly fixed
8757 structure.
</p
>
8759 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8760 this might work for Debian Edu:
</p
>
8762 <blockquote
><pre
>
8764 cn=machine-info (dhcpService) - dhcpServiceDN points here
8765 cn=dhcp (dhcpServer)
8766 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8767 cn=
10.0.2.0 (dhcpSubnet)
8768 cn=group1 (dhcpGroup/dhcpOptions)
8769 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8770 cn=
192.168.0.0 (dhcpSubnet)
8771 cn=group1 (dhcpGroup/dhcpOptions)
8772 ou=machines - PowerDNS base points here
8773 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8774 </pre
></blockquote
>
8776 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8777 entries to be in the dhcpGroup subtrees, the entries can be stored
8778 there instead of a common machines subtree, and the PowerDNS base
8779 would have to be moved one level up to the machine-info subtree.
</p
>
8781 <p
>The combined object under the machines subtree would look something
8782 like this:
</p
>
8784 <blockquote
><pre
>
8785 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8788 objectClass: dhcpHost
8789 objectclass: domainrelatedobject
8790 objectclass: dnsDomainAux
8791 associateddomain: hostname.intern
8792 arecord:
10.11.12.13
8793 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8794 dhcpStatements: fixed-address hostname.intern
8795 </pre
></blockquote
>
8797 </p
>One could even add the LTSP configuration associated with a given
8798 machine, as long as the required attributes are available in a
8799 auxiliary object class.
</p
>
8804 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8805 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8806 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8807 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8808 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8809 DHCP services in Debian Edu to use the same LDAP objects for a given
8810 computer, to avoid the possibility of having a inconsistent state for
8811 a computer in LDAP (as in DHCP but no DNS entry or the other way
8812 around) and make it easier to add computers to LDAP.
</p
>
8814 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8815 information finally found a solution that seem to work.
</p
>
8817 <p
>The old setup required three LDAP objects for a given computer.
8818 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8819 we switch powerdns to use its strict LDAP method (ldap-method=strict
8820 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8821 merged into one while making it impossible to transfer the reverse map
8822 to a slave DNS server.
</p
>
8824 <p
>If we also replace the object class used to get the DNS related
8825 attributes to one allowing these attributes to be combined with the
8826 dhcphost object class, we can merge the DNS and DHCP entries into one.
8827 I
've written such object class in the dnsdomainaux.schema file (need
8828 proper OIDs, but that is a minor issue), and tested the setup. It
8829 seem to work.
</p
>
8831 <p
>With this test setup in place, we can get away with one LDAP object
8832 for both DNS and DHCP, and even the LTSP configuration I suggested in
8833 an earlier email. The combined LDAP object will look something like
8836 <blockquote
><pre
>
8837 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8839 objectClass: dhcphost
8840 objectclass: domainrelatedobject
8841 objectclass: dnsdomainaux
8842 associateddomain: hostname.intern
8843 arecord:
10.11.12.13
8844 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8845 dhcpstatements: fixed-address hostname
8847 </pre
></blockquote
>
8849 <p
>The DNS server uses the associateddomain and arecord entries, while
8850 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8851 before asking DNS to resolve the fixed-adddress. LTSP will use
8852 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8854 <p
>I am not yet sure if I can get the DHCP server to look for its
8855 dhcphost in a different location, to allow us to put the objects
8856 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8857 that. If I can
't figure out a way to do that, we can still get rid of
8858 the hosts subtree and move all its content into the DHCP Config tree
8859 (which probably should be renamed to be more related to the new
8860 content. I suspect cn=dnsdhcp,ou=services or something like that
8861 might be a good place to put it.
</p
>
8863 <p
>If you want to help out with implementing this for Debian Edu,
8864 please contact us on debian-edu@lists.debian.org.
</p
>
8869 <title>Idea for storing LTSP configuration in LDAP
</title>
8870 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8871 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8872 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8873 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8874 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8875 clients, and that this can be used to fetch configuration from LDAP if
8876 Debian Edu choose to store configuration there.
</p
>
8878 <p
>Armed with this information, I got inspired and wrote a test module
8879 to get configuration from LDAP. The idea is to look up the MAC
8880 address of the client in LDAP, and look for attributes on the form
8881 ltspconfigsetting=value, and use this to export SETTING=value to the
8882 LTSP clients.
</p
>
8884 <p
>The goal is to be able to store the LTSP configuration attributes
8885 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8886 allowing us to store all information about a computer in one place.
</p
>
8888 <p
>This is a untested draft implementation, and I welcome feedback on
8889 this approach. A real LDAP schema for the ltspClientAux objectclass
8890 need to be written. Comments, suggestions, etc?
</p
>
8892 <blockquote
><pre
>
8893 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8895 # Fetch LTSP client settings from LDAP based on MAC address
8897 # Uses ethernet address as stored in the dhcpHost objectclass using
8898 # the dhcpHWAddress attribute or ethernet address stored in the
8899 # ieee802Device objectclass with the macAddress attribute.
8901 # This module is written to be schema agnostic, and only depend on the
8902 # existence of attribute names.
8904 # The LTSP configuration variables are saved directly using a
8905 # ltspConfig prefix and uppercasing the rest of the attribute name.
8906 # To set the SERVER variable, set the ltspConfigServer attribute.
8908 # Some LDAP schema should be created with all the relevant
8909 # configuration settings. Something like this should work:
8911 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8914 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8916 LDAPSERVER=$(debian-edu-ldapserver)
8917 if [
"$LDAPSERVER
" ] ; then
8918 LDAPBASE=$(debian-edu-ldapserver -b)
8919 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8920 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8921 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8922 grep
'^ltspConfig
' | while read attr value ; do
8923 # Remove prefix and convert to upper case
8924 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8925 # bass value on to clients
8926 eval
"$attr=$value; export $attr
"
8930 </pre
></blockquote
>
8932 <p
>I
'm not sure this shell construction will work, because I suspect
8933 the while block might end up in a subshell causing the variables set
8934 there to not show up in ltsp-config, but if that is the case I am sure
8935 the code can be restructured to make sure the variables are passed on.
8936 I expect that can be solved with some testing. :)
</p
>
8938 <p
>If you want to help out with implementing this for Debian Edu,
8939 please contact us on debian-edu@lists.debian.org.
</p
>
8941 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8942 configuration in LDAP that was created around year
2000 by
8943 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8944 Xperience, Inc.,
2000</a
>. I found its
8945 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8946 personal home page over at redhat.com.
</p
>
8951 <title>jXplorer, a very nice LDAP GUI
</title>
8952 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8953 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8954 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8955 <description><p
>Since
8956 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8957 last post
</a
> about available LDAP tools in Debian, I was told about a
8958 LDAP GUI that is even better than luma. The java application
8959 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8960 moving LDAP objects and subtrees using drag-and-drop, and can
8961 authenticate using Kerberos. I have only tested the Kerberos
8962 authentication, but do not have a LDAP setup allowing me to rewrite
8963 LDAP with my test user yet. It is
8964 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8965 Debian
</a
> testing and unstable at the moment. The only problem I
8966 have with it is how it handle errors. If something go wrong, its
8967 non-intuitive behaviour require me to go through some query work list
8968 and remove the failing query. Nothing big, but very annoying.
</p
>
8973 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8974 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8975 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8976 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8977 <description><p
>Here is a short update on my
<a
8978 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8979 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8980 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8981 not reporting the status for KDE, because the upgrade crashes when
8982 aptitude try because of missing conflicts
8983 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8984 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8986 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8987 complete list of the installed packages. Based on this I see these
8988 differences when I did a test run today. As usual, I do not really
8989 know what the correct set of packages would be, but thought it best to
8990 publish the difference.
</p
>
8992 <p
>Installed using apt-get, missing with aptitude
</p
>
8994 <blockquote
><p
>
8995 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
8996 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
8997 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
8998 libgtksourceview-common libpt-
1.10.10-plugins-alsa
8999 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9000 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9001 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9002 python-gtkmozembed svgalibg1 xserver-xephyr zip
9003 </p
></blockquote
>
9005 <p
>Installed using apt-get, removed with aptitude
</p
>
9007 <blockquote
><p
>
9008 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9009 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9010 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9011 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9012 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9013 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9014 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9015 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9016 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9017 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9018 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9019 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9020 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9021 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9022 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9023 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9024 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9025 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9026 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9027 mysql-common swfdec-gnome totem-gstreamer wodim
9028 </p
></blockquote
>
9030 <p
>Installed using aptitude, missing with apt-get
</p
>
9032 <blockquote
><p
>
9033 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9034 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9035 xserver-xorg-input-all xserver-xorg-input-evdev
9036 xserver-xorg-input-kbd xserver-xorg-input-mouse
9037 xserver-xorg-input-synaptics xserver-xorg-video-all
9038 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9039 xserver-xorg-video-chips xserver-xorg-video-cirrus
9040 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9041 xserver-xorg-video-glint xserver-xorg-video-i128
9042 xserver-xorg-video-i740 xserver-xorg-video-mach64
9043 xserver-xorg-video-mga xserver-xorg-video-neomagic
9044 xserver-xorg-video-nouveau xserver-xorg-video-nv
9045 xserver-xorg-video-r128 xserver-xorg-video-radeon
9046 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9047 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9048 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9049 xserver-xorg-video-sis xserver-xorg-video-sisusb
9050 xserver-xorg-video-tdfx xserver-xorg-video-tga
9051 xserver-xorg-video-trident xserver-xorg-video-tseng
9052 xserver-xorg-video-vesa xserver-xorg-video-vmware
9053 xserver-xorg-video-voodoo
9054 </p
></blockquote
>
9056 <p
>Installed using aptitude, removed with apt-get
</p
>
9058 <blockquote
><p
>
9059 deskbar-applet xserver-xorg xserver-xorg-core
9060 xserver-xorg-input-wacom xserver-xorg-video-intel
9061 xserver-xorg-video-openchrome
9062 </p
></blockquote
>
9064 <p
>I was told on IRC that the xorg-xserver package was
9065 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9066 in git
</a
> today to try to get apt-get to not remove xorg completely.
9067 No idea when it hits Squeeze, but when it does I hope it will reduce
9068 the difference somewhat.
9073 <title>LUMA, a very nice LDAP GUI
</title>
9074 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9075 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9076 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9077 <description><p
>The last few days I have been looking into the status of the LDAP
9078 directory in Debian Edu, and in the process I started to miss a GUI
9079 tool to browse the LDAP tree. The only one I was able to find in
9080 Debian/Squeeze and Lenny is
9081 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9082 be a great tool to get a overview of the current LDAP directory
9083 populated by default in Skolelinux. Thanks to it, I have been able to
9084 find empty and obsolete subtrees, misplaced objects and duplicate
9085 objects. It will be installed by default in Debian/Squeeze. If you
9086 are working with LDAP, give it a go. :)
</p
>
9088 <p
>I did notice one problem with it I have not had time to report to
9089 the BTS yet. There is no .desktop file in the package, so the tool do
9090 not show up in the Gnome and KDE menus, but only deep down in in the
9091 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9094 <p
>I have not yet been able to get it to modify the tree yet. I would
9095 like to move objects and remove subtrees directly in the GUI, but have
9096 not found a way to do that with LUMA yet. So in the mean time, I use
9097 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9099 <p
>If you have tips on other GUI tools for LDAP that might be useful
9100 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9102 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9103 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9104 useful GUI alternative. It seem like a good tool, but is unmaintained
9105 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9106 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9111 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9112 <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>
9113 <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>
9114 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9115 <description><p
>A while back, I
9116 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9117 about the fact
</a
> that it is not possible with the provided schemas
9118 for storing DNS and DHCP information in LDAP to combine the two sets
9119 of information into one LDAP object representing a computer.
</p
>
9121 <p
>In the mean time, I discovered that a simple fix would be to make
9122 the dhcpHost object class auxiliary, to allow it to be combined with
9123 the dNSDomain object class, and thus forming one object for one
9124 computer when storing both DHCP and DNS information in LDAP.
</p
>
9126 <p
>If I understand this correctly, it is not safe to do this change
9127 without also changing the assigned number for the object class, and I
9128 do not know enough about LDAP schema design to do that properly for
9129 Debian Edu.
</p
>
9131 <p
>Anyway, for future reference, this is how I believe we could change
9133 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9134 schema
</a
> to solve at least part of the problem with the LDAP schemas
9135 available today from IETF.
</p
>
9138 --- dhcp.schema (revision
65192)
9139 +++ dhcp.schema (working copy)
9141 objectclass (
2.16.840.1.113719.1.203.6.6
9142 NAME
'dhcpHost
'
9143 DESC
'This represents information about a particular client
'
9147 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9148 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9151 <p
>I very much welcome clues on how to do this properly for Debian
9152 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9153 package, and should thus be free to rewrite it as we see fit.
</p
>
9155 <p
>If you want to help out with implementing this for Debian Edu,
9156 please contact us on debian-edu@lists.debian.org.
</p
>
9161 <title>Calling tasksel like the installer, while still getting useful output
</title>
9162 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9163 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9164 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9165 <description><p
>A few times I have had the need to simulate the way tasksel
9166 installs packages during the normal debian-installer run. Until now,
9167 I have ended up letting tasksel do the work, with the annoying problem
9168 of not getting any feedback at all when something fails (like a
9169 conffile question from dpkg or a download that fails), using code like
9172 <blockquote
><pre
>
9173 export DEBIAN_FRONTEND=noninteractive
9174 tasksel --new-install
9175 </pre
></blockquote
>
9177 This would invoke tasksel, let its automatic task selection pick the
9178 tasks to install, and continue to install the requested tasks without
9179 any output what so ever.
9181 Recently I revisited this problem while working on the automatic
9182 package upgrade testing, because tasksel would some times hang without
9183 any useful feedback, and I want to see what is going on when it
9184 happen. Then it occured to me, I can parse the output from tasksel
9185 when asked to run in test mode, and use that aptitude command line
9186 printed by tasksel then to simulate the tasksel run. I ended up using
9189 <blockquote
><pre
>
9190 export DEBIAN_FRONTEND=noninteractive
9191 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9193 </pre
></blockquote
>
9195 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9196 --without-recommends -o APT::Install-Recommends=no -y install
9197 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9198 ~pimportant
</tt
>", which will install the gnome desktop task, the
9199 laptop task and all packages with priority standard , required and
9200 important, just like tasksel would have done it during
9201 installation.
</p
>
9203 <p
>A better approach is probably to extend tasksel to be able to
9204 install packages without using debconf-apt-progress, for use cases
9205 like this.
</p
>
9210 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9211 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9212 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9213 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9214 <description><p
>My
9215 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9216 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9217 finally made the upgrade logs available from
9218 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9219 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9220 apt and aptitude, and found their differences interesting. This time
9221 I will only focus on their removal plans.
</p
>
9223 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9224 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9225 surprising part is that it want to remove xorg and all
9226 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9227 sure why. When asking aptitude to do the same, it want to remove
129
9228 packages, but most of them are library packages I suspect are no
9229 longer needed. Both of them want to remove bluetooth packages, which
9230 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9232 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9233 which seem like a bad idea and xorg the same way as with Gnome. Asking
9234 aptitude for the same, it wants to remove
192 packages, none which are
9235 too surprising.
</p
>
9237 <p
>I guess the removal of xorg during upgrades should be investigated
9238 and avoided, and perhaps others as well. Here are the complete list
9239 of planned removals. The complete logs is available from the URL
9240 above. Note if you want to repeat these tests, that the upgrade test
9241 for kde+apt-get hung in the tasksel setup because of dpkg asking
9242 conffile questions. No idea why. I worked around it by using
9243 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9246 <p
><b
>apt-get gnome
72</b
>
9247 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9248 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9249 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9250 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9251 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9252 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9253 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9254 xserver-xorg-input-kbd xserver-xorg-input-mouse
9255 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9256 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9257 xserver-xorg-video-ati xserver-xorg-video-chips
9258 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9259 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9260 xserver-xorg-video-glint xserver-xorg-video-i128
9261 xserver-xorg-video-i740 xserver-xorg-video-imstt
9262 xserver-xorg-video-intel xserver-xorg-video-mach64
9263 xserver-xorg-video-mga xserver-xorg-video-neomagic
9264 xserver-xorg-video-nsc xserver-xorg-video-nv
9265 xserver-xorg-video-openchrome xserver-xorg-video-r128
9266 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9267 xserver-xorg-video-rendition xserver-xorg-video-s3
9268 xserver-xorg-video-s3virge xserver-xorg-video-savage
9269 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9270 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9271 xserver-xorg-video-tga xserver-xorg-video-trident
9272 xserver-xorg-video-tseng xserver-xorg-video-v4l
9273 xserver-xorg-video-vesa xserver-xorg-video-vga
9274 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9275 xulrunner-
1.9-gnome-support
</p
>
9277 <p
><b
>aptitude gnome
129</b
>
9279 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9280 djvulibre-desktop finger gnome-app-install gnome-mount
9281 gnome-network-admin gnome-spell gnome-vfs-obexftp
9282 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9283 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9284 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9285 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9286 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9287 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9288 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9289 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9290 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9291 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9292 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9293 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9294 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9295 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9296 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9297 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9298 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9299 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9300 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9301 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9302 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9303 openoffice.org-writer2latex openssl-blacklist p7zip
9304 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9305 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9306 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9307 swfdec-mozilla totem-gstreamer update-manager wodim
9308 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9309 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9312 <p
><b
>apt-get kde
82</b
>
9314 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9315 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9316 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9317 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9318 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9319 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9320 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9321 xserver-xorg-input-kbd xserver-xorg-input-mouse
9322 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9323 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9324 xserver-xorg-video-ati xserver-xorg-video-chips
9325 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9326 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9327 xserver-xorg-video-glint xserver-xorg-video-i128
9328 xserver-xorg-video-i740 xserver-xorg-video-imstt
9329 xserver-xorg-video-intel xserver-xorg-video-mach64
9330 xserver-xorg-video-mga xserver-xorg-video-neomagic
9331 xserver-xorg-video-nsc xserver-xorg-video-nv
9332 xserver-xorg-video-openchrome xserver-xorg-video-r128
9333 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9334 xserver-xorg-video-rendition xserver-xorg-video-s3
9335 xserver-xorg-video-s3virge xserver-xorg-video-savage
9336 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9337 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9338 xserver-xorg-video-tga xserver-xorg-video-trident
9339 xserver-xorg-video-tseng xserver-xorg-video-v4l
9340 xserver-xorg-video-vesa xserver-xorg-video-vga
9341 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9343 <p
><b
>aptitude kde
192</b
>
9344 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9345 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9346 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9347 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9348 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9349 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9350 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9351 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9352 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9353 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9354 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9355 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9356 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9357 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9358 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9359 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9360 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9361 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9362 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9363 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9364 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9365 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9366 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9367 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9368 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9369 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9370 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9371 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9372 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9373 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9374 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9375 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9376 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9377 texlive-common texlive-doc-base texlive-fonts-recommended
9378 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9379 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9380 xulrunner-
1.9</p
>
9386 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9387 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9388 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9389 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9390 <description><p
>The last few days I have done some upgrade testing in Debian, to
9391 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9392 have been discovered and reported in the process
9393 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9394 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9395 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9396 kdebase-workspace-data), and to get a more regular testing going on, I
9397 am working on a script to automate the test.
</p
>
9399 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9400 Gnome or KDE desktop installation inside the chroot before upgrading
9401 it. To ensure no services are started in the chroot, a policy-rc.d
9402 script is inserted. To make sure tasksel believe it is to install a
9403 desktop on a laptop, the tasksel tests are replaced in the chroot
9404 (only acceptable because this is a throw-away chroot).
</p
>
9406 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9407 currently always fail because udev refuses to upgrade with the kernel
9408 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9409 is created. The bug report
9410 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9411 this problem do not trigger in a chroot, but I touch the file anyway
9412 to make sure the upgrade go well. Testing on virtual and real
9413 hardware have failed me because of udev so far, and creating this file
9414 do the trick in such settings anyway. This is a
9415 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9416 issue
</a
> and the current udev behaviour is intended by the udev
9417 maintainer because he lack the resources to rewrite udev to keep
9418 working with old kernels or something like that. I really wish the
9419 udev upstream would keep udev backwards compatible, to avoid such
9420 upgrade problem, but given that they fail to do so, I guess
9421 documenting the way out of this mess is the best option we got for
9422 Debian Squeeze.
</p
>
9424 <p
>Anyway, back to the task at hand, testing upgrades. This test
9425 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9428 <blockquote
><pre
>
9432 if [
"$
1" ] ; then
9441 exec
&lt; /dev/null
9443 mirror=http://ftp.skolelinux.org/debian
9444 tmpdir=chroot-$from-upgrade-$to-$desktop
9446 debootstrap $from $tmpdir $mirror
9447 chroot $tmpdir aptitude update
9448 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9452 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9456 mount -t proc proc $tmpdir/proc
9457 # Make sure proc is unmounted also on failure
9458 trap exit_cleanup EXIT INT
9460 chroot $tmpdir aptitude -y install debconf-utils
9462 # Make sure tasksel autoselection trigger. It need the test scripts
9463 # to return the correct answers.
9464 echo tasksel tasksel/desktop multiselect $desktop | \
9465 chroot $tmpdir debconf-set-selections
9467 # Include the desktop and laptop task
9468 for test in desktop laptop ; do
9469 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9473 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9476 DEBIAN_FRONTEND=noninteractive
9477 DEBIAN_PRIORITY=critical
9478 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9479 chroot $tmpdir tasksel --new-install
9481 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9482 chroot $tmpdir aptitude update
9483 touch $tmpdir/etc/udev/kernel-upgrade
9484 chroot $tmpdir aptitude -y dist-upgrade
9486 </pre
></blockquote
>
9488 <p
>I suspect it would be useful to test upgrades with both apt-get and
9489 with aptitude, but I have not had time to look at how they behave
9490 differently so far. I hope to get a cron job running to do the test
9491 regularly and post the result on the web. The Gnome upgrade currently
9492 work, while the KDE upgrade fail because of the bug in
9493 kdebase-workspace-data
</p
>
9495 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9496 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9497 post, so I will refrain from trying. I can report that for Gnome,
9498 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9499 remove and
1 not upgraded and
1024MB need to be downloaded while for
9500 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9501 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9503 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9504 is able to migrate to dependency based boot sequencing and parallel
9505 booting without a hitch. Was unsure if there were still bugs with
9506 packages failing to clean up their obsolete init.d script during
9507 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9513 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9514 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9515 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9516 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9517 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9518 scripts to migrate (some of) their operations to upstart job while
9519 keeping the init.d for hurd and kfreebsd. The packages with such
9520 needs will need a way to get their init.d scripts to behave
9521 differently when used with sysvinit and with upstart. Because of
9522 this, I had a look at the environment variables set when a init.d
9523 script is running under upstart, and when it is not.
</p
>
9525 <p
>With upstart, I notice these environment variables are set when a
9526 script is started from rcS.d/ (ignoring some irrelevant ones like
9529 <blockquote
><pre
>
9535 UPSTART_EVENTS=startup
9537 UPSTART_JOB=rc-sysinit
9538 </pre
></blockquote
>
9540 <p
>With sysvinit, these environment variables are set for the same
9543 <blockquote
><pre
>
9544 INIT_VERSION=sysvinit-
2.88
9549 </pre
></blockquote
>
9551 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9552 sysvinit are not set by upstart. Not sure if it is intentional or not
9553 to not be compatible with sysvinit in this regard.
</p
>
9555 <p
>For scripts needing to behave differently when upstart is used,
9556 looking for the UPSTART_JOB environment variable seem to be a good
9562 <title>A manual for standards wars...
</title>
9563 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9564 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9565 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9566 <description><p
>Via the
9567 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9568 of Rob Weir
</a
> I came across the very interesting essay named
9569 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9570 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9571 following the standards wars of today.
</p
>
9576 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9577 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9578 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9579 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9580 <description><p
>When using sitesummary at a site to track machines, it is possible
9581 to get a list of the machine types in use thanks to the DMI
9582 information extracted from each machine. The script to do so is
9583 included in the sitesummary package, and here is example output from
9584 the Skolelinux build servers:
</p
>
9586 <blockquote
><pre
>
9587 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9589 Dell Computer Corporation
1
9592 eserver xSeries
345 -[
8670M1X]-
1
9596 </pre
></blockquote
>
9598 <p
>The quality of the report depend on the quality of the DMI tables
9599 provided in each machine. Here there are Intel machines without model
9600 information listed with Intel as vendor and no model, and virtual Xen
9601 machines listed as [no-dmi-info]. One can add -l as a command line
9602 option to list the individual machines.
</p
>
9604 <p
>A larger list is
9605 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9606 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9607 provide the basic sitesummary report publicly. In their report there
9608 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9609 their machines, and as sitesummary is available in both distributions,
9610 it is trivial to get all of them to report to the same central
9611 collector.
</p
>
9616 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9617 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9618 <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>
9619 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9620 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9621 start at boot when an NVidia video card is used is handled. The
9622 problem seem to be that the nvidia X.org driver uses a long time to
9623 initialize, and this duration is longer than kdm is configured to
9626 <p
>I came across two bugs related to this issue,
9627 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9628 against initscripts and passed on to nvidia-glx when it became obvious
9629 that the nvidia drivers were involved, and
9630 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9631 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9633 <p
>To me, it seem that no-one is interested in actually solving the
9634 problem nvidia video card owners experience and make sure the Debian
9635 distribution work out of the box for these users. The nvidia driver
9636 maintainers expect kdm to be set up to wait longer, while kdm expect
9637 the nvidia driver maintainers to fix the driver to start faster, and
9638 while they wait for each other I guess the users end up switching to a
9639 distribution that work for them. I have no idea what the solution is,
9640 but I am pretty sure that waiting for each other is not it.
</p
>
9642 <p
>I wonder why we end up handling bugs this way.
</p
>
9647 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9648 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9649 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9650 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9651 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9652 The feature seem to hold up pretty well, but three fairly serious
9653 issues are known and should be solved:
9657 <li
>The wicd package seen to
9658 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9659 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9660 parallel booting is enabled. No idea why, but the wicd maintainer
9661 seem to be on the case.
</li
>
9663 <li
>The nvidia X driver seem to
9664 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9665 triggered more easily when parallel booting is in effect. The
9666 maintainer is on the case.
</li
>
9668 <li
>The sysv-rc package fail to properly enable dependency based boot
9669 sequencing (the shutdown is broken) when old file-rc users
9670 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9671 sysv-rc. One way to solve it would be for file-rc to create
9672 /etc/init.d/.legacy-bootordering, and another is to try to make
9673 sysv-rc more robust. Will investigate some more and probably upload a
9674 workaround in sysv-rc to help those trying to move from file-rc to
9675 sysv-rc get a working shutdown.
</li
>
9677 </ul
></p
>
9679 <p
>All in all not many surprising issues, and all of them seem
9680 solvable before Squeeze is released. In addition to these there are
9681 some packages with bugs in their dependencies and run level settings,
9682 which I expect will be fixed in a reasonable time span.
</p
>
9684 <p
>If you report any problems with dependencies in init.d scripts to
9685 the BTS, please usertag the report to get it to show up at
9686 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9687 list of usertagged bugs related to this
</a
>.
</p
>
9689 <p
>Update: Correct bug number to file-rc issue.
</p
>
9694 <title>More flexible firmware handling in debian-installer
</title>
9695 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9696 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9697 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9698 <description><p
>After a long break from debian-installer development, I finally
9699 found time today to return to the project. Having to spend less time
9700 working dependency based boot in debian, as it is almost complete now,
9701 definitely helped freeing some time.
</p
>
9703 <p
>A while back, I ran into a problem while working on Debian Edu. We
9704 include some firmware packages on the Debian Edu CDs, those needed to
9705 get disk and network controllers working. Without having these
9706 firmware packages available during installation, it is impossible to
9707 install Debian Edu on the given machine, and because our target group
9708 are non-technical people, asking them to provide firmware packages on
9709 an external medium is a support pain. Initially, I expected it to be
9710 enough to include the firmware packages on the CD to get
9711 debian-installer to find and use them. This proved to be wrong.
9712 Next, I hoped it was enough to symlink the relevant firmware packages
9713 to some useful location on the CD (tried /cdrom/ and
9714 /cdrom/firmware/). This also proved to not work, and at this point I
9715 found time to look at the debian-installer code to figure out what was
9716 going to work.
</p
>
9718 <p
>The firmware loading code is in the hw-detect package, and a closer
9719 look revealed that it would only look for firmware packages outside
9720 the installation media, so the CD was never checked for firmware
9721 packages. It would only check USB sticks, floppies and other
9722 "external
" media devices. Today I changed it to also look in the
9723 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9724 solve the problem I ran into with Debian edu. I also changed it to
9725 look in /firmware/, to make sure the installer also find firmware
9726 provided in the initrd when booting the installer via PXE, to allow us
9727 to provide the same feature in the PXE setup included in Debian
9730 <p
>To make sure firmware deb packages with a license questions are not
9731 activated without asking if the license is accepted, I extended
9732 hw-detect to look for preinst scripts in the firmware packages, and
9733 run these before activating the firmware during installation. The
9734 license question is asked using debconf in the preinst, so this should
9735 solve the issue for the firmware packages I have looked at so far.
</p
>
9737 <p
>If you want to discuss the details of these features, please
9738 contact us on debian-boot@lists.debian.org.
</p
>
9743 <title>Parallellized boot is now the default in Debian/unstable
</title>
9744 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9745 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9746 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9747 <description><p
>Since this evening, parallel booting is the default in
9748 Debian/unstable for machines using dependency based boot sequencing.
9749 Apparently the testing of concurrent booting has been wider than
9750 expected, if I am to believe the
9751 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9752 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9753 with the feature this weekend, to give us some time to detect any
9754 remaining problems before Squeeze is frozen. If serious problems are
9755 detected, it is simple to change the default back to sequential boot.
9756 The upload of the new sysvinit package also activate a new upstream
9759 More information about
9760 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9761 based boot sequencing
</a
> is available from the Debian wiki. It is
9762 currently possible to disable parallel booting when one run into
9763 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9765 <blockquote
><pre
>
9767 </pre
></blockquote
>
9769 <p
>If you report any problems with dependencies in init.d scripts to
9770 the BTS, please usertag the report to get it to show up at
9771 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9772 list of usertagged bugs related to this
</a
>.
</p
>
9777 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9778 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9780 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9781 <description><p
>In the recent Debian Edu versions, the
9782 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9783 system
</a
> is used to keep track of the machines in the school
9784 network. Each machine will automatically report its status to the
9785 central server after boot and once per night. The network setup is
9786 also reported, and using this information it is possible to get the
9787 MAC address of all network interfaces in the machines. This is useful
9788 to update the DHCP configuration.
</p
>
9790 <p
>To give some idea how to use sitesummary, here is a one-liner to
9791 ist all MAC addresses of all machines reporting to sitesummary. Run
9792 this on the collector host:
</p
>
9794 <blockquote
><pre
>
9795 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9796 </pre
></blockquote
>
9798 <p
>This will list all MAC addresses assosiated with all machine, one
9799 line per machine and with space between the MAC addresses.
</p
>
9801 <p
>To allow system administrators easier job at adding static DHCP
9802 addresses for hosts, it would be possible to extend this to fetch
9803 machine information from sitesummary and update the DHCP and DNS
9804 tables in LDAP using this information. Such tool is unfortunately not
9805 written yet.
</p
>
9810 <title>systemd, an interesting alternative to upstart
</title>
9811 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9812 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9813 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9814 <description><p
>The last few days a new boot system called
9815 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9817 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9819 to the free software world. I have not yet had time to play around
9820 with it, but it seem to be a very interesting alternative to
9821 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9822 a good alternative for Debian when we are able to switch to an event
9823 based boot system. Tollef is
9824 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9825 systemd into Debian, and I look forward to seeing how well it work. I
9826 like the fact that systemd handles init.d scripts with dependency
9827 information natively, allowing them to run in parallel where upstart
9828 at the moment do not.
</p
>
9830 <p
>Unfortunately do systemd have the same problem as upstart regarding
9831 platform support. It only work on recent Linux kernels, and also need
9832 some new kernel features enabled to function properly. This means
9833 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9834 system. Not sure how that will be handled if systemd proves to be the
9835 way forward.
</p
>
9837 <p
>In the mean time, based on the
9838 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9839 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9840 decided to enable full parallel booting as the default in Debian as
9841 soon as possible (probably this weekend or early next week), to see if
9842 there are any remaining serious bugs in the init.d dependencies. A
9843 new version of the sysvinit package implementing this change is
9844 already in experimental. If all go well, Squeeze will be released
9845 with parallel booting enabled by default.
</p
>
9850 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9851 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9852 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9853 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9854 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9855 complete, so complete that it is actually possible to run all the
9856 init.d scripts in parallell based on these dependencies. If you want
9857 to test your Squeeze system, make sure
9858 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9859 based boot sequencing
</a
> is enabled, and add this line to
9860 /etc/default/rcS:
</p
>
9862 <blockquote
><pre
>
9863 CONCURRENCY=makefile
9864 </pre
></blockquote
>
9866 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9867 scripts in parallel using the dependency information stored in
9868 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9869 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9870 to try to start the kdm and gdm scripts as early as possible, and will
9871 start the facilities required by kdm or gdm as early as possible to
9872 make this happen.
</p
>
9874 <p
>Give it a try, and see if you like the result. If some services
9875 fail to start properly, it is most likely because they have incomplete
9876 init.d script dependencies in their startup script (or some of their
9877 dependent scripts have incomplete dependencies). Report bugs and get
9878 the package maintainers to fix it. :)
</p
>
9880 <p
>Running scripts in parallel could be the default in Debian when we
9881 manage to get the init.d script dependencies complete and correct. I
9882 expect we will get there in Squeeze+
1, if we get manage to test and
9883 fix the remaining issues.
</p
>
9885 <p
>If you report any problems with dependencies in init.d scripts to
9886 the BTS, please usertag the report to get it to show up at
9887 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9888 list of usertagged bugs related to this
</a
>.
</p
>
9893 <title>Debian has switched to dependency based boot sequencing
</title>
9894 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9895 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9896 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9897 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9898 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9899 have been migrated to using dependency based boot sequencing. This
9900 conclude work me and others have been doing for the last three days.
9901 It feels great to see this finally part of the default Debian
9902 installation. Now we just need to weed out the last few problems that
9903 are bound to show up, to get everything ready for Squeeze.
</p
>
9905 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9906 fixing the more fundamental problem of handing the event based
9907 non-predictable kernel in the early boot.
</p
>
9912 <title>Taking over sysvinit development
</title>
9913 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9914 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9915 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9916 <description><p
>After several years of frustration with the lack of activity from
9917 the existing sysvinit upstream developer, I decided a few weeks ago to
9918 take over the package and become the new upstream. The number of
9919 patches to track for the Debian package was becoming a burden, and the
9920 lack of synchronization between the distribution made it hard to keep
9921 the package up to date.
</p
>
9923 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9924 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9925 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9926 and Fedora), based on the patches currently in use in these
9927 distributions. We Debian maintainers plan to move to this tarball as
9928 the new upstream as soon as we find time to do the merge. Since the
9929 new tarball was created, we agreed with Werner at SuSe to make a new
9930 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9931 development there. The project is registered and currently waiting
9932 for approval by the Savannah administrators, and as soon as it is
9933 approved, we will import the old versions from svn and continue
9934 working on the future release.
</p
>
9936 <p
>It is a bit ironic that this is done now, when some of the involved
9937 distributions are moving to upstart as a syvinit replacement.
</p
>
9942 <title>Debian boots quicker and quicker
</title>
9943 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9944 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9945 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9946 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9947 people involved in the boot system on Debian and Ubuntu, to see if we
9948 could find more ways to speed up the boot system. This was an Ubuntu
9950 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9951 gathering
</a
>. It was quite productive. We also discussed the future
9952 of boot systems, and ways to handle the increasing number of boot
9953 issues introduced by the Linux kernel becoming more and more
9954 asynchronous and event base. The Ubuntu approach using udev and
9955 upstart might be a good way forward. Time will show.
</p
>
9957 <p
>Anyway, there are a few ways at the moment to speed up the boot
9958 process in Debian. All of these should be applied to get a quick
9963 <li
>Use dash as /bin/sh.
</li
>
9965 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9966 clock is in UTC.
</li
>
9968 <li
>Install and activate the insserv package to enable
9969 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9970 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9974 These points are based on the Google summer of code work done by
9975 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9978 <p
>Support for makefile-style concurrency during boot was uploaded to
9979 unstable yesterday. When we tested it, we were able to cut
6 seconds
9980 from the boot sequence. It depend on very correct dependency
9981 declaration in all init.d scripts, so I expect us to find edge cases
9982 where the dependences in some scripts are slightly wrong when we start
9983 using this.
</p
>
9985 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9986 introduced by Raphael Geissert today, one that could affect the
9987 startup speed as well. Instead of starting some scripts concurrently
9988 from rcS.d/ and another set of scripts from rc2.d/, it would be
9989 possible to run a of them in the same process. A quick way to test
9990 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9991 insserv
'. Will need to test if that work. :)
</p
>
9996 <title>BSAs påstander om piratkopiering møter motstand
</title>
9997 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
9998 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
9999 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10000 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10001 programvareselskapene som Microsoft og Apple, publisert en rapport der
10002 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10003 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10005 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10006 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10007 dagene. Et spesielt interessant kommentar fra Sverige,
10008 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10009 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10012 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10013 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10014 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10015 exakta
", säger BSAs Sverigechef John Hugosson.
10016 </blockquote
>
10018 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10019 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10020 piracy figures need a shot of reality
</a
> og
<a
10021 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10022 Copyright Treaty Work?
</a
></p
>
10024 <p
>Fant lenkene via
<a
10025 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10026 på Slashdot
</a
>.
</p
>
10031 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10032 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10033 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10034 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10035 <description><p
>Kom over
10036 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10037 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10038 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10039 jobber til daglig. En rask opptelling forteller meg at vi har
490
10040 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10041 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10042 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10047 <title>Kryptert harddisk - naturligvis
</title>
10048 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10049 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10050 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10051 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10052 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10053 når en tar tap av arbeidstid, fortrolige dokumenter,
10054 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10055 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10056 til at jeg har kryptert harddisken på både kontormaskinen og min
10057 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10058 komme på avveie, den første informasjon relatert til jobben min ved
10059 Universitetet i Oslo, og den andre relatert til blant annet
10060 foreningsarbeide. Kryptering av diskene gjør at det er lite
10061 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10062 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10063 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10064 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10065 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10066 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10067 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10068 det er gjort slik jeg gjør det er minimale, og gevinstene er
10069 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10070 maskinen reinstalleres og alt er tapt.
</p
>
10072 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10073 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10074 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10075 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10076 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10077 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10078 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10079 betydelige.
</p
>
10084 <title>Two projects that have improved the quality of free software a lot
</title>
10085 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10086 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10087 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10088 <description><p
>There are two software projects that have had huge influence on the
10089 quality of free software, and I wanted to mention both in case someone
10090 do not yet know them.
</p
>
10092 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10093 tool to detect and expose errors in the memory handling of programs.
10094 It is easy to use, all one need to do is to run
'valgrind program
',
10095 and it will report any problems on stdout. It is even better if the
10096 program include debug information. With debug information, it is able
10097 to report the source file name and line number where the problem
10098 occurs. It can report things like
'reading past memory block in file
10099 X line N, the memory block was allocated in file Y, line M
', and
10100 'using uninitialised value in control logic
'. This tool has made it
10101 trivial to investigate reproducible crash bugs in programs, and have
10102 reduced the number of this kind of bugs in free software a lot.
10104 <p
>The second one is
10105 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10106 a source code checker. It is able to process the source of a program
10107 and find problems in the logic without running the program. It
10108 started out as the Stanford Checker and became well known when it was
10109 used to find bugs in the Linux kernel. It is now a commercial tool
10110 and the company behind it is running
10111 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10112 free software community, where a lot of free software projects get
10113 their source checked for free. Several thousand defects have been
10114 found and fixed so far. It can find errors like
'lock L taken in file
10115 X line N is never released if exiting in line M
', or
'the code in file
10116 Y lines O to P can never be executed
'. The projects included in the
10117 community service project have managed to get rid of a lot of
10118 reliability problems thanks to Coverity.
</p
>
10120 <p
>I believe tools like this, that are able to automatically find
10121 errors in the source, are vital to improve the quality of software and
10122 make sure we can get rid of the crashing and failing software we are
10123 surrounded by today.
</p
>
10128 <title>No patch is not better than a useless patch
</title>
10129 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10130 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10131 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10132 <description><p
>Julien Blache
10133 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10134 patch is better than a useless patch
</a
>. I completely disagree, as a
10135 patch allow one to discuss a concrete and proposed solution, and also
10136 prove that the issue at hand is important enough for someone to spent
10137 time on fixing it. No patch do not provide any of these positive
10138 properties.
</p
>
10143 <title>Standardize on protocols and formats, not vendors and applications
</title>
10144 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10145 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10146 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10147 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10148 very good one to form a long lived computer infrastructure. It is the
10149 simple one, lost by many in todays computer industry: Standardize on
10150 open network protocols and open exchange/storage formats, not applications.
10151 Applications come and go, while protocols and files tend to stay, and
10152 thus one want to make it easy to change application and vendor, while
10153 avoiding conversion costs and locking users to a specific platform or
10154 application.
</p
>
10156 <p
>This approach make it possible to replace the client applications
10157 independently of the server applications. One can even allow users to
10158 use several different applications as long as they handle the selected
10159 protocol and format. In the normal case, only one client application
10160 is recommended and users only get help if they choose to use this
10161 application, but those that want to deviate from the easy path are not
10162 blocked from doing so.
</p
>
10164 <p
>It also allow us to replace the server side without forcing the
10165 users to replace their applications, and thus allow us to select the
10166 best server implementation at any moment, when scale and resouce
10167 requirements change.
</p
>
10169 <p
>I strongly recommend standardizing - on open network protocols and
10170 open formats, but I would never recommend standardizing on a single
10171 application that do not use open network protocol or open formats.
</p
>
10176 <title>Returning from Skolelinux developer gathering
</title>
10177 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10178 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10179 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10180 <description><p
>I
'm sitting on the train going home from this weekends Debian
10181 Edu/Skolelinux development gathering. I got a bit done tuning the
10182 desktop, and looked into the dynamic service location protocol
10183 implementation avahi. It look like it could be useful for us. Almost
10184 30 people participated, and I believe it was a great environment to
10185 get to know the Skolelinux system. Walter Bender, involved in the
10186 development of the Sugar educational platform, presented his stuff and
10187 also helped me improve my OLPC installation. He also showed me that
10188 his Turtle Art application can be used in standalone mode, and we
10189 agreed that I would help getting it packaged for Debian. As a
10190 standalone application it would be great for Debian Edu. We also
10191 tried to get the video conferencing working with two OLPCs, but that
10192 proved to be too hard for us. The application seem to need more work
10193 before it is ready for me. I look forward to getting home and relax
10199 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10200 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10201 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10202 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10203 <description><p
>The state of standardized LDAP schemas on Linux is far from
10204 optimal. There is RFC
2307 documenting one way to store NIS maps in
10205 LDAP, and a modified version of this normally called RFC
2307bis, with
10206 some modifications to be compatible with Active Directory. The RFC
10207 specification handle the content of a lot of system databases, but do
10208 not handle DNS zones and DHCP configuration.
</p
>
10210 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10211 we would like to store information about users, SMB clients/hosts,
10212 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10213 and LTSP configuration in LDAP. These objects have a lot in common,
10214 but with the current LDAP schemas it is not possible to have one
10215 object per entity. For example, one need to have at least three LDAP
10216 objects for a given computer, one with the SMB related stuff, one with
10217 DNS information and another with DHCP information. The schemas
10218 provided for DNS and DHCP are impossible to combine into one LDAP
10219 object. In addition, it is impossible to implement quick queries for
10220 netgroup membership, because of the way NIS triples are implemented.
10221 It just do not scale. I believe it is time for a few RFC
10222 specifications to cleam up this mess.
</p
>
10224 <p
>I would like to have one LDAP object representing each computer in
10225 the network, and this object can then keep the SMB (ie host key), DHCP
10226 (mac address/name) and DNS (name/IP address) settings in one place.
10227 It need to be efficently stored to make sure it scale well.
</p
>
10229 <p
>I would also like to have a quick way to map from a user or
10230 computer and to the net group this user or computer is a member.
</p
>
10232 <p
>Active Directory have done a better job than unix heads like myself
10233 in this regard, and the unix side need to catch up. Time to start a
10234 new IETF work group?
</p
>
10239 <title>Endelig er Debian Lenny gitt ut
</title>
10240 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10242 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10243 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10244 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10245 Et langt steg videre for Debian-prosjektet, og en rekke nye
10246 programpakker blir nå tilgjengelig for de av oss som bruker den
10247 stabile utgaven av Debian. Neste steg er nå å få
10248 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10249 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10250 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10251 slippes løs på skolene. Takk til alle debian-utviklerne som har
10252 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10253 bootsekvens tilgjengelig i stabil utgave, vha pakken
10254 <tt
>insserv
</tt
>.
</p
>
10259 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10260 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10261 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10262 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10263 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10264 Oslo. Most of Saturday was used for the general assemly for the
10265 member organization, but the rest of the weekend I used to tune the
10266 LTSP installation. LTSP now work out of the box on the
10-network.
10267 Acer Aspire One proved to be a very nice thin client, with both
10268 screen, mouse and keybard in a small box. Was working on getting the
10269 diskless workstation setup configured out of the box, but did not
10270 finish it before the weekend was up.
</p
>
10272 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10273 the Brazilian group, so that will have to wait for the next
10274 development gathering. Would love to have the Debian Edu installer
10275 automatically detect and configure a multiseat setup when it find one
10276 of these cards.
</p
>
10281 <title>The sorry state of multimedia browser plugins in Debian
</title>
10282 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10283 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10284 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10285 <description><p
>Recently I have spent some time evaluating the multimedia browser
10286 plugins available in Debian Lenny, to see which one we should use by
10287 default in Debian Edu. We need an embedded video playing plugin with
10288 control buttons to pause or stop the video, and capable of streaming
10289 all the multimedia content available on the web. The test results and
10290 notes are available on
10291 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10292 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10293 fill this need. My personal video player favorite, VLC, has a really
10294 bad plugin which fail on a lot of the test pages. A lot of the MIME
10295 types I would expect to work with any free software player (like
10296 video/ogg), just do not work. And simple formats like the
10297 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10298 totem and vlc plugins. I hope the situation will improve soon. No
10299 wonder sites use the proprietary Adobe flash to play video.
</p
>
10301 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10302 be the only one fitting our needs. :/
</p
>