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
>
1217 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
1219 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
1220 and updated recipe for using the Signal app without a mobile
1221 phone
</a
>.
</p
>
1226 <title>The new
"best
" multimedia player in Debian?
</title>
1227 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
1228 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
1229 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
1230 <description><p
>When I set out a few weeks ago to figure out
1231 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
1232 multimedia player in Debian claimed to support most file formats /
1233 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
1234 the various players claimed support for. The range was from
55 to
130
1235 MIME types. I suspect most media formats are supported by all
1236 players, but this is not really reflected in the MimeTypes values in
1237 their desktop files. There are probably also some bogus MIME types
1238 listed, but it is hard to identify which one this is.
</p
>
1240 <p
>Anyway, in the mean time I got in touch with upstream for some of
1241 the players suggesting to add more MIME types to their desktop files,
1242 and decided to spend some time myself improving the situation for my
1243 favorite media player VLC. The fixes for VLC entered Debian unstable
1244 yesterday. The complete list of MIME types can be seen on the
1245 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
1246 player MIME type support status
</a
> Debian wiki page.
</p
>
1248 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
1249 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
1250 kmplayer. I am sure some of the other players desktop files support
1251 several of the formats currently listed as working only with vlc,
1252 toten and parole.
</p
>
1254 <p
>A sad observation is that only
14 MIME types are listed as
1255 supported by all the tested multimedia players in Debian in their
1256 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
1257 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
1258 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
1259 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
1260 it sad that video/ogg and video/webm is not supported by all the media
1261 players in Debian. As far as I can tell, all of them can handle both
1267 <title>A program should be able to open its own files on Linux
</title>
1268 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
1269 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
1270 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
1271 <description><p
>Many years ago, when koffice was fresh and with few users, I
1272 decided to test its presentation tool when making the slides for a
1273 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
1274 wrote the first draft of the slides, saved the result and went to bed
1275 the day before I would give the talk. The next day I took a plane to
1276 the location where the meeting should take place, and on the plane I
1277 started up koffice again to polish the talk a bit, only to discover
1278 that kpresenter refused to load its own data file. I cursed a bit and
1279 started making the slides again from memory, to have something to
1280 present when I arrived. I tested that the saved files could be
1281 loaded, and the day seemed to be rescued. I continued to polish the
1282 slides until I suddenly discovered that the saved file could no longer
1283 be loaded into kpresenter. In the end I had to rewrite the slides
1284 three times, condensing the content until the talk became shorter and
1285 shorter. After the talk I was able to pinpoint the problem
&ndash;
1286 kpresenter wrote inline images in a way itself could not understand.
1287 Eventually that bug was fixed and kpresenter ended up being a great
1288 program to make slides. The point I
'm trying to make is that we
1289 expect a program to be able to load its own data files, and it is
1290 embarrassing to its developers if it can
't.
</p
>
1292 <p
>Did you ever experience a program failing to load its own data
1293 files from the desktop file browser? It is not a uncommon problem. A
1294 while back I discovered that the screencast recorder
1295 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
1296 browser would refuse to open. No video player claimed to understand
1297 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
1298 returning the application/ogg MIME type, which no video player I had
1299 installed listed as a MIME type they would understand. I asked for
1300 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
1301 behavour
</a
> and use the MIME type video/ogg instead. I also asked
1302 several video players to add video/ogg to their desktop files, to give
1303 the file browser an idea what to do about Ogg Theora files. After a
1304 while, the desktop file browsers in Debian started to handle the
1305 output from gtk-recordmydesktop properly.
</p
>
1307 <p
>But history repeats itself. A few days ago I tested the music
1308 system Rosegarden again, and I discovered that the KDE and xfce file
1309 browsers did not know what to do with the Rosegarden project files
1310 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
1311 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
1312 included in the next upload. To increase the chance of me remembering
1313 how to fix the problem next time some program fail to load its files
1314 from the file browser, here are some notes on how to fix it.
</p
>
1316 <p
>The file browsers in Debian in general operates on MIME types.
1317 There are two sources for the MIME type of a given file. The output from
1318 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
1319 shared MIME type registry (under /usr/share/mime/). The file MIME
1320 type is mapped to programs supporting the MIME type, and this
1321 information is collected from
1322 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
1323 desktop files
</a
> available in /usr/share/applications/. If there is
1324 one desktop file claiming support for the MIME type of the file, it is
1325 activated when asking to open a given file. If there are more, one
1326 can normally select which one to use by right-clicking on the file and
1327 selecting the wanted one using
'Open with
' or similar. In general
1328 this work well. But it depend on each program picking a good MIME
1330 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
1331 MIME type registered with IANA
</a
>), file and/or the shared MIME
1332 registry recognizing the file and the desktop file to list the MIME
1333 type in its list of supported MIME types.
</p
>
1335 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
1336 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
1337 Shared MIME database
</a
> look like this:
</p
>
1339 <p
><blockquote
><pre
>
1340 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
1341 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
1342 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
1343 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
1344 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
1345 &lt;glob pattern=
"*.rg
"/
&gt;
1346 &lt;/mime-type
&gt;
1347 &lt;/mime-info
&gt;
1348 </pre
></blockquote
></p
>
1350 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
1351 (it is a gzipped XML file). Note, it is much better to use an
1352 official MIME type registered with IANA than it is to make up ones own
1353 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
1355 <p
>The desktop file of the rosegarden program failed to list
1356 audio/x-rosegarden in its list of supported MIME types, causing the
1357 file browsers to have no idea what to do with *.rg files:
</p
>
1359 <p
><blockquote
><pre
>
1360 % grep Mime /usr/share/applications/rosegarden.desktop
1361 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
1362 X-KDE-NativeMimeType=audio/x-rosegarden-composition
1364 </pre
></blockquote
></p
>
1366 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
1367 MimeType= line.
</p
>
1369 <p
>If you run into a file which fail to open the correct program when
1370 selected from the file browser, please check out the output from
1371 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
1372 MIME type is registered somewhere under /usr/share/mime/ and check
1373 that some desktop file under /usr/share/applications/ is claiming
1374 support for this MIME type. If not, please report a bug to have it
1380 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
1381 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
1382 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
1383 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
1384 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
1385 system
</a
> is a user-focused solution in Debian for handling hardware
1386 related packages. The idea is to have a database of mappings between
1387 hardware and packages, and pop up a dialog suggesting for the user to
1388 install the packages to use a given hardware dongle. Some use cases
1389 are when you insert a Yubikey, it proposes to install the software
1390 needed to control it; when you insert a braille reader list it
1391 proposes to install the packages needed to send text to the reader;
1392 and when you insert a ColorHug screen calibrator it suggests to
1393 install the driver for it. The system work well, and even have a few
1394 command line tools to install firmware packages and packages for the
1395 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
1397 <p
>The system was initially written using aptdaemon, because I found
1398 good documentation and example code on how to use it. But aptdaemon
1399 is going away and is generally being replaced by
1400 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
1401 so Isenkram needed a rewrite. And today, thanks to the great patch
1402 from my college Sunil Mohan Adapa in the FreedomBox project, the
1403 rewrite finally took place. I
've just uploaded a new version of
1404 Isenkram into Debian Unstable with the patch included, and the default
1405 for the background daemon is now to use PackageKit. To check it out,
1406 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
1407 and see if it is recognised.
</p
>
1409 <p
>If you want to know what kind of packages isenkram would propose for
1410 the machine it is running on, you can check out the isenkram-lookup
1411 program. This is what it look like on a Thinkpad X230:
</p
>
1413 <p
><blockquote
><pre
>
1429 </pre
></blockquote
></p
>
1431 <p
>The hardware mappings come from several places. The preferred way
1432 is for packages to announce their hardware support using
1433 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
1434 cross distribution appstream system
</a
>.
1436 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
1437 blog posts about isenkram
</a
> to learn how to do that.
</p
>
1442 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
1443 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
1444 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
1445 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
1446 <description><p
>Yesterday I updated the
1447 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
1448 package in Debian
</a
> with a few patches sent to me by skilled and
1449 enterprising users. There were some nice user and visible changes.
1450 First of all, both desktop menu entries now work. A design flaw in
1451 one of the script made the history graph fail to show up (its PNG was
1452 dumped in ~/.xsession-errors) if no controlling TTY was available.
1453 The script worked when called from the command line, but not when
1454 called from the desktop menu. I changed this to look for a DISPLAY
1455 variable or a TTY before deciding where to draw the graph, and now the
1456 graph window pop up as expected.
</p
>
1458 <p
>The next new feature is a discharge rate estimator in one of the
1459 graphs (the one showing the last few hours). New is also the user of
1460 colours showing charging in blue and discharge in red. The percentages
1461 of this graph is relative to last full charge, not battery design
1464 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
1466 <p
>The other graph show the entire history of the collected battery
1467 statistics, comparing it to the design capacity of the battery to
1468 visualise how the battery life time get shorter over time. The red
1469 line in this graph is what the previous graph considers
100 percent:
1471 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
1473 <p
>In this graph you can see that I only charge the battery to
80
1474 percent of last full capacity, and how the capacity of the battery is
1475 shrinking. :(
</p
>
1477 <p
>The last new feature is in the collector, which now will handle
1478 more hardware models. On some hardware, Linux power supply
1479 information is stored in /sys/class/power_supply/ACAD/, while the
1480 collector previously only looked in /sys/class/power_supply/AC/. Now
1481 both are checked to figure if there is power connected to the
1484 <p
>If you are interested in how your laptop battery is doing, please
1486 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1487 in Debian unstable, or rebuild it on Jessie to get it working on
1488 Debian stable. :) The upstream source is available from
<a
1489 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1490 Patches are very welcome.
</p
>
1492 <p
>As usual, if you use Bitcoin and want to show your support of my
1493 activities, please send Bitcoin donations to my address
1494 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1499 <title>Debian now with ZFS on Linux included
</title>
1500 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
1501 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
1502 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
1503 <description><p
>Today, after many years of hard work from many people,
1504 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
1505 Debian. The package status can be seen on
1506 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
1507 for zfs-linux
</a
>. and
1508 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1509 team status page
</a
>. If you want to help out, please join us.
1510 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
1511 source code
</a
> is available via git on Alioth. It would also be
1512 great if you could help out with
1513 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
1514 it is an important piece of the puzzle to get ZFS working.
</p
>
1519 <title>What is the best multimedia player in Debian?
</title>
1520 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
1521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
1522 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
1523 <description><p
><strong
>Where I set out to figure out which multimedia player in
1524 Debian claim support for most file formats.
</strong
></p
>
1526 <p
>A few years ago, I had a look at the media support for Browser
1527 plugins in Debian, to get an idea which plugins to include in Debian
1528 Edu. I created a script to extract the set of supported MIME types
1529 for each plugin, and used this to find out which multimedia browser
1530 plugin supported most file formats / media types.
1531 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
1532 result
</a
> can still be seen on the Debian wiki, even though it have
1533 not been updated for a while. But browser plugins are less relevant
1534 these days, so I thought it was time to look at standalone
1537 <p
>A few days ago I was tired of VLC not being listed as a viable
1538 player when I wanted to play videos from the Norwegian National
1539 Broadcasting Company, and decided to investigate why. The cause is a
1540 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
1541 desktop file
</a
>. In the process I wrote a script to compare the set
1542 of MIME types announced in the desktop file and the browser plugin,
1543 only to discover that there is quite a large difference between the
1544 two for VLC. This discovery made me dig up the script I used to
1545 compare browser plugins, and adjust it to compare desktop files
1546 instead, to try to figure out which multimedia player in Debian
1547 support most file formats.
</p
>
1549 <p
>The result can be seen on the Debian Wiki, as
1550 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
1551 table listing all MIME types supported by one of the packages included
1552 in the table
</a
>, with the package supporting most MIME types being
1553 listed first in the table.
</p
>
1555 </p
>The best multimedia player in Debian? It is totem, followed by
1556 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
1557 kmplayer. Time for the other players to update their announced MIME
1563 <title>The Pyra - handheld computer with Debian preinstalled
</title>
1564 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
1565 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
1566 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
1567 <description>A friend of mine made me aware of
1568 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
1569 handheld computer which will be delivered with Debian preinstalled. I
1570 would love to get one of those for my birthday. :)
</p
>
1572 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
1573 plugs and many others connectors, and include a full keyboard and a
5"
1574 LCD touch screen. The
6000mAh battery is claimed to provide a whole
1575 day of battery life time, but I have not seen any independent tests
1576 confirming this. The vendor is still collecting preorders, and the
1577 last I heard last night was that
22 more orders were needed before
1578 production started.
</p
>
1580 <p
>As far as I know, this is the first handheld preinstalled with
1581 Debian. Please let me know if you know of any others. Is it the
1582 first computer being sold with Debian preinstalled?
</p
>
1587 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
1588 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
1589 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
1590 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
1591 <description><p
>During this weekends
1592 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
1593 squashing party and developer gathering
</a
>, we decided to do our part
1594 to make sure there are good books about Debian available in Norwegian
1595 Bokmål, and got in touch with the people behind the
1596 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
1597 project
</a
> to get started. If you want to help out, please start
1599 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
1600 hosted weblate project page
</a
>, and get in touch using
1601 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
1602 translators mailing list
</a
>. Please also check out
1603 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
1604 contributors
</a
>.
</p
>
1606 <p
>The book is already available on paper in English, French and
1607 Japanese, and our goal is to get it available on paper in Norwegian
1608 Bokmål too. In addition to the paper edition, there are also EPUB and
1609 Mobi versions available. And there are incomplete translations
1610 available for many more languages.
</p
>
1615 <title>One in two hundred Debian users using ZFS on Linux?
</title>
1616 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
1617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
1618 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
1619 <description><p
>Just for fun I had a look at the popcon number of ZFS related
1620 packages in Debian, and was quite surprised with what I found. I use
1621 ZFS myself at home, but did not really expect many others to do so.
1622 But I might be wrong.
</p
>
1624 <p
>According to
1625 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
1626 results for spl-linux
</a
>, there are
1019 Debian installations, or
1627 0.53% of the population, with the package installed. As far as I know
1628 the only use of the spl-linux package is as a support library for ZFS
1629 on Linux, so I use it here as proxy for measuring the number of ZFS
1630 installation on Linux in Debian. In the kFreeBSD variant of Debian
1631 the ZFS feature is already available, and there
1632 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
1633 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
1634 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
1636 <p
>But even though the Debian project leader Lucas Nussbaum
1637 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
1638 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
1639 cleared, the package is still not in Debian. The package is again in
1640 the NEW queue. Several uploads have been rejected so far because the
1641 debian/copyright file was incomplete or wrong, but there is no reason
1642 to give up. The current status can be seen on
1643 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
1644 team status page
</a
>, and
1645 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
1646 source code
</a
> is available on Alioth.
</p
>
1648 <p
>As I want ZFS to be included in next version of Debian to make sure
1649 my home server can function in the future using only official Debian
1650 packages, and the current blocker is to get the debian/copyright file
1651 accepted by the FTP masters in Debian, I decided a while back to try
1652 to help out the team. This was the background for my blog post about
1653 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
1654 updating and checking debian/copyright semi-automatically
</a
>, and I
1655 used the techniques I explored there to try to find any errors in the
1656 copyright file. It is not very easy to check every one of the around
1657 2000 files in the source package, but I hope we this time got it
1658 right. If you want to help out, check out the git source and try to
1659 find missing entries in the debian/copyright file.
</p
>
1664 <title>Full battery stats collector is now available in Debian
</title>
1665 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
1666 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
1667 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
1668 <description><p
>Since this morning, the battery-stats package in Debian include an
1669 extended collector that will collect the complete battery history for
1670 later processing and graphing. The original collector store the
1671 battery level as percentage of last full level, while the new
1672 collector also record battery vendor, model, serial number, design
1673 full level, last full level and current battery level. This make it
1674 possible to predict the lifetime of the battery as well as visualise
1675 the energy flow when the battery is charging or discharging.
</p
>
1677 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
1678 in the version
0.5.1 package in unstable. Get the new battery level graph
1679 and lifetime prediction by running:
1681 <p
><pre
>
1682 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
1683 </pre
></p
>
1685 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
1687 <p
>The flow in/out of the battery can be seen by running (no menu
1688 entry yet):
</p
>
1690 <p
><pre
>
1691 /usr/share/battery-stats/battery-stats-graph-flow
1692 </pre
></p
>
1694 <p
>I
'm not quite happy with the way the data is visualised, at least
1695 when there are few data points. The graphs look a bit better with a
1696 few years of data.
</p
>
1698 <p
>A while back one important feature I use in the battery stats
1699 collector broke in Debian. The scripts in
1700 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
1701 suspect it happened when Jessie started using systemd, but I do not
1702 know. The issue is reported as
1703 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
1704 pm-utils. I managed to work around it by adding an udev rule to call
1705 the collector script every time the power connector is connected and
1706 disconnected. With this fix in place it was finally time to make a
1707 new release of the package, and get it into Debian.
</p
>
1709 <p
>If you are interested in how your laptop battery is doing, please
1711 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
1712 in Debian unstable, or rebuild it on Jessie to get it working on
1713 Debian stable. :) The upstream source is available from
1714 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1715 As always, patches are very welcome.
</p
>
1720 <title>Making battery measurements a little easier in Debian
</title>
1721 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
1722 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
1723 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
1724 <description><p
>Back in September, I blogged about
1725 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
1726 system I wrote to collect statistics about my laptop battery
</a
>, and
1727 how it showed the decay and death of this battery (now replaced). I
1728 created a simple deb package to handle the collection and graphing,
1729 but did not want to upload it to Debian as there were already
1730 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
1731 package in Debian
</a
> that should do the same thing, and I did not see
1732 a point of uploading a competing package when battery-stats could be
1733 fixed instead. I reported a few bugs about its non-function, and
1734 hoped someone would step in and fix it. But no-one did.
</p
>
1736 <p
>I got tired of waiting a few days ago, and took matters in my own
1737 hands. The end result is that I am now the new upstream developer of
1738 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
1739 battery-stats in Debian, and the package in Debian unstable is finally
1740 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
1741 information provided by the Linux kernel. If you install the
1742 battery-stats package from unstable now, you will be able to get a
1743 graph of the current battery fill level, to get some idea about the
1744 status of the battery. The source package build and work just fine in
1745 Debian testing and stable (and probably oldstable too, but I have not
1746 tested). The default graph you get for that system look like this:
</p
>
1748 <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
>
1750 <p
>My plans for the future is to merge my old scripts into the
1751 battery-stats package, as my old scripts collected a lot more details
1752 about the battery. The scripts are merged into the upstream
1753 battery-stats git repository already, but I am not convinced they work
1754 yet, as I changed a lot of paths along the way. Will have to test a
1755 bit more before I make a new release.
</p
>
1757 <p
>I will also consider changing the file format slightly, as I
1758 suspect the way I combine several values into one field might make it
1759 impossible to know the type of the value when using it for processing
1760 and graphing.
</p
>
1762 <p
>If you would like I would like to keep an close eye on your laptop
1763 battery, check out the battery-stats package in
1764 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
1766 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
1767 I would love some help to improve the system further.
</p
>
1772 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
1773 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
1774 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
1775 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
1776 <description><p
>Making packages for Debian requires quite a lot of attention to
1777 details. And one of the details is the content of the
1778 debian/copyright file, which should list all relevant licenses used by
1779 the code in the package in question, preferably in
1780 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
1781 readable DEP5 format
</a
>.
</p
>
1783 <p
>For large packages with lots of contributors it is hard to write
1784 and update this file manually, and if you get some detail wrong, the
1785 package is normally rejected by the ftpmasters. So getting it right
1786 the first time around get the package into Debian faster, and save
1787 both you and the ftpmasters some work.. Today, while trying to figure
1788 out what was wrong with
1789 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
1790 zfsonlinux copyright file
</a
>, I decided to spend some time on
1791 figuring out the options for doing this job automatically, or at least
1792 semi-automatically.
</p
>
1794 <p
>Lucikly, there are at least two tools available for generating the
1795 file based on the code in the source package,
1796 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
1797 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
1798 not sure which one of them came first, but both seem to be able to
1799 create a sensible draft file. As far as I can tell, none of them can
1800 be trusted to get the result just right, so the content need to be
1801 polished a bit before the file is OK to upload. I found the debmake
1803 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
1804 blog posts from
2014</a
>.
1806 <p
>To generate using debmake, use the -cc option:
1808 <p
><pre
>
1809 debmake -cc
> debian/copyright
1810 </pre
></p
>
1812 <p
>Note there are some problems with python and non-ASCII names, so
1813 this might not be the best option.
</p
>
1815 <p
>The cme option is based on a config parsing library, and I found
1817 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
1818 blog post from
2015</a
>. To generate using cme, use the
'update
1819 dpkg-copyright
' option:
1821 <p
><pre
>
1822 cme update dpkg-copyright
1823 </pre
></p
>
1825 <p
>This will create or update debian/copyright. The cme tool seem to
1826 handle UTF-
8 names better than debmake.
</p
>
1828 <p
>When the copyright file is created, I would also like some help to
1829 check if the file is correct. For this I found two good options,
1830 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
1831 to focus on license types and file matching, and is able to detect
1832 ineffective blocks in the copyright file. The latter reports missing
1833 copyright holders and years, but was confused by inconsistent license
1834 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
1835 fix all issues reported by them before uploading. But I do not know
1836 if the tools and the ftpmasters agree on what is important to fix in a
1837 copyright file, so the package might still be rejected.
</p
>
1839 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
1840 will read through the source and try to find all copyright statements.
1841 It is not comparing the result to the content of debian/copyright, but
1842 can be useful when verifying the content of the copyright file.
</p
>
1844 <p
>Are you aware of better tools in Debian to create and update
1845 debian/copyright file. Please let me know, or blog about it on
1846 planet.debian.org.
</p
>
1848 <p
>As usual, if you use Bitcoin and want to show your support of my
1849 activities, please send Bitcoin donations to my address
1850 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1852 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
1853 on how to use licensecheck and cdbs to create a draft copyright file
1855 <p
><pre
>
1856 licensecheck --copyright -r `find * -type f` | \
1857 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
1858 </pre
></p
>
1860 <p
>He mentioned that he normally check the generated file into the
1861 version control system to make it easier to discover license and
1862 copyright changes in the upstream source. I will try to do the same
1863 with my packages in the future.
</p
>
1865 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
1866 against using -quiet for new users, so I removed it from the proposed
1867 command line.
</p
>
1872 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
1873 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
1874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
1875 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
1876 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
1877 is taking shape in Debian, and one provided feature is a very
1878 convenient way to tell you which package to install to make a given
1879 firmware file available when the kernel is looking for it. This can
1880 be done using apt-file too, but that is for someone else to blog
1883 <p
>Here is a small recipe to find the package with a given firmware
1884 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
1885 picked from the set of firmware announced using appstream in Debian
1886 unstable. In general you would be looking for the firmware requested
1887 by the kernel during kernel module loading. To find the package
1888 providing the example file, do like this:
</p
>
1890 <blockquote
><pre
>
1891 % apt install appstream
1895 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
1896 awk
'/Package:/ {print $
2}
'
1899 </pre
></blockquote
>
1901 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
1902 appstream wiki
</a
> page to learn how to embed the package metadata in
1903 a way appstream can use.
</p
>
1905 <p
>This same approach can be used to find any package supporting a
1906 given MIME type. This is very useful when you get a file you do not
1907 know how to handle. First find the mime type using
<tt
>file
1908 --mime-type
</tt
>, and next look up the package providing support for
1909 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
1910 and you can find all packages handling this type like this:
</p
>
1912 <blockquote
><pre
>
1913 % apt install appstream
1917 % appstreamcli what-provides mimetype image/svg+xml | \
1918 awk
'/Package:/ {print $
2}
'
1940 </pre
></blockquote
>
1942 <p
>I believe the MIME types are fetched from the desktop file for
1943 packages providing appstream metadata.
</p
>
1948 <title>Creepy, visualise geotagged social media information - nice free software
</title>
1949 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
1950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
1951 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
1952 <description><p
>Most people seem not to realise that every time they walk around
1953 with the computerised radio beacon known as a mobile phone their
1954 position is tracked by the phone company and often stored for a long
1955 time (like every time a SMS is received or sent). And if their
1956 computerised radio beacon is capable of running programs (often called
1957 mobile apps) downloaded from the Internet, these programs are often
1958 also capable of tracking their location (if the app requested access
1959 during installation). And when these programs send out information to
1960 central collection points, the location is often included, unless
1961 extra care is taken to not send the location. The provided
1962 information is used by several entities, for good and bad (what is
1963 good and bad, depend on your point of view). What is certain, is that
1964 the private sphere and the right to free movement is challenged and
1965 perhaps even eradicated for those announcing their location this way,
1966 when they share their whereabouts with private and public
1969 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
1971 <p
>The phone company logs provide a register of locations to check out
1972 when one want to figure out what the tracked person was doing. It is
1973 unavailable for most of us, but provided to selected government
1974 officials, company staff, those illegally buying information from
1975 unfaithful servants and crackers stealing the information. But the
1976 public information can be collected and analysed, and a free software
1977 tool to do so is called
1978 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
1979 discovered it when I read
1980 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
1981 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
1982 November
2014, and decided to check if it was available in Debian.
1983 The python program was in Debian, but
1984 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
1985 Debian
</a
> was completely broken and practically unmaintained. I
1986 uploaded a new version which did not work quite right, but did not
1987 have time to fix it then. This Christmas I decided to finally try to
1988 get Creepy operational in Debian. Now a fixed version is available in
1989 Debian unstable and testing, and almost all Debian specific patches
1991 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
1993 <p
>The Creepy program visualises geolocation information fetched from
1994 Twitter, Instagram, Flickr and Google+, and allow one to get a
1995 complete picture of every social media message posted recently in a
1996 given area, or track the movement of a given individual across all
1997 these services. Earlier it was possible to use the search API of at
1998 least some of these services without identifying oneself, but these
1999 days it is impossible. This mean that to use Creepy, you need to
2000 configure it to log in as yourself on these services, and provide
2001 information to them about your search interests. This should be taken
2002 into account when using Creepy, as it will also share information
2003 about yourself with the services.
</p
>
2005 <p
>The picture above show the twitter messages sent from (or at least
2006 geotagged with a position from) the city centre of Oslo, the capital
2007 of Norway. One useful way to use Creepy is to first look at
2008 information tagged with an area of interest, and next look at all the
2009 information provided by one or more individuals who was in the area.
2010 I tested it by checking out which celebrity provide their location in
2011 twitter messages by checkout out who sent twitter messages near a
2012 Norwegian TV station, and next could track their position over time,
2013 making it possible to locate their home and work place, among other
2014 things. A similar technique have been
2015 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
2016 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
2017 tool to discover lying governments, and a useful tool to help people
2018 understand the value of the private information they provide to the
2021 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
2022 it depend on several python modules currently missing in Jessie (at
2023 least python-instagram, python-flickrapi and
2024 python-requests-toolbelt).
</p
>
2026 <p
>(I have uploaded
2027 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
2028 screenshots.debian.net
</a
> and licensed it under the same terms as the
2029 Creepy program in Debian.)
</p
>
2034 <title>Always download Debian packages using Tor - the simple recipe
</title>
2035 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
2036 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
2037 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
2038 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
2039 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
2040 that those listening on the Internet lines would have good reason to
2041 believe a computer have a given security hole
</a
> if it download a
2042 security fix from a Debian mirror. This is a good reason to always
2043 use encrypted connections to the Debian mirror, to make sure those
2044 listening do not know which IP address to attack. In August, Richard
2045 Hartmann observed that encryption was not enough, when it was possible
2046 to interfere download size to security patches or the fact that
2047 download took place shortly after a security fix was released, and
2048 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
2049 to always use Tor to download packages from the Debian mirror
</a
>. He
2050 was not the first to propose this, as the
2051 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
2052 package by Tim Retout already existed to make it easy to convince apt
2053 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
2054 aware of that package when I read the blog post from Richard.
</p
>
2056 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
2057 sysadmins, and he set up a Tor hidden service on one of the central
2058 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
2059 it possible to download packages directly between two tor nodes,
2060 making sure the network traffic always were encrypted.
</p
>
2062 <p
>Here is a short recipe for enabling this on your machine, by
2063 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
2064 urls with tor+http and tor+https, and using the hidden service instead
2065 of the official Debian mirror site. I recommend installing
2066 <tt
>etckeeper
</tt
> before you start to have a history of the changes
2067 done in /etc/.
</p
>
2069 <blockquote
><pre
>
2070 apt install apt-transport-tor
2071 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
2072 sed -i
's% http% tor+http%
' /etc/apt/sources.list
2073 </pre
></blockquote
>
2075 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
2076 the sed commands for these too. The sed command is assuming your are
2077 using the ftp.debian.org Debian mirror. Adjust the command (or just
2078 edit the file manually) to match your mirror.
</p
>
2080 <p
>This work in Debian Jessie and later. Note that tools like
2081 <tt
>apt-file
</tt
> only recently started using the apt transport
2082 system, and do not work with these tor+http URLs. For
2083 <tt
>apt-file
</tt
> you need the version currently in experimental,
2084 which need a recent apt version currently only in unstable. So if you
2085 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
2087 <p
>Another advantage from this change is that your machine will start
2088 using Tor regularly and at fairly random intervals (every time you
2089 update the package lists or upgrade or install a new package), thus
2090 masking other Tor traffic done from the same machine. Using Tor will
2091 become normal for the machine in question.
</p
>
2093 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
2094 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
2095 enabled. It would be great if it was the default on any Debian
2101 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
2102 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
2103 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
2104 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
2105 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
2106 call the car license plate numbers in those days. I would write the
2107 numbers down in my little book and compare notes with the other kids
2108 to see how many region codes we had seen and if we had seen some
2109 exotic or special region codes and numbers. It was a fun game to pass
2110 time, as we kids have plenty of it.
</p
>
2112 <p
>A few days I came across
2113 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
2114 project
</a
>, a free software project to automatically discover and
2115 report license plates in images and video streams, and provide the
2116 "car numbers
" in a machine readable format. I
've been looking for
2117 such system for a while now, because I believe it is a bad idea that the
2118 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
2119 number plate recognition
</a
> tool only is available in the hands of
2120 the powerful, and want it to be available also for the powerless to
2121 even the score when it comes to surveillance and sousveillance. I
2122 discovered the developer
2123 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
2124 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
2125 help him get it into shape to get the package uploaded into the Debian
2128 <p
>Today we finally managed to get the package into shape and uploaded
2129 it into Debian, where it currently
2130 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
2131 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
2133 <p
>I guess you are wondering why on earth such tool would be useful
2134 for the common folks, ie those not running a large government
2135 surveillance system? Well, I plan to put it in a computer on my bike
2136 and in my car, tracking the cars nearby and allowing me to be notified
2137 when number plates on my watch list are discovered. Another use case
2138 was suggested by a friend of mine, who wanted to set it up at his home
2139 to open the car port automatically when it discovered the plate on his
2140 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
2141 capable of placing his license plate number of a piece of cardboard to
2142 open his car port, men replied that it was always unlocked anyway. I
2143 guess for such use case it make sense. I am sure there are other use
2144 cases too, for those with imagination and a vision.
</p
>
2146 <p
>If you want to build your own version of the Debian package, check
2147 out the upstream git source and symlink ./distros/debian to ./debian/
2148 before running
"debuild
" to build the source. Or wait a bit until the
2149 package show up in unstable.
</p
>
2154 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
2155 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
2156 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
2157 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
2158 <description><p
>Around three years ago, I created
2159 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
2160 system
</a
> to get a more practical solution in Debian for handing
2161 hardware related packages. A GUI system in the isenkram package will
2162 present a pop-up dialog when some hardware dongle supported by
2163 relevant packages in Debian is inserted into the machine. The same
2164 lookup mechanism to detect packages is available as command line
2165 tools in the isenkram-cli package. In addition to mapping hardware,
2166 it will also map kernel firmware files to packages and make it easy to
2167 install needed firmware packages automatically. The key for this
2168 system to work is a good way to map hardware to packages, in other
2169 words, allow packages to announce what hardware they will work
2172 <p
>I started by providing data files in the isenkram source, and
2173 adding code to download the latest version of these data files at run
2174 time, to ensure every user had the most up to date mapping available.
2175 I also added support for storing the mapping in the Packages file in
2176 the apt repositories, but did not push this approach because while I
2177 was trying to figure out how to best store hardware/package mappings,
2178 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
2179 appstream system
</a
> was announced. I got in touch and suggested to
2180 add the hardware mapping into that data set to be able to use
2181 appstream as a data source, and this was accepted at least for the
2182 Debian version of appstream.
</p
>
2184 <p
>A few days ago using appstream in Debian for this became possible,
2185 and today I uploaded a new version
0.20 of isenkram adding support for
2186 appstream as a data source for mapping hardware to packages. The only
2187 package so far using appstream to announce its hardware support is my
2188 pymissile package. I got help from Matthias Klumpp with figuring out
2189 how do add the required
2190 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
2191 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
2192 this content:
</p
>
2194 <blockquote
><pre
>
2195 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
2196 &lt;component
&gt;
2197 &lt;id
&gt;pymissile
&lt;/id
&gt;
2198 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
2199 &lt;name
&gt;pymissile
&lt;/name
&gt;
2200 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
2201 &lt;description
&gt;
2203 Pymissile provides a curses interface to control an original
2204 Marks and Spencer / Striker USB Missile Launcher, as well as a
2205 motion control script to allow a webcamera to control the
2208 &lt;/description
&gt;
2209 &lt;provides
&gt;
2210 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
2211 &lt;/provides
&gt;
2212 &lt;/component
&gt;
2213 </pre
></blockquote
>
2215 <p
>The key for isenkram is the component/provides/modalias value,
2216 which is a glob style match rule for hardware specific strings
2217 (modalias strings) provided by the Linux kernel. In this case, it
2218 will map to all USB devices with vendor code
1130 and product code
2221 <p
>Note, it is important that the license of all the metadata files
2222 are compatible to have permissions to aggregate them into archive wide
2223 appstream files. Matthias suggested to use MIT or BSD licenses for
2224 these files. A challenge is figuring out a good id for the data, as
2225 it is supposed to be globally unique and shared across distributions
2226 (in other words, best to coordinate with upstream what to use). But
2227 it can be changed later or, so we went with the package name as
2228 upstream for this project is dormant.
</p
>
2230 <p
>To get the metadata file installed in the correct location for the
2231 mirror update scripts to pick it up and include its content the
2232 appstream data source, the file must be installed in the binary
2233 package under /usr/share/appdata/. I did this by adding the following
2234 line to debian/pymissile.install:
</p
>
2236 <blockquote
><pre
>
2237 debian/pymissile.metainfo.xml usr/share/appdata
2238 </pre
></blockquote
>
2240 <p
>With that in place, the command line tool isenkram-lookup will list
2241 all packages useful on the current computer automatically, and the GUI
2242 pop-up handler will propose to install the package not already
2243 installed if a hardware dongle is inserted into the machine in
2246 <p
>Details of the modalias field in appstream is available from the
2247 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
2249 <p
>To locate the modalias values of all hardware present in a machine,
2250 try running this command on the command line:
</p
>
2252 <blockquote
><pre
>
2253 cat $(find /sys/devices/|grep modalias)
2254 </pre
></blockquote
>
2256 <p
>To learn more about the isenkram system, please check out
2257 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
2258 blog posts tagged isenkram
</a
>.
</p
>
2263 <title>The GNU General Public License is not magic pixie dust
</title>
2264 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
2265 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
2266 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
2267 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
2268 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
2269 GPL is not magic pixie dust
</a
>" explain the importance of making sure
2270 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
2271 I quote the blog post from Paul in full here with his permission:
<p
>
2275 <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
>
2278 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
2280 The first step is to choose a
2281 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
2284 The next step is, when someone fails to follow that copyleft license,
2285 <b
>it must be enforced
</b
><br/
>
2287 and its a simple fact of our modern society that such type of
2290 is incredibly expensive to do and incredibly difficult to do.
2293 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
2294 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
2295 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
2296 0x57</a
></small
></p
>
2298 <p
>As the Debian Website
2299 <a href=
"https://bugs.debian.org/
794116">used
</a
>
2300 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
2301 imply, public domain and permissively licensed software can lead to
2302 the production of more proprietary software as people discover useful
2303 software, extend it and or incorporate it into their hardware or
2304 software products. Copyleft licenses such as the GNU GPL were created
2305 to close off this avenue to the production of proprietary software but
2306 such licenses are not enough. With the ongoing adoption of Free
2307 Software by individuals and groups, inevitably the community
's
2308 expectations of license compliance are violated, usually out of
2309 ignorance of the way Free Software works, but not always. As Karen
2310 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
2311 Freedom
">FaiF
</a
>
2312 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
2313 copyleft is nothing if no-one is willing and able to stand up in court
2314 to protect it. The reality of today
's world is that legal
2315 representation is expensive, difficult and time consuming. With
2316 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
2317 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
2318 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
2319 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
2320 of the Linux project, Debian and other groups against GPL violations.
2321 In March the SFC supported a
2322 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
2323 by Christoph Hellwig
</a
> against VMware for refusing to
2324 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
2325 with the GPL
</a
> in relation to their use of parts of the Linux
2326 kernel. Since then two of their sponsors pulled corporate funding and
2328 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
2329 or cancelled their talks
</a
>. As a result they have decided to rely
2330 less on corporate funding and more on the broad community of
2331 individuals who support Free Software and copyleft. So the SFC has
2332 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
2333 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
2334 a community of folks who stand up for copyleft and the GPL by
2335 supporting their work on promoting and supporting copyleft and Free
2338 <p
>If you support Free Software,
2339 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
2340 what the SFC do, agree with their
2341 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
2342 principles
</a
>, are happy about their
2343 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
2344 work on a project that is an SFC
2345 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
2346 just want to stand up for copyleft, please join
2347 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
2348 Allan Webber
</a
>,
2349 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
2351 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
2352 Bacon
</a
>, myself and
2353 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
2355 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
2356 next week your donation will be
2357 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
2358 by an anonymous donor. Please also consider asking your employer to
2359 match your donation or become a sponsor of SFC. Don
't forget to
2360 spread the word about your support for SFC via email, your blog and or
2361 social media accounts.
</p
>
2365 <p
>I agree with Paul on this topic and just signed up as a Supporter
2366 of Software Freedom Conservancy myself. Perhaps you should be a
2367 supporter too?
</p
>
2372 <title>PGP key transition statement for key EE4E02F9
</title>
2373 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
2374 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
2375 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
2376 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
2377 set it up properly. I wanted to generate it offline and have it
2378 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
2379 smart card
</a
> for daily use, and learning how to do it and finding
2380 time to sit down with an offline machine almost took forever. But
2381 finally I
've been able to complete the process, and have now moved
2382 from my old GPG key to a new GPG key. See
2383 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
2384 full transition statement, signed with both my old and new key
</a
> for
2385 the details. This is my new key:
</p
>
2388 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
2389 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
2390 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
2391 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
2392 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
2393 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
2394 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
2397 <p
>The key can be downloaded from the OpenPGP key servers, signed by
2398 my old key.
</p
>
2400 <p
>If you signed my old key
2401 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
2402 I
'd very much appreciate a signature on my new key, details and
2403 instructions in the transition statement. I m happy to reciprocate if
2404 you have a similarly signed transition statement to present.
</p
>
2409 <title>The life and death of a laptop battery
</title>
2410 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
2411 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
2412 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
2413 <description><p
>When I get a new laptop, the battery life time at the start is OK.
2414 But this do not last. The last few laptops gave me a feeling that
2415 within a year, the life time is just a fraction of what it used to be,
2416 and it slowly become painful to use the laptop without power connected
2417 all the time. Because of this, when I got a new Thinkpad X230 laptop
2418 about two years ago, I decided to monitor its battery state to have
2419 more hard facts when the battery started to fail.
</p
>
2421 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
2423 <p
>First I tried to find a sensible Debian package to record the
2424 battery status, assuming that this must be a problem already handled
2425 by someone else. I found
2426 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
2427 which collects statistics from the battery, but it was completely
2428 broken. I sent a few suggestions to the maintainer, but decided to
2429 write my own collector as a shell script while I waited for feedback
2431 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
2432 blog post about the battery development on a MacBook Air
</a
> I also
2434 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
2435 available in Debian.
</p
>
2437 <p
>I started my collector
2013-
07-
15, and it has been collecting
2438 battery stats ever since. Now my
2439 /var/log/hjemmenett-battery-status.log file contain around
115,
000
2440 measurements, from the time the battery was working great until now,
2441 when it is unable to charge above
7% of original capacity. My
2442 collector shell script is quite simple and look like this:
</p
>
2447 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
2449 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
2450 logfile=/var/log/hjemmenett-battery-status.log
2452 files=
"manufacturer model_name technology serial_number \
2453 energy_full energy_full_design energy_now cycle_count status
"
2455 if [ ! -e
"$logfile
" ] ; then
2457 printf
"timestamp,
"
2459 printf
"%s,
" $f
2462 )
> "$logfile
"
2466 # Print complete message in one echo call, to avoid race condition
2467 # when several log processes run in parallel.
2468 msg=$(printf
"%s,
" $(date +%s); \
2469 for f in $files; do \
2470 printf
"%s,
" $(cat $f); \
2472 echo
"$msg
"
2475 cd /sys/class/power_supply
2478 (cd $bat
&& log_battery
>> "$logfile
")
2482 <p
>The script is called when the power management system detect a
2483 change in the power status (power plug in or out), and when going into
2484 and out of hibernation and suspend. In addition, it collect a value
2485 every
10 minutes. This make it possible for me know when the battery
2486 is discharging, charging and how the maximum charge change over time.
2487 The code for the Debian package
2488 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
2489 available on github
</a
>.
</p
>
2491 <p
>The collected log file look like this:
</p
>
2494 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
2495 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
2497 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2498 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
2501 <p
>I wrote a small script to create a graph of the charge development
2502 over time. This graph depicted above show the slow death of my laptop
2505 <p
>But why is this happening? Why are my laptop batteries always
2506 dying in a year or two, while the batteries of space probes and
2507 satellites keep working year after year. If we are to believe
2508 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
2509 University
</a
>, the cause is me charging the battery whenever I have a
2510 chance, and the fix is to not charge the Lithium-ion batteries to
100%
2511 all the time, but to stay below
90% of full charge most of the time.
2512 I
've been told that the Tesla electric cars
2513 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
2514 the charge of their batteries to
80%
</a
>, with the option to charge to
2515 100% when preparing for a longer trip (not that I would want a car
2516 like Tesla where rights to privacy is abandoned, but that is another
2517 story), which I guess is the option we should have for laptops on
2518 Linux too.
</p
>
2520 <p
>Is there a good and generic way with Linux to tell the battery to
2521 stop charging at
80%, unless requested to charge to
100% once in
2522 preparation for a longer trip? I found
2523 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
2524 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
2525 80%
</a
>, but could not get it to work (kernel module refused to
2528 <p
>I wonder why the battery capacity was reported to be more than
100%
2529 at the start. I also wonder why the
"full capacity
" increases some
2530 times, and if it is possible to repeat the process to get the battery
2531 back to design capacity. And I wonder if the discharge and charge
2532 speed change over time, or if this stay the same. I did not yet try
2533 to write a tool to calculate the derivative values of the battery
2534 level, but suspect some interesting insights might be learned from
2537 <p
>Update
2015-
09-
24: I got a tip to install the packages
2538 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
2539 packages instead of the tp-smapi-dkms package I had tried to use
2540 initially, and use
'tlp setcharge
40 80' to change when charging start
2541 and stop. I
've done so now, but expect my existing battery is toast
2542 and need to be replaced. The proposal is unfortunately Thinkpad
2548 <title>New laptop - some more clues and ideas based on feedback
</title>
2549 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
2550 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
2551 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
2552 <description><p
>Several people contacted me after my previous blog post about my
2553 need for a new laptop, and provided very useful feedback. I wish to
2554 thank every one of these. Several pointed me to the possibility of
2555 fixing my X230, and I am already in the process of getting Lenovo to
2556 do so thanks to the on site, next day support contract covering the
2557 machine. But the battery is almost useless (I expect to replace it
2558 with a non-official battery) and I do not expect the machine to live
2559 for many more years, so it is time to plan its replacement. If I did
2560 not have a support contract, it was suggested to find replacement parts
2561 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
2562 might present a language barrier as I do not understand French.
</p
>
2564 <p
>One tip I got was to use the
2565 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
2566 compare laptop models. It seem to have more models available than
2567 prisjakt.no. Another tip I got from someone I know have similar
2568 keyboard preferences was that the HP EliteBook
840 keyboard is not
2569 very good, and this matches my experience with earlier EliteBook
2570 keyboards I tested. Because of this, I will not consider it any further.
2572 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
2573 newest Thinkpad X model. The keyboard reintroduces mouse buttons
2574 (which is missing from the X240), and is working fairly well with
2575 Debian Sid/Unstable according to
2576 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
2577 got on the keyboard quality are not consistent. Some say the keyboard
2578 is good, others say it is ok, while others say it is not very good.
2579 Those with experience from X41 and and X60 agree that the X250
2580 keyboard is not as good as those trusty old laptops, and suggest I
2581 keep and fix my X230 instead of upgrading, or get a used X230 to
2582 replace it. I
'm also told that the X250 lack leds for caps lock, disk
2583 activity and battery status, which is very convenient on my X230. I
'm
2584 also told that the CPU fan is running very often, making it a bit
2585 noisy. In any case, the X250 do not work out of the box with Debian
2586 Stable/Jessie, one of my requirements.
</p
>
2588 <p
>I have also gotten a few vendor proposals, one was
2589 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
2590 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
2591 The latter look very attractive to me.
</p
>
2593 <p
>Again, thank you all for the very useful feedback. It help a lot
2594 as I keep looking for a replacement.
</p
>
2596 <p
>Update
2015-
07-
06: I was recommended to check out the
2597 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
2599 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
2600 thinkpad X models
</a
>, and provide one year warranty.
</p
>
2605 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
2606 <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>
2607 <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>
2608 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
2609 <description><p
>My primary work horse laptop is failing, and will need a
2610 replacement soon. The left
5 cm of the screen on my Thinkpad X230
2611 started flickering yesterday, and I suspect the cause is a broken
2612 cable, as changing the angle of the screen some times get rid of the
2613 flickering.
</p
>
2615 <p
>My requirements have not really changed since I bought it, and is
2617 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
2618 described them in
2013</a
>. The last time I bought a laptop, I had
2620 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
2621 where I could select at least a few of the requirements (mouse pin,
2622 wifi, weight) and go through the rest manually. Three button mouse
2623 and a good keyboard is not available as an option, and all the three
2624 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
2625 G2) lack three mouse buttons). It is also unclear to me how good the
2626 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
2627 the keyboard, even if the quality and robustness in the X series have
2628 deteriorated since X41.
</p
>
2630 <p
>I wonder how I can find a sensible laptop when none of the options
2631 seem sensible to me? Are there better services around to search the
2632 set of available laptops for features? Please send me an email if you
2633 have suggestions.
</p
>
2635 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
2636 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
2637 of endorsed hardware
</a
>, which is useful background information.
</p
>
2642 <title>How to stay with sysvinit in Debian Jessie
</title>
2643 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
2644 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
2645 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
2646 <description><p
>By now, it is well known that Debian Jessie will not be using
2647 sysvinit as its boot system by default. But how can one keep using
2648 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
2650 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
2651 Schubert
</a
> and
2652 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
2655 <p
>If you already are using Wheezy and want to upgrade to Jessie and
2656 keep sysvinit as your boot system, create a file
2657 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
2658 you upgrade:
</p
>
2660 <p
><blockquote
><pre
>
2661 Package: systemd-sysv
2662 Pin: release o=Debian
2664 </pre
></blockquote
><p
>
2666 <p
>This file content will tell apt and aptitude to not consider
2667 installing systemd-sysv as part of any installation and upgrade
2668 solution when resolving dependencies, and thus tell it to avoid
2669 systemd as a default boot system. The end result should be that the
2670 upgraded system keep using sysvinit.
</p
>
2672 <p
>If you are installing Jessie for the first time, there is no way to
2673 get sysvinit installed by default (debootstrap used by
2674 debian-installer have no option for this), but one can tell the
2675 installer to switch to sysvinit before the first boot. Either by
2676 using a kernel argument to the installer, or by adding a line to the
2677 preseed file used. First, the kernel command line argument:
2679 <p
><blockquote
><pre
>
2680 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
2681 </pre
></blockquote
><p
>
2683 <p
>Next, the line to use in a preseed file:
</p
>
2685 <p
><blockquote
><pre
>
2686 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
2687 </pre
></blockquote
><p
>
2689 <p
>One can of course also do this after the first boot by installing
2690 the sysvinit-core package.
</p
>
2692 <p
>I recommend only using sysvinit if you really need it, as the
2693 sysvinit boot sequence in Debian have several hardware specific bugs
2694 on Linux caused by the fact that it is unpredictable when hardware
2695 devices show up during boot. But on the other hand, the new default
2696 boot system still have a few rough edges I hope will be fixed before
2697 Jessie is released.
</p
>
2699 <p
>Update
2014-
11-
26: Inspired by
2700 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
2701 blog post by Torsten Glaser
</a
>, added --purge to the preseed
2707 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
2708 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
2709 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
2710 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
2711 <description><p
>The right to communicate with your friends and family in private,
2712 without anyone snooping, is a right every citicen have in a liberal
2713 democracy. But this right is under serious attack these days.
</p
>
2715 <p
>A while back it occurred to me that one way to make the dragnet
2716 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
2717 the whisleblower Snowden) more expensive for Internet email,
2718 is to deliver all email using SMTP via Tor. Such SMTP option would be
2719 a nice addition to the FreedomBox project if we could send email
2720 between FreedomBox machines without leaking metadata about the emails
2721 to the people peeking on the wire. I
2722 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
2723 this on the FreedomBox project mailing list in October
</a
> and got a
2724 lot of useful feedback and suggestions. It also became obvious to me
2725 that this was not a novel idea, as the same idea was tested and
2726 documented by Johannes Berg as early as
2006, and both
2727 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
2728 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
2729 propose a similar method / protocol to pass emails between users.
</p
>
2731 <p
>To implement such system one need to set up a Tor hidden service
2732 providing the SMTP protocol on port
25, and use email addresses
2733 looking like username@hidden-service-name.onion. With such addresses
2734 the connections to port
25 on hidden-service-name.onion using Tor will
2735 go to the correct SMTP server. To do this, one need to configure the
2736 Tor daemon to provide the hidden service and the mail server to accept
2737 emails for this .onion domain. To learn more about Exim configuration
2738 in Debian and test the design provided by Johannes Berg in his FAQ, I
2739 set out yesterday to create a Debian package for making it trivial to
2740 set up such SMTP over Tor service based on Debian. Getting it to work
2741 were fairly easy, and
2742 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
2743 source code for the Debian package
</a
> is available from github. I
2744 plan to move it into Debian if further testing prove this to be a
2745 useful approach.
</p
>
2747 <p
>If you want to test this, set up a blank Debian machine without any
2748 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
2749 get rid of exim4). Install tor, clone the git repository mentioned
2750 above, build the deb and install it on the machine. Next, run
2751 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
2752 the instructions to get the service up and running. Restart tor and
2753 exim when it is done, and test mail delivery using swaks like
2756 <p
><blockquote
><pre
>
2757 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
2758 --to fbx@dutlqrrmjhtfa3vp.onion
2759 </pre
></blockquote
></p
>
2761 <p
>This will test the SMTP delivery using tor. Replace the email
2762 address with your own address to test your server. :)
</p
>
2764 <p
>The setup procedure is still to complex, and I hope it can be made
2765 easier and more automatic. Especially the tor setup need more work.
2766 Also, the package include a tor-smtp tool written in C, but its task
2767 should probably be rewritten in some script language to make the deb
2768 architecture independent. It would probably also make the code easier
2769 to review. The tor-smtp tool currently need to listen on a socket for
2770 exim to talk to it and is started using xinetd. It would be better if
2771 no daemon and no socket is needed. I suspect it is possible to get
2772 exim to run a command line tool for delivery instead of talking to a
2773 socket, and hope to figure out how in a future version of this
2776 <p
>Until I wipe my test machine, I can be reached using the
2777 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
2778 SMTorP. :)
</p
>
2783 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
2784 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
2785 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
2786 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
2787 <description><p
>If you ever had to moderate a mailman list, like the ones on
2788 alioth.debian.org, you know the web interface is fairly slow to
2789 operate. First you visit one web page, enter the moderation password
2790 and get a new page shown with a list of all the messages to moderate
2791 and various options for each email address. This take a while for
2792 every list you moderate, and you need to do it regularly to do a good
2793 job as a list moderator. But there is a quick alternative,
2794 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
2795 listadmin program
</a
>. It allow you to check lists for new messages
2796 to moderate in a fraction of a second. Here is a test run on two
2797 lists I recently took over:
</p
>
2799 <p
><blockquote
><pre
>
2800 % time listadmin xiph
2801 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
2802 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
2808 </pre
></blockquote
></p
>
2810 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
2811 there are no message in the moderation queue. Every morning I
2812 currently moderate
68 mailman lists, and it normally take around two
2813 minutes. When I took over the two pkg-xiph lists above a few days
2814 ago, there were
400 emails waiting in the moderator queue. It took me
2815 less than
15 minutes to process them all using the listadmin
2818 <p
>If you install
2819 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
2820 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
2821 with content like this, the moderation task is a breeze:
</p
>
2823 <p
><blockquote
><pre
>
2824 username username@example.org
2827 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
2830 adminurl https://{domain}/mailman/admindb/{list}
2831 mailman-list@lists.example.com
2834 other-list@otherserver.example.org
2835 </pre
></blockquote
></p
>
2837 <p
>There are other options to set as well. Check the manual page to
2838 learn the details.
</p
>
2840 <p
>If you are forced to moderate lists on a mailman installation where
2841 the SSL certificate is self signed or not properly signed by a
2842 generally accepted signing authority, you can set a environment
2843 variable when calling listadmin to disable SSL verification:
</p
>
2845 <p
><blockquote
><pre
>
2846 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
2847 </pre
></blockquote
></p
>
2849 <p
>If you want to moderate a subset of the lists you take care of, you
2850 can provide an argument to the listadmin script like I do in the
2851 initial screen dump (the xiph argument). Using an argument, only
2852 lists matching the argument string will be processed. This make it
2853 quick to accept messages if you notice the moderation request in your
2856 <p
>Without the listadmin program, I would never be the moderator of
68
2857 mailing lists, as I simply do not have time to spend on that if the
2858 process was any slower. The listadmin program have saved me hours of
2859 time I could spend elsewhere over the years. It truly is nice free
2862 <p
>As usual, if you use Bitcoin and want to show your support of my
2863 activities, please send Bitcoin donations to my address
2864 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2866 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
2867 configuration example. Also, I
've been told that the
2868 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
2874 <title>Debian Jessie, PXE and automatic firmware installation
</title>
2875 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
2876 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
2877 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
2878 <description><p
>When PXE installing laptops with Debian, I often run into the
2879 problem that the WiFi card require some firmware to work properly.
2880 And it has been a pain to fix this using preseeding in Debian.
2881 Normally something more is needed. But thanks to
2882 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
2883 package
</a
> and its recent tasksel extension, it has now become easy
2884 to do this using simple preseeding.
</p
>
2886 <p
>The isenkram-cli package provide tasksel tasks which will install
2887 firmware for the hardware found in the machine (actually, requested by
2888 the kernel modules for the hardware). (It can also install user space
2889 programs supporting the hardware detected, but that is not the focus
2890 of this story.)
</p
>
2892 <p
>To get this working in the default installation, two preeseding
2893 values are needed. First, the isenkram-cli package must be installed
2894 into the target chroot (aka the hard drive) before tasksel is executed
2895 in the pkgsel step of the debian-installer system. This is done by
2896 preseeding the base-installer/includes debconf value to include the
2897 isenkram-cli package. The package name is next passed to debootstrap
2898 for installation. With the isenkram-cli package in place, tasksel
2899 will automatically use the isenkram tasks to detect hardware specific
2900 packages for the machine being installed and install them, because
2901 isenkram-cli contain tasksel tasks.
</p
>
2903 <p
>Second, one need to enable the non-free APT repository, because
2904 most firmware unfortunately is non-free. This is done by preseeding
2905 the apt-mirror-setup step. This is unfortunate, but for a lot of
2906 hardware it is the only option in Debian.
</p
>
2908 <p
>The end result is two lines needed in your preseeding file to get
2909 firmware installed automatically by the installer:
</p
>
2911 <p
><blockquote
><pre
>
2912 base-installer base-installer/includes string isenkram-cli
2913 apt-mirror-setup apt-setup/non-free boolean true
2914 </pre
></blockquote
></p
>
2916 <p
>The current version of isenkram-cli in testing/jessie will install
2917 both firmware and user space packages when using this method. It also
2918 do not work well, so use version
0.15 or later. Installing both
2919 firmware and user space packages might give you a bit more than you
2920 want, so I decided to split the tasksel task in two, one for firmware
2921 and one for user space programs. The firmware task is enabled by
2922 default, while the one for user space programs is not. This split is
2923 implemented in the package currently in unstable.
</p
>
2925 <p
>If you decide to give this a go, please let me know (via email) how
2926 this recipe work for you. :)
</p
>
2928 <p
>So, I bet you are wondering, how can this work. First and
2929 foremost, it work because tasksel is modular, and driven by whatever
2930 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
2931 isenkram-cli package place two files for tasksel to find. First there
2932 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
2934 <p
><blockquote
><pre
>
2935 Task: isenkram-packages
2937 Description: Hardware specific packages (autodetected by isenkram)
2938 Based on the detected hardware various hardware specific packages are
2940 Test-new-install: show show
2942 Packages: for-current-hardware
2944 Task: isenkram-firmware
2946 Description: Hardware specific firmware packages (autodetected by isenkram)
2947 Based on the detected hardware various hardware specific firmware
2948 packages are proposed.
2949 Test-new-install: mark show
2951 Packages: for-current-hardware-firmware
2952 </pre
></blockquote
></p
>
2954 <p
>The key parts are Test-new-install which indicate how the task
2955 should be handled and the Packages line referencing to a script in
2956 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
2957 list of packages to install. The for-current-hardware-firmware script
2958 look like this to list relevant firmware for the machine:
2960 <p
><blockquote
><pre
>
2963 PATH=/usr/sbin:$PATH
2965 isenkram-autoinstall-firmware -l
2966 </pre
></blockquote
></p
>
2968 <p
>With those two pieces in place, the firmware is installed by
2969 tasksel during the normal d-i run. :)
</p
>
2971 <p
>If you want to test what tasksel will install when isenkram-cli is
2972 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
2973 --new-install
</tt
> to get the list of packages that tasksel would
2976 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
2977 pilots in testing this feature, as isenkram is used there now to
2978 install firmware, replacing the earlier scripts.
</p
>
2983 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
2984 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
2985 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
2986 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
2987 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
2988 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
2989 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
2990 on a screen normally showing the bread types and prizes:
</p
>
2992 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
2994 <p
>If it had booted as it was supposed to, I would never had known
2995 about this hidden Linux installation. It is interesting what
2996 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
3001 <title>New lsdvd release version
0.17 is ready
</title>
3002 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
3003 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
3004 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
3005 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
3006 got a new set of developers a few weeks ago, after the original
3007 developer decided to step down and pass the project to fresh blood.
3008 This project is now maintained by Petter Reinholdtsen and Steve
3011 <p
>I just wrapped up
3012 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
3013 new lsdvd release
</a
>, available in git or from
3014 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
3015 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
3020 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
3021 <li
>Check for garbage in the program chains, which indicate that a track is
3022 non-existant, to work around additional copy protection
</li
>
3023 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
3024 <li
>Fix pallete display of first entry
</li
>
3025 <li
>Fix include orders
</li
>
3026 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
3027 <li
>Fix the chapter count
</li
>
3028 <li
>Make sure the array size and the array limit used when initialising
3029 the palette size is the same.
</li
>
3030 <li
>Fix array printing.
</li
>
3031 <li
>Correct subsecond calculations.
</li
>
3032 <li
>Add sector information to the output format.
</li
>
3033 <li
>Clean up code to be closer to ANSI C and compile without warnings
3034 with more GCC compiler warnings.
</li
>
3038 <p
>This change bring together patches for lsdvd in use in various
3039 Linux and Unix distributions, as well as patches submitted to the
3040 project the last nine years. Please check it out. :)
</p
>
3045 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
3046 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
3047 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
3048 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
3049 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3050 project
</a
> provide a Linux solution for schools, including a
3051 powerful desktop with education software, a central server providing
3052 web pages, user database, user home directories, central login and PXE
3053 boot of both clients without disk and the installation to install Debian
3054 Edu on machines with disk (and a few other services perhaps to small
3055 to mention here). We in the Debian Edu team are currently working on
3056 the Jessie based version, trying to get everything in shape before the
3057 freeze, to avoid having to maintain our own package repository in the
3059 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
3060 status
</a
> can be seen on the Debian wiki, and there is still heaps of
3061 work left. Some fatal problems block testing, breaking the installer,
3062 but it is possible to work around these to get anyway. Here is a
3063 recipe on how to get the installation limping along.
</p
>
3065 <p
>First, download the test ISO via
3066 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
3067 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
3069 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
3070 The ISO build was broken on Tuesday, so we do not get a new ISO every
3071 12 hours or so, but thankfully the ISO we already got we are able to
3072 install with some tweaking.
</p
>
3074 <p
>When you get to the Debian Edu profile question, go to tty2
3075 (use Alt-Ctrl-F2), run
</p
>
3077 <p
><blockquote
><pre
>
3078 nano /usr/bin/edu-eatmydata-install
3079 </pre
></blockquote
></p
>
3081 <p
>and add
'exit
0' as the second line, disabling the eatmydata
3082 optimization. Return to the installation, select the profile you want
3083 and continue. Without this change, exim4-config will fail to install
3084 due to a known bug in eatmydata.
</p
>
3086 <p
>When you get the grub question at the end, answer /dev/sda (or if
3087 this do not work, figure out what your correct value would be. All my
3088 test machines need /dev/sda, so I have no advice if it do not fit
3089 your need.
</p
>
3091 <p
>If you installed a profile including a graphical desktop, log in as
3092 root after the initial boot from hard drive, and install the
3093 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
3094 or mate. If you want several desktop options, install more than one
3095 metapackage. Once this is done, reboot and you should have a working
3096 graphical login screen. This workaround should no longer be needed
3097 once the education-tasks package version
1.801 enter testing in two
3100 <p
>I believe the ISO build will start working on two days when the new
3101 tasksel package enter testing and Steve McIntyre get a chance to
3102 update the debian-cd git repository. The eatmydata, grub and desktop
3103 issues are already fixed in unstable and testing, and should show up
3104 on the ISO as soon as the ISO build start working again. Well the
3105 eatmydata optimization is really just disabled. The proper fix
3106 require an upload by the eatmydata maintainer applying the patch
3107 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
3108 The rest have proper fixes in unstable.
</p
>
3110 <p
>I hope this get you going with the installation testing, as we are
3111 quickly running out of time trying to get our Jessie based
3112 installation ready before the distribution freeze in a month.
</p
>
3117 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
3118 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
3119 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
3120 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
3121 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
3122 to handle my fairly large DVD collection. It is a nice command line
3123 tool to get details about a DVD, like title, tracks, track length,
3124 etc, in XML, Perl or human readable format. But lsdvd have not seen
3125 any new development since
2006 and had a few irritating bugs affecting
3126 its use with some DVDs. Upstream seemed to be dead, and in January I
3127 sent a small probe asking for a version control repository for the
3128 project, without any reply. But I use it regularly and would like to
3129 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
3130 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
3131 the project admin, and after getting a reply from him explaining that
3132 he was no longer interested in the project, I asked if I could take
3133 over. And yesterday, I became project admin.
</p
>
3135 <p
>I
've been in touch with a Gentoo developer and the Debian
3136 maintainer interested in joining forces to maintain the upstream
3137 project, and I hope we can get a new release out fairly quickly,
3138 collecting the patches spread around on the internet into on place.
3139 I
've added the relevant Debian patches to the freshly created git
3140 repository, and expect the Gentoo patches to make it too. If you got
3141 a DVD collection and care about command line tools, check out
3142 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
3143 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
3144 list
</a
>. :)
</p
>
3149 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
3150 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
3151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
3152 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
3153 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
3154 a lot quicker. When we install more than
2000 packages in
3155 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
3156 tasksel in the installer, unpacking the binary packages take forever.
3157 A part of the slow I/O issue was discussed in
3158 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
3159 much file system sync-ing done by dpkg, which is the package
3160 responsible for unpacking the binary packages. Other parts (like code
3161 executed by postinst scripts) might also sync to disk during
3162 installation. All this sync-ing to disk do not really make sense to
3163 me. If the machine crash half-way through, I start over, I do not try
3164 to salvage the half installed system. So the failure sync-ing is
3165 supposed to protect against, hardware or system crash, is not really
3166 relevant while the installer is running.
</p
>
3168 <p
>A few days ago, I thought of a way to get rid of all the file
3169 system sync()-ing in a fairly non-intrusive way, without the need to
3170 change the code in several packages. The idea is not new, but I have
3171 not heard anyone propose the approach using dpkg-divert before. It
3172 depend on the small and clever package
3173 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
3174 uses LD_PRELOAD to replace the system functions for syncing data to
3175 disk with functions doing nothing, thus allowing programs to live
3176 dangerous while speeding up disk I/O significantly. Instead of
3177 modifying the implementation of dpkg, apt and tasksel (which are the
3178 packages responsible for selecting, fetching and installing packages),
3179 it occurred to me that we could just divert the programs away, replace
3180 them with a simple shell wrapper calling
3181 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
3182 Two days ago I decided to test the idea, and wrapped up a simple
3183 implementation for the Debian Edu udeb.
</p
>
3185 <p
>The effect was stunning. In my first test it reduced the running
3186 time of the pkgsel step (installing tasks) from
64 to less than
44
3187 minutes (
20 minutes shaved off the installation) on an old Dell
3188 Latitude D505 machine. I am not quite sure what the optimised time
3189 would have been, as I messed up the testing a bit, causing the debconf
3190 priority to get low enough for two questions to pop up during
3191 installation. As soon as I saw the questions I moved the installation
3192 along, but do not know how long the question were holding up the
3193 installation. I did some more measurements using Debian Edu Jessie,
3194 and got these results. The time measured is the time stamp in
3195 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
3196 "pkgsel: finishing up
" lines, if you want to do the same measurement
3197 yourself. In Debian Edu, the tasksel dialog do not show up, and the
3198 timing thus do not depend on how quickly the user handle the tasksel
3201 <p
><table
>
3204 <th
>Machine/setup
</th
>
3205 <th
>Original tasksel
</th
>
3206 <th
>Optimised tasksel
</th
>
3207 <th
>Reduction
</th
>
3211 <td
>Latitude D505 Main+LTSP LXDE
</td
>
3212 <td
>64 min (
07:
46-
08:
50)
</td
>
3213 <td
><44 min (
11:
27-
12:
11)
</td
>
3214 <td
>>20 min
18%
</td
>
3218 <td
>Latitude D505 Roaming LXDE
</td
>
3219 <td
>57 min (
08:
48-
09:
45)
</td
>
3220 <td
>34 min (
07:
43-
08:
17)
</td
>
3221 <td
>23 min
40%
</td
>
3225 <td
>Latitude D505 Minimal
</td
>
3226 <td
>22 min (
10:
37-
10:
59)
</td
>
3227 <td
>11 min (
11:
16-
11:
27)
</td
>
3228 <td
>11 min
50%
</td
>
3232 <td
>Thinkpad X200 Minimal
</td
>
3233 <td
>6 min (
08:
19-
08:
25)
</td
>
3234 <td
>4 min (
08:
04-
08:
08)
</td
>
3235 <td
>2 min
33%
</td
>
3239 <td
>Thinkpad X200 Roaming KDE
</td
>
3240 <td
>19 min (
09:
21-
09:
40)
</td
>
3241 <td
>15 min (
10:
25-
10:
40)
</td
>
3242 <td
>4 min
21%
</td
>
3245 </table
></p
>
3247 <p
>The test is done using a netinst ISO on a USB stick, so some of the
3248 time is spent downloading packages. The connection to the Internet
3249 was
100Mbit/s during testing, so downloading should not be a
3250 significant factor in the measurement. Download typically took a few
3251 seconds to a few minutes, depending on the amount of packages being
3252 installed.
</p
>
3254 <p
>The speedup is implemented by using two hooks in
3255 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
3256 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
3257 finish-install.d hook to remove the divert at the end of the
3258 installation. I picked the pre-pkgsel.d hook instead of the
3259 post-base-installer.d hook because I test using an ISO without the
3260 eatmydata package included, and the post-base-installer.d hook in
3261 Debian Edu can only operate on packages included in the ISO. The
3262 negative effect of this is that I am unable to activate this
3263 optimization for the kernel installation step in d-i. If the code is
3264 moved to the post-base-installer.d hook, the speedup would be larger
3265 for the entire installation.
</p
>
3267 <p
>I
've implemented this in the
3268 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
3269 git repository, and plan to provide the optimization as part of the
3270 Debian Edu installation. If you want to test this yourself, you can
3271 create two files in the installer (or in an udeb). One shell script
3272 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
3274 <p
><blockquote
><pre
>
3277 . /usr/share/debconf/confmodule
3279 logger -t my-pkgsel
"info: $*
"
3282 logger -t my-pkgsel
"error: $*
"
3284 override_install() {
3285 apt-install eatmydata || true
3286 if [ -x /target/usr/bin/eatmydata ] ; then
3287 for bin in dpkg apt-get aptitude tasksel ; do
3289 # Test that the file exist and have not been diverted already.
3290 if [ -f /target$file ] ; then
3291 info
"diverting $file using eatmydata
"
3292 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
3293 > /target$file.edu
3294 chmod
755 /target$file.edu
3295 in-target dpkg-divert --package debian-edu-config \
3296 --rename --quiet --add $file
3297 ln -sf ./$bin.edu /target$file
3299 error
"unable to divert $file, as it is missing.
"
3303 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
3308 </pre
></blockquote
></p
>
3310 <p
>To clean up, another shell script should go into
3311 /usr/lib/finish-install.d/ with code like this:
3313 <p
><blockquote
><pre
>
3315 . /usr/share/debconf/confmodule
3317 logger -t my-finish-install
"error: $@
"
3319 remove_install_override() {
3320 for bin in dpkg apt-get aptitude tasksel ; do
3322 if [ -x /target$file.edu ] ; then
3324 in-target dpkg-divert --package debian-edu-config \
3325 --rename --quiet --remove $file
3328 error
"Missing divert for $file.
"
3331 sync # Flush file buffers before continuing
3334 remove_install_override
3335 </pre
></blockquote
></p
>
3337 <p
>In Debian Edu, I placed both code fragments in a separate script
3338 edu-eatmydata-install and call it from the pre-pkgsel.d and
3339 finish-install.d scripts.
</p
>
3341 <p
>By now you might ask if this change should get into the normal
3342 Debian installer too? I suspect it should, but am not sure the
3343 current debian-installer coordinators find it useful enough. It also
3344 depend on the side effects of the change. I
'm not aware of any, but I
3345 guess we will see if the change is safe after some more testing.
3346 Perhaps there is some package in Debian depending on sync() and
3347 fsync() having effect? Perhaps it should go into its own udeb, to
3348 allow those of us wanting to enable it to do so without affecting
3351 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
3352 will break installation of all programs using gnutls because of
3353 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
3354 eatmydata package in Debian will solve it.
</p
>
3356 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
3357 the optimization work again. And I have discovered that the
3358 dpkg-divert trick is not really needed and implemented a slightly
3359 simpler approach as part of the debian-edu-install package. See
3360 tools/edu-eatmydata-install in the source package.
</p
>
3362 <p
>Update
2014-
11-
11: Unfortunately, a new
3363 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
3364 triggering on i386 made it into testing, and broke this installation
3365 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
3366 request
768893</a
> is accepted, it should be working again.
</p
>
3371 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
3372 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
3373 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
3374 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
3375 <description><p
>Yesterday, I had the pleasure of attending a talk with the
3376 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
3377 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
3378 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
3379 learn that there is a large set of publicly available key servers to
3380 use when looking for peoples public key. So far I have used
3381 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
3382 were misbehaving, but those days are ended. The servers I have used
3383 up until yesterday have been slow and some times unavailable. I hope
3384 those problems are gone now.
</p
>
3386 <p
>Behind the round robin DNS entry of the
3387 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
3388 there is a pool of more than
100 keyservers which are checked every
3389 day to ensure they are well connected and up to date. It must be
3390 better than what I have used so far. :)
</p
>
3392 <p
>Yesterdays speaker told me that the service is the default
3393 keyserver provided by the default configuration in GnuPG, but this do
3394 not seem to be used in Debian. Perhaps it should?
</p
>
3396 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
3399 <p
><blockquote
><pre
>
3400 keyserver pool.sks-keyservers.net
3401 </pre
></blockquote
></p
>
3403 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
3404 entries in DNS. Just for fun, I did just that at work, so now every
3405 user of GnuPG at the University of Oslo should find a OpenGPG
3406 keyserver automatically should their need it:
</p
>
3408 <p
><blockquote
><pre
>
3409 % host -t srv _pgpkey-http._tcp.uio.no
3410 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
3412 </pre
></blockquote
></p
>
3414 <p
>Now if only
3415 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
3416 HKP lookup protocol
</a
> supported finding signature paths, I would be
3417 very happy. It can look up a given key or search for a user ID, but I
3418 normally do not want that, but to find a trust path from my key to
3419 another key. Given a user ID or key ID, I would like to find (and
3420 download) the keys representing a signature path from my key to the
3421 key in question, to be able to get a trust path between the two keys.
3422 This is as far as I can tell not possible today. Perhaps something
3423 for a future version of the protocol?
</p
>
3428 <title>From English wiki to translated PDF and epub via Docbook
</title>
3429 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
3430 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
3431 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
3432 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
3433 project
</a
> provide an instruction manual for teachers, system
3434 administrators and other users that contain useful tips for setting up
3435 and maintaining a Debian Edu installation. This text is about how the
3436 text processing of this manual is handled in the project.
</p
>
3438 <p
>One goal of the project is to provide information in the native
3439 language of its users, and for this we need to handle translations.
3440 But we also want to make sure each language contain the same
3441 information, so for this we need a good way to keep the translations
3442 in sync. And we want it to be easy for our users to improve the
3443 documentation, avoiding the need to learn special formats or tools to
3444 contribute, and the obvious way to do this is to make it possible to
3445 edit the documentation using a web browser. We also want it to be
3446 easy for translators to keep the translation up to date, and give them
3447 help in figuring out what need to be translated. Here is the list of
3448 tools and the process we have found trying to reach all these
3451 <p
>We maintain the authoritative source of our manual in the
3452 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
3453 wiki
</a
>, as several wiki pages written in English. It consist of one
3454 front page with references to the different chapters, several pages
3455 for each chapter, and finally one
"collection page
" gluing all the
3456 chapters together into one large web page (aka
3457 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
3458 AllInOne page
</a
>). The AllInOne page is the one used for further
3459 processing and translations. Thanks to the fact that the
3460 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
3461 wiki.debian.org support exporting pages in
3462 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
3463 the list of pages to export using the raw version of the AllInOne
3464 page, loop over each of them to generate a Docbook XML version of the
3465 manual. This process also download images and transform image
3466 references to use the locally downloaded images. The generated
3467 Docbook XML files are slightly broken, so some post-processing is done
3468 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
3469 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
3470 a handfull of images. The XML file can now be used to generate PDF, HTML
3471 and epub versions of the English manual. This is the basic step of
3472 our process, making PDF (using dblatex), HTML (using xsltproc) and
3473 epub (using dbtoepub) version from Docbook XML, and the resulting files
3474 are placed in the debian-edu-doc-en binary package.
</p
>
3476 <p
>But English documentation is not enough for us. We want translated
3477 documentation too, and we want to make it easy for translators to
3478 track the English original. For this we use the
3479 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
3480 which allow us to transform the English Docbook XML file into a
3481 translation file (a .pot file), usable with the normal gettext based
3482 translation tools used by those translating free software. The pot
3483 file is used to create and maintain translation files (several .po
3484 files), which the translations update with the native language
3485 translations of all titles, paragraphs and blocks of text in the
3486 original. The next step is combining the original English Docbook XML
3487 and the translation file (say debian-edu-wheezy-manual.nb.po), to
3488 create a translated Docbook XML file (in this case
3489 debian-edu-wheezy-manual.nb.xml). This translated (or partly
3490 translated, if the translation is not complete) Docbook XML file can
3491 then be used like the original to create a PDF, HTML and epub version
3492 of the documentation.
</p
>
3494 <p
>The translators use different tools to edit the .po files. We
3496 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
3497 while some use emacs and vi, others can use web based editors like
3498 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
3499 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
3500 is where the .po file end up, in our git repository. Updated
3501 translations can either be committed directly to git, or submitted as
3502 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
3503 against the debian-edu-doc package
</a
>.
</p
>
3505 <p
>One challenge is images, which both might need to be translated (if
3506 they show translated user applications), and are needed in different
3507 formats when creating PDF and HTML versions (epub is a HTML version in
3508 this regard). For this we transform the original PNG images to the
3509 needed density and format during build, and have a way to provide
3510 translated images by storing translated versions in
3511 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
3512 package maintainers know more.
</p
>
3514 <p
>If you wonder what the result look like, we provide
3515 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
3516 of the documentation packages on the web
</a
>. See for example the
3517 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
3518 PDF version
</a
> or the
3519 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
3520 HTML version
</a
>. We do not yet build the epub version by default,
3521 but perhaps it will be done in the future.
</p
>
3523 <p
>To learn more, check out
3524 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
3525 debian-edu-doc package
</a
>,
3526 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
3527 manual on the wiki
</a
> and
3528 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
3529 translation instructions
</a
> in the manual.
</p
>
3534 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
3535 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
3536 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
3537 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
3538 <description><p
>It would be nice if it was easier in Debian to get all the hardware
3539 related packages relevant for the computer installed automatically.
3540 So I implemented one, using
3541 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
3542 package
</a
>. To use it, install the tasksel and isenkram packages and
3543 run tasksel as user root. You should be presented with a new option,
3544 "Hardware specific packages (autodetected by isenkram)
". When you
3545 select it, tasksel will install the packages isenkram claim is fit for
3546 the current hardware, hot pluggable or not.
<p
>
3548 <p
>The implementation is in two files, one is the tasksel menu entry
3549 description, and the other is the script used to extract the list of
3550 packages to install. The first part is in
3551 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
3554 <p
><blockquote
><pre
>
3557 Description: Hardware specific packages (autodetected by isenkram)
3558 Based on the detected hardware various hardware specific packages are
3560 Test-new-install: mark show
3562 Packages: for-current-hardware
3563 </pre
></blockquote
></p
>
3565 <p
>The second part is in
3566 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
3569 <p
><blockquote
><pre
>
3574 isenkram-autoinstall-firmware -l
3576 </pre
></blockquote
></p
>
3578 <p
>All in all, a very short and simple implementation making it
3579 trivial to install the hardware dependent package we all may want to
3580 have installed on our machines. I
've not been able to find a way to
3581 get tasksel to tell you exactly which packages it plan to install
3582 before doing the installation. So if you are curious or careful,
3583 check the output from the isenkram-* command line tools first.
</p
>
3585 <p
>The information about which packages are handling which hardware is
3586 fetched either from the isenkram package itself in
3587 /usr/share/isenkram/, from git.debian.org or from the APT package
3588 database (using the Modaliases header). The APT package database
3589 parsing have caused a nasty resource leak in the isenkram daemon (bugs
3590 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
3591 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
3592 the python-apt code (bug
3593 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
3594 workaround I was able to get rid of the file descriptor leak and
3595 reduce the memory leak from ~
30 MiB per hardware detection down to
3596 around
2 MiB per hardware detection. It should make the desktop
3597 daemon a lot more useful. The fix is in version
0.7 uploaded to
3598 unstable today.
</p
>
3600 <p
>I believe the current way of mapping hardware to packages in
3601 Isenkram is is a good draft, but in the future I expect isenkram to
3602 use the AppStream data source for this. A proposal for getting proper
3603 AppStream support into Debian is floating around as
3604 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
3605 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
3606 project
</a
> will take place this summer to improve the situation. I
3607 look forward to seeing the result, and welcome patches for isenkram to
3608 start using the information when it is ready.
</p
>
3610 <p
>If you want your package to map to some specific hardware, either
3611 add a
"Xb-Modaliases
" header to your control file like I did in
3612 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
3613 package
</a
> or submit a bug report with the details to the isenkram
3615 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
3616 blog posts tagged isenkram
</a
> for details on the notation. I expect
3617 the information will be migrated to AppStream eventually, but for the
3618 moment I got no better place to store it.
</p
>
3623 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
3624 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
3625 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
3626 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
3627 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3628 project
</a
> is working on providing the software and hardware to make
3629 it easy for non-technical people to host their data and communication
3630 at home, and being able to communicate with their friends and family
3631 encrypted and away from prying eyes. It is still going strong, and
3632 today a major mile stone was reached.
</p
>
3634 <p
>Today, the last of the packages currently used by the project to
3635 created the system images were accepted into Debian Unstable. It was
3636 the freedombox-setup package, which is used to configure the images
3637 during build and on the first boot. Now all one need to get going is
3638 the build code from the freedom-maker git repository and packages from
3639 Debian. And once the freedombox-setup package enter testing, we can
3640 build everything directly from Debian. :)
</p
>
3642 <p
>Some key packages used by Freedombox are
3643 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
3644 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
3645 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
3646 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
3647 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
3648 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
3649 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
3650 are plans to integrate more packages into the setup. User
3651 documentation is maintained on the Debian wiki. Please
3652 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
3653 the manual
</a
> and help us improve it.
</p
>
3655 <p
>To test for yourself and create boot images with the FreedomBox
3656 setup, run this on a Debian machine using a user with sudo rights to
3657 become root:
</p
>
3659 <p
><pre
>
3660 sudo apt-get install git vmdebootstrap mercurial python-docutils \
3661 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
3663 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
3665 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
3666 </pre
></p
>
3668 <p
>Root access is needed to run debootstrap and mount loopback
3669 devices. See the README in the freedom-maker git repo for more
3670 details on the build. If you do not want all three images, trim the
3671 make line. Note that the virtualbox-image target is not really
3672 virtualbox specific. It create a x86 image usable in kvm, qemu,
3673 vmware and any other x86 virtual machine environment. You might need
3674 the version of vmdebootstrap in Jessie to get the build working, as it
3675 include fixes for a race condition with kpartx.
</p
>
3677 <p
>If you instead want to install using a Debian CD and the preseed
3678 method, boot a Debian Wheezy ISO and use this boot argument to load
3679 the preseed values:
</p
>
3681 <p
><pre
>
3682 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
3683 </pre
></p
>
3685 <p
>I have not tested it myself the last few weeks, so I do not know if
3686 it still work.
</p
>
3688 <p
>If you wonder how to help, one task you could look at is using
3689 systemd as the boot system. It will become the default for Linux in
3690 Jessie, so we need to make sure it is usable on the Freedombox. I did
3691 a simple test a few weeks ago, and noticed dnsmasq failed to start
3692 during boot when using systemd. I suspect there are other problems
3693 too. :) To detect problems, there is a test suite included, which can
3694 be run from the plinth web interface.
</p
>
3696 <p
>Give it a go and let us know how it goes on the mailing list, and help
3697 us get the new release published. :) Please join us on
3698 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
3699 irc.debian.org)
</a
> and
3700 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
3701 mailing list
</a
> if you want to help make this vision come true.
</p
>
3706 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
3707 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
3708 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
3709 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
3710 <description><p
>For a while now, I have been looking for a sensible offsite backup
3711 solution for use at home. My requirements are simple, it must be
3712 cheap and locally encrypted (in other words, I keep the encryption
3713 keys, the storage provider do not have access to my private files).
3714 One idea me and my friends had many years ago, before the cloud
3715 storage providers showed up, was to use Google mail as storage,
3716 writing a Linux block device storing blocks as emails in the mail
3717 service provided by Google, and thus get heaps of free space. On top
3718 of this one can add encryption, RAID and volume management to have
3719 lots of (fairly slow, I admit that) cheap and encrypted storage. But
3720 I never found time to implement such system. But the last few weeks I
3721 have looked at a system called
3722 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
3723 mounted network backed file system with the features I need.
</p
>
3725 <p
>S3QL is a fuse file system with a local cache and cloud storage,
3726 handling several different storage providers, any with Amazon S3,
3727 Google Drive or OpenStack API. There are heaps of such storage
3728 providers. S3QL can also use a local directory as storage, which
3729 combined with sshfs allow for file storage on any ssh server. S3QL
3730 include support for encryption, compression, de-duplication, snapshots
3731 and immutable file systems, allowing me to mount the remote storage as
3732 a local mount point, look at and use the files as if they were local,
3733 while the content is stored in the cloud as well. This allow me to
3734 have a backup that should survive fire. The file system can not be
3735 shared between several machines at the same time, as only one can
3736 mount it at the time, but any machine with the encryption key and
3737 access to the storage service can mount it if it is unmounted.
</p
>
3739 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
3740 package is included already. So to get started, run
<tt
>apt-get
3741 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
3742 Greenqloud, after reading their nice recipe on
3743 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
3744 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
3745 in Iceland more than those in USA when it come to keeping my personal
3746 data safe and private, and thus would rather spend money on a company
3747 in Iceland. Another nice recipe is available from the article
3748 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
3749 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
3750 Admin magazine. When the provider is picked, figure out how to get
3751 the API key needed to connect to the storage API. With Greencloud,
3752 the key did not show up until I had added payment details to my
3755 <p
>Armed with the API access details, it is time to create the file
3756 system. First, create a new bucket in the cloud. This bucket is the
3757 file system storage area. I picked a bucket name reflecting the
3758 machine that was going to store data there, but any name will do.
3759 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
3760 the API login and password, and a locally created password. Store it
3761 all in ~root/.s3ql/authinfo2 like this:
3763 <p
><blockquote
><pre
>
3765 storage-url: s3c://s.greenqloud.com:
443/bucket-name
3766 backend-login: API-login
3767 backend-password: API-password
3768 fs-passphrase: local-password
3769 </pre
></blockquote
></p
>
3771 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
3772 but any sensible way to create a fairly random password should do it.
3773 Armed with these details, it is now time to run mkfs, entering the API
3774 details and password to create it:
</p
>
3776 <p
><blockquote
><pre
>
3777 # mkdir -m
700 /var/lib/s3ql-cache
3778 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3779 --ssl s3c://s.greenqloud.com:
443/bucket-name
3780 Enter backend login:
3781 Enter backend password:
3782 Before using S3QL, make sure to read the user
's guide, especially
3783 the
'Important Rules to Avoid Loosing Data
' section.
3784 Enter encryption password:
3785 Confirm encryption password:
3786 Generating random encryption key...
3787 Creating metadata tables...
3797 Compressing and uploading metadata...
3798 Wrote
0.00 MB of compressed metadata.
3799 #
</pre
></blockquote
></p
>
3801 <p
>The next step is mounting the file system to make the storage available.
3803 <p
><blockquote
><pre
>
3804 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3805 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3806 Using
4 upload threads.
3807 Downloading and decompressing metadata...
3817 Mounting filesystem...
3819 Filesystem Size Used Avail Use% Mounted on
3820 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
3822 </pre
></blockquote
></p
>
3824 <p
>The file system is now ready for use. I use rsync to store my
3825 backups in it, and as the metadata used by rsync is downloaded at
3826 mount time, no network traffic (and storage cost) is triggered by
3827 running rsync. To unmount, one should not use the normal umount
3828 command, as this will not flush the cache to the cloud storage, but
3829 instead running the umount.s3ql command like this:
3831 <p
><blockquote
><pre
>
3834 </pre
></blockquote
></p
>
3836 <p
>There is a fsck command available to check the file system and
3837 correct any problems detected. This can be used if the local server
3838 crashes while the file system is mounted, to reset the
"already
3839 mounted
" flag. This is what it look like when processing a working
3840 file system:
</p
>
3842 <p
><blockquote
><pre
>
3843 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
3844 Using cached metadata.
3845 File system seems clean, checking anyway.
3846 Checking DB integrity...
3847 Creating temporary extra indices...
3848 Checking lost+found...
3849 Checking cached objects...
3850 Checking names (refcounts)...
3851 Checking contents (names)...
3852 Checking contents (inodes)...
3853 Checking contents (parent inodes)...
3854 Checking objects (reference counts)...
3855 Checking objects (backend)...
3856 ..processed
5000 objects so far..
3857 ..processed
10000 objects so far..
3858 ..processed
15000 objects so far..
3859 Checking objects (sizes)...
3860 Checking blocks (referenced objects)...
3861 Checking blocks (refcounts)...
3862 Checking inode-block mapping (blocks)...
3863 Checking inode-block mapping (inodes)...
3864 Checking inodes (refcounts)...
3865 Checking inodes (sizes)...
3866 Checking extended attributes (names)...
3867 Checking extended attributes (inodes)...
3868 Checking symlinks (inodes)...
3869 Checking directory reachability...
3870 Checking unix conventions...
3871 Checking referential integrity...
3872 Dropping temporary indices...
3873 Backing up old metadata...
3883 Compressing and uploading metadata...
3884 Wrote
0.89 MB of compressed metadata.
3886 </pre
></blockquote
></p
>
3888 <p
>Thanks to the cache, working on files that fit in the cache is very
3889 quick, about the same speed as local file access. Uploading large
3890 amount of data is to me limited by the bandwidth out of and into my
3891 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
3892 which is very close to my upload speed, and downloading the same
3893 Debian installation ISO gave me
610 kiB/s, close to my download speed.
3894 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
3895 network, not the file system code. I do not know what a good cache
3896 size would be, but suspect that the cache should e larger than your
3897 working set.
</p
>
3899 <p
>I mentioned that only one machine can mount the file system at the
3900 time. If another machine try, it is told that the file system is
3903 <p
><blockquote
><pre
>
3904 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
3905 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
3906 Using
8 upload threads.
3907 Backend reports that fs is still mounted elsewhere, aborting.
3909 </pre
></blockquote
></p
>
3911 <p
>The file content is uploaded when the cache is full, while the
3912 metadata is uploaded once every
24 hour by default. To ensure the
3913 file system content is flushed to the cloud, one can either umount the
3914 file system, or ask S3QL to flush the cache and metadata using
3917 <p
><blockquote
><pre
>
3918 # s3qlctrl upload-meta /s3ql
3919 # s3qlctrl flushcache /s3ql
3921 </pre
></blockquote
></p
>
3923 <p
>If you are curious about how much space your data uses in the
3924 cloud, and how much compression and deduplication cut down on the
3925 storage usage, you can use s3qlstat on the mounted file system to get
3928 <p
><blockquote
><pre
>
3930 Directory entries:
9141
3933 Total data size:
22049.38 MB
3934 After de-duplication:
21955.46 MB (
99.57% of total)
3935 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
3936 Database size:
2.39 MB (uncompressed)
3937 (some values do not take into account not-yet-uploaded dirty blocks in cache)
3939 </pre
></blockquote
></p
>
3941 <p
>I mentioned earlier that there are several possible suppliers of
3942 storage. I did not try to locate them all, but am aware of at least
3943 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
3944 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
3945 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
3946 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
3947 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
3948 accept payment in Bitcoin. Pick one that suit your need. Some of
3949 them provide several GiB of free storage, but the prize models are
3950 quite different and you will have to figure out what suits you
3953 <p
>While researching this blog post, I had a look at research papers
3954 and posters discussing the S3QL file system. There are several, which
3955 told me that the file system is getting a critical check by the
3956 science community and increased my confidence in using it. One nice
3958 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
3959 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
3960 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
3961 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
3962 and Pamela Smith. Please have a look.
</p
>
3964 <p
>Given my problems with different file systems earlier, I decided to
3965 check out the mounted S3QL file system to see if it would be usable as
3966 a home directory (in other word, that it provided POSIX semantics when
3967 it come to locking and umask handling etc). Running
3968 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
3969 test code to check file system semantics
</a
>, I was happy to discover that
3970 no error was found. So the file system can be used for home
3971 directories, if one chooses to do so.
</p
>
3973 <p
>If you do not want a locally file system, and want something that
3974 work without the Linux fuse file system, I would like to mention the
3975 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
3976 provide locally encrypted backup using a command line client. It have
3977 a nicer access control system, where one can split out read and write
3978 access, allowing some systems to write to the backup and others to
3979 only read from it.
</p
>
3981 <p
>As usual, if you use Bitcoin and want to show your support of my
3982 activities, please send Bitcoin donations to my address
3983 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3988 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
3989 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
3990 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
3991 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
3992 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
3993 project
</a
> is working on providing the software and hardware for
3994 making it easy for non-technical people to host their data and
3995 communication at home, and being able to communicate with their
3996 friends and family encrypted and away from prying eyes. It has been
3997 going on for a while, and is slowly progressing towards a new test
3998 release (
0.2).
</p
>
4000 <p
>And what day could be better than the Pi day to announce that the
4001 new version will provide
"hard drive
" / SD card / USB stick images for
4002 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
4003 system), and can also be installed using a Debian installer preseed
4004 file. The Debian based Freedombox is now based on Debian Jessie,
4005 where most of the needed packages used are already present. Only one,
4006 the freedombox-setup package, is missing. To try to build your own
4007 boot image to test the current status, fetch the freedom-maker scripts
4009 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
4010 with a user with sudo access to become root:
4013 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
4015 sudo apt-get install git vmdebootstrap mercurial python-docutils \
4016 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
4018 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
4021 <p
>Root access is needed to run debootstrap and mount loopback
4022 devices. See the README for more details on the build. If you do not
4023 want all three images, trim the make line. But note that thanks to
<a
4024 href=
"https://bugs.debian.org/
741407">a race condition in
4025 vmdebootstrap
</a
>, the build might fail without the patch to the
4026 kpartx call.
</p
>
4028 <p
>If you instead want to install using a Debian CD and the preseed
4029 method, boot a Debian Wheezy ISO and use this boot argument to load
4030 the preseed values:
</p
>
4033 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
4036 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
4037 recently introduced bug in apt in Jessie
</a
>, the installer will
4038 currently hang while setting up APT sources. Killing the
4039 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
4040 installation will get the installation going. This affect all
4041 installations in Jessie, and I expect it will be fixed soon.
</p
>
4043 <p
>Give it a go and let us know how it goes on the mailing list, and help
4044 us get the new release published. :) Please join us on
4045 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
4046 irc.debian.org)
</a
> and
4047 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4048 mailing list
</a
> if you want to help make this vision come true.
</p
>
4053 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
4054 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
4055 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
4056 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
4057 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
4058 innetgr tools, because I needed them in
4059 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
4060 ng-utils, and it has served me well. I placed the project under the
4061 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
4062 repository. But many years ago, the CVS repository was dropped (lost,
4063 not migrated to new hardware, not sure), and the project have lacked a
4064 proper home since then.
</p
>
4066 <p
>Last summer, I had a look at the package and made a new release
4067 fixing a irritating crash bug, but was unable to store the changes in
4068 a proper source control system. I applied for a project on
4069 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
4070 to follow up on it. Until today. :)
</p
>
4072 <p
>After many hours of cleaning and migration, the ng-utils project
4073 now have a new home, and a git repository with the highlight of the
4074 history of the project. I published all release tarballs and imported
4075 them into the git repository. As the project is really stable and not
4076 expected to gain new features any time soon, I decided to make a new
4077 release and call it
1.0. Visit the new project home on
4078 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
4079 if you want to check it out. The new version is also uploaded into
4080 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
4085 <title>Testing sysvinit from experimental in Debian Hurd
</title>
4086 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
4087 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
4088 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
4089 <description><p
>A few days ago I decided to try to help the Hurd people to get
4090 their changes into sysvinit, to allow them to use the normal sysvinit
4091 boot system instead of their old one. This follow up on the
4092 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
4093 Google Summer of Code work
</a
> done last summer by Justus Winter to
4094 get Debian on Hurd working more like Debian on Linux. To get started,
4095 I downloaded a prebuilt hard disk image from
4096 <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
>,
4097 and started it using virt-manager.
</p
>
4099 <p
>The first think I had to do after logging in (root without any
4100 password) was to get the network operational. I followed
4101 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
4102 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
4103 commands as root to get the machine to accept a IP address from the
4104 kvm internal DHCP server:
</p
>
4106 <p
><blockquote
><pre
>
4107 settrans -fgap /dev/netdde /hurd/netdde
4108 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
4109 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
4111 </pre
></blockquote
></p
>
4113 <p
>After this, the machine had internet connectivity, and I could
4114 upgrade it and install the sysvinit packages from experimental and
4115 enable it as the default boot system in Hurd.
</p
>
4117 <p
>But before I did that, I set a password on the root user, as ssh is
4118 running on the machine it for ssh login to work a password need to be
4119 set. Also, note that a bug somewhere in openssh on Hurd block
4120 compression from working. Remember to turn that off on the client
4123 <p
>Run these commands as root to upgrade and test the new sysvinit
4126 <p
><blockquote
><pre
>
4127 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
4128 deb http://http.debian.net/debian/ experimental main
4131 apt-get dist-upgrade
4132 apt-get install -t experimental initscripts sysv-rc sysvinit \
4133 sysvinit-core sysvinit-utils
4134 update-alternatives --config runsystem
4135 </pre
></blockquote
></p
>
4137 <p
>To reboot after switching boot system, you have to use
4138 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
4139 yet a sysvinit process able to receive the signals from the normal
4140 'reboot
' command. After switching to sysvinit as the boot system,
4141 upgrading every package and rebooting, the network come up with DHCP
4142 after boot as it should, and the settrans/pkill hack mentioned at the
4143 start is no longer needed. But for some strange reason, there are no
4144 longer any login prompt in the virtual console, so I logged in using
4147 <p
>Note that there are some race conditions in Hurd making the boot
4148 fail some times. No idea what the cause is, but hope the Hurd porters
4149 figure it out. At least Justus said on IRC (#debian-hurd on
4150 irc.debian.org) that they are aware of the problem. A way to reduce
4151 the impact is to upgrade to the Hurd packages built by Justus by
4152 adding this repository to the machine:
</p
>
4154 <p
><blockquote
><pre
>
4155 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
4156 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
4158 </pre
></blockquote
></p
>
4160 <p
>At the moment the prebuilt virtual machine get some packages from
4161 http://ftp.debian-ports.org/debian, because some of the packages in
4162 unstable do not yet include the required patches that are lingering in
4163 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
4165 <p
><blockquote
><pre
>
4166 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
4167 i emacs - GNU Emacs editor (metapackage)
4168 i gdb - GNU Debugger
4169 i hurd-recommended - Miscellaneous translators
4170 i isc-dhcp-client - ISC DHCP client
4171 i isc-dhcp-common - common files used by all the isc-dhcp* packages
4172 i libc-bin - Embedded GNU C Library: Binaries
4173 i libc-dev-bin - Embedded GNU C Library: Development binaries
4174 i libc0.3 - Embedded GNU C Library: Shared libraries
4175 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
4176 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
4177 i multiarch-support - Transitional package to ensure multiarch compatibilit
4178 i A x11-common - X Window System (X.Org) infrastructure
4179 i xorg - X.Org X Window System
4180 i A xserver-xorg - X.Org X server
4181 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
4183 </pre
></blockquote
></p
>
4185 <p
>All in all, testing hurd has been an interesting experience. :)
4186 X.org did not work out of the box and I never took the time to follow
4187 the porters instructions to fix it. This time I was interested in the
4188 command line stuff.
<p
>
4193 <title>New chrpath release
0.16</title>
4194 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
4195 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
4196 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
4197 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
4198 find problems in C, C++ and Java code using static source code
4199 analysis. It can detect a lot of different problems, and is very
4200 useful to find memory and locking bugs in the error handling part of
4201 the source. The company behind it provide
4202 <a href=
"https://scan.coverity.com/
">check of free software projects as
4203 a community service
</a
>, and many hundred free software projects are
4204 already checked. A few days ago I decided to have a closer look at
4205 the Coverity system, and discovered that the
4206 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
4207 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
4208 projects I am involved with was already registered. But these are
4209 fairly big, and I would also like to have a small and easy project to
4210 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
4211 checking of the chrpath project
</a
>. It was
4212 added to the checker and discovered seven potential defects. Six of
4213 these were real, mostly resource
"leak
" when the program detected an
4214 error. Nothing serious, as the resources would be released a fraction
4215 of a second later when the program exited because of the error, but it
4216 is nice to do it right in case the source of the program some time in
4217 the future end up in a library. Having fixed all defects and added
4218 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
4219 mailing list for the chrpath developers
</a
>, I decided it was time to
4220 publish a new release. These are the release notes:
</p
>
4222 <p
>New in
0.16 released
2014-
01-
14:
</p
>
4226 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
4227 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
4228 <li
>Mention new project mailing list in the documentation.
</li
>
4233 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4234 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
4235 project if something is wrong with the new release. The test suite
4236 did not discover any old errors, so if you find a new one, please also
4237 include a test suite check.
</p
>
4242 <title>New chrpath release
0.15</title>
4243 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
4244 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
4245 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
4246 <description><p
>After many years break from the package and a vain hope that
4247 development would be continued by someone else, I finally pulled my
4248 acts together this morning and wrapped up a new release of chrpath,
4249 the command line tool to modify the rpath and runpath of already
4250 compiled ELF programs. The update was triggered by the persistence of
4251 Isha Vishnoi at IBM, which needed a new config.guess file to get
4252 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
4253 is working on. I checked the
4254 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
4255 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
4256 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
4257 packages for interesting patches (failed to find the source from
4258 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
4259 These are the release notes:
</p
>
4261 <p
>New in
0.15 released
2013-
11-
24:
</p
>
4265 <li
>Updated config.sub and config.guess from the GNU project to work
4266 with newer architectures. Thanks to isha vishnoi for the heads
4269 <li
>Updated README with current URLs.
</li
>
4271 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
4272 Matthias Klose.
</li
>
4274 <li
>Added missing help for -k|--keepgoing option, using patch by
4275 Petr Machata found in Fedora.
</li
>
4277 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
4278 .dynamic is a NULL terminated string. Based on patch found in
4279 Fedora credited Axel Thimm and Christian Krause.
</li
>
4284 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
4285 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
4286 project if something is wrong with the new release. The test suite
4287 did not discover any old errors, so if you find a new one, please also
4288 include a testsuite check.
</p
>
4293 <title>Debian init.d boot script example for rsyslog
</title>
4294 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
4295 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
4296 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
4297 <description><p
>If one of the points of switching to a new init system in Debian is
4298 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
4299 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
4300 init.d scripts at all. Here is an example init.d script, ie a rewrite
4301 of /etc/init.d/rsyslog:
</p
>
4303 <p
><pre
>
4304 #!/lib/init/init-d-script
4307 # Required-Start: $remote_fs $time
4308 # Required-Stop: umountnfs $time
4309 # X-Stop-After: sendsigs
4310 # Default-Start:
2 3 4 5
4311 # Default-Stop:
0 1 6
4312 # Short-Description: enhanced syslogd
4313 # Description: Rsyslog is an enhanced multi-threaded syslogd.
4314 # It is quite compatible to stock sysklogd and can be
4315 # used as a drop-in replacement.
4317 DESC=
"enhanced syslogd
"
4318 DAEMON=/usr/sbin/rsyslogd
4319 </pre
></p
>
4321 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
4322 script was
137 lines, and the above is just
15 lines, most of it meta
4323 info/comments.
</p
>
4325 <p
>How to do this, you ask? Well, one create a new script
4326 /lib/init/init-d-script looking something like this:
4328 <p
><pre
>
4331 # Define LSB log_* functions.
4332 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
4333 # and status_of_proc is working.
4334 . /lib/lsb/init-functions
4337 # Function that starts the daemon/service
4343 #
0 if daemon has been started
4344 #
1 if daemon was already running
4345 #
2 if daemon could not be started
4346 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
4348 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
4351 # Add code here, if necessary, that waits for the process to be ready
4352 # to handle requests from services started subsequently which depend
4353 # on this one. As a last resort, sleep for some time.
4357 # Function that stops the daemon/service
4362 #
0 if daemon has been stopped
4363 #
1 if daemon was already stopped
4364 #
2 if daemon could not be stopped
4365 # other if a failure occurred
4366 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
4367 RETVAL=
"$?
"
4368 [
"$RETVAL
" =
2 ]
&& return
2
4369 # Wait for children to finish too if this is a daemon that forks
4370 # and if the daemon is only ever run from this initscript.
4371 # If the above conditions are not satisfied then add some other code
4372 # that waits for the process to drop all resources that could be
4373 # needed by services started subsequently. A last resort is to
4374 # sleep for some time.
4375 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
4376 [
"$?
" =
2 ]
&& return
2
4377 # Many daemons don
't delete their pidfiles when they exit.
4379 return
"$RETVAL
"
4383 # Function that sends a SIGHUP to the daemon/service
4387 # If the daemon can reload its configuration without
4388 # restarting (for example, when it is sent a SIGHUP),
4389 # then implement that here.
4391 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
4396 scriptbasename=
"$(basename $
1)
"
4397 echo
"SN: $scriptbasename
"
4398 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
4399 script=
"$
1"
4406 NAME=$(basename $DAEMON)
4407 PIDFILE=/var/run/$NAME.pid
4409 # Exit if the package is not installed
4410 #[ -x
"$DAEMON
" ] || exit
0
4412 # Read configuration variable file if it is present
4413 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
4415 # Load the VERBOSE setting and other rcS variables
4418 case
"$
1" in
4420 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
4422 case
"$?
" in
4423 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4424 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4428 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
4430 case
"$?
" in
4431 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
4432 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
4436 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
4438 #reload|force-reload)
4440 # If do_reload() is not implemented then leave this commented out
4441 # and leave
'force-reload
' as an alias for
'restart
'.
4443 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
4447 restart|force-reload)
4449 # If the
"reload
" option is implemented then remove the
4450 #
'force-reload
' alias
4452 log_daemon_msg
"Restarting $DESC
" "$NAME
"
4454 case
"$?
" in
4457 case
"$?
" in
4459 1) log_end_msg
1 ;; # Old process is still running
4460 *) log_end_msg
1 ;; # Failed to start
4470 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
4476 </pre
></p
>
4478 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
4479 lot. I did not really polish the approach, so it might not always
4480 work out of the box, but you get the idea. I did not try very hard to
4481 optimize it nor make it more robust either.
</p
>
4483 <p
>A better argument for switching init system in Debian than reducing
4484 the size of init scripts (which is a good thing to do anyway), is to
4485 get boot system that is able to handle the kernel events sensibly and
4486 robustly, and do not depend on the boot to run sequentially. The boot
4487 and the kernel have not behaved sequentially in years.
</p
>
4492 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
4493 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
4494 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
4495 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
4496 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
4497 remote display access is the preferred solution with oVirt and RedHat
4498 Enterprise Virtualization, and I was sad to discover the other day
4499 that the browser plugin needed to use these systems seamlessly was
4500 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
4501 for a package
</a
> was from
2012-
04-
10 with no progress since
4502 2013-
04-
01, so I decided to wrap up a package based on the great work
4503 from Cajus Pollmeier and put it in a collab-maint maintained git
4504 repository to get a package I could use. I would very much like
4505 others to help me maintain the package (or just take over, I do not
4506 mind), but as no-one had volunteered so far, I just uploaded it to
4507 NEW. I hope it will be available in Debian in a few days.
</p
>
4509 <p
>The source is now available from
4510 <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
>
4515 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
4516 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
4517 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
4518 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
4519 <description><p
>The
4520 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
4521 program is a a very nice system to create virtual machine images. It
4522 create a image file, add a partition table, mount it and run
4523 debootstrap in the mounted directory to create a Debian system on a
4524 stick. Yesterday, I decided to try to teach it how to make images for
4525 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
4526 of a plan to simplify the build system for
4527 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
4528 project
</a
>. The FreedomBox project already uses vmdebootstrap for
4529 the virtualbox images, but its current build system made multistrap
4530 based system for Dreamplug images, and it is lacking support for
4531 Raspberry Pi.
</p
>
4533 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
4534 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
4535 code and adjusted it to be able to build armel images on my amd64
4536 Debian laptop. I ended up giving vmdebootstrap five new options,
4537 allowing me to replicate the image creation process I use to make
4538 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
4539 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
4540 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
4541 call debootstrap with --foreign and to copy the handler into the
4542 generated chroot before running the second stage. This allow
4543 vmdebootstrap to create armel images on an amd64 host. Next I added
4544 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
4545 fstype
</tt
> to teach it to create a separate /boot/ partition with the
4546 given file system type, allowing me to create an image with a vfat
4547 partition for the /boot/ stuff. I also added a
<tt
>--variant
4548 variant
</tt
> option to allow me to create smaller images without the
4549 Debian base system packages installed. Finally, I added an option
4550 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
4551 as a boot loader. It is not needed on the Raspberry Pi and probably
4552 most other non-x86 architectures. The changes were accepted by the
4553 upstream author of vmdebootstrap yesterday and today, and is now
4555 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
4556 upstream project page
</a
>.
</p
>
4558 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
4559 create a small script (the customize script) to add the non-free
4560 binary blob needed to boot the Raspberry Pi and the APT source
4563 <p
><pre
>
4565 set -e # Exit on first error
4566 rootdir=
"$
1"
4567 cd
"$rootdir
"
4568 cat
&lt;
&lt;EOF
> etc/apt/sources.list
4569 deb http://http.debian.net/debian/ jessie main contrib non-free
4571 # Install non-free binary blob needed to boot Raspberry Pi. This
4572 # install a kernel somewhere too.
4573 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
4574 -O $rootdir/usr/bin/rpi-update
4575 chmod a+x $rootdir/usr/bin/rpi-update
4576 mkdir -p $rootdir/lib/modules
4577 touch $rootdir/boot/start.elf
4578 chroot $rootdir rpi-update
4579 </pre
></p
>
4581 <p
>Next, fetch the latest vmdebootstrap script and call it like this
4582 to build the image:
</p
>
4585 sudo ./vmdebootstrap \
4588 --distribution jessie \
4589 --mirror http://http.debian.net/debian \
4598 --root-password raspberry \
4599 --hostname raspberrypi \
4600 --foreign /usr/bin/qemu-arm-static \
4601 --customize `pwd`/customize \
4603 --package git-core \
4604 --package binutils \
4605 --package ca-certificates \
4608 </pre
></p
>
4610 <p
>The list of packages being installed are the ones needed by
4611 rpi-update to make the image bootable on the Raspberry Pi, with the
4612 exception of netbase, which is needed by debootstrap to find
4613 /etc/hosts with the minbase variant. I really wish there was a way to
4614 set up an Raspberry Pi using only packages in the Debian archive, but
4615 that is not possible as far as I know, because it boots from the GPU
4616 using a non-free binary blob.
</p
>
4618 <p
>The build host need debootstrap, kpartx and qemu-user-static and
4619 probably a few others installed. I have not checked the complete
4620 build dependency list.
</p
>
4622 <p
>The resulting image will not use the hardware floating point unit
4623 on the Raspberry PI, because the armel architecture in Debian is not
4624 optimized for that use. So the images created will be a bit slower
4625 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
4630 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
4631 <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>
4632 <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>
4633 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
4634 <description><p
>The last few days I came across a few good causes that should get
4635 wider attention. I recommend signing and donating to each one of
4638 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
4639 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
4640 Women program which is a Google Summer of Code like initiative to get
4641 more women involved in free software. One debian sponsor has offered
4642 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
4643 earmarked
</a
> for this initiative. I donated a few minutes ago, and
4644 hope you will to. :)
</p
>
4646 <p
>And the Electronic Frontier Foundation just announced plans to
4647 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
4648 documentaries about the excessive spying
</a
> on every Internet user that
4649 take place these days, and their need to fund the work. I
've already
4650 donated. Are you next?
</p
>
4652 <p
>For my Norwegian audience, the organisation Studentenes og
4653 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
4654 statement under the heading
4655 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
4656 Access
</a
> for those of us asking for more focus on open access in the
4657 Norwegian government. So far
499 signatures. I hope you will sign it
4663 <title>Videos about the Freedombox project - for inspiration and learning
</title>
4664 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
4665 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
4666 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
4667 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
4668 project
</a
> have been going on for a while, and have presented the
4669 vision, ideas and solution several places. Here is a little
4670 collection of videos of talks and presentation of the project.
</p
>
4674 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
4675 2,
5 minute marketing film
</a
> (Youtube)
</li
>
4677 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
4678 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
4680 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
4681 Freedom in the Cloud - Software Freedom, Privacy and and Security for
4682 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
4683 (Youtube)
</li
>
4685 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
4686 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
4688 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
4689 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
4691 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
4692 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
4693 York City in
2012</a
> (Youtube)
</li
>
4695 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
4696 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
4697 (Youtube)
</li
>
4699 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
4700 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
4702 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
4703 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
4705 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
4706 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
4707 2013</a
> (Youtube)
</li
>
4711 <p
>A larger list is available from
4712 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
4713 Freedombox Wiki
</a
>.
</p
>
4715 <p
>On other news, I am happy to report that Freedombox based on Debian
4716 Jessie is coming along quite well, and soon both Owncloud and using
4717 Tor should be available for testers of the Freedombox solution. :) In
4718 a few weeks I hope everything needed to test it is included in Debian.
4719 The withsqlite package is already in Debian, and the plinth package is
4720 pending in NEW. The third and vital part of that puzzle is the
4721 metapackage/setup framework, which is still pending an upload. Join
4722 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
4723 (#freedombox on irc.debian.org)
</a
> and
4724 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
4725 mailing list
</a
> if you want to help make this vision come true.
</p
>
4730 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
4731 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
4732 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
4733 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
4734 <description><p
>I was introduced to the
4735 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
4736 in
2010, when Eben Moglen presented his vision about serving the need
4737 of non-technical people to keep their personal information private and
4738 within the legal protection of their own homes. The idea is to give
4739 people back the power over their network and machines, and return
4740 Internet back to its intended peer-to-peer architecture. Instead of
4741 depending on a central service, the Freedombox will give everyone
4742 control over their own basic infrastructure.
</p
>
4744 <p
>I
've intended to join the effort since then, but other tasks have
4745 taken priority. But this summers nasty news about the misuse of trust
4746 and privilege exercised by the
"western
" intelligence gathering
4747 communities increased my eagerness to contribute to a point where I
4748 actually started working on the project a while back.
</p
>
4750 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
4751 Debian initiative
</a
> based on the vision from Eben Moglen, is to
4752 create a simple and cheap Debian based appliance that anyone can hook
4753 up in their home and get access to secure and private services and
4754 communication. The initial deployment platform have been the
4755 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
4756 which is a piece of hardware I do not own. So to be able to test what
4757 the current Freedombox setup look like, I had to come up with a way to install
4758 it on some hardware I do have access to. I have rewritten the
4759 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
4760 image build framework to use .deb packages instead of only copying
4761 setup into the boot images, and thanks to this rewrite I am able to
4762 set up any machine supported by Debian Wheezy as a Freedombox, using
4763 the previously mentioned deb (and a few support debs for packages
4764 missing in Debian).
</p
>
4766 <p
>The current Freedombox setup consist of a set of bootstrapping
4768 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
4769 and a administrative web interface
4770 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
4771 withsqlite), as well as a privacy enhancing proxy based on
4772 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
4773 (freedombox-privoxy). There is also a web/javascript based XMPP
4774 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
4775 trying (unsuccessfully so far) to talk to the XMPP server
4776 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
4777 web interface is pluggable, and the goal is to use it to enable OpenID
4778 services, mesh network connectivity, use of TOR, etc, etc. Not much of
4779 this is really working yet, see
4780 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
4781 project TODO
</a
> for links to GIT repositories. Most of the code is
4782 on github at the moment. The HTTP proxy is operational out of the
4783 box, and the admin web interface can be used to add/remove plinth
4784 users. I
've not been able to do anything else with it so far, but
4785 know there are several branches spread around github and other places
4786 with lots of half baked features.
</p
>
4788 <p
>Anyway, if you want to have a look at the current state, the
4789 following recipes should work to give you a test machine to poke
4792 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
4796 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
4797 <li
>Boot from it, either as CD or USB stick.
</li
>
4798 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
4799 to the Debian installer:
<p
>
4800 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
4802 <li
>Answer the few language/region/password questions and pick disk to
4803 install on.
</li
>
4805 <li
>When the installation is finished and the machine have rebooted a
4806 few times, your Freedombox is ready for testing.
</li
>
4810 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
4814 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
4815 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
4816 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
4818 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
4819 </pre
></li
>
4820 <li
><p
>Run this as root:
</p
>
4822 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
4825 apt-get install freedombox-setup
4826 /usr/lib/freedombox/setup
4827 </pre
></li
>
4828 <li
>Reboot into your freshly created Freedombox.
</li
>
4832 <p
>You can test it on other architectures too, but because the
4833 freedombox-privoxy package is binary, it will only work as intended on
4834 the architectures where I have had time to build the binary and put it
4835 in my APT repository. But do not let this stop you. It is only a
4836 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
4838 <p
>Note that by default Freedombox is a DHCP server on the
4839 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
4840 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
4841 disable
</tt
>" as root.
</p
>
4843 <p
>Please let me know if this works for you, or if you have any
4844 problems. We gather on the IRC channel
4845 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
4846 irc.debian.org and the
4847 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
4848 mailing list
</a
>.
</p
>
4850 <p
>Once you get your freedombox operational, you can visit
4851 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
4852 welcome screen (dead end - do not be surprised if you are unable to
4853 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
4854 to look at the rest of plinth. The default user is
'admin
' and the
4855 default password is
'secret
'.
</p
>
4860 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
4861 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
4862 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
4863 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
4864 <description><p
>Earlier, I reported about
4865 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
4866 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
4867 told by IBM that the original disk should be thrown away. And as
4868 there no longer was a problem if I bricked the firmware, I decided
4869 today to try to install Intel firmware to replace the Lenovo firmware
4870 currently on the disk.
</p
>
4872 <p
>I searched the Intel site for firmware, and found
4873 <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
>
4874 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
4875 according to the site should contain the latest firmware for SSD
4876 disks. I inserted the broken disk in one of my spare laptops and
4877 booted the ISO from a USB stick. The disk was recognized, but the
4878 program claimed the newest firmware already were installed and refused
4879 to insert any Intel firmware. So no change, and the disk is still
4880 unable to handle write load. :( I guess the only way to get them
4881 working would be if Lenovo releases new firmware. No idea how likely
4882 that is. Anyway, just blogging about this test for completeness. I
4883 got a working Samsung disk, and see no point in spending more time on
4884 the broken disks.
</p
>
4889 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
4890 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
4891 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
4892 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
4893 <description><p
>Today I switched to
4894 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
4895 new laptop
</a
>. I
've previously written about the problems I had with
4896 my new Thinkpad X230, which was delivered with an
4897 <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
4898 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
4899 sustained writes. My hardware supplier have been very forthcoming in
4900 trying to find a solution, and after first trying with another
4901 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
4902 disk instead to fix it once and for all. The Samsung disk survived
4903 the installation of Debian with encrypted disks (filling the disk with
4904 random data during installation killed the first two), and I thus
4905 decided to trust it with my data. I have installed it as a Debian Edu
4906 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
4907 server at home using Kerberos and LDAP, and will use it as my work
4908 station from now on.
</p
>
4910 <p
>As this is a solid state disk with no moving parts, I believe the
4911 Debian Wheezy default installation need to be tuned a bit to increase
4912 performance and increase life time of the disk. The Linux kernel and
4913 user space applications do not yet adjust automatically to such
4914 environment. To make it easier for my self, I created a draft Debian
4915 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
4916 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
4917 for the ssd-setup package
</a
> is available from collab-maint, and it
4918 is set up to adjust the setup of the machine by just installing the
4919 package. If there is any non-SSD disk in the machine, the package
4920 will refuse to install, as I did not try to write any logic to sort
4921 file systems in SSD and non-SSD file systems.
</p
>
4923 <p
>I consider the package a draft, as I am a bit unsure how to best
4924 set up Debian Wheezy with an SSD. It is adjusted to my use case,
4925 where I set up the machine with one large encrypted partition (in
4926 addition to /boot), put LVM on top of this and set up partitions on
4927 top of this again. See the README file in the package source for the
4928 references I used to pick the settings. At the moment these
4929 parameters are tuned:
</p
>
4933 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
4934 (adding discard to /etc/crypttab)
</li
>
4936 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
4937 this case a cryptsetup partition) by changing issue_discards from
4938 0 to
1 in /etc/lvm/lvm.conf.
</li
>
4940 <li
>Set relatime as a file system option for ext3 and ext4 file
4943 <li
>Tell swap to use TRIM commands by adding
'discard
' to
4944 /etc/fstab.
</li
>
4946 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
4948 <li
>Run fstrim on every ext3 and ext4 file system every night (from
4949 cron.daily).
</li
>
4951 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
4952 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
4956 <p
>During installation, I cancelled the part where the installer fill
4957 the disk with random data, as this would kill the SSD performance for
4958 little gain. My goal with the encrypted file system is to ensure
4959 those stealing my laptop end up with a brick and not a working
4960 computer. I have no hope in keeping the really resourceful people
4961 from getting the data on the disk (see
4962 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
4963 Thus I concluded that adding the discard option to crypttab is the
4964 right thing to do.
</p
>
4966 <p
>I considered using the noop I/O scheduler, as several recommended
4967 it for SSD, but others recommended deadline and a benchmark I found
4968 indicated that deadline might be better for interactive use.
</p
>
4970 <p
>I also considered using the
'discard
' file system option for ext3
4971 and ext4, but read that it would give a performance hit ever time a
4972 file is removed, and thought it best to that that slowdown once a day
4973 instead of during my work.
</p
>
4975 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
4976 this is already done by Debian Edu.
</p
>
4978 <p
>I have not yet started on the user space tuning. I expect
4979 iceweasel need some tuning, and perhaps other applications too, but
4980 have not yet had time to investigate those parts.
</p
>
4982 <p
>The package should work on Ubuntu too, but I have not yet tested it
4985 <p
>As for the answer to the question in the title of this blog post,
4986 as far as I know, the only solution I know about is to replace the
4987 disk. It might be possible to flash it with Intel firmware instead of
4988 the Lenovo firmware. But I have not tried and did not want to do so
4989 without approval from Lenovo as I wanted to keep the warranty on the
4990 disk until a solution was found and they wanted the broken disks
4996 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
4997 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
4998 <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>
4999 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
5000 <description><p
>A few days ago, I wrote about
5001 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
5002 problems I experienced with my new X230 and its SSD disk
</a
>, which
5003 was dying during installation because it is unable to cope with
5004 sustained write. My supplier is in contact with
5005 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
5006 replacement disk to try to fix the problem. They decided to send an
5007 identical model, so my hopes for a permanent fix was slim.
</p
>
5009 <p
>Anyway, today I got the replacement disk and tried to install
5010 Debian Edu Wheezy with encrypted disk on it. The new disk have the
5011 same firmware version as the original. This time my hope raised
5012 slightly as the installation progressed, as the original disk used to
5013 die after
4-
7% of the disk was written to, while this time it kept
5014 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
5015 died again and I was back on square one. I still do not have a new
5016 laptop with a disk I can trust. I can not live with a disk that might
5017 lock up when I download a new
5018 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
5019 other large files. I look forward to hearing from my supplier with
5020 the next proposal from Lenovo.
</p
>
5022 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
5023 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
5024 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5025 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
5026 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5027 P/N
45N8295, P0C38732.
</p
>
5029 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
5030 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
5031 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
5032 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
5033 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
5034 P/N
45N8295, P0C38732.
</p
>
5036 <p
>The only difference is in the first number (serial number?), ISN,
5037 SA, date and WNPP values. Mentioning all the details here in case
5038 someone is able to use the information to find a way to identify the
5039 failing disk among working ones (if any such working disk actually
5045 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
5046 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
5047 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
5048 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
5049 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
5050 Debian Edu developer gathering and Debian and Ubuntu bug squashing
5051 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
5052 member assosiation NUUG
</a
> and
5053 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
5054 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
5055 Bitraf
</a
>.
</p
>
5057 <p
>It starts
10:
00 and continue until late evening. Everyone is
5058 welcome, and there is no fee to participate. There is on the other
5059 hand limited space, and only room for
30 people. Please put your name
5060 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
5061 wiki page
</a
> if you plan to join us.
</p
>
5066 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
5067 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
5068 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
5069 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
5070 <description><p
>Half a year ago, I reported that I had to find a
5071 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
5072 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
5073 time to spend on it, and it took a while to find a model I believe
5074 will do the job, but two days ago the replacement finally arrived. I
5076 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
5077 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
5078 a roaming workstation, and it seemed to work flawlessly. But my
5079 second installation with encrypted disk was not as successful. More
5080 on that below.
</p
>
5082 <p
>I had a hard time trying to track down a good laptop, as my most
5083 important requirements (robust and with a good keyboard) are never
5084 listed in the feature list. But I did get good help from the search
5085 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5086 allowed me to limit the list of interesting laptops based on my other
5087 requirements. A bit surprising that SSD disk are not disks according
5088 to that search interface, so I had to drop specifying the number of
5089 disks from my search parameters. I also asked around among friends to
5090 get their impression on keyboards and robustness.
</p
>
5092 <p
>So the new laptop arrived, and it is quite a lot wider than the
5093 X41. I am not quite convinced about the keyboard, as it is
5094 significantly wider than my old keyboard, and I have to stretch my
5095 hand a lot more to reach the edges. But the key response is fairly
5096 good and the individual key shape is fairly easy to handle, so I hope
5097 I will get used to it. My old X40 was starting to fail, and I really
5098 needed a new laptop now. :)
</p
>
5100 <p
>Turning off the touch pad was simple. All it took was a quick
5101 visit to the BIOS during boot it disable it.
</p
>
5103 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
5104 lock up during load. And this happen when installing Debian Wheezy
5105 with encrypted disk, while the disk is being filled with random data.
5106 I also tested to install Ubuntu Raring, and it happen there too if I
5107 reenable the code to fill the disk with random data (it is disabled by
5108 default in Ubuntu). And the bug with is already known. It was
5109 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
5110 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
5111 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
5112 kernel developers as
5113 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
5114 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
5115 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
5116 Lenovo forums, both for
5117 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
5118 2012-
11-
10</a
> and for
5119 <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
5120 03-
20-
2013</a
>. The problem do not only affect installation. The
5121 reports state that the disk lock up during use if many writes are done
5122 on the disk, so it is much no use to work around the installation
5123 problem and end up with a computer that can lock up at any moment.
5125 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
5126 available
</a
> that will lock up the hard drive after running a few
5127 minutes by writing to a file.
</p
>
5129 <p
>I
've contacted my supplier and asked how to handle this, and after
5130 contacting PCHELP Norway (request
01D1FDP) which handle support
5131 requests for Lenovo, his first suggestion was to upgrade the disk
5132 firmware. Unfortunately there is no newer firmware available from
5133 Lenovo, as my disk already have the most recent one (version LF1i). I
5134 hope to hear more from him today and hope the problem can be
5140 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
5141 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
5142 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
5143 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
5144 <description><p
>Half a year ago, I reported that I had to find a replacement for my
5145 trusty old Thinkpad X41. Unfortunately I did not have much time to
5146 spend on it, but today the replacement finally arrived. I ended up
5147 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
5148 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
5149 Wheezy as a roaming workstation, and it worked flawlessly. As I write
5150 this, it is installing what I hope will be a more final installation,
5151 with a encrypted hard drive to ensure any dope head stealing it end up
5152 with an expencive door stop.
</p
>
5154 <p
>I had a hard time trying to track down a good laptop, as my most
5155 important requirements (robust and with a good keyboard) are never
5156 listed in the feature list. But I did get good help from the search
5157 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
5158 allowed me to limit the list of interesting laptops based on my other
5159 requirements. A bit surprising that SSD disk are not disks, so I had
5160 to drop number of disks from my search parameters.
</p
>
5162 <p
>I am not quite convinced about the keyboard, as it is significantly
5163 wider than my old keyboard, and I have to stretch my hand a lot more
5164 to reach the edges. But the key response is fairly good and the
5165 individual key shape is fairly easy to handle, so I hope I will get
5166 used to it. My old X40 was starting to fail, and I really needed a
5167 new laptop now. :)
</p
>
5169 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
5174 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
5175 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
5176 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
5177 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
5178 <description><p
>It annoys me when the computer fail to do automatically what it is
5179 perfectly capable of, and I have to do it manually to get things
5180 working. One such task is to find out what firmware packages are
5181 needed to get the hardware on my computer working. Most often this
5182 affect the wifi card, but some times it even affect the RAID
5183 controller or the ethernet card. Today I pushed version
0.4 of the
5184 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
5185 including a new script isenkram-autoinstall-firmware handling the
5186 process of asking all the loaded kernel modules what firmware files
5187 they want, find debian packages providing these files and install the
5188 debian packages. Here is a test run on my laptop:
</p
>
5190 <p
><pre
>
5191 # isenkram-autoinstall-firmware
5192 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
5193 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
5194 info: locating packages with the requested firmware files
5195 info: Updating APT sources after adding non-free APT source
5196 info: trying to install firmware-ipw2x00
5199 Preconfiguring packages ...
5200 Selecting previously deselected package firmware-ipw2x00.
5201 (Reading database ...
259727 files and directories currently installed.)
5202 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
5203 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
5205 </pre
></p
>
5207 <p
>When all the requested firmware is present, a simple message is
5208 printed instead:
</p
>
5210 <p
><pre
>
5211 # isenkram-autoinstall-firmware
5212 info: did not find any firmware files requested by loaded kernel modules. exiting
5214 </pre
></p
>
5216 <p
>It could use some polish, but it is already working well and saving
5217 me some time when setting up new machines. :)
</p
>
5219 <p
>So, how does it work? It look at the set of currently loaded
5220 kernel modules, and look up each one of them using modinfo, to find
5221 the firmware files listed in the module meta-information. Next, it
5222 download the Contents file from a nearby APT mirror, and search for
5223 the firmware files in this file to locate the package with the
5224 requested firmware file. If the package is in the non-free section, a
5225 non-free APT source is added and the package is installed using
5226 <tt
>apt-get install
</tt
>. The end result is a slightly better working
5229 <p
>I hope someone find time to implement a more polished version of
5230 this script as part of the hw-detect debian-installer module, to
5231 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
5232 #
655507</a
>. There really is no need to insert USB sticks with
5233 firmware during a PXE install when the packages already are available
5234 from the nearby Debian mirror.
</p
>
5239 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
5240 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
5241 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
5242 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
5243 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
5244 the screen just turn black when Linux boot, either during installation
5245 or on first boot from the hard disk. I
've seen it once in a while the
5246 last few years, but only recently understood the cause. I
've seen it
5247 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
5248 The reason seem to be in the wiring of some laptops. The system to
5249 control the screen background light is inverted, so when Linux try to
5250 turn the brightness fully on, it end up turning it off instead. I do
5251 not know which Linux drivers are affected, but this post is about the
5252 i915 driver used by the
5253 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5254 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
5256 <p
>The problem can be worked around two ways. Either by adding
5257 i915.invert_brightness=
1 as a kernel option, or by adding a file in
5258 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
5259 option when it load the i915 kernel module. On Debian and Ubuntu, it
5260 can be done by running these commands as root:
</p
>
5263 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
5264 update-initramfs -u -k all
5267 <p
>Since March
2012 there is
5268 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
5269 mechanism in the Linux kernel
</a
> to tell the i915 driver which
5270 hardware have this problem, and get the driver to invert the
5271 brightness setting automatically. To use it, one need to add a row in
5272 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
5273 intel_quirks array
</a
> in the driver source
5274 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
5275 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
5276 number (vendor number
8086 is assumed) and subdevice vendor and device
5279 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
5280 -vvnn
</tt
> for the video card in question:
</p
>
5282 <p
><pre
>
5283 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
5284 3rd Gen Core processor Graphics Controller [
8086:
0156] \
5285 (rev
09) (prog-if
00 [VGA controller])
5286 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
5287 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
5288 ParErr- Stepping- SE RR- FastB2B- DisINTx+
5289 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
5290 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
5292 Interrupt: pin A routed to IRQ
42
5293 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
5294 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
5295 Region
4: I/O ports at
4000 [size=
64]
5296 Expansion ROM at
<unassigned
> [disabled]
5297 Capabilities:
<access denied
>
5298 Kernel driver in use: i915
5299 </pre
></p
>
5301 <p
>The resulting intel_quirks entry would then look like this:
</p
>
5303 <p
><pre
>
5304 struct intel_quirk intel_quirks[] = {
5306 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
5307 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
5310 </pre
></p
>
5312 <p
>According to the kernel module instructions (as seen using
5313 <tt
>modinfo i915
</tt
>), information about hardware needing the
5314 invert_brightness flag should be sent to the
5315 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
5316 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
5317 developers. But my email about the laptop sent
2013-
06-
03 have not
5319 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
5320 web archive for the mailing list
</a
>, so I suspect they do not accept
5321 emails from non-subscribers. Because of this, I sent my patch also to
5322 the Debian bug tracking system instead as
5323 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
5324 sure the patch is not lost.
</p
>
5326 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
5327 with this problem working properly with Linux. If you use Gnome, your
5328 worries should be over at this point. But if you use KDE, there is
5329 something in KDE ignoring the invert_brightness setting and turning on
5330 the screen during login. I
've reported it to Debian as
5331 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
5332 have no idea yet how to figure out exactly what subsystem is doing
5333 this. Perhaps you can help? Perhaps you know what the Gnome
5334 developers did to handle this, and this can give a clue to the KDE
5335 developers? Or you know where in KDE the screen brightness is changed
5336 during login? If so, please update the BTS report (or get in touch if
5337 you do not know how to update BTS).
</p
>
5339 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
5340 acpi_backlight=vendor, to disable ACPI backlight support completely,
5341 as the ACPI information on the machine is trash and it is better to
5342 leave it to the intel video driver to control the screen
5343 backlight.
</p
>
5348 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
5349 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
5350 <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>
5351 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
5352 <description><p
>Two days ago, I asked
5353 <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
5354 I could install Linux on a Packard Bell EasyNote LV computer
5355 preinstalled with Windows
8</a
>. I found a solution, but am horrified
5356 with the obstacles put in the way of Linux users on a laptop with UEFI
5357 and Windows
8.
</p
>
5359 <p
>I never found out if the cause of my problems were the use of UEFI
5360 secure booting or fast boot. I suspect fast boot was the problem,
5361 causing the firmware to boot directly from HD without considering any
5362 key presses and alternative devices, but do not know UEFI settings
5363 enough to tell.
</p
>
5365 <p
>There is no way to install Linux on the machine in question without
5366 opening the box and disconnecting the hard drive! This is as far as I
5367 can tell, the only way to get access to the firmware setup menu
5368 without accepting the Windows
8 license agreement. I am told (and
5369 found description on how to) that it is possible to configure the
5370 firmware setup once booted into Windows
8. But as I believe the terms
5371 of that agreement are completely unacceptable, accepting the license
5372 was never an alternative. I do not enter agreements I do not intend
5373 to follow.
</p
>
5375 <p
>I feared I had to return the laptops and ask for a refund, and
5376 waste many hours on this, but luckily there was a way to get it to
5377 work. But I would not recommend it to anyone planning to run Linux on
5378 it, and I have become sceptical to Windows
8 certified laptops. Is
5379 this the way Linux will be forced out of the market place, by making
5380 it close to impossible for
"normal
" users to install Linux without
5381 accepting the Microsoft Windows license terms? Or at least not
5382 without risking to loose the warranty?
</p
>
5384 <p
>I
've updated the
5385 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
5386 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
5387 do not have to struggle as much as I did to get Linux into the
5390 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
5391 Michael Tokarev and others for feedback and ideas.
</p
>
5396 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
5397 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
5398 <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>
5399 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
5400 <description><p
>I
've run into quite a problem the last few days. I bought three
5401 new laptops for my parents and a few others. I bought Packard Bell
5402 Easynote LV to run Kubuntu on and use as their home computer. But I
5403 am completely unable to figure out how to install Linux on it. The
5404 computer is preinstalled with Windows
8, and I suspect it uses UEFI
5405 instead of a BIOS to boot.
</p
>
5407 <p
>The problem is that I am unable to get it to PXE boot, and unable
5408 to get it to boot the Linux installer from my USB stick. I have yet
5409 to try the DVD install, and still hope it will work. when I turn on
5410 the computer, there is no information on what buttons to press to get
5411 the normal boot menu. I expect to get some boot menu to select PXE or
5412 USB stick booting. When booting, it first ask for the language to
5413 use, then for some regional settings, and finally if I will accept the
5414 Windows
8 terms of use. As these terms are completely unacceptable to
5415 me, I have no other choice but to turn off the computer and try again
5416 to get it to boot the Linux installer.
</p
>
5418 <p
>I have gathered my findings so far on a Linlap page about the
5419 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
5420 EasyNote LV
</a
> model. If you have any idea how to get Linux
5421 installed on this machine, please get in touch or update that wiki
5422 page. If I can
't find a way to install Linux, I will have to return
5423 the laptop to the seller and find another machine for my parents.
</p
>
5425 <p
>I wonder, is this the way Linux will be forced out of the market
5426 using UEFI and
"secure boot
" by making it impossible to install Linux
5427 on new Laptops?
</p
>
5432 <title>How to transform a Debian based system to a Debian Edu installation
</title>
5433 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
5434 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
5435 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
5436 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
5437 an operating system based on Debian intended for use in schools. It
5438 contain a turn-key solution for the computer network provided to
5439 pupils in the primary schools. It provide both the central server,
5440 network boot servers and desktop environments with heaps of
5441 educational software. The project was founded almost
12 years ago,
5442 2001-
07-
02. If you want to support the project, which is in need for
5443 cash to fund developer gatherings and other project related activity,
5444 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
5445 donate some money
</a
>.
5447 <p
>A topic that come up again and again on the Debian Edu mailing
5448 lists and elsewhere, is the question on how to transform a Debian or
5449 Ubuntu installation into a Debian Edu installation. It isn
't very
5450 hard, and last week I wrote a script to replicate the steps done by
5451 the Debian Edu installer.
</p
>
5453 <p
>The script,
5454 <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/
>
5455 in the debian-edu-config package, will go through these six steps and
5456 transform an existing Debian Wheezy or Ubuntu (untested) installation
5457 into a Debian Edu Workstation:
</p
>
5461 <li
>Add skolelinux related APT sources.
</li
>
5462 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
5463 <li
>Install debian-edu-install to load preseeding values and pull in
5464 our configuration.
</li
>
5465 <li
>Preseed debconf database with profile setup in
5466 /etc/debian-edu/config, and run tasksel to install packages
5467 according to the profile specified in the config above,
5468 overriding some of the Debian automation machinery.
</li
>
5469 <li
>Run debian-edu-cfengine-D installation to configure everything
5470 that could not be done using preseeding.
</li
>
5471 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
5475 <p
>There are some steps in the Debian Edu installation that can not be
5476 replicated like this. Disk partitioning and LVM setup, for example.
5477 So this script just assume there is enough disk space to install all
5478 the needed packages.
</p
>
5480 <p
>The script was created to help a Debian Edu student working on
5481 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
5482 Debian Edu client, and using it he can take the existing
5483 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
5484 transform it into a fully functioning Debian Edu Workstation (or
5485 Roaming Workstation, or whatever :).
</p
>
5487 <p
>The default setting in the script is to create a KDE Workstation.
5488 If a LXDE based Roaming workstation is wanted instead, modify the
5489 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
5491 <p
><pre
>
5492 PROFILE=
"Roaming-Workstation
"
5493 DESKTOP=
"lxde
"
5494 </pre
></p
>
5496 <p
>The script could even become useful to set up Debian Edu servers in
5497 the cloud, by starting with a virtual Debian installation at some
5498 virtual hosting service and setting up all the services on first
5504 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
5505 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
5506 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
5507 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
5508 <description><P
>In January,
5509 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
5510 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
5511 channel #debian-lego
</a
>, for those of us in the Debian and Linux
5512 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
5513 marvellous construction system from Denmark. We also created
5514 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
5515 a place to take notes and write down our plans and hopes. And several
5516 people showed up to help. I was very happy to see the effect of my
5517 call. Since the small start, we have a debtags tag
5518 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
5519 tag for LEGO related packages, and now count
10 packages related to
5520 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
5522 <p
><table
>
5523 <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
>
5524 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
5525 <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
>
5526 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
5527 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
5528 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
5529 <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
>
5530 <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
>
5531 <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
>
5532 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
5533 </table
></p
>
5535 <p
>Some of these are available in Wheezy, and all but one are
5536 currently available in Jessie/testing. leocad is so far only
5537 available in experimental.
</p
>
5539 <p
>If you care about LEGO in Debian, please join us on IRC and help
5540 adding the rest of the great free software tools available on Linux
5541 for LEGO designers.
</p
>
5546 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
5547 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
5548 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
5549 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
5550 <description><p
>When I woke up this morning, I was very happy to see that the
5551 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
5552 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
5553 Debian release, and I expect to move my machines at home over to it fairly
5556 <p
>The new debian release contain heaps of new stuff, and one program
5557 in particular make me very happy to see included. The
5558 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
5559 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
5560 included for the first time. Alongside similar programs like
5561 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
5562 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
5563 it allow for visual programming where syntax errors can not happen,
5564 and a friendly programming environment for learning to control the
5565 computer. Scratch will also be included in the next release of Debian
5568 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
5569 Edu/Skolelinux release too. The
5570 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
5571 alpha release
</a
> went out last week, and the next should soon
5577 <title>Isenkram
0.2 finally in the Debian archive
</title>
5578 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
5579 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
5580 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
5581 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
5582 package
</a
> finally made it into the archive, after lingering in NEW
5583 for many months. I uploaded it to the Debian experimental suite
5584 2013-
01-
27, and today it was accepted into the archive.
</p
>
5586 <p
>Isenkram is a system for suggesting to users what packages to
5587 install to work with a pluggable hardware device. The suggestion pop
5588 up when the device is plugged in. For example if a Lego Mindstorm NXT
5589 is inserted, it will suggest to install the program needed to program
5590 the NXT controller. Give it a go, and report bugs and suggestions to
5596 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
5597 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
5598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
5599 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
5600 <description><p
>My
5601 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
5602 bitcoin related blog post
</a
> mentioned that the new
5603 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
5604 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
5605 2013-
01-
19, and have been available in unstable since then. It was
5606 automatically copied to Ubuntu, and is available in their Raring
5607 version too.
</p
>
5609 <p
>But there is a strange problem with the build that block this new
5610 version from being available on the i386 and kfreebsd-i386
5611 architectures. For some strange reason, the autobuilders in Debian
5612 for these architectures fail to run the test suite on these
5613 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
5614 We are so far unable to reproduce it when building it manually, and
5615 no-one have been able to propose a fix. If you got an idea what is
5616 failing, please let us know via the BTS.
</p
>
5618 <p
>One feature that is annoying me with of the bitcoin client, because
5619 I often run low on disk space, is the fact that the client will exit
5620 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
5621 #
696715</a
>). So make sure you have enough disk space when you run
5624 <p
>As usual, if you use bitcoin and want to show your support of my
5625 activities, please send Bitcoin donations to my address
5626 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5631 <title>Welcome to the world, Isenkram!
</title>
5632 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
5633 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
5634 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
5635 <description><p
>Yesterday, I
5636 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
5637 for testers
</a
> for my prototype for making Debian better at handling
5638 pluggable hardware devices, which I
5639 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
5640 out to create
</a
> earlier this month. Several valuable testers showed
5641 up, and caused me to really want to to open up the development to more
5642 people. But before I did this, I want to come up with a sensible name
5643 for this project. Today I finally decided on a new name, and I have
5644 renamed the project from hw-support-handler to this new name. In the
5645 process, I moved the source to git and made it available as a
5646 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
5647 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
5648 To fetch and build the latest version of the source, use
</p
>
5651 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
5652 cd isenkram
&& git-buildpackage -us -uc
5655 <p
>I have not yet adjusted all files to use the new name yet. If you
5656 want to hack on the source or improve the package, please go ahead.
5657 But please talk to me first on IRC or via email before you do major
5658 changes, to make sure we do not step on each others toes. :)
</p
>
5660 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
5661 stuff, typically meaning tools, nails, screws, etc. Typical hardware
5662 stuff, in other words. I
've been told it is the Norwegian variant of
5663 the German word eisenkram, for those that are familiar with that
5666 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
5667 instructions, to avoid confusing people with an error from the signing
5670 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
5671 clone argument to avoid the need for authentication.
</p
>
5676 <title>First prototype ready making hardware easier to use in Debian
</title>
5677 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
5678 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
5679 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
5680 <description><p
>Early this month I set out to try to
5681 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
5682 the Debian support for pluggable hardware devices
</a
>. Now my
5683 prototype is working, and it is ready for a larger audience. To test
5685 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
5686 from the Debian Edu subversion repository
</a
>, build and install the
5687 package. You might have to log out and in again activate the
5688 autostart script.
</p
>
5690 <p
>The design is simple:
</p
>
5694 <li
>Add desktop entry in /usr/share/autostart/ causing a program
5695 hw-support-handlerd to start when the user log in.
</li
>
5697 <li
>This program listen for kernel events about new hardware (directly
5698 from the kernel like udev does), not using HAL dbus events as I
5699 initially did.
</li
>
5701 <li
>When new hardware is inserted, look up the hardware modalias in
5702 the APT database, a database
5703 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
5704 via HTTP
</a
> and a database available as part of the package.
</li
>
5706 <li
>If a package is mapped to the hardware in question, the package
5707 isn
't installed yet and this is the first time the hardware was
5708 plugged in, show a desktop notification suggesting to install the
5709 package or packages.
</li
>
5711 <li
>If the user click on the
'install package now
' button, ask
5712 aptdaemon via the PackageKit API to install the requrired package.
</li
>
5714 <li
>aptdaemon ask for root password or sudo password, and install the
5715 package while showing progress information in a window.
</li
>
5719 <p
>I still need to come up with a better name for the system. Here
5720 are some screen shots showing the prototype in action. First the
5721 notification, then the password request, and finally the request to
5722 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
5724 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
5725 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
5726 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
5727 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
5728 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
5730 <p
>The prototype still need to be improved with longer timeouts, but
5731 is already useful. The database of hardware to package mappings also
5732 need more work. It is currently compatible with the Ubuntu way of
5733 storing such information in the package control file, but could be
5734 changed to use other formats instead or in addition to the current
5735 method. I
've dropped the use of discover for this mapping, as the
5736 modalias approach is more flexible and easier to use on Linux as long
5737 as the Linux kernel expose its modalias strings directly.
</p
>
5739 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
5740 here is the command required to check out and build the source: Use
5741 '<tt
>svn checkout
5742 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
5743 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
5744 devscripts package.
</p
>
5746 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
5747 renamed to Isenkram and the source moved from the Debian Edu
5748 subversion repository to a Debian collab-maint git repository. See
5749 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
5750 instructions
</a
> for details.
</p
>
5755 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
5756 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
5757 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
5758 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
5759 <description><p
>This Christmas my trusty old laptop died. It died quietly and
5760 suddenly in bed. With a quiet whimper, it went completely quiet and
5761 black. The power button was no longer able to turn it on. It was a
5762 IBM Thinkpad X41, and the best laptop I ever had. Better than both
5763 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
5764 Compaq I had before that. Now I need to find a replacement. To keep
5765 going during Christmas, I moved the one year old SSD disk to my old
5766 X40 where it fitted (only one I had left that could use it), but it is
5767 not a durable solution.
5769 <p
>My laptop needs are fairly modest. This is my wishlist from when I
5770 got a new one more than
10 years ago. It still holds true.:)
</p
>
5774 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
5775 than A4).
</li
>
5776 <li
>Robust, it will be in my backpack every day.
</li
>
5777 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
5778 <li
>Long battery life time. Preferable a week.
</li
>
5779 <li
>Internal WIFI network card.
</li
>
5780 <li
>Internal Twisted Pair network card.
</li
>
5781 <li
>Some USB slots (
2-
3 is plenty)
</li
>
5782 <li
>Good keyboard - similar to the Thinkpad.
</li
>
5783 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
5785 <li
>Hardware supported by Debian Stable, ie the default kernel and
5786 X.org packages.
</li
>
5787 <li
>Quiet, preferably fan free (or at least not using the fan most of
5792 <p
>You will notice that there are no RAM and CPU requirements in the
5793 list. The reason is simply that the specifications on laptops the
5794 last
10-
15 years have been sufficient for my needs, and I have to look
5795 at other features to choose my laptop. But are there still made as
5796 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
5797 robust, and Thinkpads seem to be heading in the wrong direction since
5798 Lenovo took over. But I
've been told that X220 and X1 Carbon might
5799 still be useful.
</p
>
5801 <p
>Perhaps I should rethink my needs, and look for a pad with an
5802 external keyboard? I
'll have to check the
5803 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
5804 well-supported laptops, or perhaps just buy one preinstalled from one
5805 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
5806 Pre-loaded site
</a
>.
</p
>
5811 <title>How to find a browser plugin supporting a given MIME type
</title>
5812 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
5813 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
5814 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
5815 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
5816 install to get support for a given MIME type. Thanks to
5817 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
5818 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
5819 Unfortunately, not very many packages provide the needed meta
5820 information, Anyway, here is a small script to look up all browser
5821 plugin packages announcing ther MIME support using this specification:
</p
>
5827 def pkgs_handling_mimetype(mimetype):
5832 version = pkg.candidate
5834 version = pkg.installed
5837 record = version.record
5838 if not record.has_key(
'Npp-MimeType
'):
5840 mime_types = record[
'Npp-MimeType
'].split(
',
')
5841 for t in mime_types:
5842 t = t.rstrip().strip()
5844 thepkgs.append(pkg.name)
5846 mimetype =
"audio/ogg
"
5847 if
1 < len(sys.argv):
5848 mimetype = sys.argv[
1]
5849 print
"Browser plugin packages supporting %s:
" % mimetype
5850 for pkg in pkgs_handling_mimetype(mimetype):
5851 print
" %s
" %pkg
5854 <p
>It can be used like this to look up a given MIME type:
</p
>
5857 % ./apt-find-browserplug-for-mimetype
5858 Browser plugin packages supporting audio/ogg:
5860 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
5861 Browser plugin packages supporting application/x-shockwave-flash:
5862 browser-plugin-gnash
5866 <p
>In Ubuntu this mechanism is combined with support in the browser
5867 itself to query for plugins and propose to install the needed
5868 packages. It would be great if Debian supported such feature too. Is
5869 anyone working on adding it?
</p
>
5871 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
5872 request for icweasel support for this feature is
5873 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
5874 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
5875 of manpower and wish for a different design is the reason thus feature
5876 is not yet in iceweasel from Debian.
</p
>
5881 <title>What is the most supported MIME type in Debian?
</title>
5882 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
5883 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
5884 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
5885 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
5886 proposal to add AppStream information to the Debian archive
</a
>, is a
5887 proposal to make it possible for a Desktop application to propose to
5888 the user some package to install to gain support for a given MIME
5889 type, font, library etc. that is currently missing. With such
5890 mechanism in place, it would be possible for the desktop to
5891 automatically propose and install leocad if some LDraw file is
5892 downloaded by the browser.
</p
>
5894 <p
>To get some idea about the current content of the archive, I decided
5895 to write a simple program to extract all .desktop files from the
5896 Debian archive and look up the claimed MIME support there. The result
5898 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
5899 site
</a
>. Using the collected information, it become possible to
5900 answer the question in the title. Here are the
20 most supported MIME
5901 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
5902 The complete list is available from the link above.
</p
>
5904 <p
><strong
>Debian Stable:
</strong
></p
>
5908 ----- -----------------------
5924 18 application/x-ogg
5931 <p
><strong
>Debian Testing:
</strong
></p
>
5935 ----- -----------------------
5951 18 application/x-ogg
5958 <p
><strong
>Debian Unstable:
</strong
></p
>
5962 ----- -----------------------
5979 18 application/x-ogg
5985 <p
>I am told that PackageKit can provide an API to access the kind of
5986 information mentioned in DEP-
11. I have not yet had time to look at
5987 it, but hope the PackageKit people in Debian are on top of these
5990 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
5991 discovering a typo in my script.
</p
>
5996 <title>Using modalias info to find packages handling my hardware
</title>
5997 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
5998 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
5999 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
6000 <description><p
>Yesterday, I wrote about the
6001 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
6002 values provided by the Linux kernel
</a
> following my hope for
6003 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
6004 dongle support in Debian
</a
>. Using this knowledge, I have tested how
6005 modalias values attached to package names can be used to map packages
6006 to hardware. This allow the system to look up and suggest relevant
6007 packages when I plug in some new hardware into my machine, and replace
6008 discover and discover-data as the database used to map hardware to
6011 <p
>I create a modaliases file with entries like the following,
6012 containing package name, kernel module name (if relevant, otherwise
6013 the package name) and globs matching the relevant hardware
6016 <p
><blockquote
>
6017 Package: package-name
6018 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
6019 </blockquote
></p
>
6021 <p
>It is fairly trivial to write code to find the relevant packages
6022 for a given modalias value using this file.
</p
>
6024 <p
>An entry like this would suggest the video and picture application
6025 cheese for many USB web cameras (interface bus class
0E01):
</p
>
6027 <p
><blockquote
>
6029 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
6030 </blockquote
></p
>
6032 <p
>An entry like this would suggest the pcmciautils package when a
6033 CardBus bridge (bus class
0607) PCI device is present:
</p
>
6035 <p
><blockquote
>
6036 Package: pcmciautils
6037 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
6038 </blockquote
></p
>
6040 <p
>An entry like this would suggest the package colorhug-client when
6041 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
6043 <p
><blockquote
>
6044 Package: colorhug-client
6045 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
6046 </blockquote
></p
>
6048 <p
>I believe the format is compatible with the format of the Packages
6049 file in the Debian archive. Ubuntu already uses their Packages file
6050 to store their mappings from packages to hardware.
</p
>
6052 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
6053 announce the hardware it support in a way my prototype understand.
6054 This allow those publishing packages in an APT source outside the
6055 Debian archive as well as those backporting packages to make sure the
6056 hardware mapping are included in the package meta information. I
've
6057 tested such header in the pymissile package, and its modalias mapping
6058 is working as it should with my prototype. It even made it to Ubuntu
6061 <p
>To test if it was possible to look up supported hardware using only
6062 the shell tools available in the Debian installer, I wrote a shell
6063 implementation of the lookup code. The idea is to create files for
6064 each modalias and let the shell do the matching. Please check out and
6066 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
6067 shell script. It run without any extra dependencies and fetch the
6068 hardware mappings from the Debian archive and the subversion
6069 repository where I currently work on my prototype.
</p
>
6071 <p
>When I use it on a machine with a yubikey inserted, it suggest to
6072 install yubikey-personalization:
</p
>
6074 <p
><blockquote
>
6075 % ./hw-support-lookup
6076 <br
>yubikey-personalization
6078 </blockquote
></p
>
6080 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
6081 propose to install the pcmciautils package:
</p
>
6083 <p
><blockquote
>
6084 % ./hw-support-lookup
6085 <br
>pcmciautils
6087 </blockquote
></p
>
6089 <p
>If you know of any hardware-package mapping that should be added to
6090 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
6091 database
</a
>, please tell me about it.
</p
>
6093 <p
>It could be possible to generate several of the mappings between
6094 packages and hardware. One source would be to look at packages with
6095 kernel modules, ie packages with *.ko files in /lib/modules/, and
6096 extract their modalias information. Another would be to look at
6097 packages with udev rules, ie packages with files in
6098 /lib/udev/rules.d/, and extract their vendor/model information to
6099 generate a modalias matching rule. I have not tested any of these to
6100 see if it work.
</p
>
6102 <p
>If you want to help implementing a system to let us propose what
6103 packages to install when new hardware is plugged into a Debian
6104 machine, please send me an email or talk to me on
6105 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6110 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
6111 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
6112 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
6113 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
6114 <description><p
>While looking into how to look up Debian packages based on hardware
6115 information, to find the packages that support a given piece of
6116 hardware, I refreshed my memory regarding modalias values, and decided
6117 to document the details. Here are my findings so far, also available
6119 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6120 Debian Edu subversion repository
</a
>:
6122 <p
><strong
>Modalias decoded
</strong
></p
>
6124 <p
>This document try to explain what the different types of modalias
6125 values stands for. It is in part based on information from
6126 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
6127 &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;,
6128 &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
6129 &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;.
6131 <p
>The modalias entries for a given Linux machine can be found using
6132 this shell script:
</p
>
6135 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
6138 <p
>The supported modalias globs for a given kernel module can be found
6139 using modinfo:
</p
>
6142 % /sbin/modinfo psmouse | grep alias:
6143 alias: serio:ty05pr*id*ex*
6144 alias: serio:ty01pr*id*ex*
6148 <p
><strong
>PCI subtype
</strong
></p
>
6150 <p
>A typical PCI entry can look like this. This is an Intel Host
6151 Bridge memory controller:
</p
>
6153 <p
><blockquote
>
6154 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
6155 </blockquote
></p
>
6157 <p
>This represent these values:
</p
>
6162 sv
00001028 (subvendor)
6163 sd
000001AD (subdevice)
6165 sc
00 (bus subclass)
6169 <p
>The vendor/device values are the same values outputted from
'lspci
6170 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
6171 0600. The
0600 class is a host bridge. Other useful bus values are
6172 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
6174 <p
>Not sure how to figure out the interface value, nor what it
6177 <p
><strong
>USB subtype
</strong
></p
>
6179 <p
>Some typical USB entries can look like this. This is an internal
6180 USB hub in a laptop:
</p
>
6182 <p
><blockquote
>
6183 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
6184 </blockquote
></p
>
6186 <p
>Here is the values included in this alias:
</p
>
6189 v
1D6B (device vendor)
6190 p
0001 (device product)
6192 dc
09 (device class)
6193 dsc
00 (device subclass)
6194 dp
00 (device protocol)
6195 ic
09 (interface class)
6196 isc
00 (interface subclass)
6197 ip
00 (interface protocol)
6200 <p
>The
0900 device class/subclass means hub. Some times the relevant
6201 class is in the interface class section. For a simple USB web camera,
6202 these alias entries show up:
</p
>
6204 <p
><blockquote
>
6205 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
6206 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
6207 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
6208 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
6209 </blockquote
></p
>
6211 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
6212 camera),
0101 is audio control device and
0102 is audio streaming (aka
6213 microphone). Thus this is a camera with microphone included.
</p
>
6215 <p
><strong
>ACPI subtype
</strong
></p
>
6217 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
6218 receiver in a Thinkpad X40:
</p
>
6220 <p
><blockquote
>
6221 acpi:IBM0071:PNP0511:
6222 </blockquote
></p
>
6224 <p
>The values between the colons are IDs.
</p
>
6226 <p
><strong
>DMI subtype
</strong
></p
>
6228 <p
>The DMI table contain lots of information about the computer case
6229 and model. This is an entry for a IBM Thinkpad X40, fetched from
6230 /sys/devices/virtual/dmi/id/modalias:
</p
>
6232 <p
><blockquote
>
6233 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
6234 </blockquote
></p
>
6236 <p
>The values present are
</p
>
6239 bvn IBM (BIOS vendor)
6240 bvr
1UETB
6WW(
1.66) (BIOS version)
6241 bd
06/
15/
2005 (BIOS date)
6242 svn IBM (system vendor)
6243 pn
2371H4G (product name)
6244 pvr ThinkPadX40 (product version)
6245 rvn IBM (board vendor)
6246 rn
2371H4G (board name)
6247 rvr NotAvailable (board version)
6248 cvn IBM (chassis vendor)
6249 ct
10 (chassis type)
6250 cvr NotAvailable (chassis version)
6253 <p
>The chassis type
10 is Notebook. Other interesting values can be
6254 found in the dmidecode source:
</p
>
6258 4 Low Profile Desktop
6271 17 Main Server Chassis
6272 18 Expansion Chassis
6274 20 Bus Expansion Chassis
6275 21 Peripheral Chassis
6277 23 Rack Mount Chassis
6286 <p
>The chassis type values are not always accurately set in the DMI
6287 table. For example my home server is a tower, but the DMI modalias
6288 claim it is a desktop.
</p
>
6290 <p
><strong
>SerIO subtype
</strong
></p
>
6292 <p
>This type is used for PS/
2 mouse plugs. One example is from my
6293 test machine:
</p
>
6295 <p
><blockquote
>
6296 serio:ty01pr00id00ex00
6297 </blockquote
></p
>
6299 <p
>The values present are
</p
>
6308 <p
>This type is supported by the psmouse driver. I am not sure what
6309 the valid values are.
</p
>
6311 <p
><strong
>Other subtypes
</strong
></p
>
6313 <p
>There are heaps of other modalias subtypes according to
6314 file2alias.c. There is the rest of the list from that source: amba,
6315 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
6316 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
6317 vmbus, x86cpu and zorro. I did not spend time documenting all of
6318 these, as they do not seem relevant for my intended use with mapping
6319 hardware to packages when new stuff is inserted during run time.
</p
>
6321 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
6323 <p
>To check which kernel modules provide support for a given modalias,
6324 one can use the following shell script:
</p
>
6327 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
6328 echo
"$id
" ; \
6329 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
6333 <p
>The output can look like this (only the first few entries as the
6334 list is very long on my test machine):
</p
>
6338 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
6340 FATAL: Module acpi:device: not found.
6342 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
6343 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
6344 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
6345 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
6346 acpi:IBM0071:PNP0511:
6347 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
6348 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
6349 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
6353 <p
>If you want to help implementing a system to let us propose what
6354 packages to install when new hardware is plugged into a Debian
6355 machine, please send me an email or talk to me on
6356 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
6358 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
6359 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
6360 in /sys/ with space in them.
</p
>
6365 <title>Moved the pymissile Debian packaging to collab-maint
</title>
6366 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
6367 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
6368 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
6369 <description><p
>As part of my investigation on how to improve the support in Debian
6370 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
6371 Launcher and updated the Debian package
6372 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
6373 sure udev will fix the device permissions when it is plugged in. I
6374 also added a
"Modaliases
" header to test it in the Debian archive and
6375 hopefully make the package be proposed by jockey in Ubuntu when a user
6376 plug in his rocket launcher. In the process I moved the source to a
6377 git repository under collab-maint, to make it easier for any DD to
6378 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
6379 is not very active, but the software still work for me even after five
6380 years of relative silence. The new git repository is not listed in
6381 the uploaded package yet, because I want to test the other changes a
6382 bit more before I upload the new version. If you want to check out
6383 the new version with a .desktop file included, visit the
6384 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
6385 view
</a
> or use
"<tt
>git clone
6386 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
6391 <title>Lets make hardware dongles easier to use in Debian
</title>
6392 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
6393 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
6394 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
6395 <description><p
>One thing that annoys me with Debian and Linux distributions in
6396 general, is that there is a great package management system with the
6397 ability to automatically install software packages by downloading them
6398 from the distribution mirrors, but no way to get it to automatically
6399 install the packages I need to use the hardware I plug into my
6400 machine. Even if the package to use it is easily available from the
6401 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
6402 suggest to automatically install the python-nxt, nbc and t2n packages
6403 I need to talk to it. When I plug in a Yubikey, it could propose the
6404 yubikey-personalization package. The information required to do this
6405 is available, but no-one have pulled all the pieces together.
</p
>
6407 <p
>Some years ago, I proposed to
6408 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
6409 the discover subsystem to implement this
</a
>. The idea is fairly
6414 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
6415 starting when a user log in.
</li
>
6417 <li
>Set this program up to listen for kernel events emitted when new
6418 hardware is inserted into the computer.
</li
>
6420 <li
>When new hardware is inserted, look up the hardware ID in a
6421 database mapping to packages, and take note of any non-installed
6422 packages.
</li
>
6424 <li
>Show a message to the user proposing to install the discovered
6425 package, and make it easy to install it.
</li
>
6429 <p
>I am not sure what the best way to implement this is, but my
6430 initial idea was to use dbus events to discover new hardware, the
6431 discover database to find packages and
6432 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
6435 <p
>Yesterday, I found time to try to implement this idea, and the
6436 draft package is now checked into
6437 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
6438 Debian Edu subversion repository
</a
>. In the process, I updated the
6439 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
6440 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
6441 the relevant packages in Debian, and uploaded a new version
6442 2.2013.01.09 to unstable. I also discovered that the current
6443 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
6444 package in Debian no longer discovered any USB devices, because
6445 /proc/bus/usb/devices is no longer present. I ported it to use
6446 libusb as a fall back option to get it working. The fixed package
6447 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
6448 because of the freeze).
</p
>
6450 <p
>With this prototype in place, I can insert my Yubikey, and get this
6451 desktop notification to show up (only once, the first time it is
6452 inserted):
</p
>
6454 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
6456 <p
>For this prototype to be really useful, some way to automatically
6457 install the proposed packages by pressing the
"Please install
6458 program(s)
" button should to be implemented.
</p
>
6460 <p
>If this idea seem useful to you, and you want to help make it
6461 happen, please help me update the discover-data database with mappings
6462 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
6463 list the package you would like to have installed when a given
6464 hardware device is inserted into your computer, and report bugs using
6465 reportbug if it isn
't. Or, if you know of a better way to provide
6466 such mapping, please let me know.
</p
>
6468 <p
>This prototype need more work, and there are several questions that
6469 should be considered before it is ready for production use. Is dbus
6470 the correct way to detect new hardware? At the moment I look for HAL
6471 dbus events on the system bus, because that is the events I could see
6472 on my Debian Squeeze KDE desktop. Are there better events to use?
6473 How should the user be notified? Is the desktop notification
6474 mechanism the best option, or should the background daemon raise a
6475 popup instead? How should packages be installed? When should they
6476 not be installed?
</p
>
6478 <p
>If you want to help getting such feature implemented in Debian,
6479 please send me an email. :)
</p
>
6484 <title>New IRC channel for LEGO designers using Debian
</title>
6485 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
6486 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
6487 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
6488 <description><p
>During Christmas, I have worked a bit on the Debian support for
6489 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
6490 NXT
</a
>. My son and I have played a bit with my NXT set, and I
6491 discovered I had to build all the tools myself because none were
6492 already in Debian Squeeze. If Debian support for LEGO is something
6493 you care about, please join me on the IRC channel
6494 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
6495 irc.debian.org). There is a lot that could be done to improve the
6496 Debian support for LEGO designers. For example both CAD software
6497 and Mindstorm compilers are missing. :)
</p
>
6499 <p
>Update
2012-
01-
03: A
6500 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
6501 including links to Lego related packages is now available.
</p
>
6506 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
6507 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
6508 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
6509 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
6510 <description><p
>Let me start by wishing you all marry Christmas and a happy new
6511 year! I hope next year will prove to be a good year.
</p
>
6513 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
6514 decentralised
"currency
" that allow people to transfer bitcoins
6515 between each other with minimal overhead, is a very interesting
6516 experiment. And as I wrote a few days ago, the bitcoin situation in
6517 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
6518 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
6519 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
6520 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
6521 for one of the ftpmasters to approve the new bitcoin-qt package
6524 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
6525 team in Debian, you can easily test the package in Debian Squeeze
6526 using the following steps to get a set of working packages:
</p
>
6528 <blockquote
><pre
>
6529 git clone git://git.debian.org/git/collab-maint/bitcoin
6531 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
6532 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
6533 </pre
></blockquote
>
6535 <p
>You might have to install some build dependencies as well. The
6536 list of commands should give you two packages, bitcoind and
6537 bitcoin-qt, ready for use in a Squeeze environment. Note that the
6538 client will download the complete set of bitcoin
"blocks
", which need
6539 around
5.6 GiB of data on my machine at the moment. Make sure your
6540 ~/.bitcoin/ directory have lots of spare room if you want to download
6541 all the blocks. The client will warn if the disk is getting full, so
6542 there is not really a problem if you got too little room, but you will
6543 not be able to get all the features out of the client.
</p
>
6545 <p
>As usual, if you use bitcoin and want to show your support of my
6546 activities, please send Bitcoin donations to my address
6547 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6552 <title>A word on bitcoin support in Debian
</title>
6553 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
6554 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
6555 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
6556 <description><p
>It has been a while since I wrote about
6557 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
6558 peer-to-peer based crypto-currency, and the reason is simply that I
6559 have been busy elsewhere. But two days ago, I started looking at the
6560 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
6561 Debian
</a
> again to try to recover my old bitcoin wallet. The package
6562 is now maintained by a
6563 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
6564 people
</a
>, and the grunt work had already been done by this team. We
6565 owe a huge thank you to all these team members. :)
6566 But I was sad to discover that the bitcoin client is missing in
6567 Wheezy. It is only available in Sid (and an outdated client from
6568 backports). The client had several RC bugs registered in BTS blocking
6569 it from entering testing. To try to help the team and improve the
6570 situation, I spent some time providing patches and triaging the bug
6571 reports. I also had a look at the bitcoin package available from Matt
6573 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
6574 Ubuntu
</a
>, and moved the useful pieces from that version into the
6575 Debian package.
</p
>
6577 <p
>After checking with the main package maintainer Jonas Smedegaard on
6578 IRC, I pushed several patches into the collab-maint git repository to
6579 improve the package. It now contains fixes for the RC issues (not from
6580 me, but fixed by Scott Howard), build rules for a Qt GUI client
6581 package, konqueror support for the bitcoin: URI and bash completion
6582 setup. As I work on Debian Squeeze, I also created
6583 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
6584 patch to backport
</a
> the latest version. Jonas is going to look at
6585 it and try to integrate it into the git repository before uploading a
6586 new version to unstable.
6588 <p
>I would very much like bitcoin to succeed, to get rid of the
6589 centralized control currently exercised in the monetary system. I
6590 find it completely unacceptable that the USA government is collecting
6591 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
6592 that the major credit card companies can block legal money
6593 transactions to Wikileaks. But for bitcoin to succeed, more people
6594 need to use bitcoins, and more people need to accept bitcoins when
6595 they sell products and services. Improving the bitcoin support in
6596 Debian is a small step in the right direction, but not enough.
6597 Unfortunately the user experience when browsing the web and wanting to
6598 pay with bitcoin is still not very good. The bitcoin: URI is a step
6599 in the right direction, but need to work in most or every browser in
6600 use. Also the bitcoin-qt client is too heavy to fire up to do a
6601 quick transaction. I believe there are other clients available, but
6602 have not tested them.
</p
>
6605 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
6606 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
6607 I received
20.15 BTC so far on the address I provided in my blog two
6608 years ago, as can be
6609 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
6610 on the blockexplorer service
</a
>. Thank you everyone for your
6611 donation. The blockexplorer service demonstrates quite well that
6612 bitcoin is not quite anonymous and untracked. :) I wonder if the
6613 number of users have gone up since then. If you use bitcoin and want
6614 to show your support of my activity, please send Bitcoin donations to
6615 the same address as last time,
6616 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6621 <title>Git repository for song book for Computer Scientists
</title>
6622 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
6623 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
6624 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
6625 <description><p
>As I
6626 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
6627 this summer
</a
>, I have created a Computer Science song book a few
6628 years ago, and today I finally found time to create a public
6629 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
6630 repository for the project
</a
>.
</p
>
6632 <p
>If you want to help out, please clone the source and submit patches
6633 to the HTML version. To generate the PDF and PostScript version,
6634 please use prince XML, or let me know about a useful free software
6635 processor capable of creating a good looking PDF from the HTML.
</p
>
6637 <p
>Want to sing? You can still find the song book in HTML, PDF and
6638 PostScript formats at
6639 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
6640 Science Songbook
</a
>.
</p
>
6645 <title>Gratulerer med
19-årsdagen, Debian!
</title>
6646 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
6647 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
6648 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
6649 <description><p
>I dag fyller
6650 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
6651 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
6652 si gratulerer med dagen, Debian!
</p
>
6657 <title>Song book for Computer Scientists
</title>
6658 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
6659 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
6660 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
6661 <description><p
>Many years ago, while studying Computer Science at the
6662 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
6663 collecting computer related songs for use at parties. The original
6664 version was written in LaTeX, but a few years ago I got help from
6665 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
6666 while keeping the ability to create a nice book in PDF format. I have
6667 not had time to maintain the book for a while now, and guess I should
6668 put it up on some public version control repository where others can
6669 help me extend and update the book. If anyone is volunteering to help
6670 me with this, send me an email. Also let me know if there are songs
6671 missing in my book.
</p
>
6673 <p
>I have not mentioned the book on my blog so far, and it occured to
6674 me today that I really should let all my readers share the joys of
6675 singing out load about programming, computers and computer networks.
6676 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
6677 12</a
> is about to start (and I am not going). Want to sing? Check
6678 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
6679 Computer Science Songbook
</a
>.
6684 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
6685 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
6686 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
6687 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
6688 <description><p
>At work we have heaps of servers. I believe the total count is
6689 around
1000 at the moment. To be able to get help from the vendors
6690 when something go wrong, we want to keep the firmware on the servers
6691 up to date. If the firmware isn
't the latest and greatest, the
6692 vendors typically refuse to start debugging any problems until the
6693 firmware is upgraded. So before every reboot, we want to upgrade the
6694 firmware, and we would really like everyone handling servers at the
6695 university to do this themselves when they plan to reboot a machine.
6696 For that to happen we at the unix server admin group need to provide
6697 the tools to do so.
</p
>
6699 <p
>To make firmware upgrading easier, I am working on a script to
6700 fetch and install the latest firmware for the servers we got. Most of
6701 our hardware are from Dell and HP, so I have focused on these servers
6702 so far. This blog post is about the Dell part.
</P
>
6704 <p
>On the Dell FTP site I was lucky enough to find
6705 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
6706 with firmware information for all
11th generation servers, listing
6707 which firmware should be used on a given model and where on the FTP
6708 site I can find it. Using a simple perl XML parser I can then
6709 download the shell scripts Dell provides to do firmware upgrades from
6710 within Linux and reboot when all the firmware is primed and ready to
6711 be activated on the first reboot.
</p
>
6713 <p
>This is the Dell related fragment of the perl code I am working on.
6714 Are there anyone working on similar tools for firmware upgrading all
6715 servers at a site? Please get in touch and lets share resources.
</p
>
6717 <p
><pre
>
6721 use File::Temp qw(tempdir);
6723 # Install needed RHEL packages if missing
6725 'XML::Simple
' =
> 'perl-XML-Simple
',
6727 for my $module (keys %rhelmodules) {
6728 eval
"use $module;
";
6730 my $pkg = $rhelmodules{$module};
6731 system(
"yum install -y $pkg
");
6732 eval
"use $module;
";
6736 my $errorsto =
'pere@hungry.com
';
6742 sub run_firmware_script {
6743 my ($opts, $script) = @_;
6745 print STDERR
"fail: missing script name\n
";
6748 print STDERR
"Running $script\n\n
";
6750 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
6751 print STDERR
"success: firmware script ran succcessfully\n
";
6753 print STDERR
"fail: firmware script returned error\n
";
6757 sub run_firmware_scripts {
6758 my ($opts, @dirs) = @_;
6759 # Run firmware packages
6760 for my $dir (@dirs) {
6761 print STDERR
"info: Running scripts in $dir\n
";
6762 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
6763 while (my $s = readdir $dh) {
6764 next if $s =~ m/^\.\.?/;
6765 run_firmware_script($opts,
"$dir/$s
");
6773 print STDERR
"info: Downloading $url\n
";
6774 system(
"wget --quiet \
"$url\
"");
6779 my $product = `dmidecode -s system-product-name`;
6782 if ($product =~ m/PowerEdge/) {
6784 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
6785 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
6787 my $tmpdir = tempdir(
6791 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
6792 system(
'gunzip Catalog.xml.gz
');
6793 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
6794 # -q is quiet, disabling interactivity and reducing console output
6795 my $fwopts =
"-q
";
6797 for my $url (@paths) {
6798 fetch_dell_fw($url);
6800 run_firmware_scripts($fwopts, $tmpdir);
6802 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6803 print STDERR
"error: Please report to $errorsto.\n
";
6807 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
6808 print STDERR
"error: Please report to $errorsto.\n
";
6814 my $url =
"ftp://ftp.us.dell.com/$path
";
6818 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
6819 # firmware packages to download from Dell. Only work for Linux
6820 # machines and
11th generation Dell servers.
6821 sub fetch_dell_fw_list {
6822 my $filename = shift;
6824 my $product = `dmidecode -s system-product-name`;
6826 my ($mybrand, $mymodel) = split(/\s+/, $product);
6828 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
6830 my $xml = XMLin($filename);
6832 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
6833 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
6834 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
6836 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
6837 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
6839 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
6841 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
6843 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
6846 for my $component (@{$xml-
>{SoftwareComponent}}) {
6847 my $componenttype = $component-
>{ComponentType}-
>{value};
6849 # Drop application packages, only firmware and BIOS
6850 next if
'APAC
' eq $componenttype;
6852 my $cpath = $component-
>{path};
6853 for my $path (@paths) {
6854 if ($cpath =~ m%/$path$%) {
6855 push(@paths, $cpath);
6863 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
6864 it could work on other platforms with some tweaking. Anyone know a
6865 index like Catalog.xml is available from HP for HP servers? At the
6866 moment I maintain a similar list manually and it is quickly getting
6872 <title>How is booting into runlevel
1 different from single user boots?
</title>
6873 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
6874 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
6875 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
6876 <description><p
>Wouter Verhelst have some
6877 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
6878 comments and opinions
</a
> on my blog post on
6879 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
6880 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
6881 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
6882 default KDE desktop in Debian
</a
>. I only have time to address one
6883 small piece of his comment now, and though it best to address the
6884 misunderstanding he bring forward:
</p
>
6886 <p
><blockquote
>
6887 Currently, a system admin has four options: [...] boot to a
6888 single-user system (by adding
'single
' to the kernel command line;
6889 this runs rcS and rc1 scripts)
6890 </blockquote
></p
>
6892 <p
>This make me believe Wouter believe booting into single user mode
6893 and booting into runlevel
1 is the same. I am not surprised he
6894 believe this, because it would make sense and is a quite sensible
6895 thing to believe. But because the boot in Debian is slightly broken,
6896 runlevel
1 do not work properly and it isn
't the same as single user
6897 mode. I
'll try to explain what is actually happing, but it is a bit
6898 hard to explain.
</p
>
6900 <p
>Single user mode is defined like this in /etc/inittab:
6901 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
6902 executed in single user mode is sulogin. Single user mode is a boot
6903 state
"between
" the runlevels, and when booting into single user mode,
6904 only the scripts in /etc/rcS.d/ are executed before the init process
6905 enters the single user state. When switching to runlevel
1, the state
6906 is in fact not ending in runlevel
1, but it passes through runlevel
1
6907 and end up in the single user mode (see /etc/rc1.d/S03single, which
6908 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
6909 1. It is confusing that the
'S
' (single user) init mode is not the
6910 mode enabled by /etc/rcS.d/ (which is more like the initial boot
6913 <p
>This summary might make it clearer. When booting for the first
6914 time into single user mode, the following commands are executed:
6915 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
6916 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
6917 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
6918 trying to continue after visiting single user mode. Not all services
6919 are started again as they should, causing the machine to end up in an
6920 unpredicatble state. This is why Debian admins recommend rebooting
6921 after visiting single user mode.
</p
>
6923 <p
>A similar problem with runlevel
1 is caused by the amount of
6924 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
6925 to runlevel
1, the services started from /etc/rcS.d/ are not properly
6926 stopped when passing through the scripts in /etc/rc1.d/, and not
6927 started again when switching away from runlevel
1 to the runlevels
6928 2-
5. I believe the problem is best fixed by moving all the scripts
6929 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
6930 functioning single user mode during boot.
</p
>
6932 <p
>I have spent several years investigating the Debian boot system,
6933 and discovered this problem a few years ago. I suspect it originates
6934 from when sysvinit was introduced into Debian, a long time ago.
</p
>
6939 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
6940 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
6941 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
6942 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
6943 <description><p
>In the Debian boot system, several packages include scripts that
6944 are started from /etc/rcS.d/. In fact, there is a bite more of them
6945 than make sense, and this causes a few problems. What kind of
6946 problems, you might ask. There are at least two problems. The first
6947 is that it is not possible to recover a machine after switching to
6948 runlevel
1. One need to actually reboot to get the machine back to
6949 the expected state. The other is that single user boot will sometimes
6950 run into problems because some of the subsystems are activated before
6951 the root login is presented, causing problems when trying to recover a
6952 machine from a problem in that subsystem. A minor additional point is
6953 that moving more scripts out of rcS.d/ and into the other rc#.d/
6954 directories will increase the amount of scripts that can run in
6955 parallel during boot, and thus decrease the boot time.
</p
>
6957 <p
>So, which scripts should start from rcS.d/. In short, only the
6958 scripts that _have_ to execute before the root login prompt is
6959 presented during a single user boot should go there. Everything else
6960 should go into the numeric runlevels. This means things like
6961 lm-sensors, fuse and x11-common should not run from rcS.d, but from
6962 the numeric runlevels. Today in Debian, there are around
115 init.d
6963 scripts that are started from rcS.d/, and most of them should be moved
6964 out. Do your package have one of them? Please help us make single
6965 user and runlevel
1 better by moving it.
</p
>
6967 <p
>Scripts setting up the screen, keyboard, system partitions
6968 etc. should still be started from rcS.d/, but there is for example no
6969 need to have the network enabled before the single user login prompt
6970 is presented.
</p
>
6972 <p
>As always, things are not so easy to fix as they sound. To keep
6973 Debian systems working while scripts migrate and during upgrades, the
6974 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
6975 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
6976 and the next ones can only be moved when their dependencies have been
6977 moved first. This migration must be done sequentially while we ensure
6978 that the package system upgrade packages in the right order to keep
6979 the system state correct. This will require some coordination when it
6980 comes to network related packages, but most of the packages with
6981 scripts that should migrate do not have anything in rcS.d/ depending
6982 on them. Some packages have already been updated, like the sudo
6983 package, while others are still left to do. I wish I had time to work
6984 on this myself, but real live constrains make it unlikely that I will
6985 find time to push this forward.
</p
>
6990 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
6991 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
6992 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
6993 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
6994 <description><p
>While at Debconf11, I have several times during discussions
6995 mentioned the issues I believe should be improved in Debian for its
6996 desktop to be useful for more people. The use case for this is my
6997 parents, which are currently running Kubuntu which solve the
7000 <p
>I suspect these four missing features are not very hard to
7001 implement. After all, they are present in Ubuntu, so if we wanted to
7002 do this in Debian we would have a source.
</p
>
7006 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
7007 are new packages available for upgrades, a icon in the KDE status bar
7008 indicate this, and clicking on it will activate the simple upgrade
7009 tool to handle it. I have no problem guiding both of my parents
7010 through the process over the phone. If a kernel reboot is required,
7011 this too is indicated by the status bars and the upgrade tool. Last
7012 time I checked, nothing with the same features was working in KDE in
7015 <li
><strong
>Simple handling of missing Firefox browser
7016 plugins.
</strong
> When the browser encounter a MIME type it do not
7017 currently have a handler for, it will ask the user if the system
7018 should search for a package that would add support for this MIME type,
7019 and if the user say yes, the APT sources will be searched for packages
7020 advertising the MIME type in their control file (visible in the
7021 Packages file in the APT archive). If one or more packages are found,
7022 it is a simple click of the mouse to add support for the missing mime
7023 type. If the package require the user to accept some non-free
7024 license, this is explained to the user. The entire process make it
7025 more clear to the user why something do not work in the browser, and
7026 make the chances higher for the user to blame the web page authors and
7027 not the browser for any missing features.
</li
>
7029 <li
><strong
>Simple handling of missing multimedia codec/format
7030 handlers.
</strong
> When the media players encounter a format or codec
7031 it is not supporting, a dialog pop up asking the user if the system
7032 should search for a package that would add support for it. This
7033 happen with things like MP3, Windows Media or H
.264. The selection
7034 and installation procedure is very similar to the Firefox browser
7035 plugin handling. This is as far as I know implemented using a
7036 gstreamer hook. The end result is that the user easily get access to
7037 the codecs that are present from the APT archives available, while
7038 explaining more on why a given format is unsupported by Ubuntu.
</li
>
7040 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
7041 displaying a text/plain file in my Debian browser, it will propose to
7042 start emacs to show it. If I remember correctly, when doing the same
7043 in Kunbutu it show the file as a text file in the browser. At least I
7044 know Opera will show text files within the browser. I much prefer the
7045 latter behaviour.
</li
>
7049 <p
>There are other nice features as well, like the simplified suite
7050 upgrader, but given that I am the one mostly doing the dist-upgrade,
7051 it do not matter much.
</p
>
7053 <p
>I really hope we could get these features in place for the next
7054 Debian release. It would require the coordinated effort of several
7055 maintainers, but would make the end user experience a lot better.
</p
>
7060 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
7061 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
7062 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
7063 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
7064 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
7065 site is build on Debian/Squeeze, and this platform was chosen because
7066 I am most familiar with Debian (being a Debian Developer for around
10
7067 years) because it is the latest stable Debian release which should get
7068 security support for a few years.
</p
>
7070 <p
>The web service is written in Perl, and depend on some perl modules
7071 that are missing in Debian at the moment. It would be great if these
7072 modules were added to the Debian archive, allowing anyone to set up
7073 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
7074 in their own country using only Debian packages. The list of modules
7075 missing in Debian/Squeeze isn
't very long, and I hope the perl group
7076 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
7077 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
7078 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
7079 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
7080 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
7081 easier in the future.
</p
>
7083 <p
>Thanks to the great tools in Debian, getting the missing modules
7084 installed on my server was a simple call to
'cpan2deb Module::Name
'
7085 and
'dpkg -i
' to install the resulting package. But this leave me
7086 with the responsibility of tracking security problems, which I really
7087 do not have time for.
</p
>
7092 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
7093 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
7094 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
7095 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
7096 <description><p
>Here is a small update for my English readers. Most of my blog
7097 posts have been in Norwegian the last few weeks, so here is a short
7098 update in English.
</p
>
7100 <p
>The kids still keep me too busy to get much free software work
7101 done, but I did manage to organise a project to get a Norwegian port
7102 of the British service
7103 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
7104 and it has been running for a month now. The entire project has been
7105 organised by me and two others. Around Christmas we gathered sponsors
7106 to fund the development work. In January I drafted a contract with
7107 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
7108 and in February the development took place. Most of it involved
7109 converting the source to use GPS coordinates instead of British
7110 easting/northing, and the resulting code should be a lot easier to get
7111 running in any country by now. The Norwegian
7112 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
7113 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
7114 source and the source for administrative borders in Norway, and
7115 support for this had to be added/fixed.
</p
>
7117 <p
>The Norwegian version went live March
3th, and we spent the weekend
7118 polishing the system before we announced it March
7th. The system is
7119 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
7120 problem reports in a few weeks. Soon we hope to announce the Android
7121 and iPhone versions making it even easier to report problems with the
7122 public infrastructure.
</p
>
7124 <p
>Perhaps something to consider for those of you in countries without
7125 such service?
</p
>
7130 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
7131 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
7132 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
7133 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
7134 <description><p
>The last few days I have looked at ways to track open security
7135 issues here at my work with the University of Oslo. My idea is that
7136 it should be possible to use the information about security issues
7137 available on the Internet, and check our locally
7138 maintained/distributed software against this information. It should
7139 allow us to verify that no known security issues are forgotten. The
7140 CVE database listing vulnerabilities seem like a great central point,
7141 and by using the package lists from Debian mapped to CVEs provided by
7142 the testing security team, I believed it should be possible to figure
7143 out which security holes were present in our free software
7144 collection.
</p
>
7146 <p
>After reading up on the topic, it became obvious that the first
7147 building block is to be able to name software packages in a unique and
7148 consistent way across data sources. I considered several ways to do
7149 this, for example coming up with my own naming scheme like using URLs
7150 to project home pages or URLs to the Freshmeat entries, or using some
7151 existing naming scheme. And it seem like I am not the first one to
7152 come across this problem, as MITRE already proposed and implemented a
7153 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
7154 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
7155 software, hardware and other platform components. The CPE ids are
7156 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
7157 Vulnerability Database
</a
>, allowing me to look up know security
7158 issues for any CPE name. With this in place, all I need to do is to
7159 locate the CPE id for the software packages we use at the university.
7160 This is fairly trivial (I google for
'cve cpe $package
' and check the
7161 NVD entry if a CVE for the package exist).
</p
>
7163 <p
>To give you an example. The GNU gzip source package have the CPE
7164 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
7165 check out, one could look up
7166 <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
7167 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
7168 The most recent one is
7169 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
7170 and at the bottom of the NVD page for this vulnerability the complete
7171 list of affected versions is provided.
</p
>
7173 <p
>The NVD database of CVEs is also available as a XML dump, allowing
7174 for offline processing of issues. Using this dump, I
've written a
7175 small script taking a list of CPEs as input and list all CVEs
7176 affecting the packages represented by these CPEs. One give it CPEs
7177 with version numbers as specified above and get a list of open
7178 security issues out.
</p
>
7180 <p
>Of course for this approach to be useful, the quality of the NVD
7181 information need to be high. For that to happen, I believe as many as
7182 possible need to use and contribute to the NVD database. I notice
7184 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
7185 map from CVE to CPE
</a
>, indicating that they are using the CPE
7186 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
7188 <p
>To get an idea about the quality for free software, I spent some
7189 time making it possible to compare the CVE database from Debian with
7190 the CVE database in NVD. The result look fairly good, but there are
7191 some inconsistencies in NVD (same software package having several
7192 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
7193 Debian believe are affected by a CVE). Hope to find time to improve
7194 the quality of NVD, but that require being able to get in touch with
7195 someone maintaining it. So far my three emails with questions and
7196 corrections have not seen any reply, but I hope contact can be
7197 established soon.
</p
>
7199 <p
>An interesting application for CPEs is cross platform package
7200 mapping. It would be useful to know which packages in for example
7201 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
7202 this would be trivial if all linux distributions provided CPE entries
7203 for their packages.
</p
>
7208 <title>Which module is loaded for a given PCI and USB device?
</title>
7209 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
7210 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
7211 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
7212 <description><p
>In the
7213 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
7214 package in Debian, there is a script to report useful information
7215 about the running hardware for use when people report missing
7216 information. One part of this script that I find very useful when
7217 debugging hardware problems, is the part mapping loaded kernel module
7218 to the PCI device it claims. It allow me to quickly see if the kernel
7219 module I expect is driving the hardware I am struggling with. To see
7220 the output, make sure discover-data is installed and run
7221 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
7222 one of my machines like this:
</p
>
7226 10de:
03eb i2c_nforce2
7229 10de:
03f0 snd_hda_intel
7238 <p
>The code in question look like this, slightly modified for
7239 readability and to drop the output to file descriptor
3:
</p
>
7242 if [ -d /sys/bus/pci/devices/ ] ; then
7243 echo loaded pci modules:
7245 cd /sys/bus/pci/devices/
7246 for address in * ; do
7247 if [ -d
"$address/driver/module
" ] ; then
7248 module=`cd $address/driver/module ; pwd -P | xargs basename`
7249 if grep -q
"^$module
" /proc/modules ; then
7250 address=$(echo $address |sed s/
0000://)
7251 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
7252 echo
"$id $module
"
7261 <p
>Similar code could be used to extract USB device module
7265 if [ -d /sys/bus/usb/devices/ ] ; then
7266 echo loaded usb modules:
7268 cd /sys/bus/usb/devices/
7269 for address in * ; do
7270 if [ -d
"$address/driver/module
" ] ; then
7271 module=`cd $address/driver/module ; pwd -P | xargs basename`
7272 if grep -q
"^$module
" /proc/modules ; then
7273 address=$(echo $address |sed s/
0000://)
7274 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
7275 if [
"$id
" ] ; then
7276 echo
"$id $module
"
7286 <p
>This might perhaps be something to include in other tools as
7292 <title>How to test if a laptop is working with Linux
</title>
7293 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
7294 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
7295 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
7296 <description><p
>The last few days I have spent at work here at the
<a
7297 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
7298 batch of computers will work with Linux. Every year for the last few
7299 years the university have organised shared bid of a few thousand
7300 computers, and this year HP won the bid. Two different desktops and
7301 five different laptops are on the list this year. We in the UNIX
7302 group want to know which one of these computers work well with RHEL
7303 and Ubuntu, the two Linux distributions we currently handle at the
7304 university.
</p
>
7306 <p
>My test method is simple, and I share it here to get feedback and
7307 perhaps inspire others to test hardware as well. To test, I PXE
7308 install the OS version of choice, and log in as my normal user and run
7309 a few applications and plug in selected pieces of hardware. When
7310 something fail, I make a note about this in the test matrix and move
7311 on. If I have some spare time I try to report the bug to the OS
7312 vendor, but as I only have the machines for a short time, I rarely
7313 have the time to do this for all the problems I find.
</p
>
7315 <p
>Anyway, to get to the point of this post. Here is the simple tests
7316 I perform on a new model.
</p
>
7320 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
7321 and Ubuntu Maverik at the moment. If I feel like it, I also test with
7322 RHEL5 and Debian Edu/Squeeze.
</li
>
7324 <li
>Is X.org working? If the graphical login screen show up after
7325 installation, X.org is working.
</li
>
7327 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
7328 package mesa-utils on Ubuntu) and writing down the frames per second
7329 reported by the program.
</li
>
7331 <li
>Is sound working? With Gnome and KDE, a sound is played when
7332 logging in, and if I can hear this the test is successful. If there
7333 are several audio exits on the machine, I try them all and check if
7334 the Gnome/KDE audio mixer can control where to send the sound. I
7335 normally test this by playing
7336 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
7337 video
</a
> in Firefox/Iceweasel.
</li
>
7339 <li
>Is the USB subsystem working? I test this by plugging in a USB
7340 memory stick and see if Gnome/KDE notices this.
</li
>
7342 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
7343 I have lying around, and see if Gnome/KDE notices this.
</li
>
7345 <li
>Is any built in camera working? Test using cheese, and see if a
7346 picture from the v4l device show up.
</li
>
7348 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
7349 any bluetooth devices are discovered. In my office, I normally see a
7352 <li
>For laptops, is the SD or Compaq Flash reader working. I have
7353 memory modules lying around, and stick them in and see if Gnome/KDE
7354 notice this.
</li
>
7356 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
7357 special button work, and if the laptop continue to work after
7360 <li
>For laptops, is the extra buttons working, like audio level,
7361 adjusting background light, switching on/off external video output,
7362 switching on/off wifi, bluetooth, etc? The set of buttons differ from
7363 laptop to laptop, so I just write down which are working and which are
7366 <li
>Some laptops have smart card readers, finger print readers,
7367 acceleration sensors etc. I rarely test these, as I do not know how
7368 to quickly test if they are working or not, so I only document their
7369 existence.
</li
>
7373 <p
>By now I suspect you are really curious what the test results are
7374 for the HP machines I am testing. I
'm not done yet, so I will report
7375 the test results later. For now I can report that HP
8100 Elite work
7376 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
7377 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
7378 can see, I have most machines left to test. One interesting
7379 observation is that Ubuntu Lucid has almost twice the frame rate than
7380 RHEL6 with glxgears. No idea why.
</p
>
7385 <title>Some thoughts on BitCoins
</title>
7386 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
7387 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
7388 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
7389 <description><p
>As I continue to explore
7390 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
7391 what properties the system have, and how it will be affected by laws
7392 and regulations here in Norway. Here are some random notes.
</p
>
7394 <p
>One interesting thing to note is that since the transactions are
7395 verified using a peer to peer network, all details about a transaction
7396 is known to everyone. This means that if a BitCoin address has been
7397 published like I did with mine in my initial post about BitCoin, it is
7398 possible for everyone to see how many BitCoins have been transfered to
7399 that address. There is even a web service to look at the details for
7400 all transactions. There I can see that my address
7401 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
7402 have received
16.06 Bitcoin, the
7403 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
7404 address of Simon Phipps have received
181.97 BitCoin and the address
7405 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
7406 of EFF have received
2447.38 BitCoins so far. Thank you to each and
7407 every one of you that donated bitcoins to support my activity. The
7408 fact that anyone can see how much money was transfered to a given
7409 address make it more obvious why the BitCoin community recommend to
7410 generate and hand out a new address for each transaction. I
'm told
7411 there is no way to track which addresses belong to a given person or
7412 organisation without the person or organisation revealing it
7413 themselves, as Simon, EFF and I have done.
</p
>
7415 <p
>In Norway, and in most other countries, there are laws and
7416 regulations limiting how much money one can transfer across the border
7417 without declaring it. There are money laundering, tax and accounting
7418 laws and regulations I would expect to apply to the use of BitCoin.
7419 If the Skolelinux foundation
7420 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
7421 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
7422 normal bank transfers like EFF is doing, how should this be accounted?
7423 Given that it is impossible to know if money can cross the border or
7424 not, should everything or nothing be declared? What exchange rate
7425 should be used when calculating taxes? Would receivers have to pay
7426 income tax if the foundation were to pay Skolelinux contributors in
7427 BitCoin? I have no idea, but it would be interesting to know.
</p
>
7429 <p
>For a currency to be useful and successful, it must be trusted and
7430 accepted by a lot of users. It must be possible to get easy access to
7431 the currency (as a wage or using currency exchanges), and it must be
7432 easy to spend it. At the moment BitCoin seem fairly easy to get
7433 access to, but there are very few places to spend it. I am not really
7434 a regular user of any of the vendor types currently accepting BitCoin,
7435 so I wonder when my kind of shop would start accepting BitCoins. I
7436 would like to buy electronics, travels and subway tickets, not herbs
7437 and books. :) The currency is young, and this will improve over time
7438 if it become popular, but I suspect regular banks will start to lobby
7439 to get BitCoin declared illegal if it become popular. I
'm sure they
7440 will claim it is helping fund terrorism and money laundering (which
7441 probably would be true, as is any currency in existence), but I
7442 believe the problems should be solved elsewhere and not by blaming
7443 currencies.
</p
>
7445 <p
>The process of creating new BitCoins is called mining, and it is
7446 CPU intensive process that depend on a bit of luck as well (as one is
7447 competing against all the other miners currently spending CPU cycles
7448 to see which one get the next lump of cash). The
"winner
" get
50
7449 BitCoin when this happen. Yesterday I came across the obvious way to
7450 join forces to increase ones changes of getting at least some coins,
7451 by coordinating the work on mining BitCoins across several machines
7452 and people, and sharing the result if one is lucky and get the
50
7454 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
7455 if this sounds interesting. I have not had time to try to set up a
7456 machine to participate there yet, but have seen that running on ones
7457 own for a few days have not yield any BitCoins througth mining
7460 <p
>Update
2010-
12-
15: Found an
<a
7461 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
7462 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
7463 it was interesting to read. The arguments presented seem to be
7464 equally valid for gold, which was used as a currency for many years.
</p
>
7469 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
7470 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
7471 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
7472 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
7473 <description><p
>With this weeks lawless
7474 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
7475 attacks
</a
> on Wikileak and
7476 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
7477 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
7478 not be trusted to handle money transactions.
7480 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
7481 Phipps on bitcoin
</a
> reminded me about a project that a friend of
7482 mine mentioned earlier. I decided to follow Simon
's example, and get
7483 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
7484 some help from my friend to get it all running, and he even handed me
7485 some bitcoins to get started. I even donated a few bitcoins to Simon
7486 for helping me remember BitCoin.
</p
>
7488 <p
>So, what is bitcoins, you probably wonder? It is a digital
7489 crypto-currency, decentralised and handled using peer-to-peer
7490 networks. It allows anonymous transactions and prohibits central
7491 control over the transactions, making it impossible for governments
7492 and companies alike to block donations and other transactions. The
7493 source is free software, and while the key dependency wxWidgets
2.9
7494 for the graphical user interface is missing in Debian, the command
7495 line client builds just fine. Hopefully Jonas
7496 <a href=
"http://bugs.debian.org/
578157">will get the package into
7497 Debian
</a
> soon.
</p
>
7499 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
7500 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
7501 bitcoins
</a
> when selling services and goods, and there are even
7502 currency
"stock
" markets where the exchange rate is decided. There
7503 are not many users so far, but the concept seems promising. If you
7504 want to get started and lack a friend with any bitcoins to spare,
7506 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
7507 bitcoin at the time of writing). Use
7508 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
7509 on the current exchange rates.
</p
>
7511 <p
>As an experiment, I have decided to set up bitcoind on one of my
7512 machines. If you want to support my activity, please send Bitcoin
7513 donations to the address
7514 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
7519 <title>Why isn
't Debian Edu using VLC?
</title>
7520 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
7521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
7522 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
7523 <description><p
>In the latest issue of Linux Journal, the readers choices were
7524 presented, and the winner among the multimedia player were VLC.
7525 Personally, I like VLC, and it is my player of choice when I first try
7526 to play a video file or stream. Only if VLC fail will I drag out
7527 gmplayer to see if it can do better. The reason is mostly the failure
7528 model and trust. When VLC fail, it normally pop up a error message
7529 reporting the problem. When mplayer fail, it normally segfault or
7530 just hangs. The latter failure mode drain my trust in the program.
<p
>
7532 <p
>But even if VLC is my player of choice, we have choosen to use
7533 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
7534 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
7535 plugin to play web videos seamlessly, and the VLC browser plugin is
7536 not very good. For example, it lack in-line control buttons, so there
7537 is no way for the user to pause the video. Also, when I
7538 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
7539 tested the browser plugins
</a
> available in Debian, the VLC plugin
7540 failed on several video pages where mplayer based plugins worked. If
7541 the browser plugin for VLC was as good as the gecko-mediaplayer
7542 package (which uses mplayer), we would switch.
</P
>
7544 <p
>While VLC is a good player, its user interface is slightly
7545 annoying. The most annoying feature is its inconsistent use of
7546 keyboard shortcuts. When the player is in full screen mode, its
7547 shortcuts are different from when it is playing the video in a window.
7548 For example, space only work as pause when in full screen mode. I
7549 wish it had consisten shortcuts and that space also would work when in
7550 window mode. Another nice shortcut in gmplayer is [enter] to restart
7551 the current video. It is very nice when playing short videos from the
7552 web and want to restart it when new people arrive to have a look at
7553 what is going on.
</p
>
7558 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
7559 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
7560 <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>
7561 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
7562 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
7563 upgrade testing of the
7564 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
7565 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
7566 This seem like a very good idea, so I adjusted by test scripts and
7567 can now present the updated result from today:
</p
>
7569 <p
>This is for Gnome:
</p
>
7571 <p
>Installed using apt-get, missing with aptitude
</p
>
7573 <blockquote
><p
>
7578 browser-plugin-gnash
7585 freedesktop-sound-theme
7587 gconf-defaults-service
7602 gnome-desktop-environment
7606 gnome-session-canberra
7611 gstreamer0.10-fluendo-mp3
7617 libapache2-mod-dnssd
7620 libaprutil1-dbd-sqlite3
7623 libboost-date-time1.42
.0
7624 libboost-python1.42
.0
7625 libboost-thread1.42
.0
7627 libchamplain-gtk-
0.4-
0
7629 libclutter-gtk-
0.10-
0
7636 libfreerdp-plugins-standard
7651 libgnomepanel2.24-cil
7656 libgtksourceview2.0-common
7657 libmono-addins-gui0.2-cil
7658 libmono-addins0.2-cil
7659 libmono-cairo2.0-cil
7660 libmono-corlib2.0-cil
7661 libmono-i18n-west2.0-cil
7662 libmono-posix2.0-cil
7663 libmono-security2.0-cil
7664 libmono-sharpzip2.84-cil
7665 libmono-system2.0-cil
7668 libndesk-dbus-glib1.0-cil
7669 libndesk-dbus1.0-cil
7679 libtelepathy-farsight0
7688 nautilus-sendto-empathy
7692 python-aptdaemon-gtk
7694 python-beautifulsoup
7709 python-gtksourceview2
7720 python-pkg-resources
7727 python-twisted-conch
7733 python-zope.interface
7738 rhythmbox-plugin-cdrecorder
7745 system-config-printer-udev
7747 telepathy-mission-control-
5
7758 </p
></blockquote
>
7760 <p
>Installed using apt-get, removed with aptitude
</p
>
7762 <blockquote
><p
>
7768 fast-user-switch-applet
7787 libgtksourceview2.0-
0
7789 libsdl1.2debian-alsa
7795 system-config-printer
7800 </p
></blockquote
>
7802 <p
>Installed using aptitude, missing with apt-get
</p
>
7804 <blockquote
><p
>
7805 gstreamer0.10-gnomevfs
7806 </p
></blockquote
>
7808 <p
>Installed using aptitude, removed with apt-get
</p
>
7810 <blockquote
><p
>
7812 </p
></blockquote
>
7814 <p
>This is for KDE:
</p
>
7816 <p
>Installed using apt-get, missing with aptitude
</p
>
7818 <blockquote
><p
>
7820 </p
></blockquote
>
7822 <p
>Installed using apt-get, removed with aptitude
</p
>
7824 <blockquote
><p
>
7827 </p
></blockquote
>
7829 <p
>Installed using aptitude, missing with apt-get
</p
>
7831 <blockquote
><p
>
7845 kdeartwork-emoticons
7847 kdeartwork-theme-icon
7851 kdebase-workspace-bin
7852 kdebase-workspace-data
7866 kscreensaver-xsavers
7881 plasma-dataengines-workspace
7883 plasma-desktopthemes-artwork
7884 plasma-runners-addons
7885 plasma-scriptengine-googlegadgets
7886 plasma-scriptengine-python
7887 plasma-scriptengine-qedje
7888 plasma-scriptengine-ruby
7889 plasma-scriptengine-webkit
7890 plasma-scriptengines
7891 plasma-wallpapers-addons
7892 plasma-widget-folderview
7893 plasma-widget-networkmanagement
7897 xscreensaver-data-extra
7899 xscreensaver-gl-extra
7900 xscreensaver-screensaver-bsod
7901 </p
></blockquote
>
7903 <p
>Installed using aptitude, removed with apt-get
</p
>
7905 <blockquote
><p
>
7907 google-gadgets-common
7925 libggadget-qt-
1.0-
0b
7930 libkonqsidebarplugin4a
7939 libplasma-geolocation-interface4
7941 libplasmagenericshell4
7955 libsmokeknewstuff2-
3
7956 libsmokeknewstuff3-
3
7958 libsmokektexteditor3
7966 libsmokeqtnetwork4-
3
7972 libsmokeqtuitools4-
3
7984 plasma-dataengines-addons
7985 plasma-scriptengine-superkaramba
7986 plasma-widget-lancelot
7987 plasma-widgets-addons
7988 plasma-widgets-workspace
7992 update-notifier-common
7993 </p
></blockquote
>
7995 <p
>Running apt-get autoremove made the results using apt-get and
7996 aptitude a bit more similar, but there are still quite a lott of
7997 differences. I have no idea what packages should be installed after
7998 the upgrade, but hope those that do can have a look.
</p
>
8003 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
8004 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
8005 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
8006 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
8007 <description><p
>Most of the computers in use by the
8008 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
8009 are virtual machines. And they have been Xen machines running on a
8010 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
8011 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
8012 bit harder that it could have been, because we set up the Xen virtual
8013 machines to get the virtual partitions from LVM, which as far as I
8014 know is not supported by KVM. So to migrate, we had to convert
8015 several LVM logical volumes to partitions on a virtual disk file.
</p
>
8018 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
8019 nice recipe
</a
> to do this, and wrote the following script to do the
8020 migration. It uses qemu-img from the qemu package to make the disk
8021 image, parted to partition it, losetup and kpartx to present the disk
8022 image partions as devices, and dd to copy the data. I NFS mounted the
8023 new servers storage area on the old server to do the migration.
</p
>
8029 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
8034 if [ -z
"$
1" ] ; then
8035 echo
"Usage: $
0 &lt;hostname
&gt;
"
8041 if [ ! -e /dev/vg_data/$host-disk ] ; then
8042 echo
"error: unable to find LVM volume for $host
"
8046 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
8047 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8048 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
8049 totalsize=$(( ( $disksize + $swapsize ) ))
8052 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
8053 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
8055 parted $img mklabel msdos
8056 parted $img mkpart primary linux-swap
0 $disksize
8057 parted $img mkpart primary ext2 $disksize $totalsize
8058 parted $img set
1 boot on
8061 losetup /dev/loop0 $img
8062 kpartx -a /dev/loop0
8064 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
8065 fsck.ext3 -f /dev/mapper/loop0p1 || true
8066 mkswap /dev/mapper/loop0p2
8068 kpartx -d /dev/loop0
8069 losetup -d /dev/loop0
8072 <p
>The script is perhaps so simple that it is not copyrightable, but
8073 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
8075 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
8076 the new disk image attached, installed grub-pc and linux-image-
686 and
8077 set up grub to boot from the disk image. After this, the KVM machines
8078 seem to work just fine.
</p
>
8083 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
8084 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
8085 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
8086 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
8087 <description><p
>I
'm still running upgrade testing of the
8088 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
8089 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
8090 status. Here is a short update based on a test I ran
20101118.
</p
>
8092 <p
>I still do not know what a correct migration should look like, so I
8093 report any differences between apt and aptitude and hope someone else
8094 can see if anything should be changed.
</p
>
8096 <p
>This is for Gnome:
</p
>
8098 <p
>Installed using apt-get, missing with aptitude
</p
>
8100 <blockquote
><p
>
8101 apache2.2-bin aptdaemon at-spi baobab binfmt-support
8102 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
8103 dmz-cursor-theme empathy empathy-common finger
8104 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
8105 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
8106 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
8107 gnome-cards-data gnome-codec-install gnome-core
8108 gnome-desktop-environment gnome-disk-utility gnome-screenshot
8109 gnome-search-tool gnome-session-canberra gnome-spell
8110 gnome-system-log gnome-themes-extras gnome-themes-more
8111 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
8112 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
8113 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
8114 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
8115 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
8116 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
8117 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
8118 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
8119 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
8120 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
8121 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
8122 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
8123 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
8124 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
8125 libgtk2.0-cil libgtkglext1 libgtksourceview-common
8126 libgtksourceview2.0-common libmono-addins-gui0.2-cil
8127 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
8128 libmono-i18n-west2.0-cil libmono-posix2.0-cil
8129 libmono-security2.0-cil libmono-sharpzip2.84-cil
8130 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
8131 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
8132 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
8133 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
8134 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
8135 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
8136 libxalan2-java libxerces2-java media-player-info mesa-utils
8137 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
8138 nautilus-sendto-empathy openoffice.org-writer2latex
8139 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
8140 python-aptdaemon python-aptdaemon-gtk python-axiom
8141 python-beautifulsoup python-bugbuddy python-clientform
8142 python-coherence python-configobj python-crypto python-cupshelpers
8143 python-cupsutils python-eggtrayicon python-elementtree
8144 python-epsilon python-evolution python-feedparser python-gdata
8145 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
8146 python-gtksourceview2 python-httplib2 python-louie python-mako
8147 python-markupsafe python-mechanize python-nevow python-notify
8148 python-opengl python-openssl python-pam python-pkg-resources
8149 python-pyasn1 python-pysqlite2 python-rdflib python-serial
8150 python-tagpy python-twisted-bin python-twisted-conch
8151 python-twisted-core python-twisted-web python-utidylib python-webkit
8152 python-xdg python-zope.interface remmina remmina-plugin-data
8153 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
8154 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
8155 software-center svgalibg1 system-config-printer-udev
8156 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
8157 totem totem-coherence totem-mozilla totem-plugins
8158 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
8160 </p
></blockquote
>
8162 Installed using apt-get, removed with aptitude
8164 <blockquote
><p
>
8165 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
8166 epiphany-extensions epiphany-gecko evolution-exchange
8167 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
8168 gedit-common gnome-app-install gnome-games gnome-games-data
8169 gnome-nettool gnome-system-tools gnome-themes gnome-utils
8170 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
8171 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
8172 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
8173 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
8174 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
8175 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
8176 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
8177 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
8178 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
8179 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
8180 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
8181 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
8182 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
8183 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
8184 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
8185 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
8186 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
8187 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
8188 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
8189 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
8190 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
8191 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
8192 sound-juicer swfdec-gnome system-config-printer totem-common
8193 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
8194 </p
></blockquote
>
8196 <p
>Installed using aptitude, missing with apt-get
</p
>
8198 <blockquote
><p
>
8199 gstreamer0.10-gnomevfs
8200 </p
></blockquote
>
8202 <p
>Installed using aptitude, removed with apt-get
</p
>
8204 <blockquote
><p
>
8206 </p
></blockquote
>
8208 <p
>This is for KDE:
</p
>
8210 <p
>Installed using apt-get, missing with aptitude
</p
>
8212 <blockquote
><p
>
8213 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
8214 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
8215 ghostscript-x git gnome-audio gnugo granatier gs-common
8216 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
8217 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
8218 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
8219 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8220 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
8221 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
8222 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8223 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
8224 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
8225 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
8226 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
8227 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
8228 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
8229 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
8230 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
8231 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
8232 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
8233 libkrossui4 libmailtools-perl libmime-tools-perl
8234 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
8235 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
8236 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
8237 lirc luatex marble networkstatus noatun-plugins
8238 openoffice.org-writer2latex palapeli palapeli-data parley
8239 parley-data poster psutils pulseaudio pulseaudio-esound-compat
8240 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
8241 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
8243 </p
></blockquote
>
8245 <p
>Installed using apt-get, removed with aptitude
</p
>
8247 <blockquote
><p
>
8248 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
8249 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
8250 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
8251 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
8252 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
8253 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
8254 kitchensync kiten kjumpingcube klatin klettres klickety klines
8255 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
8256 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
8257 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
8258 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
8259 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
8260 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
8261 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
8262 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
8263 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8264 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
8265 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
8266 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8267 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
8268 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
8269 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
8270 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
8271 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8272 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
8273 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
8274 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
8275 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
8276 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
8277 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
8278 mpeglib network-manager-kde noatun pmount tex-common texlive-base
8279 texlive-common texlive-doc-base texlive-fonts-recommended tidy
8280 ttf-dustin ttf-kochi-gothic ttf-sjfonts
8281 </p
></blockquote
>
8283 <p
>Installed using aptitude, missing with apt-get
</p
>
8285 <blockquote
><p
>
8286 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
8287 kdeartwork kdebase kdebase-apps kdebase-workspace
8288 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
8289 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
8290 netpbm plasma-widget-folderview plasma-widget-networkmanagement
8291 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
8292 xscreensaver-screensaver-bsod
8293 </p
></blockquote
>
8295 <p
>Installed using aptitude, removed with apt-get
</p
>
8297 <blockquote
><p
>
8298 kdebase-bin konq-plugins konqueror
8299 </p
></blockquote
>
8304 <title>Gnash buildbot slave and Debian kfreebsd
</title>
8305 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
8306 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
8307 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
8308 <description><p
>Answering
8309 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
8310 call from the Gnash project
</a
> for
8311 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
8312 current source, I have set up a virtual KVM machine on the Debian
8313 Edu/Skolelinux virtualization host to test the git source on
8314 Debian/Squeeze. I hope this can help the developers in getting new
8315 releases out more often.
</p
>
8317 <p
>As the developers want less main-stream build platforms tested to,
8318 I have considered setting up a
<a
8319 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
8320 machine as well. I have also considered using the kfreebsd
8321 architecture in Debian as a file server in NUUG to get access to the
5
8322 TB zfs volume we currently use to store DV video. Because of this, I
8323 finally got around to do a test installation of Debian/Squeeze with
8324 kfreebsd. Installation went fairly smooth, thought I noticed some
8325 visual glitches in the cdebconf dialogs (black cursor left on the
8326 screen at random locations). Have not gotten very far with the
8327 testing. Noticed cfdisk did not work, but fdisk did so it was not a
8328 fatal problem. Have to spend some more time on it to see if it is
8329 useful as a file server for NUUG. Will try to find time to set up a
8330 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
8335 <title>Debian in
3D
</title>
8336 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
8337 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
8338 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
8339 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
8341 <p
>3D printing is just great. I just came across this Debian logo in
8343 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
8344 thingiverse blog
</a
>.
</p
>
8349 <title>Software updates
2010-
10-
24</title>
8350 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
8351 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
8352 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
8353 <description><p
>Some updates.
</p
>
8355 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
8356 raise money for the project is going well. The lower limit of
10
8357 signers was reached in
24 hours, and so far
13 people have signed it.
8358 More signers and more funding is most welcome, and I am really curious
8359 how far we can get before the time limit of December
24 is reached.
8362 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
8363 about what appear to be a great code coverage tool capable of
8364 generating code coverage stats without any changes to the source code.
8366 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
8367 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
8368 It is missing in Debian, but the git source built just fine in Squeeze
8369 after I installed libelf-dev, libdwarf-dev, pkg-config and
8370 libglib2.0-dev. Failed to build in Lenny, but suspect that is
8371 solvable. I hope kcov make it into Debian soon.
</p
>
8373 <p
>Finally found time to wrap up the release notes for
<a
8374 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
8375 new alpha release of Debian Edu
</a
>, and just published the second
8376 alpha test release of the Squeeze based Debian Edu /
8377 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
8378 release. Give it a try if you need a complete linux solution for your
8379 school, including central infrastructure server, workstations, thin
8380 client servers and diskless workstations. A nice touch added
8381 yesterday is RDP support on the thin client servers, for windows
8382 clients to get a Linux desktop on request.
</p
>
8387 <title>Some notes on Flash in Debian and Debian Edu
</title>
8388 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
8389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
8390 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
8391 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
8392 popularity-contest numbers
</a
>, the adobe-flashplugin package the
8393 second most popular used package that is missing in Debian. The sixth
8394 most popular is flashplayer-mozilla. This is a clear indication that
8395 working flash is important for Debian users. Around
10 percent of the
8396 users submitting data to popcon.debian.org have this package
8397 installed.
</p
>
8399 <p
>In the report written by Lars Risan in August
2008
8400 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
8401 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
8402 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
8403 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
8404 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
8405 web sites require Flash to work, and lacking working Flash support in
8406 the web browser and the problems with installing it was perceived as a
8407 good reason to stay with Windows.
</p
>
8409 <p
>I once saw a funny and sad comment in a web forum, where Linux was
8410 said to be the retarded cousin that did not really understand
8411 everything you told him but could work fairly well. This was a
8412 comment regarding the problems Linux have with proprietary formats and
8413 non-standard web pages, and is sad because it exposes a fairly common
8414 understanding of whose fault it is if web pages that only work in for
8415 example Internet Explorer
6 fail to work on Firefox, and funny because
8416 it explain very well how annoying it is for users when Linux
8417 distributions do not work with the documents they receive or the web
8418 pages they want to visit.
</p
>
8420 <p
>This is part of the reason why I believe it is important for Debian
8421 and Debian Edu to have a well working Flash implementation in the
8422 distribution, to get at least popular sites as Youtube and Google
8423 Video to working out of the box. For Squeeze, Debian have the chance
8424 to include the latest version of Gnash that will make this happen, as
8425 the new release
0.8.8 was published a few weeks ago and is resting in
8426 unstable. The new version work with more sites that version
0.8.7.
8427 The Gnash maintainers have asked for a freeze exception, but the
8428 release team have not had time to reply to it yet. I hope they agree
8429 with me that Flash is important for the Debian desktop users, and thus
8430 accept the new package into Squeeze.
</p
>
8435 <title>Circular package dependencies harms apt recovery
</title>
8436 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
8437 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
8438 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
8439 <description><p
>I discovered this while doing
8440 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
8441 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
8442 in Debian still got circular dependencies, and it is often claimed
8443 that apt and aptitude should be able to handle this just fine, but
8444 some times these dependency loops causes apt to fail.
</p
>
8446 <p
>An example is from todays
8447 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
8448 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
8449 causes perl-modules to fail to upgrade. The cause is simple. If a
8450 package fail to unpack, then only part of packages with the circular
8451 dependency might end up being unpacked when unpacking aborts, and the
8452 ones already unpacked will fail to configure in the recovery phase
8453 because its dependencies are unavailable.
</p
>
8455 <p
>In this log, the problem manifest itself with this error:
</p
>
8457 <blockquote
><pre
>
8458 dpkg: dependency problems prevent configuration of perl-modules:
8459 perl-modules depends on perl (
>=
5.10.1-
1); however:
8460 Version of perl on system is
5.10.0-
19lenny
2.
8461 dpkg: error processing perl-modules (--configure):
8462 dependency problems - leaving unconfigured
8463 </pre
></blockquote
>
8465 <p
>The perl/perl-modules circular dependency is already
8466 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
8467 hopefully be solved as soon as possible, but it is not the only one,
8468 and each one of these loops in the dependency tree can cause similar
8469 failures. Of course, they only occur when there are bugs in other
8470 packages causing the unpacking to fail, but it is rather nasty when
8471 the failure of one package causes the problem to become worse because
8472 of dependency loops.
</p
>
8475 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
8476 tireless effort by Bill Allombert
</a
>, the number of circular
8478 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
8479 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
8481 <p
>Todays testing also exposed a bug in
8482 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
8483 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
8484 apt-get and aptitude, the latter possibly caused by some circular
8485 dependency. Reported both to BTS to try to get someone to look at
8491 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
8492 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
8493 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
8494 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
8495 <description><p
>This is a
8496 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
8498 <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
8500 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
8501 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
8503 <p
>As a step to try to see if it possible to merge the DNS and DHCP
8504 LDAP objects, I have had a look at how the packages pdns-backend-ldap
8505 and dhcp3-server-ldap in Debian use the LDAP server. The two
8506 implementations are quite different in how they use LDAP.
</p
>
8508 To get this information, I started slapd with debugging enabled and
8509 dumped the debug output to a file to get the LDAP searches performed
8510 on a Debian Edu main-server. Here is a summary.
8512 <p
><strong
>powerdns
</strong
></p
>
8514 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
8515 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
8518 <p
>PowerDNS have two modes of operation using LDAP as its backend.
8519 One
"strict
" mode where the forward and reverse DNS lookups are done
8520 using the same LDAP objects, and a
"tree
" mode where the forward and
8521 reverse entries are in two different subtrees in LDAP with a structure
8522 based on the DNS names, as in tjener.intern and
8523 2.2.0.10.in-addr.arpa.
</p
>
8525 <p
>In tree mode, the server is set up to use a LDAP subtree as its
8526 base, and uses a
"base
" scoped search for the DNS name by adding
8527 "dc=tjener,dc=intern,
" to the base with a filter for
8528 "(associateddomain=tjener.intern)
" for the forward entry and
8529 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
8530 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
8531 forward entries, it is looking for attributes named dnsttl, arecord,
8532 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
8533 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
8534 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
8535 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
8536 spfrecord and modifytimestamp. For reverse entries it is looking for
8537 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
8538 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
8539 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
8540 ldapsearch commands could look like this:
</p
>
8542 <blockquote
><pre
>
8543 ldapsearch -h ldap \
8544 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8545 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8546 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8547 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8548 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8549 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8551 ldapsearch -h ldap \
8552 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
8553 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
8554 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
8555 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
8556 srvrecord naptrrecord modifytimestamp
8557 </pre
></blockquote
>
8559 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
8560 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
8561 example LDAP objects used there. In addition to these objects, the
8562 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
8563 also exist.
</p
>
8565 <blockquote
><pre
>
8566 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
8568 objectclass: dnsdomain
8569 objectclass: domainrelatedobject
8572 associateddomain: tjener.intern
8574 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
8576 objectclass: dnsdomain2
8577 objectclass: domainrelatedobject
8579 ptrrecord: tjener.intern
8580 associateddomain:
2.2.0.10.in-addr.arpa
8581 </pre
></blockquote
>
8583 <p
>In strict mode, the server behaves differently. When looking for
8584 forward DNS entries, it is doing a
"subtree
" scoped search with the
8585 same base as in the tree mode for a object with filter
8586 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
8587 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
8588 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
8589 naptrrecord and modifytimestamp. For reverse entires it also do a
8590 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
8591 and the requested attributes are associateddomain, dnsttl and
8592 modifytimestamp. In short, in strict mode the objects with ptrrecord
8593 go away, and the arecord attribute in the forward object is used
8596 <p
>The forward and reverse searches can be simulated using ldapsearch
8597 like this:
</p
>
8599 <blockquote
><pre
>
8600 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8601 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
8602 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
8603 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
8604 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
8605 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
8607 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
8608 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
8609 </pre
></blockquote
>
8611 <p
>In addition to the forward and reverse searches , there is also a
8612 search for SOA records, which behave similar to the forward and
8613 reverse lookups.
</p
>
8615 <p
>A thing to note with the PowerDNS behaviour is that it do not
8616 specify any objectclass names, and instead look for the attributes it
8617 need to generate a DNS reply. This make it able to work with any
8618 objectclass that provide the needed attributes.
</p
>
8620 <p
>The attributes are normally provided in the cosine (RFC
1274) and
8621 dnsdomain2 schemas. The latter is used for reverse entries like
8622 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
8624 <p
>In Debian Edu, we have created DNS objects using the object classes
8625 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
8626 attributes) and domainrelatedobject (for associatedDomain). The use
8627 of structural object classes make it impossible to combine these
8628 classes with the object classes used by DHCP.
</p
>
8630 <p
>There are other schemas that could be used too, for example the
8631 dnszone structural object class used by Gosa and bind-sdb for the DNS
8632 attributes combined with the domainrelatedobject object class, but in
8633 this case some unused attributes would have to be included as well
8634 (zonename and relativedomainname).
</p
>
8636 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
8637 mode and not use any of the existing objectclasses (dnsdomain,
8638 dnsdomain2 and dnszone) when one want to combine the DNS information
8639 with DHCP information, and instead create a auxiliary object class
8640 defined something like this (using the attributes defined for
8641 dnsdomain and dnsdomain2 or dnszone):
</p
>
8643 <blockquote
><pre
>
8644 objectclass ( some-oid NAME
'dnsDomainAux
'
8647 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
8648 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
8649 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
8650 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
8651 A6Record $ DNAMERecord
8653 </pre
></blockquote
>
8655 <p
>This will allow any object to become a DNS entry when combined with
8656 the domainrelatedobject object class, and allow any entity to include
8657 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
8658 developers asking for their view on this schema and if they are
8659 interested in providing such schema with PowerDNS, and I hope my
8660 message will be accepted into their mailing list soon.
</p
>
8662 <p
><strong
>ISC dhcp
</strong
></p
>
8664 <p
>The DHCP server searches for specific objectclass and requests all
8665 the object attributes, and then uses the attributes it want. This
8666 make it harder to figure out exactly what attributes are used, but
8667 thanks to the working example in Debian Edu I can at least get an idea
8668 what is needed without having to read the source code.
</p
>
8670 <p
>In the DHCP server configuration, the LDAP base to use and the
8671 search filter to use to locate the correct dhcpServer entity is
8672 stored. These are the relevant entries from
8673 /etc/dhcp3/dhcpd.conf:
</p
>
8675 <blockquote
><pre
>
8676 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
8677 ldap-dhcp-server-cn
"dhcp
";
8678 </pre
></blockquote
>
8680 <p
>The DHCP server uses this information to nest all the DHCP
8681 configuration it need. The cn
"dhcp
" is located using the given LDAP
8682 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
8683 search result is this entry:
</p
>
8685 <blockquote
><pre
>
8686 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
8689 objectClass: dhcpServer
8690 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8691 </pre
></blockquote
>
8693 <p
>The content of the dhcpServiceDN attribute is next used to locate the
8694 subtree with DHCP configuration. The DHCP configuration subtree base
8695 is located using a base scope search with base
"cn=DHCP
8696 Config,dc=skole,dc=skolelinux,dc=no
" and filter
8697 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
8698 The search result is this entry:
</p
>
8700 <blockquote
><pre
>
8701 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8704 objectClass: dhcpService
8705 objectClass: dhcpOptions
8706 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
8707 dhcpStatements: ddns-update-style none
8708 dhcpStatements: authoritative
8709 dhcpOption: smtp-server code
69 = array of ip-address
8710 dhcpOption: www-server code
72 = array of ip-address
8711 dhcpOption: wpad-url code
252 = text
8712 </pre
></blockquote
>
8714 <p
>Next, the entire subtree is processed, one level at the time. When
8715 all the DHCP configuration is loaded, it is ready to receive requests.
8716 The subtree in Debian Edu contain objects with object classes
8717 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
8718 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
8719 and information about netmasks, dynamic range etc. Leaving out the
8720 details here because it is not relevant for the focus of my
8721 investigation, which is to see if it is possible to merge dns and dhcp
8722 related computer objects.
</p
>
8724 <p
>When a DHCP request come in, LDAP is searched for the MAC address
8725 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
8726 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
8727 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
8728 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
8731 <blockquote
><pre
>
8732 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8735 objectClass: dhcpHost
8736 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8737 dhcpStatements: fixed-address hostname
8738 </pre
></blockquote
>
8740 <p
>There is less flexiblity in the way LDAP searches are done here.
8741 The object classes need to have fixed names, and the configuration
8742 need to be stored in a fairly specific LDAP structure. On the
8743 positive side, the invidiual dhcpHost entires can be anywhere without
8744 the DN pointed to by the dhcpServer entries. The latter should make
8745 it possible to group all host entries in a subtree next to the
8746 configuration entries, and this subtree can also be shared with the
8747 DNS server if the schema proposed above is combined with the dhcpHost
8748 structural object class.
8750 <p
><strong
>Conclusion
</strong
></p
>
8752 <p
>The PowerDNS implementation seem to be very flexible when it come
8753 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
8754 come to the the LDAP structure, the
"strict
" mode is very flexible,
8755 allowing DNS objects to be stored anywhere under the base cn specified
8756 in the configuration.
</p
>
8758 <p
>The DHCP implementation on the other hand is very inflexible, both
8759 regarding which LDAP schemas to use and which LDAP structure to use.
8760 I guess one could implement ones own schema, as long as the
8761 objectclasses and attributes have the names used, but this do not
8762 really help when the DHCP subtree need to have a fairly fixed
8763 structure.
</p
>
8765 <p
>Based on the observed behaviour, I suspect a LDAP structure like
8766 this might work for Debian Edu:
</p
>
8768 <blockquote
><pre
>
8770 cn=machine-info (dhcpService) - dhcpServiceDN points here
8771 cn=dhcp (dhcpServer)
8772 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
8773 cn=
10.0.2.0 (dhcpSubnet)
8774 cn=group1 (dhcpGroup/dhcpOptions)
8775 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
8776 cn=
192.168.0.0 (dhcpSubnet)
8777 cn=group1 (dhcpGroup/dhcpOptions)
8778 ou=machines - PowerDNS base points here
8779 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
8780 </pre
></blockquote
>
8782 <P
>This is not tested yet. If the DHCP server require the dhcpHost
8783 entries to be in the dhcpGroup subtrees, the entries can be stored
8784 there instead of a common machines subtree, and the PowerDNS base
8785 would have to be moved one level up to the machine-info subtree.
</p
>
8787 <p
>The combined object under the machines subtree would look something
8788 like this:
</p
>
8790 <blockquote
><pre
>
8791 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
8794 objectClass: dhcpHost
8795 objectclass: domainrelatedobject
8796 objectclass: dnsDomainAux
8797 associateddomain: hostname.intern
8798 arecord:
10.11.12.13
8799 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
8800 dhcpStatements: fixed-address hostname.intern
8801 </pre
></blockquote
>
8803 </p
>One could even add the LTSP configuration associated with a given
8804 machine, as long as the required attributes are available in a
8805 auxiliary object class.
</p
>
8810 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
8811 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
8812 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
8813 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
8814 <description><p
>For a while now, I have wanted to find a way to change the DNS and
8815 DHCP services in Debian Edu to use the same LDAP objects for a given
8816 computer, to avoid the possibility of having a inconsistent state for
8817 a computer in LDAP (as in DHCP but no DNS entry or the other way
8818 around) and make it easier to add computers to LDAP.
</p
>
8820 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
8821 information finally found a solution that seem to work.
</p
>
8823 <p
>The old setup required three LDAP objects for a given computer.
8824 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
8825 we switch powerdns to use its strict LDAP method (ldap-method=strict
8826 in pdns-debian-edu.conf), the forward and reverse DNS entries are
8827 merged into one while making it impossible to transfer the reverse map
8828 to a slave DNS server.
</p
>
8830 <p
>If we also replace the object class used to get the DNS related
8831 attributes to one allowing these attributes to be combined with the
8832 dhcphost object class, we can merge the DNS and DHCP entries into one.
8833 I
've written such object class in the dnsdomainaux.schema file (need
8834 proper OIDs, but that is a minor issue), and tested the setup. It
8835 seem to work.
</p
>
8837 <p
>With this test setup in place, we can get away with one LDAP object
8838 for both DNS and DHCP, and even the LTSP configuration I suggested in
8839 an earlier email. The combined LDAP object will look something like
8842 <blockquote
><pre
>
8843 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
8845 objectClass: dhcphost
8846 objectclass: domainrelatedobject
8847 objectclass: dnsdomainaux
8848 associateddomain: hostname.intern
8849 arecord:
10.11.12.13
8850 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
8851 dhcpstatements: fixed-address hostname
8853 </pre
></blockquote
>
8855 <p
>The DNS server uses the associateddomain and arecord entries, while
8856 the DHCP server uses the dhcphwaddress and dhcpstatements entries
8857 before asking DNS to resolve the fixed-adddress. LTSP will use
8858 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
8860 <p
>I am not yet sure if I can get the DHCP server to look for its
8861 dhcphost in a different location, to allow us to put the objects
8862 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
8863 that. If I can
't figure out a way to do that, we can still get rid of
8864 the hosts subtree and move all its content into the DHCP Config tree
8865 (which probably should be renamed to be more related to the new
8866 content. I suspect cn=dnsdhcp,ou=services or something like that
8867 might be a good place to put it.
</p
>
8869 <p
>If you want to help out with implementing this for Debian Edu,
8870 please contact us on debian-edu@lists.debian.org.
</p
>
8875 <title>Idea for storing LTSP configuration in LDAP
</title>
8876 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
8877 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
8878 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
8879 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
8880 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
8881 clients, and that this can be used to fetch configuration from LDAP if
8882 Debian Edu choose to store configuration there.
</p
>
8884 <p
>Armed with this information, I got inspired and wrote a test module
8885 to get configuration from LDAP. The idea is to look up the MAC
8886 address of the client in LDAP, and look for attributes on the form
8887 ltspconfigsetting=value, and use this to export SETTING=value to the
8888 LTSP clients.
</p
>
8890 <p
>The goal is to be able to store the LTSP configuration attributes
8891 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
8892 allowing us to store all information about a computer in one place.
</p
>
8894 <p
>This is a untested draft implementation, and I welcome feedback on
8895 this approach. A real LDAP schema for the ltspClientAux objectclass
8896 need to be written. Comments, suggestions, etc?
</p
>
8898 <blockquote
><pre
>
8899 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
8901 # Fetch LTSP client settings from LDAP based on MAC address
8903 # Uses ethernet address as stored in the dhcpHost objectclass using
8904 # the dhcpHWAddress attribute or ethernet address stored in the
8905 # ieee802Device objectclass with the macAddress attribute.
8907 # This module is written to be schema agnostic, and only depend on the
8908 # existence of attribute names.
8910 # The LTSP configuration variables are saved directly using a
8911 # ltspConfig prefix and uppercasing the rest of the attribute name.
8912 # To set the SERVER variable, set the ltspConfigServer attribute.
8914 # Some LDAP schema should be created with all the relevant
8915 # configuration settings. Something like this should work:
8917 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
8920 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
8922 LDAPSERVER=$(debian-edu-ldapserver)
8923 if [
"$LDAPSERVER
" ] ; then
8924 LDAPBASE=$(debian-edu-ldapserver -b)
8925 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
8926 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
8927 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
8928 grep
'^ltspConfig
' | while read attr value ; do
8929 # Remove prefix and convert to upper case
8930 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
8931 # bass value on to clients
8932 eval
"$attr=$value; export $attr
"
8936 </pre
></blockquote
>
8938 <p
>I
'm not sure this shell construction will work, because I suspect
8939 the while block might end up in a subshell causing the variables set
8940 there to not show up in ltsp-config, but if that is the case I am sure
8941 the code can be restructured to make sure the variables are passed on.
8942 I expect that can be solved with some testing. :)
</p
>
8944 <p
>If you want to help out with implementing this for Debian Edu,
8945 please contact us on debian-edu@lists.debian.org.
</p
>
8947 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
8948 configuration in LDAP that was created around year
2000 by
8949 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
8950 Xperience, Inc.,
2000</a
>. I found its
8951 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
8952 personal home page over at redhat.com.
</p
>
8957 <title>jXplorer, a very nice LDAP GUI
</title>
8958 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
8959 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
8960 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
8961 <description><p
>Since
8962 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
8963 last post
</a
> about available LDAP tools in Debian, I was told about a
8964 LDAP GUI that is even better than luma. The java application
8965 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
8966 moving LDAP objects and subtrees using drag-and-drop, and can
8967 authenticate using Kerberos. I have only tested the Kerberos
8968 authentication, but do not have a LDAP setup allowing me to rewrite
8969 LDAP with my test user yet. It is
8970 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
8971 Debian
</a
> testing and unstable at the moment. The only problem I
8972 have with it is how it handle errors. If something go wrong, its
8973 non-intuitive behaviour require me to go through some query work list
8974 and remove the failing query. Nothing big, but very annoying.
</p
>
8979 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
8980 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
8981 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
8982 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
8983 <description><p
>Here is a short update on my
<a
8984 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
8985 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
8986 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
8987 not reporting the status for KDE, because the upgrade crashes when
8988 aptitude try because of missing conflicts
8989 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
8990 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
8992 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
8993 complete list of the installed packages. Based on this I see these
8994 differences when I did a test run today. As usual, I do not really
8995 know what the correct set of packages would be, but thought it best to
8996 publish the difference.
</p
>
8998 <p
>Installed using apt-get, missing with aptitude
</p
>
9000 <blockquote
><p
>
9001 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
9002 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
9003 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
9004 libgtksourceview-common libpt-
1.10.10-plugins-alsa
9005 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
9006 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
9007 python-
4suite-xml python-eggtrayicon python-gtkhtml2
9008 python-gtkmozembed svgalibg1 xserver-xephyr zip
9009 </p
></blockquote
>
9011 <p
>Installed using apt-get, removed with aptitude
</p
>
9013 <blockquote
><p
>
9014 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
9015 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
9016 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
9017 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
9018 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
9019 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
9020 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
9021 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
9022 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
9023 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
9024 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
9025 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
9026 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
9027 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
9028 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
9029 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
9030 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
9031 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
9032 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
9033 mysql-common swfdec-gnome totem-gstreamer wodim
9034 </p
></blockquote
>
9036 <p
>Installed using aptitude, missing with apt-get
</p
>
9038 <blockquote
><p
>
9039 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
9040 python-gnomekeyring python-wnck rhythmbox-plugins xorg
9041 xserver-xorg-input-all xserver-xorg-input-evdev
9042 xserver-xorg-input-kbd xserver-xorg-input-mouse
9043 xserver-xorg-input-synaptics xserver-xorg-video-all
9044 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
9045 xserver-xorg-video-chips xserver-xorg-video-cirrus
9046 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9047 xserver-xorg-video-glint xserver-xorg-video-i128
9048 xserver-xorg-video-i740 xserver-xorg-video-mach64
9049 xserver-xorg-video-mga xserver-xorg-video-neomagic
9050 xserver-xorg-video-nouveau xserver-xorg-video-nv
9051 xserver-xorg-video-r128 xserver-xorg-video-radeon
9052 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
9053 xserver-xorg-video-s3 xserver-xorg-video-s3virge
9054 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
9055 xserver-xorg-video-sis xserver-xorg-video-sisusb
9056 xserver-xorg-video-tdfx xserver-xorg-video-tga
9057 xserver-xorg-video-trident xserver-xorg-video-tseng
9058 xserver-xorg-video-vesa xserver-xorg-video-vmware
9059 xserver-xorg-video-voodoo
9060 </p
></blockquote
>
9062 <p
>Installed using aptitude, removed with apt-get
</p
>
9064 <blockquote
><p
>
9065 deskbar-applet xserver-xorg xserver-xorg-core
9066 xserver-xorg-input-wacom xserver-xorg-video-intel
9067 xserver-xorg-video-openchrome
9068 </p
></blockquote
>
9070 <p
>I was told on IRC that the xorg-xserver package was
9071 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
9072 in git
</a
> today to try to get apt-get to not remove xorg completely.
9073 No idea when it hits Squeeze, but when it does I hope it will reduce
9074 the difference somewhat.
9079 <title>LUMA, a very nice LDAP GUI
</title>
9080 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
9081 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
9082 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
9083 <description><p
>The last few days I have been looking into the status of the LDAP
9084 directory in Debian Edu, and in the process I started to miss a GUI
9085 tool to browse the LDAP tree. The only one I was able to find in
9086 Debian/Squeeze and Lenny is
9087 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
9088 be a great tool to get a overview of the current LDAP directory
9089 populated by default in Skolelinux. Thanks to it, I have been able to
9090 find empty and obsolete subtrees, misplaced objects and duplicate
9091 objects. It will be installed by default in Debian/Squeeze. If you
9092 are working with LDAP, give it a go. :)
</p
>
9094 <p
>I did notice one problem with it I have not had time to report to
9095 the BTS yet. There is no .desktop file in the package, so the tool do
9096 not show up in the Gnome and KDE menus, but only deep down in in the
9097 Debian submenu in KDE. I hope that can be fixed before Squeeze is
9100 <p
>I have not yet been able to get it to modify the tree yet. I would
9101 like to move objects and remove subtrees directly in the GUI, but have
9102 not found a way to do that with LUMA yet. So in the mean time, I use
9103 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
9105 <p
>If you have tips on other GUI tools for LDAP that might be useful
9106 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
9108 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
9109 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
9110 useful GUI alternative. It seem like a good tool, but is unmaintained
9111 in Debian and got a RC bug keeping it out of Squeeze. Unless that
9112 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
9117 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
9118 <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>
9119 <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>
9120 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
9121 <description><p
>A while back, I
9122 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
9123 about the fact
</a
> that it is not possible with the provided schemas
9124 for storing DNS and DHCP information in LDAP to combine the two sets
9125 of information into one LDAP object representing a computer.
</p
>
9127 <p
>In the mean time, I discovered that a simple fix would be to make
9128 the dhcpHost object class auxiliary, to allow it to be combined with
9129 the dNSDomain object class, and thus forming one object for one
9130 computer when storing both DHCP and DNS information in LDAP.
</p
>
9132 <p
>If I understand this correctly, it is not safe to do this change
9133 without also changing the assigned number for the object class, and I
9134 do not know enough about LDAP schema design to do that properly for
9135 Debian Edu.
</p
>
9137 <p
>Anyway, for future reference, this is how I believe we could change
9139 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
9140 schema
</a
> to solve at least part of the problem with the LDAP schemas
9141 available today from IETF.
</p
>
9144 --- dhcp.schema (revision
65192)
9145 +++ dhcp.schema (working copy)
9147 objectclass (
2.16.840.1.113719.1.203.6.6
9148 NAME
'dhcpHost
'
9149 DESC
'This represents information about a particular client
'
9153 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
9154 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
9157 <p
>I very much welcome clues on how to do this properly for Debian
9158 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
9159 package, and should thus be free to rewrite it as we see fit.
</p
>
9161 <p
>If you want to help out with implementing this for Debian Edu,
9162 please contact us on debian-edu@lists.debian.org.
</p
>
9167 <title>Calling tasksel like the installer, while still getting useful output
</title>
9168 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
9169 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
9170 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
9171 <description><p
>A few times I have had the need to simulate the way tasksel
9172 installs packages during the normal debian-installer run. Until now,
9173 I have ended up letting tasksel do the work, with the annoying problem
9174 of not getting any feedback at all when something fails (like a
9175 conffile question from dpkg or a download that fails), using code like
9178 <blockquote
><pre
>
9179 export DEBIAN_FRONTEND=noninteractive
9180 tasksel --new-install
9181 </pre
></blockquote
>
9183 This would invoke tasksel, let its automatic task selection pick the
9184 tasks to install, and continue to install the requested tasks without
9185 any output what so ever.
9187 Recently I revisited this problem while working on the automatic
9188 package upgrade testing, because tasksel would some times hang without
9189 any useful feedback, and I want to see what is going on when it
9190 happen. Then it occured to me, I can parse the output from tasksel
9191 when asked to run in test mode, and use that aptitude command line
9192 printed by tasksel then to simulate the tasksel run. I ended up using
9195 <blockquote
><pre
>
9196 export DEBIAN_FRONTEND=noninteractive
9197 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
9199 </pre
></blockquote
>
9201 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
9202 --without-recommends -o APT::Install-Recommends=no -y install
9203 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
9204 ~pimportant
</tt
>", which will install the gnome desktop task, the
9205 laptop task and all packages with priority standard , required and
9206 important, just like tasksel would have done it during
9207 installation.
</p
>
9209 <p
>A better approach is probably to extend tasksel to be able to
9210 install packages without using debconf-apt-progress, for use cases
9211 like this.
</p
>
9216 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
9217 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
9218 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
9219 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
9220 <description><p
>My
9221 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
9222 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
9223 finally made the upgrade logs available from
9224 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
9225 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
9226 apt and aptitude, and found their differences interesting. This time
9227 I will only focus on their removal plans.
</p
>
9229 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
9230 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
9231 surprising part is that it want to remove xorg and all
9232 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
9233 sure why. When asking aptitude to do the same, it want to remove
129
9234 packages, but most of them are library packages I suspect are no
9235 longer needed. Both of them want to remove bluetooth packages, which
9236 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
9238 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
9239 which seem like a bad idea and xorg the same way as with Gnome. Asking
9240 aptitude for the same, it wants to remove
192 packages, none which are
9241 too surprising.
</p
>
9243 <p
>I guess the removal of xorg during upgrades should be investigated
9244 and avoided, and perhaps others as well. Here are the complete list
9245 of planned removals. The complete logs is available from the URL
9246 above. Note if you want to repeat these tests, that the upgrade test
9247 for kde+apt-get hung in the tasksel setup because of dpkg asking
9248 conffile questions. No idea why. I worked around it by using
9249 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
9252 <p
><b
>apt-get gnome
72</b
>
9253 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
9254 gnome-desktop-environment gnome-network-admin gtkhtml3.14
9255 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
9256 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
9257 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
9258 serpentine swfdec-mozilla update-manager xorg xserver-xorg
9259 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9260 xserver-xorg-input-kbd xserver-xorg-input-mouse
9261 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9262 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9263 xserver-xorg-video-ati xserver-xorg-video-chips
9264 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9265 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9266 xserver-xorg-video-glint xserver-xorg-video-i128
9267 xserver-xorg-video-i740 xserver-xorg-video-imstt
9268 xserver-xorg-video-intel xserver-xorg-video-mach64
9269 xserver-xorg-video-mga xserver-xorg-video-neomagic
9270 xserver-xorg-video-nsc xserver-xorg-video-nv
9271 xserver-xorg-video-openchrome xserver-xorg-video-r128
9272 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9273 xserver-xorg-video-rendition xserver-xorg-video-s3
9274 xserver-xorg-video-s3virge xserver-xorg-video-savage
9275 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9276 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9277 xserver-xorg-video-tga xserver-xorg-video-trident
9278 xserver-xorg-video-tseng xserver-xorg-video-v4l
9279 xserver-xorg-video-vesa xserver-xorg-video-vga
9280 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
9281 xulrunner-
1.9-gnome-support
</p
>
9283 <p
><b
>aptitude gnome
129</b
>
9285 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
9286 djvulibre-desktop finger gnome-app-install gnome-mount
9287 gnome-network-admin gnome-spell gnome-vfs-obexftp
9288 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
9289 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
9290 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
9291 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
9292 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
9293 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
9294 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
9295 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
9296 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
9297 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
9298 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
9299 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
9300 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
9301 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
9302 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
9303 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
9304 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
9305 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
9306 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
9307 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
9308 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
9309 openoffice.org-writer2latex openssl-blacklist p7zip
9310 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
9311 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
9312 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
9313 swfdec-mozilla totem-gstreamer update-manager wodim
9314 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9315 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9318 <p
><b
>apt-get kde
82</b
>
9320 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
9321 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
9322 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
9323 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
9324 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
9325 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
9326 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
9327 xserver-xorg-input-kbd xserver-xorg-input-mouse
9328 xserver-xorg-input-synaptics xserver-xorg-input-wacom
9329 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
9330 xserver-xorg-video-ati xserver-xorg-video-chips
9331 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
9332 xserver-xorg-video-dummy xserver-xorg-video-fbdev
9333 xserver-xorg-video-glint xserver-xorg-video-i128
9334 xserver-xorg-video-i740 xserver-xorg-video-imstt
9335 xserver-xorg-video-intel xserver-xorg-video-mach64
9336 xserver-xorg-video-mga xserver-xorg-video-neomagic
9337 xserver-xorg-video-nsc xserver-xorg-video-nv
9338 xserver-xorg-video-openchrome xserver-xorg-video-r128
9339 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
9340 xserver-xorg-video-rendition xserver-xorg-video-s3
9341 xserver-xorg-video-s3virge xserver-xorg-video-savage
9342 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
9343 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
9344 xserver-xorg-video-tga xserver-xorg-video-trident
9345 xserver-xorg-video-tseng xserver-xorg-video-v4l
9346 xserver-xorg-video-vesa xserver-xorg-video-vga
9347 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
9349 <p
><b
>aptitude kde
192</b
>
9350 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
9351 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
9352 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
9353 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
9354 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
9355 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
9356 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
9357 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
9358 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
9359 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
9360 kghostview khelpcenter khexedit kiconedit kitchensync klatin
9361 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
9362 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
9363 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
9364 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
9365 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
9366 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
9367 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
9368 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
9369 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
9370 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
9371 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
9372 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
9373 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
9374 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
9375 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
9376 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
9377 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
9378 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
9379 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
9380 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
9381 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
9382 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
9383 texlive-common texlive-doc-base texlive-fonts-recommended
9384 xserver-xorg-video-cyrix xserver-xorg-video-imstt
9385 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
9386 xulrunner-
1.9</p
>
9392 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
9393 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
9394 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
9395 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
9396 <description><p
>The last few days I have done some upgrade testing in Debian, to
9397 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
9398 have been discovered and reported in the process
9399 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
9400 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
9401 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
9402 kdebase-workspace-data), and to get a more regular testing going on, I
9403 am working on a script to automate the test.
</p
>
9405 <p
>The idea is to create a Lenny chroot and use tasksel to install a
9406 Gnome or KDE desktop installation inside the chroot before upgrading
9407 it. To ensure no services are started in the chroot, a policy-rc.d
9408 script is inserted. To make sure tasksel believe it is to install a
9409 desktop on a laptop, the tasksel tests are replaced in the chroot
9410 (only acceptable because this is a throw-away chroot).
</p
>
9412 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
9413 currently always fail because udev refuses to upgrade with the kernel
9414 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
9415 is created. The bug report
9416 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
9417 this problem do not trigger in a chroot, but I touch the file anyway
9418 to make sure the upgrade go well. Testing on virtual and real
9419 hardware have failed me because of udev so far, and creating this file
9420 do the trick in such settings anyway. This is a
9421 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
9422 issue
</a
> and the current udev behaviour is intended by the udev
9423 maintainer because he lack the resources to rewrite udev to keep
9424 working with old kernels or something like that. I really wish the
9425 udev upstream would keep udev backwards compatible, to avoid such
9426 upgrade problem, but given that they fail to do so, I guess
9427 documenting the way out of this mess is the best option we got for
9428 Debian Squeeze.
</p
>
9430 <p
>Anyway, back to the task at hand, testing upgrades. This test
9431 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
9434 <blockquote
><pre
>
9438 if [
"$
1" ] ; then
9447 exec
&lt; /dev/null
9449 mirror=http://ftp.skolelinux.org/debian
9450 tmpdir=chroot-$from-upgrade-$to-$desktop
9452 debootstrap $from $tmpdir $mirror
9453 chroot $tmpdir aptitude update
9454 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
9458 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
9462 mount -t proc proc $tmpdir/proc
9463 # Make sure proc is unmounted also on failure
9464 trap exit_cleanup EXIT INT
9466 chroot $tmpdir aptitude -y install debconf-utils
9468 # Make sure tasksel autoselection trigger. It need the test scripts
9469 # to return the correct answers.
9470 echo tasksel tasksel/desktop multiselect $desktop | \
9471 chroot $tmpdir debconf-set-selections
9473 # Include the desktop and laptop task
9474 for test in desktop laptop ; do
9475 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
9479 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
9482 DEBIAN_FRONTEND=noninteractive
9483 DEBIAN_PRIORITY=critical
9484 export DEBIAN_FRONTEND DEBIAN_PRIORITY
9485 chroot $tmpdir tasksel --new-install
9487 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
9488 chroot $tmpdir aptitude update
9489 touch $tmpdir/etc/udev/kernel-upgrade
9490 chroot $tmpdir aptitude -y dist-upgrade
9492 </pre
></blockquote
>
9494 <p
>I suspect it would be useful to test upgrades with both apt-get and
9495 with aptitude, but I have not had time to look at how they behave
9496 differently so far. I hope to get a cron job running to do the test
9497 regularly and post the result on the web. The Gnome upgrade currently
9498 work, while the KDE upgrade fail because of the bug in
9499 kdebase-workspace-data
</p
>
9501 <p
>I am not quite sure what kind of extract from the huge upgrade logs
9502 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
9503 post, so I will refrain from trying. I can report that for Gnome,
9504 aptitude report
760 packages upgraded,
448 newly installed,
129 to
9505 remove and
1 not upgraded and
1024MB need to be downloaded while for
9506 KDE the same numbers are
702 packages upgraded,
507 newly installed,
9507 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
9509 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
9510 is able to migrate to dependency based boot sequencing and parallel
9511 booting without a hitch. Was unsure if there were still bugs with
9512 packages failing to clean up their obsolete init.d script during
9513 upgrades, and no such problem seem to affect the Gnome desktop+laptop
9519 <title>Upstart or sysvinit - as init.d scripts see it
</title>
9520 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
9521 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
9522 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
9523 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
9524 scripts to migrate (some of) their operations to upstart job while
9525 keeping the init.d for hurd and kfreebsd. The packages with such
9526 needs will need a way to get their init.d scripts to behave
9527 differently when used with sysvinit and with upstart. Because of
9528 this, I had a look at the environment variables set when a init.d
9529 script is running under upstart, and when it is not.
</p
>
9531 <p
>With upstart, I notice these environment variables are set when a
9532 script is started from rcS.d/ (ignoring some irrelevant ones like
9535 <blockquote
><pre
>
9541 UPSTART_EVENTS=startup
9543 UPSTART_JOB=rc-sysinit
9544 </pre
></blockquote
>
9546 <p
>With sysvinit, these environment variables are set for the same
9549 <blockquote
><pre
>
9550 INIT_VERSION=sysvinit-
2.88
9555 </pre
></blockquote
>
9557 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
9558 sysvinit are not set by upstart. Not sure if it is intentional or not
9559 to not be compatible with sysvinit in this regard.
</p
>
9561 <p
>For scripts needing to behave differently when upstart is used,
9562 looking for the UPSTART_JOB environment variable seem to be a good
9568 <title>A manual for standards wars...
</title>
9569 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
9570 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
9571 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
9572 <description><p
>Via the
9573 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
9574 of Rob Weir
</a
> I came across the very interesting essay named
9575 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
9576 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
9577 following the standards wars of today.
</p
>
9582 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
9583 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
9584 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
9585 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
9586 <description><p
>When using sitesummary at a site to track machines, it is possible
9587 to get a list of the machine types in use thanks to the DMI
9588 information extracted from each machine. The script to do so is
9589 included in the sitesummary package, and here is example output from
9590 the Skolelinux build servers:
</p
>
9592 <blockquote
><pre
>
9593 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
9595 Dell Computer Corporation
1
9598 eserver xSeries
345 -[
8670M1X]-
1
9602 </pre
></blockquote
>
9604 <p
>The quality of the report depend on the quality of the DMI tables
9605 provided in each machine. Here there are Intel machines without model
9606 information listed with Intel as vendor and no model, and virtual Xen
9607 machines listed as [no-dmi-info]. One can add -l as a command line
9608 option to list the individual machines.
</p
>
9610 <p
>A larger list is
9611 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
9612 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
9613 provide the basic sitesummary report publicly. In their report there
9614 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
9615 their machines, and as sitesummary is available in both distributions,
9616 it is trivial to get all of them to report to the same central
9617 collector.
</p
>
9622 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
9623 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
9624 <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>
9625 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
9626 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
9627 start at boot when an NVidia video card is used is handled. The
9628 problem seem to be that the nvidia X.org driver uses a long time to
9629 initialize, and this duration is longer than kdm is configured to
9632 <p
>I came across two bugs related to this issue,
9633 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
9634 against initscripts and passed on to nvidia-glx when it became obvious
9635 that the nvidia drivers were involved, and
9636 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
9637 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
9639 <p
>To me, it seem that no-one is interested in actually solving the
9640 problem nvidia video card owners experience and make sure the Debian
9641 distribution work out of the box for these users. The nvidia driver
9642 maintainers expect kdm to be set up to wait longer, while kdm expect
9643 the nvidia driver maintainers to fix the driver to start faster, and
9644 while they wait for each other I guess the users end up switching to a
9645 distribution that work for them. I have no idea what the solution is,
9646 but I am pretty sure that waiting for each other is not it.
</p
>
9648 <p
>I wonder why we end up handling bugs this way.
</p
>
9653 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
9654 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
9655 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
9656 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
9657 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
9658 The feature seem to hold up pretty well, but three fairly serious
9659 issues are known and should be solved:
9663 <li
>The wicd package seen to
9664 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
9665 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
9666 parallel booting is enabled. No idea why, but the wicd maintainer
9667 seem to be on the case.
</li
>
9669 <li
>The nvidia X driver seem to
9670 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
9671 triggered more easily when parallel booting is in effect. The
9672 maintainer is on the case.
</li
>
9674 <li
>The sysv-rc package fail to properly enable dependency based boot
9675 sequencing (the shutdown is broken) when old file-rc users
9676 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
9677 sysv-rc. One way to solve it would be for file-rc to create
9678 /etc/init.d/.legacy-bootordering, and another is to try to make
9679 sysv-rc more robust. Will investigate some more and probably upload a
9680 workaround in sysv-rc to help those trying to move from file-rc to
9681 sysv-rc get a working shutdown.
</li
>
9683 </ul
></p
>
9685 <p
>All in all not many surprising issues, and all of them seem
9686 solvable before Squeeze is released. In addition to these there are
9687 some packages with bugs in their dependencies and run level settings,
9688 which I expect will be fixed in a reasonable time span.
</p
>
9690 <p
>If you report any problems with dependencies in init.d scripts to
9691 the BTS, please usertag the report to get it to show up at
9692 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9693 list of usertagged bugs related to this
</a
>.
</p
>
9695 <p
>Update: Correct bug number to file-rc issue.
</p
>
9700 <title>More flexible firmware handling in debian-installer
</title>
9701 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
9702 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
9703 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
9704 <description><p
>After a long break from debian-installer development, I finally
9705 found time today to return to the project. Having to spend less time
9706 working dependency based boot in debian, as it is almost complete now,
9707 definitely helped freeing some time.
</p
>
9709 <p
>A while back, I ran into a problem while working on Debian Edu. We
9710 include some firmware packages on the Debian Edu CDs, those needed to
9711 get disk and network controllers working. Without having these
9712 firmware packages available during installation, it is impossible to
9713 install Debian Edu on the given machine, and because our target group
9714 are non-technical people, asking them to provide firmware packages on
9715 an external medium is a support pain. Initially, I expected it to be
9716 enough to include the firmware packages on the CD to get
9717 debian-installer to find and use them. This proved to be wrong.
9718 Next, I hoped it was enough to symlink the relevant firmware packages
9719 to some useful location on the CD (tried /cdrom/ and
9720 /cdrom/firmware/). This also proved to not work, and at this point I
9721 found time to look at the debian-installer code to figure out what was
9722 going to work.
</p
>
9724 <p
>The firmware loading code is in the hw-detect package, and a closer
9725 look revealed that it would only look for firmware packages outside
9726 the installation media, so the CD was never checked for firmware
9727 packages. It would only check USB sticks, floppies and other
9728 "external
" media devices. Today I changed it to also look in the
9729 /cdrom/firmware/ directory on the mounted CD or DVD, which should
9730 solve the problem I ran into with Debian edu. I also changed it to
9731 look in /firmware/, to make sure the installer also find firmware
9732 provided in the initrd when booting the installer via PXE, to allow us
9733 to provide the same feature in the PXE setup included in Debian
9736 <p
>To make sure firmware deb packages with a license questions are not
9737 activated without asking if the license is accepted, I extended
9738 hw-detect to look for preinst scripts in the firmware packages, and
9739 run these before activating the firmware during installation. The
9740 license question is asked using debconf in the preinst, so this should
9741 solve the issue for the firmware packages I have looked at so far.
</p
>
9743 <p
>If you want to discuss the details of these features, please
9744 contact us on debian-boot@lists.debian.org.
</p
>
9749 <title>Parallellized boot is now the default in Debian/unstable
</title>
9750 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
9751 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
9752 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
9753 <description><p
>Since this evening, parallel booting is the default in
9754 Debian/unstable for machines using dependency based boot sequencing.
9755 Apparently the testing of concurrent booting has been wider than
9756 expected, if I am to believe the
9757 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9758 on debian-devel@
</a
>, and I concluded a few days ago to move forward
9759 with the feature this weekend, to give us some time to detect any
9760 remaining problems before Squeeze is frozen. If serious problems are
9761 detected, it is simple to change the default back to sequential boot.
9762 The upload of the new sysvinit package also activate a new upstream
9765 More information about
9766 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9767 based boot sequencing
</a
> is available from the Debian wiki. It is
9768 currently possible to disable parallel booting when one run into
9769 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
9771 <blockquote
><pre
>
9773 </pre
></blockquote
>
9775 <p
>If you report any problems with dependencies in init.d scripts to
9776 the BTS, please usertag the report to get it to show up at
9777 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9778 list of usertagged bugs related to this
</a
>.
</p
>
9783 <title>Sitesummary tip: Listing MAC address of all clients
</title>
9784 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
9785 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
9786 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
9787 <description><p
>In the recent Debian Edu versions, the
9788 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
9789 system
</a
> is used to keep track of the machines in the school
9790 network. Each machine will automatically report its status to the
9791 central server after boot and once per night. The network setup is
9792 also reported, and using this information it is possible to get the
9793 MAC address of all network interfaces in the machines. This is useful
9794 to update the DHCP configuration.
</p
>
9796 <p
>To give some idea how to use sitesummary, here is a one-liner to
9797 ist all MAC addresses of all machines reporting to sitesummary. Run
9798 this on the collector host:
</p
>
9800 <blockquote
><pre
>
9801 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
9802 </pre
></blockquote
>
9804 <p
>This will list all MAC addresses assosiated with all machine, one
9805 line per machine and with space between the MAC addresses.
</p
>
9807 <p
>To allow system administrators easier job at adding static DHCP
9808 addresses for hosts, it would be possible to extend this to fetch
9809 machine information from sitesummary and update the DHCP and DNS
9810 tables in LDAP using this information. Such tool is unfortunately not
9811 written yet.
</p
>
9816 <title>systemd, an interesting alternative to upstart
</title>
9817 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
9818 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
9819 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
9820 <description><p
>The last few days a new boot system called
9821 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
9823 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
9825 to the free software world. I have not yet had time to play around
9826 with it, but it seem to be a very interesting alternative to
9827 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
9828 a good alternative for Debian when we are able to switch to an event
9829 based boot system. Tollef is
9830 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
9831 systemd into Debian, and I look forward to seeing how well it work. I
9832 like the fact that systemd handles init.d scripts with dependency
9833 information natively, allowing them to run in parallel where upstart
9834 at the moment do not.
</p
>
9836 <p
>Unfortunately do systemd have the same problem as upstart regarding
9837 platform support. It only work on recent Linux kernels, and also need
9838 some new kernel features enabled to function properly. This means
9839 kFreeBSD and Hurd ports of Debian will need a port or a different boot
9840 system. Not sure how that will be handled if systemd proves to be the
9841 way forward.
</p
>
9843 <p
>In the mean time, based on the
9844 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
9845 on debian-devel@
</a
> regarding parallel booting in Debian, I have
9846 decided to enable full parallel booting as the default in Debian as
9847 soon as possible (probably this weekend or early next week), to see if
9848 there are any remaining serious bugs in the init.d dependencies. A
9849 new version of the sysvinit package implementing this change is
9850 already in experimental. If all go well, Squeeze will be released
9851 with parallel booting enabled by default.
</p
>
9856 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
9857 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
9858 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
9859 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
9860 <description><p
>These days, the init.d script dependencies in Squeeze are quite
9861 complete, so complete that it is actually possible to run all the
9862 init.d scripts in parallell based on these dependencies. If you want
9863 to test your Squeeze system, make sure
9864 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9865 based boot sequencing
</a
> is enabled, and add this line to
9866 /etc/default/rcS:
</p
>
9868 <blockquote
><pre
>
9869 CONCURRENCY=makefile
9870 </pre
></blockquote
>
9872 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
9873 scripts in parallel using the dependency information stored in
9874 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
9875 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
9876 to try to start the kdm and gdm scripts as early as possible, and will
9877 start the facilities required by kdm or gdm as early as possible to
9878 make this happen.
</p
>
9880 <p
>Give it a try, and see if you like the result. If some services
9881 fail to start properly, it is most likely because they have incomplete
9882 init.d script dependencies in their startup script (or some of their
9883 dependent scripts have incomplete dependencies). Report bugs and get
9884 the package maintainers to fix it. :)
</p
>
9886 <p
>Running scripts in parallel could be the default in Debian when we
9887 manage to get the init.d script dependencies complete and correct. I
9888 expect we will get there in Squeeze+
1, if we get manage to test and
9889 fix the remaining issues.
</p
>
9891 <p
>If you report any problems with dependencies in init.d scripts to
9892 the BTS, please usertag the report to get it to show up at
9893 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
9894 list of usertagged bugs related to this
</a
>.
</p
>
9899 <title>Debian has switched to dependency based boot sequencing
</title>
9900 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
9901 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
9902 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
9903 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
9904 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
9905 have been migrated to using dependency based boot sequencing. This
9906 conclude work me and others have been doing for the last three days.
9907 It feels great to see this finally part of the default Debian
9908 installation. Now we just need to weed out the last few problems that
9909 are bound to show up, to get everything ready for Squeeze.
</p
>
9911 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
9912 fixing the more fundamental problem of handing the event based
9913 non-predictable kernel in the early boot.
</p
>
9918 <title>Taking over sysvinit development
</title>
9919 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
9920 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
9921 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
9922 <description><p
>After several years of frustration with the lack of activity from
9923 the existing sysvinit upstream developer, I decided a few weeks ago to
9924 take over the package and become the new upstream. The number of
9925 patches to track for the Debian package was becoming a burden, and the
9926 lack of synchronization between the distribution made it hard to keep
9927 the package up to date.
</p
>
9929 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
9930 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
9931 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
9932 and Fedora), based on the patches currently in use in these
9933 distributions. We Debian maintainers plan to move to this tarball as
9934 the new upstream as soon as we find time to do the merge. Since the
9935 new tarball was created, we agreed with Werner at SuSe to make a new
9936 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
9937 development there. The project is registered and currently waiting
9938 for approval by the Savannah administrators, and as soon as it is
9939 approved, we will import the old versions from svn and continue
9940 working on the future release.
</p
>
9942 <p
>It is a bit ironic that this is done now, when some of the involved
9943 distributions are moving to upstart as a syvinit replacement.
</p
>
9948 <title>Debian boots quicker and quicker
</title>
9949 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
9950 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
9951 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
9952 <description><p
>I spent Monday and tuesday this week in London with a lot of the
9953 people involved in the boot system on Debian and Ubuntu, to see if we
9954 could find more ways to speed up the boot system. This was an Ubuntu
9956 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
9957 gathering
</a
>. It was quite productive. We also discussed the future
9958 of boot systems, and ways to handle the increasing number of boot
9959 issues introduced by the Linux kernel becoming more and more
9960 asynchronous and event base. The Ubuntu approach using udev and
9961 upstart might be a good way forward. Time will show.
</p
>
9963 <p
>Anyway, there are a few ways at the moment to speed up the boot
9964 process in Debian. All of these should be applied to get a quick
9969 <li
>Use dash as /bin/sh.
</li
>
9971 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
9972 clock is in UTC.
</li
>
9974 <li
>Install and activate the insserv package to enable
9975 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
9976 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
9980 These points are based on the Google summer of code work done by
9981 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
9984 <p
>Support for makefile-style concurrency during boot was uploaded to
9985 unstable yesterday. When we tested it, we were able to cut
6 seconds
9986 from the boot sequence. It depend on very correct dependency
9987 declaration in all init.d scripts, so I expect us to find edge cases
9988 where the dependences in some scripts are slightly wrong when we start
9989 using this.
</p
>
9991 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
9992 introduced by Raphael Geissert today, one that could affect the
9993 startup speed as well. Instead of starting some scripts concurrently
9994 from rcS.d/ and another set of scripts from rc2.d/, it would be
9995 possible to run a of them in the same process. A quick way to test
9996 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
9997 insserv
'. Will need to test if that work. :)
</p
>
10002 <title>BSAs påstander om piratkopiering møter motstand
</title>
10003 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
10004 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
10005 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
10006 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
10007 programvareselskapene som Microsoft og Apple, publisert en rapport der
10008 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
10009 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
10011 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
10012 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
10013 dagene. Et spesielt interessant kommentar fra Sverige,
10014 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
10015 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
10018 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
10019 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
10020 företag.
"Man bör nog kanske inte se de här siffrorna som helt
10021 exakta
", säger BSAs Sverigechef John Hugosson.
10022 </blockquote
>
10024 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
10025 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
10026 piracy figures need a shot of reality
</a
> og
<a
10027 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
10028 Copyright Treaty Work?
</a
></p
>
10030 <p
>Fant lenkene via
<a
10031 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
10032 på Slashdot
</a
>.
</p
>
10037 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
10038 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
10039 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
10040 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
10041 <description><p
>Kom over
10042 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
10043 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
10044 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
10045 jobber til daglig. En rask opptelling forteller meg at vi har
490
10046 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
10047 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
10048 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
10053 <title>Kryptert harddisk - naturligvis
</title>
10054 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
10055 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
10056 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
10057 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
10058 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
10059 når en tar tap av arbeidstid, fortrolige dokumenter,
10060 personopplysninger og alt annet det innebærer. Det er ingen tvil om
10061 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
10062 til at jeg har kryptert harddisken på både kontormaskinen og min
10063 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
10064 komme på avveie, den første informasjon relatert til jobben min ved
10065 Universitetet i Oslo, og den andre relatert til blant annet
10066 foreningsarbeide. Kryptering av diskene gjør at det er lite
10067 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
10068 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
10069 og en reboot vil gjøre at de ber om passord før de vil starte opp.
10070 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
10071 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
10072 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
10073 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
10074 det er gjort slik jeg gjør det er minimale, og gevinstene er
10075 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
10076 maskinen reinstalleres og alt er tapt.
</p
>
10078 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
10079 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
10080 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
10081 er for min del høyere enn gevinsten. Jeg tror oddsene for at
10082 f.eks. etteretningsorganisasjoner har glede av å titte på mine
10083 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
10084 gjøre det vanskeligere for angripere med kompetanse og ressurser er
10085 betydelige.
</p
>
10090 <title>Two projects that have improved the quality of free software a lot
</title>
10091 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
10092 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
10093 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
10094 <description><p
>There are two software projects that have had huge influence on the
10095 quality of free software, and I wanted to mention both in case someone
10096 do not yet know them.
</p
>
10098 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
10099 tool to detect and expose errors in the memory handling of programs.
10100 It is easy to use, all one need to do is to run
'valgrind program
',
10101 and it will report any problems on stdout. It is even better if the
10102 program include debug information. With debug information, it is able
10103 to report the source file name and line number where the problem
10104 occurs. It can report things like
'reading past memory block in file
10105 X line N, the memory block was allocated in file Y, line M
', and
10106 'using uninitialised value in control logic
'. This tool has made it
10107 trivial to investigate reproducible crash bugs in programs, and have
10108 reduced the number of this kind of bugs in free software a lot.
10110 <p
>The second one is
10111 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
10112 a source code checker. It is able to process the source of a program
10113 and find problems in the logic without running the program. It
10114 started out as the Stanford Checker and became well known when it was
10115 used to find bugs in the Linux kernel. It is now a commercial tool
10116 and the company behind it is running
10117 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
10118 free software community, where a lot of free software projects get
10119 their source checked for free. Several thousand defects have been
10120 found and fixed so far. It can find errors like
'lock L taken in file
10121 X line N is never released if exiting in line M
', or
'the code in file
10122 Y lines O to P can never be executed
'. The projects included in the
10123 community service project have managed to get rid of a lot of
10124 reliability problems thanks to Coverity.
</p
>
10126 <p
>I believe tools like this, that are able to automatically find
10127 errors in the source, are vital to improve the quality of software and
10128 make sure we can get rid of the crashing and failing software we are
10129 surrounded by today.
</p
>
10134 <title>No patch is not better than a useless patch
</title>
10135 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
10136 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
10137 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
10138 <description><p
>Julien Blache
10139 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
10140 patch is better than a useless patch
</a
>. I completely disagree, as a
10141 patch allow one to discuss a concrete and proposed solution, and also
10142 prove that the issue at hand is important enough for someone to spent
10143 time on fixing it. No patch do not provide any of these positive
10144 properties.
</p
>
10149 <title>Standardize on protocols and formats, not vendors and applications
</title>
10150 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
10151 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
10152 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
10153 <description><p
>Where I work at the University of Oslo, one decision stand out as a
10154 very good one to form a long lived computer infrastructure. It is the
10155 simple one, lost by many in todays computer industry: Standardize on
10156 open network protocols and open exchange/storage formats, not applications.
10157 Applications come and go, while protocols and files tend to stay, and
10158 thus one want to make it easy to change application and vendor, while
10159 avoiding conversion costs and locking users to a specific platform or
10160 application.
</p
>
10162 <p
>This approach make it possible to replace the client applications
10163 independently of the server applications. One can even allow users to
10164 use several different applications as long as they handle the selected
10165 protocol and format. In the normal case, only one client application
10166 is recommended and users only get help if they choose to use this
10167 application, but those that want to deviate from the easy path are not
10168 blocked from doing so.
</p
>
10170 <p
>It also allow us to replace the server side without forcing the
10171 users to replace their applications, and thus allow us to select the
10172 best server implementation at any moment, when scale and resouce
10173 requirements change.
</p
>
10175 <p
>I strongly recommend standardizing - on open network protocols and
10176 open formats, but I would never recommend standardizing on a single
10177 application that do not use open network protocol or open formats.
</p
>
10182 <title>Returning from Skolelinux developer gathering
</title>
10183 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
10184 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
10185 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
10186 <description><p
>I
'm sitting on the train going home from this weekends Debian
10187 Edu/Skolelinux development gathering. I got a bit done tuning the
10188 desktop, and looked into the dynamic service location protocol
10189 implementation avahi. It look like it could be useful for us. Almost
10190 30 people participated, and I believe it was a great environment to
10191 get to know the Skolelinux system. Walter Bender, involved in the
10192 development of the Sugar educational platform, presented his stuff and
10193 also helped me improve my OLPC installation. He also showed me that
10194 his Turtle Art application can be used in standalone mode, and we
10195 agreed that I would help getting it packaged for Debian. As a
10196 standalone application it would be great for Debian Edu. We also
10197 tried to get the video conferencing working with two OLPCs, but that
10198 proved to be too hard for us. The application seem to need more work
10199 before it is ready for me. I look forward to getting home and relax
10205 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
10206 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
10207 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
10208 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
10209 <description><p
>The state of standardized LDAP schemas on Linux is far from
10210 optimal. There is RFC
2307 documenting one way to store NIS maps in
10211 LDAP, and a modified version of this normally called RFC
2307bis, with
10212 some modifications to be compatible with Active Directory. The RFC
10213 specification handle the content of a lot of system databases, but do
10214 not handle DNS zones and DHCP configuration.
</p
>
10216 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
10217 we would like to store information about users, SMB clients/hosts,
10218 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
10219 and LTSP configuration in LDAP. These objects have a lot in common,
10220 but with the current LDAP schemas it is not possible to have one
10221 object per entity. For example, one need to have at least three LDAP
10222 objects for a given computer, one with the SMB related stuff, one with
10223 DNS information and another with DHCP information. The schemas
10224 provided for DNS and DHCP are impossible to combine into one LDAP
10225 object. In addition, it is impossible to implement quick queries for
10226 netgroup membership, because of the way NIS triples are implemented.
10227 It just do not scale. I believe it is time for a few RFC
10228 specifications to cleam up this mess.
</p
>
10230 <p
>I would like to have one LDAP object representing each computer in
10231 the network, and this object can then keep the SMB (ie host key), DHCP
10232 (mac address/name) and DNS (name/IP address) settings in one place.
10233 It need to be efficently stored to make sure it scale well.
</p
>
10235 <p
>I would also like to have a quick way to map from a user or
10236 computer and to the net group this user or computer is a member.
</p
>
10238 <p
>Active Directory have done a better job than unix heads like myself
10239 in this regard, and the unix side need to catch up. Time to start a
10240 new IETF work group?
</p
>
10245 <title>Endelig er Debian Lenny gitt ut
</title>
10246 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
10247 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
10248 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
10249 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
10250 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
10251 Et langt steg videre for Debian-prosjektet, og en rekke nye
10252 programpakker blir nå tilgjengelig for de av oss som bruker den
10253 stabile utgaven av Debian. Neste steg er nå å få
10254 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
10255 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
10256 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
10257 slippes løs på skolene. Takk til alle debian-utviklerne som har
10258 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
10259 bootsekvens tilgjengelig i stabil utgave, vha pakken
10260 <tt
>insserv
</tt
>.
</p
>
10265 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
10266 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
10267 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
10268 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
10269 <description><p
>This weekend we had a small developer gathering for Debian Edu in
10270 Oslo. Most of Saturday was used for the general assemly for the
10271 member organization, but the rest of the weekend I used to tune the
10272 LTSP installation. LTSP now work out of the box on the
10-network.
10273 Acer Aspire One proved to be a very nice thin client, with both
10274 screen, mouse and keybard in a small box. Was working on getting the
10275 diskless workstation setup configured out of the box, but did not
10276 finish it before the weekend was up.
</p
>
10278 <p
>Did not find time to look at the
4 VGA cards in one box we got from
10279 the Brazilian group, so that will have to wait for the next
10280 development gathering. Would love to have the Debian Edu installer
10281 automatically detect and configure a multiseat setup when it find one
10282 of these cards.
</p
>
10287 <title>The sorry state of multimedia browser plugins in Debian
</title>
10288 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
10289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
10290 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
10291 <description><p
>Recently I have spent some time evaluating the multimedia browser
10292 plugins available in Debian Lenny, to see which one we should use by
10293 default in Debian Edu. We need an embedded video playing plugin with
10294 control buttons to pause or stop the video, and capable of streaming
10295 all the multimedia content available on the web. The test results and
10296 notes are available on
10297 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
10298 Debian wiki
</a
>. I was surprised how few of the plugins are able to
10299 fill this need. My personal video player favorite, VLC, has a really
10300 bad plugin which fail on a lot of the test pages. A lot of the MIME
10301 types I would expect to work with any free software player (like
10302 video/ogg), just do not work. And simple formats like the
10303 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
10304 totem and vlc plugins. I hope the situation will improve soon. No
10305 wonder sites use the proprietary Adobe flash to play video.
</p
>
10307 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
10308 be the only one fitting our needs. :/
</p
>